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 26f5ee5a8bSMax Laier20040914: 27f5ee5a8bSMax Laier The format of the pflogd(8) logfile "/var/log/pflog" has changed for 28f5ee5a8bSMax Laier architectures that have a 64 bit long type to make it compatible to 29f5ee5a8bSMax Laier the standard pcap format. In order to prevent corruption move away 30f5ee5a8bSMax Laier any old logfile before using a new pflogd(8). 31f5ee5a8bSMax Laier 32d698cdb3SJohn-Mark Gurney20040906: 33d698cdb3SJohn-Mark Gurney debug.witness_* has been renamed to debug.witness.*. There are 34d698cdb3SJohn-Mark Gurney compatibility tunables left in for a few days. Update loader.conf 35d698cdb3SJohn-Mark Gurney as necessary. 36d698cdb3SJohn-Mark Gurney 374ff62bd9SBrooks Davis20040902: 384ff62bd9SBrooks Davis The ifi_epoch change has been reverted because the ABI breakage 394ff62bd9SBrooks Davis was too extensive. If you are running with a kernel/userland 404ff62bd9SBrooks Davis containing the initial change (20040830), you should heed the 414ff62bd9SBrooks Davis warning about ifconfig incompatibility when upgrading again. 424ff62bd9SBrooks Davis With this change, 5.3 and 6.0 ifconfigs and kernels are once 434ff62bd9SBrooks Davis again interoperable. 444ff62bd9SBrooks Davis 451fc4519bSBrooks Davis20040830: 461fc4519bSBrooks Davis A new variable, ifi_epoch, has been added to struct if_data 471fc4519bSBrooks Davis which is part if struct ifnet. This means all network drivers 481fc4519bSBrooks Davis and network monitoring applications need to be recompiled. 491fc4519bSBrooks Davis 503789fb75SBrooks Davis WARNING WARNING WARNING WARNING WARNING WARNING WARNING 513789fb75SBrooks Davis 523789fb75SBrooks Davis This also breaks ifconfig compatibility. An old ifconfig will 533789fb75SBrooks Davis not work with the new kernel and a new ifconfig will not work 543789fb75SBrooks Davis with the old. It is strongly recommended that you make a copy 553789fb75SBrooks Davis of your old ifconfig before installworld. If you are installing 563789fb75SBrooks Davis remotely, you must copy over a new ifconfig before rebooting in 573789fb75SBrooks Davis to the new kernel. 583789fb75SBrooks Davis 59c1c94d5cSRobert Watson20040828: 60c1c94d5cSRobert Watson The default configuration for the network stack has been changed 61c1c94d5cSRobert Watson such that it now runs without the Giant lock unless configured 62c1c94d5cSRobert Watson otherwise. If you experience network-related instability, you 63c1c94d5cSRobert Watson may wish to try setting "debug.mpsafenet=0" or compiling the 64c1c94d5cSRobert Watson kernel with "options NET_WITH_GIANT". Details on the netperf 65c1c94d5cSRobert Watson project may be found at: 66c1c94d5cSRobert Watson 67c1c94d5cSRobert Watson http://www.watson.org/~robert/freebsd/netperf/ 68c1c94d5cSRobert Watson 69c1c94d5cSRobert Watson Including the 20040828 announcement of configuration change 70c1c94d5cSRobert Watson details. 71c1c94d5cSRobert Watson 72c21fd232SAndre Oppermann20040827: 73c21fd232SAndre Oppermann PFIL_HOOKS are a fixed part of the network stack now and do not 74c21fd232SAndre Oppermann need to be specified in the kernel configuration file anymore. 75c21fd232SAndre Oppermann 76f036d408SJulian Elischer20040819: 77f036d408SJulian Elischer Netgraph changed its message format slightly to align the data 78f036d408SJulian Elischer portion well on 64 bit machines. 79f036d408SJulian Elischer Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd, 80f036d408SJulian Elischer pppoed, bluetooth, ATM) should be recompiled when a new kernel 81f036d408SJulian Elischer is installed. 82f036d408SJulian Elischer 83b067abfaSAndre Oppermann20040817: 840ce70eb4SAndre Oppermann IPFW has been converted to use PFIL_HOOKS. This change is 85b067abfaSAndre Oppermann transparent to userland and preserves the ipfw ABI. The ipfw 86b067abfaSAndre Oppermann core packet inspection and filtering functions have not been 87b067abfaSAndre Oppermann changed, only how ipfw is invoked is different. Note that 88b067abfaSAndre Oppermann "option PFIL_HOOKS" is required to use IPFIREWALL compiled 89b067abfaSAndre Oppermann into the kernel or as KLD. 90b067abfaSAndre Oppermann 91f13a7951SDavid Malone20040814: 92f13a7951SDavid Malone The RANDOM_IP_ID option has been replaced by the sysctl 93f13a7951SDavid Malone net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then 94f13a7951SDavid Malone you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf. 95f13a7951SDavid Malone 963a004637SMax Laier20040807: 973a004637SMax Laier The size of 'struct ifnet' has changed due to the addition of the 983a004637SMax Laier if_carp placeholder. All kernel modules implementing network 993a004637SMax Laier interfaces must be recompiled as a result. 1003a004637SMax Laier 1014f34d8d1SJohn-Mark Gurney20040806: 1024f34d8d1SJohn-Mark Gurney Module loading has been fixed. Some older installations will 103ac41c814SRuslan Ermilov drop proper module_path initialization and modules will fail to 1044f34d8d1SJohn-Mark Gurney load properly. If you have a line in /boot/loader.rc that says: 1054f34d8d1SJohn-Mark Gurney "initialize drop", do (i386 only): 1064f34d8d1SJohn-Mark Gurney cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc 1074f34d8d1SJohn-Mark Gurney chown root:wheel /boot/loader.rc 1084f34d8d1SJohn-Mark Gurney chmod 444 /boot/loader.rc 1094f34d8d1SJohn-Mark Gurney 1108f075db4SMark Murray20040802: 1118f075db4SMark Murray making /dev/(null|zero) into a module proved to be too unpopular, 1128f075db4SMark Murray so this bit has been revoked from the previous (20040801) entry. 1138f075db4SMark Murray 114d064d6dbSMark Murray20040801: 115d064d6dbSMark Murray The /dev/mem, /dev/io /dev/(null/zero) devices are now modules, 116d064d6dbSMark Murray so you may wish to add them to your kernel config file. See 117d064d6dbSMark Murray GENERIC for examples. 118d064d6dbSMark Murray 119b289983eSAlexander Kabaev20040728: 12054bd5271SAlexander Kabaev System compiler has been upgraded to GCC 3.4.2-pre. As with any major 12154bd5271SAlexander Kabaev compiler upgrade, there are several issues to be aware of. GCC 3.4.x 12254bd5271SAlexander Kabaev has broken C++ ABI compatibility with previous releases yet again 12354bd5271SAlexander Kabaev and users will have to rebuild all their C++ programs with the new 124d0e54ab4SDavid E. O'Brien compiler. If you are getting run-time error such as 125d0e54ab4SDavid E. O'Brien /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE" 126d0e54ab4SDavid E. O'Brien This entry does apply to you. 127d0e54ab4SDavid E. O'Brien 128d0e54ab4SDavid E. O'Brien A new unit-at-a-time optimization mode, which is default in this 129d0e54ab4SDavid E. O'Brien compiler release, is more aggressive in removing unused static 130d0e54ab4SDavid E. O'Brien symbols. This is the likely cause of 'make buildworld' breakages 131cd5f061cSWarner Losh with non-default CFLAGS where optimization level is set to -O2 132cd5f061cSWarner Losh or higher. 13354bd5271SAlexander Kabaev 1346e1afae3SWarner Losh With the upgrade of the system compiler, the kernel has been upgraded 1356e1afae3SWarner Losh to match the new system compiler. This makes it impossible to build 1366e1afae3SWarner Losh a new kernel with the old compiler. Upgrade your system via 1376e1afae3SWarner Losh make buildworld and make kernel (see below) to fix this problem. 1386e1afae3SWarner Losh 13936ed21e6SRobert Watson20040727: 14036ed21e6SRobert Watson The size of 'struct ifnet' has changed due to the addition of 14136ed21e6SRobert Watson the IFF_NEEDSGIANT flag (and what it implies). All kernel 14236ed21e6SRobert Watson modules implementing network interfaces must be recompiled as 14336ed21e6SRobert Watson a result. 14436ed21e6SRobert Watson 1456305ac24SSeigo Tanimura20040716: 1466305ac24SSeigo Tanimura The sound device drivers are renamed. `sound' is always required, 1476305ac24SSeigo Tanimura while `snd_*' should be configured accordingly to your hardware. 1486305ac24SSeigo Tanimura Refer to NOTES for the detail of the drivers. 1496305ac24SSeigo Tanimura 150e623dcb7SMarcel Moolenaar20040710: 151e623dcb7SMarcel Moolenaar __FreeBSD_version bumped to 502122. 152e623dcb7SMarcel Moolenaar 153e623dcb7SMarcel Moolenaar20040710: 154e623dcb7SMarcel Moolenaar The console initialization on Alpha has been reworked and is now 155e623dcb7SMarcel Moolenaar identical to other platforms. This means that the hardcoding of 156e623dcb7SMarcel Moolenaar the serial console and the debug port has been removed. As such, 157e623dcb7SMarcel Moolenaar hints are now required for the sio(4) driver to become a console 158e623dcb7SMarcel Moolenaar or debug port. The NO_SIO option has been decommissioned because 159e623dcb7SMarcel Moolenaar of this. 160e623dcb7SMarcel Moolenaar 161e623dcb7SMarcel Moolenaar20040710: 162e623dcb7SMarcel Moolenaar A revamp of the debugging code in the kernel with some visible 163e623dcb7SMarcel Moolenaar changes beyond just the debugging experience: 164e623dcb7SMarcel Moolenaar o The DDB option is now specific to the DDB debugger backend 165e623dcb7SMarcel Moolenaar and should not be used any more for conditional compilation 166e623dcb7SMarcel Moolenaar of debugging code for when debugging is enabled. Use the KDB 167e623dcb7SMarcel Moolenaar option for this. 168e623dcb7SMarcel Moolenaar o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have 169e623dcb7SMarcel Moolenaar been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED 170e623dcb7SMarcel Moolenaar respectively. This is in line with the first bullet. 171e623dcb7SMarcel Moolenaar o The remote GDB support has been untangled from DDB and needs 1725bd7ce0aSJens Schweikhardt to be enabled separately now. Use the GDB option for this. 173e623dcb7SMarcel Moolenaar o The GDB_REMOTE_CHAT option has been removed. Support for this 174e623dcb7SMarcel Moolenaar homegrown feature is discontinued. The GDB remote protocol 175e623dcb7SMarcel Moolenaar supports console output and it makes sense to use that. 176e623dcb7SMarcel Moolenaar o The DDB_NOKLDSYM option has been removed. The DDB debugger 177e623dcb7SMarcel Moolenaar now supports both direct symbol table lookups as well as KLD 178e623dcb7SMarcel Moolenaar symbol lookups through the linker. 179e623dcb7SMarcel Moolenaar 1806421d1dbSMaksim Yevmenkin20040708: 1816421d1dbSMaksim Yevmenkin Bluetooth code has been marked as non-i386 specific. 1826421d1dbSMaksim Yevmenkin __FreeBSD_version has been bumped to 502121 to mark this change. 1836421d1dbSMaksim Yevmenkin 18458af3216SWarner Losh20040702: 18558af3216SWarner Losh The native preemption has been added to the kernel scheduler. 1865bd7ce0aSJens Schweikhardt There is some report that the ULE scheduler was broken in some 1875bd7ce0aSJens Schweikhardt machines and we encourage users using the ULE scheduler either 1885bd7ce0aSJens Schweikhardt stick with a known good kernel, or temporarily switch to the 4BSD 18958af3216SWarner Losh scheduler as a workaround. 19058af3216SWarner Losh 191c2dba668SNate Lawson20040630: 1928ed370fdSJulian Elischer The netgraph ABI version number has been incremented to indicate 1938ed370fdSJulian Elischer an incompatible change in the ABI. Old netgraph nodes will refuse 194a6c26e1cSBruce M Simpson to attach until recompiled. Netgraph now uses mbuf tags to move 195a6c26e1cSBruce M Simpson metadata and this commit removes its home-grown metadata facility. 196a6c26e1cSBruce M Simpson Nodes should just recompile, unless they use metadata, in which 197a6c26e1cSBruce M Simpson case the changes are simple; the file ng_ksocket.c serves as an 198a6c26e1cSBruce M Simpson example of such changes. 1998ed370fdSJulian Elischer 20058af3216SWarner Losh This also broke i4b, although the compile problem has been papered 20158af3216SWarner Losh over. 20258af3216SWarner Losh 2038ed370fdSJulian Elischer20040630: 204c2dba668SNate Lawson ACPI has been updated to disable known-bad BIOS revisions. A message 2055bd7ce0aSJens Schweikhardt will be printed on the console indicating that ACPI has been disabled 206c2dba668SNate Lawson automatically and that the user should use a newer BIOS, if possible. 207c2dba668SNate Lawson If you think ACPI does work on your system and want to override 208c2dba668SNate Lawson this (i.e., for testing), set hint.acpi.0.disabled="0" at the 209c2dba668SNate Lawson loader prompt. 210c2dba668SNate Lawson 2118ee2ac9eSMax Laier20040623: 2125bd7ce0aSJens Schweikhardt pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege 2138ee2ac9eSMax Laier separated now. It uses the newly created "_pflogd" user/group 2148ee2ac9eSMax Laier combination. If you plan to use pflogd(8) make sure to run 2158ee2ac9eSMax Laier mergemaster -p or install the "_pflogd" user and group manually. 2168ee2ac9eSMax Laier 2173db5687dSBrooks Davis20040622: 2183db5687dSBrooks Davis Network interface cloning has been overhauled. This change will 2193db5687dSBrooks Davis require a recompile of modules using cloning and modification of 2203db5687dSBrooks Davis external ones to the new API. __FreeBSD_version has been bumped 2213db5687dSBrooks Davis to 502119 to mark this change. Additionally, users creating 2223db5687dSBrooks Davis stf(4) interfaces via "ifconfig stf" will need to update their 2233db5687dSBrooks Davis scripts as this will create an interface named "stf" instead of 2243db5687dSBrooks Davis "stf0" and ifconfig will not print "stf0" to stdout. 2253db5687dSBrooks Davis 226e0ae81f3SDag-Erling Smørgrav20040621: 227e0ae81f3SDag-Erling Smørgrav On 20040524, the /etc/rc.d/nsswitch script was modified to 228e0ae81f3SDag-Erling Smørgrav automatically create /etc/nsswitch.conf on startup if it did 229e0ae81f3SDag-Erling Smørgrav not already exist. Unfortunately, an error in the man page 230e0ae81f3SDag-Erling Smørgrav was carried over to the script, resulting in incorrect 231e0ae81f3SDag-Erling Smørgrav nsswitch settings. The simplest remedy is to remove both 232e0ae81f3SDag-Erling Smørgrav /etc/nsswitch.conf and /etc/host.conf; they will be recreated 233e0ae81f3SDag-Erling Smørgrav during the next reboot. 234e0ae81f3SDag-Erling Smørgrav 2354717d22aSJohn Polstra20040614: 2364717d22aSJohn Polstra The return value of sema_timedwait(9) has been changed to 2374717d22aSJohn Polstra make it consistent with cv_timedwait(9). Be sure to recompile 2384717d22aSJohn Polstra the ips module and any third-party modules which call 2394717d22aSJohn Polstra sema_timedwait. 2404717d22aSJohn Polstra 2416cb7a382SMax Laier20040613: 2426cb7a382SMax Laier ALTQ is now linked to the build. This breaks ABI for struct ifnet. 2436cb7a382SMax Laier Make sure to recompile modules and any userland that makes use of 244df843493SMax Laier sizeof(struct ifnet). In order to get the altq headers in place 245df843493SMax Laier please recompile and reinstall world. 2466cb7a382SMax Laier 2472454685eSJulian Elischer20040607: 2482454685eSJulian Elischer Splitting kern_thread.c into 2 files (adding kern_kse.c) 2492454685eSJulian Elischer requires that you re-run config after updating your tree. 2502454685eSJulian Elischer 25164fef830SSeigo Tanimura20040601: 25264fef830SSeigo Tanimura The MIDI drivers have been removed. Until the new module-friendly 25364fef830SSeigo Tanimura ones are merged, remove or comment out midi and seq from your 25464fef830SSeigo Tanimura kernel configuration. 25564fef830SSeigo Tanimura 256bb4f06e7SAndre Oppermann20040423: 257bb4f06e7SAndre Oppermann Due to a new option in ipfw (versrcreach) the ipfw(8) command 258bb4f06e7SAndre Oppermann needs to be recompiled. Normal accept/reject rules without 259bb4f06e7SAndre Oppermann options are not affected but those with options may break until 260bb4f06e7SAndre Oppermann ipfw(8) is recompiled. 261bb4f06e7SAndre Oppermann 26205641e82SColin Percival20040420: 26305641e82SColin Percival Due to changes in the callout ABI, kernels compiled after this 26405641e82SColin Percival date may be incompatible with kernel modules compiled prior to 26505641e82SColin Percival 20040406. 26605641e82SColin Percival 267d0dc9183SWarner Losh20040414: 268d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 269d0dc9183SWarner Losh problems for your system, please disable it using the tunable 270d0dc9183SWarner Losh hw.pci.do_powerstate=0. 271d0dc9183SWarner Losh 272d0dc9183SWarner Losh20040412: 273d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 274d0dc9183SWarner Losh drive is still broken. 275d0dc9183SWarner Losh 276d0dc9183SWarner Losh20040410: 277d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 278d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 279d0dc9183SWarner Losh the unanticipated problems have been resolved. 280d0dc9183SWarner Losh 2818633bbeaSBrooks Davis20040409: 2828633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 2838633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 2848633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 2858633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 28676c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 2878633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 2888633bbeaSBrooks Davis 289d40d033aSRobert Watson20040322: 290d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 291d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 292d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 293d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 294d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 295d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 296d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 297d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 298d40d033aSRobert Watson locking is merged to permit this to take place. 299d40d033aSRobert Watson 300ec9b318eSGarance A Drosehn20040310: 301ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 302ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 303ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 304ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 305ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 306ec9b318eSGarance A Drosehn 307fc28f1ffSMax Laier20040308: 308fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 309fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 3104c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 3114c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 312fc28f1ffSMax Laier Also note that pf requires "options PFIL_HOOKS" in the kernel. The 313fc28f1ffSMax Laier pf system consists of the following three devices: 314fc28f1ffSMax Laier device pf # required 315fc28f1ffSMax Laier device pflog # optional 316fc28f1ffSMax Laier device pfsync # optional 317fc28f1ffSMax Laier 3183aff5d06SDag-Erling Smørgrav20040303: 3193aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 3203aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 3213aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 3223aff5d06SDag-Erling Smørgrav 3233aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 3243aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 3253aff5d06SDag-Erling Smørgrav 3263aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 3273aff5d06SDag-Erling Smørgrav to use libpthread instead. 3283aff5d06SDag-Erling Smørgrav 329fd63c5b3SDag-Erling Smørgrav20040226: 3309d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 331fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 332fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 333fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 334fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 335fd63c5b3SDag-Erling Smørgrav 336714ae42aSBruce M Simpson20040225: 337e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 338e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 339e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 340e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 341e07a40f3SBrian Feldman should remain unaffected. 342e07a40f3SBrian Feldman 343e07a40f3SBrian Feldman20040225: 344714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 345714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 346714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 347714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 348714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 349714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 350714ae42aSBruce M Simpson 351fbd2e692SAndre Oppermann20040224: 352fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 3535bd7ce0aSJens Schweikhardt and related userland network utilities necessary. 354fbd2e692SAndre Oppermann 355158b90daSWarner Losh20040222: 356158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 357158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 358158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 359158b90daSWarner Losh Drivers outside the tree will need to be updated. 360158b90daSWarner Losh 361b7b1e150SMike Makonnen20040207: 362b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 363b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 364b7b1e150SMike Makonnen 365aca89ee6SDaniel Eischen20040130: 366aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 367aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 368aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 369aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 370aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 371aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 372aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 373aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 374aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 375aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 376aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 377aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 378aca89ee6SDaniel Eischen do not work with libpthread. 379aca89ee6SDaniel Eischen 38068b7b3a9SAlex Dupre20040125: 38168b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 38268b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 38368b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 38468b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 38568b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 38668b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 38768b7b3a9SAlex Dupre 388ff46e0deSWarner Losh20040125: 389ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 390ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 391ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 392ff46e0deSWarner Losh 393ce41f4bfSRobert Watson20031213: 394ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 395ce41f4bfSRobert Watson if the login process is unable to successfully set the 396ce41f4bfSRobert Watson process credentials to include all groups defined for the 397ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 398ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 399ce41f4bfSRobert Watson defined, or they will be unable to log in. 400ce41f4bfSRobert Watson 401c124fa05SJohn Baldwin20031203: 402c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 403c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 404c124fa05SJohn Baldwin 4058ad1f5e4SHartmut Brandt20031112: 40630093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 40730093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 40897209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 40997209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 41097209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 41197209ca3SRobert Watson not know about the new system calls that support the new statfs 4123f631d52SMarcel Moolenaar structure. 4133f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 4143f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 4153f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 4163f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 4173f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 4183f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 4193f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 4203f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 4213f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 4223f631d52SMarcel Moolenaar these changes are installed. 42330093b05SWarner Losh 42430093b05SWarner Losh ****************************DANGER******************************* 42530093b05SWarner Losh 42630093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 42730093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 42830093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 42930093b05SWarner Losh kernel. 43064a18d6fSKirk McKusick 43164a18d6fSKirk McKusick20031112: 4328ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 4338ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 4348ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 4358ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 4368ad1f5e4SHartmut Brandt sync before rebooting. 4378ad1f5e4SHartmut Brandt 438c53a5d8fSJohn Baldwin20031111: 439c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 440c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 441c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 442c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 443c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 444c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 445c53a5d8fSJohn Baldwin 4468bf455a5SJohn Baldwin20031103: 4478bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 4488bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 4492a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 4508bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 4518bf455a5SJohn Baldwin 4529bf40edeSBrooks Davis20031031: 4539bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 4549bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 4559bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 4569bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 4579bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 4589bf40edeSBrooks Davis reflect this change. 4599bf40edeSBrooks Davis 46047a42c7aSPoul-Henning Kamp20030928: 46147a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 46247a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 4635bd7ce0aSJens Schweikhardt __FreeBSD_version bumped to 501110. 46447a42c7aSPoul-Henning Kamp 46507105342SMax Khon20030926: 46607105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 46707105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 46807105342SMax Khon 46917dcd026SSam Leffler20030925: 47017dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 47117dcd026SSam Leffler also be explicitly configured. Previously this dependency was 47217dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 47317dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 47417dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 47517dcd026SSam Leffler 476fedf1d01SBruce M Simpson20030923: 477fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 478fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 479fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 480fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 481fedf1d01SBruce M Simpson 482db38f9cbSJacques Vidrine20030915: 483db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 484db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 485db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 486db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 487db38f9cbSJacques Vidrine 488c09d2c2bSMike Makonnen20030829: 489c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 490c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 491c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 492c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 493c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 494c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 495c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 496c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 497c09d2c2bSMike Makonnen may or may not exist on your system. 498c09d2c2bSMike Makonnen 49917c159dcSSøren Schmidt20030824: 50017c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 50117c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 502f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 503f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 50417c159dcSSøren Schmidt 505c1f61aa9SDavid E. O'Brien20030819: 506c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 507c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 508c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 509c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 51069f7bcf3SWarner Losh 51138c962e7SNate Lawson20030728: 51238c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 51338c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 51438c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 51538c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 51638c962e7SNate Lawson so the quirk can be re-enabled. 51738c962e7SNate Lawson 51874111097SWarner Losh20030724: 51974111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 52074111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 52174111097SWarner Losh 522178cf4e9SWarner Losh20030722: 523178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 524178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 525178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 526178cf4e9SWarner Losh FPU hardware. 527178cf4e9SWarner Losh 528178cf4e9SWarner Losh20030714: 529178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 530178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 531178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 532178cf4e9SWarner Losh People should report those issues to current@. 533178cf4e9SWarner Losh 534157c629aSWarner Losh20030711: 535157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 5368b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 53705538fa9SWarner Losh /usr/obj. 538157c629aSWarner Losh 53974111097SWarner Losh20030610: 54074111097SWarner Losh Remove deprecated locale names and transition period code 54174111097SWarner Losh for them, finishing switching to the new scheme. Check your 54274111097SWarner Losh LANG environment variable. 54374111097SWarner Losh 54474111097SWarner Losh20030609: 54574111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 54674111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 54774111097SWarner Losh important to remember beforehand if your source tree is on 54874111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 54974111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 55074111097SWarner Losh kernel. 55174111097SWarner Losh 55274111097SWarner Losh20030605: 5536cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 5546cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 5556cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 5566cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 5576cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 5586cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 5596cc6353fSMarcel Moolenaar 5606cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 5616cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 5626cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 5636cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 5646cc6353fSMarcel Moolenaar : 5656cc6353fSMarcel Moolenaar 5666cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 5676cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 5686cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 5696cc6353fSMarcel Moolenaar 57052b47445SMark Murray20030505: 57152b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 57252b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 57352b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 57452b47445SMark Murray 575a26df538SWarner Losh20030502: 576a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 577a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 578a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 579a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 580a26df538SWarner Losh 5814b065e2cSDoug Barton20030501: 5824b065e2cSDoug Barton The old rc system has been removed. Please report any problems 5834b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 5844b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 5854b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 5864b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 5874b065e2cSDoug Barton utilizes these old scripts has also been removed. 5884b065e2cSDoug Barton 58981cda3d9SWarner Losh20030423: 59081cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 59181cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 59281cda3d9SWarner Losh work around in devd will be removed around 20030507. You 59381cda3d9SWarner Losh have until then to upgrade your kernel before updating 59481cda3d9SWarner Losh userland. In general, you should have a userland and 59581cda3d9SWarner Losh kernel that's in sync with each other. However, given the 59681cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 59781cda3d9SWarner Losh allowances are made. 59881cda3d9SWarner Losh 59947a657d1SRuslan Ermilov20030329: 60047a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 60147a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 60247a657d1SRuslan Ermilov while upgrading the system through a buildworld. 60347a657d1SRuslan Ermilov 60447a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 60547a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 60647a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 60747a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 60847a657d1SRuslan Ermilov 60947a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 61047a657d1SRuslan Ermilov make cleandir && make obj && \ 61147a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 61247a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 61347a657d1SRuslan Ermilov 6145d2af00cSGregory Neil Shapiro20030208: 6155d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 6165d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 6175d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 6185d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 6195d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 6205d2af00cSGregory Neil Shapiro 6215d2af00cSGregory Neil Shapiro20030128: 6229db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 623ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 6249db58771SPoul-Henning Kamp be removed when convenient. 6259db58771SPoul-Henning Kamp 6268d9b3f57SJake Burkholder20030126: 6278d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 6288d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 6298d9b3f57SJake Burkholder 6301c5efda5SJeff Roberson20030125: 6311c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 6321c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 633ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 6341c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 6351c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 6361c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 6371c5efda5SJeff Roberson 6389d1d64f5SWarner Losh20030115: 6399d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 6409d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 6419d1d64f5SWarner Losh properly. 6429d1d64f5SWarner Losh 643c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 644c9fdb80aSWarner Losh configured for point to point links to bring it more in line 645c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 646c9fdb80aSWarner Losh with NetBSD. 647c9fdb80aSWarner Losh 648161dc364SAlexander Kabaev20021222: 649161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 650161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 651161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 652161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 653161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 654161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 65584cc83efSAlexander Kabaev rebuilt. 656161dc364SAlexander Kabaev 657fb4c8061SMartin Blapp20021216: 658fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 65989056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 660fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 6619d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 662fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 663fb4c8061SMartin Blapp 66417d47eb3SGiorgos Keramidas20021202: 66517d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 66617d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 66717d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 66817d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 66917d47eb3SGiorgos Keramidas 670a4459294SBill Fenner20021029: 671a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 672a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 673a4459294SBill Fenner consumers in sync. 674a4459294SBill Fenner 675fc8c157fSWarner Losh20021024: 676c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 677c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 678c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 679c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 680c57404feSRuslan Ermilov partition really is on. The old device names have gone 681c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 682c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 683c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 68469f7bcf3SWarner Losh 685fd9e8bdaSAndrew Gallatin20021023: 686fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 687fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 688fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 689fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 690fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 691fd9e8bdaSAndrew Gallatin 692fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 693fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 694fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 695fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 696fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 697fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 698fd9e8bdaSAndrew Gallatin 699f8a4c901SWarner Losh20020831: 700f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 701f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 702f8a4c901SWarner Losh programs and libraries need to be recompiled. 703f8a4c901SWarner Losh 704f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 705f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 706f8a4c901SWarner Losh 707c2248fa2SJens Schweikhardt20020827: 708c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 709c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 710c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 711c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 712c2248fa2SJens Schweikhardt 7130d533e43SRuslan Ermilov20020815: 7140d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 7150d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 7160d533e43SRuslan Ermilov again. 7170d533e43SRuslan Ermilov 71833c1de7dSRuslan Ermilov20020729: 71933c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 72033c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 72133c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 72233c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 72333c1de7dSRuslan Ermilov 7242b877facSJulian Elischer20020702: 7252b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 7262b877facSJulian Elischer There are still some minor problems with some signals but the 7272b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 7282b877facSJulian Elischer but each can successfully complete multiple buildworlds. 7292b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 7302b877facSJulian Elischer 73106596d37SWarner Losh20020701: 73206596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 73306596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 73406596d37SWarner Losh GNOME. 73506596d37SWarner Losh 73695ba4330SJacques Vidrine20020511: 73795ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 73895ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 73995ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 74095ba4330SJacques Vidrine with the set-user-ID bit set. 74195ba4330SJacques Vidrine 742a81da3c9SDavid E. O'Brien20020510: 743f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 744f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 7454b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 746f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 747f50caf6fSDavid E. O'Brien 748f50caf6fSDavid E. O'Brien20020510: 749a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 750a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 751a81da3c9SDavid E. O'Brien and then do a cvs update. 752a81da3c9SDavid E. O'Brien 753528a0ef5SJacques Vidrine20020421: 754528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 755528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 756528a0ef5SJacques Vidrine 75785aa5a2eSGregory Neil Shapiro20020404: 75885aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 75985aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 76085aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 76185aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 76285aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 76385aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 76485aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 76585aa5a2eSGregory Neil Shapiro 7668f1e4358SRuslan Ermilov20020403: 7678f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 7688f1e4358SRuslan Ermilov 7692292c02eSWarner Losh20020315: 7702292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 7712292c02eSWarner Losh 77269f7bcf3SWarner Losh20020225: 77369f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 77469f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 77569f7bcf3SWarner Losh 7768f35c493SWarner Losh20020217: 7778f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 7788f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 7798f35c493SWarner Losh command line mail submission has changed. Be sure to run 7808f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 7818f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 7828f35c493SWarner Losh 783835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 784835284beSWarner Losh required in order for sendmail to run as a set-group-ID 785835284beSWarner Losh binary. A 'make installworld' will use the new user and group 786835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 787835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 788835284beSWarner Losh and group must be merged from src/etc/group and 789835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 790835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 791835284beSWarner Losh mergemaster before this will work if you are updating from a 792835284beSWarner Losh very old version of current. The updating recipe has changed 793835284beSWarner Losh as of this date. 794835284beSWarner Losh 795fa9401c1SWarner Losh20020112: 796fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 797fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 798fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 799fa9401c1SWarner Losh you have local modifications, you can use 800fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 801fa9401c1SWarner Losh /etc/pam.d. 802fa9401c1SWarner Losh 803fa9401c1SWarner Losh Please see the following url for more details: 804fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 80547d0d01fSWarner Losh20011229: 80647d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 80747d0d01fSWarner Losh networkfs_types, please note that it has changed 80847d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 80947d0d01fSWarner Losh 810514318a8SWarner Losh20011220: 811514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 812514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 813514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 814514318a8SWarner Losh own. All the accumulated features and bug fixes of the i4b 815514318a8SWarner Losh version have now been merged back into the base system's 816514318a8SWarner Losh version now. The only user-visible change resulting from this 817514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 818514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 819514318a8SWarner Losh as well. (There has never been rc file support for 820514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 821514318a8SWarner Losh reverted by the time the changes are MFCed.) 822514318a8SWarner Losh 823514318a8SWarner Losh20011215: 824514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 825514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 826514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 827514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 828514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 829514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 830514318a8SWarner Losh will need to be customized then for `odd' densities using 831514318a8SWarner Losh fdcontrol(8). 832514318a8SWarner Losh 8332d22e2bfSWarner Losh20011209: 8342d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 8352d22e2bfSWarner Losh and truss(1) now works again. 8362d22e2bfSWarner Losh 8379e0428e2SWarner Losh20011207: 8389e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 8399e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 8409e0428e2SWarner Losh see 8419e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 8429e0428e2SWarner Losh for details. 8439e0428e2SWarner Losh 8449bab8c59SWarner Losh20011204: 8459bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 8469bab8c59SWarner Losh kernel and burncd to be in sync. 8479bab8c59SWarner Losh 848e57d8b01SWarner Losh20011203: 849e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 850e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 851e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 852e57d8b01SWarner Losh not there already. 853e57d8b01SWarner Losh 854e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 855e57d8b01SWarner Losh until the issue has been resolved. 856e57d8b01SWarner Losh 857b001d36fSJacques Vidrine20011202: 858b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 859b001d36fSJacques Vidrine patched. 860b001d36fSJacques Vidrine 8614b676ec1SWarner Losh20011126: 8624b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 8635ebbf43eSWarner Losh after this date. You need to do this only once. 8644b676ec1SWarner Losh 865d961e462SWarner Losh20011103: 866d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 867d961e462SWarner Losh edges may be left, but for the most part things should be 8684b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 869d961e462SWarner Losh 870d961e462SWarner Losh20011030: 871d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 872d961e462SWarner Losh choppy waves in the upgrade process. 873d961e462SWarner Losh 8741fe003b6SWarner Losh20011030: 875a4b6fda0SWarner Losh The asr driver problem has been resolved. 8761fe003b6SWarner Losh 8771fe003b6SWarner Losh20011027: 8781fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 8791fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 8801fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 8811fe003b6SWarner Losh try to use from this date forward. 8821fe003b6SWarner Losh 8831fe003b6SWarner Losh20011025: 8841fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 8851fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 8861fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 8871fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 8881fe003b6SWarner Losh TARGET_ARCH=i386. 8891fe003b6SWarner Losh 890d05f9643SWarner Losh20011001: 891d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 892d05f9643SWarner Losh You must recompile both the kernel and userland applications 893d05f9643SWarner Losh at the same time. 894d05f9643SWarner Losh 89558970f85SWarner Losh20010929: 89658970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 89758970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 89858970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 89958970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 9009d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 90158970f85SWarner Losh 90258970f85SWarner Losh20010927: 90358970f85SWarner Losh Some weird problems result from using ACPI on some machines. 90458970f85SWarner Losh To disable ACPI you can add 90566ff0e67SMax Khon hint.acpi.0.disabled="1" 90658970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 90758970f85SWarner Losh loader "ok" prompt). 90858970f85SWarner Losh 90958970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 91058970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 91158970f85SWarner Losh file and not list acpi in that list. 912378f4486SAlfred Perlstein 9135119d237SWarner Losh20010924: 9145119d237SWarner Losh The buildworld has been fixed. You may need to install 9155119d237SWarner Losh the 4.x compatibility libraries for some old binaries 9168b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 9178b039fffSWarner Losh get them installed on every installworld, or execute the 9188b039fffSWarner Losh following to get them installed only once: 9198b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 92058970f85SWarner Losh make all install 9218b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 9225119d237SWarner Losh 9233c293725SWarner Losh20010919: 9243c293725SWarner Losh There's a bug in the world build process. The cross-tools 9253c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 9263c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 927772730c7SWarner Losh workaround is to add 9283c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 9293c293725SWarner Losh before building world when upgrading from 4.x to current. This 9303c293725SWarner Losh can be removed afterwards. 9313c293725SWarner Losh 9323c293725SWarner Losh A proper fix to the buildworld target is needed. 9333c293725SWarner Losh 9343c293725SWarner Losh20010918: 9353c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 9363c293725SWarner Losh NFS may be unstable after this date. 9373c293725SWarner Losh 9383c293725SWarner Losh20010912: 9393c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 9403c293725SWarner Losh the kernel. While a few problems were introduced in the 9413c293725SWarner Losh initial commit, most of the major ones have been found and 9423c293725SWarner Losh corrected. 9433c293725SWarner Losh 9443c293725SWarner Losh20010901: 9453c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 9463c293725SWarner Losh arounds described in the 20010604 entry are now no longer 9473c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 9483c293725SWarner Losh have been rectified around this date. 9493c293725SWarner Losh 95098b17b95SWarner Losh20010823: 95198b17b95SWarner Losh named now runs as user bind and group bind rather than as 95298b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 95398b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 95498b17b95SWarner Losh and that group bind is available in /etc/group. Also make 95598b17b95SWarner Losh sure that user or group bind has read (and not write) 95698b17b95SWarner Losh permission for your name server configuration and that it 95798b17b95SWarner Losh has read and write permission for your slave zone files and 95898b17b95SWarner Losh directory. 95998b17b95SWarner Losh 96098b17b95SWarner Losh If you wish to continue to run named as root (a less secure 96198b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 96298b17b95SWarner Losh 96398b17b95SWarner Losh named_flags= 96498b17b95SWarner Losh 9657b9786edSMark Murray20010709: 9667b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 9677b9786edSMark Murray the ability of the shared library major number to handle. 9687b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 9697b9786edSMark Murray solution is to rebuild those ports. 9707b9786edSMark Murray 9711d28950eSWarner Losh20010628: 9721d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 9731d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 9741d28950eSWarner Losh 975e72fd46aSWarner Losh20010625: 97698b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 97798b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 97898b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 97998b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 98098b17b95SWarner Losh IRQ configuration needs more safety belts. 98116de1a07SWarner Losh 9820d415dffSWarner Losh20010617: 983e72fd46aSWarner Losh Softupdates problems have been corrected. 9840d415dffSWarner Losh 9850d415dffSWarner Losh20010614: 9860d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 9870d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 9880d415dffSWarner Losh kernel building methods. 9890d415dffSWarner Losh 9908b9959adSWarner Losh20010613: 9918b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 9928b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 993e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 994e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 9958b9959adSWarner Losh 996e72fd46aSWarner Losh20010613: 9978b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 998e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 999e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 10008b9959adSWarner Losh 10010d415dffSWarner Losh20010612: 10020d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 10030d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 10040d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 10050d415dffSWarner Losh work around this issue, please use only one or the other mechanism 10060d415dffSWarner Losh until this bug is fixed. 10070d415dffSWarner Losh 1008e72fd46aSWarner Losh Please note that a feature of config is that if you have config 1009e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 1010ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 1011e72fd46aSWarner Losh 10120d415dffSWarner Losh20010610: 10130d415dffSWarner Losh Locale names have changed to match other systems better. 10140d415dffSWarner Losh 10156ccdb5e4SWarner Losh20010604: 10166ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 10176ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 10186ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 10193590182eSWarner Losh Interrupt storms look a lot like a hang. 10203590182eSWarner Losh 10213590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 10223590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 10233590182eSWarner Losh it is). 10243590182eSWarner Losh 10253590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 10263590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 10273590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 10283590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 10296ccdb5e4SWarner Losh 10300bc62786SWarner Losh20010530: 10310bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 10320bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 10330bc62786SWarner Losh a limited time. If you see 10340bc62786SWarner Losh 10350bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 10360bc62786SWarner Losh 10370bc62786SWarner Losh in your makeworld, then you need to migrate towards using 10380bc62786SWarner Losh COPY=-C. 10390bc62786SWarner Losh 104068a38c6cSWarner Losh20010525: 1041b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 1042c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 1043c4f4a728SWarner Losh definitely is in bad shape. 104468a38c6cSWarner Losh 1045ed0f29caSWarner Losh20010521: 1046ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 1047ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 1048ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 1049ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 1050ed0f29caSWarner Losh is 1051ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 1052ed0f29caSWarner Losh 105380c16af9SWarner Losh20010520: 105468a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 105580c16af9SWarner Losh 105680c16af9SWarner Losh20010519: 105780c16af9SWarner Losh pccard has had much reorganizational work done to it over 105880c16af9SWarner Losh the past few days. Everything should still work, but if 105980c16af9SWarner Losh not, please contact imp@freebsd.org. 106080c16af9SWarner Losh 1061a45f2d05SWarner Losh20010517: 1062a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 1063a45f2d05SWarner Losh userland at the same time. 1064a45f2d05SWarner Losh 1065a45f2d05SWarner Losh20010517: 1066a45f2d05SWarner Losh New ncurses imported. 1067a45f2d05SWarner Losh 10682988afcaSWarner Losh20010512: 10692988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 10702988afcaSWarner Losh will be the only way to go starting July 1. 10712988afcaSWarner Losh 10721a33dba7SWarner Losh20010504: 10731a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 10741a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 10751a33dba7SWarner Losh 107609946a51SWarner Losh20010502: 107709946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 107809946a51SWarner Losh 107909946a51SWarner Losh20010501: 108009946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 108109946a51SWarner Losh 108209946a51SWarner Losh20010430: 1083a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 108409946a51SWarner Losh go back in the water. 108509946a51SWarner Losh 108609946a51SWarner Losh20010429: 108709946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 108809946a51SWarner Losh this date, but before the correction date. 108909946a51SWarner Losh 109091dd3b53SWarner Losh20010423: 109191dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 109291dd3b53SWarner Losh 109391dd3b53SWarner Losh20010411: 109491dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 109591dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 109691dd3b53SWarner Losh Update only if you understand that you must not use the old 109791dd3b53SWarner Losh fsck with the new kernel ever. 109891dd3b53SWarner Losh 1099933b3269SWarner Losh20010330: 1100933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 1101c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 1102933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 1103933b3269SWarner Losh 1104933b3269SWarner Losh20010319: 1105933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 1106933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 1107933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 1108f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 110909946a51SWarner Losh 111009946a51SWarner Losh20010315: 111109946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 1112ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 111309946a51SWarner Losh been replaced by tunables. See ata.4 for details. 1114933b3269SWarner Losh 1115933b3269SWarner Losh20010312: 1116933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 1117933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 1118933b3269SWarner Losh 1119933b3269SWarner Losh20010312: 1120933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 1121933b3269SWarner Losh instead of ad-hoc. 1122933b3269SWarner Losh 1123933b3269SWarner Losh20010310: 1124f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 1125933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 1126933b3269SWarner Losh ssh might not work if you don't. 1127933b3269SWarner Losh 112862353691SWarner Losh20010303: 112962353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 113062353691SWarner Losh which means that you must include the miibus in your kernel if 113162353691SWarner Losh you use the ed driver. 113262353691SWarner Losh 1133d325cf65SWarner Losh20010220: 1134d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 1135d325cf65SWarner Losh safe to go back into the water. 1136d325cf65SWarner Losh 1137024daae6SWarner Losh20010211: 1138024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 1139024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 1140024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 1141024daae6SWarner Losh that before upgrading would be a good time to do a level 0 1142024daae6SWarner Losh dump of your system. No, really, I mean it this time. 1143024daae6SWarner Losh 1144024daae6SWarner Losh To get to the new system, you'll need to use the following 1145024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 1146024daae6SWarner Losh don't have to move this to the updating section. 1147024daae6SWarner Losh 1148024daae6SWarner Losh To get around the installworld problem, do: 1149024daae6SWarner Losh # cd /usr/src/usr.bin/sed 1150024daae6SWarner Losh # make install 1151024daae6SWarner Losh # cd /usr/src 1152024daae6SWarner Losh # make installworld 1153024daae6SWarner Losh If that doesn't work, then try: 1154024daae6SWarner Losh # make -k installworld 1155024daae6SWarner Losh # make installworld 1156024daae6SWarner Losh 1157024daae6SWarner Losh20010207: 1158024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 1159024daae6SWarner Losh do not include devfs in your kernel as problems result. 1160024daae6SWarner Losh 1161024daae6SWarner Losh20010205: 11627595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 1163024daae6SWarner Losh Remove them from your config. 1164024daae6SWarner Losh 11651e159248SWarner Losh20010122: 11661e159248SWarner Losh ****************************** WARNING ****************************** 11671e159248SWarner Losh buildkernel has been changed slightly 11681e159248SWarner Losh ****************************** WARNING ****************************** 11691e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 11701e159248SWarner Losh should update your scripts and make.conf accordingly. 11711e159248SWarner Losh 11721e159248SWarner Losh20010119: 11731e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 11741e159248SWarner Losh This requires a new config to build correctly. 11751e159248SWarner Losh 1176aac7dfeaSWarner Losh20010116: 1177ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 1178aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 1179aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 1180aac7dfeaSWarner Losh 1181aac7dfeaSWarner Losh20010110: 1182aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 1183aac7dfeaSWarner Losh 1184aac7dfeaSWarner Losh20010102: 1185aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 1186aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 1187aac7dfeaSWarner Losh 118863c90c9eSWarner Losh20010101: 118963c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 119063c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 11915fd2a895SWarner Losh dump while building termcap. You can work around this problem 119263c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 119363c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 119463c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 119563c90c9eSWarner Losh might have been ignored by the -k option. 119663c90c9eSWarner Losh 11975fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 11985fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 11995fd2a895SWarner Losh of this working. 12005fd2a895SWarner Losh 1201aac7dfeaSWarner Losh20001228: 1202aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 1203ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 1204aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 1205aac7dfeaSWarner Losh 1206de2bcc63SWarner Losh20001218: 1207de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 1208de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 1209de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 1210de2bcc63SWarner Losh cards will not be recognized without it. 1211de2bcc63SWarner Losh 1212960773f7SWarner Losh20001205: 1213960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 1214960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 1215960773f7SWarner Losh adding the following in pam.conf: 1216960773f7SWarner Losh 1217960773f7SWarner Losh sshd auth sufficient pam_skey.so 1218960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 1219960773f7SWarner Losh sshd session required pam_permit.so 1220960773f7SWarner Losh 12210acc635eSWarner Losh20001031: 12220acc635eSWarner Losh cvs updated to 1.11. 12230acc635eSWarner Losh 12240acc635eSWarner Losh20001020: 12250acc635eSWarner Losh The random device needs more entropy, so you need to make sure 12260acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 12270acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 12280acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 12290acc635eSWarner Losh workaround. 12300acc635eSWarner Losh 12310acc635eSWarner Losh20001010: 12320acc635eSWarner Losh ****************************** WARNING ****************************** 12330acc635eSWarner Losh Sendmail has been updated. 12340acc635eSWarner Losh ****************************** WARNING ****************************** 12350acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 12360acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 12370acc635eSWarner Losh is set. 12380acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 12390acc635eSWarner Losh commands. 12400acc635eSWarner Losh o Now using sendmail's version of vacation(1). 12410acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 12420acc635eSWarner Losh in /usr/share/sendmail/cf. 12430acc635eSWarner Losh o sendmail.cw changed to local-host-names 12440acc635eSWarner Losh 12450acc635eSWarner Losh More details can be found at 12460acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 12470acc635eSWarner Losh 12486e98a146SWarner Losh20001009: 12496e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 12506e98a146SWarner Losh your entire ports tree, or you will have problems. 12516e98a146SWarner Losh 12526e98a146SWarner Losh20001006: 1253685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 12546e98a146SWarner Losh the installed miniperl. It is recommended that you delete 12556e98a146SWarner Losh /usr/bin/miniperl. 12566e98a146SWarner Losh 1257073113a4SWarner Losh20001005: 1258073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1259685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1260073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1261073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1262073113a4SWarner Losh tree for anything to work. 1263073113a4SWarner Losh 12640acc635eSWarner Losh20000928: 12650acc635eSWarner Losh There was a change in the passwd format. Need more information. 12660acc635eSWarner Losh 1267be3885b3SWarner Losh20000916: 1268be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1269be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1270be3885b3SWarner Losh same time as your kernel. 1271be3885b3SWarner Losh 127276ec9675SWarner Losh20000914: 127376ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 127476ec9675SWarner Losh include the device will cause suspended laptops losing time 127576ec9675SWarner Losh when they resume. Include 127676ec9675SWarner Losh device pmtimer 127776ec9675SWarner Losh in your config file and 127801b9a434SWarner Losh hint.pmtimer.0.at="isa" 127976ec9675SWarner Losh to your /boot/device.hints file. 128076ec9675SWarner Losh 1281f4865386SMark Murray20000911: 1282f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1283f4865386SMark Murray rather than an option. The supplied kernel config files have 1284f4865386SMark Murray been updated. You will need to do something similar in your 1285f4865386SMark Murray own kernel config file. 1286f4865386SMark Murray Remove: 1287f4865386SMark Murray options RANDOMDEV 1288f4865386SMark Murray Add: 1289f4865386SMark Murray device random 1290f4865386SMark Murray If you prefer to load the loadable module, you need to do 1291f4865386SMark Murray nothing. 1292f4865386SMark Murray 1293d594498fSWarner Losh20000909: 1294d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1295d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1296d594498fSWarner Losh reflect this if you load this module at boot time. 1297d594498fSWarner Losh The line should read: 1298d594498fSWarner Losh random_load="YES" 1299d594498fSWarner Losh 13000deb7ddcSWarner Losh20000907: 13010deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 130216eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 130316eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 130416eb772dSWarner Losh sure you don't have model loading problems which might at 130516eb772dSWarner Losh first blush appear related to SMP. 130652bf24e7SWarner Losh 13075a01880bSWarner Losh20000906: 13085a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 13095a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 13105a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 13115a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 13125a01880bSWarner Losh don't have one, and you have host.conf. 13135a01880bSWarner Losh 13142b41163cSWarner Losh20000905: 131538d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 131638d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 131738d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 131838d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 131938d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 132038d6ecd2SWarner Losh 132138d6ecd2SWarner Losh20000905: 13228aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 13238aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 13248aab4bc7SWarner Losh is /boot/kernel. 13258aab4bc7SWarner Losh 13268aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 132738d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 132838d6ecd2SWarner Losh installkernel/installworld dance. 13292b41163cSWarner Losh 1330d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1331d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1332d594498fSWarner Losh modules in that directory instead of finding them in the correct 1333d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1334d594498fSWarner Losh is that the linux module crashes your machine after the update. 1335d594498fSWarner Losh 1336d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1337d594498fSWarner Losh mv /modules.old /boot/kernel.old 1338d594498fSWarner Losh chflags noschg /kernel.old 1339d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1340d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1341d594498fSWarner Losh fi 1342d594498fSWarner Losh 1343c22a309cSWarner Losh20000904: 1344c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1345c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1346c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1347c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1348c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1349c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1350c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1351c22a309cSWarner Losh is not likely to be generated. 1352c22a309cSWarner Losh 1353fdb9f54dSWarner Losh20000825: 1354fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 13559c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 13569c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 13579c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 13589c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 13599c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 13609c1a7444SWarner Losh messages will appear after the boot loader tries to start the 13619c1a7444SWarner Losh kernel. 13629c1a7444SWarner Losh 13639c1a7444SWarner Losh20000821: 13649c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 13659c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 13669c1a7444SWarner Losh /boot/loader.conf. 1367fdb9f54dSWarner Losh 13688f250aa7SWarner Losh20000812: 13695da0d091SWarner Losh suidperl is now always built and installed on the system, but 13705da0d091SWarner Losh with permissions of 511. If you have applications that use 13715da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 13725da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 13735da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 13745da0d091SWarner Losh will fix this until the next build. 13755da0d091SWarner Losh 13765da0d091SWarner Losh20000812: 13778f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 13788f250aa7SWarner Losh visible changes that may immediately affect your configuration 13798f250aa7SWarner Losh include: 13808f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 13818f250aa7SWarner Losh - newaliases limited to root and trusted users 13828f250aa7SWarner Losh - MSA port (587) turned on by default 13838f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 13848f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 13858f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 13868f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 13878f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 13888f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 13898f250aa7SWarner Losh 139071c38472SWarner Losh20000810: 139171c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 139271c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 139371c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 139471c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 139571c38472SWarner Losh specific use for it. 139671c38472SWarner Losh 139771c38472SWarner Losh20000729: 139871c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 139971c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 140071c38472SWarner Losh /etc/rc.conf if they want to have the same setup 140171c38472SWarner Losh afterwards (unless the variables already are set, of course): 140271c38472SWarner Losh # Enable network daemons for user convenience. 140371c38472SWarner Losh inetd_enable="YES" 140471c38472SWarner Losh portmap_enable="YES" 140571c38472SWarner Losh sendmail_enable="YES" 140671c38472SWarner Losh 140771c38472SWarner Losh20000728: 140871c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 140971c38472SWarner Losh will need to change that to nullfs_load="YES". 141071c38472SWarner Losh 14111dece4a9SWarner Losh20000728: 14121dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 14131dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 14141dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 14151dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 14161dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 14171dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 14181dece4a9SWarner Losh to /MYKERNEL. 14191dece4a9SWarner Losh 1420409e887cSWarner Losh20000711: 1421409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1422409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1423409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1424409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1425409e887cSWarner Losh for details on potential problems that you might have and how 1426409e887cSWarner Losh to get around them. 1427409e887cSWarner Losh 1428409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1429409e887cSWarner Losh clauses above, you needn't worry. 1430409e887cSWarner Losh 1431409e887cSWarner Losh20000711: 1432409e887cSWarner Losh /etc/security has been updated to print the inode number of 1433409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1434409e887cSWarner Losh in the number of changed programs the first time when you run 1435409e887cSWarner Losh mergemaster to get a new /etc/security. 1436409e887cSWarner Losh 1437673d13f2SWarner Losh20000710: 1438673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1439673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1440673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1441673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1442673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1443673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1444673d13f2SWarner Losh errors. (see below, 20000624). 1445673d13f2SWarner Losh 1446bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 14471dece4a9SWarner Losh 1448673d13f2SWarner Losh20000709: 1449c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1450c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1451c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1452673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1453673d13f2SWarner Losh 1454e98e26cdSWarner Losh20000706: 1455e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1456e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1457e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1458f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1459e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 14602c021c6cSMark Ovens interim if needed. 1461e98e26cdSWarner Losh 1462e98e26cdSWarner Losh20000705: 1463e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1464e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1465e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1466e98e26cdSWarner Losh details. 1467e98e26cdSWarner Losh 1468c373950eSWarner Losh20000704: 14692f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 14702f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 14712f961bc8SWarner Losh 14722f961bc8SWarner Losh20000704: 1473c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1474c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1475c373950eSWarner Losh rc.d scripts that haven't been updated. 1476c373950eSWarner Losh 147727dc3a2bSWarner Losh20000630: 147827dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 147927dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 148027dc3a2bSWarner Losh which should be reported to des@freebsd.org. 148127dc3a2bSWarner Losh 1482b8c215acSWarner Losh20000625: 1483b8c215acSWarner Losh From approximately this date forward, one must have the crypto 148427dc3a2bSWarner Losh system installed in order to build the system and kernel. 148527dc3a2bSWarner Losh While not technically strictly true, one should treat it as 148627dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 148727dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 148827dc3a2bSWarner Losh were required. You should check with the latest collections 148927dc3a2bSWarner Losh to make sure that these haven't changed. 1490b8c215acSWarner Losh 14917b990719SWarner Losh20000624: 14927b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 14937b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 14947b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 14951a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 14967b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 14977b990719SWarner Losh openssh and openssl should not be used to generate keys from this 14987b990719SWarner Losh date to the completion of the work. 14997b990719SWarner Losh 150027dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 150127dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 150227dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 150327dc3a2bSWarner Losh recreate the random and urandom devices. 150427dc3a2bSWarner Losh 150581e54c50SWarner Losh20000622: 150681e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 150781e54c50SWarner Losh BSD license. You may need to remove your symbolic links 150881e54c50SWarner Losh that used to be required when updating. 150981e54c50SWarner Losh 151039943833SWarner Losh20000621: 15112c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 15122a2f33fbSDaniel Baker the config file update procedure. 15132a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1514c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 151559df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 151659df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 151739943833SWarner Losh 1518290f9ad8SWarner Losh20000620: 1519290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1520290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1521290f9ad8SWarner Losh that workaround will no longer be required. 1522290f9ad8SWarner Losh 152390fb6346SWarner Losh20000615: 152490fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 152590fb6346SWarner Losh ad driver. If you haven't done so already, you must update 152690fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 152790fb6346SWarner Losh devices. 152890fb6346SWarner Losh 1529f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1530f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1531f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1532f75f65bbSWarner Losh may work). 1533f75f65bbSWarner Losh 1534ba26da8eSWarner Losh20000612: 1535ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1536290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1537c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1538290f9ad8SWarner Losh to your config file to compile them in statically. The format 1539f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1540f54a3542SWarner Losh NEWCARD for examples of the new format. 1541290f9ad8SWarner Losh 15429698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 15439698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 15449698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 15459698f2c0SWarner Losh in it. 1546bbcc5149SWarner Losh 1547d65850ebSWarner Losh20000522: 1548ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1549d65850ebSWarner Losh building a kernel after this point is advised that they need 1550d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1551d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1552d65850ebSWarner Losh 1553d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1554d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1555d9583a00SWarner Losh is recommended that you don't set this option until the problem 1556d9583a00SWarner Losh is resolved. 1557d9583a00SWarner Losh 15588039cedeSWarner Losh20000513: 15598039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 15608039cedeSWarner Losh 1561d65850ebSWarner Losh20000510: 15628039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 15638039cedeSWarner Losh This will require some care in updating alphas. A new libstand 15648039cedeSWarner Losh is requires for the boot blocks to build properly. 15658039cedeSWarner Losh 15668039cedeSWarner Losh20000503: 15678039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 15688039cedeSWarner Losh is now available. 15698039cedeSWarner Losh 1570d65850ebSWarner Losh20000502: 1571d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1572d65850ebSWarner Losh connected to the kernel building instead. 1573d65850ebSWarner Losh 1574be149406SNik Clayton20000427: 15758039cedeSWarner Losh You may need to build gperf 15768039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 15778039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 15788039cedeSWarner Losh an option only in -current. 15798039cedeSWarner Losh 15802b8dd5f4SWarner Losh20000417: 15812b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1582f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 15832b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 15842b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 15852c021c6cSMark Ovens before you reboot, you'll need to issue: 15862b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 15872b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 15882b8dd5f4SWarner Losh 15898d9f1945SWarner Losh20000320: 15902b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 15912b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 15922b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1593ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 15942b8dd5f4SWarner Losh to the start of /etc/rc.conf. 15958d9f1945SWarner Losh 1596f8ab1dd6SWarner Losh20000319: 1597f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1598f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1599f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1600f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1601f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1602f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1603f8ab1dd6SWarner Losh 160419cada77SWarner Losh20000318: 1605f699bbbbSMark Ovens We've entered the traditional post release dumping party. 160619cada77SWarner Losh Large kernel changes are being committed and are in the 160719cada77SWarner Losh works. It is important to keep the systems' klds and kernel 160819cada77SWarner Losh in sync as kernel interfaces and structures are changing. 160919cada77SWarner Losh Before reporting kernel panics, make sure that all modules 161019cada77SWarner Losh that you are loading are up to date. 1611ba228352SWarner Losh 161219cada77SWarner Losh20000315: 16136d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 16146d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 16156d23c382SWarner Losh will do the trick. This isn't critical until you remove your 16166d23c382SWarner Losh wd device entries in /dev, at which point your system will not 16176d23c382SWarner Losh boot. 16186d23c382SWarner Losh 16196d23c382SWarner Losh20000315: 162019cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 162119cada77SWarner Losh to upgrade to 4.0 from 3.x. 162257199806SWarner Losh 1623dc0dbf5cSWarner LoshCOMMON ITEMS: 1624dc0dbf5cSWarner Losh 1625cd5f061cSWarner Losh # NOTE: 5.x below applies to 6.0-currrent as well, for the 1626cd5f061cSWarner Losh # momemnt. 4.any -> 5.any upgrade support will remain in 1627cd5f061cSWarner Losh # place for 6.0 current, but after 5.3 RELEASE, the 4.any -> 1628cd5f061cSWarner Losh # 6.0-current upgrade path will require moving through 5.3 1629cd5f061cSWarner Losh # RELEASE or newer. 1630cd5f061cSWarner Losh 1631a24eff53SWarner Losh General Notes 1632a24eff53SWarner Losh ------------- 1633a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1634a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1635a24eff53SWarner Losh installworld. This is especially true when upgrading between 1636a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1637a24eff53SWarner Losh or several minor releases, or when several months have passed 1638a24eff53SWarner Losh on the -current branch). 1639a24eff53SWarner Losh 16405780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 16415780f3baSWarner Losh poisoning. This can happen because the make utility reads its 16425780f3baSWarner Losh environment when searching for values for global variables. 16435780f3baSWarner Losh To run your build attempts in an "environmental clean room", 16445780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 16455780f3baSWarner Losh page for more details. 16465780f3baSWarner Losh 1647dc0dbf5cSWarner Losh To build a kernel 1648dc0dbf5cSWarner Losh ----------------- 1649ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1650f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1651ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1652282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1653282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1654dc0dbf5cSWarner Losh 1655ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1656ba01eb20SWarner Losh -------------------------------------------------------------- 16570fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 16580fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 16590fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 16600fbd2da9SKen Smith 16610fbd2da9SKen Smith cd src/sys/${arch}/conf 166247d0d01fSWarner Losh config KERNEL_NAME_HERE 16630fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1664ba01eb20SWarner Losh make depend 1665ba01eb20SWarner Losh make 1666ba01eb20SWarner Losh make install 1667ba01eb20SWarner Losh 1668ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1669ba01eb20SWarner Losh 1670ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1671ba01eb20SWarner Losh ----------------------------------------------------------- 167263cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 167363cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 167463cb445eSWarner Losh 1675f643de42SWarner Losh <make sure you have good level 0 dumps> 167663cb445eSWarner Losh <maybe fix /etc/fstab> [7] 167763cb445eSWarner Losh make buildworld 16786586253aSWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE 167963cb445eSWarner Losh [1] 168063cb445eSWarner Losh <reboot in single user> [3] 16816586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 168263cb445eSWarner Losh mergemaster -p [5] 168363cb445eSWarner Losh make installworld 168463cb445eSWarner Losh mergemaster [4] 168563cb445eSWarner Losh <reboot> 168663cb445eSWarner Losh 1687759f0aefSWarner Losh 1688f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1689f27b1fceSJoseph Koshy -------------------------------------------------- 1690f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1691f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1692f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1693f27b1fceSJoseph Koshy # size. 1694f27b1fceSJoseph Koshy 1695f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1696f27b1fceSJoseph Koshy <boot into -stable> 1697f27b1fceSJoseph Koshy make buildworld 1698f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1699f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1700f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1701f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 17026586253aSWarner Losh cp src/sys/${ARCH}/conf/GENERIC.hints \ 1703f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1704f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 17056586253aSWarner Losh cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1706f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1707f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1708f27b1fceSJoseph Koshy <reboot into current> 1709f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 17106586253aSWarner Losh <maybe install compatibility libraries from src/lib/compat> 1711f27b1fceSJoseph Koshy <reboot> 1712f27b1fceSJoseph Koshy 1713f27b1fceSJoseph Koshy 1714f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1715f27b1fceSJoseph Koshy ---------------------------------------------- 17165c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 1717e5dc5f61SWarner Losh # modules has changed. If you are installing 5.x onto a 4.x 17185c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 17195c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1720ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1721f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1722f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1723f643de42SWarner Losh # space on /. 1724f643de42SWarner Losh 1725f643de42SWarner Losh <make sure you have good level 0 dumps> 1726fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 172721c075eaSWarner Losh make buildworld [9] 1728802fc49dSBrian Feldman cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1729e5dc5f61SWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1730802fc49dSBrian Feldman cd sys/boot ; make STRIP="" install [6] 1731fc8c157fSWarner Losh [1] 1732fc8c157fSWarner Losh <reboot in single user> [3] 17336586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 1734835284beSWarner Losh mergemaster -p [5] 1735f8a4c901SWarner Losh rm -rf /usr/include/g++ 1736ba26da8eSWarner Losh make installworld 1737802fc49dSBrian Feldman mergemaster -i [4] 1738ba26da8eSWarner Losh <reboot> 1739ba26da8eSWarner Losh 1740fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1741fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1742fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1743fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1744fdb9f54dSWarner Losh the UPDATING entries. 1745ba26da8eSWarner Losh 17461dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 17471dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 17481dece4a9SWarner Losh your sources that you have read and understood all the recent 17491dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 17501dece4a9SWarner Losh much fewer pitfalls. 17511dece4a9SWarner Losh 1752134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1753134d2e86SWarner Losh should disable them at this point so they don't crash your 1754134d2e86SWarner Losh system on reboot. 1755134d2e86SWarner Losh 17569c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 17579c1a7444SWarner Losh your own device.hints to reflect your unique hardware 17589c1a7444SWarner Losh configuration. 17599c1a7444SWarner Losh 1760ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1761ee6e1fc3SWarner Losh fsck -p 1762ee6e1fc3SWarner Losh mount -u / 1763ee6e1fc3SWarner Losh mount -a 17646586253aSWarner Losh cd src 176547d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1766f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1767f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 176866986952SRuslan Ermilov For the 4.x -> 5.x upgrade, you will also see many messages about 1769b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1770b705ae10SWarner Losh be ignored while you proceed to the next step. 1771ee6e1fc3SWarner Losh 1772a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1773a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1774a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1775a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1776a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1777a6cd4f9dSWarner Losh for potential gotchas. 1778a6cd4f9dSWarner Losh 1779835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1780835284beSWarner Losh you may need to do this if you get unknown user in the following 1781835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1782835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1783835284beSWarner Losh install) after the buildworld before this step if you last updated 1784835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1785835284beSWarner Losh 1786bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1787bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1788bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1789bd79cf40SWarner Losh ok unload 1790bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1791bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1792bd79cf40SWarner Losh described here. 1793fc8c157fSWarner Losh 1794fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1795e5dc5f61SWarner Losh compatibility slices. These are device names of the form /dev/ad0a 1796e5dc5f61SWarner Losh without the actual slice name. These will break with 5.x and newer. 1797fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1798e5dc5f61SWarner Losh 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha 1799e5dc5f61SWarner Losh is not. 1800fc8c157fSWarner Losh 1801c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1802c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1803c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1804c74fe6afSWarner Losh that is hard to boot to recover. 1805c74fe6afSWarner Losh 1806e5dc5f61SWarner Losh Make sure that you merge any new devices from GENERIC since the 1807e5dc5f61SWarner Losh last time you updated your kernel config file. 1808e5dc5f61SWarner Losh 180921c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 1810e5dc5f61SWarner Losh cvs prune empty directories. 1811e5dc5f61SWarner Losh 1812e5dc5f61SWarner Losh If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1813e5dc5f61SWarner Losh "?=" instead of the "=" assignment operator, so that buildworld can 1814e5dc5f61SWarner Losh override the CPUTYPE if it needs to. 1815e5dc5f61SWarner Losh 1816e5dc5f61SWarner Losh MAKEOBJDIRPREFIX must be defined in an environment variable, and 1817e5dc5f61SWarner Losh not on the command line, or in /etc/make.conf. buildworld will 1818e5dc5f61SWarner Losh warn if it is improperly defined. 1819e5dc5f61SWarner Losh 1820802fc49dSBrian Feldman In case you would like to avoid installing new packages of everything, 1821802fc49dSBrian Feldman you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 182266986952SRuslan Ermilov compatibility libraries are built which should allow you to continue 1823e5dc5f61SWarner Losh using your existing software for a while. Alternatively, you can 1824e5dc5f61SWarner Losh install the misc/compat4x port. 18258633bbeaSBrooks Davis 18268633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 18276586253aSWarner Losh initialized by feeding data into it. src/etc/rc.d/preseedrandom 18288633bbeaSBrooks Davis takes care of this. 1829dc0dbf5cSWarner LoshFORMAT: 1830dc0dbf5cSWarner Losh 1831f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 18321fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1833f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1834f8ab1dd6SWarner Loshprevious releases if your system is older than this. 18351fc1a0dcSWarner Losh 1836e72fd46aSWarner LoshCopyright information: 1837e72fd46aSWarner Losh 1838e5dc5f61SWarner LoshCopyright 1998-2004 M. Warner Losh. All Rights Reserved. 1839e72fd46aSWarner Losh 1840772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1841772730c7SWarner Loshmodification, in full or in part, in any form or format of this 18429698f2c0SWarner Loshdocument are permitted without further permission from the author. 1843e72fd46aSWarner Losh 1844e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1845e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1846e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1847e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1848e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1849e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1850e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1851e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1852e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1853e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1854e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1855e72fd46aSWarner Losh 1856e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1857e72fd46aSWarner Loshauthor a beer. 1858e72fd46aSWarner Losh 185922306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1860772730c7SWarner Loshthis document. 1861772730c7SWarner Losh 186297d92980SPeter Wemm$FreeBSD$ 1863