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