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 26c1c94d5cSRobert Watson20040828: 27c1c94d5cSRobert Watson The default configuration for the network stack has been changed 28c1c94d5cSRobert Watson such that it now runs without the Giant lock unless configured 29c1c94d5cSRobert Watson otherwise. If you experience network-related instability, you 30c1c94d5cSRobert Watson may wish to try setting "debug.mpsafenet=0" or compiling the 31c1c94d5cSRobert Watson kernel with "options NET_WITH_GIANT". Details on the netperf 32c1c94d5cSRobert Watson project may be found at: 33c1c94d5cSRobert Watson 34c1c94d5cSRobert Watson http://www.watson.org/~robert/freebsd/netperf/ 35c1c94d5cSRobert Watson 36c1c94d5cSRobert Watson Including the 20040828 announcement of configuration change 37c1c94d5cSRobert Watson details. 38c1c94d5cSRobert Watson 39c21fd232SAndre Oppermann20040827: 40c21fd232SAndre Oppermann PFIL_HOOKS are a fixed part of the network stack now and do not 41c21fd232SAndre Oppermann need to be specified in the kernel configuration file anymore. 42c21fd232SAndre Oppermann 43f036d408SJulian Elischer20040819: 44f036d408SJulian Elischer Netgraph changed its message format slightly to align the data 45f036d408SJulian Elischer portion well on 64 bit machines. 46f036d408SJulian Elischer Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd, 47f036d408SJulian Elischer pppoed, bluetooth, ATM) should be recompiled when a new kernel 48f036d408SJulian Elischer is installed. 49f036d408SJulian Elischer 50b067abfaSAndre Oppermann20040817: 510ce70eb4SAndre Oppermann IPFW has been converted to use PFIL_HOOKS. This change is 52b067abfaSAndre Oppermann transparent to userland and preserves the ipfw ABI. The ipfw 53b067abfaSAndre Oppermann core packet inspection and filtering functions have not been 54b067abfaSAndre Oppermann changed, only how ipfw is invoked is different. Note that 55b067abfaSAndre Oppermann "option PFIL_HOOKS" is required to use IPFIREWALL compiled 56b067abfaSAndre Oppermann into the kernel or as KLD. 57b067abfaSAndre Oppermann 58f13a7951SDavid Malone20040814: 59f13a7951SDavid Malone The RANDOM_IP_ID option has been replaced by the sysctl 60f13a7951SDavid Malone net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then 61f13a7951SDavid Malone you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf. 62f13a7951SDavid Malone 633a004637SMax Laier20040807: 643a004637SMax Laier The size of 'struct ifnet' has changed due to the addition of the 653a004637SMax Laier if_carp placeholder. All kernel modules implementing network 663a004637SMax Laier interfaces must be recompiled as a result. 673a004637SMax Laier 684f34d8d1SJohn-Mark Gurney20040806: 694f34d8d1SJohn-Mark Gurney Module loading has been fixed. Some older installations will 70ac41c814SRuslan Ermilov drop proper module_path initialization and modules will fail to 714f34d8d1SJohn-Mark Gurney load properly. If you have a line in /boot/loader.rc that says: 724f34d8d1SJohn-Mark Gurney "initialize drop", do (i386 only): 734f34d8d1SJohn-Mark Gurney cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc 744f34d8d1SJohn-Mark Gurney chown root:wheel /boot/loader.rc 754f34d8d1SJohn-Mark Gurney chmod 444 /boot/loader.rc 764f34d8d1SJohn-Mark Gurney 778f075db4SMark Murray20040802: 788f075db4SMark Murray making /dev/(null|zero) into a module proved to be too unpopular, 798f075db4SMark Murray so this bit has been revoked from the previous (20040801) entry. 808f075db4SMark Murray 81d064d6dbSMark Murray20040801: 82d064d6dbSMark Murray The /dev/mem, /dev/io /dev/(null/zero) devices are now modules, 83d064d6dbSMark Murray so you may wish to add them to your kernel config file. See 84d064d6dbSMark Murray GENERIC for examples. 85d064d6dbSMark Murray 86b289983eSAlexander Kabaev20040728: 8754bd5271SAlexander Kabaev System compiler has been upgraded to GCC 3.4.2-pre. As with any major 8854bd5271SAlexander Kabaev compiler upgrade, there are several issues to be aware of. GCC 3.4.x 8954bd5271SAlexander Kabaev has broken C++ ABI compatibility with previous releases yet again 9054bd5271SAlexander Kabaev and users will have to rebuild all their C++ programs with the new 91d0e54ab4SDavid E. O'Brien compiler. If you are getting run-time error such as 92d0e54ab4SDavid E. O'Brien /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE" 93d0e54ab4SDavid E. O'Brien This entry does apply to you. 94d0e54ab4SDavid E. O'Brien 95d0e54ab4SDavid E. O'Brien A new unit-at-a-time optimization mode, which is default in this 96d0e54ab4SDavid E. O'Brien compiler release, is more aggressive in removing unused static 97d0e54ab4SDavid E. O'Brien symbols. This is the likely cause of 'make buildworld' breakages 98cd5f061cSWarner Losh with non-default CFLAGS where optimization level is set to -O2 99cd5f061cSWarner Losh or higher. 10054bd5271SAlexander Kabaev 1016e1afae3SWarner Losh With the upgrade of the system compiler, the kernel has been upgraded 1026e1afae3SWarner Losh to match the new system compiler. This makes it impossible to build 1036e1afae3SWarner Losh a new kernel with the old compiler. Upgrade your system via 1046e1afae3SWarner Losh make buildworld and make kernel (see below) to fix this problem. 1056e1afae3SWarner Losh 10636ed21e6SRobert Watson20040727: 10736ed21e6SRobert Watson The size of 'struct ifnet' has changed due to the addition of 10836ed21e6SRobert Watson the IFF_NEEDSGIANT flag (and what it implies). All kernel 10936ed21e6SRobert Watson modules implementing network interfaces must be recompiled as 11036ed21e6SRobert Watson a result. 11136ed21e6SRobert Watson 1126305ac24SSeigo Tanimura20040716: 1136305ac24SSeigo Tanimura The sound device drivers are renamed. `sound' is always required, 1146305ac24SSeigo Tanimura while `snd_*' should be configured accordingly to your hardware. 1156305ac24SSeigo Tanimura Refer to NOTES for the detail of the drivers. 1166305ac24SSeigo Tanimura 117e623dcb7SMarcel Moolenaar20040710: 118e623dcb7SMarcel Moolenaar __FreeBSD_version bumped to 502122. 119e623dcb7SMarcel Moolenaar 120e623dcb7SMarcel Moolenaar20040710: 121e623dcb7SMarcel Moolenaar The console initialization on Alpha has been reworked and is now 122e623dcb7SMarcel Moolenaar identical to other platforms. This means that the hardcoding of 123e623dcb7SMarcel Moolenaar the serial console and the debug port has been removed. As such, 124e623dcb7SMarcel Moolenaar hints are now required for the sio(4) driver to become a console 125e623dcb7SMarcel Moolenaar or debug port. The NO_SIO option has been decommissioned because 126e623dcb7SMarcel Moolenaar of this. 127e623dcb7SMarcel Moolenaar 128e623dcb7SMarcel Moolenaar20040710: 129e623dcb7SMarcel Moolenaar A revamp of the debugging code in the kernel with some visible 130e623dcb7SMarcel Moolenaar changes beyond just the debugging experience: 131e623dcb7SMarcel Moolenaar o The DDB option is now specific to the DDB debugger backend 132e623dcb7SMarcel Moolenaar and should not be used any more for conditional compilation 133e623dcb7SMarcel Moolenaar of debugging code for when debugging is enabled. Use the KDB 134e623dcb7SMarcel Moolenaar option for this. 135e623dcb7SMarcel Moolenaar o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have 136e623dcb7SMarcel Moolenaar been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED 137e623dcb7SMarcel Moolenaar respectively. This is in line with the first bullet. 138e623dcb7SMarcel Moolenaar o The remote GDB support has been untangled from DDB and needs 1395bd7ce0aSJens Schweikhardt to be enabled separately now. Use the GDB option for this. 140e623dcb7SMarcel Moolenaar o The GDB_REMOTE_CHAT option has been removed. Support for this 141e623dcb7SMarcel Moolenaar homegrown feature is discontinued. The GDB remote protocol 142e623dcb7SMarcel Moolenaar supports console output and it makes sense to use that. 143e623dcb7SMarcel Moolenaar o The DDB_NOKLDSYM option has been removed. The DDB debugger 144e623dcb7SMarcel Moolenaar now supports both direct symbol table lookups as well as KLD 145e623dcb7SMarcel Moolenaar symbol lookups through the linker. 146e623dcb7SMarcel Moolenaar 1476421d1dbSMaksim Yevmenkin20040708: 1486421d1dbSMaksim Yevmenkin Bluetooth code has been marked as non-i386 specific. 1496421d1dbSMaksim Yevmenkin __FreeBSD_version has been bumped to 502121 to mark this change. 1506421d1dbSMaksim Yevmenkin 15158af3216SWarner Losh20040702: 15258af3216SWarner Losh The native preemption has been added to the kernel scheduler. 1535bd7ce0aSJens Schweikhardt There is some report that the ULE scheduler was broken in some 1545bd7ce0aSJens Schweikhardt machines and we encourage users using the ULE scheduler either 1555bd7ce0aSJens Schweikhardt stick with a known good kernel, or temporarily switch to the 4BSD 15658af3216SWarner Losh scheduler as a workaround. 15758af3216SWarner Losh 158c2dba668SNate Lawson20040630: 1598ed370fdSJulian Elischer The netgraph ABI version number has been incremented to indicate 1608ed370fdSJulian Elischer an incompatible change in the ABI. Old netgraph nodes will refuse 161a6c26e1cSBruce M Simpson to attach until recompiled. Netgraph now uses mbuf tags to move 162a6c26e1cSBruce M Simpson metadata and this commit removes its home-grown metadata facility. 163a6c26e1cSBruce M Simpson Nodes should just recompile, unless they use metadata, in which 164a6c26e1cSBruce M Simpson case the changes are simple; the file ng_ksocket.c serves as an 165a6c26e1cSBruce M Simpson example of such changes. 1668ed370fdSJulian Elischer 16758af3216SWarner Losh This also broke i4b, although the compile problem has been papered 16858af3216SWarner Losh over. 16958af3216SWarner Losh 1708ed370fdSJulian Elischer20040630: 171c2dba668SNate Lawson ACPI has been updated to disable known-bad BIOS revisions. A message 1725bd7ce0aSJens Schweikhardt will be printed on the console indicating that ACPI has been disabled 173c2dba668SNate Lawson automatically and that the user should use a newer BIOS, if possible. 174c2dba668SNate Lawson If you think ACPI does work on your system and want to override 175c2dba668SNate Lawson this (i.e., for testing), set hint.acpi.0.disabled="0" at the 176c2dba668SNate Lawson loader prompt. 177c2dba668SNate Lawson 1788ee2ac9eSMax Laier20040623: 1795bd7ce0aSJens Schweikhardt pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege 1808ee2ac9eSMax Laier separated now. It uses the newly created "_pflogd" user/group 1818ee2ac9eSMax Laier combination. If you plan to use pflogd(8) make sure to run 1828ee2ac9eSMax Laier mergemaster -p or install the "_pflogd" user and group manually. 1838ee2ac9eSMax Laier 1843db5687dSBrooks Davis20040622: 1853db5687dSBrooks Davis Network interface cloning has been overhauled. This change will 1863db5687dSBrooks Davis require a recompile of modules using cloning and modification of 1873db5687dSBrooks Davis external ones to the new API. __FreeBSD_version has been bumped 1883db5687dSBrooks Davis to 502119 to mark this change. Additionally, users creating 1893db5687dSBrooks Davis stf(4) interfaces via "ifconfig stf" will need to update their 1903db5687dSBrooks Davis scripts as this will create an interface named "stf" instead of 1913db5687dSBrooks Davis "stf0" and ifconfig will not print "stf0" to stdout. 1923db5687dSBrooks Davis 193e0ae81f3SDag-Erling Smørgrav20040621: 194e0ae81f3SDag-Erling Smørgrav On 20040524, the /etc/rc.d/nsswitch script was modified to 195e0ae81f3SDag-Erling Smørgrav automatically create /etc/nsswitch.conf on startup if it did 196e0ae81f3SDag-Erling Smørgrav not already exist. Unfortunately, an error in the man page 197e0ae81f3SDag-Erling Smørgrav was carried over to the script, resulting in incorrect 198e0ae81f3SDag-Erling Smørgrav nsswitch settings. The simplest remedy is to remove both 199e0ae81f3SDag-Erling Smørgrav /etc/nsswitch.conf and /etc/host.conf; they will be recreated 200e0ae81f3SDag-Erling Smørgrav during the next reboot. 201e0ae81f3SDag-Erling Smørgrav 2024717d22aSJohn Polstra20040614: 2034717d22aSJohn Polstra The return value of sema_timedwait(9) has been changed to 2044717d22aSJohn Polstra make it consistent with cv_timedwait(9). Be sure to recompile 2054717d22aSJohn Polstra the ips module and any third-party modules which call 2064717d22aSJohn Polstra sema_timedwait. 2074717d22aSJohn Polstra 2086cb7a382SMax Laier20040613: 2096cb7a382SMax Laier ALTQ is now linked to the build. This breaks ABI for struct ifnet. 2106cb7a382SMax Laier Make sure to recompile modules and any userland that makes use of 211df843493SMax Laier sizeof(struct ifnet). In order to get the altq headers in place 212df843493SMax Laier please recompile and reinstall world. 2136cb7a382SMax Laier 2142454685eSJulian Elischer20040607: 2152454685eSJulian Elischer Splitting kern_thread.c into 2 files (adding kern_kse.c) 2162454685eSJulian Elischer requires that you re-run config after updating your tree. 2172454685eSJulian Elischer 21864fef830SSeigo Tanimura20040601: 21964fef830SSeigo Tanimura The MIDI drivers have been removed. Until the new module-friendly 22064fef830SSeigo Tanimura ones are merged, remove or comment out midi and seq from your 22164fef830SSeigo Tanimura kernel configuration. 22264fef830SSeigo Tanimura 223bb4f06e7SAndre Oppermann20040423: 224bb4f06e7SAndre Oppermann Due to a new option in ipfw (versrcreach) the ipfw(8) command 225bb4f06e7SAndre Oppermann needs to be recompiled. Normal accept/reject rules without 226bb4f06e7SAndre Oppermann options are not affected but those with options may break until 227bb4f06e7SAndre Oppermann ipfw(8) is recompiled. 228bb4f06e7SAndre Oppermann 22905641e82SColin Percival20040420: 23005641e82SColin Percival Due to changes in the callout ABI, kernels compiled after this 23105641e82SColin Percival date may be incompatible with kernel modules compiled prior to 23205641e82SColin Percival 20040406. 23305641e82SColin Percival 234d0dc9183SWarner Losh20040414: 235d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 236d0dc9183SWarner Losh problems for your system, please disable it using the tunable 237d0dc9183SWarner Losh hw.pci.do_powerstate=0. 238d0dc9183SWarner Losh 239d0dc9183SWarner Losh20040412: 240d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 241d0dc9183SWarner Losh drive is still broken. 242d0dc9183SWarner Losh 243d0dc9183SWarner Losh20040410: 244d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 245d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 246d0dc9183SWarner Losh the unanticipated problems have been resolved. 247d0dc9183SWarner Losh 2488633bbeaSBrooks Davis20040409: 2498633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 2508633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 2518633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 2528633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 25376c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 2548633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 2558633bbeaSBrooks Davis 256d40d033aSRobert Watson20040322: 257d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 258d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 259d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 260d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 261d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 262d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 263d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 264d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 265d40d033aSRobert Watson locking is merged to permit this to take place. 266d40d033aSRobert Watson 267ec9b318eSGarance A Drosehn20040310: 268ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 269ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 270ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 271ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 272ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 273ec9b318eSGarance A Drosehn 274fc28f1ffSMax Laier20040308: 275fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 276fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 2774c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 2784c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 279fc28f1ffSMax Laier Also note that pf requires "options PFIL_HOOKS" in the kernel. The 280fc28f1ffSMax Laier pf system consists of the following three devices: 281fc28f1ffSMax Laier device pf # required 282fc28f1ffSMax Laier device pflog # optional 283fc28f1ffSMax Laier device pfsync # optional 284fc28f1ffSMax Laier 2853aff5d06SDag-Erling Smørgrav20040303: 2863aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 2873aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 2883aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 2893aff5d06SDag-Erling Smørgrav 2903aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 2913aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 2923aff5d06SDag-Erling Smørgrav 2933aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 2943aff5d06SDag-Erling Smørgrav to use libpthread instead. 2953aff5d06SDag-Erling Smørgrav 296fd63c5b3SDag-Erling Smørgrav20040226: 2979d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 298fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 299fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 300fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 301fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 302fd63c5b3SDag-Erling Smørgrav 303714ae42aSBruce M Simpson20040225: 304e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 305e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 306e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 307e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 308e07a40f3SBrian Feldman should remain unaffected. 309e07a40f3SBrian Feldman 310e07a40f3SBrian Feldman20040225: 311714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 312714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 313714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 314714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 315714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 316714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 317714ae42aSBruce M Simpson 318fbd2e692SAndre Oppermann20040224: 319fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 3205bd7ce0aSJens Schweikhardt and related userland network utilities necessary. 321fbd2e692SAndre Oppermann 322158b90daSWarner Losh20040222: 323158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 324158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 325158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 326158b90daSWarner Losh Drivers outside the tree will need to be updated. 327158b90daSWarner Losh 328b7b1e150SMike Makonnen20040207: 329b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 330b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 331b7b1e150SMike Makonnen 332aca89ee6SDaniel Eischen20040130: 333aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 334aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 335aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 336aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 337aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 338aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 339aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 340aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 341aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 342aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 343aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 344aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 345aca89ee6SDaniel Eischen do not work with libpthread. 346aca89ee6SDaniel Eischen 34768b7b3a9SAlex Dupre20040125: 34868b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 34968b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 35068b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 35168b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 35268b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 35368b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 35468b7b3a9SAlex Dupre 355ff46e0deSWarner Losh20040125: 356ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 357ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 358ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 359ff46e0deSWarner Losh 360ce41f4bfSRobert Watson20031213: 361ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 362ce41f4bfSRobert Watson if the login process is unable to successfully set the 363ce41f4bfSRobert Watson process credentials to include all groups defined for the 364ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 365ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 366ce41f4bfSRobert Watson defined, or they will be unable to log in. 367ce41f4bfSRobert Watson 368c124fa05SJohn Baldwin20031203: 369c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 370c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 371c124fa05SJohn Baldwin 3728ad1f5e4SHartmut Brandt20031112: 37330093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 37430093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 37597209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 37697209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 37797209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 37897209ca3SRobert Watson not know about the new system calls that support the new statfs 3793f631d52SMarcel Moolenaar structure. 3803f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 3813f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 3823f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 3833f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 3843f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 3853f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 3863f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 3873f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 3883f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 3893f631d52SMarcel Moolenaar these changes are installed. 39030093b05SWarner Losh 39130093b05SWarner Losh ****************************DANGER******************************* 39230093b05SWarner Losh 39330093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 39430093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 39530093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 39630093b05SWarner Losh kernel. 39764a18d6fSKirk McKusick 39864a18d6fSKirk McKusick20031112: 3998ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 4008ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 4018ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 4028ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 4038ad1f5e4SHartmut Brandt sync before rebooting. 4048ad1f5e4SHartmut Brandt 405c53a5d8fSJohn Baldwin20031111: 406c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 407c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 408c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 409c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 410c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 411c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 412c53a5d8fSJohn Baldwin 4138bf455a5SJohn Baldwin20031103: 4148bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 4158bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 4162a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 4178bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 4188bf455a5SJohn Baldwin 4199bf40edeSBrooks Davis20031031: 4209bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 4219bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 4229bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 4239bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 4249bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 4259bf40edeSBrooks Davis reflect this change. 4269bf40edeSBrooks Davis 42747a42c7aSPoul-Henning Kamp20030928: 42847a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 42947a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 4305bd7ce0aSJens Schweikhardt __FreeBSD_version bumped to 501110. 43147a42c7aSPoul-Henning Kamp 43207105342SMax Khon20030926: 43307105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 43407105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 43507105342SMax Khon 43617dcd026SSam Leffler20030925: 43717dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 43817dcd026SSam Leffler also be explicitly configured. Previously this dependency was 43917dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 44017dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 44117dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 44217dcd026SSam Leffler 443fedf1d01SBruce M Simpson20030923: 444fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 445fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 446fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 447fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 448fedf1d01SBruce M Simpson 449db38f9cbSJacques Vidrine20030915: 450db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 451db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 452db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 453db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 454db38f9cbSJacques Vidrine 455c09d2c2bSMike Makonnen20030829: 456c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 457c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 458c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 459c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 460c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 461c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 462c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 463c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 464c09d2c2bSMike Makonnen may or may not exist on your system. 465c09d2c2bSMike Makonnen 46617c159dcSSøren Schmidt20030824: 46717c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 46817c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 469f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 470f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 47117c159dcSSøren Schmidt 472c1f61aa9SDavid E. O'Brien20030819: 473c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 474c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 475c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 476c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 47769f7bcf3SWarner Losh 47838c962e7SNate Lawson20030728: 47938c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 48038c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 48138c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 48238c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 48338c962e7SNate Lawson so the quirk can be re-enabled. 48438c962e7SNate Lawson 48574111097SWarner Losh20030724: 48674111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 48774111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 48874111097SWarner Losh 489178cf4e9SWarner Losh20030722: 490178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 491178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 492178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 493178cf4e9SWarner Losh FPU hardware. 494178cf4e9SWarner Losh 495178cf4e9SWarner Losh20030714: 496178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 497178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 498178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 499178cf4e9SWarner Losh People should report those issues to current@. 500178cf4e9SWarner Losh 501157c629aSWarner Losh20030711: 502157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 5038b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 50405538fa9SWarner Losh /usr/obj. 505157c629aSWarner Losh 50674111097SWarner Losh20030610: 50774111097SWarner Losh Remove deprecated locale names and transition period code 50874111097SWarner Losh for them, finishing switching to the new scheme. Check your 50974111097SWarner Losh LANG environment variable. 51074111097SWarner Losh 51174111097SWarner Losh20030609: 51274111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 51374111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 51474111097SWarner Losh important to remember beforehand if your source tree is on 51574111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 51674111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 51774111097SWarner Losh kernel. 51874111097SWarner Losh 51974111097SWarner Losh20030605: 5206cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 5216cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 5226cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 5236cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 5246cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 5256cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 5266cc6353fSMarcel Moolenaar 5276cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 5286cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 5296cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 5306cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 5316cc6353fSMarcel Moolenaar : 5326cc6353fSMarcel Moolenaar 5336cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 5346cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 5356cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 5366cc6353fSMarcel Moolenaar 53752b47445SMark Murray20030505: 53852b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 53952b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 54052b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 54152b47445SMark Murray 542a26df538SWarner Losh20030502: 543a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 544a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 545a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 546a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 547a26df538SWarner Losh 5484b065e2cSDoug Barton20030501: 5494b065e2cSDoug Barton The old rc system has been removed. Please report any problems 5504b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 5514b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 5524b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 5534b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 5544b065e2cSDoug Barton utilizes these old scripts has also been removed. 5554b065e2cSDoug Barton 55681cda3d9SWarner Losh20030423: 55781cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 55881cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 55981cda3d9SWarner Losh work around in devd will be removed around 20030507. You 56081cda3d9SWarner Losh have until then to upgrade your kernel before updating 56181cda3d9SWarner Losh userland. In general, you should have a userland and 56281cda3d9SWarner Losh kernel that's in sync with each other. However, given the 56381cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 56481cda3d9SWarner Losh allowances are made. 56581cda3d9SWarner Losh 56647a657d1SRuslan Ermilov20030329: 56747a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 56847a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 56947a657d1SRuslan Ermilov while upgrading the system through a buildworld. 57047a657d1SRuslan Ermilov 57147a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 57247a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 57347a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 57447a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 57547a657d1SRuslan Ermilov 57647a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 57747a657d1SRuslan Ermilov make cleandir && make obj && \ 57847a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 57947a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 58047a657d1SRuslan Ermilov 5815d2af00cSGregory Neil Shapiro20030208: 5825d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 5835d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 5845d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 5855d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 5865d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 5875d2af00cSGregory Neil Shapiro 5885d2af00cSGregory Neil Shapiro20030128: 5899db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 590ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 5919db58771SPoul-Henning Kamp be removed when convenient. 5929db58771SPoul-Henning Kamp 5938d9b3f57SJake Burkholder20030126: 5948d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 5958d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 5968d9b3f57SJake Burkholder 5971c5efda5SJeff Roberson20030125: 5981c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 5991c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 600ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 6011c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 6021c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 6031c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 6041c5efda5SJeff Roberson 6059d1d64f5SWarner Losh20030115: 6069d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 6079d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 6089d1d64f5SWarner Losh properly. 6099d1d64f5SWarner Losh 610c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 611c9fdb80aSWarner Losh configured for point to point links to bring it more in line 612c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 613c9fdb80aSWarner Losh with NetBSD. 614c9fdb80aSWarner Losh 615161dc364SAlexander Kabaev20021222: 616161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 617161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 618161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 619161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 620161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 621161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 62284cc83efSAlexander Kabaev rebuilt. 623161dc364SAlexander Kabaev 624fb4c8061SMartin Blapp20021216: 625fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 62689056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 627fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 6289d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 629fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 630fb4c8061SMartin Blapp 63117d47eb3SGiorgos Keramidas20021202: 63217d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 63317d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 63417d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 63517d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 63617d47eb3SGiorgos Keramidas 637a4459294SBill Fenner20021029: 638a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 639a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 640a4459294SBill Fenner consumers in sync. 641a4459294SBill Fenner 642fc8c157fSWarner Losh20021024: 643c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 644c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 645c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 646c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 647c57404feSRuslan Ermilov partition really is on. The old device names have gone 648c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 649c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 650c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 65169f7bcf3SWarner Losh 652fd9e8bdaSAndrew Gallatin20021023: 653fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 654fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 655fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 656fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 657fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 658fd9e8bdaSAndrew Gallatin 659fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 660fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 661fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 662fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 663fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 664fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 665fd9e8bdaSAndrew Gallatin 666f8a4c901SWarner Losh20020831: 667f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 668f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 669f8a4c901SWarner Losh programs and libraries need to be recompiled. 670f8a4c901SWarner Losh 671f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 672f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 673f8a4c901SWarner Losh 674c2248fa2SJens Schweikhardt20020827: 675c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 676c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 677c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 678c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 679c2248fa2SJens Schweikhardt 6800d533e43SRuslan Ermilov20020815: 6810d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 6820d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 6830d533e43SRuslan Ermilov again. 6840d533e43SRuslan Ermilov 68533c1de7dSRuslan Ermilov20020729: 68633c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 68733c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 68833c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 68933c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 69033c1de7dSRuslan Ermilov 6912b877facSJulian Elischer20020702: 6922b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 6932b877facSJulian Elischer There are still some minor problems with some signals but the 6942b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 6952b877facSJulian Elischer but each can successfully complete multiple buildworlds. 6962b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 6972b877facSJulian Elischer 69806596d37SWarner Losh20020701: 69906596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 70006596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 70106596d37SWarner Losh GNOME. 70206596d37SWarner Losh 70395ba4330SJacques Vidrine20020511: 70495ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 70595ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 70695ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 70795ba4330SJacques Vidrine with the set-user-ID bit set. 70895ba4330SJacques Vidrine 709a81da3c9SDavid E. O'Brien20020510: 710f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 711f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 7124b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 713f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 714f50caf6fSDavid E. O'Brien 715f50caf6fSDavid E. O'Brien20020510: 716a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 717a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 718a81da3c9SDavid E. O'Brien and then do a cvs update. 719a81da3c9SDavid E. O'Brien 720528a0ef5SJacques Vidrine20020421: 721528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 722528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 723528a0ef5SJacques Vidrine 72485aa5a2eSGregory Neil Shapiro20020404: 72585aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 72685aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 72785aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 72885aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 72985aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 73085aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 73185aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 73285aa5a2eSGregory Neil Shapiro 7338f1e4358SRuslan Ermilov20020403: 7348f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 7358f1e4358SRuslan Ermilov 7362292c02eSWarner Losh20020315: 7372292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 7382292c02eSWarner Losh 73969f7bcf3SWarner Losh20020225: 74069f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 74169f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 74269f7bcf3SWarner Losh 7438f35c493SWarner Losh20020217: 7448f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 7458f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 7468f35c493SWarner Losh command line mail submission has changed. Be sure to run 7478f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 7488f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 7498f35c493SWarner Losh 750835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 751835284beSWarner Losh required in order for sendmail to run as a set-group-ID 752835284beSWarner Losh binary. A 'make installworld' will use the new user and group 753835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 754835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 755835284beSWarner Losh and group must be merged from src/etc/group and 756835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 757835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 758835284beSWarner Losh mergemaster before this will work if you are updating from a 759835284beSWarner Losh very old version of current. The updating recipe has changed 760835284beSWarner Losh as of this date. 761835284beSWarner Losh 762fa9401c1SWarner Losh20020112: 763fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 764fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 765fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 766fa9401c1SWarner Losh you have local modifications, you can use 767fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 768fa9401c1SWarner Losh /etc/pam.d. 769fa9401c1SWarner Losh 770fa9401c1SWarner Losh Please see the following url for more details: 771fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 77247d0d01fSWarner Losh20011229: 77347d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 77447d0d01fSWarner Losh networkfs_types, please note that it has changed 77547d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 77647d0d01fSWarner Losh 777514318a8SWarner Losh20011220: 778514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 779514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 780514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 781514318a8SWarner Losh own. All the accumulated features and bug fixes of the i4b 782514318a8SWarner Losh version have now been merged back into the base system's 783514318a8SWarner Losh version now. The only user-visible change resulting from this 784514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 785514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 786514318a8SWarner Losh as well. (There has never been rc file support for 787514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 788514318a8SWarner Losh reverted by the time the changes are MFCed.) 789514318a8SWarner Losh 790514318a8SWarner Losh20011215: 791514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 792514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 793514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 794514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 795514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 796514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 797514318a8SWarner Losh will need to be customized then for `odd' densities using 798514318a8SWarner Losh fdcontrol(8). 799514318a8SWarner Losh 8002d22e2bfSWarner Losh20011209: 8012d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 8022d22e2bfSWarner Losh and truss(1) now works again. 8032d22e2bfSWarner Losh 8049e0428e2SWarner Losh20011207: 8059e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 8069e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 8079e0428e2SWarner Losh see 8089e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 8099e0428e2SWarner Losh for details. 8109e0428e2SWarner Losh 8119bab8c59SWarner Losh20011204: 8129bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 8139bab8c59SWarner Losh kernel and burncd to be in sync. 8149bab8c59SWarner Losh 815e57d8b01SWarner Losh20011203: 816e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 817e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 818e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 819e57d8b01SWarner Losh not there already. 820e57d8b01SWarner Losh 821e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 822e57d8b01SWarner Losh until the issue has been resolved. 823e57d8b01SWarner Losh 824b001d36fSJacques Vidrine20011202: 825b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 826b001d36fSJacques Vidrine patched. 827b001d36fSJacques Vidrine 8284b676ec1SWarner Losh20011126: 8294b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 8305ebbf43eSWarner Losh after this date. You need to do this only once. 8314b676ec1SWarner Losh 832d961e462SWarner Losh20011103: 833d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 834d961e462SWarner Losh edges may be left, but for the most part things should be 8354b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 836d961e462SWarner Losh 837d961e462SWarner Losh20011030: 838d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 839d961e462SWarner Losh choppy waves in the upgrade process. 840d961e462SWarner Losh 8411fe003b6SWarner Losh20011030: 842a4b6fda0SWarner Losh The asr driver problem has been resolved. 8431fe003b6SWarner Losh 8441fe003b6SWarner Losh20011027: 8451fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 8461fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 8471fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 8481fe003b6SWarner Losh try to use from this date forward. 8491fe003b6SWarner Losh 8501fe003b6SWarner Losh20011025: 8511fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 8521fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 8531fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 8541fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 8551fe003b6SWarner Losh TARGET_ARCH=i386. 8561fe003b6SWarner Losh 857d05f9643SWarner Losh20011001: 858d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 859d05f9643SWarner Losh You must recompile both the kernel and userland applications 860d05f9643SWarner Losh at the same time. 861d05f9643SWarner Losh 86258970f85SWarner Losh20010929: 86358970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 86458970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 86558970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 86658970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 8679d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 86858970f85SWarner Losh 86958970f85SWarner Losh20010927: 87058970f85SWarner Losh Some weird problems result from using ACPI on some machines. 87158970f85SWarner Losh To disable ACPI you can add 87266ff0e67SMax Khon hint.acpi.0.disabled="1" 87358970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 87458970f85SWarner Losh loader "ok" prompt). 87558970f85SWarner Losh 87658970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 87758970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 87858970f85SWarner Losh file and not list acpi in that list. 879378f4486SAlfred Perlstein 8805119d237SWarner Losh20010924: 8815119d237SWarner Losh The buildworld has been fixed. You may need to install 8825119d237SWarner Losh the 4.x compatibility libraries for some old binaries 8838b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 8848b039fffSWarner Losh get them installed on every installworld, or execute the 8858b039fffSWarner Losh following to get them installed only once: 8868b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 88758970f85SWarner Losh make all install 8888b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 8895119d237SWarner Losh 8903c293725SWarner Losh20010919: 8913c293725SWarner Losh There's a bug in the world build process. The cross-tools 8923c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 8933c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 894772730c7SWarner Losh workaround is to add 8953c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 8963c293725SWarner Losh before building world when upgrading from 4.x to current. This 8973c293725SWarner Losh can be removed afterwards. 8983c293725SWarner Losh 8993c293725SWarner Losh A proper fix to the buildworld target is needed. 9003c293725SWarner Losh 9013c293725SWarner Losh20010918: 9023c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 9033c293725SWarner Losh NFS may be unstable after this date. 9043c293725SWarner Losh 9053c293725SWarner Losh20010912: 9063c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 9073c293725SWarner Losh the kernel. While a few problems were introduced in the 9083c293725SWarner Losh initial commit, most of the major ones have been found and 9093c293725SWarner Losh corrected. 9103c293725SWarner Losh 9113c293725SWarner Losh20010901: 9123c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 9133c293725SWarner Losh arounds described in the 20010604 entry are now no longer 9143c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 9153c293725SWarner Losh have been rectified around this date. 9163c293725SWarner Losh 91798b17b95SWarner Losh20010823: 91898b17b95SWarner Losh named now runs as user bind and group bind rather than as 91998b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 92098b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 92198b17b95SWarner Losh and that group bind is available in /etc/group. Also make 92298b17b95SWarner Losh sure that user or group bind has read (and not write) 92398b17b95SWarner Losh permission for your name server configuration and that it 92498b17b95SWarner Losh has read and write permission for your slave zone files and 92598b17b95SWarner Losh directory. 92698b17b95SWarner Losh 92798b17b95SWarner Losh If you wish to continue to run named as root (a less secure 92898b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 92998b17b95SWarner Losh 93098b17b95SWarner Losh named_flags= 93198b17b95SWarner Losh 9327b9786edSMark Murray20010709: 9337b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 9347b9786edSMark Murray the ability of the shared library major number to handle. 9357b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 9367b9786edSMark Murray solution is to rebuild those ports. 9377b9786edSMark Murray 9381d28950eSWarner Losh20010628: 9391d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 9401d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 9411d28950eSWarner Losh 942e72fd46aSWarner Losh20010625: 94398b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 94498b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 94598b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 94698b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 94798b17b95SWarner Losh IRQ configuration needs more safety belts. 94816de1a07SWarner Losh 9490d415dffSWarner Losh20010617: 950e72fd46aSWarner Losh Softupdates problems have been corrected. 9510d415dffSWarner Losh 9520d415dffSWarner Losh20010614: 9530d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 9540d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 9550d415dffSWarner Losh kernel building methods. 9560d415dffSWarner Losh 9578b9959adSWarner Losh20010613: 9588b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 9598b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 960e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 961e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 9628b9959adSWarner Losh 963e72fd46aSWarner Losh20010613: 9648b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 965e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 966e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 9678b9959adSWarner Losh 9680d415dffSWarner Losh20010612: 9690d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 9700d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 9710d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 9720d415dffSWarner Losh work around this issue, please use only one or the other mechanism 9730d415dffSWarner Losh until this bug is fixed. 9740d415dffSWarner Losh 975e72fd46aSWarner Losh Please note that a feature of config is that if you have config 976e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 977ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 978e72fd46aSWarner Losh 9790d415dffSWarner Losh20010610: 9800d415dffSWarner Losh Locale names have changed to match other systems better. 9810d415dffSWarner Losh 9826ccdb5e4SWarner Losh20010604: 9836ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 9846ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 9856ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 9863590182eSWarner Losh Interrupt storms look a lot like a hang. 9873590182eSWarner Losh 9883590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 9893590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 9903590182eSWarner Losh it is). 9913590182eSWarner Losh 9923590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 9933590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 9943590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 9953590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 9966ccdb5e4SWarner Losh 9970bc62786SWarner Losh20010530: 9980bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 9990bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 10000bc62786SWarner Losh a limited time. If you see 10010bc62786SWarner Losh 10020bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 10030bc62786SWarner Losh 10040bc62786SWarner Losh in your makeworld, then you need to migrate towards using 10050bc62786SWarner Losh COPY=-C. 10060bc62786SWarner Losh 100768a38c6cSWarner Losh20010525: 1008b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 1009c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 1010c4f4a728SWarner Losh definitely is in bad shape. 101168a38c6cSWarner Losh 1012ed0f29caSWarner Losh20010521: 1013ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 1014ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 1015ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 1016ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 1017ed0f29caSWarner Losh is 1018ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 1019ed0f29caSWarner Losh 102080c16af9SWarner Losh20010520: 102168a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 102280c16af9SWarner Losh 102380c16af9SWarner Losh20010519: 102480c16af9SWarner Losh pccard has had much reorganizational work done to it over 102580c16af9SWarner Losh the past few days. Everything should still work, but if 102680c16af9SWarner Losh not, please contact imp@freebsd.org. 102780c16af9SWarner Losh 1028a45f2d05SWarner Losh20010517: 1029a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 1030a45f2d05SWarner Losh userland at the same time. 1031a45f2d05SWarner Losh 1032a45f2d05SWarner Losh20010517: 1033a45f2d05SWarner Losh New ncurses imported. 1034a45f2d05SWarner Losh 10352988afcaSWarner Losh20010512: 10362988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 10372988afcaSWarner Losh will be the only way to go starting July 1. 10382988afcaSWarner Losh 10391a33dba7SWarner Losh20010504: 10401a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 10411a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 10421a33dba7SWarner Losh 104309946a51SWarner Losh20010502: 104409946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 104509946a51SWarner Losh 104609946a51SWarner Losh20010501: 104709946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 104809946a51SWarner Losh 104909946a51SWarner Losh20010430: 1050a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 105109946a51SWarner Losh go back in the water. 105209946a51SWarner Losh 105309946a51SWarner Losh20010429: 105409946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 105509946a51SWarner Losh this date, but before the correction date. 105609946a51SWarner Losh 105791dd3b53SWarner Losh20010423: 105891dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 105991dd3b53SWarner Losh 106091dd3b53SWarner Losh20010411: 106191dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 106291dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 106391dd3b53SWarner Losh Update only if you understand that you must not use the old 106491dd3b53SWarner Losh fsck with the new kernel ever. 106591dd3b53SWarner Losh 1066933b3269SWarner Losh20010330: 1067933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 1068c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 1069933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 1070933b3269SWarner Losh 1071933b3269SWarner Losh20010319: 1072933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 1073933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 1074933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 1075f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 107609946a51SWarner Losh 107709946a51SWarner Losh20010315: 107809946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 1079ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 108009946a51SWarner Losh been replaced by tunables. See ata.4 for details. 1081933b3269SWarner Losh 1082933b3269SWarner Losh20010312: 1083933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 1084933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 1085933b3269SWarner Losh 1086933b3269SWarner Losh20010312: 1087933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 1088933b3269SWarner Losh instead of ad-hoc. 1089933b3269SWarner Losh 1090933b3269SWarner Losh20010310: 1091f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 1092933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 1093933b3269SWarner Losh ssh might not work if you don't. 1094933b3269SWarner Losh 109562353691SWarner Losh20010303: 109662353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 109762353691SWarner Losh which means that you must include the miibus in your kernel if 109862353691SWarner Losh you use the ed driver. 109962353691SWarner Losh 1100d325cf65SWarner Losh20010220: 1101d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 1102d325cf65SWarner Losh safe to go back into the water. 1103d325cf65SWarner Losh 1104024daae6SWarner Losh20010211: 1105024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 1106024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 1107024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 1108024daae6SWarner Losh that before upgrading would be a good time to do a level 0 1109024daae6SWarner Losh dump of your system. No, really, I mean it this time. 1110024daae6SWarner Losh 1111024daae6SWarner Losh To get to the new system, you'll need to use the following 1112024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 1113024daae6SWarner Losh don't have to move this to the updating section. 1114024daae6SWarner Losh 1115024daae6SWarner Losh To get around the installworld problem, do: 1116024daae6SWarner Losh # cd /usr/src/usr.bin/sed 1117024daae6SWarner Losh # make install 1118024daae6SWarner Losh # cd /usr/src 1119024daae6SWarner Losh # make installworld 1120024daae6SWarner Losh If that doesn't work, then try: 1121024daae6SWarner Losh # make -k installworld 1122024daae6SWarner Losh # make installworld 1123024daae6SWarner Losh 1124024daae6SWarner Losh20010207: 1125024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 1126024daae6SWarner Losh do not include devfs in your kernel as problems result. 1127024daae6SWarner Losh 1128024daae6SWarner Losh20010205: 11297595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 1130024daae6SWarner Losh Remove them from your config. 1131024daae6SWarner Losh 11321e159248SWarner Losh20010122: 11331e159248SWarner Losh ****************************** WARNING ****************************** 11341e159248SWarner Losh buildkernel has been changed slightly 11351e159248SWarner Losh ****************************** WARNING ****************************** 11361e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 11371e159248SWarner Losh should update your scripts and make.conf accordingly. 11381e159248SWarner Losh 11391e159248SWarner Losh20010119: 11401e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 11411e159248SWarner Losh This requires a new config to build correctly. 11421e159248SWarner Losh 1143aac7dfeaSWarner Losh20010116: 1144ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 1145aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 1146aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 1147aac7dfeaSWarner Losh 1148aac7dfeaSWarner Losh20010110: 1149aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 1150aac7dfeaSWarner Losh 1151aac7dfeaSWarner Losh20010102: 1152aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 1153aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 1154aac7dfeaSWarner Losh 115563c90c9eSWarner Losh20010101: 115663c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 115763c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 11585fd2a895SWarner Losh dump while building termcap. You can work around this problem 115963c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 116063c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 116163c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 116263c90c9eSWarner Losh might have been ignored by the -k option. 116363c90c9eSWarner Losh 11645fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 11655fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 11665fd2a895SWarner Losh of this working. 11675fd2a895SWarner Losh 1168aac7dfeaSWarner Losh20001228: 1169aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 1170ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 1171aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 1172aac7dfeaSWarner Losh 1173de2bcc63SWarner Losh20001218: 1174de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 1175de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 1176de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 1177de2bcc63SWarner Losh cards will not be recognized without it. 1178de2bcc63SWarner Losh 1179960773f7SWarner Losh20001205: 1180960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 1181960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 1182960773f7SWarner Losh adding the following in pam.conf: 1183960773f7SWarner Losh 1184960773f7SWarner Losh sshd auth sufficient pam_skey.so 1185960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 1186960773f7SWarner Losh sshd session required pam_permit.so 1187960773f7SWarner Losh 11880acc635eSWarner Losh20001031: 11890acc635eSWarner Losh cvs updated to 1.11. 11900acc635eSWarner Losh 11910acc635eSWarner Losh20001020: 11920acc635eSWarner Losh The random device needs more entropy, so you need to make sure 11930acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 11940acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 11950acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 11960acc635eSWarner Losh workaround. 11970acc635eSWarner Losh 11980acc635eSWarner Losh20001010: 11990acc635eSWarner Losh ****************************** WARNING ****************************** 12000acc635eSWarner Losh Sendmail has been updated. 12010acc635eSWarner Losh ****************************** WARNING ****************************** 12020acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 12030acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 12040acc635eSWarner Losh is set. 12050acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 12060acc635eSWarner Losh commands. 12070acc635eSWarner Losh o Now using sendmail's version of vacation(1). 12080acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 12090acc635eSWarner Losh in /usr/share/sendmail/cf. 12100acc635eSWarner Losh o sendmail.cw changed to local-host-names 12110acc635eSWarner Losh 12120acc635eSWarner Losh More details can be found at 12130acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 12140acc635eSWarner Losh 12156e98a146SWarner Losh20001009: 12166e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 12176e98a146SWarner Losh your entire ports tree, or you will have problems. 12186e98a146SWarner Losh 12196e98a146SWarner Losh20001006: 1220685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 12216e98a146SWarner Losh the installed miniperl. It is recommended that you delete 12226e98a146SWarner Losh /usr/bin/miniperl. 12236e98a146SWarner Losh 1224073113a4SWarner Losh20001005: 1225073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1226685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1227073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1228073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1229073113a4SWarner Losh tree for anything to work. 1230073113a4SWarner Losh 12310acc635eSWarner Losh20000928: 12320acc635eSWarner Losh There was a change in the passwd format. Need more information. 12330acc635eSWarner Losh 1234be3885b3SWarner Losh20000916: 1235be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1236be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1237be3885b3SWarner Losh same time as your kernel. 1238be3885b3SWarner Losh 123976ec9675SWarner Losh20000914: 124076ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 124176ec9675SWarner Losh include the device will cause suspended laptops losing time 124276ec9675SWarner Losh when they resume. Include 124376ec9675SWarner Losh device pmtimer 124476ec9675SWarner Losh in your config file and 124501b9a434SWarner Losh hint.pmtimer.0.at="isa" 124676ec9675SWarner Losh to your /boot/device.hints file. 124776ec9675SWarner Losh 1248f4865386SMark Murray20000911: 1249f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1250f4865386SMark Murray rather than an option. The supplied kernel config files have 1251f4865386SMark Murray been updated. You will need to do something similar in your 1252f4865386SMark Murray own kernel config file. 1253f4865386SMark Murray Remove: 1254f4865386SMark Murray options RANDOMDEV 1255f4865386SMark Murray Add: 1256f4865386SMark Murray device random 1257f4865386SMark Murray If you prefer to load the loadable module, you need to do 1258f4865386SMark Murray nothing. 1259f4865386SMark Murray 1260d594498fSWarner Losh20000909: 1261d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1262d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1263d594498fSWarner Losh reflect this if you load this module at boot time. 1264d594498fSWarner Losh The line should read: 1265d594498fSWarner Losh random_load="YES" 1266d594498fSWarner Losh 12670deb7ddcSWarner Losh20000907: 12680deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 126916eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 127016eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 127116eb772dSWarner Losh sure you don't have model loading problems which might at 127216eb772dSWarner Losh first blush appear related to SMP. 127352bf24e7SWarner Losh 12745a01880bSWarner Losh20000906: 12755a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 12765a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 12775a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 12785a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 12795a01880bSWarner Losh don't have one, and you have host.conf. 12805a01880bSWarner Losh 12812b41163cSWarner Losh20000905: 128238d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 128338d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 128438d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 128538d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 128638d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 128738d6ecd2SWarner Losh 128838d6ecd2SWarner Losh20000905: 12898aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 12908aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 12918aab4bc7SWarner Losh is /boot/kernel. 12928aab4bc7SWarner Losh 12938aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 129438d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 129538d6ecd2SWarner Losh installkernel/installworld dance. 12962b41163cSWarner Losh 1297d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1298d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1299d594498fSWarner Losh modules in that directory instead of finding them in the correct 1300d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1301d594498fSWarner Losh is that the linux module crashes your machine after the update. 1302d594498fSWarner Losh 1303d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1304d594498fSWarner Losh mv /modules.old /boot/kernel.old 1305d594498fSWarner Losh chflags noschg /kernel.old 1306d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1307d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1308d594498fSWarner Losh fi 1309d594498fSWarner Losh 1310c22a309cSWarner Losh20000904: 1311c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1312c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1313c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1314c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1315c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1316c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1317c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1318c22a309cSWarner Losh is not likely to be generated. 1319c22a309cSWarner Losh 1320fdb9f54dSWarner Losh20000825: 1321fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 13229c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 13239c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 13249c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 13259c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 13269c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 13279c1a7444SWarner Losh messages will appear after the boot loader tries to start the 13289c1a7444SWarner Losh kernel. 13299c1a7444SWarner Losh 13309c1a7444SWarner Losh20000821: 13319c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 13329c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 13339c1a7444SWarner Losh /boot/loader.conf. 1334fdb9f54dSWarner Losh 13358f250aa7SWarner Losh20000812: 13365da0d091SWarner Losh suidperl is now always built and installed on the system, but 13375da0d091SWarner Losh with permissions of 511. If you have applications that use 13385da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 13395da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 13405da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 13415da0d091SWarner Losh will fix this until the next build. 13425da0d091SWarner Losh 13435da0d091SWarner Losh20000812: 13448f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 13458f250aa7SWarner Losh visible changes that may immediately affect your configuration 13468f250aa7SWarner Losh include: 13478f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 13488f250aa7SWarner Losh - newaliases limited to root and trusted users 13498f250aa7SWarner Losh - MSA port (587) turned on by default 13508f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 13518f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 13528f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 13538f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 13548f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 13558f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 13568f250aa7SWarner Losh 135771c38472SWarner Losh20000810: 135871c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 135971c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 136071c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 136171c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 136271c38472SWarner Losh specific use for it. 136371c38472SWarner Losh 136471c38472SWarner Losh20000729: 136571c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 136671c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 136771c38472SWarner Losh /etc/rc.conf if they want to have the same setup 136871c38472SWarner Losh afterwards (unless the variables already are set, of course): 136971c38472SWarner Losh # Enable network daemons for user convenience. 137071c38472SWarner Losh inetd_enable="YES" 137171c38472SWarner Losh portmap_enable="YES" 137271c38472SWarner Losh sendmail_enable="YES" 137371c38472SWarner Losh 137471c38472SWarner Losh20000728: 137571c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 137671c38472SWarner Losh will need to change that to nullfs_load="YES". 137771c38472SWarner Losh 13781dece4a9SWarner Losh20000728: 13791dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 13801dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 13811dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 13821dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 13831dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 13841dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 13851dece4a9SWarner Losh to /MYKERNEL. 13861dece4a9SWarner Losh 1387409e887cSWarner Losh20000711: 1388409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1389409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1390409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1391409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1392409e887cSWarner Losh for details on potential problems that you might have and how 1393409e887cSWarner Losh to get around them. 1394409e887cSWarner Losh 1395409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1396409e887cSWarner Losh clauses above, you needn't worry. 1397409e887cSWarner Losh 1398409e887cSWarner Losh20000711: 1399409e887cSWarner Losh /etc/security has been updated to print the inode number of 1400409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1401409e887cSWarner Losh in the number of changed programs the first time when you run 1402409e887cSWarner Losh mergemaster to get a new /etc/security. 1403409e887cSWarner Losh 1404673d13f2SWarner Losh20000710: 1405673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1406673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1407673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1408673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1409673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1410673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1411673d13f2SWarner Losh errors. (see below, 20000624). 1412673d13f2SWarner Losh 1413bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 14141dece4a9SWarner Losh 1415673d13f2SWarner Losh20000709: 1416c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1417c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1418c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1419673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1420673d13f2SWarner Losh 1421e98e26cdSWarner Losh20000706: 1422e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1423e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1424e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1425f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1426e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 14272c021c6cSMark Ovens interim if needed. 1428e98e26cdSWarner Losh 1429e98e26cdSWarner Losh20000705: 1430e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1431e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1432e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1433e98e26cdSWarner Losh details. 1434e98e26cdSWarner Losh 1435c373950eSWarner Losh20000704: 14362f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 14372f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 14382f961bc8SWarner Losh 14392f961bc8SWarner Losh20000704: 1440c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1441c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1442c373950eSWarner Losh rc.d scripts that haven't been updated. 1443c373950eSWarner Losh 144427dc3a2bSWarner Losh20000630: 144527dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 144627dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 144727dc3a2bSWarner Losh which should be reported to des@freebsd.org. 144827dc3a2bSWarner Losh 1449b8c215acSWarner Losh20000625: 1450b8c215acSWarner Losh From approximately this date forward, one must have the crypto 145127dc3a2bSWarner Losh system installed in order to build the system and kernel. 145227dc3a2bSWarner Losh While not technically strictly true, one should treat it as 145327dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 145427dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 145527dc3a2bSWarner Losh were required. You should check with the latest collections 145627dc3a2bSWarner Losh to make sure that these haven't changed. 1457b8c215acSWarner Losh 14587b990719SWarner Losh20000624: 14597b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 14607b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 14617b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 14621a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 14637b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 14647b990719SWarner Losh openssh and openssl should not be used to generate keys from this 14657b990719SWarner Losh date to the completion of the work. 14667b990719SWarner Losh 146727dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 146827dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 146927dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 147027dc3a2bSWarner Losh recreate the random and urandom devices. 147127dc3a2bSWarner Losh 147281e54c50SWarner Losh20000622: 147381e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 147481e54c50SWarner Losh BSD license. You may need to remove your symbolic links 147581e54c50SWarner Losh that used to be required when updating. 147681e54c50SWarner Losh 147739943833SWarner Losh20000621: 14782c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 14792a2f33fbSDaniel Baker the config file update procedure. 14802a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1481c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 148259df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 148359df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 148439943833SWarner Losh 1485290f9ad8SWarner Losh20000620: 1486290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1487290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1488290f9ad8SWarner Losh that workaround will no longer be required. 1489290f9ad8SWarner Losh 149090fb6346SWarner Losh20000615: 149190fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 149290fb6346SWarner Losh ad driver. If you haven't done so already, you must update 149390fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 149490fb6346SWarner Losh devices. 149590fb6346SWarner Losh 1496f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1497f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1498f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1499f75f65bbSWarner Losh may work). 1500f75f65bbSWarner Losh 1501ba26da8eSWarner Losh20000612: 1502ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1503290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1504c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1505290f9ad8SWarner Losh to your config file to compile them in statically. The format 1506f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1507f54a3542SWarner Losh NEWCARD for examples of the new format. 1508290f9ad8SWarner Losh 15099698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 15109698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 15119698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 15129698f2c0SWarner Losh in it. 1513bbcc5149SWarner Losh 1514d65850ebSWarner Losh20000522: 1515ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1516d65850ebSWarner Losh building a kernel after this point is advised that they need 1517d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1518d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1519d65850ebSWarner Losh 1520d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1521d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1522d9583a00SWarner Losh is recommended that you don't set this option until the problem 1523d9583a00SWarner Losh is resolved. 1524d9583a00SWarner Losh 15258039cedeSWarner Losh20000513: 15268039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 15278039cedeSWarner Losh 1528d65850ebSWarner Losh20000510: 15298039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 15308039cedeSWarner Losh This will require some care in updating alphas. A new libstand 15318039cedeSWarner Losh is requires for the boot blocks to build properly. 15328039cedeSWarner Losh 15338039cedeSWarner Losh20000503: 15348039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 15358039cedeSWarner Losh is now available. 15368039cedeSWarner Losh 1537d65850ebSWarner Losh20000502: 1538d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1539d65850ebSWarner Losh connected to the kernel building instead. 1540d65850ebSWarner Losh 1541be149406SNik Clayton20000427: 15428039cedeSWarner Losh You may need to build gperf 15438039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 15448039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 15458039cedeSWarner Losh an option only in -current. 15468039cedeSWarner Losh 15472b8dd5f4SWarner Losh20000417: 15482b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1549f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 15502b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 15512b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 15522c021c6cSMark Ovens before you reboot, you'll need to issue: 15532b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 15542b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 15552b8dd5f4SWarner Losh 15568d9f1945SWarner Losh20000320: 15572b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 15582b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 15592b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1560ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 15612b8dd5f4SWarner Losh to the start of /etc/rc.conf. 15628d9f1945SWarner Losh 1563f8ab1dd6SWarner Losh20000319: 1564f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1565f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1566f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1567f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1568f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1569f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1570f8ab1dd6SWarner Losh 157119cada77SWarner Losh20000318: 1572f699bbbbSMark Ovens We've entered the traditional post release dumping party. 157319cada77SWarner Losh Large kernel changes are being committed and are in the 157419cada77SWarner Losh works. It is important to keep the systems' klds and kernel 157519cada77SWarner Losh in sync as kernel interfaces and structures are changing. 157619cada77SWarner Losh Before reporting kernel panics, make sure that all modules 157719cada77SWarner Losh that you are loading are up to date. 1578ba228352SWarner Losh 157919cada77SWarner Losh20000315: 15806d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 15816d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 15826d23c382SWarner Losh will do the trick. This isn't critical until you remove your 15836d23c382SWarner Losh wd device entries in /dev, at which point your system will not 15846d23c382SWarner Losh boot. 15856d23c382SWarner Losh 15866d23c382SWarner Losh20000315: 158719cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 158819cada77SWarner Losh to upgrade to 4.0 from 3.x. 158957199806SWarner Losh 1590dc0dbf5cSWarner LoshCOMMON ITEMS: 1591dc0dbf5cSWarner Losh 1592cd5f061cSWarner Losh # NOTE: 5.x below applies to 6.0-currrent as well, for the 1593cd5f061cSWarner Losh # momemnt. 4.any -> 5.any upgrade support will remain in 1594cd5f061cSWarner Losh # place for 6.0 current, but after 5.3 RELEASE, the 4.any -> 1595cd5f061cSWarner Losh # 6.0-current upgrade path will require moving through 5.3 1596cd5f061cSWarner Losh # RELEASE or newer. 1597cd5f061cSWarner Losh 1598a24eff53SWarner Losh General Notes 1599a24eff53SWarner Losh ------------- 1600a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1601a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1602a24eff53SWarner Losh installworld. This is especially true when upgrading between 1603a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1604a24eff53SWarner Losh or several minor releases, or when several months have passed 1605a24eff53SWarner Losh on the -current branch). 1606a24eff53SWarner Losh 16075780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 16085780f3baSWarner Losh poisoning. This can happen because the make utility reads its 16095780f3baSWarner Losh environment when searching for values for global variables. 16105780f3baSWarner Losh To run your build attempts in an "environmental clean room", 16115780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 16125780f3baSWarner Losh page for more details. 16135780f3baSWarner Losh 1614dc0dbf5cSWarner Losh To build a kernel 1615dc0dbf5cSWarner Losh ----------------- 1616ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1617f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1618ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1619282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1620282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1621dc0dbf5cSWarner Losh 1622ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1623ba01eb20SWarner Losh -------------------------------------------------------------- 16240fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 16250fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 16260fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 16270fbd2da9SKen Smith 16280fbd2da9SKen Smith cd src/sys/${arch}/conf 162947d0d01fSWarner Losh config KERNEL_NAME_HERE 16300fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1631ba01eb20SWarner Losh make depend 1632ba01eb20SWarner Losh make 1633ba01eb20SWarner Losh make install 1634ba01eb20SWarner Losh 1635ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1636ba01eb20SWarner Losh 1637ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1638ba01eb20SWarner Losh ----------------------------------------------------------- 163963cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 164063cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 164163cb445eSWarner Losh 1642f643de42SWarner Losh <make sure you have good level 0 dumps> 164363cb445eSWarner Losh <maybe fix /etc/fstab> [7] 164463cb445eSWarner Losh make buildworld 16456586253aSWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE 164663cb445eSWarner Losh [1] 164763cb445eSWarner Losh <reboot in single user> [3] 16486586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 164963cb445eSWarner Losh mergemaster -p [5] 165063cb445eSWarner Losh make installworld 165163cb445eSWarner Losh mergemaster [4] 165263cb445eSWarner Losh <reboot> 165363cb445eSWarner Losh 1654759f0aefSWarner Losh 1655f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1656f27b1fceSJoseph Koshy -------------------------------------------------- 1657f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1658f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1659f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1660f27b1fceSJoseph Koshy # size. 1661f27b1fceSJoseph Koshy 1662f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1663f27b1fceSJoseph Koshy <boot into -stable> 1664f27b1fceSJoseph Koshy make buildworld 1665f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1666f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1667f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1668f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 16696586253aSWarner Losh cp src/sys/${ARCH}/conf/GENERIC.hints \ 1670f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1671f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 16726586253aSWarner Losh cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1673f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1674f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1675f27b1fceSJoseph Koshy <reboot into current> 1676f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 16776586253aSWarner Losh <maybe install compatibility libraries from src/lib/compat> 1678f27b1fceSJoseph Koshy <reboot> 1679f27b1fceSJoseph Koshy 1680f27b1fceSJoseph Koshy 1681f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1682f27b1fceSJoseph Koshy ---------------------------------------------- 16835c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 16845c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 16855c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 16865c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1687ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1688f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1689f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1690f643de42SWarner Losh # space on /. 1691f643de42SWarner Losh 1692f643de42SWarner Losh <make sure you have good level 0 dumps> 1693fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 169421c075eaSWarner Losh make buildworld [9] 1695c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1696802fc49dSBrian Feldman cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1697be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1698802fc49dSBrian Feldman cd sys/boot ; make STRIP="" install [6] 1699fc8c157fSWarner Losh [1] 1700fc8c157fSWarner Losh <reboot in single user> [3] 17016586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 1702835284beSWarner Losh mergemaster -p [5] 1703f8a4c901SWarner Losh rm -rf /usr/include/g++ 1704ba26da8eSWarner Losh make installworld 1705802fc49dSBrian Feldman mergemaster -i [4] 1706ba26da8eSWarner Losh <reboot> 1707ba26da8eSWarner Losh 1708fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1709fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1710fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1711fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1712fdb9f54dSWarner Losh the UPDATING entries. 1713ba26da8eSWarner Losh 17141dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 17151dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 17161dece4a9SWarner Losh your sources that you have read and understood all the recent 17171dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 17181dece4a9SWarner Losh much fewer pitfalls. 17191dece4a9SWarner Losh 1720134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1721134d2e86SWarner Losh should disable them at this point so they don't crash your 1722134d2e86SWarner Losh system on reboot. 1723134d2e86SWarner Losh 17249c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 17259c1a7444SWarner Losh your own device.hints to reflect your unique hardware 17269c1a7444SWarner Losh configuration. 17279c1a7444SWarner Losh 1728ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1729ee6e1fc3SWarner Losh fsck -p 1730ee6e1fc3SWarner Losh mount -u / 1731ee6e1fc3SWarner Losh mount -a 17326586253aSWarner Losh cd src 173347d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1734f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1735f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 173666986952SRuslan Ermilov For the 4.x -> 5.x upgrade, you will also see many messages about 1737b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1738b705ae10SWarner Losh be ignored while you proceed to the next step. 1739ee6e1fc3SWarner Losh 1740a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1741a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1742a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1743a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1744a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1745a6cd4f9dSWarner Losh for potential gotchas. 1746a6cd4f9dSWarner Losh 1747835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1748835284beSWarner Losh you may need to do this if you get unknown user in the following 1749835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1750835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1751835284beSWarner Losh install) after the buildworld before this step if you last updated 1752835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1753835284beSWarner Losh 1754bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1755bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1756bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1757bd79cf40SWarner Losh ok unload 1758bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1759bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1760bd79cf40SWarner Losh described here. 1761fc8c157fSWarner Losh 1762fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1763fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1764fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1765fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1766fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1767fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1768fc8c157fSWarner Losh 1769c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1770c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1771c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1772c74fe6afSWarner Losh that is hard to boot to recover. 1773c74fe6afSWarner Losh 177421c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 1775802fc49dSBrian Feldman cvs prune empty directories. Also, if CPUTYPE is defined in your 1776802fc49dSBrian Feldman /etc/make.conf, make sure to use the "?=" instead of the "=" assignment 1777802fc49dSBrian Feldman operator, so that buildworld can override the CPUTYPE if it needs to. 1778802fc49dSBrian Feldman In case you would like to avoid installing new packages of everything, 1779802fc49dSBrian Feldman you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 178066986952SRuslan Ermilov compatibility libraries are built which should allow you to continue 1781802fc49dSBrian Feldman using your existing software for a while. 17828633bbeaSBrooks Davis 17838633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 17846586253aSWarner Losh initialized by feeding data into it. src/etc/rc.d/preseedrandom 17858633bbeaSBrooks Davis takes care of this. 1786dc0dbf5cSWarner LoshFORMAT: 1787dc0dbf5cSWarner Losh 1788f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 17891fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1790f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1791f8ab1dd6SWarner Loshprevious releases if your system is older than this. 17921fc1a0dcSWarner Losh 1793e72fd46aSWarner LoshCopyright information: 1794e72fd46aSWarner Losh 17959698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1796e72fd46aSWarner Losh 1797772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1798772730c7SWarner Loshmodification, in full or in part, in any form or format of this 17999698f2c0SWarner Loshdocument are permitted without further permission from the author. 1800e72fd46aSWarner Losh 1801e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1802e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1803e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1804e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1805e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1806e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1807e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1808e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1809e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1810e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1811e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1812e72fd46aSWarner Losh 1813e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1814e72fd46aSWarner Loshauthor a beer. 1815e72fd46aSWarner Losh 181622306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1817772730c7SWarner Loshthis document. 1818772730c7SWarner Losh 181997d92980SPeter Wemm$FreeBSD$ 1820