xref: /freebsd/UPDATING (revision b8c215accdd85e3a2c2fd18ad3568a4ba2fa0cde)
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
8b8c215acSWarner Losh20000625:
9b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
10b8c215acSWarner Losh	system installed in order to build the system and kernel.  While
11b8c215acSWarner Losh	not technically strictly true, one should treat it as true and
12b8c215acSWarner Losh	grab the crypto bits.  If you are grabbing CVS trees, src-all
13b8c215acSWarner Losh	and cvs-crypto should be treated as if they were required.
14b8c215acSWarner Losh
157b990719SWarner Losh20000624:
167b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
177b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
187b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
197b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
207b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
217b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
227b990719SWarner Losh	date to the completion of the work.
237b990719SWarner Losh
2481e54c50SWarner Losh20000622:
2581e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
2681e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
2781e54c50SWarner Losh	that used to be required when updating.
2881e54c50SWarner Losh
2939943833SWarner Losh20000621:
3039943833SWarner Losh	Scott Flatman <sf@aracnet.com> sent in a decent writeup on
312a2f33fbSDaniel Baker	the config file update procedure.
322a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
3339943833SWarner Losh
34290f9ad8SWarner Losh20000620:
35290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
36290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
37290f9ad8SWarner Losh	that workaround will no longer be required.
38290f9ad8SWarner Losh
3990fb6346SWarner Losh20000615:
4090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
4190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
4290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
4390fb6346SWarner Losh	devices.
4490fb6346SWarner Losh
45f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
46f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
47f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
48f75f65bbSWarner Losh	may work).
49f75f65bbSWarner Losh
50ba26da8eSWarner Losh20000612:
51ba26da8eSWarner Losh	Peter took an axe to config(8).  Besure that you read his mail
52290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
53290f9ad8SWarner Losh	need to create a /boot/devices.hints or add a hints directive
54290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
55290f9ad8SWarner Losh	of the config file has changed as well.  Please see LINT,
56290f9ad8SWarner Losh	GENERIC or NEWCARD for examples of the new format.
57290f9ad8SWarner Losh
58d65850ebSWarner Losh20000522:
59ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
60d65850ebSWarner Losh	building a kernel after this point is advised that they need
61d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
62d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
63d65850ebSWarner Losh
64d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
65d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
66d9583a00SWarner Losh	is recommended that you don't set this option until the problem
67d9583a00SWarner Losh	is resolved.
68d9583a00SWarner Losh
698039cedeSWarner Losh20000513:
708039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
718039cedeSWarner Losh
72d65850ebSWarner Losh20000510:
738039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
748039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
758039cedeSWarner Losh	is requires for the boot blocks to build properly.
768039cedeSWarner Losh
778039cedeSWarner Losh20000503:
788039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
798039cedeSWarner Losh	is now available.
808039cedeSWarner Losh
81d65850ebSWarner Losh20000502:
82d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
83d65850ebSWarner Losh	connected to the kernel building instead.
84d65850ebSWarner Losh
858039cedeSWarner Losh2000427:
868039cedeSWarner Losh	You may need to build gperf
878039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
888039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
898039cedeSWarner Losh	an option only in -current.
908039cedeSWarner Losh
912b8dd5f4SWarner Losh20000417:
922b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
932b8dd5f4SWarner Losh	acceptible to the binutils maintainers.  You will need to
942b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
952b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
962b8dd5f4SWarner Losh	before you reboot, you'll neeed to issue:
972b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
982b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
992b8dd5f4SWarner Losh
1008d9f1945SWarner Losh20000320:
1012b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
1022b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
1032b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1048d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
1052b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
1068d9f1945SWarner Losh
107f8ab1dd6SWarner Losh20000319:
108f8ab1dd6SWarner Losh	The ISA and PCI compatability shims have been connected to the
109f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
110f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
111f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
112f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
113f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
114f8ab1dd6SWarner Losh
11519cada77SWarner Losh20000318:
11619cada77SWarner Losh	We've entered the tradtional post release dumping party.
11719cada77SWarner Losh	Large kernel changes are being committed and are in the
11819cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
11919cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
12019cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
12119cada77SWarner Losh	that you are loading are up to date.
122ba228352SWarner Losh
12319cada77SWarner Losh20000315:
1246d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
1256d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
1266d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
1276d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
1286d23c382SWarner Losh	boot.
1296d23c382SWarner Losh
1306d23c382SWarner Losh20000315:
13119cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
13219cada77SWarner Losh	to upgrade to 4.0 from 3.x.
13357199806SWarner Losh
134dc0dbf5cSWarner LoshCOMMON ITEMS:
135dc0dbf5cSWarner Losh
136dc0dbf5cSWarner Losh	To build a kernel
137dc0dbf5cSWarner Losh	-----------------
138dc0dbf5cSWarner Losh	Update config, genassym and go:
139ba26da8eSWarner Losh		config YOUR_KERNEL_HERE			[1]
140dc0dbf5cSWarner Losh		cd ../../compile/YOUR_KERNEL_HERE
141dc0dbf5cSWarner Losh		make depend && make
1423645fc1cSWarner Losh		make install
143ba26da8eSWarner Losh	[1] If upgrading, add -r won't hurt and sometimes helps.
144dc0dbf5cSWarner Losh
14516de1a07SWarner Losh	To rebuild everything
14616de1a07SWarner Losh	---------------------
147759f0aefSWarner Losh	make world
148759f0aefSWarner Losh
149ba26da8eSWarner Losh	To upgrade from 4.0-stable to current
150ba26da8eSWarner Losh	-------------------------------------
151ba26da8eSWarner Losh	make buildworld
152ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
153ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
154ba26da8eSWarner Losh	make installworld
155ba26da8eSWarner Losh	<reboot>
156ba26da8eSWarner Losh
157ba26da8eSWarner Losh	Make sure that you've read the UPDATING file to understand
158ba26da8eSWarner Losh	the tweaks to various things you need.  At this point in the
159ba26da8eSWarner Losh	life cycloe of current, things change often and you are on
160ba26da8eSWarner Losh	your own to cope.
161ba26da8eSWarner Losh
162dc0dbf5cSWarner LoshFORMAT:
163dc0dbf5cSWarner Losh
1641fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major
1651fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
166f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
167f8ab1dd6SWarner Loshprevious releases if your system is older than this.
1681fc1a0dcSWarner Losh
1693645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
1703645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
171f8c77507SWarner Losh
17297d92980SPeter Wemm$FreeBSD$
173