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