xref: /freebsd/UPDATING (revision 58970f854bc0f851635d1039dd55bf71fec690a8)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh
4e72fd46aSWarner Losh<imp@village.org>.  Please send new entries directly to him.  See end
5e72fd46aSWarner Loshof file for further details.  For commonly done items, please see the
6e72fd46aSWarner LoshCOMMON ITEMS: section later in the file.
7e72fd46aSWarner Losh
858970f85SWarner Losh20010929:
958970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
1058970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
1158970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
1258970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
1358970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
1458970f85SWarner Losh
1558970f85SWarner Losh20010927:
1658970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
1758970f85SWarner Losh	To disable ACPI you can add
18378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
1958970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
2058970f85SWarner Losh	loader "ok" prompt).
2158970f85SWarner Losh
2258970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
2358970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
2458970f85SWarner Losh	file and not list acpi in that list.
25378f4486SAlfred Perlstein
265119d237SWarner Losh20010924:
275119d237SWarner Losh	The buildworld has been fixed.  You may need to install
285119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
2958970f85SWarner Losh	to work.
3058970f85SWarner Losh		cd src/lib/compat/compat4x.i386
3158970f85SWarner Losh		make all install
325119d237SWarner Losh
333c293725SWarner Losh20010919:
343c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
353c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
363c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
37772730c7SWarner Losh	workaround is to add
383c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
393c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
403c293725SWarner Losh	can be removed afterwards.
413c293725SWarner Losh
423c293725SWarner Losh	A proper fix to the buildworld target is needed.
433c293725SWarner Losh
443c293725SWarner Losh20010918:
453c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
463c293725SWarner Losh	NFS may be unstable after this date.
473c293725SWarner Losh
483c293725SWarner Losh20010912:
493c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
503c293725SWarner Losh	the kernel.  While a few problems were introduced in the
513c293725SWarner Losh	initial commit, most of the major ones have been found and
523c293725SWarner Losh	corrected.
533c293725SWarner Losh
543c293725SWarner Losh20010901:
553c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
563c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
573c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
583c293725SWarner Losh	have been rectified around this date.
593c293725SWarner Losh
6098b17b95SWarner Losh20010823:
6198b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
6298b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
6398b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
6498b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
6598b17b95SWarner Losh 	sure that user or group bind has read (and not write)
6698b17b95SWarner Losh 	permission for your name server configuration and that it
6798b17b95SWarner Losh 	has read and write permission for your slave zone files and
6898b17b95SWarner Losh 	directory.
6998b17b95SWarner Losh
7098b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
7198b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
7298b17b95SWarner Losh
7398b17b95SWarner Losh 		named_flags=
7498b17b95SWarner Losh
757b9786edSMark Murray20010709:
767b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
777b9786edSMark Murray	the ability of the shared library major number to handle.
787b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
797b9786edSMark Murray	solution is to rebuild those ports.
807b9786edSMark Murray
811d28950eSWarner Losh20010628:
821d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
831d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
841d28950eSWarner Losh
85e72fd46aSWarner Losh20010625:
8698b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
8798b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
8898b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
8998b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
9098b17b95SWarner Losh	IRQ configuration needs more safety belts.
9116de1a07SWarner Losh
920d415dffSWarner Losh20010617:
93e72fd46aSWarner Losh	Softupdates problems have been corrected.
940d415dffSWarner Losh
950d415dffSWarner Losh20010614:
960d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
970d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
980d415dffSWarner Losh	kernel building methods.
990d415dffSWarner Losh
1008b9959adSWarner Losh20010613:
1018b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
1028b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
103e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
104e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
1058b9959adSWarner Losh
106e72fd46aSWarner Losh20010613:
1078b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
108e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
109e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
1108b9959adSWarner Losh
1110d415dffSWarner Losh20010612:
1120d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
1130d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
1140d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
1150d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
1160d415dffSWarner Losh	until this bug is fixed.
1170d415dffSWarner Losh
118e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
119e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
120e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
121e72fd46aSWarner Losh
1220d415dffSWarner Losh20010610:
1230d415dffSWarner Losh	Locale names have changed to match other systems better.
1240d415dffSWarner Losh
1256ccdb5e4SWarner Losh20010604:
1266ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
1276ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
1286ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
1293590182eSWarner Losh	Interrupt storms look a lot like a hang.
1303590182eSWarner Losh
1313590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
1323590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
1333590182eSWarner Losh	it is).
1343590182eSWarner Losh
1353590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
1363590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
1373590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
1383590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
1396ccdb5e4SWarner Losh
1400bc62786SWarner Losh20010530:
1410bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
1420bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
1430bc62786SWarner Losh	a limited time.  If you see
1440bc62786SWarner Losh
1450bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
1460bc62786SWarner Losh
1470bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
1480bc62786SWarner Losh	COPY=-C.
1490bc62786SWarner Losh
15068a38c6cSWarner Losh20010525:
151b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
152c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
153c4f4a728SWarner Losh	definitely is in bad shape.
15468a38c6cSWarner Losh
155ed0f29caSWarner Losh20010521:
156f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
157ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
158ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
159ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
160ed0f29caSWarner Losh	is
161ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
162ed0f29caSWarner Losh
16380c16af9SWarner Losh20010520:
16468a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
16580c16af9SWarner Losh
16680c16af9SWarner Losh20010519:
16780c16af9SWarner Losh	pccard has had much reorganizational work done to it over
16880c16af9SWarner Losh	the past few days.  Everything should still work, but if
16980c16af9SWarner Losh	not, please contact imp@freebsd.org.
17080c16af9SWarner Losh
171a45f2d05SWarner Losh20010517:
172a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
173a45f2d05SWarner Losh	userland at the same time.
174a45f2d05SWarner Losh
175a45f2d05SWarner Losh20010517:
176a45f2d05SWarner Losh	New ncurses imported.
177a45f2d05SWarner Losh
1782988afcaSWarner Losh20010512:
1792988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
1802988afcaSWarner Losh	will be the only way to go starting July 1.
1812988afcaSWarner Losh
18209946a51SWarner Losh20010502:
18309946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
18409946a51SWarner Losh
18509946a51SWarner Losh20010501:
18609946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
18709946a51SWarner Losh
18809946a51SWarner Losh20010430:
189a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
19009946a51SWarner Losh	go back in the water.
19109946a51SWarner Losh
19209946a51SWarner Losh20010429:
19309946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
19409946a51SWarner Losh	this date, but before the correction date.
19509946a51SWarner Losh
19691dd3b53SWarner Losh20010423:
19791dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
19891dd3b53SWarner Losh
19991dd3b53SWarner Losh20010411:
20091dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
20191dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
20291dd3b53SWarner Losh	Update only if you understand that you must not use the old
20391dd3b53SWarner Losh	fsck with the new kernel ever.
20491dd3b53SWarner Losh
205933b3269SWarner Losh20010330:
206933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
207c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
208933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
209933b3269SWarner Losh
210933b3269SWarner Losh20010319:
211933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
212933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
213933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
214f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
21509946a51SWarner Losh
21609946a51SWarner Losh20010315:
21709946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
21809946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
21909946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
220933b3269SWarner Losh
221933b3269SWarner Losh20010312:
222933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
223933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
224933b3269SWarner Losh
225933b3269SWarner Losh20010312:
226933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
227933b3269SWarner Losh	instead of ad-hoc.
228933b3269SWarner Losh
229933b3269SWarner Losh20010310:
230f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
231933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
232933b3269SWarner Losh	ssh might not work if you don't.
233933b3269SWarner Losh
23462353691SWarner Losh20010303:
23562353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
23662353691SWarner Losh	which means that you must include the miibus in your kernel if
23762353691SWarner Losh	you use the ed driver.
23862353691SWarner Losh
239d325cf65SWarner Losh20010220:
240d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
241d325cf65SWarner Losh	safe to go back into the water.
242d325cf65SWarner Losh
243024daae6SWarner Losh20010211:
244024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
245024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
246024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
247024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
248024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
249024daae6SWarner Losh
250024daae6SWarner Losh	To get to the new system, you'll need to use the following
251024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
252024daae6SWarner Losh	don't have to move this to the updating section.
253024daae6SWarner Losh
254024daae6SWarner Losh	To get around the installworld problem, do:
255024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
256024daae6SWarner Losh		# make install
257024daae6SWarner Losh		# cd /usr/src
258024daae6SWarner Losh		# make installworld
259024daae6SWarner Losh	If that doesn't work, then try:
260024daae6SWarner Losh		# make -k installworld
261024daae6SWarner Losh		# make installworld
262024daae6SWarner Losh
263024daae6SWarner Losh20010207:
264024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
265024daae6SWarner Losh	do not include devfs in your kernel as problems result.
266024daae6SWarner Losh
267024daae6SWarner Losh20010205:
2687595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
269024daae6SWarner Losh	Remove them from your config.
270024daae6SWarner Losh
2711e159248SWarner Losh20010122:
2721e159248SWarner Losh	****************************** WARNING ******************************
2731e159248SWarner Losh			buildkernel has been changed slightly
2741e159248SWarner Losh	****************************** WARNING ******************************
2751e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
2761e159248SWarner Losh	should update your scripts and make.conf accordingly.
2771e159248SWarner Losh
2781e159248SWarner Losh20010119:
2791e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
2801e159248SWarner Losh	This requires a new config to build correctly.
2811e159248SWarner Losh
282aac7dfeaSWarner Losh20010116:
283aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
284aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
285aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
286aac7dfeaSWarner Losh
287aac7dfeaSWarner Losh20010110:
288aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
289aac7dfeaSWarner Losh
290aac7dfeaSWarner Losh20010102:
291aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
292aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
293aac7dfeaSWarner Losh
29463c90c9eSWarner Losh20010101:
29563c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
29663c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
2975fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
29863c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
29963c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
30063c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
30163c90c9eSWarner Losh	might have been ignored by the -k option.
30263c90c9eSWarner Losh
3035fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
3045fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
3055fd2a895SWarner Losh	of this working.
3065fd2a895SWarner Losh
307aac7dfeaSWarner Losh20001228:
308aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
309aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
310aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
311aac7dfeaSWarner Losh
312de2bcc63SWarner Losh20001218:
313de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
314de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
315de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
316de2bcc63SWarner Losh	cards will not be recognized without it.
317de2bcc63SWarner Losh
318960773f7SWarner Losh20001205:
319960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
320960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
321960773f7SWarner Losh	adding the following in pam.conf:
322960773f7SWarner Losh
323960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
324960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
325960773f7SWarner Losh	sshd    session required        pam_permit.so
326960773f7SWarner Losh
3270acc635eSWarner Losh20001031:
3280acc635eSWarner Losh	cvs updated to 1.11.
3290acc635eSWarner Losh
3300acc635eSWarner Losh20001020:
3310acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
3320acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
3330acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
3340acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
3350acc635eSWarner Losh	workaround.
3360acc635eSWarner Losh
3370acc635eSWarner Losh20001010:
3380acc635eSWarner Losh	****************************** WARNING ******************************
3390acc635eSWarner Losh				Sendmail has been updated.
3400acc635eSWarner Losh	****************************** WARNING ******************************
3410acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
3420acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
3430acc635eSWarner Losh	  is set.
3440acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
3450acc635eSWarner Losh	  commands.
3460acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
3470acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
3480acc635eSWarner Losh	  in /usr/share/sendmail/cf.
3490acc635eSWarner Losh	o sendmail.cw changed to local-host-names
3500acc635eSWarner Losh
3510acc635eSWarner Losh	More details can be found at
3520acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
3530acc635eSWarner Losh
3546e98a146SWarner Losh20001009:
3556e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
3566e98a146SWarner Losh	your entire ports tree, or you will have problems.
3576e98a146SWarner Losh
3586e98a146SWarner Losh20001006:
359685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
3606e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
3616e98a146SWarner Losh	/usr/bin/miniperl.
3626e98a146SWarner Losh
363073113a4SWarner Losh20001005:
364073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
365685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
366073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
367073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
368073113a4SWarner Losh	tree for anything to work.
369073113a4SWarner Losh
3700acc635eSWarner Losh20000928:
3710acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
3720acc635eSWarner Losh
373be3885b3SWarner Losh20000916:
374be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
375be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
376be3885b3SWarner Losh	same time as your kernel.
377be3885b3SWarner Losh
37876ec9675SWarner Losh20000914:
37976ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
38076ec9675SWarner Losh	include the device will cause suspended laptops losing time
38176ec9675SWarner Losh	when they resume.  Include
38276ec9675SWarner Losh		device		pmtimer
38376ec9675SWarner Losh	in your config file and
38401b9a434SWarner Losh		hint.pmtimer.0.at="isa"
38576ec9675SWarner Losh	to your /boot/device.hints file.
38676ec9675SWarner Losh
387f4865386SMark Murray20000911:
388f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
389f4865386SMark Murray	rather than an option. The supplied kernel config files have
390f4865386SMark Murray	been updated. You will need to do something similar in your
391f4865386SMark Murray	own kernel config file.
392f4865386SMark Murray	Remove:
393f4865386SMark Murray		options		RANDOMDEV
394f4865386SMark Murray	Add:
395f4865386SMark Murray		device		random
396f4865386SMark Murray	If you prefer to load the loadable module, you need to do
397f4865386SMark Murray	nothing.
398f4865386SMark Murray
399d594498fSWarner Losh20000909:
400d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
401d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
402d594498fSWarner Losh	reflect this if you load this module at boot time.
403d594498fSWarner Losh	The line should read:
404d594498fSWarner Losh		random_load="YES"
405d594498fSWarner Losh
4060deb7ddcSWarner Losh20000907:
4070deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
40816eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
40916eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
41016eb772dSWarner Losh	sure you don't have model loading problems which might at
41116eb772dSWarner Losh	first blush appear related to SMP.
41252bf24e7SWarner Losh
4135a01880bSWarner Losh20000906:
4145a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
4155a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
4165a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
4175a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
4185a01880bSWarner Losh	don't have one, and you have host.conf.
4195a01880bSWarner Losh
4202b41163cSWarner Losh20000905:
42138d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
42238d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
42338d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
42438d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
42538d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
42638d6ecd2SWarner Losh
42738d6ecd2SWarner Losh20000905:
4288aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
4298aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
4308aab4bc7SWarner Losh	is /boot/kernel.
4318aab4bc7SWarner Losh
4328aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
43338d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
43438d6ecd2SWarner Losh	installkernel/installworld dance.
4352b41163cSWarner Losh
436d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
437d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
438d594498fSWarner Losh	modules in that directory instead of finding them in the correct
439d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
440d594498fSWarner Losh	is that the linux module crashes your machine after the update.
441d594498fSWarner Losh
442d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
443d594498fSWarner Losh		mv /modules.old /boot/kernel.old
444d594498fSWarner Losh		chflags noschg /kernel.old
445d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
446d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
447d594498fSWarner Losh	fi
448d594498fSWarner Losh
449c22a309cSWarner Losh20000904:
450c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
451c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
452c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
453c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
454c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
455c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
456c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
457c22a309cSWarner Losh	is not likely to be generated.
458c22a309cSWarner Losh
459fdb9f54dSWarner Losh20000825:
460fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
4619c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
4629c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
4639c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
4649c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
4659c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
4669c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
4679c1a7444SWarner Losh	kernel.
4689c1a7444SWarner Losh
4699c1a7444SWarner Losh20000821:
4709c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
4719c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
4729c1a7444SWarner Losh	/boot/loader.conf.
473fdb9f54dSWarner Losh
4748f250aa7SWarner Losh20000812:
4755da0d091SWarner Losh	suidperl is now always built and installed on the system, but
4765da0d091SWarner Losh	with permissions of 511.  If you have applications that use
4775da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
4785da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
4795da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
4805da0d091SWarner Losh	will fix this until the next build.
4815da0d091SWarner Losh
4825da0d091SWarner Losh20000812:
4838f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
4848f250aa7SWarner Losh	visible changes that may immediately affect your configuration
4858f250aa7SWarner Losh	include:
4868f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
4878f250aa7SWarner Losh	- newaliases limited to root and trusted users
4888f250aa7SWarner Losh	- MSA port (587) turned on by default
4898f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
4908f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
4918f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
4928f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
4938f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
4948f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
4958f250aa7SWarner Losh
49671c38472SWarner Losh20000810:
49771c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
49871c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
49971c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
50071c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
50171c38472SWarner Losh	specific use for it.
50271c38472SWarner Losh
50371c38472SWarner Losh20000729:
50471c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
50571c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
50671c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
50771c38472SWarner Losh	afterwards (unless the variables already are set, of course):
50871c38472SWarner Losh		# Enable network daemons for user convenience.
50971c38472SWarner Losh		inetd_enable="YES"
51071c38472SWarner Losh		portmap_enable="YES"
51171c38472SWarner Losh		sendmail_enable="YES"
51271c38472SWarner Losh
51371c38472SWarner Losh20000728:
51471c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
51571c38472SWarner Losh	will need to change that to nullfs_load="YES".
51671c38472SWarner Losh
5171dece4a9SWarner Losh20000728:
5181dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
5191dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
5201dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
5211dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
5221dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
5231dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
5241dece4a9SWarner Losh	to /MYKERNEL.
5251dece4a9SWarner Losh
526409e887cSWarner Losh20000711:
527409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
528409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
529409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
530409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
531409e887cSWarner Losh	for details on potential problems that you might have and how
532409e887cSWarner Losh	to get around them.
533409e887cSWarner Losh
534409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
535409e887cSWarner Losh	clauses above, you needn't worry.
536409e887cSWarner Losh
537409e887cSWarner Losh20000711:
538409e887cSWarner Losh	/etc/security has been updated to print the inode number of
539409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
540409e887cSWarner Losh	in the number of changed programs the first time when you run
541409e887cSWarner Losh	mergemaster to get a new /etc/security.
542409e887cSWarner Losh
543673d13f2SWarner Losh20000710:
544673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
545673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
546673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
547673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
548673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
549673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
550673d13f2SWarner Losh	errors. (see below, 20000624).
551673d13f2SWarner Losh
552bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
5531dece4a9SWarner Losh
554673d13f2SWarner Losh20000709:
555c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
556c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
557c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
558673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
559673d13f2SWarner Losh
560e98e26cdSWarner Losh20000706:
561e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
562e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
563e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
564f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
565e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
5662c021c6cSMark Ovens	interim if needed.
567e98e26cdSWarner Losh
568e98e26cdSWarner Losh20000705:
569e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
570e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
571e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
572e98e26cdSWarner Losh	details.
573e98e26cdSWarner Losh
574c373950eSWarner Losh20000704:
5752f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
5762f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
5772f961bc8SWarner Losh
5782f961bc8SWarner Losh20000704:
579c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
580c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
581c373950eSWarner Losh	rc.d scripts that haven't been updated.
582c373950eSWarner Losh
58327dc3a2bSWarner Losh20000630:
58427dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
58527dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
58627dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
58727dc3a2bSWarner Losh
588b8c215acSWarner Losh20000625:
589b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
59027dc3a2bSWarner Losh	system installed in order to build the system and kernel.
59127dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
59227dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
59327dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
59427dc3a2bSWarner Losh	were required.  You should check with the latest collections
59527dc3a2bSWarner Losh	to make sure that these haven't changed.
596b8c215acSWarner Losh
5977b990719SWarner Losh20000624:
5987b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
5997b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
6007b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
6017b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
6027b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
6037b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
6047b990719SWarner Losh	date to the completion of the work.
6057b990719SWarner Losh
60627dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
60727dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
60827dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
60927dc3a2bSWarner Losh	recreate the random and urandom devices.
61027dc3a2bSWarner Losh
61181e54c50SWarner Losh20000622:
61281e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
61381e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
61481e54c50SWarner Losh	that used to be required when updating.
61581e54c50SWarner Losh
61639943833SWarner Losh20000621:
6172c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
6182a2f33fbSDaniel Baker	the config file update procedure.
6192a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
620c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
621a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
62239943833SWarner Losh
623290f9ad8SWarner Losh20000620:
624290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
625290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
626290f9ad8SWarner Losh	that workaround will no longer be required.
627290f9ad8SWarner Losh
62890fb6346SWarner Losh20000615:
62990fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
63090fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
63190fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
63290fb6346SWarner Losh	devices.
63390fb6346SWarner Losh
634f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
635f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
636f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
637f75f65bbSWarner Losh	may work).
638f75f65bbSWarner Losh
639ba26da8eSWarner Losh20000612:
640ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
641290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
642c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
643290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
644f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
645f54a3542SWarner Losh	NEWCARD for examples of the new format.
646290f9ad8SWarner Losh
647d65850ebSWarner Losh20000522:
648ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
649d65850ebSWarner Losh	building a kernel after this point is advised that they need
650d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
651d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
652d65850ebSWarner Losh
653d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
654d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
655d9583a00SWarner Losh	is recommended that you don't set this option until the problem
656d9583a00SWarner Losh	is resolved.
657d9583a00SWarner Losh
6588039cedeSWarner Losh20000513:
6598039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
6608039cedeSWarner Losh
661d65850ebSWarner Losh20000510:
6628039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
6638039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
6648039cedeSWarner Losh	is requires for the boot blocks to build properly.
6658039cedeSWarner Losh
6668039cedeSWarner Losh20000503:
6678039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
6688039cedeSWarner Losh	is now available.
6698039cedeSWarner Losh
670d65850ebSWarner Losh20000502:
671d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
672d65850ebSWarner Losh	connected to the kernel building instead.
673d65850ebSWarner Losh
674be149406SNik Clayton20000427:
6758039cedeSWarner Losh	You may need to build gperf
6768039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
6778039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
6788039cedeSWarner Losh	an option only in -current.
6798039cedeSWarner Losh
6802b8dd5f4SWarner Losh20000417:
6812b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
682f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
6832b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
6842b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
6852c021c6cSMark Ovens	before you reboot, you'll need to issue:
6862b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
6872b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
6882b8dd5f4SWarner Losh
6898d9f1945SWarner Losh20000320:
6902b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
6912b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
6922b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
6938d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
6942b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
6958d9f1945SWarner Losh
696f8ab1dd6SWarner Losh20000319:
697f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
698f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
699f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
700f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
701f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
702f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
703f8ab1dd6SWarner Losh
70419cada77SWarner Losh20000318:
705f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
70619cada77SWarner Losh	Large kernel changes are being committed and are in the
70719cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
70819cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
70919cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
71019cada77SWarner Losh	that you are loading are up to date.
711ba228352SWarner Losh
71219cada77SWarner Losh20000315:
7136d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
7146d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
7156d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
7166d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
7176d23c382SWarner Losh	boot.
7186d23c382SWarner Losh
7196d23c382SWarner Losh20000315:
72019cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
72119cada77SWarner Losh	to upgrade to 4.0 from 3.x.
72257199806SWarner Losh
723dc0dbf5cSWarner LoshCOMMON ITEMS:
724dc0dbf5cSWarner Losh
725a24eff53SWarner Losh	General Notes
726a24eff53SWarner Losh	-------------
727a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
728a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
729a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
730a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
731a24eff53SWarner Losh	or several minor releases, or when several months have passed
732a24eff53SWarner Losh	on the -current branch).
733a24eff53SWarner Losh
734dc0dbf5cSWarner Losh	To build a kernel
735dc0dbf5cSWarner Losh	-----------------
736ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
737f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
738ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
7391e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
7401e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
741dc0dbf5cSWarner Losh
742ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
743ba01eb20SWarner Losh	--------------------------------------------------------------
744ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
745ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
746ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
747ba01eb20SWarner Losh	make depend
748ba01eb20SWarner Losh	make
749ba01eb20SWarner Losh	make install
750ba01eb20SWarner Losh
751ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
752ba01eb20SWarner Losh
753ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
754ba01eb20SWarner Losh
755ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
756ba01eb20SWarner Losh	-----------------------------------------------------------
757759f0aefSWarner Losh	make world
758fdb9f54dSWarner Losh	Build a new kernel, see above.
759759f0aefSWarner Losh
7601dece4a9SWarner Losh	To upgrade from 4.x-stable to current
761ba26da8eSWarner Losh	-------------------------------------
762ba26da8eSWarner Losh	make buildworld
7631e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
7647595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
7651e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
766ee6e1fc3SWarner Losh	reboot in single user [3]
767ba26da8eSWarner Losh	make installworld
768a6cd4f9dSWarner Losh	mergemaster		[4]
769134d2e86SWarner Losh	[1]
770ba26da8eSWarner Losh	<reboot>
771ba26da8eSWarner Losh
772fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
773fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
774fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
775fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
776fdb9f54dSWarner Losh	the UPDATING entries.
777ba26da8eSWarner Losh
7781dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
7791dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
7801dece4a9SWarner Losh	your sources that you have read and understood all the recent
7811dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
7821dece4a9SWarner Losh	much fewer pitfalls.
7831dece4a9SWarner Losh
784134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
785134d2e86SWarner Losh	should disable them at this point so they don't crash your
786134d2e86SWarner Losh	system on reboot.
787134d2e86SWarner Losh
7889c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
7899c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
7909c1a7444SWarner Losh	configuration.
7919c1a7444SWarner Losh
792ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
793ee6e1fc3SWarner Losh		fsck -p
794ee6e1fc3SWarner Losh		mount -u /
795ee6e1fc3SWarner Losh		mount -a
796ee6e1fc3SWarner Losh		cd /usr/src
797ee6e1fc3SWarner Losh		adjkerntz -i		# if COMS is wall time
798ee6e1fc3SWarner Losh
799a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
800a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
801a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
802a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
803a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
804a6cd4f9dSWarner Losh	for potential gotchas.
805a6cd4f9dSWarner Losh
806dc0dbf5cSWarner LoshFORMAT:
807dc0dbf5cSWarner Losh
808f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
8091fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
810f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
811f8ab1dd6SWarner Loshprevious releases if your system is older than this.
8121fc1a0dcSWarner Losh
8133645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
8143645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
815f8c77507SWarner Losh
816e72fd46aSWarner LoshCopyright information:
817e72fd46aSWarner Losh
818e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
819e72fd46aSWarner Losh
820772730c7SWarner LoshRedistribution, publication, translation and use, with or without
821772730c7SWarner Loshmodification, in full or in part, in any form or format of this
822772730c7SWarner Loshdocument are permitted.
823e72fd46aSWarner Losh
824e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
825e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
826e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
827e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
828e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
829e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
830e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
831e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
832e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
833e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
834e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
835e72fd46aSWarner Losh
836e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
837e72fd46aSWarner Loshauthor a beer.
838e72fd46aSWarner Losh
83922306abcSWarner LoshContact Warner Losh if you have any questions about your use of
840772730c7SWarner Loshthis document.
841772730c7SWarner Losh
84297d92980SPeter Wemm$FreeBSD$
843