xref: /freebsd/UPDATING (revision a6c26e1ca86cd25fe8acca5dce91d889f8da7fbb)
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
20c2dba668SNate Lawson20040630:
218ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
228ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
23a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
24a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
25a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
26a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
27a6c26e1cSBruce M Simpson	example of such changes.
288ed370fdSJulian Elischer
298ed370fdSJulian Elischer20040630:
30c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
31c2dba668SNate Lawson	will be printed on console indicating that ACPI has been disabled
32c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
33c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
34c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
35c2dba668SNate Lawson	loader prompt.
36c2dba668SNate Lawson
378ee2ac9eSMax Laier20040623:
388ee2ac9eSMax Laier	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is priviledge
398ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
408ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
418ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
428ee2ac9eSMax Laier
433db5687dSBrooks Davis20040622:
443db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
453db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
463db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
473db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
483db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
493db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
503db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
513db5687dSBrooks Davis
52e0ae81f3SDag-Erling Smørgrav20040621:
53e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
54e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
55e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
56e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
57e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
58e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
59e0ae81f3SDag-Erling Smørgrav	during the next reboot.
60e0ae81f3SDag-Erling Smørgrav
614717d22aSJohn Polstra20040614:
624717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
634717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
644717d22aSJohn Polstra	the ips module and any third-party modules which call
654717d22aSJohn Polstra	sema_timedwait.
664717d22aSJohn Polstra
676cb7a382SMax Laier20040613:
686cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
696cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
70df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
71df843493SMax Laier	please recompile and reinstall world.
726cb7a382SMax Laier
732454685eSJulian Elischer20040607:
742454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
752454685eSJulian Elischer	requires that you re-run config after updating your tree.
762454685eSJulian Elischer
7764fef830SSeigo Tanimura20040601:
7864fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
7964fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
8064fef830SSeigo Tanimura	kernel configuration.
8164fef830SSeigo Tanimura
82bb4f06e7SAndre Oppermann20040423:
83bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
84bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
85bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
86bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
87bb4f06e7SAndre Oppermann
8805641e82SColin Percival20040420:
8905641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
9005641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
9105641e82SColin Percival	20040406.
9205641e82SColin Percival
93d0dc9183SWarner Losh20040414:
94d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
95d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
96d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
97d0dc9183SWarner Losh
98d0dc9183SWarner Losh20040412:
99d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
100d0dc9183SWarner Losh	drive is still broken.
101d0dc9183SWarner Losh
102d0dc9183SWarner Losh20040410:
103d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
104d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
105d0dc9183SWarner Losh	the unanticipated problems have been resolved.
106d0dc9183SWarner Losh
1078633bbeaSBrooks Davis20040409:
1088633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
1098633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
1108633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
1118633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
11276c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
1138633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
1148633bbeaSBrooks Davis
115d40d033aSRobert Watson20040322:
116d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
117d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
118d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
119d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
120d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
121d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
122d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
123d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
124d40d033aSRobert Watson	locking is merged to permit this to take place.
125d40d033aSRobert Watson
126ec9b318eSGarance A Drosehn20040310:
127ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
128ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
129ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
130ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
131ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
132ec9b318eSGarance A Drosehn
133fc28f1ffSMax Laier20040308:
134fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
135fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
1364c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
1374c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
138fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
139fc28f1ffSMax Laier	pf system consists of the following three devices:
140fc28f1ffSMax Laier	device		pf		# required
141fc28f1ffSMax Laier	device		pflog		# optional
142fc28f1ffSMax Laier	device		pfsync		# optional
143fc28f1ffSMax Laier
1443aff5d06SDag-Erling Smørgrav20040303:
1453aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
1463aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
1473aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
1483aff5d06SDag-Erling Smørgrav
1493aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
1503aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
1513aff5d06SDag-Erling Smørgrav
1523aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
1533aff5d06SDag-Erling Smørgrav	to use libpthread instead.
1543aff5d06SDag-Erling Smørgrav
155fd63c5b3SDag-Erling Smørgrav20040226:
1569d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
157fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
158fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
159fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
160fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
161fd63c5b3SDag-Erling Smørgrav
162714ae42aSBruce M Simpson20040225:
163e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
164e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
165e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
166e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
167e07a40f3SBrian Feldman	should remain unaffected.
168e07a40f3SBrian Feldman
169e07a40f3SBrian Feldman20040225:
170714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
171714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
172714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
173714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
174714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
175714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
176714ae42aSBruce M Simpson
177fbd2e692SAndre Oppermann20040224:
178fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
179fbd2e692SAndre Oppermann	and related userland network utilities neccessary.
180fbd2e692SAndre Oppermann
181158b90daSWarner Losh20040222:
182158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
183158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
184158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
185158b90daSWarner Losh	Drivers outside the tree will need to be updated.
186158b90daSWarner Losh
187b7b1e150SMike Makonnen20040207:
188b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
189b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
190b7b1e150SMike Makonnen
191aca89ee6SDaniel Eischen20040130:
192aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
193aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
194aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
195aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
196aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
197aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
198aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
199aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
200aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
201aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
202aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
203aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
204aca89ee6SDaniel Eischen	do not work with libpthread.
205aca89ee6SDaniel Eischen
20668b7b3a9SAlex Dupre20040125:
20768b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
20868b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
20968b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
21068b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
21168b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
21268b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
21368b7b3a9SAlex Dupre
214ff46e0deSWarner Losh20040125:
215ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
216ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
217ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
218ff46e0deSWarner Losh
219ce41f4bfSRobert Watson20031213:
220ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
221ce41f4bfSRobert Watson	if the login process is unable to successfully set the
222ce41f4bfSRobert Watson	process credentials to include all groups defined for the
223ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
224ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
225ce41f4bfSRobert Watson	defined, or they will be unable to log in.
226ce41f4bfSRobert Watson
227c124fa05SJohn Baldwin20031203:
228c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
229c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
230c124fa05SJohn Baldwin
2318ad1f5e4SHartmut Brandt20031112:
23230093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
23330093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
23497209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
23597209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
23697209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
23797209ca3SRobert Watson	not know about the new system calls that support the new statfs
2383f631d52SMarcel Moolenaar	structure.
2393f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
2403f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
2413f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
2423f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
2433f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
2443f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
2453f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
2463f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
2473f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
2483f631d52SMarcel Moolenaar	these changes are installed.
24930093b05SWarner Losh
25030093b05SWarner Losh	****************************DANGER*******************************
25130093b05SWarner Losh
25230093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
25330093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
25430093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
25530093b05SWarner Losh	kernel.
25664a18d6fSKirk McKusick
25764a18d6fSKirk McKusick20031112:
2588ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
2598ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
2608ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
2618ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
2628ad1f5e4SHartmut Brandt	sync before rebooting.
2638ad1f5e4SHartmut Brandt
264c53a5d8fSJohn Baldwin20031111:
265c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
266c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
267c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
268c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
269c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
270c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
271c53a5d8fSJohn Baldwin
2728bf455a5SJohn Baldwin20031103:
2738bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
2748bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
2752a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
2768bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
2778bf455a5SJohn Baldwin
2789bf40edeSBrooks Davis20031031:
2799bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
2809bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
2819bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
2829bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
2839bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
2849bf40edeSBrooks Davis	reflect this change.
2859bf40edeSBrooks Davis
28647a42c7aSPoul-Henning Kamp20030928:
28747a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
28847a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
28947a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
29047a42c7aSPoul-Henning Kamp
29107105342SMax Khon20030926:
29207105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
29307105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
29407105342SMax Khon
29517dcd026SSam Leffler20030925:
29617dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
29717dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
29817dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
29917dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
30017dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
30117dcd026SSam Leffler
302fedf1d01SBruce M Simpson20030923:
303fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
304fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
305fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
306fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
307fedf1d01SBruce M Simpson
308db38f9cbSJacques Vidrine20030915:
309db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
310db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
311db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
312db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
313db38f9cbSJacques Vidrine
314c09d2c2bSMike Makonnen20030829:
315c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
316c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
317c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
318c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
319c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
320c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
321c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
322c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
323c09d2c2bSMike Makonnen	may or may not exist on your system.
324c09d2c2bSMike Makonnen
32517c159dcSSøren Schmidt20030824:
32617c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
32717c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
328f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
329f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
33017c159dcSSøren Schmidt
331c1f61aa9SDavid E. O'Brien20030819:
332c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
333c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
334c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
335c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
33669f7bcf3SWarner Losh
33738c962e7SNate Lawson20030728:
33838c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
33938c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
34038c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
34138c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
34238c962e7SNate Lawson	so the quirk can be re-enabled.
34338c962e7SNate Lawson
34474111097SWarner Losh20030724:
34574111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
34674111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
34774111097SWarner Losh
348178cf4e9SWarner Losh20030722:
349178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
350178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
351178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
352178cf4e9SWarner Losh	FPU hardware.
353178cf4e9SWarner Losh
354178cf4e9SWarner Losh20030714:
355178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
356178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
357178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
358178cf4e9SWarner Losh	People should report those issues to current@.
359178cf4e9SWarner Losh
360157c629aSWarner Losh20030711:
361157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
3628b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
36305538fa9SWarner Losh	/usr/obj.
364157c629aSWarner Losh
36574111097SWarner Losh20030610:
36674111097SWarner Losh	Remove deprecated locale names and transition period code
36774111097SWarner Losh	for them, finishing switching to the new scheme. Check your
36874111097SWarner Losh	LANG environment variable.
36974111097SWarner Losh
37074111097SWarner Losh20030609:
37174111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
37274111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
37374111097SWarner Losh	important to remember beforehand if your source tree is on
37474111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
37574111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
37674111097SWarner Losh	kernel.
37774111097SWarner Losh
37874111097SWarner Losh20030605:
3796cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
3806cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
3816cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
3826cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
3836cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
3846cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
3856cc6353fSMarcel Moolenaar
3866cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
3876cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
3886cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
3896cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
3906cc6353fSMarcel Moolenaar		:
3916cc6353fSMarcel Moolenaar
3926cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
3936cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
3946cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
3956cc6353fSMarcel Moolenaar
39652b47445SMark Murray20030505:
39752b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
39852b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
39952b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
40052b47445SMark Murray
401a26df538SWarner Losh20030502:
402a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
403a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
404a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
405a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
406a26df538SWarner Losh
4074b065e2cSDoug Barton20030501:
4084b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
4094b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
4104b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
4114b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
4124b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
4134b065e2cSDoug Barton	utilizes these old scripts has also been removed.
4144b065e2cSDoug Barton
41581cda3d9SWarner Losh20030423:
41681cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
41781cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
41881cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
41981cda3d9SWarner Losh	have until then to upgrade your kernel before updating
42081cda3d9SWarner Losh	userland.  In general, you should have a userland and
42181cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
42281cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
42381cda3d9SWarner Losh	allowances are made.
42481cda3d9SWarner Losh
42547a657d1SRuslan Ermilov20030329:
42647a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
42747a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
42847a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
42947a657d1SRuslan Ermilov
43047a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
43147a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
43247a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
43347a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
43447a657d1SRuslan Ermilov
43547a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
43647a657d1SRuslan Ermilov	    make cleandir && make obj && \
43747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
43847a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
43947a657d1SRuslan Ermilov
4405d2af00cSGregory Neil Shapiro20030208:
4415d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
4425d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
4435d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
4445d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
4455d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
4465d2af00cSGregory Neil Shapiro
4475d2af00cSGregory Neil Shapiro20030128:
4489db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
449ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
4509db58771SPoul-Henning Kamp	be removed when convenient.
4519db58771SPoul-Henning Kamp
4528d9b3f57SJake Burkholder20030126:
4538d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
4548d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
4558d9b3f57SJake Burkholder
4561c5efda5SJeff Roberson20030125:
4571c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
4581c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
459ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
4601c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
4611c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
4621c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
4631c5efda5SJeff Roberson
4649d1d64f5SWarner Losh20030115:
4659d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
4669d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
4679d1d64f5SWarner Losh	properly.
4689d1d64f5SWarner Losh
469c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
470c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
471c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
472c9fdb80aSWarner Losh	with NetBSD.
473c9fdb80aSWarner Losh
474161dc364SAlexander Kabaev20021222:
475161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
476161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
477161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
478161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
479161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
480161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
48184cc83efSAlexander Kabaev	rebuilt.
482161dc364SAlexander Kabaev
483fb4c8061SMartin Blapp20021216:
484fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
48589056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
486fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
4879d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
488fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
489fb4c8061SMartin Blapp
49017d47eb3SGiorgos Keramidas20021202:
49117d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
49217d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
49317d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
49417d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
49517d47eb3SGiorgos Keramidas
496a4459294SBill Fenner20021029:
497a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
498a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
499a4459294SBill Fenner	consumers in sync.
500a4459294SBill Fenner
501fc8c157fSWarner Losh20021024:
502c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
503c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
504c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
505c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
506c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
507c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
508c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
509c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
51069f7bcf3SWarner Losh
511fd9e8bdaSAndrew Gallatin20021023:
512fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
513fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
514fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
515fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
516fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
517fd9e8bdaSAndrew Gallatin
518fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
519fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
520fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
521fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
522fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
523fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
524fd9e8bdaSAndrew Gallatin
525f8a4c901SWarner Losh20020831:
526f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
527f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
528f8a4c901SWarner Losh	programs and libraries need to be recompiled.
529f8a4c901SWarner Losh
530f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
531f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
532f8a4c901SWarner Losh
533c2248fa2SJens Schweikhardt20020827:
534c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
535c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
536c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
537c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
538c2248fa2SJens Schweikhardt
5390d533e43SRuslan Ermilov20020815:
5400d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
5410d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
5420d533e43SRuslan Ermilov	again.
5430d533e43SRuslan Ermilov
54433c1de7dSRuslan Ermilov20020729:
54533c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
54633c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
54733c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
54833c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
54933c1de7dSRuslan Ermilov
5502b877facSJulian Elischer20020702:
5512b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
5522b877facSJulian Elischer	There are still some minor problems with some signals but the
5532b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
5542b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
5552b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
5562b877facSJulian Elischer
55706596d37SWarner Losh20020701:
55806596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
55906596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
56006596d37SWarner Losh	GNOME.
56106596d37SWarner Losh
56295ba4330SJacques Vidrine20020511:
56395ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
56495ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
56595ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
56695ba4330SJacques Vidrine	with the set-user-ID bit set.
56795ba4330SJacques Vidrine
568a81da3c9SDavid E. O'Brien20020510:
569f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
570f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
5714b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
572f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
573f50caf6fSDavid E. O'Brien
574f50caf6fSDavid E. O'Brien20020510:
575a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
576a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
577a81da3c9SDavid E. O'Brien	and then do a cvs update.
578a81da3c9SDavid E. O'Brien
579528a0ef5SJacques Vidrine20020421:
580528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
581528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
582528a0ef5SJacques Vidrine
58385aa5a2eSGregory Neil Shapiro20020404:
58485aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
58585aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
58685aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
58785aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
58885aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
58985aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
59085aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
59185aa5a2eSGregory Neil Shapiro
5928f1e4358SRuslan Ermilov20020403:
5938f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
5948f1e4358SRuslan Ermilov
5952292c02eSWarner Losh20020315:
5962292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
5972292c02eSWarner Losh
59869f7bcf3SWarner Losh20020225:
59969f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
60069f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
60169f7bcf3SWarner Losh
6028f35c493SWarner Losh20020217:
6038f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
6048f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
6058f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
6068f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
6078f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
6088f35c493SWarner Losh
609835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
610835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
611835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
612835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
613835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
614835284beSWarner Losh	and group must be merged from src/etc/group and
615835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
616835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
617835284beSWarner Losh	mergemaster before this will work if you are updating from a
618835284beSWarner Losh	very old version of current.  The updating recipe has changed
619835284beSWarner Losh	as of this date.
620835284beSWarner Losh
621fa9401c1SWarner Losh20020112:
622fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
623fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
624fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
625fa9401c1SWarner Losh	you have local modifications, you can use
626fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
627fa9401c1SWarner Losh	/etc/pam.d.
628fa9401c1SWarner Losh
629fa9401c1SWarner Losh	Please see the following url for more details:
630fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
63147d0d01fSWarner Losh20011229:
63247d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
63347d0d01fSWarner Losh	networkfs_types, please note that it has changed
63447d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
63547d0d01fSWarner Losh
636514318a8SWarner Losh20011220:
637514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
638514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
639514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
640514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
641514318a8SWarner Losh	version have now been merged back into the base system's
642514318a8SWarner Losh	version now.  The only user-visible change resulting from this
643514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
644514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
645514318a8SWarner Losh	as well.  (There has never been rc file support for
646514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
647514318a8SWarner Losh	reverted by the time the changes are MFCed.)
648514318a8SWarner Losh
649514318a8SWarner Losh20011215:
650514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
651514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
652514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
653514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
654514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
655514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
656514318a8SWarner Losh	will need to be customized then for `odd' densities using
657514318a8SWarner Losh	fdcontrol(8).
658514318a8SWarner Losh
6592d22e2bfSWarner Losh20011209:
6602d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
6612d22e2bfSWarner Losh	and truss(1) now works again.
6622d22e2bfSWarner Losh
6639e0428e2SWarner Losh20011207:
6649e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
6659e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
6669e0428e2SWarner Losh	see
6679e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
6689e0428e2SWarner Losh	for details.
6699e0428e2SWarner Losh
6709bab8c59SWarner Losh20011204:
6719bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
6729bab8c59SWarner Losh	kernel and burncd to be in sync.
6739bab8c59SWarner Losh
674e57d8b01SWarner Losh20011203:
675e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
676e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
677e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
678e57d8b01SWarner Losh	not there already.
679e57d8b01SWarner Losh
680e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
681e57d8b01SWarner Losh	until the issue has been resolved.
682e57d8b01SWarner Losh
683b001d36fSJacques Vidrine20011202:
684b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
685b001d36fSJacques Vidrine	patched.
686b001d36fSJacques Vidrine
6874b676ec1SWarner Losh20011126:
6884b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
6895ebbf43eSWarner Losh	after this date.  You need to do this only once.
6904b676ec1SWarner Losh
691d961e462SWarner Losh20011103:
692d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
693d961e462SWarner Losh	edges may be left, but for the most part things should be
6944b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
695d961e462SWarner Losh
696d961e462SWarner Losh20011030:
697d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
698d961e462SWarner Losh	choppy waves in the upgrade process.
699d961e462SWarner Losh
7001fe003b6SWarner Losh20011030:
701a4b6fda0SWarner Losh	The asr driver problem has been resolved.
7021fe003b6SWarner Losh
7031fe003b6SWarner Losh20011027:
7041fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
7051fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
7061fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
7071fe003b6SWarner Losh	try to use from this date forward.
7081fe003b6SWarner Losh
7091fe003b6SWarner Losh20011025:
7101fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
7111fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
7121fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
7131fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
7141fe003b6SWarner Losh	TARGET_ARCH=i386.
7151fe003b6SWarner Losh
716d05f9643SWarner Losh20011001:
717d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
718d05f9643SWarner Losh	You must recompile both the kernel and userland applications
719d05f9643SWarner Losh	at the same time.
720d05f9643SWarner Losh
72158970f85SWarner Losh20010929:
72258970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
72358970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
72458970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
72558970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
7269d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
72758970f85SWarner Losh
72858970f85SWarner Losh20010927:
72958970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
73058970f85SWarner Losh	To disable ACPI you can add
73166ff0e67SMax Khon		hint.acpi.0.disabled="1"
73258970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
73358970f85SWarner Losh	loader "ok" prompt).
73458970f85SWarner Losh
73558970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
73658970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
73758970f85SWarner Losh	file and not list acpi in that list.
738378f4486SAlfred Perlstein
7395119d237SWarner Losh20010924:
7405119d237SWarner Losh	The buildworld has been fixed.  You may need to install
7415119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
7428b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
7438b039fffSWarner Losh	get them installed on every installworld, or execute the
7448b039fffSWarner Losh	following to get them installed only once:
7458b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
74658970f85SWarner Losh		make all install
7478b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
7485119d237SWarner Losh
7493c293725SWarner Losh20010919:
7503c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
7513c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
7523c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
753772730c7SWarner Losh	workaround is to add
7543c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
7553c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
7563c293725SWarner Losh	can be removed afterwards.
7573c293725SWarner Losh
7583c293725SWarner Losh	A proper fix to the buildworld target is needed.
7593c293725SWarner Losh
7603c293725SWarner Losh20010918:
7613c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
7623c293725SWarner Losh	NFS may be unstable after this date.
7633c293725SWarner Losh
7643c293725SWarner Losh20010912:
7653c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
7663c293725SWarner Losh	the kernel.  While a few problems were introduced in the
7673c293725SWarner Losh	initial commit, most of the major ones have been found and
7683c293725SWarner Losh	corrected.
7693c293725SWarner Losh
7703c293725SWarner Losh20010901:
7713c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
7723c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
7733c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
7743c293725SWarner Losh	have been rectified around this date.
7753c293725SWarner Losh
77698b17b95SWarner Losh20010823:
77798b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
77898b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
77998b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
78098b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
78198b17b95SWarner Losh 	sure that user or group bind has read (and not write)
78298b17b95SWarner Losh 	permission for your name server configuration and that it
78398b17b95SWarner Losh 	has read and write permission for your slave zone files and
78498b17b95SWarner Losh 	directory.
78598b17b95SWarner Losh
78698b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
78798b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
78898b17b95SWarner Losh
78998b17b95SWarner Losh 		named_flags=
79098b17b95SWarner Losh
7917b9786edSMark Murray20010709:
7927b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
7937b9786edSMark Murray	the ability of the shared library major number to handle.
7947b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
7957b9786edSMark Murray	solution is to rebuild those ports.
7967b9786edSMark Murray
7971d28950eSWarner Losh20010628:
7981d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
7991d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
8001d28950eSWarner Losh
801e72fd46aSWarner Losh20010625:
80298b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
80398b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
80498b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
80598b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
80698b17b95SWarner Losh	IRQ configuration needs more safety belts.
80716de1a07SWarner Losh
8080d415dffSWarner Losh20010617:
809e72fd46aSWarner Losh	Softupdates problems have been corrected.
8100d415dffSWarner Losh
8110d415dffSWarner Losh20010614:
8120d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
8130d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
8140d415dffSWarner Losh	kernel building methods.
8150d415dffSWarner Losh
8168b9959adSWarner Losh20010613:
8178b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
8188b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
819e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
820e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
8218b9959adSWarner Losh
822e72fd46aSWarner Losh20010613:
8238b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
824e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
825e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
8268b9959adSWarner Losh
8270d415dffSWarner Losh20010612:
8280d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
8290d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
8300d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
8310d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
8320d415dffSWarner Losh	until this bug is fixed.
8330d415dffSWarner Losh
834e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
835e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
836ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
837e72fd46aSWarner Losh
8380d415dffSWarner Losh20010610:
8390d415dffSWarner Losh	Locale names have changed to match other systems better.
8400d415dffSWarner Losh
8416ccdb5e4SWarner Losh20010604:
8426ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
8436ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
8446ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
8453590182eSWarner Losh	Interrupt storms look a lot like a hang.
8463590182eSWarner Losh
8473590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
8483590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
8493590182eSWarner Losh	it is).
8503590182eSWarner Losh
8513590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
8523590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
8533590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
8543590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
8556ccdb5e4SWarner Losh
8560bc62786SWarner Losh20010530:
8570bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
8580bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
8590bc62786SWarner Losh	a limited time.  If you see
8600bc62786SWarner Losh
8610bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
8620bc62786SWarner Losh
8630bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
8640bc62786SWarner Losh	COPY=-C.
8650bc62786SWarner Losh
86668a38c6cSWarner Losh20010525:
867b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
868c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
869c4f4a728SWarner Losh	definitely is in bad shape.
87068a38c6cSWarner Losh
871ed0f29caSWarner Losh20010521:
872ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
873ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
874ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
875ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
876ed0f29caSWarner Losh	is
877ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
878ed0f29caSWarner Losh
87980c16af9SWarner Losh20010520:
88068a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
88180c16af9SWarner Losh
88280c16af9SWarner Losh20010519:
88380c16af9SWarner Losh	pccard has had much reorganizational work done to it over
88480c16af9SWarner Losh	the past few days.  Everything should still work, but if
88580c16af9SWarner Losh	not, please contact imp@freebsd.org.
88680c16af9SWarner Losh
887a45f2d05SWarner Losh20010517:
888a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
889a45f2d05SWarner Losh	userland at the same time.
890a45f2d05SWarner Losh
891a45f2d05SWarner Losh20010517:
892a45f2d05SWarner Losh	New ncurses imported.
893a45f2d05SWarner Losh
8942988afcaSWarner Losh20010512:
8952988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
8962988afcaSWarner Losh	will be the only way to go starting July 1.
8972988afcaSWarner Losh
8981a33dba7SWarner Losh20010504:
8991a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
9001a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
9011a33dba7SWarner Losh
90209946a51SWarner Losh20010502:
90309946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
90409946a51SWarner Losh
90509946a51SWarner Losh20010501:
90609946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
90709946a51SWarner Losh
90809946a51SWarner Losh20010430:
909a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
91009946a51SWarner Losh	go back in the water.
91109946a51SWarner Losh
91209946a51SWarner Losh20010429:
91309946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
91409946a51SWarner Losh	this date, but before the correction date.
91509946a51SWarner Losh
91691dd3b53SWarner Losh20010423:
91791dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
91891dd3b53SWarner Losh
91991dd3b53SWarner Losh20010411:
92091dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
92191dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
92291dd3b53SWarner Losh	Update only if you understand that you must not use the old
92391dd3b53SWarner Losh	fsck with the new kernel ever.
92491dd3b53SWarner Losh
925933b3269SWarner Losh20010330:
926933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
927c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
928933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
929933b3269SWarner Losh
930933b3269SWarner Losh20010319:
931933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
932933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
933933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
934f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
93509946a51SWarner Losh
93609946a51SWarner Losh20010315:
93709946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
938ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
93909946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
940933b3269SWarner Losh
941933b3269SWarner Losh20010312:
942933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
943933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
944933b3269SWarner Losh
945933b3269SWarner Losh20010312:
946933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
947933b3269SWarner Losh	instead of ad-hoc.
948933b3269SWarner Losh
949933b3269SWarner Losh20010310:
950f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
951933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
952933b3269SWarner Losh	ssh might not work if you don't.
953933b3269SWarner Losh
95462353691SWarner Losh20010303:
95562353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
95662353691SWarner Losh	which means that you must include the miibus in your kernel if
95762353691SWarner Losh	you use the ed driver.
95862353691SWarner Losh
959d325cf65SWarner Losh20010220:
960d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
961d325cf65SWarner Losh	safe to go back into the water.
962d325cf65SWarner Losh
963024daae6SWarner Losh20010211:
964024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
965024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
966024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
967024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
968024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
969024daae6SWarner Losh
970024daae6SWarner Losh	To get to the new system, you'll need to use the following
971024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
972024daae6SWarner Losh	don't have to move this to the updating section.
973024daae6SWarner Losh
974024daae6SWarner Losh	To get around the installworld problem, do:
975024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
976024daae6SWarner Losh		# make install
977024daae6SWarner Losh		# cd /usr/src
978024daae6SWarner Losh		# make installworld
979024daae6SWarner Losh	If that doesn't work, then try:
980024daae6SWarner Losh		# make -k installworld
981024daae6SWarner Losh		# make installworld
982024daae6SWarner Losh
983024daae6SWarner Losh20010207:
984024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
985024daae6SWarner Losh	do not include devfs in your kernel as problems result.
986024daae6SWarner Losh
987024daae6SWarner Losh20010205:
9887595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
989024daae6SWarner Losh	Remove them from your config.
990024daae6SWarner Losh
9911e159248SWarner Losh20010122:
9921e159248SWarner Losh	****************************** WARNING ******************************
9931e159248SWarner Losh			buildkernel has been changed slightly
9941e159248SWarner Losh	****************************** WARNING ******************************
9951e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
9961e159248SWarner Losh	should update your scripts and make.conf accordingly.
9971e159248SWarner Losh
9981e159248SWarner Losh20010119:
9991e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
10001e159248SWarner Losh	This requires a new config to build correctly.
10011e159248SWarner Losh
1002aac7dfeaSWarner Losh20010116:
1003ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1004aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1005aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1006aac7dfeaSWarner Losh
1007aac7dfeaSWarner Losh20010110:
1008aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1009aac7dfeaSWarner Losh
1010aac7dfeaSWarner Losh20010102:
1011aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1012aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1013aac7dfeaSWarner Losh
101463c90c9eSWarner Losh20010101:
101563c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
101663c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
10175fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
101863c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
101963c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
102063c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
102163c90c9eSWarner Losh	might have been ignored by the -k option.
102263c90c9eSWarner Losh
10235fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
10245fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
10255fd2a895SWarner Losh	of this working.
10265fd2a895SWarner Losh
1027aac7dfeaSWarner Losh20001228:
1028aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1029ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1030aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1031aac7dfeaSWarner Losh
1032de2bcc63SWarner Losh20001218:
1033de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1034de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1035de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1036de2bcc63SWarner Losh	cards will not be recognized without it.
1037de2bcc63SWarner Losh
1038960773f7SWarner Losh20001205:
1039960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1040960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1041960773f7SWarner Losh	adding the following in pam.conf:
1042960773f7SWarner Losh
1043960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1044960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1045960773f7SWarner Losh	sshd    session required        pam_permit.so
1046960773f7SWarner Losh
10470acc635eSWarner Losh20001031:
10480acc635eSWarner Losh	cvs updated to 1.11.
10490acc635eSWarner Losh
10500acc635eSWarner Losh20001020:
10510acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
10520acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
10530acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
10540acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
10550acc635eSWarner Losh	workaround.
10560acc635eSWarner Losh
10570acc635eSWarner Losh20001010:
10580acc635eSWarner Losh	****************************** WARNING ******************************
10590acc635eSWarner Losh				Sendmail has been updated.
10600acc635eSWarner Losh	****************************** WARNING ******************************
10610acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
10620acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
10630acc635eSWarner Losh	  is set.
10640acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
10650acc635eSWarner Losh	  commands.
10660acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
10670acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
10680acc635eSWarner Losh	  in /usr/share/sendmail/cf.
10690acc635eSWarner Losh	o sendmail.cw changed to local-host-names
10700acc635eSWarner Losh
10710acc635eSWarner Losh	More details can be found at
10720acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
10730acc635eSWarner Losh
10746e98a146SWarner Losh20001009:
10756e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
10766e98a146SWarner Losh	your entire ports tree, or you will have problems.
10776e98a146SWarner Losh
10786e98a146SWarner Losh20001006:
1079685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
10806e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
10816e98a146SWarner Losh	/usr/bin/miniperl.
10826e98a146SWarner Losh
1083073113a4SWarner Losh20001005:
1084073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1085685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1086073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1087073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1088073113a4SWarner Losh	tree for anything to work.
1089073113a4SWarner Losh
10900acc635eSWarner Losh20000928:
10910acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
10920acc635eSWarner Losh
1093be3885b3SWarner Losh20000916:
1094be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1095be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1096be3885b3SWarner Losh	same time as your kernel.
1097be3885b3SWarner Losh
109876ec9675SWarner Losh20000914:
109976ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
110076ec9675SWarner Losh	include the device will cause suspended laptops losing time
110176ec9675SWarner Losh	when they resume.  Include
110276ec9675SWarner Losh		device		pmtimer
110376ec9675SWarner Losh	in your config file and
110401b9a434SWarner Losh		hint.pmtimer.0.at="isa"
110576ec9675SWarner Losh	to your /boot/device.hints file.
110676ec9675SWarner Losh
1107f4865386SMark Murray20000911:
1108f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1109f4865386SMark Murray	rather than an option. The supplied kernel config files have
1110f4865386SMark Murray	been updated. You will need to do something similar in your
1111f4865386SMark Murray	own kernel config file.
1112f4865386SMark Murray	Remove:
1113f4865386SMark Murray		options		RANDOMDEV
1114f4865386SMark Murray	Add:
1115f4865386SMark Murray		device		random
1116f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1117f4865386SMark Murray	nothing.
1118f4865386SMark Murray
1119d594498fSWarner Losh20000909:
1120d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1121d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1122d594498fSWarner Losh	reflect this if you load this module at boot time.
1123d594498fSWarner Losh	The line should read:
1124d594498fSWarner Losh		random_load="YES"
1125d594498fSWarner Losh
11260deb7ddcSWarner Losh20000907:
11270deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
112816eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
112916eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
113016eb772dSWarner Losh	sure you don't have model loading problems which might at
113116eb772dSWarner Losh	first blush appear related to SMP.
113252bf24e7SWarner Losh
11335a01880bSWarner Losh20000906:
11345a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
11355a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
11365a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
11375a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
11385a01880bSWarner Losh	don't have one, and you have host.conf.
11395a01880bSWarner Losh
11402b41163cSWarner Losh20000905:
114138d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
114238d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
114338d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
114438d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
114538d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
114638d6ecd2SWarner Losh
114738d6ecd2SWarner Losh20000905:
11488aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
11498aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
11508aab4bc7SWarner Losh	is /boot/kernel.
11518aab4bc7SWarner Losh
11528aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
115338d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
115438d6ecd2SWarner Losh	installkernel/installworld dance.
11552b41163cSWarner Losh
1156d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1157d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1158d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1159d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1160d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1161d594498fSWarner Losh
1162d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1163d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1164d594498fSWarner Losh		chflags noschg /kernel.old
1165d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1166d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1167d594498fSWarner Losh	fi
1168d594498fSWarner Losh
1169c22a309cSWarner Losh20000904:
1170c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1171c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1172c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1173c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1174c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1175c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1176c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1177c22a309cSWarner Losh	is not likely to be generated.
1178c22a309cSWarner Losh
1179fdb9f54dSWarner Losh20000825:
1180fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
11819c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
11829c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
11839c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
11849c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
11859c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
11869c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
11879c1a7444SWarner Losh	kernel.
11889c1a7444SWarner Losh
11899c1a7444SWarner Losh20000821:
11909c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
11919c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
11929c1a7444SWarner Losh	/boot/loader.conf.
1193fdb9f54dSWarner Losh
11948f250aa7SWarner Losh20000812:
11955da0d091SWarner Losh	suidperl is now always built and installed on the system, but
11965da0d091SWarner Losh	with permissions of 511.  If you have applications that use
11975da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
11985da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
11995da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
12005da0d091SWarner Losh	will fix this until the next build.
12015da0d091SWarner Losh
12025da0d091SWarner Losh20000812:
12038f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
12048f250aa7SWarner Losh	visible changes that may immediately affect your configuration
12058f250aa7SWarner Losh	include:
12068f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
12078f250aa7SWarner Losh	- newaliases limited to root and trusted users
12088f250aa7SWarner Losh	- MSA port (587) turned on by default
12098f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
12108f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
12118f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
12128f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
12138f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
12148f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
12158f250aa7SWarner Losh
121671c38472SWarner Losh20000810:
121771c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
121871c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
121971c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
122071c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
122171c38472SWarner Losh	specific use for it.
122271c38472SWarner Losh
122371c38472SWarner Losh20000729:
122471c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
122571c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
122671c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
122771c38472SWarner Losh	afterwards (unless the variables already are set, of course):
122871c38472SWarner Losh		# Enable network daemons for user convenience.
122971c38472SWarner Losh		inetd_enable="YES"
123071c38472SWarner Losh		portmap_enable="YES"
123171c38472SWarner Losh		sendmail_enable="YES"
123271c38472SWarner Losh
123371c38472SWarner Losh20000728:
123471c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
123571c38472SWarner Losh	will need to change that to nullfs_load="YES".
123671c38472SWarner Losh
12371dece4a9SWarner Losh20000728:
12381dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
12391dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
12401dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
12411dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
12421dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
12431dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
12441dece4a9SWarner Losh	to /MYKERNEL.
12451dece4a9SWarner Losh
1246409e887cSWarner Losh20000711:
1247409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1248409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1249409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1250409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1251409e887cSWarner Losh	for details on potential problems that you might have and how
1252409e887cSWarner Losh	to get around them.
1253409e887cSWarner Losh
1254409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1255409e887cSWarner Losh	clauses above, you needn't worry.
1256409e887cSWarner Losh
1257409e887cSWarner Losh20000711:
1258409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1259409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1260409e887cSWarner Losh	in the number of changed programs the first time when you run
1261409e887cSWarner Losh	mergemaster to get a new /etc/security.
1262409e887cSWarner Losh
1263673d13f2SWarner Losh20000710:
1264673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1265673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1266673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1267673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1268673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1269673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1270673d13f2SWarner Losh	errors. (see below, 20000624).
1271673d13f2SWarner Losh
1272bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
12731dece4a9SWarner Losh
1274673d13f2SWarner Losh20000709:
1275c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1276c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1277c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1278673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1279673d13f2SWarner Losh
1280e98e26cdSWarner Losh20000706:
1281e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1282e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1283e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1284f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1285e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
12862c021c6cSMark Ovens	interim if needed.
1287e98e26cdSWarner Losh
1288e98e26cdSWarner Losh20000705:
1289e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1290e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1291e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1292e98e26cdSWarner Losh	details.
1293e98e26cdSWarner Losh
1294c373950eSWarner Losh20000704:
12952f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
12962f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
12972f961bc8SWarner Losh
12982f961bc8SWarner Losh20000704:
1299c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1300c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1301c373950eSWarner Losh	rc.d scripts that haven't been updated.
1302c373950eSWarner Losh
130327dc3a2bSWarner Losh20000630:
130427dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
130527dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
130627dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
130727dc3a2bSWarner Losh
1308b8c215acSWarner Losh20000625:
1309b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
131027dc3a2bSWarner Losh	system installed in order to build the system and kernel.
131127dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
131227dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
131327dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
131427dc3a2bSWarner Losh	were required.  You should check with the latest collections
131527dc3a2bSWarner Losh	to make sure that these haven't changed.
1316b8c215acSWarner Losh
13177b990719SWarner Losh20000624:
13187b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
13197b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
13207b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
13211a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
13227b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
13237b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
13247b990719SWarner Losh	date to the completion of the work.
13257b990719SWarner Losh
132627dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
132727dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
132827dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
132927dc3a2bSWarner Losh	recreate the random and urandom devices.
133027dc3a2bSWarner Losh
133181e54c50SWarner Losh20000622:
133281e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
133381e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
133481e54c50SWarner Losh	that used to be required when updating.
133581e54c50SWarner Losh
133639943833SWarner Losh20000621:
13372c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
13382a2f33fbSDaniel Baker	the config file update procedure.
13392a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1340c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
134159df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
134259df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
134339943833SWarner Losh
1344290f9ad8SWarner Losh20000620:
1345290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1346290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1347290f9ad8SWarner Losh	that workaround will no longer be required.
1348290f9ad8SWarner Losh
134990fb6346SWarner Losh20000615:
135090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
135190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
135290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
135390fb6346SWarner Losh	devices.
135490fb6346SWarner Losh
1355f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1356f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1357f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1358f75f65bbSWarner Losh	may work).
1359f75f65bbSWarner Losh
1360ba26da8eSWarner Losh20000612:
1361ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1362290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1363c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1364290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1365f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1366f54a3542SWarner Losh	NEWCARD for examples of the new format.
1367290f9ad8SWarner Losh
13689698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
13699698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
13709698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
13719698f2c0SWarner Losh	in it.
1372bbcc5149SWarner Losh
1373d65850ebSWarner Losh20000522:
1374ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1375d65850ebSWarner Losh	building a kernel after this point is advised that they need
1376d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1377d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1378d65850ebSWarner Losh
1379d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1380d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1381d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1382d9583a00SWarner Losh	is resolved.
1383d9583a00SWarner Losh
13848039cedeSWarner Losh20000513:
13858039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
13868039cedeSWarner Losh
1387d65850ebSWarner Losh20000510:
13888039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
13898039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
13908039cedeSWarner Losh	is requires for the boot blocks to build properly.
13918039cedeSWarner Losh
13928039cedeSWarner Losh20000503:
13938039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
13948039cedeSWarner Losh	is now available.
13958039cedeSWarner Losh
1396d65850ebSWarner Losh20000502:
1397d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1398d65850ebSWarner Losh	connected to the kernel building instead.
1399d65850ebSWarner Losh
1400be149406SNik Clayton20000427:
14018039cedeSWarner Losh	You may need to build gperf
14028039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
14038039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
14048039cedeSWarner Losh	an option only in -current.
14058039cedeSWarner Losh
14062b8dd5f4SWarner Losh20000417:
14072b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1408f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
14092b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
14102b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
14112c021c6cSMark Ovens	before you reboot, you'll need to issue:
14122b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
14132b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
14142b8dd5f4SWarner Losh
14158d9f1945SWarner Losh20000320:
14162b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
14172b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
14182b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1419ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
14202b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
14218d9f1945SWarner Losh
1422f8ab1dd6SWarner Losh20000319:
1423f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1424f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1425f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1426f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1427f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1428f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1429f8ab1dd6SWarner Losh
143019cada77SWarner Losh20000318:
1431f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
143219cada77SWarner Losh	Large kernel changes are being committed and are in the
143319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
143419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
143519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
143619cada77SWarner Losh	that you are loading are up to date.
1437ba228352SWarner Losh
143819cada77SWarner Losh20000315:
14396d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
14406d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
14416d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
14426d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
14436d23c382SWarner Losh	boot.
14446d23c382SWarner Losh
14456d23c382SWarner Losh20000315:
144619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
144719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
144857199806SWarner Losh
1449dc0dbf5cSWarner LoshCOMMON ITEMS:
1450dc0dbf5cSWarner Losh
1451a24eff53SWarner Losh	General Notes
1452a24eff53SWarner Losh	-------------
1453a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1454a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1455a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1456a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1457a24eff53SWarner Losh	or several minor releases, or when several months have passed
1458a24eff53SWarner Losh	on the -current branch).
1459a24eff53SWarner Losh
14605780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
14615780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
14625780f3baSWarner Losh	environment when searching for values for global variables.
14635780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
14645780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
14655780f3baSWarner Losh	page for more details.
14665780f3baSWarner Losh
1467dc0dbf5cSWarner Losh	To build a kernel
1468dc0dbf5cSWarner Losh	-----------------
1469ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1470f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1471ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1472282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1473282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1474dc0dbf5cSWarner Losh
1475ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1476ba01eb20SWarner Losh	--------------------------------------------------------------
14770fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
14780fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
14790fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
14800fbd2da9SKen Smith
14810fbd2da9SKen Smith	cd src/sys/${arch}/conf
148247d0d01fSWarner Losh	config KERNEL_NAME_HERE
14830fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1484ba01eb20SWarner Losh	make depend
1485ba01eb20SWarner Losh	make
1486ba01eb20SWarner Losh	make install
1487ba01eb20SWarner Losh
1488ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1489ba01eb20SWarner Losh
1490ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1491ba01eb20SWarner Losh	-----------------------------------------------------------
149263cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
149363cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
149463cb445eSWarner Losh
1495f643de42SWarner Losh	<make sure you have good level 0 dumps>
149663cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
149763cb445eSWarner Losh	make buildworld
149863cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
149963cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
150063cb445eSWarner Losh							[1]
150163cb445eSWarner Losh	<reboot in single user>				[3]
15028633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
150363cb445eSWarner Losh	mergemaster -p					[5]
150463cb445eSWarner Losh	make installworld
150563cb445eSWarner Losh	mergemaster					[4]
150663cb445eSWarner Losh	<reboot>
150763cb445eSWarner Losh
1508759f0aefSWarner Losh
1509f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1510f27b1fceSJoseph Koshy	--------------------------------------------------
1511f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1512f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1513f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1514f27b1fceSJoseph Koshy	# size.
1515f27b1fceSJoseph Koshy
1516f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1517f27b1fceSJoseph Koshy	<boot into -stable>
1518f27b1fceSJoseph Koshy	make buildworld
1519f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1520f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1521f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1522f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1523f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1524f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1525f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1526f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1527f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1528f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1529f27b1fceSJoseph Koshy	<reboot into current>
1530f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1531f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1532f27b1fceSJoseph Koshy 	<reboot>
1533f27b1fceSJoseph Koshy
1534f27b1fceSJoseph Koshy
1535f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1536f27b1fceSJoseph Koshy	----------------------------------------------
15375c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
15385c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
15395c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
15405c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1541ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1542f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1543f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1544f643de42SWarner Losh	# space on /.
1545f643de42SWarner Losh
1546f643de42SWarner Losh	<make sure you have good level 0 dumps>
1547fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
154821c075eaSWarner Losh	make buildworld					[9]
1549c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1550802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1551be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1552802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install			[6]
1553fc8c157fSWarner Losh							[1]
1554fc8c157fSWarner Losh	<reboot in single user>				[3]
1555802fc49dSBrian Feldman	/usr/src/etc/rc.d/preseedrandom				[10]
1556835284beSWarner Losh	mergemaster -p					[5]
1557f8a4c901SWarner Losh	rm -rf /usr/include/g++
1558ba26da8eSWarner Losh	make installworld
1559802fc49dSBrian Feldman	mergemaster -i					[4]
1560ba26da8eSWarner Losh	<reboot>
1561ba26da8eSWarner Losh
1562fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1563fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1564fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1565fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1566fdb9f54dSWarner Losh	the UPDATING entries.
1567ba26da8eSWarner Losh
15681dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
15691dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
15701dece4a9SWarner Losh	your sources that you have read and understood all the recent
15711dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
15721dece4a9SWarner Losh	much fewer pitfalls.
15731dece4a9SWarner Losh
1574134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1575134d2e86SWarner Losh	should disable them at this point so they don't crash your
1576134d2e86SWarner Losh	system on reboot.
1577134d2e86SWarner Losh
15789c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
15799c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
15809c1a7444SWarner Losh	configuration.
15819c1a7444SWarner Losh
1582ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1583ee6e1fc3SWarner Losh		fsck -p
1584ee6e1fc3SWarner Losh		mount -u /
1585ee6e1fc3SWarner Losh		mount -a
1586ee6e1fc3SWarner Losh		cd /usr/src
158747d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1588f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1589f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1590b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1591b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1592b705ae10SWarner Losh	be ignored while you proceed to the next step.
1593ee6e1fc3SWarner Losh
1594a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1595a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1596a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1597a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1598a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1599a6cd4f9dSWarner Losh	for potential gotchas.
1600a6cd4f9dSWarner Losh
1601835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1602835284beSWarner Losh	you may need to do this if you get unknown user in the following
1603835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1604835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1605835284beSWarner Losh	install) after the buildworld before this step if you last updated
1606835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1607835284beSWarner Losh
1608bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1609bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1610bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1611bd79cf40SWarner Losh		ok unload
1612bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1613bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1614bd79cf40SWarner Losh	described here.
1615fc8c157fSWarner Losh
1616fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1617fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1618fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1619fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1620fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1621fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1622fc8c157fSWarner Losh
1623c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1624c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1625c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1626c74fe6afSWarner Losh	that is hard to boot to recover.
1627c74fe6afSWarner Losh
162821c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1629802fc49dSBrian Feldman	cvs prune empty directories. Also, if CPUTYPE is defined in your
1630802fc49dSBrian Feldman	/etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1631802fc49dSBrian Feldman	operator, so that buildworld can override the CPUTYPE if it needs to.
1632802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1633802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
1634802fc49dSBrian Feldman	compatibility libraries are build which should allow you to continue
1635802fc49dSBrian Feldman	using your existing software for a while.
16368633bbeaSBrooks Davis
16378633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
16388633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
16398633bbeaSBrooks Davis	takes care of this.
1640dc0dbf5cSWarner LoshFORMAT:
1641dc0dbf5cSWarner Losh
1642f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
16431fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1644f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1645f8ab1dd6SWarner Loshprevious releases if your system is older than this.
16461fc1a0dcSWarner Losh
1647e72fd46aSWarner LoshCopyright information:
1648e72fd46aSWarner Losh
16499698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1650e72fd46aSWarner Losh
1651772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1652772730c7SWarner Loshmodification, in full or in part, in any form or format of this
16539698f2c0SWarner Loshdocument are permitted without further permission from the author.
1654e72fd46aSWarner Losh
1655e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1656e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1657e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1658e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1659e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1660e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1661e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1662e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1663e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1664e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1665e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1666e72fd46aSWarner Losh
1667e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1668e72fd46aSWarner Loshauthor a beer.
1669e72fd46aSWarner Losh
167022306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1671772730c7SWarner Loshthis document.
1672772730c7SWarner Losh
167397d92980SPeter Wemm$FreeBSD$
1674