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 Relocatable object files with the extension of .So have been renamed
36 to use an extension of .pico instead. The purpose of this change is
37 to avoid a name clash with shared libraries on case-insensitive file
38 systems. On those file systems, foo.So is the same file as foo.so.
41 GNU rcs has been turned off by default. It can (temporarily) be built
42 again by adding WITH_RCS knob in src.conf.
43 Otherwise, GNU rcs is available from packages:
44 - rcs: Latest GPLv3 GNU rcs version.
45 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
48 The backup_uses_rcs functionality has been removed from rc.subr.
51 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
52 two separate components, QUEUE_MACRO_DEBUG_TRACE and
53 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
54 QUEUE_MACRO_DEBUG behavior.
57 r304787 changed some ioctl interfaces between the iSCSI userspace
58 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
59 rebuilt to work with new kernels. __FreeBSD_version has been bumped
63 The UDP receive code has been updated to only treat incoming UDP
64 packets that were addressed to an L2 broadcast address as L3
65 broadcast packets. It is not expected that this will affect any
66 standards-conforming UDP application. The new behaviour can be
67 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
71 Remove the openbsd_poll system call.
72 __FreeBSD_version has been bumped because of this.
75 The libc stub for the pipe(2) system call has been replaced with
76 a wrapper that calls the pipe2(2) system call and the pipe(2)
77 system call is now only implemented by the kernels that include
78 "options COMPAT_FREEBSD10" in their config file (this is the
79 default). Users should ensure that this option is enabled in
80 their kernel or upgrade userspace to r302092 before upgrading their
84 CAM will now strip leading spaces from SCSI disks' serial numbers.
85 This will effect users who create UFS filesystems on SCSI disks using
86 those disk's diskid device nodes. For example, if /etc/fstab
87 previously contained a line like
88 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
89 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
90 transforms like gmirror may also be affected. ZFS users should
94 The bitstring(3) API has been updated with new functionality and
95 improved performance. But it is binary-incompatible with the old API.
96 Objects built with the new headers may not be linked against objects
97 built with the old headers.
100 The brk and sbrk functions have been removed from libc on arm64.
101 Binutils from ports has been updated to not link to these
102 functions and should be updated to the latest version before
103 installing a new libc.
106 The armv6 port now defaults to hard float ABI. Limited support
107 for running both hardfloat and soft float on the same system
108 is available using the libraries installed with -DWITH_LIBSOFT.
109 This has only been tested as an upgrade path for installworld
110 and packages may fail or need manual intervention to run. New
111 packages will be needed.
113 To update an existing self-hosted armv6hf system, you must add
114 TARGET_ARCH=armv6 on the make command line for both the build
115 and the install steps.
118 Kernel modules compiled outside of a kernel build now default to
119 installing to /boot/modules instead of /boot/kernel. Many kernel
120 modules built this way (such as those in ports) already overrode
121 KMODDIR explicitly to install into /boot/modules. However,
122 manually building and installing a module from /sys/modules will
123 now install to /boot/modules instead of /boot/kernel.
126 The CAM I/O scheduler has been committed to the kernel. There should be
127 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
128 list of known rogues that claim support for this but actually corrupt
129 data is believed to be complete, be on the lookout for data
130 corruption. The known rogue list is believed to be complete:
132 o Crucial MX100, M550 drives with MU01 firmware.
133 o Micron M510 and M550 drives with MU01 firmware.
134 o Micron M500 prior to MU07 firmware
135 o Samsung 830, 840, and 850 all firmwares
136 o FCCT M500 all firmwares
138 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
139 with working NCQ TRIM. For Micron branded drives, see your sales rep for
140 updated firmware. Black listed drives will work correctly because these
141 drives work correctly so long as no NCQ TRIMs are sent to them. Given
142 this list is the same as found in Linux, it's believed there are no
143 other rogues in the market place. All other models from the above
146 To be safe, if you are at all concerned, you can quirk each of your
147 drives to prevent NCQ from being sent by setting:
148 kern.cam.ada.X.quirks="0x2"
149 in loader.conf. If the drive requires the 4k sector quirk, set the
153 The FAST_DEPEND build option has been removed and its functionality is
154 now the one true way. The old mkdep(1) style of 'make depend' has
155 been removed. See 20160311 for further details.
158 Resource range types have grown from unsigned long to uintmax_t. All
159 drivers, and anything using libdevinfo, need to be recompiled.
162 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
163 builds. It no longer runs mkdep(1) during 'make depend', and the
164 'make depend' stage can safely be skipped now as it is auto ran
165 when building 'make all' and will generate all SRCS and DPSRCS before
166 building anything else. Dependencies are gathered at compile time with
167 -MF flags kept in separate .depend files per object file. Users should
168 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
172 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
173 kernel modules. Therefore, if you load any kernel modules at boot time,
174 please install the boot loaders after you install the kernel, but before
178 make kernel KERNCONF=YOUR_KERNEL_HERE
179 make -C sys/boot install
180 <reboot in single user>
182 Then follow the usual steps, described in the General Notes section,
186 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
187 see the 20141231 entry below for information about prerequisites and
188 upgrading, if you are not already using clang 3.5.0 or higher.
191 The AIO subsystem is now a standard part of the kernel. The
192 VFS_AIO kernel option and aio.ko kernel module have been removed.
193 Due to stability concerns, asynchronous I/O requests are only
194 permitted on sockets and raw disks by default. To enable
195 asynchronous I/O requests on all file types, set the
196 vfs.aio.enable_unsafe sysctl to a non-zero value.
199 The ELF object manipulation tool objcopy is now provided by the
200 ELF Tool Chain project rather than by GNU binutils. It should be a
201 drop-in replacement, with the addition of arm64 support. The
202 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
203 to obtain the GNU version if necessary.
206 Building ZFS pools on top of zvols is prohibited by default. That
207 feature has never worked safely; it's always been prone to deadlocks.
208 Using a zvol as the backing store for a VM guest's virtual disk will
209 still work, even if the guest is using ZFS. Legacy behavior can be
210 restored by setting vfs.zfs.vol.recursive=1.
213 The NONE and HPN patches has been removed from OpenSSH. They are
214 still available in the security/openssh-portable port.
217 With the addition of ypldap(8), a new _ypldap user is now required
218 during installworld. "mergemaster -p" can be used to add the user
219 prior to installworld, as documented in the handbook.
222 The tftp loader (pxeboot) now uses the option root-path directive. As a
223 consequence it no longer looks for a pxeboot.4th file on the tftp
224 server. Instead it uses the regular /boot infrastructure as with the
228 The code to start recording plug and play data into the modules has
229 been committed. While the old tools will properly build a new kernel,
230 a number of warnings about "unknown metadata record 4" will be produced
231 for an older kldxref. To avoid such warnings, make sure to rebuild
232 the kernel toolchain (or world). Make sure that you have r292078 or
233 later when trying to build 292077 or later before rebuilding.
236 Debug data files are now built by default with 'make buildworld' and
237 installed with 'make installworld'. This facilitates debugging but
238 requires more disk space both during the build and for the installed
239 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
243 r291527 changed the internal interface between the nfsd.ko and
244 nfscommon.ko modules. As such, they must both be upgraded to-gether.
245 __FreeBSD_version has been bumped because of this.
248 Add support for unicode collation strings leads to a change of
249 order of files listed by ls(1) for example. To get back to the old
250 behaviour, set LC_COLLATE environment variable to "C".
252 Databases administrators will need to reindex their databases given
253 collation results will be different.
255 Due to a bug in install(1) it is recommended to remove the ancient
256 locales before running make installworld.
258 rm -rf /usr/share/locale/*
261 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
262 libcrypto.so.7 or libssl.so.7 must be recompiled.
265 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
266 Kernel modules isp_2400_multi and isp_2500_multi were removed and
267 should be replaced with isp_2400 and isp_2500 modules respectively.
270 The build previously allowed using 'make -n' to not recurse into
271 sub-directories while showing what commands would be executed, and
272 'make -n -n' to recursively show commands. Now 'make -n' will recurse
273 and 'make -N' will not.
276 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
277 and etcupdate will now use this file. A custom sendmail.cf is now
278 updated via this mechanism rather than via installworld. If you had
279 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
280 want to remove the exclusion or change it to "always install".
281 /etc/mail/sendmail.cf is now managed the same way regardless of
282 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
283 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
286 Compatibility shims for legacy ATA device names have been removed.
287 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
288 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
289 environment variables, /dev/ad* and /dev/ar* symbolic links.
292 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
293 Please see the 20141231 entry below for information about prerequisites
294 and upgrading, if you are not already using clang 3.5.0 or higher.
297 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
298 and renamed from .symbols to .debug. This reduces the size requirements
299 on the boot partition or file system and provides consistency with
300 userland debug files.
302 When using the supported kernel installation method the
303 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
304 as is done with /boot/kernel.
306 Developers wishing to maintain the historical behavior of installing
307 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
310 The wireless drivers had undergone changes that remove the 'parent
311 interface' from the ifconfig -l output. The rc.d network scripts
312 used to check presence of a parent interface in the list, so old
313 scripts would fail to start wireless networking. Thus, etcupdate(3)
314 or mergemaster(8) run is required after kernel update, to update your
315 rc.d scripts in /etc.
318 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
319 These configurations are now automatically interpreted as
320 'scrub fragment reassemble'.
323 Kernel-loadable modules for the random(4) device are back. To use
324 them, the kernel must have
327 options RANDOM_LOADABLE
329 kldload(8) can then be used to load random_fortuna.ko
330 or random_yarrow.ko. Please note that due to the indirect
331 function calls that the loadable modules need to provide,
332 the build-in variants will be slightly more efficient.
334 The random(4) kernel option RANDOM_DUMMY has been retired due to
335 unpopularity. It was not all that useful anyway.
338 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
339 Control over building the ELF Tool Chain tools is now provided by
340 the WITHOUT_TOOLCHAIN knob.
343 The polarity of Pulse Per Second (PPS) capture events with the
344 uart(4) driver has been corrected. Prior to this change the PPS
345 "assert" event corresponded to the trailing edge of a positive PPS
346 pulse and the "clear" event was the leading edge of the next pulse.
348 As the width of a PPS pulse in a typical GPS receiver is on the
349 order of 1 millisecond, most users will not notice any significant
350 difference with this change.
352 Anyone who has compensated for the historical polarity reversal by
353 configuring a negative offset equal to the pulse width will need to
354 remove that workaround.
357 The default group assigned to /dev/dri entries has been changed
358 from 'wheel' to 'video' with the id of '44'. If you want to have
359 access to the dri devices please add yourself to the video group
362 # pw groupmod video -m $USER
365 The menu.rc and loader.rc files will now be replaced during
366 upgrades. Please migrate local changes to menu.rc.local and
367 loader.rc.local instead.
370 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
371 strings and strip have been removed. The src.conf(5) knob
372 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
375 As ZFS requires more kernel stack pages than is the default on some
376 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
377 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
379 Please consider using 'options KSTACK_PAGES=X' where X is greater
380 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
383 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
384 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
385 default, i.e., they will not contain "::". For example, instead
386 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
387 to have a more specific match, such as different map entries for
388 IPv6:0:0 vs IPv6:0. This change requires that configuration
389 data (including maps, files, classes, custom ruleset, etc.) must
390 use the same format, so make certain such configuration data is
391 upgrading. As a very simple check search for patterns like
392 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
393 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
394 the cf option UseCompressedIPv6Addresses.
397 The default kernel entropy-processing algorithm is now
398 Fortuna, replacing Yarrow.
400 Assuming you have 'device random' in your kernel config
401 file, the configurations allow a kernel option to override
402 this default. You may choose *ONE* of:
404 options RANDOM_YARROW # Legacy /dev/random algorithm.
405 options RANDOM_DUMMY # Blocking-only driver.
407 If you have neither, you get Fortuna. For most people,
408 read no further, Fortuna will give a /dev/random that works
409 like it always used to, and the difference will be irrelevant.
411 If you remove 'device random', you get *NO* kernel-processed
412 entropy at all. This may be acceptable to folks building
413 embedded systems, but has complications. Carry on reading,
414 and it is assumed you know what you need.
416 *PLEASE* read random(4) and random(9) if you are in the
417 habit of tweaking kernel configs, and/or if you are a member
418 of the embedded community, wanting specific and not-usual
419 behaviour from your security subsystems.
421 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
422 random', you will NOT have a functioning /dev/random, and
423 many cryptographic features will not work, including SSH.
424 You may also find strange behaviour from the random(3) set
425 of library functions, in particular sranddev(3), srandomdev(3)
426 and arc4random(3). The reason for this is that the KERN_ARND
427 sysctl only returns entropy if it thinks it has some to
428 share, and with RANDOM_DUMMY or no 'device random' this
432 An additional fix for the issue described in the 20150614 sendmail
433 entry below has been been committed in revision 284717.
436 FreeBSD's old make (fmake) has been removed from the system. It is
437 available as the devel/fmake port or via pkg install fmake.
440 The fix for the issue described in the 20150614 sendmail entry
441 below has been been committed in revision 284436. The work
442 around described in that entry is no longer needed unless the
443 default setting is overridden by a confDH_PARAMETERS configuration
444 setting of '5' or pointing to a 512 bit DH parameter file.
447 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
448 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
449 and devel/kyua to version 0.20+ and adjust any calling code to work
450 with Kyuafile and kyua.
453 The import of openssl to address the FreeBSD-SA-15:10.openssl
454 security advisory includes a change which rejects handshakes
455 with DH parameters below 768 bits. sendmail releases prior
456 to 8.15.2 (not yet released), defaulted to a 512 bit
457 DH parameter setting for client connections. To work around
458 this interoperability, sendmail can be configured to use a
459 2048 bit DH parameter by:
461 1. Edit /etc/mail/`hostname`.mc
462 2. If a setting for confDH_PARAMETERS does not exist or
463 exists and is set to a string beginning with '5',
465 3. If a setting for confDH_PARAMETERS exists and is set to
466 a file path, create a new file with:
467 openssl dhparam -out /path/to/file 2048
468 4. Rebuild the .cf file:
469 cd /etc/mail/; make; make install
471 cd /etc/mail/; make restart
473 A sendmail patch is coming, at which time this file will be
477 Generation of legacy formatted entries have been disabled by default
478 in pwd_mkdb(8), as all base system consumers of the legacy formatted
479 entries were converted to use the new format by default when the new,
480 machine independent format have been added and supported since FreeBSD
483 Please see the pwd_mkdb(8) manual page for further details.
486 Clang and llvm have been upgraded to 3.6.1 release. Please see the
487 20141231 entry below for information about prerequisites and upgrading,
488 if you are not already using 3.5.0 or higher.
491 TI platform code switched to using vendor DTS files and this update
492 may break existing systems running on Beaglebone, Beaglebone Black,
495 - dtb files should be regenerated/reinstalled. Filenames are the
496 same but content is different now
497 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
498 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
499 addressing scheme is now pin 25 on /dev/gpioc3.
500 - Pandaboard: /etc/ttys should be updated, serial console device is
501 now /dev/ttyu2, not /dev/ttyu0
504 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
505 If you need the GNU extension from groff soelim(1), install groff
506 from package: pkg install groff, or via ports: textproc/groff.
509 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
510 defined in symlink(7); previously symlinks were silently ignored.
513 The const qualifier has been removed from iconv(3) to comply with
514 POSIX. The ports tree is aware of this from r384038 onwards.
517 Libraries specified by LIBADD in Makefiles must have a corresponding
518 DPADD_<lib> variable to ensure correct dependencies. This is now
519 enforced in src.libnames.mk.
522 From legacy ata(4) driver was removed support for SATA controllers
523 supported by more functional drivers ahci(4), siis(4) and mvs(4).
524 Kernel modules ataahci and ataadaptec were removed completely,
525 replaced by ahci and mvs modules respectively.
528 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
529 the 20141231 entry below for information about prerequisites and
530 upgrading, if you are not already using 3.5.0 or higher.
533 The 32-bit PowerPC kernel has been changed to a position-independent
534 executable. This can only be booted with a version of loader(8)
535 newer than January 31, 2015, so make sure to update both world and
536 kernel before rebooting.
539 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
540 but before r278950, the RNG was not seeded properly. Immediately
541 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
542 ssh keys or openssl keys) that were generated w/ a kernel from that
543 range. This does not affect programs that directly used /dev/random
544 or /dev/urandom. All userland uses of arc4random(3) are affected.
547 The autofs(4) ABI was changed in order to restore binary compatibility
548 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
552 The powerpc64 kernel has been changed to a position-independent
553 executable. This can only be booted with a new version of loader(8),
554 so make sure to update both world and kernel before rebooting.
557 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
558 only release, no new features have been added. Please see the 20141231
559 entry below for information about prerequisites and upgrading, if you
560 are not already using 3.5.0.
563 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
564 taken from the ELF Tool Chain project rather than GNU binutils. They
565 should be drop-in replacements, with the addition of arm64 support.
566 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
567 binutils tools, if necessary. See 20150805 for updated information.
570 The default Unbound configuration now enables remote control
571 using a local socket. Users who have already enabled the
572 local_unbound service should regenerate their configuration
573 by running "service local_unbound setup" as root.
576 The GNU texinfo and GNU info pages have been removed.
577 To be able to view GNU info pages please install texinfo from ports.
580 Clang, llvm and lldb have been upgraded to 3.5.0 release.
582 As of this release, a prerequisite for building clang, llvm and lldb is
583 a C++11 capable compiler and C++11 standard library. This means that to
584 be able to successfully build the cross-tools stage of buildworld, with
585 clang as the bootstrap compiler, your system compiler or cross compiler
586 should either be clang 3.3 or later, or gcc 4.8 or later, and your
587 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
590 On any standard FreeBSD 10.x or 11.x installation, where clang and
591 libc++ are on by default (that is, on x86 or arm), this should work out
594 On 9.x installations where clang is enabled by default, e.g. on x86 and
595 powerpc, libc++ will not be enabled by default, so libc++ should be
596 built (with clang) and installed first. If both clang and libc++ are
597 missing, build clang first, then use it to build libc++.
599 On 8.x and earlier installations, upgrade to 9.x first, and then follow
600 the instructions for 9.x above.
602 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
603 default, and do not build clang.
605 Many embedded systems are resource constrained, and will not be able to
606 build clang in a reasonable time, or in some cases at all. In those
607 cases, cross building bootable systems on amd64 is a workaround.
609 This new version of clang introduces a number of new warnings, of which
610 the following are most likely to appear:
614 This warns in two cases, for both C and C++:
615 * When the code is trying to take the absolute value of an unsigned
616 quantity, which is effectively a no-op, and almost never what was
617 intended. The code should be fixed, if at all possible. If you are
618 sure that the unsigned quantity can be safely cast to signed, without
619 loss of information or undefined behavior, you can add an explicit
620 cast, or disable the warning.
622 * When the code is trying to take an absolute value, but the called
623 abs() variant is for the wrong type, which can lead to truncation.
624 If you want to disable the warning instead of fixing the code, please
625 make sure that truncation will not occur, or it might lead to unwanted
628 -Wtautological-undefined-compare and
629 -Wundefined-bool-conversion
631 These warn when C++ code is trying to compare 'this' against NULL, while
632 'this' should never be NULL in well-defined C++ code. However, there is
633 some legacy (pre C++11) code out there, which actively abuses this
634 feature, which was less strictly defined in previous C++ versions.
636 Squid and openjdk do this, for example. The warning can be turned off
637 for C++98 and earlier, but compiling the code in C++11 mode might result
638 in unexpected behavior; for example, the parts of the program that are
639 unreachable could be optimized away.
642 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
643 kernel sources have been removed. The .h files remain, since some
644 utilities include them. This will need to be fixed later.
645 If "mount -t oldnfs ..." is attempted, it will fail.
646 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
647 the utilities will report errors.
650 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
651 directories to top level SUBDIR variable when their parent
652 directory is included in LOCAL_DIRS. Users with build systems with
653 such hierarchies and without SUBDIR entries in the parent
654 directory Makefiles should add them or add the directories to
658 faith(4) and faithd(8) have been removed from the base system. Faith
659 has been obsolete for a very long time.
662 vt(4), the new console driver, is enabled by default. It brings
663 support for Unicode and double-width characters, as well as
664 support for UEFI and integration with the KMS kernel video
667 You may need to update your console settings in /etc/rc.conf,
668 most probably the keymap. During boot, /etc/rc.d/syscons will
669 indicate what you need to do.
671 vt(4) still has issues and lacks some features compared to
672 syscons(4). See the wiki for up-to-date information:
673 https://wiki.freebsd.org/Newcons
675 If you want to keep using syscons(4), you can do so by adding
676 the following line to /boot/loader.conf:
680 pjdfstest has been integrated into kyua as an opt-in test suite.
681 Please see share/doc/pjdfstest/README for more details on how to
685 gperf has been removed from the base system for architectures
686 that use clang. Ports that require gperf will obtain it from the
690 pjdfstest has been moved from tools/regression/pjdfstest to
694 At svn r271982, The default linux compat kernel ABI has been adjusted
695 to 2.6.18 in support of the linux-c6 compat ports infrastructure
696 update. If you wish to continue using the linux-f10 compat ports,
697 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
698 encouraged to update their linux-compat packages to linux-c6 during
699 their next update cycle.
702 The ofwfb driver, used to provide a graphics console on PowerPC when
703 using vt(4), no longer allows mmap() of all physical memory. This
704 will prevent Xorg on PowerPC with some ATI graphics cards from
705 initializing properly unless x11-servers/xorg-server is updated to
709 The xdev targets have been converted to using TARGET and
710 TARGET_ARCH instead of XDEV and XDEV_ARCH.
713 The default unbound configuration has been modified to address
714 issues with reverse lookups on networks that use private
715 address ranges. If you use the local_unbound service, run
716 "service local_unbound setup" as root to regenerate your
717 configuration, then "service local_unbound reload" to load the
721 The GNU texinfo and GNU info pages are not built and installed
722 anymore, WITH_INFO knob has been added to allow to built and install
724 UPDATE: see 20150102 entry on texinfo's removal
727 The GNU readline library is now an INTERNALLIB - that is, it is
728 statically linked into consumers (GDB and variants) in the base
729 system, and the shared library is no longer installed. The
730 devel/readline port is available for third party software that
734 The Itanium architecture (ia64) has been removed from the list of
735 known architectures. This is the first step in the removal of the
739 Commit r268115 has added NFSv4.1 server support, merged from
740 projects/nfsv4.1-server. Since this includes changes to the
741 internal interfaces between the NFS related modules, a full
742 build of the kernel and modules will be necessary.
743 __FreeBSD_version has been bumped.
746 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
747 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
748 which differs from the behaviour controlled by this knob.)
751 Maximal length of the serial number in CTL was increased from 16 to
752 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
753 and ctld, need to be rebuilt to work with a new kernel.
756 The libatf-c and libatf-c++ major versions were downgraded to 0 and
757 1 respectively to match the upstream numbers. They were out of
758 sync because, when they were originally added to FreeBSD, the
759 upstream versions were not respected. These libraries are private
760 and not yet built by default, so renumbering them should be a
761 non-issue. However, unclean source trees will yield broken test
762 programs once the operator executes "make delete-old-libs" after a
765 Additionally, the atf-sh binary was made private by moving it into
766 /usr/libexec/. Already-built shell test programs will keep the
767 path to the old binary so they will break after "make delete-old"
770 If you are using WITH_TESTS=yes (not the default), wipe the object
771 tree and rebuild from scratch to prevent spurious test failures.
772 This is only needed once: the misnumbered libraries and misplaced
773 binaries have been added to OptionalObsoleteFiles.inc so they will
774 be removed during a clean upgrade.
777 Clang and llvm have been upgraded to 3.4.1 release.
780 We bogusly installed src.opts.mk in /usr/share/mk. This file should
781 be removed to avoid issues in the future (and has been added to
785 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
786 past, it affected all builds that used the bsd.*.mk files. The old
787 behavior was a bug, but people may have relied upon it. To get this
788 behavior back, you can .include /etc/src.conf from /etc/make.conf
789 (which is still global and isn't changed). This also changes the
790 behavior of incremental builds inside the tree of individual
791 directories. Set MAKESYSPATH to ".../share/mk" to do that.
792 Although this has survived make universe and some upgrade scenarios,
793 other upgrade scenarios may have broken. At least one form of
794 temporary breakage was fixed with MAKESYSPATH settings for buildworld
795 as well... In cases where MAKESYSPATH isn't working with this
796 setting, you'll need to set it to the full path to your tree.
798 One side effect of all this cleaning up is that bsd.compiler.mk
799 is no longer implicitly included by bsd.own.mk. If you wish to
800 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
804 The lindev device has been removed since /dev/full has been made a
805 standard device. __FreeBSD_version has been bumped.
808 The knob WITHOUT_VI was added to the base system, which controls
809 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
810 in order to reorder files share/termcap and didn't build ex(1) as a
811 build tool, so building/installing with WITH_VI is highly advised for
812 build hosts for older releases.
814 This issue has been fixed in stable/9 and stable/10 in r277022 and
815 r276991, respectively.
818 The YES_HESIOD knob has been removed. It has been obsolete for
819 a decade. Please move to using WITH_HESIOD instead or your builds
820 will silently lack HESIOD.
823 The uart(4) driver has been changed with respect to its handling
824 of the low-level console. Previously the uart(4) driver prevented
825 any process from changing the baudrate or the CLOCAL and HUPCL
826 control flags. By removing the restrictions, operators can make
827 changes to the serial console port without having to reboot.
828 However, when getty(8) is started on the serial device that is
829 associated with the low-level console, a misconfigured terminal
830 line in /etc/ttys will now have a real impact.
831 Before upgrading the kernel, make sure that /etc/ttys has the
832 serial console device configured as 3wire without baudrate to
833 preserve the previous behaviour. E.g:
834 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
837 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
838 to improve performance. To re-enable it, if needed, run rpcbind
839 with command line option -W.
842 Switched back to the GPL dtc compiler due to updates in the upstream
843 dts files not being supported by the BSDL dtc compiler. You will need
844 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
845 may result while building dtb files during a kernel build if you fail
846 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
849 Clang and llvm have been upgraded to 3.4 release.
852 The nve(4) driver has been removed. Please use the nfe(4) driver
853 for NVIDIA nForce MCP Ethernet adapters instead.
856 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
857 This could cause certain C++ applications using shared libraries built
858 against the previous version of libc++ to crash. The incompatibility
859 has now been fixed, but any C++ applications or shared libraries built
860 between r261283 and r261801 should be recompiled.
863 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
864 capability mode support. Please note that enabling the feature in
865 kernel is still highly recommended.
868 OpenSSH is now built with sandbox support, and will use sandbox as
869 the default privilege separation method. This requires Capsicum
870 capability mode support in kernel.
873 The libelf and libdwarf libraries have been updated to newer
874 versions from upstream. Shared library version numbers for
875 these two libraries were bumped. Any ports or binaries
876 requiring these two libraries should be recompiled.
877 __FreeBSD_version is bumped to 1100006.
880 If a Makefile in a tests/ directory was auto-generating a Kyuafile
881 instead of providing an explicit one, this would prevent such
882 Makefile from providing its own Kyuafile in the future during
883 NO_CLEAN builds. This has been fixed in the Makefiles but manual
884 intervention is needed to clean an objdir if you use NO_CLEAN:
885 # find /usr/obj -name Kyuafile | xargs rm -f
888 The behavior of gss_pseudo_random() for the krb5 mechanism
889 has changed, for applications requesting a longer random string
890 than produced by the underlying enctype's pseudo-random() function.
891 In particular, the random string produced from a session key of
892 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
893 be different at the 17th octet and later, after this change.
894 The counter used in the PRF+ construction is now encoded as a
895 big-endian integer in accordance with RFC 4402.
896 __FreeBSD_version is bumped to 1100004.
899 The WITHOUT_ATF build knob has been removed and its functionality
900 has been subsumed into the more generic WITHOUT_TESTS. If you were
901 using the former to disable the build of the ATF libraries, you
902 should change your settings to use the latter.
905 The default version of mtree is nmtree which is obtained from
906 NetBSD. The output is generally the same, but may vary
907 slightly. If you found you need identical output adding
908 "-F freebsd9" to the command line should do the trick. For the
909 time being, the old mtree is available as fmtree.
912 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
913 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
914 1.1.4_8 and verify bsdyml not linked in, before running "make
916 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
918 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
921 The stable/10 branch has been created in subversion from head
925 The rc.d/jail script has been updated to support jail(8)
926 configuration file. The "jail_<jname>_*" rc.conf(5) variables
927 for per-jail configuration are automatically converted to
928 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
929 This is transparently backward compatible. See below about some
930 incompatibilities and rc.conf(5) manual page for more details.
932 These variables are now deprecated in favor of jail(8) configuration
933 file. One can use "rc.d/jail config <jname>" command to generate
934 a jail(8) configuration file in /var/run/jail.<jname>.conf without
935 running the jail(8) utility. The default pathname of the
936 configuration file is /etc/jail.conf and can be specified by
937 using $jail_conf or $jail_<jname>_conf variables.
939 Please note that jail_devfs_ruleset accepts an integer at
940 this moment. Please consider to rewrite the ruleset name
944 BIND has been removed from the base system. If all you need
945 is a local resolver, simply enable and start the local_unbound
946 service instead. Otherwise, several versions of BIND are
947 available in the ports tree. The dns/bind99 port is one example.
949 With this change, nslookup(1) and dig(1) are no longer in the base
950 system. Users should instead use host(1) and drill(1) which are
951 in the base system. Alternatively, nslookup and dig can
952 be obtained by installing the dns/bind-tools port.
955 With the addition of unbound(8), a new unbound user is now
956 required during installworld. "mergemaster -p" can be used to
957 add the user prior to installworld, as documented in the handbook.
960 OpenSSH is now built with DNSSEC support, and will by default
961 silently trust signed SSHFP records. This can be controlled with
962 the VerifyHostKeyDNS client configuration setting. DNSSEC support
963 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
966 The GNU Compiler Collection and C++ standard library (libstdc++)
967 are no longer built by default on platforms where clang is the system
968 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
972 The PROCDESC kernel option is now part of the GENERIC kernel
973 configuration and is required for the rwhod(8) to work.
974 If you are using custom kernel configuration, you should include
978 The API and ABI related to the Capsicum framework was modified
979 in backward incompatible way. The userland libraries and programs
980 have to be recompiled to work with the new kernel. This includes the
981 following libraries and programs, but the whole buildworld is
982 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
983 kdump, procstat, rwho, rwhod, uniq.
986 AES-NI intrinsic support has been added to gcc. The AES-NI module
987 has been updated to use this support. A new gcc is required to build
988 the aesni module on both i386 and amd64.
991 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
992 Thus "device padlock_rng" and "device rdrand_rng" should be
993 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
996 WITH_ICONV has been split into two feature sets. WITH_ICONV now
997 enables just the iconv* functionality and is now on by default.
998 WITH_LIBICONV_COMPAT enables the libiconv api and link time
999 compatibility. Set WITHOUT_ICONV to build the old way.
1000 If you have been using WITH_ICONV before, you will very likely
1001 need to turn on WITH_LIBICONV_COMPAT.
1004 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1005 Illumos origin, including ZFS. If you have INVARIANTS in your
1006 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1008 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1009 locks if WITNESS option was set. Because that generated a lot of
1010 witness(9) reports and all of them were believed to be false
1011 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1012 can be used to achieve the previous behavior.
1015 Timer values in IPv6 data structures now use time_uptime instead
1016 of time_second. Although this is not a user-visible functional
1017 change, userland utilities which directly use them---ndp(8),
1018 rtadvd(8), and rtsold(8) in the base system---need to be updated
1019 to r253970 or later.
1022 find -delete can now delete the pathnames given as arguments,
1023 instead of only files found below them or if the pathname did
1024 not contain any slashes. Formerly, the following error message
1027 find: -delete: <path>: relative path potentially not safe
1029 Deleting the pathnames given as arguments can be prevented
1030 without error messages using -mindepth 1 or by changing
1031 directory and passing "." as argument to find. This works in the
1032 old as well as the new version of find.
1035 Behavior of devfs rules path matching has been changed.
1036 Pattern is now always matched against fully qualified devfs
1037 path and slash characters must be explicitly matched by
1038 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1039 subdirectories must be reviewed.
1042 The default ARM ABI has changed to the ARM EABI. The old ABI is
1043 incompatible with the ARM EABI and all programs and modules will
1044 need to be rebuilt to work with a new kernel.
1046 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1048 NOTE: Support for the old ABI will be removed in the future and
1049 users are advised to upgrade.
1052 pkg_install has been disconnected from the build if you really need it
1053 you should add WITH_PKGTOOLS in your src.conf(5).
1056 Most of network statistics structures were changed to be able
1057 keep 64-bits counters. Thus all tools, that work with networking
1058 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1061 Fix a bug that allowed a tracing process (e.g. gdb) to write
1062 to a memory-mapped file in the traced process's address space
1063 even if neither the traced process nor the tracing process had
1064 write access to that file.
1067 CVS has been removed from the base system. An exact copy
1068 of the code is available from the devel/cvs port.
1071 Some people report the following error after the switch to bmake:
1073 make: illegal option -- J
1074 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1076 *** [buildworld] Error code 2
1078 this likely due to an old instance of make in
1079 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1080 which src/Makefile will use that blindly, if it exists, so if
1081 you see the above error:
1083 rm -rf `make -V MAKEPATH`
1088 Use bmake by default.
1089 Whereas before one could choose to build with bmake via
1090 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1091 make. The goal is to remove these knobs for 10-RELEASE.
1093 It is worth noting that bmake (like gmake) treats the command
1094 line as the unit of failure, rather than statements within the
1095 command line. Thus '(cd some/where && dosomething)' is safer
1096 than 'cd some/where; dosomething'. The '()' allows consistent
1097 behavior in parallel build.
1100 Fix a bug that allows NFS clients to issue READDIR on files.
1103 The WITHOUT_IDEA option has been removed because
1104 the IDEA patent expired.
1107 The sysctl which controls TRIM support under ZFS has been renamed
1108 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1112 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1113 rather than creating it's own in the temporary directory in
1114 order allow access to bootstrapped versions of tools such as
1115 install and mtree. When upgrading from version of FreeBSD where
1116 the install command does not support -l, you will need to
1117 install a new mergemaster command if mergemaster -p is required.
1118 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1122 Legacy ATA stack, disabled and replaced by new CAM-based one since
1123 FreeBSD 9.0, completely removed from the sources. Kernel modules
1124 atadisk and atapi*, user-level tools atacontrol and burncd are
1125 removed. Kernel option `options ATA_CAM` is now permanently enabled
1129 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1130 and socketpair(2). Software, in particular Kerberos, may
1131 automatically detect and use these during building. The resulting
1132 binaries will not work on older kernels.
1135 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1136 information, see the respective 20130304 entry).
1139 Recent commits to callout(9) changed the size of struct callout,
1140 so the KBI is probably heavily disturbed. Also, some functions
1141 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1142 by macros. Every kernel module using it won't load, so rebuild
1145 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1146 but does not initialize by default (because of the new CTL_DISABLE
1147 option) to save memory. To re-enable it, remove the CTL_DISABLE
1148 option from the kernel config file or set kern.cam.ctl.disable=0
1149 in /boot/loader.conf.
1152 The ctl device has been disabled in GENERIC for i386 and amd64.
1153 This was done due to the extra memory being allocated at system
1154 initialisation time by the ctl driver which was only used if
1155 a CAM target device was created. This makes a FreeBSD system
1156 unusable on 128MB or less of RAM.
1159 A new compression method (lz4) has been merged to -HEAD. Please
1160 refer to zpool-features(7) for more information.
1162 Please refer to the "ZFS notes" section of this file for information
1163 on upgrading boot ZFS pools.
1166 A BSD-licensed patch(1) variant has been added and is installed
1167 as bsdpatch, being the GNU version the default patch.
1168 To inverse the logic and use the BSD-licensed one as default,
1169 while having the GNU version installed as gnupatch, rebuild
1170 and install world with the WITH_BSD_PATCH knob set.
1173 Due to the use of the new -l option to install(1) during build
1174 and install, you must take care not to directly set the INSTALL
1175 make variable in your /etc/make.conf, /etc/src.conf, or on the
1176 command line. If you wish to use the -C flag for all installs
1177 you may be able to add INSTALL+=-C to /etc/make.conf or
1181 The install(1) option -M has changed meaning and now takes an
1182 argument that is a file or path to append logs to. In the
1183 unlikely event that -M was the last option on the command line
1184 and the command line contained at least two files and a target
1185 directory the first file will have logs appended to it. The -M
1186 option served little practical purpose in the last decade so its
1187 use is expected to be extremely rare.
1190 After switching to Clang as the default compiler some users of ZFS
1191 on i386 systems started to experience stack overflow kernel panics.
1192 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1195 GEOM_LABEL now mangles label names read from file system metadata.
1196 Mangling affect labels containing spaces, non-printable characters,
1197 '%' or '"'. Device names in /etc/fstab and other places may need to
1201 By default, only the 10 most recent kernel dumps will be saved. To
1202 restore the previous behaviour (no limit on the number of kernel dumps
1203 stored in the dump directory) add the following line to /etc/rc.conf:
1208 With the addition of auditdistd(8), a new auditdistd user is now
1209 required during installworld. "mergemaster -p" can be used to
1210 add the user prior to installworld, as documented in the handbook.
1213 The sin6_scope_id member variable in struct sockaddr_in6 is now
1214 filled by the kernel before passing the structure to the userland via
1215 sysctl or routing socket. This means the KAME-specific embedded scope
1216 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1217 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1218 __FreeBSD_version is bumped to 1000025.
1221 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1222 This means that the world and kernel will be compiled with clang
1223 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1224 and /usr/bin/cpp. To disable this behavior and revert to building
1225 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1226 of current may need to bootstrap WITHOUT_CLANG first if the clang
1227 build fails (its compatibility window doesn't extend to the 9 stable
1231 The IPFIREWALL_FORWARD kernel option has been removed. Its
1232 functionality now turned on by default.
1235 The ZERO_COPY_SOCKET kernel option has been removed and
1236 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1237 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1238 mechanism which is not safe and may result in kernel crashes.
1239 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1240 driver supports disposeable external page sized mbuf storage.
1241 Proper replacements for both zero-copy mechanisms are under
1242 consideration and will eventually lead to complete removal
1243 of the two kernel options.
1246 The IPv4 network stack has been converted to network byte
1247 order. The following modules need to be recompiled together
1248 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1249 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1252 Support for non-MPSAFE filesystems was removed from VFS. The
1253 VFS_VERSION was bumped, all filesystem modules shall be
1257 All the non-MPSAFE filesystems have been disconnected from
1258 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1259 portalfs, smbfs, xfs.
1262 The interface cloning API and ABI has changed. The following
1263 modules need to be recompiled together with kernel:
1264 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1265 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1266 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1269 The sdhci driver was split in two parts: sdhci (generic SD Host
1270 Controller logic) and sdhci_pci (actual hardware driver).
1271 No kernel config modifications are required, but if you
1272 load sdhc as a module you must switch to sdhci_pci instead.
1275 Import the FUSE kernel and userland support into base system.
1278 The GNU sort(1) program has been removed since the BSD-licensed
1279 sort(1) has been the default for quite some time and no serious
1280 problems have been reported. The corresponding WITH_GNU_SORT
1284 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1285 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1289 The net80211(4) ABI has been changed to allow for improved driver
1290 PS-POLL and power-save support. All wireless drivers need to be
1291 recompiled to work with the new kernel.
1294 The random(4) support for the VIA hardware random number
1295 generator (`PADLOCK') is no longer enabled unconditionally.
1296 Add the padlock_rng device in the custom kernel config if
1297 needed. The GENERIC kernels on i386 and amd64 do include the
1298 device, so the change only affects the custom kernel
1302 The pf(4) packet filter ABI has been changed. pfctl(8) and
1303 snmp_pf module need to be recompiled to work with new kernel.
1306 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1307 to -HEAD. Pools that have empty_bpobj in active state can not be
1308 imported read-write with ZFS implementations that do not support
1309 this feature. For more information read the zpool-features(5)
1313 The sparc64 ZFS loader has been changed to no longer try to auto-
1314 detect ZFS providers based on diskN aliases but now requires these
1315 to be explicitly listed in the OFW boot-device environment variable.
1318 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1319 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1320 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1323 The following sysctls and tunables have been renamed for consistency
1324 with other variables:
1325 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1326 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1329 The sort utility has been replaced with BSD sort. For now, GNU sort
1330 is also available as "gnusort" or the default can be set back to
1331 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1332 installed as "bsdsort".
1335 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1336 Starting with this version the old system of ZFS pool versioning
1337 is superseded by "feature flags". This concept enables forward
1338 compatibility against certain future changes in functionality of ZFS
1339 pools. The first read-only compatible "feature flag" for ZFS pools
1340 is named "com.delphix:async_destroy". For more information
1341 read the new zpool-features(5) manual page.
1342 Please refer to the "ZFS notes" section of this file for information
1343 on upgrading boot ZFS pools.
1346 The malloc(3) implementation embedded in libc now uses sources imported
1347 as contrib/jemalloc. The most disruptive API change is to
1348 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1349 delete it prior to installworld, and optionally re-create it using the
1350 new format after rebooting. See malloc.conf(5) for details
1351 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1355 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1356 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1357 now spelled mips. This is to aid compatibility with third-party
1358 software that expects this naming scheme in uname(3). Little-endian
1359 settings are unchanged. If you are updating a big-endian mips64 machine
1360 from before this change, you may need to set MACHINE_ARCH=mips64 in
1361 your environment before the new build system will recognize your machine.
1364 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1368 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1369 nullfs(5) did not pass through all behaviours to the underlying layer,
1370 as a result if we bound to a socket on the lower layer we could connect
1371 only to the lower path; if we bound to the upper layer we could connect
1372 only to the upper path. The new behavior is one can connect to both the
1373 lower and the upper paths regardless what layer path one binds to.
1376 The getifaddrs upgrade path broken with 20111215 has been restored.
1377 If you have upgraded in between 20111215 and 20120209 you need to
1378 recompile libc again with your kernel. You still need to recompile
1379 world to be able to configure CARP but this restriction already
1380 comes from 20111215.
1383 The set_rcvar() function has been removed from /etc/rc.subr. All
1384 base and ports rc.d scripts have been updated, so if you have a
1385 port installed with a script in /usr/local/etc/rc.d you can either
1386 hand-edit the rcvar= line, or reinstall the port.
1388 An easy way to handle the mass-update of /etc/rc.d:
1389 rm /etc/rc.d/* && mergemaster -i
1392 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1393 on the current CPU and prevents other threads from running.
1394 This behavior can be reverted using the kern.stop_scheduler_on_panic
1396 The new behavior can be incompatible with kern.sync_on_panic.
1399 The carp(4) facility has been changed significantly. Configuration
1400 of the CARP protocol via ifconfig(8) has changed, as well as format
1401 of CARP events submitted to devd(8) has changed. See manual pages
1402 for more information. The arpbalance feature of carp(4) is currently
1403 not supported anymore.
1405 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1406 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1407 need to be recompiled.
1410 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1414 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1415 explicitely support non-MPSAFE filesystems.
1416 It is on by default for all supported platform at this present
1420 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1421 i386 and pc98 GENERIC kernel configuration files.
1424 sysinstall has been removed
1427 The stable/9 branch created in subversion. This corresponds to the
1428 RELENG_9 branch in CVS.
1434 Avoid using make -j when upgrading. While generally safe, there are
1435 sometimes problems using -j to upgrade. If your upgrade fails with
1436 -j, please try again without -j. From time to time in the past there
1437 have been problems using -j with buildworld and/or installworld. This
1438 is especially true when upgrading between "distant" versions (eg one
1439 that cross a major release boundary or several minor releases, or when
1440 several months have passed on the -current branch).
1442 Sometimes, obscure build problems are the result of environment
1443 poisoning. This can happen because the make utility reads its
1444 environment when searching for values for global variables. To run
1445 your build attempts in an "environmental clean room", prefix all make
1446 commands with 'env -i '. See the env(1) manual page for more details.
1448 When upgrading from one major version to another it is generally best
1449 to upgrade to the latest code in the currently installed branch first,
1450 then do an upgrade to the new branch. This is the best-tested upgrade
1451 path, and has the highest probability of being successful. Please try
1452 this approach before reporting problems with a major version upgrade.
1454 When upgrading a live system, having a root shell around before
1455 installing anything can help undo problems. Not having a root shell
1456 around can lead to problems if pam has changed too much from your
1457 starting point to allow continued authentication after the upgrade.
1459 This file should be read as a log of events. When a later event changes
1460 information of a prior event, the prior event should not be deleted.
1461 Instead, a pointer to the entry with the new information should be
1462 placed in the old entry. Readers of this file should also sanity check
1463 older entries before relying on them blindly. Authors of new entries
1464 should write them with this in mind.
1468 When upgrading the boot ZFS pool to a new version, always follow
1471 1.) recompile and reinstall the ZFS boot loader and boot block
1472 (this is part of "make buildworld" and "make installworld")
1474 2.) update the ZFS boot block on your boot drive
1476 The following example updates the ZFS boot block on the first
1477 partition (freebsd-boot) of a GPT partitioned drive ada0:
1478 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1480 Non-boot pools do not need these updates.
1484 If you are updating from a prior version of FreeBSD (even one just
1485 a few days old), you should follow this procedure. It is the most
1486 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1488 make kernel-toolchain
1489 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1490 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1492 To test a kernel once
1493 ---------------------
1494 If you just want to boot a kernel once (because you are not sure
1495 if it works, or if you want to boot a known bad kernel to provide
1496 debugging information) run
1497 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1498 nextboot -k testkernel
1500 To just build a kernel when you know that it won't mess you up
1501 --------------------------------------------------------------
1502 This assumes you are already running a CURRENT system. Replace
1503 ${arch} with the architecture of your machine (e.g. "i386",
1504 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1506 cd src/sys/${arch}/conf
1507 config KERNEL_NAME_HERE
1508 cd ../compile/KERNEL_NAME_HERE
1513 If this fails, go to the "To build a kernel" section.
1515 To rebuild everything and install it on the current system.
1516 -----------------------------------------------------------
1517 # Note: sometimes if you are running current you gotta do more than
1518 # is listed here if you are upgrading from a really old current.
1520 <make sure you have good level 0 dumps>
1522 make kernel KERNCONF=YOUR_KERNEL_HERE
1524 <reboot in single user> [3]
1531 To cross-install current onto a separate partition
1532 --------------------------------------------------
1533 # In this approach we use a separate partition to hold
1534 # current's root, 'usr', and 'var' directories. A partition
1535 # holding "/", "/usr" and "/var" should be about 2GB in
1538 <make sure you have good level 0 dumps>
1541 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1542 <maybe newfs current's root partition>
1543 <mount current's root partition on directory ${CURRENT_ROOT}>
1544 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1545 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1546 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1547 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1548 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1549 <reboot into current>
1550 <do a "native" rebuild/install as described in the previous section>
1551 <maybe install compatibility libraries from ports/misc/compat*>
1555 To upgrade in-place from stable to current
1556 ----------------------------------------------
1557 <make sure you have good level 0 dumps>
1559 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1561 <reboot in single user> [3]
1568 Make sure that you've read the UPDATING file to understand the
1569 tweaks to various things you need. At this point in the life
1570 cycle of current, things change often and you are on your own
1571 to cope. The defaults can also change, so please read ALL of
1572 the UPDATING entries.
1574 Also, if you are tracking -current, you must be subscribed to
1575 freebsd-current@freebsd.org. Make sure that before you update
1576 your sources that you have read and understood all the recent
1577 messages there. If in doubt, please track -stable which has
1578 much fewer pitfalls.
1580 [1] If you have third party modules, such as vmware, you
1581 should disable them at this point so they don't crash your
1584 [3] From the bootblocks, boot -s, and then do
1589 adjkerntz -i # if CMOS is wall time
1590 Also, when doing a major release upgrade, it is required that
1591 you boot into single user mode to do the installworld.
1593 [4] Note: This step is non-optional. Failure to do this step
1594 can result in a significant reduction in the functionality of the
1595 system. Attempting to do it by hand is not recommended and those
1596 that pursue this avenue should read this file carefully, as well
1597 as the archives of freebsd-current and freebsd-hackers mailing lists
1598 for potential gotchas. The -U option is also useful to consider.
1599 See mergemaster(8) for more information.
1601 [5] Usually this step is a noop. However, from time to time
1602 you may need to do this if you get unknown user in the following
1603 step. It never hurts to do it all the time. You may need to
1604 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1605 install) after the buildworld before this step if you last updated
1606 from current before 20130425 or from -stable before 20130430.
1608 [6] This only deletes old files and directories. Old libraries
1609 can be deleted by "make delete-old-libs", but you have to make
1610 sure that no program is using those libraries anymore.
1612 [8] In order to have a kernel that can run the 4.x binaries needed to
1613 do an installworld, you must include the COMPAT_FREEBSD4 option in
1614 your kernel. Failure to do so may leave you with a system that is
1615 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1616 required to run the 5.x binaries on more recent kernels. And so on
1617 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1619 Make sure that you merge any new devices from GENERIC since the
1620 last time you updated your kernel config file.
1622 [9] When checking out sources, you must include the -P flag to have
1623 cvs prune empty directories.
1625 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1626 "?=" instead of the "=" assignment operator, so that buildworld can
1627 override the CPUTYPE if it needs to.
1629 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1630 not on the command line, or in /etc/make.conf. buildworld will
1631 warn if it is improperly defined.
1634 This file contains a list, in reverse chronological order, of major
1635 breakages in tracking -current. It is not guaranteed to be a complete
1636 list of such breakages, and only contains entries since September 23, 2011.
1637 If you need to see UPDATING entries from before that date, you will need
1638 to fetch an UPDATING file from an older FreeBSD release.
1640 Copyright information:
1642 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1644 Redistribution, publication, translation and use, with or without
1645 modification, in full or in part, in any form or format of this
1646 document are permitted without further permission from the author.
1648 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1649 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1650 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1651 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1652 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1653 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1654 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1655 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1656 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1657 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1658 POSSIBILITY OF SUCH DAMAGE.
1660 Contact Warner Losh if you have any questions about your use of