UPDATING revision 64577
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
820000812:
9	suidperl is now always built and installed on the system, but
10	with permissions of 511.  If you have applications that use
11	this program, you are now required to add ENABLE_SUIDPERL=true
12	to /etc/make.conf.  If you forget to do this,
13		chmod 4511 /usr/bin/suidperl
14	will fix this until the next build.
15
1620000812:
17	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
18	visible changes that may immediately affect your configuration
19	include:
20	- New default file locations from src/contrib/sendmail/cf/README
21	- newaliases limited to root and trusted users
22	- MSA port (587) turned on by default
23	- New queue file naming system so can't go from 8.11 -> 8.9
24	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
25	- FEATURE(`nullclient') is more full featured
26	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
27	- mail.local FreeBSD-only -b option changed to -B
28	- See src/contrib/sendmail/RELEASE_NOTES for more info
29
3020000810:
31	suidperl (aka sperl) is no longer build by default.  You must
32	specifically define BUILD_SUIDPERL to "true" for it to be build.
33	Furthermore, we recommend that you remove /usr/bin/sperl* and
34	/usr/bin/suidperl files from your system unless you have a
35	specific use for it.
36
3720000729:
38	Networking defaults have been tightened.  Anybody upgrading
39	/etc/defaults/rc.conf needs to add the following lines to
40	/etc/rc.conf if they want to have the same setup
41	afterwards (unless the variables already are set, of course):
42		# Enable network daemons for user convenience.
43		inetd_enable="YES"
44		portmap_enable="YES"
45		sendmail_enable="YES"
46
4720000728:
48	If you have null_load="YES" in your /boot/loader.conf, you
49	will need to change that to nullfs_load="YES".
50
5120000728:
52	The "installkernel" target has changed slightly. Now even if
53	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
54	it will install the MYKERNEL file (built with the buildkernel
55	target) as /kernel rather than /MYKERNEL. Those who have
56	updated their /boot/loader.conf files to point to /MYKERNEL
57	should remove that entry or perform manual rename of /kernel
58	to /MYKERNEL.
59
6020000711:
61	If you use CVSUP or CTM to get CVS trees, AND you used to get 
62	the old crypto files from internat.freebsd.org AND you check
63	out files from the CVS tree with the cvs command, please read
64		http://people.freebsd.org/~imp/internat.txt
65	for details on potential problems that you might have and how
66	to get around them.
67
68	If you are merely a mirror, or don't answer yes to each of the
69	clauses above, you needn't worry.
70
7120000711:
72	/etc/security has been updated to print the inode number of
73	setuid programs that have changed.  You will see a large spike
74	in the number of changed programs the first time when you run
75	mergemaster to get a new /etc/security.
76
7720000710:
78	/dev/random now has good entropy collection (from the keyboard
79	and sysmouse drivers). Please ensure that either `options
80	RANDOMDEV' is present in your kernel config file or that
81	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
82	not have the /dev/random driver, OpenSSL (and consequently
83	lots of crypto tools (like SSH)) will fail with strange
84	errors. (see below, 20000624).
85
86	FreeBSD-current is safe again to run Crypto.
87
8820000709:
89	phk made the malloc default options AJ.  This may slow things
90	down and uncover other latent bugs in the code.  If you need to
91	run at full speed, you can disable this by doing the following:
92		ln -s aj /etc/malloc.conf
93
9420000706:
95	libftpio's version was accidentally bumped a few days ago.  This
96	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
97	before doing your next buildworld/installworld pair.  It certainly
98	won't hurt to remove it before the update proceedure.  It will
99	break fetch until a new one is built, but ftp can be used in the
100	interrum if needed.
101
10220000705:
103	The crypto packages have changed for the cvsup.  This has been done
104	in a backward compatible way, but the old packages will go away at
105	some point in the future.  Look at /usr/share/examples/cvsup for
106	details.
107
10820000704:
109	With the new sys/modules/sound/drivers/*, you will need to
110	set SYSDIR until you do an installworld after July 7th.
111
11220000704:
113	rc.shutdown and rc will now call the rc.d scripts with start
114	or stop.  This may cause some harmless warnings from older
115	rc.d scripts that haven't been updated.
116
11720000630:
118	The libfetch based version of fetch has gone into the tree.
119	Minor problems may result on some of the less popular sites,
120	which should be reported to des@freebsd.org.
121
12220000625:
123	From approximately this date forward, one must have the crypto
124	system installed in order to build the system and kernel.
125	While not technically strictly true, one should treat it as
126	required and grab the crypto bits.  If you are grabbing CVS
127	trees, src-all and cvs-crypto should be treated as if they
128	were required.  You should check with the latest collections
129	to make sure that these haven't changed.
130
13120000624:
132	Mark Murray just committed the first parts of a cleanup of
133	/dev/zero, et al.  This is also cleaning up /dev/random.
134	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
135	-CURRENT FROM THIS POINT FORWARD for cryptographic services
136	until Mark can merge in the fixes to this work in progress.
137	openssh and openssl should not be used to generate keys from this
138	date to the completion of the work.
139
140	If you must operate at this reduced level of security, add '
141	options RANDOMDEV' to your kernel or modload the randomdev
142	module.  You may also need to copy a new MAKEDEV to /dev and
143	recreate the random and urandom devices.
144
14520000622:
146	The license on the softupdates is now a standard 2 clause
147	BSD license.  You may need to remove your symbolic links
148	that used to be required when updating.
149
15020000621:
151	Scott Flatman <sf@aracnet.com> sent in a decent writeup on
152	the config file update procedure.
153		http://people.freebsd.org/~imp/config-upd.html
154	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
155	isn't buildable.
156
15720000620:
158	Binutils 2.10 have hit the tree, or will shortly.  As soon
159	as they do, the problem noted in 20000522 will be resolved and
160	that workaround will no longer be required.
161
16220000615:
163	phk removed the compatibility creation of wd devices in the
164	ad driver.  If you haven't done so already, you must update
165	your fstab, etc to use the ad devices instead of the wd
166	devices.
167
168	In addition, you'll need to update your boot blocks to a
169	more modern version, if you haven't already done so.  Modern
170	here means 4.0 release or newer (although older releases
171	may work).
172
17320000612:
174	Peter took an axe to config(8).  Besure that you read his mail
175	on the topic before even thinking about updating.  You will
176	need to create a /boot/device.hints or add a hints directive
177	to your config file to compile them in statically.  The format
178	of the config file has changed as well.  Please see GENERIC or
179	NEWCARD for examples of the new format.
180
18120000522:
182	A new set of binutils went into the tree today.  Anybody
183	building a kernel after this point is advised that they need
184	to rebuild their binutils (or better yet do a
185	buildworld/installworld) before building a new kernel.
186
187	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
188	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
189	is recommended that you don't set this option until the problem
190	is resolved.
191
19220000513:
193	The ethernet drivers were all updated to clean up the BPF handling.
194
19520000510:
196	The problems with boot blocks on the alphas have been corrected.
197	This will require some care in updating alphas.  A new libstand
198	is requires for the boot blocks to build properly.
199
20020000503:
201	Recompile all kld modules.  Proper version dependency info
202	is now available.
203
20420000502:
205	Modules have been disconnected from the buildworld tree and 
206	connected to the kernel building instead.
207
2082000427:
209	You may need to build gperf
210		cd /usr/src/gnu/usr.bin/gperf && make depend all install
211	when upgrading from 4.0 -> current.  The build system now uses
212	an option only in -current.
213
21420000417:
215	The method that we brand ELF binaries has changed to be more
216	acceptible to the binutils maintainers.  You will need to
217	rebrand your ELF binaries that aren't native.  One problem
218	binary is the Linux ldconfig.  After your make world, but
219	before you reboot, you'll neeed to issue:
220		brandelf -t Linux /compat/linux/sbin/ldconfig
221	if you have Linux compatibility enabled on your machine.
222
22320000320:
224	If you have really bad/marginal IDE drives, you may find they
225	don't work well.  Use pio mode instead.  The easiest way to
226	cope if you have a problem combination is to add:
227		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
228	to the start of /etc/rc.conf.
229
23020000319:
231	The ISA and PCI compatability shims have been connected to the
232	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
233	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
234	include the appropriate option in your kernel config.  Drivers
235	using the shims should be updated or they won't ship with
236	5.0-RELEASE, targeted for 2001.
237
23820000318:
239	We've entered the tradtional post release dumping party.
240	Large kernel changes are being committed and are in the
241	works.  It is important to keep the systems' klds and kernel
242	in sync as kernel interfaces and structures are changing.
243	Before reporting kernel panics, make sure that all modules
244	that you are loading are up to date.
245
24620000315:
247	If you are upgrading from an older version of FreeBSD, you
248	need to update your boot blocks as well.  'disklabel -B ad0'
249	will do the trick.  This isn't critical until you remove your
250	wd device entries in /dev, at which point your system will not
251	boot.
252
25320000315:
254	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
255	to upgrade to 4.0 from 3.x.
256
257COMMON ITEMS:
258
259	To build a kernel
260	-----------------
261	If you are updating from a prior version of FreeBSD (even one just
262	a few days old), you should follow this proceedure. With a
263	/usr/obj tree with a fresh buildworld,
264	make buildkernel KERNEL=YOUR_KERNEL_HERE
265	make installkernel KERNEL=YOUR_KERNEL_HERE
266
267	To just build a kernel when you know that it won't mess you up
268	--------------------------------------------------------------
269	cd src/sys/{i386,alpha}/conf
270	config KERNEL_NAME_HERE			[1]
271	cd ../../compile/KERNEL_NAME_HERE
272	make depend
273	make
274	make install	
275	
276	[1] If in doubt, -r might help here.
277
278	If this fails, go to the "To build a kernel" section.
279
280	To rebuild everything and install it on the current system.
281	-----------------------------------------------------------
282	make world
283
284	To upgrade from 4.x-stable to current
285	-------------------------------------
286	make buildworld
287	make buildkernel KERNEL=YOUR_KERNEL_HERE
288	make installkernel KERNEL=YOUR_KERNEL_HERE
289	make installworld
290	[1]
291	<reboot>
292
293	Make sure that you've read the UPDATING file to understand
294	the tweaks to various things you need.  At this point in the
295	life cycloe of current, things change often and you are on
296	your own to cope.
297
298	Also, if you are tracking -current, you must be subscribed to
299	freebsd-current@freebsd.org.  Make sure that before you update
300	your sources that you have read and understood all the recent
301	messages there.  If in doubt, please track -stable which has
302	much fewer pitfalls.
303
304	[1] If you have third party modules, such as vmware, you
305	should disable them at this point so they don't crash your
306	system on reboot.
307
308FORMAT:
309
310This file contains a list, in reverse chronologocal order, of major
311breakages in tracking -current.  Not all things will be listed here,
312and it only starts on March 15, 2000.  Updating files can found in
313previous releases if your system is older than this.
314
315Please filter your entries through Warner Losh (imp@village.org) so
316that the style, formatting, etc of this file can be maintained.
317
318$FreeBSD: head/UPDATING 64577 2000-08-13 02:19:13Z imp $
319