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 264ff62bd9SBrooks Davis20040902: 274ff62bd9SBrooks Davis The ifi_epoch change has been reverted because the ABI breakage 284ff62bd9SBrooks Davis was too extensive. If you are running with a kernel/userland 294ff62bd9SBrooks Davis containing the initial change (20040830), you should heed the 304ff62bd9SBrooks Davis warning about ifconfig incompatibility when upgrading again. 314ff62bd9SBrooks Davis With this change, 5.3 and 6.0 ifconfigs and kernels are once 324ff62bd9SBrooks Davis again interoperable. 334ff62bd9SBrooks Davis 341fc4519bSBrooks Davis20040830: 351fc4519bSBrooks Davis A new variable, ifi_epoch, has been added to struct if_data 361fc4519bSBrooks Davis which is part if struct ifnet. This means all network drivers 371fc4519bSBrooks Davis and network monitoring applications need to be recompiled. 381fc4519bSBrooks Davis 393789fb75SBrooks Davis WARNING WARNING WARNING WARNING WARNING WARNING WARNING 403789fb75SBrooks Davis 413789fb75SBrooks Davis This also breaks ifconfig compatibility. An old ifconfig will 423789fb75SBrooks Davis not work with the new kernel and a new ifconfig will not work 433789fb75SBrooks Davis with the old. It is strongly recommended that you make a copy 443789fb75SBrooks Davis of your old ifconfig before installworld. If you are installing 453789fb75SBrooks Davis remotely, you must copy over a new ifconfig before rebooting in 463789fb75SBrooks Davis to the new kernel. 473789fb75SBrooks Davis 48c1c94d5cSRobert Watson20040828: 49c1c94d5cSRobert Watson The default configuration for the network stack has been changed 50c1c94d5cSRobert Watson such that it now runs without the Giant lock unless configured 51c1c94d5cSRobert Watson otherwise. If you experience network-related instability, you 52c1c94d5cSRobert Watson may wish to try setting "debug.mpsafenet=0" or compiling the 53c1c94d5cSRobert Watson kernel with "options NET_WITH_GIANT". Details on the netperf 54c1c94d5cSRobert Watson project may be found at: 55c1c94d5cSRobert Watson 56c1c94d5cSRobert Watson http://www.watson.org/~robert/freebsd/netperf/ 57c1c94d5cSRobert Watson 58c1c94d5cSRobert Watson Including the 20040828 announcement of configuration change 59c1c94d5cSRobert Watson details. 60c1c94d5cSRobert Watson 61c21fd232SAndre Oppermann20040827: 62c21fd232SAndre Oppermann PFIL_HOOKS are a fixed part of the network stack now and do not 63c21fd232SAndre Oppermann need to be specified in the kernel configuration file anymore. 64c21fd232SAndre Oppermann 65f036d408SJulian Elischer20040819: 66f036d408SJulian Elischer Netgraph changed its message format slightly to align the data 67f036d408SJulian Elischer portion well on 64 bit machines. 68f036d408SJulian Elischer Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd, 69f036d408SJulian Elischer pppoed, bluetooth, ATM) should be recompiled when a new kernel 70f036d408SJulian Elischer is installed. 71f036d408SJulian Elischer 72b067abfaSAndre Oppermann20040817: 730ce70eb4SAndre Oppermann IPFW has been converted to use PFIL_HOOKS. This change is 74b067abfaSAndre Oppermann transparent to userland and preserves the ipfw ABI. The ipfw 75b067abfaSAndre Oppermann core packet inspection and filtering functions have not been 76b067abfaSAndre Oppermann changed, only how ipfw is invoked is different. Note that 77b067abfaSAndre Oppermann "option PFIL_HOOKS" is required to use IPFIREWALL compiled 78b067abfaSAndre Oppermann into the kernel or as KLD. 79b067abfaSAndre Oppermann 80f13a7951SDavid Malone20040814: 81f13a7951SDavid Malone The RANDOM_IP_ID option has been replaced by the sysctl 82f13a7951SDavid Malone net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then 83f13a7951SDavid Malone you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf. 84f13a7951SDavid Malone 853a004637SMax Laier20040807: 863a004637SMax Laier The size of 'struct ifnet' has changed due to the addition of the 873a004637SMax Laier if_carp placeholder. All kernel modules implementing network 883a004637SMax Laier interfaces must be recompiled as a result. 893a004637SMax Laier 904f34d8d1SJohn-Mark Gurney20040806: 914f34d8d1SJohn-Mark Gurney Module loading has been fixed. Some older installations will 92ac41c814SRuslan Ermilov drop proper module_path initialization and modules will fail to 934f34d8d1SJohn-Mark Gurney load properly. If you have a line in /boot/loader.rc that says: 944f34d8d1SJohn-Mark Gurney "initialize drop", do (i386 only): 954f34d8d1SJohn-Mark Gurney cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc 964f34d8d1SJohn-Mark Gurney chown root:wheel /boot/loader.rc 974f34d8d1SJohn-Mark Gurney chmod 444 /boot/loader.rc 984f34d8d1SJohn-Mark Gurney 998f075db4SMark Murray20040802: 1008f075db4SMark Murray making /dev/(null|zero) into a module proved to be too unpopular, 1018f075db4SMark Murray so this bit has been revoked from the previous (20040801) entry. 1028f075db4SMark Murray 103d064d6dbSMark Murray20040801: 104d064d6dbSMark Murray The /dev/mem, /dev/io /dev/(null/zero) devices are now modules, 105d064d6dbSMark Murray so you may wish to add them to your kernel config file. See 106d064d6dbSMark Murray GENERIC for examples. 107d064d6dbSMark Murray 108b289983eSAlexander Kabaev20040728: 10954bd5271SAlexander Kabaev System compiler has been upgraded to GCC 3.4.2-pre. As with any major 11054bd5271SAlexander Kabaev compiler upgrade, there are several issues to be aware of. GCC 3.4.x 11154bd5271SAlexander Kabaev has broken C++ ABI compatibility with previous releases yet again 11254bd5271SAlexander Kabaev and users will have to rebuild all their C++ programs with the new 113d0e54ab4SDavid E. O'Brien compiler. If you are getting run-time error such as 114d0e54ab4SDavid E. O'Brien /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE" 115d0e54ab4SDavid E. O'Brien This entry does apply to you. 116d0e54ab4SDavid E. O'Brien 117d0e54ab4SDavid E. O'Brien A new unit-at-a-time optimization mode, which is default in this 118d0e54ab4SDavid E. O'Brien compiler release, is more aggressive in removing unused static 119d0e54ab4SDavid E. O'Brien symbols. This is the likely cause of 'make buildworld' breakages 120cd5f061cSWarner Losh with non-default CFLAGS where optimization level is set to -O2 121cd5f061cSWarner Losh or higher. 12254bd5271SAlexander Kabaev 1236e1afae3SWarner Losh With the upgrade of the system compiler, the kernel has been upgraded 1246e1afae3SWarner Losh to match the new system compiler. This makes it impossible to build 1256e1afae3SWarner Losh a new kernel with the old compiler. Upgrade your system via 1266e1afae3SWarner Losh make buildworld and make kernel (see below) to fix this problem. 1276e1afae3SWarner Losh 12836ed21e6SRobert Watson20040727: 12936ed21e6SRobert Watson The size of 'struct ifnet' has changed due to the addition of 13036ed21e6SRobert Watson the IFF_NEEDSGIANT flag (and what it implies). All kernel 13136ed21e6SRobert Watson modules implementing network interfaces must be recompiled as 13236ed21e6SRobert Watson a result. 13336ed21e6SRobert Watson 1346305ac24SSeigo Tanimura20040716: 1356305ac24SSeigo Tanimura The sound device drivers are renamed. `sound' is always required, 1366305ac24SSeigo Tanimura while `snd_*' should be configured accordingly to your hardware. 1376305ac24SSeigo Tanimura Refer to NOTES for the detail of the drivers. 1386305ac24SSeigo Tanimura 139e623dcb7SMarcel Moolenaar20040710: 140e623dcb7SMarcel Moolenaar __FreeBSD_version bumped to 502122. 141e623dcb7SMarcel Moolenaar 142e623dcb7SMarcel Moolenaar20040710: 143e623dcb7SMarcel Moolenaar The console initialization on Alpha has been reworked and is now 144e623dcb7SMarcel Moolenaar identical to other platforms. This means that the hardcoding of 145e623dcb7SMarcel Moolenaar the serial console and the debug port has been removed. As such, 146e623dcb7SMarcel Moolenaar hints are now required for the sio(4) driver to become a console 147e623dcb7SMarcel Moolenaar or debug port. The NO_SIO option has been decommissioned because 148e623dcb7SMarcel Moolenaar of this. 149e623dcb7SMarcel Moolenaar 150e623dcb7SMarcel Moolenaar20040710: 151e623dcb7SMarcel Moolenaar A revamp of the debugging code in the kernel with some visible 152e623dcb7SMarcel Moolenaar changes beyond just the debugging experience: 153e623dcb7SMarcel Moolenaar o The DDB option is now specific to the DDB debugger backend 154e623dcb7SMarcel Moolenaar and should not be used any more for conditional compilation 155e623dcb7SMarcel Moolenaar of debugging code for when debugging is enabled. Use the KDB 156e623dcb7SMarcel Moolenaar option for this. 157e623dcb7SMarcel Moolenaar o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have 158e623dcb7SMarcel Moolenaar been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED 159e623dcb7SMarcel Moolenaar respectively. This is in line with the first bullet. 160e623dcb7SMarcel Moolenaar o The remote GDB support has been untangled from DDB and needs 1615bd7ce0aSJens Schweikhardt to be enabled separately now. Use the GDB option for this. 162e623dcb7SMarcel Moolenaar o The GDB_REMOTE_CHAT option has been removed. Support for this 163e623dcb7SMarcel Moolenaar homegrown feature is discontinued. The GDB remote protocol 164e623dcb7SMarcel Moolenaar supports console output and it makes sense to use that. 165e623dcb7SMarcel Moolenaar o The DDB_NOKLDSYM option has been removed. The DDB debugger 166e623dcb7SMarcel Moolenaar now supports both direct symbol table lookups as well as KLD 167e623dcb7SMarcel Moolenaar symbol lookups through the linker. 168e623dcb7SMarcel Moolenaar 1696421d1dbSMaksim Yevmenkin20040708: 1706421d1dbSMaksim Yevmenkin Bluetooth code has been marked as non-i386 specific. 1716421d1dbSMaksim Yevmenkin __FreeBSD_version has been bumped to 502121 to mark this change. 1726421d1dbSMaksim Yevmenkin 17358af3216SWarner Losh20040702: 17458af3216SWarner Losh The native preemption has been added to the kernel scheduler. 1755bd7ce0aSJens Schweikhardt There is some report that the ULE scheduler was broken in some 1765bd7ce0aSJens Schweikhardt machines and we encourage users using the ULE scheduler either 1775bd7ce0aSJens Schweikhardt stick with a known good kernel, or temporarily switch to the 4BSD 17858af3216SWarner Losh scheduler as a workaround. 17958af3216SWarner Losh 180c2dba668SNate Lawson20040630: 1818ed370fdSJulian Elischer The netgraph ABI version number has been incremented to indicate 1828ed370fdSJulian Elischer an incompatible change in the ABI. Old netgraph nodes will refuse 183a6c26e1cSBruce M Simpson to attach until recompiled. Netgraph now uses mbuf tags to move 184a6c26e1cSBruce M Simpson metadata and this commit removes its home-grown metadata facility. 185a6c26e1cSBruce M Simpson Nodes should just recompile, unless they use metadata, in which 186a6c26e1cSBruce M Simpson case the changes are simple; the file ng_ksocket.c serves as an 187a6c26e1cSBruce M Simpson example of such changes. 1888ed370fdSJulian Elischer 18958af3216SWarner Losh This also broke i4b, although the compile problem has been papered 19058af3216SWarner Losh over. 19158af3216SWarner Losh 1928ed370fdSJulian Elischer20040630: 193c2dba668SNate Lawson ACPI has been updated to disable known-bad BIOS revisions. A message 1945bd7ce0aSJens Schweikhardt will be printed on the console indicating that ACPI has been disabled 195c2dba668SNate Lawson automatically and that the user should use a newer BIOS, if possible. 196c2dba668SNate Lawson If you think ACPI does work on your system and want to override 197c2dba668SNate Lawson this (i.e., for testing), set hint.acpi.0.disabled="0" at the 198c2dba668SNate Lawson loader prompt. 199c2dba668SNate Lawson 2008ee2ac9eSMax Laier20040623: 2015bd7ce0aSJens Schweikhardt pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege 2028ee2ac9eSMax Laier separated now. It uses the newly created "_pflogd" user/group 2038ee2ac9eSMax Laier combination. If you plan to use pflogd(8) make sure to run 2048ee2ac9eSMax Laier mergemaster -p or install the "_pflogd" user and group manually. 2058ee2ac9eSMax Laier 2063db5687dSBrooks Davis20040622: 2073db5687dSBrooks Davis Network interface cloning has been overhauled. This change will 2083db5687dSBrooks Davis require a recompile of modules using cloning and modification of 2093db5687dSBrooks Davis external ones to the new API. __FreeBSD_version has been bumped 2103db5687dSBrooks Davis to 502119 to mark this change. Additionally, users creating 2113db5687dSBrooks Davis stf(4) interfaces via "ifconfig stf" will need to update their 2123db5687dSBrooks Davis scripts as this will create an interface named "stf" instead of 2133db5687dSBrooks Davis "stf0" and ifconfig will not print "stf0" to stdout. 2143db5687dSBrooks Davis 215e0ae81f3SDag-Erling Smørgrav20040621: 216e0ae81f3SDag-Erling Smørgrav On 20040524, the /etc/rc.d/nsswitch script was modified to 217e0ae81f3SDag-Erling Smørgrav automatically create /etc/nsswitch.conf on startup if it did 218e0ae81f3SDag-Erling Smørgrav not already exist. Unfortunately, an error in the man page 219e0ae81f3SDag-Erling Smørgrav was carried over to the script, resulting in incorrect 220e0ae81f3SDag-Erling Smørgrav nsswitch settings. The simplest remedy is to remove both 221e0ae81f3SDag-Erling Smørgrav /etc/nsswitch.conf and /etc/host.conf; they will be recreated 222e0ae81f3SDag-Erling Smørgrav during the next reboot. 223e0ae81f3SDag-Erling Smørgrav 2244717d22aSJohn Polstra20040614: 2254717d22aSJohn Polstra The return value of sema_timedwait(9) has been changed to 2264717d22aSJohn Polstra make it consistent with cv_timedwait(9). Be sure to recompile 2274717d22aSJohn Polstra the ips module and any third-party modules which call 2284717d22aSJohn Polstra sema_timedwait. 2294717d22aSJohn Polstra 2306cb7a382SMax Laier20040613: 2316cb7a382SMax Laier ALTQ is now linked to the build. This breaks ABI for struct ifnet. 2326cb7a382SMax Laier Make sure to recompile modules and any userland that makes use of 233df843493SMax Laier sizeof(struct ifnet). In order to get the altq headers in place 234df843493SMax Laier please recompile and reinstall world. 2356cb7a382SMax Laier 2362454685eSJulian Elischer20040607: 2372454685eSJulian Elischer Splitting kern_thread.c into 2 files (adding kern_kse.c) 2382454685eSJulian Elischer requires that you re-run config after updating your tree. 2392454685eSJulian Elischer 24064fef830SSeigo Tanimura20040601: 24164fef830SSeigo Tanimura The MIDI drivers have been removed. Until the new module-friendly 24264fef830SSeigo Tanimura ones are merged, remove or comment out midi and seq from your 24364fef830SSeigo Tanimura kernel configuration. 24464fef830SSeigo Tanimura 245bb4f06e7SAndre Oppermann20040423: 246bb4f06e7SAndre Oppermann Due to a new option in ipfw (versrcreach) the ipfw(8) command 247bb4f06e7SAndre Oppermann needs to be recompiled. Normal accept/reject rules without 248bb4f06e7SAndre Oppermann options are not affected but those with options may break until 249bb4f06e7SAndre Oppermann ipfw(8) is recompiled. 250bb4f06e7SAndre Oppermann 25105641e82SColin Percival20040420: 25205641e82SColin Percival Due to changes in the callout ABI, kernels compiled after this 25305641e82SColin Percival date may be incompatible with kernel modules compiled prior to 25405641e82SColin Percival 20040406. 25505641e82SColin Percival 256d0dc9183SWarner Losh20040414: 257d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 258d0dc9183SWarner Losh problems for your system, please disable it using the tunable 259d0dc9183SWarner Losh hw.pci.do_powerstate=0. 260d0dc9183SWarner Losh 261d0dc9183SWarner Losh20040412: 262d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 263d0dc9183SWarner Losh drive is still broken. 264d0dc9183SWarner Losh 265d0dc9183SWarner Losh20040410: 266d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 267d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 268d0dc9183SWarner Losh the unanticipated problems have been resolved. 269d0dc9183SWarner Losh 2708633bbeaSBrooks Davis20040409: 2718633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 2728633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 2738633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 2748633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 27576c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 2768633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 2778633bbeaSBrooks Davis 278d40d033aSRobert Watson20040322: 279d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 280d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 281d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 282d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 283d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 284d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 285d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 286d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 287d40d033aSRobert Watson locking is merged to permit this to take place. 288d40d033aSRobert Watson 289ec9b318eSGarance A Drosehn20040310: 290ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 291ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 292ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 293ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 294ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 295ec9b318eSGarance A Drosehn 296fc28f1ffSMax Laier20040308: 297fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 298fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 2994c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 3004c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 301fc28f1ffSMax Laier Also note that pf requires "options PFIL_HOOKS" in the kernel. The 302fc28f1ffSMax Laier pf system consists of the following three devices: 303fc28f1ffSMax Laier device pf # required 304fc28f1ffSMax Laier device pflog # optional 305fc28f1ffSMax Laier device pfsync # optional 306fc28f1ffSMax Laier 3073aff5d06SDag-Erling Smørgrav20040303: 3083aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 3093aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 3103aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 3113aff5d06SDag-Erling Smørgrav 3123aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 3133aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 3143aff5d06SDag-Erling Smørgrav 3153aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 3163aff5d06SDag-Erling Smørgrav to use libpthread instead. 3173aff5d06SDag-Erling Smørgrav 318fd63c5b3SDag-Erling Smørgrav20040226: 3199d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 320fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 321fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 322fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 323fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 324fd63c5b3SDag-Erling Smørgrav 325714ae42aSBruce M Simpson20040225: 326e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 327e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 328e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 329e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 330e07a40f3SBrian Feldman should remain unaffected. 331e07a40f3SBrian Feldman 332e07a40f3SBrian Feldman20040225: 333714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 334714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 335714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 336714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 337714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 338714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 339714ae42aSBruce M Simpson 340fbd2e692SAndre Oppermann20040224: 341fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 3425bd7ce0aSJens Schweikhardt and related userland network utilities necessary. 343fbd2e692SAndre Oppermann 344158b90daSWarner Losh20040222: 345158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 346158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 347158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 348158b90daSWarner Losh Drivers outside the tree will need to be updated. 349158b90daSWarner Losh 350b7b1e150SMike Makonnen20040207: 351b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 352b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 353b7b1e150SMike Makonnen 354aca89ee6SDaniel Eischen20040130: 355aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 356aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 357aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 358aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 359aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 360aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 361aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 362aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 363aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 364aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 365aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 366aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 367aca89ee6SDaniel Eischen do not work with libpthread. 368aca89ee6SDaniel Eischen 36968b7b3a9SAlex Dupre20040125: 37068b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 37168b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 37268b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 37368b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 37468b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 37568b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 37668b7b3a9SAlex Dupre 377ff46e0deSWarner Losh20040125: 378ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 379ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 380ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 381ff46e0deSWarner Losh 382ce41f4bfSRobert Watson20031213: 383ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 384ce41f4bfSRobert Watson if the login process is unable to successfully set the 385ce41f4bfSRobert Watson process credentials to include all groups defined for the 386ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 387ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 388ce41f4bfSRobert Watson defined, or they will be unable to log in. 389ce41f4bfSRobert Watson 390c124fa05SJohn Baldwin20031203: 391c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 392c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 393c124fa05SJohn Baldwin 3948ad1f5e4SHartmut Brandt20031112: 39530093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 39630093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 39797209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 39897209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 39997209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 40097209ca3SRobert Watson not know about the new system calls that support the new statfs 4013f631d52SMarcel Moolenaar structure. 4023f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 4033f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 4043f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 4053f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 4063f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 4073f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 4083f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 4093f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 4103f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 4113f631d52SMarcel Moolenaar these changes are installed. 41230093b05SWarner Losh 41330093b05SWarner Losh ****************************DANGER******************************* 41430093b05SWarner Losh 41530093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 41630093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 41730093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 41830093b05SWarner Losh kernel. 41964a18d6fSKirk McKusick 42064a18d6fSKirk McKusick20031112: 4218ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 4228ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 4238ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 4248ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 4258ad1f5e4SHartmut Brandt sync before rebooting. 4268ad1f5e4SHartmut Brandt 427c53a5d8fSJohn Baldwin20031111: 428c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 429c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 430c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 431c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 432c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 433c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 434c53a5d8fSJohn Baldwin 4358bf455a5SJohn Baldwin20031103: 4368bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 4378bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 4382a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 4398bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 4408bf455a5SJohn Baldwin 4419bf40edeSBrooks Davis20031031: 4429bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 4439bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 4449bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 4459bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 4469bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 4479bf40edeSBrooks Davis reflect this change. 4489bf40edeSBrooks Davis 44947a42c7aSPoul-Henning Kamp20030928: 45047a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 45147a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 4525bd7ce0aSJens Schweikhardt __FreeBSD_version bumped to 501110. 45347a42c7aSPoul-Henning Kamp 45407105342SMax Khon20030926: 45507105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 45607105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 45707105342SMax Khon 45817dcd026SSam Leffler20030925: 45917dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 46017dcd026SSam Leffler also be explicitly configured. Previously this dependency was 46117dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 46217dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 46317dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 46417dcd026SSam Leffler 465fedf1d01SBruce M Simpson20030923: 466fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 467fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 468fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 469fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 470fedf1d01SBruce M Simpson 471db38f9cbSJacques Vidrine20030915: 472db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 473db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 474db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 475db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 476db38f9cbSJacques Vidrine 477c09d2c2bSMike Makonnen20030829: 478c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 479c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 480c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 481c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 482c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 483c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 484c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 485c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 486c09d2c2bSMike Makonnen may or may not exist on your system. 487c09d2c2bSMike Makonnen 48817c159dcSSøren Schmidt20030824: 48917c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 49017c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 491f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 492f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 49317c159dcSSøren Schmidt 494c1f61aa9SDavid E. O'Brien20030819: 495c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 496c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 497c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 498c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 49969f7bcf3SWarner Losh 50038c962e7SNate Lawson20030728: 50138c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 50238c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 50338c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 50438c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 50538c962e7SNate Lawson so the quirk can be re-enabled. 50638c962e7SNate Lawson 50774111097SWarner Losh20030724: 50874111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 50974111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 51074111097SWarner Losh 511178cf4e9SWarner Losh20030722: 512178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 513178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 514178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 515178cf4e9SWarner Losh FPU hardware. 516178cf4e9SWarner Losh 517178cf4e9SWarner Losh20030714: 518178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 519178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 520178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 521178cf4e9SWarner Losh People should report those issues to current@. 522178cf4e9SWarner Losh 523157c629aSWarner Losh20030711: 524157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 5258b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 52605538fa9SWarner Losh /usr/obj. 527157c629aSWarner Losh 52874111097SWarner Losh20030610: 52974111097SWarner Losh Remove deprecated locale names and transition period code 53074111097SWarner Losh for them, finishing switching to the new scheme. Check your 53174111097SWarner Losh LANG environment variable. 53274111097SWarner Losh 53374111097SWarner Losh20030609: 53474111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 53574111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 53674111097SWarner Losh important to remember beforehand if your source tree is on 53774111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 53874111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 53974111097SWarner Losh kernel. 54074111097SWarner Losh 54174111097SWarner Losh20030605: 5426cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 5436cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 5446cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 5456cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 5466cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 5476cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 5486cc6353fSMarcel Moolenaar 5496cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 5506cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 5516cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 5526cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 5536cc6353fSMarcel Moolenaar : 5546cc6353fSMarcel Moolenaar 5556cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 5566cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 5576cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 5586cc6353fSMarcel Moolenaar 55952b47445SMark Murray20030505: 56052b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 56152b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 56252b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 56352b47445SMark Murray 564a26df538SWarner Losh20030502: 565a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 566a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 567a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 568a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 569a26df538SWarner Losh 5704b065e2cSDoug Barton20030501: 5714b065e2cSDoug Barton The old rc system has been removed. Please report any problems 5724b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 5734b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 5744b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 5754b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 5764b065e2cSDoug Barton utilizes these old scripts has also been removed. 5774b065e2cSDoug Barton 57881cda3d9SWarner Losh20030423: 57981cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 58081cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 58181cda3d9SWarner Losh work around in devd will be removed around 20030507. You 58281cda3d9SWarner Losh have until then to upgrade your kernel before updating 58381cda3d9SWarner Losh userland. In general, you should have a userland and 58481cda3d9SWarner Losh kernel that's in sync with each other. However, given the 58581cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 58681cda3d9SWarner Losh allowances are made. 58781cda3d9SWarner Losh 58847a657d1SRuslan Ermilov20030329: 58947a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 59047a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 59147a657d1SRuslan Ermilov while upgrading the system through a buildworld. 59247a657d1SRuslan Ermilov 59347a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 59447a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 59547a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 59647a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 59747a657d1SRuslan Ermilov 59847a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 59947a657d1SRuslan Ermilov make cleandir && make obj && \ 60047a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 60147a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 60247a657d1SRuslan Ermilov 6035d2af00cSGregory Neil Shapiro20030208: 6045d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 6055d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 6065d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 6075d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 6085d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 6095d2af00cSGregory Neil Shapiro 6105d2af00cSGregory Neil Shapiro20030128: 6119db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 612ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 6139db58771SPoul-Henning Kamp be removed when convenient. 6149db58771SPoul-Henning Kamp 6158d9b3f57SJake Burkholder20030126: 6168d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 6178d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 6188d9b3f57SJake Burkholder 6191c5efda5SJeff Roberson20030125: 6201c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 6211c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 622ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 6231c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 6241c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 6251c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 6261c5efda5SJeff Roberson 6279d1d64f5SWarner Losh20030115: 6289d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 6299d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 6309d1d64f5SWarner Losh properly. 6319d1d64f5SWarner Losh 632c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 633c9fdb80aSWarner Losh configured for point to point links to bring it more in line 634c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 635c9fdb80aSWarner Losh with NetBSD. 636c9fdb80aSWarner Losh 637161dc364SAlexander Kabaev20021222: 638161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 639161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 640161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 641161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 642161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 643161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 64484cc83efSAlexander Kabaev rebuilt. 645161dc364SAlexander Kabaev 646fb4c8061SMartin Blapp20021216: 647fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 64889056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 649fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 6509d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 651fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 652fb4c8061SMartin Blapp 65317d47eb3SGiorgos Keramidas20021202: 65417d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 65517d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 65617d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 65717d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 65817d47eb3SGiorgos Keramidas 659a4459294SBill Fenner20021029: 660a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 661a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 662a4459294SBill Fenner consumers in sync. 663a4459294SBill Fenner 664fc8c157fSWarner Losh20021024: 665c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 666c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 667c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 668c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 669c57404feSRuslan Ermilov partition really is on. The old device names have gone 670c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 671c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 672c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 67369f7bcf3SWarner Losh 674fd9e8bdaSAndrew Gallatin20021023: 675fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 676fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 677fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 678fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 679fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 680fd9e8bdaSAndrew Gallatin 681fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 682fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 683fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 684fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 685fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 686fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 687fd9e8bdaSAndrew Gallatin 688f8a4c901SWarner Losh20020831: 689f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 690f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 691f8a4c901SWarner Losh programs and libraries need to be recompiled. 692f8a4c901SWarner Losh 693f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 694f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 695f8a4c901SWarner Losh 696c2248fa2SJens Schweikhardt20020827: 697c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 698c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 699c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 700c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 701c2248fa2SJens Schweikhardt 7020d533e43SRuslan Ermilov20020815: 7030d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 7040d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 7050d533e43SRuslan Ermilov again. 7060d533e43SRuslan Ermilov 70733c1de7dSRuslan Ermilov20020729: 70833c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 70933c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 71033c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 71133c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 71233c1de7dSRuslan Ermilov 7132b877facSJulian Elischer20020702: 7142b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 7152b877facSJulian Elischer There are still some minor problems with some signals but the 7162b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 7172b877facSJulian Elischer but each can successfully complete multiple buildworlds. 7182b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 7192b877facSJulian Elischer 72006596d37SWarner Losh20020701: 72106596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 72206596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 72306596d37SWarner Losh GNOME. 72406596d37SWarner Losh 72595ba4330SJacques Vidrine20020511: 72695ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 72795ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 72895ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 72995ba4330SJacques Vidrine with the set-user-ID bit set. 73095ba4330SJacques Vidrine 731a81da3c9SDavid E. O'Brien20020510: 732f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 733f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 7344b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 735f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 736f50caf6fSDavid E. O'Brien 737f50caf6fSDavid E. O'Brien20020510: 738a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 739a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 740a81da3c9SDavid E. O'Brien and then do a cvs update. 741a81da3c9SDavid E. O'Brien 742528a0ef5SJacques Vidrine20020421: 743528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 744528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 745528a0ef5SJacques Vidrine 74685aa5a2eSGregory Neil Shapiro20020404: 74785aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 74885aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 74985aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 75085aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 75185aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 75285aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 75385aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 75485aa5a2eSGregory Neil Shapiro 7558f1e4358SRuslan Ermilov20020403: 7568f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 7578f1e4358SRuslan Ermilov 7582292c02eSWarner Losh20020315: 7592292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 7602292c02eSWarner Losh 76169f7bcf3SWarner Losh20020225: 76269f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 76369f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 76469f7bcf3SWarner Losh 7658f35c493SWarner Losh20020217: 7668f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 7678f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 7688f35c493SWarner Losh command line mail submission has changed. Be sure to run 7698f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 7708f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 7718f35c493SWarner Losh 772835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 773835284beSWarner Losh required in order for sendmail to run as a set-group-ID 774835284beSWarner Losh binary. A 'make installworld' will use the new user and group 775835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 776835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 777835284beSWarner Losh and group must be merged from src/etc/group and 778835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 779835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 780835284beSWarner Losh mergemaster before this will work if you are updating from a 781835284beSWarner Losh very old version of current. The updating recipe has changed 782835284beSWarner Losh as of this date. 783835284beSWarner Losh 784fa9401c1SWarner Losh20020112: 785fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 786fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 787fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 788fa9401c1SWarner Losh you have local modifications, you can use 789fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 790fa9401c1SWarner Losh /etc/pam.d. 791fa9401c1SWarner Losh 792fa9401c1SWarner Losh Please see the following url for more details: 793fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 79447d0d01fSWarner Losh20011229: 79547d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 79647d0d01fSWarner Losh networkfs_types, please note that it has changed 79747d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 79847d0d01fSWarner Losh 799514318a8SWarner Losh20011220: 800514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 801514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 802514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 803514318a8SWarner Losh own. All the accumulated features and bug fixes of the i4b 804514318a8SWarner Losh version have now been merged back into the base system's 805514318a8SWarner Losh version now. The only user-visible change resulting from this 806514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 807514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 808514318a8SWarner Losh as well. (There has never been rc file support for 809514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 810514318a8SWarner Losh reverted by the time the changes are MFCed.) 811514318a8SWarner Losh 812514318a8SWarner Losh20011215: 813514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 814514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 815514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 816514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 817514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 818514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 819514318a8SWarner Losh will need to be customized then for `odd' densities using 820514318a8SWarner Losh fdcontrol(8). 821514318a8SWarner Losh 8222d22e2bfSWarner Losh20011209: 8232d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 8242d22e2bfSWarner Losh and truss(1) now works again. 8252d22e2bfSWarner Losh 8269e0428e2SWarner Losh20011207: 8279e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 8289e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 8299e0428e2SWarner Losh see 8309e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 8319e0428e2SWarner Losh for details. 8329e0428e2SWarner Losh 8339bab8c59SWarner Losh20011204: 8349bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 8359bab8c59SWarner Losh kernel and burncd to be in sync. 8369bab8c59SWarner Losh 837e57d8b01SWarner Losh20011203: 838e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 839e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 840e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 841e57d8b01SWarner Losh not there already. 842e57d8b01SWarner Losh 843e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 844e57d8b01SWarner Losh until the issue has been resolved. 845e57d8b01SWarner Losh 846b001d36fSJacques Vidrine20011202: 847b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 848b001d36fSJacques Vidrine patched. 849b001d36fSJacques Vidrine 8504b676ec1SWarner Losh20011126: 8514b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 8525ebbf43eSWarner Losh after this date. You need to do this only once. 8534b676ec1SWarner Losh 854d961e462SWarner Losh20011103: 855d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 856d961e462SWarner Losh edges may be left, but for the most part things should be 8574b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 858d961e462SWarner Losh 859d961e462SWarner Losh20011030: 860d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 861d961e462SWarner Losh choppy waves in the upgrade process. 862d961e462SWarner Losh 8631fe003b6SWarner Losh20011030: 864a4b6fda0SWarner Losh The asr driver problem has been resolved. 8651fe003b6SWarner Losh 8661fe003b6SWarner Losh20011027: 8671fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 8681fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 8691fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 8701fe003b6SWarner Losh try to use from this date forward. 8711fe003b6SWarner Losh 8721fe003b6SWarner Losh20011025: 8731fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 8741fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 8751fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 8761fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 8771fe003b6SWarner Losh TARGET_ARCH=i386. 8781fe003b6SWarner Losh 879d05f9643SWarner Losh20011001: 880d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 881d05f9643SWarner Losh You must recompile both the kernel and userland applications 882d05f9643SWarner Losh at the same time. 883d05f9643SWarner Losh 88458970f85SWarner Losh20010929: 88558970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 88658970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 88758970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 88858970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 8899d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 89058970f85SWarner Losh 89158970f85SWarner Losh20010927: 89258970f85SWarner Losh Some weird problems result from using ACPI on some machines. 89358970f85SWarner Losh To disable ACPI you can add 89466ff0e67SMax Khon hint.acpi.0.disabled="1" 89558970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 89658970f85SWarner Losh loader "ok" prompt). 89758970f85SWarner Losh 89858970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 89958970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 90058970f85SWarner Losh file and not list acpi in that list. 901378f4486SAlfred Perlstein 9025119d237SWarner Losh20010924: 9035119d237SWarner Losh The buildworld has been fixed. You may need to install 9045119d237SWarner Losh the 4.x compatibility libraries for some old binaries 9058b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 9068b039fffSWarner Losh get them installed on every installworld, or execute the 9078b039fffSWarner Losh following to get them installed only once: 9088b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 90958970f85SWarner Losh make all install 9108b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 9115119d237SWarner Losh 9123c293725SWarner Losh20010919: 9133c293725SWarner Losh There's a bug in the world build process. The cross-tools 9143c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 9153c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 916772730c7SWarner Losh workaround is to add 9173c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 9183c293725SWarner Losh before building world when upgrading from 4.x to current. This 9193c293725SWarner Losh can be removed afterwards. 9203c293725SWarner Losh 9213c293725SWarner Losh A proper fix to the buildworld target is needed. 9223c293725SWarner Losh 9233c293725SWarner Losh20010918: 9243c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 9253c293725SWarner Losh NFS may be unstable after this date. 9263c293725SWarner Losh 9273c293725SWarner Losh20010912: 9283c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 9293c293725SWarner Losh the kernel. While a few problems were introduced in the 9303c293725SWarner Losh initial commit, most of the major ones have been found and 9313c293725SWarner Losh corrected. 9323c293725SWarner Losh 9333c293725SWarner Losh20010901: 9343c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 9353c293725SWarner Losh arounds described in the 20010604 entry are now no longer 9363c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 9373c293725SWarner Losh have been rectified around this date. 9383c293725SWarner Losh 93998b17b95SWarner Losh20010823: 94098b17b95SWarner Losh named now runs as user bind and group bind rather than as 94198b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 94298b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 94398b17b95SWarner Losh and that group bind is available in /etc/group. Also make 94498b17b95SWarner Losh sure that user or group bind has read (and not write) 94598b17b95SWarner Losh permission for your name server configuration and that it 94698b17b95SWarner Losh has read and write permission for your slave zone files and 94798b17b95SWarner Losh directory. 94898b17b95SWarner Losh 94998b17b95SWarner Losh If you wish to continue to run named as root (a less secure 95098b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 95198b17b95SWarner Losh 95298b17b95SWarner Losh named_flags= 95398b17b95SWarner Losh 9547b9786edSMark Murray20010709: 9557b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 9567b9786edSMark Murray the ability of the shared library major number to handle. 9577b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 9587b9786edSMark Murray solution is to rebuild those ports. 9597b9786edSMark Murray 9601d28950eSWarner Losh20010628: 9611d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 9621d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 9631d28950eSWarner Losh 964e72fd46aSWarner Losh20010625: 96598b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 96698b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 96798b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 96898b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 96998b17b95SWarner Losh IRQ configuration needs more safety belts. 97016de1a07SWarner Losh 9710d415dffSWarner Losh20010617: 972e72fd46aSWarner Losh Softupdates problems have been corrected. 9730d415dffSWarner Losh 9740d415dffSWarner Losh20010614: 9750d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 9760d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 9770d415dffSWarner Losh kernel building methods. 9780d415dffSWarner Losh 9798b9959adSWarner Losh20010613: 9808b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 9818b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 982e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 983e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 9848b9959adSWarner Losh 985e72fd46aSWarner Losh20010613: 9868b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 987e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 988e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 9898b9959adSWarner Losh 9900d415dffSWarner Losh20010612: 9910d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 9920d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 9930d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 9940d415dffSWarner Losh work around this issue, please use only one or the other mechanism 9950d415dffSWarner Losh until this bug is fixed. 9960d415dffSWarner Losh 997e72fd46aSWarner Losh Please note that a feature of config is that if you have config 998e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 999ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 1000e72fd46aSWarner Losh 10010d415dffSWarner Losh20010610: 10020d415dffSWarner Losh Locale names have changed to match other systems better. 10030d415dffSWarner Losh 10046ccdb5e4SWarner Losh20010604: 10056ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 10066ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 10076ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 10083590182eSWarner Losh Interrupt storms look a lot like a hang. 10093590182eSWarner Losh 10103590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 10113590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 10123590182eSWarner Losh it is). 10133590182eSWarner Losh 10143590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 10153590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 10163590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 10173590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 10186ccdb5e4SWarner Losh 10190bc62786SWarner Losh20010530: 10200bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 10210bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 10220bc62786SWarner Losh a limited time. If you see 10230bc62786SWarner Losh 10240bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 10250bc62786SWarner Losh 10260bc62786SWarner Losh in your makeworld, then you need to migrate towards using 10270bc62786SWarner Losh COPY=-C. 10280bc62786SWarner Losh 102968a38c6cSWarner Losh20010525: 1030b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 1031c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 1032c4f4a728SWarner Losh definitely is in bad shape. 103368a38c6cSWarner Losh 1034ed0f29caSWarner Losh20010521: 1035ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 1036ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 1037ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 1038ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 1039ed0f29caSWarner Losh is 1040ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 1041ed0f29caSWarner Losh 104280c16af9SWarner Losh20010520: 104368a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 104480c16af9SWarner Losh 104580c16af9SWarner Losh20010519: 104680c16af9SWarner Losh pccard has had much reorganizational work done to it over 104780c16af9SWarner Losh the past few days. Everything should still work, but if 104880c16af9SWarner Losh not, please contact imp@freebsd.org. 104980c16af9SWarner Losh 1050a45f2d05SWarner Losh20010517: 1051a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 1052a45f2d05SWarner Losh userland at the same time. 1053a45f2d05SWarner Losh 1054a45f2d05SWarner Losh20010517: 1055a45f2d05SWarner Losh New ncurses imported. 1056a45f2d05SWarner Losh 10572988afcaSWarner Losh20010512: 10582988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 10592988afcaSWarner Losh will be the only way to go starting July 1. 10602988afcaSWarner Losh 10611a33dba7SWarner Losh20010504: 10621a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 10631a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 10641a33dba7SWarner Losh 106509946a51SWarner Losh20010502: 106609946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 106709946a51SWarner Losh 106809946a51SWarner Losh20010501: 106909946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 107009946a51SWarner Losh 107109946a51SWarner Losh20010430: 1072a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 107309946a51SWarner Losh go back in the water. 107409946a51SWarner Losh 107509946a51SWarner Losh20010429: 107609946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 107709946a51SWarner Losh this date, but before the correction date. 107809946a51SWarner Losh 107991dd3b53SWarner Losh20010423: 108091dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 108191dd3b53SWarner Losh 108291dd3b53SWarner Losh20010411: 108391dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 108491dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 108591dd3b53SWarner Losh Update only if you understand that you must not use the old 108691dd3b53SWarner Losh fsck with the new kernel ever. 108791dd3b53SWarner Losh 1088933b3269SWarner Losh20010330: 1089933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 1090c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 1091933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 1092933b3269SWarner Losh 1093933b3269SWarner Losh20010319: 1094933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 1095933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 1096933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 1097f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 109809946a51SWarner Losh 109909946a51SWarner Losh20010315: 110009946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 1101ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 110209946a51SWarner Losh been replaced by tunables. See ata.4 for details. 1103933b3269SWarner Losh 1104933b3269SWarner Losh20010312: 1105933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 1106933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 1107933b3269SWarner Losh 1108933b3269SWarner Losh20010312: 1109933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 1110933b3269SWarner Losh instead of ad-hoc. 1111933b3269SWarner Losh 1112933b3269SWarner Losh20010310: 1113f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 1114933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 1115933b3269SWarner Losh ssh might not work if you don't. 1116933b3269SWarner Losh 111762353691SWarner Losh20010303: 111862353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 111962353691SWarner Losh which means that you must include the miibus in your kernel if 112062353691SWarner Losh you use the ed driver. 112162353691SWarner Losh 1122d325cf65SWarner Losh20010220: 1123d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 1124d325cf65SWarner Losh safe to go back into the water. 1125d325cf65SWarner Losh 1126024daae6SWarner Losh20010211: 1127024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 1128024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 1129024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 1130024daae6SWarner Losh that before upgrading would be a good time to do a level 0 1131024daae6SWarner Losh dump of your system. No, really, I mean it this time. 1132024daae6SWarner Losh 1133024daae6SWarner Losh To get to the new system, you'll need to use the following 1134024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 1135024daae6SWarner Losh don't have to move this to the updating section. 1136024daae6SWarner Losh 1137024daae6SWarner Losh To get around the installworld problem, do: 1138024daae6SWarner Losh # cd /usr/src/usr.bin/sed 1139024daae6SWarner Losh # make install 1140024daae6SWarner Losh # cd /usr/src 1141024daae6SWarner Losh # make installworld 1142024daae6SWarner Losh If that doesn't work, then try: 1143024daae6SWarner Losh # make -k installworld 1144024daae6SWarner Losh # make installworld 1145024daae6SWarner Losh 1146024daae6SWarner Losh20010207: 1147024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 1148024daae6SWarner Losh do not include devfs in your kernel as problems result. 1149024daae6SWarner Losh 1150024daae6SWarner Losh20010205: 11517595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 1152024daae6SWarner Losh Remove them from your config. 1153024daae6SWarner Losh 11541e159248SWarner Losh20010122: 11551e159248SWarner Losh ****************************** WARNING ****************************** 11561e159248SWarner Losh buildkernel has been changed slightly 11571e159248SWarner Losh ****************************** WARNING ****************************** 11581e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 11591e159248SWarner Losh should update your scripts and make.conf accordingly. 11601e159248SWarner Losh 11611e159248SWarner Losh20010119: 11621e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 11631e159248SWarner Losh This requires a new config to build correctly. 11641e159248SWarner Losh 1165aac7dfeaSWarner Losh20010116: 1166ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 1167aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 1168aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 1169aac7dfeaSWarner Losh 1170aac7dfeaSWarner Losh20010110: 1171aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 1172aac7dfeaSWarner Losh 1173aac7dfeaSWarner Losh20010102: 1174aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 1175aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 1176aac7dfeaSWarner Losh 117763c90c9eSWarner Losh20010101: 117863c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 117963c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 11805fd2a895SWarner Losh dump while building termcap. You can work around this problem 118163c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 118263c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 118363c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 118463c90c9eSWarner Losh might have been ignored by the -k option. 118563c90c9eSWarner Losh 11865fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 11875fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 11885fd2a895SWarner Losh of this working. 11895fd2a895SWarner Losh 1190aac7dfeaSWarner Losh20001228: 1191aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 1192ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 1193aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 1194aac7dfeaSWarner Losh 1195de2bcc63SWarner Losh20001218: 1196de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 1197de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 1198de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 1199de2bcc63SWarner Losh cards will not be recognized without it. 1200de2bcc63SWarner Losh 1201960773f7SWarner Losh20001205: 1202960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 1203960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 1204960773f7SWarner Losh adding the following in pam.conf: 1205960773f7SWarner Losh 1206960773f7SWarner Losh sshd auth sufficient pam_skey.so 1207960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 1208960773f7SWarner Losh sshd session required pam_permit.so 1209960773f7SWarner Losh 12100acc635eSWarner Losh20001031: 12110acc635eSWarner Losh cvs updated to 1.11. 12120acc635eSWarner Losh 12130acc635eSWarner Losh20001020: 12140acc635eSWarner Losh The random device needs more entropy, so you need to make sure 12150acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 12160acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 12170acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 12180acc635eSWarner Losh workaround. 12190acc635eSWarner Losh 12200acc635eSWarner Losh20001010: 12210acc635eSWarner Losh ****************************** WARNING ****************************** 12220acc635eSWarner Losh Sendmail has been updated. 12230acc635eSWarner Losh ****************************** WARNING ****************************** 12240acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 12250acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 12260acc635eSWarner Losh is set. 12270acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 12280acc635eSWarner Losh commands. 12290acc635eSWarner Losh o Now using sendmail's version of vacation(1). 12300acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 12310acc635eSWarner Losh in /usr/share/sendmail/cf. 12320acc635eSWarner Losh o sendmail.cw changed to local-host-names 12330acc635eSWarner Losh 12340acc635eSWarner Losh More details can be found at 12350acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 12360acc635eSWarner Losh 12376e98a146SWarner Losh20001009: 12386e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 12396e98a146SWarner Losh your entire ports tree, or you will have problems. 12406e98a146SWarner Losh 12416e98a146SWarner Losh20001006: 1242685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 12436e98a146SWarner Losh the installed miniperl. It is recommended that you delete 12446e98a146SWarner Losh /usr/bin/miniperl. 12456e98a146SWarner Losh 1246073113a4SWarner Losh20001005: 1247073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1248685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1249073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1250073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1251073113a4SWarner Losh tree for anything to work. 1252073113a4SWarner Losh 12530acc635eSWarner Losh20000928: 12540acc635eSWarner Losh There was a change in the passwd format. Need more information. 12550acc635eSWarner Losh 1256be3885b3SWarner Losh20000916: 1257be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1258be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1259be3885b3SWarner Losh same time as your kernel. 1260be3885b3SWarner Losh 126176ec9675SWarner Losh20000914: 126276ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 126376ec9675SWarner Losh include the device will cause suspended laptops losing time 126476ec9675SWarner Losh when they resume. Include 126576ec9675SWarner Losh device pmtimer 126676ec9675SWarner Losh in your config file and 126701b9a434SWarner Losh hint.pmtimer.0.at="isa" 126876ec9675SWarner Losh to your /boot/device.hints file. 126976ec9675SWarner Losh 1270f4865386SMark Murray20000911: 1271f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1272f4865386SMark Murray rather than an option. The supplied kernel config files have 1273f4865386SMark Murray been updated. You will need to do something similar in your 1274f4865386SMark Murray own kernel config file. 1275f4865386SMark Murray Remove: 1276f4865386SMark Murray options RANDOMDEV 1277f4865386SMark Murray Add: 1278f4865386SMark Murray device random 1279f4865386SMark Murray If you prefer to load the loadable module, you need to do 1280f4865386SMark Murray nothing. 1281f4865386SMark Murray 1282d594498fSWarner Losh20000909: 1283d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1284d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1285d594498fSWarner Losh reflect this if you load this module at boot time. 1286d594498fSWarner Losh The line should read: 1287d594498fSWarner Losh random_load="YES" 1288d594498fSWarner Losh 12890deb7ddcSWarner Losh20000907: 12900deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 129116eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 129216eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 129316eb772dSWarner Losh sure you don't have model loading problems which might at 129416eb772dSWarner Losh first blush appear related to SMP. 129552bf24e7SWarner Losh 12965a01880bSWarner Losh20000906: 12975a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 12985a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 12995a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 13005a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 13015a01880bSWarner Losh don't have one, and you have host.conf. 13025a01880bSWarner Losh 13032b41163cSWarner Losh20000905: 130438d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 130538d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 130638d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 130738d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 130838d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 130938d6ecd2SWarner Losh 131038d6ecd2SWarner Losh20000905: 13118aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 13128aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 13138aab4bc7SWarner Losh is /boot/kernel. 13148aab4bc7SWarner Losh 13158aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 131638d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 131738d6ecd2SWarner Losh installkernel/installworld dance. 13182b41163cSWarner Losh 1319d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1320d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1321d594498fSWarner Losh modules in that directory instead of finding them in the correct 1322d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1323d594498fSWarner Losh is that the linux module crashes your machine after the update. 1324d594498fSWarner Losh 1325d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1326d594498fSWarner Losh mv /modules.old /boot/kernel.old 1327d594498fSWarner Losh chflags noschg /kernel.old 1328d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1329d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1330d594498fSWarner Losh fi 1331d594498fSWarner Losh 1332c22a309cSWarner Losh20000904: 1333c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1334c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1335c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1336c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1337c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1338c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1339c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1340c22a309cSWarner Losh is not likely to be generated. 1341c22a309cSWarner Losh 1342fdb9f54dSWarner Losh20000825: 1343fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 13449c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 13459c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 13469c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 13479c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 13489c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 13499c1a7444SWarner Losh messages will appear after the boot loader tries to start the 13509c1a7444SWarner Losh kernel. 13519c1a7444SWarner Losh 13529c1a7444SWarner Losh20000821: 13539c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 13549c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 13559c1a7444SWarner Losh /boot/loader.conf. 1356fdb9f54dSWarner Losh 13578f250aa7SWarner Losh20000812: 13585da0d091SWarner Losh suidperl is now always built and installed on the system, but 13595da0d091SWarner Losh with permissions of 511. If you have applications that use 13605da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 13615da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 13625da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 13635da0d091SWarner Losh will fix this until the next build. 13645da0d091SWarner Losh 13655da0d091SWarner Losh20000812: 13668f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 13678f250aa7SWarner Losh visible changes that may immediately affect your configuration 13688f250aa7SWarner Losh include: 13698f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 13708f250aa7SWarner Losh - newaliases limited to root and trusted users 13718f250aa7SWarner Losh - MSA port (587) turned on by default 13728f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 13738f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 13748f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 13758f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 13768f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 13778f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 13788f250aa7SWarner Losh 137971c38472SWarner Losh20000810: 138071c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 138171c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 138271c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 138371c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 138471c38472SWarner Losh specific use for it. 138571c38472SWarner Losh 138671c38472SWarner Losh20000729: 138771c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 138871c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 138971c38472SWarner Losh /etc/rc.conf if they want to have the same setup 139071c38472SWarner Losh afterwards (unless the variables already are set, of course): 139171c38472SWarner Losh # Enable network daemons for user convenience. 139271c38472SWarner Losh inetd_enable="YES" 139371c38472SWarner Losh portmap_enable="YES" 139471c38472SWarner Losh sendmail_enable="YES" 139571c38472SWarner Losh 139671c38472SWarner Losh20000728: 139771c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 139871c38472SWarner Losh will need to change that to nullfs_load="YES". 139971c38472SWarner Losh 14001dece4a9SWarner Losh20000728: 14011dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 14021dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 14031dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 14041dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 14051dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 14061dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 14071dece4a9SWarner Losh to /MYKERNEL. 14081dece4a9SWarner Losh 1409409e887cSWarner Losh20000711: 1410409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1411409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1412409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1413409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1414409e887cSWarner Losh for details on potential problems that you might have and how 1415409e887cSWarner Losh to get around them. 1416409e887cSWarner Losh 1417409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1418409e887cSWarner Losh clauses above, you needn't worry. 1419409e887cSWarner Losh 1420409e887cSWarner Losh20000711: 1421409e887cSWarner Losh /etc/security has been updated to print the inode number of 1422409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1423409e887cSWarner Losh in the number of changed programs the first time when you run 1424409e887cSWarner Losh mergemaster to get a new /etc/security. 1425409e887cSWarner Losh 1426673d13f2SWarner Losh20000710: 1427673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1428673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1429673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1430673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1431673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1432673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1433673d13f2SWarner Losh errors. (see below, 20000624). 1434673d13f2SWarner Losh 1435bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 14361dece4a9SWarner Losh 1437673d13f2SWarner Losh20000709: 1438c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1439c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1440c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1441673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1442673d13f2SWarner Losh 1443e98e26cdSWarner Losh20000706: 1444e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1445e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1446e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1447f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1448e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 14492c021c6cSMark Ovens interim if needed. 1450e98e26cdSWarner Losh 1451e98e26cdSWarner Losh20000705: 1452e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1453e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1454e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1455e98e26cdSWarner Losh details. 1456e98e26cdSWarner Losh 1457c373950eSWarner Losh20000704: 14582f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 14592f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 14602f961bc8SWarner Losh 14612f961bc8SWarner Losh20000704: 1462c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1463c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1464c373950eSWarner Losh rc.d scripts that haven't been updated. 1465c373950eSWarner Losh 146627dc3a2bSWarner Losh20000630: 146727dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 146827dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 146927dc3a2bSWarner Losh which should be reported to des@freebsd.org. 147027dc3a2bSWarner Losh 1471b8c215acSWarner Losh20000625: 1472b8c215acSWarner Losh From approximately this date forward, one must have the crypto 147327dc3a2bSWarner Losh system installed in order to build the system and kernel. 147427dc3a2bSWarner Losh While not technically strictly true, one should treat it as 147527dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 147627dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 147727dc3a2bSWarner Losh were required. You should check with the latest collections 147827dc3a2bSWarner Losh to make sure that these haven't changed. 1479b8c215acSWarner Losh 14807b990719SWarner Losh20000624: 14817b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 14827b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 14837b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 14841a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 14857b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 14867b990719SWarner Losh openssh and openssl should not be used to generate keys from this 14877b990719SWarner Losh date to the completion of the work. 14887b990719SWarner Losh 148927dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 149027dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 149127dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 149227dc3a2bSWarner Losh recreate the random and urandom devices. 149327dc3a2bSWarner Losh 149481e54c50SWarner Losh20000622: 149581e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 149681e54c50SWarner Losh BSD license. You may need to remove your symbolic links 149781e54c50SWarner Losh that used to be required when updating. 149881e54c50SWarner Losh 149939943833SWarner Losh20000621: 15002c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 15012a2f33fbSDaniel Baker the config file update procedure. 15022a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1503c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 150459df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 150559df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 150639943833SWarner Losh 1507290f9ad8SWarner Losh20000620: 1508290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1509290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1510290f9ad8SWarner Losh that workaround will no longer be required. 1511290f9ad8SWarner Losh 151290fb6346SWarner Losh20000615: 151390fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 151490fb6346SWarner Losh ad driver. If you haven't done so already, you must update 151590fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 151690fb6346SWarner Losh devices. 151790fb6346SWarner Losh 1518f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1519f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1520f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1521f75f65bbSWarner Losh may work). 1522f75f65bbSWarner Losh 1523ba26da8eSWarner Losh20000612: 1524ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1525290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1526c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1527290f9ad8SWarner Losh to your config file to compile them in statically. The format 1528f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1529f54a3542SWarner Losh NEWCARD for examples of the new format. 1530290f9ad8SWarner Losh 15319698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 15329698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 15339698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 15349698f2c0SWarner Losh in it. 1535bbcc5149SWarner Losh 1536d65850ebSWarner Losh20000522: 1537ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1538d65850ebSWarner Losh building a kernel after this point is advised that they need 1539d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1540d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1541d65850ebSWarner Losh 1542d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1543d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1544d9583a00SWarner Losh is recommended that you don't set this option until the problem 1545d9583a00SWarner Losh is resolved. 1546d9583a00SWarner Losh 15478039cedeSWarner Losh20000513: 15488039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 15498039cedeSWarner Losh 1550d65850ebSWarner Losh20000510: 15518039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 15528039cedeSWarner Losh This will require some care in updating alphas. A new libstand 15538039cedeSWarner Losh is requires for the boot blocks to build properly. 15548039cedeSWarner Losh 15558039cedeSWarner Losh20000503: 15568039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 15578039cedeSWarner Losh is now available. 15588039cedeSWarner Losh 1559d65850ebSWarner Losh20000502: 1560d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1561d65850ebSWarner Losh connected to the kernel building instead. 1562d65850ebSWarner Losh 1563be149406SNik Clayton20000427: 15648039cedeSWarner Losh You may need to build gperf 15658039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 15668039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 15678039cedeSWarner Losh an option only in -current. 15688039cedeSWarner Losh 15692b8dd5f4SWarner Losh20000417: 15702b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1571f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 15722b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 15732b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 15742c021c6cSMark Ovens before you reboot, you'll need to issue: 15752b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 15762b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 15772b8dd5f4SWarner Losh 15788d9f1945SWarner Losh20000320: 15792b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 15802b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 15812b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1582ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 15832b8dd5f4SWarner Losh to the start of /etc/rc.conf. 15848d9f1945SWarner Losh 1585f8ab1dd6SWarner Losh20000319: 1586f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1587f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1588f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1589f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1590f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1591f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1592f8ab1dd6SWarner Losh 159319cada77SWarner Losh20000318: 1594f699bbbbSMark Ovens We've entered the traditional post release dumping party. 159519cada77SWarner Losh Large kernel changes are being committed and are in the 159619cada77SWarner Losh works. It is important to keep the systems' klds and kernel 159719cada77SWarner Losh in sync as kernel interfaces and structures are changing. 159819cada77SWarner Losh Before reporting kernel panics, make sure that all modules 159919cada77SWarner Losh that you are loading are up to date. 1600ba228352SWarner Losh 160119cada77SWarner Losh20000315: 16026d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 16036d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 16046d23c382SWarner Losh will do the trick. This isn't critical until you remove your 16056d23c382SWarner Losh wd device entries in /dev, at which point your system will not 16066d23c382SWarner Losh boot. 16076d23c382SWarner Losh 16086d23c382SWarner Losh20000315: 160919cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 161019cada77SWarner Losh to upgrade to 4.0 from 3.x. 161157199806SWarner Losh 1612dc0dbf5cSWarner LoshCOMMON ITEMS: 1613dc0dbf5cSWarner Losh 1614cd5f061cSWarner Losh # NOTE: 5.x below applies to 6.0-currrent as well, for the 1615cd5f061cSWarner Losh # momemnt. 4.any -> 5.any upgrade support will remain in 1616cd5f061cSWarner Losh # place for 6.0 current, but after 5.3 RELEASE, the 4.any -> 1617cd5f061cSWarner Losh # 6.0-current upgrade path will require moving through 5.3 1618cd5f061cSWarner Losh # RELEASE or newer. 1619cd5f061cSWarner Losh 1620a24eff53SWarner Losh General Notes 1621a24eff53SWarner Losh ------------- 1622a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1623a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1624a24eff53SWarner Losh installworld. This is especially true when upgrading between 1625a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1626a24eff53SWarner Losh or several minor releases, or when several months have passed 1627a24eff53SWarner Losh on the -current branch). 1628a24eff53SWarner Losh 16295780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 16305780f3baSWarner Losh poisoning. This can happen because the make utility reads its 16315780f3baSWarner Losh environment when searching for values for global variables. 16325780f3baSWarner Losh To run your build attempts in an "environmental clean room", 16335780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 16345780f3baSWarner Losh page for more details. 16355780f3baSWarner Losh 1636dc0dbf5cSWarner Losh To build a kernel 1637dc0dbf5cSWarner Losh ----------------- 1638ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1639f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1640ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1641282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1642282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1643dc0dbf5cSWarner Losh 1644ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1645ba01eb20SWarner Losh -------------------------------------------------------------- 16460fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 16470fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 16480fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 16490fbd2da9SKen Smith 16500fbd2da9SKen Smith cd src/sys/${arch}/conf 165147d0d01fSWarner Losh config KERNEL_NAME_HERE 16520fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1653ba01eb20SWarner Losh make depend 1654ba01eb20SWarner Losh make 1655ba01eb20SWarner Losh make install 1656ba01eb20SWarner Losh 1657ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1658ba01eb20SWarner Losh 1659ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1660ba01eb20SWarner Losh ----------------------------------------------------------- 166163cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 166263cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 166363cb445eSWarner Losh 1664f643de42SWarner Losh <make sure you have good level 0 dumps> 166563cb445eSWarner Losh <maybe fix /etc/fstab> [7] 166663cb445eSWarner Losh make buildworld 16676586253aSWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE 166863cb445eSWarner Losh [1] 166963cb445eSWarner Losh <reboot in single user> [3] 16706586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 167163cb445eSWarner Losh mergemaster -p [5] 167263cb445eSWarner Losh make installworld 167363cb445eSWarner Losh mergemaster [4] 167463cb445eSWarner Losh <reboot> 167563cb445eSWarner Losh 1676759f0aefSWarner Losh 1677f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1678f27b1fceSJoseph Koshy -------------------------------------------------- 1679f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1680f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1681f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1682f27b1fceSJoseph Koshy # size. 1683f27b1fceSJoseph Koshy 1684f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1685f27b1fceSJoseph Koshy <boot into -stable> 1686f27b1fceSJoseph Koshy make buildworld 1687f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1688f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1689f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1690f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 16916586253aSWarner Losh cp src/sys/${ARCH}/conf/GENERIC.hints \ 1692f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1693f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 16946586253aSWarner Losh cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1695f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1696f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1697f27b1fceSJoseph Koshy <reboot into current> 1698f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 16996586253aSWarner Losh <maybe install compatibility libraries from src/lib/compat> 1700f27b1fceSJoseph Koshy <reboot> 1701f27b1fceSJoseph Koshy 1702f27b1fceSJoseph Koshy 1703f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1704f27b1fceSJoseph Koshy ---------------------------------------------- 17055c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 1706e5dc5f61SWarner Losh # modules has changed. If you are installing 5.x onto a 4.x 17075c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 17085c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1709ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1710f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1711f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1712f643de42SWarner Losh # space on /. 1713f643de42SWarner Losh 1714f643de42SWarner Losh <make sure you have good level 0 dumps> 1715fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 171621c075eaSWarner Losh make buildworld [9] 1717802fc49dSBrian Feldman cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1718e5dc5f61SWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1719802fc49dSBrian Feldman cd sys/boot ; make STRIP="" install [6] 1720fc8c157fSWarner Losh [1] 1721fc8c157fSWarner Losh <reboot in single user> [3] 17226586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 1723835284beSWarner Losh mergemaster -p [5] 1724f8a4c901SWarner Losh rm -rf /usr/include/g++ 1725ba26da8eSWarner Losh make installworld 1726802fc49dSBrian Feldman mergemaster -i [4] 1727ba26da8eSWarner Losh <reboot> 1728ba26da8eSWarner Losh 1729fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1730fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1731fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1732fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1733fdb9f54dSWarner Losh the UPDATING entries. 1734ba26da8eSWarner Losh 17351dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 17361dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 17371dece4a9SWarner Losh your sources that you have read and understood all the recent 17381dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 17391dece4a9SWarner Losh much fewer pitfalls. 17401dece4a9SWarner Losh 1741134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1742134d2e86SWarner Losh should disable them at this point so they don't crash your 1743134d2e86SWarner Losh system on reboot. 1744134d2e86SWarner Losh 17459c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 17469c1a7444SWarner Losh your own device.hints to reflect your unique hardware 17479c1a7444SWarner Losh configuration. 17489c1a7444SWarner Losh 1749ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1750ee6e1fc3SWarner Losh fsck -p 1751ee6e1fc3SWarner Losh mount -u / 1752ee6e1fc3SWarner Losh mount -a 17536586253aSWarner Losh cd src 175447d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1755f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1756f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 175766986952SRuslan Ermilov For the 4.x -> 5.x upgrade, you will also see many messages about 1758b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1759b705ae10SWarner Losh be ignored while you proceed to the next step. 1760ee6e1fc3SWarner Losh 1761a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1762a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1763a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1764a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1765a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1766a6cd4f9dSWarner Losh for potential gotchas. 1767a6cd4f9dSWarner Losh 1768835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1769835284beSWarner Losh you may need to do this if you get unknown user in the following 1770835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1771835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1772835284beSWarner Losh install) after the buildworld before this step if you last updated 1773835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1774835284beSWarner Losh 1775bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1776bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1777bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1778bd79cf40SWarner Losh ok unload 1779bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1780bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1781bd79cf40SWarner Losh described here. 1782fc8c157fSWarner Losh 1783fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1784e5dc5f61SWarner Losh compatibility slices. These are device names of the form /dev/ad0a 1785e5dc5f61SWarner Losh without the actual slice name. These will break with 5.x and newer. 1786fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1787e5dc5f61SWarner Losh 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha 1788e5dc5f61SWarner Losh is not. 1789fc8c157fSWarner Losh 1790c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1791c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1792c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1793c74fe6afSWarner Losh that is hard to boot to recover. 1794c74fe6afSWarner Losh 1795e5dc5f61SWarner Losh Make sure that you merge any new devices from GENERIC since the 1796e5dc5f61SWarner Losh last time you updated your kernel config file. 1797e5dc5f61SWarner Losh 179821c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 1799e5dc5f61SWarner Losh cvs prune empty directories. 1800e5dc5f61SWarner Losh 1801e5dc5f61SWarner Losh If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1802e5dc5f61SWarner Losh "?=" instead of the "=" assignment operator, so that buildworld can 1803e5dc5f61SWarner Losh override the CPUTYPE if it needs to. 1804e5dc5f61SWarner Losh 1805e5dc5f61SWarner Losh MAKEOBJDIRPREFIX must be defined in an environment variable, and 1806e5dc5f61SWarner Losh not on the command line, or in /etc/make.conf. buildworld will 1807e5dc5f61SWarner Losh warn if it is improperly defined. 1808e5dc5f61SWarner Losh 1809802fc49dSBrian Feldman In case you would like to avoid installing new packages of everything, 1810802fc49dSBrian Feldman you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 181166986952SRuslan Ermilov compatibility libraries are built which should allow you to continue 1812e5dc5f61SWarner Losh using your existing software for a while. Alternatively, you can 1813e5dc5f61SWarner Losh install the misc/compat4x port. 18148633bbeaSBrooks Davis 18158633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 18166586253aSWarner Losh initialized by feeding data into it. src/etc/rc.d/preseedrandom 18178633bbeaSBrooks Davis takes care of this. 1818dc0dbf5cSWarner LoshFORMAT: 1819dc0dbf5cSWarner Losh 1820f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 18211fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1822f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1823f8ab1dd6SWarner Loshprevious releases if your system is older than this. 18241fc1a0dcSWarner Losh 1825e72fd46aSWarner LoshCopyright information: 1826e72fd46aSWarner Losh 1827e5dc5f61SWarner LoshCopyright 1998-2004 M. Warner Losh. All Rights Reserved. 1828e72fd46aSWarner Losh 1829772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1830772730c7SWarner Loshmodification, in full or in part, in any form or format of this 18319698f2c0SWarner Loshdocument are permitted without further permission from the author. 1832e72fd46aSWarner Losh 1833e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1834e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1835e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1836e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1837e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1838e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1839e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1840e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1841e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1842e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1843e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1844e72fd46aSWarner Losh 1845e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1846e72fd46aSWarner Loshauthor a beer. 1847e72fd46aSWarner Losh 184822306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1849772730c7SWarner Loshthis document. 1850772730c7SWarner Losh 185197d92980SPeter Wemm$FreeBSD$ 1852