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