xref: /freebsd/UPDATING (revision e98e26cd692f175882dc429e40883f662c88b8d0)
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
8e98e26cdSWarner Losh20000706:
9e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
10e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
11e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
12e98e26cdSWarner Losh	won't hurt to remove it before the update proceedure.  It will
13e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
14e98e26cdSWarner Losh	interrum if needed.
15e98e26cdSWarner Losh
16e98e26cdSWarner Losh20000705:
17e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
18e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
19e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
20e98e26cdSWarner Losh	details.
21e98e26cdSWarner Losh
22c373950eSWarner Losh20000704:
23c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
24c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
25c373950eSWarner Losh	rc.d scripts that haven't been updated.
26c373950eSWarner Losh
2727dc3a2bSWarner Losh20000630:
2827dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
2927dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
3027dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
3127dc3a2bSWarner Losh
32b8c215acSWarner Losh20000625:
33b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
3427dc3a2bSWarner Losh	system installed in order to build the system and kernel.
3527dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
3627dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
3727dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
3827dc3a2bSWarner Losh	were required.  You should check with the latest collections
3927dc3a2bSWarner Losh	to make sure that these haven't changed.
40b8c215acSWarner Losh
417b990719SWarner Losh20000624:
427b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
437b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
447b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
457b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
467b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
477b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
487b990719SWarner Losh	date to the completion of the work.
497b990719SWarner Losh
5027dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
5127dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
5227dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
5327dc3a2bSWarner Losh	recreate the random and urandom devices.
5427dc3a2bSWarner Losh
5581e54c50SWarner Losh20000622:
5681e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
5781e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
5881e54c50SWarner Losh	that used to be required when updating.
5981e54c50SWarner Losh
6039943833SWarner Losh20000621:
6139943833SWarner Losh	Scott Flatman <sf@aracnet.com> sent in a decent writeup on
622a2f33fbSDaniel Baker	the config file update procedure.
632a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
64c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
65c373950eSWarner Losh	isn't buildable.
6639943833SWarner Losh
67290f9ad8SWarner Losh20000620:
68290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
69290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
70290f9ad8SWarner Losh	that workaround will no longer be required.
71290f9ad8SWarner Losh
7290fb6346SWarner Losh20000615:
7390fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
7490fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
7590fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
7690fb6346SWarner Losh	devices.
7790fb6346SWarner Losh
78f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
79f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
80f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
81f75f65bbSWarner Losh	may work).
82f75f65bbSWarner Losh
83ba26da8eSWarner Losh20000612:
84ba26da8eSWarner Losh	Peter took an axe to config(8).  Besure that you read his mail
85290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
86290f9ad8SWarner Losh	need to create a /boot/devices.hints or add a hints directive
87290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
88290f9ad8SWarner Losh	of the config file has changed as well.  Please see LINT,
89290f9ad8SWarner Losh	GENERIC or NEWCARD for examples of the new format.
90290f9ad8SWarner Losh
91d65850ebSWarner Losh20000522:
92ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
93d65850ebSWarner Losh	building a kernel after this point is advised that they need
94d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
95d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
96d65850ebSWarner Losh
97d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
98d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
99d9583a00SWarner Losh	is recommended that you don't set this option until the problem
100d9583a00SWarner Losh	is resolved.
101d9583a00SWarner Losh
1028039cedeSWarner Losh20000513:
1038039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
1048039cedeSWarner Losh
105d65850ebSWarner Losh20000510:
1068039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
1078039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
1088039cedeSWarner Losh	is requires for the boot blocks to build properly.
1098039cedeSWarner Losh
1108039cedeSWarner Losh20000503:
1118039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
1128039cedeSWarner Losh	is now available.
1138039cedeSWarner Losh
114d65850ebSWarner Losh20000502:
115d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
116d65850ebSWarner Losh	connected to the kernel building instead.
117d65850ebSWarner Losh
1188039cedeSWarner Losh2000427:
1198039cedeSWarner Losh	You may need to build gperf
1208039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
1218039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
1228039cedeSWarner Losh	an option only in -current.
1238039cedeSWarner Losh
1242b8dd5f4SWarner Losh20000417:
1252b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1262b8dd5f4SWarner Losh	acceptible to the binutils maintainers.  You will need to
1272b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
1282b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
1292b8dd5f4SWarner Losh	before you reboot, you'll neeed to issue:
1302b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
1312b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
1322b8dd5f4SWarner Losh
1338d9f1945SWarner Losh20000320:
1342b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
1352b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
1362b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1378d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
1382b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
1398d9f1945SWarner Losh
140f8ab1dd6SWarner Losh20000319:
141f8ab1dd6SWarner Losh	The ISA and PCI compatability shims have been connected to the
142f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
143f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
144f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
145f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
146f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
147f8ab1dd6SWarner Losh
14819cada77SWarner Losh20000318:
14919cada77SWarner Losh	We've entered the tradtional post release dumping party.
15019cada77SWarner Losh	Large kernel changes are being committed and are in the
15119cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
15219cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
15319cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
15419cada77SWarner Losh	that you are loading are up to date.
155ba228352SWarner Losh
15619cada77SWarner Losh20000315:
1576d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
1586d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
1596d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
1606d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
1616d23c382SWarner Losh	boot.
1626d23c382SWarner Losh
1636d23c382SWarner Losh20000315:
16419cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
16519cada77SWarner Losh	to upgrade to 4.0 from 3.x.
16657199806SWarner Losh
167dc0dbf5cSWarner LoshCOMMON ITEMS:
168dc0dbf5cSWarner Losh
169dc0dbf5cSWarner Losh	To build a kernel
170dc0dbf5cSWarner Losh	-----------------
171dc0dbf5cSWarner Losh	Update config, genassym and go:
172ba26da8eSWarner Losh		config YOUR_KERNEL_HERE			[1]
173dc0dbf5cSWarner Losh		cd ../../compile/YOUR_KERNEL_HERE
174dc0dbf5cSWarner Losh		make depend && make
1753645fc1cSWarner Losh		make install
176ba26da8eSWarner Losh	[1] If upgrading, add -r won't hurt and sometimes helps.
177dc0dbf5cSWarner Losh
17816de1a07SWarner Losh	To rebuild everything
17916de1a07SWarner Losh	---------------------
180759f0aefSWarner Losh	make world
181759f0aefSWarner Losh
182ba26da8eSWarner Losh	To upgrade from 4.0-stable to current
183ba26da8eSWarner Losh	-------------------------------------
184ba26da8eSWarner Losh	make buildworld
185ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
186ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
187ba26da8eSWarner Losh	make installworld
188ba26da8eSWarner Losh	<reboot>
189ba26da8eSWarner Losh
190ba26da8eSWarner Losh	Make sure that you've read the UPDATING file to understand
191ba26da8eSWarner Losh	the tweaks to various things you need.  At this point in the
192ba26da8eSWarner Losh	life cycloe of current, things change often and you are on
193ba26da8eSWarner Losh	your own to cope.
194ba26da8eSWarner Losh
195dc0dbf5cSWarner LoshFORMAT:
196dc0dbf5cSWarner Losh
1971fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major
1981fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
199f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
200f8ab1dd6SWarner Loshprevious releases if your system is older than this.
2011fc1a0dcSWarner Losh
2023645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
2033645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
204f8c77507SWarner Losh
20597d92980SPeter Wemm$FreeBSD$
206