xref: /freebsd/UPDATING (revision c124fa05676d69e5ba3073c254cceb8fdb134ca3)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh
49698f2c0SWarner Losh<imp@village.org>.  See end of file for further details.  For commonly
59698f2c0SWarner Loshdone items, please see the COMMON ITEMS: section later in the file.
6e72fd46aSWarner Losh
7f59d5f7aSPoul-Henning KampNOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW:
8f59d5f7aSPoul-Henning Kamp	FreeBSD 5.x has many debugging features turned on, in
969f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1069f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1169f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1269f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1369f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
1469f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
1569f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
1669f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
1769f7bcf3SWarner Losh	developers choose to disable these features on build machines
18a19f8ddaSDavid E. O'Brien	to maximize performance.
19c1f61aa9SDavid E. O'Brien
20ce41f4bfSRobert Watson20031213:
21ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
22ce41f4bfSRobert Watson	if the login process is unable to successfully set the
23ce41f4bfSRobert Watson	process credentials to include all groups defined for the
24ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
25ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
26ce41f4bfSRobert Watson	defined, or they will be unable to log in.
27ce41f4bfSRobert Watson
28c124fa05SJohn Baldwin20031203:
29c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
30c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
31c124fa05SJohn Baldwin
328ad1f5e4SHartmut Brandt20031112:
3330093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
3430093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
3597209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
3697209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
3797209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
3897209ca3SRobert Watson	not know about the new system calls that support the new statfs
393f631d52SMarcel Moolenaar	structure.
403f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
413f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
423f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
433f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
443f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
453f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
463f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
473f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
483f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
493f631d52SMarcel Moolenaar	these changes are installed.
5030093b05SWarner Losh
5130093b05SWarner Losh	****************************DANGER*******************************
5230093b05SWarner Losh
5330093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
5430093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
5530093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
5630093b05SWarner Losh	kernel.
5764a18d6fSKirk McKusick
5864a18d6fSKirk McKusick20031112:
598ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
608ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
618ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
628ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
638ad1f5e4SHartmut Brandt	sync before rebooting.
648ad1f5e4SHartmut Brandt
65c53a5d8fSJohn Baldwin20031111:
66c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
67c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
68c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
69c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
70c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
71c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
72c53a5d8fSJohn Baldwin
738bf455a5SJohn Baldwin20031103:
748bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
758bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
762a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
778bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
788bf455a5SJohn Baldwin
799bf40edeSBrooks Davis20031031:
809bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
819bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
829bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
839bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
849bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
859bf40edeSBrooks Davis	reflect this change.
869bf40edeSBrooks Davis
8747a42c7aSPoul-Henning Kamp20030928:
8847a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
8947a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
9047a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
9147a42c7aSPoul-Henning Kamp
9207105342SMax Khon20030926:
9307105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
9407105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
9507105342SMax Khon
9617dcd026SSam Leffler20030925:
9717dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
9817dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
9917dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
10017dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
10117dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
10217dcd026SSam Leffler
103fedf1d01SBruce M Simpson20030923:
104fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
105fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
106fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
107fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
108fedf1d01SBruce M Simpson
109db38f9cbSJacques Vidrine20030915:
110db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
111db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
112db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
113db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
114db38f9cbSJacques Vidrine
115c09d2c2bSMike Makonnen20030829:
116c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
117c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
118c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
119c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
120c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
121c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
122c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
123c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
124c09d2c2bSMike Makonnen	may or may not exist on your system.
125c09d2c2bSMike Makonnen
12617c159dcSSøren Schmidt20030824:
12717c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
12817c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
129f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
130f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
13117c159dcSSøren Schmidt
132c1f61aa9SDavid E. O'Brien20030819:
133c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
134c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
135c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
136c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
13769f7bcf3SWarner Losh
13838c962e7SNate Lawson20030728:
13938c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
14038c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
14138c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
14238c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
14338c962e7SNate Lawson	so the quirk can be re-enabled.
14438c962e7SNate Lawson
145178cf4e9SWarner Losh20030722:
146178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
147178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
148178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
149178cf4e9SWarner Losh	FPU hardware.
150178cf4e9SWarner Losh
151178cf4e9SWarner Losh20030714:
152178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
153178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
154178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
155178cf4e9SWarner Losh	People should report those issues to current@.
156178cf4e9SWarner Losh
157157c629aSWarner Losh20030711:
158157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
1598b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
16005538fa9SWarner Losh	/usr/obj.
161157c629aSWarner Losh
1626cc6353fSMarcel Moolenaar20030613: [retrospective]
1636cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
1646cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
1656cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
1666cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
1676cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
1686cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
1696cc6353fSMarcel Moolenaar
1706cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
1716cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
1726cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
1736cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
1746cc6353fSMarcel Moolenaar		:
1756cc6353fSMarcel Moolenaar
1766cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
1776cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
1786cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
1796cc6353fSMarcel Moolenaar
180766c34e4SAndrey A. Chernov20030610:
181766c34e4SAndrey A. Chernov	Remove deprecated locale names and transition period code
182766c34e4SAndrey A. Chernov	for them, finishing switching to the new scheme. Check your
183766c34e4SAndrey A. Chernov	LANG environment variable.
184766c34e4SAndrey A. Chernov
1857ddc2528SPoul-Henning Kamp20030609:
186df622d54SPoul-Henning Kamp	CCD has been changed to be a fully GEOMified class.  Kernel
187df622d54SPoul-Henning Kamp	and ccdconfig(8) needs to be in sync, this is particularly
188df622d54SPoul-Henning Kamp	important to remember beforehand if your source tree is on
189df622d54SPoul-Henning Kamp	a ccd device.  Consider making a copy of the old ccdconfig
190df622d54SPoul-Henning Kamp	into /boot/kernel.good or wherever you keep your backup
191df622d54SPoul-Henning Kamp	kernel.
192df622d54SPoul-Henning Kamp
19352b47445SMark Murray20030505:
19452b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
19552b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
19652b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
19752b47445SMark Murray
198a26df538SWarner Losh20030502:
199a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
200a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
201a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
202a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
203a26df538SWarner Losh
2044b065e2cSDoug Barton20030501:
2054b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
2064b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
2074b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
2084b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
2094b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
2104b065e2cSDoug Barton	utilizes these old scripts has also been removed.
2114b065e2cSDoug Barton
21281cda3d9SWarner Losh20030423:
21381cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
21481cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
21581cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
21681cda3d9SWarner Losh	have until then to upgrade your kernel before updating
21781cda3d9SWarner Losh	userland.  In general, you should have a userland and
21881cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
21981cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
22081cda3d9SWarner Losh	allowances are made.
22181cda3d9SWarner Losh
22247a657d1SRuslan Ermilov20030329:
22347a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
22447a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
22547a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
22647a657d1SRuslan Ermilov
22747a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
22847a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
22947a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
23047a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
23147a657d1SRuslan Ermilov
23247a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
23347a657d1SRuslan Ermilov	    make cleandir && make obj && \
23447a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
23547a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
23647a657d1SRuslan Ermilov
2375d2af00cSGregory Neil Shapiro20030208:
2385d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
2395d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
2405d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
2415d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
2425d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
2435d2af00cSGregory Neil Shapiro
2445d2af00cSGregory Neil Shapiro20030128:
2459db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
246ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
2479db58771SPoul-Henning Kamp	be removed when convenient.
2489db58771SPoul-Henning Kamp
2498d9b3f57SJake Burkholder20030126:
2508d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
2518d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
2528d9b3f57SJake Burkholder
2531c5efda5SJeff Roberson20030125:
2541c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
2551c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
256ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
2571c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
2581c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
2591c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
2601c5efda5SJeff Roberson
2619d1d64f5SWarner Losh20030115:
2629d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
2639d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
2649d1d64f5SWarner Losh	properly.
2659d1d64f5SWarner Losh
266c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
267c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
268c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
269c9fdb80aSWarner Losh	with NetBSD.
270c9fdb80aSWarner Losh
271161dc364SAlexander Kabaev20021222:
272161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
273161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
274161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
275161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
276161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
277161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
27884cc83efSAlexander Kabaev	rebuilt.
279161dc364SAlexander Kabaev
280fb4c8061SMartin Blapp20021216:
281fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
28289056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
283fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
2849d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
285fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
286fb4c8061SMartin Blapp
28717d47eb3SGiorgos Keramidas20021202:
28817d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
28917d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
29017d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
29117d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
29217d47eb3SGiorgos Keramidas
293a4459294SBill Fenner20021029:
294a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
295a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
296a4459294SBill Fenner	consumers in sync.
297a4459294SBill Fenner
298fc8c157fSWarner Losh20021024:
299c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
300c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
301c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
302c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
303c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
304c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
305c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
306c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
30769f7bcf3SWarner Losh
308fd9e8bdaSAndrew Gallatin20021023:
309fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
310fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
311fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
312fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
313fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
314fd9e8bdaSAndrew Gallatin
315fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
316fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
317fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
318fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
319fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
320fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
321fd9e8bdaSAndrew Gallatin
322f8a4c901SWarner Losh20020831:
323f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
324f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
325f8a4c901SWarner Losh	programs and libraries need to be recompiled.
326f8a4c901SWarner Losh
327f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
328f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
329f8a4c901SWarner Losh
330c2248fa2SJens Schweikhardt20020827:
331c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
332c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
333c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
334c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
335c2248fa2SJens Schweikhardt
3360d533e43SRuslan Ermilov20020815:
3370d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
3380d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
3390d533e43SRuslan Ermilov	again.
3400d533e43SRuslan Ermilov
34133c1de7dSRuslan Ermilov20020729:
34233c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
34333c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
34433c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
34533c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
34633c1de7dSRuslan Ermilov
3472b877facSJulian Elischer20020702:
3482b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
3492b877facSJulian Elischer	There are still some minor problems with some signals but the
3502b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
3512b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
3522b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
3532b877facSJulian Elischer
35406596d37SWarner Losh20020701:
35506596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
35606596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
35706596d37SWarner Losh	GNOME.
35806596d37SWarner Losh
35995ba4330SJacques Vidrine20020511:
36095ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
36195ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
36295ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
36395ba4330SJacques Vidrine	with the set-user-ID bit set.
36495ba4330SJacques Vidrine
365a81da3c9SDavid E. O'Brien20020510:
366f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
367f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
3684b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
369f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
370f50caf6fSDavid E. O'Brien
371f50caf6fSDavid E. O'Brien20020510:
372a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
373a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
374a81da3c9SDavid E. O'Brien	and then do a cvs update.
375a81da3c9SDavid E. O'Brien
376528a0ef5SJacques Vidrine20020421:
377528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
378528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
379528a0ef5SJacques Vidrine
38085aa5a2eSGregory Neil Shapiro20020404:
38185aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
38285aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
38385aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
38485aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
38585aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
38685aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
38785aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
38885aa5a2eSGregory Neil Shapiro
3898f1e4358SRuslan Ermilov20020403:
3908f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
3918f1e4358SRuslan Ermilov
3922292c02eSWarner Losh20020315:
3932292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
3942292c02eSWarner Losh
39569f7bcf3SWarner Losh20020225:
39669f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
39769f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
39869f7bcf3SWarner Losh
3998f35c493SWarner Losh20020217:
4008f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
4018f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
4028f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
4038f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
4048f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
4058f35c493SWarner Losh
406835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
407835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
408835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
409835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
410835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
411835284beSWarner Losh	and group must be merged from src/etc/group and
412835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
413835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
414835284beSWarner Losh	mergemaster before this will work if you are updating from a
415835284beSWarner Losh	very old version of current.  The updating recipe has changed
416835284beSWarner Losh	as of this date.
417835284beSWarner Losh
418fa9401c1SWarner Losh20020112:
419fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
420fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
421fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
422fa9401c1SWarner Losh	you have local modifications, you can use
423fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
424fa9401c1SWarner Losh	/etc/pam.d.
425fa9401c1SWarner Losh
426fa9401c1SWarner Losh	Please see the following url for more details:
427fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
42847d0d01fSWarner Losh20011229:
42947d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
43047d0d01fSWarner Losh	networkfs_types, please note that it has changed
43147d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
43247d0d01fSWarner Losh
433514318a8SWarner Losh20011220:
434514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
435514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
436514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
437514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
438514318a8SWarner Losh	version have now been merged back into the base system's
439514318a8SWarner Losh	version now.  The only user-visible change resulting from this
440514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
441514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
442514318a8SWarner Losh	as well.  (There has never been rc file support for
443514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
444514318a8SWarner Losh	reverted by the time the changes are MFCed.)
445514318a8SWarner Losh
446514318a8SWarner Losh20011215:
447514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
448514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
449514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
450514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
451514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
452514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
453514318a8SWarner Losh	will need to be customized then for `odd' densities using
454514318a8SWarner Losh	fdcontrol(8).
455514318a8SWarner Losh
4562d22e2bfSWarner Losh20011209:
4572d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
4582d22e2bfSWarner Losh	and truss(1) now works again.
4592d22e2bfSWarner Losh
4609e0428e2SWarner Losh20011207:
4619e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
4629e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
4639e0428e2SWarner Losh	see
4649e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
4659e0428e2SWarner Losh	for details.
4669e0428e2SWarner Losh
4679bab8c59SWarner Losh20011204:
4689bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
4699bab8c59SWarner Losh	kernel and burncd to be in sync.
4709bab8c59SWarner Losh
471e57d8b01SWarner Losh20011203:
472e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
473e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
474e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
475e57d8b01SWarner Losh	not there already.
476e57d8b01SWarner Losh
477e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
478e57d8b01SWarner Losh	until the issue has been resolved.
479e57d8b01SWarner Losh
480b001d36fSJacques Vidrine20011202:
481b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
482b001d36fSJacques Vidrine	patched.
483b001d36fSJacques Vidrine
4844b676ec1SWarner Losh20011126:
4854b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
4865ebbf43eSWarner Losh	after this date.  You need to do this only once.
4874b676ec1SWarner Losh
488d961e462SWarner Losh20011103:
489d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
490d961e462SWarner Losh	edges may be left, but for the most part things should be
4914b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
492d961e462SWarner Losh
493d961e462SWarner Losh20011030:
494d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
495d961e462SWarner Losh	choppy waves in the upgrade process.
496d961e462SWarner Losh
4971fe003b6SWarner Losh20011030:
498a4b6fda0SWarner Losh	The asr driver problem has been resolved.
4991fe003b6SWarner Losh
5001fe003b6SWarner Losh20011027:
5011fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
5021fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
5031fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
5041fe003b6SWarner Losh	try to use from this date forward.
5051fe003b6SWarner Losh
5061fe003b6SWarner Losh20011025:
5071fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
5081fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
5091fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
5101fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
5111fe003b6SWarner Losh	TARGET_ARCH=i386.
5121fe003b6SWarner Losh
513d05f9643SWarner Losh20011001:
514d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
515d05f9643SWarner Losh	You must recompile both the kernel and userland applications
516d05f9643SWarner Losh	at the same time.
517d05f9643SWarner Losh
51858970f85SWarner Losh20010929:
51958970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
52058970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
52158970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
52258970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
5239d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
52458970f85SWarner Losh
52558970f85SWarner Losh20010927:
52658970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
52758970f85SWarner Losh	To disable ACPI you can add
52866ff0e67SMax Khon		hint.acpi.0.disabled="1"
52958970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
53058970f85SWarner Losh	loader "ok" prompt).
53158970f85SWarner Losh
53258970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
53358970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
53458970f85SWarner Losh	file and not list acpi in that list.
535378f4486SAlfred Perlstein
5365119d237SWarner Losh20010924:
5375119d237SWarner Losh	The buildworld has been fixed.  You may need to install
5385119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
5398b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
5408b039fffSWarner Losh	get them installed on every installworld, or execute the
5418b039fffSWarner Losh	following to get them installed only once:
5428b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
54358970f85SWarner Losh		make all install
5448b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
5455119d237SWarner Losh
5463c293725SWarner Losh20010919:
5473c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
5483c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
5493c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
550772730c7SWarner Losh	workaround is to add
5513c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
5523c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
5533c293725SWarner Losh	can be removed afterwards.
5543c293725SWarner Losh
5553c293725SWarner Losh	A proper fix to the buildworld target is needed.
5563c293725SWarner Losh
5573c293725SWarner Losh20010918:
5583c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
5593c293725SWarner Losh	NFS may be unstable after this date.
5603c293725SWarner Losh
5613c293725SWarner Losh20010912:
5623c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
5633c293725SWarner Losh	the kernel.  While a few problems were introduced in the
5643c293725SWarner Losh	initial commit, most of the major ones have been found and
5653c293725SWarner Losh	corrected.
5663c293725SWarner Losh
5673c293725SWarner Losh20010901:
5683c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
5693c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
5703c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
5713c293725SWarner Losh	have been rectified around this date.
5723c293725SWarner Losh
57398b17b95SWarner Losh20010823:
57498b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
57598b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
57698b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
57798b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
57898b17b95SWarner Losh 	sure that user or group bind has read (and not write)
57998b17b95SWarner Losh 	permission for your name server configuration and that it
58098b17b95SWarner Losh 	has read and write permission for your slave zone files and
58198b17b95SWarner Losh 	directory.
58298b17b95SWarner Losh
58398b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
58498b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
58598b17b95SWarner Losh
58698b17b95SWarner Losh 		named_flags=
58798b17b95SWarner Losh
5887b9786edSMark Murray20010709:
5897b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
5907b9786edSMark Murray	the ability of the shared library major number to handle.
5917b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
5927b9786edSMark Murray	solution is to rebuild those ports.
5937b9786edSMark Murray
5941d28950eSWarner Losh20010628:
5951d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
5961d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
5971d28950eSWarner Losh
598e72fd46aSWarner Losh20010625:
59998b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
60098b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
60198b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
60298b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
60398b17b95SWarner Losh	IRQ configuration needs more safety belts.
60416de1a07SWarner Losh
6050d415dffSWarner Losh20010617:
606e72fd46aSWarner Losh	Softupdates problems have been corrected.
6070d415dffSWarner Losh
6080d415dffSWarner Losh20010614:
6090d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
6100d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
6110d415dffSWarner Losh	kernel building methods.
6120d415dffSWarner Losh
6138b9959adSWarner Losh20010613:
6148b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
6158b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
616e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
617e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
6188b9959adSWarner Losh
619e72fd46aSWarner Losh20010613:
6208b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
621e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
622e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
6238b9959adSWarner Losh
6240d415dffSWarner Losh20010612:
6250d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
6260d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
6270d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
6280d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
6290d415dffSWarner Losh	until this bug is fixed.
6300d415dffSWarner Losh
631e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
632e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
633ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
634e72fd46aSWarner Losh
6350d415dffSWarner Losh20010610:
6360d415dffSWarner Losh	Locale names have changed to match other systems better.
6370d415dffSWarner Losh
6386ccdb5e4SWarner Losh20010604:
6396ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
6406ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
6416ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
6423590182eSWarner Losh	Interrupt storms look a lot like a hang.
6433590182eSWarner Losh
6443590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
6453590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
6463590182eSWarner Losh	it is).
6473590182eSWarner Losh
6483590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
6493590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
6503590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
6513590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
6526ccdb5e4SWarner Losh
6530bc62786SWarner Losh20010530:
6540bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
6550bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
6560bc62786SWarner Losh	a limited time.  If you see
6570bc62786SWarner Losh
6580bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
6590bc62786SWarner Losh
6600bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
6610bc62786SWarner Losh	COPY=-C.
6620bc62786SWarner Losh
66368a38c6cSWarner Losh20010525:
664b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
665c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
666c4f4a728SWarner Losh	definitely is in bad shape.
66768a38c6cSWarner Losh
668ed0f29caSWarner Losh20010521:
669ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
670ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
671ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
672ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
673ed0f29caSWarner Losh	is
674ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
675ed0f29caSWarner Losh
67680c16af9SWarner Losh20010520:
67768a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
67880c16af9SWarner Losh
67980c16af9SWarner Losh20010519:
68080c16af9SWarner Losh	pccard has had much reorganizational work done to it over
68180c16af9SWarner Losh	the past few days.  Everything should still work, but if
68280c16af9SWarner Losh	not, please contact imp@freebsd.org.
68380c16af9SWarner Losh
684a45f2d05SWarner Losh20010517:
685a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
686a45f2d05SWarner Losh	userland at the same time.
687a45f2d05SWarner Losh
688a45f2d05SWarner Losh20010517:
689a45f2d05SWarner Losh	New ncurses imported.
690a45f2d05SWarner Losh
6912988afcaSWarner Losh20010512:
6922988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
6932988afcaSWarner Losh	will be the only way to go starting July 1.
6942988afcaSWarner Losh
6951a33dba7SWarner Losh20010504:
6961a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
6971a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
6981a33dba7SWarner Losh
69909946a51SWarner Losh20010502:
70009946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
70109946a51SWarner Losh
70209946a51SWarner Losh20010501:
70309946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
70409946a51SWarner Losh
70509946a51SWarner Losh20010430:
706a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
70709946a51SWarner Losh	go back in the water.
70809946a51SWarner Losh
70909946a51SWarner Losh20010429:
71009946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
71109946a51SWarner Losh	this date, but before the correction date.
71209946a51SWarner Losh
71391dd3b53SWarner Losh20010423:
71491dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
71591dd3b53SWarner Losh
71691dd3b53SWarner Losh20010411:
71791dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
71891dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
71991dd3b53SWarner Losh	Update only if you understand that you must not use the old
72091dd3b53SWarner Losh	fsck with the new kernel ever.
72191dd3b53SWarner Losh
722933b3269SWarner Losh20010330:
723933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
724c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
725933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
726933b3269SWarner Losh
727933b3269SWarner Losh20010319:
728933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
729933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
730933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
731f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
73209946a51SWarner Losh
73309946a51SWarner Losh20010315:
73409946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
735ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
73609946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
737933b3269SWarner Losh
738933b3269SWarner Losh20010312:
739933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
740933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
741933b3269SWarner Losh
742933b3269SWarner Losh20010312:
743933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
744933b3269SWarner Losh	instead of ad-hoc.
745933b3269SWarner Losh
746933b3269SWarner Losh20010310:
747f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
748933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
749933b3269SWarner Losh	ssh might not work if you don't.
750933b3269SWarner Losh
75162353691SWarner Losh20010303:
75262353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
75362353691SWarner Losh	which means that you must include the miibus in your kernel if
75462353691SWarner Losh	you use the ed driver.
75562353691SWarner Losh
756d325cf65SWarner Losh20010220:
757d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
758d325cf65SWarner Losh	safe to go back into the water.
759d325cf65SWarner Losh
760024daae6SWarner Losh20010211:
761024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
762024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
763024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
764024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
765024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
766024daae6SWarner Losh
767024daae6SWarner Losh	To get to the new system, you'll need to use the following
768024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
769024daae6SWarner Losh	don't have to move this to the updating section.
770024daae6SWarner Losh
771024daae6SWarner Losh	To get around the installworld problem, do:
772024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
773024daae6SWarner Losh		# make install
774024daae6SWarner Losh		# cd /usr/src
775024daae6SWarner Losh		# make installworld
776024daae6SWarner Losh	If that doesn't work, then try:
777024daae6SWarner Losh		# make -k installworld
778024daae6SWarner Losh		# make installworld
779024daae6SWarner Losh
780024daae6SWarner Losh20010207:
781024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
782024daae6SWarner Losh	do not include devfs in your kernel as problems result.
783024daae6SWarner Losh
784024daae6SWarner Losh20010205:
7857595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
786024daae6SWarner Losh	Remove them from your config.
787024daae6SWarner Losh
7881e159248SWarner Losh20010122:
7891e159248SWarner Losh	****************************** WARNING ******************************
7901e159248SWarner Losh			buildkernel has been changed slightly
7911e159248SWarner Losh	****************************** WARNING ******************************
7921e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
7931e159248SWarner Losh	should update your scripts and make.conf accordingly.
7941e159248SWarner Losh
7951e159248SWarner Losh20010119:
7961e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
7971e159248SWarner Losh	This requires a new config to build correctly.
7981e159248SWarner Losh
799aac7dfeaSWarner Losh20010116:
800ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
801aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
802aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
803aac7dfeaSWarner Losh
804aac7dfeaSWarner Losh20010110:
805aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
806aac7dfeaSWarner Losh
807aac7dfeaSWarner Losh20010102:
808aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
809aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
810aac7dfeaSWarner Losh
81163c90c9eSWarner Losh20010101:
81263c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
81363c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
8145fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
81563c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
81663c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
81763c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
81863c90c9eSWarner Losh	might have been ignored by the -k option.
81963c90c9eSWarner Losh
8205fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
8215fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
8225fd2a895SWarner Losh	of this working.
8235fd2a895SWarner Losh
824aac7dfeaSWarner Losh20001228:
825aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
826ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
827aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
828aac7dfeaSWarner Losh
829de2bcc63SWarner Losh20001218:
830de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
831de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
832de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
833de2bcc63SWarner Losh	cards will not be recognized without it.
834de2bcc63SWarner Losh
835960773f7SWarner Losh20001205:
836960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
837960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
838960773f7SWarner Losh	adding the following in pam.conf:
839960773f7SWarner Losh
840960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
841960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
842960773f7SWarner Losh	sshd    session required        pam_permit.so
843960773f7SWarner Losh
8440acc635eSWarner Losh20001031:
8450acc635eSWarner Losh	cvs updated to 1.11.
8460acc635eSWarner Losh
8470acc635eSWarner Losh20001020:
8480acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
8490acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
8500acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
8510acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
8520acc635eSWarner Losh	workaround.
8530acc635eSWarner Losh
8540acc635eSWarner Losh20001010:
8550acc635eSWarner Losh	****************************** WARNING ******************************
8560acc635eSWarner Losh				Sendmail has been updated.
8570acc635eSWarner Losh	****************************** WARNING ******************************
8580acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
8590acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
8600acc635eSWarner Losh	  is set.
8610acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
8620acc635eSWarner Losh	  commands.
8630acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
8640acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
8650acc635eSWarner Losh	  in /usr/share/sendmail/cf.
8660acc635eSWarner Losh	o sendmail.cw changed to local-host-names
8670acc635eSWarner Losh
8680acc635eSWarner Losh	More details can be found at
8690acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
8700acc635eSWarner Losh
8716e98a146SWarner Losh20001009:
8726e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
8736e98a146SWarner Losh	your entire ports tree, or you will have problems.
8746e98a146SWarner Losh
8756e98a146SWarner Losh20001006:
876685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
8776e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
8786e98a146SWarner Losh	/usr/bin/miniperl.
8796e98a146SWarner Losh
880073113a4SWarner Losh20001005:
881073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
882685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
883073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
884073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
885073113a4SWarner Losh	tree for anything to work.
886073113a4SWarner Losh
8870acc635eSWarner Losh20000928:
8880acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
8890acc635eSWarner Losh
890be3885b3SWarner Losh20000916:
891be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
892be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
893be3885b3SWarner Losh	same time as your kernel.
894be3885b3SWarner Losh
89576ec9675SWarner Losh20000914:
89676ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
89776ec9675SWarner Losh	include the device will cause suspended laptops losing time
89876ec9675SWarner Losh	when they resume.  Include
89976ec9675SWarner Losh		device		pmtimer
90076ec9675SWarner Losh	in your config file and
90101b9a434SWarner Losh		hint.pmtimer.0.at="isa"
90276ec9675SWarner Losh	to your /boot/device.hints file.
90376ec9675SWarner Losh
904f4865386SMark Murray20000911:
905f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
906f4865386SMark Murray	rather than an option. The supplied kernel config files have
907f4865386SMark Murray	been updated. You will need to do something similar in your
908f4865386SMark Murray	own kernel config file.
909f4865386SMark Murray	Remove:
910f4865386SMark Murray		options		RANDOMDEV
911f4865386SMark Murray	Add:
912f4865386SMark Murray		device		random
913f4865386SMark Murray	If you prefer to load the loadable module, you need to do
914f4865386SMark Murray	nothing.
915f4865386SMark Murray
916d594498fSWarner Losh20000909:
917d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
918d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
919d594498fSWarner Losh	reflect this if you load this module at boot time.
920d594498fSWarner Losh	The line should read:
921d594498fSWarner Losh		random_load="YES"
922d594498fSWarner Losh
9230deb7ddcSWarner Losh20000907:
9240deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
92516eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
92616eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
92716eb772dSWarner Losh	sure you don't have model loading problems which might at
92816eb772dSWarner Losh	first blush appear related to SMP.
92952bf24e7SWarner Losh
9305a01880bSWarner Losh20000906:
9315a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
9325a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
9335a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
9345a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
9355a01880bSWarner Losh	don't have one, and you have host.conf.
9365a01880bSWarner Losh
9372b41163cSWarner Losh20000905:
93838d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
93938d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
94038d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
94138d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
94238d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
94338d6ecd2SWarner Losh
94438d6ecd2SWarner Losh20000905:
9458aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
9468aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
9478aab4bc7SWarner Losh	is /boot/kernel.
9488aab4bc7SWarner Losh
9498aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
95038d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
95138d6ecd2SWarner Losh	installkernel/installworld dance.
9522b41163cSWarner Losh
953d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
954d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
955d594498fSWarner Losh	modules in that directory instead of finding them in the correct
956d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
957d594498fSWarner Losh	is that the linux module crashes your machine after the update.
958d594498fSWarner Losh
959d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
960d594498fSWarner Losh		mv /modules.old /boot/kernel.old
961d594498fSWarner Losh		chflags noschg /kernel.old
962d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
963d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
964d594498fSWarner Losh	fi
965d594498fSWarner Losh
966c22a309cSWarner Losh20000904:
967c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
968c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
969c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
970c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
971c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
972c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
973c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
974c22a309cSWarner Losh	is not likely to be generated.
975c22a309cSWarner Losh
976fdb9f54dSWarner Losh20000825:
977fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
9789c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
9799c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
9809c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
9819c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
9829c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
9839c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
9849c1a7444SWarner Losh	kernel.
9859c1a7444SWarner Losh
9869c1a7444SWarner Losh20000821:
9879c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
9889c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
9899c1a7444SWarner Losh	/boot/loader.conf.
990fdb9f54dSWarner Losh
9918f250aa7SWarner Losh20000812:
9925da0d091SWarner Losh	suidperl is now always built and installed on the system, but
9935da0d091SWarner Losh	with permissions of 511.  If you have applications that use
9945da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
9955da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
9965da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
9975da0d091SWarner Losh	will fix this until the next build.
9985da0d091SWarner Losh
9995da0d091SWarner Losh20000812:
10008f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
10018f250aa7SWarner Losh	visible changes that may immediately affect your configuration
10028f250aa7SWarner Losh	include:
10038f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
10048f250aa7SWarner Losh	- newaliases limited to root and trusted users
10058f250aa7SWarner Losh	- MSA port (587) turned on by default
10068f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
10078f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
10088f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
10098f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
10108f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
10118f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
10128f250aa7SWarner Losh
101371c38472SWarner Losh20000810:
101471c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
101571c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
101671c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
101771c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
101871c38472SWarner Losh	specific use for it.
101971c38472SWarner Losh
102071c38472SWarner Losh20000729:
102171c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
102271c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
102371c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
102471c38472SWarner Losh	afterwards (unless the variables already are set, of course):
102571c38472SWarner Losh		# Enable network daemons for user convenience.
102671c38472SWarner Losh		inetd_enable="YES"
102771c38472SWarner Losh		portmap_enable="YES"
102871c38472SWarner Losh		sendmail_enable="YES"
102971c38472SWarner Losh
103071c38472SWarner Losh20000728:
103171c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
103271c38472SWarner Losh	will need to change that to nullfs_load="YES".
103371c38472SWarner Losh
10341dece4a9SWarner Losh20000728:
10351dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
10361dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
10371dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
10381dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
10391dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
10401dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
10411dece4a9SWarner Losh	to /MYKERNEL.
10421dece4a9SWarner Losh
1043409e887cSWarner Losh20000711:
1044409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1045409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1046409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1047409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1048409e887cSWarner Losh	for details on potential problems that you might have and how
1049409e887cSWarner Losh	to get around them.
1050409e887cSWarner Losh
1051409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1052409e887cSWarner Losh	clauses above, you needn't worry.
1053409e887cSWarner Losh
1054409e887cSWarner Losh20000711:
1055409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1056409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1057409e887cSWarner Losh	in the number of changed programs the first time when you run
1058409e887cSWarner Losh	mergemaster to get a new /etc/security.
1059409e887cSWarner Losh
1060673d13f2SWarner Losh20000710:
1061673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1062673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1063673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1064673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1065673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1066673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1067673d13f2SWarner Losh	errors. (see below, 20000624).
1068673d13f2SWarner Losh
1069bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
10701dece4a9SWarner Losh
1071673d13f2SWarner Losh20000709:
1072c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1073c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1074c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1075673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1076673d13f2SWarner Losh
1077e98e26cdSWarner Losh20000706:
1078e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1079e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1080e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1081f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1082e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
10832c021c6cSMark Ovens	interim if needed.
1084e98e26cdSWarner Losh
1085e98e26cdSWarner Losh20000705:
1086e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1087e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1088e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1089e98e26cdSWarner Losh	details.
1090e98e26cdSWarner Losh
1091c373950eSWarner Losh20000704:
10922f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
10932f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
10942f961bc8SWarner Losh
10952f961bc8SWarner Losh20000704:
1096c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1097c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1098c373950eSWarner Losh	rc.d scripts that haven't been updated.
1099c373950eSWarner Losh
110027dc3a2bSWarner Losh20000630:
110127dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
110227dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
110327dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
110427dc3a2bSWarner Losh
1105b8c215acSWarner Losh20000625:
1106b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
110727dc3a2bSWarner Losh	system installed in order to build the system and kernel.
110827dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
110927dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
111027dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
111127dc3a2bSWarner Losh	were required.  You should check with the latest collections
111227dc3a2bSWarner Losh	to make sure that these haven't changed.
1113b8c215acSWarner Losh
11147b990719SWarner Losh20000624:
11157b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
11167b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
11177b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
11181a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
11197b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
11207b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
11217b990719SWarner Losh	date to the completion of the work.
11227b990719SWarner Losh
112327dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
112427dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
112527dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
112627dc3a2bSWarner Losh	recreate the random and urandom devices.
112727dc3a2bSWarner Losh
112881e54c50SWarner Losh20000622:
112981e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
113081e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
113181e54c50SWarner Losh	that used to be required when updating.
113281e54c50SWarner Losh
113339943833SWarner Losh20000621:
11342c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
11352a2f33fbSDaniel Baker	the config file update procedure.
11362a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1137c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
113859df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
113959df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
114039943833SWarner Losh
1141290f9ad8SWarner Losh20000620:
1142290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1143290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1144290f9ad8SWarner Losh	that workaround will no longer be required.
1145290f9ad8SWarner Losh
114690fb6346SWarner Losh20000615:
114790fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
114890fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
114990fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
115090fb6346SWarner Losh	devices.
115190fb6346SWarner Losh
1152f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1153f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1154f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1155f75f65bbSWarner Losh	may work).
1156f75f65bbSWarner Losh
1157ba26da8eSWarner Losh20000612:
1158ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1159290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1160c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1161290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1162f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1163f54a3542SWarner Losh	NEWCARD for examples of the new format.
1164290f9ad8SWarner Losh
11659698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
11669698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
11679698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
11689698f2c0SWarner Losh	in it.
1169bbcc5149SWarner Losh
1170d65850ebSWarner Losh20000522:
1171ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1172d65850ebSWarner Losh	building a kernel after this point is advised that they need
1173d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1174d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1175d65850ebSWarner Losh
1176d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1177d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1178d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1179d9583a00SWarner Losh	is resolved.
1180d9583a00SWarner Losh
11818039cedeSWarner Losh20000513:
11828039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
11838039cedeSWarner Losh
1184d65850ebSWarner Losh20000510:
11858039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
11868039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
11878039cedeSWarner Losh	is requires for the boot blocks to build properly.
11888039cedeSWarner Losh
11898039cedeSWarner Losh20000503:
11908039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
11918039cedeSWarner Losh	is now available.
11928039cedeSWarner Losh
1193d65850ebSWarner Losh20000502:
1194d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1195d65850ebSWarner Losh	connected to the kernel building instead.
1196d65850ebSWarner Losh
1197be149406SNik Clayton20000427:
11988039cedeSWarner Losh	You may need to build gperf
11998039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
12008039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
12018039cedeSWarner Losh	an option only in -current.
12028039cedeSWarner Losh
12032b8dd5f4SWarner Losh20000417:
12042b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1205f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
12062b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
12072b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
12082c021c6cSMark Ovens	before you reboot, you'll need to issue:
12092b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
12102b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
12112b8dd5f4SWarner Losh
12128d9f1945SWarner Losh20000320:
12132b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
12142b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
12152b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1216ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
12172b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
12188d9f1945SWarner Losh
1219f8ab1dd6SWarner Losh20000319:
1220f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1221f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1222f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1223f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1224f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1225f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1226f8ab1dd6SWarner Losh
122719cada77SWarner Losh20000318:
1228f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
122919cada77SWarner Losh	Large kernel changes are being committed and are in the
123019cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
123119cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
123219cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
123319cada77SWarner Losh	that you are loading are up to date.
1234ba228352SWarner Losh
123519cada77SWarner Losh20000315:
12366d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
12376d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
12386d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
12396d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
12406d23c382SWarner Losh	boot.
12416d23c382SWarner Losh
12426d23c382SWarner Losh20000315:
124319cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
124419cada77SWarner Losh	to upgrade to 4.0 from 3.x.
124557199806SWarner Losh
1246dc0dbf5cSWarner LoshCOMMON ITEMS:
1247dc0dbf5cSWarner Losh
1248a24eff53SWarner Losh	General Notes
1249a24eff53SWarner Losh	-------------
1250a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1251a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1252a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1253a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1254a24eff53SWarner Losh	or several minor releases, or when several months have passed
1255a24eff53SWarner Losh	on the -current branch).
1256a24eff53SWarner Losh
12575780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
12585780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
12595780f3baSWarner Losh	environment when searching for values for global variables.
12605780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
12615780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
12625780f3baSWarner Losh	page for more details.
12635780f3baSWarner Losh
1264dc0dbf5cSWarner Losh	To build a kernel
1265dc0dbf5cSWarner Losh	-----------------
1266ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1267f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1268ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1269282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1270282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1271dc0dbf5cSWarner Losh
1272ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1273ba01eb20SWarner Losh	--------------------------------------------------------------
1274ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
127547d0d01fSWarner Losh	config KERNEL_NAME_HERE
1276ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1277ba01eb20SWarner Losh	make depend
1278ba01eb20SWarner Losh	make
1279ba01eb20SWarner Losh	make install
1280ba01eb20SWarner Losh
1281ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1282ba01eb20SWarner Losh
1283ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1284ba01eb20SWarner Losh	-----------------------------------------------------------
128563cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
128663cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
128763cb445eSWarner Losh
1288f643de42SWarner Losh	<make sure you have good level 0 dumps>
128963cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
129063cb445eSWarner Losh	make buildworld
129163cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
129263cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
129363cb445eSWarner Losh							[1]
129463cb445eSWarner Losh	<reboot in single user>				[3]
129563cb445eSWarner Losh	mergemaster -p					[5]
129663cb445eSWarner Losh	make installworld
129763cb445eSWarner Losh	mergemaster					[4]
129863cb445eSWarner Losh	<reboot>
129963cb445eSWarner Losh
1300759f0aefSWarner Losh
1301f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1302f27b1fceSJoseph Koshy	--------------------------------------------------
1303f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1304f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1305f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1306f27b1fceSJoseph Koshy	# size.
1307f27b1fceSJoseph Koshy
1308f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1309f27b1fceSJoseph Koshy	<boot into -stable>
1310f27b1fceSJoseph Koshy	make buildworld
1311f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1312f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1313f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1314f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1315f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1316f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1317f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1318f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1319f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1320f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1321f27b1fceSJoseph Koshy	<reboot into current>
1322f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1323f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1324f27b1fceSJoseph Koshy 	<reboot>
1325f27b1fceSJoseph Koshy
1326f27b1fceSJoseph Koshy
1327f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1328f27b1fceSJoseph Koshy	----------------------------------------------
13295c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
13305c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
13315c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
13325c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1333ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1334f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1335f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1336f643de42SWarner Losh	# space on /.
1337f643de42SWarner Losh
1338f643de42SWarner Losh	<make sure you have good level 0 dumps>
1339fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
134021c075eaSWarner Losh	make buildworld					[9]
1341c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1342d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1343be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1344fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1345fc8c157fSWarner Losh							[1]
1346fc8c157fSWarner Losh	<reboot in single user>				[3]
1347835284beSWarner Losh	mergemaster -p					[5]
1348f8a4c901SWarner Losh	rm -rf /usr/include/g++
1349ba26da8eSWarner Losh	make installworld
1350a6cd4f9dSWarner Losh	mergemaster					[4]
1351ba26da8eSWarner Losh	<reboot>
1352ba26da8eSWarner Losh
1353fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1354fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1355fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1356fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1357fdb9f54dSWarner Losh	the UPDATING entries.
1358ba26da8eSWarner Losh
13591dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
13601dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
13611dece4a9SWarner Losh	your sources that you have read and understood all the recent
13621dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
13631dece4a9SWarner Losh	much fewer pitfalls.
13641dece4a9SWarner Losh
1365134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1366134d2e86SWarner Losh	should disable them at this point so they don't crash your
1367134d2e86SWarner Losh	system on reboot.
1368134d2e86SWarner Losh
13699c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
13709c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
13719c1a7444SWarner Losh	configuration.
13729c1a7444SWarner Losh
1373ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1374ee6e1fc3SWarner Losh		fsck -p
1375ee6e1fc3SWarner Losh		mount -u /
1376ee6e1fc3SWarner Losh		mount -a
1377ee6e1fc3SWarner Losh		cd /usr/src
137847d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1379f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1380f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1381b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1382b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1383b705ae10SWarner Losh	be ignored while you proceed to the next step.
1384ee6e1fc3SWarner Losh
1385a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1386a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1387a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1388a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1389a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1390a6cd4f9dSWarner Losh	for potential gotchas.
1391a6cd4f9dSWarner Losh
1392835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1393835284beSWarner Losh	you may need to do this if you get unknown user in the following
1394835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1395835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1396835284beSWarner Losh	install) after the buildworld before this step if you last updated
1397835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1398835284beSWarner Losh
1399bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1400bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1401bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1402bd79cf40SWarner Losh		ok unload
1403bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1404bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1405bd79cf40SWarner Losh	described here.
1406fc8c157fSWarner Losh
1407fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1408fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1409fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1410fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1411fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1412fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1413fc8c157fSWarner Losh
1414c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1415c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1416c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1417c74fe6afSWarner Losh	that is hard to boot to recover.
1418c74fe6afSWarner Losh
141921c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
142021c075eaSWarner Losh	cvs prune empty directories.
1421dc0dbf5cSWarner LoshFORMAT:
1422dc0dbf5cSWarner Losh
1423f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
14241fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1425f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1426f8ab1dd6SWarner Loshprevious releases if your system is older than this.
14271fc1a0dcSWarner Losh
1428e72fd46aSWarner LoshCopyright information:
1429e72fd46aSWarner Losh
14309698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1431e72fd46aSWarner Losh
1432772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1433772730c7SWarner Loshmodification, in full or in part, in any form or format of this
14349698f2c0SWarner Loshdocument are permitted without further permission from the author.
1435e72fd46aSWarner Losh
1436e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1437e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1438e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1439e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1440e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1441e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1442e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1443e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1444e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1445e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1446e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1447e72fd46aSWarner Losh
1448e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1449e72fd46aSWarner Loshauthor a beer.
1450e72fd46aSWarner Losh
145122306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1452772730c7SWarner Loshthis document.
1453772730c7SWarner Losh
145497d92980SPeter Wemm$FreeBSD$
1455