xref: /freebsd/UPDATING (revision 81e54c501404cc264588e95bae836e604daedaf5)
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
881e54c50SWarner Losh20000622:
981e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
1081e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
1181e54c50SWarner Losh	that used to be required when updating.
1281e54c50SWarner Losh
1339943833SWarner Losh20000621:
1439943833SWarner Losh	Scott Flatman <sf@aracnet.com> sent in a decent writeup on
152a2f33fbSDaniel Baker	the config file update procedure.
162a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1739943833SWarner Losh
18290f9ad8SWarner Losh20000620:
19290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
20290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
21290f9ad8SWarner Losh	that workaround will no longer be required.
22290f9ad8SWarner Losh
2390fb6346SWarner Losh20000615:
2490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
2590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
2690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
2790fb6346SWarner Losh	devices.
2890fb6346SWarner Losh
29f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
30f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
31f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
32f75f65bbSWarner Losh	may work).
33f75f65bbSWarner Losh
34ba26da8eSWarner Losh20000612:
35ba26da8eSWarner Losh	Peter took an axe to config(8).  Besure that you read his mail
36290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
37290f9ad8SWarner Losh	need to create a /boot/devices.hints or add a hints directive
38290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
39290f9ad8SWarner Losh	of the config file has changed as well.  Please see LINT,
40290f9ad8SWarner Losh	GENERIC or NEWCARD for examples of the new format.
41290f9ad8SWarner Losh
42290f9ad8SWarner Losh	More details to follow.  A better howto would be warmly
43290f9ad8SWarner Losh	accepted by the author of UPDATING.
44ba26da8eSWarner Losh
45d65850ebSWarner Losh20000522:
46ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
47d65850ebSWarner Losh	building a kernel after this point is advised that they need
48d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
49d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
50d65850ebSWarner Losh
51d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
52d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
53d9583a00SWarner Losh	is recommended that you don't set this option until the problem
54d9583a00SWarner Losh	is resolved.
55d9583a00SWarner Losh
568039cedeSWarner Losh20000513:
578039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
588039cedeSWarner Losh
59d65850ebSWarner Losh20000510:
608039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
618039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
628039cedeSWarner Losh	is requires for the boot blocks to build properly.
638039cedeSWarner Losh
648039cedeSWarner Losh20000503:
658039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
668039cedeSWarner Losh	is now available.
678039cedeSWarner Losh
68d65850ebSWarner Losh20000502:
69d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
70d65850ebSWarner Losh	connected to the kernel building instead.
71d65850ebSWarner Losh
728039cedeSWarner Losh2000427:
738039cedeSWarner Losh	You may need to build gperf
748039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
758039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
768039cedeSWarner Losh	an option only in -current.
778039cedeSWarner Losh
782b8dd5f4SWarner Losh20000417:
792b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
802b8dd5f4SWarner Losh	acceptible to the binutils maintainers.  You will need to
812b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
822b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
832b8dd5f4SWarner Losh	before you reboot, you'll neeed to issue:
842b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
852b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
862b8dd5f4SWarner Losh
878d9f1945SWarner Losh20000320:
882b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
892b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
902b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
918d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
922b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
938d9f1945SWarner Losh
94f8ab1dd6SWarner Losh20000319:
95f8ab1dd6SWarner Losh	The ISA and PCI compatability shims have been connected to the
96f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
97f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
98f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
99f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
100f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
101f8ab1dd6SWarner Losh
10219cada77SWarner Losh20000318:
10319cada77SWarner Losh	We've entered the tradtional post release dumping party.
10419cada77SWarner Losh	Large kernel changes are being committed and are in the
10519cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
10619cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
10719cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
10819cada77SWarner Losh	that you are loading are up to date.
109ba228352SWarner Losh
11019cada77SWarner Losh20000315:
1116d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
1126d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
1136d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
1146d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
1156d23c382SWarner Losh	boot.
1166d23c382SWarner Losh
1176d23c382SWarner Losh20000315:
11819cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
11919cada77SWarner Losh	to upgrade to 4.0 from 3.x.
12057199806SWarner Losh
121dc0dbf5cSWarner LoshCOMMON ITEMS:
122dc0dbf5cSWarner Losh
123dc0dbf5cSWarner Losh	To build a kernel
124dc0dbf5cSWarner Losh	-----------------
125dc0dbf5cSWarner Losh	Update config, genassym and go:
126ba26da8eSWarner Losh		config YOUR_KERNEL_HERE			[1]
127dc0dbf5cSWarner Losh		cd ../../compile/YOUR_KERNEL_HERE
128dc0dbf5cSWarner Losh		make depend && make
1293645fc1cSWarner Losh		make install
130ba26da8eSWarner Losh	[1] If upgrading, add -r won't hurt and sometimes helps.
131dc0dbf5cSWarner Losh
13216de1a07SWarner Losh	To rebuild everything
13316de1a07SWarner Losh	---------------------
134759f0aefSWarner Losh	make world
135759f0aefSWarner Losh
136ba26da8eSWarner Losh	To upgrade from 4.0-stable to current
137ba26da8eSWarner Losh	-------------------------------------
138ba26da8eSWarner Losh	make buildworld
139ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
140ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
141ba26da8eSWarner Losh	make installworld
142ba26da8eSWarner Losh	<reboot>
143ba26da8eSWarner Losh
144ba26da8eSWarner Losh	Make sure that you've read the UPDATING file to understand
145ba26da8eSWarner Losh	the tweaks to various things you need.  At this point in the
146ba26da8eSWarner Losh	life cycloe of current, things change often and you are on
147ba26da8eSWarner Losh	your own to cope.
148ba26da8eSWarner Losh
149dc0dbf5cSWarner LoshFORMAT:
150dc0dbf5cSWarner Losh
1511fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major
1521fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
153f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
154f8ab1dd6SWarner Loshprevious releases if your system is older than this.
1551fc1a0dcSWarner Losh
1563645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
1573645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
158f8c77507SWarner Losh
15997d92980SPeter Wemm$FreeBSD$
160