xref: /freebsd/UPDATING (revision 1dece4a9c59efb44cf9a17b58d56868ef0bbaefb)
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
81dece4a9SWarner Losh20000728:
91dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
101dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
111dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
121dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
131dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
141dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
151dece4a9SWarner Losh	to /MYKERNEL.
161dece4a9SWarner Losh
17409e887cSWarner Losh20000711:
18409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
19409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
20409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
21409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
22409e887cSWarner Losh	for details on potential problems that you might have and how
23409e887cSWarner Losh	to get around them.
24409e887cSWarner Losh
25409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
26409e887cSWarner Losh	clauses above, you needn't worry.
27409e887cSWarner Losh
28409e887cSWarner Losh20000711:
29409e887cSWarner Losh	/etc/security has been updated to print the inode number of
30409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
31409e887cSWarner Losh	in the number of changed programs the first time when you run
32409e887cSWarner Losh	mergemaster to get a new /etc/security.
33409e887cSWarner Losh
34673d13f2SWarner Losh20000710:
35673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
36673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
37673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
38673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
39673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
40673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
41673d13f2SWarner Losh	errors. (see below, 20000624).
42673d13f2SWarner Losh
431dece4a9SWarner Losh	FreESBD-current is safe again to run Crypto.
441dece4a9SWarner Losh
45673d13f2SWarner Losh20000709:
46c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
47c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
48c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
49673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
50673d13f2SWarner Losh
51e98e26cdSWarner Losh20000706:
52e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
53e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
54e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
55e98e26cdSWarner Losh	won't hurt to remove it before the update proceedure.  It will
56e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
57e98e26cdSWarner Losh	interrum if needed.
58e98e26cdSWarner Losh
59e98e26cdSWarner Losh20000705:
60e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
61e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
62e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
63e98e26cdSWarner Losh	details.
64e98e26cdSWarner Losh
65c373950eSWarner Losh20000704:
662f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
672f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
682f961bc8SWarner Losh
692f961bc8SWarner Losh20000704:
70c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
71c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
72c373950eSWarner Losh	rc.d scripts that haven't been updated.
73c373950eSWarner Losh
7427dc3a2bSWarner Losh20000630:
7527dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
7627dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
7727dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
7827dc3a2bSWarner Losh
79b8c215acSWarner Losh20000625:
80b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
8127dc3a2bSWarner Losh	system installed in order to build the system and kernel.
8227dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
8327dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
8427dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
8527dc3a2bSWarner Losh	were required.  You should check with the latest collections
8627dc3a2bSWarner Losh	to make sure that these haven't changed.
87b8c215acSWarner Losh
887b990719SWarner Losh20000624:
897b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
907b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
917b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
927b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
937b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
947b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
957b990719SWarner Losh	date to the completion of the work.
967b990719SWarner Losh
9727dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
9827dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
9927dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
10027dc3a2bSWarner Losh	recreate the random and urandom devices.
10127dc3a2bSWarner Losh
10281e54c50SWarner Losh20000622:
10381e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
10481e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
10581e54c50SWarner Losh	that used to be required when updating.
10681e54c50SWarner Losh
10739943833SWarner Losh20000621:
10839943833SWarner Losh	Scott Flatman <sf@aracnet.com> sent in a decent writeup on
1092a2f33fbSDaniel Baker	the config file update procedure.
1102a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
111c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
112c373950eSWarner Losh	isn't buildable.
11339943833SWarner Losh
114290f9ad8SWarner Losh20000620:
115290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
116290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
117290f9ad8SWarner Losh	that workaround will no longer be required.
118290f9ad8SWarner Losh
11990fb6346SWarner Losh20000615:
12090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
12190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
12290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
12390fb6346SWarner Losh	devices.
12490fb6346SWarner Losh
125f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
126f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
127f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
128f75f65bbSWarner Losh	may work).
129f75f65bbSWarner Losh
130ba26da8eSWarner Losh20000612:
131ba26da8eSWarner Losh	Peter took an axe to config(8).  Besure that you read his mail
132290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
133c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
134290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
135f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
136f54a3542SWarner Losh	NEWCARD for examples of the new format.
137290f9ad8SWarner Losh
138d65850ebSWarner Losh20000522:
139ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
140d65850ebSWarner Losh	building a kernel after this point is advised that they need
141d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
142d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
143d65850ebSWarner Losh
144d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
145d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
146d9583a00SWarner Losh	is recommended that you don't set this option until the problem
147d9583a00SWarner Losh	is resolved.
148d9583a00SWarner Losh
1498039cedeSWarner Losh20000513:
1508039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
1518039cedeSWarner Losh
152d65850ebSWarner Losh20000510:
1538039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
1548039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
1558039cedeSWarner Losh	is requires for the boot blocks to build properly.
1568039cedeSWarner Losh
1578039cedeSWarner Losh20000503:
1588039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
1598039cedeSWarner Losh	is now available.
1608039cedeSWarner Losh
161d65850ebSWarner Losh20000502:
162d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
163d65850ebSWarner Losh	connected to the kernel building instead.
164d65850ebSWarner Losh
1658039cedeSWarner Losh2000427:
1668039cedeSWarner Losh	You may need to build gperf
1678039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
1688039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
1698039cedeSWarner Losh	an option only in -current.
1708039cedeSWarner Losh
1712b8dd5f4SWarner Losh20000417:
1722b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1732b8dd5f4SWarner Losh	acceptible to the binutils maintainers.  You will need to
1742b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
1752b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
1762b8dd5f4SWarner Losh	before you reboot, you'll neeed to issue:
1772b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
1782b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
1792b8dd5f4SWarner Losh
1808d9f1945SWarner Losh20000320:
1812b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
1822b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
1832b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1848d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
1852b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
1868d9f1945SWarner Losh
187f8ab1dd6SWarner Losh20000319:
188f8ab1dd6SWarner Losh	The ISA and PCI compatability shims have been connected to the
189f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
190f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
191f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
192f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
193f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
194f8ab1dd6SWarner Losh
19519cada77SWarner Losh20000318:
19619cada77SWarner Losh	We've entered the tradtional post release dumping party.
19719cada77SWarner Losh	Large kernel changes are being committed and are in the
19819cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
19919cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
20019cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
20119cada77SWarner Losh	that you are loading are up to date.
202ba228352SWarner Losh
20319cada77SWarner Losh20000315:
2046d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
2056d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
2066d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
2076d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
2086d23c382SWarner Losh	boot.
2096d23c382SWarner Losh
2106d23c382SWarner Losh20000315:
21119cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
21219cada77SWarner Losh	to upgrade to 4.0 from 3.x.
21357199806SWarner Losh
214dc0dbf5cSWarner LoshCOMMON ITEMS:
215dc0dbf5cSWarner Losh
216dc0dbf5cSWarner Losh	To build a kernel
217dc0dbf5cSWarner Losh	-----------------
218dc0dbf5cSWarner Losh	Update config, genassym and go:
219ba26da8eSWarner Losh		config YOUR_KERNEL_HERE			[1]
220dc0dbf5cSWarner Losh		cd ../../compile/YOUR_KERNEL_HERE
221dc0dbf5cSWarner Losh		make depend && make
2223645fc1cSWarner Losh		make install
223ba26da8eSWarner Losh	[1] If upgrading, add -r won't hurt and sometimes helps.
224dc0dbf5cSWarner Losh
22516de1a07SWarner Losh	To rebuild everything
22616de1a07SWarner Losh	---------------------
227759f0aefSWarner Losh	make world
228759f0aefSWarner Losh
2291dece4a9SWarner Losh	To upgrade from 4.x-stable to current
230ba26da8eSWarner Losh	-------------------------------------
231ba26da8eSWarner Losh	make buildworld
232ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
233ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
234ba26da8eSWarner Losh	make installworld
235ba26da8eSWarner Losh	<reboot>
236ba26da8eSWarner Losh
237ba26da8eSWarner Losh	Make sure that you've read the UPDATING file to understand
238ba26da8eSWarner Losh	the tweaks to various things you need.  At this point in the
239ba26da8eSWarner Losh	life cycloe of current, things change often and you are on
240ba26da8eSWarner Losh	your own to cope.
241ba26da8eSWarner Losh
2421dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
2431dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
2441dece4a9SWarner Losh	your sources that you have read and understood all the recent
2451dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
2461dece4a9SWarner Losh	much fewer pitfalls.
2471dece4a9SWarner Losh
248dc0dbf5cSWarner LoshFORMAT:
249dc0dbf5cSWarner Losh
2501fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major
2511fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
252f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
253f8ab1dd6SWarner Loshprevious releases if your system is older than this.
2541fc1a0dcSWarner Losh
2553645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
2563645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
257f8c77507SWarner Losh
25897d92980SPeter Wemm$FreeBSD$
259