1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 ****************************** SPECIAL WARNING: ******************************
37 Due to a bug in some versions of clang that's very hard to workaround in
38 the upgrade process, to upgrade to -current you must first upgrade
39 either stable/9 after r286035 or stable/10 after r286033 (including
40 10.3-RELEASE) or current after r286007 (including stable/11 and
41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
42 you'll need to take the unusual step of upgrading to the tip of the
43 stable branch before moving to 11 or -current via a source upgrade.
44 stable/11 and 11.0-RELEASE have working newer compiler. This differs
45 from the historical situation where one could upgrade from anywhere on
46 the last couple of stable branches, so be careful.
48 If you're running a hybrid system on 9.x or 10.x with an updated clang
49 compiler or are using an supported external toolchain, the build system
50 will allow the upgrade. Otherwise it will print a reminder.
52 ****************************** SPECIAL WARNING: ******************************
55 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
56 Please see the 20141231 entry below for information about prerequisites
57 and upgrading, if you are not already using clang 3.5.0 or higher.
60 The layout of the pmap structure has changed for powerpc to put the pmap
61 statistics at the front for all CPU variations. libkvm(3) and all tools
62 that link against it need to be recompiled.
65 isl(4) and cyapa(4) drivers now require a new driver,
66 chromebook_platform(4), to work properly on Chromebook-class hardware.
67 On other types of hardware the drivers may need to be configured using
68 device hints. Please see the corresponding manual pages for details.
71 The urtwn(4) driver was merged into rtwn(4) and now consists of
72 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
74 Also, firmware for RTL8188CE was renamed due to possible name
75 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
78 GNU rcs has been removed from base. It is available as packages:
79 - rcs: Latest GPLv3 GNU rcs version.
80 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
84 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
85 modules now requires that the kernel configuration contain the
86 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
89 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
90 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
93 Relocatable object files with the extension of .So have been renamed
94 to use an extension of .pico instead. The purpose of this change is
95 to avoid a name clash with shared libraries on case-insensitive file
96 systems. On those file systems, foo.So is the same file as foo.so.
99 GNU rcs has been turned off by default. It can (temporarily) be built
100 again by adding WITH_RCS knob in src.conf.
101 Otherwise, GNU rcs is available from packages:
102 - rcs: Latest GPLv3 GNU rcs version.
103 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
106 The backup_uses_rcs functionality has been removed from rc.subr.
109 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
110 two separate components, QUEUE_MACRO_DEBUG_TRACE and
111 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
112 QUEUE_MACRO_DEBUG behavior.
115 r304787 changed some ioctl interfaces between the iSCSI userspace
116 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
117 rebuilt to work with new kernels. __FreeBSD_version has been bumped
121 The UDP receive code has been updated to only treat incoming UDP
122 packets that were addressed to an L2 broadcast address as L3
123 broadcast packets. It is not expected that this will affect any
124 standards-conforming UDP application. The new behaviour can be
125 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
129 Remove the openbsd_poll system call.
130 __FreeBSD_version has been bumped because of this.
133 The libc stub for the pipe(2) system call has been replaced with
134 a wrapper that calls the pipe2(2) system call and the pipe(2)
135 system call is now only implemented by the kernels that include
136 "options COMPAT_FREEBSD10" in their config file (this is the
137 default). Users should ensure that this option is enabled in
138 their kernel or upgrade userspace to r302092 before upgrading their
142 CAM will now strip leading spaces from SCSI disks' serial numbers.
143 This will affect users who create UFS filesystems on SCSI disks using
144 those disk's diskid device nodes. For example, if /etc/fstab
145 previously contained a line like
146 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
147 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
148 transforms like gmirror may also be affected. ZFS users should
152 The bitstring(3) API has been updated with new functionality and
153 improved performance. But it is binary-incompatible with the old API.
154 Objects built with the new headers may not be linked against objects
155 built with the old headers.
158 The brk and sbrk functions have been removed from libc on arm64.
159 Binutils from ports has been updated to not link to these
160 functions and should be updated to the latest version before
161 installing a new libc.
164 The armv6 port now defaults to hard float ABI. Limited support
165 for running both hardfloat and soft float on the same system
166 is available using the libraries installed with -DWITH_LIBSOFT.
167 This has only been tested as an upgrade path for installworld
168 and packages may fail or need manual intervention to run. New
169 packages will be needed.
171 To update an existing self-hosted armv6hf system, you must add
172 TARGET_ARCH=armv6 on the make command line for both the build
173 and the install steps.
176 Kernel modules compiled outside of a kernel build now default to
177 installing to /boot/modules instead of /boot/kernel. Many kernel
178 modules built this way (such as those in ports) already overrode
179 KMODDIR explicitly to install into /boot/modules. However,
180 manually building and installing a module from /sys/modules will
181 now install to /boot/modules instead of /boot/kernel.
184 The CAM I/O scheduler has been committed to the kernel. There should be
185 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
186 list of known rogues that claim support for this but actually corrupt
187 data is believed to be complete, be on the lookout for data
188 corruption. The known rogue list is believed to be complete:
190 o Crucial MX100, M550 drives with MU01 firmware.
191 o Micron M510 and M550 drives with MU01 firmware.
192 o Micron M500 prior to MU07 firmware
193 o Samsung 830, 840, and 850 all firmwares
194 o FCCT M500 all firmwares
196 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
197 with working NCQ TRIM. For Micron branded drives, see your sales rep for
198 updated firmware. Black listed drives will work correctly because these
199 drives work correctly so long as no NCQ TRIMs are sent to them. Given
200 this list is the same as found in Linux, it's believed there are no
201 other rogues in the market place. All other models from the above
204 To be safe, if you are at all concerned, you can quirk each of your
205 drives to prevent NCQ from being sent by setting:
206 kern.cam.ada.X.quirks="0x2"
207 in loader.conf. If the drive requires the 4k sector quirk, set the
211 The FAST_DEPEND build option has been removed and its functionality is
212 now the one true way. The old mkdep(1) style of 'make depend' has
213 been removed. See 20160311 for further details.
216 Resource range types have grown from unsigned long to uintmax_t. All
217 drivers, and anything using libdevinfo, need to be recompiled.
220 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
221 builds. It no longer runs mkdep(1) during 'make depend', and the
222 'make depend' stage can safely be skipped now as it is auto ran
223 when building 'make all' and will generate all SRCS and DPSRCS before
224 building anything else. Dependencies are gathered at compile time with
225 -MF flags kept in separate .depend files per object file. Users should
226 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
230 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
231 kernel modules. Therefore, if you load any kernel modules at boot time,
232 please install the boot loaders after you install the kernel, but before
236 make kernel KERNCONF=YOUR_KERNEL_HERE
237 make -C sys/boot install
238 <reboot in single user>
240 Then follow the usual steps, described in the General Notes section,
244 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
245 see the 20141231 entry below for information about prerequisites and
246 upgrading, if you are not already using clang 3.5.0 or higher.
249 The AIO subsystem is now a standard part of the kernel. The
250 VFS_AIO kernel option and aio.ko kernel module have been removed.
251 Due to stability concerns, asynchronous I/O requests are only
252 permitted on sockets and raw disks by default. To enable
253 asynchronous I/O requests on all file types, set the
254 vfs.aio.enable_unsafe sysctl to a non-zero value.
257 The ELF object manipulation tool objcopy is now provided by the
258 ELF Tool Chain project rather than by GNU binutils. It should be a
259 drop-in replacement, with the addition of arm64 support. The
260 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
261 to obtain the GNU version if necessary.
264 Building ZFS pools on top of zvols is prohibited by default. That
265 feature has never worked safely; it's always been prone to deadlocks.
266 Using a zvol as the backing store for a VM guest's virtual disk will
267 still work, even if the guest is using ZFS. Legacy behavior can be
268 restored by setting vfs.zfs.vol.recursive=1.
271 The NONE and HPN patches has been removed from OpenSSH. They are
272 still available in the security/openssh-portable port.
275 With the addition of ypldap(8), a new _ypldap user is now required
276 during installworld. "mergemaster -p" can be used to add the user
277 prior to installworld, as documented in the handbook.
280 The tftp loader (pxeboot) now uses the option root-path directive. As a
281 consequence it no longer looks for a pxeboot.4th file on the tftp
282 server. Instead it uses the regular /boot infrastructure as with the
286 The code to start recording plug and play data into the modules has
287 been committed. While the old tools will properly build a new kernel,
288 a number of warnings about "unknown metadata record 4" will be produced
289 for an older kldxref. To avoid such warnings, make sure to rebuild
290 the kernel toolchain (or world). Make sure that you have r292078 or
291 later when trying to build 292077 or later before rebuilding.
294 Debug data files are now built by default with 'make buildworld' and
295 installed with 'make installworld'. This facilitates debugging but
296 requires more disk space both during the build and for the installed
297 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
301 r291527 changed the internal interface between the nfsd.ko and
302 nfscommon.ko modules. As such, they must both be upgraded to-gether.
303 __FreeBSD_version has been bumped because of this.
306 Add support for unicode collation strings leads to a change of
307 order of files listed by ls(1) for example. To get back to the old
308 behaviour, set LC_COLLATE environment variable to "C".
310 Databases administrators will need to reindex their databases given
311 collation results will be different.
313 Due to a bug in install(1) it is recommended to remove the ancient
314 locales before running make installworld.
316 rm -rf /usr/share/locale/*
319 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
320 libcrypto.so.7 or libssl.so.7 must be recompiled.
323 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
324 Kernel modules isp_2400_multi and isp_2500_multi were removed and
325 should be replaced with isp_2400 and isp_2500 modules respectively.
328 The build previously allowed using 'make -n' to not recurse into
329 sub-directories while showing what commands would be executed, and
330 'make -n -n' to recursively show commands. Now 'make -n' will recurse
331 and 'make -N' will not.
334 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
335 and etcupdate will now use this file. A custom sendmail.cf is now
336 updated via this mechanism rather than via installworld. If you had
337 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
338 want to remove the exclusion or change it to "always install".
339 /etc/mail/sendmail.cf is now managed the same way regardless of
340 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
341 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
344 Compatibility shims for legacy ATA device names have been removed.
345 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
346 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
347 environment variables, /dev/ad* and /dev/ar* symbolic links.
350 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
351 Please see the 20141231 entry below for information about prerequisites
352 and upgrading, if you are not already using clang 3.5.0 or higher.
355 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
356 and renamed from .symbols to .debug. This reduces the size requirements
357 on the boot partition or file system and provides consistency with
358 userland debug files.
360 When using the supported kernel installation method the
361 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
362 as is done with /boot/kernel.
364 Developers wishing to maintain the historical behavior of installing
365 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
368 The wireless drivers had undergone changes that remove the 'parent
369 interface' from the ifconfig -l output. The rc.d network scripts
370 used to check presence of a parent interface in the list, so old
371 scripts would fail to start wireless networking. Thus, etcupdate(3)
372 or mergemaster(8) run is required after kernel update, to update your
373 rc.d scripts in /etc.
376 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
377 These configurations are now automatically interpreted as
378 'scrub fragment reassemble'.
381 Kernel-loadable modules for the random(4) device are back. To use
382 them, the kernel must have
385 options RANDOM_LOADABLE
387 kldload(8) can then be used to load random_fortuna.ko
388 or random_yarrow.ko. Please note that due to the indirect
389 function calls that the loadable modules need to provide,
390 the build-in variants will be slightly more efficient.
392 The random(4) kernel option RANDOM_DUMMY has been retired due to
393 unpopularity. It was not all that useful anyway.
396 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
397 Control over building the ELF Tool Chain tools is now provided by
398 the WITHOUT_TOOLCHAIN knob.
401 The polarity of Pulse Per Second (PPS) capture events with the
402 uart(4) driver has been corrected. Prior to this change the PPS
403 "assert" event corresponded to the trailing edge of a positive PPS
404 pulse and the "clear" event was the leading edge of the next pulse.
406 As the width of a PPS pulse in a typical GPS receiver is on the
407 order of 1 millisecond, most users will not notice any significant
408 difference with this change.
410 Anyone who has compensated for the historical polarity reversal by
411 configuring a negative offset equal to the pulse width will need to
412 remove that workaround.
415 The default group assigned to /dev/dri entries has been changed
416 from 'wheel' to 'video' with the id of '44'. If you want to have
417 access to the dri devices please add yourself to the video group
420 # pw groupmod video -m $USER
423 The menu.rc and loader.rc files will now be replaced during
424 upgrades. Please migrate local changes to menu.rc.local and
425 loader.rc.local instead.
428 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
429 strings and strip have been removed. The src.conf(5) knob
430 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
433 As ZFS requires more kernel stack pages than is the default on some
434 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
435 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
437 Please consider using 'options KSTACK_PAGES=X' where X is greater
438 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
441 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
442 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
443 default, i.e., they will not contain "::". For example, instead
444 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
445 to have a more specific match, such as different map entries for
446 IPv6:0:0 vs IPv6:0. This change requires that configuration
447 data (including maps, files, classes, custom ruleset, etc.) must
448 use the same format, so make certain such configuration data is
449 upgrading. As a very simple check search for patterns like
450 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
451 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
452 the cf option UseCompressedIPv6Addresses.
455 The default kernel entropy-processing algorithm is now
456 Fortuna, replacing Yarrow.
458 Assuming you have 'device random' in your kernel config
459 file, the configurations allow a kernel option to override
460 this default. You may choose *ONE* of:
462 options RANDOM_YARROW # Legacy /dev/random algorithm.
463 options RANDOM_DUMMY # Blocking-only driver.
465 If you have neither, you get Fortuna. For most people,
466 read no further, Fortuna will give a /dev/random that works
467 like it always used to, and the difference will be irrelevant.
469 If you remove 'device random', you get *NO* kernel-processed
470 entropy at all. This may be acceptable to folks building
471 embedded systems, but has complications. Carry on reading,
472 and it is assumed you know what you need.
474 *PLEASE* read random(4) and random(9) if you are in the
475 habit of tweaking kernel configs, and/or if you are a member
476 of the embedded community, wanting specific and not-usual
477 behaviour from your security subsystems.
479 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
480 random', you will NOT have a functioning /dev/random, and
481 many cryptographic features will not work, including SSH.
482 You may also find strange behaviour from the random(3) set
483 of library functions, in particular sranddev(3), srandomdev(3)
484 and arc4random(3). The reason for this is that the KERN_ARND
485 sysctl only returns entropy if it thinks it has some to
486 share, and with RANDOM_DUMMY or no 'device random' this
490 An additional fix for the issue described in the 20150614 sendmail
491 entry below has been been committed in revision 284717.
494 FreeBSD's old make (fmake) has been removed from the system. It is
495 available as the devel/fmake port or via pkg install fmake.
498 The fix for the issue described in the 20150614 sendmail entry
499 below has been been committed in revision 284436. The work
500 around described in that entry is no longer needed unless the
501 default setting is overridden by a confDH_PARAMETERS configuration
502 setting of '5' or pointing to a 512 bit DH parameter file.
505 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
506 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
507 and devel/kyua to version 0.20+ and adjust any calling code to work
508 with Kyuafile and kyua.
511 The import of openssl to address the FreeBSD-SA-15:10.openssl
512 security advisory includes a change which rejects handshakes
513 with DH parameters below 768 bits. sendmail releases prior
514 to 8.15.2 (not yet released), defaulted to a 512 bit
515 DH parameter setting for client connections. To work around
516 this interoperability, sendmail can be configured to use a
517 2048 bit DH parameter by:
519 1. Edit /etc/mail/`hostname`.mc
520 2. If a setting for confDH_PARAMETERS does not exist or
521 exists and is set to a string beginning with '5',
523 3. If a setting for confDH_PARAMETERS exists and is set to
524 a file path, create a new file with:
525 openssl dhparam -out /path/to/file 2048
526 4. Rebuild the .cf file:
527 cd /etc/mail/; make; make install
529 cd /etc/mail/; make restart
531 A sendmail patch is coming, at which time this file will be
535 Generation of legacy formatted entries have been disabled by default
536 in pwd_mkdb(8), as all base system consumers of the legacy formatted
537 entries were converted to use the new format by default when the new,
538 machine independent format have been added and supported since FreeBSD
541 Please see the pwd_mkdb(8) manual page for further details.
544 Clang and llvm have been upgraded to 3.6.1 release. Please see the
545 20141231 entry below for information about prerequisites and upgrading,
546 if you are not already using 3.5.0 or higher.
549 TI platform code switched to using vendor DTS files and this update
550 may break existing systems running on Beaglebone, Beaglebone Black,
553 - dtb files should be regenerated/reinstalled. Filenames are the
554 same but content is different now
555 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
556 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
557 addressing scheme is now pin 25 on /dev/gpioc3.
558 - Pandaboard: /etc/ttys should be updated, serial console device is
559 now /dev/ttyu2, not /dev/ttyu0
562 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
563 If you need the GNU extension from groff soelim(1), install groff
564 from package: pkg install groff, or via ports: textproc/groff.
567 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
568 defined in symlink(7); previously symlinks were silently ignored.
571 The const qualifier has been removed from iconv(3) to comply with
572 POSIX. The ports tree is aware of this from r384038 onwards.
575 Libraries specified by LIBADD in Makefiles must have a corresponding
576 DPADD_<lib> variable to ensure correct dependencies. This is now
577 enforced in src.libnames.mk.
580 From legacy ata(4) driver was removed support for SATA controllers
581 supported by more functional drivers ahci(4), siis(4) and mvs(4).
582 Kernel modules ataahci and ataadaptec were removed completely,
583 replaced by ahci and mvs modules respectively.
586 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
587 the 20141231 entry below for information about prerequisites and
588 upgrading, if you are not already using 3.5.0 or higher.
591 The 32-bit PowerPC kernel has been changed to a position-independent
592 executable. This can only be booted with a version of loader(8)
593 newer than January 31, 2015, so make sure to update both world and
594 kernel before rebooting.
597 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
598 but before r278950, the RNG was not seeded properly. Immediately
599 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
600 ssh keys or openssl keys) that were generated w/ a kernel from that
601 range. This does not affect programs that directly used /dev/random
602 or /dev/urandom. All userland uses of arc4random(3) are affected.
605 The autofs(4) ABI was changed in order to restore binary compatibility
606 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
610 The powerpc64 kernel has been changed to a position-independent
611 executable. This can only be booted with a new version of loader(8),
612 so make sure to update both world and kernel before rebooting.
615 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
616 only release, no new features have been added. Please see the 20141231
617 entry below for information about prerequisites and upgrading, if you
618 are not already using 3.5.0.
621 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
622 taken from the ELF Tool Chain project rather than GNU binutils. They
623 should be drop-in replacements, with the addition of arm64 support.
624 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
625 binutils tools, if necessary. See 20150805 for updated information.
628 The default Unbound configuration now enables remote control
629 using a local socket. Users who have already enabled the
630 local_unbound service should regenerate their configuration
631 by running "service local_unbound setup" as root.
634 The GNU texinfo and GNU info pages have been removed.
635 To be able to view GNU info pages please install texinfo from ports.
638 Clang, llvm and lldb have been upgraded to 3.5.0 release.
640 As of this release, a prerequisite for building clang, llvm and lldb is
641 a C++11 capable compiler and C++11 standard library. This means that to
642 be able to successfully build the cross-tools stage of buildworld, with
643 clang as the bootstrap compiler, your system compiler or cross compiler
644 should either be clang 3.3 or later, or gcc 4.8 or later, and your
645 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
648 On any standard FreeBSD 10.x or 11.x installation, where clang and
649 libc++ are on by default (that is, on x86 or arm), this should work out
652 On 9.x installations where clang is enabled by default, e.g. on x86 and
653 powerpc, libc++ will not be enabled by default, so libc++ should be
654 built (with clang) and installed first. If both clang and libc++ are
655 missing, build clang first, then use it to build libc++.
657 On 8.x and earlier installations, upgrade to 9.x first, and then follow
658 the instructions for 9.x above.
660 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
661 default, and do not build clang.
663 Many embedded systems are resource constrained, and will not be able to
664 build clang in a reasonable time, or in some cases at all. In those
665 cases, cross building bootable systems on amd64 is a workaround.
667 This new version of clang introduces a number of new warnings, of which
668 the following are most likely to appear:
672 This warns in two cases, for both C and C++:
673 * When the code is trying to take the absolute value of an unsigned
674 quantity, which is effectively a no-op, and almost never what was
675 intended. The code should be fixed, if at all possible. If you are
676 sure that the unsigned quantity can be safely cast to signed, without
677 loss of information or undefined behavior, you can add an explicit
678 cast, or disable the warning.
680 * When the code is trying to take an absolute value, but the called
681 abs() variant is for the wrong type, which can lead to truncation.
682 If you want to disable the warning instead of fixing the code, please
683 make sure that truncation will not occur, or it might lead to unwanted
686 -Wtautological-undefined-compare and
687 -Wundefined-bool-conversion
689 These warn when C++ code is trying to compare 'this' against NULL, while
690 'this' should never be NULL in well-defined C++ code. However, there is
691 some legacy (pre C++11) code out there, which actively abuses this
692 feature, which was less strictly defined in previous C++ versions.
694 Squid and openjdk do this, for example. The warning can be turned off
695 for C++98 and earlier, but compiling the code in C++11 mode might result
696 in unexpected behavior; for example, the parts of the program that are
697 unreachable could be optimized away.
700 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
701 kernel sources have been removed. The .h files remain, since some
702 utilities include them. This will need to be fixed later.
703 If "mount -t oldnfs ..." is attempted, it will fail.
704 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
705 the utilities will report errors.
708 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
709 directories to top level SUBDIR variable when their parent
710 directory is included in LOCAL_DIRS. Users with build systems with
711 such hierarchies and without SUBDIR entries in the parent
712 directory Makefiles should add them or add the directories to
716 faith(4) and faithd(8) have been removed from the base system. Faith
717 has been obsolete for a very long time.
720 vt(4), the new console driver, is enabled by default. It brings
721 support for Unicode and double-width characters, as well as
722 support for UEFI and integration with the KMS kernel video
725 You may need to update your console settings in /etc/rc.conf,
726 most probably the keymap. During boot, /etc/rc.d/syscons will
727 indicate what you need to do.
729 vt(4) still has issues and lacks some features compared to
730 syscons(4). See the wiki for up-to-date information:
731 https://wiki.freebsd.org/Newcons
733 If you want to keep using syscons(4), you can do so by adding
734 the following line to /boot/loader.conf:
738 pjdfstest has been integrated into kyua as an opt-in test suite.
739 Please see share/doc/pjdfstest/README for more details on how to
743 gperf has been removed from the base system for architectures
744 that use clang. Ports that require gperf will obtain it from the
748 pjdfstest has been moved from tools/regression/pjdfstest to
752 At svn r271982, The default linux compat kernel ABI has been adjusted
753 to 2.6.18 in support of the linux-c6 compat ports infrastructure
754 update. If you wish to continue using the linux-f10 compat ports,
755 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
756 encouraged to update their linux-compat packages to linux-c6 during
757 their next update cycle.
760 The ofwfb driver, used to provide a graphics console on PowerPC when
761 using vt(4), no longer allows mmap() of all physical memory. This
762 will prevent Xorg on PowerPC with some ATI graphics cards from
763 initializing properly unless x11-servers/xorg-server is updated to
767 The xdev targets have been converted to using TARGET and
768 TARGET_ARCH instead of XDEV and XDEV_ARCH.
771 The default unbound configuration has been modified to address
772 issues with reverse lookups on networks that use private
773 address ranges. If you use the local_unbound service, run
774 "service local_unbound setup" as root to regenerate your
775 configuration, then "service local_unbound reload" to load the
779 The GNU texinfo and GNU info pages are not built and installed
780 anymore, WITH_INFO knob has been added to allow to built and install
782 UPDATE: see 20150102 entry on texinfo's removal
785 The GNU readline library is now an INTERNALLIB - that is, it is
786 statically linked into consumers (GDB and variants) in the base
787 system, and the shared library is no longer installed. The
788 devel/readline port is available for third party software that
792 The Itanium architecture (ia64) has been removed from the list of
793 known architectures. This is the first step in the removal of the
797 Commit r268115 has added NFSv4.1 server support, merged from
798 projects/nfsv4.1-server. Since this includes changes to the
799 internal interfaces between the NFS related modules, a full
800 build of the kernel and modules will be necessary.
801 __FreeBSD_version has been bumped.
804 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
805 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
806 which differs from the behaviour controlled by this knob.)
809 Maximal length of the serial number in CTL was increased from 16 to
810 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
811 and ctld, need to be rebuilt to work with a new kernel.
814 The libatf-c and libatf-c++ major versions were downgraded to 0 and
815 1 respectively to match the upstream numbers. They were out of
816 sync because, when they were originally added to FreeBSD, the
817 upstream versions were not respected. These libraries are private
818 and not yet built by default, so renumbering them should be a
819 non-issue. However, unclean source trees will yield broken test
820 programs once the operator executes "make delete-old-libs" after a
823 Additionally, the atf-sh binary was made private by moving it into
824 /usr/libexec/. Already-built shell test programs will keep the
825 path to the old binary so they will break after "make delete-old"
828 If you are using WITH_TESTS=yes (not the default), wipe the object
829 tree and rebuild from scratch to prevent spurious test failures.
830 This is only needed once: the misnumbered libraries and misplaced
831 binaries have been added to OptionalObsoleteFiles.inc so they will
832 be removed during a clean upgrade.
835 Clang and llvm have been upgraded to 3.4.1 release.
838 We bogusly installed src.opts.mk in /usr/share/mk. This file should
839 be removed to avoid issues in the future (and has been added to
843 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
844 past, it affected all builds that used the bsd.*.mk files. The old
845 behavior was a bug, but people may have relied upon it. To get this
846 behavior back, you can .include /etc/src.conf from /etc/make.conf
847 (which is still global and isn't changed). This also changes the
848 behavior of incremental builds inside the tree of individual
849 directories. Set MAKESYSPATH to ".../share/mk" to do that.
850 Although this has survived make universe and some upgrade scenarios,
851 other upgrade scenarios may have broken. At least one form of
852 temporary breakage was fixed with MAKESYSPATH settings for buildworld
853 as well... In cases where MAKESYSPATH isn't working with this
854 setting, you'll need to set it to the full path to your tree.
856 One side effect of all this cleaning up is that bsd.compiler.mk
857 is no longer implicitly included by bsd.own.mk. If you wish to
858 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
862 The lindev device has been removed since /dev/full has been made a
863 standard device. __FreeBSD_version has been bumped.
866 The knob WITHOUT_VI was added to the base system, which controls
867 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
868 in order to reorder files share/termcap and didn't build ex(1) as a
869 build tool, so building/installing with WITH_VI is highly advised for
870 build hosts for older releases.
872 This issue has been fixed in stable/9 and stable/10 in r277022 and
873 r276991, respectively.
876 The YES_HESIOD knob has been removed. It has been obsolete for
877 a decade. Please move to using WITH_HESIOD instead or your builds
878 will silently lack HESIOD.
881 The uart(4) driver has been changed with respect to its handling
882 of the low-level console. Previously the uart(4) driver prevented
883 any process from changing the baudrate or the CLOCAL and HUPCL
884 control flags. By removing the restrictions, operators can make
885 changes to the serial console port without having to reboot.
886 However, when getty(8) is started on the serial device that is
887 associated with the low-level console, a misconfigured terminal
888 line in /etc/ttys will now have a real impact.
889 Before upgrading the kernel, make sure that /etc/ttys has the
890 serial console device configured as 3wire without baudrate to
891 preserve the previous behaviour. E.g:
892 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
895 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
896 to improve performance. To re-enable it, if needed, run rpcbind
897 with command line option -W.
900 Switched back to the GPL dtc compiler due to updates in the upstream
901 dts files not being supported by the BSDL dtc compiler. You will need
902 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
903 may result while building dtb files during a kernel build if you fail
904 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
907 Clang and llvm have been upgraded to 3.4 release.
910 The nve(4) driver has been removed. Please use the nfe(4) driver
911 for NVIDIA nForce MCP Ethernet adapters instead.
914 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
915 This could cause certain C++ applications using shared libraries built
916 against the previous version of libc++ to crash. The incompatibility
917 has now been fixed, but any C++ applications or shared libraries built
918 between r261283 and r261801 should be recompiled.
921 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
922 capability mode support. Please note that enabling the feature in
923 kernel is still highly recommended.
926 OpenSSH is now built with sandbox support, and will use sandbox as
927 the default privilege separation method. This requires Capsicum
928 capability mode support in kernel.
931 The libelf and libdwarf libraries have been updated to newer
932 versions from upstream. Shared library version numbers for
933 these two libraries were bumped. Any ports or binaries
934 requiring these two libraries should be recompiled.
935 __FreeBSD_version is bumped to 1100006.
938 If a Makefile in a tests/ directory was auto-generating a Kyuafile
939 instead of providing an explicit one, this would prevent such
940 Makefile from providing its own Kyuafile in the future during
941 NO_CLEAN builds. This has been fixed in the Makefiles but manual
942 intervention is needed to clean an objdir if you use NO_CLEAN:
943 # find /usr/obj -name Kyuafile | xargs rm -f
946 The behavior of gss_pseudo_random() for the krb5 mechanism
947 has changed, for applications requesting a longer random string
948 than produced by the underlying enctype's pseudo-random() function.
949 In particular, the random string produced from a session key of
950 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
951 be different at the 17th octet and later, after this change.
952 The counter used in the PRF+ construction is now encoded as a
953 big-endian integer in accordance with RFC 4402.
954 __FreeBSD_version is bumped to 1100004.
957 The WITHOUT_ATF build knob has been removed and its functionality
958 has been subsumed into the more generic WITHOUT_TESTS. If you were
959 using the former to disable the build of the ATF libraries, you
960 should change your settings to use the latter.
963 The default version of mtree is nmtree which is obtained from
964 NetBSD. The output is generally the same, but may vary
965 slightly. If you found you need identical output adding
966 "-F freebsd9" to the command line should do the trick. For the
967 time being, the old mtree is available as fmtree.
970 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
971 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
972 1.1.4_8 and verify bsdyml not linked in, before running "make
974 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
976 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
979 The stable/10 branch has been created in subversion from head
983 The rc.d/jail script has been updated to support jail(8)
984 configuration file. The "jail_<jname>_*" rc.conf(5) variables
985 for per-jail configuration are automatically converted to
986 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
987 This is transparently backward compatible. See below about some
988 incompatibilities and rc.conf(5) manual page for more details.
990 These variables are now deprecated in favor of jail(8) configuration
991 file. One can use "rc.d/jail config <jname>" command to generate
992 a jail(8) configuration file in /var/run/jail.<jname>.conf without
993 running the jail(8) utility. The default pathname of the
994 configuration file is /etc/jail.conf and can be specified by
995 using $jail_conf or $jail_<jname>_conf variables.
997 Please note that jail_devfs_ruleset accepts an integer at
998 this moment. Please consider to rewrite the ruleset name
1002 BIND has been removed from the base system. If all you need
1003 is a local resolver, simply enable and start the local_unbound
1004 service instead. Otherwise, several versions of BIND are
1005 available in the ports tree. The dns/bind99 port is one example.
1007 With this change, nslookup(1) and dig(1) are no longer in the base
1008 system. Users should instead use host(1) and drill(1) which are
1009 in the base system. Alternatively, nslookup and dig can
1010 be obtained by installing the dns/bind-tools port.
1013 With the addition of unbound(8), a new unbound user is now
1014 required during installworld. "mergemaster -p" can be used to
1015 add the user prior to installworld, as documented in the handbook.
1018 OpenSSH is now built with DNSSEC support, and will by default
1019 silently trust signed SSHFP records. This can be controlled with
1020 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1021 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1024 The GNU Compiler Collection and C++ standard library (libstdc++)
1025 are no longer built by default on platforms where clang is the system
1026 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1027 options in src.conf.
1030 The PROCDESC kernel option is now part of the GENERIC kernel
1031 configuration and is required for the rwhod(8) to work.
1032 If you are using custom kernel configuration, you should include
1036 The API and ABI related to the Capsicum framework was modified
1037 in backward incompatible way. The userland libraries and programs
1038 have to be recompiled to work with the new kernel. This includes the
1039 following libraries and programs, but the whole buildworld is
1040 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1041 kdump, procstat, rwho, rwhod, uniq.
1044 AES-NI intrinsic support has been added to gcc. The AES-NI module
1045 has been updated to use this support. A new gcc is required to build
1046 the aesni module on both i386 and amd64.
1049 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1050 Thus "device padlock_rng" and "device rdrand_rng" should be
1051 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1054 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1055 enables just the iconv* functionality and is now on by default.
1056 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1057 compatibility. Set WITHOUT_ICONV to build the old way.
1058 If you have been using WITH_ICONV before, you will very likely
1059 need to turn on WITH_LIBICONV_COMPAT.
1062 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1063 Illumos origin, including ZFS. If you have INVARIANTS in your
1064 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1066 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1067 locks if WITNESS option was set. Because that generated a lot of
1068 witness(9) reports and all of them were believed to be false
1069 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1070 can be used to achieve the previous behavior.
1073 Timer values in IPv6 data structures now use time_uptime instead
1074 of time_second. Although this is not a user-visible functional
1075 change, userland utilities which directly use them---ndp(8),
1076 rtadvd(8), and rtsold(8) in the base system---need to be updated
1077 to r253970 or later.
1080 find -delete can now delete the pathnames given as arguments,
1081 instead of only files found below them or if the pathname did
1082 not contain any slashes. Formerly, the following error message
1085 find: -delete: <path>: relative path potentially not safe
1087 Deleting the pathnames given as arguments can be prevented
1088 without error messages using -mindepth 1 or by changing
1089 directory and passing "." as argument to find. This works in the
1090 old as well as the new version of find.
1093 Behavior of devfs rules path matching has been changed.
1094 Pattern is now always matched against fully qualified devfs
1095 path and slash characters must be explicitly matched by
1096 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1097 subdirectories must be reviewed.
1100 The default ARM ABI has changed to the ARM EABI. The old ABI is
1101 incompatible with the ARM EABI and all programs and modules will
1102 need to be rebuilt to work with a new kernel.
1104 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1106 NOTE: Support for the old ABI will be removed in the future and
1107 users are advised to upgrade.
1110 pkg_install has been disconnected from the build if you really need it
1111 you should add WITH_PKGTOOLS in your src.conf(5).
1114 Most of network statistics structures were changed to be able
1115 keep 64-bits counters. Thus all tools, that work with networking
1116 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1119 Fix a bug that allowed a tracing process (e.g. gdb) to write
1120 to a memory-mapped file in the traced process's address space
1121 even if neither the traced process nor the tracing process had
1122 write access to that file.
1125 CVS has been removed from the base system. An exact copy
1126 of the code is available from the devel/cvs port.
1129 Some people report the following error after the switch to bmake:
1131 make: illegal option -- J
1132 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1134 *** [buildworld] Error code 2
1136 this likely due to an old instance of make in
1137 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1138 which src/Makefile will use that blindly, if it exists, so if
1139 you see the above error:
1141 rm -rf `make -V MAKEPATH`
1146 Use bmake by default.
1147 Whereas before one could choose to build with bmake via
1148 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1149 make. The goal is to remove these knobs for 10-RELEASE.
1151 It is worth noting that bmake (like gmake) treats the command
1152 line as the unit of failure, rather than statements within the
1153 command line. Thus '(cd some/where && dosomething)' is safer
1154 than 'cd some/where; dosomething'. The '()' allows consistent
1155 behavior in parallel build.
1158 Fix a bug that allows NFS clients to issue READDIR on files.
1161 The WITHOUT_IDEA option has been removed because
1162 the IDEA patent expired.
1165 The sysctl which controls TRIM support under ZFS has been renamed
1166 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1170 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1171 rather than creating it's own in the temporary directory in
1172 order allow access to bootstrapped versions of tools such as
1173 install and mtree. When upgrading from version of FreeBSD where
1174 the install command does not support -l, you will need to
1175 install a new mergemaster command if mergemaster -p is required.
1176 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1180 Legacy ATA stack, disabled and replaced by new CAM-based one since
1181 FreeBSD 9.0, completely removed from the sources. Kernel modules
1182 atadisk and atapi*, user-level tools atacontrol and burncd are
1183 removed. Kernel option `options ATA_CAM` is now permanently enabled
1187 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1188 and socketpair(2). Software, in particular Kerberos, may
1189 automatically detect and use these during building. The resulting
1190 binaries will not work on older kernels.
1193 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1194 information, see the respective 20130304 entry).
1197 Recent commits to callout(9) changed the size of struct callout,
1198 so the KBI is probably heavily disturbed. Also, some functions
1199 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1200 by macros. Every kernel module using it won't load, so rebuild
1203 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1204 but does not initialize by default (because of the new CTL_DISABLE
1205 option) to save memory. To re-enable it, remove the CTL_DISABLE
1206 option from the kernel config file or set kern.cam.ctl.disable=0
1207 in /boot/loader.conf.
1210 The ctl device has been disabled in GENERIC for i386 and amd64.
1211 This was done due to the extra memory being allocated at system
1212 initialisation time by the ctl driver which was only used if
1213 a CAM target device was created. This makes a FreeBSD system
1214 unusable on 128MB or less of RAM.
1217 A new compression method (lz4) has been merged to -HEAD. Please
1218 refer to zpool-features(7) for more information.
1220 Please refer to the "ZFS notes" section of this file for information
1221 on upgrading boot ZFS pools.
1224 A BSD-licensed patch(1) variant has been added and is installed
1225 as bsdpatch, being the GNU version the default patch.
1226 To inverse the logic and use the BSD-licensed one as default,
1227 while having the GNU version installed as gnupatch, rebuild
1228 and install world with the WITH_BSD_PATCH knob set.
1231 Due to the use of the new -l option to install(1) during build
1232 and install, you must take care not to directly set the INSTALL
1233 make variable in your /etc/make.conf, /etc/src.conf, or on the
1234 command line. If you wish to use the -C flag for all installs
1235 you may be able to add INSTALL+=-C to /etc/make.conf or
1239 The install(1) option -M has changed meaning and now takes an
1240 argument that is a file or path to append logs to. In the
1241 unlikely event that -M was the last option on the command line
1242 and the command line contained at least two files and a target
1243 directory the first file will have logs appended to it. The -M
1244 option served little practical purpose in the last decade so its
1245 use is expected to be extremely rare.
1248 After switching to Clang as the default compiler some users of ZFS
1249 on i386 systems started to experience stack overflow kernel panics.
1250 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1253 GEOM_LABEL now mangles label names read from file system metadata.
1254 Mangling affect labels containing spaces, non-printable characters,
1255 '%' or '"'. Device names in /etc/fstab and other places may need to
1259 By default, only the 10 most recent kernel dumps will be saved. To
1260 restore the previous behaviour (no limit on the number of kernel dumps
1261 stored in the dump directory) add the following line to /etc/rc.conf:
1266 With the addition of auditdistd(8), a new auditdistd user is now
1267 required during installworld. "mergemaster -p" can be used to
1268 add the user prior to installworld, as documented in the handbook.
1271 The sin6_scope_id member variable in struct sockaddr_in6 is now
1272 filled by the kernel before passing the structure to the userland via
1273 sysctl or routing socket. This means the KAME-specific embedded scope
1274 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1275 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1276 __FreeBSD_version is bumped to 1000025.
1279 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1280 This means that the world and kernel will be compiled with clang
1281 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1282 and /usr/bin/cpp. To disable this behavior and revert to building
1283 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1284 of current may need to bootstrap WITHOUT_CLANG first if the clang
1285 build fails (its compatibility window doesn't extend to the 9 stable
1289 The IPFIREWALL_FORWARD kernel option has been removed. Its
1290 functionality now turned on by default.
1293 The ZERO_COPY_SOCKET kernel option has been removed and
1294 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1295 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1296 mechanism which is not safe and may result in kernel crashes.
1297 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1298 driver supports disposeable external page sized mbuf storage.
1299 Proper replacements for both zero-copy mechanisms are under
1300 consideration and will eventually lead to complete removal
1301 of the two kernel options.
1304 The IPv4 network stack has been converted to network byte
1305 order. The following modules need to be recompiled together
1306 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1307 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1310 Support for non-MPSAFE filesystems was removed from VFS. The
1311 VFS_VERSION was bumped, all filesystem modules shall be
1315 All the non-MPSAFE filesystems have been disconnected from
1316 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1317 portalfs, smbfs, xfs.
1320 The interface cloning API and ABI has changed. The following
1321 modules need to be recompiled together with kernel:
1322 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1323 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1324 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1327 The sdhci driver was split in two parts: sdhci (generic SD Host
1328 Controller logic) and sdhci_pci (actual hardware driver).
1329 No kernel config modifications are required, but if you
1330 load sdhc as a module you must switch to sdhci_pci instead.
1333 Import the FUSE kernel and userland support into base system.
1336 The GNU sort(1) program has been removed since the BSD-licensed
1337 sort(1) has been the default for quite some time and no serious
1338 problems have been reported. The corresponding WITH_GNU_SORT
1342 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1343 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1347 The net80211(4) ABI has been changed to allow for improved driver
1348 PS-POLL and power-save support. All wireless drivers need to be
1349 recompiled to work with the new kernel.
1352 The random(4) support for the VIA hardware random number
1353 generator (`PADLOCK') is no longer enabled unconditionally.
1354 Add the padlock_rng device in the custom kernel config if
1355 needed. The GENERIC kernels on i386 and amd64 do include the
1356 device, so the change only affects the custom kernel
1360 The pf(4) packet filter ABI has been changed. pfctl(8) and
1361 snmp_pf module need to be recompiled to work with new kernel.
1364 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1365 to -HEAD. Pools that have empty_bpobj in active state can not be
1366 imported read-write with ZFS implementations that do not support
1367 this feature. For more information read the zpool-features(5)
1371 The sparc64 ZFS loader has been changed to no longer try to auto-
1372 detect ZFS providers based on diskN aliases but now requires these
1373 to be explicitly listed in the OFW boot-device environment variable.
1376 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1377 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1378 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1381 The following sysctls and tunables have been renamed for consistency
1382 with other variables:
1383 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1384 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1387 The sort utility has been replaced with BSD sort. For now, GNU sort
1388 is also available as "gnusort" or the default can be set back to
1389 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1390 installed as "bsdsort".
1393 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1394 Starting with this version the old system of ZFS pool versioning
1395 is superseded by "feature flags". This concept enables forward
1396 compatibility against certain future changes in functionality of ZFS
1397 pools. The first read-only compatible "feature flag" for ZFS pools
1398 is named "com.delphix:async_destroy". For more information
1399 read the new zpool-features(5) manual page.
1400 Please refer to the "ZFS notes" section of this file for information
1401 on upgrading boot ZFS pools.
1404 The malloc(3) implementation embedded in libc now uses sources imported
1405 as contrib/jemalloc. The most disruptive API change is to
1406 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1407 delete it prior to installworld, and optionally re-create it using the
1408 new format after rebooting. See malloc.conf(5) for details
1409 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1413 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1414 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1415 now spelled mips. This is to aid compatibility with third-party
1416 software that expects this naming scheme in uname(3). Little-endian
1417 settings are unchanged. If you are updating a big-endian mips64 machine
1418 from before this change, you may need to set MACHINE_ARCH=mips64 in
1419 your environment before the new build system will recognize your machine.
1422 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1426 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1427 nullfs(5) did not pass through all behaviours to the underlying layer,
1428 as a result if we bound to a socket on the lower layer we could connect
1429 only to the lower path; if we bound to the upper layer we could connect
1430 only to the upper path. The new behavior is one can connect to both the
1431 lower and the upper paths regardless what layer path one binds to.
1434 The getifaddrs upgrade path broken with 20111215 has been restored.
1435 If you have upgraded in between 20111215 and 20120209 you need to
1436 recompile libc again with your kernel. You still need to recompile
1437 world to be able to configure CARP but this restriction already
1438 comes from 20111215.
1441 The set_rcvar() function has been removed from /etc/rc.subr. All
1442 base and ports rc.d scripts have been updated, so if you have a
1443 port installed with a script in /usr/local/etc/rc.d you can either
1444 hand-edit the rcvar= line, or reinstall the port.
1446 An easy way to handle the mass-update of /etc/rc.d:
1447 rm /etc/rc.d/* && mergemaster -i
1450 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1451 on the current CPU and prevents other threads from running.
1452 This behavior can be reverted using the kern.stop_scheduler_on_panic
1454 The new behavior can be incompatible with kern.sync_on_panic.
1457 The carp(4) facility has been changed significantly. Configuration
1458 of the CARP protocol via ifconfig(8) has changed, as well as format
1459 of CARP events submitted to devd(8) has changed. See manual pages
1460 for more information. The arpbalance feature of carp(4) is currently
1461 not supported anymore.
1463 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1464 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1465 need to be recompiled.
1468 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1472 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1473 explicitely support non-MPSAFE filesystems.
1474 It is on by default for all supported platform at this present
1478 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1479 i386 and pc98 GENERIC kernel configuration files.
1482 sysinstall has been removed
1485 The stable/9 branch created in subversion. This corresponds to the
1486 RELENG_9 branch in CVS.
1492 Avoid using make -j when upgrading. While generally safe, there are
1493 sometimes problems using -j to upgrade. If your upgrade fails with
1494 -j, please try again without -j. From time to time in the past there
1495 have been problems using -j with buildworld and/or installworld. This
1496 is especially true when upgrading between "distant" versions (eg one
1497 that cross a major release boundary or several minor releases, or when
1498 several months have passed on the -current branch).
1500 Sometimes, obscure build problems are the result of environment
1501 poisoning. This can happen because the make utility reads its
1502 environment when searching for values for global variables. To run
1503 your build attempts in an "environmental clean room", prefix all make
1504 commands with 'env -i '. See the env(1) manual page for more details.
1506 When upgrading from one major version to another it is generally best to
1507 upgrade to the latest code in the currently installed branch first, then
1508 do an upgrade to the new branch. This is the best-tested upgrade path,
1509 and has the highest probability of being successful. Please try this
1510 approach if you encounter problems with a major version upgrade. Since
1511 the stable 4.x branch point, one has generally been able to upgade from
1512 anywhere in the most recent stable branch to head / current (or even the
1513 last couple of stable branches). See the top of this file when there's
1516 When upgrading a live system, having a root shell around before
1517 installing anything can help undo problems. Not having a root shell
1518 around can lead to problems if pam has changed too much from your
1519 starting point to allow continued authentication after the upgrade.
1521 This file should be read as a log of events. When a later event changes
1522 information of a prior event, the prior event should not be deleted.
1523 Instead, a pointer to the entry with the new information should be
1524 placed in the old entry. Readers of this file should also sanity check
1525 older entries before relying on them blindly. Authors of new entries
1526 should write them with this in mind.
1530 When upgrading the boot ZFS pool to a new version, always follow
1533 1.) recompile and reinstall the ZFS boot loader and boot block
1534 (this is part of "make buildworld" and "make installworld")
1536 2.) update the ZFS boot block on your boot drive
1538 The following example updates the ZFS boot block on the first
1539 partition (freebsd-boot) of a GPT partitioned drive ada0:
1540 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1542 Non-boot pools do not need these updates.
1546 If you are updating from a prior version of FreeBSD (even one just
1547 a few days old), you should follow this procedure. It is the most
1548 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1550 make kernel-toolchain
1551 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1552 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1554 To test a kernel once
1555 ---------------------
1556 If you just want to boot a kernel once (because you are not sure
1557 if it works, or if you want to boot a known bad kernel to provide
1558 debugging information) run
1559 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1560 nextboot -k testkernel
1562 To just build a kernel when you know that it won't mess you up
1563 --------------------------------------------------------------
1564 This assumes you are already running a CURRENT system. Replace
1565 ${arch} with the architecture of your machine (e.g. "i386",
1566 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1568 cd src/sys/${arch}/conf
1569 config KERNEL_NAME_HERE
1570 cd ../compile/KERNEL_NAME_HERE
1575 If this fails, go to the "To build a kernel" section.
1577 To rebuild everything and install it on the current system.
1578 -----------------------------------------------------------
1579 # Note: sometimes if you are running current you gotta do more than
1580 # is listed here if you are upgrading from a really old current.
1582 <make sure you have good level 0 dumps>
1584 make kernel KERNCONF=YOUR_KERNEL_HERE
1586 <reboot in single user> [3]
1593 To cross-install current onto a separate partition
1594 --------------------------------------------------
1595 # In this approach we use a separate partition to hold
1596 # current's root, 'usr', and 'var' directories. A partition
1597 # holding "/", "/usr" and "/var" should be about 2GB in
1600 <make sure you have good level 0 dumps>
1603 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1604 <maybe newfs current's root partition>
1605 <mount current's root partition on directory ${CURRENT_ROOT}>
1606 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1607 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1608 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1609 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1610 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1611 <reboot into current>
1612 <do a "native" rebuild/install as described in the previous section>
1613 <maybe install compatibility libraries from ports/misc/compat*>
1617 To upgrade in-place from stable to current
1618 ----------------------------------------------
1619 <make sure you have good level 0 dumps>
1621 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1623 <reboot in single user> [3]
1630 Make sure that you've read the UPDATING file to understand the
1631 tweaks to various things you need. At this point in the life
1632 cycle of current, things change often and you are on your own
1633 to cope. The defaults can also change, so please read ALL of
1634 the UPDATING entries.
1636 Also, if you are tracking -current, you must be subscribed to
1637 freebsd-current@freebsd.org. Make sure that before you update
1638 your sources that you have read and understood all the recent
1639 messages there. If in doubt, please track -stable which has
1640 much fewer pitfalls.
1642 [1] If you have third party modules, such as vmware, you
1643 should disable them at this point so they don't crash your
1646 [3] From the bootblocks, boot -s, and then do
1651 adjkerntz -i # if CMOS is wall time
1652 Also, when doing a major release upgrade, it is required that
1653 you boot into single user mode to do the installworld.
1655 [4] Note: This step is non-optional. Failure to do this step
1656 can result in a significant reduction in the functionality of the
1657 system. Attempting to do it by hand is not recommended and those
1658 that pursue this avenue should read this file carefully, as well
1659 as the archives of freebsd-current and freebsd-hackers mailing lists
1660 for potential gotchas. The -U option is also useful to consider.
1661 See mergemaster(8) for more information.
1663 [5] Usually this step is a noop. However, from time to time
1664 you may need to do this if you get unknown user in the following
1665 step. It never hurts to do it all the time. You may need to
1666 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1667 install) after the buildworld before this step if you last updated
1668 from current before 20130425 or from -stable before 20130430.
1670 [6] This only deletes old files and directories. Old libraries
1671 can be deleted by "make delete-old-libs", but you have to make
1672 sure that no program is using those libraries anymore.
1674 [8] In order to have a kernel that can run the 4.x binaries needed to
1675 do an installworld, you must include the COMPAT_FREEBSD4 option in
1676 your kernel. Failure to do so may leave you with a system that is
1677 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1678 required to run the 5.x binaries on more recent kernels. And so on
1679 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1681 Make sure that you merge any new devices from GENERIC since the
1682 last time you updated your kernel config file.
1684 [9] When checking out sources, you must include the -P flag to have
1685 cvs prune empty directories.
1687 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1688 "?=" instead of the "=" assignment operator, so that buildworld can
1689 override the CPUTYPE if it needs to.
1691 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1692 not on the command line, or in /etc/make.conf. buildworld will
1693 warn if it is improperly defined.
1696 This file contains a list, in reverse chronological order, of major
1697 breakages in tracking -current. It is not guaranteed to be a complete
1698 list of such breakages, and only contains entries since September 23, 2011.
1699 If you need to see UPDATING entries from before that date, you will need
1700 to fetch an UPDATING file from an older FreeBSD release.
1702 Copyright information:
1704 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1706 Redistribution, publication, translation and use, with or without
1707 modification, in full or in part, in any form or format of this
1708 document are permitted without further permission from the author.
1710 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1711 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1712 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1713 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1714 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1715 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1716 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1717 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1718 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1719 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1720 POSSIBILITY OF SUCH DAMAGE.
1722 Contact Warner Losh if you have any questions about your use of