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