xref: /freebsd/UPDATING (revision e0ae81f32aee8c0f63f62cfcceef1a8aa1c37cef)
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
20e0ae81f3SDag-Erling Smørgrav20040621:
21e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
22e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
23e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
24e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
25e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
26e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
27e0ae81f3SDag-Erling Smørgrav	during the next reboot.
28e0ae81f3SDag-Erling Smørgrav
294717d22aSJohn Polstra20040614:
304717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
314717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
324717d22aSJohn Polstra	the ips module and any third-party modules which call
334717d22aSJohn Polstra	sema_timedwait.
344717d22aSJohn Polstra
356cb7a382SMax Laier20040613:
366cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
376cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
38df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
39df843493SMax Laier	please recompile and reinstall world.
406cb7a382SMax Laier
412454685eSJulian Elischer20040607:
422454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
432454685eSJulian Elischer	requires that you re-run config after updating your tree.
442454685eSJulian Elischer
4564fef830SSeigo Tanimura20040601:
4664fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
4764fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
4864fef830SSeigo Tanimura	kernel configuration.
4964fef830SSeigo Tanimura
50bb4f06e7SAndre Oppermann20040423:
51bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
52bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
53bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
54bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
55bb4f06e7SAndre Oppermann
5605641e82SColin Percival20040420:
5705641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
5805641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
5905641e82SColin Percival	20040406.
6005641e82SColin Percival
61d0dc9183SWarner Losh20040414:
62d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
63d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
64d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
65d0dc9183SWarner Losh
66d0dc9183SWarner Losh20040412:
67d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
68d0dc9183SWarner Losh	drive is still broken.
69d0dc9183SWarner Losh
70d0dc9183SWarner Losh20040410:
71d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
72d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
73d0dc9183SWarner Losh	the unanticipated problems have been resolved.
74d0dc9183SWarner Losh
758633bbeaSBrooks Davis20040409:
768633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
778633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
788633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
798633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
8076c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
818633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
828633bbeaSBrooks Davis
83d40d033aSRobert Watson20040322:
84d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
85d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
86d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
87d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
88d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
89d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
90d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
91d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
92d40d033aSRobert Watson	locking is merged to permit this to take place.
93d40d033aSRobert Watson
94ec9b318eSGarance A Drosehn20040310:
95ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
96ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
97ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
98ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
99ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
100ec9b318eSGarance A Drosehn
101fc28f1ffSMax Laier20040308:
102fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
103fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
1044c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
1054c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
106fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
107fc28f1ffSMax Laier	pf system consists of the following three devices:
108fc28f1ffSMax Laier	device		pf		# required
109fc28f1ffSMax Laier	device		pflog		# optional
110fc28f1ffSMax Laier	device		pfsync		# optional
111fc28f1ffSMax Laier
1123aff5d06SDag-Erling Smørgrav20040303:
1133aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
1143aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
1153aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
1163aff5d06SDag-Erling Smørgrav
1173aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
1183aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
1193aff5d06SDag-Erling Smørgrav
1203aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
1213aff5d06SDag-Erling Smørgrav	to use libpthread instead.
1223aff5d06SDag-Erling Smørgrav
123fd63c5b3SDag-Erling Smørgrav20040226:
1249d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
125fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
126fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
127fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
128fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
129fd63c5b3SDag-Erling Smørgrav
130714ae42aSBruce M Simpson20040225:
131e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
132e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
133e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
134e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
135e07a40f3SBrian Feldman	should remain unaffected.
136e07a40f3SBrian Feldman
137e07a40f3SBrian Feldman20040225:
138714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
139714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
140714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
141714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
142714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
143714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
144714ae42aSBruce M Simpson
145fbd2e692SAndre Oppermann20040224:
146fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
147fbd2e692SAndre Oppermann	and related userland network utilities neccessary.
148fbd2e692SAndre Oppermann
149158b90daSWarner Losh20040222:
150158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
151158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
152158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
153158b90daSWarner Losh	Drivers outside the tree will need to be updated.
154158b90daSWarner Losh
155b7b1e150SMike Makonnen20040207:
156b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
157b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
158b7b1e150SMike Makonnen
159aca89ee6SDaniel Eischen20040130:
160aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
161aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
162aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
163aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
164aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
165aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
166aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
167aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
168aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
169aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
170aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
171aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
172aca89ee6SDaniel Eischen	do not work with libpthread.
173aca89ee6SDaniel Eischen
17468b7b3a9SAlex Dupre20040125:
17568b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
17668b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
17768b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
17868b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
17968b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
18068b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
18168b7b3a9SAlex Dupre
182ff46e0deSWarner Losh20040125:
183ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
184ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
185ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
186ff46e0deSWarner Losh
187ce41f4bfSRobert Watson20031213:
188ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
189ce41f4bfSRobert Watson	if the login process is unable to successfully set the
190ce41f4bfSRobert Watson	process credentials to include all groups defined for the
191ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
192ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
193ce41f4bfSRobert Watson	defined, or they will be unable to log in.
194ce41f4bfSRobert Watson
195c124fa05SJohn Baldwin20031203:
196c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
197c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
198c124fa05SJohn Baldwin
1998ad1f5e4SHartmut Brandt20031112:
20030093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
20130093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
20297209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
20397209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
20497209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
20597209ca3SRobert Watson	not know about the new system calls that support the new statfs
2063f631d52SMarcel Moolenaar	structure.
2073f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
2083f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
2093f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
2103f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
2113f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
2123f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
2133f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
2143f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
2153f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
2163f631d52SMarcel Moolenaar	these changes are installed.
21730093b05SWarner Losh
21830093b05SWarner Losh	****************************DANGER*******************************
21930093b05SWarner Losh
22030093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
22130093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
22230093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
22330093b05SWarner Losh	kernel.
22464a18d6fSKirk McKusick
22564a18d6fSKirk McKusick20031112:
2268ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
2278ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
2288ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
2298ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
2308ad1f5e4SHartmut Brandt	sync before rebooting.
2318ad1f5e4SHartmut Brandt
232c53a5d8fSJohn Baldwin20031111:
233c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
234c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
235c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
236c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
237c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
238c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
239c53a5d8fSJohn Baldwin
2408bf455a5SJohn Baldwin20031103:
2418bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
2428bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
2432a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
2448bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
2458bf455a5SJohn Baldwin
2469bf40edeSBrooks Davis20031031:
2479bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
2489bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
2499bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
2509bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
2519bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
2529bf40edeSBrooks Davis	reflect this change.
2539bf40edeSBrooks Davis
25447a42c7aSPoul-Henning Kamp20030928:
25547a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
25647a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
25747a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
25847a42c7aSPoul-Henning Kamp
25907105342SMax Khon20030926:
26007105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
26107105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
26207105342SMax Khon
26317dcd026SSam Leffler20030925:
26417dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
26517dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
26617dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
26717dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
26817dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
26917dcd026SSam Leffler
270fedf1d01SBruce M Simpson20030923:
271fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
272fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
273fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
274fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
275fedf1d01SBruce M Simpson
276db38f9cbSJacques Vidrine20030915:
277db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
278db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
279db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
280db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
281db38f9cbSJacques Vidrine
282c09d2c2bSMike Makonnen20030829:
283c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
284c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
285c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
286c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
287c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
288c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
289c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
290c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
291c09d2c2bSMike Makonnen	may or may not exist on your system.
292c09d2c2bSMike Makonnen
29317c159dcSSøren Schmidt20030824:
29417c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
29517c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
296f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
297f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
29817c159dcSSøren Schmidt
299c1f61aa9SDavid E. O'Brien20030819:
300c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
301c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
302c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
303c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
30469f7bcf3SWarner Losh
30538c962e7SNate Lawson20030728:
30638c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
30738c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
30838c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
30938c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
31038c962e7SNate Lawson	so the quirk can be re-enabled.
31138c962e7SNate Lawson
31274111097SWarner Losh20030724:
31374111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
31474111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
31574111097SWarner Losh
316178cf4e9SWarner Losh20030722:
317178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
318178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
319178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
320178cf4e9SWarner Losh	FPU hardware.
321178cf4e9SWarner Losh
322178cf4e9SWarner Losh20030714:
323178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
324178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
325178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
326178cf4e9SWarner Losh	People should report those issues to current@.
327178cf4e9SWarner Losh
328157c629aSWarner Losh20030711:
329157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
3308b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
33105538fa9SWarner Losh	/usr/obj.
332157c629aSWarner Losh
33374111097SWarner Losh20030610:
33474111097SWarner Losh	Remove deprecated locale names and transition period code
33574111097SWarner Losh	for them, finishing switching to the new scheme. Check your
33674111097SWarner Losh	LANG environment variable.
33774111097SWarner Losh
33874111097SWarner Losh20030609:
33974111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
34074111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
34174111097SWarner Losh	important to remember beforehand if your source tree is on
34274111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
34374111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
34474111097SWarner Losh	kernel.
34574111097SWarner Losh
34674111097SWarner Losh20030605:
3476cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
3486cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
3496cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
3506cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
3516cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
3526cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
3536cc6353fSMarcel Moolenaar
3546cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
3556cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
3566cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
3576cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
3586cc6353fSMarcel Moolenaar		:
3596cc6353fSMarcel Moolenaar
3606cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
3616cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
3626cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
3636cc6353fSMarcel Moolenaar
36452b47445SMark Murray20030505:
36552b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
36652b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
36752b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
36852b47445SMark Murray
369a26df538SWarner Losh20030502:
370a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
371a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
372a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
373a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
374a26df538SWarner Losh
3754b065e2cSDoug Barton20030501:
3764b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
3774b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
3784b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
3794b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
3804b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
3814b065e2cSDoug Barton	utilizes these old scripts has also been removed.
3824b065e2cSDoug Barton
38381cda3d9SWarner Losh20030423:
38481cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
38581cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
38681cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
38781cda3d9SWarner Losh	have until then to upgrade your kernel before updating
38881cda3d9SWarner Losh	userland.  In general, you should have a userland and
38981cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
39081cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
39181cda3d9SWarner Losh	allowances are made.
39281cda3d9SWarner Losh
39347a657d1SRuslan Ermilov20030329:
39447a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
39547a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
39647a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
39747a657d1SRuslan Ermilov
39847a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
39947a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
40047a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
40147a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
40247a657d1SRuslan Ermilov
40347a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
40447a657d1SRuslan Ermilov	    make cleandir && make obj && \
40547a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
40647a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
40747a657d1SRuslan Ermilov
4085d2af00cSGregory Neil Shapiro20030208:
4095d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
4105d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
4115d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
4125d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
4135d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
4145d2af00cSGregory Neil Shapiro
4155d2af00cSGregory Neil Shapiro20030128:
4169db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
417ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
4189db58771SPoul-Henning Kamp	be removed when convenient.
4199db58771SPoul-Henning Kamp
4208d9b3f57SJake Burkholder20030126:
4218d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
4228d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
4238d9b3f57SJake Burkholder
4241c5efda5SJeff Roberson20030125:
4251c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
4261c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
427ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
4281c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
4291c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
4301c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
4311c5efda5SJeff Roberson
4329d1d64f5SWarner Losh20030115:
4339d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
4349d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
4359d1d64f5SWarner Losh	properly.
4369d1d64f5SWarner Losh
437c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
438c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
439c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
440c9fdb80aSWarner Losh	with NetBSD.
441c9fdb80aSWarner Losh
442161dc364SAlexander Kabaev20021222:
443161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
444161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
445161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
446161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
447161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
448161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
44984cc83efSAlexander Kabaev	rebuilt.
450161dc364SAlexander Kabaev
451fb4c8061SMartin Blapp20021216:
452fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
45389056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
454fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
4559d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
456fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
457fb4c8061SMartin Blapp
45817d47eb3SGiorgos Keramidas20021202:
45917d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
46017d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
46117d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
46217d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
46317d47eb3SGiorgos Keramidas
464a4459294SBill Fenner20021029:
465a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
466a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
467a4459294SBill Fenner	consumers in sync.
468a4459294SBill Fenner
469fc8c157fSWarner Losh20021024:
470c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
471c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
472c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
473c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
474c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
475c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
476c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
477c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
47869f7bcf3SWarner Losh
479fd9e8bdaSAndrew Gallatin20021023:
480fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
481fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
482fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
483fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
484fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
485fd9e8bdaSAndrew Gallatin
486fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
487fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
488fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
489fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
490fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
491fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
492fd9e8bdaSAndrew Gallatin
493f8a4c901SWarner Losh20020831:
494f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
495f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
496f8a4c901SWarner Losh	programs and libraries need to be recompiled.
497f8a4c901SWarner Losh
498f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
499f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
500f8a4c901SWarner Losh
501c2248fa2SJens Schweikhardt20020827:
502c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
503c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
504c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
505c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
506c2248fa2SJens Schweikhardt
5070d533e43SRuslan Ermilov20020815:
5080d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
5090d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
5100d533e43SRuslan Ermilov	again.
5110d533e43SRuslan Ermilov
51233c1de7dSRuslan Ermilov20020729:
51333c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
51433c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
51533c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
51633c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
51733c1de7dSRuslan Ermilov
5182b877facSJulian Elischer20020702:
5192b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
5202b877facSJulian Elischer	There are still some minor problems with some signals but the
5212b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
5222b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
5232b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
5242b877facSJulian Elischer
52506596d37SWarner Losh20020701:
52606596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
52706596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
52806596d37SWarner Losh	GNOME.
52906596d37SWarner Losh
53095ba4330SJacques Vidrine20020511:
53195ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
53295ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
53395ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
53495ba4330SJacques Vidrine	with the set-user-ID bit set.
53595ba4330SJacques Vidrine
536a81da3c9SDavid E. O'Brien20020510:
537f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
538f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
5394b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
540f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
541f50caf6fSDavid E. O'Brien
542f50caf6fSDavid E. O'Brien20020510:
543a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
544a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
545a81da3c9SDavid E. O'Brien	and then do a cvs update.
546a81da3c9SDavid E. O'Brien
547528a0ef5SJacques Vidrine20020421:
548528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
549528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
550528a0ef5SJacques Vidrine
55185aa5a2eSGregory Neil Shapiro20020404:
55285aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
55385aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
55485aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
55585aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
55685aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
55785aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
55885aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
55985aa5a2eSGregory Neil Shapiro
5608f1e4358SRuslan Ermilov20020403:
5618f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
5628f1e4358SRuslan Ermilov
5632292c02eSWarner Losh20020315:
5642292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
5652292c02eSWarner Losh
56669f7bcf3SWarner Losh20020225:
56769f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
56869f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
56969f7bcf3SWarner Losh
5708f35c493SWarner Losh20020217:
5718f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
5728f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
5738f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
5748f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
5758f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
5768f35c493SWarner Losh
577835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
578835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
579835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
580835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
581835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
582835284beSWarner Losh	and group must be merged from src/etc/group and
583835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
584835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
585835284beSWarner Losh	mergemaster before this will work if you are updating from a
586835284beSWarner Losh	very old version of current.  The updating recipe has changed
587835284beSWarner Losh	as of this date.
588835284beSWarner Losh
589fa9401c1SWarner Losh20020112:
590fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
591fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
592fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
593fa9401c1SWarner Losh	you have local modifications, you can use
594fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
595fa9401c1SWarner Losh	/etc/pam.d.
596fa9401c1SWarner Losh
597fa9401c1SWarner Losh	Please see the following url for more details:
598fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
59947d0d01fSWarner Losh20011229:
60047d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
60147d0d01fSWarner Losh	networkfs_types, please note that it has changed
60247d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
60347d0d01fSWarner Losh
604514318a8SWarner Losh20011220:
605514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
606514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
607514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
608514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
609514318a8SWarner Losh	version have now been merged back into the base system's
610514318a8SWarner Losh	version now.  The only user-visible change resulting from this
611514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
612514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
613514318a8SWarner Losh	as well.  (There has never been rc file support for
614514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
615514318a8SWarner Losh	reverted by the time the changes are MFCed.)
616514318a8SWarner Losh
617514318a8SWarner Losh20011215:
618514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
619514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
620514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
621514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
622514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
623514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
624514318a8SWarner Losh	will need to be customized then for `odd' densities using
625514318a8SWarner Losh	fdcontrol(8).
626514318a8SWarner Losh
6272d22e2bfSWarner Losh20011209:
6282d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
6292d22e2bfSWarner Losh	and truss(1) now works again.
6302d22e2bfSWarner Losh
6319e0428e2SWarner Losh20011207:
6329e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
6339e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
6349e0428e2SWarner Losh	see
6359e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
6369e0428e2SWarner Losh	for details.
6379e0428e2SWarner Losh
6389bab8c59SWarner Losh20011204:
6399bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
6409bab8c59SWarner Losh	kernel and burncd to be in sync.
6419bab8c59SWarner Losh
642e57d8b01SWarner Losh20011203:
643e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
644e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
645e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
646e57d8b01SWarner Losh	not there already.
647e57d8b01SWarner Losh
648e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
649e57d8b01SWarner Losh	until the issue has been resolved.
650e57d8b01SWarner Losh
651b001d36fSJacques Vidrine20011202:
652b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
653b001d36fSJacques Vidrine	patched.
654b001d36fSJacques Vidrine
6554b676ec1SWarner Losh20011126:
6564b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
6575ebbf43eSWarner Losh	after this date.  You need to do this only once.
6584b676ec1SWarner Losh
659d961e462SWarner Losh20011103:
660d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
661d961e462SWarner Losh	edges may be left, but for the most part things should be
6624b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
663d961e462SWarner Losh
664d961e462SWarner Losh20011030:
665d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
666d961e462SWarner Losh	choppy waves in the upgrade process.
667d961e462SWarner Losh
6681fe003b6SWarner Losh20011030:
669a4b6fda0SWarner Losh	The asr driver problem has been resolved.
6701fe003b6SWarner Losh
6711fe003b6SWarner Losh20011027:
6721fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
6731fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
6741fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
6751fe003b6SWarner Losh	try to use from this date forward.
6761fe003b6SWarner Losh
6771fe003b6SWarner Losh20011025:
6781fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
6791fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
6801fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
6811fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
6821fe003b6SWarner Losh	TARGET_ARCH=i386.
6831fe003b6SWarner Losh
684d05f9643SWarner Losh20011001:
685d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
686d05f9643SWarner Losh	You must recompile both the kernel and userland applications
687d05f9643SWarner Losh	at the same time.
688d05f9643SWarner Losh
68958970f85SWarner Losh20010929:
69058970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
69158970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
69258970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
69358970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
6949d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
69558970f85SWarner Losh
69658970f85SWarner Losh20010927:
69758970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
69858970f85SWarner Losh	To disable ACPI you can add
69966ff0e67SMax Khon		hint.acpi.0.disabled="1"
70058970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
70158970f85SWarner Losh	loader "ok" prompt).
70258970f85SWarner Losh
70358970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
70458970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
70558970f85SWarner Losh	file and not list acpi in that list.
706378f4486SAlfred Perlstein
7075119d237SWarner Losh20010924:
7085119d237SWarner Losh	The buildworld has been fixed.  You may need to install
7095119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
7108b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
7118b039fffSWarner Losh	get them installed on every installworld, or execute the
7128b039fffSWarner Losh	following to get them installed only once:
7138b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
71458970f85SWarner Losh		make all install
7158b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
7165119d237SWarner Losh
7173c293725SWarner Losh20010919:
7183c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
7193c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
7203c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
721772730c7SWarner Losh	workaround is to add
7223c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
7233c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
7243c293725SWarner Losh	can be removed afterwards.
7253c293725SWarner Losh
7263c293725SWarner Losh	A proper fix to the buildworld target is needed.
7273c293725SWarner Losh
7283c293725SWarner Losh20010918:
7293c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
7303c293725SWarner Losh	NFS may be unstable after this date.
7313c293725SWarner Losh
7323c293725SWarner Losh20010912:
7333c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
7343c293725SWarner Losh	the kernel.  While a few problems were introduced in the
7353c293725SWarner Losh	initial commit, most of the major ones have been found and
7363c293725SWarner Losh	corrected.
7373c293725SWarner Losh
7383c293725SWarner Losh20010901:
7393c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
7403c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
7413c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
7423c293725SWarner Losh	have been rectified around this date.
7433c293725SWarner Losh
74498b17b95SWarner Losh20010823:
74598b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
74698b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
74798b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
74898b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
74998b17b95SWarner Losh 	sure that user or group bind has read (and not write)
75098b17b95SWarner Losh 	permission for your name server configuration and that it
75198b17b95SWarner Losh 	has read and write permission for your slave zone files and
75298b17b95SWarner Losh 	directory.
75398b17b95SWarner Losh
75498b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
75598b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
75698b17b95SWarner Losh
75798b17b95SWarner Losh 		named_flags=
75898b17b95SWarner Losh
7597b9786edSMark Murray20010709:
7607b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
7617b9786edSMark Murray	the ability of the shared library major number to handle.
7627b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
7637b9786edSMark Murray	solution is to rebuild those ports.
7647b9786edSMark Murray
7651d28950eSWarner Losh20010628:
7661d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
7671d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
7681d28950eSWarner Losh
769e72fd46aSWarner Losh20010625:
77098b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
77198b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
77298b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
77398b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
77498b17b95SWarner Losh	IRQ configuration needs more safety belts.
77516de1a07SWarner Losh
7760d415dffSWarner Losh20010617:
777e72fd46aSWarner Losh	Softupdates problems have been corrected.
7780d415dffSWarner Losh
7790d415dffSWarner Losh20010614:
7800d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
7810d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
7820d415dffSWarner Losh	kernel building methods.
7830d415dffSWarner Losh
7848b9959adSWarner Losh20010613:
7858b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
7868b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
787e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
788e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
7898b9959adSWarner Losh
790e72fd46aSWarner Losh20010613:
7918b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
792e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
793e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
7948b9959adSWarner Losh
7950d415dffSWarner Losh20010612:
7960d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
7970d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
7980d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
7990d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
8000d415dffSWarner Losh	until this bug is fixed.
8010d415dffSWarner Losh
802e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
803e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
804ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
805e72fd46aSWarner Losh
8060d415dffSWarner Losh20010610:
8070d415dffSWarner Losh	Locale names have changed to match other systems better.
8080d415dffSWarner Losh
8096ccdb5e4SWarner Losh20010604:
8106ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
8116ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
8126ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
8133590182eSWarner Losh	Interrupt storms look a lot like a hang.
8143590182eSWarner Losh
8153590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
8163590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
8173590182eSWarner Losh	it is).
8183590182eSWarner Losh
8193590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
8203590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
8213590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
8223590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
8236ccdb5e4SWarner Losh
8240bc62786SWarner Losh20010530:
8250bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
8260bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
8270bc62786SWarner Losh	a limited time.  If you see
8280bc62786SWarner Losh
8290bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
8300bc62786SWarner Losh
8310bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
8320bc62786SWarner Losh	COPY=-C.
8330bc62786SWarner Losh
83468a38c6cSWarner Losh20010525:
835b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
836c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
837c4f4a728SWarner Losh	definitely is in bad shape.
83868a38c6cSWarner Losh
839ed0f29caSWarner Losh20010521:
840ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
841ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
842ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
843ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
844ed0f29caSWarner Losh	is
845ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
846ed0f29caSWarner Losh
84780c16af9SWarner Losh20010520:
84868a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
84980c16af9SWarner Losh
85080c16af9SWarner Losh20010519:
85180c16af9SWarner Losh	pccard has had much reorganizational work done to it over
85280c16af9SWarner Losh	the past few days.  Everything should still work, but if
85380c16af9SWarner Losh	not, please contact imp@freebsd.org.
85480c16af9SWarner Losh
855a45f2d05SWarner Losh20010517:
856a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
857a45f2d05SWarner Losh	userland at the same time.
858a45f2d05SWarner Losh
859a45f2d05SWarner Losh20010517:
860a45f2d05SWarner Losh	New ncurses imported.
861a45f2d05SWarner Losh
8622988afcaSWarner Losh20010512:
8632988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
8642988afcaSWarner Losh	will be the only way to go starting July 1.
8652988afcaSWarner Losh
8661a33dba7SWarner Losh20010504:
8671a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
8681a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
8691a33dba7SWarner Losh
87009946a51SWarner Losh20010502:
87109946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
87209946a51SWarner Losh
87309946a51SWarner Losh20010501:
87409946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
87509946a51SWarner Losh
87609946a51SWarner Losh20010430:
877a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
87809946a51SWarner Losh	go back in the water.
87909946a51SWarner Losh
88009946a51SWarner Losh20010429:
88109946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
88209946a51SWarner Losh	this date, but before the correction date.
88309946a51SWarner Losh
88491dd3b53SWarner Losh20010423:
88591dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
88691dd3b53SWarner Losh
88791dd3b53SWarner Losh20010411:
88891dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
88991dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
89091dd3b53SWarner Losh	Update only if you understand that you must not use the old
89191dd3b53SWarner Losh	fsck with the new kernel ever.
89291dd3b53SWarner Losh
893933b3269SWarner Losh20010330:
894933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
895c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
896933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
897933b3269SWarner Losh
898933b3269SWarner Losh20010319:
899933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
900933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
901933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
902f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
90309946a51SWarner Losh
90409946a51SWarner Losh20010315:
90509946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
906ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
90709946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
908933b3269SWarner Losh
909933b3269SWarner Losh20010312:
910933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
911933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
912933b3269SWarner Losh
913933b3269SWarner Losh20010312:
914933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
915933b3269SWarner Losh	instead of ad-hoc.
916933b3269SWarner Losh
917933b3269SWarner Losh20010310:
918f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
919933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
920933b3269SWarner Losh	ssh might not work if you don't.
921933b3269SWarner Losh
92262353691SWarner Losh20010303:
92362353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
92462353691SWarner Losh	which means that you must include the miibus in your kernel if
92562353691SWarner Losh	you use the ed driver.
92662353691SWarner Losh
927d325cf65SWarner Losh20010220:
928d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
929d325cf65SWarner Losh	safe to go back into the water.
930d325cf65SWarner Losh
931024daae6SWarner Losh20010211:
932024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
933024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
934024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
935024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
936024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
937024daae6SWarner Losh
938024daae6SWarner Losh	To get to the new system, you'll need to use the following
939024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
940024daae6SWarner Losh	don't have to move this to the updating section.
941024daae6SWarner Losh
942024daae6SWarner Losh	To get around the installworld problem, do:
943024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
944024daae6SWarner Losh		# make install
945024daae6SWarner Losh		# cd /usr/src
946024daae6SWarner Losh		# make installworld
947024daae6SWarner Losh	If that doesn't work, then try:
948024daae6SWarner Losh		# make -k installworld
949024daae6SWarner Losh		# make installworld
950024daae6SWarner Losh
951024daae6SWarner Losh20010207:
952024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
953024daae6SWarner Losh	do not include devfs in your kernel as problems result.
954024daae6SWarner Losh
955024daae6SWarner Losh20010205:
9567595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
957024daae6SWarner Losh	Remove them from your config.
958024daae6SWarner Losh
9591e159248SWarner Losh20010122:
9601e159248SWarner Losh	****************************** WARNING ******************************
9611e159248SWarner Losh			buildkernel has been changed slightly
9621e159248SWarner Losh	****************************** WARNING ******************************
9631e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
9641e159248SWarner Losh	should update your scripts and make.conf accordingly.
9651e159248SWarner Losh
9661e159248SWarner Losh20010119:
9671e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
9681e159248SWarner Losh	This requires a new config to build correctly.
9691e159248SWarner Losh
970aac7dfeaSWarner Losh20010116:
971ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
972aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
973aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
974aac7dfeaSWarner Losh
975aac7dfeaSWarner Losh20010110:
976aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
977aac7dfeaSWarner Losh
978aac7dfeaSWarner Losh20010102:
979aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
980aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
981aac7dfeaSWarner Losh
98263c90c9eSWarner Losh20010101:
98363c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
98463c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
9855fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
98663c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
98763c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
98863c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
98963c90c9eSWarner Losh	might have been ignored by the -k option.
99063c90c9eSWarner Losh
9915fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
9925fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
9935fd2a895SWarner Losh	of this working.
9945fd2a895SWarner Losh
995aac7dfeaSWarner Losh20001228:
996aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
997ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
998aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
999aac7dfeaSWarner Losh
1000de2bcc63SWarner Losh20001218:
1001de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1002de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1003de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1004de2bcc63SWarner Losh	cards will not be recognized without it.
1005de2bcc63SWarner Losh
1006960773f7SWarner Losh20001205:
1007960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1008960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1009960773f7SWarner Losh	adding the following in pam.conf:
1010960773f7SWarner Losh
1011960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1012960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1013960773f7SWarner Losh	sshd    session required        pam_permit.so
1014960773f7SWarner Losh
10150acc635eSWarner Losh20001031:
10160acc635eSWarner Losh	cvs updated to 1.11.
10170acc635eSWarner Losh
10180acc635eSWarner Losh20001020:
10190acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
10200acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
10210acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
10220acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
10230acc635eSWarner Losh	workaround.
10240acc635eSWarner Losh
10250acc635eSWarner Losh20001010:
10260acc635eSWarner Losh	****************************** WARNING ******************************
10270acc635eSWarner Losh				Sendmail has been updated.
10280acc635eSWarner Losh	****************************** WARNING ******************************
10290acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
10300acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
10310acc635eSWarner Losh	  is set.
10320acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
10330acc635eSWarner Losh	  commands.
10340acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
10350acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
10360acc635eSWarner Losh	  in /usr/share/sendmail/cf.
10370acc635eSWarner Losh	o sendmail.cw changed to local-host-names
10380acc635eSWarner Losh
10390acc635eSWarner Losh	More details can be found at
10400acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
10410acc635eSWarner Losh
10426e98a146SWarner Losh20001009:
10436e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
10446e98a146SWarner Losh	your entire ports tree, or you will have problems.
10456e98a146SWarner Losh
10466e98a146SWarner Losh20001006:
1047685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
10486e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
10496e98a146SWarner Losh	/usr/bin/miniperl.
10506e98a146SWarner Losh
1051073113a4SWarner Losh20001005:
1052073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1053685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1054073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1055073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1056073113a4SWarner Losh	tree for anything to work.
1057073113a4SWarner Losh
10580acc635eSWarner Losh20000928:
10590acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
10600acc635eSWarner Losh
1061be3885b3SWarner Losh20000916:
1062be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1063be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1064be3885b3SWarner Losh	same time as your kernel.
1065be3885b3SWarner Losh
106676ec9675SWarner Losh20000914:
106776ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
106876ec9675SWarner Losh	include the device will cause suspended laptops losing time
106976ec9675SWarner Losh	when they resume.  Include
107076ec9675SWarner Losh		device		pmtimer
107176ec9675SWarner Losh	in your config file and
107201b9a434SWarner Losh		hint.pmtimer.0.at="isa"
107376ec9675SWarner Losh	to your /boot/device.hints file.
107476ec9675SWarner Losh
1075f4865386SMark Murray20000911:
1076f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1077f4865386SMark Murray	rather than an option. The supplied kernel config files have
1078f4865386SMark Murray	been updated. You will need to do something similar in your
1079f4865386SMark Murray	own kernel config file.
1080f4865386SMark Murray	Remove:
1081f4865386SMark Murray		options		RANDOMDEV
1082f4865386SMark Murray	Add:
1083f4865386SMark Murray		device		random
1084f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1085f4865386SMark Murray	nothing.
1086f4865386SMark Murray
1087d594498fSWarner Losh20000909:
1088d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1089d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1090d594498fSWarner Losh	reflect this if you load this module at boot time.
1091d594498fSWarner Losh	The line should read:
1092d594498fSWarner Losh		random_load="YES"
1093d594498fSWarner Losh
10940deb7ddcSWarner Losh20000907:
10950deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
109616eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
109716eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
109816eb772dSWarner Losh	sure you don't have model loading problems which might at
109916eb772dSWarner Losh	first blush appear related to SMP.
110052bf24e7SWarner Losh
11015a01880bSWarner Losh20000906:
11025a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
11035a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
11045a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
11055a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
11065a01880bSWarner Losh	don't have one, and you have host.conf.
11075a01880bSWarner Losh
11082b41163cSWarner Losh20000905:
110938d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
111038d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
111138d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
111238d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
111338d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
111438d6ecd2SWarner Losh
111538d6ecd2SWarner Losh20000905:
11168aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
11178aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
11188aab4bc7SWarner Losh	is /boot/kernel.
11198aab4bc7SWarner Losh
11208aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
112138d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
112238d6ecd2SWarner Losh	installkernel/installworld dance.
11232b41163cSWarner Losh
1124d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1125d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1126d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1127d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1128d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1129d594498fSWarner Losh
1130d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1131d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1132d594498fSWarner Losh		chflags noschg /kernel.old
1133d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1134d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1135d594498fSWarner Losh	fi
1136d594498fSWarner Losh
1137c22a309cSWarner Losh20000904:
1138c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1139c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1140c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1141c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1142c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1143c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1144c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1145c22a309cSWarner Losh	is not likely to be generated.
1146c22a309cSWarner Losh
1147fdb9f54dSWarner Losh20000825:
1148fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
11499c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
11509c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
11519c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
11529c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
11539c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
11549c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
11559c1a7444SWarner Losh	kernel.
11569c1a7444SWarner Losh
11579c1a7444SWarner Losh20000821:
11589c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
11599c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
11609c1a7444SWarner Losh	/boot/loader.conf.
1161fdb9f54dSWarner Losh
11628f250aa7SWarner Losh20000812:
11635da0d091SWarner Losh	suidperl is now always built and installed on the system, but
11645da0d091SWarner Losh	with permissions of 511.  If you have applications that use
11655da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
11665da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
11675da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
11685da0d091SWarner Losh	will fix this until the next build.
11695da0d091SWarner Losh
11705da0d091SWarner Losh20000812:
11718f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
11728f250aa7SWarner Losh	visible changes that may immediately affect your configuration
11738f250aa7SWarner Losh	include:
11748f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
11758f250aa7SWarner Losh	- newaliases limited to root and trusted users
11768f250aa7SWarner Losh	- MSA port (587) turned on by default
11778f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
11788f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
11798f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
11808f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
11818f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
11828f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
11838f250aa7SWarner Losh
118471c38472SWarner Losh20000810:
118571c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
118671c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
118771c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
118871c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
118971c38472SWarner Losh	specific use for it.
119071c38472SWarner Losh
119171c38472SWarner Losh20000729:
119271c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
119371c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
119471c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
119571c38472SWarner Losh	afterwards (unless the variables already are set, of course):
119671c38472SWarner Losh		# Enable network daemons for user convenience.
119771c38472SWarner Losh		inetd_enable="YES"
119871c38472SWarner Losh		portmap_enable="YES"
119971c38472SWarner Losh		sendmail_enable="YES"
120071c38472SWarner Losh
120171c38472SWarner Losh20000728:
120271c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
120371c38472SWarner Losh	will need to change that to nullfs_load="YES".
120471c38472SWarner Losh
12051dece4a9SWarner Losh20000728:
12061dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
12071dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
12081dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
12091dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
12101dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
12111dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
12121dece4a9SWarner Losh	to /MYKERNEL.
12131dece4a9SWarner Losh
1214409e887cSWarner Losh20000711:
1215409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1216409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1217409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1218409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1219409e887cSWarner Losh	for details on potential problems that you might have and how
1220409e887cSWarner Losh	to get around them.
1221409e887cSWarner Losh
1222409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1223409e887cSWarner Losh	clauses above, you needn't worry.
1224409e887cSWarner Losh
1225409e887cSWarner Losh20000711:
1226409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1227409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1228409e887cSWarner Losh	in the number of changed programs the first time when you run
1229409e887cSWarner Losh	mergemaster to get a new /etc/security.
1230409e887cSWarner Losh
1231673d13f2SWarner Losh20000710:
1232673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1233673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1234673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1235673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1236673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1237673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1238673d13f2SWarner Losh	errors. (see below, 20000624).
1239673d13f2SWarner Losh
1240bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
12411dece4a9SWarner Losh
1242673d13f2SWarner Losh20000709:
1243c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1244c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1245c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1246673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1247673d13f2SWarner Losh
1248e98e26cdSWarner Losh20000706:
1249e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1250e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1251e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1252f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1253e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
12542c021c6cSMark Ovens	interim if needed.
1255e98e26cdSWarner Losh
1256e98e26cdSWarner Losh20000705:
1257e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1258e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1259e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1260e98e26cdSWarner Losh	details.
1261e98e26cdSWarner Losh
1262c373950eSWarner Losh20000704:
12632f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
12642f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
12652f961bc8SWarner Losh
12662f961bc8SWarner Losh20000704:
1267c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1268c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1269c373950eSWarner Losh	rc.d scripts that haven't been updated.
1270c373950eSWarner Losh
127127dc3a2bSWarner Losh20000630:
127227dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
127327dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
127427dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
127527dc3a2bSWarner Losh
1276b8c215acSWarner Losh20000625:
1277b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
127827dc3a2bSWarner Losh	system installed in order to build the system and kernel.
127927dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
128027dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
128127dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
128227dc3a2bSWarner Losh	were required.  You should check with the latest collections
128327dc3a2bSWarner Losh	to make sure that these haven't changed.
1284b8c215acSWarner Losh
12857b990719SWarner Losh20000624:
12867b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
12877b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
12887b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
12891a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
12907b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
12917b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
12927b990719SWarner Losh	date to the completion of the work.
12937b990719SWarner Losh
129427dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
129527dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
129627dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
129727dc3a2bSWarner Losh	recreate the random and urandom devices.
129827dc3a2bSWarner Losh
129981e54c50SWarner Losh20000622:
130081e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
130181e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
130281e54c50SWarner Losh	that used to be required when updating.
130381e54c50SWarner Losh
130439943833SWarner Losh20000621:
13052c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
13062a2f33fbSDaniel Baker	the config file update procedure.
13072a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1308c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
130959df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
131059df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
131139943833SWarner Losh
1312290f9ad8SWarner Losh20000620:
1313290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1314290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1315290f9ad8SWarner Losh	that workaround will no longer be required.
1316290f9ad8SWarner Losh
131790fb6346SWarner Losh20000615:
131890fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
131990fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
132090fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
132190fb6346SWarner Losh	devices.
132290fb6346SWarner Losh
1323f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1324f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1325f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1326f75f65bbSWarner Losh	may work).
1327f75f65bbSWarner Losh
1328ba26da8eSWarner Losh20000612:
1329ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1330290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1331c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1332290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1333f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1334f54a3542SWarner Losh	NEWCARD for examples of the new format.
1335290f9ad8SWarner Losh
13369698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
13379698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
13389698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
13399698f2c0SWarner Losh	in it.
1340bbcc5149SWarner Losh
1341d65850ebSWarner Losh20000522:
1342ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1343d65850ebSWarner Losh	building a kernel after this point is advised that they need
1344d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1345d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1346d65850ebSWarner Losh
1347d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1348d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1349d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1350d9583a00SWarner Losh	is resolved.
1351d9583a00SWarner Losh
13528039cedeSWarner Losh20000513:
13538039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
13548039cedeSWarner Losh
1355d65850ebSWarner Losh20000510:
13568039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
13578039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
13588039cedeSWarner Losh	is requires for the boot blocks to build properly.
13598039cedeSWarner Losh
13608039cedeSWarner Losh20000503:
13618039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
13628039cedeSWarner Losh	is now available.
13638039cedeSWarner Losh
1364d65850ebSWarner Losh20000502:
1365d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1366d65850ebSWarner Losh	connected to the kernel building instead.
1367d65850ebSWarner Losh
1368be149406SNik Clayton20000427:
13698039cedeSWarner Losh	You may need to build gperf
13708039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
13718039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
13728039cedeSWarner Losh	an option only in -current.
13738039cedeSWarner Losh
13742b8dd5f4SWarner Losh20000417:
13752b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1376f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
13772b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
13782b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
13792c021c6cSMark Ovens	before you reboot, you'll need to issue:
13802b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
13812b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
13822b8dd5f4SWarner Losh
13838d9f1945SWarner Losh20000320:
13842b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
13852b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
13862b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1387ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
13882b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
13898d9f1945SWarner Losh
1390f8ab1dd6SWarner Losh20000319:
1391f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1392f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1393f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1394f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1395f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1396f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1397f8ab1dd6SWarner Losh
139819cada77SWarner Losh20000318:
1399f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
140019cada77SWarner Losh	Large kernel changes are being committed and are in the
140119cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
140219cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
140319cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
140419cada77SWarner Losh	that you are loading are up to date.
1405ba228352SWarner Losh
140619cada77SWarner Losh20000315:
14076d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
14086d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
14096d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
14106d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
14116d23c382SWarner Losh	boot.
14126d23c382SWarner Losh
14136d23c382SWarner Losh20000315:
141419cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
141519cada77SWarner Losh	to upgrade to 4.0 from 3.x.
141657199806SWarner Losh
1417dc0dbf5cSWarner LoshCOMMON ITEMS:
1418dc0dbf5cSWarner Losh
1419a24eff53SWarner Losh	General Notes
1420a24eff53SWarner Losh	-------------
1421a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1422a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1423a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1424a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1425a24eff53SWarner Losh	or several minor releases, or when several months have passed
1426a24eff53SWarner Losh	on the -current branch).
1427a24eff53SWarner Losh
14285780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
14295780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
14305780f3baSWarner Losh	environment when searching for values for global variables.
14315780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
14325780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
14335780f3baSWarner Losh	page for more details.
14345780f3baSWarner Losh
1435dc0dbf5cSWarner Losh	To build a kernel
1436dc0dbf5cSWarner Losh	-----------------
1437ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1438f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1439ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1440282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1441282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1442dc0dbf5cSWarner Losh
1443ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1444ba01eb20SWarner Losh	--------------------------------------------------------------
14450fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
14460fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
14470fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
14480fbd2da9SKen Smith
14490fbd2da9SKen Smith	cd src/sys/${arch}/conf
145047d0d01fSWarner Losh	config KERNEL_NAME_HERE
14510fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1452ba01eb20SWarner Losh	make depend
1453ba01eb20SWarner Losh	make
1454ba01eb20SWarner Losh	make install
1455ba01eb20SWarner Losh
1456ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1457ba01eb20SWarner Losh
1458ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1459ba01eb20SWarner Losh	-----------------------------------------------------------
146063cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
146163cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
146263cb445eSWarner Losh
1463f643de42SWarner Losh	<make sure you have good level 0 dumps>
146463cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
146563cb445eSWarner Losh	make buildworld
146663cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
146763cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
146863cb445eSWarner Losh							[1]
146963cb445eSWarner Losh	<reboot in single user>				[3]
14708633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
147163cb445eSWarner Losh	mergemaster -p					[5]
147263cb445eSWarner Losh	make installworld
147363cb445eSWarner Losh	mergemaster					[4]
147463cb445eSWarner Losh	<reboot>
147563cb445eSWarner Losh
1476759f0aefSWarner Losh
1477f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1478f27b1fceSJoseph Koshy	--------------------------------------------------
1479f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1480f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1481f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1482f27b1fceSJoseph Koshy	# size.
1483f27b1fceSJoseph Koshy
1484f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1485f27b1fceSJoseph Koshy	<boot into -stable>
1486f27b1fceSJoseph Koshy	make buildworld
1487f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1488f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1489f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1490f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1491f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1492f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1493f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1494f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1495f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1496f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1497f27b1fceSJoseph Koshy	<reboot into current>
1498f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1499f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1500f27b1fceSJoseph Koshy 	<reboot>
1501f27b1fceSJoseph Koshy
1502f27b1fceSJoseph Koshy
1503f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1504f27b1fceSJoseph Koshy	----------------------------------------------
15055c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
15065c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
15075c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
15085c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1509ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1510f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1511f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1512f643de42SWarner Losh	# space on /.
1513f643de42SWarner Losh
1514f643de42SWarner Losh	<make sure you have good level 0 dumps>
1515fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
151621c075eaSWarner Losh	make buildworld					[9]
1517c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1518d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1519be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1520fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1521fc8c157fSWarner Losh							[1]
1522fc8c157fSWarner Losh	<reboot in single user>				[3]
15238633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
1524835284beSWarner Losh	mergemaster -p					[5]
1525f8a4c901SWarner Losh	rm -rf /usr/include/g++
1526ba26da8eSWarner Losh	make installworld
1527a6cd4f9dSWarner Losh	mergemaster					[4]
1528ba26da8eSWarner Losh	<reboot>
1529ba26da8eSWarner Losh
1530fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1531fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1532fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1533fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1534fdb9f54dSWarner Losh	the UPDATING entries.
1535ba26da8eSWarner Losh
15361dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
15371dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
15381dece4a9SWarner Losh	your sources that you have read and understood all the recent
15391dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
15401dece4a9SWarner Losh	much fewer pitfalls.
15411dece4a9SWarner Losh
1542134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1543134d2e86SWarner Losh	should disable them at this point so they don't crash your
1544134d2e86SWarner Losh	system on reboot.
1545134d2e86SWarner Losh
15469c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
15479c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
15489c1a7444SWarner Losh	configuration.
15499c1a7444SWarner Losh
1550ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1551ee6e1fc3SWarner Losh		fsck -p
1552ee6e1fc3SWarner Losh		mount -u /
1553ee6e1fc3SWarner Losh		mount -a
1554ee6e1fc3SWarner Losh		cd /usr/src
155547d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1556f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1557f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1558b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1559b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1560b705ae10SWarner Losh	be ignored while you proceed to the next step.
1561ee6e1fc3SWarner Losh
1562a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1563a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1564a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1565a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1566a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1567a6cd4f9dSWarner Losh	for potential gotchas.
1568a6cd4f9dSWarner Losh
1569835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1570835284beSWarner Losh	you may need to do this if you get unknown user in the following
1571835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1572835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1573835284beSWarner Losh	install) after the buildworld before this step if you last updated
1574835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1575835284beSWarner Losh
1576bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1577bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1578bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1579bd79cf40SWarner Losh		ok unload
1580bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1581bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1582bd79cf40SWarner Losh	described here.
1583fc8c157fSWarner Losh
1584fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1585fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1586fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1587fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1588fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1589fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1590fc8c157fSWarner Losh
1591c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1592c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1593c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1594c74fe6afSWarner Losh	that is hard to boot to recover.
1595c74fe6afSWarner Losh
159621c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
159721c075eaSWarner Losh	cvs prune empty directories.
15988633bbeaSBrooks Davis
15998633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
16008633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
16018633bbeaSBrooks Davis	takes care of this.
1602dc0dbf5cSWarner LoshFORMAT:
1603dc0dbf5cSWarner Losh
1604f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
16051fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1606f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1607f8ab1dd6SWarner Loshprevious releases if your system is older than this.
16081fc1a0dcSWarner Losh
1609e72fd46aSWarner LoshCopyright information:
1610e72fd46aSWarner Losh
16119698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1612e72fd46aSWarner Losh
1613772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1614772730c7SWarner Loshmodification, in full or in part, in any form or format of this
16159698f2c0SWarner Loshdocument are permitted without further permission from the author.
1616e72fd46aSWarner Losh
1617e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1618e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1619e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1620e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1621e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1622e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1623e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1624e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1625e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1626e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1627e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1628e72fd46aSWarner Losh
1629e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1630e72fd46aSWarner Loshauthor a beer.
1631e72fd46aSWarner Losh
163222306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1633772730c7SWarner Loshthis document.
1634772730c7SWarner Losh
163597d92980SPeter Wemm$FreeBSD$
1636