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