xref: /freebsd/UPDATING (revision c373950effbcd918ab9651a180a11be82c10d97b)
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
8c373950eSWarner Losh20000704:
9c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
10c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
11c373950eSWarner Losh	rc.d scripts that haven't been updated.
12c373950eSWarner Losh
1327dc3a2bSWarner Losh20000630:
1427dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
1527dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
1627dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
1727dc3a2bSWarner Losh
18b8c215acSWarner Losh20000625:
19b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
2027dc3a2bSWarner Losh	system installed in order to build the system and kernel.
2127dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
2227dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
2327dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
2427dc3a2bSWarner Losh	were required.  You should check with the latest collections
2527dc3a2bSWarner Losh	to make sure that these haven't changed.
26b8c215acSWarner Losh
277b990719SWarner Losh20000624:
287b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
297b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
307b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
317b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
327b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
337b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
347b990719SWarner Losh	date to the completion of the work.
357b990719SWarner Losh
3627dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
3727dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
3827dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
3927dc3a2bSWarner Losh	recreate the random and urandom devices.
4027dc3a2bSWarner Losh
4181e54c50SWarner Losh20000622:
4281e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
4381e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
4481e54c50SWarner Losh	that used to be required when updating.
4581e54c50SWarner Losh
4639943833SWarner Losh20000621:
4739943833SWarner Losh	Scott Flatman <sf@aracnet.com> sent in a decent writeup on
482a2f33fbSDaniel Baker	the config file update procedure.
492a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
50c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
51c373950eSWarner Losh	isn't buildable.
5239943833SWarner Losh
53290f9ad8SWarner Losh20000620:
54290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
55290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
56290f9ad8SWarner Losh	that workaround will no longer be required.
57290f9ad8SWarner Losh
5890fb6346SWarner Losh20000615:
5990fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
6090fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
6190fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
6290fb6346SWarner Losh	devices.
6390fb6346SWarner Losh
64f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
65f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
66f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
67f75f65bbSWarner Losh	may work).
68f75f65bbSWarner Losh
69ba26da8eSWarner Losh20000612:
70ba26da8eSWarner Losh	Peter took an axe to config(8).  Besure that you read his mail
71290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
72290f9ad8SWarner Losh	need to create a /boot/devices.hints or add a hints directive
73290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
74290f9ad8SWarner Losh	of the config file has changed as well.  Please see LINT,
75290f9ad8SWarner Losh	GENERIC or NEWCARD for examples of the new format.
76290f9ad8SWarner Losh
77d65850ebSWarner Losh20000522:
78ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
79d65850ebSWarner Losh	building a kernel after this point is advised that they need
80d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
81d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
82d65850ebSWarner Losh
83d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
84d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
85d9583a00SWarner Losh	is recommended that you don't set this option until the problem
86d9583a00SWarner Losh	is resolved.
87d9583a00SWarner Losh
888039cedeSWarner Losh20000513:
898039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
908039cedeSWarner Losh
91d65850ebSWarner Losh20000510:
928039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
938039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
948039cedeSWarner Losh	is requires for the boot blocks to build properly.
958039cedeSWarner Losh
968039cedeSWarner Losh20000503:
978039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
988039cedeSWarner Losh	is now available.
998039cedeSWarner Losh
100d65850ebSWarner Losh20000502:
101d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
102d65850ebSWarner Losh	connected to the kernel building instead.
103d65850ebSWarner Losh
1048039cedeSWarner Losh2000427:
1058039cedeSWarner Losh	You may need to build gperf
1068039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
1078039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
1088039cedeSWarner Losh	an option only in -current.
1098039cedeSWarner Losh
1102b8dd5f4SWarner Losh20000417:
1112b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1122b8dd5f4SWarner Losh	acceptible to the binutils maintainers.  You will need to
1132b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
1142b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
1152b8dd5f4SWarner Losh	before you reboot, you'll neeed to issue:
1162b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
1172b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
1182b8dd5f4SWarner Losh
1198d9f1945SWarner Losh20000320:
1202b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
1212b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
1222b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1238d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
1242b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
1258d9f1945SWarner Losh
126f8ab1dd6SWarner Losh20000319:
127f8ab1dd6SWarner Losh	The ISA and PCI compatability shims have been connected to the
128f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
129f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
130f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
131f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
132f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
133f8ab1dd6SWarner Losh
13419cada77SWarner Losh20000318:
13519cada77SWarner Losh	We've entered the tradtional post release dumping party.
13619cada77SWarner Losh	Large kernel changes are being committed and are in the
13719cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
13819cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
13919cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
14019cada77SWarner Losh	that you are loading are up to date.
141ba228352SWarner Losh
14219cada77SWarner Losh20000315:
1436d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
1446d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
1456d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
1466d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
1476d23c382SWarner Losh	boot.
1486d23c382SWarner Losh
1496d23c382SWarner Losh20000315:
15019cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
15119cada77SWarner Losh	to upgrade to 4.0 from 3.x.
15257199806SWarner Losh
153dc0dbf5cSWarner LoshCOMMON ITEMS:
154dc0dbf5cSWarner Losh
155dc0dbf5cSWarner Losh	To build a kernel
156dc0dbf5cSWarner Losh	-----------------
157dc0dbf5cSWarner Losh	Update config, genassym and go:
158ba26da8eSWarner Losh		config YOUR_KERNEL_HERE			[1]
159dc0dbf5cSWarner Losh		cd ../../compile/YOUR_KERNEL_HERE
160dc0dbf5cSWarner Losh		make depend && make
1613645fc1cSWarner Losh		make install
162ba26da8eSWarner Losh	[1] If upgrading, add -r won't hurt and sometimes helps.
163dc0dbf5cSWarner Losh
16416de1a07SWarner Losh	To rebuild everything
16516de1a07SWarner Losh	---------------------
166759f0aefSWarner Losh	make world
167759f0aefSWarner Losh
168ba26da8eSWarner Losh	To upgrade from 4.0-stable to current
169ba26da8eSWarner Losh	-------------------------------------
170ba26da8eSWarner Losh	make buildworld
171ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
172ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
173ba26da8eSWarner Losh	make installworld
174ba26da8eSWarner Losh	<reboot>
175ba26da8eSWarner Losh
176ba26da8eSWarner Losh	Make sure that you've read the UPDATING file to understand
177ba26da8eSWarner Losh	the tweaks to various things you need.  At this point in the
178ba26da8eSWarner Losh	life cycloe of current, things change often and you are on
179ba26da8eSWarner Losh	your own to cope.
180ba26da8eSWarner Losh
181dc0dbf5cSWarner LoshFORMAT:
182dc0dbf5cSWarner Losh
1831fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major
1841fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
185f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
186f8ab1dd6SWarner Loshprevious releases if your system is older than this.
1871fc1a0dcSWarner Losh
1883645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
1893645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
190f8c77507SWarner Losh
19197d92980SPeter Wemm$FreeBSD$
192