xref: /freebsd/UPDATING (revision fdb9f54dde1e924195632e737f2bc72811287def)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3f8c77507SWarner LoshThis file is maintained by imp@village.org.  Please send new entries
4dc0dbf5cSWarner Loshdirectly to him.  See end of file for further details.  For commonly
516de1a07SWarner Loshdone items, please see the end of the file.  Search for 'COMMON
616de1a07SWarner LoshITEMS:'
716de1a07SWarner Losh
8fdb9f54dSWarner Losh20000825:
9fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
10fdb9f54dSWarner Losh	succeed.
11fdb9f54dSWarner Losh
128f250aa7SWarner Losh20000812:
135da0d091SWarner Losh	suidperl is now always built and installed on the system, but
145da0d091SWarner Losh	with permissions of 511.  If you have applications that use
155da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
165da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
175da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
185da0d091SWarner Losh	will fix this until the next build.
195da0d091SWarner Losh
205da0d091SWarner Losh20000812:
218f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
228f250aa7SWarner Losh	visible changes that may immediately affect your configuration
238f250aa7SWarner Losh	include:
248f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
258f250aa7SWarner Losh	- newaliases limited to root and trusted users
268f250aa7SWarner Losh	- MSA port (587) turned on by default
278f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
288f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
298f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
308f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
318f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
328f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
338f250aa7SWarner Losh
3471c38472SWarner Losh20000810:
3571c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
3671c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
3771c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
3871c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
3971c38472SWarner Losh	specific use for it.
4071c38472SWarner Losh
4171c38472SWarner Losh20000729:
4271c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
4371c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
4471c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
4571c38472SWarner Losh	afterwards (unless the variables already are set, of course):
4671c38472SWarner Losh		# Enable network daemons for user convenience.
4771c38472SWarner Losh		inetd_enable="YES"
4871c38472SWarner Losh		portmap_enable="YES"
4971c38472SWarner Losh		sendmail_enable="YES"
5071c38472SWarner Losh
5171c38472SWarner Losh20000728:
5271c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
5371c38472SWarner Losh	will need to change that to nullfs_load="YES".
5471c38472SWarner Losh
551dece4a9SWarner Losh20000728:
561dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
571dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
581dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
591dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
601dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
611dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
621dece4a9SWarner Losh	to /MYKERNEL.
631dece4a9SWarner Losh
64409e887cSWarner Losh20000711:
65409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
66409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
67409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
68409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
69409e887cSWarner Losh	for details on potential problems that you might have and how
70409e887cSWarner Losh	to get around them.
71409e887cSWarner Losh
72409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
73409e887cSWarner Losh	clauses above, you needn't worry.
74409e887cSWarner Losh
75409e887cSWarner Losh20000711:
76409e887cSWarner Losh	/etc/security has been updated to print the inode number of
77409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
78409e887cSWarner Losh	in the number of changed programs the first time when you run
79409e887cSWarner Losh	mergemaster to get a new /etc/security.
80409e887cSWarner Losh
81673d13f2SWarner Losh20000710:
82673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
83673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
84673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
85673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
86673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
87673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
88673d13f2SWarner Losh	errors. (see below, 20000624).
89673d13f2SWarner Losh
90bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
911dece4a9SWarner Losh
92673d13f2SWarner Losh20000709:
93c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
94c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
95c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
96673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
97673d13f2SWarner Losh
98e98e26cdSWarner Losh20000706:
99e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
100e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
101e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
102e98e26cdSWarner Losh	won't hurt to remove it before the update proceedure.  It will
103e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
104e98e26cdSWarner Losh	interrum if needed.
105e98e26cdSWarner Losh
106e98e26cdSWarner Losh20000705:
107e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
108e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
109e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
110e98e26cdSWarner Losh	details.
111e98e26cdSWarner Losh
112c373950eSWarner Losh20000704:
1132f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
1142f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
1152f961bc8SWarner Losh
1162f961bc8SWarner Losh20000704:
117c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
118c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
119c373950eSWarner Losh	rc.d scripts that haven't been updated.
120c373950eSWarner Losh
12127dc3a2bSWarner Losh20000630:
12227dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
12327dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
12427dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
12527dc3a2bSWarner Losh
126b8c215acSWarner Losh20000625:
127b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
12827dc3a2bSWarner Losh	system installed in order to build the system and kernel.
12927dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
13027dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
13127dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
13227dc3a2bSWarner Losh	were required.  You should check with the latest collections
13327dc3a2bSWarner Losh	to make sure that these haven't changed.
134b8c215acSWarner Losh
1357b990719SWarner Losh20000624:
1367b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
1377b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
1387b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1397b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
1407b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
1417b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
1427b990719SWarner Losh	date to the completion of the work.
1437b990719SWarner Losh
14427dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
14527dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
14627dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
14727dc3a2bSWarner Losh	recreate the random and urandom devices.
14827dc3a2bSWarner Losh
14981e54c50SWarner Losh20000622:
15081e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
15181e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
15281e54c50SWarner Losh	that used to be required when updating.
15381e54c50SWarner Losh
15439943833SWarner Losh20000621:
15539943833SWarner Losh	Scott Flatman <sf@aracnet.com> sent in a decent writeup on
1562a2f33fbSDaniel Baker	the config file update procedure.
1572a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
158c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
159c373950eSWarner Losh	isn't buildable.
16039943833SWarner Losh
161290f9ad8SWarner Losh20000620:
162290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
163290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
164290f9ad8SWarner Losh	that workaround will no longer be required.
165290f9ad8SWarner Losh
16690fb6346SWarner Losh20000615:
16790fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
16890fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
16990fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
17090fb6346SWarner Losh	devices.
17190fb6346SWarner Losh
172f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
173f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
174f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
175f75f65bbSWarner Losh	may work).
176f75f65bbSWarner Losh
177ba26da8eSWarner Losh20000612:
178ba26da8eSWarner Losh	Peter took an axe to config(8).  Besure that you read his mail
179290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
180c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
181290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
182f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
183f54a3542SWarner Losh	NEWCARD for examples of the new format.
184290f9ad8SWarner Losh
185d65850ebSWarner Losh20000522:
186ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
187d65850ebSWarner Losh	building a kernel after this point is advised that they need
188d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
189d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
190d65850ebSWarner Losh
191d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
192d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
193d9583a00SWarner Losh	is recommended that you don't set this option until the problem
194d9583a00SWarner Losh	is resolved.
195d9583a00SWarner Losh
1968039cedeSWarner Losh20000513:
1978039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
1988039cedeSWarner Losh
199d65850ebSWarner Losh20000510:
2008039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
2018039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
2028039cedeSWarner Losh	is requires for the boot blocks to build properly.
2038039cedeSWarner Losh
2048039cedeSWarner Losh20000503:
2058039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
2068039cedeSWarner Losh	is now available.
2078039cedeSWarner Losh
208d65850ebSWarner Losh20000502:
209d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
210d65850ebSWarner Losh	connected to the kernel building instead.
211d65850ebSWarner Losh
2128039cedeSWarner Losh2000427:
2138039cedeSWarner Losh	You may need to build gperf
2148039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
2158039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
2168039cedeSWarner Losh	an option only in -current.
2178039cedeSWarner Losh
2182b8dd5f4SWarner Losh20000417:
2192b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
2202b8dd5f4SWarner Losh	acceptible to the binutils maintainers.  You will need to
2212b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
2222b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
2232b8dd5f4SWarner Losh	before you reboot, you'll neeed to issue:
2242b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
2252b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
2262b8dd5f4SWarner Losh
2278d9f1945SWarner Losh20000320:
2282b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
2292b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
2302b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
2318d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
2322b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
2338d9f1945SWarner Losh
234f8ab1dd6SWarner Losh20000319:
235f8ab1dd6SWarner Losh	The ISA and PCI compatability shims have been connected to the
236f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
237f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
238f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
239f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
240f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
241f8ab1dd6SWarner Losh
24219cada77SWarner Losh20000318:
24319cada77SWarner Losh	We've entered the tradtional post release dumping party.
24419cada77SWarner Losh	Large kernel changes are being committed and are in the
24519cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
24619cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
24719cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
24819cada77SWarner Losh	that you are loading are up to date.
249ba228352SWarner Losh
25019cada77SWarner Losh20000315:
2516d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
2526d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
2536d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
2546d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
2556d23c382SWarner Losh	boot.
2566d23c382SWarner Losh
2576d23c382SWarner Losh20000315:
25819cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
25919cada77SWarner Losh	to upgrade to 4.0 from 3.x.
26057199806SWarner Losh
261dc0dbf5cSWarner LoshCOMMON ITEMS:
262dc0dbf5cSWarner Losh
263dc0dbf5cSWarner Losh	To build a kernel
264dc0dbf5cSWarner Losh	-----------------
265ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
266ba01eb20SWarner Losh	a few days old), you should follow this proceedure. With a
267ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
268ba01eb20SWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
269ba01eb20SWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
270dc0dbf5cSWarner Losh
271ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
272ba01eb20SWarner Losh	--------------------------------------------------------------
273ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
274ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
275ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
276ba01eb20SWarner Losh	make depend
277ba01eb20SWarner Losh	make
278ba01eb20SWarner Losh	make install
279ba01eb20SWarner Losh
280ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
281ba01eb20SWarner Losh
282ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
283ba01eb20SWarner Losh
284ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
285ba01eb20SWarner Losh	-----------------------------------------------------------
286759f0aefSWarner Losh	make world
287fdb9f54dSWarner Losh	Build a new kernel, see above.
288759f0aefSWarner Losh
2891dece4a9SWarner Losh	To upgrade from 4.x-stable to current
290ba26da8eSWarner Losh	-------------------------------------
291ba26da8eSWarner Losh	make buildworld
292ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
293ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
294ba26da8eSWarner Losh	make installworld
295134d2e86SWarner Losh	[1]
296ba26da8eSWarner Losh	<reboot>
297ba26da8eSWarner Losh
298fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
299fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
300fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
301fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
302fdb9f54dSWarner Losh	the UPDATING entries.
303ba26da8eSWarner Losh
3041dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
3051dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
3061dece4a9SWarner Losh	your sources that you have read and understood all the recent
3071dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
3081dece4a9SWarner Losh	much fewer pitfalls.
3091dece4a9SWarner Losh
310134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
311134d2e86SWarner Losh	should disable them at this point so they don't crash your
312134d2e86SWarner Losh	system on reboot.
313134d2e86SWarner Losh
314dc0dbf5cSWarner LoshFORMAT:
315dc0dbf5cSWarner Losh
3161fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major
3171fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
318f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
319f8ab1dd6SWarner Loshprevious releases if your system is older than this.
3201fc1a0dcSWarner Losh
3213645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
3223645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
323f8c77507SWarner Losh
32497d92980SPeter Wemm$FreeBSD$
325