xref: /freebsd/UPDATING (revision df843493adbe62bdbee13a0433a9c51c810733e5)
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
206cb7a382SMax Laier20040613:
216cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
226cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
23df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
24df843493SMax Laier	please recompile and reinstall world.
256cb7a382SMax Laier
262454685eSJulian Elischer20040607:
272454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
282454685eSJulian Elischer	requires that you re-run config after updating your tree.
292454685eSJulian Elischer
3064fef830SSeigo Tanimura20040601:
3164fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
3264fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
3364fef830SSeigo Tanimura	kernel configuration.
3464fef830SSeigo Tanimura
35bb4f06e7SAndre Oppermann20040423:
36bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
37bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
38bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
39bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
40bb4f06e7SAndre Oppermann
4105641e82SColin Percival20040420:
4205641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
4305641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
4405641e82SColin Percival	20040406.
4505641e82SColin Percival
46d0dc9183SWarner Losh20040414:
47d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
48d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
49d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
50d0dc9183SWarner Losh
51d0dc9183SWarner Losh20040412:
52d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
53d0dc9183SWarner Losh	drive is still broken.
54d0dc9183SWarner Losh
55d0dc9183SWarner Losh20040410:
56d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
57d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
58d0dc9183SWarner Losh	the unanticipated problems have been resolved.
59d0dc9183SWarner Losh
608633bbeaSBrooks Davis20040409:
618633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
628633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
638633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
648633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
6576c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
668633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
678633bbeaSBrooks Davis
68d40d033aSRobert Watson20040322:
69d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
70d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
71d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
72d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
73d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
74d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
75d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
76d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
77d40d033aSRobert Watson	locking is merged to permit this to take place.
78d40d033aSRobert Watson
79ec9b318eSGarance A Drosehn20040310:
80ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
81ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
82ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
83ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
84ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
85ec9b318eSGarance A Drosehn
86fc28f1ffSMax Laier20040308:
87fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
88fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
894c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
904c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
91fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
92fc28f1ffSMax Laier	pf system consists of the following three devices:
93fc28f1ffSMax Laier	device		pf		# required
94fc28f1ffSMax Laier	device		pflog		# optional
95fc28f1ffSMax Laier	device		pfsync		# optional
96fc28f1ffSMax Laier
973aff5d06SDag-Erling Smørgrav20040303:
983aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
993aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
1003aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
1013aff5d06SDag-Erling Smørgrav
1023aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
1033aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
1043aff5d06SDag-Erling Smørgrav
1053aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
1063aff5d06SDag-Erling Smørgrav	to use libpthread instead.
1073aff5d06SDag-Erling Smørgrav
108fd63c5b3SDag-Erling Smørgrav20040226:
1099d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
110fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
111fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
112fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
113fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
114fd63c5b3SDag-Erling Smørgrav
115714ae42aSBruce M Simpson20040225:
116e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
117e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
118e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
119e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
120e07a40f3SBrian Feldman	should remain unaffected.
121e07a40f3SBrian Feldman
122e07a40f3SBrian Feldman20040225:
123714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
124714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
125714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
126714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
127714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
128714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
129714ae42aSBruce M Simpson
130fbd2e692SAndre Oppermann20040224:
131fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
132fbd2e692SAndre Oppermann	and related userland network utilities neccessary.
133fbd2e692SAndre Oppermann
134158b90daSWarner Losh20040222:
135158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
136158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
137158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
138158b90daSWarner Losh	Drivers outside the tree will need to be updated.
139158b90daSWarner Losh
140b7b1e150SMike Makonnen20040207:
141b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
142b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
143b7b1e150SMike Makonnen
144aca89ee6SDaniel Eischen20040130:
145aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
146aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
147aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
148aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
149aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
150aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
151aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
152aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
153aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
154aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
155aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
156aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
157aca89ee6SDaniel Eischen	do not work with libpthread.
158aca89ee6SDaniel Eischen
15968b7b3a9SAlex Dupre20040125:
16068b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
16168b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
16268b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
16368b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
16468b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
16568b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
16668b7b3a9SAlex Dupre
167ff46e0deSWarner Losh20040125:
168ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
169ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
170ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
171ff46e0deSWarner Losh
172ce41f4bfSRobert Watson20031213:
173ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
174ce41f4bfSRobert Watson	if the login process is unable to successfully set the
175ce41f4bfSRobert Watson	process credentials to include all groups defined for the
176ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
177ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
178ce41f4bfSRobert Watson	defined, or they will be unable to log in.
179ce41f4bfSRobert Watson
180c124fa05SJohn Baldwin20031203:
181c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
182c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
183c124fa05SJohn Baldwin
1848ad1f5e4SHartmut Brandt20031112:
18530093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
18630093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
18797209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
18897209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
18997209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
19097209ca3SRobert Watson	not know about the new system calls that support the new statfs
1913f631d52SMarcel Moolenaar	structure.
1923f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
1933f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
1943f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
1953f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
1963f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
1973f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
1983f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
1993f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
2003f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
2013f631d52SMarcel Moolenaar	these changes are installed.
20230093b05SWarner Losh
20330093b05SWarner Losh	****************************DANGER*******************************
20430093b05SWarner Losh
20530093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
20630093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
20730093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
20830093b05SWarner Losh	kernel.
20964a18d6fSKirk McKusick
21064a18d6fSKirk McKusick20031112:
2118ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
2128ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
2138ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
2148ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
2158ad1f5e4SHartmut Brandt	sync before rebooting.
2168ad1f5e4SHartmut Brandt
217c53a5d8fSJohn Baldwin20031111:
218c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
219c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
220c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
221c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
222c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
223c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
224c53a5d8fSJohn Baldwin
2258bf455a5SJohn Baldwin20031103:
2268bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
2278bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
2282a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
2298bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
2308bf455a5SJohn Baldwin
2319bf40edeSBrooks Davis20031031:
2329bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
2339bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
2349bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
2359bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
2369bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
2379bf40edeSBrooks Davis	reflect this change.
2389bf40edeSBrooks Davis
23947a42c7aSPoul-Henning Kamp20030928:
24047a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
24147a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
24247a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
24347a42c7aSPoul-Henning Kamp
24407105342SMax Khon20030926:
24507105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
24607105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
24707105342SMax Khon
24817dcd026SSam Leffler20030925:
24917dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
25017dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
25117dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
25217dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
25317dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
25417dcd026SSam Leffler
255fedf1d01SBruce M Simpson20030923:
256fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
257fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
258fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
259fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
260fedf1d01SBruce M Simpson
261db38f9cbSJacques Vidrine20030915:
262db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
263db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
264db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
265db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
266db38f9cbSJacques Vidrine
267c09d2c2bSMike Makonnen20030829:
268c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
269c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
270c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
271c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
272c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
273c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
274c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
275c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
276c09d2c2bSMike Makonnen	may or may not exist on your system.
277c09d2c2bSMike Makonnen
27817c159dcSSøren Schmidt20030824:
27917c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
28017c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
281f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
282f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
28317c159dcSSøren Schmidt
284c1f61aa9SDavid E. O'Brien20030819:
285c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
286c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
287c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
288c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
28969f7bcf3SWarner Losh
29038c962e7SNate Lawson20030728:
29138c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
29238c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
29338c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
29438c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
29538c962e7SNate Lawson	so the quirk can be re-enabled.
29638c962e7SNate Lawson
29774111097SWarner Losh20030724:
29874111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
29974111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
30074111097SWarner Losh
301178cf4e9SWarner Losh20030722:
302178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
303178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
304178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
305178cf4e9SWarner Losh	FPU hardware.
306178cf4e9SWarner Losh
307178cf4e9SWarner Losh20030714:
308178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
309178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
310178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
311178cf4e9SWarner Losh	People should report those issues to current@.
312178cf4e9SWarner Losh
313157c629aSWarner Losh20030711:
314157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
3158b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
31605538fa9SWarner Losh	/usr/obj.
317157c629aSWarner Losh
31874111097SWarner Losh20030610:
31974111097SWarner Losh	Remove deprecated locale names and transition period code
32074111097SWarner Losh	for them, finishing switching to the new scheme. Check your
32174111097SWarner Losh	LANG environment variable.
32274111097SWarner Losh
32374111097SWarner Losh20030609:
32474111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
32574111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
32674111097SWarner Losh	important to remember beforehand if your source tree is on
32774111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
32874111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
32974111097SWarner Losh	kernel.
33074111097SWarner Losh
33174111097SWarner Losh20030605:
3326cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
3336cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
3346cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
3356cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
3366cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
3376cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
3386cc6353fSMarcel Moolenaar
3396cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
3406cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
3416cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
3426cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
3436cc6353fSMarcel Moolenaar		:
3446cc6353fSMarcel Moolenaar
3456cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
3466cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
3476cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
3486cc6353fSMarcel Moolenaar
34952b47445SMark Murray20030505:
35052b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
35152b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
35252b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
35352b47445SMark Murray
354a26df538SWarner Losh20030502:
355a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
356a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
357a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
358a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
359a26df538SWarner Losh
3604b065e2cSDoug Barton20030501:
3614b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
3624b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
3634b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
3644b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
3654b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
3664b065e2cSDoug Barton	utilizes these old scripts has also been removed.
3674b065e2cSDoug Barton
36881cda3d9SWarner Losh20030423:
36981cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
37081cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
37181cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
37281cda3d9SWarner Losh	have until then to upgrade your kernel before updating
37381cda3d9SWarner Losh	userland.  In general, you should have a userland and
37481cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
37581cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
37681cda3d9SWarner Losh	allowances are made.
37781cda3d9SWarner Losh
37847a657d1SRuslan Ermilov20030329:
37947a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
38047a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
38147a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
38247a657d1SRuslan Ermilov
38347a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
38447a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
38547a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
38647a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
38747a657d1SRuslan Ermilov
38847a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
38947a657d1SRuslan Ermilov	    make cleandir && make obj && \
39047a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
39147a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
39247a657d1SRuslan Ermilov
3935d2af00cSGregory Neil Shapiro20030208:
3945d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
3955d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
3965d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
3975d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
3985d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
3995d2af00cSGregory Neil Shapiro
4005d2af00cSGregory Neil Shapiro20030128:
4019db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
402ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
4039db58771SPoul-Henning Kamp	be removed when convenient.
4049db58771SPoul-Henning Kamp
4058d9b3f57SJake Burkholder20030126:
4068d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
4078d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
4088d9b3f57SJake Burkholder
4091c5efda5SJeff Roberson20030125:
4101c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
4111c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
412ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
4131c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
4141c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
4151c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
4161c5efda5SJeff Roberson
4179d1d64f5SWarner Losh20030115:
4189d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
4199d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
4209d1d64f5SWarner Losh	properly.
4219d1d64f5SWarner Losh
422c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
423c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
424c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
425c9fdb80aSWarner Losh	with NetBSD.
426c9fdb80aSWarner Losh
427161dc364SAlexander Kabaev20021222:
428161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
429161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
430161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
431161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
432161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
433161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
43484cc83efSAlexander Kabaev	rebuilt.
435161dc364SAlexander Kabaev
436fb4c8061SMartin Blapp20021216:
437fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
43889056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
439fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
4409d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
441fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
442fb4c8061SMartin Blapp
44317d47eb3SGiorgos Keramidas20021202:
44417d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
44517d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
44617d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
44717d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
44817d47eb3SGiorgos Keramidas
449a4459294SBill Fenner20021029:
450a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
451a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
452a4459294SBill Fenner	consumers in sync.
453a4459294SBill Fenner
454fc8c157fSWarner Losh20021024:
455c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
456c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
457c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
458c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
459c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
460c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
461c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
462c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
46369f7bcf3SWarner Losh
464fd9e8bdaSAndrew Gallatin20021023:
465fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
466fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
467fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
468fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
469fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
470fd9e8bdaSAndrew Gallatin
471fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
472fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
473fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
474fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
475fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
476fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
477fd9e8bdaSAndrew Gallatin
478f8a4c901SWarner Losh20020831:
479f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
480f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
481f8a4c901SWarner Losh	programs and libraries need to be recompiled.
482f8a4c901SWarner Losh
483f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
484f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
485f8a4c901SWarner Losh
486c2248fa2SJens Schweikhardt20020827:
487c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
488c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
489c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
490c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
491c2248fa2SJens Schweikhardt
4920d533e43SRuslan Ermilov20020815:
4930d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
4940d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
4950d533e43SRuslan Ermilov	again.
4960d533e43SRuslan Ermilov
49733c1de7dSRuslan Ermilov20020729:
49833c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
49933c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
50033c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
50133c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
50233c1de7dSRuslan Ermilov
5032b877facSJulian Elischer20020702:
5042b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
5052b877facSJulian Elischer	There are still some minor problems with some signals but the
5062b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
5072b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
5082b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
5092b877facSJulian Elischer
51006596d37SWarner Losh20020701:
51106596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
51206596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
51306596d37SWarner Losh	GNOME.
51406596d37SWarner Losh
51595ba4330SJacques Vidrine20020511:
51695ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
51795ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
51895ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
51995ba4330SJacques Vidrine	with the set-user-ID bit set.
52095ba4330SJacques Vidrine
521a81da3c9SDavid E. O'Brien20020510:
522f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
523f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
5244b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
525f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
526f50caf6fSDavid E. O'Brien
527f50caf6fSDavid E. O'Brien20020510:
528a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
529a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
530a81da3c9SDavid E. O'Brien	and then do a cvs update.
531a81da3c9SDavid E. O'Brien
532528a0ef5SJacques Vidrine20020421:
533528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
534528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
535528a0ef5SJacques Vidrine
53685aa5a2eSGregory Neil Shapiro20020404:
53785aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
53885aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
53985aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
54085aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
54185aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
54285aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
54385aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
54485aa5a2eSGregory Neil Shapiro
5458f1e4358SRuslan Ermilov20020403:
5468f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
5478f1e4358SRuslan Ermilov
5482292c02eSWarner Losh20020315:
5492292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
5502292c02eSWarner Losh
55169f7bcf3SWarner Losh20020225:
55269f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
55369f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
55469f7bcf3SWarner Losh
5558f35c493SWarner Losh20020217:
5568f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
5578f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
5588f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
5598f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
5608f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
5618f35c493SWarner Losh
562835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
563835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
564835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
565835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
566835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
567835284beSWarner Losh	and group must be merged from src/etc/group and
568835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
569835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
570835284beSWarner Losh	mergemaster before this will work if you are updating from a
571835284beSWarner Losh	very old version of current.  The updating recipe has changed
572835284beSWarner Losh	as of this date.
573835284beSWarner Losh
574fa9401c1SWarner Losh20020112:
575fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
576fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
577fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
578fa9401c1SWarner Losh	you have local modifications, you can use
579fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
580fa9401c1SWarner Losh	/etc/pam.d.
581fa9401c1SWarner Losh
582fa9401c1SWarner Losh	Please see the following url for more details:
583fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
58447d0d01fSWarner Losh20011229:
58547d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
58647d0d01fSWarner Losh	networkfs_types, please note that it has changed
58747d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
58847d0d01fSWarner Losh
589514318a8SWarner Losh20011220:
590514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
591514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
592514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
593514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
594514318a8SWarner Losh	version have now been merged back into the base system's
595514318a8SWarner Losh	version now.  The only user-visible change resulting from this
596514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
597514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
598514318a8SWarner Losh	as well.  (There has never been rc file support for
599514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
600514318a8SWarner Losh	reverted by the time the changes are MFCed.)
601514318a8SWarner Losh
602514318a8SWarner Losh20011215:
603514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
604514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
605514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
606514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
607514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
608514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
609514318a8SWarner Losh	will need to be customized then for `odd' densities using
610514318a8SWarner Losh	fdcontrol(8).
611514318a8SWarner Losh
6122d22e2bfSWarner Losh20011209:
6132d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
6142d22e2bfSWarner Losh	and truss(1) now works again.
6152d22e2bfSWarner Losh
6169e0428e2SWarner Losh20011207:
6179e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
6189e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
6199e0428e2SWarner Losh	see
6209e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
6219e0428e2SWarner Losh	for details.
6229e0428e2SWarner Losh
6239bab8c59SWarner Losh20011204:
6249bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
6259bab8c59SWarner Losh	kernel and burncd to be in sync.
6269bab8c59SWarner Losh
627e57d8b01SWarner Losh20011203:
628e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
629e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
630e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
631e57d8b01SWarner Losh	not there already.
632e57d8b01SWarner Losh
633e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
634e57d8b01SWarner Losh	until the issue has been resolved.
635e57d8b01SWarner Losh
636b001d36fSJacques Vidrine20011202:
637b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
638b001d36fSJacques Vidrine	patched.
639b001d36fSJacques Vidrine
6404b676ec1SWarner Losh20011126:
6414b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
6425ebbf43eSWarner Losh	after this date.  You need to do this only once.
6434b676ec1SWarner Losh
644d961e462SWarner Losh20011103:
645d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
646d961e462SWarner Losh	edges may be left, but for the most part things should be
6474b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
648d961e462SWarner Losh
649d961e462SWarner Losh20011030:
650d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
651d961e462SWarner Losh	choppy waves in the upgrade process.
652d961e462SWarner Losh
6531fe003b6SWarner Losh20011030:
654a4b6fda0SWarner Losh	The asr driver problem has been resolved.
6551fe003b6SWarner Losh
6561fe003b6SWarner Losh20011027:
6571fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
6581fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
6591fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
6601fe003b6SWarner Losh	try to use from this date forward.
6611fe003b6SWarner Losh
6621fe003b6SWarner Losh20011025:
6631fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
6641fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
6651fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
6661fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
6671fe003b6SWarner Losh	TARGET_ARCH=i386.
6681fe003b6SWarner Losh
669d05f9643SWarner Losh20011001:
670d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
671d05f9643SWarner Losh	You must recompile both the kernel and userland applications
672d05f9643SWarner Losh	at the same time.
673d05f9643SWarner Losh
67458970f85SWarner Losh20010929:
67558970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
67658970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
67758970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
67858970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
6799d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
68058970f85SWarner Losh
68158970f85SWarner Losh20010927:
68258970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
68358970f85SWarner Losh	To disable ACPI you can add
68466ff0e67SMax Khon		hint.acpi.0.disabled="1"
68558970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
68658970f85SWarner Losh	loader "ok" prompt).
68758970f85SWarner Losh
68858970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
68958970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
69058970f85SWarner Losh	file and not list acpi in that list.
691378f4486SAlfred Perlstein
6925119d237SWarner Losh20010924:
6935119d237SWarner Losh	The buildworld has been fixed.  You may need to install
6945119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
6958b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
6968b039fffSWarner Losh	get them installed on every installworld, or execute the
6978b039fffSWarner Losh	following to get them installed only once:
6988b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
69958970f85SWarner Losh		make all install
7008b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
7015119d237SWarner Losh
7023c293725SWarner Losh20010919:
7033c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
7043c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
7053c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
706772730c7SWarner Losh	workaround is to add
7073c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
7083c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
7093c293725SWarner Losh	can be removed afterwards.
7103c293725SWarner Losh
7113c293725SWarner Losh	A proper fix to the buildworld target is needed.
7123c293725SWarner Losh
7133c293725SWarner Losh20010918:
7143c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
7153c293725SWarner Losh	NFS may be unstable after this date.
7163c293725SWarner Losh
7173c293725SWarner Losh20010912:
7183c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
7193c293725SWarner Losh	the kernel.  While a few problems were introduced in the
7203c293725SWarner Losh	initial commit, most of the major ones have been found and
7213c293725SWarner Losh	corrected.
7223c293725SWarner Losh
7233c293725SWarner Losh20010901:
7243c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
7253c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
7263c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
7273c293725SWarner Losh	have been rectified around this date.
7283c293725SWarner Losh
72998b17b95SWarner Losh20010823:
73098b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
73198b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
73298b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
73398b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
73498b17b95SWarner Losh 	sure that user or group bind has read (and not write)
73598b17b95SWarner Losh 	permission for your name server configuration and that it
73698b17b95SWarner Losh 	has read and write permission for your slave zone files and
73798b17b95SWarner Losh 	directory.
73898b17b95SWarner Losh
73998b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
74098b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
74198b17b95SWarner Losh
74298b17b95SWarner Losh 		named_flags=
74398b17b95SWarner Losh
7447b9786edSMark Murray20010709:
7457b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
7467b9786edSMark Murray	the ability of the shared library major number to handle.
7477b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
7487b9786edSMark Murray	solution is to rebuild those ports.
7497b9786edSMark Murray
7501d28950eSWarner Losh20010628:
7511d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
7521d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
7531d28950eSWarner Losh
754e72fd46aSWarner Losh20010625:
75598b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
75698b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
75798b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
75898b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
75998b17b95SWarner Losh	IRQ configuration needs more safety belts.
76016de1a07SWarner Losh
7610d415dffSWarner Losh20010617:
762e72fd46aSWarner Losh	Softupdates problems have been corrected.
7630d415dffSWarner Losh
7640d415dffSWarner Losh20010614:
7650d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
7660d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
7670d415dffSWarner Losh	kernel building methods.
7680d415dffSWarner Losh
7698b9959adSWarner Losh20010613:
7708b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
7718b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
772e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
773e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
7748b9959adSWarner Losh
775e72fd46aSWarner Losh20010613:
7768b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
777e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
778e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
7798b9959adSWarner Losh
7800d415dffSWarner Losh20010612:
7810d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
7820d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
7830d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
7840d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
7850d415dffSWarner Losh	until this bug is fixed.
7860d415dffSWarner Losh
787e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
788e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
789ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
790e72fd46aSWarner Losh
7910d415dffSWarner Losh20010610:
7920d415dffSWarner Losh	Locale names have changed to match other systems better.
7930d415dffSWarner Losh
7946ccdb5e4SWarner Losh20010604:
7956ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
7966ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
7976ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
7983590182eSWarner Losh	Interrupt storms look a lot like a hang.
7993590182eSWarner Losh
8003590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
8013590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
8023590182eSWarner Losh	it is).
8033590182eSWarner Losh
8043590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
8053590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
8063590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
8073590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
8086ccdb5e4SWarner Losh
8090bc62786SWarner Losh20010530:
8100bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
8110bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
8120bc62786SWarner Losh	a limited time.  If you see
8130bc62786SWarner Losh
8140bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
8150bc62786SWarner Losh
8160bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
8170bc62786SWarner Losh	COPY=-C.
8180bc62786SWarner Losh
81968a38c6cSWarner Losh20010525:
820b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
821c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
822c4f4a728SWarner Losh	definitely is in bad shape.
82368a38c6cSWarner Losh
824ed0f29caSWarner Losh20010521:
825ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
826ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
827ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
828ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
829ed0f29caSWarner Losh	is
830ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
831ed0f29caSWarner Losh
83280c16af9SWarner Losh20010520:
83368a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
83480c16af9SWarner Losh
83580c16af9SWarner Losh20010519:
83680c16af9SWarner Losh	pccard has had much reorganizational work done to it over
83780c16af9SWarner Losh	the past few days.  Everything should still work, but if
83880c16af9SWarner Losh	not, please contact imp@freebsd.org.
83980c16af9SWarner Losh
840a45f2d05SWarner Losh20010517:
841a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
842a45f2d05SWarner Losh	userland at the same time.
843a45f2d05SWarner Losh
844a45f2d05SWarner Losh20010517:
845a45f2d05SWarner Losh	New ncurses imported.
846a45f2d05SWarner Losh
8472988afcaSWarner Losh20010512:
8482988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
8492988afcaSWarner Losh	will be the only way to go starting July 1.
8502988afcaSWarner Losh
8511a33dba7SWarner Losh20010504:
8521a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
8531a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
8541a33dba7SWarner Losh
85509946a51SWarner Losh20010502:
85609946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
85709946a51SWarner Losh
85809946a51SWarner Losh20010501:
85909946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
86009946a51SWarner Losh
86109946a51SWarner Losh20010430:
862a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
86309946a51SWarner Losh	go back in the water.
86409946a51SWarner Losh
86509946a51SWarner Losh20010429:
86609946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
86709946a51SWarner Losh	this date, but before the correction date.
86809946a51SWarner Losh
86991dd3b53SWarner Losh20010423:
87091dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
87191dd3b53SWarner Losh
87291dd3b53SWarner Losh20010411:
87391dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
87491dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
87591dd3b53SWarner Losh	Update only if you understand that you must not use the old
87691dd3b53SWarner Losh	fsck with the new kernel ever.
87791dd3b53SWarner Losh
878933b3269SWarner Losh20010330:
879933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
880c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
881933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
882933b3269SWarner Losh
883933b3269SWarner Losh20010319:
884933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
885933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
886933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
887f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
88809946a51SWarner Losh
88909946a51SWarner Losh20010315:
89009946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
891ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
89209946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
893933b3269SWarner Losh
894933b3269SWarner Losh20010312:
895933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
896933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
897933b3269SWarner Losh
898933b3269SWarner Losh20010312:
899933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
900933b3269SWarner Losh	instead of ad-hoc.
901933b3269SWarner Losh
902933b3269SWarner Losh20010310:
903f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
904933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
905933b3269SWarner Losh	ssh might not work if you don't.
906933b3269SWarner Losh
90762353691SWarner Losh20010303:
90862353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
90962353691SWarner Losh	which means that you must include the miibus in your kernel if
91062353691SWarner Losh	you use the ed driver.
91162353691SWarner Losh
912d325cf65SWarner Losh20010220:
913d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
914d325cf65SWarner Losh	safe to go back into the water.
915d325cf65SWarner Losh
916024daae6SWarner Losh20010211:
917024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
918024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
919024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
920024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
921024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
922024daae6SWarner Losh
923024daae6SWarner Losh	To get to the new system, you'll need to use the following
924024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
925024daae6SWarner Losh	don't have to move this to the updating section.
926024daae6SWarner Losh
927024daae6SWarner Losh	To get around the installworld problem, do:
928024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
929024daae6SWarner Losh		# make install
930024daae6SWarner Losh		# cd /usr/src
931024daae6SWarner Losh		# make installworld
932024daae6SWarner Losh	If that doesn't work, then try:
933024daae6SWarner Losh		# make -k installworld
934024daae6SWarner Losh		# make installworld
935024daae6SWarner Losh
936024daae6SWarner Losh20010207:
937024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
938024daae6SWarner Losh	do not include devfs in your kernel as problems result.
939024daae6SWarner Losh
940024daae6SWarner Losh20010205:
9417595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
942024daae6SWarner Losh	Remove them from your config.
943024daae6SWarner Losh
9441e159248SWarner Losh20010122:
9451e159248SWarner Losh	****************************** WARNING ******************************
9461e159248SWarner Losh			buildkernel has been changed slightly
9471e159248SWarner Losh	****************************** WARNING ******************************
9481e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
9491e159248SWarner Losh	should update your scripts and make.conf accordingly.
9501e159248SWarner Losh
9511e159248SWarner Losh20010119:
9521e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
9531e159248SWarner Losh	This requires a new config to build correctly.
9541e159248SWarner Losh
955aac7dfeaSWarner Losh20010116:
956ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
957aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
958aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
959aac7dfeaSWarner Losh
960aac7dfeaSWarner Losh20010110:
961aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
962aac7dfeaSWarner Losh
963aac7dfeaSWarner Losh20010102:
964aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
965aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
966aac7dfeaSWarner Losh
96763c90c9eSWarner Losh20010101:
96863c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
96963c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
9705fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
97163c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
97263c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
97363c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
97463c90c9eSWarner Losh	might have been ignored by the -k option.
97563c90c9eSWarner Losh
9765fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
9775fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
9785fd2a895SWarner Losh	of this working.
9795fd2a895SWarner Losh
980aac7dfeaSWarner Losh20001228:
981aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
982ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
983aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
984aac7dfeaSWarner Losh
985de2bcc63SWarner Losh20001218:
986de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
987de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
988de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
989de2bcc63SWarner Losh	cards will not be recognized without it.
990de2bcc63SWarner Losh
991960773f7SWarner Losh20001205:
992960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
993960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
994960773f7SWarner Losh	adding the following in pam.conf:
995960773f7SWarner Losh
996960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
997960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
998960773f7SWarner Losh	sshd    session required        pam_permit.so
999960773f7SWarner Losh
10000acc635eSWarner Losh20001031:
10010acc635eSWarner Losh	cvs updated to 1.11.
10020acc635eSWarner Losh
10030acc635eSWarner Losh20001020:
10040acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
10050acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
10060acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
10070acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
10080acc635eSWarner Losh	workaround.
10090acc635eSWarner Losh
10100acc635eSWarner Losh20001010:
10110acc635eSWarner Losh	****************************** WARNING ******************************
10120acc635eSWarner Losh				Sendmail has been updated.
10130acc635eSWarner Losh	****************************** WARNING ******************************
10140acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
10150acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
10160acc635eSWarner Losh	  is set.
10170acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
10180acc635eSWarner Losh	  commands.
10190acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
10200acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
10210acc635eSWarner Losh	  in /usr/share/sendmail/cf.
10220acc635eSWarner Losh	o sendmail.cw changed to local-host-names
10230acc635eSWarner Losh
10240acc635eSWarner Losh	More details can be found at
10250acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
10260acc635eSWarner Losh
10276e98a146SWarner Losh20001009:
10286e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
10296e98a146SWarner Losh	your entire ports tree, or you will have problems.
10306e98a146SWarner Losh
10316e98a146SWarner Losh20001006:
1032685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
10336e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
10346e98a146SWarner Losh	/usr/bin/miniperl.
10356e98a146SWarner Losh
1036073113a4SWarner Losh20001005:
1037073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1038685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1039073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1040073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1041073113a4SWarner Losh	tree for anything to work.
1042073113a4SWarner Losh
10430acc635eSWarner Losh20000928:
10440acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
10450acc635eSWarner Losh
1046be3885b3SWarner Losh20000916:
1047be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1048be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1049be3885b3SWarner Losh	same time as your kernel.
1050be3885b3SWarner Losh
105176ec9675SWarner Losh20000914:
105276ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
105376ec9675SWarner Losh	include the device will cause suspended laptops losing time
105476ec9675SWarner Losh	when they resume.  Include
105576ec9675SWarner Losh		device		pmtimer
105676ec9675SWarner Losh	in your config file and
105701b9a434SWarner Losh		hint.pmtimer.0.at="isa"
105876ec9675SWarner Losh	to your /boot/device.hints file.
105976ec9675SWarner Losh
1060f4865386SMark Murray20000911:
1061f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1062f4865386SMark Murray	rather than an option. The supplied kernel config files have
1063f4865386SMark Murray	been updated. You will need to do something similar in your
1064f4865386SMark Murray	own kernel config file.
1065f4865386SMark Murray	Remove:
1066f4865386SMark Murray		options		RANDOMDEV
1067f4865386SMark Murray	Add:
1068f4865386SMark Murray		device		random
1069f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1070f4865386SMark Murray	nothing.
1071f4865386SMark Murray
1072d594498fSWarner Losh20000909:
1073d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1074d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1075d594498fSWarner Losh	reflect this if you load this module at boot time.
1076d594498fSWarner Losh	The line should read:
1077d594498fSWarner Losh		random_load="YES"
1078d594498fSWarner Losh
10790deb7ddcSWarner Losh20000907:
10800deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
108116eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
108216eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
108316eb772dSWarner Losh	sure you don't have model loading problems which might at
108416eb772dSWarner Losh	first blush appear related to SMP.
108552bf24e7SWarner Losh
10865a01880bSWarner Losh20000906:
10875a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
10885a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
10895a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
10905a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
10915a01880bSWarner Losh	don't have one, and you have host.conf.
10925a01880bSWarner Losh
10932b41163cSWarner Losh20000905:
109438d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
109538d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
109638d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
109738d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
109838d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
109938d6ecd2SWarner Losh
110038d6ecd2SWarner Losh20000905:
11018aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
11028aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
11038aab4bc7SWarner Losh	is /boot/kernel.
11048aab4bc7SWarner Losh
11058aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
110638d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
110738d6ecd2SWarner Losh	installkernel/installworld dance.
11082b41163cSWarner Losh
1109d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1110d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1111d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1112d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1113d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1114d594498fSWarner Losh
1115d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1116d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1117d594498fSWarner Losh		chflags noschg /kernel.old
1118d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1119d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1120d594498fSWarner Losh	fi
1121d594498fSWarner Losh
1122c22a309cSWarner Losh20000904:
1123c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1124c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1125c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1126c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1127c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1128c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1129c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1130c22a309cSWarner Losh	is not likely to be generated.
1131c22a309cSWarner Losh
1132fdb9f54dSWarner Losh20000825:
1133fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
11349c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
11359c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
11369c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
11379c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
11389c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
11399c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
11409c1a7444SWarner Losh	kernel.
11419c1a7444SWarner Losh
11429c1a7444SWarner Losh20000821:
11439c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
11449c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
11459c1a7444SWarner Losh	/boot/loader.conf.
1146fdb9f54dSWarner Losh
11478f250aa7SWarner Losh20000812:
11485da0d091SWarner Losh	suidperl is now always built and installed on the system, but
11495da0d091SWarner Losh	with permissions of 511.  If you have applications that use
11505da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
11515da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
11525da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
11535da0d091SWarner Losh	will fix this until the next build.
11545da0d091SWarner Losh
11555da0d091SWarner Losh20000812:
11568f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
11578f250aa7SWarner Losh	visible changes that may immediately affect your configuration
11588f250aa7SWarner Losh	include:
11598f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
11608f250aa7SWarner Losh	- newaliases limited to root and trusted users
11618f250aa7SWarner Losh	- MSA port (587) turned on by default
11628f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
11638f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
11648f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
11658f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
11668f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
11678f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
11688f250aa7SWarner Losh
116971c38472SWarner Losh20000810:
117071c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
117171c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
117271c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
117371c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
117471c38472SWarner Losh	specific use for it.
117571c38472SWarner Losh
117671c38472SWarner Losh20000729:
117771c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
117871c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
117971c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
118071c38472SWarner Losh	afterwards (unless the variables already are set, of course):
118171c38472SWarner Losh		# Enable network daemons for user convenience.
118271c38472SWarner Losh		inetd_enable="YES"
118371c38472SWarner Losh		portmap_enable="YES"
118471c38472SWarner Losh		sendmail_enable="YES"
118571c38472SWarner Losh
118671c38472SWarner Losh20000728:
118771c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
118871c38472SWarner Losh	will need to change that to nullfs_load="YES".
118971c38472SWarner Losh
11901dece4a9SWarner Losh20000728:
11911dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
11921dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
11931dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
11941dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
11951dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
11961dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
11971dece4a9SWarner Losh	to /MYKERNEL.
11981dece4a9SWarner Losh
1199409e887cSWarner Losh20000711:
1200409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1201409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1202409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1203409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1204409e887cSWarner Losh	for details on potential problems that you might have and how
1205409e887cSWarner Losh	to get around them.
1206409e887cSWarner Losh
1207409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1208409e887cSWarner Losh	clauses above, you needn't worry.
1209409e887cSWarner Losh
1210409e887cSWarner Losh20000711:
1211409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1212409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1213409e887cSWarner Losh	in the number of changed programs the first time when you run
1214409e887cSWarner Losh	mergemaster to get a new /etc/security.
1215409e887cSWarner Losh
1216673d13f2SWarner Losh20000710:
1217673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1218673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1219673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1220673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1221673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1222673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1223673d13f2SWarner Losh	errors. (see below, 20000624).
1224673d13f2SWarner Losh
1225bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
12261dece4a9SWarner Losh
1227673d13f2SWarner Losh20000709:
1228c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1229c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1230c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1231673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1232673d13f2SWarner Losh
1233e98e26cdSWarner Losh20000706:
1234e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1235e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1236e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1237f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1238e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
12392c021c6cSMark Ovens	interim if needed.
1240e98e26cdSWarner Losh
1241e98e26cdSWarner Losh20000705:
1242e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1243e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1244e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1245e98e26cdSWarner Losh	details.
1246e98e26cdSWarner Losh
1247c373950eSWarner Losh20000704:
12482f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
12492f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
12502f961bc8SWarner Losh
12512f961bc8SWarner Losh20000704:
1252c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1253c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1254c373950eSWarner Losh	rc.d scripts that haven't been updated.
1255c373950eSWarner Losh
125627dc3a2bSWarner Losh20000630:
125727dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
125827dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
125927dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
126027dc3a2bSWarner Losh
1261b8c215acSWarner Losh20000625:
1262b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
126327dc3a2bSWarner Losh	system installed in order to build the system and kernel.
126427dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
126527dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
126627dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
126727dc3a2bSWarner Losh	were required.  You should check with the latest collections
126827dc3a2bSWarner Losh	to make sure that these haven't changed.
1269b8c215acSWarner Losh
12707b990719SWarner Losh20000624:
12717b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
12727b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
12737b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
12741a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
12757b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
12767b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
12777b990719SWarner Losh	date to the completion of the work.
12787b990719SWarner Losh
127927dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
128027dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
128127dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
128227dc3a2bSWarner Losh	recreate the random and urandom devices.
128327dc3a2bSWarner Losh
128481e54c50SWarner Losh20000622:
128581e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
128681e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
128781e54c50SWarner Losh	that used to be required when updating.
128881e54c50SWarner Losh
128939943833SWarner Losh20000621:
12902c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
12912a2f33fbSDaniel Baker	the config file update procedure.
12922a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1293c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
129459df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
129559df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
129639943833SWarner Losh
1297290f9ad8SWarner Losh20000620:
1298290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1299290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1300290f9ad8SWarner Losh	that workaround will no longer be required.
1301290f9ad8SWarner Losh
130290fb6346SWarner Losh20000615:
130390fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
130490fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
130590fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
130690fb6346SWarner Losh	devices.
130790fb6346SWarner Losh
1308f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1309f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1310f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1311f75f65bbSWarner Losh	may work).
1312f75f65bbSWarner Losh
1313ba26da8eSWarner Losh20000612:
1314ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1315290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1316c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1317290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1318f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1319f54a3542SWarner Losh	NEWCARD for examples of the new format.
1320290f9ad8SWarner Losh
13219698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
13229698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
13239698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
13249698f2c0SWarner Losh	in it.
1325bbcc5149SWarner Losh
1326d65850ebSWarner Losh20000522:
1327ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1328d65850ebSWarner Losh	building a kernel after this point is advised that they need
1329d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1330d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1331d65850ebSWarner Losh
1332d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1333d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1334d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1335d9583a00SWarner Losh	is resolved.
1336d9583a00SWarner Losh
13378039cedeSWarner Losh20000513:
13388039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
13398039cedeSWarner Losh
1340d65850ebSWarner Losh20000510:
13418039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
13428039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
13438039cedeSWarner Losh	is requires for the boot blocks to build properly.
13448039cedeSWarner Losh
13458039cedeSWarner Losh20000503:
13468039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
13478039cedeSWarner Losh	is now available.
13488039cedeSWarner Losh
1349d65850ebSWarner Losh20000502:
1350d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1351d65850ebSWarner Losh	connected to the kernel building instead.
1352d65850ebSWarner Losh
1353be149406SNik Clayton20000427:
13548039cedeSWarner Losh	You may need to build gperf
13558039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
13568039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
13578039cedeSWarner Losh	an option only in -current.
13588039cedeSWarner Losh
13592b8dd5f4SWarner Losh20000417:
13602b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1361f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
13622b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
13632b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
13642c021c6cSMark Ovens	before you reboot, you'll need to issue:
13652b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
13662b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
13672b8dd5f4SWarner Losh
13688d9f1945SWarner Losh20000320:
13692b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
13702b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
13712b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1372ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
13732b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
13748d9f1945SWarner Losh
1375f8ab1dd6SWarner Losh20000319:
1376f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1377f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1378f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1379f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1380f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1381f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1382f8ab1dd6SWarner Losh
138319cada77SWarner Losh20000318:
1384f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
138519cada77SWarner Losh	Large kernel changes are being committed and are in the
138619cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
138719cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
138819cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
138919cada77SWarner Losh	that you are loading are up to date.
1390ba228352SWarner Losh
139119cada77SWarner Losh20000315:
13926d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
13936d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
13946d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
13956d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
13966d23c382SWarner Losh	boot.
13976d23c382SWarner Losh
13986d23c382SWarner Losh20000315:
139919cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
140019cada77SWarner Losh	to upgrade to 4.0 from 3.x.
140157199806SWarner Losh
1402dc0dbf5cSWarner LoshCOMMON ITEMS:
1403dc0dbf5cSWarner Losh
1404a24eff53SWarner Losh	General Notes
1405a24eff53SWarner Losh	-------------
1406a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1407a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1408a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1409a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1410a24eff53SWarner Losh	or several minor releases, or when several months have passed
1411a24eff53SWarner Losh	on the -current branch).
1412a24eff53SWarner Losh
14135780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
14145780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
14155780f3baSWarner Losh	environment when searching for values for global variables.
14165780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
14175780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
14185780f3baSWarner Losh	page for more details.
14195780f3baSWarner Losh
1420dc0dbf5cSWarner Losh	To build a kernel
1421dc0dbf5cSWarner Losh	-----------------
1422ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1423f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1424ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1425282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1426282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1427dc0dbf5cSWarner Losh
1428ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1429ba01eb20SWarner Losh	--------------------------------------------------------------
14300fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
14310fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
14320fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
14330fbd2da9SKen Smith
14340fbd2da9SKen Smith	cd src/sys/${arch}/conf
143547d0d01fSWarner Losh	config KERNEL_NAME_HERE
14360fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1437ba01eb20SWarner Losh	make depend
1438ba01eb20SWarner Losh	make
1439ba01eb20SWarner Losh	make install
1440ba01eb20SWarner Losh
1441ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1442ba01eb20SWarner Losh
1443ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1444ba01eb20SWarner Losh	-----------------------------------------------------------
144563cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
144663cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
144763cb445eSWarner Losh
1448f643de42SWarner Losh	<make sure you have good level 0 dumps>
144963cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
145063cb445eSWarner Losh	make buildworld
145163cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
145263cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
145363cb445eSWarner Losh							[1]
145463cb445eSWarner Losh	<reboot in single user>				[3]
14558633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
145663cb445eSWarner Losh	mergemaster -p					[5]
145763cb445eSWarner Losh	make installworld
145863cb445eSWarner Losh	mergemaster					[4]
145963cb445eSWarner Losh	<reboot>
146063cb445eSWarner Losh
1461759f0aefSWarner Losh
1462f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1463f27b1fceSJoseph Koshy	--------------------------------------------------
1464f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1465f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1466f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1467f27b1fceSJoseph Koshy	# size.
1468f27b1fceSJoseph Koshy
1469f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1470f27b1fceSJoseph Koshy	<boot into -stable>
1471f27b1fceSJoseph Koshy	make buildworld
1472f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1473f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1474f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1475f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1476f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1477f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1478f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1479f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1480f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1481f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1482f27b1fceSJoseph Koshy	<reboot into current>
1483f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1484f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1485f27b1fceSJoseph Koshy 	<reboot>
1486f27b1fceSJoseph Koshy
1487f27b1fceSJoseph Koshy
1488f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1489f27b1fceSJoseph Koshy	----------------------------------------------
14905c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
14915c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
14925c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
14935c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1494ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1495f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1496f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1497f643de42SWarner Losh	# space on /.
1498f643de42SWarner Losh
1499f643de42SWarner Losh	<make sure you have good level 0 dumps>
1500fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
150121c075eaSWarner Losh	make buildworld					[9]
1502c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1503d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1504be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1505fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1506fc8c157fSWarner Losh							[1]
1507fc8c157fSWarner Losh	<reboot in single user>				[3]
15088633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
1509835284beSWarner Losh	mergemaster -p					[5]
1510f8a4c901SWarner Losh	rm -rf /usr/include/g++
1511ba26da8eSWarner Losh	make installworld
1512a6cd4f9dSWarner Losh	mergemaster					[4]
1513ba26da8eSWarner Losh	<reboot>
1514ba26da8eSWarner Losh
1515fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1516fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1517fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1518fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1519fdb9f54dSWarner Losh	the UPDATING entries.
1520ba26da8eSWarner Losh
15211dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
15221dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
15231dece4a9SWarner Losh	your sources that you have read and understood all the recent
15241dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
15251dece4a9SWarner Losh	much fewer pitfalls.
15261dece4a9SWarner Losh
1527134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1528134d2e86SWarner Losh	should disable them at this point so they don't crash your
1529134d2e86SWarner Losh	system on reboot.
1530134d2e86SWarner Losh
15319c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
15329c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
15339c1a7444SWarner Losh	configuration.
15349c1a7444SWarner Losh
1535ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1536ee6e1fc3SWarner Losh		fsck -p
1537ee6e1fc3SWarner Losh		mount -u /
1538ee6e1fc3SWarner Losh		mount -a
1539ee6e1fc3SWarner Losh		cd /usr/src
154047d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1541f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1542f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1543b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1544b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1545b705ae10SWarner Losh	be ignored while you proceed to the next step.
1546ee6e1fc3SWarner Losh
1547a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1548a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1549a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1550a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1551a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1552a6cd4f9dSWarner Losh	for potential gotchas.
1553a6cd4f9dSWarner Losh
1554835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1555835284beSWarner Losh	you may need to do this if you get unknown user in the following
1556835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1557835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1558835284beSWarner Losh	install) after the buildworld before this step if you last updated
1559835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1560835284beSWarner Losh
1561bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1562bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1563bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1564bd79cf40SWarner Losh		ok unload
1565bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1566bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1567bd79cf40SWarner Losh	described here.
1568fc8c157fSWarner Losh
1569fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1570fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1571fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1572fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1573fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1574fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1575fc8c157fSWarner Losh
1576c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1577c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1578c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1579c74fe6afSWarner Losh	that is hard to boot to recover.
1580c74fe6afSWarner Losh
158121c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
158221c075eaSWarner Losh	cvs prune empty directories.
15838633bbeaSBrooks Davis
15848633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
15858633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
15868633bbeaSBrooks Davis	takes care of this.
1587dc0dbf5cSWarner LoshFORMAT:
1588dc0dbf5cSWarner Losh
1589f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
15901fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1591f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1592f8ab1dd6SWarner Loshprevious releases if your system is older than this.
15931fc1a0dcSWarner Losh
1594e72fd46aSWarner LoshCopyright information:
1595e72fd46aSWarner Losh
15969698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1597e72fd46aSWarner Losh
1598772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1599772730c7SWarner Loshmodification, in full or in part, in any form or format of this
16009698f2c0SWarner Loshdocument are permitted without further permission from the author.
1601e72fd46aSWarner Losh
1602e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1603e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1604e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1605e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1606e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1607e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1608e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1609e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1610e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1611e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1612e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1613e72fd46aSWarner Losh
1614e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1615e72fd46aSWarner Loshauthor a beer.
1616e72fd46aSWarner Losh
161722306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1618772730c7SWarner Loshthis document.
1619772730c7SWarner Losh
162097d92980SPeter Wemm$FreeBSD$
1621