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 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-src.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 20171017 p13 FreeBSD-SA-17:07.wpa
21 Fix WPA2 protocol vulnerability. [SA-17:07]
23 20170810 p1 FreeBSD-SA-17:06.openssh
27 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
29 Fix VNET kernel panic with asynchronous I/O. [EN-17:07]
31 Fix pf(4) housekeeping thread causes kernel panic. [EN-17:08]
37 arm64 builds now use the base system LLD 4.0.0 linker by default,
38 instead of requiring that the aarch64-binutils port or package be
39 installed. To continue using aarch64-binutils, set
40 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
43 The ctl.ko module no longer implements the iSCSI target frontend:
44 cfiscsi.ko does instead.
46 If building cfiscsi.ko as a kernel module, the module can be loaded
47 via one of the following methods:
48 - `cfiscsi_load="YES"` in loader.conf(5).
49 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
50 - ctladm(8)/ctld(8), when compiled with iSCSI support
51 (`WITH_ISCSI=yes` in src.conf(5))
53 Please see cfiscsi(4) for more details.
56 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
57 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
58 same source (previously, the dependency of mmcsd.ko on mmc.ko was
59 missing, but mmcsd.ko now will refuse to load if it is incompatible
63 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
64 use any explicitly assigned loopback address available in the jail
65 instead of using the first assigned address of the jail.
68 As of r316810 for ipfilter, keep frags is no longer assumed when
69 keep state is specified in a rule. r316810 aligns ipfilter with
70 documentation in man pages separating keep frags from keep state.
71 This allows keep state to specified without forcing keep frags
72 and allows keep frags to be specified independently of keep state.
73 To maintain previous behaviour, also specify keep frags with
74 keep state (as documented in ipf.conf.5).
77 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
78 Please see the 20141231 entry below for information about prerequisites
79 and upgrading, if you are not already using clang 3.5.0 or higher.
82 The code that provides support for ZFS .zfs/ directory functionality
83 has been reimplemented. It's not possible now to create a snapshot
84 by mkdir under .zfs/snapshot/. That should be the only user visible
88 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
89 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
90 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
91 and now NAT-T is supported by default. Security associations now use
92 the single namespace for SPI allocation, so if you use several manually
93 configured security associations with the same SPI, this configuration
97 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
98 Please see the 20141231 entry below for information about prerequisites
99 and upgrading, if you are not already using clang 3.5.0 or higher.
102 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
103 Please see the 20141231 entry below for information about prerequisites
104 and upgrading, if you are not already using clang 3.5.0 or higher.
107 The layout of the pmap structure has changed for powerpc to put the pmap
108 statistics at the front for all CPU variations. libkvm(3) and all tools
109 that link against it need to be recompiled.
112 isl(4) and cyapa(4) drivers now require a new driver,
113 chromebook_platform(4), to work properly on Chromebook-class hardware.
114 On other types of hardware the drivers may need to be configured using
115 device hints. Please see the corresponding manual pages for details.
118 Relocatable object files with the extension of .So have been renamed
119 to use an extension of .pico instead. The purpose of this change is
120 to avoid a name clash with shared libraries on case-insensitive file
121 systems. On those file systems, foo.So is the same file as foo.so.
124 The libc stub for the pipe(2) system call has been replaced with
125 a wrapper that calls the pipe2(2) system call and the pipe(2)
126 system call is now only implemented by the kernels that include
127 "options COMPAT_FREEBSD10" in their config file (this is the
128 default). Users should ensure that this option is enabled in
129 their kernel or upgrade userspace to r302092 before upgrading their
133 CAM will now strip leading spaces from SCSI disks' serial numbers.
134 This will effect users who create UFS filesystems on SCSI disks using
135 those disk's diskid device nodes. For example, if /etc/fstab
136 previously contained a line like
137 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
138 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
139 transforms like gmirror may also be affected. ZFS users should
143 The bitstring(3) API has been updated with new functionality and
144 improved performance. But it is binary-incompatible with the old API.
145 Objects built with the new headers may not be linked against objects
146 built with the old headers.
149 The brk and sbrk functions have been removed from libc on arm64.
150 Binutils from ports has been updated to not link to these
151 functions and should be updated to the latest version before
152 installing a new libc.
155 The armv6 port now defaults to hard float ABI. Limited support
156 for running both hardfloat and soft float on the same system
157 is available using the libraries installed with -DWITH_LIBSOFT.
158 This has only been tested as an upgrade path for installworld
159 and packages may fail or need manual intervention to run. New
160 packages will be needed.
162 To update an existing self-hosted armv6hf system, you must add
163 TARGET_ARCH=armv6 on the make command line for both the build
164 and the install steps.
167 Kernel modules compiled outside of a kernel build now default to
168 installing to /boot/modules instead of /boot/kernel. Many kernel
169 modules built this way (such as those in ports) already overrode
170 KMODDIR explicitly to install into /boot/modules. However,
171 manually building and installing a module from /sys/modules will
172 now install to /boot/modules instead of /boot/kernel.
175 The CAM I/O scheduler has been committed to the kernel. There should be
176 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
177 list of known rogues that claim support for this but actually corrupt
178 data is believed to be complete, be on the lookout for data
179 corruption. The known rogue list is believed to be complete:
181 o Crucial MX100, M550 drives with MU01 firmware.
182 o Micron M510 and M550 drives with MU01 firmware.
183 o Micron M500 prior to MU07 firmware
184 o Samsung 830, 840, and 850 all firmwares
185 o FCCT M500 all firmwares
187 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
188 with working NCQ TRIM. For Micron branded drives, see your sales rep for
189 updated firmware. Black listed drives will work correctly because these
190 drives work correctly so long as no NCQ TRIMs are sent to them. Given
191 this list is the same as found in Linux, it's believed there are no
192 other rogues in the market place. All other models from the above
195 To be safe, if you are at all concerned, you can quirk each of your
196 drives to prevent NCQ from being sent by setting:
197 kern.cam.ada.X.quirks="0x2"
198 in loader.conf. If the drive requires the 4k sector quirk, set the
202 The FAST_DEPEND build option has been removed and its functionality is
203 now the one true way. The old mkdep(1) style of 'make depend' has
204 been removed. See 20160311 for further details.
207 Resource range types have grown from unsigned long to uintmax_t. All
208 drivers, and anything using libdevinfo, need to be recompiled.
211 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
212 builds. It no longer runs mkdep(1) during 'make depend', and the
213 'make depend' stage can safely be skipped now as it is auto ran
214 when building 'make all' and will generate all SRCS and DPSRCS before
215 building anything else. Dependencies are gathered at compile time with
216 -MF flags kept in separate .depend files per object file. Users should
217 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
221 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
222 kernel modules. Therefore, if you load any kernel modules at boot time,
223 please install the boot loaders after you install the kernel, but before
227 make kernel KERNCONF=YOUR_KERNEL_HERE
228 make -C sys/boot install
229 <reboot in single user>
231 Then follow the usual steps, described in the General Notes section,
235 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
236 see the 20141231 entry below for information about prerequisites and
237 upgrading, if you are not already using clang 3.5.0 or higher.
240 The AIO subsystem is now a standard part of the kernel. The
241 VFS_AIO kernel option and aio.ko kernel module have been removed.
242 Due to stability concerns, asynchronous I/O requests are only
243 permitted on sockets and raw disks by default. To enable
244 asynchronous I/O requests on all file types, set the
245 vfs.aio.enable_unsafe sysctl to a non-zero value.
248 The ELF object manipulation tool objcopy is now provided by the
249 ELF Tool Chain project rather than by GNU binutils. It should be a
250 drop-in replacement, with the addition of arm64 support. The
251 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
252 to obtain the GNU version if necessary.
255 Building ZFS pools on top of zvols is prohibited by default. That
256 feature has never worked safely; it's always been prone to deadlocks.
257 Using a zvol as the backing store for a VM guest's virtual disk will
258 still work, even if the guest is using ZFS. Legacy behavior can be
259 restored by setting vfs.zfs.vol.recursive=1.
262 The NONE and HPN patches has been removed from OpenSSH. They are
263 still available in the security/openssh-portable port.
266 With the addition of ypldap(8), a new _ypldap user is now required
267 during installworld. "mergemaster -p" can be used to add the user
268 prior to installworld, as documented in the handbook.
271 The tftp loader (pxeboot) now uses the option root-path directive. As a
272 consequence it no longer looks for a pxeboot.4th file on the tftp
273 server. Instead it uses the regular /boot infrastructure as with the
277 The code to start recording plug and play data into the modules has
278 been committed. While the old tools will properly build a new kernel,
279 a number of warnings about "unknown metadata record 4" will be produced
280 for an older kldxref. To avoid such warnings, make sure to rebuild
281 the kernel toolchain (or world). Make sure that you have r292078 or
282 later when trying to build 292077 or later before rebuilding.
285 Debug data files are now built by default with 'make buildworld' and
286 installed with 'make installworld'. This facilitates debugging but
287 requires more disk space both during the build and for the installed
288 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
292 r291527 changed the internal interface between the nfsd.ko and
293 nfscommon.ko modules. As such, they must both be upgraded to-gether.
294 __FreeBSD_version has been bumped because of this.
297 Add support for unicode collation strings leads to a change of
298 order of files listed by ls(1) for example. To get back to the old
299 behaviour, set LC_COLLATE environment variable to "C".
301 Databases administrators will need to reindex their databases given
302 collation results will be different.
304 Due to a bug in install(1) it is recommended to remove the ancient
305 locales before running make installworld.
307 rm -rf /usr/share/locale/*
310 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
311 libcrypto.so.7 or libssl.so.7 must be recompiled.
314 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
315 Kernel modules isp_2400_multi and isp_2500_multi were removed and
316 should be replaced with isp_2400 and isp_2500 modules respectively.
319 The build previously allowed using 'make -n' to not recurse into
320 sub-directories while showing what commands would be executed, and
321 'make -n -n' to recursively show commands. Now 'make -n' will recurse
322 and 'make -N' will not.
325 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
326 and etcupdate will now use this file. A custom sendmail.cf is now
327 updated via this mechanism rather than via installworld. If you had
328 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
329 want to remove the exclusion or change it to "always install".
330 /etc/mail/sendmail.cf is now managed the same way regardless of
331 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
332 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
335 Compatibility shims for legacy ATA device names have been removed.
336 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
337 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
338 environment variables, /dev/ad* and /dev/ar* symbolic links.
341 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
342 Please see the 20141231 entry below for information about prerequisites
343 and upgrading, if you are not already using clang 3.5.0 or higher.
346 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
347 and renamed from .symbols to .debug. This reduces the size requirements
348 on the boot partition or file system and provides consistency with
349 userland debug files.
351 When using the supported kernel installation method the
352 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
353 as is done with /boot/kernel.
355 Developers wishing to maintain the historical behavior of installing
356 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
359 The wireless drivers had undergone changes that remove the 'parent
360 interface' from the ifconfig -l output. The rc.d network scripts
361 used to check presence of a parent interface in the list, so old
362 scripts would fail to start wireless networking. Thus, etcupdate(3)
363 or mergemaster(8) run is required after kernel update, to update your
364 rc.d scripts in /etc.
367 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
368 These configurations are now automatically interpreted as
369 'scrub fragment reassemble'.
372 Kernel-loadable modules for the random(4) device are back. To use
373 them, the kernel must have
376 options RANDOM_LOADABLE
378 kldload(8) can then be used to load random_fortuna.ko
379 or random_yarrow.ko. Please note that due to the indirect
380 function calls that the loadable modules need to provide,
381 the build-in variants will be slightly more efficient.
383 The random(4) kernel option RANDOM_DUMMY has been retired due to
384 unpopularity. It was not all that useful anyway.
387 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
388 Control over building the ELF Tool Chain tools is now provided by
389 the WITHOUT_TOOLCHAIN knob.
392 The polarity of Pulse Per Second (PPS) capture events with the
393 uart(4) driver has been corrected. Prior to this change the PPS
394 "assert" event corresponded to the trailing edge of a positive PPS
395 pulse and the "clear" event was the leading edge of the next pulse.
397 As the width of a PPS pulse in a typical GPS receiver is on the
398 order of 1 millisecond, most users will not notice any significant
399 difference with this change.
401 Anyone who has compensated for the historical polarity reversal by
402 configuring a negative offset equal to the pulse width will need to
403 remove that workaround.
406 The default group assigned to /dev/dri entries has been changed
407 from 'wheel' to 'video' with the id of '44'. If you want to have
408 access to the dri devices please add yourself to the video group
411 # pw groupmod video -m $USER
414 The menu.rc and loader.rc files will now be replaced during
415 upgrades. Please migrate local changes to menu.rc.local and
416 loader.rc.local instead.
419 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
420 strings and strip have been removed. The src.conf(5) knob
421 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
424 As ZFS requires more kernel stack pages than is the default on some
425 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
426 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
428 Please consider using 'options KSTACK_PAGES=X' where X is greater
429 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
432 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
433 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
434 default, i.e., they will not contain "::". For example, instead
435 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
436 to have a more specific match, such as different map entries for
437 IPv6:0:0 vs IPv6:0. This change requires that configuration
438 data (including maps, files, classes, custom ruleset, etc.) must
439 use the same format, so make certain such configuration data is
440 upgrading. As a very simple check search for patterns like
441 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
442 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
443 the cf option UseCompressedIPv6Addresses.
446 The default kernel entropy-processing algorithm is now
447 Fortuna, replacing Yarrow.
449 Assuming you have 'device random' in your kernel config
450 file, the configurations allow a kernel option to override
451 this default. You may choose *ONE* of:
453 options RANDOM_YARROW # Legacy /dev/random algorithm.
454 options RANDOM_DUMMY # Blocking-only driver.
456 If you have neither, you get Fortuna. For most people,
457 read no further, Fortuna will give a /dev/random that works
458 like it always used to, and the difference will be irrelevant.
460 If you remove 'device random', you get *NO* kernel-processed
461 entropy at all. This may be acceptable to folks building
462 embedded systems, but has complications. Carry on reading,
463 and it is assumed you know what you need.
465 *PLEASE* read random(4) and random(9) if you are in the
466 habit of tweaking kernel configs, and/or if you are a member
467 of the embedded community, wanting specific and not-usual
468 behaviour from your security subsystems.
470 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
471 random', you will NOT have a functioning /dev/random, and
472 many cryptographic features will not work, including SSH.
473 You may also find strange behaviour from the random(3) set
474 of library functions, in particular sranddev(3), srandomdev(3)
475 and arc4random(3). The reason for this is that the KERN_ARND
476 sysctl only returns entropy if it thinks it has some to
477 share, and with RANDOM_DUMMY or no 'device random' this
481 An additional fix for the issue described in the 20150614 sendmail
482 entry below has been been committed in revision 284717.
485 FreeBSD's old make (fmake) has been removed from the system. It is
486 available as the devel/fmake port or via pkg install fmake.
489 The fix for the issue described in the 20150614 sendmail entry
490 below has been been committed in revision 284436. The work
491 around described in that entry is no longer needed unless the
492 default setting is overridden by a confDH_PARAMETERS configuration
493 setting of '5' or pointing to a 512 bit DH parameter file.
496 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
497 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
498 and devel/kyua to version 0.20+ and adjust any calling code to work
499 with Kyuafile and kyua.
502 The import of openssl to address the FreeBSD-SA-15:10.openssl
503 security advisory includes a change which rejects handshakes
504 with DH parameters below 768 bits. sendmail releases prior
505 to 8.15.2 (not yet released), defaulted to a 512 bit
506 DH parameter setting for client connections. To work around
507 this interoperability, sendmail can be configured to use a
508 2048 bit DH parameter by:
510 1. Edit /etc/mail/`hostname`.mc
511 2. If a setting for confDH_PARAMETERS does not exist or
512 exists and is set to a string beginning with '5',
514 3. If a setting for confDH_PARAMETERS exists and is set to
515 a file path, create a new file with:
516 openssl dhparam -out /path/to/file 2048
517 4. Rebuild the .cf file:
518 cd /etc/mail/; make; make install
520 cd /etc/mail/; make restart
522 A sendmail patch is coming, at which time this file will be
526 Generation of legacy formatted entries have been disabled by default
527 in pwd_mkdb(8), as all base system consumers of the legacy formatted
528 entries were converted to use the new format by default when the new,
529 machine independent format have been added and supported since FreeBSD
532 Please see the pwd_mkdb(8) manual page for further details.
535 Clang and llvm have been upgraded to 3.6.1 release. Please see the
536 20141231 entry below for information about prerequisites and upgrading,
537 if you are not already using 3.5.0 or higher.
540 TI platform code switched to using vendor DTS files and this update
541 may break existing systems running on Beaglebone, Beaglebone Black,
544 - dtb files should be regenerated/reinstalled. Filenames are the
545 same but content is different now
546 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
547 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
548 addressing scheme is now pin 25 on /dev/gpioc3.
549 - Pandaboard: /etc/ttys should be updated, serial console device is
550 now /dev/ttyu2, not /dev/ttyu0
553 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
554 If you need the GNU extension from groff soelim(1), install groff
555 from package: pkg install groff, or via ports: textproc/groff.
558 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
559 defined in symlink(7); previously symlinks were silently ignored.
562 The const qualifier has been removed from iconv(3) to comply with
563 POSIX. The ports tree is aware of this from r384038 onwards.
566 Libraries specified by LIBADD in Makefiles must have a corresponding
567 DPADD_<lib> variable to ensure correct dependencies. This is now
568 enforced in src.libnames.mk.
571 From legacy ata(4) driver was removed support for SATA controllers
572 supported by more functional drivers ahci(4), siis(4) and mvs(4).
573 Kernel modules ataahci and ataadaptec were removed completely,
574 replaced by ahci and mvs modules respectively.
577 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
578 the 20141231 entry below for information about prerequisites and
579 upgrading, if you are not already using 3.5.0 or higher.
582 The 32-bit PowerPC kernel has been changed to a position-independent
583 executable. This can only be booted with a version of loader(8)
584 newer than January 31, 2015, so make sure to update both world and
585 kernel before rebooting.
588 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
589 but before r278950, the RNG was not seeded properly. Immediately
590 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
591 ssh keys or openssl keys) that were generated w/ a kernel from that
592 range. This does not affect programs that directly used /dev/random
593 or /dev/urandom. All userland uses of arc4random(3) are affected.
596 The autofs(4) ABI was changed in order to restore binary compatibility
597 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
601 The powerpc64 kernel has been changed to a position-independent
602 executable. This can only be booted with a new version of loader(8),
603 so make sure to update both world and kernel before rebooting.
606 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
607 only release, no new features have been added. Please see the 20141231
608 entry below for information about prerequisites and upgrading, if you
609 are not already using 3.5.0.
612 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
613 taken from the ELF Tool Chain project rather than GNU binutils. They
614 should be drop-in replacements, with the addition of arm64 support.
615 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
616 binutils tools, if necessary. See 20150805 for updated information.
619 The default Unbound configuration now enables remote control
620 using a local socket. Users who have already enabled the
621 local_unbound service should regenerate their configuration
622 by running "service local_unbound setup" as root.
625 The GNU texinfo and GNU info pages have been removed.
626 To be able to view GNU info pages please install texinfo from ports.
629 Clang, llvm and lldb have been upgraded to 3.5.0 release.
631 As of this release, a prerequisite for building clang, llvm and lldb is
632 a C++11 capable compiler and C++11 standard library. This means that to
633 be able to successfully build the cross-tools stage of buildworld, with
634 clang as the bootstrap compiler, your system compiler or cross compiler
635 should either be clang 3.3 or later, or gcc 4.8 or later, and your
636 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
639 On any standard FreeBSD 10.x or 11.x installation, where clang and
640 libc++ are on by default (that is, on x86 or arm), this should work out
643 On 9.x installations where clang is enabled by default, e.g. on x86 and
644 powerpc, libc++ will not be enabled by default, so libc++ should be
645 built (with clang) and installed first. If both clang and libc++ are
646 missing, build clang first, then use it to build libc++.
648 On 8.x and earlier installations, upgrade to 9.x first, and then follow
649 the instructions for 9.x above.
651 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
652 default, and do not build clang.
654 Many embedded systems are resource constrained, and will not be able to
655 build clang in a reasonable time, or in some cases at all. In those
656 cases, cross building bootable systems on amd64 is a workaround.
658 This new version of clang introduces a number of new warnings, of which
659 the following are most likely to appear:
663 This warns in two cases, for both C and C++:
664 * When the code is trying to take the absolute value of an unsigned
665 quantity, which is effectively a no-op, and almost never what was
666 intended. The code should be fixed, if at all possible. If you are
667 sure that the unsigned quantity can be safely cast to signed, without
668 loss of information or undefined behavior, you can add an explicit
669 cast, or disable the warning.
671 * When the code is trying to take an absolute value, but the called
672 abs() variant is for the wrong type, which can lead to truncation.
673 If you want to disable the warning instead of fixing the code, please
674 make sure that truncation will not occur, or it might lead to unwanted
677 -Wtautological-undefined-compare and
678 -Wundefined-bool-conversion
680 These warn when C++ code is trying to compare 'this' against NULL, while
681 'this' should never be NULL in well-defined C++ code. However, there is
682 some legacy (pre C++11) code out there, which actively abuses this
683 feature, which was less strictly defined in previous C++ versions.
685 Squid and openjdk do this, for example. The warning can be turned off
686 for C++98 and earlier, but compiling the code in C++11 mode might result
687 in unexpected behavior; for example, the parts of the program that are
688 unreachable could be optimized away.
691 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
692 kernel sources have been removed. The .h files remain, since some
693 utilities include them. This will need to be fixed later.
694 If "mount -t oldnfs ..." is attempted, it will fail.
695 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
696 the utilities will report errors.
699 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
700 directories to top level SUBDIR variable when their parent
701 directory is included in LOCAL_DIRS. Users with build systems with
702 such hierarchies and without SUBDIR entries in the parent
703 directory Makefiles should add them or add the directories to
707 faith(4) and faithd(8) have been removed from the base system. Faith
708 has been obsolete for a very long time.
711 vt(4), the new console driver, is enabled by default. It brings
712 support for Unicode and double-width characters, as well as
713 support for UEFI and integration with the KMS kernel video
716 You may need to update your console settings in /etc/rc.conf,
717 most probably the keymap. During boot, /etc/rc.d/syscons will
718 indicate what you need to do.
720 vt(4) still has issues and lacks some features compared to
721 syscons(4). See the wiki for up-to-date information:
722 https://wiki.freebsd.org/Newcons
724 If you want to keep using syscons(4), you can do so by adding
725 the following line to /boot/loader.conf:
729 pjdfstest has been integrated into kyua as an opt-in test suite.
730 Please see share/doc/pjdfstest/README for more details on how to
734 gperf has been removed from the base system for architectures
735 that use clang. Ports that require gperf will obtain it from the
739 pjdfstest has been moved from tools/regression/pjdfstest to
743 At svn r271982, The default linux compat kernel ABI has been adjusted
744 to 2.6.18 in support of the linux-c6 compat ports infrastructure
745 update. If you wish to continue using the linux-f10 compat ports,
746 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
747 encouraged to update their linux-compat packages to linux-c6 during
748 their next update cycle.
751 The ofwfb driver, used to provide a graphics console on PowerPC when
752 using vt(4), no longer allows mmap() of all physical memory. This
753 will prevent Xorg on PowerPC with some ATI graphics cards from
754 initializing properly unless x11-servers/xorg-server is updated to
758 The xdev targets have been converted to using TARGET and
759 TARGET_ARCH instead of XDEV and XDEV_ARCH.
762 The default unbound configuration has been modified to address
763 issues with reverse lookups on networks that use private
764 address ranges. If you use the local_unbound service, run
765 "service local_unbound setup" as root to regenerate your
766 configuration, then "service local_unbound reload" to load the
770 The GNU texinfo and GNU info pages are not built and installed
771 anymore, WITH_INFO knob has been added to allow to built and install
773 UPDATE: see 20150102 entry on texinfo's removal
776 The GNU readline library is now an INTERNALLIB - that is, it is
777 statically linked into consumers (GDB and variants) in the base
778 system, and the shared library is no longer installed. The
779 devel/readline port is available for third party software that
783 The Itanium architecture (ia64) has been removed from the list of
784 known architectures. This is the first step in the removal of the
788 Commit r268115 has added NFSv4.1 server support, merged from
789 projects/nfsv4.1-server. Since this includes changes to the
790 internal interfaces between the NFS related modules, a full
791 build of the kernel and modules will be necessary.
792 __FreeBSD_version has been bumped.
795 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
796 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
797 which differs from the behaviour controlled by this knob.)
800 Maximal length of the serial number in CTL was increased from 16 to
801 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
802 and ctld, need to be rebuilt to work with a new kernel.
805 The libatf-c and libatf-c++ major versions were downgraded to 0 and
806 1 respectively to match the upstream numbers. They were out of
807 sync because, when they were originally added to FreeBSD, the
808 upstream versions were not respected. These libraries are private
809 and not yet built by default, so renumbering them should be a
810 non-issue. However, unclean source trees will yield broken test
811 programs once the operator executes "make delete-old-libs" after a
814 Additionally, the atf-sh binary was made private by moving it into
815 /usr/libexec/. Already-built shell test programs will keep the
816 path to the old binary so they will break after "make delete-old"
819 If you are using WITH_TESTS=yes (not the default), wipe the object
820 tree and rebuild from scratch to prevent spurious test failures.
821 This is only needed once: the misnumbered libraries and misplaced
822 binaries have been added to OptionalObsoleteFiles.inc so they will
823 be removed during a clean upgrade.
826 Clang and llvm have been upgraded to 3.4.1 release.
829 We bogusly installed src.opts.mk in /usr/share/mk. This file should
830 be removed to avoid issues in the future (and has been added to
834 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
835 past, it affected all builds that used the bsd.*.mk files. The old
836 behavior was a bug, but people may have relied upon it. To get this
837 behavior back, you can .include /etc/src.conf from /etc/make.conf
838 (which is still global and isn't changed). This also changes the
839 behavior of incremental builds inside the tree of individual
840 directories. Set MAKESYSPATH to ".../share/mk" to do that.
841 Although this has survived make universe and some upgrade scenarios,
842 other upgrade scenarios may have broken. At least one form of
843 temporary breakage was fixed with MAKESYSPATH settings for buildworld
844 as well... In cases where MAKESYSPATH isn't working with this
845 setting, you'll need to set it to the full path to your tree.
847 One side effect of all this cleaning up is that bsd.compiler.mk
848 is no longer implicitly included by bsd.own.mk. If you wish to
849 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
853 The lindev device has been removed since /dev/full has been made a
854 standard device. __FreeBSD_version has been bumped.
857 The knob WITHOUT_VI was added to the base system, which controls
858 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
859 in order to reorder files share/termcap and didn't build ex(1) as a
860 build tool, so building/installing with WITH_VI is highly advised for
861 build hosts for older releases.
863 This issue has been fixed in stable/9 and stable/10 in r277022 and
864 r276991, respectively.
867 The YES_HESIOD knob has been removed. It has been obsolete for
868 a decade. Please move to using WITH_HESIOD instead or your builds
869 will silently lack HESIOD.
872 The uart(4) driver has been changed with respect to its handling
873 of the low-level console. Previously the uart(4) driver prevented
874 any process from changing the baudrate or the CLOCAL and HUPCL
875 control flags. By removing the restrictions, operators can make
876 changes to the serial console port without having to reboot.
877 However, when getty(8) is started on the serial device that is
878 associated with the low-level console, a misconfigured terminal
879 line in /etc/ttys will now have a real impact.
880 Before upgrading the kernel, make sure that /etc/ttys has the
881 serial console device configured as 3wire without baudrate to
882 preserve the previous behaviour. E.g:
883 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
886 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
887 to improve performance. To re-enable it, if needed, run rpcbind
888 with command line option -W.
891 Switched back to the GPL dtc compiler due to updates in the upstream
892 dts files not being supported by the BSDL dtc compiler. You will need
893 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
894 may result while building dtb files during a kernel build if you fail
895 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
898 Clang and llvm have been upgraded to 3.4 release.
901 The nve(4) driver has been removed. Please use the nfe(4) driver
902 for NVIDIA nForce MCP Ethernet adapters instead.
905 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
906 This could cause certain C++ applications using shared libraries built
907 against the previous version of libc++ to crash. The incompatibility
908 has now been fixed, but any C++ applications or shared libraries built
909 between r261283 and r261801 should be recompiled.
912 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
913 capability mode support. Please note that enabling the feature in
914 kernel is still highly recommended.
917 OpenSSH is now built with sandbox support, and will use sandbox as
918 the default privilege separation method. This requires Capsicum
919 capability mode support in kernel.
922 The libelf and libdwarf libraries have been updated to newer
923 versions from upstream. Shared library version numbers for
924 these two libraries were bumped. Any ports or binaries
925 requiring these two libraries should be recompiled.
926 __FreeBSD_version is bumped to 1100006.
929 If a Makefile in a tests/ directory was auto-generating a Kyuafile
930 instead of providing an explicit one, this would prevent such
931 Makefile from providing its own Kyuafile in the future during
932 NO_CLEAN builds. This has been fixed in the Makefiles but manual
933 intervention is needed to clean an objdir if you use NO_CLEAN:
934 # find /usr/obj -name Kyuafile | xargs rm -f
937 The behavior of gss_pseudo_random() for the krb5 mechanism
938 has changed, for applications requesting a longer random string
939 than produced by the underlying enctype's pseudo-random() function.
940 In particular, the random string produced from a session key of
941 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
942 be different at the 17th octet and later, after this change.
943 The counter used in the PRF+ construction is now encoded as a
944 big-endian integer in accordance with RFC 4402.
945 __FreeBSD_version is bumped to 1100004.
948 The WITHOUT_ATF build knob has been removed and its functionality
949 has been subsumed into the more generic WITHOUT_TESTS. If you were
950 using the former to disable the build of the ATF libraries, you
951 should change your settings to use the latter.
954 The default version of mtree is nmtree which is obtained from
955 NetBSD. The output is generally the same, but may vary
956 slightly. If you found you need identical output adding
957 "-F freebsd9" to the command line should do the trick. For the
958 time being, the old mtree is available as fmtree.
961 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
962 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
963 1.1.4_8 and verify bsdyml not linked in, before running "make
965 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
967 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
970 The stable/10 branch has been created in subversion from head
974 The rc.d/jail script has been updated to support jail(8)
975 configuration file. The "jail_<jname>_*" rc.conf(5) variables
976 for per-jail configuration are automatically converted to
977 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
978 This is transparently backward compatible. See below about some
979 incompatibilities and rc.conf(5) manual page for more details.
981 These variables are now deprecated in favor of jail(8) configuration
982 file. One can use "rc.d/jail config <jname>" command to generate
983 a jail(8) configuration file in /var/run/jail.<jname>.conf without
984 running the jail(8) utility. The default pathname of the
985 configuration file is /etc/jail.conf and can be specified by
986 using $jail_conf or $jail_<jname>_conf variables.
988 Please note that jail_devfs_ruleset accepts an integer at
989 this moment. Please consider to rewrite the ruleset name
993 BIND has been removed from the base system. If all you need
994 is a local resolver, simply enable and start the local_unbound
995 service instead. Otherwise, several versions of BIND are
996 available in the ports tree. The dns/bind99 port is one example.
998 With this change, nslookup(1) and dig(1) are no longer in the base
999 system. Users should instead use host(1) and drill(1) which are
1000 in the base system. Alternatively, nslookup and dig can
1001 be obtained by installing the dns/bind-tools port.
1004 With the addition of unbound(8), a new unbound user is now
1005 required during installworld. "mergemaster -p" can be used to
1006 add the user prior to installworld, as documented in the handbook.
1009 OpenSSH is now built with DNSSEC support, and will by default
1010 silently trust signed SSHFP records. This can be controlled with
1011 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1012 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1015 The GNU Compiler Collection and C++ standard library (libstdc++)
1016 are no longer built by default on platforms where clang is the system
1017 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1018 options in src.conf.
1021 The PROCDESC kernel option is now part of the GENERIC kernel
1022 configuration and is required for the rwhod(8) to work.
1023 If you are using custom kernel configuration, you should include
1027 The API and ABI related to the Capsicum framework was modified
1028 in backward incompatible way. The userland libraries and programs
1029 have to be recompiled to work with the new kernel. This includes the
1030 following libraries and programs, but the whole buildworld is
1031 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1032 kdump, procstat, rwho, rwhod, uniq.
1035 AES-NI intrinsic support has been added to gcc. The AES-NI module
1036 has been updated to use this support. A new gcc is required to build
1037 the aesni module on both i386 and amd64.
1040 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1041 Thus "device padlock_rng" and "device rdrand_rng" should be
1042 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1045 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1046 enables just the iconv* functionality and is now on by default.
1047 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1048 compatibility. Set WITHOUT_ICONV to build the old way.
1049 If you have been using WITH_ICONV before, you will very likely
1050 need to turn on WITH_LIBICONV_COMPAT.
1053 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1054 Illumos origin, including ZFS. If you have INVARIANTS in your
1055 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1057 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1058 locks if WITNESS option was set. Because that generated a lot of
1059 witness(9) reports and all of them were believed to be false
1060 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1061 can be used to achieve the previous behavior.
1064 Timer values in IPv6 data structures now use time_uptime instead
1065 of time_second. Although this is not a user-visible functional
1066 change, userland utilities which directly use them---ndp(8),
1067 rtadvd(8), and rtsold(8) in the base system---need to be updated
1068 to r253970 or later.
1071 find -delete can now delete the pathnames given as arguments,
1072 instead of only files found below them or if the pathname did
1073 not contain any slashes. Formerly, the following error message
1076 find: -delete: <path>: relative path potentially not safe
1078 Deleting the pathnames given as arguments can be prevented
1079 without error messages using -mindepth 1 or by changing
1080 directory and passing "." as argument to find. This works in the
1081 old as well as the new version of find.
1084 Behavior of devfs rules path matching has been changed.
1085 Pattern is now always matched against fully qualified devfs
1086 path and slash characters must be explicitly matched by
1087 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1088 subdirectories must be reviewed.
1091 The default ARM ABI has changed to the ARM EABI. The old ABI is
1092 incompatible with the ARM EABI and all programs and modules will
1093 need to be rebuilt to work with a new kernel.
1095 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1097 NOTE: Support for the old ABI will be removed in the future and
1098 users are advised to upgrade.
1101 pkg_install has been disconnected from the build if you really need it
1102 you should add WITH_PKGTOOLS in your src.conf(5).
1105 Most of network statistics structures were changed to be able
1106 keep 64-bits counters. Thus all tools, that work with networking
1107 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1110 Fix a bug that allowed a tracing process (e.g. gdb) to write
1111 to a memory-mapped file in the traced process's address space
1112 even if neither the traced process nor the tracing process had
1113 write access to that file.
1116 CVS has been removed from the base system. An exact copy
1117 of the code is available from the devel/cvs port.
1120 Some people report the following error after the switch to bmake:
1122 make: illegal option -- J
1123 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1125 *** [buildworld] Error code 2
1127 this likely due to an old instance of make in
1128 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1129 which src/Makefile will use that blindly, if it exists, so if
1130 you see the above error:
1132 rm -rf `make -V MAKEPATH`
1137 Use bmake by default.
1138 Whereas before one could choose to build with bmake via
1139 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1140 make. The goal is to remove these knobs for 10-RELEASE.
1142 It is worth noting that bmake (like gmake) treats the command
1143 line as the unit of failure, rather than statements within the
1144 command line. Thus '(cd some/where && dosomething)' is safer
1145 than 'cd some/where; dosomething'. The '()' allows consistent
1146 behavior in parallel build.
1149 Fix a bug that allows NFS clients to issue READDIR on files.
1152 The WITHOUT_IDEA option has been removed because
1153 the IDEA patent expired.
1156 The sysctl which controls TRIM support under ZFS has been renamed
1157 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1161 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1162 rather than creating it's own in the temporary directory in
1163 order allow access to bootstrapped versions of tools such as
1164 install and mtree. When upgrading from version of FreeBSD where
1165 the install command does not support -l, you will need to
1166 install a new mergemaster command if mergemaster -p is required.
1167 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1171 Legacy ATA stack, disabled and replaced by new CAM-based one since
1172 FreeBSD 9.0, completely removed from the sources. Kernel modules
1173 atadisk and atapi*, user-level tools atacontrol and burncd are
1174 removed. Kernel option `options ATA_CAM` is now permanently enabled
1178 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1179 and socketpair(2). Software, in particular Kerberos, may
1180 automatically detect and use these during building. The resulting
1181 binaries will not work on older kernels.
1184 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1185 information, see the respective 20130304 entry).
1188 Recent commits to callout(9) changed the size of struct callout,
1189 so the KBI is probably heavily disturbed. Also, some functions
1190 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1191 by macros. Every kernel module using it won't load, so rebuild
1194 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1195 but does not initialize by default (because of the new CTL_DISABLE
1196 option) to save memory. To re-enable it, remove the CTL_DISABLE
1197 option from the kernel config file or set kern.cam.ctl.disable=0
1198 in /boot/loader.conf.
1201 The ctl device has been disabled in GENERIC for i386 and amd64.
1202 This was done due to the extra memory being allocated at system
1203 initialisation time by the ctl driver which was only used if
1204 a CAM target device was created. This makes a FreeBSD system
1205 unusable on 128MB or less of RAM.
1208 A new compression method (lz4) has been merged to -HEAD. Please
1209 refer to zpool-features(7) for more information.
1211 Please refer to the "ZFS notes" section of this file for information
1212 on upgrading boot ZFS pools.
1215 A BSD-licensed patch(1) variant has been added and is installed
1216 as bsdpatch, being the GNU version the default patch.
1217 To inverse the logic and use the BSD-licensed one as default,
1218 while having the GNU version installed as gnupatch, rebuild
1219 and install world with the WITH_BSD_PATCH knob set.
1222 Due to the use of the new -l option to install(1) during build
1223 and install, you must take care not to directly set the INSTALL
1224 make variable in your /etc/make.conf, /etc/src.conf, or on the
1225 command line. If you wish to use the -C flag for all installs
1226 you may be able to add INSTALL+=-C to /etc/make.conf or
1230 The install(1) option -M has changed meaning and now takes an
1231 argument that is a file or path to append logs to. In the
1232 unlikely event that -M was the last option on the command line
1233 and the command line contained at least two files and a target
1234 directory the first file will have logs appended to it. The -M
1235 option served little practical purpose in the last decade so its
1236 use is expected to be extremely rare.
1239 After switching to Clang as the default compiler some users of ZFS
1240 on i386 systems started to experience stack overflow kernel panics.
1241 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1244 GEOM_LABEL now mangles label names read from file system metadata.
1245 Mangling affect labels containing spaces, non-printable characters,
1246 '%' or '"'. Device names in /etc/fstab and other places may need to
1250 By default, only the 10 most recent kernel dumps will be saved. To
1251 restore the previous behaviour (no limit on the number of kernel dumps
1252 stored in the dump directory) add the following line to /etc/rc.conf:
1257 With the addition of auditdistd(8), a new auditdistd user is now
1258 required during installworld. "mergemaster -p" can be used to
1259 add the user prior to installworld, as documented in the handbook.
1262 The sin6_scope_id member variable in struct sockaddr_in6 is now
1263 filled by the kernel before passing the structure to the userland via
1264 sysctl or routing socket. This means the KAME-specific embedded scope
1265 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1266 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1267 __FreeBSD_version is bumped to 1000025.
1270 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1271 This means that the world and kernel will be compiled with clang
1272 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1273 and /usr/bin/cpp. To disable this behavior and revert to building
1274 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1275 of current may need to bootstrap WITHOUT_CLANG first if the clang
1276 build fails (its compatibility window doesn't extend to the 9 stable
1280 The IPFIREWALL_FORWARD kernel option has been removed. Its
1281 functionality now turned on by default.
1284 The ZERO_COPY_SOCKET kernel option has been removed and
1285 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1286 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1287 mechanism which is not safe and may result in kernel crashes.
1288 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1289 driver supports disposeable external page sized mbuf storage.
1290 Proper replacements for both zero-copy mechanisms are under
1291 consideration and will eventually lead to complete removal
1292 of the two kernel options.
1295 The IPv4 network stack has been converted to network byte
1296 order. The following modules need to be recompiled together
1297 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1298 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1301 Support for non-MPSAFE filesystems was removed from VFS. The
1302 VFS_VERSION was bumped, all filesystem modules shall be
1306 All the non-MPSAFE filesystems have been disconnected from
1307 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1308 portalfs, smbfs, xfs.
1311 The interface cloning API and ABI has changed. The following
1312 modules need to be recompiled together with kernel:
1313 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1314 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1315 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1318 The sdhci driver was split in two parts: sdhci (generic SD Host
1319 Controller logic) and sdhci_pci (actual hardware driver).
1320 No kernel config modifications are required, but if you
1321 load sdhc as a module you must switch to sdhci_pci instead.
1324 Import the FUSE kernel and userland support into base system.
1327 The GNU sort(1) program has been removed since the BSD-licensed
1328 sort(1) has been the default for quite some time and no serious
1329 problems have been reported. The corresponding WITH_GNU_SORT
1333 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1334 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1338 The net80211(4) ABI has been changed to allow for improved driver
1339 PS-POLL and power-save support. All wireless drivers need to be
1340 recompiled to work with the new kernel.
1343 The random(4) support for the VIA hardware random number
1344 generator (`PADLOCK') is no longer enabled unconditionally.
1345 Add the padlock_rng device in the custom kernel config if
1346 needed. The GENERIC kernels on i386 and amd64 do include the
1347 device, so the change only affects the custom kernel
1351 The pf(4) packet filter ABI has been changed. pfctl(8) and
1352 snmp_pf module need to be recompiled to work with new kernel.
1355 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1356 to -HEAD. Pools that have empty_bpobj in active state can not be
1357 imported read-write with ZFS implementations that do not support
1358 this feature. For more information read the zpool-features(5)
1362 The sparc64 ZFS loader has been changed to no longer try to auto-
1363 detect ZFS providers based on diskN aliases but now requires these
1364 to be explicitly listed in the OFW boot-device environment variable.
1367 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1368 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1369 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1372 The following sysctls and tunables have been renamed for consistency
1373 with other variables:
1374 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1375 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1378 The sort utility has been replaced with BSD sort. For now, GNU sort
1379 is also available as "gnusort" or the default can be set back to
1380 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1381 installed as "bsdsort".
1384 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1385 Starting with this version the old system of ZFS pool versioning
1386 is superseded by "feature flags". This concept enables forward
1387 compatibility against certain future changes in functionality of ZFS
1388 pools. The first read-only compatible "feature flag" for ZFS pools
1389 is named "com.delphix:async_destroy". For more information
1390 read the new zpool-features(5) manual page.
1391 Please refer to the "ZFS notes" section of this file for information
1392 on upgrading boot ZFS pools.
1395 The malloc(3) implementation embedded in libc now uses sources imported
1396 as contrib/jemalloc. The most disruptive API change is to
1397 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1398 delete it prior to installworld, and optionally re-create it using the
1399 new format after rebooting. See malloc.conf(5) for details
1400 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1404 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1405 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1406 now spelled mips. This is to aid compatibility with third-party
1407 software that expects this naming scheme in uname(3). Little-endian
1408 settings are unchanged. If you are updating a big-endian mips64 machine
1409 from before this change, you may need to set MACHINE_ARCH=mips64 in
1410 your environment before the new build system will recognize your machine.
1413 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1417 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1418 nullfs(5) did not pass through all behaviours to the underlying layer,
1419 as a result if we bound to a socket on the lower layer we could connect
1420 only to the lower path; if we bound to the upper layer we could connect
1421 only to the upper path. The new behavior is one can connect to both the
1422 lower and the upper paths regardless what layer path one binds to.
1425 The getifaddrs upgrade path broken with 20111215 has been restored.
1426 If you have upgraded in between 20111215 and 20120209 you need to
1427 recompile libc again with your kernel. You still need to recompile
1428 world to be able to configure CARP but this restriction already
1429 comes from 20111215.
1432 The set_rcvar() function has been removed from /etc/rc.subr. All
1433 base and ports rc.d scripts have been updated, so if you have a
1434 port installed with a script in /usr/local/etc/rc.d you can either
1435 hand-edit the rcvar= line, or reinstall the port.
1437 An easy way to handle the mass-update of /etc/rc.d:
1438 rm /etc/rc.d/* && mergemaster -i
1441 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1442 on the current CPU and prevents other threads from running.
1443 This behavior can be reverted using the kern.stop_scheduler_on_panic
1445 The new behavior can be incompatible with kern.sync_on_panic.
1448 The carp(4) facility has been changed significantly. Configuration
1449 of the CARP protocol via ifconfig(8) has changed, as well as format
1450 of CARP events submitted to devd(8) has changed. See manual pages
1451 for more information. The arpbalance feature of carp(4) is currently
1452 not supported anymore.
1454 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1455 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1456 need to be recompiled.
1459 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1463 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1464 explicitely support non-MPSAFE filesystems.
1465 It is on by default for all supported platform at this present
1469 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1470 i386 and pc98 GENERIC kernel configuration files.
1473 sysinstall has been removed
1476 The stable/9 branch created in subversion. This corresponds to the
1477 RELENG_9 branch in CVS.
1483 Avoid using make -j when upgrading. While generally safe, there are
1484 sometimes problems using -j to upgrade. If your upgrade fails with
1485 -j, please try again without -j. From time to time in the past there
1486 have been problems using -j with buildworld and/or installworld. This
1487 is especially true when upgrading between "distant" versions (eg one
1488 that cross a major release boundary or several minor releases, or when
1489 several months have passed on the -current branch).
1491 Sometimes, obscure build problems are the result of environment
1492 poisoning. This can happen because the make utility reads its
1493 environment when searching for values for global variables. To run
1494 your build attempts in an "environmental clean room", prefix all make
1495 commands with 'env -i '. See the env(1) manual page for more details.
1497 When upgrading from one major version to another it is generally best
1498 to upgrade to the latest code in the currently installed branch first,
1499 then do an upgrade to the new branch. This is the best-tested upgrade
1500 path, and has the highest probability of being successful. Please try
1501 this approach before reporting problems with a major version upgrade.
1503 When upgrading a live system, having a root shell around before
1504 installing anything can help undo problems. Not having a root shell
1505 around can lead to problems if pam has changed too much from your
1506 starting point to allow continued authentication after the upgrade.
1508 This file should be read as a log of events. When a later event changes
1509 information of a prior event, the prior event should not be deleted.
1510 Instead, a pointer to the entry with the new information should be
1511 placed in the old entry. Readers of this file should also sanity check
1512 older entries before relying on them blindly. Authors of new entries
1513 should write them with this in mind.
1517 When upgrading the boot ZFS pool to a new version, always follow
1520 1.) recompile and reinstall the ZFS boot loader and boot block
1521 (this is part of "make buildworld" and "make installworld")
1523 2.) update the ZFS boot block on your boot drive
1525 The following example updates the ZFS boot block on the first
1526 partition (freebsd-boot) of a GPT partitioned drive ada0:
1527 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1529 Non-boot pools do not need these updates.
1533 If you are updating from a prior version of FreeBSD (even one just
1534 a few days old), you should follow this procedure. It is the most
1535 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1537 make kernel-toolchain
1538 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1539 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1541 To test a kernel once
1542 ---------------------
1543 If you just want to boot a kernel once (because you are not sure
1544 if it works, or if you want to boot a known bad kernel to provide
1545 debugging information) run
1546 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1547 nextboot -k testkernel
1549 To just build a kernel when you know that it won't mess you up
1550 --------------------------------------------------------------
1551 This assumes you are already running a CURRENT system. Replace
1552 ${arch} with the architecture of your machine (e.g. "i386",
1553 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1555 cd src/sys/${arch}/conf
1556 config KERNEL_NAME_HERE
1557 cd ../compile/KERNEL_NAME_HERE
1562 If this fails, go to the "To build a kernel" section.
1564 To rebuild everything and install it on the current system.
1565 -----------------------------------------------------------
1566 # Note: sometimes if you are running current you gotta do more than
1567 # is listed here if you are upgrading from a really old current.
1569 <make sure you have good level 0 dumps>
1571 make kernel KERNCONF=YOUR_KERNEL_HERE
1573 <reboot in single user> [3]
1580 To cross-install current onto a separate partition
1581 --------------------------------------------------
1582 # In this approach we use a separate partition to hold
1583 # current's root, 'usr', and 'var' directories. A partition
1584 # holding "/", "/usr" and "/var" should be about 2GB in
1587 <make sure you have good level 0 dumps>
1590 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1591 <maybe newfs current's root partition>
1592 <mount current's root partition on directory ${CURRENT_ROOT}>
1593 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1594 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1595 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1596 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1597 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1598 <reboot into current>
1599 <do a "native" rebuild/install as described in the previous section>
1600 <maybe install compatibility libraries from ports/misc/compat*>
1604 To upgrade in-place from stable to current
1605 ----------------------------------------------
1606 <make sure you have good level 0 dumps>
1608 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1610 <reboot in single user> [3]
1617 Make sure that you've read the UPDATING file to understand the
1618 tweaks to various things you need. At this point in the life
1619 cycle of current, things change often and you are on your own
1620 to cope. The defaults can also change, so please read ALL of
1621 the UPDATING entries.
1623 Also, if you are tracking -current, you must be subscribed to
1624 freebsd-current@freebsd.org. Make sure that before you update
1625 your sources that you have read and understood all the recent
1626 messages there. If in doubt, please track -stable which has
1627 much fewer pitfalls.
1629 [1] If you have third party modules, such as vmware, you
1630 should disable them at this point so they don't crash your
1633 [3] From the bootblocks, boot -s, and then do
1638 adjkerntz -i # if CMOS is wall time
1639 Also, when doing a major release upgrade, it is required that
1640 you boot into single user mode to do the installworld.
1642 [4] Note: This step is non-optional. Failure to do this step
1643 can result in a significant reduction in the functionality of the
1644 system. Attempting to do it by hand is not recommended and those
1645 that pursue this avenue should read this file carefully, as well
1646 as the archives of freebsd-current and freebsd-hackers mailing lists
1647 for potential gotchas. The -U option is also useful to consider.
1648 See mergemaster(8) for more information.
1650 [5] Usually this step is a noop. However, from time to time
1651 you may need to do this if you get unknown user in the following
1652 step. It never hurts to do it all the time. You may need to
1653 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1654 install) after the buildworld before this step if you last updated
1655 from current before 20130425 or from -stable before 20130430.
1657 [6] This only deletes old files and directories. Old libraries
1658 can be deleted by "make delete-old-libs", but you have to make
1659 sure that no program is using those libraries anymore.
1661 [8] In order to have a kernel that can run the 4.x binaries needed to
1662 do an installworld, you must include the COMPAT_FREEBSD4 option in
1663 your kernel. Failure to do so may leave you with a system that is
1664 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1665 required to run the 5.x binaries on more recent kernels. And so on
1666 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1668 Make sure that you merge any new devices from GENERIC since the
1669 last time you updated your kernel config file.
1671 [9] When checking out sources, you must include the -P flag to have
1672 cvs prune empty directories.
1674 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1675 "?=" instead of the "=" assignment operator, so that buildworld can
1676 override the CPUTYPE if it needs to.
1678 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1679 not on the command line, or in /etc/make.conf. buildworld will
1680 warn if it is improperly defined.
1683 This file contains a list, in reverse chronological order, of major
1684 breakages in tracking -current. It is not guaranteed to be a complete
1685 list of such breakages, and only contains entries since September 23, 2011.
1686 If you need to see UPDATING entries from before that date, you will need
1687 to fetch an UPDATING file from an older FreeBSD release.
1689 Copyright information:
1691 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1693 Redistribution, publication, translation and use, with or without
1694 modification, in full or in part, in any form or format of this
1695 document are permitted without further permission from the author.
1697 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1698 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1699 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1700 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1701 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1702 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1703 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1704 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1705 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1706 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1707 POSSIBILITY OF SUCH DAMAGE.
1709 Contact Warner Losh if you have any questions about your use of