UPDATING revision 150636
1Updating Information for FreeBSD current users
2
3This file is maintained and copyrighted by M. Warner Losh
4<imp@village.org>.  See end of file for further details.  For commonly
5done items, please see the COMMON ITEMS: section later in the file.
6
7Items affecting the ports and packages system can be found in
8/usr/ports/UPDATING.  Please read that file before running
9portupgrade.
10
11NOTE TO PEOPLE WHO THINK THAT FreeBSD 7.x IS SLOW:
12	FreeBSD 7.x has many debugging features turned on, in
13	both the kernel and userland.  These features attempt to detect
14	incorrect use of system primitives, and encourage loud failure
15	through extra sanity checking and fail stop semantics.  They
16	also substantially impact system performance.  If you want to
17	do performance measurement, benchmarking, and optimization,
18	you'll want to turn them off.  This includes various WITNESS-
19	related kernel options, INVARIANTS, malloc debugging flags
20	in userland, and various verbose features in the kernel.  Many
21	developers choose to disable these features on build machines
22	to maximize performance.
23
2420050927:
25	The old bridge(4) implementation was retired.  The new
26	if_bridge(4) serves as a full functional replacement.
27
2820050722:
29	The ai_addrlen of a struct addrinfo was changed to a socklen_t
30	to conform to POSIX-2001.  This change broke an ABI
31	compatibility on 64 bit architecture.  You have to recompile
32	userland programs that use getaddrinfo(3) on 64 bit
33	architecture.
34
3520050711:
36	RELENG_6 branched here.
37
3820050629:
39	The pccard_ifconfig rc.conf variable has been removed and a new
40	variable, ifconfig_DEFAULT has been introduced.  Unlike
41	pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
42	do not have ifconfig_ifn entries rather than just those in
43	removable_interfaces.
44
4520050616:
46	Some previous versions of PAM have permitted the use of
47	non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
48	to third party PAM modules in /usr/local/lib.  A change has been
49	made to require the use of absolute paths in order to avoid
50	ambiguity and dependence on library path configuration, which may
51	affect existing configurations.
52
5320050610:
54	Major changes to network interface API.  All drivers must be
55	recompiled.  Drivers not in the base system will need to be
56	updated to the new APIs.
57
5820050609:
59	Changes were made to kinfo_proc in sys/user.h.  Please recompile
60	userland, or commands like `fstat', `pkill', `ps', `top' and `w'
61	will not behave correctly.
62
63	The API and ABI for hwpmc(4) have changed with the addition
64	of sampling support.  Please recompile lib/libpmc(3) and
65	usr.sbin/{pmcstat,pmccontrol}.
66
6720050606:
68	The OpenBSD dhclient was imported in place of the ISC dhclient
69	and the network interface configuration scripts were updated
70	accordingly.  If you use DHCP to configure your interfaces, you
71	must now run devd.  Also, DNS updating was lost so you will need
72	to find a workaround if you use this feature.
73
7420050605:
75	if_bridge was added to the tree. This has changed struct ifnet.
76	Please recompile userland and all network related modules.
77
7820050603:
79	The n_net of a struct netent was changed to an uint32_t, and
80	1st argument of getnetbyaddr() was changed to an uint32_t, to
81	conform to POSIX-2001.  These changes broke an ABI
82	compatibility on 64 bit architecture.  With these changes,
83	shlib major of libpcap was bumped.  You have to recompile
84	userland programs that use getnetbyaddr(3), getnetbyname(3),
85	getnetent(3) and/or libpcap on 64 bit architecture.
86
8720050528:
88	Kernel parsing of extra options on '#!' first lines of shell
89	scripts has changed.  Lines with multiple options likely will
90	fail after this date.  For full details, please see
91		http://people.freebsd.org/~gad/Updating-20050528.txt
92
9320050503:
94	The packet filter (pf) code has been updated to OpenBSD 3.7
95	Please note the changed anchor syntax and the fact that
96	authpf(8) now needs a mounted fdescfs(5) to function.
97
9820050415:
99	The NO_MIXED_MODE kernel option has been removed from the i386
100	amd64 platforms as its use has been superceded by the new local
101	APIC timer code.  Any kernel config files containing this option
102	should be updated.
103
10420050227:
105	The on-disk format of LC_CTYPE files was changed to be machine
106	independent.  Please make sure NOT to use NO_CLEAN buildworld
107	when crossing this point.
108
10920050225:
110	The ifi_epoch member of struct if_data has been changed to
111	contain the uptime at which the interface was created or the
112	statistics zeroed rather then the wall clock time because
113	wallclock time may go backwards.  This should have no impact
114	unless an snmp implementation is using this value (I know of
115	none at this point.)
116
11720050224:
118	The acpi_perf and acpi_throttle drivers are now part of the
119	acpi(4) main module.  They are no longer built separately.
120
12120050223:
122	The layout of struct image_params has changed. You have to
123	recompile all compatibility modules (linux, svr4, etc) for use
124	with the new kernel.
125
12620050223:
127	The p4tcc driver has been merged into cpufreq(4).  This makes
128	"options CPU_ENABLE_TCC" obsolete.  Please load cpufreq.ko or
129	compile in "device cpufreq" to restore this functionality.
130
13120050220:
132	The responsibility of recomputing the file system summary of
133	a SoftUpdates-enabled dirty volume has been transferred to the
134	background fsck.  A rebuild of fsck(8) utility is recommended
135	if you have updated the kernel.
136
137	To get the old behavior (recompute file system summary at mount
138	time), you can set vfs.ffs.compute_summary_at_mount=1 before
139	mounting the new volume.
140
14120050206:
142	The cpufreq import is complete.  As part of this, the sysctls for
143	acpi(4) throttling have been removed.  The power_profile script
144	has been updated, so you can use performance/economy_cpu_freq in
145	rc.conf(5) to set AC on/offline cpu frequencies.
146
14720050206:
148	NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
149	requires recompiling libnetgraph and userland netgraph utilities.
150
15120050114:
152	Support for abbreviated forms of a number of ipfw options is
153	now deprecated.  Warnings are printed to stderr indicating the
154	correct full form when a match occurs.  Some abbreviations may
155	be supported at a later date based on user feedback.  To be
156	considered for support, abbreviations must be in use prior to
157	this commit and unlikely to be confused with current key words.
158
15920041221:
160	By a popular demand, a lot of NOFOO options were renamed
161	to NO_FOO (see bsd.compat.mk for a full list).  The old
162	spellings are still supported, but will cause annoying
163	warnings on stderr.  Make sure you upgrade properly (see
164	the COMMON ITEMS: section later in this file).
165
16620041219:
167	Auto-loading of ancillary wlan modules such as wlan_wep has
168	been temporarily disabled; you need to statically configure
169	the modules you need into your kernel or explicitly load them
170	prior to use.  Specifically, if you intend to use WEP encryption
171	with an 802.11 device load/configure wlan_wep; if you want to
172	use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
173	and wlan_xauth as required.
174
17520041213:
176	The behaviour of ppp(8) has changed slightly.  If lqr is enabled
177	(``enable lqr''), older versions would revert to LCP ECHO mode on
178	negotiation failure.  Now, ``enable echo'' is required for this
179	behaviour.  The ppp version number has been bumped to 3.4.2 to
180	reflect the change.
181
18220041201:
183	The wlan support has been updated to split the crypto support
184	into separate modules.  For static WEP you must configure the
185	wlan_wep module in your system or build and install the module
186	in place where it can be loaded (the kernel will auto-load
187	the module when a wep key is configured).
188
18920041201:
190	The ath driver has been updated to split the tx rate control
191	algorithm into a separate module.  You need to include either
192	ath_rate_onoe or ath_rate_amrr when configuring the kernel.
193
19420041116:
195	Support for systems with an 80386 CPU has been removed.  Please
196	use FreeBSD 5.x or earlier on systems with an 80386.
197
19820041110:
199	We have had a hack which would mount the root filesystem
200	R/W if the device were named 'md*'.  As part of the vnode
201	work I'm doing I have had to remove this hack.  People
202	building systems which use preloaded MD root filesystems
203	may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
204	their /etc/rc scripts.
205
20620041104:
207	FreeBSD 5.3 shipped here.
208
20920041102:
210	The size of struct tcpcb has changed again due to the removal
211	of RFC1644 T/TCP.  You have to recompile userland programs that
212	read kmem for tcp sockets directly (netstat, sockstat, etc.)
213
21420041022:
215	The size of struct tcpcb has changed.  You have to recompile
216	userland programs that read kmem for tcp sockets directly
217	(netstat, sockstat, etc.)
218
21920041016:
220	RELENG_5 branched here.  For older entries, please see updating
221	in the RELENG_5 branch.
222
223COMMON ITEMS:
224
225	General Notes
226	-------------
227	Avoid using make -j when upgrading.  From time to time in the
228	past there have been problems using -j with buildworld and/or
229	installworld.  This is especially true when upgrading between
230	"distant" versions (eg one that cross a major release boundary
231	or several minor releases, or when several months have passed
232	on the -current branch).
233
234	Sometimes, obscure build problems are the result of environment
235	poisoning.  This can happen because the make utility reads its
236	environment when searching for values for global variables.
237	To run your build attempts in an "environmental clean room",
238	prefix all make commands with 'env -i '.  See the env(1) manual
239	page for more details.
240
241	To build a kernel
242	-----------------
243	If you are updating from a prior version of FreeBSD (even one just
244	a few days old), you should follow this procedure.  It is the most
245	failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
246
247	make kernel-toolchain
248	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
249	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
250
251	To test a kernel once
252	---------------------
253	If you just want to boot a kernel once (because you are not sure
254	if it works, or if you want to boot a known bad kernel to provide
255	debugging information) run
256	make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
257	nextboot -k testkernel
258
259	To just build a kernel when you know that it won't mess you up
260	--------------------------------------------------------------
261	This assumes you are already running a 5.X system.  Replace
262	${arch} with the architecture of your machine (e.g. "i386",
263	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
264
265	cd src/sys/${arch}/conf
266	config KERNEL_NAME_HERE
267	cd ../compile/KERNEL_NAME_HERE
268	make depend
269	make
270	make install
271
272	If this fails, go to the "To build a kernel" section.
273
274	To rebuild everything and install it on the current system.
275	-----------------------------------------------------------
276	# Note: sometimes if you are running current you gotta do more than
277	# is listed here if you are upgrading from a really old current.
278
279	<make sure you have good level 0 dumps>
280	make buildworld
281	make kernel KERNCONF=YOUR_KERNEL_HERE
282							[1]
283	<reboot in single user>				[3]
284	mergemaster -p					[5]
285	make installworld
286	make delete-old
287	mergemaster					[4]
288	<reboot>
289
290
291	To cross-install current onto a separate partition
292	--------------------------------------------------
293	# In this approach we use a separate partition to hold
294	# current's root, 'usr', and 'var' directories.   A partition
295	# holding "/", "/usr" and "/var" should be about 2GB in
296	# size.
297
298	<make sure you have good level 0 dumps>
299	<boot into -stable>
300	make buildworld
301	make buildkernel KERNCONF=YOUR_KERNEL_HERE
302	<maybe newfs current's root partition>
303	<mount current's root partition on directory ${CURRENT_ROOT}>
304	make installworld DESTDIR=${CURRENT_ROOT}
305	cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
306	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
307	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
308	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
309	<reboot into current>
310	<do a "native" rebuild/install as described in the previous section>
311	<maybe install compatibility libraries from src/lib/compat>
312 	<reboot>
313
314
315	To upgrade in-place from 5.x-stable to current
316	----------------------------------------------
317	<make sure you have good level 0 dumps>
318	make buildworld					[9]
319	make kernel KERNCONF=YOUR_KERNEL_HERE		[8]
320							[1]
321	<reboot in single user>				[3]
322	mergemaster -p					[5]
323	make installworld
324	make delete-old
325	mergemaster -i					[4]
326	<reboot>
327
328	Make sure that you've read the UPDATING file to understand the
329	tweaks to various things you need.  At this point in the life
330	cycle of current, things change often and you are on your own
331	to cope.  The defaults can also change, so please read ALL of
332	the UPDATING entries.
333
334	Also, if you are tracking -current, you must be subscribed to
335	freebsd-current@freebsd.org.  Make sure that before you update
336	your sources that you have read and understood all the recent
337	messages there.  If in doubt, please track -stable which has
338	much fewer pitfalls.
339
340	[1] If you have third party modules, such as vmware, you
341	should disable them at this point so they don't crash your
342	system on reboot.
343
344	[3] From the bootblocks, boot -s, and then do
345		fsck -p
346		mount -u /
347		mount -a
348		cd src
349		adjkerntz -i		# if CMOS is wall time
350	Also, when doing a major release upgrade, it is required that
351	you boot into single user mode to do the installworld.
352
353	[4] Note: This step is non-optional.  Failure to do this step
354	can result in a significant reduction in the functionality of the
355	system.  Attempting to do it by hand is not recommended and those
356	that pursue this avenue should read this file carefully, as well
357	as the archives of freebsd-current and freebsd-hackers mailing lists
358	for potential gotchas.
359
360	[5] Usually this step is a noop.  However, from time to time
361	you may need to do this if you get unknown user in the following
362	step.  It never hurts to do it all the time.  You may need to
363	install a new mergemaster (cd src/usr.sbin/mergemaster && make
364	install) after the buildworld before this step if you last updated
365	from current before 20020224 or from -stable before 20020408.
366
367	[8] In order to have a kernel that can run the 4.x binaries
368	needed to do an installworld, you must include the COMPAT_FREEBSD4
369	option in your kernel.  Failure to do so may leave you with a system
370	that is hard to boot to recover.
371
372	Make sure that you merge any new devices from GENERIC since the
373	last time you updated your kernel config file.
374
375	[9] When checking out sources, you must include the -P flag to have
376	cvs prune empty directories.
377
378	If CPUTYPE is defined in your /etc/make.conf, make sure to use the
379	"?=" instead of the "=" assignment operator, so that buildworld can
380	override the CPUTYPE if it needs to.
381
382	MAKEOBJDIRPREFIX must be defined in an environment variable, and
383	not on the command line, or in /etc/make.conf.  buildworld will
384	warn if it is improperly defined.
385FORMAT:
386
387This file contains a list, in reverse chronological order, of major
388breakages in tracking -current.  Not all things will be listed here,
389and it only starts on October 16, 2004.  Updating files can found in
390previous releases if your system is older than this.
391
392Copyright information:
393
394Copyright 1998-2005 M. Warner Losh.  All Rights Reserved.
395
396Redistribution, publication, translation and use, with or without
397modification, in full or in part, in any form or format of this
398document are permitted without further permission from the author.
399
400THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
401IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
402WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
403DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
404INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
405(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
406SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
407HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
408STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
409IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
410POSSIBILITY OF SUCH DAMAGE.
411
412If you find this document useful, and you want to, you may buy the
413author a beer.
414
415Contact Warner Losh if you have any questions about your use of
416this document.
417
418$FreeBSD: head/UPDATING 150636 2005-09-27 18:10:43Z mlaier $
419