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