UPDATING revision 77381
1Updating Information for FreeBSD current users
2
3This file is maintained by imp@village.org.  Please send new entries
4directly to him.  See end of file for further details.  For commonly
5done items, please see the end of the file.  Search for 'COMMON
6ITEMS:'
7
820010525:
9	It appears that vm is now stable enough to use again.
10
1120010521:
12	Minor repo damanged has happened.  This may cause problems
13	with cvsup of ports.  If you get errors, please see
14	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
15	at the bottom for details on a workaround.  The error message
16	is
17Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
18
1920010520:
20	Vm and/or swapping are busted on -current.  Please be patient.
21
2220010519:
23	pccard has had much reorganizational work done to it over
24	the past few days.  Everything should still work, but if
25	not, please contact imp@freebsd.org.
26
2720010517:
28	ata ioctl changed.  Make sure to recompile both kernel and
29	userland at the same time.
30
3120010517:
32	New ncurses imported.
33
3420010512:
35	DEVFS is now opt out, not opt in.  Barring major problems, this
36	will be the only way to go starting July 1.
37
3820010502:
39	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
40
4120010501:
42	Building perl was broken at 02:25:25 PDT.
43
4420010430:
45	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
46	go back in the water.
47
4820010429:
49	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
50	this date, but before the correction date.
51
5220010423:
53	old fsck and new kernel interactions appear to have been fixed.
54
5520010411:
56	fsck and the kernel were changed to handle some optimizations
57	to directory layout.  This breaks backward compatibility.
58	Update only if you understand that you must not use the old
59	fsck with the new kernel ever.
60
6120010330:
62	fsck has changed the meaning of the pass column in /etc/fstab.
63	Please see the cvs commit to fsck.8 or the fsck.8 man page fora
64	details.  It is unclear if changes to /etc/fstab are necessary.
65
6620010319:
67	portmap had changed name to rpcbind for maximum POLA in your
68	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
69	other rpc based programs that rely on portmapper will not work
70	without updates to /etc/hosts.{allow,deny} and /etc/netcofnig.
71
7220010315:
73	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
74	and ATA_ENABEL_TAGS are no longer kernel options.  They have
75	been replaced by tunables.  See ata.4 for details.
76
7720010312:
78	The fxp driver was converted to use miibus.  If you compile
79	fxp into your kernel statically, you will need to add miibus.
80
8120010312:
82	The wi device now defaults to BSS (infrastructure) mode
83	instead of ad-hoc.
84
8520010310:
86	/dev/urandmon should be a sumbolic link to /dev/random now.
87	Users of current not using DEVFS need to run MAKEDEV std.
88	ssh might not work if you don't.
89
9020010220:
91	The problems with libc have been corrected.  It is now mostly
92	safe to go back into the water.
93
9420010211:
95	The size of FILE was changed.  This breaks upgrading.  If
96	you must upgrade, be prepared for pain.  It also breaks almost
97	all binaries that you've compiled on -current.  You are warned
98	that before upgrading would be a good time to do a level 0
99	dump of your system.  No, really, I mean it this time.
100
101	To get to the new system, you'll need to use the following
102	workaround.  Hopefully this can be sorted out so that we
103	don't have to move this to the updating section.
104
105	To get around the installworld problem, do:
106		# cd /usr/src/usr.bin/sed
107		# make install
108		# cd /usr/src
109		# make installworld
110	If that doesn't work, then try:
111		# make -k installworld
112		# make installworld
113
11420010207:
115	DEVFS is now the default.  If you use vinum, make sure that you
116	do not include devfs in your kernel as problems result.
117
11820010205:
119	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
120	Remove them from your config.
121
12220010122:
123	****************************** WARNING ******************************
124			buildkernel has been changed slightly
125	****************************** WARNING ******************************
126	KERNCONF replaces the variable KERNEL for buildkernel.  You
127	should update your scripts and make.conf accordingly.
128
12920010119:
130	config has changed to allow DEV_FOO as a replacement for NFOO.
131	This requires a new config to build correctly.
132
13320010116:
134	The kerrnel option I386_CPU is now mutually exclusive with the
135	other cpu types. If you have an i386 system, be sure that it
136	only had this line.  Remove it for all other configurations.
137
13820010110:
139	Changes to the kernel require it and burncd be in sync.
140
14120010102:
142	Everyone who has hw.sndunit set to something in
143	/etc/sysctl.conf, it is now hw.snd.unit.
144
14520010101:
146	ex and vi were broken by some changes to sys/queue.h.  If you
147	have a bad vi, you will see make buildworld fail with a core
148	dump while building termcap.  You can work around this problem
149	by adding -k to your make buildworld.  This will cause the
150	build to complete and install a new vi.  Once that's done, you
151	can rebuild again without the -k to pick up anything that
152	might have been ignored by the -k option.
153
154	Others have suggested that you can just rebuild libc if your
155	vi/ex is dynamically linked, but I've not received any reports
156	of this working.
157
15820001228:
159	There have been some changes to libcrypt in -current.  The
160	libscrypt/libdescrypt symlink sillyness is gone and the installed
161	libcrypt is fully functional.  Be aware of this.
162
16320001218:
164	Linksys Fast Ethernet PCCARD cards supported by the ed driver
165	now require the addition of flag 0x80000 to their config line
166	in pccard.conf(5).  This flag is not optional.  These Linksys
167	cards will not be recognized without it.
168
16920001205:
170	Important new FreeBSD-version stuff: PAM support has been worked
171	in, partially from the "Unix" OpenSSH version.  This requires
172	adding the following in pam.conf:
173  
174	sshd    auth    sufficient      pam_skey.so
175	sshd    auth    required        pam_unix.so         try_first_pass
176	sshd    session required        pam_permit.so
177
17820001031:
179	cvs updated to 1.11.
180
18120001020:
182	The random device needs more entropy, so you need to make sure
183	that you've run mergemaster to get a /etc/rc which will seed
184	/dev/random.  If you don't and the system hangs after ldconfig,
185	then banging on the keyboard randomly until it unhangs is one
186	workaround.
187
18820001010:
189	****************************** WARNING ******************************
190				Sendmail has been updated.
191	****************************** WARNING ******************************
192	o mail.local(8) is no longer installed as a set-user-id binary.
193	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
194	  is set.
195	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
196	  commands.
197	o Now using sendmail's version of vacation(1).
198	o The sendmail cf building tools (contrib/sendmail/cf) are installed
199	  in /usr/share/sendmail/cf.
200	o sendmail.cw changed to local-host-names
201
202	More details can be found at
203		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
204
20520001009:
206	The ports tree's new layout is in place.  Be sure to update
207	your entire ports tree, or you will have problems.
208
20920001006:
210	The perl build procedure no longer installs miniperl, nor uses
211	the installed miniperl.  It is recommended that you delete
212	/usr/bin/miniperl.
213
21420001005:
215	This weekend the ports tree will be updated to a new layout.
216	It will be in an inconsistent state until noted in the UPDATING
217	file, or with asami-san's message to the relevant mailing
218	lists.  With this new layout, you'll need to update the whole
219	tree for anything to work.
220
22120000928:
222	There was a change in the passwd format.  Need more information.
223
22420000916:
225	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
226	place.  Please update boot loader (not the boot blocks) at the
227	same time as your kernel.
228
22920000914:
230	The new pmtimer device is necessary for laptops.  Failure to
231	include the device will cause suspended laptops losing time
232	when they resume.  Include
233		device		pmtimer
234	in your config file and
235		hint.pmtimer.0.at="isa"
236	to your /boot/device.hints file.
237
23820000911:
239	The random device has been turned into a (pseudo-)device,
240	rather than an option. The supplied kernel config files have
241	been updated. You will need to do something similar in your
242	own kernel config file.
243	Remove:
244		options		RANDOMDEV
245	Add:
246		device		random
247	If you prefer to load the loadable module, you need to do
248	nothing.
249
25020000909:
251	The random device module has been renamed from randomdev.ko to
252	random.ko. You will need to edit your /boot/loader.conf to
253	reflect this if you load this module at boot time.
254	The line should read:
255		random_load="YES"
256
25720000907:
258	The SMPNG commit has happened.  It should work, but if it
259	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
260	to be a variety of minor issues.  Please see 20000905 to make
261	sure you don't have model loading problems which might at
262	first blush appear related to SMP.
263
26420000906:
265	nsswitch has been imported from NetBSD.  Among other things,
266	this means that /etc/host.conf is no longer used.  See
267	nsswitch.conf(5) instead.  Note that at boot time rc.network
268	will attempt to produce a new nsswitch.conf file for you if you
269	don't have one, and you have host.conf.
270
27120000905:
272	The ucred structure changed size.  This breaks the interface
273	that mountd uses.  Trying to use an older mountd with a newer
274	kernel guarantees a panic.  This means that you need to use
275	kernels newer than today only with matching mountd, but you
276	needed to do that anyway with the boot loader changes.
277
27820000905:
279	The boot loader has been updated.  The new default kernel is
280	now /boot/kernel/kernel.ko.  The new default module location
281	is /boot/kernel.
282
283	You *MUST* upgrade your boot loader and kernel at the same time.
284	The easiest way to do this is to do the buildworld/buildkernel/
285	installkernel/installworld dance.
286
287	Furthermore, you are urged to delete your old /modules directory
288	before booting the new kernel, since kldload will find stale
289	modules in that directory instead of finding them in the correct
290	path, /boot/kernel.  The most common complaint that this cures
291	is that the linux module crashes your machine after the update.
292
293	if [ ! -d /boot/kernel.old ]; then
294		mv /modules.old /boot/kernel.old
295		chflags noschg /kernel.old
296		mv /kernel.old /boot/kernel.old/kernel.ko
297		chflags schg /boot/kernel.old/kernel.ko
298	fi
299
30020000904:
301	A new issue with the sendmail upgrade has come to light.
302	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will 
303	incorrectly install the default aliases in /etc/mail rather than
304	move the old one from /etc.  So you'll need to manually move the
305	file, create a symbolic link, remove the old /etc/aliases.db and
306	run newaliases.  For safety sake, you should stop sendmail
307	while doing this and run the upgrade when locally sourced email
308	is not likely to be generated.
309
31020000825:
311	/boot/device.hints is now required for installkernel to
312	succeed.  You should copy GENERIC.hints for your architecture
313	into /boot/device.hints.  If and only if you compile hints
314	into your kernel, then this file may be empty.  Please note,
315	if you have an empty or missing /boot/device.hints file and
316	you neglected to compile hints into your kernel, no boot
317	messages will appear after the boot loader tries to start the
318	kernel.
319
32020000821:
321	If you do NOT have ``options RANDOMDEV'' in your kernel and
322	you DO want the random device then add randomdev_load="YES" to
323	/boot/loader.conf.
324
32520000812:
326	suidperl is now always built and installed on the system, but
327	with permissions of 511.  If you have applications that use
328	this program, you are now required to add ENABLE_SUIDPERL=true
329	to /etc/make.conf.  If you forget to do this,
330		chmod 4511 /usr/bin/suidperl
331	will fix this until the next build.
332
33320000812:
334	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
335	visible changes that may immediately affect your configuration
336	include:
337	- New default file locations from src/contrib/sendmail/cf/README
338	- newaliases limited to root and trusted users
339	- MSA port (587) turned on by default
340	- New queue file naming system so can't go from 8.11 -> 8.9
341	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
342	- FEATURE(`nullclient') is more full featured
343	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
344	- mail.local FreeBSD-only -b option changed to -B
345	- See src/contrib/sendmail/RELEASE_NOTES for more info
346
34720000810:
348	suidperl (aka sperl) is no longer build by default.  You must
349	specifically define BUILD_SUIDPERL to "true" for it to be build.
350	Furthermore, we recommend that you remove /usr/bin/sperl* and
351	/usr/bin/suidperl files from your system unless you have a
352	specific use for it.
353
35420000729:
355	Networking defaults have been tightened.  Anybody upgrading
356	/etc/defaults/rc.conf needs to add the following lines to
357	/etc/rc.conf if they want to have the same setup
358	afterwards (unless the variables already are set, of course):
359		# Enable network daemons for user convenience.
360		inetd_enable="YES"
361		portmap_enable="YES"
362		sendmail_enable="YES"
363
36420000728:
365	If you have null_load="YES" in your /boot/loader.conf, you
366	will need to change that to nullfs_load="YES".
367
36820000728:
369	The "installkernel" target has changed slightly. Now even if
370	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
371	it will install the MYKERNEL file (built with the buildkernel
372	target) as /kernel rather than /MYKERNEL. Those who have
373	updated their /boot/loader.conf files to point to /MYKERNEL
374	should remove that entry or perform manual rename of /kernel
375	to /MYKERNEL.
376
37720000711:
378	If you use CVSUP or CTM to get CVS trees, AND you used to get 
379	the old crypto files from internat.freebsd.org AND you check
380	out files from the CVS tree with the cvs command, please read
381		http://people.freebsd.org/~imp/internat.txt
382	for details on potential problems that you might have and how
383	to get around them.
384
385	If you are merely a mirror, or don't answer yes to each of the
386	clauses above, you needn't worry.
387
38820000711:
389	/etc/security has been updated to print the inode number of
390	setuid programs that have changed.  You will see a large spike
391	in the number of changed programs the first time when you run
392	mergemaster to get a new /etc/security.
393
39420000710:
395	/dev/random now has good entropy collection (from the keyboard
396	and sysmouse drivers). Please ensure that either `options
397	RANDOMDEV' is present in your kernel config file or that
398	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
399	not have the /dev/random driver, OpenSSL (and consequently
400	lots of crypto tools (like SSH)) will fail with strange
401	errors. (see below, 20000624).
402
403	FreeBSD-current is safe again to run Crypto.
404
40520000709:
406	phk made the malloc default options AJ.  This may slow things
407	down and uncover other latent bugs in the code.  If you need to
408	run at full speed, you can disable this by doing the following:
409		ln -s aj /etc/malloc.conf
410
41120000706:
412	libftpio's version was accidentally bumped a few days ago.  This
413	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
414	before doing your next buildworld/installworld pair.  It certainly
415	won't hurt to remove it before the update procedure.  It will
416	break fetch until a new one is built, but ftp can be used in the
417	interim if needed.
418
41920000705:
420	The crypto packages have changed for the cvsup.  This has been done
421	in a backward compatible way, but the old packages will go away at
422	some point in the future.  Look at /usr/share/examples/cvsup for
423	details.
424
42520000704:
426	With the new sys/modules/sound/drivers/*, you will need to
427	set SYSDIR until you do an installworld after July 7th.
428
42920000704:
430	rc.shutdown and rc will now call the rc.d scripts with start
431	or stop.  This may cause some harmless warnings from older
432	rc.d scripts that haven't been updated.
433
43420000630:
435	The libfetch based version of fetch has gone into the tree.
436	Minor problems may result on some of the less popular sites,
437	which should be reported to des@freebsd.org.
438
43920000625:
440	From approximately this date forward, one must have the crypto
441	system installed in order to build the system and kernel.
442	While not technically strictly true, one should treat it as
443	required and grab the crypto bits.  If you are grabbing CVS
444	trees, src-all and cvs-crypto should be treated as if they
445	were required.  You should check with the latest collections
446	to make sure that these haven't changed.
447
44820000624:
449	Mark Murray just committed the first parts of a cleanup of
450	/dev/zero, et al.  This is also cleaning up /dev/random.
451	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
452	-CURRENT FROM THIS POINT FORWARD for cryptographic services
453	until Mark can merge in the fixes to this work in progress.
454	openssh and openssl should not be used to generate keys from this
455	date to the completion of the work.
456
457	If you must operate at this reduced level of security, add '
458	options RANDOMDEV' to your kernel or modload the randomdev
459	module.  You may also need to copy a new MAKEDEV to /dev and
460	recreate the random and urandom devices.
461
46220000622:
463	The license on the softupdates is now a standard 2 clause
464	BSD license.  You may need to remove your symbolic links
465	that used to be required when updating.
466
46720000621:
468	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
469	the config file update procedure.
470		http://people.freebsd.org/~imp/config-upd.html
471	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
472	isn't buildable.  However, you can generate a LINT file.
473
47420000620:
475	Binutils 2.10 have hit the tree, or will shortly.  As soon
476	as they do, the problem noted in 20000522 will be resolved and
477	that workaround will no longer be required.
478
47920000615:
480	phk removed the compatibility creation of wd devices in the
481	ad driver.  If you haven't done so already, you must update
482	your fstab, etc to use the ad devices instead of the wd
483	devices.
484
485	In addition, you'll need to update your boot blocks to a
486	more modern version, if you haven't already done so.  Modern
487	here means 4.0 release or newer (although older releases
488	may work).
489
49020000612:
491	Peter took an axe to config(8).  Be sure that you read his mail
492	on the topic before even thinking about updating.  You will
493	need to create a /boot/device.hints or add a hints directive
494	to your config file to compile them in statically.  The format
495	of the config file has changed as well.  Please see GENERIC or
496	NEWCARD for examples of the new format.
497
49820000522:
499	A new set of binutils went into the tree today.  Anybody
500	building a kernel after this point is advised that they need
501	to rebuild their binutils (or better yet do a
502	buildworld/installworld) before building a new kernel.
503
504	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
505	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
506	is recommended that you don't set this option until the problem
507	is resolved.
508
50920000513:
510	The ethernet drivers were all updated to clean up the BPF handling.
511
51220000510:
513	The problems with boot blocks on the alphas have been corrected.
514	This will require some care in updating alphas.  A new libstand
515	is requires for the boot blocks to build properly.
516
51720000503:
518	Recompile all kld modules.  Proper version dependency info
519	is now available.
520
52120000502:
522	Modules have been disconnected from the buildworld tree and 
523	connected to the kernel building instead.
524
52520000427:
526	You may need to build gperf
527		cd /usr/src/gnu/usr.bin/gperf && make depend all install
528	when upgrading from 4.0 -> current.  The build system now uses
529	an option only in -current.
530
53120000417:
532	The method that we brand ELF binaries has changed to be more
533	acceptable to the binutils maintainers.  You will need to
534	rebrand your ELF binaries that aren't native.  One problem
535	binary is the Linux ldconfig.  After your make world, but
536	before you reboot, you'll need to issue:
537		brandelf -t Linux /compat/linux/sbin/ldconfig
538	if you have Linux compatibility enabled on your machine.
539
54020000320:
541	If you have really bad/marginal IDE drives, you may find they
542	don't work well.  Use pio mode instead.  The easiest way to
543	cope if you have a problem combination is to add:
544		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
545	to the start of /etc/rc.conf.
546
54720000319:
548	The ISA and PCI compatibility shims have been connected to the
549	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
550	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
551	include the appropriate option in your kernel config.  Drivers
552	using the shims should be updated or they won't ship with
553	5.0-RELEASE, targeted for 2001.
554
55520000318:
556	We've entered the traditional post release dumping party.
557	Large kernel changes are being committed and are in the
558	works.  It is important to keep the systems' klds and kernel
559	in sync as kernel interfaces and structures are changing.
560	Before reporting kernel panics, make sure that all modules
561	that you are loading are up to date.
562
56320000315:
564	If you are upgrading from an older version of FreeBSD, you
565	need to update your boot blocks as well.  'disklabel -B ad0'
566	will do the trick.  This isn't critical until you remove your
567	wd device entries in /dev, at which point your system will not
568	boot.
569
57020000315:
571	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
572	to upgrade to 4.0 from 3.x.
573
574COMMON ITEMS:
575
576	General Notes
577	-------------
578	Avoid using make -j when upgrading.  From time to time in the
579	past there have been problems using -j with buildworld and/or
580	installworld.  This is especially true when upgrading between
581	"distant" versions (eg one that cross a major release boundary
582	or several minor releases, or when several months have passed
583	on the -current branch).
584
585	To build a kernel
586	-----------------
587	If you are updating from a prior version of FreeBSD (even one just
588	a few days old), you should follow this procedure. With a
589	/usr/obj tree with a fresh buildworld,
590	make buildkernel KERNCONF=YOUR_KERNEL_HERE
591	make installkernel KERNCONF=YOUR_KERNEL_HERE
592
593	To just build a kernel when you know that it won't mess you up
594	--------------------------------------------------------------
595	cd src/sys/{i386,alpha}/conf
596	config KERNEL_NAME_HERE			[1]
597	cd ../../compile/KERNEL_NAME_HERE
598	make depend
599	make
600	make install	
601	
602	[1] If in doubt, -r might help here.
603
604	If this fails, go to the "To build a kernel" section.
605
606	To rebuild everything and install it on the current system.
607	-----------------------------------------------------------
608	make world
609	Build a new kernel, see above.
610
611	To upgrade from 4.x-stable to current
612	-------------------------------------
613	make buildworld
614	make buildkernel KERNCONF=YOUR_KERNEL_HERE
615	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
616	make installkernel KERNCONF=YOUR_KERNEL_HERE
617	make installworld
618	mergemaster
619	[1]
620	<reboot>
621
622	Make sure that you've read the UPDATING file to understand the
623	tweaks to various things you need.  At this point in the life
624	cycle of current, things change often and you are on your own
625	to cope.  The defaults can also change, so please read ALL of
626	the UPDATING entries.
627
628	Also, if you are tracking -current, you must be subscribed to
629	freebsd-current@freebsd.org.  Make sure that before you update
630	your sources that you have read and understood all the recent
631	messages there.  If in doubt, please track -stable which has
632	much fewer pitfalls.
633
634	[1] If you have third party modules, such as vmware, you
635	should disable them at this point so they don't crash your
636	system on reboot.
637
638	[2] If you have legacy ISA devices, you may need to create
639	your own device.hints to reflect your unique hardware
640	configuration.
641
642FORMAT:
643
644This file contains a list, in reverse chronological order, of major
645breakages in tracking -current.  Not all things will be listed here,
646and it only starts on March 15, 2000.  Updating files can found in
647previous releases if your system is older than this.
648
649Please filter your entries through Warner Losh (imp@village.org) so
650that the style, formatting, etc of this file can be maintained.
651
652$FreeBSD: head/UPDATING 77381 2001-05-29 04:26:44Z imp $
653