xref: /freebsd/UPDATING (revision 158b90da674e851c83645180b56f58169781114e)
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
20158b90daSWarner Losh20040222:
21158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
22158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
23158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
24158b90daSWarner Losh	Drivers outside the tree will need to be updated.
25158b90daSWarner Losh
26b7b1e150SMike Makonnen20040207:
27b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
28b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
29b7b1e150SMike Makonnen
30aca89ee6SDaniel Eischen20040130:
31aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
32aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
33aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
34aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
35aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
36aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
37aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
38aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
39aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
40aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
41aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
42aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
43aca89ee6SDaniel Eischen	do not work with libpthread.
44aca89ee6SDaniel Eischen
4568b7b3a9SAlex Dupre20040125:
4668b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
4768b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
4868b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
4968b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
5068b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
5168b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
5268b7b3a9SAlex Dupre
53ff46e0deSWarner Losh20040125:
54ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
55ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
56ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
57ff46e0deSWarner Losh
58ce41f4bfSRobert Watson20031213:
59ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
60ce41f4bfSRobert Watson	if the login process is unable to successfully set the
61ce41f4bfSRobert Watson	process credentials to include all groups defined for the
62ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
63ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
64ce41f4bfSRobert Watson	defined, or they will be unable to log in.
65ce41f4bfSRobert Watson
66c124fa05SJohn Baldwin20031203:
67c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
68c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
69c124fa05SJohn Baldwin
708ad1f5e4SHartmut Brandt20031112:
7130093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
7230093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
7397209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
7497209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
7597209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
7697209ca3SRobert Watson	not know about the new system calls that support the new statfs
773f631d52SMarcel Moolenaar	structure.
783f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
793f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
803f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
813f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
823f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
833f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
843f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
853f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
863f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
873f631d52SMarcel Moolenaar	these changes are installed.
8830093b05SWarner Losh
8930093b05SWarner Losh	****************************DANGER*******************************
9030093b05SWarner Losh
9130093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
9230093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
9330093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
9430093b05SWarner Losh	kernel.
9564a18d6fSKirk McKusick
9664a18d6fSKirk McKusick20031112:
978ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
988ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
998ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
1008ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
1018ad1f5e4SHartmut Brandt	sync before rebooting.
1028ad1f5e4SHartmut Brandt
103c53a5d8fSJohn Baldwin20031111:
104c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
105c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
106c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
107c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
108c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
109c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
110c53a5d8fSJohn Baldwin
1118bf455a5SJohn Baldwin20031103:
1128bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
1138bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
1142a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
1158bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
1168bf455a5SJohn Baldwin
1179bf40edeSBrooks Davis20031031:
1189bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
1199bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
1209bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
1219bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
1229bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
1239bf40edeSBrooks Davis	reflect this change.
1249bf40edeSBrooks Davis
12547a42c7aSPoul-Henning Kamp20030928:
12647a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
12747a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
12847a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
12947a42c7aSPoul-Henning Kamp
13007105342SMax Khon20030926:
13107105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
13207105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
13307105342SMax Khon
13417dcd026SSam Leffler20030925:
13517dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
13617dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
13717dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
13817dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
13917dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
14017dcd026SSam Leffler
141fedf1d01SBruce M Simpson20030923:
142fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
143fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
144fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
145fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
146fedf1d01SBruce M Simpson
147db38f9cbSJacques Vidrine20030915:
148db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
149db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
150db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
151db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
152db38f9cbSJacques Vidrine
153c09d2c2bSMike Makonnen20030829:
154c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
155c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
156c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
157c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
158c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
159c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
160c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
161c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
162c09d2c2bSMike Makonnen	may or may not exist on your system.
163c09d2c2bSMike Makonnen
16417c159dcSSøren Schmidt20030824:
16517c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
16617c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
167f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
168f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
16917c159dcSSøren Schmidt
170c1f61aa9SDavid E. O'Brien20030819:
171c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
172c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
173c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
174c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
17569f7bcf3SWarner Losh
17638c962e7SNate Lawson20030728:
17738c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
17838c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
17938c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
18038c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
18138c962e7SNate Lawson	so the quirk can be re-enabled.
18238c962e7SNate Lawson
18374111097SWarner Losh20030724:
18474111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
18574111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
18674111097SWarner Losh
187178cf4e9SWarner Losh20030722:
188178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
189178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
190178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
191178cf4e9SWarner Losh	FPU hardware.
192178cf4e9SWarner Losh
193178cf4e9SWarner Losh20030714:
194178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
195178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
196178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
197178cf4e9SWarner Losh	People should report those issues to current@.
198178cf4e9SWarner Losh
199157c629aSWarner Losh20030711:
200157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
2018b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
20205538fa9SWarner Losh	/usr/obj.
203157c629aSWarner Losh
20474111097SWarner Losh20030610:
20574111097SWarner Losh	Remove deprecated locale names and transition period code
20674111097SWarner Losh	for them, finishing switching to the new scheme. Check your
20774111097SWarner Losh	LANG environment variable.
20874111097SWarner Losh
20974111097SWarner Losh20030609:
21074111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
21174111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
21274111097SWarner Losh	important to remember beforehand if your source tree is on
21374111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
21474111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
21574111097SWarner Losh	kernel.
21674111097SWarner Losh
21774111097SWarner Losh20030605:
2186cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
2196cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
2206cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
2216cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
2226cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
2236cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
2246cc6353fSMarcel Moolenaar
2256cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
2266cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
2276cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
2286cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
2296cc6353fSMarcel Moolenaar		:
2306cc6353fSMarcel Moolenaar
2316cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
2326cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
2336cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
2346cc6353fSMarcel Moolenaar
23552b47445SMark Murray20030505:
23652b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
23752b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
23852b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
23952b47445SMark Murray
240a26df538SWarner Losh20030502:
241a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
242a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
243a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
244a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
245a26df538SWarner Losh
2464b065e2cSDoug Barton20030501:
2474b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
2484b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
2494b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
2504b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
2514b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
2524b065e2cSDoug Barton	utilizes these old scripts has also been removed.
2534b065e2cSDoug Barton
25481cda3d9SWarner Losh20030423:
25581cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
25681cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
25781cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
25881cda3d9SWarner Losh	have until then to upgrade your kernel before updating
25981cda3d9SWarner Losh	userland.  In general, you should have a userland and
26081cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
26181cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
26281cda3d9SWarner Losh	allowances are made.
26381cda3d9SWarner Losh
26447a657d1SRuslan Ermilov20030329:
26547a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
26647a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
26747a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
26847a657d1SRuslan Ermilov
26947a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
27047a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
27147a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
27247a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
27347a657d1SRuslan Ermilov
27447a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
27547a657d1SRuslan Ermilov	    make cleandir && make obj && \
27647a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
27747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
27847a657d1SRuslan Ermilov
2795d2af00cSGregory Neil Shapiro20030208:
2805d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
2815d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
2825d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
2835d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
2845d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
2855d2af00cSGregory Neil Shapiro
2865d2af00cSGregory Neil Shapiro20030128:
2879db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
288ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
2899db58771SPoul-Henning Kamp	be removed when convenient.
2909db58771SPoul-Henning Kamp
2918d9b3f57SJake Burkholder20030126:
2928d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
2938d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
2948d9b3f57SJake Burkholder
2951c5efda5SJeff Roberson20030125:
2961c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
2971c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
298ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
2991c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
3001c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
3011c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
3021c5efda5SJeff Roberson
3039d1d64f5SWarner Losh20030115:
3049d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
3059d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
3069d1d64f5SWarner Losh	properly.
3079d1d64f5SWarner Losh
308c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
309c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
310c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
311c9fdb80aSWarner Losh	with NetBSD.
312c9fdb80aSWarner Losh
313161dc364SAlexander Kabaev20021222:
314161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
315161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
316161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
317161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
318161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
319161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
32084cc83efSAlexander Kabaev	rebuilt.
321161dc364SAlexander Kabaev
322fb4c8061SMartin Blapp20021216:
323fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
32489056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
325fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
3269d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
327fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
328fb4c8061SMartin Blapp
32917d47eb3SGiorgos Keramidas20021202:
33017d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
33117d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
33217d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
33317d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
33417d47eb3SGiorgos Keramidas
335a4459294SBill Fenner20021029:
336a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
337a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
338a4459294SBill Fenner	consumers in sync.
339a4459294SBill Fenner
340fc8c157fSWarner Losh20021024:
341c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
342c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
343c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
344c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
345c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
346c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
347c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
348c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
34969f7bcf3SWarner Losh
350fd9e8bdaSAndrew Gallatin20021023:
351fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
352fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
353fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
354fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
355fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
356fd9e8bdaSAndrew Gallatin
357fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
358fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
359fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
360fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
361fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
362fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
363fd9e8bdaSAndrew Gallatin
364f8a4c901SWarner Losh20020831:
365f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
366f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
367f8a4c901SWarner Losh	programs and libraries need to be recompiled.
368f8a4c901SWarner Losh
369f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
370f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
371f8a4c901SWarner Losh
372c2248fa2SJens Schweikhardt20020827:
373c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
374c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
375c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
376c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
377c2248fa2SJens Schweikhardt
3780d533e43SRuslan Ermilov20020815:
3790d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
3800d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
3810d533e43SRuslan Ermilov	again.
3820d533e43SRuslan Ermilov
38333c1de7dSRuslan Ermilov20020729:
38433c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
38533c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
38633c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
38733c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
38833c1de7dSRuslan Ermilov
3892b877facSJulian Elischer20020702:
3902b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
3912b877facSJulian Elischer	There are still some minor problems with some signals but the
3922b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
3932b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
3942b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
3952b877facSJulian Elischer
39606596d37SWarner Losh20020701:
39706596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
39806596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
39906596d37SWarner Losh	GNOME.
40006596d37SWarner Losh
40195ba4330SJacques Vidrine20020511:
40295ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
40395ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
40495ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
40595ba4330SJacques Vidrine	with the set-user-ID bit set.
40695ba4330SJacques Vidrine
407a81da3c9SDavid E. O'Brien20020510:
408f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
409f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
4104b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
411f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
412f50caf6fSDavid E. O'Brien
413f50caf6fSDavid E. O'Brien20020510:
414a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
415a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
416a81da3c9SDavid E. O'Brien	and then do a cvs update.
417a81da3c9SDavid E. O'Brien
418528a0ef5SJacques Vidrine20020421:
419528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
420528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
421528a0ef5SJacques Vidrine
42285aa5a2eSGregory Neil Shapiro20020404:
42385aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
42485aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
42585aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
42685aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
42785aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
42885aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
42985aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
43085aa5a2eSGregory Neil Shapiro
4318f1e4358SRuslan Ermilov20020403:
4328f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
4338f1e4358SRuslan Ermilov
4342292c02eSWarner Losh20020315:
4352292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
4362292c02eSWarner Losh
43769f7bcf3SWarner Losh20020225:
43869f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
43969f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
44069f7bcf3SWarner Losh
4418f35c493SWarner Losh20020217:
4428f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
4438f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
4448f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
4458f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
4468f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
4478f35c493SWarner Losh
448835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
449835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
450835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
451835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
452835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
453835284beSWarner Losh	and group must be merged from src/etc/group and
454835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
455835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
456835284beSWarner Losh	mergemaster before this will work if you are updating from a
457835284beSWarner Losh	very old version of current.  The updating recipe has changed
458835284beSWarner Losh	as of this date.
459835284beSWarner Losh
460fa9401c1SWarner Losh20020112:
461fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
462fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
463fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
464fa9401c1SWarner Losh	you have local modifications, you can use
465fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
466fa9401c1SWarner Losh	/etc/pam.d.
467fa9401c1SWarner Losh
468fa9401c1SWarner Losh	Please see the following url for more details:
469fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
47047d0d01fSWarner Losh20011229:
47147d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
47247d0d01fSWarner Losh	networkfs_types, please note that it has changed
47347d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
47447d0d01fSWarner Losh
475514318a8SWarner Losh20011220:
476514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
477514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
478514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
479514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
480514318a8SWarner Losh	version have now been merged back into the base system's
481514318a8SWarner Losh	version now.  The only user-visible change resulting from this
482514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
483514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
484514318a8SWarner Losh	as well.  (There has never been rc file support for
485514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
486514318a8SWarner Losh	reverted by the time the changes are MFCed.)
487514318a8SWarner Losh
488514318a8SWarner Losh20011215:
489514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
490514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
491514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
492514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
493514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
494514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
495514318a8SWarner Losh	will need to be customized then for `odd' densities using
496514318a8SWarner Losh	fdcontrol(8).
497514318a8SWarner Losh
4982d22e2bfSWarner Losh20011209:
4992d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
5002d22e2bfSWarner Losh	and truss(1) now works again.
5012d22e2bfSWarner Losh
5029e0428e2SWarner Losh20011207:
5039e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
5049e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
5059e0428e2SWarner Losh	see
5069e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
5079e0428e2SWarner Losh	for details.
5089e0428e2SWarner Losh
5099bab8c59SWarner Losh20011204:
5109bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
5119bab8c59SWarner Losh	kernel and burncd to be in sync.
5129bab8c59SWarner Losh
513e57d8b01SWarner Losh20011203:
514e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
515e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
516e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
517e57d8b01SWarner Losh	not there already.
518e57d8b01SWarner Losh
519e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
520e57d8b01SWarner Losh	until the issue has been resolved.
521e57d8b01SWarner Losh
522b001d36fSJacques Vidrine20011202:
523b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
524b001d36fSJacques Vidrine	patched.
525b001d36fSJacques Vidrine
5264b676ec1SWarner Losh20011126:
5274b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
5285ebbf43eSWarner Losh	after this date.  You need to do this only once.
5294b676ec1SWarner Losh
530d961e462SWarner Losh20011103:
531d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
532d961e462SWarner Losh	edges may be left, but for the most part things should be
5334b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
534d961e462SWarner Losh
535d961e462SWarner Losh20011030:
536d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
537d961e462SWarner Losh	choppy waves in the upgrade process.
538d961e462SWarner Losh
5391fe003b6SWarner Losh20011030:
540a4b6fda0SWarner Losh	The asr driver problem has been resolved.
5411fe003b6SWarner Losh
5421fe003b6SWarner Losh20011027:
5431fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
5441fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
5451fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
5461fe003b6SWarner Losh	try to use from this date forward.
5471fe003b6SWarner Losh
5481fe003b6SWarner Losh20011025:
5491fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
5501fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
5511fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
5521fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
5531fe003b6SWarner Losh	TARGET_ARCH=i386.
5541fe003b6SWarner Losh
555d05f9643SWarner Losh20011001:
556d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
557d05f9643SWarner Losh	You must recompile both the kernel and userland applications
558d05f9643SWarner Losh	at the same time.
559d05f9643SWarner Losh
56058970f85SWarner Losh20010929:
56158970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
56258970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
56358970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
56458970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
5659d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
56658970f85SWarner Losh
56758970f85SWarner Losh20010927:
56858970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
56958970f85SWarner Losh	To disable ACPI you can add
57066ff0e67SMax Khon		hint.acpi.0.disabled="1"
57158970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
57258970f85SWarner Losh	loader "ok" prompt).
57358970f85SWarner Losh
57458970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
57558970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
57658970f85SWarner Losh	file and not list acpi in that list.
577378f4486SAlfred Perlstein
5785119d237SWarner Losh20010924:
5795119d237SWarner Losh	The buildworld has been fixed.  You may need to install
5805119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
5818b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
5828b039fffSWarner Losh	get them installed on every installworld, or execute the
5838b039fffSWarner Losh	following to get them installed only once:
5848b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
58558970f85SWarner Losh		make all install
5868b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
5875119d237SWarner Losh
5883c293725SWarner Losh20010919:
5893c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
5903c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
5913c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
592772730c7SWarner Losh	workaround is to add
5933c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
5943c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
5953c293725SWarner Losh	can be removed afterwards.
5963c293725SWarner Losh
5973c293725SWarner Losh	A proper fix to the buildworld target is needed.
5983c293725SWarner Losh
5993c293725SWarner Losh20010918:
6003c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
6013c293725SWarner Losh	NFS may be unstable after this date.
6023c293725SWarner Losh
6033c293725SWarner Losh20010912:
6043c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
6053c293725SWarner Losh	the kernel.  While a few problems were introduced in the
6063c293725SWarner Losh	initial commit, most of the major ones have been found and
6073c293725SWarner Losh	corrected.
6083c293725SWarner Losh
6093c293725SWarner Losh20010901:
6103c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
6113c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
6123c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
6133c293725SWarner Losh	have been rectified around this date.
6143c293725SWarner Losh
61598b17b95SWarner Losh20010823:
61698b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
61798b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
61898b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
61998b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
62098b17b95SWarner Losh 	sure that user or group bind has read (and not write)
62198b17b95SWarner Losh 	permission for your name server configuration and that it
62298b17b95SWarner Losh 	has read and write permission for your slave zone files and
62398b17b95SWarner Losh 	directory.
62498b17b95SWarner Losh
62598b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
62698b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
62798b17b95SWarner Losh
62898b17b95SWarner Losh 		named_flags=
62998b17b95SWarner Losh
6307b9786edSMark Murray20010709:
6317b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
6327b9786edSMark Murray	the ability of the shared library major number to handle.
6337b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
6347b9786edSMark Murray	solution is to rebuild those ports.
6357b9786edSMark Murray
6361d28950eSWarner Losh20010628:
6371d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
6381d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
6391d28950eSWarner Losh
640e72fd46aSWarner Losh20010625:
64198b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
64298b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
64398b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
64498b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
64598b17b95SWarner Losh	IRQ configuration needs more safety belts.
64616de1a07SWarner Losh
6470d415dffSWarner Losh20010617:
648e72fd46aSWarner Losh	Softupdates problems have been corrected.
6490d415dffSWarner Losh
6500d415dffSWarner Losh20010614:
6510d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
6520d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
6530d415dffSWarner Losh	kernel building methods.
6540d415dffSWarner Losh
6558b9959adSWarner Losh20010613:
6568b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
6578b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
658e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
659e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
6608b9959adSWarner Losh
661e72fd46aSWarner Losh20010613:
6628b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
663e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
664e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
6658b9959adSWarner Losh
6660d415dffSWarner Losh20010612:
6670d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
6680d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
6690d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
6700d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
6710d415dffSWarner Losh	until this bug is fixed.
6720d415dffSWarner Losh
673e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
674e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
675ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
676e72fd46aSWarner Losh
6770d415dffSWarner Losh20010610:
6780d415dffSWarner Losh	Locale names have changed to match other systems better.
6790d415dffSWarner Losh
6806ccdb5e4SWarner Losh20010604:
6816ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
6826ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
6836ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
6843590182eSWarner Losh	Interrupt storms look a lot like a hang.
6853590182eSWarner Losh
6863590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
6873590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
6883590182eSWarner Losh	it is).
6893590182eSWarner Losh
6903590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
6913590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
6923590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
6933590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
6946ccdb5e4SWarner Losh
6950bc62786SWarner Losh20010530:
6960bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
6970bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
6980bc62786SWarner Losh	a limited time.  If you see
6990bc62786SWarner Losh
7000bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
7010bc62786SWarner Losh
7020bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
7030bc62786SWarner Losh	COPY=-C.
7040bc62786SWarner Losh
70568a38c6cSWarner Losh20010525:
706b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
707c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
708c4f4a728SWarner Losh	definitely is in bad shape.
70968a38c6cSWarner Losh
710ed0f29caSWarner Losh20010521:
711ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
712ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
713ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
714ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
715ed0f29caSWarner Losh	is
716ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
717ed0f29caSWarner Losh
71880c16af9SWarner Losh20010520:
71968a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
72080c16af9SWarner Losh
72180c16af9SWarner Losh20010519:
72280c16af9SWarner Losh	pccard has had much reorganizational work done to it over
72380c16af9SWarner Losh	the past few days.  Everything should still work, but if
72480c16af9SWarner Losh	not, please contact imp@freebsd.org.
72580c16af9SWarner Losh
726a45f2d05SWarner Losh20010517:
727a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
728a45f2d05SWarner Losh	userland at the same time.
729a45f2d05SWarner Losh
730a45f2d05SWarner Losh20010517:
731a45f2d05SWarner Losh	New ncurses imported.
732a45f2d05SWarner Losh
7332988afcaSWarner Losh20010512:
7342988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
7352988afcaSWarner Losh	will be the only way to go starting July 1.
7362988afcaSWarner Losh
7371a33dba7SWarner Losh20010504:
7381a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
7391a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
7401a33dba7SWarner Losh
74109946a51SWarner Losh20010502:
74209946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
74309946a51SWarner Losh
74409946a51SWarner Losh20010501:
74509946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
74609946a51SWarner Losh
74709946a51SWarner Losh20010430:
748a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
74909946a51SWarner Losh	go back in the water.
75009946a51SWarner Losh
75109946a51SWarner Losh20010429:
75209946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
75309946a51SWarner Losh	this date, but before the correction date.
75409946a51SWarner Losh
75591dd3b53SWarner Losh20010423:
75691dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
75791dd3b53SWarner Losh
75891dd3b53SWarner Losh20010411:
75991dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
76091dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
76191dd3b53SWarner Losh	Update only if you understand that you must not use the old
76291dd3b53SWarner Losh	fsck with the new kernel ever.
76391dd3b53SWarner Losh
764933b3269SWarner Losh20010330:
765933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
766c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
767933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
768933b3269SWarner Losh
769933b3269SWarner Losh20010319:
770933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
771933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
772933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
773f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
77409946a51SWarner Losh
77509946a51SWarner Losh20010315:
77609946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
777ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
77809946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
779933b3269SWarner Losh
780933b3269SWarner Losh20010312:
781933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
782933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
783933b3269SWarner Losh
784933b3269SWarner Losh20010312:
785933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
786933b3269SWarner Losh	instead of ad-hoc.
787933b3269SWarner Losh
788933b3269SWarner Losh20010310:
789f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
790933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
791933b3269SWarner Losh	ssh might not work if you don't.
792933b3269SWarner Losh
79362353691SWarner Losh20010303:
79462353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
79562353691SWarner Losh	which means that you must include the miibus in your kernel if
79662353691SWarner Losh	you use the ed driver.
79762353691SWarner Losh
798d325cf65SWarner Losh20010220:
799d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
800d325cf65SWarner Losh	safe to go back into the water.
801d325cf65SWarner Losh
802024daae6SWarner Losh20010211:
803024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
804024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
805024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
806024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
807024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
808024daae6SWarner Losh
809024daae6SWarner Losh	To get to the new system, you'll need to use the following
810024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
811024daae6SWarner Losh	don't have to move this to the updating section.
812024daae6SWarner Losh
813024daae6SWarner Losh	To get around the installworld problem, do:
814024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
815024daae6SWarner Losh		# make install
816024daae6SWarner Losh		# cd /usr/src
817024daae6SWarner Losh		# make installworld
818024daae6SWarner Losh	If that doesn't work, then try:
819024daae6SWarner Losh		# make -k installworld
820024daae6SWarner Losh		# make installworld
821024daae6SWarner Losh
822024daae6SWarner Losh20010207:
823024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
824024daae6SWarner Losh	do not include devfs in your kernel as problems result.
825024daae6SWarner Losh
826024daae6SWarner Losh20010205:
8277595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
828024daae6SWarner Losh	Remove them from your config.
829024daae6SWarner Losh
8301e159248SWarner Losh20010122:
8311e159248SWarner Losh	****************************** WARNING ******************************
8321e159248SWarner Losh			buildkernel has been changed slightly
8331e159248SWarner Losh	****************************** WARNING ******************************
8341e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
8351e159248SWarner Losh	should update your scripts and make.conf accordingly.
8361e159248SWarner Losh
8371e159248SWarner Losh20010119:
8381e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
8391e159248SWarner Losh	This requires a new config to build correctly.
8401e159248SWarner Losh
841aac7dfeaSWarner Losh20010116:
842ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
843aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
844aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
845aac7dfeaSWarner Losh
846aac7dfeaSWarner Losh20010110:
847aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
848aac7dfeaSWarner Losh
849aac7dfeaSWarner Losh20010102:
850aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
851aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
852aac7dfeaSWarner Losh
85363c90c9eSWarner Losh20010101:
85463c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
85563c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
8565fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
85763c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
85863c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
85963c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
86063c90c9eSWarner Losh	might have been ignored by the -k option.
86163c90c9eSWarner Losh
8625fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
8635fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
8645fd2a895SWarner Losh	of this working.
8655fd2a895SWarner Losh
866aac7dfeaSWarner Losh20001228:
867aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
868ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
869aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
870aac7dfeaSWarner Losh
871de2bcc63SWarner Losh20001218:
872de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
873de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
874de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
875de2bcc63SWarner Losh	cards will not be recognized without it.
876de2bcc63SWarner Losh
877960773f7SWarner Losh20001205:
878960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
879960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
880960773f7SWarner Losh	adding the following in pam.conf:
881960773f7SWarner Losh
882960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
883960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
884960773f7SWarner Losh	sshd    session required        pam_permit.so
885960773f7SWarner Losh
8860acc635eSWarner Losh20001031:
8870acc635eSWarner Losh	cvs updated to 1.11.
8880acc635eSWarner Losh
8890acc635eSWarner Losh20001020:
8900acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
8910acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
8920acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
8930acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
8940acc635eSWarner Losh	workaround.
8950acc635eSWarner Losh
8960acc635eSWarner Losh20001010:
8970acc635eSWarner Losh	****************************** WARNING ******************************
8980acc635eSWarner Losh				Sendmail has been updated.
8990acc635eSWarner Losh	****************************** WARNING ******************************
9000acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
9010acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
9020acc635eSWarner Losh	  is set.
9030acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
9040acc635eSWarner Losh	  commands.
9050acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
9060acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
9070acc635eSWarner Losh	  in /usr/share/sendmail/cf.
9080acc635eSWarner Losh	o sendmail.cw changed to local-host-names
9090acc635eSWarner Losh
9100acc635eSWarner Losh	More details can be found at
9110acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
9120acc635eSWarner Losh
9136e98a146SWarner Losh20001009:
9146e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
9156e98a146SWarner Losh	your entire ports tree, or you will have problems.
9166e98a146SWarner Losh
9176e98a146SWarner Losh20001006:
918685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
9196e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
9206e98a146SWarner Losh	/usr/bin/miniperl.
9216e98a146SWarner Losh
922073113a4SWarner Losh20001005:
923073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
924685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
925073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
926073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
927073113a4SWarner Losh	tree for anything to work.
928073113a4SWarner Losh
9290acc635eSWarner Losh20000928:
9300acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
9310acc635eSWarner Losh
932be3885b3SWarner Losh20000916:
933be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
934be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
935be3885b3SWarner Losh	same time as your kernel.
936be3885b3SWarner Losh
93776ec9675SWarner Losh20000914:
93876ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
93976ec9675SWarner Losh	include the device will cause suspended laptops losing time
94076ec9675SWarner Losh	when they resume.  Include
94176ec9675SWarner Losh		device		pmtimer
94276ec9675SWarner Losh	in your config file and
94301b9a434SWarner Losh		hint.pmtimer.0.at="isa"
94476ec9675SWarner Losh	to your /boot/device.hints file.
94576ec9675SWarner Losh
946f4865386SMark Murray20000911:
947f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
948f4865386SMark Murray	rather than an option. The supplied kernel config files have
949f4865386SMark Murray	been updated. You will need to do something similar in your
950f4865386SMark Murray	own kernel config file.
951f4865386SMark Murray	Remove:
952f4865386SMark Murray		options		RANDOMDEV
953f4865386SMark Murray	Add:
954f4865386SMark Murray		device		random
955f4865386SMark Murray	If you prefer to load the loadable module, you need to do
956f4865386SMark Murray	nothing.
957f4865386SMark Murray
958d594498fSWarner Losh20000909:
959d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
960d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
961d594498fSWarner Losh	reflect this if you load this module at boot time.
962d594498fSWarner Losh	The line should read:
963d594498fSWarner Losh		random_load="YES"
964d594498fSWarner Losh
9650deb7ddcSWarner Losh20000907:
9660deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
96716eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
96816eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
96916eb772dSWarner Losh	sure you don't have model loading problems which might at
97016eb772dSWarner Losh	first blush appear related to SMP.
97152bf24e7SWarner Losh
9725a01880bSWarner Losh20000906:
9735a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
9745a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
9755a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
9765a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
9775a01880bSWarner Losh	don't have one, and you have host.conf.
9785a01880bSWarner Losh
9792b41163cSWarner Losh20000905:
98038d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
98138d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
98238d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
98338d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
98438d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
98538d6ecd2SWarner Losh
98638d6ecd2SWarner Losh20000905:
9878aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
9888aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
9898aab4bc7SWarner Losh	is /boot/kernel.
9908aab4bc7SWarner Losh
9918aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
99238d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
99338d6ecd2SWarner Losh	installkernel/installworld dance.
9942b41163cSWarner Losh
995d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
996d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
997d594498fSWarner Losh	modules in that directory instead of finding them in the correct
998d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
999d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1000d594498fSWarner Losh
1001d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1002d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1003d594498fSWarner Losh		chflags noschg /kernel.old
1004d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1005d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1006d594498fSWarner Losh	fi
1007d594498fSWarner Losh
1008c22a309cSWarner Losh20000904:
1009c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1010c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1011c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1012c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1013c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1014c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1015c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1016c22a309cSWarner Losh	is not likely to be generated.
1017c22a309cSWarner Losh
1018fdb9f54dSWarner Losh20000825:
1019fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
10209c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
10219c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
10229c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
10239c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
10249c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
10259c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
10269c1a7444SWarner Losh	kernel.
10279c1a7444SWarner Losh
10289c1a7444SWarner Losh20000821:
10299c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
10309c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
10319c1a7444SWarner Losh	/boot/loader.conf.
1032fdb9f54dSWarner Losh
10338f250aa7SWarner Losh20000812:
10345da0d091SWarner Losh	suidperl is now always built and installed on the system, but
10355da0d091SWarner Losh	with permissions of 511.  If you have applications that use
10365da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
10375da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
10385da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
10395da0d091SWarner Losh	will fix this until the next build.
10405da0d091SWarner Losh
10415da0d091SWarner Losh20000812:
10428f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
10438f250aa7SWarner Losh	visible changes that may immediately affect your configuration
10448f250aa7SWarner Losh	include:
10458f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
10468f250aa7SWarner Losh	- newaliases limited to root and trusted users
10478f250aa7SWarner Losh	- MSA port (587) turned on by default
10488f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
10498f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
10508f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
10518f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
10528f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
10538f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
10548f250aa7SWarner Losh
105571c38472SWarner Losh20000810:
105671c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
105771c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
105871c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
105971c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
106071c38472SWarner Losh	specific use for it.
106171c38472SWarner Losh
106271c38472SWarner Losh20000729:
106371c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
106471c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
106571c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
106671c38472SWarner Losh	afterwards (unless the variables already are set, of course):
106771c38472SWarner Losh		# Enable network daemons for user convenience.
106871c38472SWarner Losh		inetd_enable="YES"
106971c38472SWarner Losh		portmap_enable="YES"
107071c38472SWarner Losh		sendmail_enable="YES"
107171c38472SWarner Losh
107271c38472SWarner Losh20000728:
107371c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
107471c38472SWarner Losh	will need to change that to nullfs_load="YES".
107571c38472SWarner Losh
10761dece4a9SWarner Losh20000728:
10771dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
10781dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
10791dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
10801dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
10811dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
10821dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
10831dece4a9SWarner Losh	to /MYKERNEL.
10841dece4a9SWarner Losh
1085409e887cSWarner Losh20000711:
1086409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1087409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1088409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1089409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1090409e887cSWarner Losh	for details on potential problems that you might have and how
1091409e887cSWarner Losh	to get around them.
1092409e887cSWarner Losh
1093409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1094409e887cSWarner Losh	clauses above, you needn't worry.
1095409e887cSWarner Losh
1096409e887cSWarner Losh20000711:
1097409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1098409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1099409e887cSWarner Losh	in the number of changed programs the first time when you run
1100409e887cSWarner Losh	mergemaster to get a new /etc/security.
1101409e887cSWarner Losh
1102673d13f2SWarner Losh20000710:
1103673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1104673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1105673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1106673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1107673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1108673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1109673d13f2SWarner Losh	errors. (see below, 20000624).
1110673d13f2SWarner Losh
1111bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
11121dece4a9SWarner Losh
1113673d13f2SWarner Losh20000709:
1114c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1115c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1116c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1117673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1118673d13f2SWarner Losh
1119e98e26cdSWarner Losh20000706:
1120e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1121e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1122e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1123f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1124e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
11252c021c6cSMark Ovens	interim if needed.
1126e98e26cdSWarner Losh
1127e98e26cdSWarner Losh20000705:
1128e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1129e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1130e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1131e98e26cdSWarner Losh	details.
1132e98e26cdSWarner Losh
1133c373950eSWarner Losh20000704:
11342f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
11352f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
11362f961bc8SWarner Losh
11372f961bc8SWarner Losh20000704:
1138c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1139c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1140c373950eSWarner Losh	rc.d scripts that haven't been updated.
1141c373950eSWarner Losh
114227dc3a2bSWarner Losh20000630:
114327dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
114427dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
114527dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
114627dc3a2bSWarner Losh
1147b8c215acSWarner Losh20000625:
1148b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
114927dc3a2bSWarner Losh	system installed in order to build the system and kernel.
115027dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
115127dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
115227dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
115327dc3a2bSWarner Losh	were required.  You should check with the latest collections
115427dc3a2bSWarner Losh	to make sure that these haven't changed.
1155b8c215acSWarner Losh
11567b990719SWarner Losh20000624:
11577b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
11587b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
11597b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
11601a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
11617b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
11627b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
11637b990719SWarner Losh	date to the completion of the work.
11647b990719SWarner Losh
116527dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
116627dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
116727dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
116827dc3a2bSWarner Losh	recreate the random and urandom devices.
116927dc3a2bSWarner Losh
117081e54c50SWarner Losh20000622:
117181e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
117281e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
117381e54c50SWarner Losh	that used to be required when updating.
117481e54c50SWarner Losh
117539943833SWarner Losh20000621:
11762c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
11772a2f33fbSDaniel Baker	the config file update procedure.
11782a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1179c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
118059df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
118159df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
118239943833SWarner Losh
1183290f9ad8SWarner Losh20000620:
1184290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1185290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1186290f9ad8SWarner Losh	that workaround will no longer be required.
1187290f9ad8SWarner Losh
118890fb6346SWarner Losh20000615:
118990fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
119090fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
119190fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
119290fb6346SWarner Losh	devices.
119390fb6346SWarner Losh
1194f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1195f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1196f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1197f75f65bbSWarner Losh	may work).
1198f75f65bbSWarner Losh
1199ba26da8eSWarner Losh20000612:
1200ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1201290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1202c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1203290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1204f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1205f54a3542SWarner Losh	NEWCARD for examples of the new format.
1206290f9ad8SWarner Losh
12079698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
12089698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
12099698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
12109698f2c0SWarner Losh	in it.
1211bbcc5149SWarner Losh
1212d65850ebSWarner Losh20000522:
1213ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1214d65850ebSWarner Losh	building a kernel after this point is advised that they need
1215d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1216d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1217d65850ebSWarner Losh
1218d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1219d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1220d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1221d9583a00SWarner Losh	is resolved.
1222d9583a00SWarner Losh
12238039cedeSWarner Losh20000513:
12248039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
12258039cedeSWarner Losh
1226d65850ebSWarner Losh20000510:
12278039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
12288039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
12298039cedeSWarner Losh	is requires for the boot blocks to build properly.
12308039cedeSWarner Losh
12318039cedeSWarner Losh20000503:
12328039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
12338039cedeSWarner Losh	is now available.
12348039cedeSWarner Losh
1235d65850ebSWarner Losh20000502:
1236d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1237d65850ebSWarner Losh	connected to the kernel building instead.
1238d65850ebSWarner Losh
1239be149406SNik Clayton20000427:
12408039cedeSWarner Losh	You may need to build gperf
12418039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
12428039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
12438039cedeSWarner Losh	an option only in -current.
12448039cedeSWarner Losh
12452b8dd5f4SWarner Losh20000417:
12462b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1247f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
12482b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
12492b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
12502c021c6cSMark Ovens	before you reboot, you'll need to issue:
12512b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
12522b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
12532b8dd5f4SWarner Losh
12548d9f1945SWarner Losh20000320:
12552b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
12562b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
12572b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1258ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
12592b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
12608d9f1945SWarner Losh
1261f8ab1dd6SWarner Losh20000319:
1262f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1263f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1264f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1265f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1266f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1267f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1268f8ab1dd6SWarner Losh
126919cada77SWarner Losh20000318:
1270f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
127119cada77SWarner Losh	Large kernel changes are being committed and are in the
127219cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
127319cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
127419cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
127519cada77SWarner Losh	that you are loading are up to date.
1276ba228352SWarner Losh
127719cada77SWarner Losh20000315:
12786d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
12796d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
12806d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
12816d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
12826d23c382SWarner Losh	boot.
12836d23c382SWarner Losh
12846d23c382SWarner Losh20000315:
128519cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
128619cada77SWarner Losh	to upgrade to 4.0 from 3.x.
128757199806SWarner Losh
1288dc0dbf5cSWarner LoshCOMMON ITEMS:
1289dc0dbf5cSWarner Losh
1290a24eff53SWarner Losh	General Notes
1291a24eff53SWarner Losh	-------------
1292a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1293a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1294a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1295a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1296a24eff53SWarner Losh	or several minor releases, or when several months have passed
1297a24eff53SWarner Losh	on the -current branch).
1298a24eff53SWarner Losh
12995780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
13005780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
13015780f3baSWarner Losh	environment when searching for values for global variables.
13025780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
13035780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
13045780f3baSWarner Losh	page for more details.
13055780f3baSWarner Losh
1306dc0dbf5cSWarner Losh	To build a kernel
1307dc0dbf5cSWarner Losh	-----------------
1308ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1309f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1310ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1311282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1312282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1313dc0dbf5cSWarner Losh
1314ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1315ba01eb20SWarner Losh	--------------------------------------------------------------
1316ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
131747d0d01fSWarner Losh	config KERNEL_NAME_HERE
1318ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1319ba01eb20SWarner Losh	make depend
1320ba01eb20SWarner Losh	make
1321ba01eb20SWarner Losh	make install
1322ba01eb20SWarner Losh
1323ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1324ba01eb20SWarner Losh
1325ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1326ba01eb20SWarner Losh	-----------------------------------------------------------
132763cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
132863cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
132963cb445eSWarner Losh
1330f643de42SWarner Losh	<make sure you have good level 0 dumps>
133163cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
133263cb445eSWarner Losh	make buildworld
133363cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
133463cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
133563cb445eSWarner Losh							[1]
133663cb445eSWarner Losh	<reboot in single user>				[3]
133763cb445eSWarner Losh	mergemaster -p					[5]
133863cb445eSWarner Losh	make installworld
133963cb445eSWarner Losh	mergemaster					[4]
134063cb445eSWarner Losh	<reboot>
134163cb445eSWarner Losh
1342759f0aefSWarner Losh
1343f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1344f27b1fceSJoseph Koshy	--------------------------------------------------
1345f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1346f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1347f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1348f27b1fceSJoseph Koshy	# size.
1349f27b1fceSJoseph Koshy
1350f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1351f27b1fceSJoseph Koshy	<boot into -stable>
1352f27b1fceSJoseph Koshy	make buildworld
1353f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1354f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1355f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1356f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1357f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1358f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1359f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1360f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1361f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1362f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1363f27b1fceSJoseph Koshy	<reboot into current>
1364f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1365f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1366f27b1fceSJoseph Koshy 	<reboot>
1367f27b1fceSJoseph Koshy
1368f27b1fceSJoseph Koshy
1369f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1370f27b1fceSJoseph Koshy	----------------------------------------------
13715c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
13725c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
13735c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
13745c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1375ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1376f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1377f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1378f643de42SWarner Losh	# space on /.
1379f643de42SWarner Losh
1380f643de42SWarner Losh	<make sure you have good level 0 dumps>
1381fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
138221c075eaSWarner Losh	make buildworld					[9]
1383c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1384d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1385be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1386fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1387fc8c157fSWarner Losh							[1]
1388fc8c157fSWarner Losh	<reboot in single user>				[3]
1389835284beSWarner Losh	mergemaster -p					[5]
1390f8a4c901SWarner Losh	rm -rf /usr/include/g++
1391ba26da8eSWarner Losh	make installworld
1392a6cd4f9dSWarner Losh	mergemaster					[4]
1393ba26da8eSWarner Losh	<reboot>
1394ba26da8eSWarner Losh
1395fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1396fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1397fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1398fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1399fdb9f54dSWarner Losh	the UPDATING entries.
1400ba26da8eSWarner Losh
14011dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
14021dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
14031dece4a9SWarner Losh	your sources that you have read and understood all the recent
14041dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
14051dece4a9SWarner Losh	much fewer pitfalls.
14061dece4a9SWarner Losh
1407134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1408134d2e86SWarner Losh	should disable them at this point so they don't crash your
1409134d2e86SWarner Losh	system on reboot.
1410134d2e86SWarner Losh
14119c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
14129c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
14139c1a7444SWarner Losh	configuration.
14149c1a7444SWarner Losh
1415ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1416ee6e1fc3SWarner Losh		fsck -p
1417ee6e1fc3SWarner Losh		mount -u /
1418ee6e1fc3SWarner Losh		mount -a
1419ee6e1fc3SWarner Losh		cd /usr/src
142047d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1421f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1422f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1423b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1424b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1425b705ae10SWarner Losh	be ignored while you proceed to the next step.
1426ee6e1fc3SWarner Losh
1427a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1428a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1429a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1430a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1431a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1432a6cd4f9dSWarner Losh	for potential gotchas.
1433a6cd4f9dSWarner Losh
1434835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1435835284beSWarner Losh	you may need to do this if you get unknown user in the following
1436835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1437835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1438835284beSWarner Losh	install) after the buildworld before this step if you last updated
1439835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1440835284beSWarner Losh
1441bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1442bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1443bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1444bd79cf40SWarner Losh		ok unload
1445bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1446bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1447bd79cf40SWarner Losh	described here.
1448fc8c157fSWarner Losh
1449fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1450fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1451fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1452fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1453fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1454fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1455fc8c157fSWarner Losh
1456c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1457c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1458c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1459c74fe6afSWarner Losh	that is hard to boot to recover.
1460c74fe6afSWarner Losh
146121c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
146221c075eaSWarner Losh	cvs prune empty directories.
1463dc0dbf5cSWarner LoshFORMAT:
1464dc0dbf5cSWarner Losh
1465f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
14661fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1467f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1468f8ab1dd6SWarner Loshprevious releases if your system is older than this.
14691fc1a0dcSWarner Losh
1470e72fd46aSWarner LoshCopyright information:
1471e72fd46aSWarner Losh
14729698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1473e72fd46aSWarner Losh
1474772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1475772730c7SWarner Loshmodification, in full or in part, in any form or format of this
14769698f2c0SWarner Loshdocument are permitted without further permission from the author.
1477e72fd46aSWarner Losh
1478e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1479e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1480e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1481e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1482e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1483e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1484e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1485e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1486e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1487e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1488e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1489e72fd46aSWarner Losh
1490e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1491e72fd46aSWarner Loshauthor a beer.
1492e72fd46aSWarner Losh
149322306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1494772730c7SWarner Loshthis document.
1495772730c7SWarner Losh
149697d92980SPeter Wemm$FreeBSD$
1497