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 from
17 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 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
36 Please see the 20141231 entry below for information about prerequisites
37 and upgrading, if you are not already using clang 3.5.0 or higher.
40 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
41 and renamed from .symbols to .debug. This reduces the size requirements
42 on the boot partition or file system and provides consistency with
45 When using the supported kernel installation method the
46 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
47 as is done with /boot/kernel.
49 Developers wishing to maintain the historical behavior of installing
50 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
53 The wireless drivers had undergone changes that remove the 'parent
54 interface' from the ifconfig -l output. The rc.d network scripts
55 used to check presence of a parent interface in the list, so old
56 scripts would fail to start wireless networking. Thus, etcupdate(3)
57 or mergemaster(8) run is required after kernel update, to update your
61 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
62 These configurations are now automatically interpreted as
63 'scrub fragment reassemble'.
66 Kernel-loadable modules for the random(4) device are back. To use
67 them, the kernel must have
70 options RANDOM_LOADABLE
72 kldload(8) can then be used to load random_fortuna.ko
73 or random_yarrow.ko. Please note that due to the indirect
74 function calls that the loadable modules need to provide,
75 the build-in variants will be slightly more efficient.
77 The random(4) kernel option RANDOM_DUMMY has been retired due to
78 unpopularity. It was not all that useful anyway.
81 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
82 Control over building the ELF Tool Chain tools is now provided by
83 the WITHOUT_TOOLCHAIN knob.
86 The polarity of Pulse Per Second (PPS) capture events with the
87 uart(4) driver has been corrected. Prior to this change the PPS
88 "assert" event corresponded to the trailing edge of a positive PPS
89 pulse and the "clear" event was the leading edge of the next pulse.
91 As the width of a PPS pulse in a typical GPS receiver is on the
92 order of 1 millisecond, most users will not notice any significant
93 difference with this change.
95 Anyone who has compensated for the historical polarity reversal by
96 configuring a negative offset equal to the pulse width will need to
97 remove that workaround.
100 The default group assigned to /dev/dri entries has been changed
101 from 'wheel' to 'video' with the id of '44'. If you want to have
102 access to the dri devices please add yourself to the video group
105 # pw groupmod video -m $USER
108 The menu.rc and loader.rc files will now be replaced during
109 upgrades. Please migrate local changes to menu.rc.local and
110 loader.rc.local instead.
113 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
114 strings and strip have been removed. The src.conf(5) knob
115 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
118 As ZFS requires more kernel stack pages than is the default on some
119 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
120 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
122 Please consider using 'options KSTACK_PAGES=X' where X is greater
123 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
126 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
127 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
128 default, i.e., they will not contain "::". For example, instead
129 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
130 to have a more specific match, such as different map entries for
131 IPv6:0:0 vs IPv6:0. This change requires that configuration
132 data (including maps, files, classes, custom ruleset, etc.) must
133 use the same format, so make certain such configuration data is
134 upgrading. As a very simple check search for patterns like
135 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
136 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
137 the cf option UseCompressedIPv6Addresses.
140 The default kernel entropy-processing algorithm is now
141 Fortuna, replacing Yarrow.
143 Assuming you have 'device random' in your kernel config
144 file, the configurations allow a kernel option to override
145 this default. You may choose *ONE* of:
147 options RANDOM_YARROW # Legacy /dev/random algorithm.
148 options RANDOM_DUMMY # Blocking-only driver.
150 If you have neither, you get Fortuna. For most people,
151 read no further, Fortuna will give a /dev/random that works
152 like it always used to, and the difference will be irrelevant.
154 If you remove 'device random', you get *NO* kernel-processed
155 entopy at all. This may be acceptable to folks building
156 embedded systems, but has complications. Carry on reading,
157 and it is assumed you know what you need.
159 *PLEASE* read random(4) and random(9) if you are in the
160 habit of tweeking kernel configs, and/or if you are a member
161 of the embedded community, wanting specific and not-usual
162 behaviour from your security subsystems.
164 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
165 random', you will NOT have a functioning /dev/random, and
166 many cryptographic features will not work, including SSH.
167 You may also find strange behaviour from the random(3) set
168 of library functions, in particular sranddev(3), srandomdev(3)
169 and arc4random(3). The reason for this is that the KERN_ARND
170 sysctl only returns entropy if it thinks it has some to
171 share, and with RANDOM_DUMMY or no 'device random' this
175 An additional fix for the issue described in the 20150614 sendmail
176 entry below has been been committed in revision 284717.
179 FreeBSD's old make (fmake) has been removed from the system. It is
180 available as the devel/fmake port or via pkg install fmake.
183 The fix for the issue described in the 20150614 sendmail entry
184 below has been been committed in revision 284436. The work
185 around described in that entry is no longer needed unless the
186 default setting is overridden by a confDH_PARAMETERS configuration
187 setting of '5' or pointing to a 512 bit DH parameter file.
190 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
191 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
192 and devel/kyua to version 0.20+ and adjust any calling code to work
193 with Kyuafile and kyua.
196 The import of openssl to address the FreeBSD-SA-15:10.openssl
197 security advisory includes a change which rejects handshakes
198 with DH parameters below 768 bits. sendmail releases prior
199 to 8.15.2 (not yet released), defaulted to a 512 bit
200 DH parameter setting for client connections. To work around
201 this interoperability, sendmail can be configured to use a
202 2048 bit DH parameter by:
204 1. Edit /etc/mail/`hostname`.mc
205 2. If a setting for confDH_PARAMETERS does not exist or
206 exists and is set to a string beginning with '5',
208 3. If a setting for confDH_PARAMETERS exists and is set to
209 a file path, create a new file with:
210 openssl dhparam -out /path/to/file 2048
211 4. Rebuild the .cf file:
212 cd /etc/mail/; make; make install
214 cd /etc/mail/; make restart
216 A sendmail patch is coming, at which time this file will be
220 Generation of legacy formatted entries have been disabled by default
221 in pwd_mkdb(8), as all base system consumers of the legacy formatted
222 entries were converted to use the new format by default when the new,
223 machine independent format have been added and supported since FreeBSD
226 Please see the pwd_mkdb(8) manual page for further details.
229 Clang and llvm have been upgraded to 3.6.1 release. Please see the
230 20141231 entry below for information about prerequisites and upgrading,
231 if you are not already using 3.5.0 or higher.
234 TI platform code switched to using vendor DTS files and this update
235 may break existing systems running on Beaglebone, Beaglebone Black,
238 - dtb files should be regenerated/reinstalled. Filenames are the
239 same but content is different now
240 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
241 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
242 addressing scheme is now pin 25 on /dev/gpioc3.
243 - Pandaboard: /etc/ttys should be updated, serial console device is
244 now /dev/ttyu2, not /dev/ttyu0
247 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
248 If you need the GNU extension from groff soelim(1), install groff
249 from package: pkg install groff, or via ports: textproc/groff.
252 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
253 defined in symlink(7); previously symlinks were silently ignored.
256 The const qualifier has been removed from iconv(3) to comply with
257 POSIX. The ports tree is aware of this from r384038 onwards.
260 Libraries specified by LIBADD in Makefiles must have a corresponding
261 DPADD_<lib> variable to ensure correct dependencies. This is now
262 enforced in src.libnames.mk.
265 From legacy ata(4) driver was removed support for SATA controllers
266 supported by more functional drivers ahci(4), siis(4) and mvs(4).
267 Kernel modules ataahci and ataadaptec were removed completely,
268 replaced by ahci and mvs modules respectively.
271 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
272 the 20141231 entry below for information about prerequisites and
273 upgrading, if you are not already using 3.5.0 or higher.
276 The 32-bit PowerPC kernel has been changed to a position-independent
277 executable. This can only be booted with a version of loader(8)
278 newer than January 31, 2015, so make sure to update both world and
279 kernel before rebooting.
282 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
283 but before r278950, the RNG was not seeded properly. Immediately
284 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
285 ssh keys or openssl keys) that were generated w/ a kernel from that
286 range. This does not affect programs that directly used /dev/random
287 or /dev/urandom. All userland uses of arc4random(3) are affected.
290 The autofs(4) ABI was changed in order to restore binary compatibility
291 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
295 The powerpc64 kernel has been changed to a position-independent
296 executable. This can only be booted with a new version of loader(8),
297 so make sure to update both world and kernel before rebooting.
300 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
301 only release, no new features have been added. Please see the 20141231
302 entry below for information about prerequisites and upgrading, if you
303 are not already using 3.5.0.
306 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
307 taken from the ELF Tool Chain project rather than GNU binutils. They
308 should be drop-in replacements, with the addition of arm64 support.
309 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
310 binutils tools, if necessary. See 20150805 for updated information.
313 The default Unbound configuration now enables remote control
314 using a local socket. Users who have already enabled the
315 local_unbound service should regenerate their configuration
316 by running "service local_unbound setup" as root.
319 The GNU texinfo and GNU info pages have been removed.
320 To be able to view GNU info pages please install texinfo from ports.
323 Clang, llvm and lldb have been upgraded to 3.5.0 release.
325 As of this release, a prerequisite for building clang, llvm and lldb is
326 a C++11 capable compiler and C++11 standard library. This means that to
327 be able to successfully build the cross-tools stage of buildworld, with
328 clang as the bootstrap compiler, your system compiler or cross compiler
329 should either be clang 3.3 or later, or gcc 4.8 or later, and your
330 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
333 On any standard FreeBSD 10.x or 11.x installation, where clang and
334 libc++ are on by default (that is, on x86 or arm), this should work out
337 On 9.x installations where clang is enabled by default, e.g. on x86 and
338 powerpc, libc++ will not be enabled by default, so libc++ should be
339 built (with clang) and installed first. If both clang and libc++ are
340 missing, build clang first, then use it to build libc++.
342 On 8.x and earlier installations, upgrade to 9.x first, and then follow
343 the instructions for 9.x above.
345 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
346 default, and do not build clang.
348 Many embedded systems are resource constrained, and will not be able to
349 build clang in a reasonable time, or in some cases at all. In those
350 cases, cross building bootable systems on amd64 is a workaround.
352 This new version of clang introduces a number of new warnings, of which
353 the following are most likely to appear:
357 This warns in two cases, for both C and C++:
358 * When the code is trying to take the absolute value of an unsigned
359 quantity, which is effectively a no-op, and almost never what was
360 intended. The code should be fixed, if at all possible. If you are
361 sure that the unsigned quantity can be safely cast to signed, without
362 loss of information or undefined behavior, you can add an explicit
363 cast, or disable the warning.
365 * When the code is trying to take an absolute value, but the called
366 abs() variant is for the wrong type, which can lead to truncation.
367 If you want to disable the warning instead of fixing the code, please
368 make sure that truncation will not occur, or it might lead to unwanted
371 -Wtautological-undefined-compare and
372 -Wundefined-bool-conversion
374 These warn when C++ code is trying to compare 'this' against NULL, while
375 'this' should never be NULL in well-defined C++ code. However, there is
376 some legacy (pre C++11) code out there, which actively abuses this
377 feature, which was less strictly defined in previous C++ versions.
379 Squid and openjdk do this, for example. The warning can be turned off
380 for C++98 and earlier, but compiling the code in C++11 mode might result
381 in unexpected behavior; for example, the parts of the program that are
382 unreachable could be optimized away.
385 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
386 kernel sources have been removed. The .h files remain, since some
387 utilities include them. This will need to be fixed later.
388 If "mount -t oldnfs ..." is attempted, it will fail.
389 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
390 the utilities will report errors.
393 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
394 directories to top level SUBDIR variable when their parent
395 directory is included in LOCAL_DIRS. Users with build systems with
396 such hierarchies and without SUBDIR entries in the parent
397 directory Makefiles should add them or add the directories to
401 faith(4) and faithd(8) have been removed from the base system. Faith
402 has been obsolete for a very long time.
405 vt(4), the new console driver, is enabled by default. It brings
406 support for Unicode and double-width characters, as well as
407 support for UEFI and integration with the KMS kernel video
410 You may need to update your console settings in /etc/rc.conf,
411 most probably the keymap. During boot, /etc/rc.d/syscons will
412 indicate what you need to do.
414 vt(4) still has issues and lacks some features compared to
415 syscons(4). See the wiki for up-to-date information:
416 https://wiki.freebsd.org/Newcons
418 If you want to keep using syscons(4), you can do so by adding
419 the following line to /boot/loader.conf:
423 pjdfstest has been integrated into kyua as an opt-in test suite.
424 Please see share/doc/pjdfstest/README for more details on how to
428 gperf has been removed from the base system for architectures
429 that use clang. Ports that require gperf will obtain it from the
433 pjdfstest has been moved from tools/regression/pjdfstest to
437 At svn r271982, The default linux compat kernel ABI has been adjusted
438 to 2.6.18 in support of the linux-c6 compat ports infrastructure
439 update. If you wish to continue using the linux-f10 compat ports,
440 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
441 encouraged to update their linux-compat packages to linux-c6 during
442 their next update cycle.
445 The ofwfb driver, used to provide a graphics console on PowerPC when
446 using vt(4), no longer allows mmap() of all physical memory. This
447 will prevent Xorg on PowerPC with some ATI graphics cards from
448 initializing properly unless x11-servers/xorg-server is updated to
452 The xdev targets have been converted to using TARGET and
453 TARGET_ARCH instead of XDEV and XDEV_ARCH.
456 The default unbound configuration has been modified to address
457 issues with reverse lookups on networks that use private
458 address ranges. If you use the local_unbound service, run
459 "service local_unbound setup" as root to regenerate your
460 configuration, then "service local_unbound reload" to load the
464 The GNU texinfo and GNU info pages are not built and installed
465 anymore, WITH_INFO knob has been added to allow to built and install
467 UPDATE: see 20150102 entry on texinfo's removal
470 The GNU readline library is now an INTERNALLIB - that is, it is
471 statically linked into consumers (GDB and variants) in the base
472 system, and the shared library is no longer installed. The
473 devel/readline port is available for third party software that
477 The Itanium architecture (ia64) has been removed from the list of
478 known architectures. This is the first step in the removal of the
482 Commit r268115 has added NFSv4.1 server support, merged from
483 projects/nfsv4.1-server. Since this includes changes to the
484 internal interfaces between the NFS related modules, a full
485 build of the kernel and modules will be necessary.
486 __FreeBSD_version has been bumped.
489 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
490 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
491 which differs from the behaviour controlled by this knob.)
494 Maximal length of the serial number in CTL was increased from 16 to
495 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
496 and ctld, need to be rebuilt to work with a new kernel.
499 The libatf-c and libatf-c++ major versions were downgraded to 0 and
500 1 respectively to match the upstream numbers. They were out of
501 sync because, when they were originally added to FreeBSD, the
502 upstream versions were not respected. These libraries are private
503 and not yet built by default, so renumbering them should be a
504 non-issue. However, unclean source trees will yield broken test
505 programs once the operator executes "make delete-old-libs" after a
508 Additionally, the atf-sh binary was made private by moving it into
509 /usr/libexec/. Already-built shell test programs will keep the
510 path to the old binary so they will break after "make delete-old"
513 If you are using WITH_TESTS=yes (not the default), wipe the object
514 tree and rebuild from scratch to prevent spurious test failures.
515 This is only needed once: the misnumbered libraries and misplaced
516 binaries have been added to OptionalObsoleteFiles.inc so they will
517 be removed during a clean upgrade.
520 Clang and llvm have been upgraded to 3.4.1 release.
523 We bogusly installed src.opts.mk in /usr/share/mk. This file should
524 be removed to avoid issues in the future (and has been added to
528 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
529 past, it affected all builds that used the bsd.*.mk files. The old
530 behavior was a bug, but people may have relied upon it. To get this
531 behavior back, you can .include /etc/src.conf from /etc/make.conf
532 (which is still global and isn't changed). This also changes the
533 behavior of incremental builds inside the tree of individual
534 directories. Set MAKESYSPATH to ".../share/mk" to do that.
535 Although this has survived make universe and some upgrade scenarios,
536 other upgrade scenarios may have broken. At least one form of
537 temporary breakage was fixed with MAKESYSPATH settings for buildworld
538 as well... In cases where MAKESYSPATH isn't working with this
539 setting, you'll need to set it to the full path to your tree.
541 One side effect of all this cleaning up is that bsd.compiler.mk
542 is no longer implicitly included by bsd.own.mk. If you wish to
543 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
547 The lindev device has been removed since /dev/full has been made a
548 standard device. __FreeBSD_version has been bumped.
551 The knob WITHOUT_VI was added to the base system, which controls
552 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
553 in order to reorder files share/termcap and didn't build ex(1) as a
554 build tool, so building/installing with WITH_VI is highly advised for
555 build hosts for older releases.
557 This issue has been fixed in stable/9 and stable/10 in r277022 and
558 r276991, respectively.
561 The YES_HESIOD knob has been removed. It has been obsolete for
562 a decade. Please move to using WITH_HESIOD instead or your builds
563 will silently lack HESIOD.
566 The uart(4) driver has been changed with respect to its handling
567 of the low-level console. Previously the uart(4) driver prevented
568 any process from changing the baudrate or the CLOCAL and HUPCL
569 control flags. By removing the restrictions, operators can make
570 changes to the serial console port without having to reboot.
571 However, when getty(8) is started on the serial device that is
572 associated with the low-level console, a misconfigured terminal
573 line in /etc/ttys will now have a real impact.
574 Before upgrading the kernel, make sure that /etc/ttys has the
575 serial console device configured as 3wire without baudrate to
576 preserve the previous behaviour. E.g:
577 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
580 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
581 to improve performance. To re-enable it, if needed, run rpcbind
582 with command line option -W.
585 Switched back to the GPL dtc compiler due to updates in the upstream
586 dts files not being supported by the BSDL dtc compiler. You will need
587 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
588 may result while building dtb files during a kernel build if you fail
589 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
592 Clang and llvm have been upgraded to 3.4 release.
595 The nve(4) driver has been removed. Please use the nfe(4) driver
596 for NVIDIA nForce MCP Ethernet adapters instead.
599 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
600 This could cause certain C++ applications using shared libraries built
601 against the previous version of libc++ to crash. The incompatibility
602 has now been fixed, but any C++ applications or shared libraries built
603 between r261283 and r261801 should be recompiled.
606 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
607 capability mode support. Please note that enabling the feature in
608 kernel is still highly recommended.
611 OpenSSH is now built with sandbox support, and will use sandbox as
612 the default privilege separation method. This requires Capsicum
613 capability mode support in kernel.
616 The libelf and libdwarf libraries have been updated to newer
617 versions from upstream. Shared library version numbers for
618 these two libraries were bumped. Any ports or binaries
619 requiring these two libraries should be recompiled.
620 __FreeBSD_version is bumped to 1100006.
623 If a Makefile in a tests/ directory was auto-generating a Kyuafile
624 instead of providing an explicit one, this would prevent such
625 Makefile from providing its own Kyuafile in the future during
626 NO_CLEAN builds. This has been fixed in the Makefiles but manual
627 intervention is needed to clean an objdir if you use NO_CLEAN:
628 # find /usr/obj -name Kyuafile | xargs rm -f
631 The behavior of gss_pseudo_random() for the krb5 mechanism
632 has changed, for applications requesting a longer random string
633 than produced by the underlying enctype's pseudo-random() function.
634 In particular, the random string produced from a session key of
635 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
636 be different at the 17th octet and later, after this change.
637 The counter used in the PRF+ construction is now encoded as a
638 big-endian integer in accordance with RFC 4402.
639 __FreeBSD_version is bumped to 1100004.
642 The WITHOUT_ATF build knob has been removed and its functionality
643 has been subsumed into the more generic WITHOUT_TESTS. If you were
644 using the former to disable the build of the ATF libraries, you
645 should change your settings to use the latter.
648 The default version of mtree is nmtree which is obtained from
649 NetBSD. The output is generally the same, but may vary
650 slightly. If you found you need identical output adding
651 "-F freebsd9" to the command line should do the trick. For the
652 time being, the old mtree is available as fmtree.
655 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
656 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
657 1.1.4_8 and verify bsdyml not linked in, before running "make
659 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
661 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
664 The stable/10 branch has been created in subversion from head
668 The rc.d/jail script has been updated to support jail(8)
669 configuration file. The "jail_<jname>_*" rc.conf(5) variables
670 for per-jail configuration are automatically converted to
671 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
672 This is transparently backward compatible. See below about some
673 incompatibilities and rc.conf(5) manual page for more details.
675 These variables are now deprecated in favor of jail(8) configuration
676 file. One can use "rc.d/jail config <jname>" command to generate
677 a jail(8) configuration file in /var/run/jail.<jname>.conf without
678 running the jail(8) utility. The default pathname of the
679 configuration file is /etc/jail.conf and can be specified by
680 using $jail_conf or $jail_<jname>_conf variables.
682 Please note that jail_devfs_ruleset accepts an integer at
683 this moment. Please consider to rewrite the ruleset name
687 BIND has been removed from the base system. If all you need
688 is a local resolver, simply enable and start the local_unbound
689 service instead. Otherwise, several versions of BIND are
690 available in the ports tree. The dns/bind99 port is one example.
692 With this change, nslookup(1) and dig(1) are no longer in the base
693 system. Users should instead use host(1) and drill(1) which are
694 in the base system. Alternatively, nslookup and dig can
695 be obtained by installing the dns/bind-tools port.
698 With the addition of unbound(8), a new unbound user is now
699 required during installworld. "mergemaster -p" can be used to
700 add the user prior to installworld, as documented in the handbook.
703 OpenSSH is now built with DNSSEC support, and will by default
704 silently trust signed SSHFP records. This can be controlled with
705 the VerifyHostKeyDNS client configuration setting. DNSSEC support
706 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
709 The GNU Compiler Collection and C++ standard library (libstdc++)
710 are no longer built by default on platforms where clang is the system
711 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
715 The PROCDESC kernel option is now part of the GENERIC kernel
716 configuration and is required for the rwhod(8) to work.
717 If you are using custom kernel configuration, you should include
721 The API and ABI related to the Capsicum framework was modified
722 in backward incompatible way. The userland libraries and programs
723 have to be recompiled to work with the new kernel. This includes the
724 following libraries and programs, but the whole buildworld is
725 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
726 kdump, procstat, rwho, rwhod, uniq.
729 AES-NI intrinsic support has been added to gcc. The AES-NI module
730 has been updated to use this support. A new gcc is required to build
731 the aesni module on both i386 and amd64.
734 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
735 Thus "device padlock_rng" and "device rdrand_rng" should be
736 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
739 WITH_ICONV has been split into two feature sets. WITH_ICONV now
740 enables just the iconv* functionality and is now on by default.
741 WITH_LIBICONV_COMPAT enables the libiconv api and link time
742 compatability. Set WITHOUT_ICONV to build the old way.
743 If you have been using WITH_ICONV before, you will very likely
744 need to turn on WITH_LIBICONV_COMPAT.
747 INVARIANTS option now enables DEBUG for code with OpenSolaris and
748 Illumos origin, including ZFS. If you have INVARIANTS in your
749 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
751 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
752 locks if WITNESS option was set. Because that generated a lot of
753 witness(9) reports and all of them were believed to be false
754 positives, this is no longer done. New option OPENSOLARIS_WITNESS
755 can be used to achieve the previous behavior.
758 Timer values in IPv6 data structures now use time_uptime instead
759 of time_second. Although this is not a user-visible functional
760 change, userland utilities which directly use them---ndp(8),
761 rtadvd(8), and rtsold(8) in the base system---need to be updated
765 find -delete can now delete the pathnames given as arguments,
766 instead of only files found below them or if the pathname did
767 not contain any slashes. Formerly, the following error message
770 find: -delete: <path>: relative path potentially not safe
772 Deleting the pathnames given as arguments can be prevented
773 without error messages using -mindepth 1 or by changing
774 directory and passing "." as argument to find. This works in the
775 old as well as the new version of find.
778 Behavior of devfs rules path matching has been changed.
779 Pattern is now always matched against fully qualified devfs
780 path and slash characters must be explicitly matched by
781 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
782 subdirectories must be reviewed.
785 The default ARM ABI has changed to the ARM EABI. The old ABI is
786 incompatible with the ARM EABI and all programs and modules will
787 need to be rebuilt to work with a new kernel.
789 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
791 NOTE: Support for the old ABI will be removed in the future and
792 users are advised to upgrade.
795 pkg_install has been disconnected from the build if you really need it
796 you should add WITH_PKGTOOLS in your src.conf(5).
799 Most of network statistics structures were changed to be able
800 keep 64-bits counters. Thus all tools, that work with networking
801 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
804 Fix targets that run multiple make's to use && rather than ;
805 so that subsequent steps depend on success of previous.
807 NOTE: if building 'universe' with -j* on stable/8 or stable/9
808 it would be better to start the build using bmake, to avoid
809 overloading the machine.
812 Fix a bug that allowed a tracing process (e.g. gdb) to write
813 to a memory-mapped file in the traced process's address space
814 even if neither the traced process nor the tracing process had
815 write access to that file.
818 CVS has been removed from the base system. An exact copy
819 of the code is available from the devel/cvs port.
822 Some people report the following error after the switch to bmake:
824 make: illegal option -- J
825 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
827 *** [buildworld] Error code 2
829 this likely due to an old instance of make in
830 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
831 which src/Makefile will use that blindly, if it exists, so if
832 you see the above error:
834 rm -rf `make -V MAKEPATH`
839 Use bmake by default.
840 Whereas before one could choose to build with bmake via
841 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
842 make. The goal is to remove these knobs for 10-RELEASE.
844 It is worth noting that bmake (like gmake) treats the command
845 line as the unit of failure, rather than statements within the
846 command line. Thus '(cd some/where && dosomething)' is safer
847 than 'cd some/where; dosomething'. The '()' allows consistent
848 behavior in parallel build.
851 Fix a bug that allows NFS clients to issue READDIR on files.
854 The WITHOUT_IDEA option has been removed because
855 the IDEA patent expired.
858 The sysctl which controls TRIM support under ZFS has been renamed
859 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
863 The mergemaster command now uses the default MAKEOBJDIRPREFIX
864 rather than creating it's own in the temporary directory in
865 order allow access to bootstrapped versions of tools such as
866 install and mtree. When upgrading from version of FreeBSD where
867 the install command does not support -l, you will need to
868 install a new mergemaster command if mergemaster -p is required.
869 This can be accomplished with the command (cd src/usr.sbin/mergemaster
873 Legacy ATA stack, disabled and replaced by new CAM-based one since
874 FreeBSD 9.0, completely removed from the sources. Kernel modules
875 atadisk and atapi*, user-level tools atacontrol and burncd are
876 removed. Kernel option `options ATA_CAM` is now permanently enabled
880 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
881 and socketpair(2). Software, in particular Kerberos, may
882 automatically detect and use these during building. The resulting
883 binaries will not work on older kernels.
886 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
887 information, see the respective 20130304 entry).
890 Recent commits to callout(9) changed the size of struct callout,
891 so the KBI is probably heavily disturbed. Also, some functions
892 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
893 by macros. Every kernel module using it won't load, so rebuild
896 The ctl device has been re-enabled in GENERIC for i386 and amd64,
897 but does not initialize by default (because of the new CTL_DISABLE
898 option) to save memory. To re-enable it, remove the CTL_DISABLE
899 option from the kernel config file or set kern.cam.ctl.disable=0
900 in /boot/loader.conf.
903 The ctl device has been disabled in GENERIC for i386 and amd64.
904 This was done due to the extra memory being allocated at system
905 initialisation time by the ctl driver which was only used if
906 a CAM target device was created. This makes a FreeBSD system
907 unusable on 128MB or less of RAM.
910 A new compression method (lz4) has been merged to -HEAD. Please
911 refer to zpool-features(7) for more information.
913 Please refer to the "ZFS notes" section of this file for information
914 on upgrading boot ZFS pools.
917 A BSD-licensed patch(1) variant has been added and is installed
918 as bsdpatch, being the GNU version the default patch.
919 To inverse the logic and use the BSD-licensed one as default,
920 while having the GNU version installed as gnupatch, rebuild
921 and install world with the WITH_BSD_PATCH knob set.
924 Due to the use of the new -l option to install(1) during build
925 and install, you must take care not to directly set the INSTALL
926 make variable in your /etc/make.conf, /etc/src.conf, or on the
927 command line. If you wish to use the -C flag for all installs
928 you may be able to add INSTALL+=-C to /etc/make.conf or
932 The install(1) option -M has changed meaning and now takes an
933 argument that is a file or path to append logs to. In the
934 unlikely event that -M was the last option on the command line
935 and the command line contained at least two files and a target
936 directory the first file will have logs appended to it. The -M
937 option served little practical purpose in the last decade so its
938 use is expected to be extremely rare.
941 After switching to Clang as the default compiler some users of ZFS
942 on i386 systems started to experience stack overflow kernel panics.
943 Please consider using 'options KSTACK_PAGES=4' in such configurations.
946 GEOM_LABEL now mangles label names read from file system metadata.
947 Mangling affect labels containing spaces, non-printable characters,
948 '%' or '"'. Device names in /etc/fstab and other places may need to
952 By default, only the 10 most recent kernel dumps will be saved. To
953 restore the previous behaviour (no limit on the number of kernel dumps
954 stored in the dump directory) add the following line to /etc/rc.conf:
959 With the addition of auditdistd(8), a new auditdistd user is now
960 required during installworld. "mergemaster -p" can be used to
961 add the user prior to installworld, as documented in the handbook.
964 The sin6_scope_id member variable in struct sockaddr_in6 is now
965 filled by the kernel before passing the structure to the userland via
966 sysctl or routing socket. This means the KAME-specific embedded scope
967 id in sin6_addr.s6_addr[2] is always cleared in userland application.
968 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
969 __FreeBSD_version is bumped to 1000025.
972 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
973 This means that the world and kernel will be compiled with clang
974 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
975 and /usr/bin/cpp. To disable this behavior and revert to building
976 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
977 of current may need to bootstrap WITHOUT_CLANG first if the clang
978 build fails (its compatibility window doesn't extend to the 9 stable
982 The IPFIREWALL_FORWARD kernel option has been removed. Its
983 functionality now turned on by default.
986 The ZERO_COPY_SOCKET kernel option has been removed and
987 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
988 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
989 mechanism which is not safe and may result in kernel crashes.
990 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
991 driver supports disposeable external page sized mbuf storage.
992 Proper replacements for both zero-copy mechanisms are under
993 consideration and will eventually lead to complete removal
994 of the two kernel options.
997 The IPv4 network stack has been converted to network byte
998 order. The following modules need to be recompiled together
999 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1000 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1003 Support for non-MPSAFE filesystems was removed from VFS. The
1004 VFS_VERSION was bumped, all filesystem modules shall be
1008 All the non-MPSAFE filesystems have been disconnected from
1009 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1010 portalfs, smbfs, xfs.
1013 The interface cloning API and ABI has changed. The following
1014 modules need to be recompiled together with kernel:
1015 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1016 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1017 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1020 The sdhci driver was split in two parts: sdhci (generic SD Host
1021 Controller logic) and sdhci_pci (actual hardware driver).
1022 No kernel config modifications are required, but if you
1023 load sdhc as a module you must switch to sdhci_pci instead.
1026 Import the FUSE kernel and userland support into base system.
1029 The GNU sort(1) program has been removed since the BSD-licensed
1030 sort(1) has been the default for quite some time and no serious
1031 problems have been reported. The corresponding WITH_GNU_SORT
1035 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1036 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1040 The net80211(4) ABI has been changed to allow for improved driver
1041 PS-POLL and power-save support. All wireless drivers need to be
1042 recompiled to work with the new kernel.
1045 The random(4) support for the VIA hardware random number
1046 generator (`PADLOCK') is no longer enabled unconditionally.
1047 Add the padlock_rng device in the custom kernel config if
1048 needed. The GENERIC kernels on i386 and amd64 do include the
1049 device, so the change only affects the custom kernel
1053 The pf(4) packet filter ABI has been changed. pfctl(8) and
1054 snmp_pf module need to be recompiled to work with new kernel.
1057 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1058 to -HEAD. Pools that have empty_bpobj in active state can not be
1059 imported read-write with ZFS implementations that do not support
1060 this feature. For more information read the zpool-features(5)
1064 The sparc64 ZFS loader has been changed to no longer try to auto-
1065 detect ZFS providers based on diskN aliases but now requires these
1066 to be explicitly listed in the OFW boot-device environment variable.
1069 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1070 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1071 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1074 The following sysctls and tunables have been renamed for consistency
1075 with other variables:
1076 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1077 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1080 The sort utility has been replaced with BSD sort. For now, GNU sort
1081 is also available as "gnusort" or the default can be set back to
1082 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1083 installed as "bsdsort".
1086 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1087 Starting with this version the old system of ZFS pool versioning
1088 is superseded by "feature flags". This concept enables forward
1089 compatibility against certain future changes in functionality of ZFS
1090 pools. The first read-only compatible "feature flag" for ZFS pools
1091 is named "com.delphix:async_destroy". For more information
1092 read the new zpool-features(5) manual page.
1093 Please refer to the "ZFS notes" section of this file for information
1094 on upgrading boot ZFS pools.
1097 The malloc(3) implementation embedded in libc now uses sources imported
1098 as contrib/jemalloc. The most disruptive API change is to
1099 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1100 delete it prior to installworld, and optionally re-create it using the
1101 new format after rebooting. See malloc.conf(5) for details
1102 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1106 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1107 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1108 now spelled mips. This is to aid compatibility with third-party
1109 software that expects this naming scheme in uname(3). Little-endian
1110 settings are unchanged. If you are updating a big-endian mips64 machine
1111 from before this change, you may need to set MACHINE_ARCH=mips64 in
1112 your environment before the new build system will recognize your machine.
1115 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1119 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1120 nullfs(5) did not pass through all behaviours to the underlying layer,
1121 as a result if we bound to a socket on the lower layer we could connect
1122 only to the lower path; if we bound to the upper layer we could connect
1123 only to the upper path. The new behavior is one can connect to both the
1124 lower and the upper paths regardless what layer path one binds to.
1127 The getifaddrs upgrade path broken with 20111215 has been restored.
1128 If you have upgraded in between 20111215 and 20120209 you need to
1129 recompile libc again with your kernel. You still need to recompile
1130 world to be able to configure CARP but this restriction already
1131 comes from 20111215.
1134 The set_rcvar() function has been removed from /etc/rc.subr. All
1135 base and ports rc.d scripts have been updated, so if you have a
1136 port installed with a script in /usr/local/etc/rc.d you can either
1137 hand-edit the rcvar= line, or reinstall the port.
1139 An easy way to handle the mass-update of /etc/rc.d:
1140 rm /etc/rc.d/* && mergemaster -i
1143 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1144 on the current CPU and prevents other threads from running.
1145 This behavior can be reverted using the kern.stop_scheduler_on_panic
1147 The new behavior can be incompatible with kern.sync_on_panic.
1150 The carp(4) facility has been changed significantly. Configuration
1151 of the CARP protocol via ifconfig(8) has changed, as well as format
1152 of CARP events submitted to devd(8) has changed. See manual pages
1153 for more information. The arpbalance feature of carp(4) is currently
1154 not supported anymore.
1156 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1157 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1158 need to be recompiled.
1161 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1165 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1166 explicitely support non-MPSAFE filesystems.
1167 It is on by default for all supported platform at this present
1171 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1172 i386 and pc98 GENERIC kernel configuration files.
1175 sysinstall has been removed
1178 The stable/9 branch created in subversion. This corresponds to the
1179 RELENG_9 branch in CVS.
1185 Avoid using make -j when upgrading. While generally safe, there are
1186 sometimes problems using -j to upgrade. If your upgrade fails with
1187 -j, please try again without -j. From time to time in the past there
1188 have been problems using -j with buildworld and/or installworld. This
1189 is especially true when upgrading between "distant" versions (eg one
1190 that cross a major release boundary or several minor releases, or when
1191 several months have passed on the -current branch).
1193 Sometimes, obscure build problems are the result of environment
1194 poisoning. This can happen because the make utility reads its
1195 environment when searching for values for global variables. To run
1196 your build attempts in an "environmental clean room", prefix all make
1197 commands with 'env -i '. See the env(1) manual page for more details.
1199 When upgrading from one major version to another it is generally best
1200 to upgrade to the latest code in the currently installed branch first,
1201 then do an upgrade to the new branch. This is the best-tested upgrade
1202 path, and has the highest probability of being successful. Please try
1203 this approach before reporting problems with a major version upgrade.
1205 When upgrading a live system, having a root shell around before
1206 installing anything can help undo problems. Not having a root shell
1207 around can lead to problems if pam has changed too much from your
1208 starting point to allow continued authentication after the upgrade.
1210 This file should be read as a log of events. When a later event changes
1211 information of a prior event, the prior event should not be deleted.
1212 Instead, a pointer to the entry with the new information should be
1213 placed in the old entry. Readers of this file should also sanity check
1214 older entries before relying on them blindly. Authors of new entries
1215 should write them with this in mind.
1219 When upgrading the boot ZFS pool to a new version, always follow
1222 1.) recompile and reinstall the ZFS boot loader and boot block
1223 (this is part of "make buildworld" and "make installworld")
1225 2.) update the ZFS boot block on your boot drive
1227 The following example updates the ZFS boot block on the first
1228 partition (freebsd-boot) of a GPT partitioned drive ada0:
1229 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1231 Non-boot pools do not need these updates.
1235 If you are updating from a prior version of FreeBSD (even one just
1236 a few days old), you should follow this procedure. It is the most
1237 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1239 make kernel-toolchain
1240 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1241 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1243 To test a kernel once
1244 ---------------------
1245 If you just want to boot a kernel once (because you are not sure
1246 if it works, or if you want to boot a known bad kernel to provide
1247 debugging information) run
1248 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1249 nextboot -k testkernel
1251 To just build a kernel when you know that it won't mess you up
1252 --------------------------------------------------------------
1253 This assumes you are already running a CURRENT system. Replace
1254 ${arch} with the architecture of your machine (e.g. "i386",
1255 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1257 cd src/sys/${arch}/conf
1258 config KERNEL_NAME_HERE
1259 cd ../compile/KERNEL_NAME_HERE
1264 If this fails, go to the "To build a kernel" section.
1266 To rebuild everything and install it on the current system.
1267 -----------------------------------------------------------
1268 # Note: sometimes if you are running current you gotta do more than
1269 # is listed here if you are upgrading from a really old current.
1271 <make sure you have good level 0 dumps>
1273 make kernel KERNCONF=YOUR_KERNEL_HERE
1275 <reboot in single user> [3]
1282 To cross-install current onto a separate partition
1283 --------------------------------------------------
1284 # In this approach we use a separate partition to hold
1285 # current's root, 'usr', and 'var' directories. A partition
1286 # holding "/", "/usr" and "/var" should be about 2GB in
1289 <make sure you have good level 0 dumps>
1292 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1293 <maybe newfs current's root partition>
1294 <mount current's root partition on directory ${CURRENT_ROOT}>
1295 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1296 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1297 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1298 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1299 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1300 <reboot into current>
1301 <do a "native" rebuild/install as described in the previous section>
1302 <maybe install compatibility libraries from ports/misc/compat*>
1306 To upgrade in-place from stable to current
1307 ----------------------------------------------
1308 <make sure you have good level 0 dumps>
1310 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1312 <reboot in single user> [3]
1319 Make sure that you've read the UPDATING file to understand the
1320 tweaks to various things you need. At this point in the life
1321 cycle of current, things change often and you are on your own
1322 to cope. The defaults can also change, so please read ALL of
1323 the UPDATING entries.
1325 Also, if you are tracking -current, you must be subscribed to
1326 freebsd-current@freebsd.org. Make sure that before you update
1327 your sources that you have read and understood all the recent
1328 messages there. If in doubt, please track -stable which has
1329 much fewer pitfalls.
1331 [1] If you have third party modules, such as vmware, you
1332 should disable them at this point so they don't crash your
1335 [3] From the bootblocks, boot -s, and then do
1340 adjkerntz -i # if CMOS is wall time
1341 Also, when doing a major release upgrade, it is required that
1342 you boot into single user mode to do the installworld.
1344 [4] Note: This step is non-optional. Failure to do this step
1345 can result in a significant reduction in the functionality of the
1346 system. Attempting to do it by hand is not recommended and those
1347 that pursue this avenue should read this file carefully, as well
1348 as the archives of freebsd-current and freebsd-hackers mailing lists
1349 for potential gotchas. The -U option is also useful to consider.
1350 See mergemaster(8) for more information.
1352 [5] Usually this step is a noop. However, from time to time
1353 you may need to do this if you get unknown user in the following
1354 step. It never hurts to do it all the time. You may need to
1355 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1356 install) after the buildworld before this step if you last updated
1357 from current before 20130425 or from -stable before 20130430.
1359 [6] This only deletes old files and directories. Old libraries
1360 can be deleted by "make delete-old-libs", but you have to make
1361 sure that no program is using those libraries anymore.
1363 [8] In order to have a kernel that can run the 4.x binaries needed to
1364 do an installworld, you must include the COMPAT_FREEBSD4 option in
1365 your kernel. Failure to do so may leave you with a system that is
1366 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1367 required to run the 5.x binaries on more recent kernels. And so on
1368 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1370 Make sure that you merge any new devices from GENERIC since the
1371 last time you updated your kernel config file.
1373 [9] When checking out sources, you must include the -P flag to have
1374 cvs prune empty directories.
1376 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1377 "?=" instead of the "=" assignment operator, so that buildworld can
1378 override the CPUTYPE if it needs to.
1380 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1381 not on the command line, or in /etc/make.conf. buildworld will
1382 warn if it is improperly defined.
1385 This file contains a list, in reverse chronological order, of major
1386 breakages in tracking -current. It is not guaranteed to be a complete
1387 list of such breakages, and only contains entries since September 23, 2011.
1388 If you need to see UPDATING entries from before that date, you will need
1389 to fetch an UPDATING file from an older FreeBSD release.
1391 Copyright information:
1393 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1395 Redistribution, publication, translation and use, with or without
1396 modification, in full or in part, in any form or format of this
1397 document are permitted without further permission from the author.
1399 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1400 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1401 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1402 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1403 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1404 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1405 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1406 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1407 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1408 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1409 POSSIBILITY OF SUCH DAMAGE.
1411 Contact Warner Losh if you have any questions about your use of