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