1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 The build previously allowed using 'make -n' to not recurse into
36 sub-directories while showing what commands would be executed, and
37 'make -n -n' to recursively show commands. Now 'make -n' will recurse
38 and 'make -N' will not.
41 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
42 and etcupdate will now use this file. A custom sendmail.cf is now
43 updated via this mechanism rather than via installworld. If you had
44 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
45 want to remove the exclusion or change it to "always install".
46 /etc/mail/sendmail.cf is now managed the same way regardless of
47 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
48 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
51 Compatibility shims for legacy ATA device names have been removed.
52 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
53 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
54 environment variables, /dev/ad* and /dev/ar* symbolic links.
57 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
58 Please see the 20141231 entry below for information about prerequisites
59 and upgrading, if you are not already using clang 3.5.0 or higher.
62 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
63 and renamed from .symbols to .debug. This reduces the size requirements
64 on the boot partition or file system and provides consistency with
67 When using the supported kernel installation method the
68 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
69 as is done with /boot/kernel.
71 Developers wishing to maintain the historical behavior of installing
72 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
75 The wireless drivers had undergone changes that remove the 'parent
76 interface' from the ifconfig -l output. The rc.d network scripts
77 used to check presence of a parent interface in the list, so old
78 scripts would fail to start wireless networking. Thus, etcupdate(3)
79 or mergemaster(8) run is required after kernel update, to update your
83 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
84 These configurations are now automatically interpreted as
85 'scrub fragment reassemble'.
88 Kernel-loadable modules for the random(4) device are back. To use
89 them, the kernel must have
92 options RANDOM_LOADABLE
94 kldload(8) can then be used to load random_fortuna.ko
95 or random_yarrow.ko. Please note that due to the indirect
96 function calls that the loadable modules need to provide,
97 the build-in variants will be slightly more efficient.
99 The random(4) kernel option RANDOM_DUMMY has been retired due to
100 unpopularity. It was not all that useful anyway.
103 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
104 Control over building the ELF Tool Chain tools is now provided by
105 the WITHOUT_TOOLCHAIN knob.
108 The polarity of Pulse Per Second (PPS) capture events with the
109 uart(4) driver has been corrected. Prior to this change the PPS
110 "assert" event corresponded to the trailing edge of a positive PPS
111 pulse and the "clear" event was the leading edge of the next pulse.
113 As the width of a PPS pulse in a typical GPS receiver is on the
114 order of 1 millisecond, most users will not notice any significant
115 difference with this change.
117 Anyone who has compensated for the historical polarity reversal by
118 configuring a negative offset equal to the pulse width will need to
119 remove that workaround.
122 The default group assigned to /dev/dri entries has been changed
123 from 'wheel' to 'video' with the id of '44'. If you want to have
124 access to the dri devices please add yourself to the video group
127 # pw groupmod video -m $USER
130 The menu.rc and loader.rc files will now be replaced during
131 upgrades. Please migrate local changes to menu.rc.local and
132 loader.rc.local instead.
135 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
136 strings and strip have been removed. The src.conf(5) knob
137 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
140 As ZFS requires more kernel stack pages than is the default on some
141 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
142 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
144 Please consider using 'options KSTACK_PAGES=X' where X is greater
145 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
148 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
149 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
150 default, i.e., they will not contain "::". For example, instead
151 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
152 to have a more specific match, such as different map entries for
153 IPv6:0:0 vs IPv6:0. This change requires that configuration
154 data (including maps, files, classes, custom ruleset, etc.) must
155 use the same format, so make certain such configuration data is
156 upgrading. As a very simple check search for patterns like
157 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
158 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
159 the cf option UseCompressedIPv6Addresses.
162 The default kernel entropy-processing algorithm is now
163 Fortuna, replacing Yarrow.
165 Assuming you have 'device random' in your kernel config
166 file, the configurations allow a kernel option to override
167 this default. You may choose *ONE* of:
169 options RANDOM_YARROW # Legacy /dev/random algorithm.
170 options RANDOM_DUMMY # Blocking-only driver.
172 If you have neither, you get Fortuna. For most people,
173 read no further, Fortuna will give a /dev/random that works
174 like it always used to, and the difference will be irrelevant.
176 If you remove 'device random', you get *NO* kernel-processed
177 entopy at all. This may be acceptable to folks building
178 embedded systems, but has complications. Carry on reading,
179 and it is assumed you know what you need.
181 *PLEASE* read random(4) and random(9) if you are in the
182 habit of tweeking kernel configs, and/or if you are a member
183 of the embedded community, wanting specific and not-usual
184 behaviour from your security subsystems.
186 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
187 random', you will NOT have a functioning /dev/random, and
188 many cryptographic features will not work, including SSH.
189 You may also find strange behaviour from the random(3) set
190 of library functions, in particular sranddev(3), srandomdev(3)
191 and arc4random(3). The reason for this is that the KERN_ARND
192 sysctl only returns entropy if it thinks it has some to
193 share, and with RANDOM_DUMMY or no 'device random' this
197 An additional fix for the issue described in the 20150614 sendmail
198 entry below has been been committed in revision 284717.
201 FreeBSD's old make (fmake) has been removed from the system. It is
202 available as the devel/fmake port or via pkg install fmake.
205 The fix for the issue described in the 20150614 sendmail entry
206 below has been been committed in revision 284436. The work
207 around described in that entry is no longer needed unless the
208 default setting is overridden by a confDH_PARAMETERS configuration
209 setting of '5' or pointing to a 512 bit DH parameter file.
212 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
213 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
214 and devel/kyua to version 0.20+ and adjust any calling code to work
215 with Kyuafile and kyua.
218 The import of openssl to address the FreeBSD-SA-15:10.openssl
219 security advisory includes a change which rejects handshakes
220 with DH parameters below 768 bits. sendmail releases prior
221 to 8.15.2 (not yet released), defaulted to a 512 bit
222 DH parameter setting for client connections. To work around
223 this interoperability, sendmail can be configured to use a
224 2048 bit DH parameter by:
226 1. Edit /etc/mail/`hostname`.mc
227 2. If a setting for confDH_PARAMETERS does not exist or
228 exists and is set to a string beginning with '5',
230 3. If a setting for confDH_PARAMETERS exists and is set to
231 a file path, create a new file with:
232 openssl dhparam -out /path/to/file 2048
233 4. Rebuild the .cf file:
234 cd /etc/mail/; make; make install
236 cd /etc/mail/; make restart
238 A sendmail patch is coming, at which time this file will be
242 Generation of legacy formatted entries have been disabled by default
243 in pwd_mkdb(8), as all base system consumers of the legacy formatted
244 entries were converted to use the new format by default when the new,
245 machine independent format have been added and supported since FreeBSD
248 Please see the pwd_mkdb(8) manual page for further details.
251 Clang and llvm have been upgraded to 3.6.1 release. Please see the
252 20141231 entry below for information about prerequisites and upgrading,
253 if you are not already using 3.5.0 or higher.
256 TI platform code switched to using vendor DTS files and this update
257 may break existing systems running on Beaglebone, Beaglebone Black,
260 - dtb files should be regenerated/reinstalled. Filenames are the
261 same but content is different now
262 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
263 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
264 addressing scheme is now pin 25 on /dev/gpioc3.
265 - Pandaboard: /etc/ttys should be updated, serial console device is
266 now /dev/ttyu2, not /dev/ttyu0
269 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
270 If you need the GNU extension from groff soelim(1), install groff
271 from package: pkg install groff, or via ports: textproc/groff.
274 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
275 defined in symlink(7); previously symlinks were silently ignored.
278 The const qualifier has been removed from iconv(3) to comply with
279 POSIX. The ports tree is aware of this from r384038 onwards.
282 Libraries specified by LIBADD in Makefiles must have a corresponding
283 DPADD_<lib> variable to ensure correct dependencies. This is now
284 enforced in src.libnames.mk.
287 From legacy ata(4) driver was removed support for SATA controllers
288 supported by more functional drivers ahci(4), siis(4) and mvs(4).
289 Kernel modules ataahci and ataadaptec were removed completely,
290 replaced by ahci and mvs modules respectively.
293 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
294 the 20141231 entry below for information about prerequisites and
295 upgrading, if you are not already using 3.5.0 or higher.
298 The 32-bit PowerPC kernel has been changed to a position-independent
299 executable. This can only be booted with a version of loader(8)
300 newer than January 31, 2015, so make sure to update both world and
301 kernel before rebooting.
304 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
305 but before r278950, the RNG was not seeded properly. Immediately
306 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
307 ssh keys or openssl keys) that were generated w/ a kernel from that
308 range. This does not affect programs that directly used /dev/random
309 or /dev/urandom. All userland uses of arc4random(3) are affected.
312 The autofs(4) ABI was changed in order to restore binary compatibility
313 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
317 The powerpc64 kernel has been changed to a position-independent
318 executable. This can only be booted with a new version of loader(8),
319 so make sure to update both world and kernel before rebooting.
322 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
323 only release, no new features have been added. Please see the 20141231
324 entry below for information about prerequisites and upgrading, if you
325 are not already using 3.5.0.
328 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
329 taken from the ELF Tool Chain project rather than GNU binutils. They
330 should be drop-in replacements, with the addition of arm64 support.
331 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
332 binutils tools, if necessary. See 20150805 for updated information.
335 The default Unbound configuration now enables remote control
336 using a local socket. Users who have already enabled the
337 local_unbound service should regenerate their configuration
338 by running "service local_unbound setup" as root.
341 The GNU texinfo and GNU info pages have been removed.
342 To be able to view GNU info pages please install texinfo from ports.
345 Clang, llvm and lldb have been upgraded to 3.5.0 release.
347 As of this release, a prerequisite for building clang, llvm and lldb is
348 a C++11 capable compiler and C++11 standard library. This means that to
349 be able to successfully build the cross-tools stage of buildworld, with
350 clang as the bootstrap compiler, your system compiler or cross compiler
351 should either be clang 3.3 or later, or gcc 4.8 or later, and your
352 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
355 On any standard FreeBSD 10.x or 11.x installation, where clang and
356 libc++ are on by default (that is, on x86 or arm), this should work out
359 On 9.x installations where clang is enabled by default, e.g. on x86 and
360 powerpc, libc++ will not be enabled by default, so libc++ should be
361 built (with clang) and installed first. If both clang and libc++ are
362 missing, build clang first, then use it to build libc++.
364 On 8.x and earlier installations, upgrade to 9.x first, and then follow
365 the instructions for 9.x above.
367 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
368 default, and do not build clang.
370 Many embedded systems are resource constrained, and will not be able to
371 build clang in a reasonable time, or in some cases at all. In those
372 cases, cross building bootable systems on amd64 is a workaround.
374 This new version of clang introduces a number of new warnings, of which
375 the following are most likely to appear:
379 This warns in two cases, for both C and C++:
380 * When the code is trying to take the absolute value of an unsigned
381 quantity, which is effectively a no-op, and almost never what was
382 intended. The code should be fixed, if at all possible. If you are
383 sure that the unsigned quantity can be safely cast to signed, without
384 loss of information or undefined behavior, you can add an explicit
385 cast, or disable the warning.
387 * When the code is trying to take an absolute value, but the called
388 abs() variant is for the wrong type, which can lead to truncation.
389 If you want to disable the warning instead of fixing the code, please
390 make sure that truncation will not occur, or it might lead to unwanted
393 -Wtautological-undefined-compare and
394 -Wundefined-bool-conversion
396 These warn when C++ code is trying to compare 'this' against NULL, while
397 'this' should never be NULL in well-defined C++ code. However, there is
398 some legacy (pre C++11) code out there, which actively abuses this
399 feature, which was less strictly defined in previous C++ versions.
401 Squid and openjdk do this, for example. The warning can be turned off
402 for C++98 and earlier, but compiling the code in C++11 mode might result
403 in unexpected behavior; for example, the parts of the program that are
404 unreachable could be optimized away.
407 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
408 kernel sources have been removed. The .h files remain, since some
409 utilities include them. This will need to be fixed later.
410 If "mount -t oldnfs ..." is attempted, it will fail.
411 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
412 the utilities will report errors.
415 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
416 directories to top level SUBDIR variable when their parent
417 directory is included in LOCAL_DIRS. Users with build systems with
418 such hierarchies and without SUBDIR entries in the parent
419 directory Makefiles should add them or add the directories to
423 faith(4) and faithd(8) have been removed from the base system. Faith
424 has been obsolete for a very long time.
427 vt(4), the new console driver, is enabled by default. It brings
428 support for Unicode and double-width characters, as well as
429 support for UEFI and integration with the KMS kernel video
432 You may need to update your console settings in /etc/rc.conf,
433 most probably the keymap. During boot, /etc/rc.d/syscons will
434 indicate what you need to do.
436 vt(4) still has issues and lacks some features compared to
437 syscons(4). See the wiki for up-to-date information:
438 https://wiki.freebsd.org/Newcons
440 If you want to keep using syscons(4), you can do so by adding
441 the following line to /boot/loader.conf:
445 pjdfstest has been integrated into kyua as an opt-in test suite.
446 Please see share/doc/pjdfstest/README for more details on how to
450 gperf has been removed from the base system for architectures
451 that use clang. Ports that require gperf will obtain it from the
455 pjdfstest has been moved from tools/regression/pjdfstest to
459 At svn r271982, The default linux compat kernel ABI has been adjusted
460 to 2.6.18 in support of the linux-c6 compat ports infrastructure
461 update. If you wish to continue using the linux-f10 compat ports,
462 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
463 encouraged to update their linux-compat packages to linux-c6 during
464 their next update cycle.
467 The ofwfb driver, used to provide a graphics console on PowerPC when
468 using vt(4), no longer allows mmap() of all physical memory. This
469 will prevent Xorg on PowerPC with some ATI graphics cards from
470 initializing properly unless x11-servers/xorg-server is updated to
474 The xdev targets have been converted to using TARGET and
475 TARGET_ARCH instead of XDEV and XDEV_ARCH.
478 The default unbound configuration has been modified to address
479 issues with reverse lookups on networks that use private
480 address ranges. If you use the local_unbound service, run
481 "service local_unbound setup" as root to regenerate your
482 configuration, then "service local_unbound reload" to load the
486 The GNU texinfo and GNU info pages are not built and installed
487 anymore, WITH_INFO knob has been added to allow to built and install
489 UPDATE: see 20150102 entry on texinfo's removal
492 The GNU readline library is now an INTERNALLIB - that is, it is
493 statically linked into consumers (GDB and variants) in the base
494 system, and the shared library is no longer installed. The
495 devel/readline port is available for third party software that
499 The Itanium architecture (ia64) has been removed from the list of
500 known architectures. This is the first step in the removal of the
504 Commit r268115 has added NFSv4.1 server support, merged from
505 projects/nfsv4.1-server. Since this includes changes to the
506 internal interfaces between the NFS related modules, a full
507 build of the kernel and modules will be necessary.
508 __FreeBSD_version has been bumped.
511 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
512 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
513 which differs from the behaviour controlled by this knob.)
516 Maximal length of the serial number in CTL was increased from 16 to
517 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
518 and ctld, need to be rebuilt to work with a new kernel.
521 The libatf-c and libatf-c++ major versions were downgraded to 0 and
522 1 respectively to match the upstream numbers. They were out of
523 sync because, when they were originally added to FreeBSD, the
524 upstream versions were not respected. These libraries are private
525 and not yet built by default, so renumbering them should be a
526 non-issue. However, unclean source trees will yield broken test
527 programs once the operator executes "make delete-old-libs" after a
530 Additionally, the atf-sh binary was made private by moving it into
531 /usr/libexec/. Already-built shell test programs will keep the
532 path to the old binary so they will break after "make delete-old"
535 If you are using WITH_TESTS=yes (not the default), wipe the object
536 tree and rebuild from scratch to prevent spurious test failures.
537 This is only needed once: the misnumbered libraries and misplaced
538 binaries have been added to OptionalObsoleteFiles.inc so they will
539 be removed during a clean upgrade.
542 Clang and llvm have been upgraded to 3.4.1 release.
545 We bogusly installed src.opts.mk in /usr/share/mk. This file should
546 be removed to avoid issues in the future (and has been added to
550 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
551 past, it affected all builds that used the bsd.*.mk files. The old
552 behavior was a bug, but people may have relied upon it. To get this
553 behavior back, you can .include /etc/src.conf from /etc/make.conf
554 (which is still global and isn't changed). This also changes the
555 behavior of incremental builds inside the tree of individual
556 directories. Set MAKESYSPATH to ".../share/mk" to do that.
557 Although this has survived make universe and some upgrade scenarios,
558 other upgrade scenarios may have broken. At least one form of
559 temporary breakage was fixed with MAKESYSPATH settings for buildworld
560 as well... In cases where MAKESYSPATH isn't working with this
561 setting, you'll need to set it to the full path to your tree.
563 One side effect of all this cleaning up is that bsd.compiler.mk
564 is no longer implicitly included by bsd.own.mk. If you wish to
565 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
569 The lindev device has been removed since /dev/full has been made a
570 standard device. __FreeBSD_version has been bumped.
573 The knob WITHOUT_VI was added to the base system, which controls
574 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
575 in order to reorder files share/termcap and didn't build ex(1) as a
576 build tool, so building/installing with WITH_VI is highly advised for
577 build hosts for older releases.
579 This issue has been fixed in stable/9 and stable/10 in r277022 and
580 r276991, respectively.
583 The YES_HESIOD knob has been removed. It has been obsolete for
584 a decade. Please move to using WITH_HESIOD instead or your builds
585 will silently lack HESIOD.
588 The uart(4) driver has been changed with respect to its handling
589 of the low-level console. Previously the uart(4) driver prevented
590 any process from changing the baudrate or the CLOCAL and HUPCL
591 control flags. By removing the restrictions, operators can make
592 changes to the serial console port without having to reboot.
593 However, when getty(8) is started on the serial device that is
594 associated with the low-level console, a misconfigured terminal
595 line in /etc/ttys will now have a real impact.
596 Before upgrading the kernel, make sure that /etc/ttys has the
597 serial console device configured as 3wire without baudrate to
598 preserve the previous behaviour. E.g:
599 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
602 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
603 to improve performance. To re-enable it, if needed, run rpcbind
604 with command line option -W.
607 Switched back to the GPL dtc compiler due to updates in the upstream
608 dts files not being supported by the BSDL dtc compiler. You will need
609 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
610 may result while building dtb files during a kernel build if you fail
611 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
614 Clang and llvm have been upgraded to 3.4 release.
617 The nve(4) driver has been removed. Please use the nfe(4) driver
618 for NVIDIA nForce MCP Ethernet adapters instead.
621 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
622 This could cause certain C++ applications using shared libraries built
623 against the previous version of libc++ to crash. The incompatibility
624 has now been fixed, but any C++ applications or shared libraries built
625 between r261283 and r261801 should be recompiled.
628 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
629 capability mode support. Please note that enabling the feature in
630 kernel is still highly recommended.
633 OpenSSH is now built with sandbox support, and will use sandbox as
634 the default privilege separation method. This requires Capsicum
635 capability mode support in kernel.
638 The libelf and libdwarf libraries have been updated to newer
639 versions from upstream. Shared library version numbers for
640 these two libraries were bumped. Any ports or binaries
641 requiring these two libraries should be recompiled.
642 __FreeBSD_version is bumped to 1100006.
645 If a Makefile in a tests/ directory was auto-generating a Kyuafile
646 instead of providing an explicit one, this would prevent such
647 Makefile from providing its own Kyuafile in the future during
648 NO_CLEAN builds. This has been fixed in the Makefiles but manual
649 intervention is needed to clean an objdir if you use NO_CLEAN:
650 # find /usr/obj -name Kyuafile | xargs rm -f
653 The behavior of gss_pseudo_random() for the krb5 mechanism
654 has changed, for applications requesting a longer random string
655 than produced by the underlying enctype's pseudo-random() function.
656 In particular, the random string produced from a session key of
657 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
658 be different at the 17th octet and later, after this change.
659 The counter used in the PRF+ construction is now encoded as a
660 big-endian integer in accordance with RFC 4402.
661 __FreeBSD_version is bumped to 1100004.
664 The WITHOUT_ATF build knob has been removed and its functionality
665 has been subsumed into the more generic WITHOUT_TESTS. If you were
666 using the former to disable the build of the ATF libraries, you
667 should change your settings to use the latter.
670 The default version of mtree is nmtree which is obtained from
671 NetBSD. The output is generally the same, but may vary
672 slightly. If you found you need identical output adding
673 "-F freebsd9" to the command line should do the trick. For the
674 time being, the old mtree is available as fmtree.
677 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
678 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
679 1.1.4_8 and verify bsdyml not linked in, before running "make
681 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
683 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
686 The stable/10 branch has been created in subversion from head
690 The rc.d/jail script has been updated to support jail(8)
691 configuration file. The "jail_<jname>_*" rc.conf(5) variables
692 for per-jail configuration are automatically converted to
693 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
694 This is transparently backward compatible. See below about some
695 incompatibilities and rc.conf(5) manual page for more details.
697 These variables are now deprecated in favor of jail(8) configuration
698 file. One can use "rc.d/jail config <jname>" command to generate
699 a jail(8) configuration file in /var/run/jail.<jname>.conf without
700 running the jail(8) utility. The default pathname of the
701 configuration file is /etc/jail.conf and can be specified by
702 using $jail_conf or $jail_<jname>_conf variables.
704 Please note that jail_devfs_ruleset accepts an integer at
705 this moment. Please consider to rewrite the ruleset name
709 BIND has been removed from the base system. If all you need
710 is a local resolver, simply enable and start the local_unbound
711 service instead. Otherwise, several versions of BIND are
712 available in the ports tree. The dns/bind99 port is one example.
714 With this change, nslookup(1) and dig(1) are no longer in the base
715 system. Users should instead use host(1) and drill(1) which are
716 in the base system. Alternatively, nslookup and dig can
717 be obtained by installing the dns/bind-tools port.
720 With the addition of unbound(8), a new unbound user is now
721 required during installworld. "mergemaster -p" can be used to
722 add the user prior to installworld, as documented in the handbook.
725 OpenSSH is now built with DNSSEC support, and will by default
726 silently trust signed SSHFP records. This can be controlled with
727 the VerifyHostKeyDNS client configuration setting. DNSSEC support
728 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
731 The GNU Compiler Collection and C++ standard library (libstdc++)
732 are no longer built by default on platforms where clang is the system
733 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
737 The PROCDESC kernel option is now part of the GENERIC kernel
738 configuration and is required for the rwhod(8) to work.
739 If you are using custom kernel configuration, you should include
743 The API and ABI related to the Capsicum framework was modified
744 in backward incompatible way. The userland libraries and programs
745 have to be recompiled to work with the new kernel. This includes the
746 following libraries and programs, but the whole buildworld is
747 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
748 kdump, procstat, rwho, rwhod, uniq.
751 AES-NI intrinsic support has been added to gcc. The AES-NI module
752 has been updated to use this support. A new gcc is required to build
753 the aesni module on both i386 and amd64.
756 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
757 Thus "device padlock_rng" and "device rdrand_rng" should be
758 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
761 WITH_ICONV has been split into two feature sets. WITH_ICONV now
762 enables just the iconv* functionality and is now on by default.
763 WITH_LIBICONV_COMPAT enables the libiconv api and link time
764 compatability. Set WITHOUT_ICONV to build the old way.
765 If you have been using WITH_ICONV before, you will very likely
766 need to turn on WITH_LIBICONV_COMPAT.
769 INVARIANTS option now enables DEBUG for code with OpenSolaris and
770 Illumos origin, including ZFS. If you have INVARIANTS in your
771 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
773 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
774 locks if WITNESS option was set. Because that generated a lot of
775 witness(9) reports and all of them were believed to be false
776 positives, this is no longer done. New option OPENSOLARIS_WITNESS
777 can be used to achieve the previous behavior.
780 Timer values in IPv6 data structures now use time_uptime instead
781 of time_second. Although this is not a user-visible functional
782 change, userland utilities which directly use them---ndp(8),
783 rtadvd(8), and rtsold(8) in the base system---need to be updated
787 find -delete can now delete the pathnames given as arguments,
788 instead of only files found below them or if the pathname did
789 not contain any slashes. Formerly, the following error message
792 find: -delete: <path>: relative path potentially not safe
794 Deleting the pathnames given as arguments can be prevented
795 without error messages using -mindepth 1 or by changing
796 directory and passing "." as argument to find. This works in the
797 old as well as the new version of find.
800 Behavior of devfs rules path matching has been changed.
801 Pattern is now always matched against fully qualified devfs
802 path and slash characters must be explicitly matched by
803 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
804 subdirectories must be reviewed.
807 The default ARM ABI has changed to the ARM EABI. The old ABI is
808 incompatible with the ARM EABI and all programs and modules will
809 need to be rebuilt to work with a new kernel.
811 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
813 NOTE: Support for the old ABI will be removed in the future and
814 users are advised to upgrade.
817 pkg_install has been disconnected from the build if you really need it
818 you should add WITH_PKGTOOLS in your src.conf(5).
821 Most of network statistics structures were changed to be able
822 keep 64-bits counters. Thus all tools, that work with networking
823 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
826 Fix targets that run multiple make's to use && rather than ;
827 so that subsequent steps depend on success of previous.
829 NOTE: if building 'universe' with -j* on stable/8 or stable/9
830 it would be better to start the build using bmake, to avoid
831 overloading the machine.
834 Fix a bug that allowed a tracing process (e.g. gdb) to write
835 to a memory-mapped file in the traced process's address space
836 even if neither the traced process nor the tracing process had
837 write access to that file.
840 CVS has been removed from the base system. An exact copy
841 of the code is available from the devel/cvs port.
844 Some people report the following error after the switch to bmake:
846 make: illegal option -- J
847 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
849 *** [buildworld] Error code 2
851 this likely due to an old instance of make in
852 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
853 which src/Makefile will use that blindly, if it exists, so if
854 you see the above error:
856 rm -rf `make -V MAKEPATH`
861 Use bmake by default.
862 Whereas before one could choose to build with bmake via
863 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
864 make. The goal is to remove these knobs for 10-RELEASE.
866 It is worth noting that bmake (like gmake) treats the command
867 line as the unit of failure, rather than statements within the
868 command line. Thus '(cd some/where && dosomething)' is safer
869 than 'cd some/where; dosomething'. The '()' allows consistent
870 behavior in parallel build.
873 Fix a bug that allows NFS clients to issue READDIR on files.
876 The WITHOUT_IDEA option has been removed because
877 the IDEA patent expired.
880 The sysctl which controls TRIM support under ZFS has been renamed
881 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
885 The mergemaster command now uses the default MAKEOBJDIRPREFIX
886 rather than creating it's own in the temporary directory in
887 order allow access to bootstrapped versions of tools such as
888 install and mtree. When upgrading from version of FreeBSD where
889 the install command does not support -l, you will need to
890 install a new mergemaster command if mergemaster -p is required.
891 This can be accomplished with the command (cd src/usr.sbin/mergemaster
895 Legacy ATA stack, disabled and replaced by new CAM-based one since
896 FreeBSD 9.0, completely removed from the sources. Kernel modules
897 atadisk and atapi*, user-level tools atacontrol and burncd are
898 removed. Kernel option `options ATA_CAM` is now permanently enabled
902 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
903 and socketpair(2). Software, in particular Kerberos, may
904 automatically detect and use these during building. The resulting
905 binaries will not work on older kernels.
908 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
909 information, see the respective 20130304 entry).
912 Recent commits to callout(9) changed the size of struct callout,
913 so the KBI is probably heavily disturbed. Also, some functions
914 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
915 by macros. Every kernel module using it won't load, so rebuild
918 The ctl device has been re-enabled in GENERIC for i386 and amd64,
919 but does not initialize by default (because of the new CTL_DISABLE
920 option) to save memory. To re-enable it, remove the CTL_DISABLE
921 option from the kernel config file or set kern.cam.ctl.disable=0
922 in /boot/loader.conf.
925 The ctl device has been disabled in GENERIC for i386 and amd64.
926 This was done due to the extra memory being allocated at system
927 initialisation time by the ctl driver which was only used if
928 a CAM target device was created. This makes a FreeBSD system
929 unusable on 128MB or less of RAM.
932 A new compression method (lz4) has been merged to -HEAD. Please
933 refer to zpool-features(7) for more information.
935 Please refer to the "ZFS notes" section of this file for information
936 on upgrading boot ZFS pools.
939 A BSD-licensed patch(1) variant has been added and is installed
940 as bsdpatch, being the GNU version the default patch.
941 To inverse the logic and use the BSD-licensed one as default,
942 while having the GNU version installed as gnupatch, rebuild
943 and install world with the WITH_BSD_PATCH knob set.
946 Due to the use of the new -l option to install(1) during build
947 and install, you must take care not to directly set the INSTALL
948 make variable in your /etc/make.conf, /etc/src.conf, or on the
949 command line. If you wish to use the -C flag for all installs
950 you may be able to add INSTALL+=-C to /etc/make.conf or
954 The install(1) option -M has changed meaning and now takes an
955 argument that is a file or path to append logs to. In the
956 unlikely event that -M was the last option on the command line
957 and the command line contained at least two files and a target
958 directory the first file will have logs appended to it. The -M
959 option served little practical purpose in the last decade so its
960 use is expected to be extremely rare.
963 After switching to Clang as the default compiler some users of ZFS
964 on i386 systems started to experience stack overflow kernel panics.
965 Please consider using 'options KSTACK_PAGES=4' in such configurations.
968 GEOM_LABEL now mangles label names read from file system metadata.
969 Mangling affect labels containing spaces, non-printable characters,
970 '%' or '"'. Device names in /etc/fstab and other places may need to
974 By default, only the 10 most recent kernel dumps will be saved. To
975 restore the previous behaviour (no limit on the number of kernel dumps
976 stored in the dump directory) add the following line to /etc/rc.conf:
981 With the addition of auditdistd(8), a new auditdistd user is now
982 required during installworld. "mergemaster -p" can be used to
983 add the user prior to installworld, as documented in the handbook.
986 The sin6_scope_id member variable in struct sockaddr_in6 is now
987 filled by the kernel before passing the structure to the userland via
988 sysctl or routing socket. This means the KAME-specific embedded scope
989 id in sin6_addr.s6_addr[2] is always cleared in userland application.
990 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
991 __FreeBSD_version is bumped to 1000025.
994 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
995 This means that the world and kernel will be compiled with clang
996 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
997 and /usr/bin/cpp. To disable this behavior and revert to building
998 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
999 of current may need to bootstrap WITHOUT_CLANG first if the clang
1000 build fails (its compatibility window doesn't extend to the 9 stable
1004 The IPFIREWALL_FORWARD kernel option has been removed. Its
1005 functionality now turned on by default.
1008 The ZERO_COPY_SOCKET kernel option has been removed and
1009 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1010 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1011 mechanism which is not safe and may result in kernel crashes.
1012 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1013 driver supports disposeable external page sized mbuf storage.
1014 Proper replacements for both zero-copy mechanisms are under
1015 consideration and will eventually lead to complete removal
1016 of the two kernel options.
1019 The IPv4 network stack has been converted to network byte
1020 order. The following modules need to be recompiled together
1021 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1022 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1025 Support for non-MPSAFE filesystems was removed from VFS. The
1026 VFS_VERSION was bumped, all filesystem modules shall be
1030 All the non-MPSAFE filesystems have been disconnected from
1031 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1032 portalfs, smbfs, xfs.
1035 The interface cloning API and ABI has changed. The following
1036 modules need to be recompiled together with kernel:
1037 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1038 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1039 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1042 The sdhci driver was split in two parts: sdhci (generic SD Host
1043 Controller logic) and sdhci_pci (actual hardware driver).
1044 No kernel config modifications are required, but if you
1045 load sdhc as a module you must switch to sdhci_pci instead.
1048 Import the FUSE kernel and userland support into base system.
1051 The GNU sort(1) program has been removed since the BSD-licensed
1052 sort(1) has been the default for quite some time and no serious
1053 problems have been reported. The corresponding WITH_GNU_SORT
1057 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1058 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1062 The net80211(4) ABI has been changed to allow for improved driver
1063 PS-POLL and power-save support. All wireless drivers need to be
1064 recompiled to work with the new kernel.
1067 The random(4) support for the VIA hardware random number
1068 generator (`PADLOCK') is no longer enabled unconditionally.
1069 Add the padlock_rng device in the custom kernel config if
1070 needed. The GENERIC kernels on i386 and amd64 do include the
1071 device, so the change only affects the custom kernel
1075 The pf(4) packet filter ABI has been changed. pfctl(8) and
1076 snmp_pf module need to be recompiled to work with new kernel.
1079 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1080 to -HEAD. Pools that have empty_bpobj in active state can not be
1081 imported read-write with ZFS implementations that do not support
1082 this feature. For more information read the zpool-features(5)
1086 The sparc64 ZFS loader has been changed to no longer try to auto-
1087 detect ZFS providers based on diskN aliases but now requires these
1088 to be explicitly listed in the OFW boot-device environment variable.
1091 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1092 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1093 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1096 The following sysctls and tunables have been renamed for consistency
1097 with other variables:
1098 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1099 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1102 The sort utility has been replaced with BSD sort. For now, GNU sort
1103 is also available as "gnusort" or the default can be set back to
1104 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1105 installed as "bsdsort".
1108 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1109 Starting with this version the old system of ZFS pool versioning
1110 is superseded by "feature flags". This concept enables forward
1111 compatibility against certain future changes in functionality of ZFS
1112 pools. The first read-only compatible "feature flag" for ZFS pools
1113 is named "com.delphix:async_destroy". For more information
1114 read the new zpool-features(5) manual page.
1115 Please refer to the "ZFS notes" section of this file for information
1116 on upgrading boot ZFS pools.
1119 The malloc(3) implementation embedded in libc now uses sources imported
1120 as contrib/jemalloc. The most disruptive API change is to
1121 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1122 delete it prior to installworld, and optionally re-create it using the
1123 new format after rebooting. See malloc.conf(5) for details
1124 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1128 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1129 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1130 now spelled mips. This is to aid compatibility with third-party
1131 software that expects this naming scheme in uname(3). Little-endian
1132 settings are unchanged. If you are updating a big-endian mips64 machine
1133 from before this change, you may need to set MACHINE_ARCH=mips64 in
1134 your environment before the new build system will recognize your machine.
1137 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1141 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1142 nullfs(5) did not pass through all behaviours to the underlying layer,
1143 as a result if we bound to a socket on the lower layer we could connect
1144 only to the lower path; if we bound to the upper layer we could connect
1145 only to the upper path. The new behavior is one can connect to both the
1146 lower and the upper paths regardless what layer path one binds to.
1149 The getifaddrs upgrade path broken with 20111215 has been restored.
1150 If you have upgraded in between 20111215 and 20120209 you need to
1151 recompile libc again with your kernel. You still need to recompile
1152 world to be able to configure CARP but this restriction already
1153 comes from 20111215.
1156 The set_rcvar() function has been removed from /etc/rc.subr. All
1157 base and ports rc.d scripts have been updated, so if you have a
1158 port installed with a script in /usr/local/etc/rc.d you can either
1159 hand-edit the rcvar= line, or reinstall the port.
1161 An easy way to handle the mass-update of /etc/rc.d:
1162 rm /etc/rc.d/* && mergemaster -i
1165 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1166 on the current CPU and prevents other threads from running.
1167 This behavior can be reverted using the kern.stop_scheduler_on_panic
1169 The new behavior can be incompatible with kern.sync_on_panic.
1172 The carp(4) facility has been changed significantly. Configuration
1173 of the CARP protocol via ifconfig(8) has changed, as well as format
1174 of CARP events submitted to devd(8) has changed. See manual pages
1175 for more information. The arpbalance feature of carp(4) is currently
1176 not supported anymore.
1178 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1179 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1180 need to be recompiled.
1183 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1187 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1188 explicitely support non-MPSAFE filesystems.
1189 It is on by default for all supported platform at this present
1193 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1194 i386 and pc98 GENERIC kernel configuration files.
1197 sysinstall has been removed
1200 The stable/9 branch created in subversion. This corresponds to the
1201 RELENG_9 branch in CVS.
1207 Avoid using make -j when upgrading. While generally safe, there are
1208 sometimes problems using -j to upgrade. If your upgrade fails with
1209 -j, please try again without -j. From time to time in the past there
1210 have been problems using -j with buildworld and/or installworld. This
1211 is especially true when upgrading between "distant" versions (eg one
1212 that cross a major release boundary or several minor releases, or when
1213 several months have passed on the -current branch).
1215 Sometimes, obscure build problems are the result of environment
1216 poisoning. This can happen because the make utility reads its
1217 environment when searching for values for global variables. To run
1218 your build attempts in an "environmental clean room", prefix all make
1219 commands with 'env -i '. See the env(1) manual page for more details.
1221 When upgrading from one major version to another it is generally best
1222 to upgrade to the latest code in the currently installed branch first,
1223 then do an upgrade to the new branch. This is the best-tested upgrade
1224 path, and has the highest probability of being successful. Please try
1225 this approach before reporting problems with a major version upgrade.
1227 When upgrading a live system, having a root shell around before
1228 installing anything can help undo problems. Not having a root shell
1229 around can lead to problems if pam has changed too much from your
1230 starting point to allow continued authentication after the upgrade.
1232 This file should be read as a log of events. When a later event changes
1233 information of a prior event, the prior event should not be deleted.
1234 Instead, a pointer to the entry with the new information should be
1235 placed in the old entry. Readers of this file should also sanity check
1236 older entries before relying on them blindly. Authors of new entries
1237 should write them with this in mind.
1241 When upgrading the boot ZFS pool to a new version, always follow
1244 1.) recompile and reinstall the ZFS boot loader and boot block
1245 (this is part of "make buildworld" and "make installworld")
1247 2.) update the ZFS boot block on your boot drive
1249 The following example updates the ZFS boot block on the first
1250 partition (freebsd-boot) of a GPT partitioned drive ada0:
1251 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1253 Non-boot pools do not need these updates.
1257 If you are updating from a prior version of FreeBSD (even one just
1258 a few days old), you should follow this procedure. It is the most
1259 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1261 make kernel-toolchain
1262 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1263 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1265 To test a kernel once
1266 ---------------------
1267 If you just want to boot a kernel once (because you are not sure
1268 if it works, or if you want to boot a known bad kernel to provide
1269 debugging information) run
1270 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1271 nextboot -k testkernel
1273 To just build a kernel when you know that it won't mess you up
1274 --------------------------------------------------------------
1275 This assumes you are already running a CURRENT system. Replace
1276 ${arch} with the architecture of your machine (e.g. "i386",
1277 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1279 cd src/sys/${arch}/conf
1280 config KERNEL_NAME_HERE
1281 cd ../compile/KERNEL_NAME_HERE
1286 If this fails, go to the "To build a kernel" section.
1288 To rebuild everything and install it on the current system.
1289 -----------------------------------------------------------
1290 # Note: sometimes if you are running current you gotta do more than
1291 # is listed here if you are upgrading from a really old current.
1293 <make sure you have good level 0 dumps>
1295 make kernel KERNCONF=YOUR_KERNEL_HERE
1297 <reboot in single user> [3]
1304 To cross-install current onto a separate partition
1305 --------------------------------------------------
1306 # In this approach we use a separate partition to hold
1307 # current's root, 'usr', and 'var' directories. A partition
1308 # holding "/", "/usr" and "/var" should be about 2GB in
1311 <make sure you have good level 0 dumps>
1314 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1315 <maybe newfs current's root partition>
1316 <mount current's root partition on directory ${CURRENT_ROOT}>
1317 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1318 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1319 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1320 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1321 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1322 <reboot into current>
1323 <do a "native" rebuild/install as described in the previous section>
1324 <maybe install compatibility libraries from ports/misc/compat*>
1328 To upgrade in-place from stable to current
1329 ----------------------------------------------
1330 <make sure you have good level 0 dumps>
1332 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1334 <reboot in single user> [3]
1341 Make sure that you've read the UPDATING file to understand the
1342 tweaks to various things you need. At this point in the life
1343 cycle of current, things change often and you are on your own
1344 to cope. The defaults can also change, so please read ALL of
1345 the UPDATING entries.
1347 Also, if you are tracking -current, you must be subscribed to
1348 freebsd-current@freebsd.org. Make sure that before you update
1349 your sources that you have read and understood all the recent
1350 messages there. If in doubt, please track -stable which has
1351 much fewer pitfalls.
1353 [1] If you have third party modules, such as vmware, you
1354 should disable them at this point so they don't crash your
1357 [3] From the bootblocks, boot -s, and then do
1362 adjkerntz -i # if CMOS is wall time
1363 Also, when doing a major release upgrade, it is required that
1364 you boot into single user mode to do the installworld.
1366 [4] Note: This step is non-optional. Failure to do this step
1367 can result in a significant reduction in the functionality of the
1368 system. Attempting to do it by hand is not recommended and those
1369 that pursue this avenue should read this file carefully, as well
1370 as the archives of freebsd-current and freebsd-hackers mailing lists
1371 for potential gotchas. The -U option is also useful to consider.
1372 See mergemaster(8) for more information.
1374 [5] Usually this step is a noop. However, from time to time
1375 you may need to do this if you get unknown user in the following
1376 step. It never hurts to do it all the time. You may need to
1377 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1378 install) after the buildworld before this step if you last updated
1379 from current before 20130425 or from -stable before 20130430.
1381 [6] This only deletes old files and directories. Old libraries
1382 can be deleted by "make delete-old-libs", but you have to make
1383 sure that no program is using those libraries anymore.
1385 [8] In order to have a kernel that can run the 4.x binaries needed to
1386 do an installworld, you must include the COMPAT_FREEBSD4 option in
1387 your kernel. Failure to do so may leave you with a system that is
1388 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1389 required to run the 5.x binaries on more recent kernels. And so on
1390 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1392 Make sure that you merge any new devices from GENERIC since the
1393 last time you updated your kernel config file.
1395 [9] When checking out sources, you must include the -P flag to have
1396 cvs prune empty directories.
1398 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1399 "?=" instead of the "=" assignment operator, so that buildworld can
1400 override the CPUTYPE if it needs to.
1402 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1403 not on the command line, or in /etc/make.conf. buildworld will
1404 warn if it is improperly defined.
1407 This file contains a list, in reverse chronological order, of major
1408 breakages in tracking -current. It is not guaranteed to be a complete
1409 list of such breakages, and only contains entries since September 23, 2011.
1410 If you need to see UPDATING entries from before that date, you will need
1411 to fetch an UPDATING file from an older FreeBSD release.
1413 Copyright information:
1415 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1417 Redistribution, publication, translation and use, with or without
1418 modification, in full or in part, in any form or format of this
1419 document are permitted without further permission from the author.
1421 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1422 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1423 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1424 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1425 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1426 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1427 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1428 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1429 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1430 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1431 POSSIBILITY OF SUCH DAMAGE.
1433 Contact Warner Losh if you have any questions about your use of