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