1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-src.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 20171102 p3 FreeBSD-EN-17:09.tzdata
21 Update timezone database information. [EN-17:09]
23 20171017 p2 FreeBSD-SA-17:07.wpa
25 Fix WPA2 protocol vulnerability. [SA-17:07]
27 20170810 p1 FreeBSD-SA-17:06.openssh
31 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
33 Fix VNET kernel panic with asynchronous I/O. [EN-17:07]
35 Fix pf(4) housekeeping thread causes kernel panic. [EN-17:08]
41 arm64 builds now use the base system LLD 4.0.0 linker by default,
42 instead of requiring that the aarch64-binutils port or package be
43 installed. To continue using aarch64-binutils, set
44 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
47 The ctl.ko module no longer implements the iSCSI target frontend:
48 cfiscsi.ko does instead.
50 If building cfiscsi.ko as a kernel module, the module can be loaded
51 via one of the following methods:
52 - `cfiscsi_load="YES"` in loader.conf(5).
53 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
54 - ctladm(8)/ctld(8), when compiled with iSCSI support
55 (`WITH_ISCSI=yes` in src.conf(5))
57 Please see cfiscsi(4) for more details.
60 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
61 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
62 same source (previously, the dependency of mmcsd.ko on mmc.ko was
63 missing, but mmcsd.ko now will refuse to load if it is incompatible
67 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
68 use any explicitly assigned loopback address available in the jail
69 instead of using the first assigned address of the jail.
72 As of r316810 for ipfilter, keep frags is no longer assumed when
73 keep state is specified in a rule. r316810 aligns ipfilter with
74 documentation in man pages separating keep frags from keep state.
75 This allows keep state to specified without forcing keep frags
76 and allows keep frags to be specified independently of keep state.
77 To maintain previous behaviour, also specify keep frags with
78 keep state (as documented in ipf.conf.5).
81 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
82 Please see the 20141231 entry below for information about prerequisites
83 and upgrading, if you are not already using clang 3.5.0 or higher.
86 The code that provides support for ZFS .zfs/ directory functionality
87 has been reimplemented. It's not possible now to create a snapshot
88 by mkdir under .zfs/snapshot/. That should be the only user visible
92 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
93 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
94 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
95 and now NAT-T is supported by default. Security associations now use
96 the single namespace for SPI allocation, so if you use several manually
97 configured security associations with the same SPI, this configuration
101 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
102 Please see the 20141231 entry below for information about prerequisites
103 and upgrading, if you are not already using clang 3.5.0 or higher.
106 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
107 Please see the 20141231 entry below for information about prerequisites
108 and upgrading, if you are not already using clang 3.5.0 or higher.
111 The layout of the pmap structure has changed for powerpc to put the pmap
112 statistics at the front for all CPU variations. libkvm(3) and all tools
113 that link against it need to be recompiled.
116 isl(4) and cyapa(4) drivers now require a new driver,
117 chromebook_platform(4), to work properly on Chromebook-class hardware.
118 On other types of hardware the drivers may need to be configured using
119 device hints. Please see the corresponding manual pages for details.
122 Relocatable object files with the extension of .So have been renamed
123 to use an extension of .pico instead. The purpose of this change is
124 to avoid a name clash with shared libraries on case-insensitive file
125 systems. On those file systems, foo.So is the same file as foo.so.
128 The libc stub for the pipe(2) system call has been replaced with
129 a wrapper that calls the pipe2(2) system call and the pipe(2)
130 system call is now only implemented by the kernels that include
131 "options COMPAT_FREEBSD10" in their config file (this is the
132 default). Users should ensure that this option is enabled in
133 their kernel or upgrade userspace to r302092 before upgrading their
137 CAM will now strip leading spaces from SCSI disks' serial numbers.
138 This will effect users who create UFS filesystems on SCSI disks using
139 those disk's diskid device nodes. For example, if /etc/fstab
140 previously contained a line like
141 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
142 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
143 transforms like gmirror may also be affected. ZFS users should
147 The bitstring(3) API has been updated with new functionality and
148 improved performance. But it is binary-incompatible with the old API.
149 Objects built with the new headers may not be linked against objects
150 built with the old headers.
153 The brk and sbrk functions have been removed from libc on arm64.
154 Binutils from ports has been updated to not link to these
155 functions and should be updated to the latest version before
156 installing a new libc.
159 The armv6 port now defaults to hard float ABI. Limited support
160 for running both hardfloat and soft float on the same system
161 is available using the libraries installed with -DWITH_LIBSOFT.
162 This has only been tested as an upgrade path for installworld
163 and packages may fail or need manual intervention to run. New
164 packages will be needed.
166 To update an existing self-hosted armv6hf system, you must add
167 TARGET_ARCH=armv6 on the make command line for both the build
168 and the install steps.
171 Kernel modules compiled outside of a kernel build now default to
172 installing to /boot/modules instead of /boot/kernel. Many kernel
173 modules built this way (such as those in ports) already overrode
174 KMODDIR explicitly to install into /boot/modules. However,
175 manually building and installing a module from /sys/modules will
176 now install to /boot/modules instead of /boot/kernel.
179 The CAM I/O scheduler has been committed to the kernel. There should be
180 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
181 list of known rogues that claim support for this but actually corrupt
182 data is believed to be complete, be on the lookout for data
183 corruption. The known rogue list is believed to be complete:
185 o Crucial MX100, M550 drives with MU01 firmware.
186 o Micron M510 and M550 drives with MU01 firmware.
187 o Micron M500 prior to MU07 firmware
188 o Samsung 830, 840, and 850 all firmwares
189 o FCCT M500 all firmwares
191 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
192 with working NCQ TRIM. For Micron branded drives, see your sales rep for
193 updated firmware. Black listed drives will work correctly because these
194 drives work correctly so long as no NCQ TRIMs are sent to them. Given
195 this list is the same as found in Linux, it's believed there are no
196 other rogues in the market place. All other models from the above
199 To be safe, if you are at all concerned, you can quirk each of your
200 drives to prevent NCQ from being sent by setting:
201 kern.cam.ada.X.quirks="0x2"
202 in loader.conf. If the drive requires the 4k sector quirk, set the
206 The FAST_DEPEND build option has been removed and its functionality is
207 now the one true way. The old mkdep(1) style of 'make depend' has
208 been removed. See 20160311 for further details.
211 Resource range types have grown from unsigned long to uintmax_t. All
212 drivers, and anything using libdevinfo, need to be recompiled.
215 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
216 builds. It no longer runs mkdep(1) during 'make depend', and the
217 'make depend' stage can safely be skipped now as it is auto ran
218 when building 'make all' and will generate all SRCS and DPSRCS before
219 building anything else. Dependencies are gathered at compile time with
220 -MF flags kept in separate .depend files per object file. Users should
221 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
225 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
226 kernel modules. Therefore, if you load any kernel modules at boot time,
227 please install the boot loaders after you install the kernel, but before
231 make kernel KERNCONF=YOUR_KERNEL_HERE
232 make -C sys/boot install
233 <reboot in single user>
235 Then follow the usual steps, described in the General Notes section,
239 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
240 see the 20141231 entry below for information about prerequisites and
241 upgrading, if you are not already using clang 3.5.0 or higher.
244 The AIO subsystem is now a standard part of the kernel. The
245 VFS_AIO kernel option and aio.ko kernel module have been removed.
246 Due to stability concerns, asynchronous I/O requests are only
247 permitted on sockets and raw disks by default. To enable
248 asynchronous I/O requests on all file types, set the
249 vfs.aio.enable_unsafe sysctl to a non-zero value.
252 The ELF object manipulation tool objcopy is now provided by the
253 ELF Tool Chain project rather than by GNU binutils. It should be a
254 drop-in replacement, with the addition of arm64 support. The
255 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
256 to obtain the GNU version if necessary.
259 Building ZFS pools on top of zvols is prohibited by default. That
260 feature has never worked safely; it's always been prone to deadlocks.
261 Using a zvol as the backing store for a VM guest's virtual disk will
262 still work, even if the guest is using ZFS. Legacy behavior can be
263 restored by setting vfs.zfs.vol.recursive=1.
266 The NONE and HPN patches has been removed from OpenSSH. They are
267 still available in the security/openssh-portable port.
270 With the addition of ypldap(8), a new _ypldap user is now required
271 during installworld. "mergemaster -p" can be used to add the user
272 prior to installworld, as documented in the handbook.
275 The tftp loader (pxeboot) now uses the option root-path directive. As a
276 consequence it no longer looks for a pxeboot.4th file on the tftp
277 server. Instead it uses the regular /boot infrastructure as with the
281 The code to start recording plug and play data into the modules has
282 been committed. While the old tools will properly build a new kernel,
283 a number of warnings about "unknown metadata record 4" will be produced
284 for an older kldxref. To avoid such warnings, make sure to rebuild
285 the kernel toolchain (or world). Make sure that you have r292078 or
286 later when trying to build 292077 or later before rebuilding.
289 Debug data files are now built by default with 'make buildworld' and
290 installed with 'make installworld'. This facilitates debugging but
291 requires more disk space both during the build and for the installed
292 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
296 r291527 changed the internal interface between the nfsd.ko and
297 nfscommon.ko modules. As such, they must both be upgraded to-gether.
298 __FreeBSD_version has been bumped because of this.
301 Add support for unicode collation strings leads to a change of
302 order of files listed by ls(1) for example. To get back to the old
303 behaviour, set LC_COLLATE environment variable to "C".
305 Databases administrators will need to reindex their databases given
306 collation results will be different.
308 Due to a bug in install(1) it is recommended to remove the ancient
309 locales before running make installworld.
311 rm -rf /usr/share/locale/*
314 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
315 libcrypto.so.7 or libssl.so.7 must be recompiled.
318 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
319 Kernel modules isp_2400_multi and isp_2500_multi were removed and
320 should be replaced with isp_2400 and isp_2500 modules respectively.
323 The build previously allowed using 'make -n' to not recurse into
324 sub-directories while showing what commands would be executed, and
325 'make -n -n' to recursively show commands. Now 'make -n' will recurse
326 and 'make -N' will not.
329 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
330 and etcupdate will now use this file. A custom sendmail.cf is now
331 updated via this mechanism rather than via installworld. If you had
332 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
333 want to remove the exclusion or change it to "always install".
334 /etc/mail/sendmail.cf is now managed the same way regardless of
335 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
336 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
339 Compatibility shims for legacy ATA device names have been removed.
340 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
341 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
342 environment variables, /dev/ad* and /dev/ar* symbolic links.
345 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
346 Please see the 20141231 entry below for information about prerequisites
347 and upgrading, if you are not already using clang 3.5.0 or higher.
350 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
351 and renamed from .symbols to .debug. This reduces the size requirements
352 on the boot partition or file system and provides consistency with
353 userland debug files.
355 When using the supported kernel installation method the
356 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
357 as is done with /boot/kernel.
359 Developers wishing to maintain the historical behavior of installing
360 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
363 The wireless drivers had undergone changes that remove the 'parent
364 interface' from the ifconfig -l output. The rc.d network scripts
365 used to check presence of a parent interface in the list, so old
366 scripts would fail to start wireless networking. Thus, etcupdate(3)
367 or mergemaster(8) run is required after kernel update, to update your
368 rc.d scripts in /etc.
371 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
372 These configurations are now automatically interpreted as
373 'scrub fragment reassemble'.
376 Kernel-loadable modules for the random(4) device are back. To use
377 them, the kernel must have
380 options RANDOM_LOADABLE
382 kldload(8) can then be used to load random_fortuna.ko
383 or random_yarrow.ko. Please note that due to the indirect
384 function calls that the loadable modules need to provide,
385 the build-in variants will be slightly more efficient.
387 The random(4) kernel option RANDOM_DUMMY has been retired due to
388 unpopularity. It was not all that useful anyway.
391 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
392 Control over building the ELF Tool Chain tools is now provided by
393 the WITHOUT_TOOLCHAIN knob.
396 The polarity of Pulse Per Second (PPS) capture events with the
397 uart(4) driver has been corrected. Prior to this change the PPS
398 "assert" event corresponded to the trailing edge of a positive PPS
399 pulse and the "clear" event was the leading edge of the next pulse.
401 As the width of a PPS pulse in a typical GPS receiver is on the
402 order of 1 millisecond, most users will not notice any significant
403 difference with this change.
405 Anyone who has compensated for the historical polarity reversal by
406 configuring a negative offset equal to the pulse width will need to
407 remove that workaround.
410 The default group assigned to /dev/dri entries has been changed
411 from 'wheel' to 'video' with the id of '44'. If you want to have
412 access to the dri devices please add yourself to the video group
415 # pw groupmod video -m $USER
418 The menu.rc and loader.rc files will now be replaced during
419 upgrades. Please migrate local changes to menu.rc.local and
420 loader.rc.local instead.
423 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
424 strings and strip have been removed. The src.conf(5) knob
425 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
428 As ZFS requires more kernel stack pages than is the default on some
429 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
430 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
432 Please consider using 'options KSTACK_PAGES=X' where X is greater
433 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
436 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
437 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
438 default, i.e., they will not contain "::". For example, instead
439 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
440 to have a more specific match, such as different map entries for
441 IPv6:0:0 vs IPv6:0. This change requires that configuration
442 data (including maps, files, classes, custom ruleset, etc.) must
443 use the same format, so make certain such configuration data is
444 upgrading. As a very simple check search for patterns like
445 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
446 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
447 the cf option UseCompressedIPv6Addresses.
450 The default kernel entropy-processing algorithm is now
451 Fortuna, replacing Yarrow.
453 Assuming you have 'device random' in your kernel config
454 file, the configurations allow a kernel option to override
455 this default. You may choose *ONE* of:
457 options RANDOM_YARROW # Legacy /dev/random algorithm.
458 options RANDOM_DUMMY # Blocking-only driver.
460 If you have neither, you get Fortuna. For most people,
461 read no further, Fortuna will give a /dev/random that works
462 like it always used to, and the difference will be irrelevant.
464 If you remove 'device random', you get *NO* kernel-processed
465 entropy at all. This may be acceptable to folks building
466 embedded systems, but has complications. Carry on reading,
467 and it is assumed you know what you need.
469 *PLEASE* read random(4) and random(9) if you are in the
470 habit of tweaking kernel configs, and/or if you are a member
471 of the embedded community, wanting specific and not-usual
472 behaviour from your security subsystems.
474 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
475 random', you will NOT have a functioning /dev/random, and
476 many cryptographic features will not work, including SSH.
477 You may also find strange behaviour from the random(3) set
478 of library functions, in particular sranddev(3), srandomdev(3)
479 and arc4random(3). The reason for this is that the KERN_ARND
480 sysctl only returns entropy if it thinks it has some to
481 share, and with RANDOM_DUMMY or no 'device random' this
485 An additional fix for the issue described in the 20150614 sendmail
486 entry below has been been committed in revision 284717.
489 FreeBSD's old make (fmake) has been removed from the system. It is
490 available as the devel/fmake port or via pkg install fmake.
493 The fix for the issue described in the 20150614 sendmail entry
494 below has been been committed in revision 284436. The work
495 around described in that entry is no longer needed unless the
496 default setting is overridden by a confDH_PARAMETERS configuration
497 setting of '5' or pointing to a 512 bit DH parameter file.
500 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
501 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
502 and devel/kyua to version 0.20+ and adjust any calling code to work
503 with Kyuafile and kyua.
506 The import of openssl to address the FreeBSD-SA-15:10.openssl
507 security advisory includes a change which rejects handshakes
508 with DH parameters below 768 bits. sendmail releases prior
509 to 8.15.2 (not yet released), defaulted to a 512 bit
510 DH parameter setting for client connections. To work around
511 this interoperability, sendmail can be configured to use a
512 2048 bit DH parameter by:
514 1. Edit /etc/mail/`hostname`.mc
515 2. If a setting for confDH_PARAMETERS does not exist or
516 exists and is set to a string beginning with '5',
518 3. If a setting for confDH_PARAMETERS exists and is set to
519 a file path, create a new file with:
520 openssl dhparam -out /path/to/file 2048
521 4. Rebuild the .cf file:
522 cd /etc/mail/; make; make install
524 cd /etc/mail/; make restart
526 A sendmail patch is coming, at which time this file will be
530 Generation of legacy formatted entries have been disabled by default
531 in pwd_mkdb(8), as all base system consumers of the legacy formatted
532 entries were converted to use the new format by default when the new,
533 machine independent format have been added and supported since FreeBSD
536 Please see the pwd_mkdb(8) manual page for further details.
539 Clang and llvm have been upgraded to 3.6.1 release. Please see the
540 20141231 entry below for information about prerequisites and upgrading,
541 if you are not already using 3.5.0 or higher.
544 TI platform code switched to using vendor DTS files and this update
545 may break existing systems running on Beaglebone, Beaglebone Black,
548 - dtb files should be regenerated/reinstalled. Filenames are the
549 same but content is different now
550 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
551 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
552 addressing scheme is now pin 25 on /dev/gpioc3.
553 - Pandaboard: /etc/ttys should be updated, serial console device is
554 now /dev/ttyu2, not /dev/ttyu0
557 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
558 If you need the GNU extension from groff soelim(1), install groff
559 from package: pkg install groff, or via ports: textproc/groff.
562 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
563 defined in symlink(7); previously symlinks were silently ignored.
566 The const qualifier has been removed from iconv(3) to comply with
567 POSIX. The ports tree is aware of this from r384038 onwards.
570 Libraries specified by LIBADD in Makefiles must have a corresponding
571 DPADD_<lib> variable to ensure correct dependencies. This is now
572 enforced in src.libnames.mk.
575 From legacy ata(4) driver was removed support for SATA controllers
576 supported by more functional drivers ahci(4), siis(4) and mvs(4).
577 Kernel modules ataahci and ataadaptec were removed completely,
578 replaced by ahci and mvs modules respectively.
581 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
582 the 20141231 entry below for information about prerequisites and
583 upgrading, if you are not already using 3.5.0 or higher.
586 The 32-bit PowerPC kernel has been changed to a position-independent
587 executable. This can only be booted with a version of loader(8)
588 newer than January 31, 2015, so make sure to update both world and
589 kernel before rebooting.
592 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
593 but before r278950, the RNG was not seeded properly. Immediately
594 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
595 ssh keys or openssl keys) that were generated w/ a kernel from that
596 range. This does not affect programs that directly used /dev/random
597 or /dev/urandom. All userland uses of arc4random(3) are affected.
600 The autofs(4) ABI was changed in order to restore binary compatibility
601 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
605 The powerpc64 kernel has been changed to a position-independent
606 executable. This can only be booted with a new version of loader(8),
607 so make sure to update both world and kernel before rebooting.
610 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
611 only release, no new features have been added. Please see the 20141231
612 entry below for information about prerequisites and upgrading, if you
613 are not already using 3.5.0.
616 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
617 taken from the ELF Tool Chain project rather than GNU binutils. They
618 should be drop-in replacements, with the addition of arm64 support.
619 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
620 binutils tools, if necessary. See 20150805 for updated information.
623 The default Unbound configuration now enables remote control
624 using a local socket. Users who have already enabled the
625 local_unbound service should regenerate their configuration
626 by running "service local_unbound setup" as root.
629 The GNU texinfo and GNU info pages have been removed.
630 To be able to view GNU info pages please install texinfo from ports.
633 Clang, llvm and lldb have been upgraded to 3.5.0 release.
635 As of this release, a prerequisite for building clang, llvm and lldb is
636 a C++11 capable compiler and C++11 standard library. This means that to
637 be able to successfully build the cross-tools stage of buildworld, with
638 clang as the bootstrap compiler, your system compiler or cross compiler
639 should either be clang 3.3 or later, or gcc 4.8 or later, and your
640 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
643 On any standard FreeBSD 10.x or 11.x installation, where clang and
644 libc++ are on by default (that is, on x86 or arm), this should work out
647 On 9.x installations where clang is enabled by default, e.g. on x86 and
648 powerpc, libc++ will not be enabled by default, so libc++ should be
649 built (with clang) and installed first. If both clang and libc++ are
650 missing, build clang first, then use it to build libc++.
652 On 8.x and earlier installations, upgrade to 9.x first, and then follow
653 the instructions for 9.x above.
655 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
656 default, and do not build clang.
658 Many embedded systems are resource constrained, and will not be able to
659 build clang in a reasonable time, or in some cases at all. In those
660 cases, cross building bootable systems on amd64 is a workaround.
662 This new version of clang introduces a number of new warnings, of which
663 the following are most likely to appear:
667 This warns in two cases, for both C and C++:
668 * When the code is trying to take the absolute value of an unsigned
669 quantity, which is effectively a no-op, and almost never what was
670 intended. The code should be fixed, if at all possible. If you are
671 sure that the unsigned quantity can be safely cast to signed, without
672 loss of information or undefined behavior, you can add an explicit
673 cast, or disable the warning.
675 * When the code is trying to take an absolute value, but the called
676 abs() variant is for the wrong type, which can lead to truncation.
677 If you want to disable the warning instead of fixing the code, please
678 make sure that truncation will not occur, or it might lead to unwanted
681 -Wtautological-undefined-compare and
682 -Wundefined-bool-conversion
684 These warn when C++ code is trying to compare 'this' against NULL, while
685 'this' should never be NULL in well-defined C++ code. However, there is
686 some legacy (pre C++11) code out there, which actively abuses this
687 feature, which was less strictly defined in previous C++ versions.
689 Squid and openjdk do this, for example. The warning can be turned off
690 for C++98 and earlier, but compiling the code in C++11 mode might result
691 in unexpected behavior; for example, the parts of the program that are
692 unreachable could be optimized away.
695 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
696 kernel sources have been removed. The .h files remain, since some
697 utilities include them. This will need to be fixed later.
698 If "mount -t oldnfs ..." is attempted, it will fail.
699 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
700 the utilities will report errors.
703 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
704 directories to top level SUBDIR variable when their parent
705 directory is included in LOCAL_DIRS. Users with build systems with
706 such hierarchies and without SUBDIR entries in the parent
707 directory Makefiles should add them or add the directories to
711 faith(4) and faithd(8) have been removed from the base system. Faith
712 has been obsolete for a very long time.
715 vt(4), the new console driver, is enabled by default. It brings
716 support for Unicode and double-width characters, as well as
717 support for UEFI and integration with the KMS kernel video
720 You may need to update your console settings in /etc/rc.conf,
721 most probably the keymap. During boot, /etc/rc.d/syscons will
722 indicate what you need to do.
724 vt(4) still has issues and lacks some features compared to
725 syscons(4). See the wiki for up-to-date information:
726 https://wiki.freebsd.org/Newcons
728 If you want to keep using syscons(4), you can do so by adding
729 the following line to /boot/loader.conf:
733 pjdfstest has been integrated into kyua as an opt-in test suite.
734 Please see share/doc/pjdfstest/README for more details on how to
738 gperf has been removed from the base system for architectures
739 that use clang. Ports that require gperf will obtain it from the
743 pjdfstest has been moved from tools/regression/pjdfstest to
747 At svn r271982, The default linux compat kernel ABI has been adjusted
748 to 2.6.18 in support of the linux-c6 compat ports infrastructure
749 update. If you wish to continue using the linux-f10 compat ports,
750 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
751 encouraged to update their linux-compat packages to linux-c6 during
752 their next update cycle.
755 The ofwfb driver, used to provide a graphics console on PowerPC when
756 using vt(4), no longer allows mmap() of all physical memory. This
757 will prevent Xorg on PowerPC with some ATI graphics cards from
758 initializing properly unless x11-servers/xorg-server is updated to
762 The xdev targets have been converted to using TARGET and
763 TARGET_ARCH instead of XDEV and XDEV_ARCH.
766 The default unbound configuration has been modified to address
767 issues with reverse lookups on networks that use private
768 address ranges. If you use the local_unbound service, run
769 "service local_unbound setup" as root to regenerate your
770 configuration, then "service local_unbound reload" to load the
774 The GNU texinfo and GNU info pages are not built and installed
775 anymore, WITH_INFO knob has been added to allow to built and install
777 UPDATE: see 20150102 entry on texinfo's removal
780 The GNU readline library is now an INTERNALLIB - that is, it is
781 statically linked into consumers (GDB and variants) in the base
782 system, and the shared library is no longer installed. The
783 devel/readline port is available for third party software that
787 The Itanium architecture (ia64) has been removed from the list of
788 known architectures. This is the first step in the removal of the
792 Commit r268115 has added NFSv4.1 server support, merged from
793 projects/nfsv4.1-server. Since this includes changes to the
794 internal interfaces between the NFS related modules, a full
795 build of the kernel and modules will be necessary.
796 __FreeBSD_version has been bumped.
799 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
800 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
801 which differs from the behaviour controlled by this knob.)
804 Maximal length of the serial number in CTL was increased from 16 to
805 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
806 and ctld, need to be rebuilt to work with a new kernel.
809 The libatf-c and libatf-c++ major versions were downgraded to 0 and
810 1 respectively to match the upstream numbers. They were out of
811 sync because, when they were originally added to FreeBSD, the
812 upstream versions were not respected. These libraries are private
813 and not yet built by default, so renumbering them should be a
814 non-issue. However, unclean source trees will yield broken test
815 programs once the operator executes "make delete-old-libs" after a
818 Additionally, the atf-sh binary was made private by moving it into
819 /usr/libexec/. Already-built shell test programs will keep the
820 path to the old binary so they will break after "make delete-old"
823 If you are using WITH_TESTS=yes (not the default), wipe the object
824 tree and rebuild from scratch to prevent spurious test failures.
825 This is only needed once: the misnumbered libraries and misplaced
826 binaries have been added to OptionalObsoleteFiles.inc so they will
827 be removed during a clean upgrade.
830 Clang and llvm have been upgraded to 3.4.1 release.
833 We bogusly installed src.opts.mk in /usr/share/mk. This file should
834 be removed to avoid issues in the future (and has been added to
838 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
839 past, it affected all builds that used the bsd.*.mk files. The old
840 behavior was a bug, but people may have relied upon it. To get this
841 behavior back, you can .include /etc/src.conf from /etc/make.conf
842 (which is still global and isn't changed). This also changes the
843 behavior of incremental builds inside the tree of individual
844 directories. Set MAKESYSPATH to ".../share/mk" to do that.
845 Although this has survived make universe and some upgrade scenarios,
846 other upgrade scenarios may have broken. At least one form of
847 temporary breakage was fixed with MAKESYSPATH settings for buildworld
848 as well... In cases where MAKESYSPATH isn't working with this
849 setting, you'll need to set it to the full path to your tree.
851 One side effect of all this cleaning up is that bsd.compiler.mk
852 is no longer implicitly included by bsd.own.mk. If you wish to
853 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
857 The lindev device has been removed since /dev/full has been made a
858 standard device. __FreeBSD_version has been bumped.
861 The knob WITHOUT_VI was added to the base system, which controls
862 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
863 in order to reorder files share/termcap and didn't build ex(1) as a
864 build tool, so building/installing with WITH_VI is highly advised for
865 build hosts for older releases.
867 This issue has been fixed in stable/9 and stable/10 in r277022 and
868 r276991, respectively.
871 The YES_HESIOD knob has been removed. It has been obsolete for
872 a decade. Please move to using WITH_HESIOD instead or your builds
873 will silently lack HESIOD.
876 The uart(4) driver has been changed with respect to its handling
877 of the low-level console. Previously the uart(4) driver prevented
878 any process from changing the baudrate or the CLOCAL and HUPCL
879 control flags. By removing the restrictions, operators can make
880 changes to the serial console port without having to reboot.
881 However, when getty(8) is started on the serial device that is
882 associated with the low-level console, a misconfigured terminal
883 line in /etc/ttys will now have a real impact.
884 Before upgrading the kernel, make sure that /etc/ttys has the
885 serial console device configured as 3wire without baudrate to
886 preserve the previous behaviour. E.g:
887 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
890 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
891 to improve performance. To re-enable it, if needed, run rpcbind
892 with command line option -W.
895 Switched back to the GPL dtc compiler due to updates in the upstream
896 dts files not being supported by the BSDL dtc compiler. You will need
897 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
898 may result while building dtb files during a kernel build if you fail
899 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
902 Clang and llvm have been upgraded to 3.4 release.
905 The nve(4) driver has been removed. Please use the nfe(4) driver
906 for NVIDIA nForce MCP Ethernet adapters instead.
909 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
910 This could cause certain C++ applications using shared libraries built
911 against the previous version of libc++ to crash. The incompatibility
912 has now been fixed, but any C++ applications or shared libraries built
913 between r261283 and r261801 should be recompiled.
916 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
917 capability mode support. Please note that enabling the feature in
918 kernel is still highly recommended.
921 OpenSSH is now built with sandbox support, and will use sandbox as
922 the default privilege separation method. This requires Capsicum
923 capability mode support in kernel.
926 The libelf and libdwarf libraries have been updated to newer
927 versions from upstream. Shared library version numbers for
928 these two libraries were bumped. Any ports or binaries
929 requiring these two libraries should be recompiled.
930 __FreeBSD_version is bumped to 1100006.
933 If a Makefile in a tests/ directory was auto-generating a Kyuafile
934 instead of providing an explicit one, this would prevent such
935 Makefile from providing its own Kyuafile in the future during
936 NO_CLEAN builds. This has been fixed in the Makefiles but manual
937 intervention is needed to clean an objdir if you use NO_CLEAN:
938 # find /usr/obj -name Kyuafile | xargs rm -f
941 The behavior of gss_pseudo_random() for the krb5 mechanism
942 has changed, for applications requesting a longer random string
943 than produced by the underlying enctype's pseudo-random() function.
944 In particular, the random string produced from a session key of
945 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
946 be different at the 17th octet and later, after this change.
947 The counter used in the PRF+ construction is now encoded as a
948 big-endian integer in accordance with RFC 4402.
949 __FreeBSD_version is bumped to 1100004.
952 The WITHOUT_ATF build knob has been removed and its functionality
953 has been subsumed into the more generic WITHOUT_TESTS. If you were
954 using the former to disable the build of the ATF libraries, you
955 should change your settings to use the latter.
958 The default version of mtree is nmtree which is obtained from
959 NetBSD. The output is generally the same, but may vary
960 slightly. If you found you need identical output adding
961 "-F freebsd9" to the command line should do the trick. For the
962 time being, the old mtree is available as fmtree.
965 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
966 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
967 1.1.4_8 and verify bsdyml not linked in, before running "make
969 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
971 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
974 The stable/10 branch has been created in subversion from head
978 The rc.d/jail script has been updated to support jail(8)
979 configuration file. The "jail_<jname>_*" rc.conf(5) variables
980 for per-jail configuration are automatically converted to
981 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
982 This is transparently backward compatible. See below about some
983 incompatibilities and rc.conf(5) manual page for more details.
985 These variables are now deprecated in favor of jail(8) configuration
986 file. One can use "rc.d/jail config <jname>" command to generate
987 a jail(8) configuration file in /var/run/jail.<jname>.conf without
988 running the jail(8) utility. The default pathname of the
989 configuration file is /etc/jail.conf and can be specified by
990 using $jail_conf or $jail_<jname>_conf variables.
992 Please note that jail_devfs_ruleset accepts an integer at
993 this moment. Please consider to rewrite the ruleset name
997 BIND has been removed from the base system. If all you need
998 is a local resolver, simply enable and start the local_unbound
999 service instead. Otherwise, several versions of BIND are
1000 available in the ports tree. The dns/bind99 port is one example.
1002 With this change, nslookup(1) and dig(1) are no longer in the base
1003 system. Users should instead use host(1) and drill(1) which are
1004 in the base system. Alternatively, nslookup and dig can
1005 be obtained by installing the dns/bind-tools port.
1008 With the addition of unbound(8), a new unbound user is now
1009 required during installworld. "mergemaster -p" can be used to
1010 add the user prior to installworld, as documented in the handbook.
1013 OpenSSH is now built with DNSSEC support, and will by default
1014 silently trust signed SSHFP records. This can be controlled with
1015 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1016 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1019 The GNU Compiler Collection and C++ standard library (libstdc++)
1020 are no longer built by default on platforms where clang is the system
1021 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1022 options in src.conf.
1025 The PROCDESC kernel option is now part of the GENERIC kernel
1026 configuration and is required for the rwhod(8) to work.
1027 If you are using custom kernel configuration, you should include
1031 The API and ABI related to the Capsicum framework was modified
1032 in backward incompatible way. The userland libraries and programs
1033 have to be recompiled to work with the new kernel. This includes the
1034 following libraries and programs, but the whole buildworld is
1035 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1036 kdump, procstat, rwho, rwhod, uniq.
1039 AES-NI intrinsic support has been added to gcc. The AES-NI module
1040 has been updated to use this support. A new gcc is required to build
1041 the aesni module on both i386 and amd64.
1044 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1045 Thus "device padlock_rng" and "device rdrand_rng" should be
1046 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1049 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1050 enables just the iconv* functionality and is now on by default.
1051 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1052 compatibility. Set WITHOUT_ICONV to build the old way.
1053 If you have been using WITH_ICONV before, you will very likely
1054 need to turn on WITH_LIBICONV_COMPAT.
1057 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1058 Illumos origin, including ZFS. If you have INVARIANTS in your
1059 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1061 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1062 locks if WITNESS option was set. Because that generated a lot of
1063 witness(9) reports and all of them were believed to be false
1064 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1065 can be used to achieve the previous behavior.
1068 Timer values in IPv6 data structures now use time_uptime instead
1069 of time_second. Although this is not a user-visible functional
1070 change, userland utilities which directly use them---ndp(8),
1071 rtadvd(8), and rtsold(8) in the base system---need to be updated
1072 to r253970 or later.
1075 find -delete can now delete the pathnames given as arguments,
1076 instead of only files found below them or if the pathname did
1077 not contain any slashes. Formerly, the following error message
1080 find: -delete: <path>: relative path potentially not safe
1082 Deleting the pathnames given as arguments can be prevented
1083 without error messages using -mindepth 1 or by changing
1084 directory and passing "." as argument to find. This works in the
1085 old as well as the new version of find.
1088 Behavior of devfs rules path matching has been changed.
1089 Pattern is now always matched against fully qualified devfs
1090 path and slash characters must be explicitly matched by
1091 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1092 subdirectories must be reviewed.
1095 The default ARM ABI has changed to the ARM EABI. The old ABI is
1096 incompatible with the ARM EABI and all programs and modules will
1097 need to be rebuilt to work with a new kernel.
1099 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1101 NOTE: Support for the old ABI will be removed in the future and
1102 users are advised to upgrade.
1105 pkg_install has been disconnected from the build if you really need it
1106 you should add WITH_PKGTOOLS in your src.conf(5).
1109 Most of network statistics structures were changed to be able
1110 keep 64-bits counters. Thus all tools, that work with networking
1111 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1114 Fix a bug that allowed a tracing process (e.g. gdb) to write
1115 to a memory-mapped file in the traced process's address space
1116 even if neither the traced process nor the tracing process had
1117 write access to that file.
1120 CVS has been removed from the base system. An exact copy
1121 of the code is available from the devel/cvs port.
1124 Some people report the following error after the switch to bmake:
1126 make: illegal option -- J
1127 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1129 *** [buildworld] Error code 2
1131 this likely due to an old instance of make in
1132 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1133 which src/Makefile will use that blindly, if it exists, so if
1134 you see the above error:
1136 rm -rf `make -V MAKEPATH`
1141 Use bmake by default.
1142 Whereas before one could choose to build with bmake via
1143 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1144 make. The goal is to remove these knobs for 10-RELEASE.
1146 It is worth noting that bmake (like gmake) treats the command
1147 line as the unit of failure, rather than statements within the
1148 command line. Thus '(cd some/where && dosomething)' is safer
1149 than 'cd some/where; dosomething'. The '()' allows consistent
1150 behavior in parallel build.
1153 Fix a bug that allows NFS clients to issue READDIR on files.
1156 The WITHOUT_IDEA option has been removed because
1157 the IDEA patent expired.
1160 The sysctl which controls TRIM support under ZFS has been renamed
1161 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1165 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1166 rather than creating it's own in the temporary directory in
1167 order allow access to bootstrapped versions of tools such as
1168 install and mtree. When upgrading from version of FreeBSD where
1169 the install command does not support -l, you will need to
1170 install a new mergemaster command if mergemaster -p is required.
1171 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1175 Legacy ATA stack, disabled and replaced by new CAM-based one since
1176 FreeBSD 9.0, completely removed from the sources. Kernel modules
1177 atadisk and atapi*, user-level tools atacontrol and burncd are
1178 removed. Kernel option `options ATA_CAM` is now permanently enabled
1182 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1183 and socketpair(2). Software, in particular Kerberos, may
1184 automatically detect and use these during building. The resulting
1185 binaries will not work on older kernels.
1188 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1189 information, see the respective 20130304 entry).
1192 Recent commits to callout(9) changed the size of struct callout,
1193 so the KBI is probably heavily disturbed. Also, some functions
1194 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1195 by macros. Every kernel module using it won't load, so rebuild
1198 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1199 but does not initialize by default (because of the new CTL_DISABLE
1200 option) to save memory. To re-enable it, remove the CTL_DISABLE
1201 option from the kernel config file or set kern.cam.ctl.disable=0
1202 in /boot/loader.conf.
1205 The ctl device has been disabled in GENERIC for i386 and amd64.
1206 This was done due to the extra memory being allocated at system
1207 initialisation time by the ctl driver which was only used if
1208 a CAM target device was created. This makes a FreeBSD system
1209 unusable on 128MB or less of RAM.
1212 A new compression method (lz4) has been merged to -HEAD. Please
1213 refer to zpool-features(7) for more information.
1215 Please refer to the "ZFS notes" section of this file for information
1216 on upgrading boot ZFS pools.
1219 A BSD-licensed patch(1) variant has been added and is installed
1220 as bsdpatch, being the GNU version the default patch.
1221 To inverse the logic and use the BSD-licensed one as default,
1222 while having the GNU version installed as gnupatch, rebuild
1223 and install world with the WITH_BSD_PATCH knob set.
1226 Due to the use of the new -l option to install(1) during build
1227 and install, you must take care not to directly set the INSTALL
1228 make variable in your /etc/make.conf, /etc/src.conf, or on the
1229 command line. If you wish to use the -C flag for all installs
1230 you may be able to add INSTALL+=-C to /etc/make.conf or
1234 The install(1) option -M has changed meaning and now takes an
1235 argument that is a file or path to append logs to. In the
1236 unlikely event that -M was the last option on the command line
1237 and the command line contained at least two files and a target
1238 directory the first file will have logs appended to it. The -M
1239 option served little practical purpose in the last decade so its
1240 use is expected to be extremely rare.
1243 After switching to Clang as the default compiler some users of ZFS
1244 on i386 systems started to experience stack overflow kernel panics.
1245 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1248 GEOM_LABEL now mangles label names read from file system metadata.
1249 Mangling affect labels containing spaces, non-printable characters,
1250 '%' or '"'. Device names in /etc/fstab and other places may need to
1254 By default, only the 10 most recent kernel dumps will be saved. To
1255 restore the previous behaviour (no limit on the number of kernel dumps
1256 stored in the dump directory) add the following line to /etc/rc.conf:
1261 With the addition of auditdistd(8), a new auditdistd user is now
1262 required during installworld. "mergemaster -p" can be used to
1263 add the user prior to installworld, as documented in the handbook.
1266 The sin6_scope_id member variable in struct sockaddr_in6 is now
1267 filled by the kernel before passing the structure to the userland via
1268 sysctl or routing socket. This means the KAME-specific embedded scope
1269 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1270 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1271 __FreeBSD_version is bumped to 1000025.
1274 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1275 This means that the world and kernel will be compiled with clang
1276 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1277 and /usr/bin/cpp. To disable this behavior and revert to building
1278 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1279 of current may need to bootstrap WITHOUT_CLANG first if the clang
1280 build fails (its compatibility window doesn't extend to the 9 stable
1284 The IPFIREWALL_FORWARD kernel option has been removed. Its
1285 functionality now turned on by default.
1288 The ZERO_COPY_SOCKET kernel option has been removed and
1289 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1290 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1291 mechanism which is not safe and may result in kernel crashes.
1292 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1293 driver supports disposeable external page sized mbuf storage.
1294 Proper replacements for both zero-copy mechanisms are under
1295 consideration and will eventually lead to complete removal
1296 of the two kernel options.
1299 The IPv4 network stack has been converted to network byte
1300 order. The following modules need to be recompiled together
1301 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1302 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1305 Support for non-MPSAFE filesystems was removed from VFS. The
1306 VFS_VERSION was bumped, all filesystem modules shall be
1310 All the non-MPSAFE filesystems have been disconnected from
1311 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1312 portalfs, smbfs, xfs.
1315 The interface cloning API and ABI has changed. The following
1316 modules need to be recompiled together with kernel:
1317 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1318 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1319 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1322 The sdhci driver was split in two parts: sdhci (generic SD Host
1323 Controller logic) and sdhci_pci (actual hardware driver).
1324 No kernel config modifications are required, but if you
1325 load sdhc as a module you must switch to sdhci_pci instead.
1328 Import the FUSE kernel and userland support into base system.
1331 The GNU sort(1) program has been removed since the BSD-licensed
1332 sort(1) has been the default for quite some time and no serious
1333 problems have been reported. The corresponding WITH_GNU_SORT
1337 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1338 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1342 The net80211(4) ABI has been changed to allow for improved driver
1343 PS-POLL and power-save support. All wireless drivers need to be
1344 recompiled to work with the new kernel.
1347 The random(4) support for the VIA hardware random number
1348 generator (`PADLOCK') is no longer enabled unconditionally.
1349 Add the padlock_rng device in the custom kernel config if
1350 needed. The GENERIC kernels on i386 and amd64 do include the
1351 device, so the change only affects the custom kernel
1355 The pf(4) packet filter ABI has been changed. pfctl(8) and
1356 snmp_pf module need to be recompiled to work with new kernel.
1359 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1360 to -HEAD. Pools that have empty_bpobj in active state can not be
1361 imported read-write with ZFS implementations that do not support
1362 this feature. For more information read the zpool-features(5)
1366 The sparc64 ZFS loader has been changed to no longer try to auto-
1367 detect ZFS providers based on diskN aliases but now requires these
1368 to be explicitly listed in the OFW boot-device environment variable.
1371 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1372 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1373 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1376 The following sysctls and tunables have been renamed for consistency
1377 with other variables:
1378 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1379 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1382 The sort utility has been replaced with BSD sort. For now, GNU sort
1383 is also available as "gnusort" or the default can be set back to
1384 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1385 installed as "bsdsort".
1388 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1389 Starting with this version the old system of ZFS pool versioning
1390 is superseded by "feature flags". This concept enables forward
1391 compatibility against certain future changes in functionality of ZFS
1392 pools. The first read-only compatible "feature flag" for ZFS pools
1393 is named "com.delphix:async_destroy". For more information
1394 read the new zpool-features(5) manual page.
1395 Please refer to the "ZFS notes" section of this file for information
1396 on upgrading boot ZFS pools.
1399 The malloc(3) implementation embedded in libc now uses sources imported
1400 as contrib/jemalloc. The most disruptive API change is to
1401 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1402 delete it prior to installworld, and optionally re-create it using the
1403 new format after rebooting. See malloc.conf(5) for details
1404 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1408 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1409 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1410 now spelled mips. This is to aid compatibility with third-party
1411 software that expects this naming scheme in uname(3). Little-endian
1412 settings are unchanged. If you are updating a big-endian mips64 machine
1413 from before this change, you may need to set MACHINE_ARCH=mips64 in
1414 your environment before the new build system will recognize your machine.
1417 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1421 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1422 nullfs(5) did not pass through all behaviours to the underlying layer,
1423 as a result if we bound to a socket on the lower layer we could connect
1424 only to the lower path; if we bound to the upper layer we could connect
1425 only to the upper path. The new behavior is one can connect to both the
1426 lower and the upper paths regardless what layer path one binds to.
1429 The getifaddrs upgrade path broken with 20111215 has been restored.
1430 If you have upgraded in between 20111215 and 20120209 you need to
1431 recompile libc again with your kernel. You still need to recompile
1432 world to be able to configure CARP but this restriction already
1433 comes from 20111215.
1436 The set_rcvar() function has been removed from /etc/rc.subr. All
1437 base and ports rc.d scripts have been updated, so if you have a
1438 port installed with a script in /usr/local/etc/rc.d you can either
1439 hand-edit the rcvar= line, or reinstall the port.
1441 An easy way to handle the mass-update of /etc/rc.d:
1442 rm /etc/rc.d/* && mergemaster -i
1445 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1446 on the current CPU and prevents other threads from running.
1447 This behavior can be reverted using the kern.stop_scheduler_on_panic
1449 The new behavior can be incompatible with kern.sync_on_panic.
1452 The carp(4) facility has been changed significantly. Configuration
1453 of the CARP protocol via ifconfig(8) has changed, as well as format
1454 of CARP events submitted to devd(8) has changed. See manual pages
1455 for more information. The arpbalance feature of carp(4) is currently
1456 not supported anymore.
1458 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1459 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1460 need to be recompiled.
1463 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1467 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1468 explicitely support non-MPSAFE filesystems.
1469 It is on by default for all supported platform at this present
1473 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1474 i386 and pc98 GENERIC kernel configuration files.
1477 sysinstall has been removed
1480 The stable/9 branch created in subversion. This corresponds to the
1481 RELENG_9 branch in CVS.
1487 Avoid using make -j when upgrading. While generally safe, there are
1488 sometimes problems using -j to upgrade. If your upgrade fails with
1489 -j, please try again without -j. From time to time in the past there
1490 have been problems using -j with buildworld and/or installworld. This
1491 is especially true when upgrading between "distant" versions (eg one
1492 that cross a major release boundary or several minor releases, or when
1493 several months have passed on the -current branch).
1495 Sometimes, obscure build problems are the result of environment
1496 poisoning. This can happen because the make utility reads its
1497 environment when searching for values for global variables. To run
1498 your build attempts in an "environmental clean room", prefix all make
1499 commands with 'env -i '. See the env(1) manual page for more details.
1501 When upgrading from one major version to another it is generally best
1502 to upgrade to the latest code in the currently installed branch first,
1503 then do an upgrade to the new branch. This is the best-tested upgrade
1504 path, and has the highest probability of being successful. Please try
1505 this approach before reporting problems with a major version upgrade.
1507 When upgrading a live system, having a root shell around before
1508 installing anything can help undo problems. Not having a root shell
1509 around can lead to problems if pam has changed too much from your
1510 starting point to allow continued authentication after the upgrade.
1512 This file should be read as a log of events. When a later event changes
1513 information of a prior event, the prior event should not be deleted.
1514 Instead, a pointer to the entry with the new information should be
1515 placed in the old entry. Readers of this file should also sanity check
1516 older entries before relying on them blindly. Authors of new entries
1517 should write them with this in mind.
1521 When upgrading the boot ZFS pool to a new version, always follow
1524 1.) recompile and reinstall the ZFS boot loader and boot block
1525 (this is part of "make buildworld" and "make installworld")
1527 2.) update the ZFS boot block on your boot drive
1529 The following example updates the ZFS boot block on the first
1530 partition (freebsd-boot) of a GPT partitioned drive ada0:
1531 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1533 Non-boot pools do not need these updates.
1537 If you are updating from a prior version of FreeBSD (even one just
1538 a few days old), you should follow this procedure. It is the most
1539 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1541 make kernel-toolchain
1542 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1543 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1545 To test a kernel once
1546 ---------------------
1547 If you just want to boot a kernel once (because you are not sure
1548 if it works, or if you want to boot a known bad kernel to provide
1549 debugging information) run
1550 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1551 nextboot -k testkernel
1553 To just build a kernel when you know that it won't mess you up
1554 --------------------------------------------------------------
1555 This assumes you are already running a CURRENT system. Replace
1556 ${arch} with the architecture of your machine (e.g. "i386",
1557 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1559 cd src/sys/${arch}/conf
1560 config KERNEL_NAME_HERE
1561 cd ../compile/KERNEL_NAME_HERE
1566 If this fails, go to the "To build a kernel" section.
1568 To rebuild everything and install it on the current system.
1569 -----------------------------------------------------------
1570 # Note: sometimes if you are running current you gotta do more than
1571 # is listed here if you are upgrading from a really old current.
1573 <make sure you have good level 0 dumps>
1575 make kernel KERNCONF=YOUR_KERNEL_HERE
1577 <reboot in single user> [3]
1584 To cross-install current onto a separate partition
1585 --------------------------------------------------
1586 # In this approach we use a separate partition to hold
1587 # current's root, 'usr', and 'var' directories. A partition
1588 # holding "/", "/usr" and "/var" should be about 2GB in
1591 <make sure you have good level 0 dumps>
1594 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1595 <maybe newfs current's root partition>
1596 <mount current's root partition on directory ${CURRENT_ROOT}>
1597 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1598 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1599 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1600 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1601 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1602 <reboot into current>
1603 <do a "native" rebuild/install as described in the previous section>
1604 <maybe install compatibility libraries from ports/misc/compat*>
1608 To upgrade in-place from stable to current
1609 ----------------------------------------------
1610 <make sure you have good level 0 dumps>
1612 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1614 <reboot in single user> [3]
1621 Make sure that you've read the UPDATING file to understand the
1622 tweaks to various things you need. At this point in the life
1623 cycle of current, things change often and you are on your own
1624 to cope. The defaults can also change, so please read ALL of
1625 the UPDATING entries.
1627 Also, if you are tracking -current, you must be subscribed to
1628 freebsd-current@freebsd.org. Make sure that before you update
1629 your sources that you have read and understood all the recent
1630 messages there. If in doubt, please track -stable which has
1631 much fewer pitfalls.
1633 [1] If you have third party modules, such as vmware, you
1634 should disable them at this point so they don't crash your
1637 [3] From the bootblocks, boot -s, and then do
1642 adjkerntz -i # if CMOS is wall time
1643 Also, when doing a major release upgrade, it is required that
1644 you boot into single user mode to do the installworld.
1646 [4] Note: This step is non-optional. Failure to do this step
1647 can result in a significant reduction in the functionality of the
1648 system. Attempting to do it by hand is not recommended and those
1649 that pursue this avenue should read this file carefully, as well
1650 as the archives of freebsd-current and freebsd-hackers mailing lists
1651 for potential gotchas. The -U option is also useful to consider.
1652 See mergemaster(8) for more information.
1654 [5] Usually this step is a noop. However, from time to time
1655 you may need to do this if you get unknown user in the following
1656 step. It never hurts to do it all the time. You may need to
1657 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1658 install) after the buildworld before this step if you last updated
1659 from current before 20130425 or from -stable before 20130430.
1661 [6] This only deletes old files and directories. Old libraries
1662 can be deleted by "make delete-old-libs", but you have to make
1663 sure that no program is using those libraries anymore.
1665 [8] In order to have a kernel that can run the 4.x binaries needed to
1666 do an installworld, you must include the COMPAT_FREEBSD4 option in
1667 your kernel. Failure to do so may leave you with a system that is
1668 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1669 required to run the 5.x binaries on more recent kernels. And so on
1670 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1672 Make sure that you merge any new devices from GENERIC since the
1673 last time you updated your kernel config file.
1675 [9] When checking out sources, you must include the -P flag to have
1676 cvs prune empty directories.
1678 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1679 "?=" instead of the "=" assignment operator, so that buildworld can
1680 override the CPUTYPE if it needs to.
1682 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1683 not on the command line, or in /etc/make.conf. buildworld will
1684 warn if it is improperly defined.
1687 This file contains a list, in reverse chronological order, of major
1688 breakages in tracking -current. It is not guaranteed to be a complete
1689 list of such breakages, and only contains entries since September 23, 2011.
1690 If you need to see UPDATING entries from before that date, you will need
1691 to fetch an UPDATING file from an older FreeBSD release.
1693 Copyright information:
1695 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1697 Redistribution, publication, translation and use, with or without
1698 modification, in full or in part, in any form or format of this
1699 document are permitted without further permission from the author.
1701 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1702 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1703 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1704 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1705 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1706 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1707 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1708 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1709 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1710 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1711 POSSIBILITY OF SUCH DAMAGE.
1713 Contact Warner Losh if you have any questions about your use of