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 72c724730SWarner LoshItems affecting the ports and packages system can be found in 82c724730SWarner Losh/usr/ports/UPDATING. Please read that file before running 92c724730SWarner Loshportupgrade. Important recent entries: 20040724 (default X changes). 102c724730SWarner Losh 11f692e7ecSWarner Losh[[ The UPDATING file will be trimmed to 20040814 on or about Oct 1, 2004 ]] 12f692e7ecSWarner Losh 13f692e7ecSWarner LoshNOTE TO PEOPLE WHO THINK THAT FreeBSD 6.x IS SLOW: 14f692e7ecSWarner Losh FreeBSD 6.x has many debugging features turned on, in 1569f7bcf3SWarner Losh both the kernel and userland. These features attempt to detect 1669f7bcf3SWarner Losh incorrect use of system primitives, and encourage loud failure 1769f7bcf3SWarner Losh through extra sanity checking and fail stop semantics. They 1869f7bcf3SWarner Losh also substantially impact system performance. If you want to 1969f7bcf3SWarner Losh do performance measurement, benchmarking, and optimization, 2069f7bcf3SWarner Losh you'll want to turn them off. This includes various WITNESS- 2169f7bcf3SWarner Losh related kernel options, INVARIANTS, malloc debugging flags 2269f7bcf3SWarner Losh in userland, and various verbose features in the kernel. Many 2369f7bcf3SWarner Losh developers choose to disable these features on build machines 24a19f8ddaSDavid E. O'Brien to maximize performance. 25c1f61aa9SDavid E. O'Brien 261fc4519bSBrooks Davis20040830: 271fc4519bSBrooks Davis A new variable, ifi_epoch, has been added to struct if_data 281fc4519bSBrooks Davis which is part if struct ifnet. This means all network drivers 291fc4519bSBrooks Davis and network monitoring applications need to be recompiled. 301fc4519bSBrooks Davis 31c1c94d5cSRobert Watson20040828: 32c1c94d5cSRobert Watson The default configuration for the network stack has been changed 33c1c94d5cSRobert Watson such that it now runs without the Giant lock unless configured 34c1c94d5cSRobert Watson otherwise. If you experience network-related instability, you 35c1c94d5cSRobert Watson may wish to try setting "debug.mpsafenet=0" or compiling the 36c1c94d5cSRobert Watson kernel with "options NET_WITH_GIANT". Details on the netperf 37c1c94d5cSRobert Watson project may be found at: 38c1c94d5cSRobert Watson 39c1c94d5cSRobert Watson http://www.watson.org/~robert/freebsd/netperf/ 40c1c94d5cSRobert Watson 41c1c94d5cSRobert Watson Including the 20040828 announcement of configuration change 42c1c94d5cSRobert Watson details. 43c1c94d5cSRobert Watson 44c21fd232SAndre Oppermann20040827: 45c21fd232SAndre Oppermann PFIL_HOOKS are a fixed part of the network stack now and do not 46c21fd232SAndre Oppermann need to be specified in the kernel configuration file anymore. 47c21fd232SAndre Oppermann 48f036d408SJulian Elischer20040819: 49f036d408SJulian Elischer Netgraph changed its message format slightly to align the data 50f036d408SJulian Elischer portion well on 64 bit machines. 51f036d408SJulian Elischer Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd, 52f036d408SJulian Elischer pppoed, bluetooth, ATM) should be recompiled when a new kernel 53f036d408SJulian Elischer is installed. 54f036d408SJulian Elischer 55b067abfaSAndre Oppermann20040817: 560ce70eb4SAndre Oppermann IPFW has been converted to use PFIL_HOOKS. This change is 57b067abfaSAndre Oppermann transparent to userland and preserves the ipfw ABI. The ipfw 58b067abfaSAndre Oppermann core packet inspection and filtering functions have not been 59b067abfaSAndre Oppermann changed, only how ipfw is invoked is different. Note that 60b067abfaSAndre Oppermann "option PFIL_HOOKS" is required to use IPFIREWALL compiled 61b067abfaSAndre Oppermann into the kernel or as KLD. 62b067abfaSAndre Oppermann 63f13a7951SDavid Malone20040814: 64f13a7951SDavid Malone The RANDOM_IP_ID option has been replaced by the sysctl 65f13a7951SDavid Malone net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then 66f13a7951SDavid Malone you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf. 67f13a7951SDavid Malone 683a004637SMax Laier20040807: 693a004637SMax Laier The size of 'struct ifnet' has changed due to the addition of the 703a004637SMax Laier if_carp placeholder. All kernel modules implementing network 713a004637SMax Laier interfaces must be recompiled as a result. 723a004637SMax Laier 734f34d8d1SJohn-Mark Gurney20040806: 744f34d8d1SJohn-Mark Gurney Module loading has been fixed. Some older installations will 75ac41c814SRuslan Ermilov drop proper module_path initialization and modules will fail to 764f34d8d1SJohn-Mark Gurney load properly. If you have a line in /boot/loader.rc that says: 774f34d8d1SJohn-Mark Gurney "initialize drop", do (i386 only): 784f34d8d1SJohn-Mark Gurney cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc 794f34d8d1SJohn-Mark Gurney chown root:wheel /boot/loader.rc 804f34d8d1SJohn-Mark Gurney chmod 444 /boot/loader.rc 814f34d8d1SJohn-Mark Gurney 828f075db4SMark Murray20040802: 838f075db4SMark Murray making /dev/(null|zero) into a module proved to be too unpopular, 848f075db4SMark Murray so this bit has been revoked from the previous (20040801) entry. 858f075db4SMark Murray 86d064d6dbSMark Murray20040801: 87d064d6dbSMark Murray The /dev/mem, /dev/io /dev/(null/zero) devices are now modules, 88d064d6dbSMark Murray so you may wish to add them to your kernel config file. See 89d064d6dbSMark Murray GENERIC for examples. 90d064d6dbSMark Murray 91b289983eSAlexander Kabaev20040728: 9254bd5271SAlexander Kabaev System compiler has been upgraded to GCC 3.4.2-pre. As with any major 9354bd5271SAlexander Kabaev compiler upgrade, there are several issues to be aware of. GCC 3.4.x 9454bd5271SAlexander Kabaev has broken C++ ABI compatibility with previous releases yet again 9554bd5271SAlexander Kabaev and users will have to rebuild all their C++ programs with the new 96d0e54ab4SDavid E. O'Brien compiler. If you are getting run-time error such as 97d0e54ab4SDavid E. O'Brien /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE" 98d0e54ab4SDavid E. O'Brien This entry does apply to you. 99d0e54ab4SDavid E. O'Brien 100d0e54ab4SDavid E. O'Brien A new unit-at-a-time optimization mode, which is default in this 101d0e54ab4SDavid E. O'Brien compiler release, is more aggressive in removing unused static 102d0e54ab4SDavid E. O'Brien symbols. This is the likely cause of 'make buildworld' breakages 103cd5f061cSWarner Losh with non-default CFLAGS where optimization level is set to -O2 104cd5f061cSWarner Losh or higher. 10554bd5271SAlexander Kabaev 1066e1afae3SWarner Losh With the upgrade of the system compiler, the kernel has been upgraded 1076e1afae3SWarner Losh to match the new system compiler. This makes it impossible to build 1086e1afae3SWarner Losh a new kernel with the old compiler. Upgrade your system via 1096e1afae3SWarner Losh make buildworld and make kernel (see below) to fix this problem. 1106e1afae3SWarner Losh 11136ed21e6SRobert Watson20040727: 11236ed21e6SRobert Watson The size of 'struct ifnet' has changed due to the addition of 11336ed21e6SRobert Watson the IFF_NEEDSGIANT flag (and what it implies). All kernel 11436ed21e6SRobert Watson modules implementing network interfaces must be recompiled as 11536ed21e6SRobert Watson a result. 11636ed21e6SRobert Watson 1176305ac24SSeigo Tanimura20040716: 1186305ac24SSeigo Tanimura The sound device drivers are renamed. `sound' is always required, 1196305ac24SSeigo Tanimura while `snd_*' should be configured accordingly to your hardware. 1206305ac24SSeigo Tanimura Refer to NOTES for the detail of the drivers. 1216305ac24SSeigo Tanimura 122e623dcb7SMarcel Moolenaar20040710: 123e623dcb7SMarcel Moolenaar __FreeBSD_version bumped to 502122. 124e623dcb7SMarcel Moolenaar 125e623dcb7SMarcel Moolenaar20040710: 126e623dcb7SMarcel Moolenaar The console initialization on Alpha has been reworked and is now 127e623dcb7SMarcel Moolenaar identical to other platforms. This means that the hardcoding of 128e623dcb7SMarcel Moolenaar the serial console and the debug port has been removed. As such, 129e623dcb7SMarcel Moolenaar hints are now required for the sio(4) driver to become a console 130e623dcb7SMarcel Moolenaar or debug port. The NO_SIO option has been decommissioned because 131e623dcb7SMarcel Moolenaar of this. 132e623dcb7SMarcel Moolenaar 133e623dcb7SMarcel Moolenaar20040710: 134e623dcb7SMarcel Moolenaar A revamp of the debugging code in the kernel with some visible 135e623dcb7SMarcel Moolenaar changes beyond just the debugging experience: 136e623dcb7SMarcel Moolenaar o The DDB option is now specific to the DDB debugger backend 137e623dcb7SMarcel Moolenaar and should not be used any more for conditional compilation 138e623dcb7SMarcel Moolenaar of debugging code for when debugging is enabled. Use the KDB 139e623dcb7SMarcel Moolenaar option for this. 140e623dcb7SMarcel Moolenaar o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have 141e623dcb7SMarcel Moolenaar been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED 142e623dcb7SMarcel Moolenaar respectively. This is in line with the first bullet. 143e623dcb7SMarcel Moolenaar o The remote GDB support has been untangled from DDB and needs 1445bd7ce0aSJens Schweikhardt to be enabled separately now. Use the GDB option for this. 145e623dcb7SMarcel Moolenaar o The GDB_REMOTE_CHAT option has been removed. Support for this 146e623dcb7SMarcel Moolenaar homegrown feature is discontinued. The GDB remote protocol 147e623dcb7SMarcel Moolenaar supports console output and it makes sense to use that. 148e623dcb7SMarcel Moolenaar o The DDB_NOKLDSYM option has been removed. The DDB debugger 149e623dcb7SMarcel Moolenaar now supports both direct symbol table lookups as well as KLD 150e623dcb7SMarcel Moolenaar symbol lookups through the linker. 151e623dcb7SMarcel Moolenaar 1526421d1dbSMaksim Yevmenkin20040708: 1536421d1dbSMaksim Yevmenkin Bluetooth code has been marked as non-i386 specific. 1546421d1dbSMaksim Yevmenkin __FreeBSD_version has been bumped to 502121 to mark this change. 1556421d1dbSMaksim Yevmenkin 15658af3216SWarner Losh20040702: 15758af3216SWarner Losh The native preemption has been added to the kernel scheduler. 1585bd7ce0aSJens Schweikhardt There is some report that the ULE scheduler was broken in some 1595bd7ce0aSJens Schweikhardt machines and we encourage users using the ULE scheduler either 1605bd7ce0aSJens Schweikhardt stick with a known good kernel, or temporarily switch to the 4BSD 16158af3216SWarner Losh scheduler as a workaround. 16258af3216SWarner Losh 163c2dba668SNate Lawson20040630: 1648ed370fdSJulian Elischer The netgraph ABI version number has been incremented to indicate 1658ed370fdSJulian Elischer an incompatible change in the ABI. Old netgraph nodes will refuse 166a6c26e1cSBruce M Simpson to attach until recompiled. Netgraph now uses mbuf tags to move 167a6c26e1cSBruce M Simpson metadata and this commit removes its home-grown metadata facility. 168a6c26e1cSBruce M Simpson Nodes should just recompile, unless they use metadata, in which 169a6c26e1cSBruce M Simpson case the changes are simple; the file ng_ksocket.c serves as an 170a6c26e1cSBruce M Simpson example of such changes. 1718ed370fdSJulian Elischer 17258af3216SWarner Losh This also broke i4b, although the compile problem has been papered 17358af3216SWarner Losh over. 17458af3216SWarner Losh 1758ed370fdSJulian Elischer20040630: 176c2dba668SNate Lawson ACPI has been updated to disable known-bad BIOS revisions. A message 1775bd7ce0aSJens Schweikhardt will be printed on the console indicating that ACPI has been disabled 178c2dba668SNate Lawson automatically and that the user should use a newer BIOS, if possible. 179c2dba668SNate Lawson If you think ACPI does work on your system and want to override 180c2dba668SNate Lawson this (i.e., for testing), set hint.acpi.0.disabled="0" at the 181c2dba668SNate Lawson loader prompt. 182c2dba668SNate Lawson 1838ee2ac9eSMax Laier20040623: 1845bd7ce0aSJens Schweikhardt pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege 1858ee2ac9eSMax Laier separated now. It uses the newly created "_pflogd" user/group 1868ee2ac9eSMax Laier combination. If you plan to use pflogd(8) make sure to run 1878ee2ac9eSMax Laier mergemaster -p or install the "_pflogd" user and group manually. 1888ee2ac9eSMax Laier 1893db5687dSBrooks Davis20040622: 1903db5687dSBrooks Davis Network interface cloning has been overhauled. This change will 1913db5687dSBrooks Davis require a recompile of modules using cloning and modification of 1923db5687dSBrooks Davis external ones to the new API. __FreeBSD_version has been bumped 1933db5687dSBrooks Davis to 502119 to mark this change. Additionally, users creating 1943db5687dSBrooks Davis stf(4) interfaces via "ifconfig stf" will need to update their 1953db5687dSBrooks Davis scripts as this will create an interface named "stf" instead of 1963db5687dSBrooks Davis "stf0" and ifconfig will not print "stf0" to stdout. 1973db5687dSBrooks Davis 198e0ae81f3SDag-Erling Smørgrav20040621: 199e0ae81f3SDag-Erling Smørgrav On 20040524, the /etc/rc.d/nsswitch script was modified to 200e0ae81f3SDag-Erling Smørgrav automatically create /etc/nsswitch.conf on startup if it did 201e0ae81f3SDag-Erling Smørgrav not already exist. Unfortunately, an error in the man page 202e0ae81f3SDag-Erling Smørgrav was carried over to the script, resulting in incorrect 203e0ae81f3SDag-Erling Smørgrav nsswitch settings. The simplest remedy is to remove both 204e0ae81f3SDag-Erling Smørgrav /etc/nsswitch.conf and /etc/host.conf; they will be recreated 205e0ae81f3SDag-Erling Smørgrav during the next reboot. 206e0ae81f3SDag-Erling Smørgrav 2074717d22aSJohn Polstra20040614: 2084717d22aSJohn Polstra The return value of sema_timedwait(9) has been changed to 2094717d22aSJohn Polstra make it consistent with cv_timedwait(9). Be sure to recompile 2104717d22aSJohn Polstra the ips module and any third-party modules which call 2114717d22aSJohn Polstra sema_timedwait. 2124717d22aSJohn Polstra 2136cb7a382SMax Laier20040613: 2146cb7a382SMax Laier ALTQ is now linked to the build. This breaks ABI for struct ifnet. 2156cb7a382SMax Laier Make sure to recompile modules and any userland that makes use of 216df843493SMax Laier sizeof(struct ifnet). In order to get the altq headers in place 217df843493SMax Laier please recompile and reinstall world. 2186cb7a382SMax Laier 2192454685eSJulian Elischer20040607: 2202454685eSJulian Elischer Splitting kern_thread.c into 2 files (adding kern_kse.c) 2212454685eSJulian Elischer requires that you re-run config after updating your tree. 2222454685eSJulian Elischer 22364fef830SSeigo Tanimura20040601: 22464fef830SSeigo Tanimura The MIDI drivers have been removed. Until the new module-friendly 22564fef830SSeigo Tanimura ones are merged, remove or comment out midi and seq from your 22664fef830SSeigo Tanimura kernel configuration. 22764fef830SSeigo Tanimura 228bb4f06e7SAndre Oppermann20040423: 229bb4f06e7SAndre Oppermann Due to a new option in ipfw (versrcreach) the ipfw(8) command 230bb4f06e7SAndre Oppermann needs to be recompiled. Normal accept/reject rules without 231bb4f06e7SAndre Oppermann options are not affected but those with options may break until 232bb4f06e7SAndre Oppermann ipfw(8) is recompiled. 233bb4f06e7SAndre Oppermann 23405641e82SColin Percival20040420: 23505641e82SColin Percival Due to changes in the callout ABI, kernels compiled after this 23605641e82SColin Percival date may be incompatible with kernel modules compiled prior to 23705641e82SColin Percival 20040406. 23805641e82SColin Percival 239d0dc9183SWarner Losh20040414: 240d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 241d0dc9183SWarner Losh problems for your system, please disable it using the tunable 242d0dc9183SWarner Losh hw.pci.do_powerstate=0. 243d0dc9183SWarner Losh 244d0dc9183SWarner Losh20040412: 245d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 246d0dc9183SWarner Losh drive is still broken. 247d0dc9183SWarner Losh 248d0dc9183SWarner Losh20040410: 249d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 250d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 251d0dc9183SWarner Losh the unanticipated problems have been resolved. 252d0dc9183SWarner Losh 2538633bbeaSBrooks Davis20040409: 2548633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 2558633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 2568633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 2578633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 25876c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 2598633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 2608633bbeaSBrooks Davis 261d40d033aSRobert Watson20040322: 262d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 263d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 264d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 265d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 266d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 267d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 268d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 269d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 270d40d033aSRobert Watson locking is merged to permit this to take place. 271d40d033aSRobert Watson 272ec9b318eSGarance A Drosehn20040310: 273ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 274ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 275ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 276ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 277ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 278ec9b318eSGarance A Drosehn 279fc28f1ffSMax Laier20040308: 280fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 281fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 2824c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 2834c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 284fc28f1ffSMax Laier Also note that pf requires "options PFIL_HOOKS" in the kernel. The 285fc28f1ffSMax Laier pf system consists of the following three devices: 286fc28f1ffSMax Laier device pf # required 287fc28f1ffSMax Laier device pflog # optional 288fc28f1ffSMax Laier device pfsync # optional 289fc28f1ffSMax Laier 2903aff5d06SDag-Erling Smørgrav20040303: 2913aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 2923aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 2933aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 2943aff5d06SDag-Erling Smørgrav 2953aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 2963aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 2973aff5d06SDag-Erling Smørgrav 2983aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 2993aff5d06SDag-Erling Smørgrav to use libpthread instead. 3003aff5d06SDag-Erling Smørgrav 301fd63c5b3SDag-Erling Smørgrav20040226: 3029d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 303fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 304fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 305fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 306fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 307fd63c5b3SDag-Erling Smørgrav 308714ae42aSBruce M Simpson20040225: 309e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 310e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 311e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 312e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 313e07a40f3SBrian Feldman should remain unaffected. 314e07a40f3SBrian Feldman 315e07a40f3SBrian Feldman20040225: 316714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 317714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 318714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 319714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 320714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 321714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 322714ae42aSBruce M Simpson 323fbd2e692SAndre Oppermann20040224: 324fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 3255bd7ce0aSJens Schweikhardt and related userland network utilities necessary. 326fbd2e692SAndre Oppermann 327158b90daSWarner Losh20040222: 328158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 329158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 330158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 331158b90daSWarner Losh Drivers outside the tree will need to be updated. 332158b90daSWarner Losh 333b7b1e150SMike Makonnen20040207: 334b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 335b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 336b7b1e150SMike Makonnen 337aca89ee6SDaniel Eischen20040130: 338aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 339aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 340aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 341aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 342aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 343aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 344aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 345aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 346aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 347aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 348aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 349aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 350aca89ee6SDaniel Eischen do not work with libpthread. 351aca89ee6SDaniel Eischen 35268b7b3a9SAlex Dupre20040125: 35368b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 35468b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 35568b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 35668b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 35768b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 35868b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 35968b7b3a9SAlex Dupre 360ff46e0deSWarner Losh20040125: 361ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 362ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 363ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 364ff46e0deSWarner Losh 365ce41f4bfSRobert Watson20031213: 366ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 367ce41f4bfSRobert Watson if the login process is unable to successfully set the 368ce41f4bfSRobert Watson process credentials to include all groups defined for the 369ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 370ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 371ce41f4bfSRobert Watson defined, or they will be unable to log in. 372ce41f4bfSRobert Watson 373c124fa05SJohn Baldwin20031203: 374c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 375c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 376c124fa05SJohn Baldwin 3778ad1f5e4SHartmut Brandt20031112: 37830093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 37930093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 38097209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 38197209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 38297209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 38397209ca3SRobert Watson not know about the new system calls that support the new statfs 3843f631d52SMarcel Moolenaar structure. 3853f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 3863f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 3873f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 3883f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 3893f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 3903f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 3913f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 3923f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 3933f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 3943f631d52SMarcel Moolenaar these changes are installed. 39530093b05SWarner Losh 39630093b05SWarner Losh ****************************DANGER******************************* 39730093b05SWarner Losh 39830093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 39930093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 40030093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 40130093b05SWarner Losh kernel. 40264a18d6fSKirk McKusick 40364a18d6fSKirk McKusick20031112: 4048ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 4058ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 4068ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 4078ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 4088ad1f5e4SHartmut Brandt sync before rebooting. 4098ad1f5e4SHartmut Brandt 410c53a5d8fSJohn Baldwin20031111: 411c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 412c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 413c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 414c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 415c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 416c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 417c53a5d8fSJohn Baldwin 4188bf455a5SJohn Baldwin20031103: 4198bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 4208bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 4212a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 4228bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 4238bf455a5SJohn Baldwin 4249bf40edeSBrooks Davis20031031: 4259bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 4269bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 4279bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 4289bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 4299bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 4309bf40edeSBrooks Davis reflect this change. 4319bf40edeSBrooks Davis 43247a42c7aSPoul-Henning Kamp20030928: 43347a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 43447a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 4355bd7ce0aSJens Schweikhardt __FreeBSD_version bumped to 501110. 43647a42c7aSPoul-Henning Kamp 43707105342SMax Khon20030926: 43807105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 43907105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 44007105342SMax Khon 44117dcd026SSam Leffler20030925: 44217dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 44317dcd026SSam Leffler also be explicitly configured. Previously this dependency was 44417dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 44517dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 44617dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 44717dcd026SSam Leffler 448fedf1d01SBruce M Simpson20030923: 449fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 450fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 451fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 452fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 453fedf1d01SBruce M Simpson 454db38f9cbSJacques Vidrine20030915: 455db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 456db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 457db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 458db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 459db38f9cbSJacques Vidrine 460c09d2c2bSMike Makonnen20030829: 461c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 462c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 463c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 464c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 465c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 466c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 467c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 468c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 469c09d2c2bSMike Makonnen may or may not exist on your system. 470c09d2c2bSMike Makonnen 47117c159dcSSøren Schmidt20030824: 47217c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 47317c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 474f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 475f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 47617c159dcSSøren Schmidt 477c1f61aa9SDavid E. O'Brien20030819: 478c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 479c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 480c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 481c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 48269f7bcf3SWarner Losh 48338c962e7SNate Lawson20030728: 48438c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 48538c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 48638c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 48738c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 48838c962e7SNate Lawson so the quirk can be re-enabled. 48938c962e7SNate Lawson 49074111097SWarner Losh20030724: 49174111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 49274111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 49374111097SWarner Losh 494178cf4e9SWarner Losh20030722: 495178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 496178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 497178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 498178cf4e9SWarner Losh FPU hardware. 499178cf4e9SWarner Losh 500178cf4e9SWarner Losh20030714: 501178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 502178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 503178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 504178cf4e9SWarner Losh People should report those issues to current@. 505178cf4e9SWarner Losh 506157c629aSWarner Losh20030711: 507157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 5088b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 50905538fa9SWarner Losh /usr/obj. 510157c629aSWarner Losh 51174111097SWarner Losh20030610: 51274111097SWarner Losh Remove deprecated locale names and transition period code 51374111097SWarner Losh for them, finishing switching to the new scheme. Check your 51474111097SWarner Losh LANG environment variable. 51574111097SWarner Losh 51674111097SWarner Losh20030609: 51774111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 51874111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 51974111097SWarner Losh important to remember beforehand if your source tree is on 52074111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 52174111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 52274111097SWarner Losh kernel. 52374111097SWarner Losh 52474111097SWarner Losh20030605: 5256cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 5266cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 5276cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 5286cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 5296cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 5306cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 5316cc6353fSMarcel Moolenaar 5326cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 5336cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 5346cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 5356cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 5366cc6353fSMarcel Moolenaar : 5376cc6353fSMarcel Moolenaar 5386cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 5396cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 5406cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 5416cc6353fSMarcel Moolenaar 54252b47445SMark Murray20030505: 54352b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 54452b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 54552b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 54652b47445SMark Murray 547a26df538SWarner Losh20030502: 548a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 549a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 550a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 551a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 552a26df538SWarner Losh 5534b065e2cSDoug Barton20030501: 5544b065e2cSDoug Barton The old rc system has been removed. Please report any problems 5554b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 5564b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 5574b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 5584b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 5594b065e2cSDoug Barton utilizes these old scripts has also been removed. 5604b065e2cSDoug Barton 56181cda3d9SWarner Losh20030423: 56281cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 56381cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 56481cda3d9SWarner Losh work around in devd will be removed around 20030507. You 56581cda3d9SWarner Losh have until then to upgrade your kernel before updating 56681cda3d9SWarner Losh userland. In general, you should have a userland and 56781cda3d9SWarner Losh kernel that's in sync with each other. However, given the 56881cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 56981cda3d9SWarner Losh allowances are made. 57081cda3d9SWarner Losh 57147a657d1SRuslan Ermilov20030329: 57247a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 57347a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 57447a657d1SRuslan Ermilov while upgrading the system through a buildworld. 57547a657d1SRuslan Ermilov 57647a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 57747a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 57847a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 57947a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 58047a657d1SRuslan Ermilov 58147a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 58247a657d1SRuslan Ermilov make cleandir && make obj && \ 58347a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 58447a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 58547a657d1SRuslan Ermilov 5865d2af00cSGregory Neil Shapiro20030208: 5875d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 5885d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 5895d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 5905d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 5915d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 5925d2af00cSGregory Neil Shapiro 5935d2af00cSGregory Neil Shapiro20030128: 5949db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 595ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 5969db58771SPoul-Henning Kamp be removed when convenient. 5979db58771SPoul-Henning Kamp 5988d9b3f57SJake Burkholder20030126: 5998d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 6008d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 6018d9b3f57SJake Burkholder 6021c5efda5SJeff Roberson20030125: 6031c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 6041c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 605ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 6061c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 6071c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 6081c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 6091c5efda5SJeff Roberson 6109d1d64f5SWarner Losh20030115: 6119d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 6129d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 6139d1d64f5SWarner Losh properly. 6149d1d64f5SWarner Losh 615c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 616c9fdb80aSWarner Losh configured for point to point links to bring it more in line 617c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 618c9fdb80aSWarner Losh with NetBSD. 619c9fdb80aSWarner Losh 620161dc364SAlexander Kabaev20021222: 621161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 622161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 623161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 624161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 625161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 626161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 62784cc83efSAlexander Kabaev rebuilt. 628161dc364SAlexander Kabaev 629fb4c8061SMartin Blapp20021216: 630fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 63189056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 632fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 6339d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 634fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 635fb4c8061SMartin Blapp 63617d47eb3SGiorgos Keramidas20021202: 63717d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 63817d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 63917d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 64017d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 64117d47eb3SGiorgos Keramidas 642a4459294SBill Fenner20021029: 643a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 644a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 645a4459294SBill Fenner consumers in sync. 646a4459294SBill Fenner 647fc8c157fSWarner Losh20021024: 648c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 649c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 650c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 651c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 652c57404feSRuslan Ermilov partition really is on. The old device names have gone 653c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 654c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 655c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 65669f7bcf3SWarner Losh 657fd9e8bdaSAndrew Gallatin20021023: 658fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 659fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 660fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 661fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 662fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 663fd9e8bdaSAndrew Gallatin 664fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 665fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 666fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 667fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 668fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 669fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 670fd9e8bdaSAndrew Gallatin 671f8a4c901SWarner Losh20020831: 672f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 673f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 674f8a4c901SWarner Losh programs and libraries need to be recompiled. 675f8a4c901SWarner Losh 676f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 677f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 678f8a4c901SWarner Losh 679c2248fa2SJens Schweikhardt20020827: 680c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 681c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 682c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 683c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 684c2248fa2SJens Schweikhardt 6850d533e43SRuslan Ermilov20020815: 6860d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 6870d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 6880d533e43SRuslan Ermilov again. 6890d533e43SRuslan Ermilov 69033c1de7dSRuslan Ermilov20020729: 69133c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 69233c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 69333c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 69433c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 69533c1de7dSRuslan Ermilov 6962b877facSJulian Elischer20020702: 6972b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 6982b877facSJulian Elischer There are still some minor problems with some signals but the 6992b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 7002b877facSJulian Elischer but each can successfully complete multiple buildworlds. 7012b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 7022b877facSJulian Elischer 70306596d37SWarner Losh20020701: 70406596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 70506596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 70606596d37SWarner Losh GNOME. 70706596d37SWarner Losh 70895ba4330SJacques Vidrine20020511: 70995ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 71095ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 71195ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 71295ba4330SJacques Vidrine with the set-user-ID bit set. 71395ba4330SJacques Vidrine 714a81da3c9SDavid E. O'Brien20020510: 715f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 716f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 7174b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 718f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 719f50caf6fSDavid E. O'Brien 720f50caf6fSDavid E. O'Brien20020510: 721a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 722a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 723a81da3c9SDavid E. O'Brien and then do a cvs update. 724a81da3c9SDavid E. O'Brien 725528a0ef5SJacques Vidrine20020421: 726528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 727528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 728528a0ef5SJacques Vidrine 72985aa5a2eSGregory Neil Shapiro20020404: 73085aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 73185aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 73285aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 73385aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 73485aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 73585aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 73685aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 73785aa5a2eSGregory Neil Shapiro 7388f1e4358SRuslan Ermilov20020403: 7398f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 7408f1e4358SRuslan Ermilov 7412292c02eSWarner Losh20020315: 7422292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 7432292c02eSWarner Losh 74469f7bcf3SWarner Losh20020225: 74569f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 74669f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 74769f7bcf3SWarner Losh 7488f35c493SWarner Losh20020217: 7498f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 7508f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 7518f35c493SWarner Losh command line mail submission has changed. Be sure to run 7528f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 7538f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 7548f35c493SWarner Losh 755835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 756835284beSWarner Losh required in order for sendmail to run as a set-group-ID 757835284beSWarner Losh binary. A 'make installworld' will use the new user and group 758835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 759835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 760835284beSWarner Losh and group must be merged from src/etc/group and 761835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 762835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 763835284beSWarner Losh mergemaster before this will work if you are updating from a 764835284beSWarner Losh very old version of current. The updating recipe has changed 765835284beSWarner Losh as of this date. 766835284beSWarner Losh 767fa9401c1SWarner Losh20020112: 768fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 769fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 770fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 771fa9401c1SWarner Losh you have local modifications, you can use 772fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 773fa9401c1SWarner Losh /etc/pam.d. 774fa9401c1SWarner Losh 775fa9401c1SWarner Losh Please see the following url for more details: 776fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 77747d0d01fSWarner Losh20011229: 77847d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 77947d0d01fSWarner Losh networkfs_types, please note that it has changed 78047d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 78147d0d01fSWarner Losh 782514318a8SWarner Losh20011220: 783514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 784514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 785514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 786514318a8SWarner Losh own. All the accumulated features and bug fixes of the i4b 787514318a8SWarner Losh version have now been merged back into the base system's 788514318a8SWarner Losh version now. The only user-visible change resulting from this 789514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 790514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 791514318a8SWarner Losh as well. (There has never been rc file support for 792514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 793514318a8SWarner Losh reverted by the time the changes are MFCed.) 794514318a8SWarner Losh 795514318a8SWarner Losh20011215: 796514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 797514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 798514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 799514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 800514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 801514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 802514318a8SWarner Losh will need to be customized then for `odd' densities using 803514318a8SWarner Losh fdcontrol(8). 804514318a8SWarner Losh 8052d22e2bfSWarner Losh20011209: 8062d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 8072d22e2bfSWarner Losh and truss(1) now works again. 8082d22e2bfSWarner Losh 8099e0428e2SWarner Losh20011207: 8109e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 8119e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 8129e0428e2SWarner Losh see 8139e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 8149e0428e2SWarner Losh for details. 8159e0428e2SWarner Losh 8169bab8c59SWarner Losh20011204: 8179bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 8189bab8c59SWarner Losh kernel and burncd to be in sync. 8199bab8c59SWarner Losh 820e57d8b01SWarner Losh20011203: 821e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 822e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 823e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 824e57d8b01SWarner Losh not there already. 825e57d8b01SWarner Losh 826e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 827e57d8b01SWarner Losh until the issue has been resolved. 828e57d8b01SWarner Losh 829b001d36fSJacques Vidrine20011202: 830b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 831b001d36fSJacques Vidrine patched. 832b001d36fSJacques Vidrine 8334b676ec1SWarner Losh20011126: 8344b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 8355ebbf43eSWarner Losh after this date. You need to do this only once. 8364b676ec1SWarner Losh 837d961e462SWarner Losh20011103: 838d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 839d961e462SWarner Losh edges may be left, but for the most part things should be 8404b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 841d961e462SWarner Losh 842d961e462SWarner Losh20011030: 843d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 844d961e462SWarner Losh choppy waves in the upgrade process. 845d961e462SWarner Losh 8461fe003b6SWarner Losh20011030: 847a4b6fda0SWarner Losh The asr driver problem has been resolved. 8481fe003b6SWarner Losh 8491fe003b6SWarner Losh20011027: 8501fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 8511fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 8521fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 8531fe003b6SWarner Losh try to use from this date forward. 8541fe003b6SWarner Losh 8551fe003b6SWarner Losh20011025: 8561fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 8571fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 8581fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 8591fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 8601fe003b6SWarner Losh TARGET_ARCH=i386. 8611fe003b6SWarner Losh 862d05f9643SWarner Losh20011001: 863d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 864d05f9643SWarner Losh You must recompile both the kernel and userland applications 865d05f9643SWarner Losh at the same time. 866d05f9643SWarner Losh 86758970f85SWarner Losh20010929: 86858970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 86958970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 87058970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 87158970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 8729d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 87358970f85SWarner Losh 87458970f85SWarner Losh20010927: 87558970f85SWarner Losh Some weird problems result from using ACPI on some machines. 87658970f85SWarner Losh To disable ACPI you can add 87766ff0e67SMax Khon hint.acpi.0.disabled="1" 87858970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 87958970f85SWarner Losh loader "ok" prompt). 88058970f85SWarner Losh 88158970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 88258970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 88358970f85SWarner Losh file and not list acpi in that list. 884378f4486SAlfred Perlstein 8855119d237SWarner Losh20010924: 8865119d237SWarner Losh The buildworld has been fixed. You may need to install 8875119d237SWarner Losh the 4.x compatibility libraries for some old binaries 8888b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 8898b039fffSWarner Losh get them installed on every installworld, or execute the 8908b039fffSWarner Losh following to get them installed only once: 8918b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 89258970f85SWarner Losh make all install 8938b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 8945119d237SWarner Losh 8953c293725SWarner Losh20010919: 8963c293725SWarner Losh There's a bug in the world build process. The cross-tools 8973c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 8983c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 899772730c7SWarner Losh workaround is to add 9003c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 9013c293725SWarner Losh before building world when upgrading from 4.x to current. This 9023c293725SWarner Losh can be removed afterwards. 9033c293725SWarner Losh 9043c293725SWarner Losh A proper fix to the buildworld target is needed. 9053c293725SWarner Losh 9063c293725SWarner Losh20010918: 9073c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 9083c293725SWarner Losh NFS may be unstable after this date. 9093c293725SWarner Losh 9103c293725SWarner Losh20010912: 9113c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 9123c293725SWarner Losh the kernel. While a few problems were introduced in the 9133c293725SWarner Losh initial commit, most of the major ones have been found and 9143c293725SWarner Losh corrected. 9153c293725SWarner Losh 9163c293725SWarner Losh20010901: 9173c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 9183c293725SWarner Losh arounds described in the 20010604 entry are now no longer 9193c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 9203c293725SWarner Losh have been rectified around this date. 9213c293725SWarner Losh 92298b17b95SWarner Losh20010823: 92398b17b95SWarner Losh named now runs as user bind and group bind rather than as 92498b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 92598b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 92698b17b95SWarner Losh and that group bind is available in /etc/group. Also make 92798b17b95SWarner Losh sure that user or group bind has read (and not write) 92898b17b95SWarner Losh permission for your name server configuration and that it 92998b17b95SWarner Losh has read and write permission for your slave zone files and 93098b17b95SWarner Losh directory. 93198b17b95SWarner Losh 93298b17b95SWarner Losh If you wish to continue to run named as root (a less secure 93398b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 93498b17b95SWarner Losh 93598b17b95SWarner Losh named_flags= 93698b17b95SWarner Losh 9377b9786edSMark Murray20010709: 9387b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 9397b9786edSMark Murray the ability of the shared library major number to handle. 9407b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 9417b9786edSMark Murray solution is to rebuild those ports. 9427b9786edSMark Murray 9431d28950eSWarner Losh20010628: 9441d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 9451d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 9461d28950eSWarner Losh 947e72fd46aSWarner Losh20010625: 94898b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 94998b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 95098b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 95198b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 95298b17b95SWarner Losh IRQ configuration needs more safety belts. 95316de1a07SWarner Losh 9540d415dffSWarner Losh20010617: 955e72fd46aSWarner Losh Softupdates problems have been corrected. 9560d415dffSWarner Losh 9570d415dffSWarner Losh20010614: 9580d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 9590d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 9600d415dffSWarner Losh kernel building methods. 9610d415dffSWarner Losh 9628b9959adSWarner Losh20010613: 9638b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 9648b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 965e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 966e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 9678b9959adSWarner Losh 968e72fd46aSWarner Losh20010613: 9698b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 970e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 971e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 9728b9959adSWarner Losh 9730d415dffSWarner Losh20010612: 9740d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 9750d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 9760d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 9770d415dffSWarner Losh work around this issue, please use only one or the other mechanism 9780d415dffSWarner Losh until this bug is fixed. 9790d415dffSWarner Losh 980e72fd46aSWarner Losh Please note that a feature of config is that if you have config 981e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 982ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 983e72fd46aSWarner Losh 9840d415dffSWarner Losh20010610: 9850d415dffSWarner Losh Locale names have changed to match other systems better. 9860d415dffSWarner Losh 9876ccdb5e4SWarner Losh20010604: 9886ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 9896ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 9906ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 9913590182eSWarner Losh Interrupt storms look a lot like a hang. 9923590182eSWarner Losh 9933590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 9943590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 9953590182eSWarner Losh it is). 9963590182eSWarner Losh 9973590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 9983590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 9993590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 10003590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 10016ccdb5e4SWarner Losh 10020bc62786SWarner Losh20010530: 10030bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 10040bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 10050bc62786SWarner Losh a limited time. If you see 10060bc62786SWarner Losh 10070bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 10080bc62786SWarner Losh 10090bc62786SWarner Losh in your makeworld, then you need to migrate towards using 10100bc62786SWarner Losh COPY=-C. 10110bc62786SWarner Losh 101268a38c6cSWarner Losh20010525: 1013b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 1014c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 1015c4f4a728SWarner Losh definitely is in bad shape. 101668a38c6cSWarner Losh 1017ed0f29caSWarner Losh20010521: 1018ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 1019ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 1020ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 1021ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 1022ed0f29caSWarner Losh is 1023ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 1024ed0f29caSWarner Losh 102580c16af9SWarner Losh20010520: 102668a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 102780c16af9SWarner Losh 102880c16af9SWarner Losh20010519: 102980c16af9SWarner Losh pccard has had much reorganizational work done to it over 103080c16af9SWarner Losh the past few days. Everything should still work, but if 103180c16af9SWarner Losh not, please contact imp@freebsd.org. 103280c16af9SWarner Losh 1033a45f2d05SWarner Losh20010517: 1034a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 1035a45f2d05SWarner Losh userland at the same time. 1036a45f2d05SWarner Losh 1037a45f2d05SWarner Losh20010517: 1038a45f2d05SWarner Losh New ncurses imported. 1039a45f2d05SWarner Losh 10402988afcaSWarner Losh20010512: 10412988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 10422988afcaSWarner Losh will be the only way to go starting July 1. 10432988afcaSWarner Losh 10441a33dba7SWarner Losh20010504: 10451a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 10461a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 10471a33dba7SWarner Losh 104809946a51SWarner Losh20010502: 104909946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 105009946a51SWarner Losh 105109946a51SWarner Losh20010501: 105209946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 105309946a51SWarner Losh 105409946a51SWarner Losh20010430: 1055a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 105609946a51SWarner Losh go back in the water. 105709946a51SWarner Losh 105809946a51SWarner Losh20010429: 105909946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 106009946a51SWarner Losh this date, but before the correction date. 106109946a51SWarner Losh 106291dd3b53SWarner Losh20010423: 106391dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 106491dd3b53SWarner Losh 106591dd3b53SWarner Losh20010411: 106691dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 106791dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 106891dd3b53SWarner Losh Update only if you understand that you must not use the old 106991dd3b53SWarner Losh fsck with the new kernel ever. 107091dd3b53SWarner Losh 1071933b3269SWarner Losh20010330: 1072933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 1073c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 1074933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 1075933b3269SWarner Losh 1076933b3269SWarner Losh20010319: 1077933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 1078933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 1079933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 1080f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 108109946a51SWarner Losh 108209946a51SWarner Losh20010315: 108309946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 1084ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 108509946a51SWarner Losh been replaced by tunables. See ata.4 for details. 1086933b3269SWarner Losh 1087933b3269SWarner Losh20010312: 1088933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 1089933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 1090933b3269SWarner Losh 1091933b3269SWarner Losh20010312: 1092933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 1093933b3269SWarner Losh instead of ad-hoc. 1094933b3269SWarner Losh 1095933b3269SWarner Losh20010310: 1096f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 1097933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 1098933b3269SWarner Losh ssh might not work if you don't. 1099933b3269SWarner Losh 110062353691SWarner Losh20010303: 110162353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 110262353691SWarner Losh which means that you must include the miibus in your kernel if 110362353691SWarner Losh you use the ed driver. 110462353691SWarner Losh 1105d325cf65SWarner Losh20010220: 1106d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 1107d325cf65SWarner Losh safe to go back into the water. 1108d325cf65SWarner Losh 1109024daae6SWarner Losh20010211: 1110024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 1111024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 1112024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 1113024daae6SWarner Losh that before upgrading would be a good time to do a level 0 1114024daae6SWarner Losh dump of your system. No, really, I mean it this time. 1115024daae6SWarner Losh 1116024daae6SWarner Losh To get to the new system, you'll need to use the following 1117024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 1118024daae6SWarner Losh don't have to move this to the updating section. 1119024daae6SWarner Losh 1120024daae6SWarner Losh To get around the installworld problem, do: 1121024daae6SWarner Losh # cd /usr/src/usr.bin/sed 1122024daae6SWarner Losh # make install 1123024daae6SWarner Losh # cd /usr/src 1124024daae6SWarner Losh # make installworld 1125024daae6SWarner Losh If that doesn't work, then try: 1126024daae6SWarner Losh # make -k installworld 1127024daae6SWarner Losh # make installworld 1128024daae6SWarner Losh 1129024daae6SWarner Losh20010207: 1130024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 1131024daae6SWarner Losh do not include devfs in your kernel as problems result. 1132024daae6SWarner Losh 1133024daae6SWarner Losh20010205: 11347595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 1135024daae6SWarner Losh Remove them from your config. 1136024daae6SWarner Losh 11371e159248SWarner Losh20010122: 11381e159248SWarner Losh ****************************** WARNING ****************************** 11391e159248SWarner Losh buildkernel has been changed slightly 11401e159248SWarner Losh ****************************** WARNING ****************************** 11411e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 11421e159248SWarner Losh should update your scripts and make.conf accordingly. 11431e159248SWarner Losh 11441e159248SWarner Losh20010119: 11451e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 11461e159248SWarner Losh This requires a new config to build correctly. 11471e159248SWarner Losh 1148aac7dfeaSWarner Losh20010116: 1149ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 1150aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 1151aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 1152aac7dfeaSWarner Losh 1153aac7dfeaSWarner Losh20010110: 1154aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 1155aac7dfeaSWarner Losh 1156aac7dfeaSWarner Losh20010102: 1157aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 1158aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 1159aac7dfeaSWarner Losh 116063c90c9eSWarner Losh20010101: 116163c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 116263c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 11635fd2a895SWarner Losh dump while building termcap. You can work around this problem 116463c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 116563c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 116663c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 116763c90c9eSWarner Losh might have been ignored by the -k option. 116863c90c9eSWarner Losh 11695fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 11705fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 11715fd2a895SWarner Losh of this working. 11725fd2a895SWarner Losh 1173aac7dfeaSWarner Losh20001228: 1174aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 1175ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 1176aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 1177aac7dfeaSWarner Losh 1178de2bcc63SWarner Losh20001218: 1179de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 1180de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 1181de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 1182de2bcc63SWarner Losh cards will not be recognized without it. 1183de2bcc63SWarner Losh 1184960773f7SWarner Losh20001205: 1185960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 1186960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 1187960773f7SWarner Losh adding the following in pam.conf: 1188960773f7SWarner Losh 1189960773f7SWarner Losh sshd auth sufficient pam_skey.so 1190960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 1191960773f7SWarner Losh sshd session required pam_permit.so 1192960773f7SWarner Losh 11930acc635eSWarner Losh20001031: 11940acc635eSWarner Losh cvs updated to 1.11. 11950acc635eSWarner Losh 11960acc635eSWarner Losh20001020: 11970acc635eSWarner Losh The random device needs more entropy, so you need to make sure 11980acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 11990acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 12000acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 12010acc635eSWarner Losh workaround. 12020acc635eSWarner Losh 12030acc635eSWarner Losh20001010: 12040acc635eSWarner Losh ****************************** WARNING ****************************** 12050acc635eSWarner Losh Sendmail has been updated. 12060acc635eSWarner Losh ****************************** WARNING ****************************** 12070acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 12080acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 12090acc635eSWarner Losh is set. 12100acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 12110acc635eSWarner Losh commands. 12120acc635eSWarner Losh o Now using sendmail's version of vacation(1). 12130acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 12140acc635eSWarner Losh in /usr/share/sendmail/cf. 12150acc635eSWarner Losh o sendmail.cw changed to local-host-names 12160acc635eSWarner Losh 12170acc635eSWarner Losh More details can be found at 12180acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 12190acc635eSWarner Losh 12206e98a146SWarner Losh20001009: 12216e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 12226e98a146SWarner Losh your entire ports tree, or you will have problems. 12236e98a146SWarner Losh 12246e98a146SWarner Losh20001006: 1225685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 12266e98a146SWarner Losh the installed miniperl. It is recommended that you delete 12276e98a146SWarner Losh /usr/bin/miniperl. 12286e98a146SWarner Losh 1229073113a4SWarner Losh20001005: 1230073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1231685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1232073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1233073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1234073113a4SWarner Losh tree for anything to work. 1235073113a4SWarner Losh 12360acc635eSWarner Losh20000928: 12370acc635eSWarner Losh There was a change in the passwd format. Need more information. 12380acc635eSWarner Losh 1239be3885b3SWarner Losh20000916: 1240be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1241be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1242be3885b3SWarner Losh same time as your kernel. 1243be3885b3SWarner Losh 124476ec9675SWarner Losh20000914: 124576ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 124676ec9675SWarner Losh include the device will cause suspended laptops losing time 124776ec9675SWarner Losh when they resume. Include 124876ec9675SWarner Losh device pmtimer 124976ec9675SWarner Losh in your config file and 125001b9a434SWarner Losh hint.pmtimer.0.at="isa" 125176ec9675SWarner Losh to your /boot/device.hints file. 125276ec9675SWarner Losh 1253f4865386SMark Murray20000911: 1254f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1255f4865386SMark Murray rather than an option. The supplied kernel config files have 1256f4865386SMark Murray been updated. You will need to do something similar in your 1257f4865386SMark Murray own kernel config file. 1258f4865386SMark Murray Remove: 1259f4865386SMark Murray options RANDOMDEV 1260f4865386SMark Murray Add: 1261f4865386SMark Murray device random 1262f4865386SMark Murray If you prefer to load the loadable module, you need to do 1263f4865386SMark Murray nothing. 1264f4865386SMark Murray 1265d594498fSWarner Losh20000909: 1266d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1267d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1268d594498fSWarner Losh reflect this if you load this module at boot time. 1269d594498fSWarner Losh The line should read: 1270d594498fSWarner Losh random_load="YES" 1271d594498fSWarner Losh 12720deb7ddcSWarner Losh20000907: 12730deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 127416eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 127516eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 127616eb772dSWarner Losh sure you don't have model loading problems which might at 127716eb772dSWarner Losh first blush appear related to SMP. 127852bf24e7SWarner Losh 12795a01880bSWarner Losh20000906: 12805a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 12815a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 12825a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 12835a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 12845a01880bSWarner Losh don't have one, and you have host.conf. 12855a01880bSWarner Losh 12862b41163cSWarner Losh20000905: 128738d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 128838d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 128938d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 129038d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 129138d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 129238d6ecd2SWarner Losh 129338d6ecd2SWarner Losh20000905: 12948aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 12958aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 12968aab4bc7SWarner Losh is /boot/kernel. 12978aab4bc7SWarner Losh 12988aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 129938d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 130038d6ecd2SWarner Losh installkernel/installworld dance. 13012b41163cSWarner Losh 1302d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1303d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1304d594498fSWarner Losh modules in that directory instead of finding them in the correct 1305d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1306d594498fSWarner Losh is that the linux module crashes your machine after the update. 1307d594498fSWarner Losh 1308d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1309d594498fSWarner Losh mv /modules.old /boot/kernel.old 1310d594498fSWarner Losh chflags noschg /kernel.old 1311d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1312d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1313d594498fSWarner Losh fi 1314d594498fSWarner Losh 1315c22a309cSWarner Losh20000904: 1316c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1317c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1318c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1319c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1320c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1321c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1322c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1323c22a309cSWarner Losh is not likely to be generated. 1324c22a309cSWarner Losh 1325fdb9f54dSWarner Losh20000825: 1326fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 13279c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 13289c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 13299c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 13309c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 13319c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 13329c1a7444SWarner Losh messages will appear after the boot loader tries to start the 13339c1a7444SWarner Losh kernel. 13349c1a7444SWarner Losh 13359c1a7444SWarner Losh20000821: 13369c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 13379c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 13389c1a7444SWarner Losh /boot/loader.conf. 1339fdb9f54dSWarner Losh 13408f250aa7SWarner Losh20000812: 13415da0d091SWarner Losh suidperl is now always built and installed on the system, but 13425da0d091SWarner Losh with permissions of 511. If you have applications that use 13435da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 13445da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 13455da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 13465da0d091SWarner Losh will fix this until the next build. 13475da0d091SWarner Losh 13485da0d091SWarner Losh20000812: 13498f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 13508f250aa7SWarner Losh visible changes that may immediately affect your configuration 13518f250aa7SWarner Losh include: 13528f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 13538f250aa7SWarner Losh - newaliases limited to root and trusted users 13548f250aa7SWarner Losh - MSA port (587) turned on by default 13558f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 13568f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 13578f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 13588f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 13598f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 13608f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 13618f250aa7SWarner Losh 136271c38472SWarner Losh20000810: 136371c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 136471c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 136571c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 136671c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 136771c38472SWarner Losh specific use for it. 136871c38472SWarner Losh 136971c38472SWarner Losh20000729: 137071c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 137171c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 137271c38472SWarner Losh /etc/rc.conf if they want to have the same setup 137371c38472SWarner Losh afterwards (unless the variables already are set, of course): 137471c38472SWarner Losh # Enable network daemons for user convenience. 137571c38472SWarner Losh inetd_enable="YES" 137671c38472SWarner Losh portmap_enable="YES" 137771c38472SWarner Losh sendmail_enable="YES" 137871c38472SWarner Losh 137971c38472SWarner Losh20000728: 138071c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 138171c38472SWarner Losh will need to change that to nullfs_load="YES". 138271c38472SWarner Losh 13831dece4a9SWarner Losh20000728: 13841dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 13851dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 13861dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 13871dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 13881dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 13891dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 13901dece4a9SWarner Losh to /MYKERNEL. 13911dece4a9SWarner Losh 1392409e887cSWarner Losh20000711: 1393409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1394409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1395409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1396409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1397409e887cSWarner Losh for details on potential problems that you might have and how 1398409e887cSWarner Losh to get around them. 1399409e887cSWarner Losh 1400409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1401409e887cSWarner Losh clauses above, you needn't worry. 1402409e887cSWarner Losh 1403409e887cSWarner Losh20000711: 1404409e887cSWarner Losh /etc/security has been updated to print the inode number of 1405409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1406409e887cSWarner Losh in the number of changed programs the first time when you run 1407409e887cSWarner Losh mergemaster to get a new /etc/security. 1408409e887cSWarner Losh 1409673d13f2SWarner Losh20000710: 1410673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1411673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1412673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1413673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1414673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1415673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1416673d13f2SWarner Losh errors. (see below, 20000624). 1417673d13f2SWarner Losh 1418bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 14191dece4a9SWarner Losh 1420673d13f2SWarner Losh20000709: 1421c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1422c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1423c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1424673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1425673d13f2SWarner Losh 1426e98e26cdSWarner Losh20000706: 1427e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1428e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1429e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1430f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1431e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 14322c021c6cSMark Ovens interim if needed. 1433e98e26cdSWarner Losh 1434e98e26cdSWarner Losh20000705: 1435e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1436e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1437e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1438e98e26cdSWarner Losh details. 1439e98e26cdSWarner Losh 1440c373950eSWarner Losh20000704: 14412f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 14422f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 14432f961bc8SWarner Losh 14442f961bc8SWarner Losh20000704: 1445c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1446c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1447c373950eSWarner Losh rc.d scripts that haven't been updated. 1448c373950eSWarner Losh 144927dc3a2bSWarner Losh20000630: 145027dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 145127dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 145227dc3a2bSWarner Losh which should be reported to des@freebsd.org. 145327dc3a2bSWarner Losh 1454b8c215acSWarner Losh20000625: 1455b8c215acSWarner Losh From approximately this date forward, one must have the crypto 145627dc3a2bSWarner Losh system installed in order to build the system and kernel. 145727dc3a2bSWarner Losh While not technically strictly true, one should treat it as 145827dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 145927dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 146027dc3a2bSWarner Losh were required. You should check with the latest collections 146127dc3a2bSWarner Losh to make sure that these haven't changed. 1462b8c215acSWarner Losh 14637b990719SWarner Losh20000624: 14647b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 14657b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 14667b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 14671a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 14687b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 14697b990719SWarner Losh openssh and openssl should not be used to generate keys from this 14707b990719SWarner Losh date to the completion of the work. 14717b990719SWarner Losh 147227dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 147327dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 147427dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 147527dc3a2bSWarner Losh recreate the random and urandom devices. 147627dc3a2bSWarner Losh 147781e54c50SWarner Losh20000622: 147881e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 147981e54c50SWarner Losh BSD license. You may need to remove your symbolic links 148081e54c50SWarner Losh that used to be required when updating. 148181e54c50SWarner Losh 148239943833SWarner Losh20000621: 14832c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 14842a2f33fbSDaniel Baker the config file update procedure. 14852a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1486c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 148759df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 148859df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 148939943833SWarner Losh 1490290f9ad8SWarner Losh20000620: 1491290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1492290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1493290f9ad8SWarner Losh that workaround will no longer be required. 1494290f9ad8SWarner Losh 149590fb6346SWarner Losh20000615: 149690fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 149790fb6346SWarner Losh ad driver. If you haven't done so already, you must update 149890fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 149990fb6346SWarner Losh devices. 150090fb6346SWarner Losh 1501f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1502f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1503f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1504f75f65bbSWarner Losh may work). 1505f75f65bbSWarner Losh 1506ba26da8eSWarner Losh20000612: 1507ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1508290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1509c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1510290f9ad8SWarner Losh to your config file to compile them in statically. The format 1511f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1512f54a3542SWarner Losh NEWCARD for examples of the new format. 1513290f9ad8SWarner Losh 15149698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 15159698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 15169698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 15179698f2c0SWarner Losh in it. 1518bbcc5149SWarner Losh 1519d65850ebSWarner Losh20000522: 1520ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1521d65850ebSWarner Losh building a kernel after this point is advised that they need 1522d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1523d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1524d65850ebSWarner Losh 1525d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1526d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1527d9583a00SWarner Losh is recommended that you don't set this option until the problem 1528d9583a00SWarner Losh is resolved. 1529d9583a00SWarner Losh 15308039cedeSWarner Losh20000513: 15318039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 15328039cedeSWarner Losh 1533d65850ebSWarner Losh20000510: 15348039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 15358039cedeSWarner Losh This will require some care in updating alphas. A new libstand 15368039cedeSWarner Losh is requires for the boot blocks to build properly. 15378039cedeSWarner Losh 15388039cedeSWarner Losh20000503: 15398039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 15408039cedeSWarner Losh is now available. 15418039cedeSWarner Losh 1542d65850ebSWarner Losh20000502: 1543d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1544d65850ebSWarner Losh connected to the kernel building instead. 1545d65850ebSWarner Losh 1546be149406SNik Clayton20000427: 15478039cedeSWarner Losh You may need to build gperf 15488039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 15498039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 15508039cedeSWarner Losh an option only in -current. 15518039cedeSWarner Losh 15522b8dd5f4SWarner Losh20000417: 15532b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1554f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 15552b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 15562b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 15572c021c6cSMark Ovens before you reboot, you'll need to issue: 15582b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 15592b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 15602b8dd5f4SWarner Losh 15618d9f1945SWarner Losh20000320: 15622b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 15632b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 15642b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1565ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 15662b8dd5f4SWarner Losh to the start of /etc/rc.conf. 15678d9f1945SWarner Losh 1568f8ab1dd6SWarner Losh20000319: 1569f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1570f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1571f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1572f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1573f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1574f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1575f8ab1dd6SWarner Losh 157619cada77SWarner Losh20000318: 1577f699bbbbSMark Ovens We've entered the traditional post release dumping party. 157819cada77SWarner Losh Large kernel changes are being committed and are in the 157919cada77SWarner Losh works. It is important to keep the systems' klds and kernel 158019cada77SWarner Losh in sync as kernel interfaces and structures are changing. 158119cada77SWarner Losh Before reporting kernel panics, make sure that all modules 158219cada77SWarner Losh that you are loading are up to date. 1583ba228352SWarner Losh 158419cada77SWarner Losh20000315: 15856d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 15866d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 15876d23c382SWarner Losh will do the trick. This isn't critical until you remove your 15886d23c382SWarner Losh wd device entries in /dev, at which point your system will not 15896d23c382SWarner Losh boot. 15906d23c382SWarner Losh 15916d23c382SWarner Losh20000315: 159219cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 159319cada77SWarner Losh to upgrade to 4.0 from 3.x. 159457199806SWarner Losh 1595dc0dbf5cSWarner LoshCOMMON ITEMS: 1596dc0dbf5cSWarner Losh 1597cd5f061cSWarner Losh # NOTE: 5.x below applies to 6.0-currrent as well, for the 1598cd5f061cSWarner Losh # momemnt. 4.any -> 5.any upgrade support will remain in 1599cd5f061cSWarner Losh # place for 6.0 current, but after 5.3 RELEASE, the 4.any -> 1600cd5f061cSWarner Losh # 6.0-current upgrade path will require moving through 5.3 1601cd5f061cSWarner Losh # RELEASE or newer. 1602cd5f061cSWarner Losh 1603a24eff53SWarner Losh General Notes 1604a24eff53SWarner Losh ------------- 1605a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1606a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1607a24eff53SWarner Losh installworld. This is especially true when upgrading between 1608a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1609a24eff53SWarner Losh or several minor releases, or when several months have passed 1610a24eff53SWarner Losh on the -current branch). 1611a24eff53SWarner Losh 16125780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 16135780f3baSWarner Losh poisoning. This can happen because the make utility reads its 16145780f3baSWarner Losh environment when searching for values for global variables. 16155780f3baSWarner Losh To run your build attempts in an "environmental clean room", 16165780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 16175780f3baSWarner Losh page for more details. 16185780f3baSWarner Losh 1619dc0dbf5cSWarner Losh To build a kernel 1620dc0dbf5cSWarner Losh ----------------- 1621ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1622f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1623ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1624282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1625282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1626dc0dbf5cSWarner Losh 1627ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1628ba01eb20SWarner Losh -------------------------------------------------------------- 16290fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 16300fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 16310fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 16320fbd2da9SKen Smith 16330fbd2da9SKen Smith cd src/sys/${arch}/conf 163447d0d01fSWarner Losh config KERNEL_NAME_HERE 16350fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1636ba01eb20SWarner Losh make depend 1637ba01eb20SWarner Losh make 1638ba01eb20SWarner Losh make install 1639ba01eb20SWarner Losh 1640ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1641ba01eb20SWarner Losh 1642ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1643ba01eb20SWarner Losh ----------------------------------------------------------- 164463cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 164563cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 164663cb445eSWarner Losh 1647f643de42SWarner Losh <make sure you have good level 0 dumps> 164863cb445eSWarner Losh <maybe fix /etc/fstab> [7] 164963cb445eSWarner Losh make buildworld 16506586253aSWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE 165163cb445eSWarner Losh [1] 165263cb445eSWarner Losh <reboot in single user> [3] 16536586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 165463cb445eSWarner Losh mergemaster -p [5] 165563cb445eSWarner Losh make installworld 165663cb445eSWarner Losh mergemaster [4] 165763cb445eSWarner Losh <reboot> 165863cb445eSWarner Losh 1659759f0aefSWarner Losh 1660f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1661f27b1fceSJoseph Koshy -------------------------------------------------- 1662f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1663f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1664f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1665f27b1fceSJoseph Koshy # size. 1666f27b1fceSJoseph Koshy 1667f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1668f27b1fceSJoseph Koshy <boot into -stable> 1669f27b1fceSJoseph Koshy make buildworld 1670f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1671f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1672f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1673f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 16746586253aSWarner Losh cp src/sys/${ARCH}/conf/GENERIC.hints \ 1675f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1676f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 16776586253aSWarner Losh cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1678f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1679f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1680f27b1fceSJoseph Koshy <reboot into current> 1681f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 16826586253aSWarner Losh <maybe install compatibility libraries from src/lib/compat> 1683f27b1fceSJoseph Koshy <reboot> 1684f27b1fceSJoseph Koshy 1685f27b1fceSJoseph Koshy 1686f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1687f27b1fceSJoseph Koshy ---------------------------------------------- 16885c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 16895c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 16905c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 16915c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1692ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1693f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1694f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1695f643de42SWarner Losh # space on /. 1696f643de42SWarner Losh 1697f643de42SWarner Losh <make sure you have good level 0 dumps> 1698fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 169921c075eaSWarner Losh make buildworld [9] 1700c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1701802fc49dSBrian Feldman cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1702be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1703802fc49dSBrian Feldman cd sys/boot ; make STRIP="" install [6] 1704fc8c157fSWarner Losh [1] 1705fc8c157fSWarner Losh <reboot in single user> [3] 17066586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 1707835284beSWarner Losh mergemaster -p [5] 1708f8a4c901SWarner Losh rm -rf /usr/include/g++ 1709ba26da8eSWarner Losh make installworld 1710802fc49dSBrian Feldman mergemaster -i [4] 1711ba26da8eSWarner Losh <reboot> 1712ba26da8eSWarner Losh 1713fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1714fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1715fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1716fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1717fdb9f54dSWarner Losh the UPDATING entries. 1718ba26da8eSWarner Losh 17191dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 17201dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 17211dece4a9SWarner Losh your sources that you have read and understood all the recent 17221dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 17231dece4a9SWarner Losh much fewer pitfalls. 17241dece4a9SWarner Losh 1725134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1726134d2e86SWarner Losh should disable them at this point so they don't crash your 1727134d2e86SWarner Losh system on reboot. 1728134d2e86SWarner Losh 17299c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 17309c1a7444SWarner Losh your own device.hints to reflect your unique hardware 17319c1a7444SWarner Losh configuration. 17329c1a7444SWarner Losh 1733ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1734ee6e1fc3SWarner Losh fsck -p 1735ee6e1fc3SWarner Losh mount -u / 1736ee6e1fc3SWarner Losh mount -a 17376586253aSWarner Losh cd src 173847d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1739f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1740f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 174166986952SRuslan Ermilov For the 4.x -> 5.x upgrade, you will also see many messages about 1742b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1743b705ae10SWarner Losh be ignored while you proceed to the next step. 1744ee6e1fc3SWarner Losh 1745a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1746a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1747a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1748a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1749a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1750a6cd4f9dSWarner Losh for potential gotchas. 1751a6cd4f9dSWarner Losh 1752835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1753835284beSWarner Losh you may need to do this if you get unknown user in the following 1754835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1755835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1756835284beSWarner Losh install) after the buildworld before this step if you last updated 1757835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1758835284beSWarner Losh 1759bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1760bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1761bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1762bd79cf40SWarner Losh ok unload 1763bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1764bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1765bd79cf40SWarner Losh described here. 1766fc8c157fSWarner Losh 1767fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1768fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1769fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1770fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1771fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1772fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1773fc8c157fSWarner Losh 1774c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1775c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1776c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1777c74fe6afSWarner Losh that is hard to boot to recover. 1778c74fe6afSWarner Losh 177921c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 1780802fc49dSBrian Feldman cvs prune empty directories. Also, if CPUTYPE is defined in your 1781802fc49dSBrian Feldman /etc/make.conf, make sure to use the "?=" instead of the "=" assignment 1782802fc49dSBrian Feldman operator, so that buildworld can override the CPUTYPE if it needs to. 1783802fc49dSBrian Feldman In case you would like to avoid installing new packages of everything, 1784802fc49dSBrian Feldman you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 178566986952SRuslan Ermilov compatibility libraries are built which should allow you to continue 1786802fc49dSBrian Feldman using your existing software for a while. 17878633bbeaSBrooks Davis 17888633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 17896586253aSWarner Losh initialized by feeding data into it. src/etc/rc.d/preseedrandom 17908633bbeaSBrooks Davis takes care of this. 1791dc0dbf5cSWarner LoshFORMAT: 1792dc0dbf5cSWarner Losh 1793f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 17941fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1795f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1796f8ab1dd6SWarner Loshprevious releases if your system is older than this. 17971fc1a0dcSWarner Losh 1798e72fd46aSWarner LoshCopyright information: 1799e72fd46aSWarner Losh 18009698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1801e72fd46aSWarner Losh 1802772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1803772730c7SWarner Loshmodification, in full or in part, in any form or format of this 18049698f2c0SWarner Loshdocument are permitted without further permission from the author. 1805e72fd46aSWarner Losh 1806e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1807e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1808e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1809e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1810e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1811e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1812e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1813e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1814e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1815e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1816e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1817e72fd46aSWarner Losh 1818e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1819e72fd46aSWarner Loshauthor a beer. 1820e72fd46aSWarner Losh 182122306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1822772730c7SWarner Loshthis document. 1823772730c7SWarner Losh 182497d92980SPeter Wemm$FreeBSD$ 1825