xref: /freebsd/UPDATING (revision bb4f06e701d98c0129a67dd579f09c8c16d55843)
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
20bb4f06e7SAndre Oppermann20040423:
21bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
22bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
23bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
24bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
25bb4f06e7SAndre Oppermann
2605641e82SColin Percival20040420:
2705641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
2805641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
2905641e82SColin Percival	20040406.
3005641e82SColin Percival
31d0dc9183SWarner Losh20040414:
32d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
33d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
34d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
35d0dc9183SWarner Losh
36d0dc9183SWarner Losh20040412:
37d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
38d0dc9183SWarner Losh	drive is still broken.
39d0dc9183SWarner Losh
40d0dc9183SWarner Losh20040410:
41d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
42d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
43d0dc9183SWarner Losh	the unanticipated problems have been resolved.
44d0dc9183SWarner Losh
458633bbeaSBrooks Davis20040409:
468633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
478633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
488633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
498633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
5076c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
518633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
528633bbeaSBrooks Davis
53d40d033aSRobert Watson20040322:
54d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
55d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
56d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
57d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
58d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
59d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
60d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
61d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
62d40d033aSRobert Watson	locking is merged to permit this to take place.
63d40d033aSRobert Watson
64ec9b318eSGarance A Drosehn20040310:
65ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
66ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
67ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
68ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
69ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
70ec9b318eSGarance A Drosehn
71fc28f1ffSMax Laier20040308:
72fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
73fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
744c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
754c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
76fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
77fc28f1ffSMax Laier	pf system consists of the following three devices:
78fc28f1ffSMax Laier	device		pf		# required
79fc28f1ffSMax Laier	device		pflog		# optional
80fc28f1ffSMax Laier	device		pfsync		# optional
81fc28f1ffSMax Laier
823aff5d06SDag-Erling Smørgrav20040303:
833aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
843aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
853aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
863aff5d06SDag-Erling Smørgrav
873aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
883aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
893aff5d06SDag-Erling Smørgrav
903aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
913aff5d06SDag-Erling Smørgrav	to use libpthread instead.
923aff5d06SDag-Erling Smørgrav
93fd63c5b3SDag-Erling Smørgrav20040226:
949d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
95fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
96fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
97fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
98fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
99fd63c5b3SDag-Erling Smørgrav
100714ae42aSBruce M Simpson20040225:
101e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
102e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
103e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
104e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
105e07a40f3SBrian Feldman	should remain unaffected.
106e07a40f3SBrian Feldman
107e07a40f3SBrian Feldman20040225:
108714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
109714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
110714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
111714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
112714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
113714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
114714ae42aSBruce M Simpson
115fbd2e692SAndre Oppermann20040224:
116fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
117fbd2e692SAndre Oppermann	and related userland network utilities neccessary.
118fbd2e692SAndre Oppermann
119158b90daSWarner Losh20040222:
120158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
121158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
122158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
123158b90daSWarner Losh	Drivers outside the tree will need to be updated.
124158b90daSWarner Losh
125b7b1e150SMike Makonnen20040207:
126b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
127b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
128b7b1e150SMike Makonnen
129aca89ee6SDaniel Eischen20040130:
130aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
131aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
132aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
133aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
134aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
135aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
136aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
137aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
138aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
139aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
140aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
141aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
142aca89ee6SDaniel Eischen	do not work with libpthread.
143aca89ee6SDaniel Eischen
14468b7b3a9SAlex Dupre20040125:
14568b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
14668b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
14768b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
14868b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
14968b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
15068b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
15168b7b3a9SAlex Dupre
152ff46e0deSWarner Losh20040125:
153ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
154ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
155ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
156ff46e0deSWarner Losh
157ce41f4bfSRobert Watson20031213:
158ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
159ce41f4bfSRobert Watson	if the login process is unable to successfully set the
160ce41f4bfSRobert Watson	process credentials to include all groups defined for the
161ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
162ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
163ce41f4bfSRobert Watson	defined, or they will be unable to log in.
164ce41f4bfSRobert Watson
165c124fa05SJohn Baldwin20031203:
166c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
167c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
168c124fa05SJohn Baldwin
1698ad1f5e4SHartmut Brandt20031112:
17030093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
17130093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
17297209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
17397209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
17497209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
17597209ca3SRobert Watson	not know about the new system calls that support the new statfs
1763f631d52SMarcel Moolenaar	structure.
1773f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
1783f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
1793f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
1803f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
1813f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
1823f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
1833f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
1843f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
1853f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
1863f631d52SMarcel Moolenaar	these changes are installed.
18730093b05SWarner Losh
18830093b05SWarner Losh	****************************DANGER*******************************
18930093b05SWarner Losh
19030093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
19130093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
19230093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
19330093b05SWarner Losh	kernel.
19464a18d6fSKirk McKusick
19564a18d6fSKirk McKusick20031112:
1968ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
1978ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
1988ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
1998ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
2008ad1f5e4SHartmut Brandt	sync before rebooting.
2018ad1f5e4SHartmut Brandt
202c53a5d8fSJohn Baldwin20031111:
203c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
204c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
205c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
206c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
207c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
208c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
209c53a5d8fSJohn Baldwin
2108bf455a5SJohn Baldwin20031103:
2118bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
2128bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
2132a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
2148bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
2158bf455a5SJohn Baldwin
2169bf40edeSBrooks Davis20031031:
2179bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
2189bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
2199bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
2209bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
2219bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
2229bf40edeSBrooks Davis	reflect this change.
2239bf40edeSBrooks Davis
22447a42c7aSPoul-Henning Kamp20030928:
22547a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
22647a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
22747a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
22847a42c7aSPoul-Henning Kamp
22907105342SMax Khon20030926:
23007105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
23107105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
23207105342SMax Khon
23317dcd026SSam Leffler20030925:
23417dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
23517dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
23617dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
23717dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
23817dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
23917dcd026SSam Leffler
240fedf1d01SBruce M Simpson20030923:
241fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
242fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
243fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
244fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
245fedf1d01SBruce M Simpson
246db38f9cbSJacques Vidrine20030915:
247db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
248db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
249db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
250db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
251db38f9cbSJacques Vidrine
252c09d2c2bSMike Makonnen20030829:
253c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
254c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
255c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
256c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
257c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
258c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
259c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
260c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
261c09d2c2bSMike Makonnen	may or may not exist on your system.
262c09d2c2bSMike Makonnen
26317c159dcSSøren Schmidt20030824:
26417c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
26517c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
266f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
267f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
26817c159dcSSøren Schmidt
269c1f61aa9SDavid E. O'Brien20030819:
270c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
271c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
272c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
273c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
27469f7bcf3SWarner Losh
27538c962e7SNate Lawson20030728:
27638c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
27738c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
27838c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
27938c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
28038c962e7SNate Lawson	so the quirk can be re-enabled.
28138c962e7SNate Lawson
28274111097SWarner Losh20030724:
28374111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
28474111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
28574111097SWarner Losh
286178cf4e9SWarner Losh20030722:
287178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
288178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
289178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
290178cf4e9SWarner Losh	FPU hardware.
291178cf4e9SWarner Losh
292178cf4e9SWarner Losh20030714:
293178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
294178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
295178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
296178cf4e9SWarner Losh	People should report those issues to current@.
297178cf4e9SWarner Losh
298157c629aSWarner Losh20030711:
299157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
3008b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
30105538fa9SWarner Losh	/usr/obj.
302157c629aSWarner Losh
30374111097SWarner Losh20030610:
30474111097SWarner Losh	Remove deprecated locale names and transition period code
30574111097SWarner Losh	for them, finishing switching to the new scheme. Check your
30674111097SWarner Losh	LANG environment variable.
30774111097SWarner Losh
30874111097SWarner Losh20030609:
30974111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
31074111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
31174111097SWarner Losh	important to remember beforehand if your source tree is on
31274111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
31374111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
31474111097SWarner Losh	kernel.
31574111097SWarner Losh
31674111097SWarner Losh20030605:
3176cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
3186cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
3196cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
3206cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
3216cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
3226cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
3236cc6353fSMarcel Moolenaar
3246cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
3256cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
3266cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
3276cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
3286cc6353fSMarcel Moolenaar		:
3296cc6353fSMarcel Moolenaar
3306cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
3316cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
3326cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
3336cc6353fSMarcel Moolenaar
33452b47445SMark Murray20030505:
33552b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
33652b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
33752b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
33852b47445SMark Murray
339a26df538SWarner Losh20030502:
340a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
341a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
342a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
343a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
344a26df538SWarner Losh
3454b065e2cSDoug Barton20030501:
3464b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
3474b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
3484b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
3494b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
3504b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
3514b065e2cSDoug Barton	utilizes these old scripts has also been removed.
3524b065e2cSDoug Barton
35381cda3d9SWarner Losh20030423:
35481cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
35581cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
35681cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
35781cda3d9SWarner Losh	have until then to upgrade your kernel before updating
35881cda3d9SWarner Losh	userland.  In general, you should have a userland and
35981cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
36081cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
36181cda3d9SWarner Losh	allowances are made.
36281cda3d9SWarner Losh
36347a657d1SRuslan Ermilov20030329:
36447a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
36547a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
36647a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
36747a657d1SRuslan Ermilov
36847a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
36947a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
37047a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
37147a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
37247a657d1SRuslan Ermilov
37347a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
37447a657d1SRuslan Ermilov	    make cleandir && make obj && \
37547a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
37647a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
37747a657d1SRuslan Ermilov
3785d2af00cSGregory Neil Shapiro20030208:
3795d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
3805d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
3815d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
3825d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
3835d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
3845d2af00cSGregory Neil Shapiro
3855d2af00cSGregory Neil Shapiro20030128:
3869db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
387ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
3889db58771SPoul-Henning Kamp	be removed when convenient.
3899db58771SPoul-Henning Kamp
3908d9b3f57SJake Burkholder20030126:
3918d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
3928d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
3938d9b3f57SJake Burkholder
3941c5efda5SJeff Roberson20030125:
3951c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
3961c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
397ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
3981c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
3991c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
4001c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
4011c5efda5SJeff Roberson
4029d1d64f5SWarner Losh20030115:
4039d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
4049d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
4059d1d64f5SWarner Losh	properly.
4069d1d64f5SWarner Losh
407c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
408c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
409c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
410c9fdb80aSWarner Losh	with NetBSD.
411c9fdb80aSWarner Losh
412161dc364SAlexander Kabaev20021222:
413161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
414161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
415161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
416161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
417161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
418161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
41984cc83efSAlexander Kabaev	rebuilt.
420161dc364SAlexander Kabaev
421fb4c8061SMartin Blapp20021216:
422fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
42389056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
424fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
4259d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
426fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
427fb4c8061SMartin Blapp
42817d47eb3SGiorgos Keramidas20021202:
42917d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
43017d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
43117d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
43217d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
43317d47eb3SGiorgos Keramidas
434a4459294SBill Fenner20021029:
435a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
436a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
437a4459294SBill Fenner	consumers in sync.
438a4459294SBill Fenner
439fc8c157fSWarner Losh20021024:
440c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
441c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
442c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
443c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
444c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
445c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
446c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
447c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
44869f7bcf3SWarner Losh
449fd9e8bdaSAndrew Gallatin20021023:
450fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
451fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
452fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
453fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
454fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
455fd9e8bdaSAndrew Gallatin
456fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
457fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
458fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
459fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
460fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
461fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
462fd9e8bdaSAndrew Gallatin
463f8a4c901SWarner Losh20020831:
464f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
465f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
466f8a4c901SWarner Losh	programs and libraries need to be recompiled.
467f8a4c901SWarner Losh
468f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
469f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
470f8a4c901SWarner Losh
471c2248fa2SJens Schweikhardt20020827:
472c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
473c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
474c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
475c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
476c2248fa2SJens Schweikhardt
4770d533e43SRuslan Ermilov20020815:
4780d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
4790d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
4800d533e43SRuslan Ermilov	again.
4810d533e43SRuslan Ermilov
48233c1de7dSRuslan Ermilov20020729:
48333c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
48433c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
48533c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
48633c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
48733c1de7dSRuslan Ermilov
4882b877facSJulian Elischer20020702:
4892b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
4902b877facSJulian Elischer	There are still some minor problems with some signals but the
4912b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
4922b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
4932b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
4942b877facSJulian Elischer
49506596d37SWarner Losh20020701:
49606596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
49706596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
49806596d37SWarner Losh	GNOME.
49906596d37SWarner Losh
50095ba4330SJacques Vidrine20020511:
50195ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
50295ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
50395ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
50495ba4330SJacques Vidrine	with the set-user-ID bit set.
50595ba4330SJacques Vidrine
506a81da3c9SDavid E. O'Brien20020510:
507f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
508f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
5094b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
510f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
511f50caf6fSDavid E. O'Brien
512f50caf6fSDavid E. O'Brien20020510:
513a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
514a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
515a81da3c9SDavid E. O'Brien	and then do a cvs update.
516a81da3c9SDavid E. O'Brien
517528a0ef5SJacques Vidrine20020421:
518528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
519528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
520528a0ef5SJacques Vidrine
52185aa5a2eSGregory Neil Shapiro20020404:
52285aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
52385aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
52485aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
52585aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
52685aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
52785aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
52885aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
52985aa5a2eSGregory Neil Shapiro
5308f1e4358SRuslan Ermilov20020403:
5318f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
5328f1e4358SRuslan Ermilov
5332292c02eSWarner Losh20020315:
5342292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
5352292c02eSWarner Losh
53669f7bcf3SWarner Losh20020225:
53769f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
53869f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
53969f7bcf3SWarner Losh
5408f35c493SWarner Losh20020217:
5418f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
5428f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
5438f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
5448f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
5458f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
5468f35c493SWarner Losh
547835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
548835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
549835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
550835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
551835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
552835284beSWarner Losh	and group must be merged from src/etc/group and
553835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
554835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
555835284beSWarner Losh	mergemaster before this will work if you are updating from a
556835284beSWarner Losh	very old version of current.  The updating recipe has changed
557835284beSWarner Losh	as of this date.
558835284beSWarner Losh
559fa9401c1SWarner Losh20020112:
560fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
561fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
562fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
563fa9401c1SWarner Losh	you have local modifications, you can use
564fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
565fa9401c1SWarner Losh	/etc/pam.d.
566fa9401c1SWarner Losh
567fa9401c1SWarner Losh	Please see the following url for more details:
568fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
56947d0d01fSWarner Losh20011229:
57047d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
57147d0d01fSWarner Losh	networkfs_types, please note that it has changed
57247d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
57347d0d01fSWarner Losh
574514318a8SWarner Losh20011220:
575514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
576514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
577514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
578514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
579514318a8SWarner Losh	version have now been merged back into the base system's
580514318a8SWarner Losh	version now.  The only user-visible change resulting from this
581514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
582514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
583514318a8SWarner Losh	as well.  (There has never been rc file support for
584514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
585514318a8SWarner Losh	reverted by the time the changes are MFCed.)
586514318a8SWarner Losh
587514318a8SWarner Losh20011215:
588514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
589514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
590514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
591514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
592514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
593514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
594514318a8SWarner Losh	will need to be customized then for `odd' densities using
595514318a8SWarner Losh	fdcontrol(8).
596514318a8SWarner Losh
5972d22e2bfSWarner Losh20011209:
5982d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
5992d22e2bfSWarner Losh	and truss(1) now works again.
6002d22e2bfSWarner Losh
6019e0428e2SWarner Losh20011207:
6029e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
6039e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
6049e0428e2SWarner Losh	see
6059e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
6069e0428e2SWarner Losh	for details.
6079e0428e2SWarner Losh
6089bab8c59SWarner Losh20011204:
6099bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
6109bab8c59SWarner Losh	kernel and burncd to be in sync.
6119bab8c59SWarner Losh
612e57d8b01SWarner Losh20011203:
613e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
614e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
615e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
616e57d8b01SWarner Losh	not there already.
617e57d8b01SWarner Losh
618e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
619e57d8b01SWarner Losh	until the issue has been resolved.
620e57d8b01SWarner Losh
621b001d36fSJacques Vidrine20011202:
622b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
623b001d36fSJacques Vidrine	patched.
624b001d36fSJacques Vidrine
6254b676ec1SWarner Losh20011126:
6264b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
6275ebbf43eSWarner Losh	after this date.  You need to do this only once.
6284b676ec1SWarner Losh
629d961e462SWarner Losh20011103:
630d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
631d961e462SWarner Losh	edges may be left, but for the most part things should be
6324b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
633d961e462SWarner Losh
634d961e462SWarner Losh20011030:
635d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
636d961e462SWarner Losh	choppy waves in the upgrade process.
637d961e462SWarner Losh
6381fe003b6SWarner Losh20011030:
639a4b6fda0SWarner Losh	The asr driver problem has been resolved.
6401fe003b6SWarner Losh
6411fe003b6SWarner Losh20011027:
6421fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
6431fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
6441fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
6451fe003b6SWarner Losh	try to use from this date forward.
6461fe003b6SWarner Losh
6471fe003b6SWarner Losh20011025:
6481fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
6491fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
6501fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
6511fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
6521fe003b6SWarner Losh	TARGET_ARCH=i386.
6531fe003b6SWarner Losh
654d05f9643SWarner Losh20011001:
655d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
656d05f9643SWarner Losh	You must recompile both the kernel and userland applications
657d05f9643SWarner Losh	at the same time.
658d05f9643SWarner Losh
65958970f85SWarner Losh20010929:
66058970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
66158970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
66258970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
66358970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
6649d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
66558970f85SWarner Losh
66658970f85SWarner Losh20010927:
66758970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
66858970f85SWarner Losh	To disable ACPI you can add
66966ff0e67SMax Khon		hint.acpi.0.disabled="1"
67058970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
67158970f85SWarner Losh	loader "ok" prompt).
67258970f85SWarner Losh
67358970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
67458970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
67558970f85SWarner Losh	file and not list acpi in that list.
676378f4486SAlfred Perlstein
6775119d237SWarner Losh20010924:
6785119d237SWarner Losh	The buildworld has been fixed.  You may need to install
6795119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
6808b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
6818b039fffSWarner Losh	get them installed on every installworld, or execute the
6828b039fffSWarner Losh	following to get them installed only once:
6838b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
68458970f85SWarner Losh		make all install
6858b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
6865119d237SWarner Losh
6873c293725SWarner Losh20010919:
6883c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
6893c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
6903c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
691772730c7SWarner Losh	workaround is to add
6923c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
6933c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
6943c293725SWarner Losh	can be removed afterwards.
6953c293725SWarner Losh
6963c293725SWarner Losh	A proper fix to the buildworld target is needed.
6973c293725SWarner Losh
6983c293725SWarner Losh20010918:
6993c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
7003c293725SWarner Losh	NFS may be unstable after this date.
7013c293725SWarner Losh
7023c293725SWarner Losh20010912:
7033c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
7043c293725SWarner Losh	the kernel.  While a few problems were introduced in the
7053c293725SWarner Losh	initial commit, most of the major ones have been found and
7063c293725SWarner Losh	corrected.
7073c293725SWarner Losh
7083c293725SWarner Losh20010901:
7093c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
7103c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
7113c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
7123c293725SWarner Losh	have been rectified around this date.
7133c293725SWarner Losh
71498b17b95SWarner Losh20010823:
71598b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
71698b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
71798b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
71898b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
71998b17b95SWarner Losh 	sure that user or group bind has read (and not write)
72098b17b95SWarner Losh 	permission for your name server configuration and that it
72198b17b95SWarner Losh 	has read and write permission for your slave zone files and
72298b17b95SWarner Losh 	directory.
72398b17b95SWarner Losh
72498b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
72598b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
72698b17b95SWarner Losh
72798b17b95SWarner Losh 		named_flags=
72898b17b95SWarner Losh
7297b9786edSMark Murray20010709:
7307b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
7317b9786edSMark Murray	the ability of the shared library major number to handle.
7327b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
7337b9786edSMark Murray	solution is to rebuild those ports.
7347b9786edSMark Murray
7351d28950eSWarner Losh20010628:
7361d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
7371d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
7381d28950eSWarner Losh
739e72fd46aSWarner Losh20010625:
74098b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
74198b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
74298b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
74398b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
74498b17b95SWarner Losh	IRQ configuration needs more safety belts.
74516de1a07SWarner Losh
7460d415dffSWarner Losh20010617:
747e72fd46aSWarner Losh	Softupdates problems have been corrected.
7480d415dffSWarner Losh
7490d415dffSWarner Losh20010614:
7500d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
7510d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
7520d415dffSWarner Losh	kernel building methods.
7530d415dffSWarner Losh
7548b9959adSWarner Losh20010613:
7558b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
7568b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
757e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
758e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
7598b9959adSWarner Losh
760e72fd46aSWarner Losh20010613:
7618b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
762e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
763e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
7648b9959adSWarner Losh
7650d415dffSWarner Losh20010612:
7660d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
7670d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
7680d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
7690d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
7700d415dffSWarner Losh	until this bug is fixed.
7710d415dffSWarner Losh
772e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
773e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
774ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
775e72fd46aSWarner Losh
7760d415dffSWarner Losh20010610:
7770d415dffSWarner Losh	Locale names have changed to match other systems better.
7780d415dffSWarner Losh
7796ccdb5e4SWarner Losh20010604:
7806ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
7816ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
7826ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
7833590182eSWarner Losh	Interrupt storms look a lot like a hang.
7843590182eSWarner Losh
7853590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
7863590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
7873590182eSWarner Losh	it is).
7883590182eSWarner Losh
7893590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
7903590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
7913590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
7923590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
7936ccdb5e4SWarner Losh
7940bc62786SWarner Losh20010530:
7950bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
7960bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
7970bc62786SWarner Losh	a limited time.  If you see
7980bc62786SWarner Losh
7990bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
8000bc62786SWarner Losh
8010bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
8020bc62786SWarner Losh	COPY=-C.
8030bc62786SWarner Losh
80468a38c6cSWarner Losh20010525:
805b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
806c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
807c4f4a728SWarner Losh	definitely is in bad shape.
80868a38c6cSWarner Losh
809ed0f29caSWarner Losh20010521:
810ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
811ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
812ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
813ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
814ed0f29caSWarner Losh	is
815ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
816ed0f29caSWarner Losh
81780c16af9SWarner Losh20010520:
81868a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
81980c16af9SWarner Losh
82080c16af9SWarner Losh20010519:
82180c16af9SWarner Losh	pccard has had much reorganizational work done to it over
82280c16af9SWarner Losh	the past few days.  Everything should still work, but if
82380c16af9SWarner Losh	not, please contact imp@freebsd.org.
82480c16af9SWarner Losh
825a45f2d05SWarner Losh20010517:
826a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
827a45f2d05SWarner Losh	userland at the same time.
828a45f2d05SWarner Losh
829a45f2d05SWarner Losh20010517:
830a45f2d05SWarner Losh	New ncurses imported.
831a45f2d05SWarner Losh
8322988afcaSWarner Losh20010512:
8332988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
8342988afcaSWarner Losh	will be the only way to go starting July 1.
8352988afcaSWarner Losh
8361a33dba7SWarner Losh20010504:
8371a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
8381a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
8391a33dba7SWarner Losh
84009946a51SWarner Losh20010502:
84109946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
84209946a51SWarner Losh
84309946a51SWarner Losh20010501:
84409946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
84509946a51SWarner Losh
84609946a51SWarner Losh20010430:
847a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
84809946a51SWarner Losh	go back in the water.
84909946a51SWarner Losh
85009946a51SWarner Losh20010429:
85109946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
85209946a51SWarner Losh	this date, but before the correction date.
85309946a51SWarner Losh
85491dd3b53SWarner Losh20010423:
85591dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
85691dd3b53SWarner Losh
85791dd3b53SWarner Losh20010411:
85891dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
85991dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
86091dd3b53SWarner Losh	Update only if you understand that you must not use the old
86191dd3b53SWarner Losh	fsck with the new kernel ever.
86291dd3b53SWarner Losh
863933b3269SWarner Losh20010330:
864933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
865c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
866933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
867933b3269SWarner Losh
868933b3269SWarner Losh20010319:
869933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
870933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
871933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
872f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
87309946a51SWarner Losh
87409946a51SWarner Losh20010315:
87509946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
876ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
87709946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
878933b3269SWarner Losh
879933b3269SWarner Losh20010312:
880933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
881933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
882933b3269SWarner Losh
883933b3269SWarner Losh20010312:
884933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
885933b3269SWarner Losh	instead of ad-hoc.
886933b3269SWarner Losh
887933b3269SWarner Losh20010310:
888f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
889933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
890933b3269SWarner Losh	ssh might not work if you don't.
891933b3269SWarner Losh
89262353691SWarner Losh20010303:
89362353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
89462353691SWarner Losh	which means that you must include the miibus in your kernel if
89562353691SWarner Losh	you use the ed driver.
89662353691SWarner Losh
897d325cf65SWarner Losh20010220:
898d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
899d325cf65SWarner Losh	safe to go back into the water.
900d325cf65SWarner Losh
901024daae6SWarner Losh20010211:
902024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
903024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
904024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
905024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
906024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
907024daae6SWarner Losh
908024daae6SWarner Losh	To get to the new system, you'll need to use the following
909024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
910024daae6SWarner Losh	don't have to move this to the updating section.
911024daae6SWarner Losh
912024daae6SWarner Losh	To get around the installworld problem, do:
913024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
914024daae6SWarner Losh		# make install
915024daae6SWarner Losh		# cd /usr/src
916024daae6SWarner Losh		# make installworld
917024daae6SWarner Losh	If that doesn't work, then try:
918024daae6SWarner Losh		# make -k installworld
919024daae6SWarner Losh		# make installworld
920024daae6SWarner Losh
921024daae6SWarner Losh20010207:
922024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
923024daae6SWarner Losh	do not include devfs in your kernel as problems result.
924024daae6SWarner Losh
925024daae6SWarner Losh20010205:
9267595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
927024daae6SWarner Losh	Remove them from your config.
928024daae6SWarner Losh
9291e159248SWarner Losh20010122:
9301e159248SWarner Losh	****************************** WARNING ******************************
9311e159248SWarner Losh			buildkernel has been changed slightly
9321e159248SWarner Losh	****************************** WARNING ******************************
9331e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
9341e159248SWarner Losh	should update your scripts and make.conf accordingly.
9351e159248SWarner Losh
9361e159248SWarner Losh20010119:
9371e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
9381e159248SWarner Losh	This requires a new config to build correctly.
9391e159248SWarner Losh
940aac7dfeaSWarner Losh20010116:
941ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
942aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
943aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
944aac7dfeaSWarner Losh
945aac7dfeaSWarner Losh20010110:
946aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
947aac7dfeaSWarner Losh
948aac7dfeaSWarner Losh20010102:
949aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
950aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
951aac7dfeaSWarner Losh
95263c90c9eSWarner Losh20010101:
95363c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
95463c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
9555fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
95663c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
95763c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
95863c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
95963c90c9eSWarner Losh	might have been ignored by the -k option.
96063c90c9eSWarner Losh
9615fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
9625fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
9635fd2a895SWarner Losh	of this working.
9645fd2a895SWarner Losh
965aac7dfeaSWarner Losh20001228:
966aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
967ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
968aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
969aac7dfeaSWarner Losh
970de2bcc63SWarner Losh20001218:
971de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
972de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
973de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
974de2bcc63SWarner Losh	cards will not be recognized without it.
975de2bcc63SWarner Losh
976960773f7SWarner Losh20001205:
977960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
978960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
979960773f7SWarner Losh	adding the following in pam.conf:
980960773f7SWarner Losh
981960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
982960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
983960773f7SWarner Losh	sshd    session required        pam_permit.so
984960773f7SWarner Losh
9850acc635eSWarner Losh20001031:
9860acc635eSWarner Losh	cvs updated to 1.11.
9870acc635eSWarner Losh
9880acc635eSWarner Losh20001020:
9890acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
9900acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
9910acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
9920acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
9930acc635eSWarner Losh	workaround.
9940acc635eSWarner Losh
9950acc635eSWarner Losh20001010:
9960acc635eSWarner Losh	****************************** WARNING ******************************
9970acc635eSWarner Losh				Sendmail has been updated.
9980acc635eSWarner Losh	****************************** WARNING ******************************
9990acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
10000acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
10010acc635eSWarner Losh	  is set.
10020acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
10030acc635eSWarner Losh	  commands.
10040acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
10050acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
10060acc635eSWarner Losh	  in /usr/share/sendmail/cf.
10070acc635eSWarner Losh	o sendmail.cw changed to local-host-names
10080acc635eSWarner Losh
10090acc635eSWarner Losh	More details can be found at
10100acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
10110acc635eSWarner Losh
10126e98a146SWarner Losh20001009:
10136e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
10146e98a146SWarner Losh	your entire ports tree, or you will have problems.
10156e98a146SWarner Losh
10166e98a146SWarner Losh20001006:
1017685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
10186e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
10196e98a146SWarner Losh	/usr/bin/miniperl.
10206e98a146SWarner Losh
1021073113a4SWarner Losh20001005:
1022073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1023685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1024073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1025073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1026073113a4SWarner Losh	tree for anything to work.
1027073113a4SWarner Losh
10280acc635eSWarner Losh20000928:
10290acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
10300acc635eSWarner Losh
1031be3885b3SWarner Losh20000916:
1032be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1033be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1034be3885b3SWarner Losh	same time as your kernel.
1035be3885b3SWarner Losh
103676ec9675SWarner Losh20000914:
103776ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
103876ec9675SWarner Losh	include the device will cause suspended laptops losing time
103976ec9675SWarner Losh	when they resume.  Include
104076ec9675SWarner Losh		device		pmtimer
104176ec9675SWarner Losh	in your config file and
104201b9a434SWarner Losh		hint.pmtimer.0.at="isa"
104376ec9675SWarner Losh	to your /boot/device.hints file.
104476ec9675SWarner Losh
1045f4865386SMark Murray20000911:
1046f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1047f4865386SMark Murray	rather than an option. The supplied kernel config files have
1048f4865386SMark Murray	been updated. You will need to do something similar in your
1049f4865386SMark Murray	own kernel config file.
1050f4865386SMark Murray	Remove:
1051f4865386SMark Murray		options		RANDOMDEV
1052f4865386SMark Murray	Add:
1053f4865386SMark Murray		device		random
1054f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1055f4865386SMark Murray	nothing.
1056f4865386SMark Murray
1057d594498fSWarner Losh20000909:
1058d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1059d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1060d594498fSWarner Losh	reflect this if you load this module at boot time.
1061d594498fSWarner Losh	The line should read:
1062d594498fSWarner Losh		random_load="YES"
1063d594498fSWarner Losh
10640deb7ddcSWarner Losh20000907:
10650deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
106616eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
106716eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
106816eb772dSWarner Losh	sure you don't have model loading problems which might at
106916eb772dSWarner Losh	first blush appear related to SMP.
107052bf24e7SWarner Losh
10715a01880bSWarner Losh20000906:
10725a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
10735a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
10745a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
10755a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
10765a01880bSWarner Losh	don't have one, and you have host.conf.
10775a01880bSWarner Losh
10782b41163cSWarner Losh20000905:
107938d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
108038d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
108138d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
108238d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
108338d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
108438d6ecd2SWarner Losh
108538d6ecd2SWarner Losh20000905:
10868aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
10878aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
10888aab4bc7SWarner Losh	is /boot/kernel.
10898aab4bc7SWarner Losh
10908aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
109138d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
109238d6ecd2SWarner Losh	installkernel/installworld dance.
10932b41163cSWarner Losh
1094d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1095d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1096d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1097d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1098d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1099d594498fSWarner Losh
1100d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1101d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1102d594498fSWarner Losh		chflags noschg /kernel.old
1103d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1104d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1105d594498fSWarner Losh	fi
1106d594498fSWarner Losh
1107c22a309cSWarner Losh20000904:
1108c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1109c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1110c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1111c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1112c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1113c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1114c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1115c22a309cSWarner Losh	is not likely to be generated.
1116c22a309cSWarner Losh
1117fdb9f54dSWarner Losh20000825:
1118fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
11199c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
11209c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
11219c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
11229c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
11239c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
11249c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
11259c1a7444SWarner Losh	kernel.
11269c1a7444SWarner Losh
11279c1a7444SWarner Losh20000821:
11289c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
11299c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
11309c1a7444SWarner Losh	/boot/loader.conf.
1131fdb9f54dSWarner Losh
11328f250aa7SWarner Losh20000812:
11335da0d091SWarner Losh	suidperl is now always built and installed on the system, but
11345da0d091SWarner Losh	with permissions of 511.  If you have applications that use
11355da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
11365da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
11375da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
11385da0d091SWarner Losh	will fix this until the next build.
11395da0d091SWarner Losh
11405da0d091SWarner Losh20000812:
11418f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
11428f250aa7SWarner Losh	visible changes that may immediately affect your configuration
11438f250aa7SWarner Losh	include:
11448f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
11458f250aa7SWarner Losh	- newaliases limited to root and trusted users
11468f250aa7SWarner Losh	- MSA port (587) turned on by default
11478f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
11488f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
11498f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
11508f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
11518f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
11528f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
11538f250aa7SWarner Losh
115471c38472SWarner Losh20000810:
115571c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
115671c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
115771c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
115871c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
115971c38472SWarner Losh	specific use for it.
116071c38472SWarner Losh
116171c38472SWarner Losh20000729:
116271c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
116371c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
116471c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
116571c38472SWarner Losh	afterwards (unless the variables already are set, of course):
116671c38472SWarner Losh		# Enable network daemons for user convenience.
116771c38472SWarner Losh		inetd_enable="YES"
116871c38472SWarner Losh		portmap_enable="YES"
116971c38472SWarner Losh		sendmail_enable="YES"
117071c38472SWarner Losh
117171c38472SWarner Losh20000728:
117271c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
117371c38472SWarner Losh	will need to change that to nullfs_load="YES".
117471c38472SWarner Losh
11751dece4a9SWarner Losh20000728:
11761dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
11771dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
11781dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
11791dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
11801dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
11811dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
11821dece4a9SWarner Losh	to /MYKERNEL.
11831dece4a9SWarner Losh
1184409e887cSWarner Losh20000711:
1185409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1186409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1187409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1188409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1189409e887cSWarner Losh	for details on potential problems that you might have and how
1190409e887cSWarner Losh	to get around them.
1191409e887cSWarner Losh
1192409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1193409e887cSWarner Losh	clauses above, you needn't worry.
1194409e887cSWarner Losh
1195409e887cSWarner Losh20000711:
1196409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1197409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1198409e887cSWarner Losh	in the number of changed programs the first time when you run
1199409e887cSWarner Losh	mergemaster to get a new /etc/security.
1200409e887cSWarner Losh
1201673d13f2SWarner Losh20000710:
1202673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1203673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1204673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1205673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1206673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1207673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1208673d13f2SWarner Losh	errors. (see below, 20000624).
1209673d13f2SWarner Losh
1210bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
12111dece4a9SWarner Losh
1212673d13f2SWarner Losh20000709:
1213c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1214c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1215c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1216673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1217673d13f2SWarner Losh
1218e98e26cdSWarner Losh20000706:
1219e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1220e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1221e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1222f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1223e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
12242c021c6cSMark Ovens	interim if needed.
1225e98e26cdSWarner Losh
1226e98e26cdSWarner Losh20000705:
1227e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1228e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1229e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1230e98e26cdSWarner Losh	details.
1231e98e26cdSWarner Losh
1232c373950eSWarner Losh20000704:
12332f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
12342f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
12352f961bc8SWarner Losh
12362f961bc8SWarner Losh20000704:
1237c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1238c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1239c373950eSWarner Losh	rc.d scripts that haven't been updated.
1240c373950eSWarner Losh
124127dc3a2bSWarner Losh20000630:
124227dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
124327dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
124427dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
124527dc3a2bSWarner Losh
1246b8c215acSWarner Losh20000625:
1247b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
124827dc3a2bSWarner Losh	system installed in order to build the system and kernel.
124927dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
125027dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
125127dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
125227dc3a2bSWarner Losh	were required.  You should check with the latest collections
125327dc3a2bSWarner Losh	to make sure that these haven't changed.
1254b8c215acSWarner Losh
12557b990719SWarner Losh20000624:
12567b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
12577b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
12587b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
12591a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
12607b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
12617b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
12627b990719SWarner Losh	date to the completion of the work.
12637b990719SWarner Losh
126427dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
126527dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
126627dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
126727dc3a2bSWarner Losh	recreate the random and urandom devices.
126827dc3a2bSWarner Losh
126981e54c50SWarner Losh20000622:
127081e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
127181e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
127281e54c50SWarner Losh	that used to be required when updating.
127381e54c50SWarner Losh
127439943833SWarner Losh20000621:
12752c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
12762a2f33fbSDaniel Baker	the config file update procedure.
12772a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1278c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
127959df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
128059df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
128139943833SWarner Losh
1282290f9ad8SWarner Losh20000620:
1283290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1284290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1285290f9ad8SWarner Losh	that workaround will no longer be required.
1286290f9ad8SWarner Losh
128790fb6346SWarner Losh20000615:
128890fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
128990fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
129090fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
129190fb6346SWarner Losh	devices.
129290fb6346SWarner Losh
1293f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1294f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1295f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1296f75f65bbSWarner Losh	may work).
1297f75f65bbSWarner Losh
1298ba26da8eSWarner Losh20000612:
1299ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1300290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1301c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1302290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1303f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1304f54a3542SWarner Losh	NEWCARD for examples of the new format.
1305290f9ad8SWarner Losh
13069698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
13079698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
13089698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
13099698f2c0SWarner Losh	in it.
1310bbcc5149SWarner Losh
1311d65850ebSWarner Losh20000522:
1312ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1313d65850ebSWarner Losh	building a kernel after this point is advised that they need
1314d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1315d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1316d65850ebSWarner Losh
1317d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1318d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1319d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1320d9583a00SWarner Losh	is resolved.
1321d9583a00SWarner Losh
13228039cedeSWarner Losh20000513:
13238039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
13248039cedeSWarner Losh
1325d65850ebSWarner Losh20000510:
13268039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
13278039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
13288039cedeSWarner Losh	is requires for the boot blocks to build properly.
13298039cedeSWarner Losh
13308039cedeSWarner Losh20000503:
13318039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
13328039cedeSWarner Losh	is now available.
13338039cedeSWarner Losh
1334d65850ebSWarner Losh20000502:
1335d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1336d65850ebSWarner Losh	connected to the kernel building instead.
1337d65850ebSWarner Losh
1338be149406SNik Clayton20000427:
13398039cedeSWarner Losh	You may need to build gperf
13408039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
13418039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
13428039cedeSWarner Losh	an option only in -current.
13438039cedeSWarner Losh
13442b8dd5f4SWarner Losh20000417:
13452b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1346f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
13472b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
13482b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
13492c021c6cSMark Ovens	before you reboot, you'll need to issue:
13502b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
13512b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
13522b8dd5f4SWarner Losh
13538d9f1945SWarner Losh20000320:
13542b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
13552b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
13562b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1357ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
13582b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
13598d9f1945SWarner Losh
1360f8ab1dd6SWarner Losh20000319:
1361f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1362f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1363f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1364f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1365f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1366f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1367f8ab1dd6SWarner Losh
136819cada77SWarner Losh20000318:
1369f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
137019cada77SWarner Losh	Large kernel changes are being committed and are in the
137119cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
137219cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
137319cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
137419cada77SWarner Losh	that you are loading are up to date.
1375ba228352SWarner Losh
137619cada77SWarner Losh20000315:
13776d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
13786d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
13796d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
13806d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
13816d23c382SWarner Losh	boot.
13826d23c382SWarner Losh
13836d23c382SWarner Losh20000315:
138419cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
138519cada77SWarner Losh	to upgrade to 4.0 from 3.x.
138657199806SWarner Losh
1387dc0dbf5cSWarner LoshCOMMON ITEMS:
1388dc0dbf5cSWarner Losh
1389a24eff53SWarner Losh	General Notes
1390a24eff53SWarner Losh	-------------
1391a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1392a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1393a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1394a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1395a24eff53SWarner Losh	or several minor releases, or when several months have passed
1396a24eff53SWarner Losh	on the -current branch).
1397a24eff53SWarner Losh
13985780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
13995780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
14005780f3baSWarner Losh	environment when searching for values for global variables.
14015780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
14025780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
14035780f3baSWarner Losh	page for more details.
14045780f3baSWarner Losh
1405dc0dbf5cSWarner Losh	To build a kernel
1406dc0dbf5cSWarner Losh	-----------------
1407ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1408f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1409ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1410282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1411282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1412dc0dbf5cSWarner Losh
1413ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1414ba01eb20SWarner Losh	--------------------------------------------------------------
14150fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
14160fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
14170fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
14180fbd2da9SKen Smith
14190fbd2da9SKen Smith	cd src/sys/${arch}/conf
142047d0d01fSWarner Losh	config KERNEL_NAME_HERE
14210fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1422ba01eb20SWarner Losh	make depend
1423ba01eb20SWarner Losh	make
1424ba01eb20SWarner Losh	make install
1425ba01eb20SWarner Losh
1426ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1427ba01eb20SWarner Losh
1428ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1429ba01eb20SWarner Losh	-----------------------------------------------------------
143063cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
143163cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
143263cb445eSWarner Losh
1433f643de42SWarner Losh	<make sure you have good level 0 dumps>
143463cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
143563cb445eSWarner Losh	make buildworld
143663cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
143763cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
143863cb445eSWarner Losh							[1]
143963cb445eSWarner Losh	<reboot in single user>				[3]
14408633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
144163cb445eSWarner Losh	mergemaster -p					[5]
144263cb445eSWarner Losh	make installworld
144363cb445eSWarner Losh	mergemaster					[4]
144463cb445eSWarner Losh	<reboot>
144563cb445eSWarner Losh
1446759f0aefSWarner Losh
1447f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1448f27b1fceSJoseph Koshy	--------------------------------------------------
1449f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1450f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1451f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1452f27b1fceSJoseph Koshy	# size.
1453f27b1fceSJoseph Koshy
1454f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1455f27b1fceSJoseph Koshy	<boot into -stable>
1456f27b1fceSJoseph Koshy	make buildworld
1457f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1458f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1459f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1460f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1461f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1462f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1463f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1464f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1465f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1466f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1467f27b1fceSJoseph Koshy	<reboot into current>
1468f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1469f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1470f27b1fceSJoseph Koshy 	<reboot>
1471f27b1fceSJoseph Koshy
1472f27b1fceSJoseph Koshy
1473f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1474f27b1fceSJoseph Koshy	----------------------------------------------
14755c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
14765c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
14775c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
14785c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1479ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1480f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1481f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1482f643de42SWarner Losh	# space on /.
1483f643de42SWarner Losh
1484f643de42SWarner Losh	<make sure you have good level 0 dumps>
1485fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
148621c075eaSWarner Losh	make buildworld					[9]
1487c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1488d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1489be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1490fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1491fc8c157fSWarner Losh							[1]
1492fc8c157fSWarner Losh	<reboot in single user>				[3]
14938633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
1494835284beSWarner Losh	mergemaster -p					[5]
1495f8a4c901SWarner Losh	rm -rf /usr/include/g++
1496ba26da8eSWarner Losh	make installworld
1497a6cd4f9dSWarner Losh	mergemaster					[4]
1498ba26da8eSWarner Losh	<reboot>
1499ba26da8eSWarner Losh
1500fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1501fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1502fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1503fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1504fdb9f54dSWarner Losh	the UPDATING entries.
1505ba26da8eSWarner Losh
15061dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
15071dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
15081dece4a9SWarner Losh	your sources that you have read and understood all the recent
15091dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
15101dece4a9SWarner Losh	much fewer pitfalls.
15111dece4a9SWarner Losh
1512134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1513134d2e86SWarner Losh	should disable them at this point so they don't crash your
1514134d2e86SWarner Losh	system on reboot.
1515134d2e86SWarner Losh
15169c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
15179c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
15189c1a7444SWarner Losh	configuration.
15199c1a7444SWarner Losh
1520ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1521ee6e1fc3SWarner Losh		fsck -p
1522ee6e1fc3SWarner Losh		mount -u /
1523ee6e1fc3SWarner Losh		mount -a
1524ee6e1fc3SWarner Losh		cd /usr/src
152547d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1526f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1527f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1528b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1529b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1530b705ae10SWarner Losh	be ignored while you proceed to the next step.
1531ee6e1fc3SWarner Losh
1532a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1533a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1534a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1535a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1536a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1537a6cd4f9dSWarner Losh	for potential gotchas.
1538a6cd4f9dSWarner Losh
1539835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1540835284beSWarner Losh	you may need to do this if you get unknown user in the following
1541835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1542835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1543835284beSWarner Losh	install) after the buildworld before this step if you last updated
1544835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1545835284beSWarner Losh
1546bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1547bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1548bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1549bd79cf40SWarner Losh		ok unload
1550bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1551bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1552bd79cf40SWarner Losh	described here.
1553fc8c157fSWarner Losh
1554fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1555fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1556fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1557fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1558fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1559fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1560fc8c157fSWarner Losh
1561c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1562c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1563c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1564c74fe6afSWarner Losh	that is hard to boot to recover.
1565c74fe6afSWarner Losh
156621c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
156721c075eaSWarner Losh	cvs prune empty directories.
15688633bbeaSBrooks Davis
15698633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
15708633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
15718633bbeaSBrooks Davis	takes care of this.
1572dc0dbf5cSWarner LoshFORMAT:
1573dc0dbf5cSWarner Losh
1574f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
15751fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1576f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1577f8ab1dd6SWarner Loshprevious releases if your system is older than this.
15781fc1a0dcSWarner Losh
1579e72fd46aSWarner LoshCopyright information:
1580e72fd46aSWarner Losh
15819698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1582e72fd46aSWarner Losh
1583772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1584772730c7SWarner Loshmodification, in full or in part, in any form or format of this
15859698f2c0SWarner Loshdocument are permitted without further permission from the author.
1586e72fd46aSWarner Losh
1587e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1588e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1589e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1590e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1591e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1592e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1593e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1594e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1595e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1596e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1597e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1598e72fd46aSWarner Losh
1599e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1600e72fd46aSWarner Loshauthor a beer.
1601e72fd46aSWarner Losh
160222306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1603772730c7SWarner Loshthis document.
1604772730c7SWarner Losh
160597d92980SPeter Wemm$FreeBSD$
1606