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.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 r304787 changed some ioctl interfaces between the iSCSI userspace
36 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
37 rebuilt to work with new kernels. __FreeBSD_version has been bumped
41 The UDP receive code has been updated to only treat incoming UDP
42 packets that were addressed to an L2 broadcast address as L3
43 broadcast packets. It is not expected that this will affect any
44 standards-conforming UDP application. The new behaviour can be
45 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
49 Remove the openbsd_poll system call.
50 __FreeBSD_version has been bumped because of this.
53 The libc stub for the pipe(2) system call has been replaced with
54 a wrapper that calls the pipe2(2) system call and the pipe(2)
55 system call is now only implemented by the kernels that include
56 "options COMPAT_FREEBSD10" in their config file (this is the
57 default). Users should ensure that this option is enabled in
58 their kernel or upgrade userspace to r302092 before upgrading their
62 CAM will now strip leading spaces from SCSI disks' serial numbers.
63 This will effect users who create UFS filesystems on SCSI disks using
64 those disk's diskid device nodes. For example, if /etc/fstab
65 previously contained a line like
66 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
67 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
68 transforms like gmirror may also be affected. ZFS users should
72 The bitstring(3) API has been updated with new functionality and
73 improved performance. But it is binary-incompatible with the old API.
74 Objects built with the new headers may not be linked against objects
75 built with the old headers.
78 The brk and sbrk functions have been removed from libc on arm64.
79 Binutils from ports has been updated to not link to these
80 functions and should be updated to the latest version before
81 installing a new libc.
84 The armv6 port now defaults to hard float ABI. Limited support
85 for running both hardfloat and soft float on the same system
86 is available using the libraries installed with -DWITH_LIBSOFT.
87 This has only been tested as an upgrade path for installworld
88 and packages may fail or need manual intervention to run. New
89 packages will be needed.
91 To update an existing self-hosted armv6hf system, you must add
92 TARGET_ARCH=armv6 on the make command line for both the build
93 and the install steps.
96 Kernel modules compiled outside of a kernel build now default to
97 installing to /boot/modules instead of /boot/kernel. Many kernel
98 modules built this way (such as those in ports) already overrode
99 KMODDIR explicitly to install into /boot/modules. However,
100 manually building and installing a module from /sys/modules will
101 now install to /boot/modules instead of /boot/kernel.
104 The CAM I/O scheduler has been committed to the kernel. There should be
105 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
106 list of known rogues that claim support for this but actually corrupt
107 data is believed to be complete, be on the lookout for data
108 corruption. The known rogue list is believed to be complete:
110 o Crucial MX100, M550 drives with MU01 firmware.
111 o Micron M510 and M550 drives with MU01 firmware.
112 o Micron M500 prior to MU07 firmware
113 o Samsung 830, 840, and 850 all firmwares
114 o FCCT M500 all firmwares
116 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
117 with working NCQ TRIM. For Micron branded drives, see your sales rep for
118 updated firmware. Black listed drives will work correctly because these
119 drives work correctly so long as no NCQ TRIMs are sent to them. Given
120 this list is the same as found in Linux, it's believed there are no
121 other rogues in the market place. All other models from the above
124 To be safe, if you are at all concerned, you can quirk each of your
125 drives to prevent NCQ from being sent by setting:
126 kern.cam.ada.X.quirks="0x2"
127 in loader.conf. If the drive requires the 4k sector quirk, set the
131 The FAST_DEPEND build option has been removed and its functionality is
132 now the one true way. The old mkdep(1) style of 'make depend' has
133 been removed. See 20160311 for further details.
136 Resource range types have grown from unsigned long to uintmax_t. All
137 drivers, and anything using libdevinfo, need to be recompiled.
140 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
141 builds. It no longer runs mkdep(1) during 'make depend', and the
142 'make depend' stage can safely be skipped now as it is auto ran
143 when building 'make all' and will generate all SRCS and DPSRCS before
144 building anything else. Dependencies are gathered at compile time with
145 -MF flags kept in separate .depend files per object file. Users should
146 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
150 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
151 kernel modules. Therefore, if you load any kernel modules at boot time,
152 please install the boot loaders after you install the kernel, but before
156 make kernel KERNCONF=YOUR_KERNEL_HERE
157 make -C sys/boot install
158 <reboot in single user>
160 Then follow the usual steps, described in the General Notes section,
164 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
165 see the 20141231 entry below for information about prerequisites and
166 upgrading, if you are not already using clang 3.5.0 or higher.
169 The AIO subsystem is now a standard part of the kernel. The
170 VFS_AIO kernel option and aio.ko kernel module have been removed.
171 Due to stability concerns, asynchronous I/O requests are only
172 permitted on sockets and raw disks by default. To enable
173 asynchronous I/O requests on all file types, set the
174 vfs.aio.enable_unsafe sysctl to a non-zero value.
177 The ELF object manipulation tool objcopy is now provided by the
178 ELF Tool Chain project rather than by GNU binutils. It should be a
179 drop-in replacement, with the addition of arm64 support. The
180 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
181 to obtain the GNU version if necessary.
184 Building ZFS pools on top of zvols is prohibited by default. That
185 feature has never worked safely; it's always been prone to deadlocks.
186 Using a zvol as the backing store for a VM guest's virtual disk will
187 still work, even if the guest is using ZFS. Legacy behavior can be
188 restored by setting vfs.zfs.vol.recursive=1.
191 The NONE and HPN patches has been removed from OpenSSH. They are
192 still available in the security/openssh-portable port.
195 With the addition of ypldap(8), a new _ypldap user is now required
196 during installworld. "mergemaster -p" can be used to add the user
197 prior to installworld, as documented in the handbook.
200 The tftp loader (pxeboot) now uses the option root-path directive. As a
201 consequence it no longer looks for a pxeboot.4th file on the tftp
202 server. Instead it uses the regular /boot infrastructure as with the
206 The code to start recording plug and play data into the modules has
207 been committed. While the old tools will properly build a new kernel,
208 a number of warnings about "unknown metadata record 4" will be produced
209 for an older kldxref. To avoid such warnings, make sure to rebuild
210 the kernel toolchain (or world). Make sure that you have r292078 or
211 later when trying to build 292077 or later before rebuilding.
214 Debug data files are now built by default with 'make buildworld' and
215 installed with 'make installworld'. This facilitates debugging but
216 requires more disk space both during the build and for the installed
217 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
221 r291527 changed the internal interface between the nfsd.ko and
222 nfscommon.ko modules. As such, they must both be upgraded to-gether.
223 __FreeBSD_version has been bumped because of this.
226 Add support for unicode collation strings leads to a change of
227 order of files listed by ls(1) for example. To get back to the old
228 behaviour, set LC_COLLATE environment variable to "C".
230 Databases administrators will need to reindex their databases given
231 collation results will be different.
233 Due to a bug in install(1) it is recommended to remove the ancient
234 locales before running make installworld.
236 rm -rf /usr/share/locale/*
239 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
240 libcrypto.so.7 or libssl.so.7 must be recompiled.
243 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
244 Kernel modules isp_2400_multi and isp_2500_multi were removed and
245 should be replaced with isp_2400 and isp_2500 modules respectively.
248 The build previously allowed using 'make -n' to not recurse into
249 sub-directories while showing what commands would be executed, and
250 'make -n -n' to recursively show commands. Now 'make -n' will recurse
251 and 'make -N' will not.
254 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
255 and etcupdate will now use this file. A custom sendmail.cf is now
256 updated via this mechanism rather than via installworld. If you had
257 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
258 want to remove the exclusion or change it to "always install".
259 /etc/mail/sendmail.cf is now managed the same way regardless of
260 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
261 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
264 Compatibility shims for legacy ATA device names have been removed.
265 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
266 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
267 environment variables, /dev/ad* and /dev/ar* symbolic links.
270 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
271 Please see the 20141231 entry below for information about prerequisites
272 and upgrading, if you are not already using clang 3.5.0 or higher.
275 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
276 and renamed from .symbols to .debug. This reduces the size requirements
277 on the boot partition or file system and provides consistency with
278 userland debug files.
280 When using the supported kernel installation method the
281 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
282 as is done with /boot/kernel.
284 Developers wishing to maintain the historical behavior of installing
285 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
288 The wireless drivers had undergone changes that remove the 'parent
289 interface' from the ifconfig -l output. The rc.d network scripts
290 used to check presence of a parent interface in the list, so old
291 scripts would fail to start wireless networking. Thus, etcupdate(3)
292 or mergemaster(8) run is required after kernel update, to update your
293 rc.d scripts in /etc.
296 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
297 These configurations are now automatically interpreted as
298 'scrub fragment reassemble'.
301 Kernel-loadable modules for the random(4) device are back. To use
302 them, the kernel must have
305 options RANDOM_LOADABLE
307 kldload(8) can then be used to load random_fortuna.ko
308 or random_yarrow.ko. Please note that due to the indirect
309 function calls that the loadable modules need to provide,
310 the build-in variants will be slightly more efficient.
312 The random(4) kernel option RANDOM_DUMMY has been retired due to
313 unpopularity. It was not all that useful anyway.
316 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
317 Control over building the ELF Tool Chain tools is now provided by
318 the WITHOUT_TOOLCHAIN knob.
321 The polarity of Pulse Per Second (PPS) capture events with the
322 uart(4) driver has been corrected. Prior to this change the PPS
323 "assert" event corresponded to the trailing edge of a positive PPS
324 pulse and the "clear" event was the leading edge of the next pulse.
326 As the width of a PPS pulse in a typical GPS receiver is on the
327 order of 1 millisecond, most users will not notice any significant
328 difference with this change.
330 Anyone who has compensated for the historical polarity reversal by
331 configuring a negative offset equal to the pulse width will need to
332 remove that workaround.
335 The default group assigned to /dev/dri entries has been changed
336 from 'wheel' to 'video' with the id of '44'. If you want to have
337 access to the dri devices please add yourself to the video group
340 # pw groupmod video -m $USER
343 The menu.rc and loader.rc files will now be replaced during
344 upgrades. Please migrate local changes to menu.rc.local and
345 loader.rc.local instead.
348 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
349 strings and strip have been removed. The src.conf(5) knob
350 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
353 As ZFS requires more kernel stack pages than is the default on some
354 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
355 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
357 Please consider using 'options KSTACK_PAGES=X' where X is greater
358 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
361 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
362 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
363 default, i.e., they will not contain "::". For example, instead
364 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
365 to have a more specific match, such as different map entries for
366 IPv6:0:0 vs IPv6:0. This change requires that configuration
367 data (including maps, files, classes, custom ruleset, etc.) must
368 use the same format, so make certain such configuration data is
369 upgrading. As a very simple check search for patterns like
370 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
371 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
372 the cf option UseCompressedIPv6Addresses.
375 The default kernel entropy-processing algorithm is now
376 Fortuna, replacing Yarrow.
378 Assuming you have 'device random' in your kernel config
379 file, the configurations allow a kernel option to override
380 this default. You may choose *ONE* of:
382 options RANDOM_YARROW # Legacy /dev/random algorithm.
383 options RANDOM_DUMMY # Blocking-only driver.
385 If you have neither, you get Fortuna. For most people,
386 read no further, Fortuna will give a /dev/random that works
387 like it always used to, and the difference will be irrelevant.
389 If you remove 'device random', you get *NO* kernel-processed
390 entropy at all. This may be acceptable to folks building
391 embedded systems, but has complications. Carry on reading,
392 and it is assumed you know what you need.
394 *PLEASE* read random(4) and random(9) if you are in the
395 habit of tweaking kernel configs, and/or if you are a member
396 of the embedded community, wanting specific and not-usual
397 behaviour from your security subsystems.
399 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
400 random', you will NOT have a functioning /dev/random, and
401 many cryptographic features will not work, including SSH.
402 You may also find strange behaviour from the random(3) set
403 of library functions, in particular sranddev(3), srandomdev(3)
404 and arc4random(3). The reason for this is that the KERN_ARND
405 sysctl only returns entropy if it thinks it has some to
406 share, and with RANDOM_DUMMY or no 'device random' this
410 An additional fix for the issue described in the 20150614 sendmail
411 entry below has been been committed in revision 284717.
414 FreeBSD's old make (fmake) has been removed from the system. It is
415 available as the devel/fmake port or via pkg install fmake.
418 The fix for the issue described in the 20150614 sendmail entry
419 below has been been committed in revision 284436. The work
420 around described in that entry is no longer needed unless the
421 default setting is overridden by a confDH_PARAMETERS configuration
422 setting of '5' or pointing to a 512 bit DH parameter file.
425 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
426 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
427 and devel/kyua to version 0.20+ and adjust any calling code to work
428 with Kyuafile and kyua.
431 The import of openssl to address the FreeBSD-SA-15:10.openssl
432 security advisory includes a change which rejects handshakes
433 with DH parameters below 768 bits. sendmail releases prior
434 to 8.15.2 (not yet released), defaulted to a 512 bit
435 DH parameter setting for client connections. To work around
436 this interoperability, sendmail can be configured to use a
437 2048 bit DH parameter by:
439 1. Edit /etc/mail/`hostname`.mc
440 2. If a setting for confDH_PARAMETERS does not exist or
441 exists and is set to a string beginning with '5',
443 3. If a setting for confDH_PARAMETERS exists and is set to
444 a file path, create a new file with:
445 openssl dhparam -out /path/to/file 2048
446 4. Rebuild the .cf file:
447 cd /etc/mail/; make; make install
449 cd /etc/mail/; make restart
451 A sendmail patch is coming, at which time this file will be
455 Generation of legacy formatted entries have been disabled by default
456 in pwd_mkdb(8), as all base system consumers of the legacy formatted
457 entries were converted to use the new format by default when the new,
458 machine independent format have been added and supported since FreeBSD
461 Please see the pwd_mkdb(8) manual page for further details.
464 Clang and llvm have been upgraded to 3.6.1 release. Please see the
465 20141231 entry below for information about prerequisites and upgrading,
466 if you are not already using 3.5.0 or higher.
469 TI platform code switched to using vendor DTS files and this update
470 may break existing systems running on Beaglebone, Beaglebone Black,
473 - dtb files should be regenerated/reinstalled. Filenames are the
474 same but content is different now
475 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
476 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
477 addressing scheme is now pin 25 on /dev/gpioc3.
478 - Pandaboard: /etc/ttys should be updated, serial console device is
479 now /dev/ttyu2, not /dev/ttyu0
482 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
483 If you need the GNU extension from groff soelim(1), install groff
484 from package: pkg install groff, or via ports: textproc/groff.
487 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
488 defined in symlink(7); previously symlinks were silently ignored.
491 The const qualifier has been removed from iconv(3) to comply with
492 POSIX. The ports tree is aware of this from r384038 onwards.
495 Libraries specified by LIBADD in Makefiles must have a corresponding
496 DPADD_<lib> variable to ensure correct dependencies. This is now
497 enforced in src.libnames.mk.
500 From legacy ata(4) driver was removed support for SATA controllers
501 supported by more functional drivers ahci(4), siis(4) and mvs(4).
502 Kernel modules ataahci and ataadaptec were removed completely,
503 replaced by ahci and mvs modules respectively.
506 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
507 the 20141231 entry below for information about prerequisites and
508 upgrading, if you are not already using 3.5.0 or higher.
511 The 32-bit PowerPC kernel has been changed to a position-independent
512 executable. This can only be booted with a version of loader(8)
513 newer than January 31, 2015, so make sure to update both world and
514 kernel before rebooting.
517 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
518 but before r278950, the RNG was not seeded properly. Immediately
519 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
520 ssh keys or openssl keys) that were generated w/ a kernel from that
521 range. This does not affect programs that directly used /dev/random
522 or /dev/urandom. All userland uses of arc4random(3) are affected.
525 The autofs(4) ABI was changed in order to restore binary compatibility
526 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
530 The powerpc64 kernel has been changed to a position-independent
531 executable. This can only be booted with a new version of loader(8),
532 so make sure to update both world and kernel before rebooting.
535 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
536 only release, no new features have been added. Please see the 20141231
537 entry below for information about prerequisites and upgrading, if you
538 are not already using 3.5.0.
541 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
542 taken from the ELF Tool Chain project rather than GNU binutils. They
543 should be drop-in replacements, with the addition of arm64 support.
544 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
545 binutils tools, if necessary. See 20150805 for updated information.
548 The default Unbound configuration now enables remote control
549 using a local socket. Users who have already enabled the
550 local_unbound service should regenerate their configuration
551 by running "service local_unbound setup" as root.
554 The GNU texinfo and GNU info pages have been removed.
555 To be able to view GNU info pages please install texinfo from ports.
558 Clang, llvm and lldb have been upgraded to 3.5.0 release.
560 As of this release, a prerequisite for building clang, llvm and lldb is
561 a C++11 capable compiler and C++11 standard library. This means that to
562 be able to successfully build the cross-tools stage of buildworld, with
563 clang as the bootstrap compiler, your system compiler or cross compiler
564 should either be clang 3.3 or later, or gcc 4.8 or later, and your
565 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
568 On any standard FreeBSD 10.x or 11.x installation, where clang and
569 libc++ are on by default (that is, on x86 or arm), this should work out
572 On 9.x installations where clang is enabled by default, e.g. on x86 and
573 powerpc, libc++ will not be enabled by default, so libc++ should be
574 built (with clang) and installed first. If both clang and libc++ are
575 missing, build clang first, then use it to build libc++.
577 On 8.x and earlier installations, upgrade to 9.x first, and then follow
578 the instructions for 9.x above.
580 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
581 default, and do not build clang.
583 Many embedded systems are resource constrained, and will not be able to
584 build clang in a reasonable time, or in some cases at all. In those
585 cases, cross building bootable systems on amd64 is a workaround.
587 This new version of clang introduces a number of new warnings, of which
588 the following are most likely to appear:
592 This warns in two cases, for both C and C++:
593 * When the code is trying to take the absolute value of an unsigned
594 quantity, which is effectively a no-op, and almost never what was
595 intended. The code should be fixed, if at all possible. If you are
596 sure that the unsigned quantity can be safely cast to signed, without
597 loss of information or undefined behavior, you can add an explicit
598 cast, or disable the warning.
600 * When the code is trying to take an absolute value, but the called
601 abs() variant is for the wrong type, which can lead to truncation.
602 If you want to disable the warning instead of fixing the code, please
603 make sure that truncation will not occur, or it might lead to unwanted
606 -Wtautological-undefined-compare and
607 -Wundefined-bool-conversion
609 These warn when C++ code is trying to compare 'this' against NULL, while
610 'this' should never be NULL in well-defined C++ code. However, there is
611 some legacy (pre C++11) code out there, which actively abuses this
612 feature, which was less strictly defined in previous C++ versions.
614 Squid and openjdk do this, for example. The warning can be turned off
615 for C++98 and earlier, but compiling the code in C++11 mode might result
616 in unexpected behavior; for example, the parts of the program that are
617 unreachable could be optimized away.
620 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
621 kernel sources have been removed. The .h files remain, since some
622 utilities include them. This will need to be fixed later.
623 If "mount -t oldnfs ..." is attempted, it will fail.
624 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
625 the utilities will report errors.
628 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
629 directories to top level SUBDIR variable when their parent
630 directory is included in LOCAL_DIRS. Users with build systems with
631 such hierarchies and without SUBDIR entries in the parent
632 directory Makefiles should add them or add the directories to
636 faith(4) and faithd(8) have been removed from the base system. Faith
637 has been obsolete for a very long time.
640 vt(4), the new console driver, is enabled by default. It brings
641 support for Unicode and double-width characters, as well as
642 support for UEFI and integration with the KMS kernel video
645 You may need to update your console settings in /etc/rc.conf,
646 most probably the keymap. During boot, /etc/rc.d/syscons will
647 indicate what you need to do.
649 vt(4) still has issues and lacks some features compared to
650 syscons(4). See the wiki for up-to-date information:
651 https://wiki.freebsd.org/Newcons
653 If you want to keep using syscons(4), you can do so by adding
654 the following line to /boot/loader.conf:
658 pjdfstest has been integrated into kyua as an opt-in test suite.
659 Please see share/doc/pjdfstest/README for more details on how to
663 gperf has been removed from the base system for architectures
664 that use clang. Ports that require gperf will obtain it from the
668 pjdfstest has been moved from tools/regression/pjdfstest to
672 At svn r271982, The default linux compat kernel ABI has been adjusted
673 to 2.6.18 in support of the linux-c6 compat ports infrastructure
674 update. If you wish to continue using the linux-f10 compat ports,
675 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
676 encouraged to update their linux-compat packages to linux-c6 during
677 their next update cycle.
680 The ofwfb driver, used to provide a graphics console on PowerPC when
681 using vt(4), no longer allows mmap() of all physical memory. This
682 will prevent Xorg on PowerPC with some ATI graphics cards from
683 initializing properly unless x11-servers/xorg-server is updated to
687 The xdev targets have been converted to using TARGET and
688 TARGET_ARCH instead of XDEV and XDEV_ARCH.
691 The default unbound configuration has been modified to address
692 issues with reverse lookups on networks that use private
693 address ranges. If you use the local_unbound service, run
694 "service local_unbound setup" as root to regenerate your
695 configuration, then "service local_unbound reload" to load the
699 The GNU texinfo and GNU info pages are not built and installed
700 anymore, WITH_INFO knob has been added to allow to built and install
702 UPDATE: see 20150102 entry on texinfo's removal
705 The GNU readline library is now an INTERNALLIB - that is, it is
706 statically linked into consumers (GDB and variants) in the base
707 system, and the shared library is no longer installed. The
708 devel/readline port is available for third party software that
712 The Itanium architecture (ia64) has been removed from the list of
713 known architectures. This is the first step in the removal of the
717 Commit r268115 has added NFSv4.1 server support, merged from
718 projects/nfsv4.1-server. Since this includes changes to the
719 internal interfaces between the NFS related modules, a full
720 build of the kernel and modules will be necessary.
721 __FreeBSD_version has been bumped.
724 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
725 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
726 which differs from the behaviour controlled by this knob.)
729 Maximal length of the serial number in CTL was increased from 16 to
730 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
731 and ctld, need to be rebuilt to work with a new kernel.
734 The libatf-c and libatf-c++ major versions were downgraded to 0 and
735 1 respectively to match the upstream numbers. They were out of
736 sync because, when they were originally added to FreeBSD, the
737 upstream versions were not respected. These libraries are private
738 and not yet built by default, so renumbering them should be a
739 non-issue. However, unclean source trees will yield broken test
740 programs once the operator executes "make delete-old-libs" after a
743 Additionally, the atf-sh binary was made private by moving it into
744 /usr/libexec/. Already-built shell test programs will keep the
745 path to the old binary so they will break after "make delete-old"
748 If you are using WITH_TESTS=yes (not the default), wipe the object
749 tree and rebuild from scratch to prevent spurious test failures.
750 This is only needed once: the misnumbered libraries and misplaced
751 binaries have been added to OptionalObsoleteFiles.inc so they will
752 be removed during a clean upgrade.
755 Clang and llvm have been upgraded to 3.4.1 release.
758 We bogusly installed src.opts.mk in /usr/share/mk. This file should
759 be removed to avoid issues in the future (and has been added to
763 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
764 past, it affected all builds that used the bsd.*.mk files. The old
765 behavior was a bug, but people may have relied upon it. To get this
766 behavior back, you can .include /etc/src.conf from /etc/make.conf
767 (which is still global and isn't changed). This also changes the
768 behavior of incremental builds inside the tree of individual
769 directories. Set MAKESYSPATH to ".../share/mk" to do that.
770 Although this has survived make universe and some upgrade scenarios,
771 other upgrade scenarios may have broken. At least one form of
772 temporary breakage was fixed with MAKESYSPATH settings for buildworld
773 as well... In cases where MAKESYSPATH isn't working with this
774 setting, you'll need to set it to the full path to your tree.
776 One side effect of all this cleaning up is that bsd.compiler.mk
777 is no longer implicitly included by bsd.own.mk. If you wish to
778 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
782 The lindev device has been removed since /dev/full has been made a
783 standard device. __FreeBSD_version has been bumped.
786 The knob WITHOUT_VI was added to the base system, which controls
787 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
788 in order to reorder files share/termcap and didn't build ex(1) as a
789 build tool, so building/installing with WITH_VI is highly advised for
790 build hosts for older releases.
792 This issue has been fixed in stable/9 and stable/10 in r277022 and
793 r276991, respectively.
796 The YES_HESIOD knob has been removed. It has been obsolete for
797 a decade. Please move to using WITH_HESIOD instead or your builds
798 will silently lack HESIOD.
801 The uart(4) driver has been changed with respect to its handling
802 of the low-level console. Previously the uart(4) driver prevented
803 any process from changing the baudrate or the CLOCAL and HUPCL
804 control flags. By removing the restrictions, operators can make
805 changes to the serial console port without having to reboot.
806 However, when getty(8) is started on the serial device that is
807 associated with the low-level console, a misconfigured terminal
808 line in /etc/ttys will now have a real impact.
809 Before upgrading the kernel, make sure that /etc/ttys has the
810 serial console device configured as 3wire without baudrate to
811 preserve the previous behaviour. E.g:
812 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
815 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
816 to improve performance. To re-enable it, if needed, run rpcbind
817 with command line option -W.
820 Switched back to the GPL dtc compiler due to updates in the upstream
821 dts files not being supported by the BSDL dtc compiler. You will need
822 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
823 may result while building dtb files during a kernel build if you fail
824 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
827 Clang and llvm have been upgraded to 3.4 release.
830 The nve(4) driver has been removed. Please use the nfe(4) driver
831 for NVIDIA nForce MCP Ethernet adapters instead.
834 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
835 This could cause certain C++ applications using shared libraries built
836 against the previous version of libc++ to crash. The incompatibility
837 has now been fixed, but any C++ applications or shared libraries built
838 between r261283 and r261801 should be recompiled.
841 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
842 capability mode support. Please note that enabling the feature in
843 kernel is still highly recommended.
846 OpenSSH is now built with sandbox support, and will use sandbox as
847 the default privilege separation method. This requires Capsicum
848 capability mode support in kernel.
851 The libelf and libdwarf libraries have been updated to newer
852 versions from upstream. Shared library version numbers for
853 these two libraries were bumped. Any ports or binaries
854 requiring these two libraries should be recompiled.
855 __FreeBSD_version is bumped to 1100006.
858 If a Makefile in a tests/ directory was auto-generating a Kyuafile
859 instead of providing an explicit one, this would prevent such
860 Makefile from providing its own Kyuafile in the future during
861 NO_CLEAN builds. This has been fixed in the Makefiles but manual
862 intervention is needed to clean an objdir if you use NO_CLEAN:
863 # find /usr/obj -name Kyuafile | xargs rm -f
866 The behavior of gss_pseudo_random() for the krb5 mechanism
867 has changed, for applications requesting a longer random string
868 than produced by the underlying enctype's pseudo-random() function.
869 In particular, the random string produced from a session key of
870 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
871 be different at the 17th octet and later, after this change.
872 The counter used in the PRF+ construction is now encoded as a
873 big-endian integer in accordance with RFC 4402.
874 __FreeBSD_version is bumped to 1100004.
877 The WITHOUT_ATF build knob has been removed and its functionality
878 has been subsumed into the more generic WITHOUT_TESTS. If you were
879 using the former to disable the build of the ATF libraries, you
880 should change your settings to use the latter.
883 The default version of mtree is nmtree which is obtained from
884 NetBSD. The output is generally the same, but may vary
885 slightly. If you found you need identical output adding
886 "-F freebsd9" to the command line should do the trick. For the
887 time being, the old mtree is available as fmtree.
890 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
891 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
892 1.1.4_8 and verify bsdyml not linked in, before running "make
894 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
896 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
899 The stable/10 branch has been created in subversion from head
903 The rc.d/jail script has been updated to support jail(8)
904 configuration file. The "jail_<jname>_*" rc.conf(5) variables
905 for per-jail configuration are automatically converted to
906 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
907 This is transparently backward compatible. See below about some
908 incompatibilities and rc.conf(5) manual page for more details.
910 These variables are now deprecated in favor of jail(8) configuration
911 file. One can use "rc.d/jail config <jname>" command to generate
912 a jail(8) configuration file in /var/run/jail.<jname>.conf without
913 running the jail(8) utility. The default pathname of the
914 configuration file is /etc/jail.conf and can be specified by
915 using $jail_conf or $jail_<jname>_conf variables.
917 Please note that jail_devfs_ruleset accepts an integer at
918 this moment. Please consider to rewrite the ruleset name
922 BIND has been removed from the base system. If all you need
923 is a local resolver, simply enable and start the local_unbound
924 service instead. Otherwise, several versions of BIND are
925 available in the ports tree. The dns/bind99 port is one example.
927 With this change, nslookup(1) and dig(1) are no longer in the base
928 system. Users should instead use host(1) and drill(1) which are
929 in the base system. Alternatively, nslookup and dig can
930 be obtained by installing the dns/bind-tools port.
933 With the addition of unbound(8), a new unbound user is now
934 required during installworld. "mergemaster -p" can be used to
935 add the user prior to installworld, as documented in the handbook.
938 OpenSSH is now built with DNSSEC support, and will by default
939 silently trust signed SSHFP records. This can be controlled with
940 the VerifyHostKeyDNS client configuration setting. DNSSEC support
941 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
944 The GNU Compiler Collection and C++ standard library (libstdc++)
945 are no longer built by default on platforms where clang is the system
946 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
950 The PROCDESC kernel option is now part of the GENERIC kernel
951 configuration and is required for the rwhod(8) to work.
952 If you are using custom kernel configuration, you should include
956 The API and ABI related to the Capsicum framework was modified
957 in backward incompatible way. The userland libraries and programs
958 have to be recompiled to work with the new kernel. This includes the
959 following libraries and programs, but the whole buildworld is
960 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
961 kdump, procstat, rwho, rwhod, uniq.
964 AES-NI intrinsic support has been added to gcc. The AES-NI module
965 has been updated to use this support. A new gcc is required to build
966 the aesni module on both i386 and amd64.
969 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
970 Thus "device padlock_rng" and "device rdrand_rng" should be
971 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
974 WITH_ICONV has been split into two feature sets. WITH_ICONV now
975 enables just the iconv* functionality and is now on by default.
976 WITH_LIBICONV_COMPAT enables the libiconv api and link time
977 compatibility. Set WITHOUT_ICONV to build the old way.
978 If you have been using WITH_ICONV before, you will very likely
979 need to turn on WITH_LIBICONV_COMPAT.
982 INVARIANTS option now enables DEBUG for code with OpenSolaris and
983 Illumos origin, including ZFS. If you have INVARIANTS in your
984 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
986 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
987 locks if WITNESS option was set. Because that generated a lot of
988 witness(9) reports and all of them were believed to be false
989 positives, this is no longer done. New option OPENSOLARIS_WITNESS
990 can be used to achieve the previous behavior.
993 Timer values in IPv6 data structures now use time_uptime instead
994 of time_second. Although this is not a user-visible functional
995 change, userland utilities which directly use them---ndp(8),
996 rtadvd(8), and rtsold(8) in the base system---need to be updated
1000 find -delete can now delete the pathnames given as arguments,
1001 instead of only files found below them or if the pathname did
1002 not contain any slashes. Formerly, the following error message
1005 find: -delete: <path>: relative path potentially not safe
1007 Deleting the pathnames given as arguments can be prevented
1008 without error messages using -mindepth 1 or by changing
1009 directory and passing "." as argument to find. This works in the
1010 old as well as the new version of find.
1013 Behavior of devfs rules path matching has been changed.
1014 Pattern is now always matched against fully qualified devfs
1015 path and slash characters must be explicitly matched by
1016 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1017 subdirectories must be reviewed.
1020 The default ARM ABI has changed to the ARM EABI. The old ABI is
1021 incompatible with the ARM EABI and all programs and modules will
1022 need to be rebuilt to work with a new kernel.
1024 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1026 NOTE: Support for the old ABI will be removed in the future and
1027 users are advised to upgrade.
1030 pkg_install has been disconnected from the build if you really need it
1031 you should add WITH_PKGTOOLS in your src.conf(5).
1034 Most of network statistics structures were changed to be able
1035 keep 64-bits counters. Thus all tools, that work with networking
1036 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1039 Fix a bug that allowed a tracing process (e.g. gdb) to write
1040 to a memory-mapped file in the traced process's address space
1041 even if neither the traced process nor the tracing process had
1042 write access to that file.
1045 CVS has been removed from the base system. An exact copy
1046 of the code is available from the devel/cvs port.
1049 Some people report the following error after the switch to bmake:
1051 make: illegal option -- J
1052 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1054 *** [buildworld] Error code 2
1056 this likely due to an old instance of make in
1057 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1058 which src/Makefile will use that blindly, if it exists, so if
1059 you see the above error:
1061 rm -rf `make -V MAKEPATH`
1066 Use bmake by default.
1067 Whereas before one could choose to build with bmake via
1068 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1069 make. The goal is to remove these knobs for 10-RELEASE.
1071 It is worth noting that bmake (like gmake) treats the command
1072 line as the unit of failure, rather than statements within the
1073 command line. Thus '(cd some/where && dosomething)' is safer
1074 than 'cd some/where; dosomething'. The '()' allows consistent
1075 behavior in parallel build.
1078 Fix a bug that allows NFS clients to issue READDIR on files.
1081 The WITHOUT_IDEA option has been removed because
1082 the IDEA patent expired.
1085 The sysctl which controls TRIM support under ZFS has been renamed
1086 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1090 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1091 rather than creating it's own in the temporary directory in
1092 order allow access to bootstrapped versions of tools such as
1093 install and mtree. When upgrading from version of FreeBSD where
1094 the install command does not support -l, you will need to
1095 install a new mergemaster command if mergemaster -p is required.
1096 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1100 Legacy ATA stack, disabled and replaced by new CAM-based one since
1101 FreeBSD 9.0, completely removed from the sources. Kernel modules
1102 atadisk and atapi*, user-level tools atacontrol and burncd are
1103 removed. Kernel option `options ATA_CAM` is now permanently enabled
1107 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1108 and socketpair(2). Software, in particular Kerberos, may
1109 automatically detect and use these during building. The resulting
1110 binaries will not work on older kernels.
1113 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1114 information, see the respective 20130304 entry).
1117 Recent commits to callout(9) changed the size of struct callout,
1118 so the KBI is probably heavily disturbed. Also, some functions
1119 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1120 by macros. Every kernel module using it won't load, so rebuild
1123 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1124 but does not initialize by default (because of the new CTL_DISABLE
1125 option) to save memory. To re-enable it, remove the CTL_DISABLE
1126 option from the kernel config file or set kern.cam.ctl.disable=0
1127 in /boot/loader.conf.
1130 The ctl device has been disabled in GENERIC for i386 and amd64.
1131 This was done due to the extra memory being allocated at system
1132 initialisation time by the ctl driver which was only used if
1133 a CAM target device was created. This makes a FreeBSD system
1134 unusable on 128MB or less of RAM.
1137 A new compression method (lz4) has been merged to -HEAD. Please
1138 refer to zpool-features(7) for more information.
1140 Please refer to the "ZFS notes" section of this file for information
1141 on upgrading boot ZFS pools.
1144 A BSD-licensed patch(1) variant has been added and is installed
1145 as bsdpatch, being the GNU version the default patch.
1146 To inverse the logic and use the BSD-licensed one as default,
1147 while having the GNU version installed as gnupatch, rebuild
1148 and install world with the WITH_BSD_PATCH knob set.
1151 Due to the use of the new -l option to install(1) during build
1152 and install, you must take care not to directly set the INSTALL
1153 make variable in your /etc/make.conf, /etc/src.conf, or on the
1154 command line. If you wish to use the -C flag for all installs
1155 you may be able to add INSTALL+=-C to /etc/make.conf or
1159 The install(1) option -M has changed meaning and now takes an
1160 argument that is a file or path to append logs to. In the
1161 unlikely event that -M was the last option on the command line
1162 and the command line contained at least two files and a target
1163 directory the first file will have logs appended to it. The -M
1164 option served little practical purpose in the last decade so its
1165 use is expected to be extremely rare.
1168 After switching to Clang as the default compiler some users of ZFS
1169 on i386 systems started to experience stack overflow kernel panics.
1170 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1173 GEOM_LABEL now mangles label names read from file system metadata.
1174 Mangling affect labels containing spaces, non-printable characters,
1175 '%' or '"'. Device names in /etc/fstab and other places may need to
1179 By default, only the 10 most recent kernel dumps will be saved. To
1180 restore the previous behaviour (no limit on the number of kernel dumps
1181 stored in the dump directory) add the following line to /etc/rc.conf:
1186 With the addition of auditdistd(8), a new auditdistd user is now
1187 required during installworld. "mergemaster -p" can be used to
1188 add the user prior to installworld, as documented in the handbook.
1191 The sin6_scope_id member variable in struct sockaddr_in6 is now
1192 filled by the kernel before passing the structure to the userland via
1193 sysctl or routing socket. This means the KAME-specific embedded scope
1194 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1195 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1196 __FreeBSD_version is bumped to 1000025.
1199 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1200 This means that the world and kernel will be compiled with clang
1201 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1202 and /usr/bin/cpp. To disable this behavior and revert to building
1203 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1204 of current may need to bootstrap WITHOUT_CLANG first if the clang
1205 build fails (its compatibility window doesn't extend to the 9 stable
1209 The IPFIREWALL_FORWARD kernel option has been removed. Its
1210 functionality now turned on by default.
1213 The ZERO_COPY_SOCKET kernel option has been removed and
1214 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1215 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1216 mechanism which is not safe and may result in kernel crashes.
1217 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1218 driver supports disposeable external page sized mbuf storage.
1219 Proper replacements for both zero-copy mechanisms are under
1220 consideration and will eventually lead to complete removal
1221 of the two kernel options.
1224 The IPv4 network stack has been converted to network byte
1225 order. The following modules need to be recompiled together
1226 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1227 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1230 Support for non-MPSAFE filesystems was removed from VFS. The
1231 VFS_VERSION was bumped, all filesystem modules shall be
1235 All the non-MPSAFE filesystems have been disconnected from
1236 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1237 portalfs, smbfs, xfs.
1240 The interface cloning API and ABI has changed. The following
1241 modules need to be recompiled together with kernel:
1242 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1243 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1244 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1247 The sdhci driver was split in two parts: sdhci (generic SD Host
1248 Controller logic) and sdhci_pci (actual hardware driver).
1249 No kernel config modifications are required, but if you
1250 load sdhc as a module you must switch to sdhci_pci instead.
1253 Import the FUSE kernel and userland support into base system.
1256 The GNU sort(1) program has been removed since the BSD-licensed
1257 sort(1) has been the default for quite some time and no serious
1258 problems have been reported. The corresponding WITH_GNU_SORT
1262 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1263 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1267 The net80211(4) ABI has been changed to allow for improved driver
1268 PS-POLL and power-save support. All wireless drivers need to be
1269 recompiled to work with the new kernel.
1272 The random(4) support for the VIA hardware random number
1273 generator (`PADLOCK') is no longer enabled unconditionally.
1274 Add the padlock_rng device in the custom kernel config if
1275 needed. The GENERIC kernels on i386 and amd64 do include the
1276 device, so the change only affects the custom kernel
1280 The pf(4) packet filter ABI has been changed. pfctl(8) and
1281 snmp_pf module need to be recompiled to work with new kernel.
1284 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1285 to -HEAD. Pools that have empty_bpobj in active state can not be
1286 imported read-write with ZFS implementations that do not support
1287 this feature. For more information read the zpool-features(5)
1291 The sparc64 ZFS loader has been changed to no longer try to auto-
1292 detect ZFS providers based on diskN aliases but now requires these
1293 to be explicitly listed in the OFW boot-device environment variable.
1296 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1297 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1298 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1301 The following sysctls and tunables have been renamed for consistency
1302 with other variables:
1303 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1304 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1307 The sort utility has been replaced with BSD sort. For now, GNU sort
1308 is also available as "gnusort" or the default can be set back to
1309 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1310 installed as "bsdsort".
1313 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1314 Starting with this version the old system of ZFS pool versioning
1315 is superseded by "feature flags". This concept enables forward
1316 compatibility against certain future changes in functionality of ZFS
1317 pools. The first read-only compatible "feature flag" for ZFS pools
1318 is named "com.delphix:async_destroy". For more information
1319 read the new zpool-features(5) manual page.
1320 Please refer to the "ZFS notes" section of this file for information
1321 on upgrading boot ZFS pools.
1324 The malloc(3) implementation embedded in libc now uses sources imported
1325 as contrib/jemalloc. The most disruptive API change is to
1326 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1327 delete it prior to installworld, and optionally re-create it using the
1328 new format after rebooting. See malloc.conf(5) for details
1329 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1333 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1334 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1335 now spelled mips. This is to aid compatibility with third-party
1336 software that expects this naming scheme in uname(3). Little-endian
1337 settings are unchanged. If you are updating a big-endian mips64 machine
1338 from before this change, you may need to set MACHINE_ARCH=mips64 in
1339 your environment before the new build system will recognize your machine.
1342 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1346 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1347 nullfs(5) did not pass through all behaviours to the underlying layer,
1348 as a result if we bound to a socket on the lower layer we could connect
1349 only to the lower path; if we bound to the upper layer we could connect
1350 only to the upper path. The new behavior is one can connect to both the
1351 lower and the upper paths regardless what layer path one binds to.
1354 The getifaddrs upgrade path broken with 20111215 has been restored.
1355 If you have upgraded in between 20111215 and 20120209 you need to
1356 recompile libc again with your kernel. You still need to recompile
1357 world to be able to configure CARP but this restriction already
1358 comes from 20111215.
1361 The set_rcvar() function has been removed from /etc/rc.subr. All
1362 base and ports rc.d scripts have been updated, so if you have a
1363 port installed with a script in /usr/local/etc/rc.d you can either
1364 hand-edit the rcvar= line, or reinstall the port.
1366 An easy way to handle the mass-update of /etc/rc.d:
1367 rm /etc/rc.d/* && mergemaster -i
1370 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1371 on the current CPU and prevents other threads from running.
1372 This behavior can be reverted using the kern.stop_scheduler_on_panic
1374 The new behavior can be incompatible with kern.sync_on_panic.
1377 The carp(4) facility has been changed significantly. Configuration
1378 of the CARP protocol via ifconfig(8) has changed, as well as format
1379 of CARP events submitted to devd(8) has changed. See manual pages
1380 for more information. The arpbalance feature of carp(4) is currently
1381 not supported anymore.
1383 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1384 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1385 need to be recompiled.
1388 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1392 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1393 explicitely support non-MPSAFE filesystems.
1394 It is on by default for all supported platform at this present
1398 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1399 i386 and pc98 GENERIC kernel configuration files.
1402 sysinstall has been removed
1405 The stable/9 branch created in subversion. This corresponds to the
1406 RELENG_9 branch in CVS.
1412 Avoid using make -j when upgrading. While generally safe, there are
1413 sometimes problems using -j to upgrade. If your upgrade fails with
1414 -j, please try again without -j. From time to time in the past there
1415 have been problems using -j with buildworld and/or installworld. This
1416 is especially true when upgrading between "distant" versions (eg one
1417 that cross a major release boundary or several minor releases, or when
1418 several months have passed on the -current branch).
1420 Sometimes, obscure build problems are the result of environment
1421 poisoning. This can happen because the make utility reads its
1422 environment when searching for values for global variables. To run
1423 your build attempts in an "environmental clean room", prefix all make
1424 commands with 'env -i '. See the env(1) manual page for more details.
1426 When upgrading from one major version to another it is generally best
1427 to upgrade to the latest code in the currently installed branch first,
1428 then do an upgrade to the new branch. This is the best-tested upgrade
1429 path, and has the highest probability of being successful. Please try
1430 this approach before reporting problems with a major version upgrade.
1432 When upgrading a live system, having a root shell around before
1433 installing anything can help undo problems. Not having a root shell
1434 around can lead to problems if pam has changed too much from your
1435 starting point to allow continued authentication after the upgrade.
1437 This file should be read as a log of events. When a later event changes
1438 information of a prior event, the prior event should not be deleted.
1439 Instead, a pointer to the entry with the new information should be
1440 placed in the old entry. Readers of this file should also sanity check
1441 older entries before relying on them blindly. Authors of new entries
1442 should write them with this in mind.
1446 When upgrading the boot ZFS pool to a new version, always follow
1449 1.) recompile and reinstall the ZFS boot loader and boot block
1450 (this is part of "make buildworld" and "make installworld")
1452 2.) update the ZFS boot block on your boot drive
1454 The following example updates the ZFS boot block on the first
1455 partition (freebsd-boot) of a GPT partitioned drive ada0:
1456 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1458 Non-boot pools do not need these updates.
1462 If you are updating from a prior version of FreeBSD (even one just
1463 a few days old), you should follow this procedure. It is the most
1464 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1466 make kernel-toolchain
1467 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1468 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1470 To test a kernel once
1471 ---------------------
1472 If you just want to boot a kernel once (because you are not sure
1473 if it works, or if you want to boot a known bad kernel to provide
1474 debugging information) run
1475 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1476 nextboot -k testkernel
1478 To just build a kernel when you know that it won't mess you up
1479 --------------------------------------------------------------
1480 This assumes you are already running a CURRENT system. Replace
1481 ${arch} with the architecture of your machine (e.g. "i386",
1482 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1484 cd src/sys/${arch}/conf
1485 config KERNEL_NAME_HERE
1486 cd ../compile/KERNEL_NAME_HERE
1491 If this fails, go to the "To build a kernel" section.
1493 To rebuild everything and install it on the current system.
1494 -----------------------------------------------------------
1495 # Note: sometimes if you are running current you gotta do more than
1496 # is listed here if you are upgrading from a really old current.
1498 <make sure you have good level 0 dumps>
1500 make kernel KERNCONF=YOUR_KERNEL_HERE
1502 <reboot in single user> [3]
1509 To cross-install current onto a separate partition
1510 --------------------------------------------------
1511 # In this approach we use a separate partition to hold
1512 # current's root, 'usr', and 'var' directories. A partition
1513 # holding "/", "/usr" and "/var" should be about 2GB in
1516 <make sure you have good level 0 dumps>
1519 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1520 <maybe newfs current's root partition>
1521 <mount current's root partition on directory ${CURRENT_ROOT}>
1522 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1523 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1524 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1525 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1526 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1527 <reboot into current>
1528 <do a "native" rebuild/install as described in the previous section>
1529 <maybe install compatibility libraries from ports/misc/compat*>
1533 To upgrade in-place from stable to current
1534 ----------------------------------------------
1535 <make sure you have good level 0 dumps>
1537 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1539 <reboot in single user> [3]
1546 Make sure that you've read the UPDATING file to understand the
1547 tweaks to various things you need. At this point in the life
1548 cycle of current, things change often and you are on your own
1549 to cope. The defaults can also change, so please read ALL of
1550 the UPDATING entries.
1552 Also, if you are tracking -current, you must be subscribed to
1553 freebsd-current@freebsd.org. Make sure that before you update
1554 your sources that you have read and understood all the recent
1555 messages there. If in doubt, please track -stable which has
1556 much fewer pitfalls.
1558 [1] If you have third party modules, such as vmware, you
1559 should disable them at this point so they don't crash your
1562 [3] From the bootblocks, boot -s, and then do
1567 adjkerntz -i # if CMOS is wall time
1568 Also, when doing a major release upgrade, it is required that
1569 you boot into single user mode to do the installworld.
1571 [4] Note: This step is non-optional. Failure to do this step
1572 can result in a significant reduction in the functionality of the
1573 system. Attempting to do it by hand is not recommended and those
1574 that pursue this avenue should read this file carefully, as well
1575 as the archives of freebsd-current and freebsd-hackers mailing lists
1576 for potential gotchas. The -U option is also useful to consider.
1577 See mergemaster(8) for more information.
1579 [5] Usually this step is a noop. However, from time to time
1580 you may need to do this if you get unknown user in the following
1581 step. It never hurts to do it all the time. You may need to
1582 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1583 install) after the buildworld before this step if you last updated
1584 from current before 20130425 or from -stable before 20130430.
1586 [6] This only deletes old files and directories. Old libraries
1587 can be deleted by "make delete-old-libs", but you have to make
1588 sure that no program is using those libraries anymore.
1590 [8] In order to have a kernel that can run the 4.x binaries needed to
1591 do an installworld, you must include the COMPAT_FREEBSD4 option in
1592 your kernel. Failure to do so may leave you with a system that is
1593 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1594 required to run the 5.x binaries on more recent kernels. And so on
1595 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1597 Make sure that you merge any new devices from GENERIC since the
1598 last time you updated your kernel config file.
1600 [9] When checking out sources, you must include the -P flag to have
1601 cvs prune empty directories.
1603 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1604 "?=" instead of the "=" assignment operator, so that buildworld can
1605 override the CPUTYPE if it needs to.
1607 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1608 not on the command line, or in /etc/make.conf. buildworld will
1609 warn if it is improperly defined.
1612 This file contains a list, in reverse chronological order, of major
1613 breakages in tracking -current. It is not guaranteed to be a complete
1614 list of such breakages, and only contains entries since September 23, 2011.
1615 If you need to see UPDATING entries from before that date, you will need
1616 to fetch an UPDATING file from an older FreeBSD release.
1618 Copyright information:
1620 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1622 Redistribution, publication, translation and use, with or without
1623 modification, in full or in part, in any form or format of this
1624 document are permitted without further permission from the author.
1626 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1627 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1628 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1629 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1630 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1631 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1632 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1633 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1634 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1635 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1636 POSSIBILITY OF SUCH DAMAGE.
1638 Contact Warner Losh if you have any questions about your use of