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 Resource range types have grown from unsigned long to uintmax_t. All
36 drivers, and anything using libdevinfo, need to be recompiled.
39 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
40 builds. It no longer runs mkdep(1) during 'make depend', and the
41 'make depend' stage can safely be skipped now as it is auto ran
42 when building 'make all' and will generate all SRCS and DPSRCS before
43 building anything else. Dependencies are gathered at compile time with
44 -MF flags kept in separate .depend files per object file. Users should
45 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
49 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
50 kernel modules. Therefore, if you load any kernel modules at boot time,
51 please install the boot loaders after you install the kernel, but before
55 make kernel KERNCONF=YOUR_KERNEL_HERE
56 make -C sys/boot install
57 <reboot in single user>
59 Then follow the usual steps, described in the General Notes section,
63 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
64 see the 20141231 entry below for information about prerequisites and
65 upgrading, if you are not already using clang 3.5.0 or higher.
68 The AIO subsystem is now a standard part of the kernel. The
69 VFS_AIO kernel option and aio.ko kernel module have been removed.
70 Due to stability concerns, asynchronous I/O requests are only
71 permitted on sockets and raw disks by default. To enable
72 asynchronous I/O requests on all file types, set the
73 vfs.aio.enable_unsafe sysctl to a non-zero value.
76 The ELF object manipulation tool objcopy is now provided by the
77 ELF Tool Chain project rather than by GNU binutils. It should be a
78 drop-in replacement, with the addition of arm64 support. The
79 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
80 to obtain the GNU version if necessary.
83 Building ZFS pools on top of zvols is prohibited by default. That
84 feature has never worked safely; it's always been prone to deadlocks.
85 Using a zvol as the backing store for a VM guest's virtual disk will
86 still work, even if the guest is using ZFS. Legacy behavior can be
87 restored by setting vfs.zfs.vol.recursive=1.
90 The NONE and HPN patches has been removed from OpenSSH. They are
91 still available in the security/openssh-portable port.
94 With the addition of ypldap(8), a new _ypldap user is now required
95 during installworld. "mergemaster -p" can be used to add the user
96 prior to installworld, as documented in the handbook.
99 The tftp loader (pxeboot) now uses the option root-path directive. As a
100 consequence it no longer looks for a pxeboot.4th file on the tftp
101 server. Instead it uses the regular /boot infrastructure as with the
105 The code to start recording plug and play data into the modules has
106 been committed. While the old tools will properly build a new kernel,
107 a number of warnings about "unknown metadata record 4" will be produced
108 for an older kldxref. To avoid such warnings, make sure to rebuild
109 the kernel toolchain (or world). Make sure that you have r292078 or
110 later when trying to build 292077 or later before rebuilding.
113 Debug data files are now built by default with 'make buildworld' and
114 installed with 'make installworld'. This facilitates debugging but
115 requires more disk space both during the build and for the installed
116 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
120 r291527 changed the internal interface between the nfsd.ko and
121 nfscommon.ko modules. As such, they must both be upgraded to-gether.
122 __FreeBSD_version has been bumped because of this.
125 Add support for unicode collation strings leads to a change of
126 order of files listed by ls(1) for example. To get back to the old
127 behaviour, set LC_COLLATE environment variable to "C".
129 Databases administrators will need to reindex their databases given
130 collation results will be different.
132 Due to a bug in install(1) it is recommended to remove the ancient
133 locales before running make installworld.
135 rm -rf /usr/share/locale/*
138 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
139 libcrypto.so.7 or libssl.so.7 must be recompiled.
142 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
143 Kernel modules isp_2400_multi and isp_2500_multi were removed and
144 should be replaced with isp_2400 and isp_2500 modules respectively.
147 The build previously allowed using 'make -n' to not recurse into
148 sub-directories while showing what commands would be executed, and
149 'make -n -n' to recursively show commands. Now 'make -n' will recurse
150 and 'make -N' will not.
153 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
154 and etcupdate will now use this file. A custom sendmail.cf is now
155 updated via this mechanism rather than via installworld. If you had
156 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
157 want to remove the exclusion or change it to "always install".
158 /etc/mail/sendmail.cf is now managed the same way regardless of
159 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
160 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
163 Compatibility shims for legacy ATA device names have been removed.
164 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
165 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
166 environment variables, /dev/ad* and /dev/ar* symbolic links.
169 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
170 Please see the 20141231 entry below for information about prerequisites
171 and upgrading, if you are not already using clang 3.5.0 or higher.
174 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
175 and renamed from .symbols to .debug. This reduces the size requirements
176 on the boot partition or file system and provides consistency with
177 userland debug files.
179 When using the supported kernel installation method the
180 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
181 as is done with /boot/kernel.
183 Developers wishing to maintain the historical behavior of installing
184 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
187 The wireless drivers had undergone changes that remove the 'parent
188 interface' from the ifconfig -l output. The rc.d network scripts
189 used to check presence of a parent interface in the list, so old
190 scripts would fail to start wireless networking. Thus, etcupdate(3)
191 or mergemaster(8) run is required after kernel update, to update your
192 rc.d scripts in /etc.
195 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
196 These configurations are now automatically interpreted as
197 'scrub fragment reassemble'.
200 Kernel-loadable modules for the random(4) device are back. To use
201 them, the kernel must have
204 options RANDOM_LOADABLE
206 kldload(8) can then be used to load random_fortuna.ko
207 or random_yarrow.ko. Please note that due to the indirect
208 function calls that the loadable modules need to provide,
209 the build-in variants will be slightly more efficient.
211 The random(4) kernel option RANDOM_DUMMY has been retired due to
212 unpopularity. It was not all that useful anyway.
215 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
216 Control over building the ELF Tool Chain tools is now provided by
217 the WITHOUT_TOOLCHAIN knob.
220 The polarity of Pulse Per Second (PPS) capture events with the
221 uart(4) driver has been corrected. Prior to this change the PPS
222 "assert" event corresponded to the trailing edge of a positive PPS
223 pulse and the "clear" event was the leading edge of the next pulse.
225 As the width of a PPS pulse in a typical GPS receiver is on the
226 order of 1 millisecond, most users will not notice any significant
227 difference with this change.
229 Anyone who has compensated for the historical polarity reversal by
230 configuring a negative offset equal to the pulse width will need to
231 remove that workaround.
234 The default group assigned to /dev/dri entries has been changed
235 from 'wheel' to 'video' with the id of '44'. If you want to have
236 access to the dri devices please add yourself to the video group
239 # pw groupmod video -m $USER
242 The menu.rc and loader.rc files will now be replaced during
243 upgrades. Please migrate local changes to menu.rc.local and
244 loader.rc.local instead.
247 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
248 strings and strip have been removed. The src.conf(5) knob
249 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
252 As ZFS requires more kernel stack pages than is the default on some
253 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
254 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
256 Please consider using 'options KSTACK_PAGES=X' where X is greater
257 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
260 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
261 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
262 default, i.e., they will not contain "::". For example, instead
263 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
264 to have a more specific match, such as different map entries for
265 IPv6:0:0 vs IPv6:0. This change requires that configuration
266 data (including maps, files, classes, custom ruleset, etc.) must
267 use the same format, so make certain such configuration data is
268 upgrading. As a very simple check search for patterns like
269 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
270 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
271 the cf option UseCompressedIPv6Addresses.
274 The default kernel entropy-processing algorithm is now
275 Fortuna, replacing Yarrow.
277 Assuming you have 'device random' in your kernel config
278 file, the configurations allow a kernel option to override
279 this default. You may choose *ONE* of:
281 options RANDOM_YARROW # Legacy /dev/random algorithm.
282 options RANDOM_DUMMY # Blocking-only driver.
284 If you have neither, you get Fortuna. For most people,
285 read no further, Fortuna will give a /dev/random that works
286 like it always used to, and the difference will be irrelevant.
288 If you remove 'device random', you get *NO* kernel-processed
289 entropy at all. This may be acceptable to folks building
290 embedded systems, but has complications. Carry on reading,
291 and it is assumed you know what you need.
293 *PLEASE* read random(4) and random(9) if you are in the
294 habit of tweaking kernel configs, and/or if you are a member
295 of the embedded community, wanting specific and not-usual
296 behaviour from your security subsystems.
298 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
299 random', you will NOT have a functioning /dev/random, and
300 many cryptographic features will not work, including SSH.
301 You may also find strange behaviour from the random(3) set
302 of library functions, in particular sranddev(3), srandomdev(3)
303 and arc4random(3). The reason for this is that the KERN_ARND
304 sysctl only returns entropy if it thinks it has some to
305 share, and with RANDOM_DUMMY or no 'device random' this
309 An additional fix for the issue described in the 20150614 sendmail
310 entry below has been been committed in revision 284717.
313 FreeBSD's old make (fmake) has been removed from the system. It is
314 available as the devel/fmake port or via pkg install fmake.
317 The fix for the issue described in the 20150614 sendmail entry
318 below has been been committed in revision 284436. The work
319 around described in that entry is no longer needed unless the
320 default setting is overridden by a confDH_PARAMETERS configuration
321 setting of '5' or pointing to a 512 bit DH parameter file.
324 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
325 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
326 and devel/kyua to version 0.20+ and adjust any calling code to work
327 with Kyuafile and kyua.
330 The import of openssl to address the FreeBSD-SA-15:10.openssl
331 security advisory includes a change which rejects handshakes
332 with DH parameters below 768 bits. sendmail releases prior
333 to 8.15.2 (not yet released), defaulted to a 512 bit
334 DH parameter setting for client connections. To work around
335 this interoperability, sendmail can be configured to use a
336 2048 bit DH parameter by:
338 1. Edit /etc/mail/`hostname`.mc
339 2. If a setting for confDH_PARAMETERS does not exist or
340 exists and is set to a string beginning with '5',
342 3. If a setting for confDH_PARAMETERS exists and is set to
343 a file path, create a new file with:
344 openssl dhparam -out /path/to/file 2048
345 4. Rebuild the .cf file:
346 cd /etc/mail/; make; make install
348 cd /etc/mail/; make restart
350 A sendmail patch is coming, at which time this file will be
354 Generation of legacy formatted entries have been disabled by default
355 in pwd_mkdb(8), as all base system consumers of the legacy formatted
356 entries were converted to use the new format by default when the new,
357 machine independent format have been added and supported since FreeBSD
360 Please see the pwd_mkdb(8) manual page for further details.
363 Clang and llvm have been upgraded to 3.6.1 release. Please see the
364 20141231 entry below for information about prerequisites and upgrading,
365 if you are not already using 3.5.0 or higher.
368 TI platform code switched to using vendor DTS files and this update
369 may break existing systems running on Beaglebone, Beaglebone Black,
372 - dtb files should be regenerated/reinstalled. Filenames are the
373 same but content is different now
374 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
375 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
376 addressing scheme is now pin 25 on /dev/gpioc3.
377 - Pandaboard: /etc/ttys should be updated, serial console device is
378 now /dev/ttyu2, not /dev/ttyu0
381 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
382 If you need the GNU extension from groff soelim(1), install groff
383 from package: pkg install groff, or via ports: textproc/groff.
386 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
387 defined in symlink(7); previously symlinks were silently ignored.
390 The const qualifier has been removed from iconv(3) to comply with
391 POSIX. The ports tree is aware of this from r384038 onwards.
394 Libraries specified by LIBADD in Makefiles must have a corresponding
395 DPADD_<lib> variable to ensure correct dependencies. This is now
396 enforced in src.libnames.mk.
399 From legacy ata(4) driver was removed support for SATA controllers
400 supported by more functional drivers ahci(4), siis(4) and mvs(4).
401 Kernel modules ataahci and ataadaptec were removed completely,
402 replaced by ahci and mvs modules respectively.
405 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
406 the 20141231 entry below for information about prerequisites and
407 upgrading, if you are not already using 3.5.0 or higher.
410 The 32-bit PowerPC kernel has been changed to a position-independent
411 executable. This can only be booted with a version of loader(8)
412 newer than January 31, 2015, so make sure to update both world and
413 kernel before rebooting.
416 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
417 but before r278950, the RNG was not seeded properly. Immediately
418 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
419 ssh keys or openssl keys) that were generated w/ a kernel from that
420 range. This does not affect programs that directly used /dev/random
421 or /dev/urandom. All userland uses of arc4random(3) are affected.
424 The autofs(4) ABI was changed in order to restore binary compatibility
425 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
429 The powerpc64 kernel has been changed to a position-independent
430 executable. This can only be booted with a new version of loader(8),
431 so make sure to update both world and kernel before rebooting.
434 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
435 only release, no new features have been added. Please see the 20141231
436 entry below for information about prerequisites and upgrading, if you
437 are not already using 3.5.0.
440 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
441 taken from the ELF Tool Chain project rather than GNU binutils. They
442 should be drop-in replacements, with the addition of arm64 support.
443 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
444 binutils tools, if necessary. See 20150805 for updated information.
447 The default Unbound configuration now enables remote control
448 using a local socket. Users who have already enabled the
449 local_unbound service should regenerate their configuration
450 by running "service local_unbound setup" as root.
453 The GNU texinfo and GNU info pages have been removed.
454 To be able to view GNU info pages please install texinfo from ports.
457 Clang, llvm and lldb have been upgraded to 3.5.0 release.
459 As of this release, a prerequisite for building clang, llvm and lldb is
460 a C++11 capable compiler and C++11 standard library. This means that to
461 be able to successfully build the cross-tools stage of buildworld, with
462 clang as the bootstrap compiler, your system compiler or cross compiler
463 should either be clang 3.3 or later, or gcc 4.8 or later, and your
464 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
467 On any standard FreeBSD 10.x or 11.x installation, where clang and
468 libc++ are on by default (that is, on x86 or arm), this should work out
471 On 9.x installations where clang is enabled by default, e.g. on x86 and
472 powerpc, libc++ will not be enabled by default, so libc++ should be
473 built (with clang) and installed first. If both clang and libc++ are
474 missing, build clang first, then use it to build libc++.
476 On 8.x and earlier installations, upgrade to 9.x first, and then follow
477 the instructions for 9.x above.
479 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
480 default, and do not build clang.
482 Many embedded systems are resource constrained, and will not be able to
483 build clang in a reasonable time, or in some cases at all. In those
484 cases, cross building bootable systems on amd64 is a workaround.
486 This new version of clang introduces a number of new warnings, of which
487 the following are most likely to appear:
491 This warns in two cases, for both C and C++:
492 * When the code is trying to take the absolute value of an unsigned
493 quantity, which is effectively a no-op, and almost never what was
494 intended. The code should be fixed, if at all possible. If you are
495 sure that the unsigned quantity can be safely cast to signed, without
496 loss of information or undefined behavior, you can add an explicit
497 cast, or disable the warning.
499 * When the code is trying to take an absolute value, but the called
500 abs() variant is for the wrong type, which can lead to truncation.
501 If you want to disable the warning instead of fixing the code, please
502 make sure that truncation will not occur, or it might lead to unwanted
505 -Wtautological-undefined-compare and
506 -Wundefined-bool-conversion
508 These warn when C++ code is trying to compare 'this' against NULL, while
509 'this' should never be NULL in well-defined C++ code. However, there is
510 some legacy (pre C++11) code out there, which actively abuses this
511 feature, which was less strictly defined in previous C++ versions.
513 Squid and openjdk do this, for example. The warning can be turned off
514 for C++98 and earlier, but compiling the code in C++11 mode might result
515 in unexpected behavior; for example, the parts of the program that are
516 unreachable could be optimized away.
519 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
520 kernel sources have been removed. The .h files remain, since some
521 utilities include them. This will need to be fixed later.
522 If "mount -t oldnfs ..." is attempted, it will fail.
523 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
524 the utilities will report errors.
527 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
528 directories to top level SUBDIR variable when their parent
529 directory is included in LOCAL_DIRS. Users with build systems with
530 such hierarchies and without SUBDIR entries in the parent
531 directory Makefiles should add them or add the directories to
535 faith(4) and faithd(8) have been removed from the base system. Faith
536 has been obsolete for a very long time.
539 vt(4), the new console driver, is enabled by default. It brings
540 support for Unicode and double-width characters, as well as
541 support for UEFI and integration with the KMS kernel video
544 You may need to update your console settings in /etc/rc.conf,
545 most probably the keymap. During boot, /etc/rc.d/syscons will
546 indicate what you need to do.
548 vt(4) still has issues and lacks some features compared to
549 syscons(4). See the wiki for up-to-date information:
550 https://wiki.freebsd.org/Newcons
552 If you want to keep using syscons(4), you can do so by adding
553 the following line to /boot/loader.conf:
557 pjdfstest has been integrated into kyua as an opt-in test suite.
558 Please see share/doc/pjdfstest/README for more details on how to
562 gperf has been removed from the base system for architectures
563 that use clang. Ports that require gperf will obtain it from the
567 pjdfstest has been moved from tools/regression/pjdfstest to
571 At svn r271982, The default linux compat kernel ABI has been adjusted
572 to 2.6.18 in support of the linux-c6 compat ports infrastructure
573 update. If you wish to continue using the linux-f10 compat ports,
574 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
575 encouraged to update their linux-compat packages to linux-c6 during
576 their next update cycle.
579 The ofwfb driver, used to provide a graphics console on PowerPC when
580 using vt(4), no longer allows mmap() of all physical memory. This
581 will prevent Xorg on PowerPC with some ATI graphics cards from
582 initializing properly unless x11-servers/xorg-server is updated to
586 The xdev targets have been converted to using TARGET and
587 TARGET_ARCH instead of XDEV and XDEV_ARCH.
590 The default unbound configuration has been modified to address
591 issues with reverse lookups on networks that use private
592 address ranges. If you use the local_unbound service, run
593 "service local_unbound setup" as root to regenerate your
594 configuration, then "service local_unbound reload" to load the
598 The GNU texinfo and GNU info pages are not built and installed
599 anymore, WITH_INFO knob has been added to allow to built and install
601 UPDATE: see 20150102 entry on texinfo's removal
604 The GNU readline library is now an INTERNALLIB - that is, it is
605 statically linked into consumers (GDB and variants) in the base
606 system, and the shared library is no longer installed. The
607 devel/readline port is available for third party software that
611 The Itanium architecture (ia64) has been removed from the list of
612 known architectures. This is the first step in the removal of the
616 Commit r268115 has added NFSv4.1 server support, merged from
617 projects/nfsv4.1-server. Since this includes changes to the
618 internal interfaces between the NFS related modules, a full
619 build of the kernel and modules will be necessary.
620 __FreeBSD_version has been bumped.
623 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
624 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
625 which differs from the behaviour controlled by this knob.)
628 Maximal length of the serial number in CTL was increased from 16 to
629 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
630 and ctld, need to be rebuilt to work with a new kernel.
633 The libatf-c and libatf-c++ major versions were downgraded to 0 and
634 1 respectively to match the upstream numbers. They were out of
635 sync because, when they were originally added to FreeBSD, the
636 upstream versions were not respected. These libraries are private
637 and not yet built by default, so renumbering them should be a
638 non-issue. However, unclean source trees will yield broken test
639 programs once the operator executes "make delete-old-libs" after a
642 Additionally, the atf-sh binary was made private by moving it into
643 /usr/libexec/. Already-built shell test programs will keep the
644 path to the old binary so they will break after "make delete-old"
647 If you are using WITH_TESTS=yes (not the default), wipe the object
648 tree and rebuild from scratch to prevent spurious test failures.
649 This is only needed once: the misnumbered libraries and misplaced
650 binaries have been added to OptionalObsoleteFiles.inc so they will
651 be removed during a clean upgrade.
654 Clang and llvm have been upgraded to 3.4.1 release.
657 We bogusly installed src.opts.mk in /usr/share/mk. This file should
658 be removed to avoid issues in the future (and has been added to
662 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
663 past, it affected all builds that used the bsd.*.mk files. The old
664 behavior was a bug, but people may have relied upon it. To get this
665 behavior back, you can .include /etc/src.conf from /etc/make.conf
666 (which is still global and isn't changed). This also changes the
667 behavior of incremental builds inside the tree of individual
668 directories. Set MAKESYSPATH to ".../share/mk" to do that.
669 Although this has survived make universe and some upgrade scenarios,
670 other upgrade scenarios may have broken. At least one form of
671 temporary breakage was fixed with MAKESYSPATH settings for buildworld
672 as well... In cases where MAKESYSPATH isn't working with this
673 setting, you'll need to set it to the full path to your tree.
675 One side effect of all this cleaning up is that bsd.compiler.mk
676 is no longer implicitly included by bsd.own.mk. If you wish to
677 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
681 The lindev device has been removed since /dev/full has been made a
682 standard device. __FreeBSD_version has been bumped.
685 The knob WITHOUT_VI was added to the base system, which controls
686 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
687 in order to reorder files share/termcap and didn't build ex(1) as a
688 build tool, so building/installing with WITH_VI is highly advised for
689 build hosts for older releases.
691 This issue has been fixed in stable/9 and stable/10 in r277022 and
692 r276991, respectively.
695 The YES_HESIOD knob has been removed. It has been obsolete for
696 a decade. Please move to using WITH_HESIOD instead or your builds
697 will silently lack HESIOD.
700 The uart(4) driver has been changed with respect to its handling
701 of the low-level console. Previously the uart(4) driver prevented
702 any process from changing the baudrate or the CLOCAL and HUPCL
703 control flags. By removing the restrictions, operators can make
704 changes to the serial console port without having to reboot.
705 However, when getty(8) is started on the serial device that is
706 associated with the low-level console, a misconfigured terminal
707 line in /etc/ttys will now have a real impact.
708 Before upgrading the kernel, make sure that /etc/ttys has the
709 serial console device configured as 3wire without baudrate to
710 preserve the previous behaviour. E.g:
711 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
714 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
715 to improve performance. To re-enable it, if needed, run rpcbind
716 with command line option -W.
719 Switched back to the GPL dtc compiler due to updates in the upstream
720 dts files not being supported by the BSDL dtc compiler. You will need
721 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
722 may result while building dtb files during a kernel build if you fail
723 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
726 Clang and llvm have been upgraded to 3.4 release.
729 The nve(4) driver has been removed. Please use the nfe(4) driver
730 for NVIDIA nForce MCP Ethernet adapters instead.
733 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
734 This could cause certain C++ applications using shared libraries built
735 against the previous version of libc++ to crash. The incompatibility
736 has now been fixed, but any C++ applications or shared libraries built
737 between r261283 and r261801 should be recompiled.
740 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
741 capability mode support. Please note that enabling the feature in
742 kernel is still highly recommended.
745 OpenSSH is now built with sandbox support, and will use sandbox as
746 the default privilege separation method. This requires Capsicum
747 capability mode support in kernel.
750 The libelf and libdwarf libraries have been updated to newer
751 versions from upstream. Shared library version numbers for
752 these two libraries were bumped. Any ports or binaries
753 requiring these two libraries should be recompiled.
754 __FreeBSD_version is bumped to 1100006.
757 If a Makefile in a tests/ directory was auto-generating a Kyuafile
758 instead of providing an explicit one, this would prevent such
759 Makefile from providing its own Kyuafile in the future during
760 NO_CLEAN builds. This has been fixed in the Makefiles but manual
761 intervention is needed to clean an objdir if you use NO_CLEAN:
762 # find /usr/obj -name Kyuafile | xargs rm -f
765 The behavior of gss_pseudo_random() for the krb5 mechanism
766 has changed, for applications requesting a longer random string
767 than produced by the underlying enctype's pseudo-random() function.
768 In particular, the random string produced from a session key of
769 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
770 be different at the 17th octet and later, after this change.
771 The counter used in the PRF+ construction is now encoded as a
772 big-endian integer in accordance with RFC 4402.
773 __FreeBSD_version is bumped to 1100004.
776 The WITHOUT_ATF build knob has been removed and its functionality
777 has been subsumed into the more generic WITHOUT_TESTS. If you were
778 using the former to disable the build of the ATF libraries, you
779 should change your settings to use the latter.
782 The default version of mtree is nmtree which is obtained from
783 NetBSD. The output is generally the same, but may vary
784 slightly. If you found you need identical output adding
785 "-F freebsd9" to the command line should do the trick. For the
786 time being, the old mtree is available as fmtree.
789 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
790 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
791 1.1.4_8 and verify bsdyml not linked in, before running "make
793 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
795 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
798 The stable/10 branch has been created in subversion from head
802 The rc.d/jail script has been updated to support jail(8)
803 configuration file. The "jail_<jname>_*" rc.conf(5) variables
804 for per-jail configuration are automatically converted to
805 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
806 This is transparently backward compatible. See below about some
807 incompatibilities and rc.conf(5) manual page for more details.
809 These variables are now deprecated in favor of jail(8) configuration
810 file. One can use "rc.d/jail config <jname>" command to generate
811 a jail(8) configuration file in /var/run/jail.<jname>.conf without
812 running the jail(8) utility. The default pathname of the
813 configuration file is /etc/jail.conf and can be specified by
814 using $jail_conf or $jail_<jname>_conf variables.
816 Please note that jail_devfs_ruleset accepts an integer at
817 this moment. Please consider to rewrite the ruleset name
821 BIND has been removed from the base system. If all you need
822 is a local resolver, simply enable and start the local_unbound
823 service instead. Otherwise, several versions of BIND are
824 available in the ports tree. The dns/bind99 port is one example.
826 With this change, nslookup(1) and dig(1) are no longer in the base
827 system. Users should instead use host(1) and drill(1) which are
828 in the base system. Alternatively, nslookup and dig can
829 be obtained by installing the dns/bind-tools port.
832 With the addition of unbound(8), a new unbound user is now
833 required during installworld. "mergemaster -p" can be used to
834 add the user prior to installworld, as documented in the handbook.
837 OpenSSH is now built with DNSSEC support, and will by default
838 silently trust signed SSHFP records. This can be controlled with
839 the VerifyHostKeyDNS client configuration setting. DNSSEC support
840 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
843 The GNU Compiler Collection and C++ standard library (libstdc++)
844 are no longer built by default on platforms where clang is the system
845 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
849 The PROCDESC kernel option is now part of the GENERIC kernel
850 configuration and is required for the rwhod(8) to work.
851 If you are using custom kernel configuration, you should include
855 The API and ABI related to the Capsicum framework was modified
856 in backward incompatible way. The userland libraries and programs
857 have to be recompiled to work with the new kernel. This includes the
858 following libraries and programs, but the whole buildworld is
859 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
860 kdump, procstat, rwho, rwhod, uniq.
863 AES-NI intrinsic support has been added to gcc. The AES-NI module
864 has been updated to use this support. A new gcc is required to build
865 the aesni module on both i386 and amd64.
868 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
869 Thus "device padlock_rng" and "device rdrand_rng" should be
870 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
873 WITH_ICONV has been split into two feature sets. WITH_ICONV now
874 enables just the iconv* functionality and is now on by default.
875 WITH_LIBICONV_COMPAT enables the libiconv api and link time
876 compatability. Set WITHOUT_ICONV to build the old way.
877 If you have been using WITH_ICONV before, you will very likely
878 need to turn on WITH_LIBICONV_COMPAT.
881 INVARIANTS option now enables DEBUG for code with OpenSolaris and
882 Illumos origin, including ZFS. If you have INVARIANTS in your
883 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
885 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
886 locks if WITNESS option was set. Because that generated a lot of
887 witness(9) reports and all of them were believed to be false
888 positives, this is no longer done. New option OPENSOLARIS_WITNESS
889 can be used to achieve the previous behavior.
892 Timer values in IPv6 data structures now use time_uptime instead
893 of time_second. Although this is not a user-visible functional
894 change, userland utilities which directly use them---ndp(8),
895 rtadvd(8), and rtsold(8) in the base system---need to be updated
899 find -delete can now delete the pathnames given as arguments,
900 instead of only files found below them or if the pathname did
901 not contain any slashes. Formerly, the following error message
904 find: -delete: <path>: relative path potentially not safe
906 Deleting the pathnames given as arguments can be prevented
907 without error messages using -mindepth 1 or by changing
908 directory and passing "." as argument to find. This works in the
909 old as well as the new version of find.
912 Behavior of devfs rules path matching has been changed.
913 Pattern is now always matched against fully qualified devfs
914 path and slash characters must be explicitly matched by
915 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
916 subdirectories must be reviewed.
919 The default ARM ABI has changed to the ARM EABI. The old ABI is
920 incompatible with the ARM EABI and all programs and modules will
921 need to be rebuilt to work with a new kernel.
923 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
925 NOTE: Support for the old ABI will be removed in the future and
926 users are advised to upgrade.
929 pkg_install has been disconnected from the build if you really need it
930 you should add WITH_PKGTOOLS in your src.conf(5).
933 Most of network statistics structures were changed to be able
934 keep 64-bits counters. Thus all tools, that work with networking
935 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
938 Fix a bug that allowed a tracing process (e.g. gdb) to write
939 to a memory-mapped file in the traced process's address space
940 even if neither the traced process nor the tracing process had
941 write access to that file.
944 CVS has been removed from the base system. An exact copy
945 of the code is available from the devel/cvs port.
948 Some people report the following error after the switch to bmake:
950 make: illegal option -- J
951 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
953 *** [buildworld] Error code 2
955 this likely due to an old instance of make in
956 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
957 which src/Makefile will use that blindly, if it exists, so if
958 you see the above error:
960 rm -rf `make -V MAKEPATH`
965 Use bmake by default.
966 Whereas before one could choose to build with bmake via
967 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
968 make. The goal is to remove these knobs for 10-RELEASE.
970 It is worth noting that bmake (like gmake) treats the command
971 line as the unit of failure, rather than statements within the
972 command line. Thus '(cd some/where && dosomething)' is safer
973 than 'cd some/where; dosomething'. The '()' allows consistent
974 behavior in parallel build.
977 Fix a bug that allows NFS clients to issue READDIR on files.
980 The WITHOUT_IDEA option has been removed because
981 the IDEA patent expired.
984 The sysctl which controls TRIM support under ZFS has been renamed
985 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
989 The mergemaster command now uses the default MAKEOBJDIRPREFIX
990 rather than creating it's own in the temporary directory in
991 order allow access to bootstrapped versions of tools such as
992 install and mtree. When upgrading from version of FreeBSD where
993 the install command does not support -l, you will need to
994 install a new mergemaster command if mergemaster -p is required.
995 This can be accomplished with the command (cd src/usr.sbin/mergemaster
999 Legacy ATA stack, disabled and replaced by new CAM-based one since
1000 FreeBSD 9.0, completely removed from the sources. Kernel modules
1001 atadisk and atapi*, user-level tools atacontrol and burncd are
1002 removed. Kernel option `options ATA_CAM` is now permanently enabled
1006 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1007 and socketpair(2). Software, in particular Kerberos, may
1008 automatically detect and use these during building. The resulting
1009 binaries will not work on older kernels.
1012 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1013 information, see the respective 20130304 entry).
1016 Recent commits to callout(9) changed the size of struct callout,
1017 so the KBI is probably heavily disturbed. Also, some functions
1018 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1019 by macros. Every kernel module using it won't load, so rebuild
1022 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1023 but does not initialize by default (because of the new CTL_DISABLE
1024 option) to save memory. To re-enable it, remove the CTL_DISABLE
1025 option from the kernel config file or set kern.cam.ctl.disable=0
1026 in /boot/loader.conf.
1029 The ctl device has been disabled in GENERIC for i386 and amd64.
1030 This was done due to the extra memory being allocated at system
1031 initialisation time by the ctl driver which was only used if
1032 a CAM target device was created. This makes a FreeBSD system
1033 unusable on 128MB or less of RAM.
1036 A new compression method (lz4) has been merged to -HEAD. Please
1037 refer to zpool-features(7) for more information.
1039 Please refer to the "ZFS notes" section of this file for information
1040 on upgrading boot ZFS pools.
1043 A BSD-licensed patch(1) variant has been added and is installed
1044 as bsdpatch, being the GNU version the default patch.
1045 To inverse the logic and use the BSD-licensed one as default,
1046 while having the GNU version installed as gnupatch, rebuild
1047 and install world with the WITH_BSD_PATCH knob set.
1050 Due to the use of the new -l option to install(1) during build
1051 and install, you must take care not to directly set the INSTALL
1052 make variable in your /etc/make.conf, /etc/src.conf, or on the
1053 command line. If you wish to use the -C flag for all installs
1054 you may be able to add INSTALL+=-C to /etc/make.conf or
1058 The install(1) option -M has changed meaning and now takes an
1059 argument that is a file or path to append logs to. In the
1060 unlikely event that -M was the last option on the command line
1061 and the command line contained at least two files and a target
1062 directory the first file will have logs appended to it. The -M
1063 option served little practical purpose in the last decade so its
1064 use is expected to be extremely rare.
1067 After switching to Clang as the default compiler some users of ZFS
1068 on i386 systems started to experience stack overflow kernel panics.
1069 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1072 GEOM_LABEL now mangles label names read from file system metadata.
1073 Mangling affect labels containing spaces, non-printable characters,
1074 '%' or '"'. Device names in /etc/fstab and other places may need to
1078 By default, only the 10 most recent kernel dumps will be saved. To
1079 restore the previous behaviour (no limit on the number of kernel dumps
1080 stored in the dump directory) add the following line to /etc/rc.conf:
1085 With the addition of auditdistd(8), a new auditdistd user is now
1086 required during installworld. "mergemaster -p" can be used to
1087 add the user prior to installworld, as documented in the handbook.
1090 The sin6_scope_id member variable in struct sockaddr_in6 is now
1091 filled by the kernel before passing the structure to the userland via
1092 sysctl or routing socket. This means the KAME-specific embedded scope
1093 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1094 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1095 __FreeBSD_version is bumped to 1000025.
1098 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1099 This means that the world and kernel will be compiled with clang
1100 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1101 and /usr/bin/cpp. To disable this behavior and revert to building
1102 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1103 of current may need to bootstrap WITHOUT_CLANG first if the clang
1104 build fails (its compatibility window doesn't extend to the 9 stable
1108 The IPFIREWALL_FORWARD kernel option has been removed. Its
1109 functionality now turned on by default.
1112 The ZERO_COPY_SOCKET kernel option has been removed and
1113 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1114 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1115 mechanism which is not safe and may result in kernel crashes.
1116 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1117 driver supports disposeable external page sized mbuf storage.
1118 Proper replacements for both zero-copy mechanisms are under
1119 consideration and will eventually lead to complete removal
1120 of the two kernel options.
1123 The IPv4 network stack has been converted to network byte
1124 order. The following modules need to be recompiled together
1125 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1126 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1129 Support for non-MPSAFE filesystems was removed from VFS. The
1130 VFS_VERSION was bumped, all filesystem modules shall be
1134 All the non-MPSAFE filesystems have been disconnected from
1135 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1136 portalfs, smbfs, xfs.
1139 The interface cloning API and ABI has changed. The following
1140 modules need to be recompiled together with kernel:
1141 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1142 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1143 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1146 The sdhci driver was split in two parts: sdhci (generic SD Host
1147 Controller logic) and sdhci_pci (actual hardware driver).
1148 No kernel config modifications are required, but if you
1149 load sdhc as a module you must switch to sdhci_pci instead.
1152 Import the FUSE kernel and userland support into base system.
1155 The GNU sort(1) program has been removed since the BSD-licensed
1156 sort(1) has been the default for quite some time and no serious
1157 problems have been reported. The corresponding WITH_GNU_SORT
1161 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1162 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1166 The net80211(4) ABI has been changed to allow for improved driver
1167 PS-POLL and power-save support. All wireless drivers need to be
1168 recompiled to work with the new kernel.
1171 The random(4) support for the VIA hardware random number
1172 generator (`PADLOCK') is no longer enabled unconditionally.
1173 Add the padlock_rng device in the custom kernel config if
1174 needed. The GENERIC kernels on i386 and amd64 do include the
1175 device, so the change only affects the custom kernel
1179 The pf(4) packet filter ABI has been changed. pfctl(8) and
1180 snmp_pf module need to be recompiled to work with new kernel.
1183 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1184 to -HEAD. Pools that have empty_bpobj in active state can not be
1185 imported read-write with ZFS implementations that do not support
1186 this feature. For more information read the zpool-features(5)
1190 The sparc64 ZFS loader has been changed to no longer try to auto-
1191 detect ZFS providers based on diskN aliases but now requires these
1192 to be explicitly listed in the OFW boot-device environment variable.
1195 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1196 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1197 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1200 The following sysctls and tunables have been renamed for consistency
1201 with other variables:
1202 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1203 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1206 The sort utility has been replaced with BSD sort. For now, GNU sort
1207 is also available as "gnusort" or the default can be set back to
1208 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1209 installed as "bsdsort".
1212 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1213 Starting with this version the old system of ZFS pool versioning
1214 is superseded by "feature flags". This concept enables forward
1215 compatibility against certain future changes in functionality of ZFS
1216 pools. The first read-only compatible "feature flag" for ZFS pools
1217 is named "com.delphix:async_destroy". For more information
1218 read the new zpool-features(5) manual page.
1219 Please refer to the "ZFS notes" section of this file for information
1220 on upgrading boot ZFS pools.
1223 The malloc(3) implementation embedded in libc now uses sources imported
1224 as contrib/jemalloc. The most disruptive API change is to
1225 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1226 delete it prior to installworld, and optionally re-create it using the
1227 new format after rebooting. See malloc.conf(5) for details
1228 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1232 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1233 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1234 now spelled mips. This is to aid compatibility with third-party
1235 software that expects this naming scheme in uname(3). Little-endian
1236 settings are unchanged. If you are updating a big-endian mips64 machine
1237 from before this change, you may need to set MACHINE_ARCH=mips64 in
1238 your environment before the new build system will recognize your machine.
1241 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1245 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1246 nullfs(5) did not pass through all behaviours to the underlying layer,
1247 as a result if we bound to a socket on the lower layer we could connect
1248 only to the lower path; if we bound to the upper layer we could connect
1249 only to the upper path. The new behavior is one can connect to both the
1250 lower and the upper paths regardless what layer path one binds to.
1253 The getifaddrs upgrade path broken with 20111215 has been restored.
1254 If you have upgraded in between 20111215 and 20120209 you need to
1255 recompile libc again with your kernel. You still need to recompile
1256 world to be able to configure CARP but this restriction already
1257 comes from 20111215.
1260 The set_rcvar() function has been removed from /etc/rc.subr. All
1261 base and ports rc.d scripts have been updated, so if you have a
1262 port installed with a script in /usr/local/etc/rc.d you can either
1263 hand-edit the rcvar= line, or reinstall the port.
1265 An easy way to handle the mass-update of /etc/rc.d:
1266 rm /etc/rc.d/* && mergemaster -i
1269 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1270 on the current CPU and prevents other threads from running.
1271 This behavior can be reverted using the kern.stop_scheduler_on_panic
1273 The new behavior can be incompatible with kern.sync_on_panic.
1276 The carp(4) facility has been changed significantly. Configuration
1277 of the CARP protocol via ifconfig(8) has changed, as well as format
1278 of CARP events submitted to devd(8) has changed. See manual pages
1279 for more information. The arpbalance feature of carp(4) is currently
1280 not supported anymore.
1282 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1283 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1284 need to be recompiled.
1287 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1291 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1292 explicitely support non-MPSAFE filesystems.
1293 It is on by default for all supported platform at this present
1297 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1298 i386 and pc98 GENERIC kernel configuration files.
1301 sysinstall has been removed
1304 The stable/9 branch created in subversion. This corresponds to the
1305 RELENG_9 branch in CVS.
1311 Avoid using make -j when upgrading. While generally safe, there are
1312 sometimes problems using -j to upgrade. If your upgrade fails with
1313 -j, please try again without -j. From time to time in the past there
1314 have been problems using -j with buildworld and/or installworld. This
1315 is especially true when upgrading between "distant" versions (eg one
1316 that cross a major release boundary or several minor releases, or when
1317 several months have passed on the -current branch).
1319 Sometimes, obscure build problems are the result of environment
1320 poisoning. This can happen because the make utility reads its
1321 environment when searching for values for global variables. To run
1322 your build attempts in an "environmental clean room", prefix all make
1323 commands with 'env -i '. See the env(1) manual page for more details.
1325 When upgrading from one major version to another it is generally best
1326 to upgrade to the latest code in the currently installed branch first,
1327 then do an upgrade to the new branch. This is the best-tested upgrade
1328 path, and has the highest probability of being successful. Please try
1329 this approach before reporting problems with a major version upgrade.
1331 When upgrading a live system, having a root shell around before
1332 installing anything can help undo problems. Not having a root shell
1333 around can lead to problems if pam has changed too much from your
1334 starting point to allow continued authentication after the upgrade.
1336 This file should be read as a log of events. When a later event changes
1337 information of a prior event, the prior event should not be deleted.
1338 Instead, a pointer to the entry with the new information should be
1339 placed in the old entry. Readers of this file should also sanity check
1340 older entries before relying on them blindly. Authors of new entries
1341 should write them with this in mind.
1345 When upgrading the boot ZFS pool to a new version, always follow
1348 1.) recompile and reinstall the ZFS boot loader and boot block
1349 (this is part of "make buildworld" and "make installworld")
1351 2.) update the ZFS boot block on your boot drive
1353 The following example updates the ZFS boot block on the first
1354 partition (freebsd-boot) of a GPT partitioned drive ada0:
1355 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1357 Non-boot pools do not need these updates.
1361 If you are updating from a prior version of FreeBSD (even one just
1362 a few days old), you should follow this procedure. It is the most
1363 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1365 make kernel-toolchain
1366 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1367 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1369 To test a kernel once
1370 ---------------------
1371 If you just want to boot a kernel once (because you are not sure
1372 if it works, or if you want to boot a known bad kernel to provide
1373 debugging information) run
1374 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1375 nextboot -k testkernel
1377 To just build a kernel when you know that it won't mess you up
1378 --------------------------------------------------------------
1379 This assumes you are already running a CURRENT system. Replace
1380 ${arch} with the architecture of your machine (e.g. "i386",
1381 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1383 cd src/sys/${arch}/conf
1384 config KERNEL_NAME_HERE
1385 cd ../compile/KERNEL_NAME_HERE
1390 If this fails, go to the "To build a kernel" section.
1392 To rebuild everything and install it on the current system.
1393 -----------------------------------------------------------
1394 # Note: sometimes if you are running current you gotta do more than
1395 # is listed here if you are upgrading from a really old current.
1397 <make sure you have good level 0 dumps>
1399 make kernel KERNCONF=YOUR_KERNEL_HERE
1401 <reboot in single user> [3]
1408 To cross-install current onto a separate partition
1409 --------------------------------------------------
1410 # In this approach we use a separate partition to hold
1411 # current's root, 'usr', and 'var' directories. A partition
1412 # holding "/", "/usr" and "/var" should be about 2GB in
1415 <make sure you have good level 0 dumps>
1418 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1419 <maybe newfs current's root partition>
1420 <mount current's root partition on directory ${CURRENT_ROOT}>
1421 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1422 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1423 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1424 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1425 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1426 <reboot into current>
1427 <do a "native" rebuild/install as described in the previous section>
1428 <maybe install compatibility libraries from ports/misc/compat*>
1432 To upgrade in-place from stable to current
1433 ----------------------------------------------
1434 <make sure you have good level 0 dumps>
1436 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1438 <reboot in single user> [3]
1445 Make sure that you've read the UPDATING file to understand the
1446 tweaks to various things you need. At this point in the life
1447 cycle of current, things change often and you are on your own
1448 to cope. The defaults can also change, so please read ALL of
1449 the UPDATING entries.
1451 Also, if you are tracking -current, you must be subscribed to
1452 freebsd-current@freebsd.org. Make sure that before you update
1453 your sources that you have read and understood all the recent
1454 messages there. If in doubt, please track -stable which has
1455 much fewer pitfalls.
1457 [1] If you have third party modules, such as vmware, you
1458 should disable them at this point so they don't crash your
1461 [3] From the bootblocks, boot -s, and then do
1466 adjkerntz -i # if CMOS is wall time
1467 Also, when doing a major release upgrade, it is required that
1468 you boot into single user mode to do the installworld.
1470 [4] Note: This step is non-optional. Failure to do this step
1471 can result in a significant reduction in the functionality of the
1472 system. Attempting to do it by hand is not recommended and those
1473 that pursue this avenue should read this file carefully, as well
1474 as the archives of freebsd-current and freebsd-hackers mailing lists
1475 for potential gotchas. The -U option is also useful to consider.
1476 See mergemaster(8) for more information.
1478 [5] Usually this step is a noop. However, from time to time
1479 you may need to do this if you get unknown user in the following
1480 step. It never hurts to do it all the time. You may need to
1481 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1482 install) after the buildworld before this step if you last updated
1483 from current before 20130425 or from -stable before 20130430.
1485 [6] This only deletes old files and directories. Old libraries
1486 can be deleted by "make delete-old-libs", but you have to make
1487 sure that no program is using those libraries anymore.
1489 [8] In order to have a kernel that can run the 4.x binaries needed to
1490 do an installworld, you must include the COMPAT_FREEBSD4 option in
1491 your kernel. Failure to do so may leave you with a system that is
1492 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1493 required to run the 5.x binaries on more recent kernels. And so on
1494 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1496 Make sure that you merge any new devices from GENERIC since the
1497 last time you updated your kernel config file.
1499 [9] When checking out sources, you must include the -P flag to have
1500 cvs prune empty directories.
1502 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1503 "?=" instead of the "=" assignment operator, so that buildworld can
1504 override the CPUTYPE if it needs to.
1506 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1507 not on the command line, or in /etc/make.conf. buildworld will
1508 warn if it is improperly defined.
1511 This file contains a list, in reverse chronological order, of major
1512 breakages in tracking -current. It is not guaranteed to be a complete
1513 list of such breakages, and only contains entries since September 23, 2011.
1514 If you need to see UPDATING entries from before that date, you will need
1515 to fetch an UPDATING file from an older FreeBSD release.
1517 Copyright information:
1519 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1521 Redistribution, publication, translation and use, with or without
1522 modification, in full or in part, in any form or format of this
1523 document are permitted without further permission from the author.
1525 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1526 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1527 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1528 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1529 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1530 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1531 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1532 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1533 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1534 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1535 POSSIBILITY OF SUCH DAMAGE.
1537 Contact Warner Losh if you have any questions about your use of