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