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