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 post-date the fix so you can move from them
45 to -current. This differs from the historical situation where one could
46 upgrade from anywhere on the last couple of stable branches, so be
49 ****************************** SPECIAL WARNING: ******************************
52 The urtwn(4) driver was merged into rtwn(4) and now consists of
53 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
55 Also, firmware for RTL8188CE was renamed due to possible name
56 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
59 GNU rcs has been removed from base. It is available as packages:
60 - rcs: Latest GPLv3 GNU rcs version.
61 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
65 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
66 modules now requires that the kernel configuration contain the
67 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
70 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
71 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
74 Relocatable object files with the extension of .So have been renamed
75 to use an extension of .pico instead. The purpose of this change is
76 to avoid a name clash with shared libraries on case-insensitive file
77 systems. On those file systems, foo.So is the same file as foo.so.
80 GNU rcs has been turned off by default. It can (temporarily) be built
81 again by adding WITH_RCS knob in src.conf.
82 Otherwise, GNU rcs is available from packages:
83 - rcs: Latest GPLv3 GNU rcs version.
84 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
87 The backup_uses_rcs functionality has been removed from rc.subr.
90 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
91 two separate components, QUEUE_MACRO_DEBUG_TRACE and
92 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
93 QUEUE_MACRO_DEBUG behavior.
96 r304787 changed some ioctl interfaces between the iSCSI userspace
97 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
98 rebuilt to work with new kernels. __FreeBSD_version has been bumped
102 The UDP receive code has been updated to only treat incoming UDP
103 packets that were addressed to an L2 broadcast address as L3
104 broadcast packets. It is not expected that this will affect any
105 standards-conforming UDP application. The new behaviour can be
106 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
110 Remove the openbsd_poll system call.
111 __FreeBSD_version has been bumped because of this.
114 The libc stub for the pipe(2) system call has been replaced with
115 a wrapper that calls the pipe2(2) system call and the pipe(2)
116 system call is now only implemented by the kernels that include
117 "options COMPAT_FREEBSD10" in their config file (this is the
118 default). Users should ensure that this option is enabled in
119 their kernel or upgrade userspace to r302092 before upgrading their
123 CAM will now strip leading spaces from SCSI disks' serial numbers.
124 This will effect users who create UFS filesystems on SCSI disks using
125 those disk's diskid device nodes. For example, if /etc/fstab
126 previously contained a line like
127 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
128 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
129 transforms like gmirror may also be affected. ZFS users should
133 The bitstring(3) API has been updated with new functionality and
134 improved performance. But it is binary-incompatible with the old API.
135 Objects built with the new headers may not be linked against objects
136 built with the old headers.
139 The brk and sbrk functions have been removed from libc on arm64.
140 Binutils from ports has been updated to not link to these
141 functions and should be updated to the latest version before
142 installing a new libc.
145 The armv6 port now defaults to hard float ABI. Limited support
146 for running both hardfloat and soft float on the same system
147 is available using the libraries installed with -DWITH_LIBSOFT.
148 This has only been tested as an upgrade path for installworld
149 and packages may fail or need manual intervention to run. New
150 packages will be needed.
152 To update an existing self-hosted armv6hf system, you must add
153 TARGET_ARCH=armv6 on the make command line for both the build
154 and the install steps.
157 Kernel modules compiled outside of a kernel build now default to
158 installing to /boot/modules instead of /boot/kernel. Many kernel
159 modules built this way (such as those in ports) already overrode
160 KMODDIR explicitly to install into /boot/modules. However,
161 manually building and installing a module from /sys/modules will
162 now install to /boot/modules instead of /boot/kernel.
165 The CAM I/O scheduler has been committed to the kernel. There should be
166 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
167 list of known rogues that claim support for this but actually corrupt
168 data is believed to be complete, be on the lookout for data
169 corruption. The known rogue list is believed to be complete:
171 o Crucial MX100, M550 drives with MU01 firmware.
172 o Micron M510 and M550 drives with MU01 firmware.
173 o Micron M500 prior to MU07 firmware
174 o Samsung 830, 840, and 850 all firmwares
175 o FCCT M500 all firmwares
177 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
178 with working NCQ TRIM. For Micron branded drives, see your sales rep for
179 updated firmware. Black listed drives will work correctly because these
180 drives work correctly so long as no NCQ TRIMs are sent to them. Given
181 this list is the same as found in Linux, it's believed there are no
182 other rogues in the market place. All other models from the above
185 To be safe, if you are at all concerned, you can quirk each of your
186 drives to prevent NCQ from being sent by setting:
187 kern.cam.ada.X.quirks="0x2"
188 in loader.conf. If the drive requires the 4k sector quirk, set the
192 The FAST_DEPEND build option has been removed and its functionality is
193 now the one true way. The old mkdep(1) style of 'make depend' has
194 been removed. See 20160311 for further details.
197 Resource range types have grown from unsigned long to uintmax_t. All
198 drivers, and anything using libdevinfo, need to be recompiled.
201 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
202 builds. It no longer runs mkdep(1) during 'make depend', and the
203 'make depend' stage can safely be skipped now as it is auto ran
204 when building 'make all' and will generate all SRCS and DPSRCS before
205 building anything else. Dependencies are gathered at compile time with
206 -MF flags kept in separate .depend files per object file. Users should
207 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
211 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
212 kernel modules. Therefore, if you load any kernel modules at boot time,
213 please install the boot loaders after you install the kernel, but before
217 make kernel KERNCONF=YOUR_KERNEL_HERE
218 make -C sys/boot install
219 <reboot in single user>
221 Then follow the usual steps, described in the General Notes section,
225 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
226 see the 20141231 entry below for information about prerequisites and
227 upgrading, if you are not already using clang 3.5.0 or higher.
230 The AIO subsystem is now a standard part of the kernel. The
231 VFS_AIO kernel option and aio.ko kernel module have been removed.
232 Due to stability concerns, asynchronous I/O requests are only
233 permitted on sockets and raw disks by default. To enable
234 asynchronous I/O requests on all file types, set the
235 vfs.aio.enable_unsafe sysctl to a non-zero value.
238 The ELF object manipulation tool objcopy is now provided by the
239 ELF Tool Chain project rather than by GNU binutils. It should be a
240 drop-in replacement, with the addition of arm64 support. The
241 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
242 to obtain the GNU version if necessary.
245 Building ZFS pools on top of zvols is prohibited by default. That
246 feature has never worked safely; it's always been prone to deadlocks.
247 Using a zvol as the backing store for a VM guest's virtual disk will
248 still work, even if the guest is using ZFS. Legacy behavior can be
249 restored by setting vfs.zfs.vol.recursive=1.
252 The NONE and HPN patches has been removed from OpenSSH. They are
253 still available in the security/openssh-portable port.
256 With the addition of ypldap(8), a new _ypldap user is now required
257 during installworld. "mergemaster -p" can be used to add the user
258 prior to installworld, as documented in the handbook.
261 The tftp loader (pxeboot) now uses the option root-path directive. As a
262 consequence it no longer looks for a pxeboot.4th file on the tftp
263 server. Instead it uses the regular /boot infrastructure as with the
267 The code to start recording plug and play data into the modules has
268 been committed. While the old tools will properly build a new kernel,
269 a number of warnings about "unknown metadata record 4" will be produced
270 for an older kldxref. To avoid such warnings, make sure to rebuild
271 the kernel toolchain (or world). Make sure that you have r292078 or
272 later when trying to build 292077 or later before rebuilding.
275 Debug data files are now built by default with 'make buildworld' and
276 installed with 'make installworld'. This facilitates debugging but
277 requires more disk space both during the build and for the installed
278 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
282 r291527 changed the internal interface between the nfsd.ko and
283 nfscommon.ko modules. As such, they must both be upgraded to-gether.
284 __FreeBSD_version has been bumped because of this.
287 Add support for unicode collation strings leads to a change of
288 order of files listed by ls(1) for example. To get back to the old
289 behaviour, set LC_COLLATE environment variable to "C".
291 Databases administrators will need to reindex their databases given
292 collation results will be different.
294 Due to a bug in install(1) it is recommended to remove the ancient
295 locales before running make installworld.
297 rm -rf /usr/share/locale/*
300 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
301 libcrypto.so.7 or libssl.so.7 must be recompiled.
304 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
305 Kernel modules isp_2400_multi and isp_2500_multi were removed and
306 should be replaced with isp_2400 and isp_2500 modules respectively.
309 The build previously allowed using 'make -n' to not recurse into
310 sub-directories while showing what commands would be executed, and
311 'make -n -n' to recursively show commands. Now 'make -n' will recurse
312 and 'make -N' will not.
315 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
316 and etcupdate will now use this file. A custom sendmail.cf is now
317 updated via this mechanism rather than via installworld. If you had
318 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
319 want to remove the exclusion or change it to "always install".
320 /etc/mail/sendmail.cf is now managed the same way regardless of
321 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
322 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
325 Compatibility shims for legacy ATA device names have been removed.
326 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
327 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
328 environment variables, /dev/ad* and /dev/ar* symbolic links.
331 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
332 Please see the 20141231 entry below for information about prerequisites
333 and upgrading, if you are not already using clang 3.5.0 or higher.
336 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
337 and renamed from .symbols to .debug. This reduces the size requirements
338 on the boot partition or file system and provides consistency with
339 userland debug files.
341 When using the supported kernel installation method the
342 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
343 as is done with /boot/kernel.
345 Developers wishing to maintain the historical behavior of installing
346 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
349 The wireless drivers had undergone changes that remove the 'parent
350 interface' from the ifconfig -l output. The rc.d network scripts
351 used to check presence of a parent interface in the list, so old
352 scripts would fail to start wireless networking. Thus, etcupdate(3)
353 or mergemaster(8) run is required after kernel update, to update your
354 rc.d scripts in /etc.
357 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
358 These configurations are now automatically interpreted as
359 'scrub fragment reassemble'.
362 Kernel-loadable modules for the random(4) device are back. To use
363 them, the kernel must have
366 options RANDOM_LOADABLE
368 kldload(8) can then be used to load random_fortuna.ko
369 or random_yarrow.ko. Please note that due to the indirect
370 function calls that the loadable modules need to provide,
371 the build-in variants will be slightly more efficient.
373 The random(4) kernel option RANDOM_DUMMY has been retired due to
374 unpopularity. It was not all that useful anyway.
377 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
378 Control over building the ELF Tool Chain tools is now provided by
379 the WITHOUT_TOOLCHAIN knob.
382 The polarity of Pulse Per Second (PPS) capture events with the
383 uart(4) driver has been corrected. Prior to this change the PPS
384 "assert" event corresponded to the trailing edge of a positive PPS
385 pulse and the "clear" event was the leading edge of the next pulse.
387 As the width of a PPS pulse in a typical GPS receiver is on the
388 order of 1 millisecond, most users will not notice any significant
389 difference with this change.
391 Anyone who has compensated for the historical polarity reversal by
392 configuring a negative offset equal to the pulse width will need to
393 remove that workaround.
396 The default group assigned to /dev/dri entries has been changed
397 from 'wheel' to 'video' with the id of '44'. If you want to have
398 access to the dri devices please add yourself to the video group
401 # pw groupmod video -m $USER
404 The menu.rc and loader.rc files will now be replaced during
405 upgrades. Please migrate local changes to menu.rc.local and
406 loader.rc.local instead.
409 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
410 strings and strip have been removed. The src.conf(5) knob
411 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
414 As ZFS requires more kernel stack pages than is the default on some
415 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
416 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
418 Please consider using 'options KSTACK_PAGES=X' where X is greater
419 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
422 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
423 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
424 default, i.e., they will not contain "::". For example, instead
425 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
426 to have a more specific match, such as different map entries for
427 IPv6:0:0 vs IPv6:0. This change requires that configuration
428 data (including maps, files, classes, custom ruleset, etc.) must
429 use the same format, so make certain such configuration data is
430 upgrading. As a very simple check search for patterns like
431 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
432 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
433 the cf option UseCompressedIPv6Addresses.
436 The default kernel entropy-processing algorithm is now
437 Fortuna, replacing Yarrow.
439 Assuming you have 'device random' in your kernel config
440 file, the configurations allow a kernel option to override
441 this default. You may choose *ONE* of:
443 options RANDOM_YARROW # Legacy /dev/random algorithm.
444 options RANDOM_DUMMY # Blocking-only driver.
446 If you have neither, you get Fortuna. For most people,
447 read no further, Fortuna will give a /dev/random that works
448 like it always used to, and the difference will be irrelevant.
450 If you remove 'device random', you get *NO* kernel-processed
451 entropy at all. This may be acceptable to folks building
452 embedded systems, but has complications. Carry on reading,
453 and it is assumed you know what you need.
455 *PLEASE* read random(4) and random(9) if you are in the
456 habit of tweaking kernel configs, and/or if you are a member
457 of the embedded community, wanting specific and not-usual
458 behaviour from your security subsystems.
460 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
461 random', you will NOT have a functioning /dev/random, and
462 many cryptographic features will not work, including SSH.
463 You may also find strange behaviour from the random(3) set
464 of library functions, in particular sranddev(3), srandomdev(3)
465 and arc4random(3). The reason for this is that the KERN_ARND
466 sysctl only returns entropy if it thinks it has some to
467 share, and with RANDOM_DUMMY or no 'device random' this
471 An additional fix for the issue described in the 20150614 sendmail
472 entry below has been been committed in revision 284717.
475 FreeBSD's old make (fmake) has been removed from the system. It is
476 available as the devel/fmake port or via pkg install fmake.
479 The fix for the issue described in the 20150614 sendmail entry
480 below has been been committed in revision 284436. The work
481 around described in that entry is no longer needed unless the
482 default setting is overridden by a confDH_PARAMETERS configuration
483 setting of '5' or pointing to a 512 bit DH parameter file.
486 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
487 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
488 and devel/kyua to version 0.20+ and adjust any calling code to work
489 with Kyuafile and kyua.
492 The import of openssl to address the FreeBSD-SA-15:10.openssl
493 security advisory includes a change which rejects handshakes
494 with DH parameters below 768 bits. sendmail releases prior
495 to 8.15.2 (not yet released), defaulted to a 512 bit
496 DH parameter setting for client connections. To work around
497 this interoperability, sendmail can be configured to use a
498 2048 bit DH parameter by:
500 1. Edit /etc/mail/`hostname`.mc
501 2. If a setting for confDH_PARAMETERS does not exist or
502 exists and is set to a string beginning with '5',
504 3. If a setting for confDH_PARAMETERS exists and is set to
505 a file path, create a new file with:
506 openssl dhparam -out /path/to/file 2048
507 4. Rebuild the .cf file:
508 cd /etc/mail/; make; make install
510 cd /etc/mail/; make restart
512 A sendmail patch is coming, at which time this file will be
516 Generation of legacy formatted entries have been disabled by default
517 in pwd_mkdb(8), as all base system consumers of the legacy formatted
518 entries were converted to use the new format by default when the new,
519 machine independent format have been added and supported since FreeBSD
522 Please see the pwd_mkdb(8) manual page for further details.
525 Clang and llvm have been upgraded to 3.6.1 release. Please see the
526 20141231 entry below for information about prerequisites and upgrading,
527 if you are not already using 3.5.0 or higher.
530 TI platform code switched to using vendor DTS files and this update
531 may break existing systems running on Beaglebone, Beaglebone Black,
534 - dtb files should be regenerated/reinstalled. Filenames are the
535 same but content is different now
536 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
537 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
538 addressing scheme is now pin 25 on /dev/gpioc3.
539 - Pandaboard: /etc/ttys should be updated, serial console device is
540 now /dev/ttyu2, not /dev/ttyu0
543 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
544 If you need the GNU extension from groff soelim(1), install groff
545 from package: pkg install groff, or via ports: textproc/groff.
548 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
549 defined in symlink(7); previously symlinks were silently ignored.
552 The const qualifier has been removed from iconv(3) to comply with
553 POSIX. The ports tree is aware of this from r384038 onwards.
556 Libraries specified by LIBADD in Makefiles must have a corresponding
557 DPADD_<lib> variable to ensure correct dependencies. This is now
558 enforced in src.libnames.mk.
561 From legacy ata(4) driver was removed support for SATA controllers
562 supported by more functional drivers ahci(4), siis(4) and mvs(4).
563 Kernel modules ataahci and ataadaptec were removed completely,
564 replaced by ahci and mvs modules respectively.
567 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
568 the 20141231 entry below for information about prerequisites and
569 upgrading, if you are not already using 3.5.0 or higher.
572 The 32-bit PowerPC kernel has been changed to a position-independent
573 executable. This can only be booted with a version of loader(8)
574 newer than January 31, 2015, so make sure to update both world and
575 kernel before rebooting.
578 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
579 but before r278950, the RNG was not seeded properly. Immediately
580 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
581 ssh keys or openssl keys) that were generated w/ a kernel from that
582 range. This does not affect programs that directly used /dev/random
583 or /dev/urandom. All userland uses of arc4random(3) are affected.
586 The autofs(4) ABI was changed in order to restore binary compatibility
587 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
591 The powerpc64 kernel has been changed to a position-independent
592 executable. This can only be booted with a new version of loader(8),
593 so make sure to update both world and kernel before rebooting.
596 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
597 only release, no new features have been added. Please see the 20141231
598 entry below for information about prerequisites and upgrading, if you
599 are not already using 3.5.0.
602 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
603 taken from the ELF Tool Chain project rather than GNU binutils. They
604 should be drop-in replacements, with the addition of arm64 support.
605 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
606 binutils tools, if necessary. See 20150805 for updated information.
609 The default Unbound configuration now enables remote control
610 using a local socket. Users who have already enabled the
611 local_unbound service should regenerate their configuration
612 by running "service local_unbound setup" as root.
615 The GNU texinfo and GNU info pages have been removed.
616 To be able to view GNU info pages please install texinfo from ports.
619 Clang, llvm and lldb have been upgraded to 3.5.0 release.
621 As of this release, a prerequisite for building clang, llvm and lldb is
622 a C++11 capable compiler and C++11 standard library. This means that to
623 be able to successfully build the cross-tools stage of buildworld, with
624 clang as the bootstrap compiler, your system compiler or cross compiler
625 should either be clang 3.3 or later, or gcc 4.8 or later, and your
626 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
629 On any standard FreeBSD 10.x or 11.x installation, where clang and
630 libc++ are on by default (that is, on x86 or arm), this should work out
633 On 9.x installations where clang is enabled by default, e.g. on x86 and
634 powerpc, libc++ will not be enabled by default, so libc++ should be
635 built (with clang) and installed first. If both clang and libc++ are
636 missing, build clang first, then use it to build libc++.
638 On 8.x and earlier installations, upgrade to 9.x first, and then follow
639 the instructions for 9.x above.
641 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
642 default, and do not build clang.
644 Many embedded systems are resource constrained, and will not be able to
645 build clang in a reasonable time, or in some cases at all. In those
646 cases, cross building bootable systems on amd64 is a workaround.
648 This new version of clang introduces a number of new warnings, of which
649 the following are most likely to appear:
653 This warns in two cases, for both C and C++:
654 * When the code is trying to take the absolute value of an unsigned
655 quantity, which is effectively a no-op, and almost never what was
656 intended. The code should be fixed, if at all possible. If you are
657 sure that the unsigned quantity can be safely cast to signed, without
658 loss of information or undefined behavior, you can add an explicit
659 cast, or disable the warning.
661 * When the code is trying to take an absolute value, but the called
662 abs() variant is for the wrong type, which can lead to truncation.
663 If you want to disable the warning instead of fixing the code, please
664 make sure that truncation will not occur, or it might lead to unwanted
667 -Wtautological-undefined-compare and
668 -Wundefined-bool-conversion
670 These warn when C++ code is trying to compare 'this' against NULL, while
671 'this' should never be NULL in well-defined C++ code. However, there is
672 some legacy (pre C++11) code out there, which actively abuses this
673 feature, which was less strictly defined in previous C++ versions.
675 Squid and openjdk do this, for example. The warning can be turned off
676 for C++98 and earlier, but compiling the code in C++11 mode might result
677 in unexpected behavior; for example, the parts of the program that are
678 unreachable could be optimized away.
681 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
682 kernel sources have been removed. The .h files remain, since some
683 utilities include them. This will need to be fixed later.
684 If "mount -t oldnfs ..." is attempted, it will fail.
685 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
686 the utilities will report errors.
689 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
690 directories to top level SUBDIR variable when their parent
691 directory is included in LOCAL_DIRS. Users with build systems with
692 such hierarchies and without SUBDIR entries in the parent
693 directory Makefiles should add them or add the directories to
697 faith(4) and faithd(8) have been removed from the base system. Faith
698 has been obsolete for a very long time.
701 vt(4), the new console driver, is enabled by default. It brings
702 support for Unicode and double-width characters, as well as
703 support for UEFI and integration with the KMS kernel video
706 You may need to update your console settings in /etc/rc.conf,
707 most probably the keymap. During boot, /etc/rc.d/syscons will
708 indicate what you need to do.
710 vt(4) still has issues and lacks some features compared to
711 syscons(4). See the wiki for up-to-date information:
712 https://wiki.freebsd.org/Newcons
714 If you want to keep using syscons(4), you can do so by adding
715 the following line to /boot/loader.conf:
719 pjdfstest has been integrated into kyua as an opt-in test suite.
720 Please see share/doc/pjdfstest/README for more details on how to
724 gperf has been removed from the base system for architectures
725 that use clang. Ports that require gperf will obtain it from the
729 pjdfstest has been moved from tools/regression/pjdfstest to
733 At svn r271982, The default linux compat kernel ABI has been adjusted
734 to 2.6.18 in support of the linux-c6 compat ports infrastructure
735 update. If you wish to continue using the linux-f10 compat ports,
736 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
737 encouraged to update their linux-compat packages to linux-c6 during
738 their next update cycle.
741 The ofwfb driver, used to provide a graphics console on PowerPC when
742 using vt(4), no longer allows mmap() of all physical memory. This
743 will prevent Xorg on PowerPC with some ATI graphics cards from
744 initializing properly unless x11-servers/xorg-server is updated to
748 The xdev targets have been converted to using TARGET and
749 TARGET_ARCH instead of XDEV and XDEV_ARCH.
752 The default unbound configuration has been modified to address
753 issues with reverse lookups on networks that use private
754 address ranges. If you use the local_unbound service, run
755 "service local_unbound setup" as root to regenerate your
756 configuration, then "service local_unbound reload" to load the
760 The GNU texinfo and GNU info pages are not built and installed
761 anymore, WITH_INFO knob has been added to allow to built and install
763 UPDATE: see 20150102 entry on texinfo's removal
766 The GNU readline library is now an INTERNALLIB - that is, it is
767 statically linked into consumers (GDB and variants) in the base
768 system, and the shared library is no longer installed. The
769 devel/readline port is available for third party software that
773 The Itanium architecture (ia64) has been removed from the list of
774 known architectures. This is the first step in the removal of the
778 Commit r268115 has added NFSv4.1 server support, merged from
779 projects/nfsv4.1-server. Since this includes changes to the
780 internal interfaces between the NFS related modules, a full
781 build of the kernel and modules will be necessary.
782 __FreeBSD_version has been bumped.
785 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
786 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
787 which differs from the behaviour controlled by this knob.)
790 Maximal length of the serial number in CTL was increased from 16 to
791 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
792 and ctld, need to be rebuilt to work with a new kernel.
795 The libatf-c and libatf-c++ major versions were downgraded to 0 and
796 1 respectively to match the upstream numbers. They were out of
797 sync because, when they were originally added to FreeBSD, the
798 upstream versions were not respected. These libraries are private
799 and not yet built by default, so renumbering them should be a
800 non-issue. However, unclean source trees will yield broken test
801 programs once the operator executes "make delete-old-libs" after a
804 Additionally, the atf-sh binary was made private by moving it into
805 /usr/libexec/. Already-built shell test programs will keep the
806 path to the old binary so they will break after "make delete-old"
809 If you are using WITH_TESTS=yes (not the default), wipe the object
810 tree and rebuild from scratch to prevent spurious test failures.
811 This is only needed once: the misnumbered libraries and misplaced
812 binaries have been added to OptionalObsoleteFiles.inc so they will
813 be removed during a clean upgrade.
816 Clang and llvm have been upgraded to 3.4.1 release.
819 We bogusly installed src.opts.mk in /usr/share/mk. This file should
820 be removed to avoid issues in the future (and has been added to
824 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
825 past, it affected all builds that used the bsd.*.mk files. The old
826 behavior was a bug, but people may have relied upon it. To get this
827 behavior back, you can .include /etc/src.conf from /etc/make.conf
828 (which is still global and isn't changed). This also changes the
829 behavior of incremental builds inside the tree of individual
830 directories. Set MAKESYSPATH to ".../share/mk" to do that.
831 Although this has survived make universe and some upgrade scenarios,
832 other upgrade scenarios may have broken. At least one form of
833 temporary breakage was fixed with MAKESYSPATH settings for buildworld
834 as well... In cases where MAKESYSPATH isn't working with this
835 setting, you'll need to set it to the full path to your tree.
837 One side effect of all this cleaning up is that bsd.compiler.mk
838 is no longer implicitly included by bsd.own.mk. If you wish to
839 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
843 The lindev device has been removed since /dev/full has been made a
844 standard device. __FreeBSD_version has been bumped.
847 The knob WITHOUT_VI was added to the base system, which controls
848 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
849 in order to reorder files share/termcap and didn't build ex(1) as a
850 build tool, so building/installing with WITH_VI is highly advised for
851 build hosts for older releases.
853 This issue has been fixed in stable/9 and stable/10 in r277022 and
854 r276991, respectively.
857 The YES_HESIOD knob has been removed. It has been obsolete for
858 a decade. Please move to using WITH_HESIOD instead or your builds
859 will silently lack HESIOD.
862 The uart(4) driver has been changed with respect to its handling
863 of the low-level console. Previously the uart(4) driver prevented
864 any process from changing the baudrate or the CLOCAL and HUPCL
865 control flags. By removing the restrictions, operators can make
866 changes to the serial console port without having to reboot.
867 However, when getty(8) is started on the serial device that is
868 associated with the low-level console, a misconfigured terminal
869 line in /etc/ttys will now have a real impact.
870 Before upgrading the kernel, make sure that /etc/ttys has the
871 serial console device configured as 3wire without baudrate to
872 preserve the previous behaviour. E.g:
873 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
876 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
877 to improve performance. To re-enable it, if needed, run rpcbind
878 with command line option -W.
881 Switched back to the GPL dtc compiler due to updates in the upstream
882 dts files not being supported by the BSDL dtc compiler. You will need
883 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
884 may result while building dtb files during a kernel build if you fail
885 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
888 Clang and llvm have been upgraded to 3.4 release.
891 The nve(4) driver has been removed. Please use the nfe(4) driver
892 for NVIDIA nForce MCP Ethernet adapters instead.
895 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
896 This could cause certain C++ applications using shared libraries built
897 against the previous version of libc++ to crash. The incompatibility
898 has now been fixed, but any C++ applications or shared libraries built
899 between r261283 and r261801 should be recompiled.
902 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
903 capability mode support. Please note that enabling the feature in
904 kernel is still highly recommended.
907 OpenSSH is now built with sandbox support, and will use sandbox as
908 the default privilege separation method. This requires Capsicum
909 capability mode support in kernel.
912 The libelf and libdwarf libraries have been updated to newer
913 versions from upstream. Shared library version numbers for
914 these two libraries were bumped. Any ports or binaries
915 requiring these two libraries should be recompiled.
916 __FreeBSD_version is bumped to 1100006.
919 If a Makefile in a tests/ directory was auto-generating a Kyuafile
920 instead of providing an explicit one, this would prevent such
921 Makefile from providing its own Kyuafile in the future during
922 NO_CLEAN builds. This has been fixed in the Makefiles but manual
923 intervention is needed to clean an objdir if you use NO_CLEAN:
924 # find /usr/obj -name Kyuafile | xargs rm -f
927 The behavior of gss_pseudo_random() for the krb5 mechanism
928 has changed, for applications requesting a longer random string
929 than produced by the underlying enctype's pseudo-random() function.
930 In particular, the random string produced from a session key of
931 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
932 be different at the 17th octet and later, after this change.
933 The counter used in the PRF+ construction is now encoded as a
934 big-endian integer in accordance with RFC 4402.
935 __FreeBSD_version is bumped to 1100004.
938 The WITHOUT_ATF build knob has been removed and its functionality
939 has been subsumed into the more generic WITHOUT_TESTS. If you were
940 using the former to disable the build of the ATF libraries, you
941 should change your settings to use the latter.
944 The default version of mtree is nmtree which is obtained from
945 NetBSD. The output is generally the same, but may vary
946 slightly. If you found you need identical output adding
947 "-F freebsd9" to the command line should do the trick. For the
948 time being, the old mtree is available as fmtree.
951 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
952 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
953 1.1.4_8 and verify bsdyml not linked in, before running "make
955 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
957 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
960 The stable/10 branch has been created in subversion from head
964 The rc.d/jail script has been updated to support jail(8)
965 configuration file. The "jail_<jname>_*" rc.conf(5) variables
966 for per-jail configuration are automatically converted to
967 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
968 This is transparently backward compatible. See below about some
969 incompatibilities and rc.conf(5) manual page for more details.
971 These variables are now deprecated in favor of jail(8) configuration
972 file. One can use "rc.d/jail config <jname>" command to generate
973 a jail(8) configuration file in /var/run/jail.<jname>.conf without
974 running the jail(8) utility. The default pathname of the
975 configuration file is /etc/jail.conf and can be specified by
976 using $jail_conf or $jail_<jname>_conf variables.
978 Please note that jail_devfs_ruleset accepts an integer at
979 this moment. Please consider to rewrite the ruleset name
983 BIND has been removed from the base system. If all you need
984 is a local resolver, simply enable and start the local_unbound
985 service instead. Otherwise, several versions of BIND are
986 available in the ports tree. The dns/bind99 port is one example.
988 With this change, nslookup(1) and dig(1) are no longer in the base
989 system. Users should instead use host(1) and drill(1) which are
990 in the base system. Alternatively, nslookup and dig can
991 be obtained by installing the dns/bind-tools port.
994 With the addition of unbound(8), a new unbound user is now
995 required during installworld. "mergemaster -p" can be used to
996 add the user prior to installworld, as documented in the handbook.
999 OpenSSH is now built with DNSSEC support, and will by default
1000 silently trust signed SSHFP records. This can be controlled with
1001 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1002 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1005 The GNU Compiler Collection and C++ standard library (libstdc++)
1006 are no longer built by default on platforms where clang is the system
1007 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1008 options in src.conf.
1011 The PROCDESC kernel option is now part of the GENERIC kernel
1012 configuration and is required for the rwhod(8) to work.
1013 If you are using custom kernel configuration, you should include
1017 The API and ABI related to the Capsicum framework was modified
1018 in backward incompatible way. The userland libraries and programs
1019 have to be recompiled to work with the new kernel. This includes the
1020 following libraries and programs, but the whole buildworld is
1021 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1022 kdump, procstat, rwho, rwhod, uniq.
1025 AES-NI intrinsic support has been added to gcc. The AES-NI module
1026 has been updated to use this support. A new gcc is required to build
1027 the aesni module on both i386 and amd64.
1030 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1031 Thus "device padlock_rng" and "device rdrand_rng" should be
1032 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1035 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1036 enables just the iconv* functionality and is now on by default.
1037 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1038 compatibility. Set WITHOUT_ICONV to build the old way.
1039 If you have been using WITH_ICONV before, you will very likely
1040 need to turn on WITH_LIBICONV_COMPAT.
1043 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1044 Illumos origin, including ZFS. If you have INVARIANTS in your
1045 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1047 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1048 locks if WITNESS option was set. Because that generated a lot of
1049 witness(9) reports and all of them were believed to be false
1050 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1051 can be used to achieve the previous behavior.
1054 Timer values in IPv6 data structures now use time_uptime instead
1055 of time_second. Although this is not a user-visible functional
1056 change, userland utilities which directly use them---ndp(8),
1057 rtadvd(8), and rtsold(8) in the base system---need to be updated
1058 to r253970 or later.
1061 find -delete can now delete the pathnames given as arguments,
1062 instead of only files found below them or if the pathname did
1063 not contain any slashes. Formerly, the following error message
1066 find: -delete: <path>: relative path potentially not safe
1068 Deleting the pathnames given as arguments can be prevented
1069 without error messages using -mindepth 1 or by changing
1070 directory and passing "." as argument to find. This works in the
1071 old as well as the new version of find.
1074 Behavior of devfs rules path matching has been changed.
1075 Pattern is now always matched against fully qualified devfs
1076 path and slash characters must be explicitly matched by
1077 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1078 subdirectories must be reviewed.
1081 The default ARM ABI has changed to the ARM EABI. The old ABI is
1082 incompatible with the ARM EABI and all programs and modules will
1083 need to be rebuilt to work with a new kernel.
1085 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1087 NOTE: Support for the old ABI will be removed in the future and
1088 users are advised to upgrade.
1091 pkg_install has been disconnected from the build if you really need it
1092 you should add WITH_PKGTOOLS in your src.conf(5).
1095 Most of network statistics structures were changed to be able
1096 keep 64-bits counters. Thus all tools, that work with networking
1097 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1100 Fix a bug that allowed a tracing process (e.g. gdb) to write
1101 to a memory-mapped file in the traced process's address space
1102 even if neither the traced process nor the tracing process had
1103 write access to that file.
1106 CVS has been removed from the base system. An exact copy
1107 of the code is available from the devel/cvs port.
1110 Some people report the following error after the switch to bmake:
1112 make: illegal option -- J
1113 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1115 *** [buildworld] Error code 2
1117 this likely due to an old instance of make in
1118 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1119 which src/Makefile will use that blindly, if it exists, so if
1120 you see the above error:
1122 rm -rf `make -V MAKEPATH`
1127 Use bmake by default.
1128 Whereas before one could choose to build with bmake via
1129 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1130 make. The goal is to remove these knobs for 10-RELEASE.
1132 It is worth noting that bmake (like gmake) treats the command
1133 line as the unit of failure, rather than statements within the
1134 command line. Thus '(cd some/where && dosomething)' is safer
1135 than 'cd some/where; dosomething'. The '()' allows consistent
1136 behavior in parallel build.
1139 Fix a bug that allows NFS clients to issue READDIR on files.
1142 The WITHOUT_IDEA option has been removed because
1143 the IDEA patent expired.
1146 The sysctl which controls TRIM support under ZFS has been renamed
1147 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1151 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1152 rather than creating it's own in the temporary directory in
1153 order allow access to bootstrapped versions of tools such as
1154 install and mtree. When upgrading from version of FreeBSD where
1155 the install command does not support -l, you will need to
1156 install a new mergemaster command if mergemaster -p is required.
1157 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1161 Legacy ATA stack, disabled and replaced by new CAM-based one since
1162 FreeBSD 9.0, completely removed from the sources. Kernel modules
1163 atadisk and atapi*, user-level tools atacontrol and burncd are
1164 removed. Kernel option `options ATA_CAM` is now permanently enabled
1168 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1169 and socketpair(2). Software, in particular Kerberos, may
1170 automatically detect and use these during building. The resulting
1171 binaries will not work on older kernels.
1174 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1175 information, see the respective 20130304 entry).
1178 Recent commits to callout(9) changed the size of struct callout,
1179 so the KBI is probably heavily disturbed. Also, some functions
1180 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1181 by macros. Every kernel module using it won't load, so rebuild
1184 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1185 but does not initialize by default (because of the new CTL_DISABLE
1186 option) to save memory. To re-enable it, remove the CTL_DISABLE
1187 option from the kernel config file or set kern.cam.ctl.disable=0
1188 in /boot/loader.conf.
1191 The ctl device has been disabled in GENERIC for i386 and amd64.
1192 This was done due to the extra memory being allocated at system
1193 initialisation time by the ctl driver which was only used if
1194 a CAM target device was created. This makes a FreeBSD system
1195 unusable on 128MB or less of RAM.
1198 A new compression method (lz4) has been merged to -HEAD. Please
1199 refer to zpool-features(7) for more information.
1201 Please refer to the "ZFS notes" section of this file for information
1202 on upgrading boot ZFS pools.
1205 A BSD-licensed patch(1) variant has been added and is installed
1206 as bsdpatch, being the GNU version the default patch.
1207 To inverse the logic and use the BSD-licensed one as default,
1208 while having the GNU version installed as gnupatch, rebuild
1209 and install world with the WITH_BSD_PATCH knob set.
1212 Due to the use of the new -l option to install(1) during build
1213 and install, you must take care not to directly set the INSTALL
1214 make variable in your /etc/make.conf, /etc/src.conf, or on the
1215 command line. If you wish to use the -C flag for all installs
1216 you may be able to add INSTALL+=-C to /etc/make.conf or
1220 The install(1) option -M has changed meaning and now takes an
1221 argument that is a file or path to append logs to. In the
1222 unlikely event that -M was the last option on the command line
1223 and the command line contained at least two files and a target
1224 directory the first file will have logs appended to it. The -M
1225 option served little practical purpose in the last decade so its
1226 use is expected to be extremely rare.
1229 After switching to Clang as the default compiler some users of ZFS
1230 on i386 systems started to experience stack overflow kernel panics.
1231 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1234 GEOM_LABEL now mangles label names read from file system metadata.
1235 Mangling affect labels containing spaces, non-printable characters,
1236 '%' or '"'. Device names in /etc/fstab and other places may need to
1240 By default, only the 10 most recent kernel dumps will be saved. To
1241 restore the previous behaviour (no limit on the number of kernel dumps
1242 stored in the dump directory) add the following line to /etc/rc.conf:
1247 With the addition of auditdistd(8), a new auditdistd user is now
1248 required during installworld. "mergemaster -p" can be used to
1249 add the user prior to installworld, as documented in the handbook.
1252 The sin6_scope_id member variable in struct sockaddr_in6 is now
1253 filled by the kernel before passing the structure to the userland via
1254 sysctl or routing socket. This means the KAME-specific embedded scope
1255 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1256 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1257 __FreeBSD_version is bumped to 1000025.
1260 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1261 This means that the world and kernel will be compiled with clang
1262 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1263 and /usr/bin/cpp. To disable this behavior and revert to building
1264 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1265 of current may need to bootstrap WITHOUT_CLANG first if the clang
1266 build fails (its compatibility window doesn't extend to the 9 stable
1270 The IPFIREWALL_FORWARD kernel option has been removed. Its
1271 functionality now turned on by default.
1274 The ZERO_COPY_SOCKET kernel option has been removed and
1275 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1276 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1277 mechanism which is not safe and may result in kernel crashes.
1278 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1279 driver supports disposeable external page sized mbuf storage.
1280 Proper replacements for both zero-copy mechanisms are under
1281 consideration and will eventually lead to complete removal
1282 of the two kernel options.
1285 The IPv4 network stack has been converted to network byte
1286 order. The following modules need to be recompiled together
1287 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1288 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1291 Support for non-MPSAFE filesystems was removed from VFS. The
1292 VFS_VERSION was bumped, all filesystem modules shall be
1296 All the non-MPSAFE filesystems have been disconnected from
1297 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1298 portalfs, smbfs, xfs.
1301 The interface cloning API and ABI has changed. The following
1302 modules need to be recompiled together with kernel:
1303 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1304 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1305 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1308 The sdhci driver was split in two parts: sdhci (generic SD Host
1309 Controller logic) and sdhci_pci (actual hardware driver).
1310 No kernel config modifications are required, but if you
1311 load sdhc as a module you must switch to sdhci_pci instead.
1314 Import the FUSE kernel and userland support into base system.
1317 The GNU sort(1) program has been removed since the BSD-licensed
1318 sort(1) has been the default for quite some time and no serious
1319 problems have been reported. The corresponding WITH_GNU_SORT
1323 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1324 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1328 The net80211(4) ABI has been changed to allow for improved driver
1329 PS-POLL and power-save support. All wireless drivers need to be
1330 recompiled to work with the new kernel.
1333 The random(4) support for the VIA hardware random number
1334 generator (`PADLOCK') is no longer enabled unconditionally.
1335 Add the padlock_rng device in the custom kernel config if
1336 needed. The GENERIC kernels on i386 and amd64 do include the
1337 device, so the change only affects the custom kernel
1341 The pf(4) packet filter ABI has been changed. pfctl(8) and
1342 snmp_pf module need to be recompiled to work with new kernel.
1345 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1346 to -HEAD. Pools that have empty_bpobj in active state can not be
1347 imported read-write with ZFS implementations that do not support
1348 this feature. For more information read the zpool-features(5)
1352 The sparc64 ZFS loader has been changed to no longer try to auto-
1353 detect ZFS providers based on diskN aliases but now requires these
1354 to be explicitly listed in the OFW boot-device environment variable.
1357 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1358 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1359 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1362 The following sysctls and tunables have been renamed for consistency
1363 with other variables:
1364 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1365 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1368 The sort utility has been replaced with BSD sort. For now, GNU sort
1369 is also available as "gnusort" or the default can be set back to
1370 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1371 installed as "bsdsort".
1374 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1375 Starting with this version the old system of ZFS pool versioning
1376 is superseded by "feature flags". This concept enables forward
1377 compatibility against certain future changes in functionality of ZFS
1378 pools. The first read-only compatible "feature flag" for ZFS pools
1379 is named "com.delphix:async_destroy". For more information
1380 read the new zpool-features(5) manual page.
1381 Please refer to the "ZFS notes" section of this file for information
1382 on upgrading boot ZFS pools.
1385 The malloc(3) implementation embedded in libc now uses sources imported
1386 as contrib/jemalloc. The most disruptive API change is to
1387 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1388 delete it prior to installworld, and optionally re-create it using the
1389 new format after rebooting. See malloc.conf(5) for details
1390 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1394 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1395 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1396 now spelled mips. This is to aid compatibility with third-party
1397 software that expects this naming scheme in uname(3). Little-endian
1398 settings are unchanged. If you are updating a big-endian mips64 machine
1399 from before this change, you may need to set MACHINE_ARCH=mips64 in
1400 your environment before the new build system will recognize your machine.
1403 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1407 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1408 nullfs(5) did not pass through all behaviours to the underlying layer,
1409 as a result if we bound to a socket on the lower layer we could connect
1410 only to the lower path; if we bound to the upper layer we could connect
1411 only to the upper path. The new behavior is one can connect to both the
1412 lower and the upper paths regardless what layer path one binds to.
1415 The getifaddrs upgrade path broken with 20111215 has been restored.
1416 If you have upgraded in between 20111215 and 20120209 you need to
1417 recompile libc again with your kernel. You still need to recompile
1418 world to be able to configure CARP but this restriction already
1419 comes from 20111215.
1422 The set_rcvar() function has been removed from /etc/rc.subr. All
1423 base and ports rc.d scripts have been updated, so if you have a
1424 port installed with a script in /usr/local/etc/rc.d you can either
1425 hand-edit the rcvar= line, or reinstall the port.
1427 An easy way to handle the mass-update of /etc/rc.d:
1428 rm /etc/rc.d/* && mergemaster -i
1431 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1432 on the current CPU and prevents other threads from running.
1433 This behavior can be reverted using the kern.stop_scheduler_on_panic
1435 The new behavior can be incompatible with kern.sync_on_panic.
1438 The carp(4) facility has been changed significantly. Configuration
1439 of the CARP protocol via ifconfig(8) has changed, as well as format
1440 of CARP events submitted to devd(8) has changed. See manual pages
1441 for more information. The arpbalance feature of carp(4) is currently
1442 not supported anymore.
1444 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1445 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1446 need to be recompiled.
1449 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1453 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1454 explicitely support non-MPSAFE filesystems.
1455 It is on by default for all supported platform at this present
1459 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1460 i386 and pc98 GENERIC kernel configuration files.
1463 sysinstall has been removed
1466 The stable/9 branch created in subversion. This corresponds to the
1467 RELENG_9 branch in CVS.
1473 Avoid using make -j when upgrading. While generally safe, there are
1474 sometimes problems using -j to upgrade. If your upgrade fails with
1475 -j, please try again without -j. From time to time in the past there
1476 have been problems using -j with buildworld and/or installworld. This
1477 is especially true when upgrading between "distant" versions (eg one
1478 that cross a major release boundary or several minor releases, or when
1479 several months have passed on the -current branch).
1481 Sometimes, obscure build problems are the result of environment
1482 poisoning. This can happen because the make utility reads its
1483 environment when searching for values for global variables. To run
1484 your build attempts in an "environmental clean room", prefix all make
1485 commands with 'env -i '. See the env(1) manual page for more details.
1487 When upgrading from one major version to another it is generally best to
1488 upgrade to the latest code in the currently installed branch first, then
1489 do an upgrade to the new branch. This is the best-tested upgrade path,
1490 and has the highest probability of being successful. Please try this
1491 approach if you encounter problems with a major version upgrade. Since
1492 the stable 4.x branch point, one has generally been able to upgade from
1493 anywhere in the most recent stable branch to head / current (or even the
1494 last couple of stable branches). See the top of this file when there's
1497 When upgrading a live system, having a root shell around before
1498 installing anything can help undo problems. Not having a root shell
1499 around can lead to problems if pam has changed too much from your
1500 starting point to allow continued authentication after the upgrade.
1502 This file should be read as a log of events. When a later event changes
1503 information of a prior event, the prior event should not be deleted.
1504 Instead, a pointer to the entry with the new information should be
1505 placed in the old entry. Readers of this file should also sanity check
1506 older entries before relying on them blindly. Authors of new entries
1507 should write them with this in mind.
1511 When upgrading the boot ZFS pool to a new version, always follow
1514 1.) recompile and reinstall the ZFS boot loader and boot block
1515 (this is part of "make buildworld" and "make installworld")
1517 2.) update the ZFS boot block on your boot drive
1519 The following example updates the ZFS boot block on the first
1520 partition (freebsd-boot) of a GPT partitioned drive ada0:
1521 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1523 Non-boot pools do not need these updates.
1527 If you are updating from a prior version of FreeBSD (even one just
1528 a few days old), you should follow this procedure. It is the most
1529 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1531 make kernel-toolchain
1532 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1533 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1535 To test a kernel once
1536 ---------------------
1537 If you just want to boot a kernel once (because you are not sure
1538 if it works, or if you want to boot a known bad kernel to provide
1539 debugging information) run
1540 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1541 nextboot -k testkernel
1543 To just build a kernel when you know that it won't mess you up
1544 --------------------------------------------------------------
1545 This assumes you are already running a CURRENT system. Replace
1546 ${arch} with the architecture of your machine (e.g. "i386",
1547 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1549 cd src/sys/${arch}/conf
1550 config KERNEL_NAME_HERE
1551 cd ../compile/KERNEL_NAME_HERE
1556 If this fails, go to the "To build a kernel" section.
1558 To rebuild everything and install it on the current system.
1559 -----------------------------------------------------------
1560 # Note: sometimes if you are running current you gotta do more than
1561 # is listed here if you are upgrading from a really old current.
1563 <make sure you have good level 0 dumps>
1565 make kernel KERNCONF=YOUR_KERNEL_HERE
1567 <reboot in single user> [3]
1574 To cross-install current onto a separate partition
1575 --------------------------------------------------
1576 # In this approach we use a separate partition to hold
1577 # current's root, 'usr', and 'var' directories. A partition
1578 # holding "/", "/usr" and "/var" should be about 2GB in
1581 <make sure you have good level 0 dumps>
1584 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1585 <maybe newfs current's root partition>
1586 <mount current's root partition on directory ${CURRENT_ROOT}>
1587 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1588 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1589 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1590 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1591 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1592 <reboot into current>
1593 <do a "native" rebuild/install as described in the previous section>
1594 <maybe install compatibility libraries from ports/misc/compat*>
1598 To upgrade in-place from stable to current
1599 ----------------------------------------------
1600 <make sure you have good level 0 dumps>
1602 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1604 <reboot in single user> [3]
1611 Make sure that you've read the UPDATING file to understand the
1612 tweaks to various things you need. At this point in the life
1613 cycle of current, things change often and you are on your own
1614 to cope. The defaults can also change, so please read ALL of
1615 the UPDATING entries.
1617 Also, if you are tracking -current, you must be subscribed to
1618 freebsd-current@freebsd.org. Make sure that before you update
1619 your sources that you have read and understood all the recent
1620 messages there. If in doubt, please track -stable which has
1621 much fewer pitfalls.
1623 [1] If you have third party modules, such as vmware, you
1624 should disable them at this point so they don't crash your
1627 [3] From the bootblocks, boot -s, and then do
1632 adjkerntz -i # if CMOS is wall time
1633 Also, when doing a major release upgrade, it is required that
1634 you boot into single user mode to do the installworld.
1636 [4] Note: This step is non-optional. Failure to do this step
1637 can result in a significant reduction in the functionality of the
1638 system. Attempting to do it by hand is not recommended and those
1639 that pursue this avenue should read this file carefully, as well
1640 as the archives of freebsd-current and freebsd-hackers mailing lists
1641 for potential gotchas. The -U option is also useful to consider.
1642 See mergemaster(8) for more information.
1644 [5] Usually this step is a noop. However, from time to time
1645 you may need to do this if you get unknown user in the following
1646 step. It never hurts to do it all the time. You may need to
1647 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1648 install) after the buildworld before this step if you last updated
1649 from current before 20130425 or from -stable before 20130430.
1651 [6] This only deletes old files and directories. Old libraries
1652 can be deleted by "make delete-old-libs", but you have to make
1653 sure that no program is using those libraries anymore.
1655 [8] In order to have a kernel that can run the 4.x binaries needed to
1656 do an installworld, you must include the COMPAT_FREEBSD4 option in
1657 your kernel. Failure to do so may leave you with a system that is
1658 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1659 required to run the 5.x binaries on more recent kernels. And so on
1660 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1662 Make sure that you merge any new devices from GENERIC since the
1663 last time you updated your kernel config file.
1665 [9] When checking out sources, you must include the -P flag to have
1666 cvs prune empty directories.
1668 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1669 "?=" instead of the "=" assignment operator, so that buildworld can
1670 override the CPUTYPE if it needs to.
1672 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1673 not on the command line, or in /etc/make.conf. buildworld will
1674 warn if it is improperly defined.
1677 This file contains a list, in reverse chronological order, of major
1678 breakages in tracking -current. It is not guaranteed to be a complete
1679 list of such breakages, and only contains entries since September 23, 2011.
1680 If you need to see UPDATING entries from before that date, you will need
1681 to fetch an UPDATING file from an older FreeBSD release.
1683 Copyright information:
1685 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1687 Redistribution, publication, translation and use, with or without
1688 modification, in full or in part, in any form or format of this
1689 document are permitted without further permission from the author.
1691 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1692 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1693 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1694 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1695 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1696 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1697 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1698 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1699 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1700 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1701 POSSIBILITY OF SUCH DAMAGE.
1703 Contact Warner Losh if you have any questions about your use of