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