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 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
56 Please see the 20141231 entry below for information about prerequisites
57 and upgrading, if you are not already using clang 3.5.0 or higher.
60 The code that provides support for ZFS .zfs/ directory functionality
61 has been reimplemented. It's not possible now to create a snapshot
62 by mkdir under .zfs/snapshot/. That should be the only user visible
66 EISA bus support has been removed. The WITH_EISA option is no longer
70 MCA bus support has been removed.
73 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
74 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
77 The EM_MULTIQUEUE kernel configuration option is deprecated now that
78 the em(4) driver conforms to iflib specifications.
81 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
82 IFLIB. If you have a custom kernel configuration that excludes em(4)
83 but you use igb(4), you need to re-add em(4) to your custom configuration.
86 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
87 Please see the 20141231 entry below for information about prerequisites
88 and upgrading, if you are not already using clang 3.5.0 or higher.
91 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
92 Please see the 20141231 entry below for information about prerequisites
93 and upgrading, if you are not already using clang 3.5.0 or higher.
96 The layout of the pmap structure has changed for powerpc to put the pmap
97 statistics at the front for all CPU variations. libkvm(3) and all tools
98 that link against it need to be recompiled.
101 isl(4) and cyapa(4) drivers now require a new driver,
102 chromebook_platform(4), to work properly on Chromebook-class hardware.
103 On other types of hardware the drivers may need to be configured using
104 device hints. Please see the corresponding manual pages for details.
107 The urtwn(4) driver was merged into rtwn(4) and now consists of
108 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
110 Also, firmware for RTL8188CE was renamed due to possible name
111 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
114 GNU rcs has been removed from base. It is available as packages:
115 - rcs: Latest GPLv3 GNU rcs version.
116 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
120 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
121 modules now requires that the kernel configuration contain the
122 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
125 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
126 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
129 Relocatable object files with the extension of .So have been renamed
130 to use an extension of .pico instead. The purpose of this change is
131 to avoid a name clash with shared libraries on case-insensitive file
132 systems. On those file systems, foo.So is the same file as foo.so.
135 GNU rcs has been turned off by default. It can (temporarily) be built
136 again by adding WITH_RCS knob in src.conf.
137 Otherwise, GNU rcs is available from packages:
138 - rcs: Latest GPLv3 GNU rcs version.
139 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
142 The backup_uses_rcs functionality has been removed from rc.subr.
145 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
146 two separate components, QUEUE_MACRO_DEBUG_TRACE and
147 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
148 QUEUE_MACRO_DEBUG behavior.
151 r304787 changed some ioctl interfaces between the iSCSI userspace
152 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
153 rebuilt to work with new kernels. __FreeBSD_version has been bumped
157 The UDP receive code has been updated to only treat incoming UDP
158 packets that were addressed to an L2 broadcast address as L3
159 broadcast packets. It is not expected that this will affect any
160 standards-conforming UDP application. The new behaviour can be
161 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
165 Remove the openbsd_poll system call.
166 __FreeBSD_version has been bumped because of this.
169 The libc stub for the pipe(2) system call has been replaced with
170 a wrapper that calls the pipe2(2) system call and the pipe(2)
171 system call is now only implemented by the kernels that include
172 "options COMPAT_FREEBSD10" in their config file (this is the
173 default). Users should ensure that this option is enabled in
174 their kernel or upgrade userspace to r302092 before upgrading their
178 CAM will now strip leading spaces from SCSI disks' serial numbers.
179 This will affect users who create UFS filesystems on SCSI disks using
180 those disk's diskid device nodes. For example, if /etc/fstab
181 previously contained a line like
182 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
183 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
184 transforms like gmirror may also be affected. ZFS users should
188 The bitstring(3) API has been updated with new functionality and
189 improved performance. But it is binary-incompatible with the old API.
190 Objects built with the new headers may not be linked against objects
191 built with the old headers.
194 The brk and sbrk functions have been removed from libc on arm64.
195 Binutils from ports has been updated to not link to these
196 functions and should be updated to the latest version before
197 installing a new libc.
200 The armv6 port now defaults to hard float ABI. Limited support
201 for running both hardfloat and soft float on the same system
202 is available using the libraries installed with -DWITH_LIBSOFT.
203 This has only been tested as an upgrade path for installworld
204 and packages may fail or need manual intervention to run. New
205 packages will be needed.
207 To update an existing self-hosted armv6hf system, you must add
208 TARGET_ARCH=armv6 on the make command line for both the build
209 and the install steps.
212 Kernel modules compiled outside of a kernel build now default to
213 installing to /boot/modules instead of /boot/kernel. Many kernel
214 modules built this way (such as those in ports) already overrode
215 KMODDIR explicitly to install into /boot/modules. However,
216 manually building and installing a module from /sys/modules will
217 now install to /boot/modules instead of /boot/kernel.
220 The CAM I/O scheduler has been committed to the kernel. There should be
221 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
222 list of known rogues that claim support for this but actually corrupt
223 data is believed to be complete, be on the lookout for data
224 corruption. The known rogue list is believed to be complete:
226 o Crucial MX100, M550 drives with MU01 firmware.
227 o Micron M510 and M550 drives with MU01 firmware.
228 o Micron M500 prior to MU07 firmware
229 o Samsung 830, 840, and 850 all firmwares
230 o FCCT M500 all firmwares
232 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
233 with working NCQ TRIM. For Micron branded drives, see your sales rep for
234 updated firmware. Black listed drives will work correctly because these
235 drives work correctly so long as no NCQ TRIMs are sent to them. Given
236 this list is the same as found in Linux, it's believed there are no
237 other rogues in the market place. All other models from the above
240 To be safe, if you are at all concerned, you can quirk each of your
241 drives to prevent NCQ from being sent by setting:
242 kern.cam.ada.X.quirks="0x2"
243 in loader.conf. If the drive requires the 4k sector quirk, set the
247 The FAST_DEPEND build option has been removed and its functionality is
248 now the one true way. The old mkdep(1) style of 'make depend' has
249 been removed. See 20160311 for further details.
252 Resource range types have grown from unsigned long to uintmax_t. All
253 drivers, and anything using libdevinfo, need to be recompiled.
256 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
257 builds. It no longer runs mkdep(1) during 'make depend', and the
258 'make depend' stage can safely be skipped now as it is auto ran
259 when building 'make all' and will generate all SRCS and DPSRCS before
260 building anything else. Dependencies are gathered at compile time with
261 -MF flags kept in separate .depend files per object file. Users should
262 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
266 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
267 kernel modules. Therefore, if you load any kernel modules at boot time,
268 please install the boot loaders after you install the kernel, but before
272 make kernel KERNCONF=YOUR_KERNEL_HERE
273 make -C sys/boot install
274 <reboot in single user>
276 Then follow the usual steps, described in the General Notes section,
280 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
281 see the 20141231 entry below for information about prerequisites and
282 upgrading, if you are not already using clang 3.5.0 or higher.
285 The AIO subsystem is now a standard part of the kernel. The
286 VFS_AIO kernel option and aio.ko kernel module have been removed.
287 Due to stability concerns, asynchronous I/O requests are only
288 permitted on sockets and raw disks by default. To enable
289 asynchronous I/O requests on all file types, set the
290 vfs.aio.enable_unsafe sysctl to a non-zero value.
293 The ELF object manipulation tool objcopy is now provided by the
294 ELF Tool Chain project rather than by GNU binutils. It should be a
295 drop-in replacement, with the addition of arm64 support. The
296 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
297 to obtain the GNU version if necessary.
300 Building ZFS pools on top of zvols is prohibited by default. That
301 feature has never worked safely; it's always been prone to deadlocks.
302 Using a zvol as the backing store for a VM guest's virtual disk will
303 still work, even if the guest is using ZFS. Legacy behavior can be
304 restored by setting vfs.zfs.vol.recursive=1.
307 The NONE and HPN patches has been removed from OpenSSH. They are
308 still available in the security/openssh-portable port.
311 With the addition of ypldap(8), a new _ypldap user is now required
312 during installworld. "mergemaster -p" can be used to add the user
313 prior to installworld, as documented in the handbook.
316 The tftp loader (pxeboot) now uses the option root-path directive. As a
317 consequence it no longer looks for a pxeboot.4th file on the tftp
318 server. Instead it uses the regular /boot infrastructure as with the
322 The code to start recording plug and play data into the modules has
323 been committed. While the old tools will properly build a new kernel,
324 a number of warnings about "unknown metadata record 4" will be produced
325 for an older kldxref. To avoid such warnings, make sure to rebuild
326 the kernel toolchain (or world). Make sure that you have r292078 or
327 later when trying to build 292077 or later before rebuilding.
330 Debug data files are now built by default with 'make buildworld' and
331 installed with 'make installworld'. This facilitates debugging but
332 requires more disk space both during the build and for the installed
333 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
337 r291527 changed the internal interface between the nfsd.ko and
338 nfscommon.ko modules. As such, they must both be upgraded to-gether.
339 __FreeBSD_version has been bumped because of this.
342 Add support for unicode collation strings leads to a change of
343 order of files listed by ls(1) for example. To get back to the old
344 behaviour, set LC_COLLATE environment variable to "C".
346 Databases administrators will need to reindex their databases given
347 collation results will be different.
349 Due to a bug in install(1) it is recommended to remove the ancient
350 locales before running make installworld.
352 rm -rf /usr/share/locale/*
355 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
356 libcrypto.so.7 or libssl.so.7 must be recompiled.
359 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
360 Kernel modules isp_2400_multi and isp_2500_multi were removed and
361 should be replaced with isp_2400 and isp_2500 modules respectively.
364 The build previously allowed using 'make -n' to not recurse into
365 sub-directories while showing what commands would be executed, and
366 'make -n -n' to recursively show commands. Now 'make -n' will recurse
367 and 'make -N' will not.
370 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
371 and etcupdate will now use this file. A custom sendmail.cf is now
372 updated via this mechanism rather than via installworld. If you had
373 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
374 want to remove the exclusion or change it to "always install".
375 /etc/mail/sendmail.cf is now managed the same way regardless of
376 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
377 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
380 Compatibility shims for legacy ATA device names have been removed.
381 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
382 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
383 environment variables, /dev/ad* and /dev/ar* symbolic links.
386 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
387 Please see the 20141231 entry below for information about prerequisites
388 and upgrading, if you are not already using clang 3.5.0 or higher.
391 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
392 and renamed from .symbols to .debug. This reduces the size requirements
393 on the boot partition or file system and provides consistency with
394 userland debug files.
396 When using the supported kernel installation method the
397 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
398 as is done with /boot/kernel.
400 Developers wishing to maintain the historical behavior of installing
401 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
404 The wireless drivers had undergone changes that remove the 'parent
405 interface' from the ifconfig -l output. The rc.d network scripts
406 used to check presence of a parent interface in the list, so old
407 scripts would fail to start wireless networking. Thus, etcupdate(3)
408 or mergemaster(8) run is required after kernel update, to update your
409 rc.d scripts in /etc.
412 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
413 These configurations are now automatically interpreted as
414 'scrub fragment reassemble'.
417 Kernel-loadable modules for the random(4) device are back. To use
418 them, the kernel must have
421 options RANDOM_LOADABLE
423 kldload(8) can then be used to load random_fortuna.ko
424 or random_yarrow.ko. Please note that due to the indirect
425 function calls that the loadable modules need to provide,
426 the build-in variants will be slightly more efficient.
428 The random(4) kernel option RANDOM_DUMMY has been retired due to
429 unpopularity. It was not all that useful anyway.
432 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
433 Control over building the ELF Tool Chain tools is now provided by
434 the WITHOUT_TOOLCHAIN knob.
437 The polarity of Pulse Per Second (PPS) capture events with the
438 uart(4) driver has been corrected. Prior to this change the PPS
439 "assert" event corresponded to the trailing edge of a positive PPS
440 pulse and the "clear" event was the leading edge of the next pulse.
442 As the width of a PPS pulse in a typical GPS receiver is on the
443 order of 1 millisecond, most users will not notice any significant
444 difference with this change.
446 Anyone who has compensated for the historical polarity reversal by
447 configuring a negative offset equal to the pulse width will need to
448 remove that workaround.
451 The default group assigned to /dev/dri entries has been changed
452 from 'wheel' to 'video' with the id of '44'. If you want to have
453 access to the dri devices please add yourself to the video group
456 # pw groupmod video -m $USER
459 The menu.rc and loader.rc files will now be replaced during
460 upgrades. Please migrate local changes to menu.rc.local and
461 loader.rc.local instead.
464 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
465 strings and strip have been removed. The src.conf(5) knob
466 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
469 As ZFS requires more kernel stack pages than is the default on some
470 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
471 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
473 Please consider using 'options KSTACK_PAGES=X' where X is greater
474 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
477 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
478 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
479 default, i.e., they will not contain "::". For example, instead
480 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
481 to have a more specific match, such as different map entries for
482 IPv6:0:0 vs IPv6:0. This change requires that configuration
483 data (including maps, files, classes, custom ruleset, etc.) must
484 use the same format, so make certain such configuration data is
485 upgrading. As a very simple check search for patterns like
486 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
487 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
488 the cf option UseCompressedIPv6Addresses.
491 The default kernel entropy-processing algorithm is now
492 Fortuna, replacing Yarrow.
494 Assuming you have 'device random' in your kernel config
495 file, the configurations allow a kernel option to override
496 this default. You may choose *ONE* of:
498 options RANDOM_YARROW # Legacy /dev/random algorithm.
499 options RANDOM_DUMMY # Blocking-only driver.
501 If you have neither, you get Fortuna. For most people,
502 read no further, Fortuna will give a /dev/random that works
503 like it always used to, and the difference will be irrelevant.
505 If you remove 'device random', you get *NO* kernel-processed
506 entropy at all. This may be acceptable to folks building
507 embedded systems, but has complications. Carry on reading,
508 and it is assumed you know what you need.
510 *PLEASE* read random(4) and random(9) if you are in the
511 habit of tweaking kernel configs, and/or if you are a member
512 of the embedded community, wanting specific and not-usual
513 behaviour from your security subsystems.
515 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
516 random', you will NOT have a functioning /dev/random, and
517 many cryptographic features will not work, including SSH.
518 You may also find strange behaviour from the random(3) set
519 of library functions, in particular sranddev(3), srandomdev(3)
520 and arc4random(3). The reason for this is that the KERN_ARND
521 sysctl only returns entropy if it thinks it has some to
522 share, and with RANDOM_DUMMY or no 'device random' this
526 An additional fix for the issue described in the 20150614 sendmail
527 entry below has been been committed in revision 284717.
530 FreeBSD's old make (fmake) has been removed from the system. It is
531 available as the devel/fmake port or via pkg install fmake.
534 The fix for the issue described in the 20150614 sendmail entry
535 below has been been committed in revision 284436. The work
536 around described in that entry is no longer needed unless the
537 default setting is overridden by a confDH_PARAMETERS configuration
538 setting of '5' or pointing to a 512 bit DH parameter file.
541 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
542 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
543 and devel/kyua to version 0.20+ and adjust any calling code to work
544 with Kyuafile and kyua.
547 The import of openssl to address the FreeBSD-SA-15:10.openssl
548 security advisory includes a change which rejects handshakes
549 with DH parameters below 768 bits. sendmail releases prior
550 to 8.15.2 (not yet released), defaulted to a 512 bit
551 DH parameter setting for client connections. To work around
552 this interoperability, sendmail can be configured to use a
553 2048 bit DH parameter by:
555 1. Edit /etc/mail/`hostname`.mc
556 2. If a setting for confDH_PARAMETERS does not exist or
557 exists and is set to a string beginning with '5',
559 3. If a setting for confDH_PARAMETERS exists and is set to
560 a file path, create a new file with:
561 openssl dhparam -out /path/to/file 2048
562 4. Rebuild the .cf file:
563 cd /etc/mail/; make; make install
565 cd /etc/mail/; make restart
567 A sendmail patch is coming, at which time this file will be
571 Generation of legacy formatted entries have been disabled by default
572 in pwd_mkdb(8), as all base system consumers of the legacy formatted
573 entries were converted to use the new format by default when the new,
574 machine independent format have been added and supported since FreeBSD
577 Please see the pwd_mkdb(8) manual page for further details.
580 Clang and llvm have been upgraded to 3.6.1 release. Please see the
581 20141231 entry below for information about prerequisites and upgrading,
582 if you are not already using 3.5.0 or higher.
585 TI platform code switched to using vendor DTS files and this update
586 may break existing systems running on Beaglebone, Beaglebone Black,
589 - dtb files should be regenerated/reinstalled. Filenames are the
590 same but content is different now
591 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
592 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
593 addressing scheme is now pin 25 on /dev/gpioc3.
594 - Pandaboard: /etc/ttys should be updated, serial console device is
595 now /dev/ttyu2, not /dev/ttyu0
598 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
599 If you need the GNU extension from groff soelim(1), install groff
600 from package: pkg install groff, or via ports: textproc/groff.
603 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
604 defined in symlink(7); previously symlinks were silently ignored.
607 The const qualifier has been removed from iconv(3) to comply with
608 POSIX. The ports tree is aware of this from r384038 onwards.
611 Libraries specified by LIBADD in Makefiles must have a corresponding
612 DPADD_<lib> variable to ensure correct dependencies. This is now
613 enforced in src.libnames.mk.
616 From legacy ata(4) driver was removed support for SATA controllers
617 supported by more functional drivers ahci(4), siis(4) and mvs(4).
618 Kernel modules ataahci and ataadaptec were removed completely,
619 replaced by ahci and mvs modules respectively.
622 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
623 the 20141231 entry below for information about prerequisites and
624 upgrading, if you are not already using 3.5.0 or higher.
627 The 32-bit PowerPC kernel has been changed to a position-independent
628 executable. This can only be booted with a version of loader(8)
629 newer than January 31, 2015, so make sure to update both world and
630 kernel before rebooting.
633 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
634 but before r278950, the RNG was not seeded properly. Immediately
635 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
636 ssh keys or openssl keys) that were generated w/ a kernel from that
637 range. This does not affect programs that directly used /dev/random
638 or /dev/urandom. All userland uses of arc4random(3) are affected.
641 The autofs(4) ABI was changed in order to restore binary compatibility
642 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
646 The powerpc64 kernel has been changed to a position-independent
647 executable. This can only be booted with a new version of loader(8),
648 so make sure to update both world and kernel before rebooting.
651 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
652 only release, no new features have been added. Please see the 20141231
653 entry below for information about prerequisites and upgrading, if you
654 are not already using 3.5.0.
657 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
658 taken from the ELF Tool Chain project rather than GNU binutils. They
659 should be drop-in replacements, with the addition of arm64 support.
660 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
661 binutils tools, if necessary. See 20150805 for updated information.
664 The default Unbound configuration now enables remote control
665 using a local socket. Users who have already enabled the
666 local_unbound service should regenerate their configuration
667 by running "service local_unbound setup" as root.
670 The GNU texinfo and GNU info pages have been removed.
671 To be able to view GNU info pages please install texinfo from ports.
674 Clang, llvm and lldb have been upgraded to 3.5.0 release.
676 As of this release, a prerequisite for building clang, llvm and lldb is
677 a C++11 capable compiler and C++11 standard library. This means that to
678 be able to successfully build the cross-tools stage of buildworld, with
679 clang as the bootstrap compiler, your system compiler or cross compiler
680 should either be clang 3.3 or later, or gcc 4.8 or later, and your
681 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
684 On any standard FreeBSD 10.x or 11.x installation, where clang and
685 libc++ are on by default (that is, on x86 or arm), this should work out
688 On 9.x installations where clang is enabled by default, e.g. on x86 and
689 powerpc, libc++ will not be enabled by default, so libc++ should be
690 built (with clang) and installed first. If both clang and libc++ are
691 missing, build clang first, then use it to build libc++.
693 On 8.x and earlier installations, upgrade to 9.x first, and then follow
694 the instructions for 9.x above.
696 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
697 default, and do not build clang.
699 Many embedded systems are resource constrained, and will not be able to
700 build clang in a reasonable time, or in some cases at all. In those
701 cases, cross building bootable systems on amd64 is a workaround.
703 This new version of clang introduces a number of new warnings, of which
704 the following are most likely to appear:
708 This warns in two cases, for both C and C++:
709 * When the code is trying to take the absolute value of an unsigned
710 quantity, which is effectively a no-op, and almost never what was
711 intended. The code should be fixed, if at all possible. If you are
712 sure that the unsigned quantity can be safely cast to signed, without
713 loss of information or undefined behavior, you can add an explicit
714 cast, or disable the warning.
716 * When the code is trying to take an absolute value, but the called
717 abs() variant is for the wrong type, which can lead to truncation.
718 If you want to disable the warning instead of fixing the code, please
719 make sure that truncation will not occur, or it might lead to unwanted
722 -Wtautological-undefined-compare and
723 -Wundefined-bool-conversion
725 These warn when C++ code is trying to compare 'this' against NULL, while
726 'this' should never be NULL in well-defined C++ code. However, there is
727 some legacy (pre C++11) code out there, which actively abuses this
728 feature, which was less strictly defined in previous C++ versions.
730 Squid and openjdk do this, for example. The warning can be turned off
731 for C++98 and earlier, but compiling the code in C++11 mode might result
732 in unexpected behavior; for example, the parts of the program that are
733 unreachable could be optimized away.
736 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
737 kernel sources have been removed. The .h files remain, since some
738 utilities include them. This will need to be fixed later.
739 If "mount -t oldnfs ..." is attempted, it will fail.
740 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
741 the utilities will report errors.
744 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
745 directories to top level SUBDIR variable when their parent
746 directory is included in LOCAL_DIRS. Users with build systems with
747 such hierarchies and without SUBDIR entries in the parent
748 directory Makefiles should add them or add the directories to
752 faith(4) and faithd(8) have been removed from the base system. Faith
753 has been obsolete for a very long time.
756 vt(4), the new console driver, is enabled by default. It brings
757 support for Unicode and double-width characters, as well as
758 support for UEFI and integration with the KMS kernel video
761 You may need to update your console settings in /etc/rc.conf,
762 most probably the keymap. During boot, /etc/rc.d/syscons will
763 indicate what you need to do.
765 vt(4) still has issues and lacks some features compared to
766 syscons(4). See the wiki for up-to-date information:
767 https://wiki.freebsd.org/Newcons
769 If you want to keep using syscons(4), you can do so by adding
770 the following line to /boot/loader.conf:
774 pjdfstest has been integrated into kyua as an opt-in test suite.
775 Please see share/doc/pjdfstest/README for more details on how to
779 gperf has been removed from the base system for architectures
780 that use clang. Ports that require gperf will obtain it from the
784 pjdfstest has been moved from tools/regression/pjdfstest to
788 At svn r271982, The default linux compat kernel ABI has been adjusted
789 to 2.6.18 in support of the linux-c6 compat ports infrastructure
790 update. If you wish to continue using the linux-f10 compat ports,
791 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
792 encouraged to update their linux-compat packages to linux-c6 during
793 their next update cycle.
796 The ofwfb driver, used to provide a graphics console on PowerPC when
797 using vt(4), no longer allows mmap() of all physical memory. This
798 will prevent Xorg on PowerPC with some ATI graphics cards from
799 initializing properly unless x11-servers/xorg-server is updated to
803 The xdev targets have been converted to using TARGET and
804 TARGET_ARCH instead of XDEV and XDEV_ARCH.
807 The default unbound configuration has been modified to address
808 issues with reverse lookups on networks that use private
809 address ranges. If you use the local_unbound service, run
810 "service local_unbound setup" as root to regenerate your
811 configuration, then "service local_unbound reload" to load the
815 The GNU texinfo and GNU info pages are not built and installed
816 anymore, WITH_INFO knob has been added to allow to built and install
818 UPDATE: see 20150102 entry on texinfo's removal
821 The GNU readline library is now an INTERNALLIB - that is, it is
822 statically linked into consumers (GDB and variants) in the base
823 system, and the shared library is no longer installed. The
824 devel/readline port is available for third party software that
828 The Itanium architecture (ia64) has been removed from the list of
829 known architectures. This is the first step in the removal of the
833 Commit r268115 has added NFSv4.1 server support, merged from
834 projects/nfsv4.1-server. Since this includes changes to the
835 internal interfaces between the NFS related modules, a full
836 build of the kernel and modules will be necessary.
837 __FreeBSD_version has been bumped.
840 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
841 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
842 which differs from the behaviour controlled by this knob.)
845 Maximal length of the serial number in CTL was increased from 16 to
846 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
847 and ctld, need to be rebuilt to work with a new kernel.
850 The libatf-c and libatf-c++ major versions were downgraded to 0 and
851 1 respectively to match the upstream numbers. They were out of
852 sync because, when they were originally added to FreeBSD, the
853 upstream versions were not respected. These libraries are private
854 and not yet built by default, so renumbering them should be a
855 non-issue. However, unclean source trees will yield broken test
856 programs once the operator executes "make delete-old-libs" after a
859 Additionally, the atf-sh binary was made private by moving it into
860 /usr/libexec/. Already-built shell test programs will keep the
861 path to the old binary so they will break after "make delete-old"
864 If you are using WITH_TESTS=yes (not the default), wipe the object
865 tree and rebuild from scratch to prevent spurious test failures.
866 This is only needed once: the misnumbered libraries and misplaced
867 binaries have been added to OptionalObsoleteFiles.inc so they will
868 be removed during a clean upgrade.
871 Clang and llvm have been upgraded to 3.4.1 release.
874 We bogusly installed src.opts.mk in /usr/share/mk. This file should
875 be removed to avoid issues in the future (and has been added to
879 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
880 past, it affected all builds that used the bsd.*.mk files. The old
881 behavior was a bug, but people may have relied upon it. To get this
882 behavior back, you can .include /etc/src.conf from /etc/make.conf
883 (which is still global and isn't changed). This also changes the
884 behavior of incremental builds inside the tree of individual
885 directories. Set MAKESYSPATH to ".../share/mk" to do that.
886 Although this has survived make universe and some upgrade scenarios,
887 other upgrade scenarios may have broken. At least one form of
888 temporary breakage was fixed with MAKESYSPATH settings for buildworld
889 as well... In cases where MAKESYSPATH isn't working with this
890 setting, you'll need to set it to the full path to your tree.
892 One side effect of all this cleaning up is that bsd.compiler.mk
893 is no longer implicitly included by bsd.own.mk. If you wish to
894 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
898 The lindev device has been removed since /dev/full has been made a
899 standard device. __FreeBSD_version has been bumped.
902 The knob WITHOUT_VI was added to the base system, which controls
903 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
904 in order to reorder files share/termcap and didn't build ex(1) as a
905 build tool, so building/installing with WITH_VI is highly advised for
906 build hosts for older releases.
908 This issue has been fixed in stable/9 and stable/10 in r277022 and
909 r276991, respectively.
912 The YES_HESIOD knob has been removed. It has been obsolete for
913 a decade. Please move to using WITH_HESIOD instead or your builds
914 will silently lack HESIOD.
917 The uart(4) driver has been changed with respect to its handling
918 of the low-level console. Previously the uart(4) driver prevented
919 any process from changing the baudrate or the CLOCAL and HUPCL
920 control flags. By removing the restrictions, operators can make
921 changes to the serial console port without having to reboot.
922 However, when getty(8) is started on the serial device that is
923 associated with the low-level console, a misconfigured terminal
924 line in /etc/ttys will now have a real impact.
925 Before upgrading the kernel, make sure that /etc/ttys has the
926 serial console device configured as 3wire without baudrate to
927 preserve the previous behaviour. E.g:
928 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
931 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
932 to improve performance. To re-enable it, if needed, run rpcbind
933 with command line option -W.
936 Switched back to the GPL dtc compiler due to updates in the upstream
937 dts files not being supported by the BSDL dtc compiler. You will need
938 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
939 may result while building dtb files during a kernel build if you fail
940 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
943 Clang and llvm have been upgraded to 3.4 release.
946 The nve(4) driver has been removed. Please use the nfe(4) driver
947 for NVIDIA nForce MCP Ethernet adapters instead.
950 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
951 This could cause certain C++ applications using shared libraries built
952 against the previous version of libc++ to crash. The incompatibility
953 has now been fixed, but any C++ applications or shared libraries built
954 between r261283 and r261801 should be recompiled.
957 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
958 capability mode support. Please note that enabling the feature in
959 kernel is still highly recommended.
962 OpenSSH is now built with sandbox support, and will use sandbox as
963 the default privilege separation method. This requires Capsicum
964 capability mode support in kernel.
967 The libelf and libdwarf libraries have been updated to newer
968 versions from upstream. Shared library version numbers for
969 these two libraries were bumped. Any ports or binaries
970 requiring these two libraries should be recompiled.
971 __FreeBSD_version is bumped to 1100006.
974 If a Makefile in a tests/ directory was auto-generating a Kyuafile
975 instead of providing an explicit one, this would prevent such
976 Makefile from providing its own Kyuafile in the future during
977 NO_CLEAN builds. This has been fixed in the Makefiles but manual
978 intervention is needed to clean an objdir if you use NO_CLEAN:
979 # find /usr/obj -name Kyuafile | xargs rm -f
982 The behavior of gss_pseudo_random() for the krb5 mechanism
983 has changed, for applications requesting a longer random string
984 than produced by the underlying enctype's pseudo-random() function.
985 In particular, the random string produced from a session key of
986 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
987 be different at the 17th octet and later, after this change.
988 The counter used in the PRF+ construction is now encoded as a
989 big-endian integer in accordance with RFC 4402.
990 __FreeBSD_version is bumped to 1100004.
993 The WITHOUT_ATF build knob has been removed and its functionality
994 has been subsumed into the more generic WITHOUT_TESTS. If you were
995 using the former to disable the build of the ATF libraries, you
996 should change your settings to use the latter.
999 The default version of mtree is nmtree which is obtained from
1000 NetBSD. The output is generally the same, but may vary
1001 slightly. If you found you need identical output adding
1002 "-F freebsd9" to the command line should do the trick. For the
1003 time being, the old mtree is available as fmtree.
1006 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1007 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1008 1.1.4_8 and verify bsdyml not linked in, before running "make
1010 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1012 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1015 The stable/10 branch has been created in subversion from head
1019 The rc.d/jail script has been updated to support jail(8)
1020 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1021 for per-jail configuration are automatically converted to
1022 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1023 This is transparently backward compatible. See below about some
1024 incompatibilities and rc.conf(5) manual page for more details.
1026 These variables are now deprecated in favor of jail(8) configuration
1027 file. One can use "rc.d/jail config <jname>" command to generate
1028 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1029 running the jail(8) utility. The default pathname of the
1030 configuration file is /etc/jail.conf and can be specified by
1031 using $jail_conf or $jail_<jname>_conf variables.
1033 Please note that jail_devfs_ruleset accepts an integer at
1034 this moment. Please consider to rewrite the ruleset name
1038 BIND has been removed from the base system. If all you need
1039 is a local resolver, simply enable and start the local_unbound
1040 service instead. Otherwise, several versions of BIND are
1041 available in the ports tree. The dns/bind99 port is one example.
1043 With this change, nslookup(1) and dig(1) are no longer in the base
1044 system. Users should instead use host(1) and drill(1) which are
1045 in the base system. Alternatively, nslookup and dig can
1046 be obtained by installing the dns/bind-tools port.
1049 With the addition of unbound(8), a new unbound user is now
1050 required during installworld. "mergemaster -p" can be used to
1051 add the user prior to installworld, as documented in the handbook.
1054 OpenSSH is now built with DNSSEC support, and will by default
1055 silently trust signed SSHFP records. This can be controlled with
1056 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1057 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1060 The GNU Compiler Collection and C++ standard library (libstdc++)
1061 are no longer built by default on platforms where clang is the system
1062 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1063 options in src.conf.
1066 The PROCDESC kernel option is now part of the GENERIC kernel
1067 configuration and is required for the rwhod(8) to work.
1068 If you are using custom kernel configuration, you should include
1072 The API and ABI related to the Capsicum framework was modified
1073 in backward incompatible way. The userland libraries and programs
1074 have to be recompiled to work with the new kernel. This includes the
1075 following libraries and programs, but the whole buildworld is
1076 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1077 kdump, procstat, rwho, rwhod, uniq.
1080 AES-NI intrinsic support has been added to gcc. The AES-NI module
1081 has been updated to use this support. A new gcc is required to build
1082 the aesni module on both i386 and amd64.
1085 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1086 Thus "device padlock_rng" and "device rdrand_rng" should be
1087 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1090 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1091 enables just the iconv* functionality and is now on by default.
1092 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1093 compatibility. Set WITHOUT_ICONV to build the old way.
1094 If you have been using WITH_ICONV before, you will very likely
1095 need to turn on WITH_LIBICONV_COMPAT.
1098 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1099 Illumos origin, including ZFS. If you have INVARIANTS in your
1100 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1102 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1103 locks if WITNESS option was set. Because that generated a lot of
1104 witness(9) reports and all of them were believed to be false
1105 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1106 can be used to achieve the previous behavior.
1109 Timer values in IPv6 data structures now use time_uptime instead
1110 of time_second. Although this is not a user-visible functional
1111 change, userland utilities which directly use them---ndp(8),
1112 rtadvd(8), and rtsold(8) in the base system---need to be updated
1113 to r253970 or later.
1116 find -delete can now delete the pathnames given as arguments,
1117 instead of only files found below them or if the pathname did
1118 not contain any slashes. Formerly, the following error message
1121 find: -delete: <path>: relative path potentially not safe
1123 Deleting the pathnames given as arguments can be prevented
1124 without error messages using -mindepth 1 or by changing
1125 directory and passing "." as argument to find. This works in the
1126 old as well as the new version of find.
1129 Behavior of devfs rules path matching has been changed.
1130 Pattern is now always matched against fully qualified devfs
1131 path and slash characters must be explicitly matched by
1132 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1133 subdirectories must be reviewed.
1136 The default ARM ABI has changed to the ARM EABI. The old ABI is
1137 incompatible with the ARM EABI and all programs and modules will
1138 need to be rebuilt to work with a new kernel.
1140 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1142 NOTE: Support for the old ABI will be removed in the future and
1143 users are advised to upgrade.
1146 pkg_install has been disconnected from the build if you really need it
1147 you should add WITH_PKGTOOLS in your src.conf(5).
1150 Most of network statistics structures were changed to be able
1151 keep 64-bits counters. Thus all tools, that work with networking
1152 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1155 Fix a bug that allowed a tracing process (e.g. gdb) to write
1156 to a memory-mapped file in the traced process's address space
1157 even if neither the traced process nor the tracing process had
1158 write access to that file.
1161 CVS has been removed from the base system. An exact copy
1162 of the code is available from the devel/cvs port.
1165 Some people report the following error after the switch to bmake:
1167 make: illegal option -- J
1168 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1170 *** [buildworld] Error code 2
1172 this likely due to an old instance of make in
1173 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1174 which src/Makefile will use that blindly, if it exists, so if
1175 you see the above error:
1177 rm -rf `make -V MAKEPATH`
1182 Use bmake by default.
1183 Whereas before one could choose to build with bmake via
1184 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1185 make. The goal is to remove these knobs for 10-RELEASE.
1187 It is worth noting that bmake (like gmake) treats the command
1188 line as the unit of failure, rather than statements within the
1189 command line. Thus '(cd some/where && dosomething)' is safer
1190 than 'cd some/where; dosomething'. The '()' allows consistent
1191 behavior in parallel build.
1194 Fix a bug that allows NFS clients to issue READDIR on files.
1197 The WITHOUT_IDEA option has been removed because
1198 the IDEA patent expired.
1201 The sysctl which controls TRIM support under ZFS has been renamed
1202 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1206 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1207 rather than creating it's own in the temporary directory in
1208 order allow access to bootstrapped versions of tools such as
1209 install and mtree. When upgrading from version of FreeBSD where
1210 the install command does not support -l, you will need to
1211 install a new mergemaster command if mergemaster -p is required.
1212 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1216 Legacy ATA stack, disabled and replaced by new CAM-based one since
1217 FreeBSD 9.0, completely removed from the sources. Kernel modules
1218 atadisk and atapi*, user-level tools atacontrol and burncd are
1219 removed. Kernel option `options ATA_CAM` is now permanently enabled
1223 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1224 and socketpair(2). Software, in particular Kerberos, may
1225 automatically detect and use these during building. The resulting
1226 binaries will not work on older kernels.
1229 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1230 information, see the respective 20130304 entry).
1233 Recent commits to callout(9) changed the size of struct callout,
1234 so the KBI is probably heavily disturbed. Also, some functions
1235 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1236 by macros. Every kernel module using it won't load, so rebuild
1239 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1240 but does not initialize by default (because of the new CTL_DISABLE
1241 option) to save memory. To re-enable it, remove the CTL_DISABLE
1242 option from the kernel config file or set kern.cam.ctl.disable=0
1243 in /boot/loader.conf.
1246 The ctl device has been disabled in GENERIC for i386 and amd64.
1247 This was done due to the extra memory being allocated at system
1248 initialisation time by the ctl driver which was only used if
1249 a CAM target device was created. This makes a FreeBSD system
1250 unusable on 128MB or less of RAM.
1253 A new compression method (lz4) has been merged to -HEAD. Please
1254 refer to zpool-features(7) for more information.
1256 Please refer to the "ZFS notes" section of this file for information
1257 on upgrading boot ZFS pools.
1260 A BSD-licensed patch(1) variant has been added and is installed
1261 as bsdpatch, being the GNU version the default patch.
1262 To inverse the logic and use the BSD-licensed one as default,
1263 while having the GNU version installed as gnupatch, rebuild
1264 and install world with the WITH_BSD_PATCH knob set.
1267 Due to the use of the new -l option to install(1) during build
1268 and install, you must take care not to directly set the INSTALL
1269 make variable in your /etc/make.conf, /etc/src.conf, or on the
1270 command line. If you wish to use the -C flag for all installs
1271 you may be able to add INSTALL+=-C to /etc/make.conf or
1275 The install(1) option -M has changed meaning and now takes an
1276 argument that is a file or path to append logs to. In the
1277 unlikely event that -M was the last option on the command line
1278 and the command line contained at least two files and a target
1279 directory the first file will have logs appended to it. The -M
1280 option served little practical purpose in the last decade so its
1281 use is expected to be extremely rare.
1284 After switching to Clang as the default compiler some users of ZFS
1285 on i386 systems started to experience stack overflow kernel panics.
1286 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1289 GEOM_LABEL now mangles label names read from file system metadata.
1290 Mangling affect labels containing spaces, non-printable characters,
1291 '%' or '"'. Device names in /etc/fstab and other places may need to
1295 By default, only the 10 most recent kernel dumps will be saved. To
1296 restore the previous behaviour (no limit on the number of kernel dumps
1297 stored in the dump directory) add the following line to /etc/rc.conf:
1302 With the addition of auditdistd(8), a new auditdistd user is now
1303 required during installworld. "mergemaster -p" can be used to
1304 add the user prior to installworld, as documented in the handbook.
1307 The sin6_scope_id member variable in struct sockaddr_in6 is now
1308 filled by the kernel before passing the structure to the userland via
1309 sysctl or routing socket. This means the KAME-specific embedded scope
1310 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1311 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1312 __FreeBSD_version is bumped to 1000025.
1315 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1316 This means that the world and kernel will be compiled with clang
1317 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1318 and /usr/bin/cpp. To disable this behavior and revert to building
1319 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1320 of current may need to bootstrap WITHOUT_CLANG first if the clang
1321 build fails (its compatibility window doesn't extend to the 9 stable
1325 The IPFIREWALL_FORWARD kernel option has been removed. Its
1326 functionality now turned on by default.
1329 The ZERO_COPY_SOCKET kernel option has been removed and
1330 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1331 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1332 mechanism which is not safe and may result in kernel crashes.
1333 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1334 driver supports disposeable external page sized mbuf storage.
1335 Proper replacements for both zero-copy mechanisms are under
1336 consideration and will eventually lead to complete removal
1337 of the two kernel options.
1340 The IPv4 network stack has been converted to network byte
1341 order. The following modules need to be recompiled together
1342 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1343 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1346 Support for non-MPSAFE filesystems was removed from VFS. The
1347 VFS_VERSION was bumped, all filesystem modules shall be
1351 All the non-MPSAFE filesystems have been disconnected from
1352 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1353 portalfs, smbfs, xfs.
1356 The interface cloning API and ABI has changed. The following
1357 modules need to be recompiled together with kernel:
1358 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1359 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1360 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1363 The sdhci driver was split in two parts: sdhci (generic SD Host
1364 Controller logic) and sdhci_pci (actual hardware driver).
1365 No kernel config modifications are required, but if you
1366 load sdhc as a module you must switch to sdhci_pci instead.
1369 Import the FUSE kernel and userland support into base system.
1372 The GNU sort(1) program has been removed since the BSD-licensed
1373 sort(1) has been the default for quite some time and no serious
1374 problems have been reported. The corresponding WITH_GNU_SORT
1378 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1379 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1383 The net80211(4) ABI has been changed to allow for improved driver
1384 PS-POLL and power-save support. All wireless drivers need to be
1385 recompiled to work with the new kernel.
1388 The random(4) support for the VIA hardware random number
1389 generator (`PADLOCK') is no longer enabled unconditionally.
1390 Add the padlock_rng device in the custom kernel config if
1391 needed. The GENERIC kernels on i386 and amd64 do include the
1392 device, so the change only affects the custom kernel
1396 The pf(4) packet filter ABI has been changed. pfctl(8) and
1397 snmp_pf module need to be recompiled to work with new kernel.
1400 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1401 to -HEAD. Pools that have empty_bpobj in active state can not be
1402 imported read-write with ZFS implementations that do not support
1403 this feature. For more information read the zpool-features(5)
1407 The sparc64 ZFS loader has been changed to no longer try to auto-
1408 detect ZFS providers based on diskN aliases but now requires these
1409 to be explicitly listed in the OFW boot-device environment variable.
1412 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1413 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1414 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1417 The following sysctls and tunables have been renamed for consistency
1418 with other variables:
1419 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1420 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1423 The sort utility has been replaced with BSD sort. For now, GNU sort
1424 is also available as "gnusort" or the default can be set back to
1425 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1426 installed as "bsdsort".
1429 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1430 Starting with this version the old system of ZFS pool versioning
1431 is superseded by "feature flags". This concept enables forward
1432 compatibility against certain future changes in functionality of ZFS
1433 pools. The first read-only compatible "feature flag" for ZFS pools
1434 is named "com.delphix:async_destroy". For more information
1435 read the new zpool-features(5) manual page.
1436 Please refer to the "ZFS notes" section of this file for information
1437 on upgrading boot ZFS pools.
1440 The malloc(3) implementation embedded in libc now uses sources imported
1441 as contrib/jemalloc. The most disruptive API change is to
1442 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1443 delete it prior to installworld, and optionally re-create it using the
1444 new format after rebooting. See malloc.conf(5) for details
1445 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1449 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1450 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1451 now spelled mips. This is to aid compatibility with third-party
1452 software that expects this naming scheme in uname(3). Little-endian
1453 settings are unchanged. If you are updating a big-endian mips64 machine
1454 from before this change, you may need to set MACHINE_ARCH=mips64 in
1455 your environment before the new build system will recognize your machine.
1458 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1462 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1463 nullfs(5) did not pass through all behaviours to the underlying layer,
1464 as a result if we bound to a socket on the lower layer we could connect
1465 only to the lower path; if we bound to the upper layer we could connect
1466 only to the upper path. The new behavior is one can connect to both the
1467 lower and the upper paths regardless what layer path one binds to.
1470 The getifaddrs upgrade path broken with 20111215 has been restored.
1471 If you have upgraded in between 20111215 and 20120209 you need to
1472 recompile libc again with your kernel. You still need to recompile
1473 world to be able to configure CARP but this restriction already
1474 comes from 20111215.
1477 The set_rcvar() function has been removed from /etc/rc.subr. All
1478 base and ports rc.d scripts have been updated, so if you have a
1479 port installed with a script in /usr/local/etc/rc.d you can either
1480 hand-edit the rcvar= line, or reinstall the port.
1482 An easy way to handle the mass-update of /etc/rc.d:
1483 rm /etc/rc.d/* && mergemaster -i
1486 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1487 on the current CPU and prevents other threads from running.
1488 This behavior can be reverted using the kern.stop_scheduler_on_panic
1490 The new behavior can be incompatible with kern.sync_on_panic.
1493 The carp(4) facility has been changed significantly. Configuration
1494 of the CARP protocol via ifconfig(8) has changed, as well as format
1495 of CARP events submitted to devd(8) has changed. See manual pages
1496 for more information. The arpbalance feature of carp(4) is currently
1497 not supported anymore.
1499 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1500 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1501 need to be recompiled.
1504 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1508 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1509 explicitely support non-MPSAFE filesystems.
1510 It is on by default for all supported platform at this present
1514 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1515 i386 and pc98 GENERIC kernel configuration files.
1518 sysinstall has been removed
1521 The stable/9 branch created in subversion. This corresponds to the
1522 RELENG_9 branch in CVS.
1528 Avoid using make -j when upgrading. While generally safe, there are
1529 sometimes problems using -j to upgrade. If your upgrade fails with
1530 -j, please try again without -j. From time to time in the past there
1531 have been problems using -j with buildworld and/or installworld. This
1532 is especially true when upgrading between "distant" versions (eg one
1533 that cross a major release boundary or several minor releases, or when
1534 several months have passed on the -current branch).
1536 Sometimes, obscure build problems are the result of environment
1537 poisoning. This can happen because the make utility reads its
1538 environment when searching for values for global variables. To run
1539 your build attempts in an "environmental clean room", prefix all make
1540 commands with 'env -i '. See the env(1) manual page for more details.
1542 When upgrading from one major version to another it is generally best to
1543 upgrade to the latest code in the currently installed branch first, then
1544 do an upgrade to the new branch. This is the best-tested upgrade path,
1545 and has the highest probability of being successful. Please try this
1546 approach if you encounter problems with a major version upgrade. Since
1547 the stable 4.x branch point, one has generally been able to upgade from
1548 anywhere in the most recent stable branch to head / current (or even the
1549 last couple of stable branches). See the top of this file when there's
1552 When upgrading a live system, having a root shell around before
1553 installing anything can help undo problems. Not having a root shell
1554 around can lead to problems if pam has changed too much from your
1555 starting point to allow continued authentication after the upgrade.
1557 This file should be read as a log of events. When a later event changes
1558 information of a prior event, the prior event should not be deleted.
1559 Instead, a pointer to the entry with the new information should be
1560 placed in the old entry. Readers of this file should also sanity check
1561 older entries before relying on them blindly. Authors of new entries
1562 should write them with this in mind.
1566 When upgrading the boot ZFS pool to a new version, always follow
1569 1.) recompile and reinstall the ZFS boot loader and boot block
1570 (this is part of "make buildworld" and "make installworld")
1572 2.) update the ZFS boot block on your boot drive
1574 The following example updates the ZFS boot block on the first
1575 partition (freebsd-boot) of a GPT partitioned drive ada0:
1576 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1578 Non-boot pools do not need these updates.
1582 If you are updating from a prior version of FreeBSD (even one just
1583 a few days old), you should follow this procedure. It is the most
1584 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1586 make kernel-toolchain
1587 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1588 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1590 To test a kernel once
1591 ---------------------
1592 If you just want to boot a kernel once (because you are not sure
1593 if it works, or if you want to boot a known bad kernel to provide
1594 debugging information) run
1595 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1596 nextboot -k testkernel
1598 To just build a kernel when you know that it won't mess you up
1599 --------------------------------------------------------------
1600 This assumes you are already running a CURRENT system. Replace
1601 ${arch} with the architecture of your machine (e.g. "i386",
1602 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1604 cd src/sys/${arch}/conf
1605 config KERNEL_NAME_HERE
1606 cd ../compile/KERNEL_NAME_HERE
1611 If this fails, go to the "To build a kernel" section.
1613 To rebuild everything and install it on the current system.
1614 -----------------------------------------------------------
1615 # Note: sometimes if you are running current you gotta do more than
1616 # is listed here if you are upgrading from a really old current.
1618 <make sure you have good level 0 dumps>
1620 make kernel KERNCONF=YOUR_KERNEL_HERE
1622 <reboot in single user> [3]
1629 To cross-install current onto a separate partition
1630 --------------------------------------------------
1631 # In this approach we use a separate partition to hold
1632 # current's root, 'usr', and 'var' directories. A partition
1633 # holding "/", "/usr" and "/var" should be about 2GB in
1636 <make sure you have good level 0 dumps>
1639 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1640 <maybe newfs current's root partition>
1641 <mount current's root partition on directory ${CURRENT_ROOT}>
1642 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1643 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1644 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1645 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1646 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1647 <reboot into current>
1648 <do a "native" rebuild/install as described in the previous section>
1649 <maybe install compatibility libraries from ports/misc/compat*>
1653 To upgrade in-place from stable to current
1654 ----------------------------------------------
1655 <make sure you have good level 0 dumps>
1657 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1659 <reboot in single user> [3]
1666 Make sure that you've read the UPDATING file to understand the
1667 tweaks to various things you need. At this point in the life
1668 cycle of current, things change often and you are on your own
1669 to cope. The defaults can also change, so please read ALL of
1670 the UPDATING entries.
1672 Also, if you are tracking -current, you must be subscribed to
1673 freebsd-current@freebsd.org. Make sure that before you update
1674 your sources that you have read and understood all the recent
1675 messages there. If in doubt, please track -stable which has
1676 much fewer pitfalls.
1678 [1] If you have third party modules, such as vmware, you
1679 should disable them at this point so they don't crash your
1682 [3] From the bootblocks, boot -s, and then do
1687 adjkerntz -i # if CMOS is wall time
1688 Also, when doing a major release upgrade, it is required that
1689 you boot into single user mode to do the installworld.
1691 [4] Note: This step is non-optional. Failure to do this step
1692 can result in a significant reduction in the functionality of the
1693 system. Attempting to do it by hand is not recommended and those
1694 that pursue this avenue should read this file carefully, as well
1695 as the archives of freebsd-current and freebsd-hackers mailing lists
1696 for potential gotchas. The -U option is also useful to consider.
1697 See mergemaster(8) for more information.
1699 [5] Usually this step is a noop. However, from time to time
1700 you may need to do this if you get unknown user in the following
1701 step. It never hurts to do it all the time. You may need to
1702 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1703 install) after the buildworld before this step if you last updated
1704 from current before 20130425 or from -stable before 20130430.
1706 [6] This only deletes old files and directories. Old libraries
1707 can be deleted by "make delete-old-libs", but you have to make
1708 sure that no program is using those libraries anymore.
1710 [8] In order to have a kernel that can run the 4.x binaries needed to
1711 do an installworld, you must include the COMPAT_FREEBSD4 option in
1712 your kernel. Failure to do so may leave you with a system that is
1713 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1714 required to run the 5.x binaries on more recent kernels. And so on
1715 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1717 Make sure that you merge any new devices from GENERIC since the
1718 last time you updated your kernel config file.
1720 [9] When checking out sources, you must include the -P flag to have
1721 cvs prune empty directories.
1723 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1724 "?=" instead of the "=" assignment operator, so that buildworld can
1725 override the CPUTYPE if it needs to.
1727 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1728 not on the command line, or in /etc/make.conf. buildworld will
1729 warn if it is improperly defined.
1732 This file contains a list, in reverse chronological order, of major
1733 breakages in tracking -current. It is not guaranteed to be a complete
1734 list of such breakages, and only contains entries since September 23, 2011.
1735 If you need to see UPDATING entries from before that date, you will need
1736 to fetch an UPDATING file from an older FreeBSD release.
1738 Copyright information:
1740 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1742 Redistribution, publication, translation and use, with or without
1743 modification, in full or in part, in any form or format of this
1744 document are permitted without further permission from the author.
1746 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1747 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1748 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1749 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1750 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1751 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1752 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1753 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1754 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1755 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1756 POSSIBILITY OF SUCH DAMAGE.
1758 Contact Warner Losh if you have any questions about your use of