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