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 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.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 "ino64" 64-bit inode project has been committed, which extends
56 a number of types to 64 bits. In order to upgrade, carefully follow
57 the full procedure documented below under the heading "To rebuild
58 everything and install it on the current system." Specifically, a
59 reboot is required after installing the new kernel before installing
60 world. In addition, if using a custom kernel configuration ensure
61 that the COMPAT_FREEBSD11 option is included.
64 The NATM framework including the en(4), fatm(4), hatm(4), and
65 patm(4) devices has been removed. Consumers should plan a
66 migration before the end-of-life date for FreeBSD 11.
69 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
70 diff has not been implemented, if those are needed a newer version of
71 GNU diff is available via the diffutils package under the gdiff name.
74 As of r316810 for ipfilter, keep frags is no longer assumed when
75 keep state is specified in a rule. r316810 aligns ipfilter with
76 documentation in man pages separating keep frags from keep state.
77 This allows keep state to be specified without forcing keep frags
78 and allows keep frags to be specified independently of keep state.
79 To maintain previous behaviour, also specify keep frags with
80 keep state (as documented in ipf.conf.5).
83 arm64 builds now use the base system LLD 4.0.0 linker by default,
84 instead of requiring that the aarch64-binutils port or package be
85 installed. To continue using aarch64-binutils, set
86 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
89 The UDP optimization in entry 20160818 that added the sysctl
90 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
91 packets will no longer be treated as L3 broadcast packets.
94 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
95 use any explicitly assigned loopback address available in the jail
96 instead of using the first assigned address of the jail.
99 The ctl.ko module no longer implements the iSCSI target frontend:
100 cfiscsi.ko does instead.
102 If building cfiscsi.ko as a kernel module, the module can be loaded
103 via one of the following methods:
104 - `cfiscsi_load="YES"` in loader.conf(5).
105 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
106 - ctladm(8)/ctld(8), when compiled with iSCSI support
107 (`WITH_ISCSI=yes` in src.conf(5))
109 Please see cfiscsi(4) for more details.
112 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
113 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
114 same source (previously, the dependency of mmcsd.ko on mmc.ko was
115 missing, but mmcsd.ko now will refuse to load if it is incompatible
119 The syntax of ipfw(8) named states was changed to avoid ambiguity.
120 If you have used named states in the firewall rules, you need to modify
121 them after installworld and before rebooting. Now named states must
122 be prefixed with colon.
125 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
126 removed as the userland we provide cannot use them. The KMS version
127 (sys/dev/drm2) supports the same hardware.
130 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
131 Please see the 20141231 entry below for information about prerequisites
132 and upgrading, if you are not already using clang 3.5.0 or higher.
135 The code that provides support for ZFS .zfs/ directory functionality
136 has been reimplemented. It's not possible now to create a snapshot
137 by mkdir under .zfs/snapshot/. That should be the only user visible
141 EISA bus support has been removed. The WITH_EISA option is no longer
145 MCA bus support has been removed.
148 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
149 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
152 The EM_MULTIQUEUE kernel configuration option is deprecated now that
153 the em(4) driver conforms to iflib specifications.
156 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
157 IFLIB. If you have a custom kernel configuration that excludes em(4)
158 but you use igb(4), you need to re-add em(4) to your custom configuration.
161 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
162 Please see the 20141231 entry below for information about prerequisites
163 and upgrading, if you are not already using clang 3.5.0 or higher.
166 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
167 Please see the 20141231 entry below for information about prerequisites
168 and upgrading, if you are not already using clang 3.5.0 or higher.
171 The layout of the pmap structure has changed for powerpc to put the pmap
172 statistics at the front for all CPU variations. libkvm(3) and all tools
173 that link against it need to be recompiled.
176 isl(4) and cyapa(4) drivers now require a new driver,
177 chromebook_platform(4), to work properly on Chromebook-class hardware.
178 On other types of hardware the drivers may need to be configured using
179 device hints. Please see the corresponding manual pages for details.
182 The urtwn(4) driver was merged into rtwn(4) and now consists of
183 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
185 Also, firmware for RTL8188CE was renamed due to possible name
186 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
189 GNU rcs has been removed from base. It is available as packages:
190 - rcs: Latest GPLv3 GNU rcs version.
191 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
195 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
196 modules now requires that the kernel configuration contain the
197 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
200 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
201 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
204 Relocatable object files with the extension of .So have been renamed
205 to use an extension of .pico instead. The purpose of this change is
206 to avoid a name clash with shared libraries on case-insensitive file
207 systems. On those file systems, foo.So is the same file as foo.so.
210 GNU rcs has been turned off by default. It can (temporarily) be built
211 again by adding WITH_RCS knob in src.conf.
212 Otherwise, GNU rcs is available from packages:
213 - rcs: Latest GPLv3 GNU rcs version.
214 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
217 The backup_uses_rcs functionality has been removed from rc.subr.
220 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
221 two separate components, QUEUE_MACRO_DEBUG_TRACE and
222 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
223 QUEUE_MACRO_DEBUG behavior.
226 r304787 changed some ioctl interfaces between the iSCSI userspace
227 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
228 rebuilt to work with new kernels. __FreeBSD_version has been bumped
232 The UDP receive code has been updated to only treat incoming UDP
233 packets that were addressed to an L2 broadcast address as L3
234 broadcast packets. It is not expected that this will affect any
235 standards-conforming UDP application. The new behaviour can be
236 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
240 Remove the openbsd_poll system call.
241 __FreeBSD_version has been bumped because of this.
244 The libc stub for the pipe(2) system call has been replaced with
245 a wrapper that calls the pipe2(2) system call and the pipe(2)
246 system call is now only implemented by the kernels that include
247 "options COMPAT_FREEBSD10" in their config file (this is the
248 default). Users should ensure that this option is enabled in
249 their kernel or upgrade userspace to r302092 before upgrading their
253 CAM will now strip leading spaces from SCSI disks' serial numbers.
254 This will affect users who create UFS filesystems on SCSI disks using
255 those disk's diskid device nodes. For example, if /etc/fstab
256 previously contained a line like
257 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
258 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
259 transforms like gmirror may also be affected. ZFS users should
263 The bitstring(3) API has been updated with new functionality and
264 improved performance. But it is binary-incompatible with the old API.
265 Objects built with the new headers may not be linked against objects
266 built with the old headers.
269 The brk and sbrk functions have been removed from libc on arm64.
270 Binutils from ports has been updated to not link to these
271 functions and should be updated to the latest version before
272 installing a new libc.
275 The armv6 port now defaults to hard float ABI. Limited support
276 for running both hardfloat and soft float on the same system
277 is available using the libraries installed with -DWITH_LIBSOFT.
278 This has only been tested as an upgrade path for installworld
279 and packages may fail or need manual intervention to run. New
280 packages will be needed.
282 To update an existing self-hosted armv6hf system, you must add
283 TARGET_ARCH=armv6 on the make command line for both the build
284 and the install steps.
287 Kernel modules compiled outside of a kernel build now default to
288 installing to /boot/modules instead of /boot/kernel. Many kernel
289 modules built this way (such as those in ports) already overrode
290 KMODDIR explicitly to install into /boot/modules. However,
291 manually building and installing a module from /sys/modules will
292 now install to /boot/modules instead of /boot/kernel.
295 The CAM I/O scheduler has been committed to the kernel. There should be
296 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
297 list of known rogues that claim support for this but actually corrupt
298 data is believed to be complete, be on the lookout for data
299 corruption. The known rogue list is believed to be complete:
301 o Crucial MX100, M550 drives with MU01 firmware.
302 o Micron M510 and M550 drives with MU01 firmware.
303 o Micron M500 prior to MU07 firmware
304 o Samsung 830, 840, and 850 all firmwares
305 o FCCT M500 all firmwares
307 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
308 with working NCQ TRIM. For Micron branded drives, see your sales rep for
309 updated firmware. Black listed drives will work correctly because these
310 drives work correctly so long as no NCQ TRIMs are sent to them. Given
311 this list is the same as found in Linux, it's believed there are no
312 other rogues in the market place. All other models from the above
315 To be safe, if you are at all concerned, you can quirk each of your
316 drives to prevent NCQ from being sent by setting:
317 kern.cam.ada.X.quirks="0x2"
318 in loader.conf. If the drive requires the 4k sector quirk, set the
322 The FAST_DEPEND build option has been removed and its functionality is
323 now the one true way. The old mkdep(1) style of 'make depend' has
324 been removed. See 20160311 for further details.
327 Resource range types have grown from unsigned long to uintmax_t. All
328 drivers, and anything using libdevinfo, need to be recompiled.
331 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
332 builds. It no longer runs mkdep(1) during 'make depend', and the
333 'make depend' stage can safely be skipped now as it is auto ran
334 when building 'make all' and will generate all SRCS and DPSRCS before
335 building anything else. Dependencies are gathered at compile time with
336 -MF flags kept in separate .depend files per object file. Users should
337 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
341 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
342 kernel modules. Therefore, if you load any kernel modules at boot time,
343 please install the boot loaders after you install the kernel, but before
347 make kernel KERNCONF=YOUR_KERNEL_HERE
348 make -C sys/boot install
349 <reboot in single user>
351 Then follow the usual steps, described in the General Notes section,
355 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
356 see the 20141231 entry below for information about prerequisites and
357 upgrading, if you are not already using clang 3.5.0 or higher.
360 The AIO subsystem is now a standard part of the kernel. The
361 VFS_AIO kernel option and aio.ko kernel module have been removed.
362 Due to stability concerns, asynchronous I/O requests are only
363 permitted on sockets and raw disks by default. To enable
364 asynchronous I/O requests on all file types, set the
365 vfs.aio.enable_unsafe sysctl to a non-zero value.
368 The ELF object manipulation tool objcopy is now provided by the
369 ELF Tool Chain project rather than by GNU binutils. It should be a
370 drop-in replacement, with the addition of arm64 support. The
371 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
372 to obtain the GNU version if necessary.
375 Building ZFS pools on top of zvols is prohibited by default. That
376 feature has never worked safely; it's always been prone to deadlocks.
377 Using a zvol as the backing store for a VM guest's virtual disk will
378 still work, even if the guest is using ZFS. Legacy behavior can be
379 restored by setting vfs.zfs.vol.recursive=1.
382 The NONE and HPN patches has been removed from OpenSSH. They are
383 still available in the security/openssh-portable port.
386 With the addition of ypldap(8), a new _ypldap user is now required
387 during installworld. "mergemaster -p" can be used to add the user
388 prior to installworld, as documented in the handbook.
391 The tftp loader (pxeboot) now uses the option root-path directive. As a
392 consequence it no longer looks for a pxeboot.4th file on the tftp
393 server. Instead it uses the regular /boot infrastructure as with the
397 The code to start recording plug and play data into the modules has
398 been committed. While the old tools will properly build a new kernel,
399 a number of warnings about "unknown metadata record 4" will be produced
400 for an older kldxref. To avoid such warnings, make sure to rebuild
401 the kernel toolchain (or world). Make sure that you have r292078 or
402 later when trying to build 292077 or later before rebuilding.
405 Debug data files are now built by default with 'make buildworld' and
406 installed with 'make installworld'. This facilitates debugging but
407 requires more disk space both during the build and for the installed
408 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
412 r291527 changed the internal interface between the nfsd.ko and
413 nfscommon.ko modules. As such, they must both be upgraded to-gether.
414 __FreeBSD_version has been bumped because of this.
417 Add support for unicode collation strings leads to a change of
418 order of files listed by ls(1) for example. To get back to the old
419 behaviour, set LC_COLLATE environment variable to "C".
421 Databases administrators will need to reindex their databases given
422 collation results will be different.
424 Due to a bug in install(1) it is recommended to remove the ancient
425 locales before running make installworld.
427 rm -rf /usr/share/locale/*
430 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
431 libcrypto.so.7 or libssl.so.7 must be recompiled.
434 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
435 Kernel modules isp_2400_multi and isp_2500_multi were removed and
436 should be replaced with isp_2400 and isp_2500 modules respectively.
439 The build previously allowed using 'make -n' to not recurse into
440 sub-directories while showing what commands would be executed, and
441 'make -n -n' to recursively show commands. Now 'make -n' will recurse
442 and 'make -N' will not.
445 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
446 and etcupdate will now use this file. A custom sendmail.cf is now
447 updated via this mechanism rather than via installworld. If you had
448 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
449 want to remove the exclusion or change it to "always install".
450 /etc/mail/sendmail.cf is now managed the same way regardless of
451 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
452 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
455 Compatibility shims for legacy ATA device names have been removed.
456 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
457 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
458 environment variables, /dev/ad* and /dev/ar* symbolic links.
461 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
462 Please see the 20141231 entry below for information about prerequisites
463 and upgrading, if you are not already using clang 3.5.0 or higher.
466 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
467 and renamed from .symbols to .debug. This reduces the size requirements
468 on the boot partition or file system and provides consistency with
469 userland debug files.
471 When using the supported kernel installation method the
472 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
473 as is done with /boot/kernel.
475 Developers wishing to maintain the historical behavior of installing
476 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
479 The wireless drivers had undergone changes that remove the 'parent
480 interface' from the ifconfig -l output. The rc.d network scripts
481 used to check presence of a parent interface in the list, so old
482 scripts would fail to start wireless networking. Thus, etcupdate(3)
483 or mergemaster(8) run is required after kernel update, to update your
484 rc.d scripts in /etc.
487 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
488 These configurations are now automatically interpreted as
489 'scrub fragment reassemble'.
492 Kernel-loadable modules for the random(4) device are back. To use
493 them, the kernel must have
496 options RANDOM_LOADABLE
498 kldload(8) can then be used to load random_fortuna.ko
499 or random_yarrow.ko. Please note that due to the indirect
500 function calls that the loadable modules need to provide,
501 the build-in variants will be slightly more efficient.
503 The random(4) kernel option RANDOM_DUMMY has been retired due to
504 unpopularity. It was not all that useful anyway.
507 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
508 Control over building the ELF Tool Chain tools is now provided by
509 the WITHOUT_TOOLCHAIN knob.
512 The polarity of Pulse Per Second (PPS) capture events with the
513 uart(4) driver has been corrected. Prior to this change the PPS
514 "assert" event corresponded to the trailing edge of a positive PPS
515 pulse and the "clear" event was the leading edge of the next pulse.
517 As the width of a PPS pulse in a typical GPS receiver is on the
518 order of 1 millisecond, most users will not notice any significant
519 difference with this change.
521 Anyone who has compensated for the historical polarity reversal by
522 configuring a negative offset equal to the pulse width will need to
523 remove that workaround.
526 The default group assigned to /dev/dri entries has been changed
527 from 'wheel' to 'video' with the id of '44'. If you want to have
528 access to the dri devices please add yourself to the video group
531 # pw groupmod video -m $USER
534 The menu.rc and loader.rc files will now be replaced during
535 upgrades. Please migrate local changes to menu.rc.local and
536 loader.rc.local instead.
539 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
540 strings and strip have been removed. The src.conf(5) knob
541 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
544 As ZFS requires more kernel stack pages than is the default on some
545 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
546 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
548 Please consider using 'options KSTACK_PAGES=X' where X is greater
549 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
552 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
553 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
554 default, i.e., they will not contain "::". For example, instead
555 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
556 to have a more specific match, such as different map entries for
557 IPv6:0:0 vs IPv6:0. This change requires that configuration
558 data (including maps, files, classes, custom ruleset, etc.) must
559 use the same format, so make certain such configuration data is
560 upgrading. As a very simple check search for patterns like
561 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
562 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
563 the cf option UseCompressedIPv6Addresses.
566 The default kernel entropy-processing algorithm is now
567 Fortuna, replacing Yarrow.
569 Assuming you have 'device random' in your kernel config
570 file, the configurations allow a kernel option to override
571 this default. You may choose *ONE* of:
573 options RANDOM_YARROW # Legacy /dev/random algorithm.
574 options RANDOM_DUMMY # Blocking-only driver.
576 If you have neither, you get Fortuna. For most people,
577 read no further, Fortuna will give a /dev/random that works
578 like it always used to, and the difference will be irrelevant.
580 If you remove 'device random', you get *NO* kernel-processed
581 entropy at all. This may be acceptable to folks building
582 embedded systems, but has complications. Carry on reading,
583 and it is assumed you know what you need.
585 *PLEASE* read random(4) and random(9) if you are in the
586 habit of tweaking kernel configs, and/or if you are a member
587 of the embedded community, wanting specific and not-usual
588 behaviour from your security subsystems.
590 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
591 random', you will NOT have a functioning /dev/random, and
592 many cryptographic features will not work, including SSH.
593 You may also find strange behaviour from the random(3) set
594 of library functions, in particular sranddev(3), srandomdev(3)
595 and arc4random(3). The reason for this is that the KERN_ARND
596 sysctl only returns entropy if it thinks it has some to
597 share, and with RANDOM_DUMMY or no 'device random' this
601 An additional fix for the issue described in the 20150614 sendmail
602 entry below has been been committed in revision 284717.
605 FreeBSD's old make (fmake) has been removed from the system. It is
606 available as the devel/fmake port or via pkg install fmake.
609 The fix for the issue described in the 20150614 sendmail entry
610 below has been been committed in revision 284436. The work
611 around described in that entry is no longer needed unless the
612 default setting is overridden by a confDH_PARAMETERS configuration
613 setting of '5' or pointing to a 512 bit DH parameter file.
616 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
617 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
618 and devel/kyua to version 0.20+ and adjust any calling code to work
619 with Kyuafile and kyua.
622 The import of openssl to address the FreeBSD-SA-15:10.openssl
623 security advisory includes a change which rejects handshakes
624 with DH parameters below 768 bits. sendmail releases prior
625 to 8.15.2 (not yet released), defaulted to a 512 bit
626 DH parameter setting for client connections. To work around
627 this interoperability, sendmail can be configured to use a
628 2048 bit DH parameter by:
630 1. Edit /etc/mail/`hostname`.mc
631 2. If a setting for confDH_PARAMETERS does not exist or
632 exists and is set to a string beginning with '5',
634 3. If a setting for confDH_PARAMETERS exists and is set to
635 a file path, create a new file with:
636 openssl dhparam -out /path/to/file 2048
637 4. Rebuild the .cf file:
638 cd /etc/mail/; make; make install
640 cd /etc/mail/; make restart
642 A sendmail patch is coming, at which time this file will be
646 Generation of legacy formatted entries have been disabled by default
647 in pwd_mkdb(8), as all base system consumers of the legacy formatted
648 entries were converted to use the new format by default when the new,
649 machine independent format have been added and supported since FreeBSD
652 Please see the pwd_mkdb(8) manual page for further details.
655 Clang and llvm have been upgraded to 3.6.1 release. Please see the
656 20141231 entry below for information about prerequisites and upgrading,
657 if you are not already using 3.5.0 or higher.
660 TI platform code switched to using vendor DTS files and this update
661 may break existing systems running on Beaglebone, Beaglebone Black,
664 - dtb files should be regenerated/reinstalled. Filenames are the
665 same but content is different now
666 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
667 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
668 addressing scheme is now pin 25 on /dev/gpioc3.
669 - Pandaboard: /etc/ttys should be updated, serial console device is
670 now /dev/ttyu2, not /dev/ttyu0
673 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
674 If you need the GNU extension from groff soelim(1), install groff
675 from package: pkg install groff, or via ports: textproc/groff.
678 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
679 defined in symlink(7); previously symlinks were silently ignored.
682 The const qualifier has been removed from iconv(3) to comply with
683 POSIX. The ports tree is aware of this from r384038 onwards.
686 Libraries specified by LIBADD in Makefiles must have a corresponding
687 DPADD_<lib> variable to ensure correct dependencies. This is now
688 enforced in src.libnames.mk.
691 From legacy ata(4) driver was removed support for SATA controllers
692 supported by more functional drivers ahci(4), siis(4) and mvs(4).
693 Kernel modules ataahci and ataadaptec were removed completely,
694 replaced by ahci and mvs modules respectively.
697 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
698 the 20141231 entry below for information about prerequisites and
699 upgrading, if you are not already using 3.5.0 or higher.
702 The 32-bit PowerPC kernel has been changed to a position-independent
703 executable. This can only be booted with a version of loader(8)
704 newer than January 31, 2015, so make sure to update both world and
705 kernel before rebooting.
708 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
709 but before r278950, the RNG was not seeded properly. Immediately
710 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
711 ssh keys or openssl keys) that were generated w/ a kernel from that
712 range. This does not affect programs that directly used /dev/random
713 or /dev/urandom. All userland uses of arc4random(3) are affected.
716 The autofs(4) ABI was changed in order to restore binary compatibility
717 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
721 The powerpc64 kernel has been changed to a position-independent
722 executable. This can only be booted with a new version of loader(8),
723 so make sure to update both world and kernel before rebooting.
726 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
727 only release, no new features have been added. Please see the 20141231
728 entry below for information about prerequisites and upgrading, if you
729 are not already using 3.5.0.
732 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
733 taken from the ELF Tool Chain project rather than GNU binutils. They
734 should be drop-in replacements, with the addition of arm64 support.
735 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
736 binutils tools, if necessary. See 20150805 for updated information.
739 The default Unbound configuration now enables remote control
740 using a local socket. Users who have already enabled the
741 local_unbound service should regenerate their configuration
742 by running "service local_unbound setup" as root.
745 The GNU texinfo and GNU info pages have been removed.
746 To be able to view GNU info pages please install texinfo from ports.
749 Clang, llvm and lldb have been upgraded to 3.5.0 release.
751 As of this release, a prerequisite for building clang, llvm and lldb is
752 a C++11 capable compiler and C++11 standard library. This means that to
753 be able to successfully build the cross-tools stage of buildworld, with
754 clang as the bootstrap compiler, your system compiler or cross compiler
755 should either be clang 3.3 or later, or gcc 4.8 or later, and your
756 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
759 On any standard FreeBSD 10.x or 11.x installation, where clang and
760 libc++ are on by default (that is, on x86 or arm), this should work out
763 On 9.x installations where clang is enabled by default, e.g. on x86 and
764 powerpc, libc++ will not be enabled by default, so libc++ should be
765 built (with clang) and installed first. If both clang and libc++ are
766 missing, build clang first, then use it to build libc++.
768 On 8.x and earlier installations, upgrade to 9.x first, and then follow
769 the instructions for 9.x above.
771 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
772 default, and do not build clang.
774 Many embedded systems are resource constrained, and will not be able to
775 build clang in a reasonable time, or in some cases at all. In those
776 cases, cross building bootable systems on amd64 is a workaround.
778 This new version of clang introduces a number of new warnings, of which
779 the following are most likely to appear:
783 This warns in two cases, for both C and C++:
784 * When the code is trying to take the absolute value of an unsigned
785 quantity, which is effectively a no-op, and almost never what was
786 intended. The code should be fixed, if at all possible. If you are
787 sure that the unsigned quantity can be safely cast to signed, without
788 loss of information or undefined behavior, you can add an explicit
789 cast, or disable the warning.
791 * When the code is trying to take an absolute value, but the called
792 abs() variant is for the wrong type, which can lead to truncation.
793 If you want to disable the warning instead of fixing the code, please
794 make sure that truncation will not occur, or it might lead to unwanted
797 -Wtautological-undefined-compare and
798 -Wundefined-bool-conversion
800 These warn when C++ code is trying to compare 'this' against NULL, while
801 'this' should never be NULL in well-defined C++ code. However, there is
802 some legacy (pre C++11) code out there, which actively abuses this
803 feature, which was less strictly defined in previous C++ versions.
805 Squid and openjdk do this, for example. The warning can be turned off
806 for C++98 and earlier, but compiling the code in C++11 mode might result
807 in unexpected behavior; for example, the parts of the program that are
808 unreachable could be optimized away.
811 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
812 kernel sources have been removed. The .h files remain, since some
813 utilities include them. This will need to be fixed later.
814 If "mount -t oldnfs ..." is attempted, it will fail.
815 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
816 the utilities will report errors.
819 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
820 directories to top level SUBDIR variable when their parent
821 directory is included in LOCAL_DIRS. Users with build systems with
822 such hierarchies and without SUBDIR entries in the parent
823 directory Makefiles should add them or add the directories to
827 faith(4) and faithd(8) have been removed from the base system. Faith
828 has been obsolete for a very long time.
831 vt(4), the new console driver, is enabled by default. It brings
832 support for Unicode and double-width characters, as well as
833 support for UEFI and integration with the KMS kernel video
836 You may need to update your console settings in /etc/rc.conf,
837 most probably the keymap. During boot, /etc/rc.d/syscons will
838 indicate what you need to do.
840 vt(4) still has issues and lacks some features compared to
841 syscons(4). See the wiki for up-to-date information:
842 https://wiki.freebsd.org/Newcons
844 If you want to keep using syscons(4), you can do so by adding
845 the following line to /boot/loader.conf:
849 pjdfstest has been integrated into kyua as an opt-in test suite.
850 Please see share/doc/pjdfstest/README for more details on how to
854 gperf has been removed from the base system for architectures
855 that use clang. Ports that require gperf will obtain it from the
859 pjdfstest has been moved from tools/regression/pjdfstest to
863 At svn r271982, The default linux compat kernel ABI has been adjusted
864 to 2.6.18 in support of the linux-c6 compat ports infrastructure
865 update. If you wish to continue using the linux-f10 compat ports,
866 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
867 encouraged to update their linux-compat packages to linux-c6 during
868 their next update cycle.
871 The ofwfb driver, used to provide a graphics console on PowerPC when
872 using vt(4), no longer allows mmap() of all physical memory. This
873 will prevent Xorg on PowerPC with some ATI graphics cards from
874 initializing properly unless x11-servers/xorg-server is updated to
878 The xdev targets have been converted to using TARGET and
879 TARGET_ARCH instead of XDEV and XDEV_ARCH.
882 The default unbound configuration has been modified to address
883 issues with reverse lookups on networks that use private
884 address ranges. If you use the local_unbound service, run
885 "service local_unbound setup" as root to regenerate your
886 configuration, then "service local_unbound reload" to load the
890 The GNU texinfo and GNU info pages are not built and installed
891 anymore, WITH_INFO knob has been added to allow to built and install
893 UPDATE: see 20150102 entry on texinfo's removal
896 The GNU readline library is now an INTERNALLIB - that is, it is
897 statically linked into consumers (GDB and variants) in the base
898 system, and the shared library is no longer installed. The
899 devel/readline port is available for third party software that
903 The Itanium architecture (ia64) has been removed from the list of
904 known architectures. This is the first step in the removal of the
908 Commit r268115 has added NFSv4.1 server support, merged from
909 projects/nfsv4.1-server. Since this includes changes to the
910 internal interfaces between the NFS related modules, a full
911 build of the kernel and modules will be necessary.
912 __FreeBSD_version has been bumped.
915 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
916 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
917 which differs from the behaviour controlled by this knob.)
920 Maximal length of the serial number in CTL was increased from 16 to
921 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
922 and ctld, need to be rebuilt to work with a new kernel.
925 The libatf-c and libatf-c++ major versions were downgraded to 0 and
926 1 respectively to match the upstream numbers. They were out of
927 sync because, when they were originally added to FreeBSD, the
928 upstream versions were not respected. These libraries are private
929 and not yet built by default, so renumbering them should be a
930 non-issue. However, unclean source trees will yield broken test
931 programs once the operator executes "make delete-old-libs" after a
934 Additionally, the atf-sh binary was made private by moving it into
935 /usr/libexec/. Already-built shell test programs will keep the
936 path to the old binary so they will break after "make delete-old"
939 If you are using WITH_TESTS=yes (not the default), wipe the object
940 tree and rebuild from scratch to prevent spurious test failures.
941 This is only needed once: the misnumbered libraries and misplaced
942 binaries have been added to OptionalObsoleteFiles.inc so they will
943 be removed during a clean upgrade.
946 Clang and llvm have been upgraded to 3.4.1 release.
949 We bogusly installed src.opts.mk in /usr/share/mk. This file should
950 be removed to avoid issues in the future (and has been added to
954 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
955 past, it affected all builds that used the bsd.*.mk files. The old
956 behavior was a bug, but people may have relied upon it. To get this
957 behavior back, you can .include /etc/src.conf from /etc/make.conf
958 (which is still global and isn't changed). This also changes the
959 behavior of incremental builds inside the tree of individual
960 directories. Set MAKESYSPATH to ".../share/mk" to do that.
961 Although this has survived make universe and some upgrade scenarios,
962 other upgrade scenarios may have broken. At least one form of
963 temporary breakage was fixed with MAKESYSPATH settings for buildworld
964 as well... In cases where MAKESYSPATH isn't working with this
965 setting, you'll need to set it to the full path to your tree.
967 One side effect of all this cleaning up is that bsd.compiler.mk
968 is no longer implicitly included by bsd.own.mk. If you wish to
969 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
973 The lindev device has been removed since /dev/full has been made a
974 standard device. __FreeBSD_version has been bumped.
977 The knob WITHOUT_VI was added to the base system, which controls
978 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
979 in order to reorder files share/termcap and didn't build ex(1) as a
980 build tool, so building/installing with WITH_VI is highly advised for
981 build hosts for older releases.
983 This issue has been fixed in stable/9 and stable/10 in r277022 and
984 r276991, respectively.
987 The YES_HESIOD knob has been removed. It has been obsolete for
988 a decade. Please move to using WITH_HESIOD instead or your builds
989 will silently lack HESIOD.
992 The uart(4) driver has been changed with respect to its handling
993 of the low-level console. Previously the uart(4) driver prevented
994 any process from changing the baudrate or the CLOCAL and HUPCL
995 control flags. By removing the restrictions, operators can make
996 changes to the serial console port without having to reboot.
997 However, when getty(8) is started on the serial device that is
998 associated with the low-level console, a misconfigured terminal
999 line in /etc/ttys will now have a real impact.
1000 Before upgrading the kernel, make sure that /etc/ttys has the
1001 serial console device configured as 3wire without baudrate to
1002 preserve the previous behaviour. E.g:
1003 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1006 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1007 to improve performance. To re-enable it, if needed, run rpcbind
1008 with command line option -W.
1011 Switched back to the GPL dtc compiler due to updates in the upstream
1012 dts files not being supported by the BSDL dtc compiler. You will need
1013 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1014 may result while building dtb files during a kernel build if you fail
1015 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1018 Clang and llvm have been upgraded to 3.4 release.
1021 The nve(4) driver has been removed. Please use the nfe(4) driver
1022 for NVIDIA nForce MCP Ethernet adapters instead.
1025 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1026 This could cause certain C++ applications using shared libraries built
1027 against the previous version of libc++ to crash. The incompatibility
1028 has now been fixed, but any C++ applications or shared libraries built
1029 between r261283 and r261801 should be recompiled.
1032 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1033 capability mode support. Please note that enabling the feature in
1034 kernel is still highly recommended.
1037 OpenSSH is now built with sandbox support, and will use sandbox as
1038 the default privilege separation method. This requires Capsicum
1039 capability mode support in kernel.
1042 The libelf and libdwarf libraries have been updated to newer
1043 versions from upstream. Shared library version numbers for
1044 these two libraries were bumped. Any ports or binaries
1045 requiring these two libraries should be recompiled.
1046 __FreeBSD_version is bumped to 1100006.
1049 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1050 instead of providing an explicit one, this would prevent such
1051 Makefile from providing its own Kyuafile in the future during
1052 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1053 intervention is needed to clean an objdir if you use NO_CLEAN:
1054 # find /usr/obj -name Kyuafile | xargs rm -f
1057 The behavior of gss_pseudo_random() for the krb5 mechanism
1058 has changed, for applications requesting a longer random string
1059 than produced by the underlying enctype's pseudo-random() function.
1060 In particular, the random string produced from a session key of
1061 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1062 be different at the 17th octet and later, after this change.
1063 The counter used in the PRF+ construction is now encoded as a
1064 big-endian integer in accordance with RFC 4402.
1065 __FreeBSD_version is bumped to 1100004.
1068 The WITHOUT_ATF build knob has been removed and its functionality
1069 has been subsumed into the more generic WITHOUT_TESTS. If you were
1070 using the former to disable the build of the ATF libraries, you
1071 should change your settings to use the latter.
1074 The default version of mtree is nmtree which is obtained from
1075 NetBSD. The output is generally the same, but may vary
1076 slightly. If you found you need identical output adding
1077 "-F freebsd9" to the command line should do the trick. For the
1078 time being, the old mtree is available as fmtree.
1081 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1082 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1083 1.1.4_8 and verify bsdyml not linked in, before running "make
1085 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1087 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1090 The stable/10 branch has been created in subversion from head
1094 The rc.d/jail script has been updated to support jail(8)
1095 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1096 for per-jail configuration are automatically converted to
1097 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1098 This is transparently backward compatible. See below about some
1099 incompatibilities and rc.conf(5) manual page for more details.
1101 These variables are now deprecated in favor of jail(8) configuration
1102 file. One can use "rc.d/jail config <jname>" command to generate
1103 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1104 running the jail(8) utility. The default pathname of the
1105 configuration file is /etc/jail.conf and can be specified by
1106 using $jail_conf or $jail_<jname>_conf variables.
1108 Please note that jail_devfs_ruleset accepts an integer at
1109 this moment. Please consider to rewrite the ruleset name
1113 BIND has been removed from the base system. If all you need
1114 is a local resolver, simply enable and start the local_unbound
1115 service instead. Otherwise, several versions of BIND are
1116 available in the ports tree. The dns/bind99 port is one example.
1118 With this change, nslookup(1) and dig(1) are no longer in the base
1119 system. Users should instead use host(1) and drill(1) which are
1120 in the base system. Alternatively, nslookup and dig can
1121 be obtained by installing the dns/bind-tools port.
1124 With the addition of unbound(8), a new unbound user is now
1125 required during installworld. "mergemaster -p" can be used to
1126 add the user prior to installworld, as documented in the handbook.
1129 OpenSSH is now built with DNSSEC support, and will by default
1130 silently trust signed SSHFP records. This can be controlled with
1131 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1132 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1135 The GNU Compiler Collection and C++ standard library (libstdc++)
1136 are no longer built by default on platforms where clang is the system
1137 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1138 options in src.conf.
1141 The PROCDESC kernel option is now part of the GENERIC kernel
1142 configuration and is required for the rwhod(8) to work.
1143 If you are using custom kernel configuration, you should include
1147 The API and ABI related to the Capsicum framework was modified
1148 in backward incompatible way. The userland libraries and programs
1149 have to be recompiled to work with the new kernel. This includes the
1150 following libraries and programs, but the whole buildworld is
1151 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1152 kdump, procstat, rwho, rwhod, uniq.
1155 AES-NI intrinsic support has been added to gcc. The AES-NI module
1156 has been updated to use this support. A new gcc is required to build
1157 the aesni module on both i386 and amd64.
1160 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1161 Thus "device padlock_rng" and "device rdrand_rng" should be
1162 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1165 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1166 enables just the iconv* functionality and is now on by default.
1167 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1168 compatibility. Set WITHOUT_ICONV to build the old way.
1169 If you have been using WITH_ICONV before, you will very likely
1170 need to turn on WITH_LIBICONV_COMPAT.
1173 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1174 Illumos origin, including ZFS. If you have INVARIANTS in your
1175 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1177 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1178 locks if WITNESS option was set. Because that generated a lot of
1179 witness(9) reports and all of them were believed to be false
1180 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1181 can be used to achieve the previous behavior.
1184 Timer values in IPv6 data structures now use time_uptime instead
1185 of time_second. Although this is not a user-visible functional
1186 change, userland utilities which directly use them---ndp(8),
1187 rtadvd(8), and rtsold(8) in the base system---need to be updated
1188 to r253970 or later.
1191 find -delete can now delete the pathnames given as arguments,
1192 instead of only files found below them or if the pathname did
1193 not contain any slashes. Formerly, the following error message
1196 find: -delete: <path>: relative path potentially not safe
1198 Deleting the pathnames given as arguments can be prevented
1199 without error messages using -mindepth 1 or by changing
1200 directory and passing "." as argument to find. This works in the
1201 old as well as the new version of find.
1204 Behavior of devfs rules path matching has been changed.
1205 Pattern is now always matched against fully qualified devfs
1206 path and slash characters must be explicitly matched by
1207 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1208 subdirectories must be reviewed.
1211 The default ARM ABI has changed to the ARM EABI. The old ABI is
1212 incompatible with the ARM EABI and all programs and modules will
1213 need to be rebuilt to work with a new kernel.
1215 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1217 NOTE: Support for the old ABI will be removed in the future and
1218 users are advised to upgrade.
1221 pkg_install has been disconnected from the build if you really need it
1222 you should add WITH_PKGTOOLS in your src.conf(5).
1225 Most of network statistics structures were changed to be able
1226 keep 64-bits counters. Thus all tools, that work with networking
1227 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1230 Fix a bug that allowed a tracing process (e.g. gdb) to write
1231 to a memory-mapped file in the traced process's address space
1232 even if neither the traced process nor the tracing process had
1233 write access to that file.
1236 CVS has been removed from the base system. An exact copy
1237 of the code is available from the devel/cvs port.
1240 Some people report the following error after the switch to bmake:
1242 make: illegal option -- J
1243 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1245 *** [buildworld] Error code 2
1247 this likely due to an old instance of make in
1248 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1249 which src/Makefile will use that blindly, if it exists, so if
1250 you see the above error:
1252 rm -rf `make -V MAKEPATH`
1257 Use bmake by default.
1258 Whereas before one could choose to build with bmake via
1259 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1260 make. The goal is to remove these knobs for 10-RELEASE.
1262 It is worth noting that bmake (like gmake) treats the command
1263 line as the unit of failure, rather than statements within the
1264 command line. Thus '(cd some/where && dosomething)' is safer
1265 than 'cd some/where; dosomething'. The '()' allows consistent
1266 behavior in parallel build.
1269 Fix a bug that allows NFS clients to issue READDIR on files.
1272 The WITHOUT_IDEA option has been removed because
1273 the IDEA patent expired.
1276 The sysctl which controls TRIM support under ZFS has been renamed
1277 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1281 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1282 rather than creating it's own in the temporary directory in
1283 order allow access to bootstrapped versions of tools such as
1284 install and mtree. When upgrading from version of FreeBSD where
1285 the install command does not support -l, you will need to
1286 install a new mergemaster command if mergemaster -p is required.
1287 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1291 Legacy ATA stack, disabled and replaced by new CAM-based one since
1292 FreeBSD 9.0, completely removed from the sources. Kernel modules
1293 atadisk and atapi*, user-level tools atacontrol and burncd are
1294 removed. Kernel option `options ATA_CAM` is now permanently enabled
1298 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1299 and socketpair(2). Software, in particular Kerberos, may
1300 automatically detect and use these during building. The resulting
1301 binaries will not work on older kernels.
1304 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1305 information, see the respective 20130304 entry).
1308 Recent commits to callout(9) changed the size of struct callout,
1309 so the KBI is probably heavily disturbed. Also, some functions
1310 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1311 by macros. Every kernel module using it won't load, so rebuild
1314 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1315 but does not initialize by default (because of the new CTL_DISABLE
1316 option) to save memory. To re-enable it, remove the CTL_DISABLE
1317 option from the kernel config file or set kern.cam.ctl.disable=0
1318 in /boot/loader.conf.
1321 The ctl device has been disabled in GENERIC for i386 and amd64.
1322 This was done due to the extra memory being allocated at system
1323 initialisation time by the ctl driver which was only used if
1324 a CAM target device was created. This makes a FreeBSD system
1325 unusable on 128MB or less of RAM.
1328 A new compression method (lz4) has been merged to -HEAD. Please
1329 refer to zpool-features(7) for more information.
1331 Please refer to the "ZFS notes" section of this file for information
1332 on upgrading boot ZFS pools.
1335 A BSD-licensed patch(1) variant has been added and is installed
1336 as bsdpatch, being the GNU version the default patch.
1337 To inverse the logic and use the BSD-licensed one as default,
1338 while having the GNU version installed as gnupatch, rebuild
1339 and install world with the WITH_BSD_PATCH knob set.
1342 Due to the use of the new -l option to install(1) during build
1343 and install, you must take care not to directly set the INSTALL
1344 make variable in your /etc/make.conf, /etc/src.conf, or on the
1345 command line. If you wish to use the -C flag for all installs
1346 you may be able to add INSTALL+=-C to /etc/make.conf or
1350 The install(1) option -M has changed meaning and now takes an
1351 argument that is a file or path to append logs to. In the
1352 unlikely event that -M was the last option on the command line
1353 and the command line contained at least two files and a target
1354 directory the first file will have logs appended to it. The -M
1355 option served little practical purpose in the last decade so its
1356 use is expected to be extremely rare.
1359 After switching to Clang as the default compiler some users of ZFS
1360 on i386 systems started to experience stack overflow kernel panics.
1361 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1364 GEOM_LABEL now mangles label names read from file system metadata.
1365 Mangling affect labels containing spaces, non-printable characters,
1366 '%' or '"'. Device names in /etc/fstab and other places may need to
1370 By default, only the 10 most recent kernel dumps will be saved. To
1371 restore the previous behaviour (no limit on the number of kernel dumps
1372 stored in the dump directory) add the following line to /etc/rc.conf:
1377 With the addition of auditdistd(8), a new auditdistd user is now
1378 required during installworld. "mergemaster -p" can be used to
1379 add the user prior to installworld, as documented in the handbook.
1382 The sin6_scope_id member variable in struct sockaddr_in6 is now
1383 filled by the kernel before passing the structure to the userland via
1384 sysctl or routing socket. This means the KAME-specific embedded scope
1385 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1386 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1387 __FreeBSD_version is bumped to 1000025.
1390 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1391 This means that the world and kernel will be compiled with clang
1392 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1393 and /usr/bin/cpp. To disable this behavior and revert to building
1394 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1395 of current may need to bootstrap WITHOUT_CLANG first if the clang
1396 build fails (its compatibility window doesn't extend to the 9 stable
1400 The IPFIREWALL_FORWARD kernel option has been removed. Its
1401 functionality now turned on by default.
1404 The ZERO_COPY_SOCKET kernel option has been removed and
1405 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1406 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1407 mechanism which is not safe and may result in kernel crashes.
1408 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1409 driver supports disposeable external page sized mbuf storage.
1410 Proper replacements for both zero-copy mechanisms are under
1411 consideration and will eventually lead to complete removal
1412 of the two kernel options.
1415 The IPv4 network stack has been converted to network byte
1416 order. The following modules need to be recompiled together
1417 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1418 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1421 Support for non-MPSAFE filesystems was removed from VFS. The
1422 VFS_VERSION was bumped, all filesystem modules shall be
1426 All the non-MPSAFE filesystems have been disconnected from
1427 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1428 portalfs, smbfs, xfs.
1431 The interface cloning API and ABI has changed. The following
1432 modules need to be recompiled together with kernel:
1433 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1434 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1435 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1438 The sdhci driver was split in two parts: sdhci (generic SD Host
1439 Controller logic) and sdhci_pci (actual hardware driver).
1440 No kernel config modifications are required, but if you
1441 load sdhc as a module you must switch to sdhci_pci instead.
1444 Import the FUSE kernel and userland support into base system.
1447 The GNU sort(1) program has been removed since the BSD-licensed
1448 sort(1) has been the default for quite some time and no serious
1449 problems have been reported. The corresponding WITH_GNU_SORT
1453 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1454 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1458 The net80211(4) ABI has been changed to allow for improved driver
1459 PS-POLL and power-save support. All wireless drivers need to be
1460 recompiled to work with the new kernel.
1463 The random(4) support for the VIA hardware random number
1464 generator (`PADLOCK') is no longer enabled unconditionally.
1465 Add the padlock_rng device in the custom kernel config if
1466 needed. The GENERIC kernels on i386 and amd64 do include the
1467 device, so the change only affects the custom kernel
1471 The pf(4) packet filter ABI has been changed. pfctl(8) and
1472 snmp_pf module need to be recompiled to work with new kernel.
1475 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1476 to -HEAD. Pools that have empty_bpobj in active state can not be
1477 imported read-write with ZFS implementations that do not support
1478 this feature. For more information read the zpool-features(5)
1482 The sparc64 ZFS loader has been changed to no longer try to auto-
1483 detect ZFS providers based on diskN aliases but now requires these
1484 to be explicitly listed in the OFW boot-device environment variable.
1487 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1488 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1489 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1492 The following sysctls and tunables have been renamed for consistency
1493 with other variables:
1494 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1495 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1498 The sort utility has been replaced with BSD sort. For now, GNU sort
1499 is also available as "gnusort" or the default can be set back to
1500 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1501 installed as "bsdsort".
1504 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1505 Starting with this version the old system of ZFS pool versioning
1506 is superseded by "feature flags". This concept enables forward
1507 compatibility against certain future changes in functionality of ZFS
1508 pools. The first read-only compatible "feature flag" for ZFS pools
1509 is named "com.delphix:async_destroy". For more information
1510 read the new zpool-features(5) manual page.
1511 Please refer to the "ZFS notes" section of this file for information
1512 on upgrading boot ZFS pools.
1515 The malloc(3) implementation embedded in libc now uses sources imported
1516 as contrib/jemalloc. The most disruptive API change is to
1517 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1518 delete it prior to installworld, and optionally re-create it using the
1519 new format after rebooting. See malloc.conf(5) for details
1520 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1524 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1525 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1526 now spelled mips. This is to aid compatibility with third-party
1527 software that expects this naming scheme in uname(3). Little-endian
1528 settings are unchanged. If you are updating a big-endian mips64 machine
1529 from before this change, you may need to set MACHINE_ARCH=mips64 in
1530 your environment before the new build system will recognize your machine.
1533 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1537 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1538 nullfs(5) did not pass through all behaviours to the underlying layer,
1539 as a result if we bound to a socket on the lower layer we could connect
1540 only to the lower path; if we bound to the upper layer we could connect
1541 only to the upper path. The new behavior is one can connect to both the
1542 lower and the upper paths regardless what layer path one binds to.
1545 The getifaddrs upgrade path broken with 20111215 has been restored.
1546 If you have upgraded in between 20111215 and 20120209 you need to
1547 recompile libc again with your kernel. You still need to recompile
1548 world to be able to configure CARP but this restriction already
1549 comes from 20111215.
1552 The set_rcvar() function has been removed from /etc/rc.subr. All
1553 base and ports rc.d scripts have been updated, so if you have a
1554 port installed with a script in /usr/local/etc/rc.d you can either
1555 hand-edit the rcvar= line, or reinstall the port.
1557 An easy way to handle the mass-update of /etc/rc.d:
1558 rm /etc/rc.d/* && mergemaster -i
1561 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1562 on the current CPU and prevents other threads from running.
1563 This behavior can be reverted using the kern.stop_scheduler_on_panic
1565 The new behavior can be incompatible with kern.sync_on_panic.
1568 The carp(4) facility has been changed significantly. Configuration
1569 of the CARP protocol via ifconfig(8) has changed, as well as format
1570 of CARP events submitted to devd(8) has changed. See manual pages
1571 for more information. The arpbalance feature of carp(4) is currently
1572 not supported anymore.
1574 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1575 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1576 need to be recompiled.
1579 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1583 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1584 explicitely support non-MPSAFE filesystems.
1585 It is on by default for all supported platform at this present
1589 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1590 i386 and pc98 GENERIC kernel configuration files.
1593 sysinstall has been removed
1596 The stable/9 branch created in subversion. This corresponds to the
1597 RELENG_9 branch in CVS.
1603 Avoid using make -j when upgrading. While generally safe, there are
1604 sometimes problems using -j to upgrade. If your upgrade fails with
1605 -j, please try again without -j. From time to time in the past there
1606 have been problems using -j with buildworld and/or installworld. This
1607 is especially true when upgrading between "distant" versions (eg one
1608 that cross a major release boundary or several minor releases, or when
1609 several months have passed on the -current branch).
1611 Sometimes, obscure build problems are the result of environment
1612 poisoning. This can happen because the make utility reads its
1613 environment when searching for values for global variables. To run
1614 your build attempts in an "environmental clean room", prefix all make
1615 commands with 'env -i '. See the env(1) manual page for more details.
1617 When upgrading from one major version to another it is generally best to
1618 upgrade to the latest code in the currently installed branch first, then
1619 do an upgrade to the new branch. This is the best-tested upgrade path,
1620 and has the highest probability of being successful. Please try this
1621 approach if you encounter problems with a major version upgrade. Since
1622 the stable 4.x branch point, one has generally been able to upgade from
1623 anywhere in the most recent stable branch to head / current (or even the
1624 last couple of stable branches). See the top of this file when there's
1627 When upgrading a live system, having a root shell around before
1628 installing anything can help undo problems. Not having a root shell
1629 around can lead to problems if pam has changed too much from your
1630 starting point to allow continued authentication after the upgrade.
1632 This file should be read as a log of events. When a later event changes
1633 information of a prior event, the prior event should not be deleted.
1634 Instead, a pointer to the entry with the new information should be
1635 placed in the old entry. Readers of this file should also sanity check
1636 older entries before relying on them blindly. Authors of new entries
1637 should write them with this in mind.
1641 When upgrading the boot ZFS pool to a new version, always follow
1644 1.) recompile and reinstall the ZFS boot loader and boot block
1645 (this is part of "make buildworld" and "make installworld")
1647 2.) update the ZFS boot block on your boot drive
1649 The following example updates the ZFS boot block on the first
1650 partition (freebsd-boot) of a GPT partitioned drive ada0:
1651 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1653 Non-boot pools do not need these updates.
1657 If you are updating from a prior version of FreeBSD (even one just
1658 a few days old), you should follow this procedure. It is the most
1659 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1661 make kernel-toolchain
1662 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1663 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1665 To test a kernel once
1666 ---------------------
1667 If you just want to boot a kernel once (because you are not sure
1668 if it works, or if you want to boot a known bad kernel to provide
1669 debugging information) run
1670 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1671 nextboot -k testkernel
1673 To just build a kernel when you know that it won't mess you up
1674 --------------------------------------------------------------
1675 This assumes you are already running a CURRENT system. Replace
1676 ${arch} with the architecture of your machine (e.g. "i386",
1677 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1679 cd src/sys/${arch}/conf
1680 config KERNEL_NAME_HERE
1681 cd ../compile/KERNEL_NAME_HERE
1686 If this fails, go to the "To build a kernel" section.
1688 To rebuild everything and install it on the current system.
1689 -----------------------------------------------------------
1690 # Note: sometimes if you are running current you gotta do more than
1691 # is listed here if you are upgrading from a really old current.
1693 <make sure you have good level 0 dumps>
1695 make kernel KERNCONF=YOUR_KERNEL_HERE
1697 <reboot in single user> [3]
1704 To cross-install current onto a separate partition
1705 --------------------------------------------------
1706 # In this approach we use a separate partition to hold
1707 # current's root, 'usr', and 'var' directories. A partition
1708 # holding "/", "/usr" and "/var" should be about 2GB in
1711 <make sure you have good level 0 dumps>
1714 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1715 <maybe newfs current's root partition>
1716 <mount current's root partition on directory ${CURRENT_ROOT}>
1717 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1718 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1719 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1720 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1721 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1722 <reboot into current>
1723 <do a "native" rebuild/install as described in the previous section>
1724 <maybe install compatibility libraries from ports/misc/compat*>
1728 To upgrade in-place from stable to current
1729 ----------------------------------------------
1730 <make sure you have good level 0 dumps>
1732 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1734 <reboot in single user> [3]
1741 Make sure that you've read the UPDATING file to understand the
1742 tweaks to various things you need. At this point in the life
1743 cycle of current, things change often and you are on your own
1744 to cope. The defaults can also change, so please read ALL of
1745 the UPDATING entries.
1747 Also, if you are tracking -current, you must be subscribed to
1748 freebsd-current@freebsd.org. Make sure that before you update
1749 your sources that you have read and understood all the recent
1750 messages there. If in doubt, please track -stable which has
1751 much fewer pitfalls.
1753 [1] If you have third party modules, such as vmware, you
1754 should disable them at this point so they don't crash your
1757 [3] From the bootblocks, boot -s, and then do
1762 adjkerntz -i # if CMOS is wall time
1763 Also, when doing a major release upgrade, it is required that
1764 you boot into single user mode to do the installworld.
1766 [4] Note: This step is non-optional. Failure to do this step
1767 can result in a significant reduction in the functionality of the
1768 system. Attempting to do it by hand is not recommended and those
1769 that pursue this avenue should read this file carefully, as well
1770 as the archives of freebsd-current and freebsd-hackers mailing lists
1771 for potential gotchas. The -U option is also useful to consider.
1772 See mergemaster(8) for more information.
1774 [5] Usually this step is a noop. However, from time to time
1775 you may need to do this if you get unknown user in the following
1776 step. It never hurts to do it all the time. You may need to
1777 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1778 install) after the buildworld before this step if you last updated
1779 from current before 20130425 or from -stable before 20130430.
1781 [6] This only deletes old files and directories. Old libraries
1782 can be deleted by "make delete-old-libs", but you have to make
1783 sure that no program is using those libraries anymore.
1785 [8] In order to have a kernel that can run the 4.x binaries needed to
1786 do an installworld, you must include the COMPAT_FREEBSD4 option in
1787 your kernel. Failure to do so may leave you with a system that is
1788 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1789 required to run the 5.x binaries on more recent kernels. And so on
1790 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1792 Make sure that you merge any new devices from GENERIC since the
1793 last time you updated your kernel config file.
1795 [9] When checking out sources, you must include the -P flag to have
1796 cvs prune empty directories.
1798 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1799 "?=" instead of the "=" assignment operator, so that buildworld can
1800 override the CPUTYPE if it needs to.
1802 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1803 not on the command line, or in /etc/make.conf. buildworld will
1804 warn if it is improperly defined.
1807 This file contains a list, in reverse chronological order, of major
1808 breakages in tracking -current. It is not guaranteed to be a complete
1809 list of such breakages, and only contains entries since September 23, 2011.
1810 If you need to see UPDATING entries from before that date, you will need
1811 to fetch an UPDATING file from an older FreeBSD release.
1813 Copyright information:
1815 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1817 Redistribution, publication, translation and use, with or without
1818 modification, in full or in part, in any form or format of this
1819 document are permitted without further permission from the author.
1821 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1822 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1823 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1824 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1825 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1826 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1827 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1828 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1829 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1830 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1831 POSSIBILITY OF SUCH DAMAGE.
1833 Contact Warner Losh if you have any questions about your use of