xref: /freebsd/UPDATING (revision 7411109704e71abb6a7f318dd79af2aec36d2601)
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
20b7b1e150SMike Makonnen20040207:
21b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
22b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
23b7b1e150SMike Makonnen
24aca89ee6SDaniel Eischen20040130:
25aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
26aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
27aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
28aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
29aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
30aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
31aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
32aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
33aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
34aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
35aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
36aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
37aca89ee6SDaniel Eischen	do not work with libpthread.
38aca89ee6SDaniel Eischen
3968b7b3a9SAlex Dupre20040125:
4068b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
4168b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
4268b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
4368b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
4468b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
4568b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
4668b7b3a9SAlex Dupre
47ff46e0deSWarner Losh20040125:
48ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
49ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
50ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
51ff46e0deSWarner Losh
52ce41f4bfSRobert Watson20031213:
53ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
54ce41f4bfSRobert Watson	if the login process is unable to successfully set the
55ce41f4bfSRobert Watson	process credentials to include all groups defined for the
56ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
57ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
58ce41f4bfSRobert Watson	defined, or they will be unable to log in.
59ce41f4bfSRobert Watson
60c124fa05SJohn Baldwin20031203:
61c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
62c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
63c124fa05SJohn Baldwin
648ad1f5e4SHartmut Brandt20031112:
6530093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
6630093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
6797209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
6897209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
6997209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
7097209ca3SRobert Watson	not know about the new system calls that support the new statfs
713f631d52SMarcel Moolenaar	structure.
723f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
733f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
743f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
753f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
763f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
773f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
783f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
793f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
803f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
813f631d52SMarcel Moolenaar	these changes are installed.
8230093b05SWarner Losh
8330093b05SWarner Losh	****************************DANGER*******************************
8430093b05SWarner Losh
8530093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
8630093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
8730093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
8830093b05SWarner Losh	kernel.
8964a18d6fSKirk McKusick
9064a18d6fSKirk McKusick20031112:
918ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
928ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
938ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
948ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
958ad1f5e4SHartmut Brandt	sync before rebooting.
968ad1f5e4SHartmut Brandt
97c53a5d8fSJohn Baldwin20031111:
98c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
99c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
100c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
101c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
102c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
103c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
104c53a5d8fSJohn Baldwin
1058bf455a5SJohn Baldwin20031103:
1068bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
1078bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
1082a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
1098bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
1108bf455a5SJohn Baldwin
1119bf40edeSBrooks Davis20031031:
1129bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
1139bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
1149bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
1159bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
1169bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
1179bf40edeSBrooks Davis	reflect this change.
1189bf40edeSBrooks Davis
11947a42c7aSPoul-Henning Kamp20030928:
12047a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
12147a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
12247a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
12347a42c7aSPoul-Henning Kamp
12407105342SMax Khon20030926:
12507105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
12607105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
12707105342SMax Khon
12817dcd026SSam Leffler20030925:
12917dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
13017dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
13117dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
13217dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
13317dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
13417dcd026SSam Leffler
135fedf1d01SBruce M Simpson20030923:
136fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
137fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
138fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
139fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
140fedf1d01SBruce M Simpson
141db38f9cbSJacques Vidrine20030915:
142db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
143db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
144db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
145db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
146db38f9cbSJacques Vidrine
147c09d2c2bSMike Makonnen20030829:
148c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
149c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
150c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
151c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
152c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
153c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
154c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
155c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
156c09d2c2bSMike Makonnen	may or may not exist on your system.
157c09d2c2bSMike Makonnen
15817c159dcSSøren Schmidt20030824:
15917c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
16017c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
161f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
162f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
16317c159dcSSøren Schmidt
164c1f61aa9SDavid E. O'Brien20030819:
165c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
166c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
167c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
168c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
16969f7bcf3SWarner Losh
17038c962e7SNate Lawson20030728:
17138c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
17238c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
17338c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
17438c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
17538c962e7SNate Lawson	so the quirk can be re-enabled.
17638c962e7SNate Lawson
17774111097SWarner Losh20030724:
17874111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
17974111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
18074111097SWarner Losh
181178cf4e9SWarner Losh20030722:
182178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
183178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
184178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
185178cf4e9SWarner Losh	FPU hardware.
186178cf4e9SWarner Losh
187178cf4e9SWarner Losh20030714:
188178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
189178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
190178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
191178cf4e9SWarner Losh	People should report those issues to current@.
192178cf4e9SWarner Losh
193157c629aSWarner Losh20030711:
194157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
1958b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
19605538fa9SWarner Losh	/usr/obj.
197157c629aSWarner Losh
19874111097SWarner Losh20030610:
19974111097SWarner Losh	Remove deprecated locale names and transition period code
20074111097SWarner Losh	for them, finishing switching to the new scheme. Check your
20174111097SWarner Losh	LANG environment variable.
20274111097SWarner Losh
20374111097SWarner Losh20030609:
20474111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
20574111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
20674111097SWarner Losh	important to remember beforehand if your source tree is on
20774111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
20874111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
20974111097SWarner Losh	kernel.
21074111097SWarner Losh
21174111097SWarner Losh20030605:
2126cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
2136cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
2146cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
2156cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
2166cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
2176cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
2186cc6353fSMarcel Moolenaar
2196cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
2206cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
2216cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
2226cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
2236cc6353fSMarcel Moolenaar		:
2246cc6353fSMarcel Moolenaar
2256cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
2266cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
2276cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
2286cc6353fSMarcel Moolenaar
22952b47445SMark Murray20030505:
23052b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
23152b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
23252b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
23352b47445SMark Murray
234a26df538SWarner Losh20030502:
235a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
236a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
237a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
238a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
239a26df538SWarner Losh
2404b065e2cSDoug Barton20030501:
2414b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
2424b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
2434b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
2444b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
2454b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
2464b065e2cSDoug Barton	utilizes these old scripts has also been removed.
2474b065e2cSDoug Barton
24881cda3d9SWarner Losh20030423:
24981cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
25081cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
25181cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
25281cda3d9SWarner Losh	have until then to upgrade your kernel before updating
25381cda3d9SWarner Losh	userland.  In general, you should have a userland and
25481cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
25581cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
25681cda3d9SWarner Losh	allowances are made.
25781cda3d9SWarner Losh
25847a657d1SRuslan Ermilov20030329:
25947a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
26047a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
26147a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
26247a657d1SRuslan Ermilov
26347a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
26447a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
26547a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
26647a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
26747a657d1SRuslan Ermilov
26847a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
26947a657d1SRuslan Ermilov	    make cleandir && make obj && \
27047a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
27147a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
27247a657d1SRuslan Ermilov
2735d2af00cSGregory Neil Shapiro20030208:
2745d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
2755d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
2765d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
2775d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
2785d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
2795d2af00cSGregory Neil Shapiro
2805d2af00cSGregory Neil Shapiro20030128:
2819db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
282ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
2839db58771SPoul-Henning Kamp	be removed when convenient.
2849db58771SPoul-Henning Kamp
2858d9b3f57SJake Burkholder20030126:
2868d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
2878d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
2888d9b3f57SJake Burkholder
2891c5efda5SJeff Roberson20030125:
2901c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
2911c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
292ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
2931c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
2941c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
2951c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
2961c5efda5SJeff Roberson
2979d1d64f5SWarner Losh20030115:
2989d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
2999d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
3009d1d64f5SWarner Losh	properly.
3019d1d64f5SWarner Losh
302c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
303c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
304c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
305c9fdb80aSWarner Losh	with NetBSD.
306c9fdb80aSWarner Losh
307161dc364SAlexander Kabaev20021222:
308161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
309161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
310161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
311161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
312161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
313161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
31484cc83efSAlexander Kabaev	rebuilt.
315161dc364SAlexander Kabaev
316fb4c8061SMartin Blapp20021216:
317fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
31889056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
319fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
3209d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
321fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
322fb4c8061SMartin Blapp
32317d47eb3SGiorgos Keramidas20021202:
32417d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
32517d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
32617d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
32717d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
32817d47eb3SGiorgos Keramidas
329a4459294SBill Fenner20021029:
330a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
331a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
332a4459294SBill Fenner	consumers in sync.
333a4459294SBill Fenner
334fc8c157fSWarner Losh20021024:
335c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
336c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
337c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
338c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
339c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
340c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
341c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
342c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
34369f7bcf3SWarner Losh
344fd9e8bdaSAndrew Gallatin20021023:
345fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
346fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
347fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
348fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
349fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
350fd9e8bdaSAndrew Gallatin
351fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
352fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
353fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
354fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
355fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
356fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
357fd9e8bdaSAndrew Gallatin
358f8a4c901SWarner Losh20020831:
359f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
360f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
361f8a4c901SWarner Losh	programs and libraries need to be recompiled.
362f8a4c901SWarner Losh
363f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
364f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
365f8a4c901SWarner Losh
366c2248fa2SJens Schweikhardt20020827:
367c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
368c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
369c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
370c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
371c2248fa2SJens Schweikhardt
3720d533e43SRuslan Ermilov20020815:
3730d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
3740d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
3750d533e43SRuslan Ermilov	again.
3760d533e43SRuslan Ermilov
37733c1de7dSRuslan Ermilov20020729:
37833c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
37933c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
38033c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
38133c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
38233c1de7dSRuslan Ermilov
3832b877facSJulian Elischer20020702:
3842b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
3852b877facSJulian Elischer	There are still some minor problems with some signals but the
3862b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
3872b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
3882b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
3892b877facSJulian Elischer
39006596d37SWarner Losh20020701:
39106596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
39206596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
39306596d37SWarner Losh	GNOME.
39406596d37SWarner Losh
39595ba4330SJacques Vidrine20020511:
39695ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
39795ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
39895ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
39995ba4330SJacques Vidrine	with the set-user-ID bit set.
40095ba4330SJacques Vidrine
401a81da3c9SDavid E. O'Brien20020510:
402f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
403f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
4044b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
405f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
406f50caf6fSDavid E. O'Brien
407f50caf6fSDavid E. O'Brien20020510:
408a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
409a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
410a81da3c9SDavid E. O'Brien	and then do a cvs update.
411a81da3c9SDavid E. O'Brien
412528a0ef5SJacques Vidrine20020421:
413528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
414528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
415528a0ef5SJacques Vidrine
41685aa5a2eSGregory Neil Shapiro20020404:
41785aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
41885aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
41985aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
42085aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
42185aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
42285aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
42385aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
42485aa5a2eSGregory Neil Shapiro
4258f1e4358SRuslan Ermilov20020403:
4268f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
4278f1e4358SRuslan Ermilov
4282292c02eSWarner Losh20020315:
4292292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
4302292c02eSWarner Losh
43169f7bcf3SWarner Losh20020225:
43269f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
43369f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
43469f7bcf3SWarner Losh
4358f35c493SWarner Losh20020217:
4368f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
4378f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
4388f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
4398f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
4408f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
4418f35c493SWarner Losh
442835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
443835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
444835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
445835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
446835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
447835284beSWarner Losh	and group must be merged from src/etc/group and
448835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
449835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
450835284beSWarner Losh	mergemaster before this will work if you are updating from a
451835284beSWarner Losh	very old version of current.  The updating recipe has changed
452835284beSWarner Losh	as of this date.
453835284beSWarner Losh
454fa9401c1SWarner Losh20020112:
455fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
456fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
457fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
458fa9401c1SWarner Losh	you have local modifications, you can use
459fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
460fa9401c1SWarner Losh	/etc/pam.d.
461fa9401c1SWarner Losh
462fa9401c1SWarner Losh	Please see the following url for more details:
463fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
46447d0d01fSWarner Losh20011229:
46547d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
46647d0d01fSWarner Losh	networkfs_types, please note that it has changed
46747d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
46847d0d01fSWarner Losh
469514318a8SWarner Losh20011220:
470514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
471514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
472514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
473514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
474514318a8SWarner Losh	version have now been merged back into the base system's
475514318a8SWarner Losh	version now.  The only user-visible change resulting from this
476514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
477514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
478514318a8SWarner Losh	as well.  (There has never been rc file support for
479514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
480514318a8SWarner Losh	reverted by the time the changes are MFCed.)
481514318a8SWarner Losh
482514318a8SWarner Losh20011215:
483514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
484514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
485514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
486514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
487514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
488514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
489514318a8SWarner Losh	will need to be customized then for `odd' densities using
490514318a8SWarner Losh	fdcontrol(8).
491514318a8SWarner Losh
4922d22e2bfSWarner Losh20011209:
4932d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
4942d22e2bfSWarner Losh	and truss(1) now works again.
4952d22e2bfSWarner Losh
4969e0428e2SWarner Losh20011207:
4979e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
4989e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
4999e0428e2SWarner Losh	see
5009e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
5019e0428e2SWarner Losh	for details.
5029e0428e2SWarner Losh
5039bab8c59SWarner Losh20011204:
5049bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
5059bab8c59SWarner Losh	kernel and burncd to be in sync.
5069bab8c59SWarner Losh
507e57d8b01SWarner Losh20011203:
508e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
509e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
510e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
511e57d8b01SWarner Losh	not there already.
512e57d8b01SWarner Losh
513e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
514e57d8b01SWarner Losh	until the issue has been resolved.
515e57d8b01SWarner Losh
516b001d36fSJacques Vidrine20011202:
517b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
518b001d36fSJacques Vidrine	patched.
519b001d36fSJacques Vidrine
5204b676ec1SWarner Losh20011126:
5214b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
5225ebbf43eSWarner Losh	after this date.  You need to do this only once.
5234b676ec1SWarner Losh
524d961e462SWarner Losh20011103:
525d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
526d961e462SWarner Losh	edges may be left, but for the most part things should be
5274b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
528d961e462SWarner Losh
529d961e462SWarner Losh20011030:
530d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
531d961e462SWarner Losh	choppy waves in the upgrade process.
532d961e462SWarner Losh
5331fe003b6SWarner Losh20011030:
534a4b6fda0SWarner Losh	The asr driver problem has been resolved.
5351fe003b6SWarner Losh
5361fe003b6SWarner Losh20011027:
5371fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
5381fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
5391fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
5401fe003b6SWarner Losh	try to use from this date forward.
5411fe003b6SWarner Losh
5421fe003b6SWarner Losh20011025:
5431fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
5441fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
5451fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
5461fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
5471fe003b6SWarner Losh	TARGET_ARCH=i386.
5481fe003b6SWarner Losh
549d05f9643SWarner Losh20011001:
550d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
551d05f9643SWarner Losh	You must recompile both the kernel and userland applications
552d05f9643SWarner Losh	at the same time.
553d05f9643SWarner Losh
55458970f85SWarner Losh20010929:
55558970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
55658970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
55758970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
55858970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
5599d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
56058970f85SWarner Losh
56158970f85SWarner Losh20010927:
56258970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
56358970f85SWarner Losh	To disable ACPI you can add
56466ff0e67SMax Khon		hint.acpi.0.disabled="1"
56558970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
56658970f85SWarner Losh	loader "ok" prompt).
56758970f85SWarner Losh
56858970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
56958970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
57058970f85SWarner Losh	file and not list acpi in that list.
571378f4486SAlfred Perlstein
5725119d237SWarner Losh20010924:
5735119d237SWarner Losh	The buildworld has been fixed.  You may need to install
5745119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
5758b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
5768b039fffSWarner Losh	get them installed on every installworld, or execute the
5778b039fffSWarner Losh	following to get them installed only once:
5788b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
57958970f85SWarner Losh		make all install
5808b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
5815119d237SWarner Losh
5823c293725SWarner Losh20010919:
5833c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
5843c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
5853c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
586772730c7SWarner Losh	workaround is to add
5873c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
5883c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
5893c293725SWarner Losh	can be removed afterwards.
5903c293725SWarner Losh
5913c293725SWarner Losh	A proper fix to the buildworld target is needed.
5923c293725SWarner Losh
5933c293725SWarner Losh20010918:
5943c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
5953c293725SWarner Losh	NFS may be unstable after this date.
5963c293725SWarner Losh
5973c293725SWarner Losh20010912:
5983c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
5993c293725SWarner Losh	the kernel.  While a few problems were introduced in the
6003c293725SWarner Losh	initial commit, most of the major ones have been found and
6013c293725SWarner Losh	corrected.
6023c293725SWarner Losh
6033c293725SWarner Losh20010901:
6043c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
6053c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
6063c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
6073c293725SWarner Losh	have been rectified around this date.
6083c293725SWarner Losh
60998b17b95SWarner Losh20010823:
61098b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
61198b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
61298b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
61398b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
61498b17b95SWarner Losh 	sure that user or group bind has read (and not write)
61598b17b95SWarner Losh 	permission for your name server configuration and that it
61698b17b95SWarner Losh 	has read and write permission for your slave zone files and
61798b17b95SWarner Losh 	directory.
61898b17b95SWarner Losh
61998b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
62098b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
62198b17b95SWarner Losh
62298b17b95SWarner Losh 		named_flags=
62398b17b95SWarner Losh
6247b9786edSMark Murray20010709:
6257b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
6267b9786edSMark Murray	the ability of the shared library major number to handle.
6277b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
6287b9786edSMark Murray	solution is to rebuild those ports.
6297b9786edSMark Murray
6301d28950eSWarner Losh20010628:
6311d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
6321d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
6331d28950eSWarner Losh
634e72fd46aSWarner Losh20010625:
63598b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
63698b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
63798b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
63898b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
63998b17b95SWarner Losh	IRQ configuration needs more safety belts.
64016de1a07SWarner Losh
6410d415dffSWarner Losh20010617:
642e72fd46aSWarner Losh	Softupdates problems have been corrected.
6430d415dffSWarner Losh
6440d415dffSWarner Losh20010614:
6450d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
6460d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
6470d415dffSWarner Losh	kernel building methods.
6480d415dffSWarner Losh
6498b9959adSWarner Losh20010613:
6508b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
6518b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
652e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
653e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
6548b9959adSWarner Losh
655e72fd46aSWarner Losh20010613:
6568b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
657e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
658e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
6598b9959adSWarner Losh
6600d415dffSWarner Losh20010612:
6610d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
6620d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
6630d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
6640d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
6650d415dffSWarner Losh	until this bug is fixed.
6660d415dffSWarner Losh
667e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
668e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
669ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
670e72fd46aSWarner Losh
6710d415dffSWarner Losh20010610:
6720d415dffSWarner Losh	Locale names have changed to match other systems better.
6730d415dffSWarner Losh
6746ccdb5e4SWarner Losh20010604:
6756ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
6766ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
6776ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
6783590182eSWarner Losh	Interrupt storms look a lot like a hang.
6793590182eSWarner Losh
6803590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
6813590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
6823590182eSWarner Losh	it is).
6833590182eSWarner Losh
6843590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
6853590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
6863590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
6873590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
6886ccdb5e4SWarner Losh
6890bc62786SWarner Losh20010530:
6900bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
6910bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
6920bc62786SWarner Losh	a limited time.  If you see
6930bc62786SWarner Losh
6940bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
6950bc62786SWarner Losh
6960bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
6970bc62786SWarner Losh	COPY=-C.
6980bc62786SWarner Losh
69968a38c6cSWarner Losh20010525:
700b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
701c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
702c4f4a728SWarner Losh	definitely is in bad shape.
70368a38c6cSWarner Losh
704ed0f29caSWarner Losh20010521:
705ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
706ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
707ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
708ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
709ed0f29caSWarner Losh	is
710ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
711ed0f29caSWarner Losh
71280c16af9SWarner Losh20010520:
71368a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
71480c16af9SWarner Losh
71580c16af9SWarner Losh20010519:
71680c16af9SWarner Losh	pccard has had much reorganizational work done to it over
71780c16af9SWarner Losh	the past few days.  Everything should still work, but if
71880c16af9SWarner Losh	not, please contact imp@freebsd.org.
71980c16af9SWarner Losh
720a45f2d05SWarner Losh20010517:
721a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
722a45f2d05SWarner Losh	userland at the same time.
723a45f2d05SWarner Losh
724a45f2d05SWarner Losh20010517:
725a45f2d05SWarner Losh	New ncurses imported.
726a45f2d05SWarner Losh
7272988afcaSWarner Losh20010512:
7282988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
7292988afcaSWarner Losh	will be the only way to go starting July 1.
7302988afcaSWarner Losh
7311a33dba7SWarner Losh20010504:
7321a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
7331a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
7341a33dba7SWarner Losh
73509946a51SWarner Losh20010502:
73609946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
73709946a51SWarner Losh
73809946a51SWarner Losh20010501:
73909946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
74009946a51SWarner Losh
74109946a51SWarner Losh20010430:
742a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
74309946a51SWarner Losh	go back in the water.
74409946a51SWarner Losh
74509946a51SWarner Losh20010429:
74609946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
74709946a51SWarner Losh	this date, but before the correction date.
74809946a51SWarner Losh
74991dd3b53SWarner Losh20010423:
75091dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
75191dd3b53SWarner Losh
75291dd3b53SWarner Losh20010411:
75391dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
75491dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
75591dd3b53SWarner Losh	Update only if you understand that you must not use the old
75691dd3b53SWarner Losh	fsck with the new kernel ever.
75791dd3b53SWarner Losh
758933b3269SWarner Losh20010330:
759933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
760c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
761933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
762933b3269SWarner Losh
763933b3269SWarner Losh20010319:
764933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
765933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
766933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
767f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
76809946a51SWarner Losh
76909946a51SWarner Losh20010315:
77009946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
771ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
77209946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
773933b3269SWarner Losh
774933b3269SWarner Losh20010312:
775933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
776933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
777933b3269SWarner Losh
778933b3269SWarner Losh20010312:
779933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
780933b3269SWarner Losh	instead of ad-hoc.
781933b3269SWarner Losh
782933b3269SWarner Losh20010310:
783f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
784933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
785933b3269SWarner Losh	ssh might not work if you don't.
786933b3269SWarner Losh
78762353691SWarner Losh20010303:
78862353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
78962353691SWarner Losh	which means that you must include the miibus in your kernel if
79062353691SWarner Losh	you use the ed driver.
79162353691SWarner Losh
792d325cf65SWarner Losh20010220:
793d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
794d325cf65SWarner Losh	safe to go back into the water.
795d325cf65SWarner Losh
796024daae6SWarner Losh20010211:
797024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
798024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
799024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
800024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
801024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
802024daae6SWarner Losh
803024daae6SWarner Losh	To get to the new system, you'll need to use the following
804024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
805024daae6SWarner Losh	don't have to move this to the updating section.
806024daae6SWarner Losh
807024daae6SWarner Losh	To get around the installworld problem, do:
808024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
809024daae6SWarner Losh		# make install
810024daae6SWarner Losh		# cd /usr/src
811024daae6SWarner Losh		# make installworld
812024daae6SWarner Losh	If that doesn't work, then try:
813024daae6SWarner Losh		# make -k installworld
814024daae6SWarner Losh		# make installworld
815024daae6SWarner Losh
816024daae6SWarner Losh20010207:
817024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
818024daae6SWarner Losh	do not include devfs in your kernel as problems result.
819024daae6SWarner Losh
820024daae6SWarner Losh20010205:
8217595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
822024daae6SWarner Losh	Remove them from your config.
823024daae6SWarner Losh
8241e159248SWarner Losh20010122:
8251e159248SWarner Losh	****************************** WARNING ******************************
8261e159248SWarner Losh			buildkernel has been changed slightly
8271e159248SWarner Losh	****************************** WARNING ******************************
8281e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
8291e159248SWarner Losh	should update your scripts and make.conf accordingly.
8301e159248SWarner Losh
8311e159248SWarner Losh20010119:
8321e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
8331e159248SWarner Losh	This requires a new config to build correctly.
8341e159248SWarner Losh
835aac7dfeaSWarner Losh20010116:
836ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
837aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
838aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
839aac7dfeaSWarner Losh
840aac7dfeaSWarner Losh20010110:
841aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
842aac7dfeaSWarner Losh
843aac7dfeaSWarner Losh20010102:
844aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
845aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
846aac7dfeaSWarner Losh
84763c90c9eSWarner Losh20010101:
84863c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
84963c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
8505fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
85163c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
85263c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
85363c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
85463c90c9eSWarner Losh	might have been ignored by the -k option.
85563c90c9eSWarner Losh
8565fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
8575fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
8585fd2a895SWarner Losh	of this working.
8595fd2a895SWarner Losh
860aac7dfeaSWarner Losh20001228:
861aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
862ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
863aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
864aac7dfeaSWarner Losh
865de2bcc63SWarner Losh20001218:
866de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
867de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
868de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
869de2bcc63SWarner Losh	cards will not be recognized without it.
870de2bcc63SWarner Losh
871960773f7SWarner Losh20001205:
872960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
873960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
874960773f7SWarner Losh	adding the following in pam.conf:
875960773f7SWarner Losh
876960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
877960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
878960773f7SWarner Losh	sshd    session required        pam_permit.so
879960773f7SWarner Losh
8800acc635eSWarner Losh20001031:
8810acc635eSWarner Losh	cvs updated to 1.11.
8820acc635eSWarner Losh
8830acc635eSWarner Losh20001020:
8840acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
8850acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
8860acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
8870acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
8880acc635eSWarner Losh	workaround.
8890acc635eSWarner Losh
8900acc635eSWarner Losh20001010:
8910acc635eSWarner Losh	****************************** WARNING ******************************
8920acc635eSWarner Losh				Sendmail has been updated.
8930acc635eSWarner Losh	****************************** WARNING ******************************
8940acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
8950acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
8960acc635eSWarner Losh	  is set.
8970acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
8980acc635eSWarner Losh	  commands.
8990acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
9000acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
9010acc635eSWarner Losh	  in /usr/share/sendmail/cf.
9020acc635eSWarner Losh	o sendmail.cw changed to local-host-names
9030acc635eSWarner Losh
9040acc635eSWarner Losh	More details can be found at
9050acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
9060acc635eSWarner Losh
9076e98a146SWarner Losh20001009:
9086e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
9096e98a146SWarner Losh	your entire ports tree, or you will have problems.
9106e98a146SWarner Losh
9116e98a146SWarner Losh20001006:
912685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
9136e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
9146e98a146SWarner Losh	/usr/bin/miniperl.
9156e98a146SWarner Losh
916073113a4SWarner Losh20001005:
917073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
918685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
919073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
920073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
921073113a4SWarner Losh	tree for anything to work.
922073113a4SWarner Losh
9230acc635eSWarner Losh20000928:
9240acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
9250acc635eSWarner Losh
926be3885b3SWarner Losh20000916:
927be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
928be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
929be3885b3SWarner Losh	same time as your kernel.
930be3885b3SWarner Losh
93176ec9675SWarner Losh20000914:
93276ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
93376ec9675SWarner Losh	include the device will cause suspended laptops losing time
93476ec9675SWarner Losh	when they resume.  Include
93576ec9675SWarner Losh		device		pmtimer
93676ec9675SWarner Losh	in your config file and
93701b9a434SWarner Losh		hint.pmtimer.0.at="isa"
93876ec9675SWarner Losh	to your /boot/device.hints file.
93976ec9675SWarner Losh
940f4865386SMark Murray20000911:
941f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
942f4865386SMark Murray	rather than an option. The supplied kernel config files have
943f4865386SMark Murray	been updated. You will need to do something similar in your
944f4865386SMark Murray	own kernel config file.
945f4865386SMark Murray	Remove:
946f4865386SMark Murray		options		RANDOMDEV
947f4865386SMark Murray	Add:
948f4865386SMark Murray		device		random
949f4865386SMark Murray	If you prefer to load the loadable module, you need to do
950f4865386SMark Murray	nothing.
951f4865386SMark Murray
952d594498fSWarner Losh20000909:
953d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
954d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
955d594498fSWarner Losh	reflect this if you load this module at boot time.
956d594498fSWarner Losh	The line should read:
957d594498fSWarner Losh		random_load="YES"
958d594498fSWarner Losh
9590deb7ddcSWarner Losh20000907:
9600deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
96116eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
96216eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
96316eb772dSWarner Losh	sure you don't have model loading problems which might at
96416eb772dSWarner Losh	first blush appear related to SMP.
96552bf24e7SWarner Losh
9665a01880bSWarner Losh20000906:
9675a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
9685a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
9695a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
9705a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
9715a01880bSWarner Losh	don't have one, and you have host.conf.
9725a01880bSWarner Losh
9732b41163cSWarner Losh20000905:
97438d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
97538d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
97638d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
97738d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
97838d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
97938d6ecd2SWarner Losh
98038d6ecd2SWarner Losh20000905:
9818aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
9828aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
9838aab4bc7SWarner Losh	is /boot/kernel.
9848aab4bc7SWarner Losh
9858aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
98638d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
98738d6ecd2SWarner Losh	installkernel/installworld dance.
9882b41163cSWarner Losh
989d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
990d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
991d594498fSWarner Losh	modules in that directory instead of finding them in the correct
992d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
993d594498fSWarner Losh	is that the linux module crashes your machine after the update.
994d594498fSWarner Losh
995d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
996d594498fSWarner Losh		mv /modules.old /boot/kernel.old
997d594498fSWarner Losh		chflags noschg /kernel.old
998d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
999d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1000d594498fSWarner Losh	fi
1001d594498fSWarner Losh
1002c22a309cSWarner Losh20000904:
1003c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1004c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1005c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1006c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1007c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1008c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1009c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1010c22a309cSWarner Losh	is not likely to be generated.
1011c22a309cSWarner Losh
1012fdb9f54dSWarner Losh20000825:
1013fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
10149c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
10159c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
10169c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
10179c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
10189c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
10199c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
10209c1a7444SWarner Losh	kernel.
10219c1a7444SWarner Losh
10229c1a7444SWarner Losh20000821:
10239c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
10249c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
10259c1a7444SWarner Losh	/boot/loader.conf.
1026fdb9f54dSWarner Losh
10278f250aa7SWarner Losh20000812:
10285da0d091SWarner Losh	suidperl is now always built and installed on the system, but
10295da0d091SWarner Losh	with permissions of 511.  If you have applications that use
10305da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
10315da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
10325da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
10335da0d091SWarner Losh	will fix this until the next build.
10345da0d091SWarner Losh
10355da0d091SWarner Losh20000812:
10368f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
10378f250aa7SWarner Losh	visible changes that may immediately affect your configuration
10388f250aa7SWarner Losh	include:
10398f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
10408f250aa7SWarner Losh	- newaliases limited to root and trusted users
10418f250aa7SWarner Losh	- MSA port (587) turned on by default
10428f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
10438f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
10448f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
10458f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
10468f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
10478f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
10488f250aa7SWarner Losh
104971c38472SWarner Losh20000810:
105071c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
105171c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
105271c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
105371c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
105471c38472SWarner Losh	specific use for it.
105571c38472SWarner Losh
105671c38472SWarner Losh20000729:
105771c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
105871c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
105971c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
106071c38472SWarner Losh	afterwards (unless the variables already are set, of course):
106171c38472SWarner Losh		# Enable network daemons for user convenience.
106271c38472SWarner Losh		inetd_enable="YES"
106371c38472SWarner Losh		portmap_enable="YES"
106471c38472SWarner Losh		sendmail_enable="YES"
106571c38472SWarner Losh
106671c38472SWarner Losh20000728:
106771c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
106871c38472SWarner Losh	will need to change that to nullfs_load="YES".
106971c38472SWarner Losh
10701dece4a9SWarner Losh20000728:
10711dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
10721dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
10731dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
10741dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
10751dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
10761dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
10771dece4a9SWarner Losh	to /MYKERNEL.
10781dece4a9SWarner Losh
1079409e887cSWarner Losh20000711:
1080409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1081409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1082409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1083409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1084409e887cSWarner Losh	for details on potential problems that you might have and how
1085409e887cSWarner Losh	to get around them.
1086409e887cSWarner Losh
1087409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1088409e887cSWarner Losh	clauses above, you needn't worry.
1089409e887cSWarner Losh
1090409e887cSWarner Losh20000711:
1091409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1092409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1093409e887cSWarner Losh	in the number of changed programs the first time when you run
1094409e887cSWarner Losh	mergemaster to get a new /etc/security.
1095409e887cSWarner Losh
1096673d13f2SWarner Losh20000710:
1097673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1098673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1099673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1100673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1101673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1102673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1103673d13f2SWarner Losh	errors. (see below, 20000624).
1104673d13f2SWarner Losh
1105bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
11061dece4a9SWarner Losh
1107673d13f2SWarner Losh20000709:
1108c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1109c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1110c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1111673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1112673d13f2SWarner Losh
1113e98e26cdSWarner Losh20000706:
1114e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1115e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1116e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1117f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1118e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
11192c021c6cSMark Ovens	interim if needed.
1120e98e26cdSWarner Losh
1121e98e26cdSWarner Losh20000705:
1122e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1123e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1124e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1125e98e26cdSWarner Losh	details.
1126e98e26cdSWarner Losh
1127c373950eSWarner Losh20000704:
11282f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
11292f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
11302f961bc8SWarner Losh
11312f961bc8SWarner Losh20000704:
1132c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1133c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1134c373950eSWarner Losh	rc.d scripts that haven't been updated.
1135c373950eSWarner Losh
113627dc3a2bSWarner Losh20000630:
113727dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
113827dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
113927dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
114027dc3a2bSWarner Losh
1141b8c215acSWarner Losh20000625:
1142b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
114327dc3a2bSWarner Losh	system installed in order to build the system and kernel.
114427dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
114527dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
114627dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
114727dc3a2bSWarner Losh	were required.  You should check with the latest collections
114827dc3a2bSWarner Losh	to make sure that these haven't changed.
1149b8c215acSWarner Losh
11507b990719SWarner Losh20000624:
11517b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
11527b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
11537b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
11541a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
11557b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
11567b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
11577b990719SWarner Losh	date to the completion of the work.
11587b990719SWarner Losh
115927dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
116027dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
116127dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
116227dc3a2bSWarner Losh	recreate the random and urandom devices.
116327dc3a2bSWarner Losh
116481e54c50SWarner Losh20000622:
116581e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
116681e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
116781e54c50SWarner Losh	that used to be required when updating.
116881e54c50SWarner Losh
116939943833SWarner Losh20000621:
11702c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
11712a2f33fbSDaniel Baker	the config file update procedure.
11722a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1173c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
117459df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
117559df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
117639943833SWarner Losh
1177290f9ad8SWarner Losh20000620:
1178290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1179290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1180290f9ad8SWarner Losh	that workaround will no longer be required.
1181290f9ad8SWarner Losh
118290fb6346SWarner Losh20000615:
118390fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
118490fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
118590fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
118690fb6346SWarner Losh	devices.
118790fb6346SWarner Losh
1188f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1189f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1190f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1191f75f65bbSWarner Losh	may work).
1192f75f65bbSWarner Losh
1193ba26da8eSWarner Losh20000612:
1194ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1195290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1196c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1197290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1198f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1199f54a3542SWarner Losh	NEWCARD for examples of the new format.
1200290f9ad8SWarner Losh
12019698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
12029698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
12039698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
12049698f2c0SWarner Losh	in it.
1205bbcc5149SWarner Losh
1206d65850ebSWarner Losh20000522:
1207ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1208d65850ebSWarner Losh	building a kernel after this point is advised that they need
1209d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1210d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1211d65850ebSWarner Losh
1212d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1213d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1214d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1215d9583a00SWarner Losh	is resolved.
1216d9583a00SWarner Losh
12178039cedeSWarner Losh20000513:
12188039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
12198039cedeSWarner Losh
1220d65850ebSWarner Losh20000510:
12218039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
12228039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
12238039cedeSWarner Losh	is requires for the boot blocks to build properly.
12248039cedeSWarner Losh
12258039cedeSWarner Losh20000503:
12268039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
12278039cedeSWarner Losh	is now available.
12288039cedeSWarner Losh
1229d65850ebSWarner Losh20000502:
1230d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1231d65850ebSWarner Losh	connected to the kernel building instead.
1232d65850ebSWarner Losh
1233be149406SNik Clayton20000427:
12348039cedeSWarner Losh	You may need to build gperf
12358039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
12368039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
12378039cedeSWarner Losh	an option only in -current.
12388039cedeSWarner Losh
12392b8dd5f4SWarner Losh20000417:
12402b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1241f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
12422b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
12432b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
12442c021c6cSMark Ovens	before you reboot, you'll need to issue:
12452b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
12462b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
12472b8dd5f4SWarner Losh
12488d9f1945SWarner Losh20000320:
12492b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
12502b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
12512b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1252ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
12532b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
12548d9f1945SWarner Losh
1255f8ab1dd6SWarner Losh20000319:
1256f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1257f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1258f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1259f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1260f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1261f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1262f8ab1dd6SWarner Losh
126319cada77SWarner Losh20000318:
1264f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
126519cada77SWarner Losh	Large kernel changes are being committed and are in the
126619cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
126719cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
126819cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
126919cada77SWarner Losh	that you are loading are up to date.
1270ba228352SWarner Losh
127119cada77SWarner Losh20000315:
12726d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
12736d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
12746d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
12756d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
12766d23c382SWarner Losh	boot.
12776d23c382SWarner Losh
12786d23c382SWarner Losh20000315:
127919cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
128019cada77SWarner Losh	to upgrade to 4.0 from 3.x.
128157199806SWarner Losh
1282dc0dbf5cSWarner LoshCOMMON ITEMS:
1283dc0dbf5cSWarner Losh
1284a24eff53SWarner Losh	General Notes
1285a24eff53SWarner Losh	-------------
1286a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1287a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1288a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1289a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1290a24eff53SWarner Losh	or several minor releases, or when several months have passed
1291a24eff53SWarner Losh	on the -current branch).
1292a24eff53SWarner Losh
12935780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
12945780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
12955780f3baSWarner Losh	environment when searching for values for global variables.
12965780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
12975780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
12985780f3baSWarner Losh	page for more details.
12995780f3baSWarner Losh
1300dc0dbf5cSWarner Losh	To build a kernel
1301dc0dbf5cSWarner Losh	-----------------
1302ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1303f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1304ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1305282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1306282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1307dc0dbf5cSWarner Losh
1308ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1309ba01eb20SWarner Losh	--------------------------------------------------------------
1310ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
131147d0d01fSWarner Losh	config KERNEL_NAME_HERE
1312ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1313ba01eb20SWarner Losh	make depend
1314ba01eb20SWarner Losh	make
1315ba01eb20SWarner Losh	make install
1316ba01eb20SWarner Losh
1317ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1318ba01eb20SWarner Losh
1319ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1320ba01eb20SWarner Losh	-----------------------------------------------------------
132163cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
132263cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
132363cb445eSWarner Losh
1324f643de42SWarner Losh	<make sure you have good level 0 dumps>
132563cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
132663cb445eSWarner Losh	make buildworld
132763cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
132863cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
132963cb445eSWarner Losh							[1]
133063cb445eSWarner Losh	<reboot in single user>				[3]
133163cb445eSWarner Losh	mergemaster -p					[5]
133263cb445eSWarner Losh	make installworld
133363cb445eSWarner Losh	mergemaster					[4]
133463cb445eSWarner Losh	<reboot>
133563cb445eSWarner Losh
1336759f0aefSWarner Losh
1337f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1338f27b1fceSJoseph Koshy	--------------------------------------------------
1339f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1340f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1341f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1342f27b1fceSJoseph Koshy	# size.
1343f27b1fceSJoseph Koshy
1344f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1345f27b1fceSJoseph Koshy	<boot into -stable>
1346f27b1fceSJoseph Koshy	make buildworld
1347f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1348f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1349f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1350f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1351f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1352f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1353f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1354f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1355f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1356f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1357f27b1fceSJoseph Koshy	<reboot into current>
1358f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1359f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1360f27b1fceSJoseph Koshy 	<reboot>
1361f27b1fceSJoseph Koshy
1362f27b1fceSJoseph Koshy
1363f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1364f27b1fceSJoseph Koshy	----------------------------------------------
13655c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
13665c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
13675c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
13685c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1369ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1370f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1371f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1372f643de42SWarner Losh	# space on /.
1373f643de42SWarner Losh
1374f643de42SWarner Losh	<make sure you have good level 0 dumps>
1375fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
137621c075eaSWarner Losh	make buildworld					[9]
1377c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1378d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1379be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1380fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1381fc8c157fSWarner Losh							[1]
1382fc8c157fSWarner Losh	<reboot in single user>				[3]
1383835284beSWarner Losh	mergemaster -p					[5]
1384f8a4c901SWarner Losh	rm -rf /usr/include/g++
1385ba26da8eSWarner Losh	make installworld
1386a6cd4f9dSWarner Losh	mergemaster					[4]
1387ba26da8eSWarner Losh	<reboot>
1388ba26da8eSWarner Losh
1389fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1390fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1391fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1392fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1393fdb9f54dSWarner Losh	the UPDATING entries.
1394ba26da8eSWarner Losh
13951dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
13961dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
13971dece4a9SWarner Losh	your sources that you have read and understood all the recent
13981dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
13991dece4a9SWarner Losh	much fewer pitfalls.
14001dece4a9SWarner Losh
1401134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1402134d2e86SWarner Losh	should disable them at this point so they don't crash your
1403134d2e86SWarner Losh	system on reboot.
1404134d2e86SWarner Losh
14059c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
14069c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
14079c1a7444SWarner Losh	configuration.
14089c1a7444SWarner Losh
1409ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1410ee6e1fc3SWarner Losh		fsck -p
1411ee6e1fc3SWarner Losh		mount -u /
1412ee6e1fc3SWarner Losh		mount -a
1413ee6e1fc3SWarner Losh		cd /usr/src
141447d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1415f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1416f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1417b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1418b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1419b705ae10SWarner Losh	be ignored while you proceed to the next step.
1420ee6e1fc3SWarner Losh
1421a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1422a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1423a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1424a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1425a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1426a6cd4f9dSWarner Losh	for potential gotchas.
1427a6cd4f9dSWarner Losh
1428835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1429835284beSWarner Losh	you may need to do this if you get unknown user in the following
1430835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1431835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1432835284beSWarner Losh	install) after the buildworld before this step if you last updated
1433835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1434835284beSWarner Losh
1435bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1436bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1437bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1438bd79cf40SWarner Losh		ok unload
1439bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1440bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1441bd79cf40SWarner Losh	described here.
1442fc8c157fSWarner Losh
1443fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1444fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1445fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1446fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1447fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1448fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1449fc8c157fSWarner Losh
1450c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1451c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1452c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1453c74fe6afSWarner Losh	that is hard to boot to recover.
1454c74fe6afSWarner Losh
145521c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
145621c075eaSWarner Losh	cvs prune empty directories.
1457dc0dbf5cSWarner LoshFORMAT:
1458dc0dbf5cSWarner Losh
1459f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
14601fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1461f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1462f8ab1dd6SWarner Loshprevious releases if your system is older than this.
14631fc1a0dcSWarner Losh
1464e72fd46aSWarner LoshCopyright information:
1465e72fd46aSWarner Losh
14669698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1467e72fd46aSWarner Losh
1468772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1469772730c7SWarner Loshmodification, in full or in part, in any form or format of this
14709698f2c0SWarner Loshdocument are permitted without further permission from the author.
1471e72fd46aSWarner Losh
1472e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1473e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1474e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1475e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1476e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1477e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1478e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1479e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1480e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1481e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1482e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1483e72fd46aSWarner Losh
1484e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1485e72fd46aSWarner Loshauthor a beer.
1486e72fd46aSWarner Losh
148722306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1488772730c7SWarner Loshthis document.
1489772730c7SWarner Losh
149097d92980SPeter Wemm$FreeBSD$
1491