xref: /freebsd/UPDATING (revision aca89ee6024ed19831d8f11d9a8d957bffc983b1)
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
20aca89ee6SDaniel Eischen20040130:
21aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
22aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
23aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
24aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
25aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
26aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
27aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
28aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
29aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
30aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
31aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
32aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
33aca89ee6SDaniel Eischen	do not work with libpthread.
34aca89ee6SDaniel Eischen
3568b7b3a9SAlex Dupre20040125:
3668b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
3768b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
3868b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
3968b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
4068b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
4168b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
4268b7b3a9SAlex Dupre
43ce41f4bfSRobert Watson20031213:
44ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
45ce41f4bfSRobert Watson	if the login process is unable to successfully set the
46ce41f4bfSRobert Watson	process credentials to include all groups defined for the
47ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
48ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
49ce41f4bfSRobert Watson	defined, or they will be unable to log in.
50ce41f4bfSRobert Watson
51c124fa05SJohn Baldwin20031203:
52c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
53c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
54c124fa05SJohn Baldwin
558ad1f5e4SHartmut Brandt20031112:
5630093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
5730093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
5897209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
5997209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
6097209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
6197209ca3SRobert Watson	not know about the new system calls that support the new statfs
623f631d52SMarcel Moolenaar	structure.
633f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
643f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
653f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
663f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
673f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
683f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
693f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
703f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
713f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
723f631d52SMarcel Moolenaar	these changes are installed.
7330093b05SWarner Losh
7430093b05SWarner Losh	****************************DANGER*******************************
7530093b05SWarner Losh
7630093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
7730093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
7830093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
7930093b05SWarner Losh	kernel.
8064a18d6fSKirk McKusick
8164a18d6fSKirk McKusick20031112:
828ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
838ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
848ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
858ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
868ad1f5e4SHartmut Brandt	sync before rebooting.
878ad1f5e4SHartmut Brandt
88c53a5d8fSJohn Baldwin20031111:
89c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
90c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
91c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
92c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
93c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
94c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
95c53a5d8fSJohn Baldwin
968bf455a5SJohn Baldwin20031103:
978bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
988bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
992a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
1008bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
1018bf455a5SJohn Baldwin
1029bf40edeSBrooks Davis20031031:
1039bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
1049bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
1059bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
1069bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
1079bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
1089bf40edeSBrooks Davis	reflect this change.
1099bf40edeSBrooks Davis
11047a42c7aSPoul-Henning Kamp20030928:
11147a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
11247a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
11347a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
11447a42c7aSPoul-Henning Kamp
11507105342SMax Khon20030926:
11607105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
11707105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
11807105342SMax Khon
11917dcd026SSam Leffler20030925:
12017dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
12117dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
12217dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
12317dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
12417dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
12517dcd026SSam Leffler
126fedf1d01SBruce M Simpson20030923:
127fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
128fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
129fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
130fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
131fedf1d01SBruce M Simpson
132db38f9cbSJacques Vidrine20030915:
133db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
134db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
135db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
136db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
137db38f9cbSJacques Vidrine
138c09d2c2bSMike Makonnen20030829:
139c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
140c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
141c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
142c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
143c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
144c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
145c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
146c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
147c09d2c2bSMike Makonnen	may or may not exist on your system.
148c09d2c2bSMike Makonnen
14917c159dcSSøren Schmidt20030824:
15017c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
15117c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
152f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
153f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
15417c159dcSSøren Schmidt
155c1f61aa9SDavid E. O'Brien20030819:
156c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
157c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
158c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
159c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
16069f7bcf3SWarner Losh
16138c962e7SNate Lawson20030728:
16238c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
16338c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
16438c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
16538c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
16638c962e7SNate Lawson	so the quirk can be re-enabled.
16738c962e7SNate Lawson
168178cf4e9SWarner Losh20030722:
169178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
170178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
171178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
172178cf4e9SWarner Losh	FPU hardware.
173178cf4e9SWarner Losh
174178cf4e9SWarner Losh20030714:
175178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
176178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
177178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
178178cf4e9SWarner Losh	People should report those issues to current@.
179178cf4e9SWarner Losh
180157c629aSWarner Losh20030711:
181157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
1828b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
18305538fa9SWarner Losh	/usr/obj.
184157c629aSWarner Losh
1856cc6353fSMarcel Moolenaar20030613: [retrospective]
1866cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
1876cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
1886cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
1896cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
1906cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
1916cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
1926cc6353fSMarcel Moolenaar
1936cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
1946cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
1956cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
1966cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
1976cc6353fSMarcel Moolenaar		:
1986cc6353fSMarcel Moolenaar
1996cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
2006cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
2016cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
2026cc6353fSMarcel Moolenaar
203766c34e4SAndrey A. Chernov20030610:
204766c34e4SAndrey A. Chernov	Remove deprecated locale names and transition period code
205766c34e4SAndrey A. Chernov	for them, finishing switching to the new scheme. Check your
206766c34e4SAndrey A. Chernov	LANG environment variable.
207766c34e4SAndrey A. Chernov
2087ddc2528SPoul-Henning Kamp20030609:
209df622d54SPoul-Henning Kamp	CCD has been changed to be a fully GEOMified class.  Kernel
210df622d54SPoul-Henning Kamp	and ccdconfig(8) needs to be in sync, this is particularly
211df622d54SPoul-Henning Kamp	important to remember beforehand if your source tree is on
212df622d54SPoul-Henning Kamp	a ccd device.  Consider making a copy of the old ccdconfig
213df622d54SPoul-Henning Kamp	into /boot/kernel.good or wherever you keep your backup
214df622d54SPoul-Henning Kamp	kernel.
215df622d54SPoul-Henning Kamp
21652b47445SMark Murray20030505:
21752b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
21852b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
21952b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
22052b47445SMark Murray
221a26df538SWarner Losh20030502:
222a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
223a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
224a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
225a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
226a26df538SWarner Losh
2274b065e2cSDoug Barton20030501:
2284b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
2294b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
2304b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
2314b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
2324b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
2334b065e2cSDoug Barton	utilizes these old scripts has also been removed.
2344b065e2cSDoug Barton
23581cda3d9SWarner Losh20030423:
23681cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
23781cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
23881cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
23981cda3d9SWarner Losh	have until then to upgrade your kernel before updating
24081cda3d9SWarner Losh	userland.  In general, you should have a userland and
24181cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
24281cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
24381cda3d9SWarner Losh	allowances are made.
24481cda3d9SWarner Losh
24547a657d1SRuslan Ermilov20030329:
24647a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
24747a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
24847a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
24947a657d1SRuslan Ermilov
25047a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
25147a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
25247a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
25347a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
25447a657d1SRuslan Ermilov
25547a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
25647a657d1SRuslan Ermilov	    make cleandir && make obj && \
25747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
25847a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
25947a657d1SRuslan Ermilov
2605d2af00cSGregory Neil Shapiro20030208:
2615d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
2625d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
2635d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
2645d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
2655d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
2665d2af00cSGregory Neil Shapiro
2675d2af00cSGregory Neil Shapiro20030128:
2689db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
269ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
2709db58771SPoul-Henning Kamp	be removed when convenient.
2719db58771SPoul-Henning Kamp
2728d9b3f57SJake Burkholder20030126:
2738d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
2748d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
2758d9b3f57SJake Burkholder
2761c5efda5SJeff Roberson20030125:
2771c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
2781c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
279ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
2801c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
2811c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
2821c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
2831c5efda5SJeff Roberson
2849d1d64f5SWarner Losh20030115:
2859d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
2869d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
2879d1d64f5SWarner Losh	properly.
2889d1d64f5SWarner Losh
289c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
290c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
291c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
292c9fdb80aSWarner Losh	with NetBSD.
293c9fdb80aSWarner Losh
294161dc364SAlexander Kabaev20021222:
295161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
296161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
297161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
298161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
299161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
300161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
30184cc83efSAlexander Kabaev	rebuilt.
302161dc364SAlexander Kabaev
303fb4c8061SMartin Blapp20021216:
304fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
30589056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
306fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
3079d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
308fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
309fb4c8061SMartin Blapp
31017d47eb3SGiorgos Keramidas20021202:
31117d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
31217d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
31317d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
31417d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
31517d47eb3SGiorgos Keramidas
316a4459294SBill Fenner20021029:
317a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
318a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
319a4459294SBill Fenner	consumers in sync.
320a4459294SBill Fenner
321fc8c157fSWarner Losh20021024:
322c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
323c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
324c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
325c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
326c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
327c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
328c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
329c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
33069f7bcf3SWarner Losh
331fd9e8bdaSAndrew Gallatin20021023:
332fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
333fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
334fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
335fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
336fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
337fd9e8bdaSAndrew Gallatin
338fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
339fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
340fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
341fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
342fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
343fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
344fd9e8bdaSAndrew Gallatin
345f8a4c901SWarner Losh20020831:
346f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
347f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
348f8a4c901SWarner Losh	programs and libraries need to be recompiled.
349f8a4c901SWarner Losh
350f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
351f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
352f8a4c901SWarner Losh
353c2248fa2SJens Schweikhardt20020827:
354c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
355c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
356c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
357c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
358c2248fa2SJens Schweikhardt
3590d533e43SRuslan Ermilov20020815:
3600d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
3610d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
3620d533e43SRuslan Ermilov	again.
3630d533e43SRuslan Ermilov
36433c1de7dSRuslan Ermilov20020729:
36533c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
36633c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
36733c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
36833c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
36933c1de7dSRuslan Ermilov
3702b877facSJulian Elischer20020702:
3712b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
3722b877facSJulian Elischer	There are still some minor problems with some signals but the
3732b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
3742b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
3752b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
3762b877facSJulian Elischer
37706596d37SWarner Losh20020701:
37806596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
37906596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
38006596d37SWarner Losh	GNOME.
38106596d37SWarner Losh
38295ba4330SJacques Vidrine20020511:
38395ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
38495ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
38595ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
38695ba4330SJacques Vidrine	with the set-user-ID bit set.
38795ba4330SJacques Vidrine
388a81da3c9SDavid E. O'Brien20020510:
389f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
390f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
3914b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
392f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
393f50caf6fSDavid E. O'Brien
394f50caf6fSDavid E. O'Brien20020510:
395a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
396a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
397a81da3c9SDavid E. O'Brien	and then do a cvs update.
398a81da3c9SDavid E. O'Brien
399528a0ef5SJacques Vidrine20020421:
400528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
401528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
402528a0ef5SJacques Vidrine
40385aa5a2eSGregory Neil Shapiro20020404:
40485aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
40585aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
40685aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
40785aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
40885aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
40985aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
41085aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
41185aa5a2eSGregory Neil Shapiro
4128f1e4358SRuslan Ermilov20020403:
4138f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
4148f1e4358SRuslan Ermilov
4152292c02eSWarner Losh20020315:
4162292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
4172292c02eSWarner Losh
41869f7bcf3SWarner Losh20020225:
41969f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
42069f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
42169f7bcf3SWarner Losh
4228f35c493SWarner Losh20020217:
4238f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
4248f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
4258f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
4268f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
4278f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
4288f35c493SWarner Losh
429835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
430835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
431835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
432835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
433835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
434835284beSWarner Losh	and group must be merged from src/etc/group and
435835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
436835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
437835284beSWarner Losh	mergemaster before this will work if you are updating from a
438835284beSWarner Losh	very old version of current.  The updating recipe has changed
439835284beSWarner Losh	as of this date.
440835284beSWarner Losh
441fa9401c1SWarner Losh20020112:
442fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
443fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
444fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
445fa9401c1SWarner Losh	you have local modifications, you can use
446fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
447fa9401c1SWarner Losh	/etc/pam.d.
448fa9401c1SWarner Losh
449fa9401c1SWarner Losh	Please see the following url for more details:
450fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
45147d0d01fSWarner Losh20011229:
45247d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
45347d0d01fSWarner Losh	networkfs_types, please note that it has changed
45447d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
45547d0d01fSWarner Losh
456514318a8SWarner Losh20011220:
457514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
458514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
459514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
460514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
461514318a8SWarner Losh	version have now been merged back into the base system's
462514318a8SWarner Losh	version now.  The only user-visible change resulting from this
463514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
464514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
465514318a8SWarner Losh	as well.  (There has never been rc file support for
466514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
467514318a8SWarner Losh	reverted by the time the changes are MFCed.)
468514318a8SWarner Losh
469514318a8SWarner Losh20011215:
470514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
471514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
472514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
473514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
474514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
475514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
476514318a8SWarner Losh	will need to be customized then for `odd' densities using
477514318a8SWarner Losh	fdcontrol(8).
478514318a8SWarner Losh
4792d22e2bfSWarner Losh20011209:
4802d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
4812d22e2bfSWarner Losh	and truss(1) now works again.
4822d22e2bfSWarner Losh
4839e0428e2SWarner Losh20011207:
4849e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
4859e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
4869e0428e2SWarner Losh	see
4879e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
4889e0428e2SWarner Losh	for details.
4899e0428e2SWarner Losh
4909bab8c59SWarner Losh20011204:
4919bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
4929bab8c59SWarner Losh	kernel and burncd to be in sync.
4939bab8c59SWarner Losh
494e57d8b01SWarner Losh20011203:
495e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
496e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
497e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
498e57d8b01SWarner Losh	not there already.
499e57d8b01SWarner Losh
500e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
501e57d8b01SWarner Losh	until the issue has been resolved.
502e57d8b01SWarner Losh
503b001d36fSJacques Vidrine20011202:
504b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
505b001d36fSJacques Vidrine	patched.
506b001d36fSJacques Vidrine
5074b676ec1SWarner Losh20011126:
5084b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
5095ebbf43eSWarner Losh	after this date.  You need to do this only once.
5104b676ec1SWarner Losh
511d961e462SWarner Losh20011103:
512d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
513d961e462SWarner Losh	edges may be left, but for the most part things should be
5144b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
515d961e462SWarner Losh
516d961e462SWarner Losh20011030:
517d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
518d961e462SWarner Losh	choppy waves in the upgrade process.
519d961e462SWarner Losh
5201fe003b6SWarner Losh20011030:
521a4b6fda0SWarner Losh	The asr driver problem has been resolved.
5221fe003b6SWarner Losh
5231fe003b6SWarner Losh20011027:
5241fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
5251fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
5261fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
5271fe003b6SWarner Losh	try to use from this date forward.
5281fe003b6SWarner Losh
5291fe003b6SWarner Losh20011025:
5301fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
5311fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
5321fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
5331fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
5341fe003b6SWarner Losh	TARGET_ARCH=i386.
5351fe003b6SWarner Losh
536d05f9643SWarner Losh20011001:
537d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
538d05f9643SWarner Losh	You must recompile both the kernel and userland applications
539d05f9643SWarner Losh	at the same time.
540d05f9643SWarner Losh
54158970f85SWarner Losh20010929:
54258970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
54358970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
54458970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
54558970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
5469d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
54758970f85SWarner Losh
54858970f85SWarner Losh20010927:
54958970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
55058970f85SWarner Losh	To disable ACPI you can add
55166ff0e67SMax Khon		hint.acpi.0.disabled="1"
55258970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
55358970f85SWarner Losh	loader "ok" prompt).
55458970f85SWarner Losh
55558970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
55658970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
55758970f85SWarner Losh	file and not list acpi in that list.
558378f4486SAlfred Perlstein
5595119d237SWarner Losh20010924:
5605119d237SWarner Losh	The buildworld has been fixed.  You may need to install
5615119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
5628b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
5638b039fffSWarner Losh	get them installed on every installworld, or execute the
5648b039fffSWarner Losh	following to get them installed only once:
5658b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
56658970f85SWarner Losh		make all install
5678b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
5685119d237SWarner Losh
5693c293725SWarner Losh20010919:
5703c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
5713c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
5723c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
573772730c7SWarner Losh	workaround is to add
5743c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
5753c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
5763c293725SWarner Losh	can be removed afterwards.
5773c293725SWarner Losh
5783c293725SWarner Losh	A proper fix to the buildworld target is needed.
5793c293725SWarner Losh
5803c293725SWarner Losh20010918:
5813c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
5823c293725SWarner Losh	NFS may be unstable after this date.
5833c293725SWarner Losh
5843c293725SWarner Losh20010912:
5853c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
5863c293725SWarner Losh	the kernel.  While a few problems were introduced in the
5873c293725SWarner Losh	initial commit, most of the major ones have been found and
5883c293725SWarner Losh	corrected.
5893c293725SWarner Losh
5903c293725SWarner Losh20010901:
5913c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
5923c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
5933c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
5943c293725SWarner Losh	have been rectified around this date.
5953c293725SWarner Losh
59698b17b95SWarner Losh20010823:
59798b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
59898b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
59998b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
60098b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
60198b17b95SWarner Losh 	sure that user or group bind has read (and not write)
60298b17b95SWarner Losh 	permission for your name server configuration and that it
60398b17b95SWarner Losh 	has read and write permission for your slave zone files and
60498b17b95SWarner Losh 	directory.
60598b17b95SWarner Losh
60698b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
60798b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
60898b17b95SWarner Losh
60998b17b95SWarner Losh 		named_flags=
61098b17b95SWarner Losh
6117b9786edSMark Murray20010709:
6127b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
6137b9786edSMark Murray	the ability of the shared library major number to handle.
6147b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
6157b9786edSMark Murray	solution is to rebuild those ports.
6167b9786edSMark Murray
6171d28950eSWarner Losh20010628:
6181d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
6191d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
6201d28950eSWarner Losh
621e72fd46aSWarner Losh20010625:
62298b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
62398b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
62498b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
62598b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
62698b17b95SWarner Losh	IRQ configuration needs more safety belts.
62716de1a07SWarner Losh
6280d415dffSWarner Losh20010617:
629e72fd46aSWarner Losh	Softupdates problems have been corrected.
6300d415dffSWarner Losh
6310d415dffSWarner Losh20010614:
6320d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
6330d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
6340d415dffSWarner Losh	kernel building methods.
6350d415dffSWarner Losh
6368b9959adSWarner Losh20010613:
6378b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
6388b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
639e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
640e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
6418b9959adSWarner Losh
642e72fd46aSWarner Losh20010613:
6438b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
644e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
645e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
6468b9959adSWarner Losh
6470d415dffSWarner Losh20010612:
6480d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
6490d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
6500d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
6510d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
6520d415dffSWarner Losh	until this bug is fixed.
6530d415dffSWarner Losh
654e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
655e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
656ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
657e72fd46aSWarner Losh
6580d415dffSWarner Losh20010610:
6590d415dffSWarner Losh	Locale names have changed to match other systems better.
6600d415dffSWarner Losh
6616ccdb5e4SWarner Losh20010604:
6626ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
6636ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
6646ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
6653590182eSWarner Losh	Interrupt storms look a lot like a hang.
6663590182eSWarner Losh
6673590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
6683590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
6693590182eSWarner Losh	it is).
6703590182eSWarner Losh
6713590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
6723590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
6733590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
6743590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
6756ccdb5e4SWarner Losh
6760bc62786SWarner Losh20010530:
6770bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
6780bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
6790bc62786SWarner Losh	a limited time.  If you see
6800bc62786SWarner Losh
6810bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
6820bc62786SWarner Losh
6830bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
6840bc62786SWarner Losh	COPY=-C.
6850bc62786SWarner Losh
68668a38c6cSWarner Losh20010525:
687b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
688c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
689c4f4a728SWarner Losh	definitely is in bad shape.
69068a38c6cSWarner Losh
691ed0f29caSWarner Losh20010521:
692ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
693ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
694ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
695ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
696ed0f29caSWarner Losh	is
697ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
698ed0f29caSWarner Losh
69980c16af9SWarner Losh20010520:
70068a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
70180c16af9SWarner Losh
70280c16af9SWarner Losh20010519:
70380c16af9SWarner Losh	pccard has had much reorganizational work done to it over
70480c16af9SWarner Losh	the past few days.  Everything should still work, but if
70580c16af9SWarner Losh	not, please contact imp@freebsd.org.
70680c16af9SWarner Losh
707a45f2d05SWarner Losh20010517:
708a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
709a45f2d05SWarner Losh	userland at the same time.
710a45f2d05SWarner Losh
711a45f2d05SWarner Losh20010517:
712a45f2d05SWarner Losh	New ncurses imported.
713a45f2d05SWarner Losh
7142988afcaSWarner Losh20010512:
7152988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
7162988afcaSWarner Losh	will be the only way to go starting July 1.
7172988afcaSWarner Losh
7181a33dba7SWarner Losh20010504:
7191a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
7201a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
7211a33dba7SWarner Losh
72209946a51SWarner Losh20010502:
72309946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
72409946a51SWarner Losh
72509946a51SWarner Losh20010501:
72609946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
72709946a51SWarner Losh
72809946a51SWarner Losh20010430:
729a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
73009946a51SWarner Losh	go back in the water.
73109946a51SWarner Losh
73209946a51SWarner Losh20010429:
73309946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
73409946a51SWarner Losh	this date, but before the correction date.
73509946a51SWarner Losh
73691dd3b53SWarner Losh20010423:
73791dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
73891dd3b53SWarner Losh
73991dd3b53SWarner Losh20010411:
74091dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
74191dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
74291dd3b53SWarner Losh	Update only if you understand that you must not use the old
74391dd3b53SWarner Losh	fsck with the new kernel ever.
74491dd3b53SWarner Losh
745933b3269SWarner Losh20010330:
746933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
747c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
748933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
749933b3269SWarner Losh
750933b3269SWarner Losh20010319:
751933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
752933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
753933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
754f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
75509946a51SWarner Losh
75609946a51SWarner Losh20010315:
75709946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
758ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
75909946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
760933b3269SWarner Losh
761933b3269SWarner Losh20010312:
762933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
763933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
764933b3269SWarner Losh
765933b3269SWarner Losh20010312:
766933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
767933b3269SWarner Losh	instead of ad-hoc.
768933b3269SWarner Losh
769933b3269SWarner Losh20010310:
770f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
771933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
772933b3269SWarner Losh	ssh might not work if you don't.
773933b3269SWarner Losh
77462353691SWarner Losh20010303:
77562353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
77662353691SWarner Losh	which means that you must include the miibus in your kernel if
77762353691SWarner Losh	you use the ed driver.
77862353691SWarner Losh
779d325cf65SWarner Losh20010220:
780d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
781d325cf65SWarner Losh	safe to go back into the water.
782d325cf65SWarner Losh
783024daae6SWarner Losh20010211:
784024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
785024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
786024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
787024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
788024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
789024daae6SWarner Losh
790024daae6SWarner Losh	To get to the new system, you'll need to use the following
791024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
792024daae6SWarner Losh	don't have to move this to the updating section.
793024daae6SWarner Losh
794024daae6SWarner Losh	To get around the installworld problem, do:
795024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
796024daae6SWarner Losh		# make install
797024daae6SWarner Losh		# cd /usr/src
798024daae6SWarner Losh		# make installworld
799024daae6SWarner Losh	If that doesn't work, then try:
800024daae6SWarner Losh		# make -k installworld
801024daae6SWarner Losh		# make installworld
802024daae6SWarner Losh
803024daae6SWarner Losh20010207:
804024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
805024daae6SWarner Losh	do not include devfs in your kernel as problems result.
806024daae6SWarner Losh
807024daae6SWarner Losh20010205:
8087595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
809024daae6SWarner Losh	Remove them from your config.
810024daae6SWarner Losh
8111e159248SWarner Losh20010122:
8121e159248SWarner Losh	****************************** WARNING ******************************
8131e159248SWarner Losh			buildkernel has been changed slightly
8141e159248SWarner Losh	****************************** WARNING ******************************
8151e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
8161e159248SWarner Losh	should update your scripts and make.conf accordingly.
8171e159248SWarner Losh
8181e159248SWarner Losh20010119:
8191e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
8201e159248SWarner Losh	This requires a new config to build correctly.
8211e159248SWarner Losh
822aac7dfeaSWarner Losh20010116:
823ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
824aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
825aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
826aac7dfeaSWarner Losh
827aac7dfeaSWarner Losh20010110:
828aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
829aac7dfeaSWarner Losh
830aac7dfeaSWarner Losh20010102:
831aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
832aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
833aac7dfeaSWarner Losh
83463c90c9eSWarner Losh20010101:
83563c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
83663c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
8375fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
83863c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
83963c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
84063c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
84163c90c9eSWarner Losh	might have been ignored by the -k option.
84263c90c9eSWarner Losh
8435fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
8445fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
8455fd2a895SWarner Losh	of this working.
8465fd2a895SWarner Losh
847aac7dfeaSWarner Losh20001228:
848aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
849ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
850aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
851aac7dfeaSWarner Losh
852de2bcc63SWarner Losh20001218:
853de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
854de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
855de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
856de2bcc63SWarner Losh	cards will not be recognized without it.
857de2bcc63SWarner Losh
858960773f7SWarner Losh20001205:
859960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
860960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
861960773f7SWarner Losh	adding the following in pam.conf:
862960773f7SWarner Losh
863960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
864960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
865960773f7SWarner Losh	sshd    session required        pam_permit.so
866960773f7SWarner Losh
8670acc635eSWarner Losh20001031:
8680acc635eSWarner Losh	cvs updated to 1.11.
8690acc635eSWarner Losh
8700acc635eSWarner Losh20001020:
8710acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
8720acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
8730acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
8740acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
8750acc635eSWarner Losh	workaround.
8760acc635eSWarner Losh
8770acc635eSWarner Losh20001010:
8780acc635eSWarner Losh	****************************** WARNING ******************************
8790acc635eSWarner Losh				Sendmail has been updated.
8800acc635eSWarner Losh	****************************** WARNING ******************************
8810acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
8820acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
8830acc635eSWarner Losh	  is set.
8840acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
8850acc635eSWarner Losh	  commands.
8860acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
8870acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
8880acc635eSWarner Losh	  in /usr/share/sendmail/cf.
8890acc635eSWarner Losh	o sendmail.cw changed to local-host-names
8900acc635eSWarner Losh
8910acc635eSWarner Losh	More details can be found at
8920acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
8930acc635eSWarner Losh
8946e98a146SWarner Losh20001009:
8956e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
8966e98a146SWarner Losh	your entire ports tree, or you will have problems.
8976e98a146SWarner Losh
8986e98a146SWarner Losh20001006:
899685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
9006e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
9016e98a146SWarner Losh	/usr/bin/miniperl.
9026e98a146SWarner Losh
903073113a4SWarner Losh20001005:
904073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
905685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
906073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
907073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
908073113a4SWarner Losh	tree for anything to work.
909073113a4SWarner Losh
9100acc635eSWarner Losh20000928:
9110acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
9120acc635eSWarner Losh
913be3885b3SWarner Losh20000916:
914be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
915be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
916be3885b3SWarner Losh	same time as your kernel.
917be3885b3SWarner Losh
91876ec9675SWarner Losh20000914:
91976ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
92076ec9675SWarner Losh	include the device will cause suspended laptops losing time
92176ec9675SWarner Losh	when they resume.  Include
92276ec9675SWarner Losh		device		pmtimer
92376ec9675SWarner Losh	in your config file and
92401b9a434SWarner Losh		hint.pmtimer.0.at="isa"
92576ec9675SWarner Losh	to your /boot/device.hints file.
92676ec9675SWarner Losh
927f4865386SMark Murray20000911:
928f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
929f4865386SMark Murray	rather than an option. The supplied kernel config files have
930f4865386SMark Murray	been updated. You will need to do something similar in your
931f4865386SMark Murray	own kernel config file.
932f4865386SMark Murray	Remove:
933f4865386SMark Murray		options		RANDOMDEV
934f4865386SMark Murray	Add:
935f4865386SMark Murray		device		random
936f4865386SMark Murray	If you prefer to load the loadable module, you need to do
937f4865386SMark Murray	nothing.
938f4865386SMark Murray
939d594498fSWarner Losh20000909:
940d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
941d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
942d594498fSWarner Losh	reflect this if you load this module at boot time.
943d594498fSWarner Losh	The line should read:
944d594498fSWarner Losh		random_load="YES"
945d594498fSWarner Losh
9460deb7ddcSWarner Losh20000907:
9470deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
94816eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
94916eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
95016eb772dSWarner Losh	sure you don't have model loading problems which might at
95116eb772dSWarner Losh	first blush appear related to SMP.
95252bf24e7SWarner Losh
9535a01880bSWarner Losh20000906:
9545a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
9555a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
9565a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
9575a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
9585a01880bSWarner Losh	don't have one, and you have host.conf.
9595a01880bSWarner Losh
9602b41163cSWarner Losh20000905:
96138d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
96238d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
96338d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
96438d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
96538d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
96638d6ecd2SWarner Losh
96738d6ecd2SWarner Losh20000905:
9688aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
9698aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
9708aab4bc7SWarner Losh	is /boot/kernel.
9718aab4bc7SWarner Losh
9728aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
97338d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
97438d6ecd2SWarner Losh	installkernel/installworld dance.
9752b41163cSWarner Losh
976d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
977d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
978d594498fSWarner Losh	modules in that directory instead of finding them in the correct
979d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
980d594498fSWarner Losh	is that the linux module crashes your machine after the update.
981d594498fSWarner Losh
982d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
983d594498fSWarner Losh		mv /modules.old /boot/kernel.old
984d594498fSWarner Losh		chflags noschg /kernel.old
985d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
986d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
987d594498fSWarner Losh	fi
988d594498fSWarner Losh
989c22a309cSWarner Losh20000904:
990c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
991c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
992c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
993c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
994c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
995c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
996c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
997c22a309cSWarner Losh	is not likely to be generated.
998c22a309cSWarner Losh
999fdb9f54dSWarner Losh20000825:
1000fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
10019c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
10029c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
10039c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
10049c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
10059c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
10069c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
10079c1a7444SWarner Losh	kernel.
10089c1a7444SWarner Losh
10099c1a7444SWarner Losh20000821:
10109c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
10119c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
10129c1a7444SWarner Losh	/boot/loader.conf.
1013fdb9f54dSWarner Losh
10148f250aa7SWarner Losh20000812:
10155da0d091SWarner Losh	suidperl is now always built and installed on the system, but
10165da0d091SWarner Losh	with permissions of 511.  If you have applications that use
10175da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
10185da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
10195da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
10205da0d091SWarner Losh	will fix this until the next build.
10215da0d091SWarner Losh
10225da0d091SWarner Losh20000812:
10238f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
10248f250aa7SWarner Losh	visible changes that may immediately affect your configuration
10258f250aa7SWarner Losh	include:
10268f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
10278f250aa7SWarner Losh	- newaliases limited to root and trusted users
10288f250aa7SWarner Losh	- MSA port (587) turned on by default
10298f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
10308f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
10318f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
10328f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
10338f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
10348f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
10358f250aa7SWarner Losh
103671c38472SWarner Losh20000810:
103771c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
103871c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
103971c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
104071c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
104171c38472SWarner Losh	specific use for it.
104271c38472SWarner Losh
104371c38472SWarner Losh20000729:
104471c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
104571c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
104671c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
104771c38472SWarner Losh	afterwards (unless the variables already are set, of course):
104871c38472SWarner Losh		# Enable network daemons for user convenience.
104971c38472SWarner Losh		inetd_enable="YES"
105071c38472SWarner Losh		portmap_enable="YES"
105171c38472SWarner Losh		sendmail_enable="YES"
105271c38472SWarner Losh
105371c38472SWarner Losh20000728:
105471c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
105571c38472SWarner Losh	will need to change that to nullfs_load="YES".
105671c38472SWarner Losh
10571dece4a9SWarner Losh20000728:
10581dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
10591dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
10601dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
10611dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
10621dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
10631dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
10641dece4a9SWarner Losh	to /MYKERNEL.
10651dece4a9SWarner Losh
1066409e887cSWarner Losh20000711:
1067409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1068409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1069409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1070409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1071409e887cSWarner Losh	for details on potential problems that you might have and how
1072409e887cSWarner Losh	to get around them.
1073409e887cSWarner Losh
1074409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1075409e887cSWarner Losh	clauses above, you needn't worry.
1076409e887cSWarner Losh
1077409e887cSWarner Losh20000711:
1078409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1079409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1080409e887cSWarner Losh	in the number of changed programs the first time when you run
1081409e887cSWarner Losh	mergemaster to get a new /etc/security.
1082409e887cSWarner Losh
1083673d13f2SWarner Losh20000710:
1084673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1085673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1086673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1087673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1088673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1089673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1090673d13f2SWarner Losh	errors. (see below, 20000624).
1091673d13f2SWarner Losh
1092bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
10931dece4a9SWarner Losh
1094673d13f2SWarner Losh20000709:
1095c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1096c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1097c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1098673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1099673d13f2SWarner Losh
1100e98e26cdSWarner Losh20000706:
1101e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1102e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1103e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1104f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1105e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
11062c021c6cSMark Ovens	interim if needed.
1107e98e26cdSWarner Losh
1108e98e26cdSWarner Losh20000705:
1109e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1110e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1111e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1112e98e26cdSWarner Losh	details.
1113e98e26cdSWarner Losh
1114c373950eSWarner Losh20000704:
11152f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
11162f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
11172f961bc8SWarner Losh
11182f961bc8SWarner Losh20000704:
1119c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1120c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1121c373950eSWarner Losh	rc.d scripts that haven't been updated.
1122c373950eSWarner Losh
112327dc3a2bSWarner Losh20000630:
112427dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
112527dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
112627dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
112727dc3a2bSWarner Losh
1128b8c215acSWarner Losh20000625:
1129b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
113027dc3a2bSWarner Losh	system installed in order to build the system and kernel.
113127dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
113227dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
113327dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
113427dc3a2bSWarner Losh	were required.  You should check with the latest collections
113527dc3a2bSWarner Losh	to make sure that these haven't changed.
1136b8c215acSWarner Losh
11377b990719SWarner Losh20000624:
11387b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
11397b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
11407b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
11411a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
11427b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
11437b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
11447b990719SWarner Losh	date to the completion of the work.
11457b990719SWarner Losh
114627dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
114727dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
114827dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
114927dc3a2bSWarner Losh	recreate the random and urandom devices.
115027dc3a2bSWarner Losh
115181e54c50SWarner Losh20000622:
115281e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
115381e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
115481e54c50SWarner Losh	that used to be required when updating.
115581e54c50SWarner Losh
115639943833SWarner Losh20000621:
11572c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
11582a2f33fbSDaniel Baker	the config file update procedure.
11592a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1160c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
116159df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
116259df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
116339943833SWarner Losh
1164290f9ad8SWarner Losh20000620:
1165290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1166290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1167290f9ad8SWarner Losh	that workaround will no longer be required.
1168290f9ad8SWarner Losh
116990fb6346SWarner Losh20000615:
117090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
117190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
117290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
117390fb6346SWarner Losh	devices.
117490fb6346SWarner Losh
1175f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1176f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1177f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1178f75f65bbSWarner Losh	may work).
1179f75f65bbSWarner Losh
1180ba26da8eSWarner Losh20000612:
1181ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1182290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1183c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1184290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1185f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1186f54a3542SWarner Losh	NEWCARD for examples of the new format.
1187290f9ad8SWarner Losh
11889698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
11899698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
11909698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
11919698f2c0SWarner Losh	in it.
1192bbcc5149SWarner Losh
1193d65850ebSWarner Losh20000522:
1194ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1195d65850ebSWarner Losh	building a kernel after this point is advised that they need
1196d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1197d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1198d65850ebSWarner Losh
1199d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1200d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1201d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1202d9583a00SWarner Losh	is resolved.
1203d9583a00SWarner Losh
12048039cedeSWarner Losh20000513:
12058039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
12068039cedeSWarner Losh
1207d65850ebSWarner Losh20000510:
12088039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
12098039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
12108039cedeSWarner Losh	is requires for the boot blocks to build properly.
12118039cedeSWarner Losh
12128039cedeSWarner Losh20000503:
12138039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
12148039cedeSWarner Losh	is now available.
12158039cedeSWarner Losh
1216d65850ebSWarner Losh20000502:
1217d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1218d65850ebSWarner Losh	connected to the kernel building instead.
1219d65850ebSWarner Losh
1220be149406SNik Clayton20000427:
12218039cedeSWarner Losh	You may need to build gperf
12228039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
12238039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
12248039cedeSWarner Losh	an option only in -current.
12258039cedeSWarner Losh
12262b8dd5f4SWarner Losh20000417:
12272b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1228f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
12292b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
12302b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
12312c021c6cSMark Ovens	before you reboot, you'll need to issue:
12322b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
12332b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
12342b8dd5f4SWarner Losh
12358d9f1945SWarner Losh20000320:
12362b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
12372b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
12382b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1239ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
12402b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
12418d9f1945SWarner Losh
1242f8ab1dd6SWarner Losh20000319:
1243f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1244f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1245f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1246f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1247f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1248f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1249f8ab1dd6SWarner Losh
125019cada77SWarner Losh20000318:
1251f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
125219cada77SWarner Losh	Large kernel changes are being committed and are in the
125319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
125419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
125519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
125619cada77SWarner Losh	that you are loading are up to date.
1257ba228352SWarner Losh
125819cada77SWarner Losh20000315:
12596d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
12606d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
12616d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
12626d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
12636d23c382SWarner Losh	boot.
12646d23c382SWarner Losh
12656d23c382SWarner Losh20000315:
126619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
126719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
126857199806SWarner Losh
1269dc0dbf5cSWarner LoshCOMMON ITEMS:
1270dc0dbf5cSWarner Losh
1271a24eff53SWarner Losh	General Notes
1272a24eff53SWarner Losh	-------------
1273a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1274a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1275a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1276a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1277a24eff53SWarner Losh	or several minor releases, or when several months have passed
1278a24eff53SWarner Losh	on the -current branch).
1279a24eff53SWarner Losh
12805780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
12815780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
12825780f3baSWarner Losh	environment when searching for values for global variables.
12835780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
12845780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
12855780f3baSWarner Losh	page for more details.
12865780f3baSWarner Losh
1287dc0dbf5cSWarner Losh	To build a kernel
1288dc0dbf5cSWarner Losh	-----------------
1289ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1290f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1291ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1292282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1293282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1294dc0dbf5cSWarner Losh
1295ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1296ba01eb20SWarner Losh	--------------------------------------------------------------
1297ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
129847d0d01fSWarner Losh	config KERNEL_NAME_HERE
1299ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1300ba01eb20SWarner Losh	make depend
1301ba01eb20SWarner Losh	make
1302ba01eb20SWarner Losh	make install
1303ba01eb20SWarner Losh
1304ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1305ba01eb20SWarner Losh
1306ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1307ba01eb20SWarner Losh	-----------------------------------------------------------
130863cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
130963cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
131063cb445eSWarner Losh
1311f643de42SWarner Losh	<make sure you have good level 0 dumps>
131263cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
131363cb445eSWarner Losh	make buildworld
131463cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
131563cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
131663cb445eSWarner Losh							[1]
131763cb445eSWarner Losh	<reboot in single user>				[3]
131863cb445eSWarner Losh	mergemaster -p					[5]
131963cb445eSWarner Losh	make installworld
132063cb445eSWarner Losh	mergemaster					[4]
132163cb445eSWarner Losh	<reboot>
132263cb445eSWarner Losh
1323759f0aefSWarner Losh
1324f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1325f27b1fceSJoseph Koshy	--------------------------------------------------
1326f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1327f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1328f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1329f27b1fceSJoseph Koshy	# size.
1330f27b1fceSJoseph Koshy
1331f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1332f27b1fceSJoseph Koshy	<boot into -stable>
1333f27b1fceSJoseph Koshy	make buildworld
1334f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1335f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1336f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1337f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1338f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1339f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1340f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1341f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1342f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1343f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1344f27b1fceSJoseph Koshy	<reboot into current>
1345f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1346f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1347f27b1fceSJoseph Koshy 	<reboot>
1348f27b1fceSJoseph Koshy
1349f27b1fceSJoseph Koshy
1350f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1351f27b1fceSJoseph Koshy	----------------------------------------------
13525c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
13535c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
13545c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
13555c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1356ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1357f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1358f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1359f643de42SWarner Losh	# space on /.
1360f643de42SWarner Losh
1361f643de42SWarner Losh	<make sure you have good level 0 dumps>
1362fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
136321c075eaSWarner Losh	make buildworld					[9]
1364c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1365d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1366be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1367fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1368fc8c157fSWarner Losh							[1]
1369fc8c157fSWarner Losh	<reboot in single user>				[3]
1370835284beSWarner Losh	mergemaster -p					[5]
1371f8a4c901SWarner Losh	rm -rf /usr/include/g++
1372ba26da8eSWarner Losh	make installworld
1373a6cd4f9dSWarner Losh	mergemaster					[4]
1374ba26da8eSWarner Losh	<reboot>
1375ba26da8eSWarner Losh
1376fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1377fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1378fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1379fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1380fdb9f54dSWarner Losh	the UPDATING entries.
1381ba26da8eSWarner Losh
13821dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
13831dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
13841dece4a9SWarner Losh	your sources that you have read and understood all the recent
13851dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
13861dece4a9SWarner Losh	much fewer pitfalls.
13871dece4a9SWarner Losh
1388134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1389134d2e86SWarner Losh	should disable them at this point so they don't crash your
1390134d2e86SWarner Losh	system on reboot.
1391134d2e86SWarner Losh
13929c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
13939c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
13949c1a7444SWarner Losh	configuration.
13959c1a7444SWarner Losh
1396ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1397ee6e1fc3SWarner Losh		fsck -p
1398ee6e1fc3SWarner Losh		mount -u /
1399ee6e1fc3SWarner Losh		mount -a
1400ee6e1fc3SWarner Losh		cd /usr/src
140147d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1402f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1403f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1404b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1405b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1406b705ae10SWarner Losh	be ignored while you proceed to the next step.
1407ee6e1fc3SWarner Losh
1408a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1409a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1410a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1411a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1412a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1413a6cd4f9dSWarner Losh	for potential gotchas.
1414a6cd4f9dSWarner Losh
1415835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1416835284beSWarner Losh	you may need to do this if you get unknown user in the following
1417835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1418835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1419835284beSWarner Losh	install) after the buildworld before this step if you last updated
1420835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1421835284beSWarner Losh
1422bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1423bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1424bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1425bd79cf40SWarner Losh		ok unload
1426bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1427bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1428bd79cf40SWarner Losh	described here.
1429fc8c157fSWarner Losh
1430fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1431fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1432fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1433fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1434fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1435fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1436fc8c157fSWarner Losh
1437c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1438c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1439c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1440c74fe6afSWarner Losh	that is hard to boot to recover.
1441c74fe6afSWarner Losh
144221c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
144321c075eaSWarner Losh	cvs prune empty directories.
1444dc0dbf5cSWarner LoshFORMAT:
1445dc0dbf5cSWarner Losh
1446f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
14471fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1448f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1449f8ab1dd6SWarner Loshprevious releases if your system is older than this.
14501fc1a0dcSWarner Losh
1451e72fd46aSWarner LoshCopyright information:
1452e72fd46aSWarner Losh
14539698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1454e72fd46aSWarner Losh
1455772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1456772730c7SWarner Loshmodification, in full or in part, in any form or format of this
14579698f2c0SWarner Loshdocument are permitted without further permission from the author.
1458e72fd46aSWarner Losh
1459e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1460e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1461e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1462e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1463e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1464e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1465e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1466e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1467e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1468e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1469e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1470e72fd46aSWarner Losh
1471e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1472e72fd46aSWarner Loshauthor a beer.
1473e72fd46aSWarner Losh
147422306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1475772730c7SWarner Loshthis document.
1476772730c7SWarner Losh
147797d92980SPeter Wemm$FreeBSD$
1478