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.
20 arm64 builds now use the base system LLD 4.0.0 linker by default,
21 instead of requiring that the aarch64-binutils port or package be
22 installed. To continue using aarch64-binutils, set
23 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
26 The ctl.ko module no longer implements the iSCSI target frontend:
27 cfiscsi.ko does instead.
29 If building cfiscsi.ko as a kernel module, the module can be loaded
30 via one of the following methods:
31 - `cfiscsi_load="YES"` in loader.conf(5).
32 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
33 - ctladm(8)/ctld(8), when compiled with iSCSI support
34 (`WITH_ISCSI=yes` in src.conf(5))
36 Please see cfiscsi(4) for more details.
39 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
40 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
41 same source (previously, the dependency of mmcsd.ko on mmc.ko was
42 missing, but mmcsd.ko now will refuse to load if it is incompatible
46 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
47 use any explicitly assigned loopback address available in the jail
48 instead of using the first assigned address of the jail.
51 As of r316810 for ipfilter, keep frags is no longer assumed when
52 keep state is specified in a rule. r316810 aligns ipfilter with
53 documentation in man pages separating keep frags from keep state.
54 This allows keep state to specified without forcing keep frags
55 and allows keep frags to be specified independently of keep state.
56 To maintain previous behaviour, also specify keep frags with
57 keep state (as documented in ipf.conf.5).
60 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
61 Please see the 20141231 entry below for information about prerequisites
62 and upgrading, if you are not already using clang 3.5.0 or higher.
65 The code that provides support for ZFS .zfs/ directory functionality
66 has been reimplemented. It's not possible now to create a snapshot
67 by mkdir under .zfs/snapshot/. That should be the only user visible
71 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
72 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
73 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
74 and now NAT-T is supported by default. Security associations now use
75 the single namespace for SPI allocation, so if you use several manually
76 configured security associations with the same SPI, this configuration
80 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
81 Please see the 20141231 entry below for information about prerequisites
82 and upgrading, if you are not already using clang 3.5.0 or higher.
85 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
86 Please see the 20141231 entry below for information about prerequisites
87 and upgrading, if you are not already using clang 3.5.0 or higher.
90 The layout of the pmap structure has changed for powerpc to put the pmap
91 statistics at the front for all CPU variations. libkvm(3) and all tools
92 that link against it need to be recompiled.
95 isl(4) and cyapa(4) drivers now require a new driver,
96 chromebook_platform(4), to work properly on Chromebook-class hardware.
97 On other types of hardware the drivers may need to be configured using
98 device hints. Please see the corresponding manual pages for details.
101 Relocatable object files with the extension of .So have been renamed
102 to use an extension of .pico instead. The purpose of this change is
103 to avoid a name clash with shared libraries on case-insensitive file
104 systems. On those file systems, foo.So is the same file as foo.so.
107 The libc stub for the pipe(2) system call has been replaced with
108 a wrapper that calls the pipe2(2) system call and the pipe(2)
109 system call is now only implemented by the kernels that include
110 "options COMPAT_FREEBSD10" in their config file (this is the
111 default). Users should ensure that this option is enabled in
112 their kernel or upgrade userspace to r302092 before upgrading their
116 CAM will now strip leading spaces from SCSI disks' serial numbers.
117 This will effect users who create UFS filesystems on SCSI disks using
118 those disk's diskid device nodes. For example, if /etc/fstab
119 previously contained a line like
120 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
121 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
122 transforms like gmirror may also be affected. ZFS users should
126 The bitstring(3) API has been updated with new functionality and
127 improved performance. But it is binary-incompatible with the old API.
128 Objects built with the new headers may not be linked against objects
129 built with the old headers.
132 The brk and sbrk functions have been removed from libc on arm64.
133 Binutils from ports has been updated to not link to these
134 functions and should be updated to the latest version before
135 installing a new libc.
138 The armv6 port now defaults to hard float ABI. Limited support
139 for running both hardfloat and soft float on the same system
140 is available using the libraries installed with -DWITH_LIBSOFT.
141 This has only been tested as an upgrade path for installworld
142 and packages may fail or need manual intervention to run. New
143 packages will be needed.
145 To update an existing self-hosted armv6hf system, you must add
146 TARGET_ARCH=armv6 on the make command line for both the build
147 and the install steps.
150 Kernel modules compiled outside of a kernel build now default to
151 installing to /boot/modules instead of /boot/kernel. Many kernel
152 modules built this way (such as those in ports) already overrode
153 KMODDIR explicitly to install into /boot/modules. However,
154 manually building and installing a module from /sys/modules will
155 now install to /boot/modules instead of /boot/kernel.
158 The CAM I/O scheduler has been committed to the kernel. There should be
159 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
160 list of known rogues that claim support for this but actually corrupt
161 data is believed to be complete, be on the lookout for data
162 corruption. The known rogue list is believed to be complete:
164 o Crucial MX100, M550 drives with MU01 firmware.
165 o Micron M510 and M550 drives with MU01 firmware.
166 o Micron M500 prior to MU07 firmware
167 o Samsung 830, 840, and 850 all firmwares
168 o FCCT M500 all firmwares
170 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
171 with working NCQ TRIM. For Micron branded drives, see your sales rep for
172 updated firmware. Black listed drives will work correctly because these
173 drives work correctly so long as no NCQ TRIMs are sent to them. Given
174 this list is the same as found in Linux, it's believed there are no
175 other rogues in the market place. All other models from the above
178 To be safe, if you are at all concerned, you can quirk each of your
179 drives to prevent NCQ from being sent by setting:
180 kern.cam.ada.X.quirks="0x2"
181 in loader.conf. If the drive requires the 4k sector quirk, set the
185 The FAST_DEPEND build option has been removed and its functionality is
186 now the one true way. The old mkdep(1) style of 'make depend' has
187 been removed. See 20160311 for further details.
190 Resource range types have grown from unsigned long to uintmax_t. All
191 drivers, and anything using libdevinfo, need to be recompiled.
194 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
195 builds. It no longer runs mkdep(1) during 'make depend', and the
196 'make depend' stage can safely be skipped now as it is auto ran
197 when building 'make all' and will generate all SRCS and DPSRCS before
198 building anything else. Dependencies are gathered at compile time with
199 -MF flags kept in separate .depend files per object file. Users should
200 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
204 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
205 kernel modules. Therefore, if you load any kernel modules at boot time,
206 please install the boot loaders after you install the kernel, but before
210 make kernel KERNCONF=YOUR_KERNEL_HERE
211 make -C sys/boot install
212 <reboot in single user>
214 Then follow the usual steps, described in the General Notes section,
218 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
219 see the 20141231 entry below for information about prerequisites and
220 upgrading, if you are not already using clang 3.5.0 or higher.
223 The AIO subsystem is now a standard part of the kernel. The
224 VFS_AIO kernel option and aio.ko kernel module have been removed.
225 Due to stability concerns, asynchronous I/O requests are only
226 permitted on sockets and raw disks by default. To enable
227 asynchronous I/O requests on all file types, set the
228 vfs.aio.enable_unsafe sysctl to a non-zero value.
231 The ELF object manipulation tool objcopy is now provided by the
232 ELF Tool Chain project rather than by GNU binutils. It should be a
233 drop-in replacement, with the addition of arm64 support. The
234 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
235 to obtain the GNU version if necessary.
238 Building ZFS pools on top of zvols is prohibited by default. That
239 feature has never worked safely; it's always been prone to deadlocks.
240 Using a zvol as the backing store for a VM guest's virtual disk will
241 still work, even if the guest is using ZFS. Legacy behavior can be
242 restored by setting vfs.zfs.vol.recursive=1.
245 The NONE and HPN patches has been removed from OpenSSH. They are
246 still available in the security/openssh-portable port.
249 With the addition of ypldap(8), a new _ypldap user is now required
250 during installworld. "mergemaster -p" can be used to add the user
251 prior to installworld, as documented in the handbook.
254 The tftp loader (pxeboot) now uses the option root-path directive. As a
255 consequence it no longer looks for a pxeboot.4th file on the tftp
256 server. Instead it uses the regular /boot infrastructure as with the
260 The code to start recording plug and play data into the modules has
261 been committed. While the old tools will properly build a new kernel,
262 a number of warnings about "unknown metadata record 4" will be produced
263 for an older kldxref. To avoid such warnings, make sure to rebuild
264 the kernel toolchain (or world). Make sure that you have r292078 or
265 later when trying to build 292077 or later before rebuilding.
268 Debug data files are now built by default with 'make buildworld' and
269 installed with 'make installworld'. This facilitates debugging but
270 requires more disk space both during the build and for the installed
271 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
275 r291527 changed the internal interface between the nfsd.ko and
276 nfscommon.ko modules. As such, they must both be upgraded to-gether.
277 __FreeBSD_version has been bumped because of this.
280 Add support for unicode collation strings leads to a change of
281 order of files listed by ls(1) for example. To get back to the old
282 behaviour, set LC_COLLATE environment variable to "C".
284 Databases administrators will need to reindex their databases given
285 collation results will be different.
287 Due to a bug in install(1) it is recommended to remove the ancient
288 locales before running make installworld.
290 rm -rf /usr/share/locale/*
293 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
294 libcrypto.so.7 or libssl.so.7 must be recompiled.
297 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
298 Kernel modules isp_2400_multi and isp_2500_multi were removed and
299 should be replaced with isp_2400 and isp_2500 modules respectively.
302 The build previously allowed using 'make -n' to not recurse into
303 sub-directories while showing what commands would be executed, and
304 'make -n -n' to recursively show commands. Now 'make -n' will recurse
305 and 'make -N' will not.
308 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
309 and etcupdate will now use this file. A custom sendmail.cf is now
310 updated via this mechanism rather than via installworld. If you had
311 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
312 want to remove the exclusion or change it to "always install".
313 /etc/mail/sendmail.cf is now managed the same way regardless of
314 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
315 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
318 Compatibility shims for legacy ATA device names have been removed.
319 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
320 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
321 environment variables, /dev/ad* and /dev/ar* symbolic links.
324 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
325 Please see the 20141231 entry below for information about prerequisites
326 and upgrading, if you are not already using clang 3.5.0 or higher.
329 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
330 and renamed from .symbols to .debug. This reduces the size requirements
331 on the boot partition or file system and provides consistency with
332 userland debug files.
334 When using the supported kernel installation method the
335 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
336 as is done with /boot/kernel.
338 Developers wishing to maintain the historical behavior of installing
339 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
342 The wireless drivers had undergone changes that remove the 'parent
343 interface' from the ifconfig -l output. The rc.d network scripts
344 used to check presence of a parent interface in the list, so old
345 scripts would fail to start wireless networking. Thus, etcupdate(3)
346 or mergemaster(8) run is required after kernel update, to update your
347 rc.d scripts in /etc.
350 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
351 These configurations are now automatically interpreted as
352 'scrub fragment reassemble'.
355 Kernel-loadable modules for the random(4) device are back. To use
356 them, the kernel must have
359 options RANDOM_LOADABLE
361 kldload(8) can then be used to load random_fortuna.ko
362 or random_yarrow.ko. Please note that due to the indirect
363 function calls that the loadable modules need to provide,
364 the build-in variants will be slightly more efficient.
366 The random(4) kernel option RANDOM_DUMMY has been retired due to
367 unpopularity. It was not all that useful anyway.
370 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
371 Control over building the ELF Tool Chain tools is now provided by
372 the WITHOUT_TOOLCHAIN knob.
375 The polarity of Pulse Per Second (PPS) capture events with the
376 uart(4) driver has been corrected. Prior to this change the PPS
377 "assert" event corresponded to the trailing edge of a positive PPS
378 pulse and the "clear" event was the leading edge of the next pulse.
380 As the width of a PPS pulse in a typical GPS receiver is on the
381 order of 1 millisecond, most users will not notice any significant
382 difference with this change.
384 Anyone who has compensated for the historical polarity reversal by
385 configuring a negative offset equal to the pulse width will need to
386 remove that workaround.
389 The default group assigned to /dev/dri entries has been changed
390 from 'wheel' to 'video' with the id of '44'. If you want to have
391 access to the dri devices please add yourself to the video group
394 # pw groupmod video -m $USER
397 The menu.rc and loader.rc files will now be replaced during
398 upgrades. Please migrate local changes to menu.rc.local and
399 loader.rc.local instead.
402 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
403 strings and strip have been removed. The src.conf(5) knob
404 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
407 As ZFS requires more kernel stack pages than is the default on some
408 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
409 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
411 Please consider using 'options KSTACK_PAGES=X' where X is greater
412 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
415 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
416 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
417 default, i.e., they will not contain "::". For example, instead
418 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
419 to have a more specific match, such as different map entries for
420 IPv6:0:0 vs IPv6:0. This change requires that configuration
421 data (including maps, files, classes, custom ruleset, etc.) must
422 use the same format, so make certain such configuration data is
423 upgrading. As a very simple check search for patterns like
424 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
425 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
426 the cf option UseCompressedIPv6Addresses.
429 The default kernel entropy-processing algorithm is now
430 Fortuna, replacing Yarrow.
432 Assuming you have 'device random' in your kernel config
433 file, the configurations allow a kernel option to override
434 this default. You may choose *ONE* of:
436 options RANDOM_YARROW # Legacy /dev/random algorithm.
437 options RANDOM_DUMMY # Blocking-only driver.
439 If you have neither, you get Fortuna. For most people,
440 read no further, Fortuna will give a /dev/random that works
441 like it always used to, and the difference will be irrelevant.
443 If you remove 'device random', you get *NO* kernel-processed
444 entropy at all. This may be acceptable to folks building
445 embedded systems, but has complications. Carry on reading,
446 and it is assumed you know what you need.
448 *PLEASE* read random(4) and random(9) if you are in the
449 habit of tweaking kernel configs, and/or if you are a member
450 of the embedded community, wanting specific and not-usual
451 behaviour from your security subsystems.
453 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
454 random', you will NOT have a functioning /dev/random, and
455 many cryptographic features will not work, including SSH.
456 You may also find strange behaviour from the random(3) set
457 of library functions, in particular sranddev(3), srandomdev(3)
458 and arc4random(3). The reason for this is that the KERN_ARND
459 sysctl only returns entropy if it thinks it has some to
460 share, and with RANDOM_DUMMY or no 'device random' this
464 An additional fix for the issue described in the 20150614 sendmail
465 entry below has been been committed in revision 284717.
468 FreeBSD's old make (fmake) has been removed from the system. It is
469 available as the devel/fmake port or via pkg install fmake.
472 The fix for the issue described in the 20150614 sendmail entry
473 below has been been committed in revision 284436. The work
474 around described in that entry is no longer needed unless the
475 default setting is overridden by a confDH_PARAMETERS configuration
476 setting of '5' or pointing to a 512 bit DH parameter file.
479 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
480 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
481 and devel/kyua to version 0.20+ and adjust any calling code to work
482 with Kyuafile and kyua.
485 The import of openssl to address the FreeBSD-SA-15:10.openssl
486 security advisory includes a change which rejects handshakes
487 with DH parameters below 768 bits. sendmail releases prior
488 to 8.15.2 (not yet released), defaulted to a 512 bit
489 DH parameter setting for client connections. To work around
490 this interoperability, sendmail can be configured to use a
491 2048 bit DH parameter by:
493 1. Edit /etc/mail/`hostname`.mc
494 2. If a setting for confDH_PARAMETERS does not exist or
495 exists and is set to a string beginning with '5',
497 3. If a setting for confDH_PARAMETERS exists and is set to
498 a file path, create a new file with:
499 openssl dhparam -out /path/to/file 2048
500 4. Rebuild the .cf file:
501 cd /etc/mail/; make; make install
503 cd /etc/mail/; make restart
505 A sendmail patch is coming, at which time this file will be
509 Generation of legacy formatted entries have been disabled by default
510 in pwd_mkdb(8), as all base system consumers of the legacy formatted
511 entries were converted to use the new format by default when the new,
512 machine independent format have been added and supported since FreeBSD
515 Please see the pwd_mkdb(8) manual page for further details.
518 Clang and llvm have been upgraded to 3.6.1 release. Please see the
519 20141231 entry below for information about prerequisites and upgrading,
520 if you are not already using 3.5.0 or higher.
523 TI platform code switched to using vendor DTS files and this update
524 may break existing systems running on Beaglebone, Beaglebone Black,
527 - dtb files should be regenerated/reinstalled. Filenames are the
528 same but content is different now
529 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
530 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
531 addressing scheme is now pin 25 on /dev/gpioc3.
532 - Pandaboard: /etc/ttys should be updated, serial console device is
533 now /dev/ttyu2, not /dev/ttyu0
536 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
537 If you need the GNU extension from groff soelim(1), install groff
538 from package: pkg install groff, or via ports: textproc/groff.
541 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
542 defined in symlink(7); previously symlinks were silently ignored.
545 The const qualifier has been removed from iconv(3) to comply with
546 POSIX. The ports tree is aware of this from r384038 onwards.
549 Libraries specified by LIBADD in Makefiles must have a corresponding
550 DPADD_<lib> variable to ensure correct dependencies. This is now
551 enforced in src.libnames.mk.
554 From legacy ata(4) driver was removed support for SATA controllers
555 supported by more functional drivers ahci(4), siis(4) and mvs(4).
556 Kernel modules ataahci and ataadaptec were removed completely,
557 replaced by ahci and mvs modules respectively.
560 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
561 the 20141231 entry below for information about prerequisites and
562 upgrading, if you are not already using 3.5.0 or higher.
565 The 32-bit PowerPC kernel has been changed to a position-independent
566 executable. This can only be booted with a version of loader(8)
567 newer than January 31, 2015, so make sure to update both world and
568 kernel before rebooting.
571 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
572 but before r278950, the RNG was not seeded properly. Immediately
573 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
574 ssh keys or openssl keys) that were generated w/ a kernel from that
575 range. This does not affect programs that directly used /dev/random
576 or /dev/urandom. All userland uses of arc4random(3) are affected.
579 The autofs(4) ABI was changed in order to restore binary compatibility
580 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
584 The powerpc64 kernel has been changed to a position-independent
585 executable. This can only be booted with a new version of loader(8),
586 so make sure to update both world and kernel before rebooting.
589 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
590 only release, no new features have been added. Please see the 20141231
591 entry below for information about prerequisites and upgrading, if you
592 are not already using 3.5.0.
595 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
596 taken from the ELF Tool Chain project rather than GNU binutils. They
597 should be drop-in replacements, with the addition of arm64 support.
598 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
599 binutils tools, if necessary. See 20150805 for updated information.
602 The default Unbound configuration now enables remote control
603 using a local socket. Users who have already enabled the
604 local_unbound service should regenerate their configuration
605 by running "service local_unbound setup" as root.
608 The GNU texinfo and GNU info pages have been removed.
609 To be able to view GNU info pages please install texinfo from ports.
612 Clang, llvm and lldb have been upgraded to 3.5.0 release.
614 As of this release, a prerequisite for building clang, llvm and lldb is
615 a C++11 capable compiler and C++11 standard library. This means that to
616 be able to successfully build the cross-tools stage of buildworld, with
617 clang as the bootstrap compiler, your system compiler or cross compiler
618 should either be clang 3.3 or later, or gcc 4.8 or later, and your
619 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
622 On any standard FreeBSD 10.x or 11.x installation, where clang and
623 libc++ are on by default (that is, on x86 or arm), this should work out
626 On 9.x installations where clang is enabled by default, e.g. on x86 and
627 powerpc, libc++ will not be enabled by default, so libc++ should be
628 built (with clang) and installed first. If both clang and libc++ are
629 missing, build clang first, then use it to build libc++.
631 On 8.x and earlier installations, upgrade to 9.x first, and then follow
632 the instructions for 9.x above.
634 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
635 default, and do not build clang.
637 Many embedded systems are resource constrained, and will not be able to
638 build clang in a reasonable time, or in some cases at all. In those
639 cases, cross building bootable systems on amd64 is a workaround.
641 This new version of clang introduces a number of new warnings, of which
642 the following are most likely to appear:
646 This warns in two cases, for both C and C++:
647 * When the code is trying to take the absolute value of an unsigned
648 quantity, which is effectively a no-op, and almost never what was
649 intended. The code should be fixed, if at all possible. If you are
650 sure that the unsigned quantity can be safely cast to signed, without
651 loss of information or undefined behavior, you can add an explicit
652 cast, or disable the warning.
654 * When the code is trying to take an absolute value, but the called
655 abs() variant is for the wrong type, which can lead to truncation.
656 If you want to disable the warning instead of fixing the code, please
657 make sure that truncation will not occur, or it might lead to unwanted
660 -Wtautological-undefined-compare and
661 -Wundefined-bool-conversion
663 These warn when C++ code is trying to compare 'this' against NULL, while
664 'this' should never be NULL in well-defined C++ code. However, there is
665 some legacy (pre C++11) code out there, which actively abuses this
666 feature, which was less strictly defined in previous C++ versions.
668 Squid and openjdk do this, for example. The warning can be turned off
669 for C++98 and earlier, but compiling the code in C++11 mode might result
670 in unexpected behavior; for example, the parts of the program that are
671 unreachable could be optimized away.
674 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
675 kernel sources have been removed. The .h files remain, since some
676 utilities include them. This will need to be fixed later.
677 If "mount -t oldnfs ..." is attempted, it will fail.
678 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
679 the utilities will report errors.
682 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
683 directories to top level SUBDIR variable when their parent
684 directory is included in LOCAL_DIRS. Users with build systems with
685 such hierarchies and without SUBDIR entries in the parent
686 directory Makefiles should add them or add the directories to
690 faith(4) and faithd(8) have been removed from the base system. Faith
691 has been obsolete for a very long time.
694 vt(4), the new console driver, is enabled by default. It brings
695 support for Unicode and double-width characters, as well as
696 support for UEFI and integration with the KMS kernel video
699 You may need to update your console settings in /etc/rc.conf,
700 most probably the keymap. During boot, /etc/rc.d/syscons will
701 indicate what you need to do.
703 vt(4) still has issues and lacks some features compared to
704 syscons(4). See the wiki for up-to-date information:
705 https://wiki.freebsd.org/Newcons
707 If you want to keep using syscons(4), you can do so by adding
708 the following line to /boot/loader.conf:
712 pjdfstest has been integrated into kyua as an opt-in test suite.
713 Please see share/doc/pjdfstest/README for more details on how to
717 gperf has been removed from the base system for architectures
718 that use clang. Ports that require gperf will obtain it from the
722 pjdfstest has been moved from tools/regression/pjdfstest to
726 At svn r271982, The default linux compat kernel ABI has been adjusted
727 to 2.6.18 in support of the linux-c6 compat ports infrastructure
728 update. If you wish to continue using the linux-f10 compat ports,
729 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
730 encouraged to update their linux-compat packages to linux-c6 during
731 their next update cycle.
734 The ofwfb driver, used to provide a graphics console on PowerPC when
735 using vt(4), no longer allows mmap() of all physical memory. This
736 will prevent Xorg on PowerPC with some ATI graphics cards from
737 initializing properly unless x11-servers/xorg-server is updated to
741 The xdev targets have been converted to using TARGET and
742 TARGET_ARCH instead of XDEV and XDEV_ARCH.
745 The default unbound configuration has been modified to address
746 issues with reverse lookups on networks that use private
747 address ranges. If you use the local_unbound service, run
748 "service local_unbound setup" as root to regenerate your
749 configuration, then "service local_unbound reload" to load the
753 The GNU texinfo and GNU info pages are not built and installed
754 anymore, WITH_INFO knob has been added to allow to built and install
756 UPDATE: see 20150102 entry on texinfo's removal
759 The GNU readline library is now an INTERNALLIB - that is, it is
760 statically linked into consumers (GDB and variants) in the base
761 system, and the shared library is no longer installed. The
762 devel/readline port is available for third party software that
766 The Itanium architecture (ia64) has been removed from the list of
767 known architectures. This is the first step in the removal of the
771 Commit r268115 has added NFSv4.1 server support, merged from
772 projects/nfsv4.1-server. Since this includes changes to the
773 internal interfaces between the NFS related modules, a full
774 build of the kernel and modules will be necessary.
775 __FreeBSD_version has been bumped.
778 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
779 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
780 which differs from the behaviour controlled by this knob.)
783 Maximal length of the serial number in CTL was increased from 16 to
784 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
785 and ctld, need to be rebuilt to work with a new kernel.
788 The libatf-c and libatf-c++ major versions were downgraded to 0 and
789 1 respectively to match the upstream numbers. They were out of
790 sync because, when they were originally added to FreeBSD, the
791 upstream versions were not respected. These libraries are private
792 and not yet built by default, so renumbering them should be a
793 non-issue. However, unclean source trees will yield broken test
794 programs once the operator executes "make delete-old-libs" after a
797 Additionally, the atf-sh binary was made private by moving it into
798 /usr/libexec/. Already-built shell test programs will keep the
799 path to the old binary so they will break after "make delete-old"
802 If you are using WITH_TESTS=yes (not the default), wipe the object
803 tree and rebuild from scratch to prevent spurious test failures.
804 This is only needed once: the misnumbered libraries and misplaced
805 binaries have been added to OptionalObsoleteFiles.inc so they will
806 be removed during a clean upgrade.
809 Clang and llvm have been upgraded to 3.4.1 release.
812 We bogusly installed src.opts.mk in /usr/share/mk. This file should
813 be removed to avoid issues in the future (and has been added to
817 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
818 past, it affected all builds that used the bsd.*.mk files. The old
819 behavior was a bug, but people may have relied upon it. To get this
820 behavior back, you can .include /etc/src.conf from /etc/make.conf
821 (which is still global and isn't changed). This also changes the
822 behavior of incremental builds inside the tree of individual
823 directories. Set MAKESYSPATH to ".../share/mk" to do that.
824 Although this has survived make universe and some upgrade scenarios,
825 other upgrade scenarios may have broken. At least one form of
826 temporary breakage was fixed with MAKESYSPATH settings for buildworld
827 as well... In cases where MAKESYSPATH isn't working with this
828 setting, you'll need to set it to the full path to your tree.
830 One side effect of all this cleaning up is that bsd.compiler.mk
831 is no longer implicitly included by bsd.own.mk. If you wish to
832 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
836 The lindev device has been removed since /dev/full has been made a
837 standard device. __FreeBSD_version has been bumped.
840 The knob WITHOUT_VI was added to the base system, which controls
841 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
842 in order to reorder files share/termcap and didn't build ex(1) as a
843 build tool, so building/installing with WITH_VI is highly advised for
844 build hosts for older releases.
846 This issue has been fixed in stable/9 and stable/10 in r277022 and
847 r276991, respectively.
850 The YES_HESIOD knob has been removed. It has been obsolete for
851 a decade. Please move to using WITH_HESIOD instead or your builds
852 will silently lack HESIOD.
855 The uart(4) driver has been changed with respect to its handling
856 of the low-level console. Previously the uart(4) driver prevented
857 any process from changing the baudrate or the CLOCAL and HUPCL
858 control flags. By removing the restrictions, operators can make
859 changes to the serial console port without having to reboot.
860 However, when getty(8) is started on the serial device that is
861 associated with the low-level console, a misconfigured terminal
862 line in /etc/ttys will now have a real impact.
863 Before upgrading the kernel, make sure that /etc/ttys has the
864 serial console device configured as 3wire without baudrate to
865 preserve the previous behaviour. E.g:
866 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
869 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
870 to improve performance. To re-enable it, if needed, run rpcbind
871 with command line option -W.
874 Switched back to the GPL dtc compiler due to updates in the upstream
875 dts files not being supported by the BSDL dtc compiler. You will need
876 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
877 may result while building dtb files during a kernel build if you fail
878 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
881 Clang and llvm have been upgraded to 3.4 release.
884 The nve(4) driver has been removed. Please use the nfe(4) driver
885 for NVIDIA nForce MCP Ethernet adapters instead.
888 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
889 This could cause certain C++ applications using shared libraries built
890 against the previous version of libc++ to crash. The incompatibility
891 has now been fixed, but any C++ applications or shared libraries built
892 between r261283 and r261801 should be recompiled.
895 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
896 capability mode support. Please note that enabling the feature in
897 kernel is still highly recommended.
900 OpenSSH is now built with sandbox support, and will use sandbox as
901 the default privilege separation method. This requires Capsicum
902 capability mode support in kernel.
905 The libelf and libdwarf libraries have been updated to newer
906 versions from upstream. Shared library version numbers for
907 these two libraries were bumped. Any ports or binaries
908 requiring these two libraries should be recompiled.
909 __FreeBSD_version is bumped to 1100006.
912 If a Makefile in a tests/ directory was auto-generating a Kyuafile
913 instead of providing an explicit one, this would prevent such
914 Makefile from providing its own Kyuafile in the future during
915 NO_CLEAN builds. This has been fixed in the Makefiles but manual
916 intervention is needed to clean an objdir if you use NO_CLEAN:
917 # find /usr/obj -name Kyuafile | xargs rm -f
920 The behavior of gss_pseudo_random() for the krb5 mechanism
921 has changed, for applications requesting a longer random string
922 than produced by the underlying enctype's pseudo-random() function.
923 In particular, the random string produced from a session key of
924 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
925 be different at the 17th octet and later, after this change.
926 The counter used in the PRF+ construction is now encoded as a
927 big-endian integer in accordance with RFC 4402.
928 __FreeBSD_version is bumped to 1100004.
931 The WITHOUT_ATF build knob has been removed and its functionality
932 has been subsumed into the more generic WITHOUT_TESTS. If you were
933 using the former to disable the build of the ATF libraries, you
934 should change your settings to use the latter.
937 The default version of mtree is nmtree which is obtained from
938 NetBSD. The output is generally the same, but may vary
939 slightly. If you found you need identical output adding
940 "-F freebsd9" to the command line should do the trick. For the
941 time being, the old mtree is available as fmtree.
944 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
945 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
946 1.1.4_8 and verify bsdyml not linked in, before running "make
948 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
950 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
953 The stable/10 branch has been created in subversion from head
957 The rc.d/jail script has been updated to support jail(8)
958 configuration file. The "jail_<jname>_*" rc.conf(5) variables
959 for per-jail configuration are automatically converted to
960 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
961 This is transparently backward compatible. See below about some
962 incompatibilities and rc.conf(5) manual page for more details.
964 These variables are now deprecated in favor of jail(8) configuration
965 file. One can use "rc.d/jail config <jname>" command to generate
966 a jail(8) configuration file in /var/run/jail.<jname>.conf without
967 running the jail(8) utility. The default pathname of the
968 configuration file is /etc/jail.conf and can be specified by
969 using $jail_conf or $jail_<jname>_conf variables.
971 Please note that jail_devfs_ruleset accepts an integer at
972 this moment. Please consider to rewrite the ruleset name
976 BIND has been removed from the base system. If all you need
977 is a local resolver, simply enable and start the local_unbound
978 service instead. Otherwise, several versions of BIND are
979 available in the ports tree. The dns/bind99 port is one example.
981 With this change, nslookup(1) and dig(1) are no longer in the base
982 system. Users should instead use host(1) and drill(1) which are
983 in the base system. Alternatively, nslookup and dig can
984 be obtained by installing the dns/bind-tools port.
987 With the addition of unbound(8), a new unbound user is now
988 required during installworld. "mergemaster -p" can be used to
989 add the user prior to installworld, as documented in the handbook.
992 OpenSSH is now built with DNSSEC support, and will by default
993 silently trust signed SSHFP records. This can be controlled with
994 the VerifyHostKeyDNS client configuration setting. DNSSEC support
995 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
998 The GNU Compiler Collection and C++ standard library (libstdc++)
999 are no longer built by default on platforms where clang is the system
1000 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1001 options in src.conf.
1004 The PROCDESC kernel option is now part of the GENERIC kernel
1005 configuration and is required for the rwhod(8) to work.
1006 If you are using custom kernel configuration, you should include
1010 The API and ABI related to the Capsicum framework was modified
1011 in backward incompatible way. The userland libraries and programs
1012 have to be recompiled to work with the new kernel. This includes the
1013 following libraries and programs, but the whole buildworld is
1014 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1015 kdump, procstat, rwho, rwhod, uniq.
1018 AES-NI intrinsic support has been added to gcc. The AES-NI module
1019 has been updated to use this support. A new gcc is required to build
1020 the aesni module on both i386 and amd64.
1023 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1024 Thus "device padlock_rng" and "device rdrand_rng" should be
1025 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1028 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1029 enables just the iconv* functionality and is now on by default.
1030 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1031 compatibility. Set WITHOUT_ICONV to build the old way.
1032 If you have been using WITH_ICONV before, you will very likely
1033 need to turn on WITH_LIBICONV_COMPAT.
1036 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1037 Illumos origin, including ZFS. If you have INVARIANTS in your
1038 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1040 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1041 locks if WITNESS option was set. Because that generated a lot of
1042 witness(9) reports and all of them were believed to be false
1043 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1044 can be used to achieve the previous behavior.
1047 Timer values in IPv6 data structures now use time_uptime instead
1048 of time_second. Although this is not a user-visible functional
1049 change, userland utilities which directly use them---ndp(8),
1050 rtadvd(8), and rtsold(8) in the base system---need to be updated
1051 to r253970 or later.
1054 find -delete can now delete the pathnames given as arguments,
1055 instead of only files found below them or if the pathname did
1056 not contain any slashes. Formerly, the following error message
1059 find: -delete: <path>: relative path potentially not safe
1061 Deleting the pathnames given as arguments can be prevented
1062 without error messages using -mindepth 1 or by changing
1063 directory and passing "." as argument to find. This works in the
1064 old as well as the new version of find.
1067 Behavior of devfs rules path matching has been changed.
1068 Pattern is now always matched against fully qualified devfs
1069 path and slash characters must be explicitly matched by
1070 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1071 subdirectories must be reviewed.
1074 The default ARM ABI has changed to the ARM EABI. The old ABI is
1075 incompatible with the ARM EABI and all programs and modules will
1076 need to be rebuilt to work with a new kernel.
1078 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1080 NOTE: Support for the old ABI will be removed in the future and
1081 users are advised to upgrade.
1084 pkg_install has been disconnected from the build if you really need it
1085 you should add WITH_PKGTOOLS in your src.conf(5).
1088 Most of network statistics structures were changed to be able
1089 keep 64-bits counters. Thus all tools, that work with networking
1090 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1093 Fix a bug that allowed a tracing process (e.g. gdb) to write
1094 to a memory-mapped file in the traced process's address space
1095 even if neither the traced process nor the tracing process had
1096 write access to that file.
1099 CVS has been removed from the base system. An exact copy
1100 of the code is available from the devel/cvs port.
1103 Some people report the following error after the switch to bmake:
1105 make: illegal option -- J
1106 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1108 *** [buildworld] Error code 2
1110 this likely due to an old instance of make in
1111 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1112 which src/Makefile will use that blindly, if it exists, so if
1113 you see the above error:
1115 rm -rf `make -V MAKEPATH`
1120 Use bmake by default.
1121 Whereas before one could choose to build with bmake via
1122 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1123 make. The goal is to remove these knobs for 10-RELEASE.
1125 It is worth noting that bmake (like gmake) treats the command
1126 line as the unit of failure, rather than statements within the
1127 command line. Thus '(cd some/where && dosomething)' is safer
1128 than 'cd some/where; dosomething'. The '()' allows consistent
1129 behavior in parallel build.
1132 Fix a bug that allows NFS clients to issue READDIR on files.
1135 The WITHOUT_IDEA option has been removed because
1136 the IDEA patent expired.
1139 The sysctl which controls TRIM support under ZFS has been renamed
1140 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1144 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1145 rather than creating it's own in the temporary directory in
1146 order allow access to bootstrapped versions of tools such as
1147 install and mtree. When upgrading from version of FreeBSD where
1148 the install command does not support -l, you will need to
1149 install a new mergemaster command if mergemaster -p is required.
1150 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1154 Legacy ATA stack, disabled and replaced by new CAM-based one since
1155 FreeBSD 9.0, completely removed from the sources. Kernel modules
1156 atadisk and atapi*, user-level tools atacontrol and burncd are
1157 removed. Kernel option `options ATA_CAM` is now permanently enabled
1161 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1162 and socketpair(2). Software, in particular Kerberos, may
1163 automatically detect and use these during building. The resulting
1164 binaries will not work on older kernels.
1167 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1168 information, see the respective 20130304 entry).
1171 Recent commits to callout(9) changed the size of struct callout,
1172 so the KBI is probably heavily disturbed. Also, some functions
1173 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1174 by macros. Every kernel module using it won't load, so rebuild
1177 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1178 but does not initialize by default (because of the new CTL_DISABLE
1179 option) to save memory. To re-enable it, remove the CTL_DISABLE
1180 option from the kernel config file or set kern.cam.ctl.disable=0
1181 in /boot/loader.conf.
1184 The ctl device has been disabled in GENERIC for i386 and amd64.
1185 This was done due to the extra memory being allocated at system
1186 initialisation time by the ctl driver which was only used if
1187 a CAM target device was created. This makes a FreeBSD system
1188 unusable on 128MB or less of RAM.
1191 A new compression method (lz4) has been merged to -HEAD. Please
1192 refer to zpool-features(7) for more information.
1194 Please refer to the "ZFS notes" section of this file for information
1195 on upgrading boot ZFS pools.
1198 A BSD-licensed patch(1) variant has been added and is installed
1199 as bsdpatch, being the GNU version the default patch.
1200 To inverse the logic and use the BSD-licensed one as default,
1201 while having the GNU version installed as gnupatch, rebuild
1202 and install world with the WITH_BSD_PATCH knob set.
1205 Due to the use of the new -l option to install(1) during build
1206 and install, you must take care not to directly set the INSTALL
1207 make variable in your /etc/make.conf, /etc/src.conf, or on the
1208 command line. If you wish to use the -C flag for all installs
1209 you may be able to add INSTALL+=-C to /etc/make.conf or
1213 The install(1) option -M has changed meaning and now takes an
1214 argument that is a file or path to append logs to. In the
1215 unlikely event that -M was the last option on the command line
1216 and the command line contained at least two files and a target
1217 directory the first file will have logs appended to it. The -M
1218 option served little practical purpose in the last decade so its
1219 use is expected to be extremely rare.
1222 After switching to Clang as the default compiler some users of ZFS
1223 on i386 systems started to experience stack overflow kernel panics.
1224 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1227 GEOM_LABEL now mangles label names read from file system metadata.
1228 Mangling affect labels containing spaces, non-printable characters,
1229 '%' or '"'. Device names in /etc/fstab and other places may need to
1233 By default, only the 10 most recent kernel dumps will be saved. To
1234 restore the previous behaviour (no limit on the number of kernel dumps
1235 stored in the dump directory) add the following line to /etc/rc.conf:
1240 With the addition of auditdistd(8), a new auditdistd user is now
1241 required during installworld. "mergemaster -p" can be used to
1242 add the user prior to installworld, as documented in the handbook.
1245 The sin6_scope_id member variable in struct sockaddr_in6 is now
1246 filled by the kernel before passing the structure to the userland via
1247 sysctl or routing socket. This means the KAME-specific embedded scope
1248 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1249 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1250 __FreeBSD_version is bumped to 1000025.
1253 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1254 This means that the world and kernel will be compiled with clang
1255 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1256 and /usr/bin/cpp. To disable this behavior and revert to building
1257 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1258 of current may need to bootstrap WITHOUT_CLANG first if the clang
1259 build fails (its compatibility window doesn't extend to the 9 stable
1263 The IPFIREWALL_FORWARD kernel option has been removed. Its
1264 functionality now turned on by default.
1267 The ZERO_COPY_SOCKET kernel option has been removed and
1268 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1269 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1270 mechanism which is not safe and may result in kernel crashes.
1271 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1272 driver supports disposeable external page sized mbuf storage.
1273 Proper replacements for both zero-copy mechanisms are under
1274 consideration and will eventually lead to complete removal
1275 of the two kernel options.
1278 The IPv4 network stack has been converted to network byte
1279 order. The following modules need to be recompiled together
1280 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1281 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1284 Support for non-MPSAFE filesystems was removed from VFS. The
1285 VFS_VERSION was bumped, all filesystem modules shall be
1289 All the non-MPSAFE filesystems have been disconnected from
1290 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1291 portalfs, smbfs, xfs.
1294 The interface cloning API and ABI has changed. The following
1295 modules need to be recompiled together with kernel:
1296 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1297 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1298 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1301 The sdhci driver was split in two parts: sdhci (generic SD Host
1302 Controller logic) and sdhci_pci (actual hardware driver).
1303 No kernel config modifications are required, but if you
1304 load sdhc as a module you must switch to sdhci_pci instead.
1307 Import the FUSE kernel and userland support into base system.
1310 The GNU sort(1) program has been removed since the BSD-licensed
1311 sort(1) has been the default for quite some time and no serious
1312 problems have been reported. The corresponding WITH_GNU_SORT
1316 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1317 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1321 The net80211(4) ABI has been changed to allow for improved driver
1322 PS-POLL and power-save support. All wireless drivers need to be
1323 recompiled to work with the new kernel.
1326 The random(4) support for the VIA hardware random number
1327 generator (`PADLOCK') is no longer enabled unconditionally.
1328 Add the padlock_rng device in the custom kernel config if
1329 needed. The GENERIC kernels on i386 and amd64 do include the
1330 device, so the change only affects the custom kernel
1334 The pf(4) packet filter ABI has been changed. pfctl(8) and
1335 snmp_pf module need to be recompiled to work with new kernel.
1338 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1339 to -HEAD. Pools that have empty_bpobj in active state can not be
1340 imported read-write with ZFS implementations that do not support
1341 this feature. For more information read the zpool-features(5)
1345 The sparc64 ZFS loader has been changed to no longer try to auto-
1346 detect ZFS providers based on diskN aliases but now requires these
1347 to be explicitly listed in the OFW boot-device environment variable.
1350 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1351 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1352 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1355 The following sysctls and tunables have been renamed for consistency
1356 with other variables:
1357 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1358 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1361 The sort utility has been replaced with BSD sort. For now, GNU sort
1362 is also available as "gnusort" or the default can be set back to
1363 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1364 installed as "bsdsort".
1367 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1368 Starting with this version the old system of ZFS pool versioning
1369 is superseded by "feature flags". This concept enables forward
1370 compatibility against certain future changes in functionality of ZFS
1371 pools. The first read-only compatible "feature flag" for ZFS pools
1372 is named "com.delphix:async_destroy". For more information
1373 read the new zpool-features(5) manual page.
1374 Please refer to the "ZFS notes" section of this file for information
1375 on upgrading boot ZFS pools.
1378 The malloc(3) implementation embedded in libc now uses sources imported
1379 as contrib/jemalloc. The most disruptive API change is to
1380 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1381 delete it prior to installworld, and optionally re-create it using the
1382 new format after rebooting. See malloc.conf(5) for details
1383 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1387 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1388 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1389 now spelled mips. This is to aid compatibility with third-party
1390 software that expects this naming scheme in uname(3). Little-endian
1391 settings are unchanged. If you are updating a big-endian mips64 machine
1392 from before this change, you may need to set MACHINE_ARCH=mips64 in
1393 your environment before the new build system will recognize your machine.
1396 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1400 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1401 nullfs(5) did not pass through all behaviours to the underlying layer,
1402 as a result if we bound to a socket on the lower layer we could connect
1403 only to the lower path; if we bound to the upper layer we could connect
1404 only to the upper path. The new behavior is one can connect to both the
1405 lower and the upper paths regardless what layer path one binds to.
1408 The getifaddrs upgrade path broken with 20111215 has been restored.
1409 If you have upgraded in between 20111215 and 20120209 you need to
1410 recompile libc again with your kernel. You still need to recompile
1411 world to be able to configure CARP but this restriction already
1412 comes from 20111215.
1415 The set_rcvar() function has been removed from /etc/rc.subr. All
1416 base and ports rc.d scripts have been updated, so if you have a
1417 port installed with a script in /usr/local/etc/rc.d you can either
1418 hand-edit the rcvar= line, or reinstall the port.
1420 An easy way to handle the mass-update of /etc/rc.d:
1421 rm /etc/rc.d/* && mergemaster -i
1424 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1425 on the current CPU and prevents other threads from running.
1426 This behavior can be reverted using the kern.stop_scheduler_on_panic
1428 The new behavior can be incompatible with kern.sync_on_panic.
1431 The carp(4) facility has been changed significantly. Configuration
1432 of the CARP protocol via ifconfig(8) has changed, as well as format
1433 of CARP events submitted to devd(8) has changed. See manual pages
1434 for more information. The arpbalance feature of carp(4) is currently
1435 not supported anymore.
1437 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1438 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1439 need to be recompiled.
1442 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1446 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1447 explicitely support non-MPSAFE filesystems.
1448 It is on by default for all supported platform at this present
1452 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1453 i386 and pc98 GENERIC kernel configuration files.
1456 sysinstall has been removed
1459 The stable/9 branch created in subversion. This corresponds to the
1460 RELENG_9 branch in CVS.
1466 Avoid using make -j when upgrading. While generally safe, there are
1467 sometimes problems using -j to upgrade. If your upgrade fails with
1468 -j, please try again without -j. From time to time in the past there
1469 have been problems using -j with buildworld and/or installworld. This
1470 is especially true when upgrading between "distant" versions (eg one
1471 that cross a major release boundary or several minor releases, or when
1472 several months have passed on the -current branch).
1474 Sometimes, obscure build problems are the result of environment
1475 poisoning. This can happen because the make utility reads its
1476 environment when searching for values for global variables. To run
1477 your build attempts in an "environmental clean room", prefix all make
1478 commands with 'env -i '. See the env(1) manual page for more details.
1480 When upgrading from one major version to another it is generally best
1481 to upgrade to the latest code in the currently installed branch first,
1482 then do an upgrade to the new branch. This is the best-tested upgrade
1483 path, and has the highest probability of being successful. Please try
1484 this approach before reporting problems with a major version upgrade.
1486 When upgrading a live system, having a root shell around before
1487 installing anything can help undo problems. Not having a root shell
1488 around can lead to problems if pam has changed too much from your
1489 starting point to allow continued authentication after the upgrade.
1491 This file should be read as a log of events. When a later event changes
1492 information of a prior event, the prior event should not be deleted.
1493 Instead, a pointer to the entry with the new information should be
1494 placed in the old entry. Readers of this file should also sanity check
1495 older entries before relying on them blindly. Authors of new entries
1496 should write them with this in mind.
1500 When upgrading the boot ZFS pool to a new version, always follow
1503 1.) recompile and reinstall the ZFS boot loader and boot block
1504 (this is part of "make buildworld" and "make installworld")
1506 2.) update the ZFS boot block on your boot drive
1508 The following example updates the ZFS boot block on the first
1509 partition (freebsd-boot) of a GPT partitioned drive ada0:
1510 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1512 Non-boot pools do not need these updates.
1516 If you are updating from a prior version of FreeBSD (even one just
1517 a few days old), you should follow this procedure. It is the most
1518 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1520 make kernel-toolchain
1521 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1522 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1524 To test a kernel once
1525 ---------------------
1526 If you just want to boot a kernel once (because you are not sure
1527 if it works, or if you want to boot a known bad kernel to provide
1528 debugging information) run
1529 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1530 nextboot -k testkernel
1532 To just build a kernel when you know that it won't mess you up
1533 --------------------------------------------------------------
1534 This assumes you are already running a CURRENT system. Replace
1535 ${arch} with the architecture of your machine (e.g. "i386",
1536 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1538 cd src/sys/${arch}/conf
1539 config KERNEL_NAME_HERE
1540 cd ../compile/KERNEL_NAME_HERE
1545 If this fails, go to the "To build a kernel" section.
1547 To rebuild everything and install it on the current system.
1548 -----------------------------------------------------------
1549 # Note: sometimes if you are running current you gotta do more than
1550 # is listed here if you are upgrading from a really old current.
1552 <make sure you have good level 0 dumps>
1554 make kernel KERNCONF=YOUR_KERNEL_HERE
1556 <reboot in single user> [3]
1563 To cross-install current onto a separate partition
1564 --------------------------------------------------
1565 # In this approach we use a separate partition to hold
1566 # current's root, 'usr', and 'var' directories. A partition
1567 # holding "/", "/usr" and "/var" should be about 2GB in
1570 <make sure you have good level 0 dumps>
1573 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1574 <maybe newfs current's root partition>
1575 <mount current's root partition on directory ${CURRENT_ROOT}>
1576 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1577 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1578 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1579 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1580 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1581 <reboot into current>
1582 <do a "native" rebuild/install as described in the previous section>
1583 <maybe install compatibility libraries from ports/misc/compat*>
1587 To upgrade in-place from stable to current
1588 ----------------------------------------------
1589 <make sure you have good level 0 dumps>
1591 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1593 <reboot in single user> [3]
1600 Make sure that you've read the UPDATING file to understand the
1601 tweaks to various things you need. At this point in the life
1602 cycle of current, things change often and you are on your own
1603 to cope. The defaults can also change, so please read ALL of
1604 the UPDATING entries.
1606 Also, if you are tracking -current, you must be subscribed to
1607 freebsd-current@freebsd.org. Make sure that before you update
1608 your sources that you have read and understood all the recent
1609 messages there. If in doubt, please track -stable which has
1610 much fewer pitfalls.
1612 [1] If you have third party modules, such as vmware, you
1613 should disable them at this point so they don't crash your
1616 [3] From the bootblocks, boot -s, and then do
1621 adjkerntz -i # if CMOS is wall time
1622 Also, when doing a major release upgrade, it is required that
1623 you boot into single user mode to do the installworld.
1625 [4] Note: This step is non-optional. Failure to do this step
1626 can result in a significant reduction in the functionality of the
1627 system. Attempting to do it by hand is not recommended and those
1628 that pursue this avenue should read this file carefully, as well
1629 as the archives of freebsd-current and freebsd-hackers mailing lists
1630 for potential gotchas. The -U option is also useful to consider.
1631 See mergemaster(8) for more information.
1633 [5] Usually this step is a noop. However, from time to time
1634 you may need to do this if you get unknown user in the following
1635 step. It never hurts to do it all the time. You may need to
1636 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1637 install) after the buildworld before this step if you last updated
1638 from current before 20130425 or from -stable before 20130430.
1640 [6] This only deletes old files and directories. Old libraries
1641 can be deleted by "make delete-old-libs", but you have to make
1642 sure that no program is using those libraries anymore.
1644 [8] In order to have a kernel that can run the 4.x binaries needed to
1645 do an installworld, you must include the COMPAT_FREEBSD4 option in
1646 your kernel. Failure to do so may leave you with a system that is
1647 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1648 required to run the 5.x binaries on more recent kernels. And so on
1649 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1651 Make sure that you merge any new devices from GENERIC since the
1652 last time you updated your kernel config file.
1654 [9] When checking out sources, you must include the -P flag to have
1655 cvs prune empty directories.
1657 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1658 "?=" instead of the "=" assignment operator, so that buildworld can
1659 override the CPUTYPE if it needs to.
1661 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1662 not on the command line, or in /etc/make.conf. buildworld will
1663 warn if it is improperly defined.
1666 This file contains a list, in reverse chronological order, of major
1667 breakages in tracking -current. It is not guaranteed to be a complete
1668 list of such breakages, and only contains entries since September 23, 2011.
1669 If you need to see UPDATING entries from before that date, you will need
1670 to fetch an UPDATING file from an older FreeBSD release.
1672 Copyright information:
1674 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1676 Redistribution, publication, translation and use, with or without
1677 modification, in full or in part, in any form or format of this
1678 document are permitted without further permission from the author.
1680 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1681 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1682 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1683 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1684 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1685 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1686 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1687 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1688 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1689 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1690 POSSIBILITY OF SUCH DAMAGE.
1692 Contact Warner Losh if you have any questions about your use of