xref: /freebsd/UPDATING (revision ebeff3f9b4f3a7459c712833bbb7179b357681de)
1Updating Information for FreeBSD current users.
2
3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4See end of file for further details.  For commonly done items, please see the
5COMMON ITEMS: section later in the file.  These instructions assume that you
6basically know what you are doing.  If not, then please consult the FreeBSD
7handbook:
8
9    http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
10
11Items affecting the ports and packages system can be found in
12/usr/ports/UPDATING.  Please read that file before running portupgrade.
13
14NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16the tip of head, and then rebuild without this option. The bootstrap process from
17older version of current across the gcc/clang cutover is a bit fragile.
18
19NOTE 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".)
33
342015mmdd:
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.
38
3920150525:
40	Clang and llvm have been upgraded to 3.6.1 release.  Please see the
41	20141231 entry below for information about prerequisites and upgrading,
42	if you are not already using 3.5.0 or higher.
43
4420150521:
45	TI platform code switched to using vendor DTS files and this update
46	may break existing systems running on Beaglebone, Beaglebone Black,
47	and Pandaboard:
48
49	- dtb files should be regenerated/reinstalled. Filenames are the
50	  same but content is different now
51	- GPIO addressing was changed, now each GPIO bank (32 pins per bank)
52	  has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
53	  addressing scheme is now pin 25 on /dev/gpioc3.
54	- Pandaboard: /etc/ttys should be updated, serial console device is
55	  now /dev/ttyu2, not /dev/ttyu0
56
5720150501:
58	soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
59	If you need the GNU extension from groff soelim(1), install groff
60	from package: pkg install groff, or via ports: textproc/groff.
61
6220150423:
63	chmod, chflags, chown and chgrp now affect symlinks in -R mode as
64	defined in symlink(7); previously symlinks were silently ignored.
65
6620150415:
67	The const qualifier has been removed from iconv(3) to comply with
68	POSIX.  The ports tree is aware of this from r384038 onwards.
69
7020150416:
71	Libraries specified by LIBADD in Makefiles must have a corresponding
72	DPADD_<lib> variable to ensure correct dependencies.  This is now
73	enforced in src.libnames.mk.
74
7520150324:
76	From legacy ata(4) driver was removed support for SATA controllers
77	supported by more functional drivers ahci(4), siis(4) and mvs(4).
78	Kernel modules ataahci and ataadaptec were removed completely,
79	replaced by ahci and mvs modules respectively.
80
8120150315:
82	Clang, llvm and lldb have been upgraded to 3.6.0 release.  Please see
83	the 20141231 entry below for information about prerequisites and
84	upgrading, if you are not already using 3.5.0 or higher.
85
8620150307:
87	The 32-bit PowerPC kernel has been changed to a position-independent
88	executable. This can only be booted with a version of loader(8)
89	newer than January 31, 2015, so make sure to update both world and
90	kernel before rebooting.
91
9220150217:
93	If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
94	but before r278950, the RNG was not seeded properly.  Immediately
95	upgrade the kernel to r278950 or later and regenerate any keys (e.g.
96	ssh keys or openssl keys) that were generated w/ a kernel from that
97	range.  This does not affect programs that directly used /dev/random
98	or /dev/urandom.  All userland uses of arc4random(3) are affected.
99
10020150210:
101	The autofs(4) ABI was changed in order to restore binary compatibility
102	with 10.1-RELEASE.  The automountd(8) daemon needs to be rebuilt to work
103	with the new kernel.
104
10520150131:
106	The powerpc64 kernel has been changed to a position-independent
107	executable. This can only be booted with a new version of loader(8),
108	so make sure to update both world and kernel before rebooting.
109
11020150118:
111	Clang and llvm have been upgraded to 3.5.1 release.  This is a bugfix
112	only release, no new features have been added.  Please see the 20141231
113	entry below for information about prerequisites and upgrading, if you
114	are not already using 3.5.0.
115
11620150107:
117	ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
118	taken from the ELF Tool Chain project rather than GNU binutils. They
119	should be drop-in replacements, with the addition of arm64 support.
120	The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
121	binutils tools, if necessary.
122
12320150105:
124	The default Unbound configuration now enables remote control
125	using a local socket.  Users who have already enabled the
126	local_unbound service should regenerate their configuration
127	by running "service local_unbound setup" as root.
128
12920150102:
130	The GNU texinfo and GNU info pages have been removed.
131	To be able to view GNU info pages please install texinfo from ports.
132
13320141231:
134	Clang, llvm and lldb have been upgraded to 3.5.0 release.
135
136	As of this release, a prerequisite for building clang, llvm and lldb is
137	a C++11 capable compiler and C++11 standard library.  This means that to
138	be able to successfully build the cross-tools stage of buildworld, with
139	clang as the bootstrap compiler, your system compiler or cross compiler
140	should either be clang 3.3 or later, or gcc 4.8 or later, and your
141	system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
142	later.
143
144	On any standard FreeBSD 10.x or 11.x installation, where clang and
145	libc++ are on by default (that is, on x86 or arm), this should work out
146	of the box.
147
148	On 9.x installations where clang is enabled by default, e.g. on x86 and
149	powerpc, libc++ will not be enabled by default, so libc++ should be
150	built (with clang) and installed first.  If both clang and libc++ are
151	missing, build clang first, then use it to build libc++.
152
153	On 8.x and earlier installations, upgrade to 9.x first, and then follow
154	the instructions for 9.x above.
155
156	Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
157	default, and do not build clang.
158
159	Many embedded systems are resource constrained, and will not be able to
160	build clang in a reasonable time, or in some cases at all.  In those
161	cases, cross building bootable systems on amd64 is a workaround.
162
163	This new version of clang introduces a number of new warnings, of which
164	the following are most likely to appear:
165
166	-Wabsolute-value
167
168	This warns in two cases, for both C and C++:
169	* When the code is trying to take the absolute value of an unsigned
170	  quantity, which is effectively a no-op, and almost never what was
171	  intended.  The code should be fixed, if at all possible.  If you are
172	  sure that the unsigned quantity can be safely cast to signed, without
173	  loss of information or undefined behavior, you can add an explicit
174	  cast, or disable the warning.
175
176	* When the code is trying to take an absolute value, but the called
177	  abs() variant is for the wrong type, which can lead to truncation.
178	  If you want to disable the warning instead of fixing the code, please
179	  make sure that truncation will not occur, or it might lead to unwanted
180	  side-effects.
181
182	-Wtautological-undefined-compare and
183	-Wundefined-bool-conversion
184
185	These warn when C++ code is trying to compare 'this' against NULL, while
186	'this' should never be NULL in well-defined C++ code.  However, there is
187	some legacy (pre C++11) code out there, which actively abuses this
188	feature, which was less strictly defined in previous C++ versions.
189
190	Squid and openjdk do this, for example.  The warning can be turned off
191	for C++98 and earlier, but compiling the code in C++11 mode might result
192	in unexpected behavior; for example, the parts of the program that are
193	unreachable could be optimized away.
194
19520141222:
196	The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
197	kernel sources have been removed. The .h files remain, since some
198	utilities include them. This will need to be fixed later.
199	If "mount -t oldnfs ..." is attempted, it will fail.
200	If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
201	the utilities will report errors.
202
20320141121:
204	The handling of LOCAL_LIB_DIRS has been altered to skip addition of
205	directories to top level SUBDIR variable when their parent
206	directory is included in LOCAL_DIRS.  Users with build systems with
207	such hierarchies and without SUBDIR entries in the parent
208	directory Makefiles should add them or add the directories to
209	LOCAL_DIRS.
210
21120141109:
212	faith(4) and faithd(8) have been removed from the base system. Faith
213	has been obsolete for a very long time.
214
21520141104:
216	vt(4), the new console driver, is enabled by default. It brings
217	support for Unicode and double-width characters, as well as
218	support for UEFI and integration with the KMS kernel video
219	drivers.
220
221	You may need to update your console settings in /etc/rc.conf,
222	most probably the keymap. During boot, /etc/rc.d/syscons will
223	indicate what you need to do.
224
225	vt(4) still has issues and lacks some features compared to
226	syscons(4). See the wiki for up-to-date information:
227	  https://wiki.freebsd.org/Newcons
228
229	If you want to keep using syscons(4), you can do so by adding
230	the following line to /boot/loader.conf:
231	  kern.vty=sc
232
23320141102:
234	pjdfstest has been integrated into kyua as an opt-in test suite.
235	Please see share/doc/pjdfstest/README for more details on how to
236	execute it.
237
23820141009:
239	gperf has been removed from the base system for architectures
240	that use clang. Ports that require gperf will obtain it from the
241	devel/gperf port.
242
24320140923:
244	pjdfstest has been moved from tools/regression/pjdfstest to
245	contrib/pjdfstest .
246
24720140922:
248	At svn r271982, The default linux compat kernel ABI has been adjusted
249	to 2.6.18 in support of the linux-c6 compat ports infrastructure
250	update.  If you wish to continue using the linux-f10 compat ports,
251	add compat.linux.osrelease=2.6.16 to your local sysctl.conf.  Users are
252	encouraged to update their linux-compat packages to linux-c6 during
253	their next update cycle.
254
25520140729:
256	The ofwfb driver, used to provide a graphics console on PowerPC when
257	using vt(4), no longer allows mmap() of all physical memory. This
258	will prevent Xorg on PowerPC with some ATI graphics cards from
259	initializing properly unless x11-servers/xorg-server is updated to
260	1.12.4_8 or newer.
261
26220140723:
263	The xdev targets have been converted to using TARGET and
264	TARGET_ARCH instead of XDEV and XDEV_ARCH.
265
26620140719:
267	The default unbound configuration has been modified to address
268	issues with reverse lookups on networks that use private
269	address ranges.  If you use the local_unbound service, run
270	"service local_unbound setup" as root to regenerate your
271	configuration, then "service local_unbound reload" to load the
272	new configuration.
273
27420140709:
275	The GNU texinfo and GNU info pages are not built and installed
276	anymore, WITH_INFO knob has been added to allow to built and install
277	them again.
278	UPDATE: see 20150102 entry on texinfo's removal
279
28020140708:
281	The GNU readline library is now an INTERNALLIB - that is, it is
282	statically linked into consumers (GDB and variants) in the base
283	system, and the shared library is no longer installed.  The
284	devel/readline port is available for third party software that
285	requires readline.
286
28720140702:
288	The Itanium architecture (ia64) has been removed from the list of
289	known architectures. This is the first step in the removal of the
290	architecture.
291
29220140701:
293	Commit r268115 has added NFSv4.1 server support, merged from
294	projects/nfsv4.1-server.  Since this includes changes to the
295	internal interfaces between the NFS related modules, a full
296	build of the kernel and modules will be necessary.
297	__FreeBSD_version has been bumped.
298
29920140629:
300	The WITHOUT_VT_SUPPORT kernel config knob has been renamed
301	WITHOUT_VT.  (The other _SUPPORT knobs have a consistent meaning
302	which differs from the behaviour controlled by this knob.)
303
30420140619:
305	Maximal length of the serial number in CTL was increased from 16 to
306	64 chars, that breaks ABI.  All CTL-related tools, such as ctladm
307	and ctld, need to be rebuilt to work with a new kernel.
308
30920140606:
310	The libatf-c and libatf-c++ major versions were downgraded to 0 and
311	1 respectively to match the upstream numbers.  They were out of
312	sync because, when they were originally added to FreeBSD, the
313	upstream versions were not respected.  These libraries are private
314	and not yet built by default, so renumbering them should be a
315	non-issue.  However, unclean source trees will yield broken test
316	programs once the operator executes "make delete-old-libs" after a
317	"make installworld".
318
319	Additionally, the atf-sh binary was made private by moving it into
320	/usr/libexec/.  Already-built shell test programs will keep the
321	path to the old binary so they will break after "make delete-old"
322	is run.
323
324	If you are using WITH_TESTS=yes (not the default), wipe the object
325	tree and rebuild from scratch to prevent spurious test failures.
326	This is only needed once: the misnumbered libraries and misplaced
327	binaries have been added to OptionalObsoleteFiles.inc so they will
328	be removed during a clean upgrade.
329
33020140512:
331	Clang and llvm have been upgraded to 3.4.1 release.
332
33320140508:
334	We bogusly installed src.opts.mk in /usr/share/mk. This file should
335	be removed to avoid issues in the future (and has been added to
336	ObsoleteFiles.inc).
337
33820140505:
339	/etc/src.conf now affects only builds of the FreeBSD src tree. In the
340	past, it affected all builds that used the bsd.*.mk files. The old
341	behavior was a bug, but people may have relied upon it. To get this
342	behavior back, you can .include /etc/src.conf from /etc/make.conf
343	(which is still global and isn't changed). This also changes the
344	behavior of incremental builds inside the tree of individual
345	directories. Set MAKESYSPATH to ".../share/mk" to do that.
346	Although this has survived make universe and some upgrade scenarios,
347	other upgrade scenarios may have broken. At least one form of
348	temporary breakage was fixed with MAKESYSPATH settings for buildworld
349	as well... In cases where MAKESYSPATH isn't working with this
350	setting, you'll need to set it to the full path to your tree.
351
352	One side effect of all this cleaning up is that bsd.compiler.mk
353	is no longer implicitly included by bsd.own.mk. If you wish to
354	use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
355	as well.
356
35720140430:
358	The lindev device has been removed since /dev/full has been made a
359	standard device.  __FreeBSD_version has been bumped.
360
36120140424:
362	The knob WITHOUT_VI was added to the base system, which controls
363	building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
364	in order to reorder files share/termcap and didn't build ex(1) as a
365	build tool, so building/installing with WITH_VI is highly advised for
366	build hosts for older releases.
367
368	This issue has been fixed in stable/9 and stable/10 in r277022 and
369	r276991, respectively.
370
37120140418:
372	The YES_HESIOD knob has been removed. It has been obsolete for
373	a decade. Please move to using WITH_HESIOD instead or your builds
374	will silently lack HESIOD.
375
37620140405:
377	The uart(4) driver has been changed with respect to its handling
378	of the low-level console. Previously the uart(4) driver prevented
379	any process from changing the baudrate or the CLOCAL and HUPCL
380	control flags. By removing the restrictions, operators can make
381	changes to the serial console port without having to reboot.
382	However, when getty(8) is started on the serial device that is
383	associated with the low-level console, a misconfigured terminal
384	line in /etc/ttys will now have a real impact.
385	Before upgrading the kernel, make sure that /etc/ttys has the
386	serial console device configured as 3wire without baudrate to
387	preserve the previous behaviour. E.g:
388	    ttyu0  "/usr/libexec/getty 3wire"  vt100  on  secure
389
39020140306:
391	Support for libwrap (TCP wrappers) in rpcbind was disabled by default
392	to improve performance.  To re-enable it, if needed, run rpcbind
393	with command line option -W.
394
39520140226:
396	Switched back to the GPL dtc compiler due to updates in the upstream
397	dts files not being supported by the BSDL dtc compiler. You will need
398	to rebuild your kernel toolchain to pick up the new compiler. Core dumps
399	may result while building dtb files during a kernel build if you fail
400	to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
401
40220140216:
403	Clang and llvm have been upgraded to 3.4 release.
404
40520140216:
406	The nve(4) driver has been removed.  Please use the nfe(4) driver
407	for NVIDIA nForce MCP Ethernet adapters instead.
408
40920140212:
410	An ABI incompatibility crept into the libc++ 3.4 import in r261283.
411	This could cause certain C++ applications using shared libraries built
412	against the previous version of libc++ to crash.  The incompatibility
413	has now been fixed, but any C++ applications or shared libraries built
414	between r261283 and r261801 should be recompiled.
415
41620140204:
417	OpenSSH will now ignore errors caused by kernel lacking of Capsicum
418	capability mode support.  Please note that enabling the feature in
419	kernel is still highly recommended.
420
42120140131:
422	OpenSSH is now built with sandbox support, and will use sandbox as
423	the default privilege separation method.  This requires Capsicum
424	capability mode support in kernel.
425
42620140128:
427	The libelf and libdwarf libraries have been updated to newer
428	versions from upstream. Shared library version numbers for
429	these two libraries were bumped. Any ports or binaries
430	requiring these two libraries should be recompiled.
431	__FreeBSD_version is bumped to 1100006.
432
43320140110:
434	If a Makefile in a tests/ directory was auto-generating a Kyuafile
435	instead of providing an explicit one, this would prevent such
436	Makefile from providing its own Kyuafile in the future during
437	NO_CLEAN builds.  This has been fixed in the Makefiles but manual
438	intervention is needed to clean an objdir if you use NO_CLEAN:
439	  # find /usr/obj -name Kyuafile | xargs rm -f
440
44120131213:
442	The behavior of gss_pseudo_random() for the krb5 mechanism
443	has changed, for applications requesting a longer random string
444	than produced by the underlying enctype's pseudo-random() function.
445	In particular, the random string produced from a session key of
446	enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
447	be different at the 17th octet and later, after this change.
448	The counter used in the PRF+ construction is now encoded as a
449	big-endian integer in accordance with RFC 4402.
450	__FreeBSD_version is bumped to 1100004.
451
45220131108:
453	The WITHOUT_ATF build knob has been removed and its functionality
454	has been subsumed into the more generic WITHOUT_TESTS.  If you were
455	using the former to disable the build of the ATF libraries, you
456	should change your settings to use the latter.
457
45820131025:
459	The default version of mtree is nmtree which is obtained from
460	NetBSD.  The output is generally the same, but may vary
461	slightly.  If you found you need identical output adding
462	"-F freebsd9" to the command line should do the trick.  For the
463	time being, the old mtree is available as fmtree.
464
46520131014:
466	libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
467	This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
468	1.1.4_8 and verify bsdyml not linked in, before running "make
469	delete-old-libs":
470	  # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
471	  or
472	  # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
473
47420131010:
475	The rc.d/jail script has been updated to support jail(8)
476	configuration file.  The "jail_<jname>_*" rc.conf(5) variables
477	for per-jail configuration are automatically converted to
478	/var/run/jail.<jname>.conf before the jail(8) utility is invoked.
479	This is transparently backward compatible.  See below about some
480	incompatibilities and rc.conf(5) manual page for more details.
481
482	These variables are now deprecated in favor of jail(8) configuration
483	file.  One can use "rc.d/jail config <jname>" command to generate
484	a jail(8) configuration file in /var/run/jail.<jname>.conf without
485	running the jail(8) utility.   The default pathname of the
486	configuration file is /etc/jail.conf and can be specified by
487	using $jail_conf or $jail_<jname>_conf variables.
488
489	Please note that jail_devfs_ruleset accepts an integer at
490	this moment.  Please consider to rewrite the ruleset name
491	with an integer.
492
49320130930:
494	BIND has been removed from the base system.  If all you need
495	is a local resolver, simply enable and start the local_unbound
496	service instead.  Otherwise, several versions of BIND are
497	available in the ports tree.   The dns/bind99 port is one example.
498
499	With this change, nslookup(1) and dig(1) are no longer in the base
500	system.  Users should instead use host(1) and drill(1) which are
501	in the base system.  Alternatively, nslookup and dig can
502	be obtained by installing the dns/bind-tools port.
503
50420130916:
505	With the addition of unbound(8), a new unbound user is now
506	required during installworld.  "mergemaster -p" can be used to
507	add the user prior to installworld, as documented in the handbook.
508
50920130911:
510	OpenSSH is now built with DNSSEC support, and will by default
511	silently trust signed SSHFP records.  This can be controlled with
512	the VerifyHostKeyDNS client configuration setting.  DNSSEC support
513	can be disabled entirely with the WITHOUT_LDNS option in src.conf.
514
51520130906:
516	The GNU Compiler Collection and C++ standard library (libstdc++)
517	are no longer built by default on platforms where clang is the system
518	compiler.  You can enable them with the WITH_GCC and WITH_GNUCXX
519	options in src.conf.
520
52120130905:
522	The PROCDESC kernel option is now part of the GENERIC kernel
523	configuration and is required for the rwhod(8) to work.
524	If you are using custom kernel configuration, you should include
525	'options PROCDESC'.
526
52720130905:
528	The API and ABI related to the Capsicum framework was modified
529	in backward incompatible way. The userland libraries and programs
530	have to be recompiled to work with the new kernel. This includes the
531	following libraries and programs, but the whole buildworld is
532	advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
533	kdump, procstat, rwho, rwhod, uniq.
534
53520130903:
536	AES-NI intrinsic support has been added to gcc.  The AES-NI module
537	has been updated to use this support.  A new gcc is required to build
538	the aesni module on both i386 and amd64.
539
54020130821:
541	The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
542	Thus "device padlock_rng" and "device rdrand_rng" should be
543	used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
544
54520130813:
546	WITH_ICONV has been split into two feature sets.  WITH_ICONV now
547	enables just the iconv* functionality and is now on by default.
548	WITH_LIBICONV_COMPAT enables the libiconv api and link time
549	compatability.  Set WITHOUT_ICONV to build the old way.
550	If you have been using WITH_ICONV before, you will very likely
551	need to turn on WITH_LIBICONV_COMPAT.
552
55320130806:
554	INVARIANTS option now enables DEBUG for code with OpenSolaris and
555	Illumos origin, including ZFS.  If you have INVARIANTS in your
556	kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
557	explicitly.
558	DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
559	locks if WITNESS option was set.  Because that generated a lot of
560	witness(9) reports and all of them were believed to be false
561	positives, this is no longer done.  New option OPENSOLARIS_WITNESS
562	can be used to achieve the previous behavior.
563
56420130806:
565	Timer values in IPv6 data structures now use time_uptime instead
566	of time_second.  Although this is not a user-visible functional
567	change, userland utilities which directly use them---ndp(8),
568	rtadvd(8), and rtsold(8) in the base system---need to be updated
569	to r253970 or later.
570
57120130802:
572	find -delete can now delete the pathnames given as arguments,
573	instead of only files found below them or if the pathname did
574	not contain any slashes. Formerly, the following error message
575	would result:
576
577	find: -delete: <path>: relative path potentially not safe
578
579	Deleting the pathnames given as arguments can be prevented
580	without error messages using -mindepth 1 or by changing
581	directory and passing "." as argument to find. This works in the
582	old as well as the new version of find.
583
58420130726:
585	Behavior of devfs rules path matching has been changed.
586	Pattern is now always matched against fully qualified devfs
587	path and slash characters must be explicitly matched by
588	slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
589	subdirectories must be reviewed.
590
59120130716:
592	The default ARM ABI has changed to the ARM EABI. The old ABI is
593	incompatible with the ARM EABI and all programs and modules will
594	need to be rebuilt to work with a new kernel.
595
596	To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
597
598	NOTE: Support for the old ABI will be removed in the future and
599	users are advised to upgrade.
600
60120130709:
602	pkg_install has been disconnected from the build if you really need it
603	you should add WITH_PKGTOOLS in your src.conf(5).
604
60520130709:
606	Most of network statistics structures were changed to be able
607	keep 64-bits counters. Thus all tools, that work with networking
608	statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
609
61020130629:
611	Fix targets that run multiple make's to use && rather than ;
612	so that subsequent steps depend on success of previous.
613
614	NOTE: if building 'universe' with -j* on stable/8 or stable/9
615	it would be better to start the build using bmake, to avoid
616	overloading the machine.
617
61820130618:
619	Fix a bug that allowed a tracing process (e.g. gdb) to write
620	to a memory-mapped file in the traced process's address space
621	even if neither the traced process nor the tracing process had
622	write access to that file.
623
62420130615:
625	CVS has been removed from the base system.  An exact copy
626	of the code is available from the devel/cvs port.
627
62820130613:
629	Some people report the following error after the switch to bmake:
630
631		make: illegal option -- J
632		usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
633			...
634		*** [buildworld] Error code 2
635
636	this likely due to an old instance of make in
637	${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
638	which src/Makefile will use that blindly, if it exists, so if
639	you see the above error:
640
641		rm -rf `make -V MAKEPATH`
642
643	should resolve it.
644
64520130516:
646	Use bmake by default.
647	Whereas before one could choose to build with bmake via
648	-DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
649	make. The goal is to remove these knobs for 10-RELEASE.
650
651	It is worth noting that bmake (like gmake) treats the command
652	line as the unit of failure, rather than statements within the
653	command line.  Thus '(cd some/where && dosomething)' is safer
654	than 'cd some/where; dosomething'. The '()' allows consistent
655	behavior in parallel build.
656
65720130429:
658        Fix a bug that allows NFS clients to issue READDIR on files.
659
66020130426:
661	The WITHOUT_IDEA option has been removed because
662	the IDEA patent expired.
663
66420130426:
665	The sysctl which controls TRIM support under ZFS has been renamed
666	from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
667	enabled by default.
668
66920130425:
670	The mergemaster command now uses the default MAKEOBJDIRPREFIX
671	rather than creating it's own in the temporary directory in
672	order allow access to bootstrapped versions of tools such as
673	install and mtree.  When upgrading from version of FreeBSD where
674	the install command does not support -l, you will need to
675	install a new mergemaster command if mergemaster -p is required.
676	This can be accomplished with the command (cd src/usr.sbin/mergemaster
677	&& make install).
678
67920130404:
680	Legacy ATA stack, disabled and replaced by new CAM-based one since
681	FreeBSD 9.0, completely removed from the sources.  Kernel modules
682	atadisk and atapi*, user-level tools atacontrol and burncd are
683	removed.  Kernel option `options ATA_CAM` is now permanently enabled
684	and removed.
685
68620130319:
687	SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
688	and socketpair(2). Software, in particular Kerberos, may
689	automatically detect and use these during building. The resulting
690	binaries will not work on older kernels.
691
69220130308:
693	CTL_DISABLE has also been added to the sparc64 GENERIC (for further
694	information, see the respective 20130304 entry).
695
69620130304:
697	Recent commits to callout(9) changed the size of struct callout,
698	so the KBI is probably heavily disturbed. Also, some functions
699	in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
700	by macros. Every kernel module using it won't load, so rebuild
701	is requested.
702
703	The ctl device has been re-enabled in GENERIC for i386 and amd64,
704	but does not initialize by default (because of the new CTL_DISABLE
705	option) to save memory.  To re-enable it, remove the CTL_DISABLE
706	option from the kernel config file or set kern.cam.ctl.disable=0
707	in /boot/loader.conf.
708
70920130301:
710	The ctl device has been disabled in GENERIC for i386 and amd64.
711	This was done due to the extra memory being allocated at system
712	initialisation time by the ctl driver which was only used if
713	a CAM target device was created.  This makes a FreeBSD system
714	unusable on 128MB or less of RAM.
715
71620130208:
717	A new compression method (lz4) has been merged to -HEAD.  Please
718	refer to zpool-features(7) for more information.
719
720	Please refer to the "ZFS notes" section of this file for information
721	on upgrading boot ZFS pools.
722
72320130129:
724	A BSD-licensed patch(1) variant has been added and is installed
725	as bsdpatch, being the GNU version the default patch.
726	To inverse the logic and use the BSD-licensed one as default,
727	while having the GNU version installed as gnupatch, rebuild
728	and install world with the WITH_BSD_PATCH knob set.
729
73020130121:
731	Due to the use of the new -l option to install(1) during build
732	and install, you must take care not to directly set the INSTALL
733	make variable in your /etc/make.conf, /etc/src.conf, or on the
734	command line.  If you wish to use the -C flag for all installs
735	you may be able to add INSTALL+=-C to /etc/make.conf or
736	/etc/src.conf.
737
73820130118:
739	The install(1) option -M has changed meaning and now takes an
740	argument that is a file or path to append logs to.  In the
741	unlikely event that -M was the last option on the command line
742	and the command line contained at least two files and a target
743	directory the first file will have logs appended to it.  The -M
744	option served little practical purpose in the last decade so its
745	use is expected to be extremely rare.
746
74720121223:
748	After switching to Clang as the default compiler some users of ZFS
749	on i386 systems started to experience stack overflow kernel panics.
750	Please consider using 'options KSTACK_PAGES=4' in such configurations.
751
75220121222:
753	GEOM_LABEL now mangles label names read from file system metadata.
754	Mangling affect labels containing spaces, non-printable characters,
755	'%' or '"'. Device names in /etc/fstab and other places may need to
756	be updated.
757
75820121217:
759	By default, only the 10 most recent kernel dumps will be saved.  To
760	restore the previous behaviour (no limit on the number of kernel dumps
761	stored in the dump directory) add the following line to /etc/rc.conf:
762
763		savecore_flags=""
764
76520121201:
766	With the addition of auditdistd(8), a new auditdistd user is now
767	required during installworld.  "mergemaster -p" can be used to
768	add the user prior to installworld, as documented in the handbook.
769
77020121117:
771	The sin6_scope_id member variable in struct sockaddr_in6 is now
772	filled by the kernel before passing the structure to the userland via
773	sysctl or routing socket.  This means the KAME-specific embedded scope
774	id in sin6_addr.s6_addr[2] is always cleared in userland application.
775	This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
776	__FreeBSD_version is bumped to 1000025.
777
77820121105:
779	On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
780	This means that the world and kernel will be compiled with clang
781	and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
782	and /usr/bin/cpp.  To disable this behavior and revert to building
783	with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
784	of current may need to bootstrap WITHOUT_CLANG first if the clang
785	build fails (its compatibility window doesn't extend to the 9 stable
786	branch point).
787
78820121102:
789	The IPFIREWALL_FORWARD kernel option has been removed. Its
790	functionality now turned on by default.
791
79220121023:
793	The ZERO_COPY_SOCKET kernel option has been removed and
794	split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
795	NB: SOCKET_SEND_COW uses the VM page based copy-on-write
796	mechanism which is not safe and may result in kernel crashes.
797	NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
798	driver supports disposeable external page sized mbuf storage.
799	Proper replacements for both zero-copy mechanisms are under
800	consideration and will eventually lead to complete removal
801	of the two kernel options.
802
80320121023:
804	The IPv4 network stack has been converted to network byte
805	order. The following modules need to be recompiled together
806	with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
807	pf(4), ipfw(4), ng_ipfw(4), stf(4).
808
80920121022:
810	Support for non-MPSAFE filesystems was removed from VFS. The
811	VFS_VERSION was bumped, all filesystem modules shall be
812	recompiled.
813
81420121018:
815	All the non-MPSAFE filesystems have been disconnected from
816	the build. The full list includes: codafs, hpfs, ntfs, nwfs,
817	portalfs, smbfs, xfs.
818
81920121016:
820	The interface cloning API and ABI has changed. The following
821	modules need to be recompiled together with kernel:
822	ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
823	vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
824	faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
825
82620121015:
827	The sdhci driver was split in two parts: sdhci (generic SD Host
828	Controller logic) and sdhci_pci (actual hardware driver).
829	No kernel config modifications are required, but if you
830	load sdhc as a module you must switch to sdhci_pci instead.
831
83220121014:
833	Import the FUSE kernel and userland support into base system.
834
83520121013:
836	The GNU sort(1) program has been removed since the BSD-licensed
837	sort(1) has been the default for quite some time and no serious
838	problems have been reported.  The corresponding WITH_GNU_SORT
839	knob has also gone.
840
84120121006:
842	The pfil(9) API/ABI for AF_INET family has been changed. Packet
843	filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
844	with new kernel.
845
84620121001:
847	The net80211(4) ABI has been changed to allow for improved driver
848	PS-POLL and power-save support.  All wireless drivers need to be
849	recompiled to work with the new kernel.
850
85120120913:
852	The random(4) support for the VIA hardware random number
853	generator (`PADLOCK') is no longer enabled unconditionally.
854	Add the padlock_rng device in the custom kernel config if
855	needed.  The GENERIC kernels on i386 and amd64 do include the
856	device, so the change only affects the custom kernel
857	configurations.
858
85920120908:
860	The pf(4) packet filter ABI has been changed. pfctl(8) and
861	snmp_pf module need to be recompiled to work with new kernel.
862
86320120828:
864	A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
865	to -HEAD. Pools that have empty_bpobj in active state can not be
866	imported read-write with ZFS implementations that do not support
867	this feature. For more information read the zpool-features(5)
868	manual page.
869
87020120727:
871	The sparc64 ZFS loader has been changed to no longer try to auto-
872	detect ZFS providers based on diskN aliases but now requires these
873	to be explicitly listed in the OFW boot-device environment variable.
874
87520120712:
876	The OpenSSL has been upgraded to 1.0.1c.  Any binaries requiring
877	libcrypto.so.6 or libssl.so.6 must be recompiled.  Also, there are
878	configuration changes.  Make sure to merge /etc/ssl/openssl.cnf.
879
88020120712:
881	The following sysctls and tunables have been renamed for consistency
882	with other variables:
883	  kern.cam.da.da_send_ordered   -> kern.cam.da.send_ordered
884	  kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
885
88620120628:
887	The sort utility has been replaced with BSD sort.  For now, GNU sort
888	is also available as "gnusort" or the default can be set back to
889	GNU sort by setting WITH_GNU_SORT.  In this case, BSD sort will be
890	installed as "bsdsort".
891
89220120611:
893	A new version of ZFS (pool version 5000) has been merged to -HEAD.
894	Starting with this version the old system of ZFS pool versioning
895	is superseded by "feature flags". This concept enables forward
896	compatibility against certain future changes in functionality of ZFS
897	pools. The first read-only compatible "feature flag" for ZFS pools
898	is named "com.delphix:async_destroy". For more information
899	read the new zpool-features(5) manual page.
900	Please refer to the "ZFS notes" section of this file for information
901	on upgrading boot ZFS pools.
902
90320120417:
904	The malloc(3) implementation embedded in libc now uses sources imported
905	as contrib/jemalloc.  The most disruptive API change is to
906	/etc/malloc.conf.  If your system has an old-style /etc/malloc.conf,
907	delete it prior to installworld, and optionally re-create it using the
908	new format after rebooting.  See malloc.conf(5) for details
909	(specifically the TUNING section and the "opt.*" entries in the MALLCTL
910	NAMESPACE section).
911
91220120328:
913	Big-endian MIPS TARGET_ARCH values no longer end in "eb".  mips64eb
914	is now spelled mips64.  mipsn32eb is now spelled mipsn32.  mipseb is
915	now spelled mips.  This is to aid compatibility with third-party
916	software that expects this naming scheme in uname(3).  Little-endian
917	settings are unchanged. If you are updating a big-endian mips64 machine
918	from before this change, you may need to set MACHINE_ARCH=mips64 in
919	your environment before the new build system will recognize your machine.
920
92120120306:
922	Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
923	platforms.
924
92520120229:
926	Now unix domain sockets behave "as expected" on	nullfs(5). Previously
927	nullfs(5) did not pass through all behaviours to the underlying layer,
928	as a result if we bound to a socket on the lower layer we could connect
929	only to the lower path; if we bound to the upper layer we could connect
930	only to	the upper path. The new behavior is one can connect to both the
931	lower and the upper paths regardless what layer path one binds to.
932
93320120211:
934	The getifaddrs upgrade path broken with 20111215 has been restored.
935	If you have upgraded in between 20111215 and 20120209 you need to
936	recompile libc again with your kernel.  You still need to recompile
937	world to be able to configure CARP but this restriction already
938	comes from 20111215.
939
94020120114:
941	The set_rcvar() function has been removed from /etc/rc.subr.  All
942	base and ports rc.d scripts have been updated, so if you have a
943	port installed with a script in /usr/local/etc/rc.d you can either
944	hand-edit the rcvar= line, or reinstall the port.
945
946	An easy way to handle the mass-update of /etc/rc.d:
947	rm /etc/rc.d/* && mergemaster -i
948
94920120109:
950	panic(9) now stops other CPUs in the SMP systems, disables interrupts
951	on the current CPU and prevents other threads from running.
952	This behavior can be reverted using the kern.stop_scheduler_on_panic
953	tunable/sysctl.
954	The new behavior can be incompatible with kern.sync_on_panic.
955
95620111215:
957	The carp(4) facility has been changed significantly. Configuration
958	of the CARP protocol via ifconfig(8) has changed, as well as format
959	of CARP events submitted to devd(8) has changed. See manual pages
960	for more information. The arpbalance feature of carp(4) is currently
961	not supported anymore.
962
963	Size of struct in_aliasreq, struct in6_aliasreq has changed. User
964	utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
965	need to be recompiled.
966
96720111122:
968	The acpi_wmi(4) status device /dev/wmistat has been renamed to
969	/dev/wmistat0.
970
97120111108:
972	The option VFS_ALLOW_NONMPSAFE option has been added in order to
973	explicitely support non-MPSAFE filesystems.
974	It is on by default for all supported platform at this present
975	time.
976
97720111101:
978	The broken amd(4) driver has been replaced with esp(4) in the amd64,
979	i386 and pc98 GENERIC kernel configuration files.
980
98120110930:
982	sysinstall has been removed
983
98420110923:
985	The stable/9 branch created in subversion.  This corresponds to the
986	RELENG_9 branch in CVS.
987
988COMMON ITEMS:
989
990	General Notes
991	-------------
992	Avoid using make -j when upgrading.  While generally safe, there are
993	sometimes problems using -j to upgrade.  If your upgrade fails with
994	-j, please try again without -j.  From time to time in the past there
995	have been problems using -j with buildworld and/or installworld.  This
996	is especially true when upgrading between "distant" versions (eg one
997	that cross a major release boundary or several minor releases, or when
998	several months have passed on the -current branch).
999
1000	Sometimes, obscure build problems are the result of environment
1001	poisoning.  This can happen because the make utility reads its
1002	environment when searching for values for global variables.  To run
1003	your build attempts in an "environmental clean room", prefix all make
1004	commands with 'env -i '.  See the env(1) manual page for more details.
1005
1006	When upgrading from one major version to another it is generally best
1007	to upgrade to the latest code in the currently installed branch first,
1008	then do an upgrade to the new branch. This is the best-tested upgrade
1009	path, and has the highest probability of being successful.  Please try
1010	this approach before reporting problems with a major version upgrade.
1011
1012	When upgrading a live system, having a root shell around before
1013	installing anything can help undo problems. Not having a root shell
1014	around can lead to problems if pam has changed too much from your
1015	starting point to allow continued authentication after the upgrade.
1016
1017	ZFS notes
1018	---------
1019	When upgrading the boot ZFS pool to a new version, always follow
1020	these two steps:
1021
1022	1.) recompile and reinstall the ZFS boot loader and boot block
1023	(this is part of "make buildworld" and "make installworld")
1024
1025	2.) update the ZFS boot block on your boot drive
1026
1027	The following example updates the ZFS boot block on the first
1028	partition (freebsd-boot) of a GPT partitioned drive ada0:
1029	"gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1030
1031	Non-boot pools do not need these updates.
1032
1033	To build a kernel
1034	-----------------
1035	If you are updating from a prior version of FreeBSD (even one just
1036	a few days old), you should follow this procedure.  It is the most
1037	failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1038
1039	make kernel-toolchain
1040	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1041	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1042
1043	To test a kernel once
1044	---------------------
1045	If you just want to boot a kernel once (because you are not sure
1046	if it works, or if you want to boot a known bad kernel to provide
1047	debugging information) run
1048	make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1049	nextboot -k testkernel
1050
1051	To just build a kernel when you know that it won't mess you up
1052	--------------------------------------------------------------
1053	This assumes you are already running a CURRENT system.  Replace
1054	${arch} with the architecture of your machine (e.g. "i386",
1055	"arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1056
1057	cd src/sys/${arch}/conf
1058	config KERNEL_NAME_HERE
1059	cd ../compile/KERNEL_NAME_HERE
1060	make depend
1061	make
1062	make install
1063
1064	If this fails, go to the "To build a kernel" section.
1065
1066	To rebuild everything and install it on the current system.
1067	-----------------------------------------------------------
1068	# Note: sometimes if you are running current you gotta do more than
1069	# is listed here if you are upgrading from a really old current.
1070
1071	<make sure you have good level 0 dumps>
1072	make buildworld
1073	make kernel KERNCONF=YOUR_KERNEL_HERE
1074							[1]
1075	<reboot in single user>				[3]
1076	mergemaster -Fp					[5]
1077	make installworld
1078	mergemaster -Fi					[4]
1079	make delete-old					[6]
1080	<reboot>
1081
1082	To cross-install current onto a separate partition
1083	--------------------------------------------------
1084	# In this approach we use a separate partition to hold
1085	# current's root, 'usr', and 'var' directories.   A partition
1086	# holding "/", "/usr" and "/var" should be about 2GB in
1087	# size.
1088
1089	<make sure you have good level 0 dumps>
1090	<boot into -stable>
1091	make buildworld
1092	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1093	<maybe newfs current's root partition>
1094	<mount current's root partition on directory ${CURRENT_ROOT}>
1095	make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1096	make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1097	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1098	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1099	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1100	<reboot into current>
1101	<do a "native" rebuild/install as described in the previous section>
1102	<maybe install compatibility libraries from ports/misc/compat*>
1103	<reboot>
1104
1105
1106	To upgrade in-place from stable to current
1107	----------------------------------------------
1108	<make sure you have good level 0 dumps>
1109	make buildworld					[9]
1110	make kernel KERNCONF=YOUR_KERNEL_HERE		[8]
1111							[1]
1112	<reboot in single user>				[3]
1113	mergemaster -Fp					[5]
1114	make installworld
1115	mergemaster -Fi					[4]
1116	make delete-old					[6]
1117	<reboot>
1118
1119	Make sure that you've read the UPDATING file to understand the
1120	tweaks to various things you need.  At this point in the life
1121	cycle of current, things change often and you are on your own
1122	to cope.  The defaults can also change, so please read ALL of
1123	the UPDATING entries.
1124
1125	Also, if you are tracking -current, you must be subscribed to
1126	freebsd-current@freebsd.org.  Make sure that before you update
1127	your sources that you have read and understood all the recent
1128	messages there.  If in doubt, please track -stable which has
1129	much fewer pitfalls.
1130
1131	[1] If you have third party modules, such as vmware, you
1132	should disable them at this point so they don't crash your
1133	system on reboot.
1134
1135	[3] From the bootblocks, boot -s, and then do
1136		fsck -p
1137		mount -u /
1138		mount -a
1139		cd src
1140		adjkerntz -i		# if CMOS is wall time
1141	Also, when doing a major release upgrade, it is required that
1142	you boot into single user mode to do the installworld.
1143
1144	[4] Note: This step is non-optional.  Failure to do this step
1145	can result in a significant reduction in the functionality of the
1146	system.  Attempting to do it by hand is not recommended and those
1147	that pursue this avenue should read this file carefully, as well
1148	as the archives of freebsd-current and freebsd-hackers mailing lists
1149	for potential gotchas.  The -U option is also useful to consider.
1150	See mergemaster(8) for more information.
1151
1152	[5] Usually this step is a noop.  However, from time to time
1153	you may need to do this if you get unknown user in the following
1154	step.  It never hurts to do it all the time.  You may need to
1155	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1156	install) after the buildworld before this step if you last updated
1157	from current before 20130425 or from -stable before 20130430.
1158
1159	[6] This only deletes old files and directories. Old libraries
1160	can be deleted by "make delete-old-libs", but you have to make
1161	sure that no program is using those libraries anymore.
1162
1163	[8] In order to have a kernel that can run the 4.x binaries needed to
1164	do an installworld, you must include the COMPAT_FREEBSD4 option in
1165	your kernel.  Failure to do so may leave you with a system that is
1166	hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1167	required to run the 5.x binaries on more recent kernels.  And so on
1168	for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1169
1170	Make sure that you merge any new devices from GENERIC since the
1171	last time you updated your kernel config file.
1172
1173	[9] When checking out sources, you must include the -P flag to have
1174	cvs prune empty directories.
1175
1176	If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1177	"?=" instead of the "=" assignment operator, so that buildworld can
1178	override the CPUTYPE if it needs to.
1179
1180	MAKEOBJDIRPREFIX must be defined in an environment variable, and
1181	not on the command line, or in /etc/make.conf.  buildworld will
1182	warn if it is improperly defined.
1183FORMAT:
1184
1185This file contains a list, in reverse chronological order, of major
1186breakages in tracking -current.  It is not guaranteed to be a complete
1187list of such breakages, and only contains entries since October 10, 2007.
1188If you need to see UPDATING entries from before that date, you will need
1189to fetch an UPDATING file from an older FreeBSD release.
1190
1191Copyright information:
1192
1193Copyright 1998-2009 M. Warner Losh.  All Rights Reserved.
1194
1195Redistribution, publication, translation and use, with or without
1196modification, in full or in part, in any form or format of this
1197document are permitted without further permission from the author.
1198
1199THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1200IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1201WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1202DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1203INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1204(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1205SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1206HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1207STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1208IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1209POSSIBILITY OF SUCH DAMAGE.
1210
1211Contact Warner Losh if you have any questions about your use of
1212this document.
1213
1214$FreeBSD$
1215