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