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 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
20 The code that provides support for ZFS .zfs/ directory functionality
21 has been reimplemented. It's not possible now to create a snapshot
22 by mkdir under .zfs/snapshot/. That should be the only user visible
26 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
27 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
28 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
29 and now NAT-T is supported by default. Security associations now use
30 the single namespace for SPI allocation, so if you use several manually
31 configured security associations with the same SPI, this configuration
35 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
36 Please see the 20141231 entry below for information about prerequisites
37 and upgrading, if you are not already using clang 3.5.0 or higher.
40 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
41 Please see the 20141231 entry below for information about prerequisites
42 and upgrading, if you are not already using clang 3.5.0 or higher.
45 The layout of the pmap structure has changed for powerpc to put the pmap
46 statistics at the front for all CPU variations. libkvm(3) and all tools
47 that link against it need to be recompiled.
50 isl(4) and cyapa(4) drivers now require a new driver,
51 chromebook_platform(4), to work properly on Chromebook-class hardware.
52 On other types of hardware the drivers may need to be configured using
53 device hints. Please see the corresponding manual pages for details.
56 Relocatable object files with the extension of .So have been renamed
57 to use an extension of .pico instead. The purpose of this change is
58 to avoid a name clash with shared libraries on case-insensitive file
59 systems. On those file systems, foo.So is the same file as foo.so.
62 The libc stub for the pipe(2) system call has been replaced with
63 a wrapper that calls the pipe2(2) system call and the pipe(2)
64 system call is now only implemented by the kernels that include
65 "options COMPAT_FREEBSD10" in their config file (this is the
66 default). Users should ensure that this option is enabled in
67 their kernel or upgrade userspace to r302092 before upgrading their
71 CAM will now strip leading spaces from SCSI disks' serial numbers.
72 This will effect users who create UFS filesystems on SCSI disks using
73 those disk's diskid device nodes. For example, if /etc/fstab
74 previously contained a line like
75 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
76 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
77 transforms like gmirror may also be affected. ZFS users should
81 The bitstring(3) API has been updated with new functionality and
82 improved performance. But it is binary-incompatible with the old API.
83 Objects built with the new headers may not be linked against objects
84 built with the old headers.
87 The brk and sbrk functions have been removed from libc on arm64.
88 Binutils from ports has been updated to not link to these
89 functions and should be updated to the latest version before
90 installing a new libc.
93 The armv6 port now defaults to hard float ABI. Limited support
94 for running both hardfloat and soft float on the same system
95 is available using the libraries installed with -DWITH_LIBSOFT.
96 This has only been tested as an upgrade path for installworld
97 and packages may fail or need manual intervention to run. New
98 packages will be needed.
100 To update an existing self-hosted armv6hf system, you must add
101 TARGET_ARCH=armv6 on the make command line for both the build
102 and the install steps.
105 Kernel modules compiled outside of a kernel build now default to
106 installing to /boot/modules instead of /boot/kernel. Many kernel
107 modules built this way (such as those in ports) already overrode
108 KMODDIR explicitly to install into /boot/modules. However,
109 manually building and installing a module from /sys/modules will
110 now install to /boot/modules instead of /boot/kernel.
113 The CAM I/O scheduler has been committed to the kernel. There should be
114 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
115 list of known rogues that claim support for this but actually corrupt
116 data is believed to be complete, be on the lookout for data
117 corruption. The known rogue list is believed to be complete:
119 o Crucial MX100, M550 drives with MU01 firmware.
120 o Micron M510 and M550 drives with MU01 firmware.
121 o Micron M500 prior to MU07 firmware
122 o Samsung 830, 840, and 850 all firmwares
123 o FCCT M500 all firmwares
125 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
126 with working NCQ TRIM. For Micron branded drives, see your sales rep for
127 updated firmware. Black listed drives will work correctly because these
128 drives work correctly so long as no NCQ TRIMs are sent to them. Given
129 this list is the same as found in Linux, it's believed there are no
130 other rogues in the market place. All other models from the above
133 To be safe, if you are at all concerned, you can quirk each of your
134 drives to prevent NCQ from being sent by setting:
135 kern.cam.ada.X.quirks="0x2"
136 in loader.conf. If the drive requires the 4k sector quirk, set the
140 The FAST_DEPEND build option has been removed and its functionality is
141 now the one true way. The old mkdep(1) style of 'make depend' has
142 been removed. See 20160311 for further details.
145 Resource range types have grown from unsigned long to uintmax_t. All
146 drivers, and anything using libdevinfo, need to be recompiled.
149 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
150 builds. It no longer runs mkdep(1) during 'make depend', and the
151 'make depend' stage can safely be skipped now as it is auto ran
152 when building 'make all' and will generate all SRCS and DPSRCS before
153 building anything else. Dependencies are gathered at compile time with
154 -MF flags kept in separate .depend files per object file. Users should
155 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
159 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
160 kernel modules. Therefore, if you load any kernel modules at boot time,
161 please install the boot loaders after you install the kernel, but before
165 make kernel KERNCONF=YOUR_KERNEL_HERE
166 make -C sys/boot install
167 <reboot in single user>
169 Then follow the usual steps, described in the General Notes section,
173 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
174 see the 20141231 entry below for information about prerequisites and
175 upgrading, if you are not already using clang 3.5.0 or higher.
178 The AIO subsystem is now a standard part of the kernel. The
179 VFS_AIO kernel option and aio.ko kernel module have been removed.
180 Due to stability concerns, asynchronous I/O requests are only
181 permitted on sockets and raw disks by default. To enable
182 asynchronous I/O requests on all file types, set the
183 vfs.aio.enable_unsafe sysctl to a non-zero value.
186 The ELF object manipulation tool objcopy is now provided by the
187 ELF Tool Chain project rather than by GNU binutils. It should be a
188 drop-in replacement, with the addition of arm64 support. The
189 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
190 to obtain the GNU version if necessary.
193 Building ZFS pools on top of zvols is prohibited by default. That
194 feature has never worked safely; it's always been prone to deadlocks.
195 Using a zvol as the backing store for a VM guest's virtual disk will
196 still work, even if the guest is using ZFS. Legacy behavior can be
197 restored by setting vfs.zfs.vol.recursive=1.
200 The NONE and HPN patches has been removed from OpenSSH. They are
201 still available in the security/openssh-portable port.
204 With the addition of ypldap(8), a new _ypldap user is now required
205 during installworld. "mergemaster -p" can be used to add the user
206 prior to installworld, as documented in the handbook.
209 The tftp loader (pxeboot) now uses the option root-path directive. As a
210 consequence it no longer looks for a pxeboot.4th file on the tftp
211 server. Instead it uses the regular /boot infrastructure as with the
215 The code to start recording plug and play data into the modules has
216 been committed. While the old tools will properly build a new kernel,
217 a number of warnings about "unknown metadata record 4" will be produced
218 for an older kldxref. To avoid such warnings, make sure to rebuild
219 the kernel toolchain (or world). Make sure that you have r292078 or
220 later when trying to build 292077 or later before rebuilding.
223 Debug data files are now built by default with 'make buildworld' and
224 installed with 'make installworld'. This facilitates debugging but
225 requires more disk space both during the build and for the installed
226 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
230 r291527 changed the internal interface between the nfsd.ko and
231 nfscommon.ko modules. As such, they must both be upgraded to-gether.
232 __FreeBSD_version has been bumped because of this.
235 Add support for unicode collation strings leads to a change of
236 order of files listed by ls(1) for example. To get back to the old
237 behaviour, set LC_COLLATE environment variable to "C".
239 Databases administrators will need to reindex their databases given
240 collation results will be different.
242 Due to a bug in install(1) it is recommended to remove the ancient
243 locales before running make installworld.
245 rm -rf /usr/share/locale/*
248 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
249 libcrypto.so.7 or libssl.so.7 must be recompiled.
252 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
253 Kernel modules isp_2400_multi and isp_2500_multi were removed and
254 should be replaced with isp_2400 and isp_2500 modules respectively.
257 The build previously allowed using 'make -n' to not recurse into
258 sub-directories while showing what commands would be executed, and
259 'make -n -n' to recursively show commands. Now 'make -n' will recurse
260 and 'make -N' will not.
263 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
264 and etcupdate will now use this file. A custom sendmail.cf is now
265 updated via this mechanism rather than via installworld. If you had
266 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
267 want to remove the exclusion or change it to "always install".
268 /etc/mail/sendmail.cf is now managed the same way regardless of
269 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
270 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
273 Compatibility shims for legacy ATA device names have been removed.
274 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
275 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
276 environment variables, /dev/ad* and /dev/ar* symbolic links.
279 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
280 Please see the 20141231 entry below for information about prerequisites
281 and upgrading, if you are not already using clang 3.5.0 or higher.
284 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
285 and renamed from .symbols to .debug. This reduces the size requirements
286 on the boot partition or file system and provides consistency with
287 userland debug files.
289 When using the supported kernel installation method the
290 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
291 as is done with /boot/kernel.
293 Developers wishing to maintain the historical behavior of installing
294 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
297 The wireless drivers had undergone changes that remove the 'parent
298 interface' from the ifconfig -l output. The rc.d network scripts
299 used to check presence of a parent interface in the list, so old
300 scripts would fail to start wireless networking. Thus, etcupdate(3)
301 or mergemaster(8) run is required after kernel update, to update your
302 rc.d scripts in /etc.
305 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
306 These configurations are now automatically interpreted as
307 'scrub fragment reassemble'.
310 Kernel-loadable modules for the random(4) device are back. To use
311 them, the kernel must have
314 options RANDOM_LOADABLE
316 kldload(8) can then be used to load random_fortuna.ko
317 or random_yarrow.ko. Please note that due to the indirect
318 function calls that the loadable modules need to provide,
319 the build-in variants will be slightly more efficient.
321 The random(4) kernel option RANDOM_DUMMY has been retired due to
322 unpopularity. It was not all that useful anyway.
325 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
326 Control over building the ELF Tool Chain tools is now provided by
327 the WITHOUT_TOOLCHAIN knob.
330 The polarity of Pulse Per Second (PPS) capture events with the
331 uart(4) driver has been corrected. Prior to this change the PPS
332 "assert" event corresponded to the trailing edge of a positive PPS
333 pulse and the "clear" event was the leading edge of the next pulse.
335 As the width of a PPS pulse in a typical GPS receiver is on the
336 order of 1 millisecond, most users will not notice any significant
337 difference with this change.
339 Anyone who has compensated for the historical polarity reversal by
340 configuring a negative offset equal to the pulse width will need to
341 remove that workaround.
344 The default group assigned to /dev/dri entries has been changed
345 from 'wheel' to 'video' with the id of '44'. If you want to have
346 access to the dri devices please add yourself to the video group
349 # pw groupmod video -m $USER
352 The menu.rc and loader.rc files will now be replaced during
353 upgrades. Please migrate local changes to menu.rc.local and
354 loader.rc.local instead.
357 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
358 strings and strip have been removed. The src.conf(5) knob
359 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
362 As ZFS requires more kernel stack pages than is the default on some
363 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
364 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
366 Please consider using 'options KSTACK_PAGES=X' where X is greater
367 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
370 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
371 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
372 default, i.e., they will not contain "::". For example, instead
373 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
374 to have a more specific match, such as different map entries for
375 IPv6:0:0 vs IPv6:0. This change requires that configuration
376 data (including maps, files, classes, custom ruleset, etc.) must
377 use the same format, so make certain such configuration data is
378 upgrading. As a very simple check search for patterns like
379 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
380 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
381 the cf option UseCompressedIPv6Addresses.
384 The default kernel entropy-processing algorithm is now
385 Fortuna, replacing Yarrow.
387 Assuming you have 'device random' in your kernel config
388 file, the configurations allow a kernel option to override
389 this default. You may choose *ONE* of:
391 options RANDOM_YARROW # Legacy /dev/random algorithm.
392 options RANDOM_DUMMY # Blocking-only driver.
394 If you have neither, you get Fortuna. For most people,
395 read no further, Fortuna will give a /dev/random that works
396 like it always used to, and the difference will be irrelevant.
398 If you remove 'device random', you get *NO* kernel-processed
399 entropy at all. This may be acceptable to folks building
400 embedded systems, but has complications. Carry on reading,
401 and it is assumed you know what you need.
403 *PLEASE* read random(4) and random(9) if you are in the
404 habit of tweaking kernel configs, and/or if you are a member
405 of the embedded community, wanting specific and not-usual
406 behaviour from your security subsystems.
408 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
409 random', you will NOT have a functioning /dev/random, and
410 many cryptographic features will not work, including SSH.
411 You may also find strange behaviour from the random(3) set
412 of library functions, in particular sranddev(3), srandomdev(3)
413 and arc4random(3). The reason for this is that the KERN_ARND
414 sysctl only returns entropy if it thinks it has some to
415 share, and with RANDOM_DUMMY or no 'device random' this
419 An additional fix for the issue described in the 20150614 sendmail
420 entry below has been been committed in revision 284717.
423 FreeBSD's old make (fmake) has been removed from the system. It is
424 available as the devel/fmake port or via pkg install fmake.
427 The fix for the issue described in the 20150614 sendmail entry
428 below has been been committed in revision 284436. The work
429 around described in that entry is no longer needed unless the
430 default setting is overridden by a confDH_PARAMETERS configuration
431 setting of '5' or pointing to a 512 bit DH parameter file.
434 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
435 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
436 and devel/kyua to version 0.20+ and adjust any calling code to work
437 with Kyuafile and kyua.
440 The import of openssl to address the FreeBSD-SA-15:10.openssl
441 security advisory includes a change which rejects handshakes
442 with DH parameters below 768 bits. sendmail releases prior
443 to 8.15.2 (not yet released), defaulted to a 512 bit
444 DH parameter setting for client connections. To work around
445 this interoperability, sendmail can be configured to use a
446 2048 bit DH parameter by:
448 1. Edit /etc/mail/`hostname`.mc
449 2. If a setting for confDH_PARAMETERS does not exist or
450 exists and is set to a string beginning with '5',
452 3. If a setting for confDH_PARAMETERS exists and is set to
453 a file path, create a new file with:
454 openssl dhparam -out /path/to/file 2048
455 4. Rebuild the .cf file:
456 cd /etc/mail/; make; make install
458 cd /etc/mail/; make restart
460 A sendmail patch is coming, at which time this file will be
464 Generation of legacy formatted entries have been disabled by default
465 in pwd_mkdb(8), as all base system consumers of the legacy formatted
466 entries were converted to use the new format by default when the new,
467 machine independent format have been added and supported since FreeBSD
470 Please see the pwd_mkdb(8) manual page for further details.
473 Clang and llvm have been upgraded to 3.6.1 release. Please see the
474 20141231 entry below for information about prerequisites and upgrading,
475 if you are not already using 3.5.0 or higher.
478 TI platform code switched to using vendor DTS files and this update
479 may break existing systems running on Beaglebone, Beaglebone Black,
482 - dtb files should be regenerated/reinstalled. Filenames are the
483 same but content is different now
484 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
485 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
486 addressing scheme is now pin 25 on /dev/gpioc3.
487 - Pandaboard: /etc/ttys should be updated, serial console device is
488 now /dev/ttyu2, not /dev/ttyu0
491 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
492 If you need the GNU extension from groff soelim(1), install groff
493 from package: pkg install groff, or via ports: textproc/groff.
496 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
497 defined in symlink(7); previously symlinks were silently ignored.
500 The const qualifier has been removed from iconv(3) to comply with
501 POSIX. The ports tree is aware of this from r384038 onwards.
504 Libraries specified by LIBADD in Makefiles must have a corresponding
505 DPADD_<lib> variable to ensure correct dependencies. This is now
506 enforced in src.libnames.mk.
509 From legacy ata(4) driver was removed support for SATA controllers
510 supported by more functional drivers ahci(4), siis(4) and mvs(4).
511 Kernel modules ataahci and ataadaptec were removed completely,
512 replaced by ahci and mvs modules respectively.
515 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
516 the 20141231 entry below for information about prerequisites and
517 upgrading, if you are not already using 3.5.0 or higher.
520 The 32-bit PowerPC kernel has been changed to a position-independent
521 executable. This can only be booted with a version of loader(8)
522 newer than January 31, 2015, so make sure to update both world and
523 kernel before rebooting.
526 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
527 but before r278950, the RNG was not seeded properly. Immediately
528 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
529 ssh keys or openssl keys) that were generated w/ a kernel from that
530 range. This does not affect programs that directly used /dev/random
531 or /dev/urandom. All userland uses of arc4random(3) are affected.
534 The autofs(4) ABI was changed in order to restore binary compatibility
535 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
539 The powerpc64 kernel has been changed to a position-independent
540 executable. This can only be booted with a new version of loader(8),
541 so make sure to update both world and kernel before rebooting.
544 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
545 only release, no new features have been added. Please see the 20141231
546 entry below for information about prerequisites and upgrading, if you
547 are not already using 3.5.0.
550 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
551 taken from the ELF Tool Chain project rather than GNU binutils. They
552 should be drop-in replacements, with the addition of arm64 support.
553 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
554 binutils tools, if necessary. See 20150805 for updated information.
557 The default Unbound configuration now enables remote control
558 using a local socket. Users who have already enabled the
559 local_unbound service should regenerate their configuration
560 by running "service local_unbound setup" as root.
563 The GNU texinfo and GNU info pages have been removed.
564 To be able to view GNU info pages please install texinfo from ports.
567 Clang, llvm and lldb have been upgraded to 3.5.0 release.
569 As of this release, a prerequisite for building clang, llvm and lldb is
570 a C++11 capable compiler and C++11 standard library. This means that to
571 be able to successfully build the cross-tools stage of buildworld, with
572 clang as the bootstrap compiler, your system compiler or cross compiler
573 should either be clang 3.3 or later, or gcc 4.8 or later, and your
574 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
577 On any standard FreeBSD 10.x or 11.x installation, where clang and
578 libc++ are on by default (that is, on x86 or arm), this should work out
581 On 9.x installations where clang is enabled by default, e.g. on x86 and
582 powerpc, libc++ will not be enabled by default, so libc++ should be
583 built (with clang) and installed first. If both clang and libc++ are
584 missing, build clang first, then use it to build libc++.
586 On 8.x and earlier installations, upgrade to 9.x first, and then follow
587 the instructions for 9.x above.
589 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
590 default, and do not build clang.
592 Many embedded systems are resource constrained, and will not be able to
593 build clang in a reasonable time, or in some cases at all. In those
594 cases, cross building bootable systems on amd64 is a workaround.
596 This new version of clang introduces a number of new warnings, of which
597 the following are most likely to appear:
601 This warns in two cases, for both C and C++:
602 * When the code is trying to take the absolute value of an unsigned
603 quantity, which is effectively a no-op, and almost never what was
604 intended. The code should be fixed, if at all possible. If you are
605 sure that the unsigned quantity can be safely cast to signed, without
606 loss of information or undefined behavior, you can add an explicit
607 cast, or disable the warning.
609 * When the code is trying to take an absolute value, but the called
610 abs() variant is for the wrong type, which can lead to truncation.
611 If you want to disable the warning instead of fixing the code, please
612 make sure that truncation will not occur, or it might lead to unwanted
615 -Wtautological-undefined-compare and
616 -Wundefined-bool-conversion
618 These warn when C++ code is trying to compare 'this' against NULL, while
619 'this' should never be NULL in well-defined C++ code. However, there is
620 some legacy (pre C++11) code out there, which actively abuses this
621 feature, which was less strictly defined in previous C++ versions.
623 Squid and openjdk do this, for example. The warning can be turned off
624 for C++98 and earlier, but compiling the code in C++11 mode might result
625 in unexpected behavior; for example, the parts of the program that are
626 unreachable could be optimized away.
629 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
630 kernel sources have been removed. The .h files remain, since some
631 utilities include them. This will need to be fixed later.
632 If "mount -t oldnfs ..." is attempted, it will fail.
633 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
634 the utilities will report errors.
637 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
638 directories to top level SUBDIR variable when their parent
639 directory is included in LOCAL_DIRS. Users with build systems with
640 such hierarchies and without SUBDIR entries in the parent
641 directory Makefiles should add them or add the directories to
645 faith(4) and faithd(8) have been removed from the base system. Faith
646 has been obsolete for a very long time.
649 vt(4), the new console driver, is enabled by default. It brings
650 support for Unicode and double-width characters, as well as
651 support for UEFI and integration with the KMS kernel video
654 You may need to update your console settings in /etc/rc.conf,
655 most probably the keymap. During boot, /etc/rc.d/syscons will
656 indicate what you need to do.
658 vt(4) still has issues and lacks some features compared to
659 syscons(4). See the wiki for up-to-date information:
660 https://wiki.freebsd.org/Newcons
662 If you want to keep using syscons(4), you can do so by adding
663 the following line to /boot/loader.conf:
667 pjdfstest has been integrated into kyua as an opt-in test suite.
668 Please see share/doc/pjdfstest/README for more details on how to
672 gperf has been removed from the base system for architectures
673 that use clang. Ports that require gperf will obtain it from the
677 pjdfstest has been moved from tools/regression/pjdfstest to
681 At svn r271982, The default linux compat kernel ABI has been adjusted
682 to 2.6.18 in support of the linux-c6 compat ports infrastructure
683 update. If you wish to continue using the linux-f10 compat ports,
684 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
685 encouraged to update their linux-compat packages to linux-c6 during
686 their next update cycle.
689 The ofwfb driver, used to provide a graphics console on PowerPC when
690 using vt(4), no longer allows mmap() of all physical memory. This
691 will prevent Xorg on PowerPC with some ATI graphics cards from
692 initializing properly unless x11-servers/xorg-server is updated to
696 The xdev targets have been converted to using TARGET and
697 TARGET_ARCH instead of XDEV and XDEV_ARCH.
700 The default unbound configuration has been modified to address
701 issues with reverse lookups on networks that use private
702 address ranges. If you use the local_unbound service, run
703 "service local_unbound setup" as root to regenerate your
704 configuration, then "service local_unbound reload" to load the
708 The GNU texinfo and GNU info pages are not built and installed
709 anymore, WITH_INFO knob has been added to allow to built and install
711 UPDATE: see 20150102 entry on texinfo's removal
714 The GNU readline library is now an INTERNALLIB - that is, it is
715 statically linked into consumers (GDB and variants) in the base
716 system, and the shared library is no longer installed. The
717 devel/readline port is available for third party software that
721 The Itanium architecture (ia64) has been removed from the list of
722 known architectures. This is the first step in the removal of the
726 Commit r268115 has added NFSv4.1 server support, merged from
727 projects/nfsv4.1-server. Since this includes changes to the
728 internal interfaces between the NFS related modules, a full
729 build of the kernel and modules will be necessary.
730 __FreeBSD_version has been bumped.
733 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
734 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
735 which differs from the behaviour controlled by this knob.)
738 Maximal length of the serial number in CTL was increased from 16 to
739 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
740 and ctld, need to be rebuilt to work with a new kernel.
743 The libatf-c and libatf-c++ major versions were downgraded to 0 and
744 1 respectively to match the upstream numbers. They were out of
745 sync because, when they were originally added to FreeBSD, the
746 upstream versions were not respected. These libraries are private
747 and not yet built by default, so renumbering them should be a
748 non-issue. However, unclean source trees will yield broken test
749 programs once the operator executes "make delete-old-libs" after a
752 Additionally, the atf-sh binary was made private by moving it into
753 /usr/libexec/. Already-built shell test programs will keep the
754 path to the old binary so they will break after "make delete-old"
757 If you are using WITH_TESTS=yes (not the default), wipe the object
758 tree and rebuild from scratch to prevent spurious test failures.
759 This is only needed once: the misnumbered libraries and misplaced
760 binaries have been added to OptionalObsoleteFiles.inc so they will
761 be removed during a clean upgrade.
764 Clang and llvm have been upgraded to 3.4.1 release.
767 We bogusly installed src.opts.mk in /usr/share/mk. This file should
768 be removed to avoid issues in the future (and has been added to
772 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
773 past, it affected all builds that used the bsd.*.mk files. The old
774 behavior was a bug, but people may have relied upon it. To get this
775 behavior back, you can .include /etc/src.conf from /etc/make.conf
776 (which is still global and isn't changed). This also changes the
777 behavior of incremental builds inside the tree of individual
778 directories. Set MAKESYSPATH to ".../share/mk" to do that.
779 Although this has survived make universe and some upgrade scenarios,
780 other upgrade scenarios may have broken. At least one form of
781 temporary breakage was fixed with MAKESYSPATH settings for buildworld
782 as well... In cases where MAKESYSPATH isn't working with this
783 setting, you'll need to set it to the full path to your tree.
785 One side effect of all this cleaning up is that bsd.compiler.mk
786 is no longer implicitly included by bsd.own.mk. If you wish to
787 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
791 The lindev device has been removed since /dev/full has been made a
792 standard device. __FreeBSD_version has been bumped.
795 The knob WITHOUT_VI was added to the base system, which controls
796 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
797 in order to reorder files share/termcap and didn't build ex(1) as a
798 build tool, so building/installing with WITH_VI is highly advised for
799 build hosts for older releases.
801 This issue has been fixed in stable/9 and stable/10 in r277022 and
802 r276991, respectively.
805 The YES_HESIOD knob has been removed. It has been obsolete for
806 a decade. Please move to using WITH_HESIOD instead or your builds
807 will silently lack HESIOD.
810 The uart(4) driver has been changed with respect to its handling
811 of the low-level console. Previously the uart(4) driver prevented
812 any process from changing the baudrate or the CLOCAL and HUPCL
813 control flags. By removing the restrictions, operators can make
814 changes to the serial console port without having to reboot.
815 However, when getty(8) is started on the serial device that is
816 associated with the low-level console, a misconfigured terminal
817 line in /etc/ttys will now have a real impact.
818 Before upgrading the kernel, make sure that /etc/ttys has the
819 serial console device configured as 3wire without baudrate to
820 preserve the previous behaviour. E.g:
821 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
824 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
825 to improve performance. To re-enable it, if needed, run rpcbind
826 with command line option -W.
829 Switched back to the GPL dtc compiler due to updates in the upstream
830 dts files not being supported by the BSDL dtc compiler. You will need
831 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
832 may result while building dtb files during a kernel build if you fail
833 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
836 Clang and llvm have been upgraded to 3.4 release.
839 The nve(4) driver has been removed. Please use the nfe(4) driver
840 for NVIDIA nForce MCP Ethernet adapters instead.
843 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
844 This could cause certain C++ applications using shared libraries built
845 against the previous version of libc++ to crash. The incompatibility
846 has now been fixed, but any C++ applications or shared libraries built
847 between r261283 and r261801 should be recompiled.
850 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
851 capability mode support. Please note that enabling the feature in
852 kernel is still highly recommended.
855 OpenSSH is now built with sandbox support, and will use sandbox as
856 the default privilege separation method. This requires Capsicum
857 capability mode support in kernel.
860 The libelf and libdwarf libraries have been updated to newer
861 versions from upstream. Shared library version numbers for
862 these two libraries were bumped. Any ports or binaries
863 requiring these two libraries should be recompiled.
864 __FreeBSD_version is bumped to 1100006.
867 If a Makefile in a tests/ directory was auto-generating a Kyuafile
868 instead of providing an explicit one, this would prevent such
869 Makefile from providing its own Kyuafile in the future during
870 NO_CLEAN builds. This has been fixed in the Makefiles but manual
871 intervention is needed to clean an objdir if you use NO_CLEAN:
872 # find /usr/obj -name Kyuafile | xargs rm -f
875 The behavior of gss_pseudo_random() for the krb5 mechanism
876 has changed, for applications requesting a longer random string
877 than produced by the underlying enctype's pseudo-random() function.
878 In particular, the random string produced from a session key of
879 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
880 be different at the 17th octet and later, after this change.
881 The counter used in the PRF+ construction is now encoded as a
882 big-endian integer in accordance with RFC 4402.
883 __FreeBSD_version is bumped to 1100004.
886 The WITHOUT_ATF build knob has been removed and its functionality
887 has been subsumed into the more generic WITHOUT_TESTS. If you were
888 using the former to disable the build of the ATF libraries, you
889 should change your settings to use the latter.
892 The default version of mtree is nmtree which is obtained from
893 NetBSD. The output is generally the same, but may vary
894 slightly. If you found you need identical output adding
895 "-F freebsd9" to the command line should do the trick. For the
896 time being, the old mtree is available as fmtree.
899 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
900 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
901 1.1.4_8 and verify bsdyml not linked in, before running "make
903 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
905 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
908 The stable/10 branch has been created in subversion from head
912 The rc.d/jail script has been updated to support jail(8)
913 configuration file. The "jail_<jname>_*" rc.conf(5) variables
914 for per-jail configuration are automatically converted to
915 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
916 This is transparently backward compatible. See below about some
917 incompatibilities and rc.conf(5) manual page for more details.
919 These variables are now deprecated in favor of jail(8) configuration
920 file. One can use "rc.d/jail config <jname>" command to generate
921 a jail(8) configuration file in /var/run/jail.<jname>.conf without
922 running the jail(8) utility. The default pathname of the
923 configuration file is /etc/jail.conf and can be specified by
924 using $jail_conf or $jail_<jname>_conf variables.
926 Please note that jail_devfs_ruleset accepts an integer at
927 this moment. Please consider to rewrite the ruleset name
931 BIND has been removed from the base system. If all you need
932 is a local resolver, simply enable and start the local_unbound
933 service instead. Otherwise, several versions of BIND are
934 available in the ports tree. The dns/bind99 port is one example.
936 With this change, nslookup(1) and dig(1) are no longer in the base
937 system. Users should instead use host(1) and drill(1) which are
938 in the base system. Alternatively, nslookup and dig can
939 be obtained by installing the dns/bind-tools port.
942 With the addition of unbound(8), a new unbound user is now
943 required during installworld. "mergemaster -p" can be used to
944 add the user prior to installworld, as documented in the handbook.
947 OpenSSH is now built with DNSSEC support, and will by default
948 silently trust signed SSHFP records. This can be controlled with
949 the VerifyHostKeyDNS client configuration setting. DNSSEC support
950 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
953 The GNU Compiler Collection and C++ standard library (libstdc++)
954 are no longer built by default on platforms where clang is the system
955 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
959 The PROCDESC kernel option is now part of the GENERIC kernel
960 configuration and is required for the rwhod(8) to work.
961 If you are using custom kernel configuration, you should include
965 The API and ABI related to the Capsicum framework was modified
966 in backward incompatible way. The userland libraries and programs
967 have to be recompiled to work with the new kernel. This includes the
968 following libraries and programs, but the whole buildworld is
969 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
970 kdump, procstat, rwho, rwhod, uniq.
973 AES-NI intrinsic support has been added to gcc. The AES-NI module
974 has been updated to use this support. A new gcc is required to build
975 the aesni module on both i386 and amd64.
978 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
979 Thus "device padlock_rng" and "device rdrand_rng" should be
980 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
983 WITH_ICONV has been split into two feature sets. WITH_ICONV now
984 enables just the iconv* functionality and is now on by default.
985 WITH_LIBICONV_COMPAT enables the libiconv api and link time
986 compatibility. Set WITHOUT_ICONV to build the old way.
987 If you have been using WITH_ICONV before, you will very likely
988 need to turn on WITH_LIBICONV_COMPAT.
991 INVARIANTS option now enables DEBUG for code with OpenSolaris and
992 Illumos origin, including ZFS. If you have INVARIANTS in your
993 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
995 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
996 locks if WITNESS option was set. Because that generated a lot of
997 witness(9) reports and all of them were believed to be false
998 positives, this is no longer done. New option OPENSOLARIS_WITNESS
999 can be used to achieve the previous behavior.
1002 Timer values in IPv6 data structures now use time_uptime instead
1003 of time_second. Although this is not a user-visible functional
1004 change, userland utilities which directly use them---ndp(8),
1005 rtadvd(8), and rtsold(8) in the base system---need to be updated
1006 to r253970 or later.
1009 find -delete can now delete the pathnames given as arguments,
1010 instead of only files found below them or if the pathname did
1011 not contain any slashes. Formerly, the following error message
1014 find: -delete: <path>: relative path potentially not safe
1016 Deleting the pathnames given as arguments can be prevented
1017 without error messages using -mindepth 1 or by changing
1018 directory and passing "." as argument to find. This works in the
1019 old as well as the new version of find.
1022 Behavior of devfs rules path matching has been changed.
1023 Pattern is now always matched against fully qualified devfs
1024 path and slash characters must be explicitly matched by
1025 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1026 subdirectories must be reviewed.
1029 The default ARM ABI has changed to the ARM EABI. The old ABI is
1030 incompatible with the ARM EABI and all programs and modules will
1031 need to be rebuilt to work with a new kernel.
1033 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1035 NOTE: Support for the old ABI will be removed in the future and
1036 users are advised to upgrade.
1039 pkg_install has been disconnected from the build if you really need it
1040 you should add WITH_PKGTOOLS in your src.conf(5).
1043 Most of network statistics structures were changed to be able
1044 keep 64-bits counters. Thus all tools, that work with networking
1045 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1048 Fix a bug that allowed a tracing process (e.g. gdb) to write
1049 to a memory-mapped file in the traced process's address space
1050 even if neither the traced process nor the tracing process had
1051 write access to that file.
1054 CVS has been removed from the base system. An exact copy
1055 of the code is available from the devel/cvs port.
1058 Some people report the following error after the switch to bmake:
1060 make: illegal option -- J
1061 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1063 *** [buildworld] Error code 2
1065 this likely due to an old instance of make in
1066 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1067 which src/Makefile will use that blindly, if it exists, so if
1068 you see the above error:
1070 rm -rf `make -V MAKEPATH`
1075 Use bmake by default.
1076 Whereas before one could choose to build with bmake via
1077 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1078 make. The goal is to remove these knobs for 10-RELEASE.
1080 It is worth noting that bmake (like gmake) treats the command
1081 line as the unit of failure, rather than statements within the
1082 command line. Thus '(cd some/where && dosomething)' is safer
1083 than 'cd some/where; dosomething'. The '()' allows consistent
1084 behavior in parallel build.
1087 Fix a bug that allows NFS clients to issue READDIR on files.
1090 The WITHOUT_IDEA option has been removed because
1091 the IDEA patent expired.
1094 The sysctl which controls TRIM support under ZFS has been renamed
1095 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1099 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1100 rather than creating it's own in the temporary directory in
1101 order allow access to bootstrapped versions of tools such as
1102 install and mtree. When upgrading from version of FreeBSD where
1103 the install command does not support -l, you will need to
1104 install a new mergemaster command if mergemaster -p is required.
1105 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1109 Legacy ATA stack, disabled and replaced by new CAM-based one since
1110 FreeBSD 9.0, completely removed from the sources. Kernel modules
1111 atadisk and atapi*, user-level tools atacontrol and burncd are
1112 removed. Kernel option `options ATA_CAM` is now permanently enabled
1116 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1117 and socketpair(2). Software, in particular Kerberos, may
1118 automatically detect and use these during building. The resulting
1119 binaries will not work on older kernels.
1122 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1123 information, see the respective 20130304 entry).
1126 Recent commits to callout(9) changed the size of struct callout,
1127 so the KBI is probably heavily disturbed. Also, some functions
1128 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1129 by macros. Every kernel module using it won't load, so rebuild
1132 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1133 but does not initialize by default (because of the new CTL_DISABLE
1134 option) to save memory. To re-enable it, remove the CTL_DISABLE
1135 option from the kernel config file or set kern.cam.ctl.disable=0
1136 in /boot/loader.conf.
1139 The ctl device has been disabled in GENERIC for i386 and amd64.
1140 This was done due to the extra memory being allocated at system
1141 initialisation time by the ctl driver which was only used if
1142 a CAM target device was created. This makes a FreeBSD system
1143 unusable on 128MB or less of RAM.
1146 A new compression method (lz4) has been merged to -HEAD. Please
1147 refer to zpool-features(7) for more information.
1149 Please refer to the "ZFS notes" section of this file for information
1150 on upgrading boot ZFS pools.
1153 A BSD-licensed patch(1) variant has been added and is installed
1154 as bsdpatch, being the GNU version the default patch.
1155 To inverse the logic and use the BSD-licensed one as default,
1156 while having the GNU version installed as gnupatch, rebuild
1157 and install world with the WITH_BSD_PATCH knob set.
1160 Due to the use of the new -l option to install(1) during build
1161 and install, you must take care not to directly set the INSTALL
1162 make variable in your /etc/make.conf, /etc/src.conf, or on the
1163 command line. If you wish to use the -C flag for all installs
1164 you may be able to add INSTALL+=-C to /etc/make.conf or
1168 The install(1) option -M has changed meaning and now takes an
1169 argument that is a file or path to append logs to. In the
1170 unlikely event that -M was the last option on the command line
1171 and the command line contained at least two files and a target
1172 directory the first file will have logs appended to it. The -M
1173 option served little practical purpose in the last decade so its
1174 use is expected to be extremely rare.
1177 After switching to Clang as the default compiler some users of ZFS
1178 on i386 systems started to experience stack overflow kernel panics.
1179 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1182 GEOM_LABEL now mangles label names read from file system metadata.
1183 Mangling affect labels containing spaces, non-printable characters,
1184 '%' or '"'. Device names in /etc/fstab and other places may need to
1188 By default, only the 10 most recent kernel dumps will be saved. To
1189 restore the previous behaviour (no limit on the number of kernel dumps
1190 stored in the dump directory) add the following line to /etc/rc.conf:
1195 With the addition of auditdistd(8), a new auditdistd user is now
1196 required during installworld. "mergemaster -p" can be used to
1197 add the user prior to installworld, as documented in the handbook.
1200 The sin6_scope_id member variable in struct sockaddr_in6 is now
1201 filled by the kernel before passing the structure to the userland via
1202 sysctl or routing socket. This means the KAME-specific embedded scope
1203 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1204 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1205 __FreeBSD_version is bumped to 1000025.
1208 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1209 This means that the world and kernel will be compiled with clang
1210 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1211 and /usr/bin/cpp. To disable this behavior and revert to building
1212 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1213 of current may need to bootstrap WITHOUT_CLANG first if the clang
1214 build fails (its compatibility window doesn't extend to the 9 stable
1218 The IPFIREWALL_FORWARD kernel option has been removed. Its
1219 functionality now turned on by default.
1222 The ZERO_COPY_SOCKET kernel option has been removed and
1223 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1224 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1225 mechanism which is not safe and may result in kernel crashes.
1226 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1227 driver supports disposeable external page sized mbuf storage.
1228 Proper replacements for both zero-copy mechanisms are under
1229 consideration and will eventually lead to complete removal
1230 of the two kernel options.
1233 The IPv4 network stack has been converted to network byte
1234 order. The following modules need to be recompiled together
1235 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1236 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1239 Support for non-MPSAFE filesystems was removed from VFS. The
1240 VFS_VERSION was bumped, all filesystem modules shall be
1244 All the non-MPSAFE filesystems have been disconnected from
1245 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1246 portalfs, smbfs, xfs.
1249 The interface cloning API and ABI has changed. The following
1250 modules need to be recompiled together with kernel:
1251 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1252 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1253 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1256 The sdhci driver was split in two parts: sdhci (generic SD Host
1257 Controller logic) and sdhci_pci (actual hardware driver).
1258 No kernel config modifications are required, but if you
1259 load sdhc as a module you must switch to sdhci_pci instead.
1262 Import the FUSE kernel and userland support into base system.
1265 The GNU sort(1) program has been removed since the BSD-licensed
1266 sort(1) has been the default for quite some time and no serious
1267 problems have been reported. The corresponding WITH_GNU_SORT
1271 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1272 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1276 The net80211(4) ABI has been changed to allow for improved driver
1277 PS-POLL and power-save support. All wireless drivers need to be
1278 recompiled to work with the new kernel.
1281 The random(4) support for the VIA hardware random number
1282 generator (`PADLOCK') is no longer enabled unconditionally.
1283 Add the padlock_rng device in the custom kernel config if
1284 needed. The GENERIC kernels on i386 and amd64 do include the
1285 device, so the change only affects the custom kernel
1289 The pf(4) packet filter ABI has been changed. pfctl(8) and
1290 snmp_pf module need to be recompiled to work with new kernel.
1293 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1294 to -HEAD. Pools that have empty_bpobj in active state can not be
1295 imported read-write with ZFS implementations that do not support
1296 this feature. For more information read the zpool-features(5)
1300 The sparc64 ZFS loader has been changed to no longer try to auto-
1301 detect ZFS providers based on diskN aliases but now requires these
1302 to be explicitly listed in the OFW boot-device environment variable.
1305 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1306 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1307 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1310 The following sysctls and tunables have been renamed for consistency
1311 with other variables:
1312 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1313 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1316 The sort utility has been replaced with BSD sort. For now, GNU sort
1317 is also available as "gnusort" or the default can be set back to
1318 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1319 installed as "bsdsort".
1322 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1323 Starting with this version the old system of ZFS pool versioning
1324 is superseded by "feature flags". This concept enables forward
1325 compatibility against certain future changes in functionality of ZFS
1326 pools. The first read-only compatible "feature flag" for ZFS pools
1327 is named "com.delphix:async_destroy". For more information
1328 read the new zpool-features(5) manual page.
1329 Please refer to the "ZFS notes" section of this file for information
1330 on upgrading boot ZFS pools.
1333 The malloc(3) implementation embedded in libc now uses sources imported
1334 as contrib/jemalloc. The most disruptive API change is to
1335 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1336 delete it prior to installworld, and optionally re-create it using the
1337 new format after rebooting. See malloc.conf(5) for details
1338 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1342 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1343 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1344 now spelled mips. This is to aid compatibility with third-party
1345 software that expects this naming scheme in uname(3). Little-endian
1346 settings are unchanged. If you are updating a big-endian mips64 machine
1347 from before this change, you may need to set MACHINE_ARCH=mips64 in
1348 your environment before the new build system will recognize your machine.
1351 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1355 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1356 nullfs(5) did not pass through all behaviours to the underlying layer,
1357 as a result if we bound to a socket on the lower layer we could connect
1358 only to the lower path; if we bound to the upper layer we could connect
1359 only to the upper path. The new behavior is one can connect to both the
1360 lower and the upper paths regardless what layer path one binds to.
1363 The getifaddrs upgrade path broken with 20111215 has been restored.
1364 If you have upgraded in between 20111215 and 20120209 you need to
1365 recompile libc again with your kernel. You still need to recompile
1366 world to be able to configure CARP but this restriction already
1367 comes from 20111215.
1370 The set_rcvar() function has been removed from /etc/rc.subr. All
1371 base and ports rc.d scripts have been updated, so if you have a
1372 port installed with a script in /usr/local/etc/rc.d you can either
1373 hand-edit the rcvar= line, or reinstall the port.
1375 An easy way to handle the mass-update of /etc/rc.d:
1376 rm /etc/rc.d/* && mergemaster -i
1379 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1380 on the current CPU and prevents other threads from running.
1381 This behavior can be reverted using the kern.stop_scheduler_on_panic
1383 The new behavior can be incompatible with kern.sync_on_panic.
1386 The carp(4) facility has been changed significantly. Configuration
1387 of the CARP protocol via ifconfig(8) has changed, as well as format
1388 of CARP events submitted to devd(8) has changed. See manual pages
1389 for more information. The arpbalance feature of carp(4) is currently
1390 not supported anymore.
1392 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1393 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1394 need to be recompiled.
1397 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1401 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1402 explicitely support non-MPSAFE filesystems.
1403 It is on by default for all supported platform at this present
1407 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1408 i386 and pc98 GENERIC kernel configuration files.
1411 sysinstall has been removed
1414 The stable/9 branch created in subversion. This corresponds to the
1415 RELENG_9 branch in CVS.
1421 Avoid using make -j when upgrading. While generally safe, there are
1422 sometimes problems using -j to upgrade. If your upgrade fails with
1423 -j, please try again without -j. From time to time in the past there
1424 have been problems using -j with buildworld and/or installworld. This
1425 is especially true when upgrading between "distant" versions (eg one
1426 that cross a major release boundary or several minor releases, or when
1427 several months have passed on the -current branch).
1429 Sometimes, obscure build problems are the result of environment
1430 poisoning. This can happen because the make utility reads its
1431 environment when searching for values for global variables. To run
1432 your build attempts in an "environmental clean room", prefix all make
1433 commands with 'env -i '. See the env(1) manual page for more details.
1435 When upgrading from one major version to another it is generally best
1436 to upgrade to the latest code in the currently installed branch first,
1437 then do an upgrade to the new branch. This is the best-tested upgrade
1438 path, and has the highest probability of being successful. Please try
1439 this approach before reporting problems with a major version upgrade.
1441 When upgrading a live system, having a root shell around before
1442 installing anything can help undo problems. Not having a root shell
1443 around can lead to problems if pam has changed too much from your
1444 starting point to allow continued authentication after the upgrade.
1446 This file should be read as a log of events. When a later event changes
1447 information of a prior event, the prior event should not be deleted.
1448 Instead, a pointer to the entry with the new information should be
1449 placed in the old entry. Readers of this file should also sanity check
1450 older entries before relying on them blindly. Authors of new entries
1451 should write them with this in mind.
1455 When upgrading the boot ZFS pool to a new version, always follow
1458 1.) recompile and reinstall the ZFS boot loader and boot block
1459 (this is part of "make buildworld" and "make installworld")
1461 2.) update the ZFS boot block on your boot drive
1463 The following example updates the ZFS boot block on the first
1464 partition (freebsd-boot) of a GPT partitioned drive ada0:
1465 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1467 Non-boot pools do not need these updates.
1471 If you are updating from a prior version of FreeBSD (even one just
1472 a few days old), you should follow this procedure. It is the most
1473 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1475 make kernel-toolchain
1476 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1477 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1479 To test a kernel once
1480 ---------------------
1481 If you just want to boot a kernel once (because you are not sure
1482 if it works, or if you want to boot a known bad kernel to provide
1483 debugging information) run
1484 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1485 nextboot -k testkernel
1487 To just build a kernel when you know that it won't mess you up
1488 --------------------------------------------------------------
1489 This assumes you are already running a CURRENT system. Replace
1490 ${arch} with the architecture of your machine (e.g. "i386",
1491 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1493 cd src/sys/${arch}/conf
1494 config KERNEL_NAME_HERE
1495 cd ../compile/KERNEL_NAME_HERE
1500 If this fails, go to the "To build a kernel" section.
1502 To rebuild everything and install it on the current system.
1503 -----------------------------------------------------------
1504 # Note: sometimes if you are running current you gotta do more than
1505 # is listed here if you are upgrading from a really old current.
1507 <make sure you have good level 0 dumps>
1509 make kernel KERNCONF=YOUR_KERNEL_HERE
1511 <reboot in single user> [3]
1518 To cross-install current onto a separate partition
1519 --------------------------------------------------
1520 # In this approach we use a separate partition to hold
1521 # current's root, 'usr', and 'var' directories. A partition
1522 # holding "/", "/usr" and "/var" should be about 2GB in
1525 <make sure you have good level 0 dumps>
1528 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1529 <maybe newfs current's root partition>
1530 <mount current's root partition on directory ${CURRENT_ROOT}>
1531 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1532 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1533 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1534 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1535 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1536 <reboot into current>
1537 <do a "native" rebuild/install as described in the previous section>
1538 <maybe install compatibility libraries from ports/misc/compat*>
1542 To upgrade in-place from stable to current
1543 ----------------------------------------------
1544 <make sure you have good level 0 dumps>
1546 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1548 <reboot in single user> [3]
1555 Make sure that you've read the UPDATING file to understand the
1556 tweaks to various things you need. At this point in the life
1557 cycle of current, things change often and you are on your own
1558 to cope. The defaults can also change, so please read ALL of
1559 the UPDATING entries.
1561 Also, if you are tracking -current, you must be subscribed to
1562 freebsd-current@freebsd.org. Make sure that before you update
1563 your sources that you have read and understood all the recent
1564 messages there. If in doubt, please track -stable which has
1565 much fewer pitfalls.
1567 [1] If you have third party modules, such as vmware, you
1568 should disable them at this point so they don't crash your
1571 [3] From the bootblocks, boot -s, and then do
1576 adjkerntz -i # if CMOS is wall time
1577 Also, when doing a major release upgrade, it is required that
1578 you boot into single user mode to do the installworld.
1580 [4] Note: This step is non-optional. Failure to do this step
1581 can result in a significant reduction in the functionality of the
1582 system. Attempting to do it by hand is not recommended and those
1583 that pursue this avenue should read this file carefully, as well
1584 as the archives of freebsd-current and freebsd-hackers mailing lists
1585 for potential gotchas. The -U option is also useful to consider.
1586 See mergemaster(8) for more information.
1588 [5] Usually this step is a noop. However, from time to time
1589 you may need to do this if you get unknown user in the following
1590 step. It never hurts to do it all the time. You may need to
1591 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1592 install) after the buildworld before this step if you last updated
1593 from current before 20130425 or from -stable before 20130430.
1595 [6] This only deletes old files and directories. Old libraries
1596 can be deleted by "make delete-old-libs", but you have to make
1597 sure that no program is using those libraries anymore.
1599 [8] In order to have a kernel that can run the 4.x binaries needed to
1600 do an installworld, you must include the COMPAT_FREEBSD4 option in
1601 your kernel. Failure to do so may leave you with a system that is
1602 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1603 required to run the 5.x binaries on more recent kernels. And so on
1604 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1606 Make sure that you merge any new devices from GENERIC since the
1607 last time you updated your kernel config file.
1609 [9] When checking out sources, you must include the -P flag to have
1610 cvs prune empty directories.
1612 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1613 "?=" instead of the "=" assignment operator, so that buildworld can
1614 override the CPUTYPE if it needs to.
1616 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1617 not on the command line, or in /etc/make.conf. buildworld will
1618 warn if it is improperly defined.
1621 This file contains a list, in reverse chronological order, of major
1622 breakages in tracking -current. It is not guaranteed to be a complete
1623 list of such breakages, and only contains entries since September 23, 2011.
1624 If you need to see UPDATING entries from before that date, you will need
1625 to fetch an UPDATING file from an older FreeBSD release.
1627 Copyright information:
1629 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1631 Redistribution, publication, translation and use, with or without
1632 modification, in full or in part, in any form or format of this
1633 document are permitted without further permission from the author.
1635 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1636 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1637 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1638 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1639 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1640 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1641 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1642 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1643 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1644 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1645 POSSIBILITY OF SUCH DAMAGE.
1647 Contact Warner Losh if you have any questions about your use of