xref: /freebsd/UPDATING (revision 1fe003b61fbadc5da105642687d7c01ca4f23d6d)
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
81fe003b6SWarner Losh20011030:
91fe003b6SWarner Losh	The asr driver now no longer panics the system on machines that
101fe003b6SWarner Losh	do not have the asr hardware.  It is unknown if asr works still
111fe003b6SWarner Losh	for the hardware it supports.
121fe003b6SWarner Losh
131fe003b6SWarner Losh20011027:
141fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
151fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
161fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
171fe003b6SWarner Losh	try to use from this date forward.
181fe003b6SWarner Losh
191fe003b6SWarner Losh20011025:
201fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
211fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
221fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
231fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
241fe003b6SWarner Losh	TARGET_ARCH=i386.
251fe003b6SWarner Losh
26d05f9643SWarner Losh20011001:
27d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
28d05f9643SWarner Losh	You must recompile both the kernel and userland applications
29d05f9643SWarner Losh	at the same time.
30d05f9643SWarner Losh
3158970f85SWarner Losh20010929:
3258970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
3358970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
3458970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
3558970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
3658970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
3758970f85SWarner Losh
3858970f85SWarner Losh20010927:
3958970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
4058970f85SWarner Losh	To disable ACPI you can add
41378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
4258970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
4358970f85SWarner Losh	loader "ok" prompt).
4458970f85SWarner Losh
4558970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
4658970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
4758970f85SWarner Losh	file and not list acpi in that list.
48378f4486SAlfred Perlstein
495119d237SWarner Losh20010924:
505119d237SWarner Losh	The buildworld has been fixed.  You may need to install
515119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
5258970f85SWarner Losh	to work.
5358970f85SWarner Losh		cd src/lib/compat/compat4x.i386
5458970f85SWarner Losh		make all install
555119d237SWarner Losh
563c293725SWarner Losh20010919:
573c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
583c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
593c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
60772730c7SWarner Losh	workaround is to add
613c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
623c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
633c293725SWarner Losh	can be removed afterwards.
643c293725SWarner Losh
653c293725SWarner Losh	A proper fix to the buildworld target is needed.
663c293725SWarner Losh
673c293725SWarner Losh20010918:
683c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
693c293725SWarner Losh	NFS may be unstable after this date.
703c293725SWarner Losh
713c293725SWarner Losh20010912:
723c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
733c293725SWarner Losh	the kernel.  While a few problems were introduced in the
743c293725SWarner Losh	initial commit, most of the major ones have been found and
753c293725SWarner Losh	corrected.
763c293725SWarner Losh
773c293725SWarner Losh20010901:
783c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
793c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
803c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
813c293725SWarner Losh	have been rectified around this date.
823c293725SWarner Losh
8398b17b95SWarner Losh20010823:
8498b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
8598b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
8698b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
8798b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
8898b17b95SWarner Losh 	sure that user or group bind has read (and not write)
8998b17b95SWarner Losh 	permission for your name server configuration and that it
9098b17b95SWarner Losh 	has read and write permission for your slave zone files and
9198b17b95SWarner Losh 	directory.
9298b17b95SWarner Losh
9398b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
9498b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
9598b17b95SWarner Losh
9698b17b95SWarner Losh 		named_flags=
9798b17b95SWarner Losh
987b9786edSMark Murray20010709:
997b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
1007b9786edSMark Murray	the ability of the shared library major number to handle.
1017b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
1027b9786edSMark Murray	solution is to rebuild those ports.
1037b9786edSMark Murray
1041d28950eSWarner Losh20010628:
1051d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
1061d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
1071d28950eSWarner Losh
108e72fd46aSWarner Losh20010625:
10998b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
11098b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
11198b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
11298b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
11398b17b95SWarner Losh	IRQ configuration needs more safety belts.
11416de1a07SWarner Losh
1150d415dffSWarner Losh20010617:
116e72fd46aSWarner Losh	Softupdates problems have been corrected.
1170d415dffSWarner Losh
1180d415dffSWarner Losh20010614:
1190d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
1200d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
1210d415dffSWarner Losh	kernel building methods.
1220d415dffSWarner Losh
1238b9959adSWarner Losh20010613:
1248b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
1258b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
126e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
127e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
1288b9959adSWarner Losh
129e72fd46aSWarner Losh20010613:
1308b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
131e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
132e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
1338b9959adSWarner Losh
1340d415dffSWarner Losh20010612:
1350d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
1360d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
1370d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
1380d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
1390d415dffSWarner Losh	until this bug is fixed.
1400d415dffSWarner Losh
141e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
142e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
143e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
144e72fd46aSWarner Losh
1450d415dffSWarner Losh20010610:
1460d415dffSWarner Losh	Locale names have changed to match other systems better.
1470d415dffSWarner Losh
1486ccdb5e4SWarner Losh20010604:
1496ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
1506ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
1516ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
1523590182eSWarner Losh	Interrupt storms look a lot like a hang.
1533590182eSWarner Losh
1543590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
1553590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
1563590182eSWarner Losh	it is).
1573590182eSWarner Losh
1583590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
1593590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
1603590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
1613590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
1626ccdb5e4SWarner Losh
1630bc62786SWarner Losh20010530:
1640bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
1650bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
1660bc62786SWarner Losh	a limited time.  If you see
1670bc62786SWarner Losh
1680bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
1690bc62786SWarner Losh
1700bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
1710bc62786SWarner Losh	COPY=-C.
1720bc62786SWarner Losh
17368a38c6cSWarner Losh20010525:
174b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
175c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
176c4f4a728SWarner Losh	definitely is in bad shape.
17768a38c6cSWarner Losh
178ed0f29caSWarner Losh20010521:
179f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
180ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
181ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
182ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
183ed0f29caSWarner Losh	is
184ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
185ed0f29caSWarner Losh
18680c16af9SWarner Losh20010520:
18768a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
18880c16af9SWarner Losh
18980c16af9SWarner Losh20010519:
19080c16af9SWarner Losh	pccard has had much reorganizational work done to it over
19180c16af9SWarner Losh	the past few days.  Everything should still work, but if
19280c16af9SWarner Losh	not, please contact imp@freebsd.org.
19380c16af9SWarner Losh
194a45f2d05SWarner Losh20010517:
195a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
196a45f2d05SWarner Losh	userland at the same time.
197a45f2d05SWarner Losh
198a45f2d05SWarner Losh20010517:
199a45f2d05SWarner Losh	New ncurses imported.
200a45f2d05SWarner Losh
2012988afcaSWarner Losh20010512:
2022988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
2032988afcaSWarner Losh	will be the only way to go starting July 1.
2042988afcaSWarner Losh
20509946a51SWarner Losh20010502:
20609946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
20709946a51SWarner Losh
20809946a51SWarner Losh20010501:
20909946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
21009946a51SWarner Losh
21109946a51SWarner Losh20010430:
212a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
21309946a51SWarner Losh	go back in the water.
21409946a51SWarner Losh
21509946a51SWarner Losh20010429:
21609946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
21709946a51SWarner Losh	this date, but before the correction date.
21809946a51SWarner Losh
21991dd3b53SWarner Losh20010423:
22091dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
22191dd3b53SWarner Losh
22291dd3b53SWarner Losh20010411:
22391dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
22491dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
22591dd3b53SWarner Losh	Update only if you understand that you must not use the old
22691dd3b53SWarner Losh	fsck with the new kernel ever.
22791dd3b53SWarner Losh
228933b3269SWarner Losh20010330:
229933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
230c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
231933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
232933b3269SWarner Losh
233933b3269SWarner Losh20010319:
234933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
235933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
236933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
237f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
23809946a51SWarner Losh
23909946a51SWarner Losh20010315:
24009946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
24109946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
24209946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
243933b3269SWarner Losh
244933b3269SWarner Losh20010312:
245933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
246933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
247933b3269SWarner Losh
248933b3269SWarner Losh20010312:
249933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
250933b3269SWarner Losh	instead of ad-hoc.
251933b3269SWarner Losh
252933b3269SWarner Losh20010310:
253f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
254933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
255933b3269SWarner Losh	ssh might not work if you don't.
256933b3269SWarner Losh
25762353691SWarner Losh20010303:
25862353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
25962353691SWarner Losh	which means that you must include the miibus in your kernel if
26062353691SWarner Losh	you use the ed driver.
26162353691SWarner Losh
262d325cf65SWarner Losh20010220:
263d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
264d325cf65SWarner Losh	safe to go back into the water.
265d325cf65SWarner Losh
266024daae6SWarner Losh20010211:
267024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
268024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
269024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
270024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
271024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
272024daae6SWarner Losh
273024daae6SWarner Losh	To get to the new system, you'll need to use the following
274024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
275024daae6SWarner Losh	don't have to move this to the updating section.
276024daae6SWarner Losh
277024daae6SWarner Losh	To get around the installworld problem, do:
278024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
279024daae6SWarner Losh		# make install
280024daae6SWarner Losh		# cd /usr/src
281024daae6SWarner Losh		# make installworld
282024daae6SWarner Losh	If that doesn't work, then try:
283024daae6SWarner Losh		# make -k installworld
284024daae6SWarner Losh		# make installworld
285024daae6SWarner Losh
286024daae6SWarner Losh20010207:
287024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
288024daae6SWarner Losh	do not include devfs in your kernel as problems result.
289024daae6SWarner Losh
290024daae6SWarner Losh20010205:
2917595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
292024daae6SWarner Losh	Remove them from your config.
293024daae6SWarner Losh
2941e159248SWarner Losh20010122:
2951e159248SWarner Losh	****************************** WARNING ******************************
2961e159248SWarner Losh			buildkernel has been changed slightly
2971e159248SWarner Losh	****************************** WARNING ******************************
2981e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
2991e159248SWarner Losh	should update your scripts and make.conf accordingly.
3001e159248SWarner Losh
3011e159248SWarner Losh20010119:
3021e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
3031e159248SWarner Losh	This requires a new config to build correctly.
3041e159248SWarner Losh
305aac7dfeaSWarner Losh20010116:
306aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
307aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
308aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
309aac7dfeaSWarner Losh
310aac7dfeaSWarner Losh20010110:
311aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
312aac7dfeaSWarner Losh
313aac7dfeaSWarner Losh20010102:
314aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
315aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
316aac7dfeaSWarner Losh
31763c90c9eSWarner Losh20010101:
31863c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
31963c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
3205fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
32163c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
32263c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
32363c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
32463c90c9eSWarner Losh	might have been ignored by the -k option.
32563c90c9eSWarner Losh
3265fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
3275fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
3285fd2a895SWarner Losh	of this working.
3295fd2a895SWarner Losh
330aac7dfeaSWarner Losh20001228:
331aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
332aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
333aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
334aac7dfeaSWarner Losh
335de2bcc63SWarner Losh20001218:
336de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
337de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
338de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
339de2bcc63SWarner Losh	cards will not be recognized without it.
340de2bcc63SWarner Losh
341960773f7SWarner Losh20001205:
342960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
343960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
344960773f7SWarner Losh	adding the following in pam.conf:
345960773f7SWarner Losh
346960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
347960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
348960773f7SWarner Losh	sshd    session required        pam_permit.so
349960773f7SWarner Losh
3500acc635eSWarner Losh20001031:
3510acc635eSWarner Losh	cvs updated to 1.11.
3520acc635eSWarner Losh
3530acc635eSWarner Losh20001020:
3540acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
3550acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
3560acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
3570acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
3580acc635eSWarner Losh	workaround.
3590acc635eSWarner Losh
3600acc635eSWarner Losh20001010:
3610acc635eSWarner Losh	****************************** WARNING ******************************
3620acc635eSWarner Losh				Sendmail has been updated.
3630acc635eSWarner Losh	****************************** WARNING ******************************
3640acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
3650acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
3660acc635eSWarner Losh	  is set.
3670acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
3680acc635eSWarner Losh	  commands.
3690acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
3700acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
3710acc635eSWarner Losh	  in /usr/share/sendmail/cf.
3720acc635eSWarner Losh	o sendmail.cw changed to local-host-names
3730acc635eSWarner Losh
3740acc635eSWarner Losh	More details can be found at
3750acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
3760acc635eSWarner Losh
3776e98a146SWarner Losh20001009:
3786e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
3796e98a146SWarner Losh	your entire ports tree, or you will have problems.
3806e98a146SWarner Losh
3816e98a146SWarner Losh20001006:
382685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
3836e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
3846e98a146SWarner Losh	/usr/bin/miniperl.
3856e98a146SWarner Losh
386073113a4SWarner Losh20001005:
387073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
388685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
389073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
390073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
391073113a4SWarner Losh	tree for anything to work.
392073113a4SWarner Losh
3930acc635eSWarner Losh20000928:
3940acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
3950acc635eSWarner Losh
396be3885b3SWarner Losh20000916:
397be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
398be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
399be3885b3SWarner Losh	same time as your kernel.
400be3885b3SWarner Losh
40176ec9675SWarner Losh20000914:
40276ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
40376ec9675SWarner Losh	include the device will cause suspended laptops losing time
40476ec9675SWarner Losh	when they resume.  Include
40576ec9675SWarner Losh		device		pmtimer
40676ec9675SWarner Losh	in your config file and
40701b9a434SWarner Losh		hint.pmtimer.0.at="isa"
40876ec9675SWarner Losh	to your /boot/device.hints file.
40976ec9675SWarner Losh
410f4865386SMark Murray20000911:
411f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
412f4865386SMark Murray	rather than an option. The supplied kernel config files have
413f4865386SMark Murray	been updated. You will need to do something similar in your
414f4865386SMark Murray	own kernel config file.
415f4865386SMark Murray	Remove:
416f4865386SMark Murray		options		RANDOMDEV
417f4865386SMark Murray	Add:
418f4865386SMark Murray		device		random
419f4865386SMark Murray	If you prefer to load the loadable module, you need to do
420f4865386SMark Murray	nothing.
421f4865386SMark Murray
422d594498fSWarner Losh20000909:
423d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
424d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
425d594498fSWarner Losh	reflect this if you load this module at boot time.
426d594498fSWarner Losh	The line should read:
427d594498fSWarner Losh		random_load="YES"
428d594498fSWarner Losh
4290deb7ddcSWarner Losh20000907:
4300deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
43116eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
43216eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
43316eb772dSWarner Losh	sure you don't have model loading problems which might at
43416eb772dSWarner Losh	first blush appear related to SMP.
43552bf24e7SWarner Losh
4365a01880bSWarner Losh20000906:
4375a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
4385a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
4395a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
4405a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
4415a01880bSWarner Losh	don't have one, and you have host.conf.
4425a01880bSWarner Losh
4432b41163cSWarner Losh20000905:
44438d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
44538d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
44638d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
44738d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
44838d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
44938d6ecd2SWarner Losh
45038d6ecd2SWarner Losh20000905:
4518aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
4528aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
4538aab4bc7SWarner Losh	is /boot/kernel.
4548aab4bc7SWarner Losh
4558aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
45638d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
45738d6ecd2SWarner Losh	installkernel/installworld dance.
4582b41163cSWarner Losh
459d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
460d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
461d594498fSWarner Losh	modules in that directory instead of finding them in the correct
462d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
463d594498fSWarner Losh	is that the linux module crashes your machine after the update.
464d594498fSWarner Losh
465d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
466d594498fSWarner Losh		mv /modules.old /boot/kernel.old
467d594498fSWarner Losh		chflags noschg /kernel.old
468d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
469d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
470d594498fSWarner Losh	fi
471d594498fSWarner Losh
472c22a309cSWarner Losh20000904:
473c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
474c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
475c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
476c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
477c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
478c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
479c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
480c22a309cSWarner Losh	is not likely to be generated.
481c22a309cSWarner Losh
482fdb9f54dSWarner Losh20000825:
483fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
4849c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
4859c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
4869c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
4879c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
4889c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
4899c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
4909c1a7444SWarner Losh	kernel.
4919c1a7444SWarner Losh
4929c1a7444SWarner Losh20000821:
4939c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
4949c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
4959c1a7444SWarner Losh	/boot/loader.conf.
496fdb9f54dSWarner Losh
4978f250aa7SWarner Losh20000812:
4985da0d091SWarner Losh	suidperl is now always built and installed on the system, but
4995da0d091SWarner Losh	with permissions of 511.  If you have applications that use
5005da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
5015da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
5025da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
5035da0d091SWarner Losh	will fix this until the next build.
5045da0d091SWarner Losh
5055da0d091SWarner Losh20000812:
5068f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
5078f250aa7SWarner Losh	visible changes that may immediately affect your configuration
5088f250aa7SWarner Losh	include:
5098f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
5108f250aa7SWarner Losh	- newaliases limited to root and trusted users
5118f250aa7SWarner Losh	- MSA port (587) turned on by default
5128f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
5138f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
5148f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
5158f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
5168f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
5178f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
5188f250aa7SWarner Losh
51971c38472SWarner Losh20000810:
52071c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
52171c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
52271c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
52371c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
52471c38472SWarner Losh	specific use for it.
52571c38472SWarner Losh
52671c38472SWarner Losh20000729:
52771c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
52871c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
52971c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
53071c38472SWarner Losh	afterwards (unless the variables already are set, of course):
53171c38472SWarner Losh		# Enable network daemons for user convenience.
53271c38472SWarner Losh		inetd_enable="YES"
53371c38472SWarner Losh		portmap_enable="YES"
53471c38472SWarner Losh		sendmail_enable="YES"
53571c38472SWarner Losh
53671c38472SWarner Losh20000728:
53771c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
53871c38472SWarner Losh	will need to change that to nullfs_load="YES".
53971c38472SWarner Losh
5401dece4a9SWarner Losh20000728:
5411dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
5421dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
5431dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
5441dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
5451dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
5461dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
5471dece4a9SWarner Losh	to /MYKERNEL.
5481dece4a9SWarner Losh
549409e887cSWarner Losh20000711:
550409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
551409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
552409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
553409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
554409e887cSWarner Losh	for details on potential problems that you might have and how
555409e887cSWarner Losh	to get around them.
556409e887cSWarner Losh
557409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
558409e887cSWarner Losh	clauses above, you needn't worry.
559409e887cSWarner Losh
560409e887cSWarner Losh20000711:
561409e887cSWarner Losh	/etc/security has been updated to print the inode number of
562409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
563409e887cSWarner Losh	in the number of changed programs the first time when you run
564409e887cSWarner Losh	mergemaster to get a new /etc/security.
565409e887cSWarner Losh
566673d13f2SWarner Losh20000710:
567673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
568673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
569673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
570673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
571673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
572673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
573673d13f2SWarner Losh	errors. (see below, 20000624).
574673d13f2SWarner Losh
575bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
5761dece4a9SWarner Losh
577673d13f2SWarner Losh20000709:
578c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
579c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
580c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
581673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
582673d13f2SWarner Losh
583e98e26cdSWarner Losh20000706:
584e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
585e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
586e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
587f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
588e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
5892c021c6cSMark Ovens	interim if needed.
590e98e26cdSWarner Losh
591e98e26cdSWarner Losh20000705:
592e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
593e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
594e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
595e98e26cdSWarner Losh	details.
596e98e26cdSWarner Losh
597c373950eSWarner Losh20000704:
5982f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
5992f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
6002f961bc8SWarner Losh
6012f961bc8SWarner Losh20000704:
602c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
603c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
604c373950eSWarner Losh	rc.d scripts that haven't been updated.
605c373950eSWarner Losh
60627dc3a2bSWarner Losh20000630:
60727dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
60827dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
60927dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
61027dc3a2bSWarner Losh
611b8c215acSWarner Losh20000625:
612b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
61327dc3a2bSWarner Losh	system installed in order to build the system and kernel.
61427dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
61527dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
61627dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
61727dc3a2bSWarner Losh	were required.  You should check with the latest collections
61827dc3a2bSWarner Losh	to make sure that these haven't changed.
619b8c215acSWarner Losh
6207b990719SWarner Losh20000624:
6217b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
6227b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
6237b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
6247b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
6257b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
6267b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
6277b990719SWarner Losh	date to the completion of the work.
6287b990719SWarner Losh
62927dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
63027dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
63127dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
63227dc3a2bSWarner Losh	recreate the random and urandom devices.
63327dc3a2bSWarner Losh
63481e54c50SWarner Losh20000622:
63581e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
63681e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
63781e54c50SWarner Losh	that used to be required when updating.
63881e54c50SWarner Losh
63939943833SWarner Losh20000621:
6402c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
6412a2f33fbSDaniel Baker	the config file update procedure.
6422a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
643c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
644a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
64539943833SWarner Losh
646290f9ad8SWarner Losh20000620:
647290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
648290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
649290f9ad8SWarner Losh	that workaround will no longer be required.
650290f9ad8SWarner Losh
65190fb6346SWarner Losh20000615:
65290fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
65390fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
65490fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
65590fb6346SWarner Losh	devices.
65690fb6346SWarner Losh
657f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
658f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
659f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
660f75f65bbSWarner Losh	may work).
661f75f65bbSWarner Losh
662ba26da8eSWarner Losh20000612:
663ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
664290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
665c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
666290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
667f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
668f54a3542SWarner Losh	NEWCARD for examples of the new format.
669290f9ad8SWarner Losh
670d65850ebSWarner Losh20000522:
671ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
672d65850ebSWarner Losh	building a kernel after this point is advised that they need
673d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
674d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
675d65850ebSWarner Losh
676d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
677d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
678d9583a00SWarner Losh	is recommended that you don't set this option until the problem
679d9583a00SWarner Losh	is resolved.
680d9583a00SWarner Losh
6818039cedeSWarner Losh20000513:
6828039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
6838039cedeSWarner Losh
684d65850ebSWarner Losh20000510:
6858039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
6868039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
6878039cedeSWarner Losh	is requires for the boot blocks to build properly.
6888039cedeSWarner Losh
6898039cedeSWarner Losh20000503:
6908039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
6918039cedeSWarner Losh	is now available.
6928039cedeSWarner Losh
693d65850ebSWarner Losh20000502:
694d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
695d65850ebSWarner Losh	connected to the kernel building instead.
696d65850ebSWarner Losh
697be149406SNik Clayton20000427:
6988039cedeSWarner Losh	You may need to build gperf
6998039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
7008039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
7018039cedeSWarner Losh	an option only in -current.
7028039cedeSWarner Losh
7032b8dd5f4SWarner Losh20000417:
7042b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
705f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
7062b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
7072b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
7082c021c6cSMark Ovens	before you reboot, you'll need to issue:
7092b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
7102b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
7112b8dd5f4SWarner Losh
7128d9f1945SWarner Losh20000320:
7132b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
7142b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
7152b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
7168d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
7172b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
7188d9f1945SWarner Losh
719f8ab1dd6SWarner Losh20000319:
720f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
721f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
722f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
723f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
724f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
725f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
726f8ab1dd6SWarner Losh
72719cada77SWarner Losh20000318:
728f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
72919cada77SWarner Losh	Large kernel changes are being committed and are in the
73019cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
73119cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
73219cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
73319cada77SWarner Losh	that you are loading are up to date.
734ba228352SWarner Losh
73519cada77SWarner Losh20000315:
7366d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
7376d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
7386d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
7396d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
7406d23c382SWarner Losh	boot.
7416d23c382SWarner Losh
7426d23c382SWarner Losh20000315:
74319cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
74419cada77SWarner Losh	to upgrade to 4.0 from 3.x.
74557199806SWarner Losh
746dc0dbf5cSWarner LoshCOMMON ITEMS:
747dc0dbf5cSWarner Losh
748a24eff53SWarner Losh	General Notes
749a24eff53SWarner Losh	-------------
750a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
751a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
752a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
753a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
754a24eff53SWarner Losh	or several minor releases, or when several months have passed
755a24eff53SWarner Losh	on the -current branch).
756a24eff53SWarner Losh
757dc0dbf5cSWarner Losh	To build a kernel
758dc0dbf5cSWarner Losh	-----------------
759ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
760f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
761ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
7621e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
7631e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
764dc0dbf5cSWarner Losh
765ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
766ba01eb20SWarner Losh	--------------------------------------------------------------
767ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
768ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
769ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
770ba01eb20SWarner Losh	make depend
771ba01eb20SWarner Losh	make
772ba01eb20SWarner Losh	make install
773ba01eb20SWarner Losh
774ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
775ba01eb20SWarner Losh
776ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
777ba01eb20SWarner Losh
778ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
779ba01eb20SWarner Losh	-----------------------------------------------------------
780759f0aefSWarner Losh	make world
781fdb9f54dSWarner Losh	Build a new kernel, see above.
782759f0aefSWarner Losh
7831dece4a9SWarner Losh	To upgrade from 4.x-stable to current
784ba26da8eSWarner Losh	-------------------------------------
785ba26da8eSWarner Losh	make buildworld
7861e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
7877595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
7881e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
789ee6e1fc3SWarner Losh	reboot in single user [3]
790ba26da8eSWarner Losh	make installworld
791a6cd4f9dSWarner Losh	mergemaster		[4]
792134d2e86SWarner Losh	[1]
793ba26da8eSWarner Losh	<reboot>
794ba26da8eSWarner Losh
795fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
796fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
797fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
798fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
799fdb9f54dSWarner Losh	the UPDATING entries.
800ba26da8eSWarner Losh
8011dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
8021dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
8031dece4a9SWarner Losh	your sources that you have read and understood all the recent
8041dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
8051dece4a9SWarner Losh	much fewer pitfalls.
8061dece4a9SWarner Losh
807134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
808134d2e86SWarner Losh	should disable them at this point so they don't crash your
809134d2e86SWarner Losh	system on reboot.
810134d2e86SWarner Losh
8119c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
8129c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
8139c1a7444SWarner Losh	configuration.
8149c1a7444SWarner Losh
815ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
816ee6e1fc3SWarner Losh		fsck -p
817ee6e1fc3SWarner Losh		mount -u /
818ee6e1fc3SWarner Losh		mount -a
819ee6e1fc3SWarner Losh		cd /usr/src
820ee6e1fc3SWarner Losh		adjkerntz -i		# if COMS is wall time
821ee6e1fc3SWarner Losh
822a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
823a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
824a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
825a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
826a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
827a6cd4f9dSWarner Losh	for potential gotchas.
828a6cd4f9dSWarner Losh
829dc0dbf5cSWarner LoshFORMAT:
830dc0dbf5cSWarner Losh
831f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
8321fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
833f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
834f8ab1dd6SWarner Loshprevious releases if your system is older than this.
8351fc1a0dcSWarner Losh
8363645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
8373645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
838f8c77507SWarner Losh
839e72fd46aSWarner LoshCopyright information:
840e72fd46aSWarner Losh
841e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
842e72fd46aSWarner Losh
843772730c7SWarner LoshRedistribution, publication, translation and use, with or without
844772730c7SWarner Loshmodification, in full or in part, in any form or format of this
845772730c7SWarner Loshdocument are permitted.
846e72fd46aSWarner Losh
847e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
848e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
849e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
850e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
851e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
852e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
853e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
854e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
855e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
856e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
857e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
858e72fd46aSWarner Losh
859e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
860e72fd46aSWarner Loshauthor a beer.
861e72fd46aSWarner Losh
86222306abcSWarner LoshContact Warner Losh if you have any questions about your use of
863772730c7SWarner Loshthis document.
864772730c7SWarner Losh
86597d92980SPeter Wemm$FreeBSD$
866