xref: /freebsd/UPDATING (revision d6b4b3b3985810ca9283a760f1d77a07d5b1bcb8)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh
49698f2c0SWarner Losh<imp@village.org>.  See end of file for further details.  For commonly
59698f2c0SWarner Loshdone items, please see the COMMON ITEMS: section later in the file.
6e72fd46aSWarner Losh
72c724730SWarner LoshItems affecting the ports and packages system can be found in
82c724730SWarner Losh/usr/ports/UPDATING.  Please read that file before running
94f638121SWarner Loshportupgrade.
102c724730SWarner Losh
1199b22782SKen SmithNOTE TO PEOPLE WHO THINK THAT FreeBSD 7.x IS SLOW:
1299b22782SKen Smith	FreeBSD 7.x has many debugging features turned on, in
1369f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1469f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1569f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1669f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1769f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
1869f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
1969f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
2069f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
2169f7bcf3SWarner Losh	developers choose to disable these features on build machines
22a19f8ddaSDavid E. O'Brien	to maximize performance.
23c1f61aa9SDavid E. O'Brien
246dba929aSSam Leffler20051211:
256dba929aSSam Leffler	The net80211-related tools in the tools/tools/ath directory
266dba929aSSam Leffler	have been moved to tools/tools/net80211 and renamed with a
276dba929aSSam Leffler	"wlan" prefix.  Scripts that use them should be adjusted
286dba929aSSam Leffler	accordingly.
296dba929aSSam Leffler
30a0cdeaecSDoug Barton20051202:
31a0cdeaecSDoug Barton	Scripts in the local_startup directories (as defined in
32a0cdeaecSDoug Barton	/etc/defaults/rc.conf) that have the new rc.d semantics will
33a0cdeaecSDoug Barton	now be run as part of the base system rcorder. If there are
34a0cdeaecSDoug Barton	errors or problems with one of these local scripts, it could
35a0cdeaecSDoug Barton	cause boot problems. If you encounter such problems, boot in
36a0cdeaecSDoug Barton	single user mode, remove that script from the */rc.d directory.
37a0cdeaecSDoug Barton	Please report the problem to the port's maintainer, and the
38a0cdeaecSDoug Barton	freebsd-ports@freebsd.org mailing list.
39a0cdeaecSDoug Barton
40b090e4ceSGleb Smirnoff20051129:
41a358ddbbSCraig Rodrigues	The nodev mount option was deprecated in RELENG_6 (where it
42a358ddbbSCraig Rodrigues	was a no-op), and is now unsupported.  If you have nodev or dev listed
43a358ddbbSCraig Rodrigues	in /etc/fstab, remove it, otherwise it will result in a mount error.
44a358ddbbSCraig Rodrigues
45a358ddbbSCraig Rodrigues20051129:
46b090e4ceSGleb Smirnoff	ABI between ipfw(4) and ipfw(8) has been changed. You need
47b090e4ceSGleb Smirnoff	to rebuild ipfw(8) when rebuilding kernel.
48b090e4ceSGleb Smirnoff
49d6b4b3b3SDavid E. O'Brien20051108:
50d6b4b3b3SDavid E. O'Brien	rp(4)'s device files now contain the unit number.
51d6b4b3b3SDavid E. O'Brien	Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
52d6b4b3b3SDavid E. O'Brien
53a52364d5SYaroslav Tykhiy20051029:
54a52364d5SYaroslav Tykhiy	/etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
55a52364d5SYaroslav Tykhiy	Its /etc/rc.conf.d configuration file has been `ppp' from
56a52364d5SYaroslav Tykhiy	the beginning, and hence there is no need to touch it.
57a52364d5SYaroslav Tykhiy
58114d09d8SGleb Smirnoff20051001:
59114d09d8SGleb Smirnoff	kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
60114d09d8SGleb Smirnoff	to turn polling(4) on your interfaces.
61114d09d8SGleb Smirnoff
62b6de9e91SMax Laier20050927:
63b6de9e91SMax Laier	The old bridge(4) implementation was retired.  The new
64b6de9e91SMax Laier	if_bridge(4) serves as a full functional replacement.
65b6de9e91SMax Laier
66bb518265SHajimu UMEMOTO20050722:
67bb518265SHajimu UMEMOTO	The ai_addrlen of a struct addrinfo was changed to a socklen_t
68bb518265SHajimu UMEMOTO	to conform to POSIX-2001.  This change broke an ABI
69bb518265SHajimu UMEMOTO	compatibility on 64 bit architecture.  You have to recompile
70bb518265SHajimu UMEMOTO	userland programs that use getaddrinfo(3) on 64 bit
71bb518265SHajimu UMEMOTO	architecture.
72bb518265SHajimu UMEMOTO
7399b22782SKen Smith20050711:
7499b22782SKen Smith	RELENG_6 branched here.
7599b22782SKen Smith
767657f595SBrooks Davis20050629:
777657f595SBrooks Davis	The pccard_ifconfig rc.conf variable has been removed and a new
787657f595SBrooks Davis	variable, ifconfig_DEFAULT has been introduced.  Unlike
797657f595SBrooks Davis	pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
807657f595SBrooks Davis	do not have ifconfig_ifn entries rather than just those in
817657f595SBrooks Davis	removable_interfaces.
827657f595SBrooks Davis
83d33db00cSDag-Erling Smørgrav20050616:
84d33db00cSDag-Erling Smørgrav	Some previous versions of PAM have permitted the use of
85d33db00cSDag-Erling Smørgrav	non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
86d33db00cSDag-Erling Smørgrav	to third party PAM modules in /usr/local/lib.  A change has been
87d33db00cSDag-Erling Smørgrav	made to require the use of absolute paths in order to avoid
88d33db00cSDag-Erling Smørgrav	ambiguity and dependence on library path configuration, which may
89d33db00cSDag-Erling Smørgrav	affect existing configurations.
90d33db00cSDag-Erling Smørgrav
91ad0fdce5SBrooks Davis20050610:
92ad0fdce5SBrooks Davis	Major changes to network interface API.  All drivers must be
93ad0fdce5SBrooks Davis	recompiled.  Drivers not in the base system will need to be
94ad0fdce5SBrooks Davis	updated to the new APIs.
95ad0fdce5SBrooks Davis
96038164a1SGarance A Drosehn20050609:
97038164a1SGarance A Drosehn	Changes were made to kinfo_proc in sys/user.h.  Please recompile
98038164a1SGarance A Drosehn	userland, or commands like `fstat', `pkill', `ps', `top' and `w'
99038164a1SGarance A Drosehn	will not behave correctly.
100038164a1SGarance A Drosehn
10131f91694SJoseph Koshy	The API and ABI for hwpmc(4) have changed with the addition
10231f91694SJoseph Koshy	of sampling support.  Please recompile lib/libpmc(3) and
10331f91694SJoseph Koshy	usr.sbin/{pmcstat,pmccontrol}.
10431f91694SJoseph Koshy
105a8d23252SBrooks Davis20050606:
106a8d23252SBrooks Davis	The OpenBSD dhclient was imported in place of the ISC dhclient
107a8d23252SBrooks Davis	and the network interface configuration scripts were updated
108a8d23252SBrooks Davis	accordingly.  If you use DHCP to configure your interfaces, you
109a8d23252SBrooks Davis	must now run devd.  Also, DNS updating was lost so you will need
110a8d23252SBrooks Davis	to find a workaround if you use this feature.
111a8d23252SBrooks Davis
112dfa58a49SAndrew Thompson20050605:
113dfa58a49SAndrew Thompson	if_bridge was added to the tree. This has changed struct ifnet.
114dfa58a49SAndrew Thompson	Please recompile userland and all network related modules.
115dfa58a49SAndrew Thompson
1162554b2d1SHajimu UMEMOTO20050603:
1172554b2d1SHajimu UMEMOTO	The n_net of a struct netent was changed to an uint32_t, and
1182554b2d1SHajimu UMEMOTO	1st argument of getnetbyaddr() was changed to an uint32_t, to
1191d6a063bSHajimu UMEMOTO	conform to POSIX-2001.  These changes broke an ABI
1200fe9e21bSHajimu UMEMOTO	compatibility on 64 bit architecture.  With these changes,
1210fe9e21bSHajimu UMEMOTO	shlib major of libpcap was bumped.  You have to recompile
1220fe9e21bSHajimu UMEMOTO	userland programs that use getnetbyaddr(3), getnetbyname(3),
1230fe9e21bSHajimu UMEMOTO	getnetent(3) and/or libpcap on 64 bit architecture.
1242554b2d1SHajimu UMEMOTO
1250a4c2543SGarance A Drosehn20050528:
1260a4c2543SGarance A Drosehn	Kernel parsing of extra options on '#!' first lines of shell
1270a4c2543SGarance A Drosehn	scripts has changed.  Lines with multiple options likely will
1280a4c2543SGarance A Drosehn	fail after this date.  For full details, please see
1290a4c2543SGarance A Drosehn		http://people.freebsd.org/~gad/Updating-20050528.txt
1300a4c2543SGarance A Drosehn
1316441fe95SMax Laier20050503:
1326441fe95SMax Laier	The packet filter (pf) code has been updated to OpenBSD 3.7
1336441fe95SMax Laier	Please note the changed anchor syntax and the fact that
1346441fe95SMax Laier	authpf(8) now needs a mounted fdescfs(5) to function.
1356441fe95SMax Laier
136cfdb76e5SScott Long20050415:
137cfdb76e5SScott Long	The NO_MIXED_MODE kernel option has been removed from the i386
138cfdb76e5SScott Long	amd64 platforms as its use has been superceded by the new local
139cfdb76e5SScott Long	APIC timer code.  Any kernel config files containing this option
140cfdb76e5SScott Long	should be updated.
141cfdb76e5SScott Long
1424bb8b8beSRuslan Ermilov20050227:
1434bb8b8beSRuslan Ermilov	The on-disk format of LC_CTYPE files was changed to be machine
1444bb8b8beSRuslan Ermilov	independent.  Please make sure NOT to use NO_CLEAN buildworld
14565f1be68SGleb Smirnoff	when crossing this point. Crossing this point also requires
14665f1be68SGleb Smirnoff	recompile or reinstall of all locale depended packages.
1474bb8b8beSRuslan Ermilov
148bc9d2991SBrooks Davis20050225:
149bc9d2991SBrooks Davis	The ifi_epoch member of struct if_data has been changed to
150bc9d2991SBrooks Davis	contain the uptime at which the interface was created or the
151bc9d2991SBrooks Davis	statistics zeroed rather then the wall clock time because
152bc9d2991SBrooks Davis	wallclock time may go backwards.  This should have no impact
153bc9d2991SBrooks Davis	unless an snmp implementation is using this value (I know of
154bc9d2991SBrooks Davis	none at this point.)
155bc9d2991SBrooks Davis
156915a554bSNate Lawson20050224:
157915a554bSNate Lawson	The acpi_perf and acpi_throttle drivers are now part of the
158915a554bSNate Lawson	acpi(4) main module.  They are no longer built separately.
159915a554bSNate Lawson
16010d6bd76SNate Lawson20050223:
16190dc539bSMaxim Sobolev	The layout of struct image_params has changed. You have to
16290dc539bSMaxim Sobolev	recompile all compatibility modules (linux, svr4, etc) for use
16390dc539bSMaxim Sobolev	with the new kernel.
16490dc539bSMaxim Sobolev
16590dc539bSMaxim Sobolev20050223:
16610d6bd76SNate Lawson	The p4tcc driver has been merged into cpufreq(4).  This makes
16710d6bd76SNate Lawson	"options CPU_ENABLE_TCC" obsolete.  Please load cpufreq.ko or
16810d6bd76SNate Lawson	compile in "device cpufreq" to restore this functionality.
16910d6bd76SNate Lawson
170aea80a64SXin LI20050220:
171aea80a64SXin LI	The responsibility of recomputing the file system summary of
172aea80a64SXin LI	a SoftUpdates-enabled dirty volume has been transferred to the
173aea80a64SXin LI	background fsck.  A rebuild of fsck(8) utility is recommended
174aea80a64SXin LI	if you have updated the kernel.
175aea80a64SXin LI
176aea80a64SXin LI	To get the old behavior (recompute file system summary at mount
177aea80a64SXin LI	time), you can set vfs.ffs.compute_summary_at_mount=1 before
178aea80a64SXin LI	mounting the new volume.
179aea80a64SXin LI
180da71ab85SGleb Smirnoff20050206:
181398dd94cSNate Lawson	The cpufreq import is complete.  As part of this, the sysctls for
182915a554bSNate Lawson	acpi(4) throttling have been removed.  The power_profile script
183398dd94cSNate Lawson	has been updated, so you can use performance/economy_cpu_freq in
184915a554bSNate Lawson	rc.conf(5) to set AC on/offline cpu frequencies.
185398dd94cSNate Lawson
186398dd94cSNate Lawson20050206:
187da71ab85SGleb Smirnoff	NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
188da71ab85SGleb Smirnoff	requires recompiling libnetgraph and userland netgraph utilities.
1895ddd0622SBrooks Davis
1905ddd0622SBrooks Davis20050114:
1915ddd0622SBrooks Davis	Support for abbreviated forms of a number of ipfw options is
1925ddd0622SBrooks Davis	now deprecated.  Warnings are printed to stderr indicating the
1935ddd0622SBrooks Davis	correct full form when a match occurs.  Some abbreviations may
1945ddd0622SBrooks Davis	be supported at a later date based on user feedback.  To be
1955ddd0622SBrooks Davis	considered for support, abbreviations must be in use prior to
1965ddd0622SBrooks Davis	this commit and unlikely to be confused with current key words.
1975ddd0622SBrooks Davis
198b521988eSRuslan Ermilov20041221:
199b521988eSRuslan Ermilov	By a popular demand, a lot of NOFOO options were renamed
200b521988eSRuslan Ermilov	to NO_FOO (see bsd.compat.mk for a full list).  The old
201b521988eSRuslan Ermilov	spellings are still supported, but will cause annoying
202b521988eSRuslan Ermilov	warnings on stderr.  Make sure you upgrade properly (see
203b521988eSRuslan Ermilov	the COMMON ITEMS: section later in this file).
204b521988eSRuslan Ermilov
20587c9e370SSam Leffler20041219:
20687c9e370SSam Leffler	Auto-loading of ancillary wlan modules such as wlan_wep has
20787c9e370SSam Leffler	been temporarily disabled; you need to statically configure
20887c9e370SSam Leffler	the modules you need into your kernel or explicitly load them
20987c9e370SSam Leffler	prior to use.  Specifically, if you intend to use WEP encryption
21087c9e370SSam Leffler	with an 802.11 device load/configure wlan_wep; if you want to
21187c9e370SSam Leffler	use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
21287c9e370SSam Leffler	and wlan_xauth as required.
21387c9e370SSam Leffler
21471c1c49aSBrian Somers20041213:
21571c1c49aSBrian Somers	The behaviour of ppp(8) has changed slightly.  If lqr is enabled
21671c1c49aSBrian Somers	(``enable lqr''), older versions would revert to LCP ECHO mode on
21771c1c49aSBrian Somers	negotiation failure.  Now, ``enable echo'' is required for this
21871c1c49aSBrian Somers	behaviour.  The ppp version number has been bumped to 3.4.2 to
21971c1c49aSBrian Somers	reflect the change.
22071c1c49aSBrian Somers
22188046524SSam Leffler20041201:
22288046524SSam Leffler	The wlan support has been updated to split the crypto support
22388046524SSam Leffler	into separate modules.  For static WEP you must configure the
22488046524SSam Leffler	wlan_wep module in your system or build and install the module
22588046524SSam Leffler	in place where it can be loaded (the kernel will auto-load
22688046524SSam Leffler	the module when a wep key is configured).
22788046524SSam Leffler
22888046524SSam Leffler20041201:
22988046524SSam Leffler	The ath driver has been updated to split the tx rate control
23088046524SSam Leffler	algorithm into a separate module.  You need to include either
23188046524SSam Leffler	ath_rate_onoe or ath_rate_amrr when configuring the kernel.
23288046524SSam Leffler
23381adddf3SJohn Baldwin20041116:
23481adddf3SJohn Baldwin	Support for systems with an 80386 CPU has been removed.  Please
23581adddf3SJohn Baldwin	use FreeBSD 5.x or earlier on systems with an 80386.
23681adddf3SJohn Baldwin
23742ba1c57SPoul-Henning Kamp20041110:
23842ba1c57SPoul-Henning Kamp	We have had a hack which would mount the root filesystem
23942ba1c57SPoul-Henning Kamp	R/W if the device were named 'md*'.  As part of the vnode
24042ba1c57SPoul-Henning Kamp	work I'm doing I have had to remove this hack.  People
24142ba1c57SPoul-Henning Kamp	building systems which use preloaded MD root filesystems
24242ba1c57SPoul-Henning Kamp	may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
24342ba1c57SPoul-Henning Kamp	their /etc/rc scripts.
24442ba1c57SPoul-Henning Kamp
245dcb5d8f8SRuslan Ermilov20041104:
246dcb5d8f8SRuslan Ermilov	FreeBSD 5.3 shipped here.
247dcb5d8f8SRuslan Ermilov
248c94c54e4SAndre Oppermann20041102:
249c94c54e4SAndre Oppermann	The size of struct tcpcb has changed again due to the removal
250c94c54e4SAndre Oppermann	of RFC1644 T/TCP.  You have to recompile userland programs that
251c94c54e4SAndre Oppermann	read kmem for tcp sockets directly (netstat, sockstat, etc.)
252c94c54e4SAndre Oppermann
253cd109b0dSAndre Oppermann20041022:
254cd109b0dSAndre Oppermann	The size of struct tcpcb has changed.  You have to recompile
255cd109b0dSAndre Oppermann	userland programs that read kmem for tcp sockets directly
256cd109b0dSAndre Oppermann	(netstat, sockstat, etc.)
257cd109b0dSAndre Oppermann
258b2723608SWarner Losh20041016:
259b2723608SWarner Losh	RELENG_5 branched here.  For older entries, please see updating
260b2723608SWarner Losh	in the RELENG_5 branch.
26157199806SWarner Losh
262dc0dbf5cSWarner LoshCOMMON ITEMS:
263dc0dbf5cSWarner Losh
264a24eff53SWarner Losh	General Notes
265a24eff53SWarner Losh	-------------
266a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
267a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
268a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
269a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
270a24eff53SWarner Losh	or several minor releases, or when several months have passed
271a24eff53SWarner Losh	on the -current branch).
272a24eff53SWarner Losh
2735780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
2745780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
2755780f3baSWarner Losh	environment when searching for values for global variables.
2765780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
2775780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
2785780f3baSWarner Losh	page for more details.
2795780f3baSWarner Losh
280081ff8acSDoug Barton	When upgrading from one major version to another it is generally
281081ff8acSDoug Barton	best to upgrade to the latest code in the currently installed branch
282081ff8acSDoug Barton	first, then do an upgrade to the new branch. This is the best-tested
283081ff8acSDoug Barton	upgrade path, and has the highest probability of being successful.
284081ff8acSDoug Barton	Please try this approach before reporting problems with a major
285081ff8acSDoug Barton	version upgrade.
286081ff8acSDoug Barton
287dc0dbf5cSWarner Losh	To build a kernel
288dc0dbf5cSWarner Losh	-----------------
289ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
2901cf0ef11SDavid E. O'Brien	a few days old), you should follow this procedure.  It is the most
2911cf0ef11SDavid E. O'Brien	failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2921cf0ef11SDavid E. O'Brien
2931cf0ef11SDavid E. O'Brien	make kernel-toolchain
294282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
295282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
296dc0dbf5cSWarner Losh
2972e937dd6SAlexander Leidinger	To test a kernel once
2982e937dd6SAlexander Leidinger	---------------------
2992e937dd6SAlexander Leidinger	If you just want to boot a kernel once (because you are not sure
3002e937dd6SAlexander Leidinger	if it works, or if you want to boot a known bad kernel to provide
3012e937dd6SAlexander Leidinger	debugging information) run
3022e937dd6SAlexander Leidinger	make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
3032e937dd6SAlexander Leidinger	nextboot -k testkernel
3042e937dd6SAlexander Leidinger
305ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
306ba01eb20SWarner Losh	--------------------------------------------------------------
3070fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
3080fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
3090fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
3100fbd2da9SKen Smith
3110fbd2da9SKen Smith	cd src/sys/${arch}/conf
31247d0d01fSWarner Losh	config KERNEL_NAME_HERE
3130fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
314ba01eb20SWarner Losh	make depend
315ba01eb20SWarner Losh	make
316ba01eb20SWarner Losh	make install
317ba01eb20SWarner Losh
318ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
319ba01eb20SWarner Losh
320ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
321ba01eb20SWarner Losh	-----------------------------------------------------------
32263cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
32363cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
32463cb445eSWarner Losh
325f643de42SWarner Losh	<make sure you have good level 0 dumps>
32663cb445eSWarner Losh	make buildworld
3276586253aSWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE
32863cb445eSWarner Losh							[1]
32963cb445eSWarner Losh	<reboot in single user>				[3]
33063cb445eSWarner Losh	mergemaster -p					[5]
33163cb445eSWarner Losh	make installworld
332e2a36081SAlexander Leidinger	make delete-old
33363cb445eSWarner Losh	mergemaster					[4]
33463cb445eSWarner Losh	<reboot>
33563cb445eSWarner Losh
336759f0aefSWarner Losh
337f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
338f27b1fceSJoseph Koshy	--------------------------------------------------
339f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
340f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
341f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
342f27b1fceSJoseph Koshy	# size.
343f27b1fceSJoseph Koshy
344f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
345f27b1fceSJoseph Koshy	<boot into -stable>
346f27b1fceSJoseph Koshy	make buildworld
3473ecf3bddSRuslan Ermilov	make buildkernel KERNCONF=YOUR_KERNEL_HERE
348f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
349f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
350f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
3516586253aSWarner Losh	cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
3523ecf3bddSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
353f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
354f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
355f27b1fceSJoseph Koshy	<reboot into current>
356f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
3576586253aSWarner Losh	<maybe install compatibility libraries from src/lib/compat>
358f27b1fceSJoseph Koshy 	<reboot>
359f27b1fceSJoseph Koshy
360f27b1fceSJoseph Koshy
3618ce4cbbfSWarner Losh	To upgrade in-place from 5.x-stable to current
362f27b1fceSJoseph Koshy	----------------------------------------------
363f643de42SWarner Losh	<make sure you have good level 0 dumps>
36421c075eaSWarner Losh	make buildworld					[9]
365e5dc5f61SWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE		[8]
366fc8c157fSWarner Losh							[1]
367fc8c157fSWarner Losh	<reboot in single user>				[3]
368835284beSWarner Losh	mergemaster -p					[5]
369ba26da8eSWarner Losh	make installworld
370e2a36081SAlexander Leidinger	make delete-old
371802fc49dSBrian Feldman	mergemaster -i					[4]
372ba26da8eSWarner Losh	<reboot>
373ba26da8eSWarner Losh
374fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
375fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
376fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
377fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
378fdb9f54dSWarner Losh	the UPDATING entries.
379ba26da8eSWarner Losh
3801dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
3811dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
3821dece4a9SWarner Losh	your sources that you have read and understood all the recent
3831dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
3841dece4a9SWarner Losh	much fewer pitfalls.
3851dece4a9SWarner Losh
386134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
387134d2e86SWarner Losh	should disable them at this point so they don't crash your
388134d2e86SWarner Losh	system on reboot.
389134d2e86SWarner Losh
390ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
391ee6e1fc3SWarner Losh		fsck -p
392ee6e1fc3SWarner Losh		mount -u /
393ee6e1fc3SWarner Losh		mount -a
3946586253aSWarner Losh		cd src
39547d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
396f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
397f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
398ee6e1fc3SWarner Losh
399a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
400a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
401a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
402a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
403a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
404a6cd4f9dSWarner Losh	for potential gotchas.
405a6cd4f9dSWarner Losh
406835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
407835284beSWarner Losh	you may need to do this if you get unknown user in the following
408835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
409835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
410835284beSWarner Losh	install) after the buildworld before this step if you last updated
411835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
412835284beSWarner Losh
413c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
414c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
415c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
41665f1be68SGleb Smirnoff	that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
41765f1be68SGleb Smirnoff	is required to run the 5.x binaries on more recent kernels.
418c74fe6afSWarner Losh
419e5dc5f61SWarner Losh	Make sure that you merge any new devices from GENERIC since the
420e5dc5f61SWarner Losh	last time you updated your kernel config file.
421e5dc5f61SWarner Losh
42221c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
423e5dc5f61SWarner Losh	cvs prune empty directories.
424e5dc5f61SWarner Losh
425e5dc5f61SWarner Losh	If CPUTYPE is defined in your /etc/make.conf, make sure to use the
426e5dc5f61SWarner Losh	"?=" instead of the "=" assignment operator, so that buildworld can
427e5dc5f61SWarner Losh	override the CPUTYPE if it needs to.
428e5dc5f61SWarner Losh
429e5dc5f61SWarner Losh	MAKEOBJDIRPREFIX must be defined in an environment variable, and
430e5dc5f61SWarner Losh	not on the command line, or in /etc/make.conf.  buildworld will
431e5dc5f61SWarner Losh	warn if it is improperly defined.
432dc0dbf5cSWarner LoshFORMAT:
433dc0dbf5cSWarner Losh
434f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
4351fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
4368ce4cbbfSWarner Loshand it only starts on October 16, 2004.  Updating files can found in
437f8ab1dd6SWarner Loshprevious releases if your system is older than this.
4381fc1a0dcSWarner Losh
439e72fd46aSWarner LoshCopyright information:
440e72fd46aSWarner Losh
4418ce4cbbfSWarner LoshCopyright 1998-2005 M. Warner Losh.  All Rights Reserved.
442e72fd46aSWarner Losh
443772730c7SWarner LoshRedistribution, publication, translation and use, with or without
444772730c7SWarner Loshmodification, in full or in part, in any form or format of this
4459698f2c0SWarner Loshdocument are permitted without further permission from the author.
446e72fd46aSWarner Losh
447e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
448e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
449e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
450e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
451e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
452e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
453e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
454e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
455e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
456e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
457e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
458e72fd46aSWarner Losh
459e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
460e72fd46aSWarner Loshauthor a beer.
461e72fd46aSWarner Losh
46222306abcSWarner LoshContact Warner Losh if you have any questions about your use of
463772730c7SWarner Loshthis document.
464772730c7SWarner Losh
46597d92980SPeter Wemm$FreeBSD$
466