UPDATING revision 258714
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 to bootstrap to the tip of
16head, and then rebuild without this option. The bootstrap process from
17older version of current 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
3420131108:
35	The WITHOUT_ATF build knob has been removed and its functionality
36	has been subsumed into the more generic WITHOUT_TESTS.  If you were
37	using the former to disable the build of the ATF libraries, you
38	should change your settings to use the latter.
39
4020131025:
41	The default version of mtree is nmtree which is obtained from
42	NetBSD.  The output is generally the same, but may vary
43	slightly.  If you found you need identical output adding
44	"-F freebsd9" to the command line should do the trick.  For the
45	time being, the old mtree is available as fmtree.
46
4720131014:
48	libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
49	This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
50	1.1.4_8 and verify bsdyml not linked in, before running "make
51	delete-old-libs":
52	  # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
53	  or
54	  # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
55
5620131010:
57	The rc.d/jail script has been updated to support jail(8)
58	configuration file.  The "jail_<jname>_*" rc.conf(5) variables
59	for per-jail configuration are automatically converted to
60	/var/run/jail.<jname>.conf before the jail(8) utility is invoked.
61	This is transparently backward compatible.  See below about some
62	incompatibilities and rc.conf(5) manual page for more details.
63
64	These variables are now deprecated in favor of jail(8) configuration
65	file.  One can use "rc.d/jail config <jname>" command to generate
66	a jail(8) configuration file in /var/run/jail.<jname>.conf without
67	running the jail(8) utility.   The default pathname of the
68	configuration file is /etc/jail.conf and can be specified by
69	using $jail_conf or $jail_<jname>_conf variables.
70
71	Please note that jail_devfs_ruleset accepts an integer at
72	this moment.  Please consider to rewrite the ruleset name
73	with an integer.
74
7520130930:
76	BIND has been removed from the base system.  If all you need
77	is a local resolver, simply enable and start the local_unbound
78	service instead.  Otherwise, several versions of BIND are
79	available in the ports tree.   The dns/bind99 port is one example.
80
81	With this change, nslookup(1) and dig(1) are no longer in the base
82	system.  Users should instead use host(1) which is still
83	in the base system.  Alternatively, nslookup and dig can
84	be obtained by installing the dns/bind-tools port.
85
8620130916:
87	With the addition of unbound(8), a new unbound user is now
88	required during installworld.  "mergemaster -p" can be used to
89	add the user prior to installworld, as documented in the handbook.
90
9120130911:
92	OpenSSH is now built with DNSSEC support, and will by default
93	silently trust signed SSHFP records.  This can be controlled with
94	the VerifyHostKeyDNS client configuration setting.  DNSSEC support
95	can be disabled entirely with the WITHOUT_LDNS option in src.conf.
96
9720130906:
98	The GNU Compiler Collection and C++ standard library (libstdc++)
99	are no longer built by default on platforms where clang is the system
100	compiler.  You can enable them with the WITH_GCC and WITH_GNUCXX
101	options in src.conf.  
102
10320130905:
104	The PROCDESC kernel option is now part of the GENERIC kernel
105	configuration and is required for the rwhod(8) to work.
106	If you are using custom kernel configuration, you should include
107	'options PROCDESC'.
108
10920130905:
110	The API and ABI related to the Capsicum framework was modified
111	in backward incompatible way. The userland libraries and programs
112	have to be recompiled to work with the new kernel. This includes the
113	following libraries and programs, but the whole buildworld is
114	advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
115	kdump, procstat, rwho, rwhod, uniq.
116
11720130903:
118	AES-NI intrinsic support has been added to gcc.  The AES-NI module
119	has been updated to use this support.  A new gcc is required to build
120	the aesni module on both i386 and amd64.
121
12220130821:
123	The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
124	Thus "device padlock_rng" and "device rdrand_rng" should be
125	used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
126
12720130813:
128	WITH_ICONV has been split into two feature sets.  WITH_ICONV now
129	enables just the iconv* functionality and is now on by default.
130	WITH_LIBICONV_COMPAT enables the libiconv api and link time
131	compatability.  Set WITHOUT_ICONV to build the old way.
132	If you have been using WITH_ICONV before, you will very likely
133	need to turn on WITH_LIBICONV_COMPAT.
134
13520130806:
136	INVARIANTS option now enables DEBUG for code with OpenSolaris and
137	Illumos origin, including ZFS.  If you have INVARIANTS in your
138	kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
139	explicitly.
140	DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
141	locks if WITNESS option was set.  Because that generated a lot of
142	witness(9) reports and all of them were believed to be false
143	positives, this is no longer done.  New option OPENSOLARIS_WITNESS
144	can be used to achieve the previous behavior.
145
14620130806:
147	Timer values in IPv6 data structures now use time_uptime instead
148	of time_second.  Although this is not a user-visible functional
149	change, userland utilities which directly use them---ndp(8),
150	rtadvd(8), and rtsold(8) in the base system---need to be updated
151	to r253970 or later.
152
15320130802:
154	find -delete can now delete the pathnames given as arguments,
155	instead of only files found below them or if the pathname did
156	not contain any slashes. Formerly, the following error message
157	would result:
158
159	find: -delete: <path>: relative path potentially not safe
160
161	Deleting the pathnames given as arguments can be prevented
162	without error messages using -mindepth 1 or by changing
163	directory and passing "." as argument to find. This works in the
164	old as well as the new version of find.
165
16620130726:
167	Behavior of devfs rules path matching has been changed.
168	Pattern is now always matched against fully qualified devfs
169	path and slash characters must be explicitly matched by
170	slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
171	subdirectories must be reviewed.
172
17320130716:
174	The default ARM ABI has changed to the ARM EABI. The old ABI is
175	incompatible with the ARM EABI and all programs and modules will
176	need to be rebuilt to work with a new kernel.
177
178	To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
179
180	NOTE: Support for the old ABI will be removed in the future and
181	users are advised to upgrade.
182
18320130709:
184	pkg_install has been disconnected from the build if you really need it
185	you should add WITH_PKGTOOLS in your src.conf(5).
186
18720130709:
188	Most of network statistics structures were changed to be able
189	keep 64-bits counters. Thus all tools, that work with networking
190	statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
191
19220130629:
193	Fix targets that run multiple make's to use && rather than ;
194	so that subsequent steps depend on success of previous.
195
196	NOTE: if building 'universe' with -j* on stable/8 or stable/9
197	it would be better to start the build using bmake, to avoid
198	overloading the machine.
199
20020130618:
201	Fix a bug that allowed a tracing process (e.g. gdb) to write
202	to a memory-mapped file in the traced process's address space
203	even if neither the traced process nor the tracing process had
204	write access to that file.
205
20620130615:
207	CVS has been removed from the base system.  An exact copy
208	of the code is available from the devel/cvs port.
209
21020130613:
211	Some people report the following error after the switch to bmake:
212
213		make: illegal option -- J
214		usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
215			...
216		*** [buildworld] Error code 2
217
218	this likely due to an old instance of make in
219	${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
220	which src/Makefile will use that blindly, if it exists, so if
221	you see the above error:
222
223		rm -rf `make -V MAKEPATH`
224
225	should resolve it.
226
22720130516:
228	Use bmake by default.
229	Whereas before one could choose to build with bmake via
230	-DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
231	make. The goal is to remove these knobs for 10-RELEASE.
232
233	It is worth noting that bmake (like gmake) treats the command
234	line as the unit of failure, rather than statements within the
235	command line.  Thus '(cd some/where && dosomething)' is safer
236	than 'cd some/where; dosomething'. The '()' allows consistent
237	behavior in parallel build.
238
23920130429:
240        Fix a bug that allows NFS clients to issue READDIR on files.
241
24220130426:
243	The WITHOUT_IDEA option has been removed because
244	the IDEA patent expired.
245
24620130426:
247	The sysctl which controls TRIM support under ZFS has been renamed
248	from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
249	enabled by default.
250
25120130425:
252	The mergemaster command now uses the default MAKEOBJDIRPREFIX
253	rather than creating it's own in the temporary directory in
254	order allow access to bootstrapped versions of tools such as
255	install and mtree.  When upgrading from version of FreeBSD where
256	the install command does not support -l, you will need to
257	install a new mergemaster command if mergemaster -p is required.
258	This can be accomplished with the command (cd src/usr.sbin/mergemaster
259	&& make install).
260
26120130404:
262	Legacy ATA stack, disabled and replaced by new CAM-based one since
263	FreeBSD 9.0, completely removed from the sources.  Kernel modules
264	atadisk and atapi*, user-level tools atacontrol and burncd are
265	removed.  Kernel option `options ATA_CAM` is now permanently enabled
266	and removed.
267
26820130319:
269	SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
270	and socketpair(2). Software, in particular Kerberos, may
271	automatically detect and use these during building. The resulting
272	binaries will not work on older kernels.
273
27420130308:
275	CTL_DISABLE has also been added to the sparc64 GENERIC (for further
276	information, see the respective 20130304 entry).
277
27820130304:
279	Recent commits to callout(9) changed the size of struct callout,
280	so the KBI is probably heavily disturbed. Also, some functions
281	in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
282	by macros. Every kernel module using it won't load, so rebuild
283	is requested.
284
285	The ctl device has been re-enabled in GENERIC for i386 and amd64,
286	but does not initialize by default (because of the new CTL_DISABLE
287	option) to save memory.  To re-enable it, remove the CTL_DISABLE
288	option from the kernel config file or set kern.cam.ctl.disable=0
289	in /boot/loader.conf.
290
29120130301:
292	The ctl device has been disabled in GENERIC for i386 and amd64.
293	This was done due to the extra memory being allocated at system
294	initialisation time by the ctl driver which was only used if
295	a CAM target device was created.  This makes a FreeBSD system
296	unusable on 128MB or less of RAM.
297
29820130208:
299	A new compression method (lz4) has been merged to -HEAD.  Please
300	refer to zpool-features(7) for more information.
301
302	Please refer to the "ZFS notes" section of this file for information
303	on upgrading boot ZFS pools.
304
30520130129:
306	A BSD-licensed patch(1) variant has been added and is installed
307	as bsdpatch, being the GNU version the default patch.
308	To inverse the logic and use the BSD-licensed one as default,
309	while having the GNU version installed as gnupatch, rebuild
310	and install world with the WITH_BSD_PATCH knob set.
311
31220130121:
313	Due to the use of the new -l option to install(1) during build
314	and install, you must take care not to directly set the INSTALL
315	make variable in your /etc/make.conf, /etc/src.conf, or on the
316	command line.  If you wish to use the -C flag for all installs
317	you may be able to add INSTALL+=-C to /etc/make.conf or
318	/etc/src.conf.
319
32020130118:
321	The install(1) option -M has changed meaning and now takes an
322	argument that is a file or path to append logs to.  In the
323	unlikely event that -M was the last option on the command line
324	and the command line contained at least two files and a target
325	directory the first file will have logs appended to it.  The -M
326	option served little practical purpose in the last decade so its
327	use is expected to be extremely rare.
328
32920121223:
330	After switching to Clang as the default compiler some users of ZFS
331	on i386 systems started to experience stack overflow kernel panics.
332	Please consider using 'options KSTACK_PAGES=4' in such configurations.
333
33420121222:
335	GEOM_LABEL now mangles label names read from file system metadata.
336	Mangling affect labels containing spaces, non-printable characters,
337	'%' or '"'. Device names in /etc/fstab and other places may need to
338	be updated.
339
34020121217:
341	By default, only the 10 most recent kernel dumps will be saved.  To
342	restore the previous behaviour (no limit on the number of kernel dumps
343	stored in the dump directory) add the following line to /etc/rc.conf:
344
345		savecore_flags=""
346
34720121201:
348	With the addition of auditdistd(8), a new auditdistd user is now
349	required during installworld.  "mergemaster -p" can be used to
350	add the user prior to installworld, as documented in the handbook.
351
35220121117:
353	The sin6_scope_id member variable in struct sockaddr_in6 is now
354	filled by the kernel before passing the structure to the userland via
355	sysctl or routing socket.  This means the KAME-specific embedded scope
356	id in sin6_addr.s6_addr[2] is always cleared in userland application.
357	This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
358	__FreeBSD_version is bumped to 1000025.
359
36020121105:
361	On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
362	This means that the world and kernel will be compiled with clang
363	and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
364	and /usr/bin/cpp.  To disable this behavior and revert to building
365	with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
366	of current may need to bootstrap WITHOUT_CLANG first if the clang
367	build fails (its compatibility window doesn't extend to the 9 stable
368	branch point).
369
37020121102:
371	The IPFIREWALL_FORWARD kernel option has been removed. Its
372	functionality now turned on by default.
373
37420121023:
375	The ZERO_COPY_SOCKET kernel option has been removed and
376	split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
377	NB: SOCKET_SEND_COW uses the VM page based copy-on-write
378	mechanism which is not safe and may result in kernel crashes.
379	NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
380	driver supports disposeable external page sized mbuf storage.
381	Proper replacements for both zero-copy mechanisms are under
382	consideration and will eventually lead to complete removal
383	of the two kernel options.
384
38520121023:
386	The IPv4 network stack has been converted to network byte
387	order. The following modules need to be recompiled together
388	with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
389	pf(4), ipfw(4), ng_ipfw(4), stf(4).
390
39120121022:
392	Support for non-MPSAFE filesystems was removed from VFS. The
393	VFS_VERSION was bumped, all filesystem modules shall be
394	recompiled.
395
39620121018:
397	All the non-MPSAFE filesystems have been disconnected from
398	the build. The full list includes: codafs, hpfs, ntfs, nwfs,
399	portalfs, smbfs, xfs.
400
40120121016:
402	The interface cloning API and ABI has changed. The following
403	modules need to be recompiled together with kernel:
404	ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
405	vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
406	faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
407
40820121015:
409	The sdhci driver was split in two parts: sdhci (generic SD Host
410	Controller logic) and sdhci_pci (actual hardware driver).
411	No kernel config modifications are required, but if you
412	load sdhc as a module you must switch to sdhci_pci instead.
413
41420121014:
415	Import the FUSE kernel and userland support into base system.
416
41720121013:
418	The GNU sort(1) program has been removed since the BSD-licensed
419	sort(1) has been the default for quite some time and no serious
420	problems have been reported.  The corresponding WITH_GNU_SORT
421	knob has also gone.
422
42320121006:
424	The pfil(9) API/ABI for AF_INET family has been changed. Packet
425	filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
426	with new kernel.
427
42820121001:
429	The net80211(4) ABI has been changed to allow for improved driver
430	PS-POLL and power-save support.  All wireless drivers need to be
431	recompiled to work with the new kernel.
432
43320120913:
434	The random(4) support for the VIA hardware random number
435	generator (`PADLOCK') is no longer enabled unconditionally.
436	Add the padlock_rng device in the custom kernel config if
437	needed.  The GENERIC kernels on i386 and amd64 do include the
438	device, so the change only affects the custom kernel
439	configurations.
440
44120120908:
442	The pf(4) packet filter ABI has been changed. pfctl(8) and
443	snmp_pf module need to be recompiled to work with new kernel.
444
44520120828:
446	A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
447	to -HEAD. Pools that have empty_bpobj in active state can not be
448	imported read-write with ZFS implementations that do not support
449	this feature. For more information read the zpool-features(5)
450	manual page.
451
45220120727:
453	The sparc64 ZFS loader has been changed to no longer try to auto-
454	detect ZFS providers based on diskN aliases but now requires these
455	to be explicitly listed in the OFW boot-device environment variable. 
456
45720120712:
458	The OpenSSL has been upgraded to 1.0.1c.  Any binaries requiring
459	libcrypto.so.6 or libssl.so.6 must be recompiled.  Also, there are
460	configuration changes.  Make sure to merge /etc/ssl/openssl.cnf.
461
46220120712:
463	The following sysctls and tunables have been renamed for consistency
464	with other variables:
465	  kern.cam.da.da_send_ordered   -> kern.cam.da.send_ordered
466	  kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
467
46820120628:
469	The sort utility has been replaced with BSD sort.  For now, GNU sort
470	is also available as "gnusort" or the default can be set back to
471	GNU sort by setting WITH_GNU_SORT.  In this case, BSD sort will be
472	installed as "bsdsort".
473
47420120611:
475	A new version of ZFS (pool version 5000) has been merged to -HEAD.
476	Starting with this version the old system of ZFS pool versioning
477	is superseded by "feature flags". This concept enables forward
478	compatibility against certain future changes in functionality of ZFS
479	pools. The first read-only compatible "feature flag" for ZFS pools
480	is named "com.delphix:async_destroy". For more information
481	read the new zpool-features(5) manual page.
482	Please refer to the "ZFS notes" section of this file for information
483	on upgrading boot ZFS pools.
484
48520120417:
486	The malloc(3) implementation embedded in libc now uses sources imported
487	as contrib/jemalloc.  The most disruptive API change is to
488	/etc/malloc.conf.  If your system has an old-style /etc/malloc.conf,
489	delete it prior to installworld, and optionally re-create it using the
490	new format after rebooting.  See malloc.conf(5) for details
491	(specifically the TUNING section and the "opt.*" entries in the MALLCTL
492	NAMESPACE section).
493
49420120328:
495	Big-endian MIPS TARGET_ARCH values no longer end in "eb".  mips64eb
496	is now spelled mips64.  mipsn32eb is now spelled mipsn32.  mipseb is
497	now spelled mips.  This is to aid compatibility with third-party
498	software that expects this naming scheme in uname(3).  Little-endian
499	settings are unchanged. If you are updating a big-endian mips64 machine
500	from before this change, you may need to set MACHINE_ARCH=mips64 in
501	your environment before the new build system will recognize your machine.
502
50320120306:
504	Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
505	platforms.
506
50720120229:
508	Now unix domain sockets behave "as expected" on	nullfs(5). Previously
509	nullfs(5) did not pass through all behaviours to the underlying layer,
510	as a result if we bound to a socket on the lower layer we could connect
511	only to the lower path; if we bound to the upper layer we could connect
512	only to	the upper path. The new behavior is one can connect to both the
513	lower and the upper paths regardless what layer path one binds to.
514
51520120211:
516	The getifaddrs upgrade path broken with 20111215 has been restored.
517	If you have upgraded in between 20111215 and 20120209 you need to
518	recompile libc again with your kernel.  You still need to recompile
519	world to be able to configure CARP but this restriction already
520	comes from 20111215.
521
52220120114:
523	The set_rcvar() function has been removed from /etc/rc.subr.  All
524	base and ports rc.d scripts have been updated, so if you have a
525	port installed with a script in /usr/local/etc/rc.d you can either
526	hand-edit the rcvar= line, or reinstall the port.
527
528	An easy way to handle the mass-update of /etc/rc.d:
529	rm /etc/rc.d/* && mergemaster -i
530
53120120109:
532	panic(9) now stops other CPUs in the SMP systems, disables interrupts
533	on the current CPU and prevents other threads from running.
534	This behavior can be reverted using the kern.stop_scheduler_on_panic
535	tunable/sysctl.
536	The new behavior can be incompatible with kern.sync_on_panic.
537
53820111215:
539	The carp(4) facility has been changed significantly. Configuration
540	of the CARP protocol via ifconfig(8) has changed, as well as format
541	of CARP events submitted to devd(8) has changed. See manual pages
542	for more information. The arpbalance feature of carp(4) is currently
543	not supported anymore.
544
545	Size of struct in_aliasreq, struct in6_aliasreq has changed. User
546	utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
547	need to be recompiled.
548
54920111122:
550	The acpi_wmi(4) status device /dev/wmistat has been renamed to
551	/dev/wmistat0.
552
55320111108:
554	The option VFS_ALLOW_NONMPSAFE option has been added in order to
555	explicitely support non-MPSAFE filesystems.
556	It is on by default for all supported platform at this present
557	time.
558
55920111101:
560	The broken amd(4) driver has been replaced with esp(4) in the amd64,
561	i386 and pc98 GENERIC kernel configuration files.
562
56320110930:
564	sysinstall has been removed
565
56620110923:
567	The stable/9 branch created in subversion.  This corresponds to the
568	RELENG_9 branch in CVS.
569
57020110913:
571	This commit modifies vfs_register() so that it uses a hash
572	calculation to set vfc_typenum, which is enabled by default.
573	The first time a system is booted after this change, the
574	vfc_typenum values will change for all file systems. The
575	main effect of this is a change to the NFS server file handles
576	for file systems that use vfc_typenum in their fsid, such as ZFS.
577	It will, however, prevent vfc_typenum from changing when file
578	systems are loaded in a different order for subsequent reboots.
579	To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
580	until you are ready to remount all NFS clients after a reboot.
581
58220110828:
583	Bump the shared library version numbers for libraries that
584	do not use symbol versioning, have changed the ABI compared
585	to stable/8 and which shared library version was not bumped.
586	Done as part of 9.0-RELEASE cycle.
587
58820110815:
589	During the merge of Capsicum features, the fget(9) KPI was modified.
590	This may require the rebuilding of out-of-tree device drivers --
591	issues have been reported specifically with the nVidia device driver.
592	__FreeBSD_version is bumped to 900041.
593
594	Also, there is a period between 20110811 and 20110814 where the
595	special devices /dev/{stdin,stdout,stderr} did not work correctly.
596	Building world from a kernel during that window may not work.
597
59820110628:
599	The packet filter (pf) code has been updated to OpenBSD 4.5.
600	You need to update userland tools to be in sync with kernel.
601	This update breaks backward compatibility with earlier pfsync(4)
602	versions.  Care must be taken when updating redundant firewall setups.
603
60420110608:
605	The following sysctls and tunables are retired on x86 platforms:
606		machdep.hlt_cpus
607		machdep.hlt_logical_cpus
608	The following sysctl is retired:
609		machdep.hyperthreading_allowed
610	The sysctls were supposed to provide a way to dynamically offline and
611	online selected CPUs on x86 platforms, but the implementation has not
612	been reliable especially with SCHED_ULE scheduler.
613	machdep.hyperthreading_allowed tunable is still available to ignore
614	hyperthreading CPUs at OS level.
615	Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
616	where X is an APIC ID of a CPU.  Be advised, though, that disabling
617	CPUs in non-uniform fashion will result in non-uniform topology and
618	may lead to sub-optimal system performance with SCHED_ULE, which is
619	a default scheduler.
620
62120110607:
622	cpumask_t type is retired and cpuset_t is used in order to describe
623	a mask of CPUs.
624
62520110531:
626	Changes to ifconfig(8) for dynamic address family detection mandate
627	that you are running a kernel of 20110525 or later.  Make sure to
628	follow the update procedure to boot a new kernel before installing
629	world.
630
63120110513:
632	Support for sun4v architecture is officially dropped
633
63420110503:
635	Several KPI breaking changes have been committed to the mii(4) layer,
636	the PHY drivers and consequently some Ethernet drivers using mii(4).
637	This means that miibus.ko and the modules of the affected Ethernet
638	drivers need to be recompiled.
639
640	Note to kernel developers: Given that the OUI bit reversion problem
641	was fixed as part of these changes all mii(4) commits related to OUIs,
642	i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
643	handling, no longer can be merged verbatim to stable/8 and previous
644	branches.
645
64620110430:
647	Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
648	into their kernel configurations along with 'device pci'.
649
65020110427:
651	The default NFS client is now the new NFS client, so fstype "newnfs"
652	is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
653	Although mounts via fstype "nfs" will usually work without userland
654	changes, it is recommended that the mount(8) and mount_nfs(8)
655	commands be rebuilt from sources and that a link to mount_nfs called
656	mount_oldnfs be created. The new client is compiled into the
657	kernel with "options NFSCL" and this is needed for diskless root
658	file systems. The GENERIC kernel configs have been changed to use
659	NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
660	To use the regular/old client, you can "mount -t oldnfs ...". For
661	a diskless root file system, you must also include a line like:
662	
663	vfs.root.mountfrom="oldnfs:"
664
665	in the boot/loader.conf on the root fs on the NFS server to make
666	a diskless root fs use the old client.
667
66820110424:
669	The GENERIC kernels for all architectures now default to the new
670	CAM-based ATA stack. It means that all legacy ATA drivers were
671	removed and replaced by respective CAM drivers. If you are using
672	ATA device names in /etc/fstab or other places, make sure to update
673	them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
674	where 'Y's are the sequential numbers starting from zero for each type
675	in order of detection, unless configured otherwise with tunables,
676	see cam(4)). There will be symbolic links created in /dev/ to map
677	old adX devices to the respective adaY. They should provide basic
678	compatibility for file systems mounting in most cases, but they do
679	not support old user-level APIs and do not have respective providers
680	in GEOM. Consider using updated management tools with new device names.
681
682	It is possible to load devices ahci, ata, siis and mvs as modules,
683	but option ATA_CAM should remain in kernel configuration to make ata
684	module work as CAM driver supporting legacy ATA controllers. Device ata
685	still can be used in modular fashion (atacore + ...). Modules atadisk
686	and atapi* are not used and won't affect operation in ATA_CAM mode.
687	Note that to use CAM-based ATA kernel should include CAM devices
688	scbus, pass, da (or explicitly ada), cd and optionally others. All of
689	them are parts of the cam module.
690
691	ataraid(4) functionality is now supported by the RAID GEOM class.
692	To use it you can load geom_raid kernel module and use graid(8) tool
693	for management. Instead of /dev/arX device names, use /dev/raid/rX.
694
695	No kernel config options or code have been removed, so if a problem
696	arises, please report it and optionally revert to the old ATA stack.
697	In order to do it you can remove from the kernel config:
698	    options        ATA_CAM
699	    device         ahci
700	    device         mvs
701	    device         siis
702	, and instead add back:
703	    device         atadisk         # ATA disk drives
704	    device         ataraid         # ATA RAID drives
705	    device         atapicd         # ATAPI CDROM drives
706	    device         atapifd         # ATAPI floppy drives
707	    device         atapist         # ATAPI tape drives
708
70920110423:
710	The default NFS server has been changed to the new server, which
711	was referred to as the experimental server. If you need to switch
712	back to the old NFS server, you must now put the "-o" option on
713	both the mountd and nfsd commands. This can be done using the
714	mountd_flags and nfs_server_flags rc.conf variables until an
715	update to the rc scripts is committed, which is coming soon.
716
71720110418:
718	The GNU Objective-C runtime library (libobjc), and other Objective-C
719	related components have been removed from the base system.  If you
720	require an Objective-C library, please use one of the available ports.
721
72220110331:
723	ath(4) has been split into bus- and device- modules. if_ath contains
724	the HAL, the TX rate control and the network device code. if_ath_pci
725	contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
726	contains the AHB glue. Users need to load both if_ath_pci and if_ath
727	in order to use ath on everything else.
728
729	TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
730	need to load if_ath and if_ath_pci for ath(4) operation.
731
73220110314:
733	As part of the replacement of sysinstall, the process of building
734	release media has changed significantly. For details, please re-read
735	release(7), which has been updated to reflect the new build process.
736
73720110218:
738	GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD.  This
739	is the last available version under GPLv2.  It brings a number of new
740	features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
741	4.1 and SSE 4.2), better support for powerpc64, a number of new
742	directives, and lots of other small improvements.  See the ChangeLog
743	file in contrib/binutils for the full details.
744
74520110218:
746	IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
747	compliant, and will now use half of hash for authentication.
748	This will break interoperability with all stacks (including all
749	actual FreeBSD versions) who implement
750	draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
751	authentication).
752	The only workaround with such peers is to use another HMAC
753	algorithm for IPsec ("phase 2") authentication.
754
75520110207:
756	Remove the uio_yield prototype and symbol.  This function has
757	been misnamed since it was introduced and should not be
758	globally exposed with this name.  The equivalent functionality
759	is now available using kern_yield(curthread->td_user_pri).
760	The function remains undocumented.
761
76220110112:
763	A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
764	symmetric with the existing SYSCTL_[ADD_]QUAD.  Type checking
765	for scalar sysctls is defined but disabled.  Code that needs
766	UQUAD to pass the type checking that must compile on older
767	systems where the define is not present can check against
768	__FreeBSD_version >= 900030.
769
770	The system dialog(1) has been replaced with a new version previously
771	in ports as devel/cdialog. dialog(1) is mostly command-line compatible
772	with the previous version, but the libdialog associated with it has
773	a largely incompatible API. As such, the original version of libdialog
774	will be kept temporarily as libodialog, until its base system consumers
775	are replaced or updated. Bump __FreeBSD_version to 900030.
776
77720110103:
778	If you are trying to run make universe on a -stable system, and you get
779	the following warning:
780	"Makefile", line 356: "Target architecture for i386/conf/GENERIC 
781	unknown.  config(8) likely too old."
782	or something similar to it, then you must upgrade your -stable system
783	to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
784	stable/8) or build the config from the latest stable/8 branch and
785	install it on your system.
786
787	Prior to this date, building a current universe on 8-stable system from
788	between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
789	error in the first kernel build phase.  A new config on those old 
790	systems will fix that problem for older versions of -current.
791
79220101228:
793	The TCP stack has been modified to allow Khelp modules to interact with
794	it via helper hook points and store per-connection data in the TCP
795	control block. Bump __FreeBSD_version to 900029. User space tools that
796	rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
797	be recompiled.
798
79920101114:
800	Generic IEEE 802.3 annex 31B full duplex flow control support has been
801	added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
802	with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
803	to take advantage of it instead of using custom implementations.  This
804	means that these drivers now no longer unconditionally advertise
805	support for flow control but only do so if flow control is a selected
806	media option.  This was implemented in the generic support that way in
807	order to allow flow control to be switched on and off via ifconfig(8)
808	with the PHY specific default to typically off in order to protect
809	from unwanted effects.  Consequently, if you used flow control with
810	one of the above mentioned drivers you now need to explicitly enable
811	it, for example via:
812		ifconfig bge0 media auto mediaopt flowcontrol
813
814	Along with the above mentioned changes generic support for setting
815	1000baseT master mode also has been added and brgphy(4), ciphy(4),
816	e1000phy(4) as well as ip1000phy(4) have been converted to take
817	advantage of it.  This means that these drivers now no longer take the
818	link0 parameter for selecting master mode but the master media option
819	has to be used instead, for example like in the following:
820		ifconfig bge0 media 1000baseT mediaopt full-duplex,master
821
822	Selection of master mode now is also available with all other PHY
823	drivers supporting 1000baseT.
824
82520101111:
826	The TCP stack has received a significant update to add support for
827	modularised congestion control and generally improve the clarity of
828	congestion control decisions. Bump __FreeBSD_version to 900025. User
829	space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
830	sockstat) need to be recompiled.
831
83220101002:
833	The man(1) utility has been replaced by a new version that no longer
834	uses /etc/manpath.config. Please consult man.conf(5) for how to
835	migrate local entries to the new format.
836
83720100928:
838	The copyright strings printed by login(1) and sshd(8) at the time of a
839	new connection have been removed to follow other operating systems and
840	upstream sshd.
841
84220100915:
843	A workaround for a fixed ld bug has been removed in kernel code,
844	so make sure that your system ld is built from sources after
845	revision 210245 from 2010-07-19 (r211583 if building head kernel
846	on stable/8, r211584 for stable/7; both from 2010-08-21).
847	A symptom of incorrect ld version is different addresses for
848	set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
849
85020100913:
851	The $ipv6_prefer variable in rc.conf(5) has been split into
852	$ip6addrctl_policy and $ipv6_activate_all_interfaces.
853
854	The $ip6addrctl_policy is a variable to choose a pre-defined
855	address selection policy set by ip6addrctl(8).  A value
856	"ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified.  The
857	default is "AUTO".
858
859	The $ipv6_activate_all_interfaces specifies whether IFDISABLED
860	flag (see an entry of 20090926) is set on an interface with no
861	corresponding $ifconfig_IF_ipv6 line.  The default is "NO" for
862	security reason.  If you want IPv6 link-local address on all
863	interfaces by default, set this to "YES".
864
865	The old ipv6_prefer="YES" is equivalent to
866	ipv6_activate_all_interfaces="YES" and
867	ip6addrctl_policy="ipv6_prefer".
868
86920100913:
870	DTrace has grown support for userland tracing. Due to this, DTrace is
871	now i386 and amd64 only.
872	dtruss(1) is now installed by default on those systems and a new
873	kernel module is needed for userland tracing: fasttrap.
874	No changes to your kernel config file are necessary to enable
875	userland tracing, but you might consider adding 'STRIP=' and
876	'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
877	to have informative userland stack traces in DTrace (ustack).
878
87920100725:
880	The acpi_aiboost(4) driver has been removed in favor of the new
881	aibs(4) driver. You should update your kernel configuration file.
882
88320100722:
884	BSD grep has been imported to the base system and it is built by
885	default.  It is completely BSD licensed, highly GNU-compatible, uses
886	less memory than its GNU counterpart and has a small codebase.
887	However, it is slower than its GNU counterpart, which is mostly
888	noticeable for larger searches, for smaller ones it is measurable
889	but not significant.  The reason is complex, the most important factor
890	is that we lack a modern and efficient regex library and GNU
891	overcomes this by optimizing the searches internally.  Future work
892	on improving the regex performance is planned, for the meantime,
893	users that need better performance, can build GNU grep instead by
894	setting the WITH_GNU_GREP knob.
895
89620100713:
897	Due to the import of powerpc64 support, all existing powerpc kernel
898	configuration files must be updated with a machine directive like this:
899	    machine powerpc powerpc
900
901	In addition, an updated config(8) is required to build powerpc kernels
902	after this change.
903
90420100713:
905	A new version of ZFS (version 15) has been merged to -HEAD.
906	This version uses a python library for the following subcommands:
907	zfs allow, zfs unallow, zfs groupspace, zfs userspace.
908	For full functionality of these commands the following port must
909	be installed: sysutils/py-zfs
910
91120100429:
912	'vm_page's are now hashed by physical address to an array of mutexes.
913	Currently this is only used to serialize access to hold_count. Over 
914	time the page queue mutex will be peeled away. This changes the size
915	of pmap on every architecture. And requires all callers of vm_page_hold
916	and vm_page_unhold to be updated. 
917 
91820100402:
919	WITH_CTF can now be specified in src.conf (not recommended, there
920	are some problems with static executables), make.conf (would also
921	affect ports which do not use GNU make and do not override the
922	compile targets) or in the kernel config (via "makeoptions
923	WITH_CTF=yes").
924	When WITH_CTF was specified there before this was silently ignored,
925	so make sure that WITH_CTF is not used in places which could lead
926	to unwanted behavior.
927
92820100311:
929	The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
930	to allow 32-bit compatibility on non-x86 platforms. All kernel
931	configurations on amd64 and ia64 platforms using these options must
932	be modified accordingly.
933
93420100113:
935	The utmp user accounting database has been replaced with utmpx,
936	the user accounting interface standardized by POSIX.
937	Unfortunately the semantics of utmp and utmpx don't match,
938	making it practically impossible to support both interfaces.
939	The user accounting database is used by tools like finger(1),
940	last(1), talk(1), w(1) and ac(8).
941
942	All applications in the base system use utmpx.  This means only
943	local binaries (e.g. from the ports tree) may still use these
944	utmp database files.  These applications must be rebuilt to make
945	use of utmpx.
946
947	After the system has been upgraded, it is safe to remove the old
948	log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
949	assuming their contents is of no importance anymore.  Old wtmp
950	databases can only be used by last(1) and ac(8) after they have
951	been converted to the new format using wtmpcvt(1).
952
95320100108:
954	Introduce the kernel thread "deadlock resolver" (which can be enabled
955	via the DEADLKRES option, see NOTES for more details) and the
956	sleepq_type() function for sleepqueues.
957
95820091202:
959	The rc.firewall and rc.firewall6 were unified, and
960	rc.firewall6 and rc.d/ip6fw were removed.
961	According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
962	variables are obsoleted.  Instead, the following new rc
963	variables are added to rc.d/ipfw:
964
965		firewall_client_net_ipv6, firewall_simple_iif_ipv6,
966		firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
967		firewall_simple_onet_ipv6, firewall_trusted_ipv6
968
969	The meanings correspond to the relevant IPv4 variables.
970
97120091125:
972	8.0-RELEASE.
973
97420091113:
975	The default terminal emulation for syscons(4) has been changed
976	from cons25 to xterm on all platforms except pc98.  This means
977	that the /etc/ttys file needs to be updated to ensure correct
978	operation of applications on the console.
979
980	The terminal emulation style can be toggled per window by using
981	vidcontrol(1)'s -T flag.  The TEKEN_CONS25 kernel configuration
982	options can be used to change the compile-time default back to
983	cons25.
984
985	To prevent graphical artifacts, make sure the TERM environment
986	variable is set to match the terminal emulation that is being
987	performed by syscons(4).
988
98920091109:
990	The layout of the structure ieee80211req_scan_result has changed.
991	Applications that require wireless scan results (e.g. ifconfig(8))
992	from net80211 need to be recompiled.
993
994	Applications such as wpa_supplicant(8) may require a full world
995	build without using NO_CLEAN in order to get synchronized with the
996	new structure.
997
99820091025:
999	The iwn(4) driver has been updated to support the 5000 and 5150 series.
1000	There's one kernel module for each firmware. Adding "device iwnfw"
1001	to the kernel configuration file means including all three firmware
1002	images inside the kernel. If you want to include just the one for
1003	your wireless card, use the devices iwn4965fw, iwn5000fw or
1004	iwn5150fw.
1005
100620090926:
1007	The rc.d/network_ipv6, IPv6 configuration script has been integrated
1008	into rc.d/netif.  The changes are the following:
1009
1010	1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1011	   for IPv4.  For aliases, $ifconfig_IF_aliasN should be used.
1012	   Note that both variables need the "inet6" keyword at the head.
1013
1014	   Do not set $ipv6_network_interfaces manually if you do not
1015	   understand what you are doing.  It is not needed in most cases. 
1016
1017	   $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1018	   they are obsolete.
1019
1020	2. $ipv6_enable is obsolete.  Use $ipv6_prefer and
1021	   "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1022
1023	   If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1024	   all configured interfaces have "inet6 accept_rtadv" in the
1025	   $ifconfig_IF_ipv6.  These are for backward compatibility.
1026
1027	3. A new variable $ipv6_prefer has been added.  If NO, IPv6
1028	   functionality of interfaces with no corresponding
1029	   $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1030	   and the default address selection policy of ip6addrctl(8) 
1031	   is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1032	   Note that if you want to configure IPv6 functionality on the
1033	   disabled interfaces after boot, first you need to clear the flag by
1034	   using ifconfig(8) like:
1035
1036		ifconfig em0 inet6 -ifdisabled
1037
1038	   If YES, the default address selection policy is set as
1039	   IPv6-preferred.
1040
1041	   The default value of $ipv6_prefer is NO.
1042
1043	4. If your system need to receive Router Advertisement messages,
1044	   define "inet6 accept_rtadv" in $ifconfig_IF_ipv6.  The rc(8)
1045	   scripts automatically invoke rtsol(8) when the interface becomes
1046	   UP.  The Router Advertisement messages are used for SLAAC
1047	   (State-Less Address AutoConfiguration).
1048
104920090922:
1050	802.11s D3.03 support was committed. This is incompatible with the
1051	previous code, which was based on D3.0.
1052
105320090912:
1054	A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1055	of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1056	control whether accepting Router Advertisement messages or not.
1057	Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1058	a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1059	The ifconfig(8) utility now supports these flags.
1060
106120090910:
1062	ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1063	mount(8) and -a option for df(1) to see them.
1064
106520090825:
1066	The old tunable hw.bus.devctl_disable has been superseded by
1067	hw.bus.devctl_queue.  hw.bus.devctl_disable=1 in loader.conf should be
1068	replaced by hw.bus.devctl_queue=0.  The default for this new tunable
1069	is 1000.
1070
107120090813:
1072	Remove the option STOP_NMI.  The default action is now to use NMI only
1073	for KDB via the newly introduced function stop_cpus_hard() and
1074	maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1075
107620090803:
1077	The stable/8 branch created in subversion.  This corresponds to the
1078	RELENG_8 branch in CVS.
1079
108020090719:
1081	Bump the shared library version numbers for all libraries that do not
1082	use symbol versioning as part of the 8.0-RELEASE cycle.  Bump
1083	__FreeBSD_version to 800105.
1084
108520090714:
1086	Due to changes in the implementation of virtual network stack support,
1087	all network-related kernel modules must be recompiled.  As this change
1088	breaks the ABI, bump __FreeBSD_version to 800104.
1089
109020090713:
1091	The TOE interface to the TCP syncache has been modified to remove
1092	struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1093	The cxgb driver is the only TOE consumer affected by this change, and
1094	needs to be recompiled along with the kernel. As this change breaks
1095	the ABI, bump __FreeBSD_version to 800103.
1096
109720090712: 
1098	Padding has been added to struct tcpcb, sackhint and tcpstat in
1099	<netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1100	maintaining the ABI. However, this change breaks the ABI, so bump
1101	__FreeBSD_version to 800102. User space tools that rely on the size of
1102	any of these structs (e.g. sockstat) need to be recompiled.
1103
110420090630:
1105	The NFS_LEGACYRPC option has been removed along with the old kernel
1106	RPC implementation that this option selected. Kernel configurations
1107	may need to be adjusted.
1108
110920090629:
1110	The network interface device nodes at /dev/net/<interface> have been
1111	removed.  All ioctl operations can be performed the normal way using
1112	routing sockets.  The kqueue functionality can generally be replaced
1113	with routing sockets.
1114
111520090628:
1116	The documentation from the FreeBSD Documentation Project (Handbook,
1117	FAQ, etc.) is now installed via packages by sysinstall(8) and under
1118	the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1119
112020090624:
1121	The ABI of various structures related to the SYSV IPC API have been
1122	changed.  As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1123	options now all require COMPAT_FREEBSD7.  Bump __FreeBSD_version to
1124	800100.
1125
112620090622:
1127	Layout of struct vnet has changed as routing related variables were
1128	moved to their own Vimage module. Modules need to be recompiled.  Bump
1129	__FreeBSD_version to 800099.
1130
113120090619:
1132	NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1133	respectively.  As long as no more than 16 groups per process are used,
1134	no changes should be visible.  When more than 16 groups are used, old
1135	binaries may fail if they call getgroups() or getgrouplist() with
1136	statically sized storage.  Recompiling will work around this, but
1137	applications should be modified to use dynamically allocated storage
1138	for group arrays as POSIX.1-2008 does not cap an implementation's
1139	number of supported groups at NGROUPS_MAX+1 as previous versions did.
1140
1141	NFS and portalfs mounts may also be affected as the list of groups is
1142	truncated to 16.  Users of NFS who use more than 16 groups, should
1143	take care that negative group permissions are not used on the exported
1144	file systems as they will not be reliable unless a GSSAPI based
1145	authentication method is used.
1146
114720090616: 
1148	The compiling option ADAPTIVE_LOCKMGRS has been introduced.  This
1149	option compiles in the support for adaptive spinning for lockmgrs
1150	which want to enable it.  The lockinit() function now accepts the flag
1151	LK_ADAPTIVE in order to make the lock object subject to adaptive
1152	spinning when both held in write and read mode.
1153
115420090613:
1155	The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1156	changed.  User applications that use this ioctl need to be rebuilt.
1157
115820090611:
1159	The layout of struct thread has changed.  Kernel and modules need to
1160	be rebuilt.
1161
116220090608:
1163	The layout of structs ifnet, domain, protosw and vnet_net has changed.
1164	Kernel modules need to be rebuilt.  Bump __FreeBSD_version to 800097.
1165
116620090602:
1167	window(1) has been removed from the base system. It can now be
1168	installed from ports. The port is called misc/window.
1169
117020090601:
1171	The way we are storing and accessing `routing table' entries has
1172	changed. Programs reading the FIB, like netstat, need to be
1173	re-compiled.
1174
117520090601:
1176	A new netisr implementation has been added for FreeBSD 8.  Network
1177	file system modules, such as igmp, ipdivert, and others, should be
1178	rebuilt.
1179	Bump __FreeBSD_version to 800096.
1180
118120090530:
1182	Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1183	more valid.
1184
118520090530:
1186	Add VOP_ACCESSX(9).  File system modules need to be rebuilt.
1187	Bump __FreeBSD_version to 800094.
1188
118920090529:
1190	Add mnt_xflag field to 'struct mount'.  File system modules need to be
1191	rebuilt.
1192	Bump __FreeBSD_version to 800093.
1193
119420090528:
1195	The compiling option ADAPTIVE_SX has been retired while it has been
1196	introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1197	The KPI for sx_init_flags() changes as accepting flags:
1198	SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1199	been introduced in order to handle the reversed logic.
1200	Bump __FreeBSD_version to 800092.
1201
120220090527:
1203	Add support for hierarchical jails.  Remove global securelevel.
1204	Bump __FreeBSD_version to 800091.
1205
120620090523:
1207	The layout of struct vnet_net has changed, therefore modules
1208	need to be rebuilt.
1209	Bump __FreeBSD_version to 800090.
1210
121120090523:
1212	The newly imported zic(8) produces a new format in the output. Please
1213	run tzsetup(8) to install the newly created data to /etc/localtime.
1214
121520090520:
1216	The sysctl tree for the usb stack has renamed from hw.usb2.* to
1217	hw.usb.* and is now consistent again with previous releases.
1218
121920090520:
1220	802.11 monitor mode support was revised and driver api's were changed.
1221	Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1222	of DLT_IEEE802_11.  No user-visible data structures were changed but
1223	applications that use DLT_IEEE802_11 may require changes.
1224	Bump __FreeBSD_version to 800088.
1225
122620090430:
1227	The layout of the following structs has changed: sysctl_oid,
1228	socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1229	vnet_inet6 and vnet_ipfw.  Most modules need to be rebuild or
1230	panics may be experienced.  World rebuild is required for
1231	correctly checking networking state from userland.
1232	Bump __FreeBSD_version to 800085.
1233
123420090429:
1235	MLDv2 and Source-Specific Multicast (SSM) have been merged
1236	to the IPv6 stack. VIMAGE hooks are in but not yet used.
1237	The implementation of SSM within FreeBSD's IPv6 stack closely
1238	follows the IPv4 implementation.
1239
1240	For kernel developers:
1241
1242	* The most important changes are that the ip6_output() and
1243	  ip6_input() paths no longer take the IN6_MULTI_LOCK,
1244	  and this lock has been downgraded to a non-recursive mutex.
1245
1246	* As with the changes to the IPv4 stack to support SSM, filtering
1247	  of inbound multicast traffic must now be performed by transport
1248	  protocols within the IPv6 stack. This does not apply to TCP and
1249	  SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1250
1251	* The KPIs used by IPv6 multicast are similar to those used by
1252	  the IPv4 stack, with the following differences:
1253	   * im6o_mc_filter() is analogous to imo_multicast_filter().
1254	   * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1255	     are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1256	   * IN6_LOOKUP_MULTI() has been deprecated and removed.
1257	   * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1258	     for MLDv1 have an additional 'timer' argument which is used to
1259	     jitter the initial membership report for the solicited-node
1260	     multicast membership on-link.
1261	   * This is not strictly needed for MLDv2, which already jitters
1262	     its report transmissions.  However, the 'timer' argument is
1263	     preserved in case MLDv1 is active on the interface.
1264
1265	* The KAME linked-list based IPv6 membership implementation has
1266	  been refactored to use a vector similar to that used by the IPv4
1267	  stack.
1268	  Code which maintains a list of its own multicast memberships
1269	  internally, e.g. carp, has been updated to reflect the new
1270	  semantics.
1271
1272	* There is a known Lock Order Reversal (LOR) due to in6_setscope()
1273	  acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1274	  Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1275	  implementation constraint which needs to be addressed in HEAD.
1276
1277	For application developers:
1278
1279	* The changes are broadly similar to those made for the IPv4
1280	  stack.
1281
1282	* The use of IPv4 and IPv6 multicast socket options on the same
1283	  socket, using mapped addresses, HAS NOT been tested or supported.
1284
1285	* There are a number of issues with the implementation of various
1286	  IPv6 multicast APIs which need to be resolved in the API surface
1287	  before the implementation is fully compatible with KAME userland
1288	  use, and these are mostly to do with interface index treatment.
1289
1290	* The literature available discusses the use of either the delta / ASM
1291	  API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1292	  using setsourcefilter(3)/getsourcefilter(3). For more information
1293	  please refer to RFC 3768, 'Socket Interface Extensions for
1294	  Multicast Source Filters'.
1295
1296	* Applications which use the published RFC 3678 APIs should be fine.
1297
1298	For systems administrators:
1299
1300	* The mtest(8) utility has been refactored to support IPv6, in
1301	  addition to IPv4. Interface addresses are no longer accepted
1302	  as arguments, their names must be used instead. The utility
1303	  will map the interface name to its first IPv4 address as
1304	  returned by getifaddrs(3).
1305
1306	* The ifmcstat(8) utility has also been updated to print the MLDv2
1307	  endpoint state and source filter lists via sysctl(3).
1308
1309	* The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1310	  loopback of IPv6 multicast datagrams by default; it defaults to 1
1311	  to preserve the existing behaviour. Disabling multicast loopback is
1312	  recommended for optimal system performance.
1313
1314	* The IPv6 MROUTING code has been changed to examine this sysctl
1315	  instead of attempting to perform a group lookup before looping
1316	  back forwarded datagrams.
1317
1318	Bump __FreeBSD_version to 800084.
1319
132020090422:
1321	Implement low-level Bluetooth HCI API.
1322	Bump __FreeBSD_version to 800083.
1323
132420090419:
1325	The layout of struct malloc_type, used by modules to register new
1326	memory allocation types, has changed.  Most modules will need to
1327	be rebuilt or panics may be experienced.
1328	Bump __FreeBSD_version to 800081.
1329
133020090415:
1331	Anticipate overflowing inp_flags - add inp_flags2.
1332	This changes most offsets in inpcb, so checking v4 connection
1333	state will require a world rebuild.
1334	Bump __FreeBSD_version to 800080.
1335
133620090415:
1337	Add an llentry to struct route and struct route_in6. Modules
1338	embedding a struct route will need to be recompiled.
1339	Bump __FreeBSD_version to 800079.
1340
134120090414:
1342	The size of rt_metrics_lite and by extension rtentry has changed.
1343	Networking administration apps will need to be recompiled.
1344	The route command now supports show as an alias for get, weighting
1345	of routes, sticky and nostick flags to alter the behavior of stateful
1346	load balancing.
1347	Bump __FreeBSD_version to 800078.
1348
134920090408:
1350	Do not use Giant for kbdmux(4) locking. This is wrong and
1351	apparently causing more problems than it solves. This will
1352	re-open the issue where interrupt handlers may race with
1353	kbdmux(4) in polling mode. Typical symptoms include (but
1354	not limited to) duplicated and/or missing characters when
1355	low level console functions (such as gets) are used while
1356	interrupts are enabled (for example geli password prompt,
1357	mountroot prompt etc.). Disabling kbdmux(4) may help.
1358
135920090407:
1360	The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1361	kernel modules referencing any of the above need to be recompiled.
1362	Bump __FreeBSD_version to 800075.
1363
136420090320:
1365	GEOM_PART has become the default partition slicer for storage devices,
1366	replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1367	introduces some changes:
1368
1369	MSDOS/EBR: the devices created from MSDOS extended partition entries
1370	(EBR) can be named differently than with GEOM_MBR and are now symlinks
1371	to devices with offset-based names. fstabs may need to be modified.
1372
1373	BSD: the "geometry does not match label" warning is harmless in most
1374	cases but it points to problems in file system misalignment with
1375	disk geometry. The "c" partition is now implicit, covers the whole
1376	top-level drive and cannot be (mis)used by users.
1377
1378	General: Kernel dumps are now not allowed to be written to devices
1379	whose partition types indicate they are meant to be used for file
1380	systems (or, in case of MSDOS partitions, as something else than
1381	the "386BSD" type).
1382
1383	Most of these changes date approximately from 200812.
1384
138520090319:
1386	The uscanner(4) driver has been removed from the kernel. This follows
1387	Linux removing theirs in 2.6 and making libusb the default interface
1388	(supported by sane).
1389
139020090319:
1391	The multicast forwarding code has been cleaned up. netstat(1)
1392	only relies on KVM now for printing bandwidth upcall meters.
1393	The IPv4 and IPv6 modules are split into ip_mroute_mod and
1394	ip6_mroute_mod respectively. The config(5) options for statically
1395	compiling this code remain the same, i.e. 'options MROUTING'.
1396
139720090315:
1398	Support for the IFF_NEEDSGIANT network interface flag has been
1399	removed, which means that non-MPSAFE network device drivers are no
1400	longer supported.  In particular, if_ar, if_sr, and network device
1401	drivers from the old (legacy) USB stack can no longer be built or
1402	used.
1403
140420090313:
1405	POSIX.1 Native Language Support (NLS) has been enabled in libc and
1406	a bunch of new language catalog files have also been added.
1407	This means that some common libc messages are now localized and
1408	they depend on the LC_MESSAGES environmental variable.
1409
141020090313:
1411	The k8temp(4) driver has been renamed to amdtemp(4) since
1412	support for Family 10 and Family 11 CPU families was added.
1413
141420090309:
1415	IGMPv3 and Source-Specific Multicast (SSM) have been merged
1416	to the IPv4 stack. VIMAGE hooks are in but not yet used.
1417
1418	For kernel developers, the most important changes are that the
1419	ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1420	and this lock has been downgraded to a non-recursive mutex.
1421
1422	Transport protocols (UDP, Raw IP) are now responsible for filtering
1423	inbound multicast traffic according to group membership and source
1424	filters. The imo_multicast_filter() KPI exists for this purpose.
1425	Transports which do not use multicast (SCTP, TCP) already reject
1426	multicast by default. Forwarding and receive performance may improve
1427	as a mutex acquisition is no longer needed in the ip_input()
1428	low-level input path.  in_addmulti() and in_delmulti() are shimmed
1429	to new KPIs which exist to support SSM in-kernel.
1430
1431	For application developers, it is recommended that loopback of
1432	multicast datagrams be disabled for best performance, as this
1433	will still cause the lock to be taken for each looped-back
1434	datagram transmission. The net.inet.ip.mcast.loop sysctl may
1435	be tuned to 0 to disable loopback by default; it defaults to 1
1436	to preserve the existing behaviour.
1437
1438	For systems administrators, to obtain best performance with
1439	multicast reception and multiple groups, it is always recommended
1440	that a card with a suitably precise hash filter is used. Hash
1441	collisions will still result in the lock being taken within the
1442	transport protocol input path to check group membership.
1443
1444	If deploying FreeBSD in an environment with IGMP snooping switches,
1445	it is recommended that the net.inet.igmp.sendlocal sysctl remain
1446	enabled; this forces 224.0.0.0/24 group membership to be announced
1447	via IGMP.
1448
1449	The size of 'struct igmpstat' has changed; netstat needs to be
1450	recompiled to reflect this.
1451	Bump __FreeBSD_version to 800070.
1452
145320090309:
1454	libusb20.so.1 is now installed as libusb.so.1 and the ports system
1455	updated to use it. This requires a buildworld/installworld in order to
1456	update the library and dependencies (usbconfig, etc). Its advisable to
1457	rebuild all ports which uses libusb. More specific directions are given
1458	in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1459	libusb are no longer required and can be removed.
1460
146120090302:
1462	A workaround is committed to allow the creation of System V shared
1463	memory segment of size > 2 GB on the 64-bit architectures.
1464	Due to a limitation of the existing ABI, the shm_segsz member
1465	of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1466	wrong for large segments. Note that limits must be explicitly
1467	raised to allow such segments to be created.
1468
146920090301:
1470	The layout of struct ifnet has changed, requiring a rebuild of all
1471	network device driver modules.
1472
147320090227:
1474	The /dev handling for the new USB stack has changed, a
1475	buildworld/installworld is required for libusb20.
1476
147720090223:
1478	The new USB2 stack has now been permanently moved in and all kernel and
1479	module names reverted to their previous values (eg, usb, ehci, ohci,
1480	ums, ...).  The old usb stack can be compiled in by prefixing the name
1481	with the letter 'o', the old usb modules have been removed.
1482	Updating entry 20090216 for xorg and 20090215 for libmap may still
1483	apply.
1484
148520090217:
1486	The rc.conf(5) option if_up_delay has been renamed to
1487	defaultroute_delay to better reflect its purpose. If you have
1488	customized this setting in /etc/rc.conf you need to update it to
1489	use the new name.
1490
149120090216:
1492	xorg 7.4 wants to configure its input devices via hald which does not
1493	yet work with USB2. If the keyboard/mouse does not work in xorg then
1494	add
1495		Option "AllowEmptyInput" "off"
1496	to your ServerLayout section.  This will cause X to use the configured
1497	kbd and mouse sections from your xorg.conf.
1498
149920090215:
1500	The GENERIC kernels for all architectures now default to the new USB2
1501	stack. No kernel config options or code have been removed so if a
1502	problem arises please report it and optionally revert to the old USB
1503	stack. If you are loading USB kernel modules or have a custom kernel
1504	that includes GENERIC then ensure that usb names are also changed over,
1505	eg uftdi -> usb2_serial_ftdi.
1506
1507	Older programs linked against the ports libusb 0.1 need to be
1508	redirected to the new stack's libusb20.  /etc/libmap.conf can
1509	be used for this:
1510		# Map old usb library to new one for usb2 stack
1511		libusb-0.1.so.8	libusb20.so.1
1512
151320090209:
1514	All USB ethernet devices now attach as interfaces under the name ueN
1515	(eg. ue0). This is to provide a predictable name as vendors often
1516	change usb chipsets in a product without notice.
1517
151820090203:
1519	The ichsmb(4) driver has been changed to require SMBus slave
1520	addresses be left-justified (xxxxxxx0b) rather than right-justified.
1521	All of the other SMBus controller drivers require left-justified
1522	slave addresses, so this change makes all the drivers provide the
1523	same interface.
1524
152520090201:
1526	INET6 statistics (struct ip6stat) was updated.
1527	netstat(1) needs to be recompiled.
1528
152920090119:
1530	NTFS has been removed from GENERIC kernel on amd64 to match
1531	GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1532	will load ntfs.ko module automatically when NTFS support is
1533	actually needed, unless ntfs.ko is not installed or security
1534	level prohibits loading kernel modules. If either is the case,
1535	"options NTFS" has to be added into kernel config.
1536
153720090115:
1538	TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1539	New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1540	800061. User space tools that rely on the size of struct tcpcb in
1541	tcp_var.h (e.g. sockstat) need to be recompiled.
1542
154320081225:
1544	ng_tty(4) module updated to match the new TTY subsystem.
1545	Due to API change, user-level applications must be updated.
1546	New API support added to mpd5 CVS and expected to be present
1547	in next mpd5.3 release.
1548
154920081219:
1550	With __FreeBSD_version 800060 the makefs tool is part of
1551	the base system (it was a port).
1552
155320081216:
1554	The afdata and ifnet locks have been changed from mutexes to
1555	rwlocks, network modules will need to be re-compiled.
1556
155720081214:
1558	__FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1559	RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1560	The new code reduced struct rtentry{} by 16 bytes on 32-bit
1561	architecture and 40 bytes on 64-bit architecture. The userland
1562	applications "arp" and "ndp" have been updated accordingly.
1563	The output from "netstat -r" shows only routing entries and
1564	none of the L2 information.
1565
156620081130:
1567	__FreeBSD_version 800057 marks the switchover from the
1568	binary ath hal to source code. Users must add the line:
1569
1570	options	AH_SUPPORT_AR5416
1571
1572	to their kernel config files when specifying:
1573
1574	device	ath_hal
1575
1576	The ath_hal module no longer exists; the code is now compiled
1577	together with the driver in the ath module.  It is now
1578	possible to tailor chip support (i.e. reduce the set of chips
1579	and thereby the code size); consult ath_hal(4) for details.
1580
158120081121:
1582	__FreeBSD_version 800054 adds memory barriers to
1583	<machine/atomic.h>, new interfaces to ifnet to facilitate
1584	multiple hardware transmit queues for cards that support
1585	them, and a lock-less ring-buffer implementation to
1586	enable drivers to more efficiently manage queueing of
1587	packets.
1588
158920081117:
1590	A new version of ZFS (version 13) has been merged to -HEAD.
1591	This version has zpool attribute "listsnapshots" off by
1592	default, which means "zfs list" does not show snapshots,
1593	and is the same as Solaris behavior.
1594
159520081028:
1596	dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1597
159820081009:
1599	The uhci, ohci, ehci and slhci USB Host controller drivers have
1600	been put into separate modules. If you load the usb module
1601	separately through loader.conf you will need to load the
1602	appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1603	controller add the following to loader.conf:
1604
1605		uhci_load="YES"
1606		ehci_load="YES"
1607
160820081009:
1609	The ABI used by the PMC toolset has changed.  Please keep
1610	userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1611	sync.
1612
161320081009:
1614	atapci kernel module now includes only generic PCI ATA
1615	driver. AHCI driver moved to ataahci kernel module.
1616	All vendor-specific code moved into separate kernel modules:
1617	ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1618	atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1619	atamarvell, atamicron, atanational, atanetcell, atanvidia,
1620	atapromise, ataserverworks, atasiliconimage, atasis, atavia
1621
162220080820:
1623	The TTY subsystem of the kernel has been replaced by a new
1624	implementation, which provides better scalability and an
1625	improved driver model. Most common drivers have been migrated to
1626	the new TTY subsystem, while others have not. The following
1627	drivers have not yet been ported to the new TTY layer:
1628
1629	PCI/ISA:
1630		cy, digi, rc, rp, sio
1631
1632	USB:
1633		ubser, ucycom
1634
1635	Line disciplines:
1636		ng_h4, ng_tty, ppp, sl, snp
1637
1638	Adding these drivers to your kernel configuration file shall
1639	cause compilation to fail.
1640
164120080818:
1642	ntpd has been upgraded to 4.2.4p5.
1643
164420080801:
1645	OpenSSH has been upgraded to 5.1p1.
1646
1647	For many years, FreeBSD's version of OpenSSH preferred DSA
1648	over RSA for host and user authentication keys.  With this
1649	upgrade, we've switched to the vendor's default of RSA over
1650	DSA.  This may cause upgraded clients to warn about unknown
1651	host keys even for previously known hosts.  Users should
1652	follow the usual procedure for verifying host keys before
1653	accepting the RSA key.
1654
1655	This can be circumvented by setting the "HostKeyAlgorithms"
1656	option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1657	command line.
1658
1659	Please note that the sequence of keys offered for
1660	authentication has been changed as well.  You may want to
1661	specify IdentityFile in a different order to revert this
1662	behavior.
1663
166420080713:
1665	The sio(4) driver has been removed from the i386 and amd64
1666	kernel configuration files. This means uart(4) is now the
1667	default serial port driver on those platforms as well.
1668
1669	To prevent collisions with the sio(4) driver, the uart(4) driver
1670	uses different names for its device nodes. This means the
1671	onboard serial port will now most likely be called "ttyu0"
1672	instead of "ttyd0". You may need to reconfigure applications to
1673	use the new device names.
1674
1675	When using the serial port as a boot console, be sure to update
1676	/boot/device.hints and /etc/ttys before booting the new kernel.
1677	If you forget to do so, you can still manually specify the hints
1678	at the loader prompt:
1679
1680		set hint.uart.0.at="isa"
1681		set hint.uart.0.port="0x3F8"
1682		set hint.uart.0.flags="0x10"
1683		set hint.uart.0.irq="4"
1684		boot -s
1685
168620080609:
1687	The gpt(8) utility has been removed. Use gpart(8) to partition
1688	disks instead.
1689
169020080603:
1691	The version that Linuxulator emulates was changed from 2.4.2
1692	to 2.6.16. If you experience any problems with Linux binaries
1693	please try to set sysctl compat.linux.osrelease to 2.4.2 and
1694	if it fixes the problem contact emulation mailing list.
1695
169620080525:
1697	ISDN4BSD (I4B) was removed from the src tree. You may need to
1698	update a your kernel configuration and remove relevant entries.
1699
170020080509:
1701	I have checked in code to support multiple routing tables.
1702	See the man pages setfib(1) and setfib(2).
1703	This is a hopefully backwards compatible version,
1704	but to make use of it you need to compile your kernel
1705	with options ROUTETABLES=2 (or more up to 16).
1706
170720080420:
1708	The 802.11 wireless support was redone to enable multi-bss
1709	operation on devices that are capable.  The underlying device
1710	is no longer used directly but instead wlanX devices are
1711	cloned with ifconfig.  This requires changes to rc.conf files.
1712	For example, change:
1713		ifconfig_ath0="WPA DHCP"
1714	to
1715		wlans_ath0=wlan0
1716		ifconfig_wlan0="WPA DHCP"
1717	see rc.conf(5) for more details.  In addition, mergemaster of
1718	/etc/rc.d is highly recommended.  Simultaneous update of userland
1719	and kernel wouldn't hurt either.
1720
1721	As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1722	modules were merged into the base wlan module.  All references
1723	to these modules (e.g. in kernel config files) must be removed.
1724
172520080408:
1726	psm(4) has gained write(2) support in native operation level.
1727	Arbitrary commands can be written to /dev/psm%d and status can
1728	be read back from it.  Therefore, an application is responsible
1729	for status validation and error recovery.  It is a no-op in
1730	other operation levels.
1731
173220080312:
1733	Support for KSE threading has been removed from the kernel.  To
1734	run legacy applications linked against KSE libmap.conf may
1735	be used.  The following libmap.conf may be used to ensure
1736	compatibility with any prior release:
1737
1738	libpthread.so.1 libthr.so.1
1739	libpthread.so.2 libthr.so.2
1740	libkse.so.3 libthr.so.3
1741
174220080301:
1743	The layout of struct vmspace has changed. This affects libkvm
1744	and any executables that link against libkvm and use the
1745	kvm_getprocs() function. In particular, but not exclusively,
1746	it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1747	The effects are minimal, but it's advisable to upgrade world
1748	nonetheless.
1749
175020080229:
1751	The latest em driver no longer has support in it for the
1752	82575 adapter, this is now moved to the igb driver. The
1753	split was done to make new features that are incompatible
1754	with older hardware easier to do.
1755
175620080220:
1757	The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1758	likewise the kernel option is now GEOM_LINUX_LVM.
1759
176020080211:
1761	The default NFS mount mode has changed from UDP to TCP for
1762	increased reliability.  If you rely on (insecurely) NFS
1763	mounting across a firewall you may need to update your
1764	firewall rules.
1765
176620080208:
1767	Belatedly note the addition of m_collapse for compacting
1768	mbuf chains.
1769
177020080126:
1771	The fts(3) structures have been changed to use adequate
1772	integer types for their members and so to be able to cope
1773	with huge file trees.  The old fts(3) ABI is preserved
1774	through symbol versioning in libc, so third-party binaries
1775	using fts(3) should still work, although they will not take
1776	advantage of the extended types.  At the same time, some
1777	third-party software might fail to build after this change
1778	due to unportable assumptions made in its source code about
1779	fts(3) structure members.  Such software should be fixed
1780	by its vendor or, in the worst case, in the ports tree.
1781	FreeBSD_version 800015 marks this change for the unlikely
1782	case that a portable fix is impossible.
1783
178420080123:
1785	To upgrade to -current after this date, you must be running
1786	FreeBSD not older than 6.0-RELEASE.  Upgrading to -current
1787	from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1788
178920071128:
1790	The ADAPTIVE_GIANT kernel option has been retired because its
1791	functionality is the default now.
1792
179320071118:
1794	The AT keyboard emulation of sunkbd(4) has been turned on
1795	by default. In order to make the special symbols of the Sun
1796	keyboards driven by sunkbd(4) work under X these now have
1797	to be configured the same way as Sun USB keyboards driven
1798	by ukbd(4) (which also does AT keyboard emulation), f.e.:
1799
1800	Option	"XkbLayout" "us"
1801	Option	"XkbRules" "xorg"
1802	Option	"XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1803
180420071024:
1805	It has been decided that it is desirable to provide ABI
1806	backwards compatibility to the FreeBSD 4/5/6 versions of the
1807	PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1808	broken with the introduction of PCI domain support (see the
1809	20070930 entry). Unfortunately, this required the ABI of
1810	PCIOCGETCONF to be broken again in order to be able to
1811	provide backwards compatibility to the old version of that
1812	IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1813	again. As for prominent ports this affects neither pciutils
1814	nor xorg-server this time, the hal port needs to be rebuilt
1815	however.
1816
181720071020:
1818	The misnamed kthread_create() and friends have been renamed
1819	to kproc_create() etc. Many of the callers already
1820	used kproc_start()..
1821	I will return kthread_create() and friends in a while
1822	with implementations that actually create threads, not procs.
1823	Renaming corresponds with version 800002.
1824
182520071010:
1826	RELENG_7 branched.
1827
1828COMMON ITEMS:
1829
1830	General Notes
1831	-------------
1832	Avoid using make -j when upgrading.  While generally safe, there are
1833	sometimes problems using -j to upgrade.  If your upgrade fails with
1834	-j, please try again without -j.  From time to time in the past there
1835	have been problems using -j with buildworld and/or installworld.  This
1836	is especially true when upgrading between "distant" versions (eg one
1837	that cross a major release boundary or several minor releases, or when
1838	several months have passed on the -current branch).
1839
1840	Sometimes, obscure build problems are the result of environment
1841	poisoning.  This can happen because the make utility reads its
1842	environment when searching for values for global variables.  To run
1843	your build attempts in an "environmental clean room", prefix all make
1844	commands with 'env -i '.  See the env(1) manual page for more details.
1845
1846	When upgrading from one major version to another it is generally best
1847	to upgrade to the latest code in the currently installed branch first,
1848	then do an upgrade to the new branch. This is the best-tested upgrade
1849	path, and has the highest probability of being successful.  Please try
1850	this approach before reporting problems with a major version upgrade.
1851
1852	When upgrading a live system, having a root shell around before
1853	installing anything can help undo problems. Not having a root shell
1854	around can lead to problems if pam has changed too much from your
1855	starting point to allow continued authentication after the upgrade.
1856
1857	ZFS notes
1858	---------
1859	When upgrading the boot ZFS pool to a new version, always follow
1860	these two steps:
1861
1862	1.) recompile and reinstall the ZFS boot loader and boot block
1863	(this is part of "make buildworld" and "make installworld")
1864
1865	2.) update the ZFS boot block on your boot drive
1866
1867	The following example updates the ZFS boot block on the first
1868	partition (freebsd-boot) of a GPT partitioned drive ad0:
1869	"gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1870
1871	Non-boot pools do not need these updates.
1872
1873	To build a kernel
1874	-----------------
1875	If you are updating from a prior version of FreeBSD (even one just
1876	a few days old), you should follow this procedure.  It is the most
1877	failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1878
1879	make kernel-toolchain
1880	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1881	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1882
1883	To test a kernel once
1884	---------------------
1885	If you just want to boot a kernel once (because you are not sure
1886	if it works, or if you want to boot a known bad kernel to provide
1887	debugging information) run
1888	make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1889	nextboot -k testkernel
1890
1891	To just build a kernel when you know that it won't mess you up
1892	--------------------------------------------------------------
1893	This assumes you are already running a CURRENT system.  Replace
1894	${arch} with the architecture of your machine (e.g. "i386",
1895	"arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1896
1897	cd src/sys/${arch}/conf
1898	config KERNEL_NAME_HERE
1899	cd ../compile/KERNEL_NAME_HERE
1900	make depend
1901	make
1902	make install
1903
1904	If this fails, go to the "To build a kernel" section.
1905
1906	To rebuild everything and install it on the current system.
1907	-----------------------------------------------------------
1908	# Note: sometimes if you are running current you gotta do more than
1909	# is listed here if you are upgrading from a really old current.
1910
1911	<make sure you have good level 0 dumps>
1912	make buildworld
1913	make kernel KERNCONF=YOUR_KERNEL_HERE
1914							[1]
1915	<reboot in single user>				[3]
1916	mergemaster -p					[5]
1917	make installworld
1918	mergemaster -i					[4]
1919	make delete-old					[6]
1920	<reboot>
1921
1922	To cross-install current onto a separate partition
1923	--------------------------------------------------
1924	# In this approach we use a separate partition to hold
1925	# current's root, 'usr', and 'var' directories.   A partition
1926	# holding "/", "/usr" and "/var" should be about 2GB in
1927	# size.
1928
1929	<make sure you have good level 0 dumps>
1930	<boot into -stable>
1931	make buildworld
1932	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1933	<maybe newfs current's root partition>
1934	<mount current's root partition on directory ${CURRENT_ROOT}>
1935	make installworld DESTDIR=${CURRENT_ROOT}
1936	make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1937	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1938	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1939	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1940	<reboot into current>
1941	<do a "native" rebuild/install as described in the previous section>
1942	<maybe install compatibility libraries from ports/misc/compat*>
1943	<reboot>
1944
1945
1946	To upgrade in-place from stable to current
1947	----------------------------------------------
1948	<make sure you have good level 0 dumps>
1949	make buildworld					[9]
1950	make kernel KERNCONF=YOUR_KERNEL_HERE		[8]
1951							[1]
1952	<reboot in single user>				[3]
1953	mergemaster -p					[5]
1954	make installworld
1955	mergemaster -i					[4]
1956	make delete-old					[6]
1957	<reboot>
1958
1959	Make sure that you've read the UPDATING file to understand the
1960	tweaks to various things you need.  At this point in the life
1961	cycle of current, things change often and you are on your own
1962	to cope.  The defaults can also change, so please read ALL of
1963	the UPDATING entries.
1964
1965	Also, if you are tracking -current, you must be subscribed to
1966	freebsd-current@freebsd.org.  Make sure that before you update
1967	your sources that you have read and understood all the recent
1968	messages there.  If in doubt, please track -stable which has
1969	much fewer pitfalls.
1970
1971	[1] If you have third party modules, such as vmware, you
1972	should disable them at this point so they don't crash your
1973	system on reboot.
1974
1975	[3] From the bootblocks, boot -s, and then do
1976		fsck -p
1977		mount -u /
1978		mount -a
1979		cd src
1980		adjkerntz -i		# if CMOS is wall time
1981	Also, when doing a major release upgrade, it is required that
1982	you boot into single user mode to do the installworld.
1983
1984	[4] Note: This step is non-optional.  Failure to do this step
1985	can result in a significant reduction in the functionality of the
1986	system.  Attempting to do it by hand is not recommended and those
1987	that pursue this avenue should read this file carefully, as well
1988	as the archives of freebsd-current and freebsd-hackers mailing lists
1989	for potential gotchas.  The -U option is also useful to consider.
1990	See mergemaster(8) for more information.
1991
1992	[5] Usually this step is a noop.  However, from time to time
1993	you may need to do this if you get unknown user in the following
1994	step.  It never hurts to do it all the time.  You may need to
1995	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1996	install) after the buildworld before this step if you last updated
1997	from current before 20130425 or from -stable before 20130430.
1998
1999	[6] This only deletes old files and directories. Old libraries
2000	can be deleted by "make delete-old-libs", but you have to make
2001	sure that no program is using those libraries anymore.
2002
2003	[8] In order to have a kernel that can run the 4.x binaries needed to
2004	do an installworld, you must include the COMPAT_FREEBSD4 option in
2005	your kernel.  Failure to do so may leave you with a system that is
2006	hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2007	required to run the 5.x binaries on more recent kernels.  And so on
2008	for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2009
2010	Make sure that you merge any new devices from GENERIC since the
2011	last time you updated your kernel config file.
2012
2013	[9] When checking out sources, you must include the -P flag to have
2014	cvs prune empty directories.
2015
2016	If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2017	"?=" instead of the "=" assignment operator, so that buildworld can
2018	override the CPUTYPE if it needs to.
2019
2020	MAKEOBJDIRPREFIX must be defined in an environment variable, and
2021	not on the command line, or in /etc/make.conf.  buildworld will
2022	warn if it is improperly defined.
2023FORMAT:
2024
2025This file contains a list, in reverse chronological order, of major
2026breakages in tracking -current.  It is not guaranteed to be a complete
2027list of such breakages, and only contains entries since October 10, 2007.
2028If you need to see UPDATING entries from before that date, you will need
2029to fetch an UPDATING file from an older FreeBSD release.
2030
2031Copyright information:
2032
2033Copyright 1998-2009 M. Warner Losh.  All Rights Reserved.
2034
2035Redistribution, publication, translation and use, with or without
2036modification, in full or in part, in any form or format of this
2037document are permitted without further permission from the author.
2038
2039THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2040IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2041WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2042DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2043INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2044(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2045SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2046HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2047STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2048IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2049POSSIBILITY OF SUCH DAMAGE.
2050
2051Contact Warner Losh if you have any questions about your use of
2052this document.
2053
2054$FreeBSD: head/UPDATING 258714 2013-11-28 19:13:05Z rodrigc $
2055