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 265d36721aSDoug Barton20040925: 275d36721aSDoug Barton BIND 9 has been imported into the base, and is now fully 285d36721aSDoug Barton functional. BIND 8 has now been removed. There are numerous 295d36721aSDoug Barton differences between BIND 8 and 9, and users with critical 305d36721aSDoug Barton named installations should read the migration documentation 315d36721aSDoug Barton in /usr/share/doc/bind9/misc/migration. There is also a 325d36721aSDoug Barton new instruction manual in /usr/share/doc/bind9/arm. 335d36721aSDoug Barton 345d36721aSDoug Barton The key differences that most users will experience are in 355d36721aSDoug Barton how picky BIND 9 is about zone file format. If you are using 365d36721aSDoug Barton named as a resolving (caching) name server, you will likely 375d36721aSDoug Barton not have trouble. 385d36721aSDoug Barton 39f5ee5a8bSMax Laier20040914: 40f5ee5a8bSMax Laier The format of the pflogd(8) logfile "/var/log/pflog" has changed for 41f5ee5a8bSMax Laier architectures that have a 64 bit long type to make it compatible to 42f5ee5a8bSMax Laier the standard pcap format. In order to prevent corruption move away 43f5ee5a8bSMax Laier any old logfile before using a new pflogd(8). 44f5ee5a8bSMax Laier 45d698cdb3SJohn-Mark Gurney20040906: 46d698cdb3SJohn-Mark Gurney debug.witness_* has been renamed to debug.witness.*. There are 47d698cdb3SJohn-Mark Gurney compatibility tunables left in for a few days. Update loader.conf 48d698cdb3SJohn-Mark Gurney as necessary. 49d698cdb3SJohn-Mark Gurney 504ff62bd9SBrooks Davis20040902: 514ff62bd9SBrooks Davis The ifi_epoch change has been reverted because the ABI breakage 524ff62bd9SBrooks Davis was too extensive. If you are running with a kernel/userland 534ff62bd9SBrooks Davis containing the initial change (20040830), you should heed the 544ff62bd9SBrooks Davis warning about ifconfig incompatibility when upgrading again. 554ff62bd9SBrooks Davis With this change, 5.3 and 6.0 ifconfigs and kernels are once 564ff62bd9SBrooks Davis again interoperable. 574ff62bd9SBrooks Davis 581fc4519bSBrooks Davis20040830: 591fc4519bSBrooks Davis A new variable, ifi_epoch, has been added to struct if_data 601fc4519bSBrooks Davis which is part if struct ifnet. This means all network drivers 611fc4519bSBrooks Davis and network monitoring applications need to be recompiled. 621fc4519bSBrooks Davis 633789fb75SBrooks Davis WARNING WARNING WARNING WARNING WARNING WARNING WARNING 643789fb75SBrooks Davis 653789fb75SBrooks Davis This also breaks ifconfig compatibility. An old ifconfig will 663789fb75SBrooks Davis not work with the new kernel and a new ifconfig will not work 673789fb75SBrooks Davis with the old. It is strongly recommended that you make a copy 683789fb75SBrooks Davis of your old ifconfig before installworld. If you are installing 693789fb75SBrooks Davis remotely, you must copy over a new ifconfig before rebooting in 703789fb75SBrooks Davis to the new kernel. 713789fb75SBrooks Davis 72c1c94d5cSRobert Watson20040828: 73c1c94d5cSRobert Watson The default configuration for the network stack has been changed 74c1c94d5cSRobert Watson such that it now runs without the Giant lock unless configured 75c1c94d5cSRobert Watson otherwise. If you experience network-related instability, you 76c1c94d5cSRobert Watson may wish to try setting "debug.mpsafenet=0" or compiling the 77c1c94d5cSRobert Watson kernel with "options NET_WITH_GIANT". Details on the netperf 78c1c94d5cSRobert Watson project may be found at: 79c1c94d5cSRobert Watson 80c1c94d5cSRobert Watson http://www.watson.org/~robert/freebsd/netperf/ 81c1c94d5cSRobert Watson 82c1c94d5cSRobert Watson Including the 20040828 announcement of configuration change 83c1c94d5cSRobert Watson details. 84c1c94d5cSRobert Watson 85c21fd232SAndre Oppermann20040827: 86c21fd232SAndre Oppermann PFIL_HOOKS are a fixed part of the network stack now and do not 87c21fd232SAndre Oppermann need to be specified in the kernel configuration file anymore. 88c21fd232SAndre Oppermann 89f036d408SJulian Elischer20040819: 90f036d408SJulian Elischer Netgraph changed its message format slightly to align the data 91f036d408SJulian Elischer portion well on 64 bit machines. 92f036d408SJulian Elischer Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd, 93f036d408SJulian Elischer pppoed, bluetooth, ATM) should be recompiled when a new kernel 94f036d408SJulian Elischer is installed. 95f036d408SJulian Elischer 96b067abfaSAndre Oppermann20040817: 970ce70eb4SAndre Oppermann IPFW has been converted to use PFIL_HOOKS. This change is 98b067abfaSAndre Oppermann transparent to userland and preserves the ipfw ABI. The ipfw 99b067abfaSAndre Oppermann core packet inspection and filtering functions have not been 100b067abfaSAndre Oppermann changed, only how ipfw is invoked is different. Note that 101b067abfaSAndre Oppermann "option PFIL_HOOKS" is required to use IPFIREWALL compiled 102b067abfaSAndre Oppermann into the kernel or as KLD. 103b067abfaSAndre Oppermann 104f13a7951SDavid Malone20040814: 105f13a7951SDavid Malone The RANDOM_IP_ID option has been replaced by the sysctl 106f13a7951SDavid Malone net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then 107f13a7951SDavid Malone you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf. 108f13a7951SDavid Malone 1093a004637SMax Laier20040807: 1103a004637SMax Laier The size of 'struct ifnet' has changed due to the addition of the 1113a004637SMax Laier if_carp placeholder. All kernel modules implementing network 1123a004637SMax Laier interfaces must be recompiled as a result. 1133a004637SMax Laier 1144f34d8d1SJohn-Mark Gurney20040806: 1154f34d8d1SJohn-Mark Gurney Module loading has been fixed. Some older installations will 116ac41c814SRuslan Ermilov drop proper module_path initialization and modules will fail to 1174f34d8d1SJohn-Mark Gurney load properly. If you have a line in /boot/loader.rc that says: 1184f34d8d1SJohn-Mark Gurney "initialize drop", do (i386 only): 1194f34d8d1SJohn-Mark Gurney cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc 1204f34d8d1SJohn-Mark Gurney chown root:wheel /boot/loader.rc 1214f34d8d1SJohn-Mark Gurney chmod 444 /boot/loader.rc 1224f34d8d1SJohn-Mark Gurney 1238f075db4SMark Murray20040802: 1248f075db4SMark Murray making /dev/(null|zero) into a module proved to be too unpopular, 1258f075db4SMark Murray so this bit has been revoked from the previous (20040801) entry. 1268f075db4SMark Murray 127d064d6dbSMark Murray20040801: 128d064d6dbSMark Murray The /dev/mem, /dev/io /dev/(null/zero) devices are now modules, 129d064d6dbSMark Murray so you may wish to add them to your kernel config file. See 130d064d6dbSMark Murray GENERIC for examples. 131d064d6dbSMark Murray 132b289983eSAlexander Kabaev20040728: 13354bd5271SAlexander Kabaev System compiler has been upgraded to GCC 3.4.2-pre. As with any major 13454bd5271SAlexander Kabaev compiler upgrade, there are several issues to be aware of. GCC 3.4.x 13554bd5271SAlexander Kabaev has broken C++ ABI compatibility with previous releases yet again 13654bd5271SAlexander Kabaev and users will have to rebuild all their C++ programs with the new 137d0e54ab4SDavid E. O'Brien compiler. If you are getting run-time error such as 138d0e54ab4SDavid E. O'Brien /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE" 139d0e54ab4SDavid E. O'Brien This entry does apply to you. 140d0e54ab4SDavid E. O'Brien 141d0e54ab4SDavid E. O'Brien A new unit-at-a-time optimization mode, which is default in this 142d0e54ab4SDavid E. O'Brien compiler release, is more aggressive in removing unused static 143d0e54ab4SDavid E. O'Brien symbols. This is the likely cause of 'make buildworld' breakages 144cd5f061cSWarner Losh with non-default CFLAGS where optimization level is set to -O2 145cd5f061cSWarner Losh or higher. 14654bd5271SAlexander Kabaev 1476e1afae3SWarner Losh With the upgrade of the system compiler, the kernel has been upgraded 1486e1afae3SWarner Losh to match the new system compiler. This makes it impossible to build 1496e1afae3SWarner Losh a new kernel with the old compiler. Upgrade your system via 1506e1afae3SWarner Losh make buildworld and make kernel (see below) to fix this problem. 1516e1afae3SWarner Losh 15236ed21e6SRobert Watson20040727: 15336ed21e6SRobert Watson The size of 'struct ifnet' has changed due to the addition of 15436ed21e6SRobert Watson the IFF_NEEDSGIANT flag (and what it implies). All kernel 15536ed21e6SRobert Watson modules implementing network interfaces must be recompiled as 15636ed21e6SRobert Watson a result. 15736ed21e6SRobert Watson 1586305ac24SSeigo Tanimura20040716: 1596305ac24SSeigo Tanimura The sound device drivers are renamed. `sound' is always required, 1606305ac24SSeigo Tanimura while `snd_*' should be configured accordingly to your hardware. 1616305ac24SSeigo Tanimura Refer to NOTES for the detail of the drivers. 1626305ac24SSeigo Tanimura 163e623dcb7SMarcel Moolenaar20040710: 164e623dcb7SMarcel Moolenaar __FreeBSD_version bumped to 502122. 165e623dcb7SMarcel Moolenaar 166e623dcb7SMarcel Moolenaar20040710: 167e623dcb7SMarcel Moolenaar The console initialization on Alpha has been reworked and is now 168e623dcb7SMarcel Moolenaar identical to other platforms. This means that the hardcoding of 169e623dcb7SMarcel Moolenaar the serial console and the debug port has been removed. As such, 170e623dcb7SMarcel Moolenaar hints are now required for the sio(4) driver to become a console 171e623dcb7SMarcel Moolenaar or debug port. The NO_SIO option has been decommissioned because 172e623dcb7SMarcel Moolenaar of this. 173e623dcb7SMarcel Moolenaar 174e623dcb7SMarcel Moolenaar20040710: 175e623dcb7SMarcel Moolenaar A revamp of the debugging code in the kernel with some visible 176e623dcb7SMarcel Moolenaar changes beyond just the debugging experience: 177e623dcb7SMarcel Moolenaar o The DDB option is now specific to the DDB debugger backend 178e623dcb7SMarcel Moolenaar and should not be used any more for conditional compilation 179e623dcb7SMarcel Moolenaar of debugging code for when debugging is enabled. Use the KDB 180e623dcb7SMarcel Moolenaar option for this. 181e623dcb7SMarcel Moolenaar o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have 182e623dcb7SMarcel Moolenaar been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED 183e623dcb7SMarcel Moolenaar respectively. This is in line with the first bullet. 184e623dcb7SMarcel Moolenaar o The remote GDB support has been untangled from DDB and needs 1855bd7ce0aSJens Schweikhardt to be enabled separately now. Use the GDB option for this. 186e623dcb7SMarcel Moolenaar o The GDB_REMOTE_CHAT option has been removed. Support for this 187e623dcb7SMarcel Moolenaar homegrown feature is discontinued. The GDB remote protocol 188e623dcb7SMarcel Moolenaar supports console output and it makes sense to use that. 189e623dcb7SMarcel Moolenaar o The DDB_NOKLDSYM option has been removed. The DDB debugger 190e623dcb7SMarcel Moolenaar now supports both direct symbol table lookups as well as KLD 191e623dcb7SMarcel Moolenaar symbol lookups through the linker. 192e623dcb7SMarcel Moolenaar 1936421d1dbSMaksim Yevmenkin20040708: 1946421d1dbSMaksim Yevmenkin Bluetooth code has been marked as non-i386 specific. 1956421d1dbSMaksim Yevmenkin __FreeBSD_version has been bumped to 502121 to mark this change. 1966421d1dbSMaksim Yevmenkin 19758af3216SWarner Losh20040702: 19858af3216SWarner Losh The native preemption has been added to the kernel scheduler. 1995bd7ce0aSJens Schweikhardt There is some report that the ULE scheduler was broken in some 2005bd7ce0aSJens Schweikhardt machines and we encourage users using the ULE scheduler either 2015bd7ce0aSJens Schweikhardt stick with a known good kernel, or temporarily switch to the 4BSD 20258af3216SWarner Losh scheduler as a workaround. 20358af3216SWarner Losh 204c2dba668SNate Lawson20040630: 2058ed370fdSJulian Elischer The netgraph ABI version number has been incremented to indicate 2068ed370fdSJulian Elischer an incompatible change in the ABI. Old netgraph nodes will refuse 207a6c26e1cSBruce M Simpson to attach until recompiled. Netgraph now uses mbuf tags to move 208a6c26e1cSBruce M Simpson metadata and this commit removes its home-grown metadata facility. 209a6c26e1cSBruce M Simpson Nodes should just recompile, unless they use metadata, in which 210a6c26e1cSBruce M Simpson case the changes are simple; the file ng_ksocket.c serves as an 211a6c26e1cSBruce M Simpson example of such changes. 2128ed370fdSJulian Elischer 21358af3216SWarner Losh This also broke i4b, although the compile problem has been papered 21458af3216SWarner Losh over. 21558af3216SWarner Losh 2168ed370fdSJulian Elischer20040630: 217c2dba668SNate Lawson ACPI has been updated to disable known-bad BIOS revisions. A message 2185bd7ce0aSJens Schweikhardt will be printed on the console indicating that ACPI has been disabled 219c2dba668SNate Lawson automatically and that the user should use a newer BIOS, if possible. 220c2dba668SNate Lawson If you think ACPI does work on your system and want to override 221c2dba668SNate Lawson this (i.e., for testing), set hint.acpi.0.disabled="0" at the 222c2dba668SNate Lawson loader prompt. 223c2dba668SNate Lawson 2248ee2ac9eSMax Laier20040623: 2255bd7ce0aSJens Schweikhardt pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege 2268ee2ac9eSMax Laier separated now. It uses the newly created "_pflogd" user/group 2278ee2ac9eSMax Laier combination. If you plan to use pflogd(8) make sure to run 2288ee2ac9eSMax Laier mergemaster -p or install the "_pflogd" user and group manually. 2298ee2ac9eSMax Laier 2303db5687dSBrooks Davis20040622: 2313db5687dSBrooks Davis Network interface cloning has been overhauled. This change will 2323db5687dSBrooks Davis require a recompile of modules using cloning and modification of 2333db5687dSBrooks Davis external ones to the new API. __FreeBSD_version has been bumped 2343db5687dSBrooks Davis to 502119 to mark this change. Additionally, users creating 2353db5687dSBrooks Davis stf(4) interfaces via "ifconfig stf" will need to update their 2363db5687dSBrooks Davis scripts as this will create an interface named "stf" instead of 2373db5687dSBrooks Davis "stf0" and ifconfig will not print "stf0" to stdout. 2383db5687dSBrooks Davis 239e0ae81f3SDag-Erling Smørgrav20040621: 240e0ae81f3SDag-Erling Smørgrav On 20040524, the /etc/rc.d/nsswitch script was modified to 241e0ae81f3SDag-Erling Smørgrav automatically create /etc/nsswitch.conf on startup if it did 242e0ae81f3SDag-Erling Smørgrav not already exist. Unfortunately, an error in the man page 243e0ae81f3SDag-Erling Smørgrav was carried over to the script, resulting in incorrect 244e0ae81f3SDag-Erling Smørgrav nsswitch settings. The simplest remedy is to remove both 245e0ae81f3SDag-Erling Smørgrav /etc/nsswitch.conf and /etc/host.conf; they will be recreated 246e0ae81f3SDag-Erling Smørgrav during the next reboot. 247e0ae81f3SDag-Erling Smørgrav 2484717d22aSJohn Polstra20040614: 2494717d22aSJohn Polstra The return value of sema_timedwait(9) has been changed to 2504717d22aSJohn Polstra make it consistent with cv_timedwait(9). Be sure to recompile 2514717d22aSJohn Polstra the ips module and any third-party modules which call 2524717d22aSJohn Polstra sema_timedwait. 2534717d22aSJohn Polstra 2546cb7a382SMax Laier20040613: 2556cb7a382SMax Laier ALTQ is now linked to the build. This breaks ABI for struct ifnet. 2566cb7a382SMax Laier Make sure to recompile modules and any userland that makes use of 257df843493SMax Laier sizeof(struct ifnet). In order to get the altq headers in place 258df843493SMax Laier please recompile and reinstall world. 2596cb7a382SMax Laier 2602454685eSJulian Elischer20040607: 2612454685eSJulian Elischer Splitting kern_thread.c into 2 files (adding kern_kse.c) 2622454685eSJulian Elischer requires that you re-run config after updating your tree. 2632454685eSJulian Elischer 26464fef830SSeigo Tanimura20040601: 26564fef830SSeigo Tanimura The MIDI drivers have been removed. Until the new module-friendly 26664fef830SSeigo Tanimura ones are merged, remove or comment out midi and seq from your 26764fef830SSeigo Tanimura kernel configuration. 26864fef830SSeigo Tanimura 269bb4f06e7SAndre Oppermann20040423: 270bb4f06e7SAndre Oppermann Due to a new option in ipfw (versrcreach) the ipfw(8) command 271bb4f06e7SAndre Oppermann needs to be recompiled. Normal accept/reject rules without 272bb4f06e7SAndre Oppermann options are not affected but those with options may break until 273bb4f06e7SAndre Oppermann ipfw(8) is recompiled. 274bb4f06e7SAndre Oppermann 27505641e82SColin Percival20040420: 27605641e82SColin Percival Due to changes in the callout ABI, kernels compiled after this 27705641e82SColin Percival date may be incompatible with kernel modules compiled prior to 27805641e82SColin Percival 20040406. 27905641e82SColin Percival 280d0dc9183SWarner Losh20040414: 281d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 282d0dc9183SWarner Losh problems for your system, please disable it using the tunable 283d0dc9183SWarner Losh hw.pci.do_powerstate=0. 284d0dc9183SWarner Losh 285d0dc9183SWarner Losh20040412: 286d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 287d0dc9183SWarner Losh drive is still broken. 288d0dc9183SWarner Losh 289d0dc9183SWarner Losh20040410: 290d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 291d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 292d0dc9183SWarner Losh the unanticipated problems have been resolved. 293d0dc9183SWarner Losh 2948633bbeaSBrooks Davis20040409: 2958633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 2968633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 2978633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 2988633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 29976c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 3008633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 3018633bbeaSBrooks Davis 302d40d033aSRobert Watson20040322: 303d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 304d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 305d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 306d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 307d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 308d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 309d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 310d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 311d40d033aSRobert Watson locking is merged to permit this to take place. 312d40d033aSRobert Watson 313ec9b318eSGarance A Drosehn20040310: 314ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 315ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 316ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 317ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 318ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 319ec9b318eSGarance A Drosehn 320fc28f1ffSMax Laier20040308: 321fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 322fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 3234c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 3244c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 325fc28f1ffSMax Laier Also note that pf requires "options PFIL_HOOKS" in the kernel. The 326fc28f1ffSMax Laier pf system consists of the following three devices: 327fc28f1ffSMax Laier device pf # required 328fc28f1ffSMax Laier device pflog # optional 329fc28f1ffSMax Laier device pfsync # optional 330fc28f1ffSMax Laier 3313aff5d06SDag-Erling Smørgrav20040303: 3323aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 3333aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 3343aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 3353aff5d06SDag-Erling Smørgrav 3363aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 3373aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 3383aff5d06SDag-Erling Smørgrav 3393aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 3403aff5d06SDag-Erling Smørgrav to use libpthread instead. 3413aff5d06SDag-Erling Smørgrav 342fd63c5b3SDag-Erling Smørgrav20040226: 3439d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 344fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 345fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 346fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 347fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 348fd63c5b3SDag-Erling Smørgrav 349714ae42aSBruce M Simpson20040225: 350e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 351e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 352e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 353e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 354e07a40f3SBrian Feldman should remain unaffected. 355e07a40f3SBrian Feldman 356e07a40f3SBrian Feldman20040225: 357714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 358714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 359714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 360714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 361714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 362714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 363714ae42aSBruce M Simpson 364fbd2e692SAndre Oppermann20040224: 365fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 3665bd7ce0aSJens Schweikhardt and related userland network utilities necessary. 367fbd2e692SAndre Oppermann 368158b90daSWarner Losh20040222: 369158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 370158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 371158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 372158b90daSWarner Losh Drivers outside the tree will need to be updated. 373158b90daSWarner Losh 374b7b1e150SMike Makonnen20040207: 375b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 376b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 377b7b1e150SMike Makonnen 378aca89ee6SDaniel Eischen20040130: 379aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 380aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 381aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 382aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 383aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 384aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 385aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 386aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 387aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 388aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 389aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 390aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 391aca89ee6SDaniel Eischen do not work with libpthread. 392aca89ee6SDaniel Eischen 39368b7b3a9SAlex Dupre20040125: 39468b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 39568b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 39668b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 39768b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 39868b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 39968b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 40068b7b3a9SAlex Dupre 401ff46e0deSWarner Losh20040125: 402ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 403ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 404ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 405ff46e0deSWarner Losh 406ce41f4bfSRobert Watson20031213: 407ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 408ce41f4bfSRobert Watson if the login process is unable to successfully set the 409ce41f4bfSRobert Watson process credentials to include all groups defined for the 410ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 411ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 412ce41f4bfSRobert Watson defined, or they will be unable to log in. 413ce41f4bfSRobert Watson 414c124fa05SJohn Baldwin20031203: 415c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 416c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 417c124fa05SJohn Baldwin 4188ad1f5e4SHartmut Brandt20031112: 41930093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 42030093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 42197209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 42297209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 42397209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 42497209ca3SRobert Watson not know about the new system calls that support the new statfs 4253f631d52SMarcel Moolenaar structure. 4263f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 4273f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 4283f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 4293f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 4303f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 4313f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 4323f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 4333f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 4343f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 4353f631d52SMarcel Moolenaar these changes are installed. 43630093b05SWarner Losh 43730093b05SWarner Losh ****************************DANGER******************************* 43830093b05SWarner Losh 43930093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 44030093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 44130093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 44230093b05SWarner Losh kernel. 44364a18d6fSKirk McKusick 44464a18d6fSKirk McKusick20031112: 4458ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 4468ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 4478ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 4488ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 4498ad1f5e4SHartmut Brandt sync before rebooting. 4508ad1f5e4SHartmut Brandt 451c53a5d8fSJohn Baldwin20031111: 452c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 453c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 454c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 455c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 456c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 457c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 458c53a5d8fSJohn Baldwin 4598bf455a5SJohn Baldwin20031103: 4608bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 4618bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 4622a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 4638bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 4648bf455a5SJohn Baldwin 4659bf40edeSBrooks Davis20031031: 4669bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 4679bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 4689bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 4699bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 4709bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 4719bf40edeSBrooks Davis reflect this change. 4729bf40edeSBrooks Davis 47347a42c7aSPoul-Henning Kamp20030928: 47447a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 47547a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 4765bd7ce0aSJens Schweikhardt __FreeBSD_version bumped to 501110. 47747a42c7aSPoul-Henning Kamp 47807105342SMax Khon20030926: 47907105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 48007105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 48107105342SMax Khon 48217dcd026SSam Leffler20030925: 48317dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 48417dcd026SSam Leffler also be explicitly configured. Previously this dependency was 48517dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 48617dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 48717dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 48817dcd026SSam Leffler 489fedf1d01SBruce M Simpson20030923: 490fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 491fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 492fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 493fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 494fedf1d01SBruce M Simpson 495db38f9cbSJacques Vidrine20030915: 496db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 497db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 498db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 499db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 500db38f9cbSJacques Vidrine 501c09d2c2bSMike Makonnen20030829: 502c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 503c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 504c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 505c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 506c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 507c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 508c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 509c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 510c09d2c2bSMike Makonnen may or may not exist on your system. 511c09d2c2bSMike Makonnen 51217c159dcSSøren Schmidt20030824: 51317c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 51417c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 515f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 516f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 51717c159dcSSøren Schmidt 518c1f61aa9SDavid E. O'Brien20030819: 519c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 520c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 521c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 522c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 52369f7bcf3SWarner Losh 52438c962e7SNate Lawson20030728: 52538c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 52638c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 52738c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 52838c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 52938c962e7SNate Lawson so the quirk can be re-enabled. 53038c962e7SNate Lawson 53174111097SWarner Losh20030724: 53274111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 53374111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 53474111097SWarner Losh 535178cf4e9SWarner Losh20030722: 536178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 537178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 538178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 539178cf4e9SWarner Losh FPU hardware. 540178cf4e9SWarner Losh 541178cf4e9SWarner Losh20030714: 542178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 543178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 544178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 545178cf4e9SWarner Losh People should report those issues to current@. 546178cf4e9SWarner Losh 547157c629aSWarner Losh20030711: 548157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 5498b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 55005538fa9SWarner Losh /usr/obj. 551157c629aSWarner Losh 55274111097SWarner Losh20030610: 55374111097SWarner Losh Remove deprecated locale names and transition period code 55474111097SWarner Losh for them, finishing switching to the new scheme. Check your 55574111097SWarner Losh LANG environment variable. 55674111097SWarner Losh 55774111097SWarner Losh20030609: 55874111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 55974111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 56074111097SWarner Losh important to remember beforehand if your source tree is on 56174111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 56274111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 56374111097SWarner Losh kernel. 56474111097SWarner Losh 56574111097SWarner Losh20030605: 5666cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 5676cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 5686cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 5696cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 5706cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 5716cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 5726cc6353fSMarcel Moolenaar 5736cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 5746cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 5756cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 5766cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 5776cc6353fSMarcel Moolenaar : 5786cc6353fSMarcel Moolenaar 5796cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 5806cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 5816cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 5826cc6353fSMarcel Moolenaar 58352b47445SMark Murray20030505: 58452b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 58552b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 58652b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 58752b47445SMark Murray 588a26df538SWarner Losh20030502: 589a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 590a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 591a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 592a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 593a26df538SWarner Losh 5944b065e2cSDoug Barton20030501: 5954b065e2cSDoug Barton The old rc system has been removed. Please report any problems 5964b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 5974b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 5984b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 5994b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 6004b065e2cSDoug Barton utilizes these old scripts has also been removed. 6014b065e2cSDoug Barton 60281cda3d9SWarner Losh20030423: 60381cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 60481cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 60581cda3d9SWarner Losh work around in devd will be removed around 20030507. You 60681cda3d9SWarner Losh have until then to upgrade your kernel before updating 60781cda3d9SWarner Losh userland. In general, you should have a userland and 60881cda3d9SWarner Losh kernel that's in sync with each other. However, given the 60981cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 61081cda3d9SWarner Losh allowances are made. 61181cda3d9SWarner Losh 61247a657d1SRuslan Ermilov20030329: 61347a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 61447a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 61547a657d1SRuslan Ermilov while upgrading the system through a buildworld. 61647a657d1SRuslan Ermilov 61747a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 61847a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 61947a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 62047a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 62147a657d1SRuslan Ermilov 62247a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 62347a657d1SRuslan Ermilov make cleandir && make obj && \ 62447a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 62547a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 62647a657d1SRuslan Ermilov 6275d2af00cSGregory Neil Shapiro20030208: 6285d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 6295d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 6305d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 6315d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 6325d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 6335d2af00cSGregory Neil Shapiro 6345d2af00cSGregory Neil Shapiro20030128: 6359db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 636ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 6379db58771SPoul-Henning Kamp be removed when convenient. 6389db58771SPoul-Henning Kamp 6398d9b3f57SJake Burkholder20030126: 6408d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 6418d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 6428d9b3f57SJake Burkholder 6431c5efda5SJeff Roberson20030125: 6441c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 6451c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 646ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 6471c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 6481c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 6491c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 6501c5efda5SJeff Roberson 6519d1d64f5SWarner Losh20030115: 6529d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 6539d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 6549d1d64f5SWarner Losh properly. 6559d1d64f5SWarner Losh 656c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 657c9fdb80aSWarner Losh configured for point to point links to bring it more in line 658c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 659c9fdb80aSWarner Losh with NetBSD. 660c9fdb80aSWarner Losh 661161dc364SAlexander Kabaev20021222: 662161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 663161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 664161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 665161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 666161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 667161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 66884cc83efSAlexander Kabaev rebuilt. 669161dc364SAlexander Kabaev 670fb4c8061SMartin Blapp20021216: 671fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 67289056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 673fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 6749d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 675fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 676fb4c8061SMartin Blapp 67717d47eb3SGiorgos Keramidas20021202: 67817d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 67917d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 68017d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 68117d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 68217d47eb3SGiorgos Keramidas 683a4459294SBill Fenner20021029: 684a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 685a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 686a4459294SBill Fenner consumers in sync. 687a4459294SBill Fenner 688fc8c157fSWarner Losh20021024: 689c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 690c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 691c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 692c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 693c57404feSRuslan Ermilov partition really is on. The old device names have gone 694c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 695c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 696c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 69769f7bcf3SWarner Losh 698fd9e8bdaSAndrew Gallatin20021023: 699fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 700fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 701fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 702fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 703fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 704fd9e8bdaSAndrew Gallatin 705fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 706fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 707fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 708fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 709fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 710fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 711fd9e8bdaSAndrew Gallatin 712f8a4c901SWarner Losh20020831: 713f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 714f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 715f8a4c901SWarner Losh programs and libraries need to be recompiled. 716f8a4c901SWarner Losh 717f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 718f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 719f8a4c901SWarner Losh 720c2248fa2SJens Schweikhardt20020827: 721c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 722c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 723c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 724c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 725c2248fa2SJens Schweikhardt 7260d533e43SRuslan Ermilov20020815: 7270d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 7280d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 7290d533e43SRuslan Ermilov again. 7300d533e43SRuslan Ermilov 73133c1de7dSRuslan Ermilov20020729: 73233c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 73333c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 73433c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 73533c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 73633c1de7dSRuslan Ermilov 7372b877facSJulian Elischer20020702: 7382b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 7392b877facSJulian Elischer There are still some minor problems with some signals but the 7402b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 7412b877facSJulian Elischer but each can successfully complete multiple buildworlds. 7422b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 7432b877facSJulian Elischer 74406596d37SWarner Losh20020701: 74506596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 74606596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 74706596d37SWarner Losh GNOME. 74806596d37SWarner Losh 74995ba4330SJacques Vidrine20020511: 75095ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 75195ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 75295ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 75395ba4330SJacques Vidrine with the set-user-ID bit set. 75495ba4330SJacques Vidrine 755a81da3c9SDavid E. O'Brien20020510: 756f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 757f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 7584b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 759f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 760f50caf6fSDavid E. O'Brien 761f50caf6fSDavid E. O'Brien20020510: 762a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 763a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 764a81da3c9SDavid E. O'Brien and then do a cvs update. 765a81da3c9SDavid E. O'Brien 766528a0ef5SJacques Vidrine20020421: 767528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 768528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 769528a0ef5SJacques Vidrine 77085aa5a2eSGregory Neil Shapiro20020404: 77185aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 77285aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 77385aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 77485aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 77585aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 77685aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 77785aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 77885aa5a2eSGregory Neil Shapiro 7798f1e4358SRuslan Ermilov20020403: 7808f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 7818f1e4358SRuslan Ermilov 7822292c02eSWarner Losh20020315: 7832292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 7842292c02eSWarner Losh 78569f7bcf3SWarner Losh20020225: 78669f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 78769f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 78869f7bcf3SWarner Losh 7898f35c493SWarner Losh20020217: 7908f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 7918f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 7928f35c493SWarner Losh command line mail submission has changed. Be sure to run 7938f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 7948f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 7958f35c493SWarner Losh 796835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 797835284beSWarner Losh required in order for sendmail to run as a set-group-ID 798835284beSWarner Losh binary. A 'make installworld' will use the new user and group 799835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 800835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 801835284beSWarner Losh and group must be merged from src/etc/group and 802835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 803835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 804835284beSWarner Losh mergemaster before this will work if you are updating from a 805835284beSWarner Losh very old version of current. The updating recipe has changed 806835284beSWarner Losh as of this date. 807835284beSWarner Losh 808fa9401c1SWarner Losh20020112: 809fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 810fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 811fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 812fa9401c1SWarner Losh you have local modifications, you can use 813fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 814fa9401c1SWarner Losh /etc/pam.d. 815fa9401c1SWarner Losh 816fa9401c1SWarner Losh Please see the following url for more details: 817fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 81847d0d01fSWarner Losh20011229: 81947d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 82047d0d01fSWarner Losh networkfs_types, please note that it has changed 82147d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 82247d0d01fSWarner Losh 823514318a8SWarner Losh20011220: 824514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 825514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 826514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 827514318a8SWarner Losh own. All the accumulated features and bug fixes of the i4b 828514318a8SWarner Losh version have now been merged back into the base system's 829514318a8SWarner Losh version now. The only user-visible change resulting from this 830514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 831514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 832514318a8SWarner Losh as well. (There has never been rc file support for 833514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 834514318a8SWarner Losh reverted by the time the changes are MFCed.) 835514318a8SWarner Losh 836514318a8SWarner Losh20011215: 837514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 838514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 839514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 840514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 841514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 842514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 843514318a8SWarner Losh will need to be customized then for `odd' densities using 844514318a8SWarner Losh fdcontrol(8). 845514318a8SWarner Losh 8462d22e2bfSWarner Losh20011209: 8472d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 8482d22e2bfSWarner Losh and truss(1) now works again. 8492d22e2bfSWarner Losh 8509e0428e2SWarner Losh20011207: 8519e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 8529e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 8539e0428e2SWarner Losh see 8549e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 8559e0428e2SWarner Losh for details. 8569e0428e2SWarner Losh 8579bab8c59SWarner Losh20011204: 8589bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 8599bab8c59SWarner Losh kernel and burncd to be in sync. 8609bab8c59SWarner Losh 861e57d8b01SWarner Losh20011203: 862e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 863e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 864e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 865e57d8b01SWarner Losh not there already. 866e57d8b01SWarner Losh 867e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 868e57d8b01SWarner Losh until the issue has been resolved. 869e57d8b01SWarner Losh 870b001d36fSJacques Vidrine20011202: 871b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 872b001d36fSJacques Vidrine patched. 873b001d36fSJacques Vidrine 8744b676ec1SWarner Losh20011126: 8754b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 8765ebbf43eSWarner Losh after this date. You need to do this only once. 8774b676ec1SWarner Losh 878d961e462SWarner Losh20011103: 879d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 880d961e462SWarner Losh edges may be left, but for the most part things should be 8814b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 882d961e462SWarner Losh 883d961e462SWarner Losh20011030: 884d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 885d961e462SWarner Losh choppy waves in the upgrade process. 886d961e462SWarner Losh 8871fe003b6SWarner Losh20011030: 888a4b6fda0SWarner Losh The asr driver problem has been resolved. 8891fe003b6SWarner Losh 8901fe003b6SWarner Losh20011027: 8911fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 8921fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 8931fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 8941fe003b6SWarner Losh try to use from this date forward. 8951fe003b6SWarner Losh 8961fe003b6SWarner Losh20011025: 8971fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 8981fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 8991fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 9001fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 9011fe003b6SWarner Losh TARGET_ARCH=i386. 9021fe003b6SWarner Losh 903d05f9643SWarner Losh20011001: 904d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 905d05f9643SWarner Losh You must recompile both the kernel and userland applications 906d05f9643SWarner Losh at the same time. 907d05f9643SWarner Losh 90858970f85SWarner Losh20010929: 90958970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 91058970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 91158970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 91258970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 9139d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 91458970f85SWarner Losh 91558970f85SWarner Losh20010927: 91658970f85SWarner Losh Some weird problems result from using ACPI on some machines. 91758970f85SWarner Losh To disable ACPI you can add 91866ff0e67SMax Khon hint.acpi.0.disabled="1" 91958970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 92058970f85SWarner Losh loader "ok" prompt). 92158970f85SWarner Losh 92258970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 92358970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 92458970f85SWarner Losh file and not list acpi in that list. 925378f4486SAlfred Perlstein 9265119d237SWarner Losh20010924: 9275119d237SWarner Losh The buildworld has been fixed. You may need to install 9285119d237SWarner Losh the 4.x compatibility libraries for some old binaries 9298b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 9308b039fffSWarner Losh get them installed on every installworld, or execute the 9318b039fffSWarner Losh following to get them installed only once: 9328b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 93358970f85SWarner Losh make all install 9348b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 9355119d237SWarner Losh 9363c293725SWarner Losh20010919: 9373c293725SWarner Losh There's a bug in the world build process. The cross-tools 9383c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 9393c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 940772730c7SWarner Losh workaround is to add 9413c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 9423c293725SWarner Losh before building world when upgrading from 4.x to current. This 9433c293725SWarner Losh can be removed afterwards. 9443c293725SWarner Losh 9453c293725SWarner Losh A proper fix to the buildworld target is needed. 9463c293725SWarner Losh 9473c293725SWarner Losh20010918: 9483c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 9493c293725SWarner Losh NFS may be unstable after this date. 9503c293725SWarner Losh 9513c293725SWarner Losh20010912: 9523c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 9533c293725SWarner Losh the kernel. While a few problems were introduced in the 9543c293725SWarner Losh initial commit, most of the major ones have been found and 9553c293725SWarner Losh corrected. 9563c293725SWarner Losh 9573c293725SWarner Losh20010901: 9583c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 9593c293725SWarner Losh arounds described in the 20010604 entry are now no longer 9603c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 9613c293725SWarner Losh have been rectified around this date. 9623c293725SWarner Losh 96398b17b95SWarner Losh20010823: 96498b17b95SWarner Losh named now runs as user bind and group bind rather than as 96598b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 96698b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 96798b17b95SWarner Losh and that group bind is available in /etc/group. Also make 96898b17b95SWarner Losh sure that user or group bind has read (and not write) 96998b17b95SWarner Losh permission for your name server configuration and that it 97098b17b95SWarner Losh has read and write permission for your slave zone files and 97198b17b95SWarner Losh directory. 97298b17b95SWarner Losh 97398b17b95SWarner Losh If you wish to continue to run named as root (a less secure 97498b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 97598b17b95SWarner Losh 97698b17b95SWarner Losh named_flags= 97798b17b95SWarner Losh 9787b9786edSMark Murray20010709: 9797b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 9807b9786edSMark Murray the ability of the shared library major number to handle. 9817b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 9827b9786edSMark Murray solution is to rebuild those ports. 9837b9786edSMark Murray 9841d28950eSWarner Losh20010628: 9851d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 9861d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 9871d28950eSWarner Losh 988e72fd46aSWarner Losh20010625: 98998b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 99098b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 99198b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 99298b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 99398b17b95SWarner Losh IRQ configuration needs more safety belts. 99416de1a07SWarner Losh 9950d415dffSWarner Losh20010617: 996e72fd46aSWarner Losh Softupdates problems have been corrected. 9970d415dffSWarner Losh 9980d415dffSWarner Losh20010614: 9990d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 10000d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 10010d415dffSWarner Losh kernel building methods. 10020d415dffSWarner Losh 10038b9959adSWarner Losh20010613: 10048b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 10058b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 1006e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 1007e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 10088b9959adSWarner Losh 1009e72fd46aSWarner Losh20010613: 10108b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 1011e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 1012e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 10138b9959adSWarner Losh 10140d415dffSWarner Losh20010612: 10150d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 10160d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 10170d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 10180d415dffSWarner Losh work around this issue, please use only one or the other mechanism 10190d415dffSWarner Losh until this bug is fixed. 10200d415dffSWarner Losh 1021e72fd46aSWarner Losh Please note that a feature of config is that if you have config 1022e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 1023ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 1024e72fd46aSWarner Losh 10250d415dffSWarner Losh20010610: 10260d415dffSWarner Losh Locale names have changed to match other systems better. 10270d415dffSWarner Losh 10286ccdb5e4SWarner Losh20010604: 10296ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 10306ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 10316ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 10323590182eSWarner Losh Interrupt storms look a lot like a hang. 10333590182eSWarner Losh 10343590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 10353590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 10363590182eSWarner Losh it is). 10373590182eSWarner Losh 10383590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 10393590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 10403590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 10413590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 10426ccdb5e4SWarner Losh 10430bc62786SWarner Losh20010530: 10440bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 10450bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 10460bc62786SWarner Losh a limited time. If you see 10470bc62786SWarner Losh 10480bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 10490bc62786SWarner Losh 10500bc62786SWarner Losh in your makeworld, then you need to migrate towards using 10510bc62786SWarner Losh COPY=-C. 10520bc62786SWarner Losh 105368a38c6cSWarner Losh20010525: 1054b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 1055c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 1056c4f4a728SWarner Losh definitely is in bad shape. 105768a38c6cSWarner Losh 1058ed0f29caSWarner Losh20010521: 1059ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 1060ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 1061ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 1062ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 1063ed0f29caSWarner Losh is 1064ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 1065ed0f29caSWarner Losh 106680c16af9SWarner Losh20010520: 106768a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 106880c16af9SWarner Losh 106980c16af9SWarner Losh20010519: 107080c16af9SWarner Losh pccard has had much reorganizational work done to it over 107180c16af9SWarner Losh the past few days. Everything should still work, but if 107280c16af9SWarner Losh not, please contact imp@freebsd.org. 107380c16af9SWarner Losh 1074a45f2d05SWarner Losh20010517: 1075a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 1076a45f2d05SWarner Losh userland at the same time. 1077a45f2d05SWarner Losh 1078a45f2d05SWarner Losh20010517: 1079a45f2d05SWarner Losh New ncurses imported. 1080a45f2d05SWarner Losh 10812988afcaSWarner Losh20010512: 10822988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 10832988afcaSWarner Losh will be the only way to go starting July 1. 10842988afcaSWarner Losh 10851a33dba7SWarner Losh20010504: 10861a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 10871a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 10881a33dba7SWarner Losh 108909946a51SWarner Losh20010502: 109009946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 109109946a51SWarner Losh 109209946a51SWarner Losh20010501: 109309946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 109409946a51SWarner Losh 109509946a51SWarner Losh20010430: 1096a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 109709946a51SWarner Losh go back in the water. 109809946a51SWarner Losh 109909946a51SWarner Losh20010429: 110009946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 110109946a51SWarner Losh this date, but before the correction date. 110209946a51SWarner Losh 110391dd3b53SWarner Losh20010423: 110491dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 110591dd3b53SWarner Losh 110691dd3b53SWarner Losh20010411: 110791dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 110891dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 110991dd3b53SWarner Losh Update only if you understand that you must not use the old 111091dd3b53SWarner Losh fsck with the new kernel ever. 111191dd3b53SWarner Losh 1112933b3269SWarner Losh20010330: 1113933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 1114c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 1115933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 1116933b3269SWarner Losh 1117933b3269SWarner Losh20010319: 1118933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 1119933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 1120933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 1121f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 112209946a51SWarner Losh 112309946a51SWarner Losh20010315: 112409946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 1125ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 112609946a51SWarner Losh been replaced by tunables. See ata.4 for details. 1127933b3269SWarner Losh 1128933b3269SWarner Losh20010312: 1129933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 1130933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 1131933b3269SWarner Losh 1132933b3269SWarner Losh20010312: 1133933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 1134933b3269SWarner Losh instead of ad-hoc. 1135933b3269SWarner Losh 1136933b3269SWarner Losh20010310: 1137f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 1138933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 1139933b3269SWarner Losh ssh might not work if you don't. 1140933b3269SWarner Losh 114162353691SWarner Losh20010303: 114262353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 114362353691SWarner Losh which means that you must include the miibus in your kernel if 114462353691SWarner Losh you use the ed driver. 114562353691SWarner Losh 1146d325cf65SWarner Losh20010220: 1147d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 1148d325cf65SWarner Losh safe to go back into the water. 1149d325cf65SWarner Losh 1150024daae6SWarner Losh20010211: 1151024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 1152024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 1153024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 1154024daae6SWarner Losh that before upgrading would be a good time to do a level 0 1155024daae6SWarner Losh dump of your system. No, really, I mean it this time. 1156024daae6SWarner Losh 1157024daae6SWarner Losh To get to the new system, you'll need to use the following 1158024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 1159024daae6SWarner Losh don't have to move this to the updating section. 1160024daae6SWarner Losh 1161024daae6SWarner Losh To get around the installworld problem, do: 1162024daae6SWarner Losh # cd /usr/src/usr.bin/sed 1163024daae6SWarner Losh # make install 1164024daae6SWarner Losh # cd /usr/src 1165024daae6SWarner Losh # make installworld 1166024daae6SWarner Losh If that doesn't work, then try: 1167024daae6SWarner Losh # make -k installworld 1168024daae6SWarner Losh # make installworld 1169024daae6SWarner Losh 1170024daae6SWarner Losh20010207: 1171024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 1172024daae6SWarner Losh do not include devfs in your kernel as problems result. 1173024daae6SWarner Losh 1174024daae6SWarner Losh20010205: 11757595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 1176024daae6SWarner Losh Remove them from your config. 1177024daae6SWarner Losh 11781e159248SWarner Losh20010122: 11791e159248SWarner Losh ****************************** WARNING ****************************** 11801e159248SWarner Losh buildkernel has been changed slightly 11811e159248SWarner Losh ****************************** WARNING ****************************** 11821e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 11831e159248SWarner Losh should update your scripts and make.conf accordingly. 11841e159248SWarner Losh 11851e159248SWarner Losh20010119: 11861e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 11871e159248SWarner Losh This requires a new config to build correctly. 11881e159248SWarner Losh 1189aac7dfeaSWarner Losh20010116: 1190ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 1191aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 1192aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 1193aac7dfeaSWarner Losh 1194aac7dfeaSWarner Losh20010110: 1195aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 1196aac7dfeaSWarner Losh 1197aac7dfeaSWarner Losh20010102: 1198aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 1199aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 1200aac7dfeaSWarner Losh 120163c90c9eSWarner Losh20010101: 120263c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 120363c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 12045fd2a895SWarner Losh dump while building termcap. You can work around this problem 120563c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 120663c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 120763c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 120863c90c9eSWarner Losh might have been ignored by the -k option. 120963c90c9eSWarner Losh 12105fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 12115fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 12125fd2a895SWarner Losh of this working. 12135fd2a895SWarner Losh 1214aac7dfeaSWarner Losh20001228: 1215aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 1216ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 1217aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 1218aac7dfeaSWarner Losh 1219de2bcc63SWarner Losh20001218: 1220de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 1221de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 1222de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 1223de2bcc63SWarner Losh cards will not be recognized without it. 1224de2bcc63SWarner Losh 1225960773f7SWarner Losh20001205: 1226960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 1227960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 1228960773f7SWarner Losh adding the following in pam.conf: 1229960773f7SWarner Losh 1230960773f7SWarner Losh sshd auth sufficient pam_skey.so 1231960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 1232960773f7SWarner Losh sshd session required pam_permit.so 1233960773f7SWarner Losh 12340acc635eSWarner Losh20001031: 12350acc635eSWarner Losh cvs updated to 1.11. 12360acc635eSWarner Losh 12370acc635eSWarner Losh20001020: 12380acc635eSWarner Losh The random device needs more entropy, so you need to make sure 12390acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 12400acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 12410acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 12420acc635eSWarner Losh workaround. 12430acc635eSWarner Losh 12440acc635eSWarner Losh20001010: 12450acc635eSWarner Losh ****************************** WARNING ****************************** 12460acc635eSWarner Losh Sendmail has been updated. 12470acc635eSWarner Losh ****************************** WARNING ****************************** 12480acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 12490acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 12500acc635eSWarner Losh is set. 12510acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 12520acc635eSWarner Losh commands. 12530acc635eSWarner Losh o Now using sendmail's version of vacation(1). 12540acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 12550acc635eSWarner Losh in /usr/share/sendmail/cf. 12560acc635eSWarner Losh o sendmail.cw changed to local-host-names 12570acc635eSWarner Losh 12580acc635eSWarner Losh More details can be found at 12590acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 12600acc635eSWarner Losh 12616e98a146SWarner Losh20001009: 12626e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 12636e98a146SWarner Losh your entire ports tree, or you will have problems. 12646e98a146SWarner Losh 12656e98a146SWarner Losh20001006: 1266685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 12676e98a146SWarner Losh the installed miniperl. It is recommended that you delete 12686e98a146SWarner Losh /usr/bin/miniperl. 12696e98a146SWarner Losh 1270073113a4SWarner Losh20001005: 1271073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1272685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1273073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1274073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1275073113a4SWarner Losh tree for anything to work. 1276073113a4SWarner Losh 12770acc635eSWarner Losh20000928: 12780acc635eSWarner Losh There was a change in the passwd format. Need more information. 12790acc635eSWarner Losh 1280be3885b3SWarner Losh20000916: 1281be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1282be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1283be3885b3SWarner Losh same time as your kernel. 1284be3885b3SWarner Losh 128576ec9675SWarner Losh20000914: 128676ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 128776ec9675SWarner Losh include the device will cause suspended laptops losing time 128876ec9675SWarner Losh when they resume. Include 128976ec9675SWarner Losh device pmtimer 129076ec9675SWarner Losh in your config file and 129101b9a434SWarner Losh hint.pmtimer.0.at="isa" 129276ec9675SWarner Losh to your /boot/device.hints file. 129376ec9675SWarner Losh 1294f4865386SMark Murray20000911: 1295f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1296f4865386SMark Murray rather than an option. The supplied kernel config files have 1297f4865386SMark Murray been updated. You will need to do something similar in your 1298f4865386SMark Murray own kernel config file. 1299f4865386SMark Murray Remove: 1300f4865386SMark Murray options RANDOMDEV 1301f4865386SMark Murray Add: 1302f4865386SMark Murray device random 1303f4865386SMark Murray If you prefer to load the loadable module, you need to do 1304f4865386SMark Murray nothing. 1305f4865386SMark Murray 1306d594498fSWarner Losh20000909: 1307d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1308d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1309d594498fSWarner Losh reflect this if you load this module at boot time. 1310d594498fSWarner Losh The line should read: 1311d594498fSWarner Losh random_load="YES" 1312d594498fSWarner Losh 13130deb7ddcSWarner Losh20000907: 13140deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 131516eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 131616eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 131716eb772dSWarner Losh sure you don't have model loading problems which might at 131816eb772dSWarner Losh first blush appear related to SMP. 131952bf24e7SWarner Losh 13205a01880bSWarner Losh20000906: 13215a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 13225a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 13235a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 13245a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 13255a01880bSWarner Losh don't have one, and you have host.conf. 13265a01880bSWarner Losh 13272b41163cSWarner Losh20000905: 132838d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 132938d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 133038d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 133138d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 133238d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 133338d6ecd2SWarner Losh 133438d6ecd2SWarner Losh20000905: 13358aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 13368aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 13378aab4bc7SWarner Losh is /boot/kernel. 13388aab4bc7SWarner Losh 13398aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 134038d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 134138d6ecd2SWarner Losh installkernel/installworld dance. 13422b41163cSWarner Losh 1343d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1344d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1345d594498fSWarner Losh modules in that directory instead of finding them in the correct 1346d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1347d594498fSWarner Losh is that the linux module crashes your machine after the update. 1348d594498fSWarner Losh 1349d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1350d594498fSWarner Losh mv /modules.old /boot/kernel.old 1351d594498fSWarner Losh chflags noschg /kernel.old 1352d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1353d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1354d594498fSWarner Losh fi 1355d594498fSWarner Losh 1356c22a309cSWarner Losh20000904: 1357c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1358c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1359c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1360c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1361c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1362c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1363c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1364c22a309cSWarner Losh is not likely to be generated. 1365c22a309cSWarner Losh 1366fdb9f54dSWarner Losh20000825: 1367fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 13689c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 13699c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 13709c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 13719c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 13729c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 13739c1a7444SWarner Losh messages will appear after the boot loader tries to start the 13749c1a7444SWarner Losh kernel. 13759c1a7444SWarner Losh 13769c1a7444SWarner Losh20000821: 13779c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 13789c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 13799c1a7444SWarner Losh /boot/loader.conf. 1380fdb9f54dSWarner Losh 13818f250aa7SWarner Losh20000812: 13825da0d091SWarner Losh suidperl is now always built and installed on the system, but 13835da0d091SWarner Losh with permissions of 511. If you have applications that use 13845da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 13855da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 13865da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 13875da0d091SWarner Losh will fix this until the next build. 13885da0d091SWarner Losh 13895da0d091SWarner Losh20000812: 13908f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 13918f250aa7SWarner Losh visible changes that may immediately affect your configuration 13928f250aa7SWarner Losh include: 13938f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 13948f250aa7SWarner Losh - newaliases limited to root and trusted users 13958f250aa7SWarner Losh - MSA port (587) turned on by default 13968f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 13978f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 13988f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 13998f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 14008f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 14018f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 14028f250aa7SWarner Losh 140371c38472SWarner Losh20000810: 140471c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 140571c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 140671c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 140771c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 140871c38472SWarner Losh specific use for it. 140971c38472SWarner Losh 141071c38472SWarner Losh20000729: 141171c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 141271c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 141371c38472SWarner Losh /etc/rc.conf if they want to have the same setup 141471c38472SWarner Losh afterwards (unless the variables already are set, of course): 141571c38472SWarner Losh # Enable network daemons for user convenience. 141671c38472SWarner Losh inetd_enable="YES" 141771c38472SWarner Losh portmap_enable="YES" 141871c38472SWarner Losh sendmail_enable="YES" 141971c38472SWarner Losh 142071c38472SWarner Losh20000728: 142171c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 142271c38472SWarner Losh will need to change that to nullfs_load="YES". 142371c38472SWarner Losh 14241dece4a9SWarner Losh20000728: 14251dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 14261dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 14271dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 14281dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 14291dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 14301dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 14311dece4a9SWarner Losh to /MYKERNEL. 14321dece4a9SWarner Losh 1433409e887cSWarner Losh20000711: 1434409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1435409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1436409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1437409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1438409e887cSWarner Losh for details on potential problems that you might have and how 1439409e887cSWarner Losh to get around them. 1440409e887cSWarner Losh 1441409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1442409e887cSWarner Losh clauses above, you needn't worry. 1443409e887cSWarner Losh 1444409e887cSWarner Losh20000711: 1445409e887cSWarner Losh /etc/security has been updated to print the inode number of 1446409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1447409e887cSWarner Losh in the number of changed programs the first time when you run 1448409e887cSWarner Losh mergemaster to get a new /etc/security. 1449409e887cSWarner Losh 1450673d13f2SWarner Losh20000710: 1451673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1452673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1453673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1454673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1455673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1456673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1457673d13f2SWarner Losh errors. (see below, 20000624). 1458673d13f2SWarner Losh 1459bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 14601dece4a9SWarner Losh 1461673d13f2SWarner Losh20000709: 1462c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1463c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1464c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1465673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1466673d13f2SWarner Losh 1467e98e26cdSWarner Losh20000706: 1468e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1469e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1470e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1471f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1472e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 14732c021c6cSMark Ovens interim if needed. 1474e98e26cdSWarner Losh 1475e98e26cdSWarner Losh20000705: 1476e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1477e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1478e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1479e98e26cdSWarner Losh details. 1480e98e26cdSWarner Losh 1481c373950eSWarner Losh20000704: 14822f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 14832f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 14842f961bc8SWarner Losh 14852f961bc8SWarner Losh20000704: 1486c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1487c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1488c373950eSWarner Losh rc.d scripts that haven't been updated. 1489c373950eSWarner Losh 149027dc3a2bSWarner Losh20000630: 149127dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 149227dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 149327dc3a2bSWarner Losh which should be reported to des@freebsd.org. 149427dc3a2bSWarner Losh 1495b8c215acSWarner Losh20000625: 1496b8c215acSWarner Losh From approximately this date forward, one must have the crypto 149727dc3a2bSWarner Losh system installed in order to build the system and kernel. 149827dc3a2bSWarner Losh While not technically strictly true, one should treat it as 149927dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 150027dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 150127dc3a2bSWarner Losh were required. You should check with the latest collections 150227dc3a2bSWarner Losh to make sure that these haven't changed. 1503b8c215acSWarner Losh 15047b990719SWarner Losh20000624: 15057b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 15067b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 15077b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 15081a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 15097b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 15107b990719SWarner Losh openssh and openssl should not be used to generate keys from this 15117b990719SWarner Losh date to the completion of the work. 15127b990719SWarner Losh 151327dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 151427dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 151527dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 151627dc3a2bSWarner Losh recreate the random and urandom devices. 151727dc3a2bSWarner Losh 151881e54c50SWarner Losh20000622: 151981e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 152081e54c50SWarner Losh BSD license. You may need to remove your symbolic links 152181e54c50SWarner Losh that used to be required when updating. 152281e54c50SWarner Losh 152339943833SWarner Losh20000621: 15242c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 15252a2f33fbSDaniel Baker the config file update procedure. 15262a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1527c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 152859df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 152959df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 153039943833SWarner Losh 1531290f9ad8SWarner Losh20000620: 1532290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1533290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1534290f9ad8SWarner Losh that workaround will no longer be required. 1535290f9ad8SWarner Losh 153690fb6346SWarner Losh20000615: 153790fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 153890fb6346SWarner Losh ad driver. If you haven't done so already, you must update 153990fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 154090fb6346SWarner Losh devices. 154190fb6346SWarner Losh 1542f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1543f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1544f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1545f75f65bbSWarner Losh may work). 1546f75f65bbSWarner Losh 1547ba26da8eSWarner Losh20000612: 1548ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1549290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1550c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1551290f9ad8SWarner Losh to your config file to compile them in statically. The format 1552f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1553f54a3542SWarner Losh NEWCARD for examples of the new format. 1554290f9ad8SWarner Losh 15559698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 15569698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 15579698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 15589698f2c0SWarner Losh in it. 1559bbcc5149SWarner Losh 1560d65850ebSWarner Losh20000522: 1561ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1562d65850ebSWarner Losh building a kernel after this point is advised that they need 1563d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1564d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1565d65850ebSWarner Losh 1566d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1567d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1568d9583a00SWarner Losh is recommended that you don't set this option until the problem 1569d9583a00SWarner Losh is resolved. 1570d9583a00SWarner Losh 15718039cedeSWarner Losh20000513: 15728039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 15738039cedeSWarner Losh 1574d65850ebSWarner Losh20000510: 15758039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 15768039cedeSWarner Losh This will require some care in updating alphas. A new libstand 15778039cedeSWarner Losh is requires for the boot blocks to build properly. 15788039cedeSWarner Losh 15798039cedeSWarner Losh20000503: 15808039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 15818039cedeSWarner Losh is now available. 15828039cedeSWarner Losh 1583d65850ebSWarner Losh20000502: 1584d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1585d65850ebSWarner Losh connected to the kernel building instead. 1586d65850ebSWarner Losh 1587be149406SNik Clayton20000427: 15888039cedeSWarner Losh You may need to build gperf 15898039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 15908039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 15918039cedeSWarner Losh an option only in -current. 15928039cedeSWarner Losh 15932b8dd5f4SWarner Losh20000417: 15942b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1595f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 15962b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 15972b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 15982c021c6cSMark Ovens before you reboot, you'll need to issue: 15992b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 16002b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 16012b8dd5f4SWarner Losh 16028d9f1945SWarner Losh20000320: 16032b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 16042b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 16052b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1606ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 16072b8dd5f4SWarner Losh to the start of /etc/rc.conf. 16088d9f1945SWarner Losh 1609f8ab1dd6SWarner Losh20000319: 1610f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1611f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1612f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1613f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1614f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1615f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1616f8ab1dd6SWarner Losh 161719cada77SWarner Losh20000318: 1618f699bbbbSMark Ovens We've entered the traditional post release dumping party. 161919cada77SWarner Losh Large kernel changes are being committed and are in the 162019cada77SWarner Losh works. It is important to keep the systems' klds and kernel 162119cada77SWarner Losh in sync as kernel interfaces and structures are changing. 162219cada77SWarner Losh Before reporting kernel panics, make sure that all modules 162319cada77SWarner Losh that you are loading are up to date. 1624ba228352SWarner Losh 162519cada77SWarner Losh20000315: 16266d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 16276d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 16286d23c382SWarner Losh will do the trick. This isn't critical until you remove your 16296d23c382SWarner Losh wd device entries in /dev, at which point your system will not 16306d23c382SWarner Losh boot. 16316d23c382SWarner Losh 16326d23c382SWarner Losh20000315: 163319cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 163419cada77SWarner Losh to upgrade to 4.0 from 3.x. 163557199806SWarner Losh 1636dc0dbf5cSWarner LoshCOMMON ITEMS: 1637dc0dbf5cSWarner Losh 1638cd5f061cSWarner Losh # NOTE: 5.x below applies to 6.0-currrent as well, for the 1639cd5f061cSWarner Losh # momemnt. 4.any -> 5.any upgrade support will remain in 1640cd5f061cSWarner Losh # place for 6.0 current, but after 5.3 RELEASE, the 4.any -> 1641cd5f061cSWarner Losh # 6.0-current upgrade path will require moving through 5.3 1642cd5f061cSWarner Losh # RELEASE or newer. 1643cd5f061cSWarner Losh 1644a24eff53SWarner Losh General Notes 1645a24eff53SWarner Losh ------------- 1646a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1647a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1648a24eff53SWarner Losh installworld. This is especially true when upgrading between 1649a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1650a24eff53SWarner Losh or several minor releases, or when several months have passed 1651a24eff53SWarner Losh on the -current branch). 1652a24eff53SWarner Losh 16535780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 16545780f3baSWarner Losh poisoning. This can happen because the make utility reads its 16555780f3baSWarner Losh environment when searching for values for global variables. 16565780f3baSWarner Losh To run your build attempts in an "environmental clean room", 16575780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 16585780f3baSWarner Losh page for more details. 16595780f3baSWarner Losh 1660dc0dbf5cSWarner Losh To build a kernel 1661dc0dbf5cSWarner Losh ----------------- 1662ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1663f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1664ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1665282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1666282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1667dc0dbf5cSWarner Losh 1668ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1669ba01eb20SWarner Losh -------------------------------------------------------------- 16700fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 16710fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 16720fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 16730fbd2da9SKen Smith 16740fbd2da9SKen Smith cd src/sys/${arch}/conf 167547d0d01fSWarner Losh config KERNEL_NAME_HERE 16760fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1677ba01eb20SWarner Losh make depend 1678ba01eb20SWarner Losh make 1679ba01eb20SWarner Losh make install 1680ba01eb20SWarner Losh 1681ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1682ba01eb20SWarner Losh 1683ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1684ba01eb20SWarner Losh ----------------------------------------------------------- 168563cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 168663cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 168763cb445eSWarner Losh 1688f643de42SWarner Losh <make sure you have good level 0 dumps> 168963cb445eSWarner Losh <maybe fix /etc/fstab> [7] 169063cb445eSWarner Losh make buildworld 16916586253aSWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE 169263cb445eSWarner Losh [1] 169363cb445eSWarner Losh <reboot in single user> [3] 16946586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 169563cb445eSWarner Losh mergemaster -p [5] 169663cb445eSWarner Losh make installworld 169763cb445eSWarner Losh mergemaster [4] 169863cb445eSWarner Losh <reboot> 169963cb445eSWarner Losh 1700759f0aefSWarner Losh 1701f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1702f27b1fceSJoseph Koshy -------------------------------------------------- 1703f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1704f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1705f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1706f27b1fceSJoseph Koshy # size. 1707f27b1fceSJoseph Koshy 1708f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1709f27b1fceSJoseph Koshy <boot into -stable> 1710f27b1fceSJoseph Koshy make buildworld 1711f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1712f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1713f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1714f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 17156586253aSWarner Losh cp src/sys/${ARCH}/conf/GENERIC.hints \ 1716f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1717f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 17186586253aSWarner Losh cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1719f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1720f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1721f27b1fceSJoseph Koshy <reboot into current> 1722f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 17236586253aSWarner Losh <maybe install compatibility libraries from src/lib/compat> 1724f27b1fceSJoseph Koshy <reboot> 1725f27b1fceSJoseph Koshy 1726f27b1fceSJoseph Koshy 1727f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1728f27b1fceSJoseph Koshy ---------------------------------------------- 17295c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 1730e5dc5f61SWarner Losh # modules has changed. If you are installing 5.x onto a 4.x 17315c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 17325c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1733ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1734f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1735f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1736f643de42SWarner Losh # space on /. 1737f643de42SWarner Losh 1738f643de42SWarner Losh <make sure you have good level 0 dumps> 1739fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 174021c075eaSWarner Losh make buildworld [9] 1741802fc49dSBrian Feldman cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1742e5dc5f61SWarner Losh make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1743802fc49dSBrian Feldman cd sys/boot ; make STRIP="" install [6] 1744fc8c157fSWarner Losh [1] 1745fc8c157fSWarner Losh <reboot in single user> [3] 17466586253aSWarner Losh src/etc/rc.d/preseedrandom [10] 1747835284beSWarner Losh mergemaster -p [5] 1748f8a4c901SWarner Losh rm -rf /usr/include/g++ 1749ba26da8eSWarner Losh make installworld 1750802fc49dSBrian Feldman mergemaster -i [4] 1751ba26da8eSWarner Losh <reboot> 1752ba26da8eSWarner Losh 1753fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1754fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1755fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1756fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1757fdb9f54dSWarner Losh the UPDATING entries. 1758ba26da8eSWarner Losh 17591dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 17601dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 17611dece4a9SWarner Losh your sources that you have read and understood all the recent 17621dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 17631dece4a9SWarner Losh much fewer pitfalls. 17641dece4a9SWarner Losh 1765134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1766134d2e86SWarner Losh should disable them at this point so they don't crash your 1767134d2e86SWarner Losh system on reboot. 1768134d2e86SWarner Losh 17699c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 17709c1a7444SWarner Losh your own device.hints to reflect your unique hardware 17719c1a7444SWarner Losh configuration. 17729c1a7444SWarner Losh 1773ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1774ee6e1fc3SWarner Losh fsck -p 1775ee6e1fc3SWarner Losh mount -u / 1776ee6e1fc3SWarner Losh mount -a 17776586253aSWarner Losh cd src 177847d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1779f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1780f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 178166986952SRuslan Ermilov For the 4.x -> 5.x upgrade, you will also see many messages about 1782b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1783b705ae10SWarner Losh be ignored while you proceed to the next step. 1784ee6e1fc3SWarner Losh 1785a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1786a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1787a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1788a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1789a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1790a6cd4f9dSWarner Losh for potential gotchas. 1791a6cd4f9dSWarner Losh 1792835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1793835284beSWarner Losh you may need to do this if you get unknown user in the following 1794835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1795835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1796835284beSWarner Losh install) after the buildworld before this step if you last updated 1797835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1798835284beSWarner Losh 1799bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1800bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1801bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1802bd79cf40SWarner Losh ok unload 1803bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1804bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1805bd79cf40SWarner Losh described here. 1806fc8c157fSWarner Losh 1807fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1808e5dc5f61SWarner Losh compatibility slices. These are device names of the form /dev/ad0a 1809e5dc5f61SWarner Losh without the actual slice name. These will break with 5.x and newer. 1810fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1811e5dc5f61SWarner Losh 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha 1812e5dc5f61SWarner Losh is not. 1813fc8c157fSWarner Losh 1814c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1815c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1816c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1817c74fe6afSWarner Losh that is hard to boot to recover. 1818c74fe6afSWarner Losh 1819e5dc5f61SWarner Losh Make sure that you merge any new devices from GENERIC since the 1820e5dc5f61SWarner Losh last time you updated your kernel config file. 1821e5dc5f61SWarner Losh 182221c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 1823e5dc5f61SWarner Losh cvs prune empty directories. 1824e5dc5f61SWarner Losh 1825e5dc5f61SWarner Losh If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1826e5dc5f61SWarner Losh "?=" instead of the "=" assignment operator, so that buildworld can 1827e5dc5f61SWarner Losh override the CPUTYPE if it needs to. 1828e5dc5f61SWarner Losh 1829e5dc5f61SWarner Losh MAKEOBJDIRPREFIX must be defined in an environment variable, and 1830e5dc5f61SWarner Losh not on the command line, or in /etc/make.conf. buildworld will 1831e5dc5f61SWarner Losh warn if it is improperly defined. 1832e5dc5f61SWarner Losh 1833802fc49dSBrian Feldman In case you would like to avoid installing new packages of everything, 1834802fc49dSBrian Feldman you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 183566986952SRuslan Ermilov compatibility libraries are built which should allow you to continue 1836e5dc5f61SWarner Losh using your existing software for a while. Alternatively, you can 1837e5dc5f61SWarner Losh install the misc/compat4x port. 18388633bbeaSBrooks Davis 18398633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 18406586253aSWarner Losh initialized by feeding data into it. src/etc/rc.d/preseedrandom 18418633bbeaSBrooks Davis takes care of this. 1842dc0dbf5cSWarner LoshFORMAT: 1843dc0dbf5cSWarner Losh 1844f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 18451fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1846f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1847f8ab1dd6SWarner Loshprevious releases if your system is older than this. 18481fc1a0dcSWarner Losh 1849e72fd46aSWarner LoshCopyright information: 1850e72fd46aSWarner Losh 1851e5dc5f61SWarner LoshCopyright 1998-2004 M. Warner Losh. All Rights Reserved. 1852e72fd46aSWarner Losh 1853772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1854772730c7SWarner Loshmodification, in full or in part, in any form or format of this 18559698f2c0SWarner Loshdocument are permitted without further permission from the author. 1856e72fd46aSWarner Losh 1857e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1858e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1859e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1860e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1861e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1862e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1863e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1864e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1865e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1866e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1867e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1868e72fd46aSWarner Losh 1869e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1870e72fd46aSWarner Loshauthor a beer. 1871e72fd46aSWarner Losh 187222306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1873772730c7SWarner Loshthis document. 1874772730c7SWarner Losh 187597d92980SPeter Wemm$FreeBSD$ 1876