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.
20 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
21 Please see the 20141231 entry below for information about prerequisites
22 and upgrading, if you are not already using clang 3.5.0 or higher.
25 The code that provides support for ZFS .zfs/ directory functionality
26 has been reimplemented. It's not possible now to create a snapshot
27 by mkdir under .zfs/snapshot/. That should be the only user visible
31 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
32 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
33 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
34 and now NAT-T is supported by default. Security associations now use
35 the single namespace for SPI allocation, so if you use several manually
36 configured security associations with the same SPI, this configuration
40 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
41 Please see the 20141231 entry below for information about prerequisites
42 and upgrading, if you are not already using clang 3.5.0 or higher.
45 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
46 Please see the 20141231 entry below for information about prerequisites
47 and upgrading, if you are not already using clang 3.5.0 or higher.
50 The layout of the pmap structure has changed for powerpc to put the pmap
51 statistics at the front for all CPU variations. libkvm(3) and all tools
52 that link against it need to be recompiled.
55 isl(4) and cyapa(4) drivers now require a new driver,
56 chromebook_platform(4), to work properly on Chromebook-class hardware.
57 On other types of hardware the drivers may need to be configured using
58 device hints. Please see the corresponding manual pages for details.
61 Relocatable object files with the extension of .So have been renamed
62 to use an extension of .pico instead. The purpose of this change is
63 to avoid a name clash with shared libraries on case-insensitive file
64 systems. On those file systems, foo.So is the same file as foo.so.
67 The libc stub for the pipe(2) system call has been replaced with
68 a wrapper that calls the pipe2(2) system call and the pipe(2)
69 system call is now only implemented by the kernels that include
70 "options COMPAT_FREEBSD10" in their config file (this is the
71 default). Users should ensure that this option is enabled in
72 their kernel or upgrade userspace to r302092 before upgrading their
76 CAM will now strip leading spaces from SCSI disks' serial numbers.
77 This will effect users who create UFS filesystems on SCSI disks using
78 those disk's diskid device nodes. For example, if /etc/fstab
79 previously contained a line like
80 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
81 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
82 transforms like gmirror may also be affected. ZFS users should
86 The bitstring(3) API has been updated with new functionality and
87 improved performance. But it is binary-incompatible with the old API.
88 Objects built with the new headers may not be linked against objects
89 built with the old headers.
92 The brk and sbrk functions have been removed from libc on arm64.
93 Binutils from ports has been updated to not link to these
94 functions and should be updated to the latest version before
95 installing a new libc.
98 The armv6 port now defaults to hard float ABI. Limited support
99 for running both hardfloat and soft float on the same system
100 is available using the libraries installed with -DWITH_LIBSOFT.
101 This has only been tested as an upgrade path for installworld
102 and packages may fail or need manual intervention to run. New
103 packages will be needed.
105 To update an existing self-hosted armv6hf system, you must add
106 TARGET_ARCH=armv6 on the make command line for both the build
107 and the install steps.
110 Kernel modules compiled outside of a kernel build now default to
111 installing to /boot/modules instead of /boot/kernel. Many kernel
112 modules built this way (such as those in ports) already overrode
113 KMODDIR explicitly to install into /boot/modules. However,
114 manually building and installing a module from /sys/modules will
115 now install to /boot/modules instead of /boot/kernel.
118 The CAM I/O scheduler has been committed to the kernel. There should be
119 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
120 list of known rogues that claim support for this but actually corrupt
121 data is believed to be complete, be on the lookout for data
122 corruption. The known rogue list is believed to be complete:
124 o Crucial MX100, M550 drives with MU01 firmware.
125 o Micron M510 and M550 drives with MU01 firmware.
126 o Micron M500 prior to MU07 firmware
127 o Samsung 830, 840, and 850 all firmwares
128 o FCCT M500 all firmwares
130 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
131 with working NCQ TRIM. For Micron branded drives, see your sales rep for
132 updated firmware. Black listed drives will work correctly because these
133 drives work correctly so long as no NCQ TRIMs are sent to them. Given
134 this list is the same as found in Linux, it's believed there are no
135 other rogues in the market place. All other models from the above
138 To be safe, if you are at all concerned, you can quirk each of your
139 drives to prevent NCQ from being sent by setting:
140 kern.cam.ada.X.quirks="0x2"
141 in loader.conf. If the drive requires the 4k sector quirk, set the
145 The FAST_DEPEND build option has been removed and its functionality is
146 now the one true way. The old mkdep(1) style of 'make depend' has
147 been removed. See 20160311 for further details.
150 Resource range types have grown from unsigned long to uintmax_t. All
151 drivers, and anything using libdevinfo, need to be recompiled.
154 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
155 builds. It no longer runs mkdep(1) during 'make depend', and the
156 'make depend' stage can safely be skipped now as it is auto ran
157 when building 'make all' and will generate all SRCS and DPSRCS before
158 building anything else. Dependencies are gathered at compile time with
159 -MF flags kept in separate .depend files per object file. Users should
160 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
164 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
165 kernel modules. Therefore, if you load any kernel modules at boot time,
166 please install the boot loaders after you install the kernel, but before
170 make kernel KERNCONF=YOUR_KERNEL_HERE
171 make -C sys/boot install
172 <reboot in single user>
174 Then follow the usual steps, described in the General Notes section,
178 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
179 see the 20141231 entry below for information about prerequisites and
180 upgrading, if you are not already using clang 3.5.0 or higher.
183 The AIO subsystem is now a standard part of the kernel. The
184 VFS_AIO kernel option and aio.ko kernel module have been removed.
185 Due to stability concerns, asynchronous I/O requests are only
186 permitted on sockets and raw disks by default. To enable
187 asynchronous I/O requests on all file types, set the
188 vfs.aio.enable_unsafe sysctl to a non-zero value.
191 The ELF object manipulation tool objcopy is now provided by the
192 ELF Tool Chain project rather than by GNU binutils. It should be a
193 drop-in replacement, with the addition of arm64 support. The
194 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
195 to obtain the GNU version if necessary.
198 Building ZFS pools on top of zvols is prohibited by default. That
199 feature has never worked safely; it's always been prone to deadlocks.
200 Using a zvol as the backing store for a VM guest's virtual disk will
201 still work, even if the guest is using ZFS. Legacy behavior can be
202 restored by setting vfs.zfs.vol.recursive=1.
205 The NONE and HPN patches has been removed from OpenSSH. They are
206 still available in the security/openssh-portable port.
209 With the addition of ypldap(8), a new _ypldap user is now required
210 during installworld. "mergemaster -p" can be used to add the user
211 prior to installworld, as documented in the handbook.
214 The tftp loader (pxeboot) now uses the option root-path directive. As a
215 consequence it no longer looks for a pxeboot.4th file on the tftp
216 server. Instead it uses the regular /boot infrastructure as with the
220 The code to start recording plug and play data into the modules has
221 been committed. While the old tools will properly build a new kernel,
222 a number of warnings about "unknown metadata record 4" will be produced
223 for an older kldxref. To avoid such warnings, make sure to rebuild
224 the kernel toolchain (or world). Make sure that you have r292078 or
225 later when trying to build 292077 or later before rebuilding.
228 Debug data files are now built by default with 'make buildworld' and
229 installed with 'make installworld'. This facilitates debugging but
230 requires more disk space both during the build and for the installed
231 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
235 r291527 changed the internal interface between the nfsd.ko and
236 nfscommon.ko modules. As such, they must both be upgraded to-gether.
237 __FreeBSD_version has been bumped because of this.
240 Add support for unicode collation strings leads to a change of
241 order of files listed by ls(1) for example. To get back to the old
242 behaviour, set LC_COLLATE environment variable to "C".
244 Databases administrators will need to reindex their databases given
245 collation results will be different.
247 Due to a bug in install(1) it is recommended to remove the ancient
248 locales before running make installworld.
250 rm -rf /usr/share/locale/*
253 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
254 libcrypto.so.7 or libssl.so.7 must be recompiled.
257 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
258 Kernel modules isp_2400_multi and isp_2500_multi were removed and
259 should be replaced with isp_2400 and isp_2500 modules respectively.
262 The build previously allowed using 'make -n' to not recurse into
263 sub-directories while showing what commands would be executed, and
264 'make -n -n' to recursively show commands. Now 'make -n' will recurse
265 and 'make -N' will not.
268 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
269 and etcupdate will now use this file. A custom sendmail.cf is now
270 updated via this mechanism rather than via installworld. If you had
271 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
272 want to remove the exclusion or change it to "always install".
273 /etc/mail/sendmail.cf is now managed the same way regardless of
274 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
275 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
278 Compatibility shims for legacy ATA device names have been removed.
279 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
280 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
281 environment variables, /dev/ad* and /dev/ar* symbolic links.
284 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
285 Please see the 20141231 entry below for information about prerequisites
286 and upgrading, if you are not already using clang 3.5.0 or higher.
289 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
290 and renamed from .symbols to .debug. This reduces the size requirements
291 on the boot partition or file system and provides consistency with
292 userland debug files.
294 When using the supported kernel installation method the
295 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
296 as is done with /boot/kernel.
298 Developers wishing to maintain the historical behavior of installing
299 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
302 The wireless drivers had undergone changes that remove the 'parent
303 interface' from the ifconfig -l output. The rc.d network scripts
304 used to check presence of a parent interface in the list, so old
305 scripts would fail to start wireless networking. Thus, etcupdate(3)
306 or mergemaster(8) run is required after kernel update, to update your
307 rc.d scripts in /etc.
310 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
311 These configurations are now automatically interpreted as
312 'scrub fragment reassemble'.
315 Kernel-loadable modules for the random(4) device are back. To use
316 them, the kernel must have
319 options RANDOM_LOADABLE
321 kldload(8) can then be used to load random_fortuna.ko
322 or random_yarrow.ko. Please note that due to the indirect
323 function calls that the loadable modules need to provide,
324 the build-in variants will be slightly more efficient.
326 The random(4) kernel option RANDOM_DUMMY has been retired due to
327 unpopularity. It was not all that useful anyway.
330 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
331 Control over building the ELF Tool Chain tools is now provided by
332 the WITHOUT_TOOLCHAIN knob.
335 The polarity of Pulse Per Second (PPS) capture events with the
336 uart(4) driver has been corrected. Prior to this change the PPS
337 "assert" event corresponded to the trailing edge of a positive PPS
338 pulse and the "clear" event was the leading edge of the next pulse.
340 As the width of a PPS pulse in a typical GPS receiver is on the
341 order of 1 millisecond, most users will not notice any significant
342 difference with this change.
344 Anyone who has compensated for the historical polarity reversal by
345 configuring a negative offset equal to the pulse width will need to
346 remove that workaround.
349 The default group assigned to /dev/dri entries has been changed
350 from 'wheel' to 'video' with the id of '44'. If you want to have
351 access to the dri devices please add yourself to the video group
354 # pw groupmod video -m $USER
357 The menu.rc and loader.rc files will now be replaced during
358 upgrades. Please migrate local changes to menu.rc.local and
359 loader.rc.local instead.
362 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
363 strings and strip have been removed. The src.conf(5) knob
364 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
367 As ZFS requires more kernel stack pages than is the default on some
368 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
369 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
371 Please consider using 'options KSTACK_PAGES=X' where X is greater
372 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
375 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
376 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
377 default, i.e., they will not contain "::". For example, instead
378 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
379 to have a more specific match, such as different map entries for
380 IPv6:0:0 vs IPv6:0. This change requires that configuration
381 data (including maps, files, classes, custom ruleset, etc.) must
382 use the same format, so make certain such configuration data is
383 upgrading. As a very simple check search for patterns like
384 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
385 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
386 the cf option UseCompressedIPv6Addresses.
389 The default kernel entropy-processing algorithm is now
390 Fortuna, replacing Yarrow.
392 Assuming you have 'device random' in your kernel config
393 file, the configurations allow a kernel option to override
394 this default. You may choose *ONE* of:
396 options RANDOM_YARROW # Legacy /dev/random algorithm.
397 options RANDOM_DUMMY # Blocking-only driver.
399 If you have neither, you get Fortuna. For most people,
400 read no further, Fortuna will give a /dev/random that works
401 like it always used to, and the difference will be irrelevant.
403 If you remove 'device random', you get *NO* kernel-processed
404 entropy at all. This may be acceptable to folks building
405 embedded systems, but has complications. Carry on reading,
406 and it is assumed you know what you need.
408 *PLEASE* read random(4) and random(9) if you are in the
409 habit of tweaking kernel configs, and/or if you are a member
410 of the embedded community, wanting specific and not-usual
411 behaviour from your security subsystems.
413 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
414 random', you will NOT have a functioning /dev/random, and
415 many cryptographic features will not work, including SSH.
416 You may also find strange behaviour from the random(3) set
417 of library functions, in particular sranddev(3), srandomdev(3)
418 and arc4random(3). The reason for this is that the KERN_ARND
419 sysctl only returns entropy if it thinks it has some to
420 share, and with RANDOM_DUMMY or no 'device random' this
424 An additional fix for the issue described in the 20150614 sendmail
425 entry below has been been committed in revision 284717.
428 FreeBSD's old make (fmake) has been removed from the system. It is
429 available as the devel/fmake port or via pkg install fmake.
432 The fix for the issue described in the 20150614 sendmail entry
433 below has been been committed in revision 284436. The work
434 around described in that entry is no longer needed unless the
435 default setting is overridden by a confDH_PARAMETERS configuration
436 setting of '5' or pointing to a 512 bit DH parameter file.
439 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
440 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
441 and devel/kyua to version 0.20+ and adjust any calling code to work
442 with Kyuafile and kyua.
445 The import of openssl to address the FreeBSD-SA-15:10.openssl
446 security advisory includes a change which rejects handshakes
447 with DH parameters below 768 bits. sendmail releases prior
448 to 8.15.2 (not yet released), defaulted to a 512 bit
449 DH parameter setting for client connections. To work around
450 this interoperability, sendmail can be configured to use a
451 2048 bit DH parameter by:
453 1. Edit /etc/mail/`hostname`.mc
454 2. If a setting for confDH_PARAMETERS does not exist or
455 exists and is set to a string beginning with '5',
457 3. If a setting for confDH_PARAMETERS exists and is set to
458 a file path, create a new file with:
459 openssl dhparam -out /path/to/file 2048
460 4. Rebuild the .cf file:
461 cd /etc/mail/; make; make install
463 cd /etc/mail/; make restart
465 A sendmail patch is coming, at which time this file will be
469 Generation of legacy formatted entries have been disabled by default
470 in pwd_mkdb(8), as all base system consumers of the legacy formatted
471 entries were converted to use the new format by default when the new,
472 machine independent format have been added and supported since FreeBSD
475 Please see the pwd_mkdb(8) manual page for further details.
478 Clang and llvm have been upgraded to 3.6.1 release. Please see the
479 20141231 entry below for information about prerequisites and upgrading,
480 if you are not already using 3.5.0 or higher.
483 TI platform code switched to using vendor DTS files and this update
484 may break existing systems running on Beaglebone, Beaglebone Black,
487 - dtb files should be regenerated/reinstalled. Filenames are the
488 same but content is different now
489 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
490 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
491 addressing scheme is now pin 25 on /dev/gpioc3.
492 - Pandaboard: /etc/ttys should be updated, serial console device is
493 now /dev/ttyu2, not /dev/ttyu0
496 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
497 If you need the GNU extension from groff soelim(1), install groff
498 from package: pkg install groff, or via ports: textproc/groff.
501 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
502 defined in symlink(7); previously symlinks were silently ignored.
505 The const qualifier has been removed from iconv(3) to comply with
506 POSIX. The ports tree is aware of this from r384038 onwards.
509 Libraries specified by LIBADD in Makefiles must have a corresponding
510 DPADD_<lib> variable to ensure correct dependencies. This is now
511 enforced in src.libnames.mk.
514 From legacy ata(4) driver was removed support for SATA controllers
515 supported by more functional drivers ahci(4), siis(4) and mvs(4).
516 Kernel modules ataahci and ataadaptec were removed completely,
517 replaced by ahci and mvs modules respectively.
520 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
521 the 20141231 entry below for information about prerequisites and
522 upgrading, if you are not already using 3.5.0 or higher.
525 The 32-bit PowerPC kernel has been changed to a position-independent
526 executable. This can only be booted with a version of loader(8)
527 newer than January 31, 2015, so make sure to update both world and
528 kernel before rebooting.
531 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
532 but before r278950, the RNG was not seeded properly. Immediately
533 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
534 ssh keys or openssl keys) that were generated w/ a kernel from that
535 range. This does not affect programs that directly used /dev/random
536 or /dev/urandom. All userland uses of arc4random(3) are affected.
539 The autofs(4) ABI was changed in order to restore binary compatibility
540 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
544 The powerpc64 kernel has been changed to a position-independent
545 executable. This can only be booted with a new version of loader(8),
546 so make sure to update both world and kernel before rebooting.
549 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
550 only release, no new features have been added. Please see the 20141231
551 entry below for information about prerequisites and upgrading, if you
552 are not already using 3.5.0.
555 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
556 taken from the ELF Tool Chain project rather than GNU binutils. They
557 should be drop-in replacements, with the addition of arm64 support.
558 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
559 binutils tools, if necessary. See 20150805 for updated information.
562 The default Unbound configuration now enables remote control
563 using a local socket. Users who have already enabled the
564 local_unbound service should regenerate their configuration
565 by running "service local_unbound setup" as root.
568 The GNU texinfo and GNU info pages have been removed.
569 To be able to view GNU info pages please install texinfo from ports.
572 Clang, llvm and lldb have been upgraded to 3.5.0 release.
574 As of this release, a prerequisite for building clang, llvm and lldb is
575 a C++11 capable compiler and C++11 standard library. This means that to
576 be able to successfully build the cross-tools stage of buildworld, with
577 clang as the bootstrap compiler, your system compiler or cross compiler
578 should either be clang 3.3 or later, or gcc 4.8 or later, and your
579 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
582 On any standard FreeBSD 10.x or 11.x installation, where clang and
583 libc++ are on by default (that is, on x86 or arm), this should work out
586 On 9.x installations where clang is enabled by default, e.g. on x86 and
587 powerpc, libc++ will not be enabled by default, so libc++ should be
588 built (with clang) and installed first. If both clang and libc++ are
589 missing, build clang first, then use it to build libc++.
591 On 8.x and earlier installations, upgrade to 9.x first, and then follow
592 the instructions for 9.x above.
594 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
595 default, and do not build clang.
597 Many embedded systems are resource constrained, and will not be able to
598 build clang in a reasonable time, or in some cases at all. In those
599 cases, cross building bootable systems on amd64 is a workaround.
601 This new version of clang introduces a number of new warnings, of which
602 the following are most likely to appear:
606 This warns in two cases, for both C and C++:
607 * When the code is trying to take the absolute value of an unsigned
608 quantity, which is effectively a no-op, and almost never what was
609 intended. The code should be fixed, if at all possible. If you are
610 sure that the unsigned quantity can be safely cast to signed, without
611 loss of information or undefined behavior, you can add an explicit
612 cast, or disable the warning.
614 * When the code is trying to take an absolute value, but the called
615 abs() variant is for the wrong type, which can lead to truncation.
616 If you want to disable the warning instead of fixing the code, please
617 make sure that truncation will not occur, or it might lead to unwanted
620 -Wtautological-undefined-compare and
621 -Wundefined-bool-conversion
623 These warn when C++ code is trying to compare 'this' against NULL, while
624 'this' should never be NULL in well-defined C++ code. However, there is
625 some legacy (pre C++11) code out there, which actively abuses this
626 feature, which was less strictly defined in previous C++ versions.
628 Squid and openjdk do this, for example. The warning can be turned off
629 for C++98 and earlier, but compiling the code in C++11 mode might result
630 in unexpected behavior; for example, the parts of the program that are
631 unreachable could be optimized away.
634 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
635 kernel sources have been removed. The .h files remain, since some
636 utilities include them. This will need to be fixed later.
637 If "mount -t oldnfs ..." is attempted, it will fail.
638 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
639 the utilities will report errors.
642 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
643 directories to top level SUBDIR variable when their parent
644 directory is included in LOCAL_DIRS. Users with build systems with
645 such hierarchies and without SUBDIR entries in the parent
646 directory Makefiles should add them or add the directories to
650 faith(4) and faithd(8) have been removed from the base system. Faith
651 has been obsolete for a very long time.
654 vt(4), the new console driver, is enabled by default. It brings
655 support for Unicode and double-width characters, as well as
656 support for UEFI and integration with the KMS kernel video
659 You may need to update your console settings in /etc/rc.conf,
660 most probably the keymap. During boot, /etc/rc.d/syscons will
661 indicate what you need to do.
663 vt(4) still has issues and lacks some features compared to
664 syscons(4). See the wiki for up-to-date information:
665 https://wiki.freebsd.org/Newcons
667 If you want to keep using syscons(4), you can do so by adding
668 the following line to /boot/loader.conf:
672 pjdfstest has been integrated into kyua as an opt-in test suite.
673 Please see share/doc/pjdfstest/README for more details on how to
677 gperf has been removed from the base system for architectures
678 that use clang. Ports that require gperf will obtain it from the
682 pjdfstest has been moved from tools/regression/pjdfstest to
686 At svn r271982, The default linux compat kernel ABI has been adjusted
687 to 2.6.18 in support of the linux-c6 compat ports infrastructure
688 update. If you wish to continue using the linux-f10 compat ports,
689 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
690 encouraged to update their linux-compat packages to linux-c6 during
691 their next update cycle.
694 The ofwfb driver, used to provide a graphics console on PowerPC when
695 using vt(4), no longer allows mmap() of all physical memory. This
696 will prevent Xorg on PowerPC with some ATI graphics cards from
697 initializing properly unless x11-servers/xorg-server is updated to
701 The xdev targets have been converted to using TARGET and
702 TARGET_ARCH instead of XDEV and XDEV_ARCH.
705 The default unbound configuration has been modified to address
706 issues with reverse lookups on networks that use private
707 address ranges. If you use the local_unbound service, run
708 "service local_unbound setup" as root to regenerate your
709 configuration, then "service local_unbound reload" to load the
713 The GNU texinfo and GNU info pages are not built and installed
714 anymore, WITH_INFO knob has been added to allow to built and install
716 UPDATE: see 20150102 entry on texinfo's removal
719 The GNU readline library is now an INTERNALLIB - that is, it is
720 statically linked into consumers (GDB and variants) in the base
721 system, and the shared library is no longer installed. The
722 devel/readline port is available for third party software that
726 The Itanium architecture (ia64) has been removed from the list of
727 known architectures. This is the first step in the removal of the
731 Commit r268115 has added NFSv4.1 server support, merged from
732 projects/nfsv4.1-server. Since this includes changes to the
733 internal interfaces between the NFS related modules, a full
734 build of the kernel and modules will be necessary.
735 __FreeBSD_version has been bumped.
738 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
739 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
740 which differs from the behaviour controlled by this knob.)
743 Maximal length of the serial number in CTL was increased from 16 to
744 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
745 and ctld, need to be rebuilt to work with a new kernel.
748 The libatf-c and libatf-c++ major versions were downgraded to 0 and
749 1 respectively to match the upstream numbers. They were out of
750 sync because, when they were originally added to FreeBSD, the
751 upstream versions were not respected. These libraries are private
752 and not yet built by default, so renumbering them should be a
753 non-issue. However, unclean source trees will yield broken test
754 programs once the operator executes "make delete-old-libs" after a
757 Additionally, the atf-sh binary was made private by moving it into
758 /usr/libexec/. Already-built shell test programs will keep the
759 path to the old binary so they will break after "make delete-old"
762 If you are using WITH_TESTS=yes (not the default), wipe the object
763 tree and rebuild from scratch to prevent spurious test failures.
764 This is only needed once: the misnumbered libraries and misplaced
765 binaries have been added to OptionalObsoleteFiles.inc so they will
766 be removed during a clean upgrade.
769 Clang and llvm have been upgraded to 3.4.1 release.
772 We bogusly installed src.opts.mk in /usr/share/mk. This file should
773 be removed to avoid issues in the future (and has been added to
777 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
778 past, it affected all builds that used the bsd.*.mk files. The old
779 behavior was a bug, but people may have relied upon it. To get this
780 behavior back, you can .include /etc/src.conf from /etc/make.conf
781 (which is still global and isn't changed). This also changes the
782 behavior of incremental builds inside the tree of individual
783 directories. Set MAKESYSPATH to ".../share/mk" to do that.
784 Although this has survived make universe and some upgrade scenarios,
785 other upgrade scenarios may have broken. At least one form of
786 temporary breakage was fixed with MAKESYSPATH settings for buildworld
787 as well... In cases where MAKESYSPATH isn't working with this
788 setting, you'll need to set it to the full path to your tree.
790 One side effect of all this cleaning up is that bsd.compiler.mk
791 is no longer implicitly included by bsd.own.mk. If you wish to
792 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
796 The lindev device has been removed since /dev/full has been made a
797 standard device. __FreeBSD_version has been bumped.
800 The knob WITHOUT_VI was added to the base system, which controls
801 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
802 in order to reorder files share/termcap and didn't build ex(1) as a
803 build tool, so building/installing with WITH_VI is highly advised for
804 build hosts for older releases.
806 This issue has been fixed in stable/9 and stable/10 in r277022 and
807 r276991, respectively.
810 The YES_HESIOD knob has been removed. It has been obsolete for
811 a decade. Please move to using WITH_HESIOD instead or your builds
812 will silently lack HESIOD.
815 The uart(4) driver has been changed with respect to its handling
816 of the low-level console. Previously the uart(4) driver prevented
817 any process from changing the baudrate or the CLOCAL and HUPCL
818 control flags. By removing the restrictions, operators can make
819 changes to the serial console port without having to reboot.
820 However, when getty(8) is started on the serial device that is
821 associated with the low-level console, a misconfigured terminal
822 line in /etc/ttys will now have a real impact.
823 Before upgrading the kernel, make sure that /etc/ttys has the
824 serial console device configured as 3wire without baudrate to
825 preserve the previous behaviour. E.g:
826 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
829 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
830 to improve performance. To re-enable it, if needed, run rpcbind
831 with command line option -W.
834 Switched back to the GPL dtc compiler due to updates in the upstream
835 dts files not being supported by the BSDL dtc compiler. You will need
836 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
837 may result while building dtb files during a kernel build if you fail
838 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
841 Clang and llvm have been upgraded to 3.4 release.
844 The nve(4) driver has been removed. Please use the nfe(4) driver
845 for NVIDIA nForce MCP Ethernet adapters instead.
848 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
849 This could cause certain C++ applications using shared libraries built
850 against the previous version of libc++ to crash. The incompatibility
851 has now been fixed, but any C++ applications or shared libraries built
852 between r261283 and r261801 should be recompiled.
855 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
856 capability mode support. Please note that enabling the feature in
857 kernel is still highly recommended.
860 OpenSSH is now built with sandbox support, and will use sandbox as
861 the default privilege separation method. This requires Capsicum
862 capability mode support in kernel.
865 The libelf and libdwarf libraries have been updated to newer
866 versions from upstream. Shared library version numbers for
867 these two libraries were bumped. Any ports or binaries
868 requiring these two libraries should be recompiled.
869 __FreeBSD_version is bumped to 1100006.
872 If a Makefile in a tests/ directory was auto-generating a Kyuafile
873 instead of providing an explicit one, this would prevent such
874 Makefile from providing its own Kyuafile in the future during
875 NO_CLEAN builds. This has been fixed in the Makefiles but manual
876 intervention is needed to clean an objdir if you use NO_CLEAN:
877 # find /usr/obj -name Kyuafile | xargs rm -f
880 The behavior of gss_pseudo_random() for the krb5 mechanism
881 has changed, for applications requesting a longer random string
882 than produced by the underlying enctype's pseudo-random() function.
883 In particular, the random string produced from a session key of
884 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
885 be different at the 17th octet and later, after this change.
886 The counter used in the PRF+ construction is now encoded as a
887 big-endian integer in accordance with RFC 4402.
888 __FreeBSD_version is bumped to 1100004.
891 The WITHOUT_ATF build knob has been removed and its functionality
892 has been subsumed into the more generic WITHOUT_TESTS. If you were
893 using the former to disable the build of the ATF libraries, you
894 should change your settings to use the latter.
897 The default version of mtree is nmtree which is obtained from
898 NetBSD. The output is generally the same, but may vary
899 slightly. If you found you need identical output adding
900 "-F freebsd9" to the command line should do the trick. For the
901 time being, the old mtree is available as fmtree.
904 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
905 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
906 1.1.4_8 and verify bsdyml not linked in, before running "make
908 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
910 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
913 The stable/10 branch has been created in subversion from head
917 The rc.d/jail script has been updated to support jail(8)
918 configuration file. The "jail_<jname>_*" rc.conf(5) variables
919 for per-jail configuration are automatically converted to
920 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
921 This is transparently backward compatible. See below about some
922 incompatibilities and rc.conf(5) manual page for more details.
924 These variables are now deprecated in favor of jail(8) configuration
925 file. One can use "rc.d/jail config <jname>" command to generate
926 a jail(8) configuration file in /var/run/jail.<jname>.conf without
927 running the jail(8) utility. The default pathname of the
928 configuration file is /etc/jail.conf and can be specified by
929 using $jail_conf or $jail_<jname>_conf variables.
931 Please note that jail_devfs_ruleset accepts an integer at
932 this moment. Please consider to rewrite the ruleset name
936 BIND has been removed from the base system. If all you need
937 is a local resolver, simply enable and start the local_unbound
938 service instead. Otherwise, several versions of BIND are
939 available in the ports tree. The dns/bind99 port is one example.
941 With this change, nslookup(1) and dig(1) are no longer in the base
942 system. Users should instead use host(1) and drill(1) which are
943 in the base system. Alternatively, nslookup and dig can
944 be obtained by installing the dns/bind-tools port.
947 With the addition of unbound(8), a new unbound user is now
948 required during installworld. "mergemaster -p" can be used to
949 add the user prior to installworld, as documented in the handbook.
952 OpenSSH is now built with DNSSEC support, and will by default
953 silently trust signed SSHFP records. This can be controlled with
954 the VerifyHostKeyDNS client configuration setting. DNSSEC support
955 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
958 The GNU Compiler Collection and C++ standard library (libstdc++)
959 are no longer built by default on platforms where clang is the system
960 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
964 The PROCDESC kernel option is now part of the GENERIC kernel
965 configuration and is required for the rwhod(8) to work.
966 If you are using custom kernel configuration, you should include
970 The API and ABI related to the Capsicum framework was modified
971 in backward incompatible way. The userland libraries and programs
972 have to be recompiled to work with the new kernel. This includes the
973 following libraries and programs, but the whole buildworld is
974 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
975 kdump, procstat, rwho, rwhod, uniq.
978 AES-NI intrinsic support has been added to gcc. The AES-NI module
979 has been updated to use this support. A new gcc is required to build
980 the aesni module on both i386 and amd64.
983 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
984 Thus "device padlock_rng" and "device rdrand_rng" should be
985 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
988 WITH_ICONV has been split into two feature sets. WITH_ICONV now
989 enables just the iconv* functionality and is now on by default.
990 WITH_LIBICONV_COMPAT enables the libiconv api and link time
991 compatibility. Set WITHOUT_ICONV to build the old way.
992 If you have been using WITH_ICONV before, you will very likely
993 need to turn on WITH_LIBICONV_COMPAT.
996 INVARIANTS option now enables DEBUG for code with OpenSolaris and
997 Illumos origin, including ZFS. If you have INVARIANTS in your
998 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1000 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1001 locks if WITNESS option was set. Because that generated a lot of
1002 witness(9) reports and all of them were believed to be false
1003 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1004 can be used to achieve the previous behavior.
1007 Timer values in IPv6 data structures now use time_uptime instead
1008 of time_second. Although this is not a user-visible functional
1009 change, userland utilities which directly use them---ndp(8),
1010 rtadvd(8), and rtsold(8) in the base system---need to be updated
1011 to r253970 or later.
1014 find -delete can now delete the pathnames given as arguments,
1015 instead of only files found below them or if the pathname did
1016 not contain any slashes. Formerly, the following error message
1019 find: -delete: <path>: relative path potentially not safe
1021 Deleting the pathnames given as arguments can be prevented
1022 without error messages using -mindepth 1 or by changing
1023 directory and passing "." as argument to find. This works in the
1024 old as well as the new version of find.
1027 Behavior of devfs rules path matching has been changed.
1028 Pattern is now always matched against fully qualified devfs
1029 path and slash characters must be explicitly matched by
1030 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1031 subdirectories must be reviewed.
1034 The default ARM ABI has changed to the ARM EABI. The old ABI is
1035 incompatible with the ARM EABI and all programs and modules will
1036 need to be rebuilt to work with a new kernel.
1038 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1040 NOTE: Support for the old ABI will be removed in the future and
1041 users are advised to upgrade.
1044 pkg_install has been disconnected from the build if you really need it
1045 you should add WITH_PKGTOOLS in your src.conf(5).
1048 Most of network statistics structures were changed to be able
1049 keep 64-bits counters. Thus all tools, that work with networking
1050 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1053 Fix a bug that allowed a tracing process (e.g. gdb) to write
1054 to a memory-mapped file in the traced process's address space
1055 even if neither the traced process nor the tracing process had
1056 write access to that file.
1059 CVS has been removed from the base system. An exact copy
1060 of the code is available from the devel/cvs port.
1063 Some people report the following error after the switch to bmake:
1065 make: illegal option -- J
1066 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1068 *** [buildworld] Error code 2
1070 this likely due to an old instance of make in
1071 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1072 which src/Makefile will use that blindly, if it exists, so if
1073 you see the above error:
1075 rm -rf `make -V MAKEPATH`
1080 Use bmake by default.
1081 Whereas before one could choose to build with bmake via
1082 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1083 make. The goal is to remove these knobs for 10-RELEASE.
1085 It is worth noting that bmake (like gmake) treats the command
1086 line as the unit of failure, rather than statements within the
1087 command line. Thus '(cd some/where && dosomething)' is safer
1088 than 'cd some/where; dosomething'. The '()' allows consistent
1089 behavior in parallel build.
1092 Fix a bug that allows NFS clients to issue READDIR on files.
1095 The WITHOUT_IDEA option has been removed because
1096 the IDEA patent expired.
1099 The sysctl which controls TRIM support under ZFS has been renamed
1100 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1104 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1105 rather than creating it's own in the temporary directory in
1106 order allow access to bootstrapped versions of tools such as
1107 install and mtree. When upgrading from version of FreeBSD where
1108 the install command does not support -l, you will need to
1109 install a new mergemaster command if mergemaster -p is required.
1110 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1114 Legacy ATA stack, disabled and replaced by new CAM-based one since
1115 FreeBSD 9.0, completely removed from the sources. Kernel modules
1116 atadisk and atapi*, user-level tools atacontrol and burncd are
1117 removed. Kernel option `options ATA_CAM` is now permanently enabled
1121 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1122 and socketpair(2). Software, in particular Kerberos, may
1123 automatically detect and use these during building. The resulting
1124 binaries will not work on older kernels.
1127 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1128 information, see the respective 20130304 entry).
1131 Recent commits to callout(9) changed the size of struct callout,
1132 so the KBI is probably heavily disturbed. Also, some functions
1133 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1134 by macros. Every kernel module using it won't load, so rebuild
1137 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1138 but does not initialize by default (because of the new CTL_DISABLE
1139 option) to save memory. To re-enable it, remove the CTL_DISABLE
1140 option from the kernel config file or set kern.cam.ctl.disable=0
1141 in /boot/loader.conf.
1144 The ctl device has been disabled in GENERIC for i386 and amd64.
1145 This was done due to the extra memory being allocated at system
1146 initialisation time by the ctl driver which was only used if
1147 a CAM target device was created. This makes a FreeBSD system
1148 unusable on 128MB or less of RAM.
1151 A new compression method (lz4) has been merged to -HEAD. Please
1152 refer to zpool-features(7) for more information.
1154 Please refer to the "ZFS notes" section of this file for information
1155 on upgrading boot ZFS pools.
1158 A BSD-licensed patch(1) variant has been added and is installed
1159 as bsdpatch, being the GNU version the default patch.
1160 To inverse the logic and use the BSD-licensed one as default,
1161 while having the GNU version installed as gnupatch, rebuild
1162 and install world with the WITH_BSD_PATCH knob set.
1165 Due to the use of the new -l option to install(1) during build
1166 and install, you must take care not to directly set the INSTALL
1167 make variable in your /etc/make.conf, /etc/src.conf, or on the
1168 command line. If you wish to use the -C flag for all installs
1169 you may be able to add INSTALL+=-C to /etc/make.conf or
1173 The install(1) option -M has changed meaning and now takes an
1174 argument that is a file or path to append logs to. In the
1175 unlikely event that -M was the last option on the command line
1176 and the command line contained at least two files and a target
1177 directory the first file will have logs appended to it. The -M
1178 option served little practical purpose in the last decade so its
1179 use is expected to be extremely rare.
1182 After switching to Clang as the default compiler some users of ZFS
1183 on i386 systems started to experience stack overflow kernel panics.
1184 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1187 GEOM_LABEL now mangles label names read from file system metadata.
1188 Mangling affect labels containing spaces, non-printable characters,
1189 '%' or '"'. Device names in /etc/fstab and other places may need to
1193 By default, only the 10 most recent kernel dumps will be saved. To
1194 restore the previous behaviour (no limit on the number of kernel dumps
1195 stored in the dump directory) add the following line to /etc/rc.conf:
1200 With the addition of auditdistd(8), a new auditdistd user is now
1201 required during installworld. "mergemaster -p" can be used to
1202 add the user prior to installworld, as documented in the handbook.
1205 The sin6_scope_id member variable in struct sockaddr_in6 is now
1206 filled by the kernel before passing the structure to the userland via
1207 sysctl or routing socket. This means the KAME-specific embedded scope
1208 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1209 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1210 __FreeBSD_version is bumped to 1000025.
1213 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1214 This means that the world and kernel will be compiled with clang
1215 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1216 and /usr/bin/cpp. To disable this behavior and revert to building
1217 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1218 of current may need to bootstrap WITHOUT_CLANG first if the clang
1219 build fails (its compatibility window doesn't extend to the 9 stable
1223 The IPFIREWALL_FORWARD kernel option has been removed. Its
1224 functionality now turned on by default.
1227 The ZERO_COPY_SOCKET kernel option has been removed and
1228 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1229 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1230 mechanism which is not safe and may result in kernel crashes.
1231 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1232 driver supports disposeable external page sized mbuf storage.
1233 Proper replacements for both zero-copy mechanisms are under
1234 consideration and will eventually lead to complete removal
1235 of the two kernel options.
1238 The IPv4 network stack has been converted to network byte
1239 order. The following modules need to be recompiled together
1240 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1241 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1244 Support for non-MPSAFE filesystems was removed from VFS. The
1245 VFS_VERSION was bumped, all filesystem modules shall be
1249 All the non-MPSAFE filesystems have been disconnected from
1250 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1251 portalfs, smbfs, xfs.
1254 The interface cloning API and ABI has changed. The following
1255 modules need to be recompiled together with kernel:
1256 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1257 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1258 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1261 The sdhci driver was split in two parts: sdhci (generic SD Host
1262 Controller logic) and sdhci_pci (actual hardware driver).
1263 No kernel config modifications are required, but if you
1264 load sdhc as a module you must switch to sdhci_pci instead.
1267 Import the FUSE kernel and userland support into base system.
1270 The GNU sort(1) program has been removed since the BSD-licensed
1271 sort(1) has been the default for quite some time and no serious
1272 problems have been reported. The corresponding WITH_GNU_SORT
1276 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1277 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1281 The net80211(4) ABI has been changed to allow for improved driver
1282 PS-POLL and power-save support. All wireless drivers need to be
1283 recompiled to work with the new kernel.
1286 The random(4) support for the VIA hardware random number
1287 generator (`PADLOCK') is no longer enabled unconditionally.
1288 Add the padlock_rng device in the custom kernel config if
1289 needed. The GENERIC kernels on i386 and amd64 do include the
1290 device, so the change only affects the custom kernel
1294 The pf(4) packet filter ABI has been changed. pfctl(8) and
1295 snmp_pf module need to be recompiled to work with new kernel.
1298 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1299 to -HEAD. Pools that have empty_bpobj in active state can not be
1300 imported read-write with ZFS implementations that do not support
1301 this feature. For more information read the zpool-features(5)
1305 The sparc64 ZFS loader has been changed to no longer try to auto-
1306 detect ZFS providers based on diskN aliases but now requires these
1307 to be explicitly listed in the OFW boot-device environment variable.
1310 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1311 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1312 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1315 The following sysctls and tunables have been renamed for consistency
1316 with other variables:
1317 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1318 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1321 The sort utility has been replaced with BSD sort. For now, GNU sort
1322 is also available as "gnusort" or the default can be set back to
1323 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1324 installed as "bsdsort".
1327 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1328 Starting with this version the old system of ZFS pool versioning
1329 is superseded by "feature flags". This concept enables forward
1330 compatibility against certain future changes in functionality of ZFS
1331 pools. The first read-only compatible "feature flag" for ZFS pools
1332 is named "com.delphix:async_destroy". For more information
1333 read the new zpool-features(5) manual page.
1334 Please refer to the "ZFS notes" section of this file for information
1335 on upgrading boot ZFS pools.
1338 The malloc(3) implementation embedded in libc now uses sources imported
1339 as contrib/jemalloc. The most disruptive API change is to
1340 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1341 delete it prior to installworld, and optionally re-create it using the
1342 new format after rebooting. See malloc.conf(5) for details
1343 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1347 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1348 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1349 now spelled mips. This is to aid compatibility with third-party
1350 software that expects this naming scheme in uname(3). Little-endian
1351 settings are unchanged. If you are updating a big-endian mips64 machine
1352 from before this change, you may need to set MACHINE_ARCH=mips64 in
1353 your environment before the new build system will recognize your machine.
1356 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1360 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1361 nullfs(5) did not pass through all behaviours to the underlying layer,
1362 as a result if we bound to a socket on the lower layer we could connect
1363 only to the lower path; if we bound to the upper layer we could connect
1364 only to the upper path. The new behavior is one can connect to both the
1365 lower and the upper paths regardless what layer path one binds to.
1368 The getifaddrs upgrade path broken with 20111215 has been restored.
1369 If you have upgraded in between 20111215 and 20120209 you need to
1370 recompile libc again with your kernel. You still need to recompile
1371 world to be able to configure CARP but this restriction already
1372 comes from 20111215.
1375 The set_rcvar() function has been removed from /etc/rc.subr. All
1376 base and ports rc.d scripts have been updated, so if you have a
1377 port installed with a script in /usr/local/etc/rc.d you can either
1378 hand-edit the rcvar= line, or reinstall the port.
1380 An easy way to handle the mass-update of /etc/rc.d:
1381 rm /etc/rc.d/* && mergemaster -i
1384 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1385 on the current CPU and prevents other threads from running.
1386 This behavior can be reverted using the kern.stop_scheduler_on_panic
1388 The new behavior can be incompatible with kern.sync_on_panic.
1391 The carp(4) facility has been changed significantly. Configuration
1392 of the CARP protocol via ifconfig(8) has changed, as well as format
1393 of CARP events submitted to devd(8) has changed. See manual pages
1394 for more information. The arpbalance feature of carp(4) is currently
1395 not supported anymore.
1397 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1398 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1399 need to be recompiled.
1402 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1406 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1407 explicitely support non-MPSAFE filesystems.
1408 It is on by default for all supported platform at this present
1412 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1413 i386 and pc98 GENERIC kernel configuration files.
1416 sysinstall has been removed
1419 The stable/9 branch created in subversion. This corresponds to the
1420 RELENG_9 branch in CVS.
1426 Avoid using make -j when upgrading. While generally safe, there are
1427 sometimes problems using -j to upgrade. If your upgrade fails with
1428 -j, please try again without -j. From time to time in the past there
1429 have been problems using -j with buildworld and/or installworld. This
1430 is especially true when upgrading between "distant" versions (eg one
1431 that cross a major release boundary or several minor releases, or when
1432 several months have passed on the -current branch).
1434 Sometimes, obscure build problems are the result of environment
1435 poisoning. This can happen because the make utility reads its
1436 environment when searching for values for global variables. To run
1437 your build attempts in an "environmental clean room", prefix all make
1438 commands with 'env -i '. See the env(1) manual page for more details.
1440 When upgrading from one major version to another it is generally best
1441 to upgrade to the latest code in the currently installed branch first,
1442 then do an upgrade to the new branch. This is the best-tested upgrade
1443 path, and has the highest probability of being successful. Please try
1444 this approach before reporting problems with a major version upgrade.
1446 When upgrading a live system, having a root shell around before
1447 installing anything can help undo problems. Not having a root shell
1448 around can lead to problems if pam has changed too much from your
1449 starting point to allow continued authentication after the upgrade.
1451 This file should be read as a log of events. When a later event changes
1452 information of a prior event, the prior event should not be deleted.
1453 Instead, a pointer to the entry with the new information should be
1454 placed in the old entry. Readers of this file should also sanity check
1455 older entries before relying on them blindly. Authors of new entries
1456 should write them with this in mind.
1460 When upgrading the boot ZFS pool to a new version, always follow
1463 1.) recompile and reinstall the ZFS boot loader and boot block
1464 (this is part of "make buildworld" and "make installworld")
1466 2.) update the ZFS boot block on your boot drive
1468 The following example updates the ZFS boot block on the first
1469 partition (freebsd-boot) of a GPT partitioned drive ada0:
1470 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1472 Non-boot pools do not need these updates.
1476 If you are updating from a prior version of FreeBSD (even one just
1477 a few days old), you should follow this procedure. It is the most
1478 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1480 make kernel-toolchain
1481 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1482 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1484 To test a kernel once
1485 ---------------------
1486 If you just want to boot a kernel once (because you are not sure
1487 if it works, or if you want to boot a known bad kernel to provide
1488 debugging information) run
1489 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1490 nextboot -k testkernel
1492 To just build a kernel when you know that it won't mess you up
1493 --------------------------------------------------------------
1494 This assumes you are already running a CURRENT system. Replace
1495 ${arch} with the architecture of your machine (e.g. "i386",
1496 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1498 cd src/sys/${arch}/conf
1499 config KERNEL_NAME_HERE
1500 cd ../compile/KERNEL_NAME_HERE
1505 If this fails, go to the "To build a kernel" section.
1507 To rebuild everything and install it on the current system.
1508 -----------------------------------------------------------
1509 # Note: sometimes if you are running current you gotta do more than
1510 # is listed here if you are upgrading from a really old current.
1512 <make sure you have good level 0 dumps>
1514 make kernel KERNCONF=YOUR_KERNEL_HERE
1516 <reboot in single user> [3]
1523 To cross-install current onto a separate partition
1524 --------------------------------------------------
1525 # In this approach we use a separate partition to hold
1526 # current's root, 'usr', and 'var' directories. A partition
1527 # holding "/", "/usr" and "/var" should be about 2GB in
1530 <make sure you have good level 0 dumps>
1533 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1534 <maybe newfs current's root partition>
1535 <mount current's root partition on directory ${CURRENT_ROOT}>
1536 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1537 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1538 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1539 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1540 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1541 <reboot into current>
1542 <do a "native" rebuild/install as described in the previous section>
1543 <maybe install compatibility libraries from ports/misc/compat*>
1547 To upgrade in-place from stable to current
1548 ----------------------------------------------
1549 <make sure you have good level 0 dumps>
1551 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1553 <reboot in single user> [3]
1560 Make sure that you've read the UPDATING file to understand the
1561 tweaks to various things you need. At this point in the life
1562 cycle of current, things change often and you are on your own
1563 to cope. The defaults can also change, so please read ALL of
1564 the UPDATING entries.
1566 Also, if you are tracking -current, you must be subscribed to
1567 freebsd-current@freebsd.org. Make sure that before you update
1568 your sources that you have read and understood all the recent
1569 messages there. If in doubt, please track -stable which has
1570 much fewer pitfalls.
1572 [1] If you have third party modules, such as vmware, you
1573 should disable them at this point so they don't crash your
1576 [3] From the bootblocks, boot -s, and then do
1581 adjkerntz -i # if CMOS is wall time
1582 Also, when doing a major release upgrade, it is required that
1583 you boot into single user mode to do the installworld.
1585 [4] Note: This step is non-optional. Failure to do this step
1586 can result in a significant reduction in the functionality of the
1587 system. Attempting to do it by hand is not recommended and those
1588 that pursue this avenue should read this file carefully, as well
1589 as the archives of freebsd-current and freebsd-hackers mailing lists
1590 for potential gotchas. The -U option is also useful to consider.
1591 See mergemaster(8) for more information.
1593 [5] Usually this step is a noop. However, from time to time
1594 you may need to do this if you get unknown user in the following
1595 step. It never hurts to do it all the time. You may need to
1596 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1597 install) after the buildworld before this step if you last updated
1598 from current before 20130425 or from -stable before 20130430.
1600 [6] This only deletes old files and directories. Old libraries
1601 can be deleted by "make delete-old-libs", but you have to make
1602 sure that no program is using those libraries anymore.
1604 [8] In order to have a kernel that can run the 4.x binaries needed to
1605 do an installworld, you must include the COMPAT_FREEBSD4 option in
1606 your kernel. Failure to do so may leave you with a system that is
1607 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1608 required to run the 5.x binaries on more recent kernels. And so on
1609 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1611 Make sure that you merge any new devices from GENERIC since the
1612 last time you updated your kernel config file.
1614 [9] When checking out sources, you must include the -P flag to have
1615 cvs prune empty directories.
1617 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1618 "?=" instead of the "=" assignment operator, so that buildworld can
1619 override the CPUTYPE if it needs to.
1621 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1622 not on the command line, or in /etc/make.conf. buildworld will
1623 warn if it is improperly defined.
1626 This file contains a list, in reverse chronological order, of major
1627 breakages in tracking -current. It is not guaranteed to be a complete
1628 list of such breakages, and only contains entries since September 23, 2011.
1629 If you need to see UPDATING entries from before that date, you will need
1630 to fetch an UPDATING file from an older FreeBSD release.
1632 Copyright information:
1634 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1636 Redistribution, publication, translation and use, with or without
1637 modification, in full or in part, in any form or format of this
1638 document are permitted without further permission from the author.
1640 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1641 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1642 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1643 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1644 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1645 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1646 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1647 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1648 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1649 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1650 POSSIBILITY OF SUCH DAMAGE.
1652 Contact Warner Losh if you have any questions about your use of