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