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 igb(4), em(4) and lem(4) ethernet drivers are now implemented via
56 IFLIB. If you have a custom kernel configuration that excludes em(4)
57 but you use igb(4), you need to re-add em(4) to your custom configuration.
60 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
61 Please see the 20141231 entry below for information about prerequisites
62 and upgrading, if you are not already using clang 3.5.0 or higher.
65 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
66 Please see the 20141231 entry below for information about prerequisites
67 and upgrading, if you are not already using clang 3.5.0 or higher.
70 The layout of the pmap structure has changed for powerpc to put the pmap
71 statistics at the front for all CPU variations. libkvm(3) and all tools
72 that link against it need to be recompiled.
75 isl(4) and cyapa(4) drivers now require a new driver,
76 chromebook_platform(4), to work properly on Chromebook-class hardware.
77 On other types of hardware the drivers may need to be configured using
78 device hints. Please see the corresponding manual pages for details.
81 The urtwn(4) driver was merged into rtwn(4) and now consists of
82 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
84 Also, firmware for RTL8188CE was renamed due to possible name
85 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
88 GNU rcs has been removed from base. It is available as packages:
89 - rcs: Latest GPLv3 GNU rcs version.
90 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
94 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
95 modules now requires that the kernel configuration contain the
96 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
99 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
100 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
103 Relocatable object files with the extension of .So have been renamed
104 to use an extension of .pico instead. The purpose of this change is
105 to avoid a name clash with shared libraries on case-insensitive file
106 systems. On those file systems, foo.So is the same file as foo.so.
109 GNU rcs has been turned off by default. It can (temporarily) be built
110 again by adding WITH_RCS knob in src.conf.
111 Otherwise, GNU rcs is available from packages:
112 - rcs: Latest GPLv3 GNU rcs version.
113 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
116 The backup_uses_rcs functionality has been removed from rc.subr.
119 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
120 two separate components, QUEUE_MACRO_DEBUG_TRACE and
121 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
122 QUEUE_MACRO_DEBUG behavior.
125 r304787 changed some ioctl interfaces between the iSCSI userspace
126 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
127 rebuilt to work with new kernels. __FreeBSD_version has been bumped
131 The UDP receive code has been updated to only treat incoming UDP
132 packets that were addressed to an L2 broadcast address as L3
133 broadcast packets. It is not expected that this will affect any
134 standards-conforming UDP application. The new behaviour can be
135 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
139 Remove the openbsd_poll system call.
140 __FreeBSD_version has been bumped because of this.
143 The libc stub for the pipe(2) system call has been replaced with
144 a wrapper that calls the pipe2(2) system call and the pipe(2)
145 system call is now only implemented by the kernels that include
146 "options COMPAT_FREEBSD10" in their config file (this is the
147 default). Users should ensure that this option is enabled in
148 their kernel or upgrade userspace to r302092 before upgrading their
152 CAM will now strip leading spaces from SCSI disks' serial numbers.
153 This will affect users who create UFS filesystems on SCSI disks using
154 those disk's diskid device nodes. For example, if /etc/fstab
155 previously contained a line like
156 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
157 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
158 transforms like gmirror may also be affected. ZFS users should
162 The bitstring(3) API has been updated with new functionality and
163 improved performance. But it is binary-incompatible with the old API.
164 Objects built with the new headers may not be linked against objects
165 built with the old headers.
168 The brk and sbrk functions have been removed from libc on arm64.
169 Binutils from ports has been updated to not link to these
170 functions and should be updated to the latest version before
171 installing a new libc.
174 The armv6 port now defaults to hard float ABI. Limited support
175 for running both hardfloat and soft float on the same system
176 is available using the libraries installed with -DWITH_LIBSOFT.
177 This has only been tested as an upgrade path for installworld
178 and packages may fail or need manual intervention to run. New
179 packages will be needed.
181 To update an existing self-hosted armv6hf system, you must add
182 TARGET_ARCH=armv6 on the make command line for both the build
183 and the install steps.
186 Kernel modules compiled outside of a kernel build now default to
187 installing to /boot/modules instead of /boot/kernel. Many kernel
188 modules built this way (such as those in ports) already overrode
189 KMODDIR explicitly to install into /boot/modules. However,
190 manually building and installing a module from /sys/modules will
191 now install to /boot/modules instead of /boot/kernel.
194 The CAM I/O scheduler has been committed to the kernel. There should be
195 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
196 list of known rogues that claim support for this but actually corrupt
197 data is believed to be complete, be on the lookout for data
198 corruption. The known rogue list is believed to be complete:
200 o Crucial MX100, M550 drives with MU01 firmware.
201 o Micron M510 and M550 drives with MU01 firmware.
202 o Micron M500 prior to MU07 firmware
203 o Samsung 830, 840, and 850 all firmwares
204 o FCCT M500 all firmwares
206 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
207 with working NCQ TRIM. For Micron branded drives, see your sales rep for
208 updated firmware. Black listed drives will work correctly because these
209 drives work correctly so long as no NCQ TRIMs are sent to them. Given
210 this list is the same as found in Linux, it's believed there are no
211 other rogues in the market place. All other models from the above
214 To be safe, if you are at all concerned, you can quirk each of your
215 drives to prevent NCQ from being sent by setting:
216 kern.cam.ada.X.quirks="0x2"
217 in loader.conf. If the drive requires the 4k sector quirk, set the
221 The FAST_DEPEND build option has been removed and its functionality is
222 now the one true way. The old mkdep(1) style of 'make depend' has
223 been removed. See 20160311 for further details.
226 Resource range types have grown from unsigned long to uintmax_t. All
227 drivers, and anything using libdevinfo, need to be recompiled.
230 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
231 builds. It no longer runs mkdep(1) during 'make depend', and the
232 'make depend' stage can safely be skipped now as it is auto ran
233 when building 'make all' and will generate all SRCS and DPSRCS before
234 building anything else. Dependencies are gathered at compile time with
235 -MF flags kept in separate .depend files per object file. Users should
236 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
240 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
241 kernel modules. Therefore, if you load any kernel modules at boot time,
242 please install the boot loaders after you install the kernel, but before
246 make kernel KERNCONF=YOUR_KERNEL_HERE
247 make -C sys/boot install
248 <reboot in single user>
250 Then follow the usual steps, described in the General Notes section,
254 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
255 see the 20141231 entry below for information about prerequisites and
256 upgrading, if you are not already using clang 3.5.0 or higher.
259 The AIO subsystem is now a standard part of the kernel. The
260 VFS_AIO kernel option and aio.ko kernel module have been removed.
261 Due to stability concerns, asynchronous I/O requests are only
262 permitted on sockets and raw disks by default. To enable
263 asynchronous I/O requests on all file types, set the
264 vfs.aio.enable_unsafe sysctl to a non-zero value.
267 The ELF object manipulation tool objcopy is now provided by the
268 ELF Tool Chain project rather than by GNU binutils. It should be a
269 drop-in replacement, with the addition of arm64 support. The
270 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
271 to obtain the GNU version if necessary.
274 Building ZFS pools on top of zvols is prohibited by default. That
275 feature has never worked safely; it's always been prone to deadlocks.
276 Using a zvol as the backing store for a VM guest's virtual disk will
277 still work, even if the guest is using ZFS. Legacy behavior can be
278 restored by setting vfs.zfs.vol.recursive=1.
281 The NONE and HPN patches has been removed from OpenSSH. They are
282 still available in the security/openssh-portable port.
285 With the addition of ypldap(8), a new _ypldap user is now required
286 during installworld. "mergemaster -p" can be used to add the user
287 prior to installworld, as documented in the handbook.
290 The tftp loader (pxeboot) now uses the option root-path directive. As a
291 consequence it no longer looks for a pxeboot.4th file on the tftp
292 server. Instead it uses the regular /boot infrastructure as with the
296 The code to start recording plug and play data into the modules has
297 been committed. While the old tools will properly build a new kernel,
298 a number of warnings about "unknown metadata record 4" will be produced
299 for an older kldxref. To avoid such warnings, make sure to rebuild
300 the kernel toolchain (or world). Make sure that you have r292078 or
301 later when trying to build 292077 or later before rebuilding.
304 Debug data files are now built by default with 'make buildworld' and
305 installed with 'make installworld'. This facilitates debugging but
306 requires more disk space both during the build and for the installed
307 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
311 r291527 changed the internal interface between the nfsd.ko and
312 nfscommon.ko modules. As such, they must both be upgraded to-gether.
313 __FreeBSD_version has been bumped because of this.
316 Add support for unicode collation strings leads to a change of
317 order of files listed by ls(1) for example. To get back to the old
318 behaviour, set LC_COLLATE environment variable to "C".
320 Databases administrators will need to reindex their databases given
321 collation results will be different.
323 Due to a bug in install(1) it is recommended to remove the ancient
324 locales before running make installworld.
326 rm -rf /usr/share/locale/*
329 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
330 libcrypto.so.7 or libssl.so.7 must be recompiled.
333 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
334 Kernel modules isp_2400_multi and isp_2500_multi were removed and
335 should be replaced with isp_2400 and isp_2500 modules respectively.
338 The build previously allowed using 'make -n' to not recurse into
339 sub-directories while showing what commands would be executed, and
340 'make -n -n' to recursively show commands. Now 'make -n' will recurse
341 and 'make -N' will not.
344 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
345 and etcupdate will now use this file. A custom sendmail.cf is now
346 updated via this mechanism rather than via installworld. If you had
347 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
348 want to remove the exclusion or change it to "always install".
349 /etc/mail/sendmail.cf is now managed the same way regardless of
350 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
351 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
354 Compatibility shims for legacy ATA device names have been removed.
355 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
356 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
357 environment variables, /dev/ad* and /dev/ar* symbolic links.
360 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
361 Please see the 20141231 entry below for information about prerequisites
362 and upgrading, if you are not already using clang 3.5.0 or higher.
365 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
366 and renamed from .symbols to .debug. This reduces the size requirements
367 on the boot partition or file system and provides consistency with
368 userland debug files.
370 When using the supported kernel installation method the
371 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
372 as is done with /boot/kernel.
374 Developers wishing to maintain the historical behavior of installing
375 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
378 The wireless drivers had undergone changes that remove the 'parent
379 interface' from the ifconfig -l output. The rc.d network scripts
380 used to check presence of a parent interface in the list, so old
381 scripts would fail to start wireless networking. Thus, etcupdate(3)
382 or mergemaster(8) run is required after kernel update, to update your
383 rc.d scripts in /etc.
386 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
387 These configurations are now automatically interpreted as
388 'scrub fragment reassemble'.
391 Kernel-loadable modules for the random(4) device are back. To use
392 them, the kernel must have
395 options RANDOM_LOADABLE
397 kldload(8) can then be used to load random_fortuna.ko
398 or random_yarrow.ko. Please note that due to the indirect
399 function calls that the loadable modules need to provide,
400 the build-in variants will be slightly more efficient.
402 The random(4) kernel option RANDOM_DUMMY has been retired due to
403 unpopularity. It was not all that useful anyway.
406 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
407 Control over building the ELF Tool Chain tools is now provided by
408 the WITHOUT_TOOLCHAIN knob.
411 The polarity of Pulse Per Second (PPS) capture events with the
412 uart(4) driver has been corrected. Prior to this change the PPS
413 "assert" event corresponded to the trailing edge of a positive PPS
414 pulse and the "clear" event was the leading edge of the next pulse.
416 As the width of a PPS pulse in a typical GPS receiver is on the
417 order of 1 millisecond, most users will not notice any significant
418 difference with this change.
420 Anyone who has compensated for the historical polarity reversal by
421 configuring a negative offset equal to the pulse width will need to
422 remove that workaround.
425 The default group assigned to /dev/dri entries has been changed
426 from 'wheel' to 'video' with the id of '44'. If you want to have
427 access to the dri devices please add yourself to the video group
430 # pw groupmod video -m $USER
433 The menu.rc and loader.rc files will now be replaced during
434 upgrades. Please migrate local changes to menu.rc.local and
435 loader.rc.local instead.
438 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
439 strings and strip have been removed. The src.conf(5) knob
440 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
443 As ZFS requires more kernel stack pages than is the default on some
444 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
445 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
447 Please consider using 'options KSTACK_PAGES=X' where X is greater
448 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
451 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
452 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
453 default, i.e., they will not contain "::". For example, instead
454 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
455 to have a more specific match, such as different map entries for
456 IPv6:0:0 vs IPv6:0. This change requires that configuration
457 data (including maps, files, classes, custom ruleset, etc.) must
458 use the same format, so make certain such configuration data is
459 upgrading. As a very simple check search for patterns like
460 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
461 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
462 the cf option UseCompressedIPv6Addresses.
465 The default kernel entropy-processing algorithm is now
466 Fortuna, replacing Yarrow.
468 Assuming you have 'device random' in your kernel config
469 file, the configurations allow a kernel option to override
470 this default. You may choose *ONE* of:
472 options RANDOM_YARROW # Legacy /dev/random algorithm.
473 options RANDOM_DUMMY # Blocking-only driver.
475 If you have neither, you get Fortuna. For most people,
476 read no further, Fortuna will give a /dev/random that works
477 like it always used to, and the difference will be irrelevant.
479 If you remove 'device random', you get *NO* kernel-processed
480 entropy at all. This may be acceptable to folks building
481 embedded systems, but has complications. Carry on reading,
482 and it is assumed you know what you need.
484 *PLEASE* read random(4) and random(9) if you are in the
485 habit of tweaking kernel configs, and/or if you are a member
486 of the embedded community, wanting specific and not-usual
487 behaviour from your security subsystems.
489 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
490 random', you will NOT have a functioning /dev/random, and
491 many cryptographic features will not work, including SSH.
492 You may also find strange behaviour from the random(3) set
493 of library functions, in particular sranddev(3), srandomdev(3)
494 and arc4random(3). The reason for this is that the KERN_ARND
495 sysctl only returns entropy if it thinks it has some to
496 share, and with RANDOM_DUMMY or no 'device random' this
500 An additional fix for the issue described in the 20150614 sendmail
501 entry below has been been committed in revision 284717.
504 FreeBSD's old make (fmake) has been removed from the system. It is
505 available as the devel/fmake port or via pkg install fmake.
508 The fix for the issue described in the 20150614 sendmail entry
509 below has been been committed in revision 284436. The work
510 around described in that entry is no longer needed unless the
511 default setting is overridden by a confDH_PARAMETERS configuration
512 setting of '5' or pointing to a 512 bit DH parameter file.
515 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
516 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
517 and devel/kyua to version 0.20+ and adjust any calling code to work
518 with Kyuafile and kyua.
521 The import of openssl to address the FreeBSD-SA-15:10.openssl
522 security advisory includes a change which rejects handshakes
523 with DH parameters below 768 bits. sendmail releases prior
524 to 8.15.2 (not yet released), defaulted to a 512 bit
525 DH parameter setting for client connections. To work around
526 this interoperability, sendmail can be configured to use a
527 2048 bit DH parameter by:
529 1. Edit /etc/mail/`hostname`.mc
530 2. If a setting for confDH_PARAMETERS does not exist or
531 exists and is set to a string beginning with '5',
533 3. If a setting for confDH_PARAMETERS exists and is set to
534 a file path, create a new file with:
535 openssl dhparam -out /path/to/file 2048
536 4. Rebuild the .cf file:
537 cd /etc/mail/; make; make install
539 cd /etc/mail/; make restart
541 A sendmail patch is coming, at which time this file will be
545 Generation of legacy formatted entries have been disabled by default
546 in pwd_mkdb(8), as all base system consumers of the legacy formatted
547 entries were converted to use the new format by default when the new,
548 machine independent format have been added and supported since FreeBSD
551 Please see the pwd_mkdb(8) manual page for further details.
554 Clang and llvm have been upgraded to 3.6.1 release. Please see the
555 20141231 entry below for information about prerequisites and upgrading,
556 if you are not already using 3.5.0 or higher.
559 TI platform code switched to using vendor DTS files and this update
560 may break existing systems running on Beaglebone, Beaglebone Black,
563 - dtb files should be regenerated/reinstalled. Filenames are the
564 same but content is different now
565 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
566 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
567 addressing scheme is now pin 25 on /dev/gpioc3.
568 - Pandaboard: /etc/ttys should be updated, serial console device is
569 now /dev/ttyu2, not /dev/ttyu0
572 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
573 If you need the GNU extension from groff soelim(1), install groff
574 from package: pkg install groff, or via ports: textproc/groff.
577 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
578 defined in symlink(7); previously symlinks were silently ignored.
581 The const qualifier has been removed from iconv(3) to comply with
582 POSIX. The ports tree is aware of this from r384038 onwards.
585 Libraries specified by LIBADD in Makefiles must have a corresponding
586 DPADD_<lib> variable to ensure correct dependencies. This is now
587 enforced in src.libnames.mk.
590 From legacy ata(4) driver was removed support for SATA controllers
591 supported by more functional drivers ahci(4), siis(4) and mvs(4).
592 Kernel modules ataahci and ataadaptec were removed completely,
593 replaced by ahci and mvs modules respectively.
596 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
597 the 20141231 entry below for information about prerequisites and
598 upgrading, if you are not already using 3.5.0 or higher.
601 The 32-bit PowerPC kernel has been changed to a position-independent
602 executable. This can only be booted with a version of loader(8)
603 newer than January 31, 2015, so make sure to update both world and
604 kernel before rebooting.
607 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
608 but before r278950, the RNG was not seeded properly. Immediately
609 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
610 ssh keys or openssl keys) that were generated w/ a kernel from that
611 range. This does not affect programs that directly used /dev/random
612 or /dev/urandom. All userland uses of arc4random(3) are affected.
615 The autofs(4) ABI was changed in order to restore binary compatibility
616 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
620 The powerpc64 kernel has been changed to a position-independent
621 executable. This can only be booted with a new version of loader(8),
622 so make sure to update both world and kernel before rebooting.
625 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
626 only release, no new features have been added. Please see the 20141231
627 entry below for information about prerequisites and upgrading, if you
628 are not already using 3.5.0.
631 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
632 taken from the ELF Tool Chain project rather than GNU binutils. They
633 should be drop-in replacements, with the addition of arm64 support.
634 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
635 binutils tools, if necessary. See 20150805 for updated information.
638 The default Unbound configuration now enables remote control
639 using a local socket. Users who have already enabled the
640 local_unbound service should regenerate their configuration
641 by running "service local_unbound setup" as root.
644 The GNU texinfo and GNU info pages have been removed.
645 To be able to view GNU info pages please install texinfo from ports.
648 Clang, llvm and lldb have been upgraded to 3.5.0 release.
650 As of this release, a prerequisite for building clang, llvm and lldb is
651 a C++11 capable compiler and C++11 standard library. This means that to
652 be able to successfully build the cross-tools stage of buildworld, with
653 clang as the bootstrap compiler, your system compiler or cross compiler
654 should either be clang 3.3 or later, or gcc 4.8 or later, and your
655 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
658 On any standard FreeBSD 10.x or 11.x installation, where clang and
659 libc++ are on by default (that is, on x86 or arm), this should work out
662 On 9.x installations where clang is enabled by default, e.g. on x86 and
663 powerpc, libc++ will not be enabled by default, so libc++ should be
664 built (with clang) and installed first. If both clang and libc++ are
665 missing, build clang first, then use it to build libc++.
667 On 8.x and earlier installations, upgrade to 9.x first, and then follow
668 the instructions for 9.x above.
670 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
671 default, and do not build clang.
673 Many embedded systems are resource constrained, and will not be able to
674 build clang in a reasonable time, or in some cases at all. In those
675 cases, cross building bootable systems on amd64 is a workaround.
677 This new version of clang introduces a number of new warnings, of which
678 the following are most likely to appear:
682 This warns in two cases, for both C and C++:
683 * When the code is trying to take the absolute value of an unsigned
684 quantity, which is effectively a no-op, and almost never what was
685 intended. The code should be fixed, if at all possible. If you are
686 sure that the unsigned quantity can be safely cast to signed, without
687 loss of information or undefined behavior, you can add an explicit
688 cast, or disable the warning.
690 * When the code is trying to take an absolute value, but the called
691 abs() variant is for the wrong type, which can lead to truncation.
692 If you want to disable the warning instead of fixing the code, please
693 make sure that truncation will not occur, or it might lead to unwanted
696 -Wtautological-undefined-compare and
697 -Wundefined-bool-conversion
699 These warn when C++ code is trying to compare 'this' against NULL, while
700 'this' should never be NULL in well-defined C++ code. However, there is
701 some legacy (pre C++11) code out there, which actively abuses this
702 feature, which was less strictly defined in previous C++ versions.
704 Squid and openjdk do this, for example. The warning can be turned off
705 for C++98 and earlier, but compiling the code in C++11 mode might result
706 in unexpected behavior; for example, the parts of the program that are
707 unreachable could be optimized away.
710 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
711 kernel sources have been removed. The .h files remain, since some
712 utilities include them. This will need to be fixed later.
713 If "mount -t oldnfs ..." is attempted, it will fail.
714 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
715 the utilities will report errors.
718 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
719 directories to top level SUBDIR variable when their parent
720 directory is included in LOCAL_DIRS. Users with build systems with
721 such hierarchies and without SUBDIR entries in the parent
722 directory Makefiles should add them or add the directories to
726 faith(4) and faithd(8) have been removed from the base system. Faith
727 has been obsolete for a very long time.
730 vt(4), the new console driver, is enabled by default. It brings
731 support for Unicode and double-width characters, as well as
732 support for UEFI and integration with the KMS kernel video
735 You may need to update your console settings in /etc/rc.conf,
736 most probably the keymap. During boot, /etc/rc.d/syscons will
737 indicate what you need to do.
739 vt(4) still has issues and lacks some features compared to
740 syscons(4). See the wiki for up-to-date information:
741 https://wiki.freebsd.org/Newcons
743 If you want to keep using syscons(4), you can do so by adding
744 the following line to /boot/loader.conf:
748 pjdfstest has been integrated into kyua as an opt-in test suite.
749 Please see share/doc/pjdfstest/README for more details on how to
753 gperf has been removed from the base system for architectures
754 that use clang. Ports that require gperf will obtain it from the
758 pjdfstest has been moved from tools/regression/pjdfstest to
762 At svn r271982, The default linux compat kernel ABI has been adjusted
763 to 2.6.18 in support of the linux-c6 compat ports infrastructure
764 update. If you wish to continue using the linux-f10 compat ports,
765 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
766 encouraged to update their linux-compat packages to linux-c6 during
767 their next update cycle.
770 The ofwfb driver, used to provide a graphics console on PowerPC when
771 using vt(4), no longer allows mmap() of all physical memory. This
772 will prevent Xorg on PowerPC with some ATI graphics cards from
773 initializing properly unless x11-servers/xorg-server is updated to
777 The xdev targets have been converted to using TARGET and
778 TARGET_ARCH instead of XDEV and XDEV_ARCH.
781 The default unbound configuration has been modified to address
782 issues with reverse lookups on networks that use private
783 address ranges. If you use the local_unbound service, run
784 "service local_unbound setup" as root to regenerate your
785 configuration, then "service local_unbound reload" to load the
789 The GNU texinfo and GNU info pages are not built and installed
790 anymore, WITH_INFO knob has been added to allow to built and install
792 UPDATE: see 20150102 entry on texinfo's removal
795 The GNU readline library is now an INTERNALLIB - that is, it is
796 statically linked into consumers (GDB and variants) in the base
797 system, and the shared library is no longer installed. The
798 devel/readline port is available for third party software that
802 The Itanium architecture (ia64) has been removed from the list of
803 known architectures. This is the first step in the removal of the
807 Commit r268115 has added NFSv4.1 server support, merged from
808 projects/nfsv4.1-server. Since this includes changes to the
809 internal interfaces between the NFS related modules, a full
810 build of the kernel and modules will be necessary.
811 __FreeBSD_version has been bumped.
814 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
815 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
816 which differs from the behaviour controlled by this knob.)
819 Maximal length of the serial number in CTL was increased from 16 to
820 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
821 and ctld, need to be rebuilt to work with a new kernel.
824 The libatf-c and libatf-c++ major versions were downgraded to 0 and
825 1 respectively to match the upstream numbers. They were out of
826 sync because, when they were originally added to FreeBSD, the
827 upstream versions were not respected. These libraries are private
828 and not yet built by default, so renumbering them should be a
829 non-issue. However, unclean source trees will yield broken test
830 programs once the operator executes "make delete-old-libs" after a
833 Additionally, the atf-sh binary was made private by moving it into
834 /usr/libexec/. Already-built shell test programs will keep the
835 path to the old binary so they will break after "make delete-old"
838 If you are using WITH_TESTS=yes (not the default), wipe the object
839 tree and rebuild from scratch to prevent spurious test failures.
840 This is only needed once: the misnumbered libraries and misplaced
841 binaries have been added to OptionalObsoleteFiles.inc so they will
842 be removed during a clean upgrade.
845 Clang and llvm have been upgraded to 3.4.1 release.
848 We bogusly installed src.opts.mk in /usr/share/mk. This file should
849 be removed to avoid issues in the future (and has been added to
853 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
854 past, it affected all builds that used the bsd.*.mk files. The old
855 behavior was a bug, but people may have relied upon it. To get this
856 behavior back, you can .include /etc/src.conf from /etc/make.conf
857 (which is still global and isn't changed). This also changes the
858 behavior of incremental builds inside the tree of individual
859 directories. Set MAKESYSPATH to ".../share/mk" to do that.
860 Although this has survived make universe and some upgrade scenarios,
861 other upgrade scenarios may have broken. At least one form of
862 temporary breakage was fixed with MAKESYSPATH settings for buildworld
863 as well... In cases where MAKESYSPATH isn't working with this
864 setting, you'll need to set it to the full path to your tree.
866 One side effect of all this cleaning up is that bsd.compiler.mk
867 is no longer implicitly included by bsd.own.mk. If you wish to
868 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
872 The lindev device has been removed since /dev/full has been made a
873 standard device. __FreeBSD_version has been bumped.
876 The knob WITHOUT_VI was added to the base system, which controls
877 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
878 in order to reorder files share/termcap and didn't build ex(1) as a
879 build tool, so building/installing with WITH_VI is highly advised for
880 build hosts for older releases.
882 This issue has been fixed in stable/9 and stable/10 in r277022 and
883 r276991, respectively.
886 The YES_HESIOD knob has been removed. It has been obsolete for
887 a decade. Please move to using WITH_HESIOD instead or your builds
888 will silently lack HESIOD.
891 The uart(4) driver has been changed with respect to its handling
892 of the low-level console. Previously the uart(4) driver prevented
893 any process from changing the baudrate or the CLOCAL and HUPCL
894 control flags. By removing the restrictions, operators can make
895 changes to the serial console port without having to reboot.
896 However, when getty(8) is started on the serial device that is
897 associated with the low-level console, a misconfigured terminal
898 line in /etc/ttys will now have a real impact.
899 Before upgrading the kernel, make sure that /etc/ttys has the
900 serial console device configured as 3wire without baudrate to
901 preserve the previous behaviour. E.g:
902 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
905 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
906 to improve performance. To re-enable it, if needed, run rpcbind
907 with command line option -W.
910 Switched back to the GPL dtc compiler due to updates in the upstream
911 dts files not being supported by the BSDL dtc compiler. You will need
912 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
913 may result while building dtb files during a kernel build if you fail
914 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
917 Clang and llvm have been upgraded to 3.4 release.
920 The nve(4) driver has been removed. Please use the nfe(4) driver
921 for NVIDIA nForce MCP Ethernet adapters instead.
924 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
925 This could cause certain C++ applications using shared libraries built
926 against the previous version of libc++ to crash. The incompatibility
927 has now been fixed, but any C++ applications or shared libraries built
928 between r261283 and r261801 should be recompiled.
931 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
932 capability mode support. Please note that enabling the feature in
933 kernel is still highly recommended.
936 OpenSSH is now built with sandbox support, and will use sandbox as
937 the default privilege separation method. This requires Capsicum
938 capability mode support in kernel.
941 The libelf and libdwarf libraries have been updated to newer
942 versions from upstream. Shared library version numbers for
943 these two libraries were bumped. Any ports or binaries
944 requiring these two libraries should be recompiled.
945 __FreeBSD_version is bumped to 1100006.
948 If a Makefile in a tests/ directory was auto-generating a Kyuafile
949 instead of providing an explicit one, this would prevent such
950 Makefile from providing its own Kyuafile in the future during
951 NO_CLEAN builds. This has been fixed in the Makefiles but manual
952 intervention is needed to clean an objdir if you use NO_CLEAN:
953 # find /usr/obj -name Kyuafile | xargs rm -f
956 The behavior of gss_pseudo_random() for the krb5 mechanism
957 has changed, for applications requesting a longer random string
958 than produced by the underlying enctype's pseudo-random() function.
959 In particular, the random string produced from a session key of
960 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
961 be different at the 17th octet and later, after this change.
962 The counter used in the PRF+ construction is now encoded as a
963 big-endian integer in accordance with RFC 4402.
964 __FreeBSD_version is bumped to 1100004.
967 The WITHOUT_ATF build knob has been removed and its functionality
968 has been subsumed into the more generic WITHOUT_TESTS. If you were
969 using the former to disable the build of the ATF libraries, you
970 should change your settings to use the latter.
973 The default version of mtree is nmtree which is obtained from
974 NetBSD. The output is generally the same, but may vary
975 slightly. If you found you need identical output adding
976 "-F freebsd9" to the command line should do the trick. For the
977 time being, the old mtree is available as fmtree.
980 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
981 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
982 1.1.4_8 and verify bsdyml not linked in, before running "make
984 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
986 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
989 The stable/10 branch has been created in subversion from head
993 The rc.d/jail script has been updated to support jail(8)
994 configuration file. The "jail_<jname>_*" rc.conf(5) variables
995 for per-jail configuration are automatically converted to
996 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
997 This is transparently backward compatible. See below about some
998 incompatibilities and rc.conf(5) manual page for more details.
1000 These variables are now deprecated in favor of jail(8) configuration
1001 file. One can use "rc.d/jail config <jname>" command to generate
1002 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1003 running the jail(8) utility. The default pathname of the
1004 configuration file is /etc/jail.conf and can be specified by
1005 using $jail_conf or $jail_<jname>_conf variables.
1007 Please note that jail_devfs_ruleset accepts an integer at
1008 this moment. Please consider to rewrite the ruleset name
1012 BIND has been removed from the base system. If all you need
1013 is a local resolver, simply enable and start the local_unbound
1014 service instead. Otherwise, several versions of BIND are
1015 available in the ports tree. The dns/bind99 port is one example.
1017 With this change, nslookup(1) and dig(1) are no longer in the base
1018 system. Users should instead use host(1) and drill(1) which are
1019 in the base system. Alternatively, nslookup and dig can
1020 be obtained by installing the dns/bind-tools port.
1023 With the addition of unbound(8), a new unbound user is now
1024 required during installworld. "mergemaster -p" can be used to
1025 add the user prior to installworld, as documented in the handbook.
1028 OpenSSH is now built with DNSSEC support, and will by default
1029 silently trust signed SSHFP records. This can be controlled with
1030 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1031 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1034 The GNU Compiler Collection and C++ standard library (libstdc++)
1035 are no longer built by default on platforms where clang is the system
1036 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1037 options in src.conf.
1040 The PROCDESC kernel option is now part of the GENERIC kernel
1041 configuration and is required for the rwhod(8) to work.
1042 If you are using custom kernel configuration, you should include
1046 The API and ABI related to the Capsicum framework was modified
1047 in backward incompatible way. The userland libraries and programs
1048 have to be recompiled to work with the new kernel. This includes the
1049 following libraries and programs, but the whole buildworld is
1050 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1051 kdump, procstat, rwho, rwhod, uniq.
1054 AES-NI intrinsic support has been added to gcc. The AES-NI module
1055 has been updated to use this support. A new gcc is required to build
1056 the aesni module on both i386 and amd64.
1059 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1060 Thus "device padlock_rng" and "device rdrand_rng" should be
1061 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1064 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1065 enables just the iconv* functionality and is now on by default.
1066 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1067 compatibility. Set WITHOUT_ICONV to build the old way.
1068 If you have been using WITH_ICONV before, you will very likely
1069 need to turn on WITH_LIBICONV_COMPAT.
1072 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1073 Illumos origin, including ZFS. If you have INVARIANTS in your
1074 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1076 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1077 locks if WITNESS option was set. Because that generated a lot of
1078 witness(9) reports and all of them were believed to be false
1079 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1080 can be used to achieve the previous behavior.
1083 Timer values in IPv6 data structures now use time_uptime instead
1084 of time_second. Although this is not a user-visible functional
1085 change, userland utilities which directly use them---ndp(8),
1086 rtadvd(8), and rtsold(8) in the base system---need to be updated
1087 to r253970 or later.
1090 find -delete can now delete the pathnames given as arguments,
1091 instead of only files found below them or if the pathname did
1092 not contain any slashes. Formerly, the following error message
1095 find: -delete: <path>: relative path potentially not safe
1097 Deleting the pathnames given as arguments can be prevented
1098 without error messages using -mindepth 1 or by changing
1099 directory and passing "." as argument to find. This works in the
1100 old as well as the new version of find.
1103 Behavior of devfs rules path matching has been changed.
1104 Pattern is now always matched against fully qualified devfs
1105 path and slash characters must be explicitly matched by
1106 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1107 subdirectories must be reviewed.
1110 The default ARM ABI has changed to the ARM EABI. The old ABI is
1111 incompatible with the ARM EABI and all programs and modules will
1112 need to be rebuilt to work with a new kernel.
1114 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1116 NOTE: Support for the old ABI will be removed in the future and
1117 users are advised to upgrade.
1120 pkg_install has been disconnected from the build if you really need it
1121 you should add WITH_PKGTOOLS in your src.conf(5).
1124 Most of network statistics structures were changed to be able
1125 keep 64-bits counters. Thus all tools, that work with networking
1126 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1129 Fix a bug that allowed a tracing process (e.g. gdb) to write
1130 to a memory-mapped file in the traced process's address space
1131 even if neither the traced process nor the tracing process had
1132 write access to that file.
1135 CVS has been removed from the base system. An exact copy
1136 of the code is available from the devel/cvs port.
1139 Some people report the following error after the switch to bmake:
1141 make: illegal option -- J
1142 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1144 *** [buildworld] Error code 2
1146 this likely due to an old instance of make in
1147 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1148 which src/Makefile will use that blindly, if it exists, so if
1149 you see the above error:
1151 rm -rf `make -V MAKEPATH`
1156 Use bmake by default.
1157 Whereas before one could choose to build with bmake via
1158 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1159 make. The goal is to remove these knobs for 10-RELEASE.
1161 It is worth noting that bmake (like gmake) treats the command
1162 line as the unit of failure, rather than statements within the
1163 command line. Thus '(cd some/where && dosomething)' is safer
1164 than 'cd some/where; dosomething'. The '()' allows consistent
1165 behavior in parallel build.
1168 Fix a bug that allows NFS clients to issue READDIR on files.
1171 The WITHOUT_IDEA option has been removed because
1172 the IDEA patent expired.
1175 The sysctl which controls TRIM support under ZFS has been renamed
1176 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1180 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1181 rather than creating it's own in the temporary directory in
1182 order allow access to bootstrapped versions of tools such as
1183 install and mtree. When upgrading from version of FreeBSD where
1184 the install command does not support -l, you will need to
1185 install a new mergemaster command if mergemaster -p is required.
1186 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1190 Legacy ATA stack, disabled and replaced by new CAM-based one since
1191 FreeBSD 9.0, completely removed from the sources. Kernel modules
1192 atadisk and atapi*, user-level tools atacontrol and burncd are
1193 removed. Kernel option `options ATA_CAM` is now permanently enabled
1197 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1198 and socketpair(2). Software, in particular Kerberos, may
1199 automatically detect and use these during building. The resulting
1200 binaries will not work on older kernels.
1203 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1204 information, see the respective 20130304 entry).
1207 Recent commits to callout(9) changed the size of struct callout,
1208 so the KBI is probably heavily disturbed. Also, some functions
1209 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1210 by macros. Every kernel module using it won't load, so rebuild
1213 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1214 but does not initialize by default (because of the new CTL_DISABLE
1215 option) to save memory. To re-enable it, remove the CTL_DISABLE
1216 option from the kernel config file or set kern.cam.ctl.disable=0
1217 in /boot/loader.conf.
1220 The ctl device has been disabled in GENERIC for i386 and amd64.
1221 This was done due to the extra memory being allocated at system
1222 initialisation time by the ctl driver which was only used if
1223 a CAM target device was created. This makes a FreeBSD system
1224 unusable on 128MB or less of RAM.
1227 A new compression method (lz4) has been merged to -HEAD. Please
1228 refer to zpool-features(7) for more information.
1230 Please refer to the "ZFS notes" section of this file for information
1231 on upgrading boot ZFS pools.
1234 A BSD-licensed patch(1) variant has been added and is installed
1235 as bsdpatch, being the GNU version the default patch.
1236 To inverse the logic and use the BSD-licensed one as default,
1237 while having the GNU version installed as gnupatch, rebuild
1238 and install world with the WITH_BSD_PATCH knob set.
1241 Due to the use of the new -l option to install(1) during build
1242 and install, you must take care not to directly set the INSTALL
1243 make variable in your /etc/make.conf, /etc/src.conf, or on the
1244 command line. If you wish to use the -C flag for all installs
1245 you may be able to add INSTALL+=-C to /etc/make.conf or
1249 The install(1) option -M has changed meaning and now takes an
1250 argument that is a file or path to append logs to. In the
1251 unlikely event that -M was the last option on the command line
1252 and the command line contained at least two files and a target
1253 directory the first file will have logs appended to it. The -M
1254 option served little practical purpose in the last decade so its
1255 use is expected to be extremely rare.
1258 After switching to Clang as the default compiler some users of ZFS
1259 on i386 systems started to experience stack overflow kernel panics.
1260 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1263 GEOM_LABEL now mangles label names read from file system metadata.
1264 Mangling affect labels containing spaces, non-printable characters,
1265 '%' or '"'. Device names in /etc/fstab and other places may need to
1269 By default, only the 10 most recent kernel dumps will be saved. To
1270 restore the previous behaviour (no limit on the number of kernel dumps
1271 stored in the dump directory) add the following line to /etc/rc.conf:
1276 With the addition of auditdistd(8), a new auditdistd user is now
1277 required during installworld. "mergemaster -p" can be used to
1278 add the user prior to installworld, as documented in the handbook.
1281 The sin6_scope_id member variable in struct sockaddr_in6 is now
1282 filled by the kernel before passing the structure to the userland via
1283 sysctl or routing socket. This means the KAME-specific embedded scope
1284 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1285 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1286 __FreeBSD_version is bumped to 1000025.
1289 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1290 This means that the world and kernel will be compiled with clang
1291 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1292 and /usr/bin/cpp. To disable this behavior and revert to building
1293 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1294 of current may need to bootstrap WITHOUT_CLANG first if the clang
1295 build fails (its compatibility window doesn't extend to the 9 stable
1299 The IPFIREWALL_FORWARD kernel option has been removed. Its
1300 functionality now turned on by default.
1303 The ZERO_COPY_SOCKET kernel option has been removed and
1304 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1305 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1306 mechanism which is not safe and may result in kernel crashes.
1307 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1308 driver supports disposeable external page sized mbuf storage.
1309 Proper replacements for both zero-copy mechanisms are under
1310 consideration and will eventually lead to complete removal
1311 of the two kernel options.
1314 The IPv4 network stack has been converted to network byte
1315 order. The following modules need to be recompiled together
1316 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1317 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1320 Support for non-MPSAFE filesystems was removed from VFS. The
1321 VFS_VERSION was bumped, all filesystem modules shall be
1325 All the non-MPSAFE filesystems have been disconnected from
1326 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1327 portalfs, smbfs, xfs.
1330 The interface cloning API and ABI has changed. The following
1331 modules need to be recompiled together with kernel:
1332 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1333 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1334 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1337 The sdhci driver was split in two parts: sdhci (generic SD Host
1338 Controller logic) and sdhci_pci (actual hardware driver).
1339 No kernel config modifications are required, but if you
1340 load sdhc as a module you must switch to sdhci_pci instead.
1343 Import the FUSE kernel and userland support into base system.
1346 The GNU sort(1) program has been removed since the BSD-licensed
1347 sort(1) has been the default for quite some time and no serious
1348 problems have been reported. The corresponding WITH_GNU_SORT
1352 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1353 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1357 The net80211(4) ABI has been changed to allow for improved driver
1358 PS-POLL and power-save support. All wireless drivers need to be
1359 recompiled to work with the new kernel.
1362 The random(4) support for the VIA hardware random number
1363 generator (`PADLOCK') is no longer enabled unconditionally.
1364 Add the padlock_rng device in the custom kernel config if
1365 needed. The GENERIC kernels on i386 and amd64 do include the
1366 device, so the change only affects the custom kernel
1370 The pf(4) packet filter ABI has been changed. pfctl(8) and
1371 snmp_pf module need to be recompiled to work with new kernel.
1374 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1375 to -HEAD. Pools that have empty_bpobj in active state can not be
1376 imported read-write with ZFS implementations that do not support
1377 this feature. For more information read the zpool-features(5)
1381 The sparc64 ZFS loader has been changed to no longer try to auto-
1382 detect ZFS providers based on diskN aliases but now requires these
1383 to be explicitly listed in the OFW boot-device environment variable.
1386 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1387 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1388 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1391 The following sysctls and tunables have been renamed for consistency
1392 with other variables:
1393 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1394 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1397 The sort utility has been replaced with BSD sort. For now, GNU sort
1398 is also available as "gnusort" or the default can be set back to
1399 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1400 installed as "bsdsort".
1403 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1404 Starting with this version the old system of ZFS pool versioning
1405 is superseded by "feature flags". This concept enables forward
1406 compatibility against certain future changes in functionality of ZFS
1407 pools. The first read-only compatible "feature flag" for ZFS pools
1408 is named "com.delphix:async_destroy". For more information
1409 read the new zpool-features(5) manual page.
1410 Please refer to the "ZFS notes" section of this file for information
1411 on upgrading boot ZFS pools.
1414 The malloc(3) implementation embedded in libc now uses sources imported
1415 as contrib/jemalloc. The most disruptive API change is to
1416 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1417 delete it prior to installworld, and optionally re-create it using the
1418 new format after rebooting. See malloc.conf(5) for details
1419 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1423 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1424 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1425 now spelled mips. This is to aid compatibility with third-party
1426 software that expects this naming scheme in uname(3). Little-endian
1427 settings are unchanged. If you are updating a big-endian mips64 machine
1428 from before this change, you may need to set MACHINE_ARCH=mips64 in
1429 your environment before the new build system will recognize your machine.
1432 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1436 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1437 nullfs(5) did not pass through all behaviours to the underlying layer,
1438 as a result if we bound to a socket on the lower layer we could connect
1439 only to the lower path; if we bound to the upper layer we could connect
1440 only to the upper path. The new behavior is one can connect to both the
1441 lower and the upper paths regardless what layer path one binds to.
1444 The getifaddrs upgrade path broken with 20111215 has been restored.
1445 If you have upgraded in between 20111215 and 20120209 you need to
1446 recompile libc again with your kernel. You still need to recompile
1447 world to be able to configure CARP but this restriction already
1448 comes from 20111215.
1451 The set_rcvar() function has been removed from /etc/rc.subr. All
1452 base and ports rc.d scripts have been updated, so if you have a
1453 port installed with a script in /usr/local/etc/rc.d you can either
1454 hand-edit the rcvar= line, or reinstall the port.
1456 An easy way to handle the mass-update of /etc/rc.d:
1457 rm /etc/rc.d/* && mergemaster -i
1460 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1461 on the current CPU and prevents other threads from running.
1462 This behavior can be reverted using the kern.stop_scheduler_on_panic
1464 The new behavior can be incompatible with kern.sync_on_panic.
1467 The carp(4) facility has been changed significantly. Configuration
1468 of the CARP protocol via ifconfig(8) has changed, as well as format
1469 of CARP events submitted to devd(8) has changed. See manual pages
1470 for more information. The arpbalance feature of carp(4) is currently
1471 not supported anymore.
1473 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1474 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1475 need to be recompiled.
1478 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1482 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1483 explicitely support non-MPSAFE filesystems.
1484 It is on by default for all supported platform at this present
1488 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1489 i386 and pc98 GENERIC kernel configuration files.
1492 sysinstall has been removed
1495 The stable/9 branch created in subversion. This corresponds to the
1496 RELENG_9 branch in CVS.
1502 Avoid using make -j when upgrading. While generally safe, there are
1503 sometimes problems using -j to upgrade. If your upgrade fails with
1504 -j, please try again without -j. From time to time in the past there
1505 have been problems using -j with buildworld and/or installworld. This
1506 is especially true when upgrading between "distant" versions (eg one
1507 that cross a major release boundary or several minor releases, or when
1508 several months have passed on the -current branch).
1510 Sometimes, obscure build problems are the result of environment
1511 poisoning. This can happen because the make utility reads its
1512 environment when searching for values for global variables. To run
1513 your build attempts in an "environmental clean room", prefix all make
1514 commands with 'env -i '. See the env(1) manual page for more details.
1516 When upgrading from one major version to another it is generally best to
1517 upgrade to the latest code in the currently installed branch first, then
1518 do an upgrade to the new branch. This is the best-tested upgrade path,
1519 and has the highest probability of being successful. Please try this
1520 approach if you encounter problems with a major version upgrade. Since
1521 the stable 4.x branch point, one has generally been able to upgade from
1522 anywhere in the most recent stable branch to head / current (or even the
1523 last couple of stable branches). See the top of this file when there's
1526 When upgrading a live system, having a root shell around before
1527 installing anything can help undo problems. Not having a root shell
1528 around can lead to problems if pam has changed too much from your
1529 starting point to allow continued authentication after the upgrade.
1531 This file should be read as a log of events. When a later event changes
1532 information of a prior event, the prior event should not be deleted.
1533 Instead, a pointer to the entry with the new information should be
1534 placed in the old entry. Readers of this file should also sanity check
1535 older entries before relying on them blindly. Authors of new entries
1536 should write them with this in mind.
1540 When upgrading the boot ZFS pool to a new version, always follow
1543 1.) recompile and reinstall the ZFS boot loader and boot block
1544 (this is part of "make buildworld" and "make installworld")
1546 2.) update the ZFS boot block on your boot drive
1548 The following example updates the ZFS boot block on the first
1549 partition (freebsd-boot) of a GPT partitioned drive ada0:
1550 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1552 Non-boot pools do not need these updates.
1556 If you are updating from a prior version of FreeBSD (even one just
1557 a few days old), you should follow this procedure. It is the most
1558 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1560 make kernel-toolchain
1561 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1562 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1564 To test a kernel once
1565 ---------------------
1566 If you just want to boot a kernel once (because you are not sure
1567 if it works, or if you want to boot a known bad kernel to provide
1568 debugging information) run
1569 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1570 nextboot -k testkernel
1572 To just build a kernel when you know that it won't mess you up
1573 --------------------------------------------------------------
1574 This assumes you are already running a CURRENT system. Replace
1575 ${arch} with the architecture of your machine (e.g. "i386",
1576 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1578 cd src/sys/${arch}/conf
1579 config KERNEL_NAME_HERE
1580 cd ../compile/KERNEL_NAME_HERE
1585 If this fails, go to the "To build a kernel" section.
1587 To rebuild everything and install it on the current system.
1588 -----------------------------------------------------------
1589 # Note: sometimes if you are running current you gotta do more than
1590 # is listed here if you are upgrading from a really old current.
1592 <make sure you have good level 0 dumps>
1594 make kernel KERNCONF=YOUR_KERNEL_HERE
1596 <reboot in single user> [3]
1603 To cross-install current onto a separate partition
1604 --------------------------------------------------
1605 # In this approach we use a separate partition to hold
1606 # current's root, 'usr', and 'var' directories. A partition
1607 # holding "/", "/usr" and "/var" should be about 2GB in
1610 <make sure you have good level 0 dumps>
1613 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1614 <maybe newfs current's root partition>
1615 <mount current's root partition on directory ${CURRENT_ROOT}>
1616 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1617 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1618 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1619 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1620 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1621 <reboot into current>
1622 <do a "native" rebuild/install as described in the previous section>
1623 <maybe install compatibility libraries from ports/misc/compat*>
1627 To upgrade in-place from stable to current
1628 ----------------------------------------------
1629 <make sure you have good level 0 dumps>
1631 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1633 <reboot in single user> [3]
1640 Make sure that you've read the UPDATING file to understand the
1641 tweaks to various things you need. At this point in the life
1642 cycle of current, things change often and you are on your own
1643 to cope. The defaults can also change, so please read ALL of
1644 the UPDATING entries.
1646 Also, if you are tracking -current, you must be subscribed to
1647 freebsd-current@freebsd.org. Make sure that before you update
1648 your sources that you have read and understood all the recent
1649 messages there. If in doubt, please track -stable which has
1650 much fewer pitfalls.
1652 [1] If you have third party modules, such as vmware, you
1653 should disable them at this point so they don't crash your
1656 [3] From the bootblocks, boot -s, and then do
1661 adjkerntz -i # if CMOS is wall time
1662 Also, when doing a major release upgrade, it is required that
1663 you boot into single user mode to do the installworld.
1665 [4] Note: This step is non-optional. Failure to do this step
1666 can result in a significant reduction in the functionality of the
1667 system. Attempting to do it by hand is not recommended and those
1668 that pursue this avenue should read this file carefully, as well
1669 as the archives of freebsd-current and freebsd-hackers mailing lists
1670 for potential gotchas. The -U option is also useful to consider.
1671 See mergemaster(8) for more information.
1673 [5] Usually this step is a noop. However, from time to time
1674 you may need to do this if you get unknown user in the following
1675 step. It never hurts to do it all the time. You may need to
1676 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1677 install) after the buildworld before this step if you last updated
1678 from current before 20130425 or from -stable before 20130430.
1680 [6] This only deletes old files and directories. Old libraries
1681 can be deleted by "make delete-old-libs", but you have to make
1682 sure that no program is using those libraries anymore.
1684 [8] In order to have a kernel that can run the 4.x binaries needed to
1685 do an installworld, you must include the COMPAT_FREEBSD4 option in
1686 your kernel. Failure to do so may leave you with a system that is
1687 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1688 required to run the 5.x binaries on more recent kernels. And so on
1689 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1691 Make sure that you merge any new devices from GENERIC since the
1692 last time you updated your kernel config file.
1694 [9] When checking out sources, you must include the -P flag to have
1695 cvs prune empty directories.
1697 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1698 "?=" instead of the "=" assignment operator, so that buildworld can
1699 override the CPUTYPE if it needs to.
1701 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1702 not on the command line, or in /etc/make.conf. buildworld will
1703 warn if it is improperly defined.
1706 This file contains a list, in reverse chronological order, of major
1707 breakages in tracking -current. It is not guaranteed to be a complete
1708 list of such breakages, and only contains entries since September 23, 2011.
1709 If you need to see UPDATING entries from before that date, you will need
1710 to fetch an UPDATING file from an older FreeBSD release.
1712 Copyright information:
1714 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1716 Redistribution, publication, translation and use, with or without
1717 modification, in full or in part, in any form or format of this
1718 document are permitted without further permission from the author.
1720 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1721 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1722 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1723 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1724 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1725 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1726 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1727 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1728 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1729 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1730 POSSIBILITY OF SUCH DAMAGE.
1732 Contact Warner Losh if you have any questions about your use of