UPDATING revision 65908
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
820000914:
9	The new pmtimer device is necessary for laptops.  Failure to
10	include the device will cause suspended laptops losing time
11	when they resume.  Include
12		device		pmtimer
13	in your config file and
14		hints.pmtimer.0.at="isa"
15	to your /boot/device.hints file.
16
1720000911:
18	The random device has been turned into a (pseudo-)device,
19	rather than an option. The supplied kernel config files have
20	been updated. You will need to do something similar in your
21	own kernel config file.
22	Remove:
23		options		RANDOMDEV
24	Add:
25		device		random
26	If you prefer to load the loadable module, you need to do
27	nothing.
28
2920000909:
30	The random device module has been renamed from randomdev.ko to
31	random.ko. You will need to edit your /boot/loader.conf to
32	reflect this if you load this module at boot time.
33	The line should read:
34		random_load="YES"
35
3620000907:
37	The SMPNG commit has happened.  It should work, but if it
38	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
39	to be a variety of minor issues.  Please see 20000905 to make
40	sure you don't have model loading problems which might at
41	first blush appear related to SMP.
42
4320000906:
44	nsswitch has been imported from NetBSD.  Among other things,
45	this means that /etc/host.conf is no longer used.  See
46	nsswitch.conf(5) instead.  Note that at boot time rc.network
47	will attempt to produce a new nsswitch.conf file for you if you
48	don't have one, and you have host.conf.
49
5020000905:
51	The ucred structure changed size.  This breaks the interface
52	that mountd uses.  Trying to use an older mountd with a newer
53	kernel guarantees a panic.  This means that you need to use
54	kernels newer than today only with matching mountd, but you
55	needed to do that anyway with the boot loader changes.
56
5720000905:
58	The boot loader has been updated.  The new default kernel is
59	now /boot/kernel/kernel.ko.  The new default module location
60	is /boot/kernel.
61
62	You *MUST* upgrade your boot loader and kernel at the same time.
63	The easiest way to do this is to do the buildworld/buildkernel/
64	installkernel/installworld dance.
65
66	Furthermore, you are urged to delete your old /modules directory
67	before booting the new kernel, since kldload will find stale
68	modules in that directory instead of finding them in the correct
69	path, /boot/kernel.  The most common complaint that this cures
70	is that the linux module crashes your machine after the update.
71
72	if [ ! -d /boot/kernel.old ]; then
73		mv /modules.old /boot/kernel.old
74		chflags noschg /kernel.old
75		mv /kernel.old /boot/kernel.old/kernel.ko
76		chflags schg /boot/kernel.old/kernel.ko
77	fi
78
7920000904:
80	A new issue with the sendmail upgrade has come to light.
81	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will 
82	incorrectly install the default aliases in /etc/mail rather than
83	move the old one from /etc.  So you'll need to manually move the
84	file, create a symbolic link, remove the old /etc/aliases.db and
85	run newaliases.  For safety sake, you should stop sendmail
86	while doing this and run the upgrade when locally sourced email
87	is not likely to be generated.
88
8920000825:
90	/boot/device.hints is now required for installkernel to
91	succeed.  You should copy GENERIC.hints for your architecture
92	into /boot/device.hints.  If and only if you compile hints
93	into your kernel, then this file may be empty.  Please note,
94	if you have an empty or missing /boot/device.hints file and
95	you neglected to compile hints into your kernel, no boot
96	messages will appear after the boot loader tries to start the
97	kernel.
98
9920000821:
100	If you do NOT have ``options RANDOMDEV'' in your kernel and
101	you DO want the random device then add randomdev_load="YES" to
102	/boot/loader.conf.
103
10420000812:
105	suidperl is now always built and installed on the system, but
106	with permissions of 511.  If you have applications that use
107	this program, you are now required to add ENABLE_SUIDPERL=true
108	to /etc/make.conf.  If you forget to do this,
109		chmod 4511 /usr/bin/suidperl
110	will fix this until the next build.
111
11220000812:
113	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
114	visible changes that may immediately affect your configuration
115	include:
116	- New default file locations from src/contrib/sendmail/cf/README
117	- newaliases limited to root and trusted users
118	- MSA port (587) turned on by default
119	- New queue file naming system so can't go from 8.11 -> 8.9
120	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
121	- FEATURE(`nullclient') is more full featured
122	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
123	- mail.local FreeBSD-only -b option changed to -B
124	- See src/contrib/sendmail/RELEASE_NOTES for more info
125
12620000810:
127	suidperl (aka sperl) is no longer build by default.  You must
128	specifically define BUILD_SUIDPERL to "true" for it to be build.
129	Furthermore, we recommend that you remove /usr/bin/sperl* and
130	/usr/bin/suidperl files from your system unless you have a
131	specific use for it.
132
13320000729:
134	Networking defaults have been tightened.  Anybody upgrading
135	/etc/defaults/rc.conf needs to add the following lines to
136	/etc/rc.conf if they want to have the same setup
137	afterwards (unless the variables already are set, of course):
138		# Enable network daemons for user convenience.
139		inetd_enable="YES"
140		portmap_enable="YES"
141		sendmail_enable="YES"
142
14320000728:
144	If you have null_load="YES" in your /boot/loader.conf, you
145	will need to change that to nullfs_load="YES".
146
14720000728:
148	The "installkernel" target has changed slightly. Now even if
149	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
150	it will install the MYKERNEL file (built with the buildkernel
151	target) as /kernel rather than /MYKERNEL. Those who have
152	updated their /boot/loader.conf files to point to /MYKERNEL
153	should remove that entry or perform manual rename of /kernel
154	to /MYKERNEL.
155
15620000711:
157	If you use CVSUP or CTM to get CVS trees, AND you used to get 
158	the old crypto files from internat.freebsd.org AND you check
159	out files from the CVS tree with the cvs command, please read
160		http://people.freebsd.org/~imp/internat.txt
161	for details on potential problems that you might have and how
162	to get around them.
163
164	If you are merely a mirror, or don't answer yes to each of the
165	clauses above, you needn't worry.
166
16720000711:
168	/etc/security has been updated to print the inode number of
169	setuid programs that have changed.  You will see a large spike
170	in the number of changed programs the first time when you run
171	mergemaster to get a new /etc/security.
172
17320000710:
174	/dev/random now has good entropy collection (from the keyboard
175	and sysmouse drivers). Please ensure that either `options
176	RANDOMDEV' is present in your kernel config file or that
177	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
178	not have the /dev/random driver, OpenSSL (and consequently
179	lots of crypto tools (like SSH)) will fail with strange
180	errors. (see below, 20000624).
181
182	FreeBSD-current is safe again to run Crypto.
183
18420000709:
185	phk made the malloc default options AJ.  This may slow things
186	down and uncover other latent bugs in the code.  If you need to
187	run at full speed, you can disable this by doing the following:
188		ln -s aj /etc/malloc.conf
189
19020000706:
191	libftpio's version was accidentally bumped a few days ago.  This
192	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
193	before doing your next buildworld/installworld pair.  It certainly
194	won't hurt to remove it before the update procedure.  It will
195	break fetch until a new one is built, but ftp can be used in the
196	interim if needed.
197
19820000705:
199	The crypto packages have changed for the cvsup.  This has been done
200	in a backward compatible way, but the old packages will go away at
201	some point in the future.  Look at /usr/share/examples/cvsup for
202	details.
203
20420000704:
205	With the new sys/modules/sound/drivers/*, you will need to
206	set SYSDIR until you do an installworld after July 7th.
207
20820000704:
209	rc.shutdown and rc will now call the rc.d scripts with start
210	or stop.  This may cause some harmless warnings from older
211	rc.d scripts that haven't been updated.
212
21320000630:
214	The libfetch based version of fetch has gone into the tree.
215	Minor problems may result on some of the less popular sites,
216	which should be reported to des@freebsd.org.
217
21820000625:
219	From approximately this date forward, one must have the crypto
220	system installed in order to build the system and kernel.
221	While not technically strictly true, one should treat it as
222	required and grab the crypto bits.  If you are grabbing CVS
223	trees, src-all and cvs-crypto should be treated as if they
224	were required.  You should check with the latest collections
225	to make sure that these haven't changed.
226
22720000624:
228	Mark Murray just committed the first parts of a cleanup of
229	/dev/zero, et al.  This is also cleaning up /dev/random.
230	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
231	-CURRENT FROM THIS POINT FORWARD for cryptographic services
232	until Mark can merge in the fixes to this work in progress.
233	openssh and openssl should not be used to generate keys from this
234	date to the completion of the work.
235
236	If you must operate at this reduced level of security, add '
237	options RANDOMDEV' to your kernel or modload the randomdev
238	module.  You may also need to copy a new MAKEDEV to /dev and
239	recreate the random and urandom devices.
240
24120000622:
242	The license on the softupdates is now a standard 2 clause
243	BSD license.  You may need to remove your symbolic links
244	that used to be required when updating.
245
24620000621:
247	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
248	the config file update procedure.
249		http://people.freebsd.org/~imp/config-upd.html
250	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
251	isn't buildable.  However, you can generate a LINT file.
252
25320000620:
254	Binutils 2.10 have hit the tree, or will shortly.  As soon
255	as they do, the problem noted in 20000522 will be resolved and
256	that workaround will no longer be required.
257
25820000615:
259	phk removed the compatibility creation of wd devices in the
260	ad driver.  If you haven't done so already, you must update
261	your fstab, etc to use the ad devices instead of the wd
262	devices.
263
264	In addition, you'll need to update your boot blocks to a
265	more modern version, if you haven't already done so.  Modern
266	here means 4.0 release or newer (although older releases
267	may work).
268
26920000612:
270	Peter took an axe to config(8).  Be sure that you read his mail
271	on the topic before even thinking about updating.  You will
272	need to create a /boot/device.hints or add a hints directive
273	to your config file to compile them in statically.  The format
274	of the config file has changed as well.  Please see GENERIC or
275	NEWCARD for examples of the new format.
276
27720000522:
278	A new set of binutils went into the tree today.  Anybody
279	building a kernel after this point is advised that they need
280	to rebuild their binutils (or better yet do a
281	buildworld/installworld) before building a new kernel.
282
283	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
284	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
285	is recommended that you don't set this option until the problem
286	is resolved.
287
28820000513:
289	The ethernet drivers were all updated to clean up the BPF handling.
290
29120000510:
292	The problems with boot blocks on the alphas have been corrected.
293	This will require some care in updating alphas.  A new libstand
294	is requires for the boot blocks to build properly.
295
29620000503:
297	Recompile all kld modules.  Proper version dependency info
298	is now available.
299
30020000502:
301	Modules have been disconnected from the buildworld tree and 
302	connected to the kernel building instead.
303
3042000427:
305	You may need to build gperf
306		cd /usr/src/gnu/usr.bin/gperf && make depend all install
307	when upgrading from 4.0 -> current.  The build system now uses
308	an option only in -current.
309
31020000417:
311	The method that we brand ELF binaries has changed to be more
312	acceptable to the binutils maintainers.  You will need to
313	rebrand your ELF binaries that aren't native.  One problem
314	binary is the Linux ldconfig.  After your make world, but
315	before you reboot, you'll need to issue:
316		brandelf -t Linux /compat/linux/sbin/ldconfig
317	if you have Linux compatibility enabled on your machine.
318
31920000320:
320	If you have really bad/marginal IDE drives, you may find they
321	don't work well.  Use pio mode instead.  The easiest way to
322	cope if you have a problem combination is to add:
323		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
324	to the start of /etc/rc.conf.
325
32620000319:
327	The ISA and PCI compatibility shims have been connected to the
328	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
329	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
330	include the appropriate option in your kernel config.  Drivers
331	using the shims should be updated or they won't ship with
332	5.0-RELEASE, targeted for 2001.
333
33420000318:
335	We've entered the traditional post release dumping party.
336	Large kernel changes are being committed and are in the
337	works.  It is important to keep the systems' klds and kernel
338	in sync as kernel interfaces and structures are changing.
339	Before reporting kernel panics, make sure that all modules
340	that you are loading are up to date.
341
34220000315:
343	If you are upgrading from an older version of FreeBSD, you
344	need to update your boot blocks as well.  'disklabel -B ad0'
345	will do the trick.  This isn't critical until you remove your
346	wd device entries in /dev, at which point your system will not
347	boot.
348
34920000315:
350	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
351	to upgrade to 4.0 from 3.x.
352
353COMMON ITEMS:
354
355	General Notes
356	-------------
357	Avoid using make -j when upgrading.  From time to time in the
358	past there have been problems using -j with buildworld and/or
359	installworld.  This is especially true when upgrading between
360	"distant" versions (eg one that cross a major release boundary
361	or several minor releases, or when several months have passed
362	on the -current branch).
363
364	To build a kernel
365	-----------------
366	If you are updating from a prior version of FreeBSD (even one just
367	a few days old), you should follow this procedure. With a
368	/usr/obj tree with a fresh buildworld,
369	make buildkernel KERNEL=YOUR_KERNEL_HERE
370	make installkernel KERNEL=YOUR_KERNEL_HERE
371
372	To just build a kernel when you know that it won't mess you up
373	--------------------------------------------------------------
374	cd src/sys/{i386,alpha}/conf
375	config KERNEL_NAME_HERE			[1]
376	cd ../../compile/KERNEL_NAME_HERE
377	make depend
378	make
379	make install	
380	
381	[1] If in doubt, -r might help here.
382
383	If this fails, go to the "To build a kernel" section.
384
385	To rebuild everything and install it on the current system.
386	-----------------------------------------------------------
387	make world
388	Build a new kernel, see above.
389
390	To upgrade from 4.x-stable to current
391	-------------------------------------
392	make buildworld
393	make buildkernel KERNEL=YOUR_KERNEL_HERE
394	cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
395	make installkernel KERNEL=YOUR_KERNEL_HERE
396	make installworld
397	[1]
398	<reboot>
399
400	Make sure that you've read the UPDATING file to understand the
401	tweaks to various things you need.  At this point in the life
402	cycle of current, things change often and you are on your own
403	to cope.  The defaults can also change, so please read ALL of
404	the UPDATING entries.
405
406	Also, if you are tracking -current, you must be subscribed to
407	freebsd-current@freebsd.org.  Make sure that before you update
408	your sources that you have read and understood all the recent
409	messages there.  If in doubt, please track -stable which has
410	much fewer pitfalls.
411
412	[1] If you have third party modules, such as vmware, you
413	should disable them at this point so they don't crash your
414	system on reboot.
415
416	[2] If you have legacy ISA devices, you may need to create
417	your own device.hints to reflect your unique hardware
418	configuration.
419
420FORMAT:
421
422This file contains a list, in reverse chronological order, of major
423breakages in tracking -current.  Not all things will be listed here,
424and it only starts on March 15, 2000.  Updating files can found in
425previous releases if your system is older than this.
426
427Please filter your entries through Warner Losh (imp@village.org) so
428that the style, formatting, etc of this file can be maintained.
429
430$FreeBSD: head/UPDATING 65908 2000-09-16 03:08:55Z imp $
431