xref: /freebsd/UPDATING (revision 3aff5d0603e3e93a7f56c85914f6da5e4b707a19)
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
203aff5d06SDag-Erling Smørgrav20040303:
213aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
223aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
233aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
243aff5d06SDag-Erling Smørgrav
253aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
263aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
273aff5d06SDag-Erling Smørgrav
283aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
293aff5d06SDag-Erling Smørgrav	to use libpthread instead.
303aff5d06SDag-Erling Smørgrav
31fd63c5b3SDag-Erling Smørgrav20040226:
329d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
33fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
34fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
35fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
36fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
37fd63c5b3SDag-Erling Smørgrav
38714ae42aSBruce M Simpson20040225:
39e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
40e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
41e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
42e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
43e07a40f3SBrian Feldman	should remain unaffected.
44e07a40f3SBrian Feldman
45e07a40f3SBrian Feldman20040225:
46714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
47714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
48714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
49714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
50714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
51714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
52714ae42aSBruce M Simpson
53fbd2e692SAndre Oppermann20040224:
54fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
55fbd2e692SAndre Oppermann	and related userland network utilities neccessary.
56fbd2e692SAndre Oppermann
57158b90daSWarner Losh20040222:
58158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
59158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
60158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
61158b90daSWarner Losh	Drivers outside the tree will need to be updated.
62158b90daSWarner Losh
63b7b1e150SMike Makonnen20040207:
64b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
65b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
66b7b1e150SMike Makonnen
67aca89ee6SDaniel Eischen20040130:
68aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
69aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
70aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
71aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
72aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
73aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
74aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
75aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
76aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
77aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
78aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
79aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
80aca89ee6SDaniel Eischen	do not work with libpthread.
81aca89ee6SDaniel Eischen
8268b7b3a9SAlex Dupre20040125:
8368b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
8468b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
8568b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
8668b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
8768b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
8868b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
8968b7b3a9SAlex Dupre
90ff46e0deSWarner Losh20040125:
91ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
92ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
93ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
94ff46e0deSWarner Losh
95ce41f4bfSRobert Watson20031213:
96ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
97ce41f4bfSRobert Watson	if the login process is unable to successfully set the
98ce41f4bfSRobert Watson	process credentials to include all groups defined for the
99ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
100ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
101ce41f4bfSRobert Watson	defined, or they will be unable to log in.
102ce41f4bfSRobert Watson
103c124fa05SJohn Baldwin20031203:
104c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
105c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
106c124fa05SJohn Baldwin
1078ad1f5e4SHartmut Brandt20031112:
10830093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
10930093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
11097209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
11197209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
11297209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
11397209ca3SRobert Watson	not know about the new system calls that support the new statfs
1143f631d52SMarcel Moolenaar	structure.
1153f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
1163f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
1173f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
1183f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
1193f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
1203f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
1213f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
1223f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
1233f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
1243f631d52SMarcel Moolenaar	these changes are installed.
12530093b05SWarner Losh
12630093b05SWarner Losh	****************************DANGER*******************************
12730093b05SWarner Losh
12830093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
12930093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
13030093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
13130093b05SWarner Losh	kernel.
13264a18d6fSKirk McKusick
13364a18d6fSKirk McKusick20031112:
1348ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
1358ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
1368ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
1378ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
1388ad1f5e4SHartmut Brandt	sync before rebooting.
1398ad1f5e4SHartmut Brandt
140c53a5d8fSJohn Baldwin20031111:
141c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
142c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
143c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
144c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
145c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
146c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
147c53a5d8fSJohn Baldwin
1488bf455a5SJohn Baldwin20031103:
1498bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
1508bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
1512a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
1528bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
1538bf455a5SJohn Baldwin
1549bf40edeSBrooks Davis20031031:
1559bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
1569bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
1579bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
1589bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
1599bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
1609bf40edeSBrooks Davis	reflect this change.
1619bf40edeSBrooks Davis
16247a42c7aSPoul-Henning Kamp20030928:
16347a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
16447a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
16547a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
16647a42c7aSPoul-Henning Kamp
16707105342SMax Khon20030926:
16807105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
16907105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
17007105342SMax Khon
17117dcd026SSam Leffler20030925:
17217dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
17317dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
17417dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
17517dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
17617dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
17717dcd026SSam Leffler
178fedf1d01SBruce M Simpson20030923:
179fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
180fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
181fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
182fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
183fedf1d01SBruce M Simpson
184db38f9cbSJacques Vidrine20030915:
185db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
186db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
187db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
188db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
189db38f9cbSJacques Vidrine
190c09d2c2bSMike Makonnen20030829:
191c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
192c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
193c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
194c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
195c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
196c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
197c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
198c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
199c09d2c2bSMike Makonnen	may or may not exist on your system.
200c09d2c2bSMike Makonnen
20117c159dcSSøren Schmidt20030824:
20217c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
20317c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
204f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
205f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
20617c159dcSSøren Schmidt
207c1f61aa9SDavid E. O'Brien20030819:
208c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
209c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
210c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
211c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
21269f7bcf3SWarner Losh
21338c962e7SNate Lawson20030728:
21438c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
21538c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
21638c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
21738c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
21838c962e7SNate Lawson	so the quirk can be re-enabled.
21938c962e7SNate Lawson
22074111097SWarner Losh20030724:
22174111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
22274111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
22374111097SWarner Losh
224178cf4e9SWarner Losh20030722:
225178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
226178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
227178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
228178cf4e9SWarner Losh	FPU hardware.
229178cf4e9SWarner Losh
230178cf4e9SWarner Losh20030714:
231178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
232178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
233178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
234178cf4e9SWarner Losh	People should report those issues to current@.
235178cf4e9SWarner Losh
236157c629aSWarner Losh20030711:
237157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
2388b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
23905538fa9SWarner Losh	/usr/obj.
240157c629aSWarner Losh
24174111097SWarner Losh20030610:
24274111097SWarner Losh	Remove deprecated locale names and transition period code
24374111097SWarner Losh	for them, finishing switching to the new scheme. Check your
24474111097SWarner Losh	LANG environment variable.
24574111097SWarner Losh
24674111097SWarner Losh20030609:
24774111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
24874111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
24974111097SWarner Losh	important to remember beforehand if your source tree is on
25074111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
25174111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
25274111097SWarner Losh	kernel.
25374111097SWarner Losh
25474111097SWarner Losh20030605:
2556cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
2566cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
2576cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
2586cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
2596cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
2606cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
2616cc6353fSMarcel Moolenaar
2626cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
2636cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
2646cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
2656cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
2666cc6353fSMarcel Moolenaar		:
2676cc6353fSMarcel Moolenaar
2686cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
2696cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
2706cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
2716cc6353fSMarcel Moolenaar
27252b47445SMark Murray20030505:
27352b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
27452b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
27552b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
27652b47445SMark Murray
277a26df538SWarner Losh20030502:
278a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
279a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
280a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
281a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
282a26df538SWarner Losh
2834b065e2cSDoug Barton20030501:
2844b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
2854b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
2864b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
2874b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
2884b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
2894b065e2cSDoug Barton	utilizes these old scripts has also been removed.
2904b065e2cSDoug Barton
29181cda3d9SWarner Losh20030423:
29281cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
29381cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
29481cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
29581cda3d9SWarner Losh	have until then to upgrade your kernel before updating
29681cda3d9SWarner Losh	userland.  In general, you should have a userland and
29781cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
29881cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
29981cda3d9SWarner Losh	allowances are made.
30081cda3d9SWarner Losh
30147a657d1SRuslan Ermilov20030329:
30247a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
30347a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
30447a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
30547a657d1SRuslan Ermilov
30647a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
30747a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
30847a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
30947a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
31047a657d1SRuslan Ermilov
31147a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
31247a657d1SRuslan Ermilov	    make cleandir && make obj && \
31347a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
31447a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
31547a657d1SRuslan Ermilov
3165d2af00cSGregory Neil Shapiro20030208:
3175d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
3185d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
3195d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
3205d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
3215d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
3225d2af00cSGregory Neil Shapiro
3235d2af00cSGregory Neil Shapiro20030128:
3249db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
325ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
3269db58771SPoul-Henning Kamp	be removed when convenient.
3279db58771SPoul-Henning Kamp
3288d9b3f57SJake Burkholder20030126:
3298d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
3308d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
3318d9b3f57SJake Burkholder
3321c5efda5SJeff Roberson20030125:
3331c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
3341c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
335ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
3361c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
3371c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
3381c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
3391c5efda5SJeff Roberson
3409d1d64f5SWarner Losh20030115:
3419d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
3429d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
3439d1d64f5SWarner Losh	properly.
3449d1d64f5SWarner Losh
345c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
346c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
347c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
348c9fdb80aSWarner Losh	with NetBSD.
349c9fdb80aSWarner Losh
350161dc364SAlexander Kabaev20021222:
351161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
352161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
353161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
354161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
355161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
356161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
35784cc83efSAlexander Kabaev	rebuilt.
358161dc364SAlexander Kabaev
359fb4c8061SMartin Blapp20021216:
360fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
36189056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
362fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
3639d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
364fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
365fb4c8061SMartin Blapp
36617d47eb3SGiorgos Keramidas20021202:
36717d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
36817d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
36917d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
37017d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
37117d47eb3SGiorgos Keramidas
372a4459294SBill Fenner20021029:
373a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
374a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
375a4459294SBill Fenner	consumers in sync.
376a4459294SBill Fenner
377fc8c157fSWarner Losh20021024:
378c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
379c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
380c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
381c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
382c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
383c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
384c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
385c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
38669f7bcf3SWarner Losh
387fd9e8bdaSAndrew Gallatin20021023:
388fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
389fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
390fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
391fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
392fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
393fd9e8bdaSAndrew Gallatin
394fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
395fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
396fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
397fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
398fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
399fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
400fd9e8bdaSAndrew Gallatin
401f8a4c901SWarner Losh20020831:
402f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
403f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
404f8a4c901SWarner Losh	programs and libraries need to be recompiled.
405f8a4c901SWarner Losh
406f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
407f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
408f8a4c901SWarner Losh
409c2248fa2SJens Schweikhardt20020827:
410c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
411c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
412c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
413c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
414c2248fa2SJens Schweikhardt
4150d533e43SRuslan Ermilov20020815:
4160d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
4170d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
4180d533e43SRuslan Ermilov	again.
4190d533e43SRuslan Ermilov
42033c1de7dSRuslan Ermilov20020729:
42133c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
42233c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
42333c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
42433c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
42533c1de7dSRuslan Ermilov
4262b877facSJulian Elischer20020702:
4272b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
4282b877facSJulian Elischer	There are still some minor problems with some signals but the
4292b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
4302b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
4312b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
4322b877facSJulian Elischer
43306596d37SWarner Losh20020701:
43406596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
43506596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
43606596d37SWarner Losh	GNOME.
43706596d37SWarner Losh
43895ba4330SJacques Vidrine20020511:
43995ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
44095ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
44195ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
44295ba4330SJacques Vidrine	with the set-user-ID bit set.
44395ba4330SJacques Vidrine
444a81da3c9SDavid E. O'Brien20020510:
445f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
446f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
4474b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
448f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
449f50caf6fSDavid E. O'Brien
450f50caf6fSDavid E. O'Brien20020510:
451a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
452a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
453a81da3c9SDavid E. O'Brien	and then do a cvs update.
454a81da3c9SDavid E. O'Brien
455528a0ef5SJacques Vidrine20020421:
456528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
457528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
458528a0ef5SJacques Vidrine
45985aa5a2eSGregory Neil Shapiro20020404:
46085aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
46185aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
46285aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
46385aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
46485aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
46585aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
46685aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
46785aa5a2eSGregory Neil Shapiro
4688f1e4358SRuslan Ermilov20020403:
4698f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
4708f1e4358SRuslan Ermilov
4712292c02eSWarner Losh20020315:
4722292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
4732292c02eSWarner Losh
47469f7bcf3SWarner Losh20020225:
47569f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
47669f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
47769f7bcf3SWarner Losh
4788f35c493SWarner Losh20020217:
4798f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
4808f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
4818f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
4828f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
4838f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
4848f35c493SWarner Losh
485835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
486835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
487835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
488835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
489835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
490835284beSWarner Losh	and group must be merged from src/etc/group and
491835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
492835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
493835284beSWarner Losh	mergemaster before this will work if you are updating from a
494835284beSWarner Losh	very old version of current.  The updating recipe has changed
495835284beSWarner Losh	as of this date.
496835284beSWarner Losh
497fa9401c1SWarner Losh20020112:
498fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
499fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
500fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
501fa9401c1SWarner Losh	you have local modifications, you can use
502fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
503fa9401c1SWarner Losh	/etc/pam.d.
504fa9401c1SWarner Losh
505fa9401c1SWarner Losh	Please see the following url for more details:
506fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
50747d0d01fSWarner Losh20011229:
50847d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
50947d0d01fSWarner Losh	networkfs_types, please note that it has changed
51047d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
51147d0d01fSWarner Losh
512514318a8SWarner Losh20011220:
513514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
514514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
515514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
516514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
517514318a8SWarner Losh	version have now been merged back into the base system's
518514318a8SWarner Losh	version now.  The only user-visible change resulting from this
519514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
520514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
521514318a8SWarner Losh	as well.  (There has never been rc file support for
522514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
523514318a8SWarner Losh	reverted by the time the changes are MFCed.)
524514318a8SWarner Losh
525514318a8SWarner Losh20011215:
526514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
527514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
528514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
529514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
530514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
531514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
532514318a8SWarner Losh	will need to be customized then for `odd' densities using
533514318a8SWarner Losh	fdcontrol(8).
534514318a8SWarner Losh
5352d22e2bfSWarner Losh20011209:
5362d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
5372d22e2bfSWarner Losh	and truss(1) now works again.
5382d22e2bfSWarner Losh
5399e0428e2SWarner Losh20011207:
5409e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
5419e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
5429e0428e2SWarner Losh	see
5439e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
5449e0428e2SWarner Losh	for details.
5459e0428e2SWarner Losh
5469bab8c59SWarner Losh20011204:
5479bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
5489bab8c59SWarner Losh	kernel and burncd to be in sync.
5499bab8c59SWarner Losh
550e57d8b01SWarner Losh20011203:
551e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
552e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
553e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
554e57d8b01SWarner Losh	not there already.
555e57d8b01SWarner Losh
556e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
557e57d8b01SWarner Losh	until the issue has been resolved.
558e57d8b01SWarner Losh
559b001d36fSJacques Vidrine20011202:
560b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
561b001d36fSJacques Vidrine	patched.
562b001d36fSJacques Vidrine
5634b676ec1SWarner Losh20011126:
5644b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
5655ebbf43eSWarner Losh	after this date.  You need to do this only once.
5664b676ec1SWarner Losh
567d961e462SWarner Losh20011103:
568d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
569d961e462SWarner Losh	edges may be left, but for the most part things should be
5704b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
571d961e462SWarner Losh
572d961e462SWarner Losh20011030:
573d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
574d961e462SWarner Losh	choppy waves in the upgrade process.
575d961e462SWarner Losh
5761fe003b6SWarner Losh20011030:
577a4b6fda0SWarner Losh	The asr driver problem has been resolved.
5781fe003b6SWarner Losh
5791fe003b6SWarner Losh20011027:
5801fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
5811fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
5821fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
5831fe003b6SWarner Losh	try to use from this date forward.
5841fe003b6SWarner Losh
5851fe003b6SWarner Losh20011025:
5861fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
5871fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
5881fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
5891fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
5901fe003b6SWarner Losh	TARGET_ARCH=i386.
5911fe003b6SWarner Losh
592d05f9643SWarner Losh20011001:
593d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
594d05f9643SWarner Losh	You must recompile both the kernel and userland applications
595d05f9643SWarner Losh	at the same time.
596d05f9643SWarner Losh
59758970f85SWarner Losh20010929:
59858970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
59958970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
60058970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
60158970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
6029d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
60358970f85SWarner Losh
60458970f85SWarner Losh20010927:
60558970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
60658970f85SWarner Losh	To disable ACPI you can add
60766ff0e67SMax Khon		hint.acpi.0.disabled="1"
60858970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
60958970f85SWarner Losh	loader "ok" prompt).
61058970f85SWarner Losh
61158970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
61258970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
61358970f85SWarner Losh	file and not list acpi in that list.
614378f4486SAlfred Perlstein
6155119d237SWarner Losh20010924:
6165119d237SWarner Losh	The buildworld has been fixed.  You may need to install
6175119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
6188b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
6198b039fffSWarner Losh	get them installed on every installworld, or execute the
6208b039fffSWarner Losh	following to get them installed only once:
6218b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
62258970f85SWarner Losh		make all install
6238b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
6245119d237SWarner Losh
6253c293725SWarner Losh20010919:
6263c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
6273c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
6283c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
629772730c7SWarner Losh	workaround is to add
6303c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
6313c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
6323c293725SWarner Losh	can be removed afterwards.
6333c293725SWarner Losh
6343c293725SWarner Losh	A proper fix to the buildworld target is needed.
6353c293725SWarner Losh
6363c293725SWarner Losh20010918:
6373c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
6383c293725SWarner Losh	NFS may be unstable after this date.
6393c293725SWarner Losh
6403c293725SWarner Losh20010912:
6413c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
6423c293725SWarner Losh	the kernel.  While a few problems were introduced in the
6433c293725SWarner Losh	initial commit, most of the major ones have been found and
6443c293725SWarner Losh	corrected.
6453c293725SWarner Losh
6463c293725SWarner Losh20010901:
6473c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
6483c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
6493c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
6503c293725SWarner Losh	have been rectified around this date.
6513c293725SWarner Losh
65298b17b95SWarner Losh20010823:
65398b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
65498b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
65598b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
65698b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
65798b17b95SWarner Losh 	sure that user or group bind has read (and not write)
65898b17b95SWarner Losh 	permission for your name server configuration and that it
65998b17b95SWarner Losh 	has read and write permission for your slave zone files and
66098b17b95SWarner Losh 	directory.
66198b17b95SWarner Losh
66298b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
66398b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
66498b17b95SWarner Losh
66598b17b95SWarner Losh 		named_flags=
66698b17b95SWarner Losh
6677b9786edSMark Murray20010709:
6687b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
6697b9786edSMark Murray	the ability of the shared library major number to handle.
6707b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
6717b9786edSMark Murray	solution is to rebuild those ports.
6727b9786edSMark Murray
6731d28950eSWarner Losh20010628:
6741d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
6751d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
6761d28950eSWarner Losh
677e72fd46aSWarner Losh20010625:
67898b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
67998b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
68098b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
68198b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
68298b17b95SWarner Losh	IRQ configuration needs more safety belts.
68316de1a07SWarner Losh
6840d415dffSWarner Losh20010617:
685e72fd46aSWarner Losh	Softupdates problems have been corrected.
6860d415dffSWarner Losh
6870d415dffSWarner Losh20010614:
6880d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
6890d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
6900d415dffSWarner Losh	kernel building methods.
6910d415dffSWarner Losh
6928b9959adSWarner Losh20010613:
6938b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
6948b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
695e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
696e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
6978b9959adSWarner Losh
698e72fd46aSWarner Losh20010613:
6998b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
700e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
701e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
7028b9959adSWarner Losh
7030d415dffSWarner Losh20010612:
7040d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
7050d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
7060d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
7070d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
7080d415dffSWarner Losh	until this bug is fixed.
7090d415dffSWarner Losh
710e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
711e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
712ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
713e72fd46aSWarner Losh
7140d415dffSWarner Losh20010610:
7150d415dffSWarner Losh	Locale names have changed to match other systems better.
7160d415dffSWarner Losh
7176ccdb5e4SWarner Losh20010604:
7186ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
7196ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
7206ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
7213590182eSWarner Losh	Interrupt storms look a lot like a hang.
7223590182eSWarner Losh
7233590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
7243590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
7253590182eSWarner Losh	it is).
7263590182eSWarner Losh
7273590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
7283590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
7293590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
7303590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
7316ccdb5e4SWarner Losh
7320bc62786SWarner Losh20010530:
7330bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
7340bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
7350bc62786SWarner Losh	a limited time.  If you see
7360bc62786SWarner Losh
7370bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
7380bc62786SWarner Losh
7390bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
7400bc62786SWarner Losh	COPY=-C.
7410bc62786SWarner Losh
74268a38c6cSWarner Losh20010525:
743b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
744c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
745c4f4a728SWarner Losh	definitely is in bad shape.
74668a38c6cSWarner Losh
747ed0f29caSWarner Losh20010521:
748ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
749ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
750ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
751ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
752ed0f29caSWarner Losh	is
753ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
754ed0f29caSWarner Losh
75580c16af9SWarner Losh20010520:
75668a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
75780c16af9SWarner Losh
75880c16af9SWarner Losh20010519:
75980c16af9SWarner Losh	pccard has had much reorganizational work done to it over
76080c16af9SWarner Losh	the past few days.  Everything should still work, but if
76180c16af9SWarner Losh	not, please contact imp@freebsd.org.
76280c16af9SWarner Losh
763a45f2d05SWarner Losh20010517:
764a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
765a45f2d05SWarner Losh	userland at the same time.
766a45f2d05SWarner Losh
767a45f2d05SWarner Losh20010517:
768a45f2d05SWarner Losh	New ncurses imported.
769a45f2d05SWarner Losh
7702988afcaSWarner Losh20010512:
7712988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
7722988afcaSWarner Losh	will be the only way to go starting July 1.
7732988afcaSWarner Losh
7741a33dba7SWarner Losh20010504:
7751a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
7761a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
7771a33dba7SWarner Losh
77809946a51SWarner Losh20010502:
77909946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
78009946a51SWarner Losh
78109946a51SWarner Losh20010501:
78209946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
78309946a51SWarner Losh
78409946a51SWarner Losh20010430:
785a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
78609946a51SWarner Losh	go back in the water.
78709946a51SWarner Losh
78809946a51SWarner Losh20010429:
78909946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
79009946a51SWarner Losh	this date, but before the correction date.
79109946a51SWarner Losh
79291dd3b53SWarner Losh20010423:
79391dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
79491dd3b53SWarner Losh
79591dd3b53SWarner Losh20010411:
79691dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
79791dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
79891dd3b53SWarner Losh	Update only if you understand that you must not use the old
79991dd3b53SWarner Losh	fsck with the new kernel ever.
80091dd3b53SWarner Losh
801933b3269SWarner Losh20010330:
802933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
803c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
804933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
805933b3269SWarner Losh
806933b3269SWarner Losh20010319:
807933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
808933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
809933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
810f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
81109946a51SWarner Losh
81209946a51SWarner Losh20010315:
81309946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
814ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
81509946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
816933b3269SWarner Losh
817933b3269SWarner Losh20010312:
818933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
819933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
820933b3269SWarner Losh
821933b3269SWarner Losh20010312:
822933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
823933b3269SWarner Losh	instead of ad-hoc.
824933b3269SWarner Losh
825933b3269SWarner Losh20010310:
826f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
827933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
828933b3269SWarner Losh	ssh might not work if you don't.
829933b3269SWarner Losh
83062353691SWarner Losh20010303:
83162353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
83262353691SWarner Losh	which means that you must include the miibus in your kernel if
83362353691SWarner Losh	you use the ed driver.
83462353691SWarner Losh
835d325cf65SWarner Losh20010220:
836d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
837d325cf65SWarner Losh	safe to go back into the water.
838d325cf65SWarner Losh
839024daae6SWarner Losh20010211:
840024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
841024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
842024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
843024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
844024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
845024daae6SWarner Losh
846024daae6SWarner Losh	To get to the new system, you'll need to use the following
847024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
848024daae6SWarner Losh	don't have to move this to the updating section.
849024daae6SWarner Losh
850024daae6SWarner Losh	To get around the installworld problem, do:
851024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
852024daae6SWarner Losh		# make install
853024daae6SWarner Losh		# cd /usr/src
854024daae6SWarner Losh		# make installworld
855024daae6SWarner Losh	If that doesn't work, then try:
856024daae6SWarner Losh		# make -k installworld
857024daae6SWarner Losh		# make installworld
858024daae6SWarner Losh
859024daae6SWarner Losh20010207:
860024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
861024daae6SWarner Losh	do not include devfs in your kernel as problems result.
862024daae6SWarner Losh
863024daae6SWarner Losh20010205:
8647595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
865024daae6SWarner Losh	Remove them from your config.
866024daae6SWarner Losh
8671e159248SWarner Losh20010122:
8681e159248SWarner Losh	****************************** WARNING ******************************
8691e159248SWarner Losh			buildkernel has been changed slightly
8701e159248SWarner Losh	****************************** WARNING ******************************
8711e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
8721e159248SWarner Losh	should update your scripts and make.conf accordingly.
8731e159248SWarner Losh
8741e159248SWarner Losh20010119:
8751e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
8761e159248SWarner Losh	This requires a new config to build correctly.
8771e159248SWarner Losh
878aac7dfeaSWarner Losh20010116:
879ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
880aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
881aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
882aac7dfeaSWarner Losh
883aac7dfeaSWarner Losh20010110:
884aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
885aac7dfeaSWarner Losh
886aac7dfeaSWarner Losh20010102:
887aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
888aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
889aac7dfeaSWarner Losh
89063c90c9eSWarner Losh20010101:
89163c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
89263c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
8935fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
89463c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
89563c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
89663c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
89763c90c9eSWarner Losh	might have been ignored by the -k option.
89863c90c9eSWarner Losh
8995fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
9005fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
9015fd2a895SWarner Losh	of this working.
9025fd2a895SWarner Losh
903aac7dfeaSWarner Losh20001228:
904aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
905ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
906aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
907aac7dfeaSWarner Losh
908de2bcc63SWarner Losh20001218:
909de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
910de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
911de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
912de2bcc63SWarner Losh	cards will not be recognized without it.
913de2bcc63SWarner Losh
914960773f7SWarner Losh20001205:
915960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
916960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
917960773f7SWarner Losh	adding the following in pam.conf:
918960773f7SWarner Losh
919960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
920960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
921960773f7SWarner Losh	sshd    session required        pam_permit.so
922960773f7SWarner Losh
9230acc635eSWarner Losh20001031:
9240acc635eSWarner Losh	cvs updated to 1.11.
9250acc635eSWarner Losh
9260acc635eSWarner Losh20001020:
9270acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
9280acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
9290acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
9300acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
9310acc635eSWarner Losh	workaround.
9320acc635eSWarner Losh
9330acc635eSWarner Losh20001010:
9340acc635eSWarner Losh	****************************** WARNING ******************************
9350acc635eSWarner Losh				Sendmail has been updated.
9360acc635eSWarner Losh	****************************** WARNING ******************************
9370acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
9380acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
9390acc635eSWarner Losh	  is set.
9400acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
9410acc635eSWarner Losh	  commands.
9420acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
9430acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
9440acc635eSWarner Losh	  in /usr/share/sendmail/cf.
9450acc635eSWarner Losh	o sendmail.cw changed to local-host-names
9460acc635eSWarner Losh
9470acc635eSWarner Losh	More details can be found at
9480acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
9490acc635eSWarner Losh
9506e98a146SWarner Losh20001009:
9516e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
9526e98a146SWarner Losh	your entire ports tree, or you will have problems.
9536e98a146SWarner Losh
9546e98a146SWarner Losh20001006:
955685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
9566e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
9576e98a146SWarner Losh	/usr/bin/miniperl.
9586e98a146SWarner Losh
959073113a4SWarner Losh20001005:
960073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
961685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
962073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
963073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
964073113a4SWarner Losh	tree for anything to work.
965073113a4SWarner Losh
9660acc635eSWarner Losh20000928:
9670acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
9680acc635eSWarner Losh
969be3885b3SWarner Losh20000916:
970be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
971be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
972be3885b3SWarner Losh	same time as your kernel.
973be3885b3SWarner Losh
97476ec9675SWarner Losh20000914:
97576ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
97676ec9675SWarner Losh	include the device will cause suspended laptops losing time
97776ec9675SWarner Losh	when they resume.  Include
97876ec9675SWarner Losh		device		pmtimer
97976ec9675SWarner Losh	in your config file and
98001b9a434SWarner Losh		hint.pmtimer.0.at="isa"
98176ec9675SWarner Losh	to your /boot/device.hints file.
98276ec9675SWarner Losh
983f4865386SMark Murray20000911:
984f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
985f4865386SMark Murray	rather than an option. The supplied kernel config files have
986f4865386SMark Murray	been updated. You will need to do something similar in your
987f4865386SMark Murray	own kernel config file.
988f4865386SMark Murray	Remove:
989f4865386SMark Murray		options		RANDOMDEV
990f4865386SMark Murray	Add:
991f4865386SMark Murray		device		random
992f4865386SMark Murray	If you prefer to load the loadable module, you need to do
993f4865386SMark Murray	nothing.
994f4865386SMark Murray
995d594498fSWarner Losh20000909:
996d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
997d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
998d594498fSWarner Losh	reflect this if you load this module at boot time.
999d594498fSWarner Losh	The line should read:
1000d594498fSWarner Losh		random_load="YES"
1001d594498fSWarner Losh
10020deb7ddcSWarner Losh20000907:
10030deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
100416eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
100516eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
100616eb772dSWarner Losh	sure you don't have model loading problems which might at
100716eb772dSWarner Losh	first blush appear related to SMP.
100852bf24e7SWarner Losh
10095a01880bSWarner Losh20000906:
10105a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
10115a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
10125a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
10135a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
10145a01880bSWarner Losh	don't have one, and you have host.conf.
10155a01880bSWarner Losh
10162b41163cSWarner Losh20000905:
101738d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
101838d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
101938d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
102038d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
102138d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
102238d6ecd2SWarner Losh
102338d6ecd2SWarner Losh20000905:
10248aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
10258aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
10268aab4bc7SWarner Losh	is /boot/kernel.
10278aab4bc7SWarner Losh
10288aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
102938d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
103038d6ecd2SWarner Losh	installkernel/installworld dance.
10312b41163cSWarner Losh
1032d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1033d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1034d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1035d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1036d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1037d594498fSWarner Losh
1038d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1039d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1040d594498fSWarner Losh		chflags noschg /kernel.old
1041d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1042d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1043d594498fSWarner Losh	fi
1044d594498fSWarner Losh
1045c22a309cSWarner Losh20000904:
1046c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1047c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1048c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1049c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1050c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1051c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1052c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1053c22a309cSWarner Losh	is not likely to be generated.
1054c22a309cSWarner Losh
1055fdb9f54dSWarner Losh20000825:
1056fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
10579c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
10589c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
10599c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
10609c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
10619c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
10629c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
10639c1a7444SWarner Losh	kernel.
10649c1a7444SWarner Losh
10659c1a7444SWarner Losh20000821:
10669c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
10679c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
10689c1a7444SWarner Losh	/boot/loader.conf.
1069fdb9f54dSWarner Losh
10708f250aa7SWarner Losh20000812:
10715da0d091SWarner Losh	suidperl is now always built and installed on the system, but
10725da0d091SWarner Losh	with permissions of 511.  If you have applications that use
10735da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
10745da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
10755da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
10765da0d091SWarner Losh	will fix this until the next build.
10775da0d091SWarner Losh
10785da0d091SWarner Losh20000812:
10798f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
10808f250aa7SWarner Losh	visible changes that may immediately affect your configuration
10818f250aa7SWarner Losh	include:
10828f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
10838f250aa7SWarner Losh	- newaliases limited to root and trusted users
10848f250aa7SWarner Losh	- MSA port (587) turned on by default
10858f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
10868f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
10878f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
10888f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
10898f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
10908f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
10918f250aa7SWarner Losh
109271c38472SWarner Losh20000810:
109371c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
109471c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
109571c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
109671c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
109771c38472SWarner Losh	specific use for it.
109871c38472SWarner Losh
109971c38472SWarner Losh20000729:
110071c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
110171c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
110271c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
110371c38472SWarner Losh	afterwards (unless the variables already are set, of course):
110471c38472SWarner Losh		# Enable network daemons for user convenience.
110571c38472SWarner Losh		inetd_enable="YES"
110671c38472SWarner Losh		portmap_enable="YES"
110771c38472SWarner Losh		sendmail_enable="YES"
110871c38472SWarner Losh
110971c38472SWarner Losh20000728:
111071c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
111171c38472SWarner Losh	will need to change that to nullfs_load="YES".
111271c38472SWarner Losh
11131dece4a9SWarner Losh20000728:
11141dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
11151dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
11161dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
11171dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
11181dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
11191dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
11201dece4a9SWarner Losh	to /MYKERNEL.
11211dece4a9SWarner Losh
1122409e887cSWarner Losh20000711:
1123409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1124409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1125409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1126409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1127409e887cSWarner Losh	for details on potential problems that you might have and how
1128409e887cSWarner Losh	to get around them.
1129409e887cSWarner Losh
1130409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1131409e887cSWarner Losh	clauses above, you needn't worry.
1132409e887cSWarner Losh
1133409e887cSWarner Losh20000711:
1134409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1135409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1136409e887cSWarner Losh	in the number of changed programs the first time when you run
1137409e887cSWarner Losh	mergemaster to get a new /etc/security.
1138409e887cSWarner Losh
1139673d13f2SWarner Losh20000710:
1140673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1141673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1142673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1143673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1144673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1145673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1146673d13f2SWarner Losh	errors. (see below, 20000624).
1147673d13f2SWarner Losh
1148bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
11491dece4a9SWarner Losh
1150673d13f2SWarner Losh20000709:
1151c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1152c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1153c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1154673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1155673d13f2SWarner Losh
1156e98e26cdSWarner Losh20000706:
1157e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1158e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1159e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1160f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1161e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
11622c021c6cSMark Ovens	interim if needed.
1163e98e26cdSWarner Losh
1164e98e26cdSWarner Losh20000705:
1165e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1166e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1167e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1168e98e26cdSWarner Losh	details.
1169e98e26cdSWarner Losh
1170c373950eSWarner Losh20000704:
11712f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
11722f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
11732f961bc8SWarner Losh
11742f961bc8SWarner Losh20000704:
1175c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1176c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1177c373950eSWarner Losh	rc.d scripts that haven't been updated.
1178c373950eSWarner Losh
117927dc3a2bSWarner Losh20000630:
118027dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
118127dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
118227dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
118327dc3a2bSWarner Losh
1184b8c215acSWarner Losh20000625:
1185b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
118627dc3a2bSWarner Losh	system installed in order to build the system and kernel.
118727dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
118827dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
118927dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
119027dc3a2bSWarner Losh	were required.  You should check with the latest collections
119127dc3a2bSWarner Losh	to make sure that these haven't changed.
1192b8c215acSWarner Losh
11937b990719SWarner Losh20000624:
11947b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
11957b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
11967b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
11971a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
11987b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
11997b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
12007b990719SWarner Losh	date to the completion of the work.
12017b990719SWarner Losh
120227dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
120327dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
120427dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
120527dc3a2bSWarner Losh	recreate the random and urandom devices.
120627dc3a2bSWarner Losh
120781e54c50SWarner Losh20000622:
120881e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
120981e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
121081e54c50SWarner Losh	that used to be required when updating.
121181e54c50SWarner Losh
121239943833SWarner Losh20000621:
12132c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
12142a2f33fbSDaniel Baker	the config file update procedure.
12152a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1216c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
121759df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
121859df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
121939943833SWarner Losh
1220290f9ad8SWarner Losh20000620:
1221290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1222290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1223290f9ad8SWarner Losh	that workaround will no longer be required.
1224290f9ad8SWarner Losh
122590fb6346SWarner Losh20000615:
122690fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
122790fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
122890fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
122990fb6346SWarner Losh	devices.
123090fb6346SWarner Losh
1231f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1232f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1233f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1234f75f65bbSWarner Losh	may work).
1235f75f65bbSWarner Losh
1236ba26da8eSWarner Losh20000612:
1237ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1238290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1239c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1240290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1241f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1242f54a3542SWarner Losh	NEWCARD for examples of the new format.
1243290f9ad8SWarner Losh
12449698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
12459698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
12469698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
12479698f2c0SWarner Losh	in it.
1248bbcc5149SWarner Losh
1249d65850ebSWarner Losh20000522:
1250ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1251d65850ebSWarner Losh	building a kernel after this point is advised that they need
1252d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1253d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1254d65850ebSWarner Losh
1255d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1256d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1257d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1258d9583a00SWarner Losh	is resolved.
1259d9583a00SWarner Losh
12608039cedeSWarner Losh20000513:
12618039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
12628039cedeSWarner Losh
1263d65850ebSWarner Losh20000510:
12648039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
12658039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
12668039cedeSWarner Losh	is requires for the boot blocks to build properly.
12678039cedeSWarner Losh
12688039cedeSWarner Losh20000503:
12698039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
12708039cedeSWarner Losh	is now available.
12718039cedeSWarner Losh
1272d65850ebSWarner Losh20000502:
1273d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1274d65850ebSWarner Losh	connected to the kernel building instead.
1275d65850ebSWarner Losh
1276be149406SNik Clayton20000427:
12778039cedeSWarner Losh	You may need to build gperf
12788039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
12798039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
12808039cedeSWarner Losh	an option only in -current.
12818039cedeSWarner Losh
12822b8dd5f4SWarner Losh20000417:
12832b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1284f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
12852b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
12862b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
12872c021c6cSMark Ovens	before you reboot, you'll need to issue:
12882b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
12892b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
12902b8dd5f4SWarner Losh
12918d9f1945SWarner Losh20000320:
12922b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
12932b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
12942b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1295ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
12962b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
12978d9f1945SWarner Losh
1298f8ab1dd6SWarner Losh20000319:
1299f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1300f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1301f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1302f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1303f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1304f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1305f8ab1dd6SWarner Losh
130619cada77SWarner Losh20000318:
1307f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
130819cada77SWarner Losh	Large kernel changes are being committed and are in the
130919cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
131019cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
131119cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
131219cada77SWarner Losh	that you are loading are up to date.
1313ba228352SWarner Losh
131419cada77SWarner Losh20000315:
13156d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
13166d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
13176d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
13186d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
13196d23c382SWarner Losh	boot.
13206d23c382SWarner Losh
13216d23c382SWarner Losh20000315:
132219cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
132319cada77SWarner Losh	to upgrade to 4.0 from 3.x.
132457199806SWarner Losh
1325dc0dbf5cSWarner LoshCOMMON ITEMS:
1326dc0dbf5cSWarner Losh
1327a24eff53SWarner Losh	General Notes
1328a24eff53SWarner Losh	-------------
1329a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1330a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1331a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1332a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1333a24eff53SWarner Losh	or several minor releases, or when several months have passed
1334a24eff53SWarner Losh	on the -current branch).
1335a24eff53SWarner Losh
13365780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
13375780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
13385780f3baSWarner Losh	environment when searching for values for global variables.
13395780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
13405780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
13415780f3baSWarner Losh	page for more details.
13425780f3baSWarner Losh
1343dc0dbf5cSWarner Losh	To build a kernel
1344dc0dbf5cSWarner Losh	-----------------
1345ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1346f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1347ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1348282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1349282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1350dc0dbf5cSWarner Losh
1351ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1352ba01eb20SWarner Losh	--------------------------------------------------------------
1353ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
135447d0d01fSWarner Losh	config KERNEL_NAME_HERE
1355ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1356ba01eb20SWarner Losh	make depend
1357ba01eb20SWarner Losh	make
1358ba01eb20SWarner Losh	make install
1359ba01eb20SWarner Losh
1360ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1361ba01eb20SWarner Losh
1362ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1363ba01eb20SWarner Losh	-----------------------------------------------------------
136463cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
136563cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
136663cb445eSWarner Losh
1367f643de42SWarner Losh	<make sure you have good level 0 dumps>
136863cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
136963cb445eSWarner Losh	make buildworld
137063cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
137163cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
137263cb445eSWarner Losh							[1]
137363cb445eSWarner Losh	<reboot in single user>				[3]
137463cb445eSWarner Losh	mergemaster -p					[5]
137563cb445eSWarner Losh	make installworld
137663cb445eSWarner Losh	mergemaster					[4]
137763cb445eSWarner Losh	<reboot>
137863cb445eSWarner Losh
1379759f0aefSWarner Losh
1380f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1381f27b1fceSJoseph Koshy	--------------------------------------------------
1382f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1383f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1384f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1385f27b1fceSJoseph Koshy	# size.
1386f27b1fceSJoseph Koshy
1387f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1388f27b1fceSJoseph Koshy	<boot into -stable>
1389f27b1fceSJoseph Koshy	make buildworld
1390f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1391f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1392f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1393f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1394f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1395f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1396f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1397f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1398f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1399f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1400f27b1fceSJoseph Koshy	<reboot into current>
1401f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1402f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1403f27b1fceSJoseph Koshy 	<reboot>
1404f27b1fceSJoseph Koshy
1405f27b1fceSJoseph Koshy
1406f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1407f27b1fceSJoseph Koshy	----------------------------------------------
14085c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
14095c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
14105c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
14115c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1412ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1413f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1414f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1415f643de42SWarner Losh	# space on /.
1416f643de42SWarner Losh
1417f643de42SWarner Losh	<make sure you have good level 0 dumps>
1418fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
141921c075eaSWarner Losh	make buildworld					[9]
1420c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1421d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1422be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1423fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1424fc8c157fSWarner Losh							[1]
1425fc8c157fSWarner Losh	<reboot in single user>				[3]
1426835284beSWarner Losh	mergemaster -p					[5]
1427f8a4c901SWarner Losh	rm -rf /usr/include/g++
1428ba26da8eSWarner Losh	make installworld
1429a6cd4f9dSWarner Losh	mergemaster					[4]
1430ba26da8eSWarner Losh	<reboot>
1431ba26da8eSWarner Losh
1432fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1433fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1434fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1435fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1436fdb9f54dSWarner Losh	the UPDATING entries.
1437ba26da8eSWarner Losh
14381dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
14391dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
14401dece4a9SWarner Losh	your sources that you have read and understood all the recent
14411dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
14421dece4a9SWarner Losh	much fewer pitfalls.
14431dece4a9SWarner Losh
1444134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1445134d2e86SWarner Losh	should disable them at this point so they don't crash your
1446134d2e86SWarner Losh	system on reboot.
1447134d2e86SWarner Losh
14489c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
14499c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
14509c1a7444SWarner Losh	configuration.
14519c1a7444SWarner Losh
1452ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1453ee6e1fc3SWarner Losh		fsck -p
1454ee6e1fc3SWarner Losh		mount -u /
1455ee6e1fc3SWarner Losh		mount -a
1456ee6e1fc3SWarner Losh		cd /usr/src
145747d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1458f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1459f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1460b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1461b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1462b705ae10SWarner Losh	be ignored while you proceed to the next step.
1463ee6e1fc3SWarner Losh
1464a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1465a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1466a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1467a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1468a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1469a6cd4f9dSWarner Losh	for potential gotchas.
1470a6cd4f9dSWarner Losh
1471835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1472835284beSWarner Losh	you may need to do this if you get unknown user in the following
1473835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1474835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1475835284beSWarner Losh	install) after the buildworld before this step if you last updated
1476835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1477835284beSWarner Losh
1478bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1479bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1480bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1481bd79cf40SWarner Losh		ok unload
1482bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1483bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1484bd79cf40SWarner Losh	described here.
1485fc8c157fSWarner Losh
1486fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1487fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1488fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1489fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1490fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1491fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1492fc8c157fSWarner Losh
1493c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1494c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1495c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1496c74fe6afSWarner Losh	that is hard to boot to recover.
1497c74fe6afSWarner Losh
149821c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
149921c075eaSWarner Losh	cvs prune empty directories.
1500dc0dbf5cSWarner LoshFORMAT:
1501dc0dbf5cSWarner Losh
1502f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
15031fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1504f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1505f8ab1dd6SWarner Loshprevious releases if your system is older than this.
15061fc1a0dcSWarner Losh
1507e72fd46aSWarner LoshCopyright information:
1508e72fd46aSWarner Losh
15099698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1510e72fd46aSWarner Losh
1511772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1512772730c7SWarner Loshmodification, in full or in part, in any form or format of this
15139698f2c0SWarner Loshdocument are permitted without further permission from the author.
1514e72fd46aSWarner Losh
1515e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1516e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1517e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1518e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1519e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1520e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1521e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1522e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1523e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1524e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1525e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1526e72fd46aSWarner Losh
1527e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1528e72fd46aSWarner Loshauthor a beer.
1529e72fd46aSWarner Losh
153022306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1531772730c7SWarner Loshthis document.
1532772730c7SWarner Losh
153397d92980SPeter Wemm$FreeBSD$
1534