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 The menu.rc and loader.rc files will now be replaced during
36 upgrades. Please migrate local changes to menu.rc.local and
37 loader.rc.local instead.
40 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
41 strings and strip have been removed. The src.conf(5) knob
42 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
45 As ZFS requires more kernel stack pages than is the default on some
46 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
47 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
49 Please consider using 'options KSTACK_PAGES=X' where X is greater
50 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
53 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
54 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
55 default, i.e., they will not contain "::". For example, instead
56 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
57 to have a more specific match, such as different map entries for
58 IPv6:0:0 vs IPv6:0. This change requires that configuration
59 data (including maps, files, classes, custom ruleset, etc.) must
60 use the same format, so make certain such configuration data is
61 upgrading. As a very simple check search for patterns like
62 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
63 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
64 the cf option UseCompressedIPv6Addresses.
67 The default kernel entropy-processing algorithm is now
68 Fortuna, replacing Yarrow.
70 Assuming you have 'device random' in your kernel config
71 file, the configurations allow a kernel option to override
72 this default. You may choose *ONE* of:
74 options RANDOM_YARROW # Legacy /dev/random algorithm.
75 options RANDOM_DUMMY # Blocking-only driver.
77 If you have neither, you get Fortuna. For most people,
78 read no further, Fortuna will give a /dev/random that works
79 like it always used to, and the difference will be irrelevant.
81 If you remove 'device random', you get *NO* kernel-processed
82 entopy at all. This may be acceptable to folks building
83 embedded systems, but has complications. Carry on reading,
84 and it is assumed you know what you need.
86 *PLEASE* read random(4) and random(9) if you are in the
87 habit of tweeking kernel configs, and/or if you are a member
88 of the embedded community, wanting specific and not-usual
89 behaviour from your security subsystems.
91 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
92 random', you will NOT have a functioning /dev/random, and
93 many cryptographic features will not work, including SSH.
94 You may also find strange behaviour from the random(3) set
95 of library functions, in particular sranddev(3), srandomdev(3)
96 and arc4random(3). The reason for this is that the KERN_ARND
97 sysctl only returns entropy if it thinks it has some to
98 share, and with RANDOM_DUMMY or no 'device random' this
102 An additional fix for the issue described in the 20150614 sendmail
103 entry below has been been committed in revision 284717.
106 FreeBSD's old make (fmake) has been removed from the system. It is
107 available as the devel/fmake port or via pkg install fmake.
110 The fix for the issue described in the 20150614 sendmail entry
111 below has been been committed in revision 284436. The work
112 around described in that entry is no longer needed unless the
113 default setting is overridden by a confDH_PARAMETERS configuration
114 setting of '5' or pointing to a 512 bit DH parameter file.
117 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
118 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
119 and devel/kyua to version 0.20+ and adjust any calling code to work
120 with Kyuafile and kyua.
123 The import of openssl to address the FreeBSD-SA-15:10.openssl
124 security advisory includes a change which rejects handshakes
125 with DH parameters below 768 bits. sendmail releases prior
126 to 8.15.2 (not yet released), defaulted to a 512 bit
127 DH parameter setting for client connections. To work around
128 this interoperability, sendmail can be configured to use a
129 2048 bit DH parameter by:
131 1. Edit /etc/mail/`hostname`.mc
132 2. If a setting for confDH_PARAMETERS does not exist or
133 exists and is set to a string beginning with '5',
135 3. If a setting for confDH_PARAMETERS exists and is set to
136 a file path, create a new file with:
137 openssl dhparam -out /path/to/file 2048
138 4. Rebuild the .cf file:
139 cd /etc/mail/; make; make install
141 cd /etc/mail/; make restart
143 A sendmail patch is coming, at which time this file will be
147 Generation of legacy formatted entries have been disabled by default
148 in pwd_mkdb(8), as all base system consumers of the legacy formatted
149 entries were converted to use the new format by default when the new,
150 machine independent format have been added and supported since FreeBSD
153 Please see the pwd_mkdb(8) manual page for further details.
156 Clang and llvm have been upgraded to 3.6.1 release. Please see the
157 20141231 entry below for information about prerequisites and upgrading,
158 if you are not already using 3.5.0 or higher.
161 TI platform code switched to using vendor DTS files and this update
162 may break existing systems running on Beaglebone, Beaglebone Black,
165 - dtb files should be regenerated/reinstalled. Filenames are the
166 same but content is different now
167 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
168 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
169 addressing scheme is now pin 25 on /dev/gpioc3.
170 - Pandaboard: /etc/ttys should be updated, serial console device is
171 now /dev/ttyu2, not /dev/ttyu0
174 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
175 If you need the GNU extension from groff soelim(1), install groff
176 from package: pkg install groff, or via ports: textproc/groff.
179 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
180 defined in symlink(7); previously symlinks were silently ignored.
183 The const qualifier has been removed from iconv(3) to comply with
184 POSIX. The ports tree is aware of this from r384038 onwards.
187 Libraries specified by LIBADD in Makefiles must have a corresponding
188 DPADD_<lib> variable to ensure correct dependencies. This is now
189 enforced in src.libnames.mk.
192 From legacy ata(4) driver was removed support for SATA controllers
193 supported by more functional drivers ahci(4), siis(4) and mvs(4).
194 Kernel modules ataahci and ataadaptec were removed completely,
195 replaced by ahci and mvs modules respectively.
198 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
199 the 20141231 entry below for information about prerequisites and
200 upgrading, if you are not already using 3.5.0 or higher.
203 The 32-bit PowerPC kernel has been changed to a position-independent
204 executable. This can only be booted with a version of loader(8)
205 newer than January 31, 2015, so make sure to update both world and
206 kernel before rebooting.
209 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
210 but before r278950, the RNG was not seeded properly. Immediately
211 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
212 ssh keys or openssl keys) that were generated w/ a kernel from that
213 range. This does not affect programs that directly used /dev/random
214 or /dev/urandom. All userland uses of arc4random(3) are affected.
217 The autofs(4) ABI was changed in order to restore binary compatibility
218 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
222 The powerpc64 kernel has been changed to a position-independent
223 executable. This can only be booted with a new version of loader(8),
224 so make sure to update both world and kernel before rebooting.
227 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
228 only release, no new features have been added. Please see the 20141231
229 entry below for information about prerequisites and upgrading, if you
230 are not already using 3.5.0.
233 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
234 taken from the ELF Tool Chain project rather than GNU binutils. They
235 should be drop-in replacements, with the addition of arm64 support.
236 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
237 binutils tools, if necessary. See 20150805 for updated information.
240 The default Unbound configuration now enables remote control
241 using a local socket. Users who have already enabled the
242 local_unbound service should regenerate their configuration
243 by running "service local_unbound setup" as root.
246 The GNU texinfo and GNU info pages have been removed.
247 To be able to view GNU info pages please install texinfo from ports.
250 Clang, llvm and lldb have been upgraded to 3.5.0 release.
252 As of this release, a prerequisite for building clang, llvm and lldb is
253 a C++11 capable compiler and C++11 standard library. This means that to
254 be able to successfully build the cross-tools stage of buildworld, with
255 clang as the bootstrap compiler, your system compiler or cross compiler
256 should either be clang 3.3 or later, or gcc 4.8 or later, and your
257 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
260 On any standard FreeBSD 10.x or 11.x installation, where clang and
261 libc++ are on by default (that is, on x86 or arm), this should work out
264 On 9.x installations where clang is enabled by default, e.g. on x86 and
265 powerpc, libc++ will not be enabled by default, so libc++ should be
266 built (with clang) and installed first. If both clang and libc++ are
267 missing, build clang first, then use it to build libc++.
269 On 8.x and earlier installations, upgrade to 9.x first, and then follow
270 the instructions for 9.x above.
272 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
273 default, and do not build clang.
275 Many embedded systems are resource constrained, and will not be able to
276 build clang in a reasonable time, or in some cases at all. In those
277 cases, cross building bootable systems on amd64 is a workaround.
279 This new version of clang introduces a number of new warnings, of which
280 the following are most likely to appear:
284 This warns in two cases, for both C and C++:
285 * When the code is trying to take the absolute value of an unsigned
286 quantity, which is effectively a no-op, and almost never what was
287 intended. The code should be fixed, if at all possible. If you are
288 sure that the unsigned quantity can be safely cast to signed, without
289 loss of information or undefined behavior, you can add an explicit
290 cast, or disable the warning.
292 * When the code is trying to take an absolute value, but the called
293 abs() variant is for the wrong type, which can lead to truncation.
294 If you want to disable the warning instead of fixing the code, please
295 make sure that truncation will not occur, or it might lead to unwanted
298 -Wtautological-undefined-compare and
299 -Wundefined-bool-conversion
301 These warn when C++ code is trying to compare 'this' against NULL, while
302 'this' should never be NULL in well-defined C++ code. However, there is
303 some legacy (pre C++11) code out there, which actively abuses this
304 feature, which was less strictly defined in previous C++ versions.
306 Squid and openjdk do this, for example. The warning can be turned off
307 for C++98 and earlier, but compiling the code in C++11 mode might result
308 in unexpected behavior; for example, the parts of the program that are
309 unreachable could be optimized away.
312 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
313 kernel sources have been removed. The .h files remain, since some
314 utilities include them. This will need to be fixed later.
315 If "mount -t oldnfs ..." is attempted, it will fail.
316 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
317 the utilities will report errors.
320 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
321 directories to top level SUBDIR variable when their parent
322 directory is included in LOCAL_DIRS. Users with build systems with
323 such hierarchies and without SUBDIR entries in the parent
324 directory Makefiles should add them or add the directories to
328 faith(4) and faithd(8) have been removed from the base system. Faith
329 has been obsolete for a very long time.
332 vt(4), the new console driver, is enabled by default. It brings
333 support for Unicode and double-width characters, as well as
334 support for UEFI and integration with the KMS kernel video
337 You may need to update your console settings in /etc/rc.conf,
338 most probably the keymap. During boot, /etc/rc.d/syscons will
339 indicate what you need to do.
341 vt(4) still has issues and lacks some features compared to
342 syscons(4). See the wiki for up-to-date information:
343 https://wiki.freebsd.org/Newcons
345 If you want to keep using syscons(4), you can do so by adding
346 the following line to /boot/loader.conf:
350 pjdfstest has been integrated into kyua as an opt-in test suite.
351 Please see share/doc/pjdfstest/README for more details on how to
355 gperf has been removed from the base system for architectures
356 that use clang. Ports that require gperf will obtain it from the
360 pjdfstest has been moved from tools/regression/pjdfstest to
364 At svn r271982, The default linux compat kernel ABI has been adjusted
365 to 2.6.18 in support of the linux-c6 compat ports infrastructure
366 update. If you wish to continue using the linux-f10 compat ports,
367 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
368 encouraged to update their linux-compat packages to linux-c6 during
369 their next update cycle.
372 The ofwfb driver, used to provide a graphics console on PowerPC when
373 using vt(4), no longer allows mmap() of all physical memory. This
374 will prevent Xorg on PowerPC with some ATI graphics cards from
375 initializing properly unless x11-servers/xorg-server is updated to
379 The xdev targets have been converted to using TARGET and
380 TARGET_ARCH instead of XDEV and XDEV_ARCH.
383 The default unbound configuration has been modified to address
384 issues with reverse lookups on networks that use private
385 address ranges. If you use the local_unbound service, run
386 "service local_unbound setup" as root to regenerate your
387 configuration, then "service local_unbound reload" to load the
391 The GNU texinfo and GNU info pages are not built and installed
392 anymore, WITH_INFO knob has been added to allow to built and install
394 UPDATE: see 20150102 entry on texinfo's removal
397 The GNU readline library is now an INTERNALLIB - that is, it is
398 statically linked into consumers (GDB and variants) in the base
399 system, and the shared library is no longer installed. The
400 devel/readline port is available for third party software that
404 The Itanium architecture (ia64) has been removed from the list of
405 known architectures. This is the first step in the removal of the
409 Commit r268115 has added NFSv4.1 server support, merged from
410 projects/nfsv4.1-server. Since this includes changes to the
411 internal interfaces between the NFS related modules, a full
412 build of the kernel and modules will be necessary.
413 __FreeBSD_version has been bumped.
416 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
417 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
418 which differs from the behaviour controlled by this knob.)
421 Maximal length of the serial number in CTL was increased from 16 to
422 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
423 and ctld, need to be rebuilt to work with a new kernel.
426 The libatf-c and libatf-c++ major versions were downgraded to 0 and
427 1 respectively to match the upstream numbers. They were out of
428 sync because, when they were originally added to FreeBSD, the
429 upstream versions were not respected. These libraries are private
430 and not yet built by default, so renumbering them should be a
431 non-issue. However, unclean source trees will yield broken test
432 programs once the operator executes "make delete-old-libs" after a
435 Additionally, the atf-sh binary was made private by moving it into
436 /usr/libexec/. Already-built shell test programs will keep the
437 path to the old binary so they will break after "make delete-old"
440 If you are using WITH_TESTS=yes (not the default), wipe the object
441 tree and rebuild from scratch to prevent spurious test failures.
442 This is only needed once: the misnumbered libraries and misplaced
443 binaries have been added to OptionalObsoleteFiles.inc so they will
444 be removed during a clean upgrade.
447 Clang and llvm have been upgraded to 3.4.1 release.
450 We bogusly installed src.opts.mk in /usr/share/mk. This file should
451 be removed to avoid issues in the future (and has been added to
455 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
456 past, it affected all builds that used the bsd.*.mk files. The old
457 behavior was a bug, but people may have relied upon it. To get this
458 behavior back, you can .include /etc/src.conf from /etc/make.conf
459 (which is still global and isn't changed). This also changes the
460 behavior of incremental builds inside the tree of individual
461 directories. Set MAKESYSPATH to ".../share/mk" to do that.
462 Although this has survived make universe and some upgrade scenarios,
463 other upgrade scenarios may have broken. At least one form of
464 temporary breakage was fixed with MAKESYSPATH settings for buildworld
465 as well... In cases where MAKESYSPATH isn't working with this
466 setting, you'll need to set it to the full path to your tree.
468 One side effect of all this cleaning up is that bsd.compiler.mk
469 is no longer implicitly included by bsd.own.mk. If you wish to
470 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
474 The lindev device has been removed since /dev/full has been made a
475 standard device. __FreeBSD_version has been bumped.
478 The knob WITHOUT_VI was added to the base system, which controls
479 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
480 in order to reorder files share/termcap and didn't build ex(1) as a
481 build tool, so building/installing with WITH_VI is highly advised for
482 build hosts for older releases.
484 This issue has been fixed in stable/9 and stable/10 in r277022 and
485 r276991, respectively.
488 The YES_HESIOD knob has been removed. It has been obsolete for
489 a decade. Please move to using WITH_HESIOD instead or your builds
490 will silently lack HESIOD.
493 The uart(4) driver has been changed with respect to its handling
494 of the low-level console. Previously the uart(4) driver prevented
495 any process from changing the baudrate or the CLOCAL and HUPCL
496 control flags. By removing the restrictions, operators can make
497 changes to the serial console port without having to reboot.
498 However, when getty(8) is started on the serial device that is
499 associated with the low-level console, a misconfigured terminal
500 line in /etc/ttys will now have a real impact.
501 Before upgrading the kernel, make sure that /etc/ttys has the
502 serial console device configured as 3wire without baudrate to
503 preserve the previous behaviour. E.g:
504 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
507 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
508 to improve performance. To re-enable it, if needed, run rpcbind
509 with command line option -W.
512 Switched back to the GPL dtc compiler due to updates in the upstream
513 dts files not being supported by the BSDL dtc compiler. You will need
514 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
515 may result while building dtb files during a kernel build if you fail
516 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
519 Clang and llvm have been upgraded to 3.4 release.
522 The nve(4) driver has been removed. Please use the nfe(4) driver
523 for NVIDIA nForce MCP Ethernet adapters instead.
526 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
527 This could cause certain C++ applications using shared libraries built
528 against the previous version of libc++ to crash. The incompatibility
529 has now been fixed, but any C++ applications or shared libraries built
530 between r261283 and r261801 should be recompiled.
533 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
534 capability mode support. Please note that enabling the feature in
535 kernel is still highly recommended.
538 OpenSSH is now built with sandbox support, and will use sandbox as
539 the default privilege separation method. This requires Capsicum
540 capability mode support in kernel.
543 The libelf and libdwarf libraries have been updated to newer
544 versions from upstream. Shared library version numbers for
545 these two libraries were bumped. Any ports or binaries
546 requiring these two libraries should be recompiled.
547 __FreeBSD_version is bumped to 1100006.
550 If a Makefile in a tests/ directory was auto-generating a Kyuafile
551 instead of providing an explicit one, this would prevent such
552 Makefile from providing its own Kyuafile in the future during
553 NO_CLEAN builds. This has been fixed in the Makefiles but manual
554 intervention is needed to clean an objdir if you use NO_CLEAN:
555 # find /usr/obj -name Kyuafile | xargs rm -f
558 The behavior of gss_pseudo_random() for the krb5 mechanism
559 has changed, for applications requesting a longer random string
560 than produced by the underlying enctype's pseudo-random() function.
561 In particular, the random string produced from a session key of
562 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
563 be different at the 17th octet and later, after this change.
564 The counter used in the PRF+ construction is now encoded as a
565 big-endian integer in accordance with RFC 4402.
566 __FreeBSD_version is bumped to 1100004.
569 The WITHOUT_ATF build knob has been removed and its functionality
570 has been subsumed into the more generic WITHOUT_TESTS. If you were
571 using the former to disable the build of the ATF libraries, you
572 should change your settings to use the latter.
575 The default version of mtree is nmtree which is obtained from
576 NetBSD. The output is generally the same, but may vary
577 slightly. If you found you need identical output adding
578 "-F freebsd9" to the command line should do the trick. For the
579 time being, the old mtree is available as fmtree.
582 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
583 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
584 1.1.4_8 and verify bsdyml not linked in, before running "make
586 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
588 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
591 The stable/10 branch has been created in subversion from head
595 The rc.d/jail script has been updated to support jail(8)
596 configuration file. The "jail_<jname>_*" rc.conf(5) variables
597 for per-jail configuration are automatically converted to
598 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
599 This is transparently backward compatible. See below about some
600 incompatibilities and rc.conf(5) manual page for more details.
602 These variables are now deprecated in favor of jail(8) configuration
603 file. One can use "rc.d/jail config <jname>" command to generate
604 a jail(8) configuration file in /var/run/jail.<jname>.conf without
605 running the jail(8) utility. The default pathname of the
606 configuration file is /etc/jail.conf and can be specified by
607 using $jail_conf or $jail_<jname>_conf variables.
609 Please note that jail_devfs_ruleset accepts an integer at
610 this moment. Please consider to rewrite the ruleset name
614 BIND has been removed from the base system. If all you need
615 is a local resolver, simply enable and start the local_unbound
616 service instead. Otherwise, several versions of BIND are
617 available in the ports tree. The dns/bind99 port is one example.
619 With this change, nslookup(1) and dig(1) are no longer in the base
620 system. Users should instead use host(1) and drill(1) which are
621 in the base system. Alternatively, nslookup and dig can
622 be obtained by installing the dns/bind-tools port.
625 With the addition of unbound(8), a new unbound user is now
626 required during installworld. "mergemaster -p" can be used to
627 add the user prior to installworld, as documented in the handbook.
630 OpenSSH is now built with DNSSEC support, and will by default
631 silently trust signed SSHFP records. This can be controlled with
632 the VerifyHostKeyDNS client configuration setting. DNSSEC support
633 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
636 The GNU Compiler Collection and C++ standard library (libstdc++)
637 are no longer built by default on platforms where clang is the system
638 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
642 The PROCDESC kernel option is now part of the GENERIC kernel
643 configuration and is required for the rwhod(8) to work.
644 If you are using custom kernel configuration, you should include
648 The API and ABI related to the Capsicum framework was modified
649 in backward incompatible way. The userland libraries and programs
650 have to be recompiled to work with the new kernel. This includes the
651 following libraries and programs, but the whole buildworld is
652 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
653 kdump, procstat, rwho, rwhod, uniq.
656 AES-NI intrinsic support has been added to gcc. The AES-NI module
657 has been updated to use this support. A new gcc is required to build
658 the aesni module on both i386 and amd64.
661 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
662 Thus "device padlock_rng" and "device rdrand_rng" should be
663 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
666 WITH_ICONV has been split into two feature sets. WITH_ICONV now
667 enables just the iconv* functionality and is now on by default.
668 WITH_LIBICONV_COMPAT enables the libiconv api and link time
669 compatability. Set WITHOUT_ICONV to build the old way.
670 If you have been using WITH_ICONV before, you will very likely
671 need to turn on WITH_LIBICONV_COMPAT.
674 INVARIANTS option now enables DEBUG for code with OpenSolaris and
675 Illumos origin, including ZFS. If you have INVARIANTS in your
676 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
678 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
679 locks if WITNESS option was set. Because that generated a lot of
680 witness(9) reports and all of them were believed to be false
681 positives, this is no longer done. New option OPENSOLARIS_WITNESS
682 can be used to achieve the previous behavior.
685 Timer values in IPv6 data structures now use time_uptime instead
686 of time_second. Although this is not a user-visible functional
687 change, userland utilities which directly use them---ndp(8),
688 rtadvd(8), and rtsold(8) in the base system---need to be updated
692 find -delete can now delete the pathnames given as arguments,
693 instead of only files found below them or if the pathname did
694 not contain any slashes. Formerly, the following error message
697 find: -delete: <path>: relative path potentially not safe
699 Deleting the pathnames given as arguments can be prevented
700 without error messages using -mindepth 1 or by changing
701 directory and passing "." as argument to find. This works in the
702 old as well as the new version of find.
705 Behavior of devfs rules path matching has been changed.
706 Pattern is now always matched against fully qualified devfs
707 path and slash characters must be explicitly matched by
708 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
709 subdirectories must be reviewed.
712 The default ARM ABI has changed to the ARM EABI. The old ABI is
713 incompatible with the ARM EABI and all programs and modules will
714 need to be rebuilt to work with a new kernel.
716 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
718 NOTE: Support for the old ABI will be removed in the future and
719 users are advised to upgrade.
722 pkg_install has been disconnected from the build if you really need it
723 you should add WITH_PKGTOOLS in your src.conf(5).
726 Most of network statistics structures were changed to be able
727 keep 64-bits counters. Thus all tools, that work with networking
728 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
731 Fix targets that run multiple make's to use && rather than ;
732 so that subsequent steps depend on success of previous.
734 NOTE: if building 'universe' with -j* on stable/8 or stable/9
735 it would be better to start the build using bmake, to avoid
736 overloading the machine.
739 Fix a bug that allowed a tracing process (e.g. gdb) to write
740 to a memory-mapped file in the traced process's address space
741 even if neither the traced process nor the tracing process had
742 write access to that file.
745 CVS has been removed from the base system. An exact copy
746 of the code is available from the devel/cvs port.
749 Some people report the following error after the switch to bmake:
751 make: illegal option -- J
752 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
754 *** [buildworld] Error code 2
756 this likely due to an old instance of make in
757 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
758 which src/Makefile will use that blindly, if it exists, so if
759 you see the above error:
761 rm -rf `make -V MAKEPATH`
766 Use bmake by default.
767 Whereas before one could choose to build with bmake via
768 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
769 make. The goal is to remove these knobs for 10-RELEASE.
771 It is worth noting that bmake (like gmake) treats the command
772 line as the unit of failure, rather than statements within the
773 command line. Thus '(cd some/where && dosomething)' is safer
774 than 'cd some/where; dosomething'. The '()' allows consistent
775 behavior in parallel build.
778 Fix a bug that allows NFS clients to issue READDIR on files.
781 The WITHOUT_IDEA option has been removed because
782 the IDEA patent expired.
785 The sysctl which controls TRIM support under ZFS has been renamed
786 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
790 The mergemaster command now uses the default MAKEOBJDIRPREFIX
791 rather than creating it's own in the temporary directory in
792 order allow access to bootstrapped versions of tools such as
793 install and mtree. When upgrading from version of FreeBSD where
794 the install command does not support -l, you will need to
795 install a new mergemaster command if mergemaster -p is required.
796 This can be accomplished with the command (cd src/usr.sbin/mergemaster
800 Legacy ATA stack, disabled and replaced by new CAM-based one since
801 FreeBSD 9.0, completely removed from the sources. Kernel modules
802 atadisk and atapi*, user-level tools atacontrol and burncd are
803 removed. Kernel option `options ATA_CAM` is now permanently enabled
807 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
808 and socketpair(2). Software, in particular Kerberos, may
809 automatically detect and use these during building. The resulting
810 binaries will not work on older kernels.
813 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
814 information, see the respective 20130304 entry).
817 Recent commits to callout(9) changed the size of struct callout,
818 so the KBI is probably heavily disturbed. Also, some functions
819 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
820 by macros. Every kernel module using it won't load, so rebuild
823 The ctl device has been re-enabled in GENERIC for i386 and amd64,
824 but does not initialize by default (because of the new CTL_DISABLE
825 option) to save memory. To re-enable it, remove the CTL_DISABLE
826 option from the kernel config file or set kern.cam.ctl.disable=0
827 in /boot/loader.conf.
830 The ctl device has been disabled in GENERIC for i386 and amd64.
831 This was done due to the extra memory being allocated at system
832 initialisation time by the ctl driver which was only used if
833 a CAM target device was created. This makes a FreeBSD system
834 unusable on 128MB or less of RAM.
837 A new compression method (lz4) has been merged to -HEAD. Please
838 refer to zpool-features(7) for more information.
840 Please refer to the "ZFS notes" section of this file for information
841 on upgrading boot ZFS pools.
844 A BSD-licensed patch(1) variant has been added and is installed
845 as bsdpatch, being the GNU version the default patch.
846 To inverse the logic and use the BSD-licensed one as default,
847 while having the GNU version installed as gnupatch, rebuild
848 and install world with the WITH_BSD_PATCH knob set.
851 Due to the use of the new -l option to install(1) during build
852 and install, you must take care not to directly set the INSTALL
853 make variable in your /etc/make.conf, /etc/src.conf, or on the
854 command line. If you wish to use the -C flag for all installs
855 you may be able to add INSTALL+=-C to /etc/make.conf or
859 The install(1) option -M has changed meaning and now takes an
860 argument that is a file or path to append logs to. In the
861 unlikely event that -M was the last option on the command line
862 and the command line contained at least two files and a target
863 directory the first file will have logs appended to it. The -M
864 option served little practical purpose in the last decade so its
865 use is expected to be extremely rare.
868 After switching to Clang as the default compiler some users of ZFS
869 on i386 systems started to experience stack overflow kernel panics.
870 Please consider using 'options KSTACK_PAGES=4' in such configurations.
873 GEOM_LABEL now mangles label names read from file system metadata.
874 Mangling affect labels containing spaces, non-printable characters,
875 '%' or '"'. Device names in /etc/fstab and other places may need to
879 By default, only the 10 most recent kernel dumps will be saved. To
880 restore the previous behaviour (no limit on the number of kernel dumps
881 stored in the dump directory) add the following line to /etc/rc.conf:
886 With the addition of auditdistd(8), a new auditdistd user is now
887 required during installworld. "mergemaster -p" can be used to
888 add the user prior to installworld, as documented in the handbook.
891 The sin6_scope_id member variable in struct sockaddr_in6 is now
892 filled by the kernel before passing the structure to the userland via
893 sysctl or routing socket. This means the KAME-specific embedded scope
894 id in sin6_addr.s6_addr[2] is always cleared in userland application.
895 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
896 __FreeBSD_version is bumped to 1000025.
899 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
900 This means that the world and kernel will be compiled with clang
901 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
902 and /usr/bin/cpp. To disable this behavior and revert to building
903 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
904 of current may need to bootstrap WITHOUT_CLANG first if the clang
905 build fails (its compatibility window doesn't extend to the 9 stable
909 The IPFIREWALL_FORWARD kernel option has been removed. Its
910 functionality now turned on by default.
913 The ZERO_COPY_SOCKET kernel option has been removed and
914 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
915 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
916 mechanism which is not safe and may result in kernel crashes.
917 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
918 driver supports disposeable external page sized mbuf storage.
919 Proper replacements for both zero-copy mechanisms are under
920 consideration and will eventually lead to complete removal
921 of the two kernel options.
924 The IPv4 network stack has been converted to network byte
925 order. The following modules need to be recompiled together
926 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
927 pf(4), ipfw(4), ng_ipfw(4), stf(4).
930 Support for non-MPSAFE filesystems was removed from VFS. The
931 VFS_VERSION was bumped, all filesystem modules shall be
935 All the non-MPSAFE filesystems have been disconnected from
936 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
937 portalfs, smbfs, xfs.
940 The interface cloning API and ABI has changed. The following
941 modules need to be recompiled together with kernel:
942 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
943 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
944 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
947 The sdhci driver was split in two parts: sdhci (generic SD Host
948 Controller logic) and sdhci_pci (actual hardware driver).
949 No kernel config modifications are required, but if you
950 load sdhc as a module you must switch to sdhci_pci instead.
953 Import the FUSE kernel and userland support into base system.
956 The GNU sort(1) program has been removed since the BSD-licensed
957 sort(1) has been the default for quite some time and no serious
958 problems have been reported. The corresponding WITH_GNU_SORT
962 The pfil(9) API/ABI for AF_INET family has been changed. Packet
963 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
967 The net80211(4) ABI has been changed to allow for improved driver
968 PS-POLL and power-save support. All wireless drivers need to be
969 recompiled to work with the new kernel.
972 The random(4) support for the VIA hardware random number
973 generator (`PADLOCK') is no longer enabled unconditionally.
974 Add the padlock_rng device in the custom kernel config if
975 needed. The GENERIC kernels on i386 and amd64 do include the
976 device, so the change only affects the custom kernel
980 The pf(4) packet filter ABI has been changed. pfctl(8) and
981 snmp_pf module need to be recompiled to work with new kernel.
984 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
985 to -HEAD. Pools that have empty_bpobj in active state can not be
986 imported read-write with ZFS implementations that do not support
987 this feature. For more information read the zpool-features(5)
991 The sparc64 ZFS loader has been changed to no longer try to auto-
992 detect ZFS providers based on diskN aliases but now requires these
993 to be explicitly listed in the OFW boot-device environment variable.
996 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
997 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
998 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1001 The following sysctls and tunables have been renamed for consistency
1002 with other variables:
1003 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1004 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1007 The sort utility has been replaced with BSD sort. For now, GNU sort
1008 is also available as "gnusort" or the default can be set back to
1009 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1010 installed as "bsdsort".
1013 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1014 Starting with this version the old system of ZFS pool versioning
1015 is superseded by "feature flags". This concept enables forward
1016 compatibility against certain future changes in functionality of ZFS
1017 pools. The first read-only compatible "feature flag" for ZFS pools
1018 is named "com.delphix:async_destroy". For more information
1019 read the new zpool-features(5) manual page.
1020 Please refer to the "ZFS notes" section of this file for information
1021 on upgrading boot ZFS pools.
1024 The malloc(3) implementation embedded in libc now uses sources imported
1025 as contrib/jemalloc. The most disruptive API change is to
1026 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1027 delete it prior to installworld, and optionally re-create it using the
1028 new format after rebooting. See malloc.conf(5) for details
1029 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1033 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1034 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1035 now spelled mips. This is to aid compatibility with third-party
1036 software that expects this naming scheme in uname(3). Little-endian
1037 settings are unchanged. If you are updating a big-endian mips64 machine
1038 from before this change, you may need to set MACHINE_ARCH=mips64 in
1039 your environment before the new build system will recognize your machine.
1042 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1046 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1047 nullfs(5) did not pass through all behaviours to the underlying layer,
1048 as a result if we bound to a socket on the lower layer we could connect
1049 only to the lower path; if we bound to the upper layer we could connect
1050 only to the upper path. The new behavior is one can connect to both the
1051 lower and the upper paths regardless what layer path one binds to.
1054 The getifaddrs upgrade path broken with 20111215 has been restored.
1055 If you have upgraded in between 20111215 and 20120209 you need to
1056 recompile libc again with your kernel. You still need to recompile
1057 world to be able to configure CARP but this restriction already
1058 comes from 20111215.
1061 The set_rcvar() function has been removed from /etc/rc.subr. All
1062 base and ports rc.d scripts have been updated, so if you have a
1063 port installed with a script in /usr/local/etc/rc.d you can either
1064 hand-edit the rcvar= line, or reinstall the port.
1066 An easy way to handle the mass-update of /etc/rc.d:
1067 rm /etc/rc.d/* && mergemaster -i
1070 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1071 on the current CPU and prevents other threads from running.
1072 This behavior can be reverted using the kern.stop_scheduler_on_panic
1074 The new behavior can be incompatible with kern.sync_on_panic.
1077 The carp(4) facility has been changed significantly. Configuration
1078 of the CARP protocol via ifconfig(8) has changed, as well as format
1079 of CARP events submitted to devd(8) has changed. See manual pages
1080 for more information. The arpbalance feature of carp(4) is currently
1081 not supported anymore.
1083 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1084 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1085 need to be recompiled.
1088 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1092 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1093 explicitely support non-MPSAFE filesystems.
1094 It is on by default for all supported platform at this present
1098 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1099 i386 and pc98 GENERIC kernel configuration files.
1102 sysinstall has been removed
1105 The stable/9 branch created in subversion. This corresponds to the
1106 RELENG_9 branch in CVS.
1112 Avoid using make -j when upgrading. While generally safe, there are
1113 sometimes problems using -j to upgrade. If your upgrade fails with
1114 -j, please try again without -j. From time to time in the past there
1115 have been problems using -j with buildworld and/or installworld. This
1116 is especially true when upgrading between "distant" versions (eg one
1117 that cross a major release boundary or several minor releases, or when
1118 several months have passed on the -current branch).
1120 Sometimes, obscure build problems are the result of environment
1121 poisoning. This can happen because the make utility reads its
1122 environment when searching for values for global variables. To run
1123 your build attempts in an "environmental clean room", prefix all make
1124 commands with 'env -i '. See the env(1) manual page for more details.
1126 When upgrading from one major version to another it is generally best
1127 to upgrade to the latest code in the currently installed branch first,
1128 then do an upgrade to the new branch. This is the best-tested upgrade
1129 path, and has the highest probability of being successful. Please try
1130 this approach before reporting problems with a major version upgrade.
1132 When upgrading a live system, having a root shell around before
1133 installing anything can help undo problems. Not having a root shell
1134 around can lead to problems if pam has changed too much from your
1135 starting point to allow continued authentication after the upgrade.
1137 This file should be read as a log of events. When a later event changes
1138 information of a prior event, the prior event should not be deleted.
1139 Instead, a pointer to the entry with the new information should be
1140 placed in the old entry. Readers of this file should also sanity check
1141 older entries before relying on them blindly. Authors of new entries
1142 should write them with this in mind.
1146 When upgrading the boot ZFS pool to a new version, always follow
1149 1.) recompile and reinstall the ZFS boot loader and boot block
1150 (this is part of "make buildworld" and "make installworld")
1152 2.) update the ZFS boot block on your boot drive
1154 The following example updates the ZFS boot block on the first
1155 partition (freebsd-boot) of a GPT partitioned drive ada0:
1156 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1158 Non-boot pools do not need these updates.
1162 If you are updating from a prior version of FreeBSD (even one just
1163 a few days old), you should follow this procedure. It is the most
1164 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1166 make kernel-toolchain
1167 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1168 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1170 To test a kernel once
1171 ---------------------
1172 If you just want to boot a kernel once (because you are not sure
1173 if it works, or if you want to boot a known bad kernel to provide
1174 debugging information) run
1175 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1176 nextboot -k testkernel
1178 To just build a kernel when you know that it won't mess you up
1179 --------------------------------------------------------------
1180 This assumes you are already running a CURRENT system. Replace
1181 ${arch} with the architecture of your machine (e.g. "i386",
1182 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1184 cd src/sys/${arch}/conf
1185 config KERNEL_NAME_HERE
1186 cd ../compile/KERNEL_NAME_HERE
1191 If this fails, go to the "To build a kernel" section.
1193 To rebuild everything and install it on the current system.
1194 -----------------------------------------------------------
1195 # Note: sometimes if you are running current you gotta do more than
1196 # is listed here if you are upgrading from a really old current.
1198 <make sure you have good level 0 dumps>
1200 make kernel KERNCONF=YOUR_KERNEL_HERE
1202 <reboot in single user> [3]
1209 To cross-install current onto a separate partition
1210 --------------------------------------------------
1211 # In this approach we use a separate partition to hold
1212 # current's root, 'usr', and 'var' directories. A partition
1213 # holding "/", "/usr" and "/var" should be about 2GB in
1216 <make sure you have good level 0 dumps>
1219 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1220 <maybe newfs current's root partition>
1221 <mount current's root partition on directory ${CURRENT_ROOT}>
1222 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1223 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1224 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1225 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1226 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1227 <reboot into current>
1228 <do a "native" rebuild/install as described in the previous section>
1229 <maybe install compatibility libraries from ports/misc/compat*>
1233 To upgrade in-place from stable to current
1234 ----------------------------------------------
1235 <make sure you have good level 0 dumps>
1237 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1239 <reboot in single user> [3]
1246 Make sure that you've read the UPDATING file to understand the
1247 tweaks to various things you need. At this point in the life
1248 cycle of current, things change often and you are on your own
1249 to cope. The defaults can also change, so please read ALL of
1250 the UPDATING entries.
1252 Also, if you are tracking -current, you must be subscribed to
1253 freebsd-current@freebsd.org. Make sure that before you update
1254 your sources that you have read and understood all the recent
1255 messages there. If in doubt, please track -stable which has
1256 much fewer pitfalls.
1258 [1] If you have third party modules, such as vmware, you
1259 should disable them at this point so they don't crash your
1262 [3] From the bootblocks, boot -s, and then do
1267 adjkerntz -i # if CMOS is wall time
1268 Also, when doing a major release upgrade, it is required that
1269 you boot into single user mode to do the installworld.
1271 [4] Note: This step is non-optional. Failure to do this step
1272 can result in a significant reduction in the functionality of the
1273 system. Attempting to do it by hand is not recommended and those
1274 that pursue this avenue should read this file carefully, as well
1275 as the archives of freebsd-current and freebsd-hackers mailing lists
1276 for potential gotchas. The -U option is also useful to consider.
1277 See mergemaster(8) for more information.
1279 [5] Usually this step is a noop. However, from time to time
1280 you may need to do this if you get unknown user in the following
1281 step. It never hurts to do it all the time. You may need to
1282 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1283 install) after the buildworld before this step if you last updated
1284 from current before 20130425 or from -stable before 20130430.
1286 [6] This only deletes old files and directories. Old libraries
1287 can be deleted by "make delete-old-libs", but you have to make
1288 sure that no program is using those libraries anymore.
1290 [8] In order to have a kernel that can run the 4.x binaries needed to
1291 do an installworld, you must include the COMPAT_FREEBSD4 option in
1292 your kernel. Failure to do so may leave you with a system that is
1293 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1294 required to run the 5.x binaries on more recent kernels. And so on
1295 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1297 Make sure that you merge any new devices from GENERIC since the
1298 last time you updated your kernel config file.
1300 [9] When checking out sources, you must include the -P flag to have
1301 cvs prune empty directories.
1303 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1304 "?=" instead of the "=" assignment operator, so that buildworld can
1305 override the CPUTYPE if it needs to.
1307 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1308 not on the command line, or in /etc/make.conf. buildworld will
1309 warn if it is improperly defined.
1312 This file contains a list, in reverse chronological order, of major
1313 breakages in tracking -current. It is not guaranteed to be a complete
1314 list of such breakages, and only contains entries since September 23, 2011.
1315 If you need to see UPDATING entries from before that date, you will need
1316 to fetch an UPDATING file from an older FreeBSD release.
1318 Copyright information:
1320 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1322 Redistribution, publication, translation and use, with or without
1323 modification, in full or in part, in any form or format of this
1324 document are permitted without further permission from the author.
1326 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1327 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1328 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1329 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1330 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1331 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1332 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1333 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1334 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1335 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1336 POSSIBILITY OF SUCH DAMAGE.
1338 Contact Warner Losh if you have any questions about your use of