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