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