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