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