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 11f59d5f7aSPoul-Henning KampNOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW: 12f59d5f7aSPoul-Henning Kamp FreeBSD 5.x has many debugging features turned on, in 1369f7bcf3SWarner Losh both the kernel and userland. These features attempt to detect 1469f7bcf3SWarner Losh incorrect use of system primitives, and encourage loud failure 1569f7bcf3SWarner Losh through extra sanity checking and fail stop semantics. They 1669f7bcf3SWarner Losh also substantially impact system performance. If you want to 1769f7bcf3SWarner Losh do performance measurement, benchmarking, and optimization, 1869f7bcf3SWarner Losh you'll want to turn them off. This includes various WITNESS- 1969f7bcf3SWarner Losh related kernel options, INVARIANTS, malloc debugging flags 2069f7bcf3SWarner Losh in userland, and various verbose features in the kernel. Many 2169f7bcf3SWarner Losh developers choose to disable these features on build machines 22a19f8ddaSDavid E. O'Brien to maximize performance. 23c1f61aa9SDavid E. O'Brien 24f13a7951SDavid Malone20040814: 25f13a7951SDavid Malone The RANDOM_IP_ID option has been replaced by the sysctl 26f13a7951SDavid Malone net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then 27f13a7951SDavid Malone you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf. 28f13a7951SDavid Malone 293a004637SMax Laier20040807: 303a004637SMax Laier The size of 'struct ifnet' has changed due to the addition of the 313a004637SMax Laier if_carp placeholder. All kernel modules implementing network 323a004637SMax Laier interfaces must be recompiled as a result. 333a004637SMax Laier 344f34d8d1SJohn-Mark Gurney20040806: 354f34d8d1SJohn-Mark Gurney Module loading has been fixed. Some older installations will 36ac41c814SRuslan Ermilov drop proper module_path initialization and modules will fail to 374f34d8d1SJohn-Mark Gurney load properly. If you have a line in /boot/loader.rc that says: 384f34d8d1SJohn-Mark Gurney "initialize drop", do (i386 only): 394f34d8d1SJohn-Mark Gurney cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc 404f34d8d1SJohn-Mark Gurney chown root:wheel /boot/loader.rc 414f34d8d1SJohn-Mark Gurney chmod 444 /boot/loader.rc 424f34d8d1SJohn-Mark Gurney 438f075db4SMark Murray20040802: 448f075db4SMark Murray making /dev/(null|zero) into a module proved to be too unpopular, 458f075db4SMark Murray so this bit has been revoked from the previous (20040801) entry. 468f075db4SMark Murray 47d064d6dbSMark Murray20040801: 48d064d6dbSMark Murray The /dev/mem, /dev/io /dev/(null/zero) devices are now modules, 49d064d6dbSMark Murray so you may wish to add them to your kernel config file. See 50d064d6dbSMark Murray GENERIC for examples. 51d064d6dbSMark Murray 52b289983eSAlexander Kabaev20040728: 5354bd5271SAlexander Kabaev System compiler has been upgraded to GCC 3.4.2-pre. As with any major 5454bd5271SAlexander Kabaev compiler upgrade, there are several issues to be aware of. GCC 3.4.x 5554bd5271SAlexander Kabaev has broken C++ ABI compatibility with previous releases yet again 5654bd5271SAlexander Kabaev and users will have to rebuild all their C++ programs with the new 5754bd5271SAlexander Kabaev compiler. A new unit-at-a-time optimization mode, which is default 5854bd5271SAlexander Kabaev in this compiler release, is more aggressive in removing unused 5954bd5271SAlexander Kabaev static symbols. This is the likely cause of 'make buildworld' 6054bd5271SAlexander Kabaev breakages with non-default CFLAGS where optimization level is set 6154bd5271SAlexander Kabaev to -O2 or higher. 6254bd5271SAlexander Kabaev 636e1afae3SWarner Losh With the upgrade of the system compiler, the kernel has been upgraded 646e1afae3SWarner Losh to match the new system compiler. This makes it impossible to build 656e1afae3SWarner Losh a new kernel with the old compiler. Upgrade your system via 666e1afae3SWarner Losh make buildworld and make kernel (see below) to fix this problem. 676e1afae3SWarner Losh 6836ed21e6SRobert Watson20040727: 6936ed21e6SRobert Watson The size of 'struct ifnet' has changed due to the addition of 7036ed21e6SRobert Watson the IFF_NEEDSGIANT flag (and what it implies). All kernel 7136ed21e6SRobert Watson modules implementing network interfaces must be recompiled as 7236ed21e6SRobert Watson a result. 7336ed21e6SRobert Watson 746305ac24SSeigo Tanimura20040716: 756305ac24SSeigo Tanimura The sound device drivers are renamed. `sound' is always required, 766305ac24SSeigo Tanimura while `snd_*' should be configured accordingly to your hardware. 776305ac24SSeigo Tanimura Refer to NOTES for the detail of the drivers. 786305ac24SSeigo Tanimura 79e623dcb7SMarcel Moolenaar20040710: 80e623dcb7SMarcel Moolenaar __FreeBSD_version bumped to 502122. 81e623dcb7SMarcel Moolenaar 82e623dcb7SMarcel Moolenaar20040710: 83e623dcb7SMarcel Moolenaar The console initialization on Alpha has been reworked and is now 84e623dcb7SMarcel Moolenaar identical to other platforms. This means that the hardcoding of 85e623dcb7SMarcel Moolenaar the serial console and the debug port has been removed. As such, 86e623dcb7SMarcel Moolenaar hints are now required for the sio(4) driver to become a console 87e623dcb7SMarcel Moolenaar or debug port. The NO_SIO option has been decommissioned because 88e623dcb7SMarcel Moolenaar of this. 89e623dcb7SMarcel Moolenaar 90e623dcb7SMarcel Moolenaar20040710: 91e623dcb7SMarcel Moolenaar A revamp of the debugging code in the kernel with some visible 92e623dcb7SMarcel Moolenaar changes beyond just the debugging experience: 93e623dcb7SMarcel Moolenaar o The DDB option is now specific to the DDB debugger backend 94e623dcb7SMarcel Moolenaar and should not be used any more for conditional compilation 95e623dcb7SMarcel Moolenaar of debugging code for when debugging is enabled. Use the KDB 96e623dcb7SMarcel Moolenaar option for this. 97e623dcb7SMarcel Moolenaar o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have 98e623dcb7SMarcel Moolenaar been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED 99e623dcb7SMarcel Moolenaar respectively. This is in line with the first bullet. 100e623dcb7SMarcel Moolenaar o The remote GDB support has been untangled from DDB and needs 1015bd7ce0aSJens Schweikhardt to be enabled separately now. Use the GDB option for this. 102e623dcb7SMarcel Moolenaar o The GDB_REMOTE_CHAT option has been removed. Support for this 103e623dcb7SMarcel Moolenaar homegrown feature is discontinued. The GDB remote protocol 104e623dcb7SMarcel Moolenaar supports console output and it makes sense to use that. 105e623dcb7SMarcel Moolenaar o The DDB_NOKLDSYM option has been removed. The DDB debugger 106e623dcb7SMarcel Moolenaar now supports both direct symbol table lookups as well as KLD 107e623dcb7SMarcel Moolenaar symbol lookups through the linker. 108e623dcb7SMarcel Moolenaar 1096421d1dbSMaksim Yevmenkin20040708: 1106421d1dbSMaksim Yevmenkin Bluetooth code has been marked as non-i386 specific. 1116421d1dbSMaksim Yevmenkin __FreeBSD_version has been bumped to 502121 to mark this change. 1126421d1dbSMaksim Yevmenkin 11358af3216SWarner Losh20040702: 11458af3216SWarner Losh The native preemption has been added to the kernel scheduler. 1155bd7ce0aSJens Schweikhardt There is some report that the ULE scheduler was broken in some 1165bd7ce0aSJens Schweikhardt machines and we encourage users using the ULE scheduler either 1175bd7ce0aSJens Schweikhardt stick with a known good kernel, or temporarily switch to the 4BSD 11858af3216SWarner Losh scheduler as a workaround. 11958af3216SWarner Losh 120c2dba668SNate Lawson20040630: 1218ed370fdSJulian Elischer The netgraph ABI version number has been incremented to indicate 1228ed370fdSJulian Elischer an incompatible change in the ABI. Old netgraph nodes will refuse 123a6c26e1cSBruce M Simpson to attach until recompiled. Netgraph now uses mbuf tags to move 124a6c26e1cSBruce M Simpson metadata and this commit removes its home-grown metadata facility. 125a6c26e1cSBruce M Simpson Nodes should just recompile, unless they use metadata, in which 126a6c26e1cSBruce M Simpson case the changes are simple; the file ng_ksocket.c serves as an 127a6c26e1cSBruce M Simpson example of such changes. 1288ed370fdSJulian Elischer 12958af3216SWarner Losh This also broke i4b, although the compile problem has been papered 13058af3216SWarner Losh over. 13158af3216SWarner Losh 1328ed370fdSJulian Elischer20040630: 133c2dba668SNate Lawson ACPI has been updated to disable known-bad BIOS revisions. A message 1345bd7ce0aSJens Schweikhardt will be printed on the console indicating that ACPI has been disabled 135c2dba668SNate Lawson automatically and that the user should use a newer BIOS, if possible. 136c2dba668SNate Lawson If you think ACPI does work on your system and want to override 137c2dba668SNate Lawson this (i.e., for testing), set hint.acpi.0.disabled="0" at the 138c2dba668SNate Lawson loader prompt. 139c2dba668SNate Lawson 1408ee2ac9eSMax Laier20040623: 1415bd7ce0aSJens Schweikhardt pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege 1428ee2ac9eSMax Laier separated now. It uses the newly created "_pflogd" user/group 1438ee2ac9eSMax Laier combination. If you plan to use pflogd(8) make sure to run 1448ee2ac9eSMax Laier mergemaster -p or install the "_pflogd" user and group manually. 1458ee2ac9eSMax Laier 1463db5687dSBrooks Davis20040622: 1473db5687dSBrooks Davis Network interface cloning has been overhauled. This change will 1483db5687dSBrooks Davis require a recompile of modules using cloning and modification of 1493db5687dSBrooks Davis external ones to the new API. __FreeBSD_version has been bumped 1503db5687dSBrooks Davis to 502119 to mark this change. Additionally, users creating 1513db5687dSBrooks Davis stf(4) interfaces via "ifconfig stf" will need to update their 1523db5687dSBrooks Davis scripts as this will create an interface named "stf" instead of 1533db5687dSBrooks Davis "stf0" and ifconfig will not print "stf0" to stdout. 1543db5687dSBrooks Davis 155e0ae81f3SDag-Erling Smørgrav20040621: 156e0ae81f3SDag-Erling Smørgrav On 20040524, the /etc/rc.d/nsswitch script was modified to 157e0ae81f3SDag-Erling Smørgrav automatically create /etc/nsswitch.conf on startup if it did 158e0ae81f3SDag-Erling Smørgrav not already exist. Unfortunately, an error in the man page 159e0ae81f3SDag-Erling Smørgrav was carried over to the script, resulting in incorrect 160e0ae81f3SDag-Erling Smørgrav nsswitch settings. The simplest remedy is to remove both 161e0ae81f3SDag-Erling Smørgrav /etc/nsswitch.conf and /etc/host.conf; they will be recreated 162e0ae81f3SDag-Erling Smørgrav during the next reboot. 163e0ae81f3SDag-Erling Smørgrav 1644717d22aSJohn Polstra20040614: 1654717d22aSJohn Polstra The return value of sema_timedwait(9) has been changed to 1664717d22aSJohn Polstra make it consistent with cv_timedwait(9). Be sure to recompile 1674717d22aSJohn Polstra the ips module and any third-party modules which call 1684717d22aSJohn Polstra sema_timedwait. 1694717d22aSJohn Polstra 1706cb7a382SMax Laier20040613: 1716cb7a382SMax Laier ALTQ is now linked to the build. This breaks ABI for struct ifnet. 1726cb7a382SMax Laier Make sure to recompile modules and any userland that makes use of 173df843493SMax Laier sizeof(struct ifnet). In order to get the altq headers in place 174df843493SMax Laier please recompile and reinstall world. 1756cb7a382SMax Laier 1762454685eSJulian Elischer20040607: 1772454685eSJulian Elischer Splitting kern_thread.c into 2 files (adding kern_kse.c) 1782454685eSJulian Elischer requires that you re-run config after updating your tree. 1792454685eSJulian Elischer 18064fef830SSeigo Tanimura20040601: 18164fef830SSeigo Tanimura The MIDI drivers have been removed. Until the new module-friendly 18264fef830SSeigo Tanimura ones are merged, remove or comment out midi and seq from your 18364fef830SSeigo Tanimura kernel configuration. 18464fef830SSeigo Tanimura 185bb4f06e7SAndre Oppermann20040423: 186bb4f06e7SAndre Oppermann Due to a new option in ipfw (versrcreach) the ipfw(8) command 187bb4f06e7SAndre Oppermann needs to be recompiled. Normal accept/reject rules without 188bb4f06e7SAndre Oppermann options are not affected but those with options may break until 189bb4f06e7SAndre Oppermann ipfw(8) is recompiled. 190bb4f06e7SAndre Oppermann 19105641e82SColin Percival20040420: 19205641e82SColin Percival Due to changes in the callout ABI, kernels compiled after this 19305641e82SColin Percival date may be incompatible with kernel modules compiled prior to 19405641e82SColin Percival 20040406. 19505641e82SColin Percival 196d0dc9183SWarner Losh20040414: 197d0dc9183SWarner Losh The PCI bus power state stuff has been turned on. If this causes 198d0dc9183SWarner Losh problems for your system, please disable it using the tunable 199d0dc9183SWarner Losh hw.pci.do_powerstate=0. 200d0dc9183SWarner Losh 201d0dc9183SWarner Losh20040412: 202d0dc9183SWarner Losh The bulk of the pci problems have been fixed, although the floppy 203d0dc9183SWarner Losh drive is still broken. 204d0dc9183SWarner Losh 205d0dc9183SWarner Losh20040410: 206d0dc9183SWarner Losh A substantial update to the pci bus resource and power management 207d0dc9183SWarner Losh have been committed. Expect a bumpy ride for a few days until 208d0dc9183SWarner Losh the unanticipated problems have been resolved. 209d0dc9183SWarner Losh 2108633bbeaSBrooks Davis20040409: 2118633bbeaSBrooks Davis Due to changes in the the Yarrow initialization process, 2128633bbeaSBrooks Davis /dev/random needs to be fed before operations requiring 2138633bbeaSBrooks Davis temp files can succeed in single user mode. This includes 2148633bbeaSBrooks Davis running "make installworld". /dev/random may be fed by running 21576c3e0f7SBrooks Davis "/etc/rc.d/initrandom start" or with 20040415 source by running 2168633bbeaSBrooks Davis "/etc/rc.d/preseedrandom". 2178633bbeaSBrooks Davis 218d40d033aSRobert Watson20040322: 219d40d033aSRobert Watson The debug.mpsafenet tunable controls whether the kernel Giant 220d40d033aSRobert Watson lock is held across the lower levels of the network stack, and 221d40d033aSRobert Watson by default is turned off. In the few days following 20040322, 222d40d033aSRobert Watson the behavior of debug.mpsafenet will change such that this 223d40d033aSRobert Watson tunable controls Giant over all levels of the network stack. 224d40d033aSRobert Watson If you are currently setting debug.mpsafenet to 1, you should 225d40d033aSRobert Watson set it back to 0 (the default) again during the change-over. 226d40d033aSRobert Watson An additional note will be added to UPDATING when sufficient 227d40d033aSRobert Watson locking is merged to permit this to take place. 228d40d033aSRobert Watson 229ec9b318eSGarance A Drosehn20040310: 230ec9b318eSGarance A Drosehn The FreeBSD/sparc64 platform is changing time_t from 32-bits to 231ec9b318eSGarance A Drosehn 64-bits. This is a very major incompatible change, so people 232ec9b318eSGarance A Drosehn using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for 233ec9b318eSGarance A Drosehn detailed instructions on how to make this upgrade. People 234ec9b318eSGarance A Drosehn upgrading FreeBSD on other platforms can ignore this event. 235ec9b318eSGarance A Drosehn 236fc28f1ffSMax Laier20040308: 237fc28f1ffSMax Laier The packet filter (pf) is now installed with the base system. Make 238fc28f1ffSMax Laier sure to run mergemaster -p before installworld to create required 2394c86458bSDavid E. O'Brien user account ("proxy"). If you do not want to build pf with your 2404c86458bSDavid E. O'Brien system you can use the NO_PF knob in make.conf. 241fc28f1ffSMax Laier Also note that pf requires "options PFIL_HOOKS" in the kernel. The 242fc28f1ffSMax Laier pf system consists of the following three devices: 243fc28f1ffSMax Laier device pf # required 244fc28f1ffSMax Laier device pflog # optional 245fc28f1ffSMax Laier device pfsync # optional 246fc28f1ffSMax Laier 2473aff5d06SDag-Erling Smørgrav20040303: 2483aff5d06SDag-Erling Smørgrav If you are having trouble with the libc_r -> libpthread transition 2493aff5d06SDag-Erling Smørgrav (see the 20040130 entry), place the following lines at the top of 2503aff5d06SDag-Erling Smørgrav /etc/libmap.conf: 2513aff5d06SDag-Erling Smørgrav 2523aff5d06SDag-Erling Smørgrav libc_r.so.5 libpthread.so.1 2533aff5d06SDag-Erling Smørgrav libc_r.so libpthread.so 2543aff5d06SDag-Erling Smørgrav 2553aff5d06SDag-Erling Smørgrav This will cause all programs and libraries linked against libc_r 2563aff5d06SDag-Erling Smørgrav to use libpthread instead. 2573aff5d06SDag-Erling Smørgrav 258fd63c5b3SDag-Erling Smørgrav20040226: 2599d7f8c80SDag-Erling Smørgrav Some sshd configuration defaults have changed: protocol version 1 260fd63c5b3SDag-Erling Smørgrav is no longer enabled by default, and password authentication is 261fd63c5b3SDag-Erling Smørgrav disabled by default if PAM is enabled (which it is by default). 262fd63c5b3SDag-Erling Smørgrav OpenSSH clients should not be affected by this; other clients may 263fd63c5b3SDag-Erling Smørgrav have to be reconfigured, upgraded or replaced. 264fd63c5b3SDag-Erling Smørgrav 265714ae42aSBruce M Simpson20040225: 266e07a40f3SBrian Feldman The ABIs defined in <resolv.h> and <netdb.h> have been updated 267e07a40f3SBrian Feldman to support improved reentrancy. Multi-threaded programs that 268e07a40f3SBrian Feldman reference the "_res" or "h_errno" symbols may experience some 269e07a40f3SBrian Feldman problems if they are not recompiled. Single-threaded programs 270e07a40f3SBrian Feldman should remain unaffected. 271e07a40f3SBrian Feldman 272e07a40f3SBrian Feldman20040225: 273714ae42aSBruce M Simpson routed has been updated in the base system from the vendor 274714ae42aSBruce M Simpson sources, routed v2.27, from rhyolite.com. This change means that 275714ae42aSBruce M Simpson for users who use RIP's MD5 authentication feature, FreeBSD 276714ae42aSBruce M Simpson -CURRENT's routed is now incompatible with previous versions 277714ae42aSBruce M Simpson of FreeBSD; however it is now compatible with implementations 278714ae42aSBruce M Simpson from Sun, Cisco and other vendors. 279714ae42aSBruce M Simpson 280fbd2e692SAndre Oppermann20040224: 281fbd2e692SAndre Oppermann The tcpcb structure has changed and makes a recompile of libkvm 2825bd7ce0aSJens Schweikhardt and related userland network utilities necessary. 283fbd2e692SAndre Oppermann 284158b90daSWarner Losh20040222: 285158b90daSWarner Losh The cdevsw structure has changed in two externally visible ways. 286158b90daSWarner Losh First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 287158b90daSWarner Losh Second, the d_version field must be filled in with D_VERSION. 288158b90daSWarner Losh Drivers outside the tree will need to be updated. 289158b90daSWarner Losh 290b7b1e150SMike Makonnen20040207: 291b7b1e150SMike Makonnen The /etc/rc.d/ttys script has been removed. It is no longer 292b7b1e150SMike Makonnen necessary since devfs has been mandatory for some time. 293b7b1e150SMike Makonnen 294aca89ee6SDaniel Eischen20040130: 295aca89ee6SDaniel Eischen libkse has been renamed back to libpthread and is now the 296aca89ee6SDaniel Eischen default threads library. The gcc -pthread option has also 297aca89ee6SDaniel Eischen been changed to link to libpthread instead of libc_r. For 298aca89ee6SDaniel Eischen alpha and sparc64 machines, libkse is not renamed and links 299aca89ee6SDaniel Eischen are installed so that libpthread points to libc_r. Until 300aca89ee6SDaniel Eischen the ports system is updated to handle this change, it is 301aca89ee6SDaniel Eischen recommended that folks install an /etc/libmap.conf(5) that 302aca89ee6SDaniel Eischen maps libc_r to libpthread. If you have any binaries or 303aca89ee6SDaniel Eischen libraries linked to libkse, then it is also recommended 304aca89ee6SDaniel Eischen that you map libkse to libpthread. Anyone that is using 305aca89ee6SDaniel Eischen nvidia supplied drivers and libraries should use a libmap.conf 306aca89ee6SDaniel Eischen that maps libpthread to libc_r since their drivers/libraries 307aca89ee6SDaniel Eischen do not work with libpthread. 308aca89ee6SDaniel Eischen 30968b7b3a9SAlex Dupre20040125: 31068b7b3a9SAlex Dupre ULE has entered into its probationary period as the default scheduler 31168b7b3a9SAlex Dupre in GENERIC. For the average user, interactivity is reported to be 31268b7b3a9SAlex Dupre better in many cases. On SMP machines ULE will be able to make more 31368b7b3a9SAlex Dupre efficient use of the available parallel resources. If you are not 31468b7b3a9SAlex Dupre running it now, please switch over, replacing the kernel option 31568b7b3a9SAlex Dupre SCHED_4BSD with SCHED_ULE. 31668b7b3a9SAlex Dupre 317ff46e0deSWarner Losh20040125: 318ff46e0deSWarner Losh Move LongRun support out of identcpu.c, where it hardly 319ff46e0deSWarner Losh belongs, into its own file and make it opt-in, not mandatory, 320ff46e0deSWarner Losh depending on CPU_ENABLE_LONGRUN config(8) option. 321ff46e0deSWarner Losh 322ce41f4bfSRobert Watson20031213: 323ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 324ce41f4bfSRobert Watson if the login process is unable to successfully set the 325ce41f4bfSRobert Watson process credentials to include all groups defined for the 326ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 327ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 328ce41f4bfSRobert Watson defined, or they will be unable to log in. 329ce41f4bfSRobert Watson 330c124fa05SJohn Baldwin20031203: 331c124fa05SJohn Baldwin The ACPI module has been reactivated. It is no longer required 332c124fa05SJohn Baldwin to compile ACPI support into kernels statically. 333c124fa05SJohn Baldwin 3348ad1f5e4SHartmut Brandt20031112: 33530093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 33630093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 33797209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 33897209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 33997209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 34097209ca3SRobert Watson not know about the new system calls that support the new statfs 3413f631d52SMarcel Moolenaar structure. 3423f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 3433f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 3443f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 3453f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 3463f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 3473f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 3483f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 3493f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 3503f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 3513f631d52SMarcel Moolenaar these changes are installed. 35230093b05SWarner Losh 35330093b05SWarner Losh ****************************DANGER******************************* 35430093b05SWarner Losh 35530093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 35630093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 35730093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 35830093b05SWarner Losh kernel. 35964a18d6fSKirk McKusick 36064a18d6fSKirk McKusick20031112: 3618ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 3628ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 3638ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 3648ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 3658ad1f5e4SHartmut Brandt sync before rebooting. 3668ad1f5e4SHartmut Brandt 367c53a5d8fSJohn Baldwin20031111: 368c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 369c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 370c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 371c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 372c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 373c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 374c53a5d8fSJohn Baldwin 3758bf455a5SJohn Baldwin20031103: 3768bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 3778bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 3782a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 3798bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 3808bf455a5SJohn Baldwin 3819bf40edeSBrooks Davis20031031: 3829bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 3839bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 3849bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 3859bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 3869bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 3879bf40edeSBrooks Davis reflect this change. 3889bf40edeSBrooks Davis 38947a42c7aSPoul-Henning Kamp20030928: 39047a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 39147a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 3925bd7ce0aSJens Schweikhardt __FreeBSD_version bumped to 501110. 39347a42c7aSPoul-Henning Kamp 39407105342SMax Khon20030926: 39507105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 39607105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 39707105342SMax Khon 39817dcd026SSam Leffler20030925: 39917dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 40017dcd026SSam Leffler also be explicitly configured. Previously this dependency was 40117dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 40217dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 40317dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 40417dcd026SSam Leffler 405fedf1d01SBruce M Simpson20030923: 406fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 407fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 408fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 409fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 410fedf1d01SBruce M Simpson 411db38f9cbSJacques Vidrine20030915: 412db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 413db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 414db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 415db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 416db38f9cbSJacques Vidrine 417c09d2c2bSMike Makonnen20030829: 418c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 419c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 420c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 421c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 422c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 423c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 424c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 425c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 426c09d2c2bSMike Makonnen may or may not exist on your system. 427c09d2c2bSMike Makonnen 42817c159dcSSøren Schmidt20030824: 42917c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 43017c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 431f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 432f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 43317c159dcSSøren Schmidt 434c1f61aa9SDavid E. O'Brien20030819: 435c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 436c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 437c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 438c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 43969f7bcf3SWarner Losh 44038c962e7SNate Lawson20030728: 44138c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 44238c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 44338c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 44438c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 44538c962e7SNate Lawson so the quirk can be re-enabled. 44638c962e7SNate Lawson 44774111097SWarner Losh20030724: 44874111097SWarner Losh Problems with entry 20030714 have been corrected and no known issues 44974111097SWarner Losh with /rescue and -j exist for host systems after this point in time. 45074111097SWarner Losh 451178cf4e9SWarner Losh20030722: 452178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 453178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 454178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 455178cf4e9SWarner Losh FPU hardware. 456178cf4e9SWarner Losh 457178cf4e9SWarner Losh20030714: 458178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 459178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 460178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 461178cf4e9SWarner Losh People should report those issues to current@. 462178cf4e9SWarner Losh 463157c629aSWarner Losh20030711: 464157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 4658b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 46605538fa9SWarner Losh /usr/obj. 467157c629aSWarner Losh 46874111097SWarner Losh20030610: 46974111097SWarner Losh Remove deprecated locale names and transition period code 47074111097SWarner Losh for them, finishing switching to the new scheme. Check your 47174111097SWarner Losh LANG environment variable. 47274111097SWarner Losh 47374111097SWarner Losh20030609: 47474111097SWarner Losh CCD has been changed to be a fully GEOMified class. Kernel 47574111097SWarner Losh and ccdconfig(8) needs to be in sync, this is particularly 47674111097SWarner Losh important to remember beforehand if your source tree is on 47774111097SWarner Losh a ccd device. Consider making a copy of the old ccdconfig 47874111097SWarner Losh into /boot/kernel.good or wherever you keep your backup 47974111097SWarner Losh kernel. 48074111097SWarner Losh 48174111097SWarner Losh20030605: 4826cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 4836cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 4846cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 4856cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 4866cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 4876cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 4886cc6353fSMarcel Moolenaar 4896cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 4906cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 4916cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 4926cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 4936cc6353fSMarcel Moolenaar : 4946cc6353fSMarcel Moolenaar 4956cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 4966cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 4976cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 4986cc6353fSMarcel Moolenaar 49952b47445SMark Murray20030505: 50052b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 50152b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 50252b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 50352b47445SMark Murray 504a26df538SWarner Losh20030502: 505a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 506a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 507a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 508a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 509a26df538SWarner Losh 5104b065e2cSDoug Barton20030501: 5114b065e2cSDoug Barton The old rc system has been removed. Please report any problems 5124b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 5134b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 5144b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 5154b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 5164b065e2cSDoug Barton utilizes these old scripts has also been removed. 5174b065e2cSDoug Barton 51881cda3d9SWarner Losh20030423: 51981cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 52081cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 52181cda3d9SWarner Losh work around in devd will be removed around 20030507. You 52281cda3d9SWarner Losh have until then to upgrade your kernel before updating 52381cda3d9SWarner Losh userland. In general, you should have a userland and 52481cda3d9SWarner Losh kernel that's in sync with each other. However, given the 52581cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 52681cda3d9SWarner Losh allowances are made. 52781cda3d9SWarner Losh 52847a657d1SRuslan Ermilov20030329: 52947a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 53047a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 53147a657d1SRuslan Ermilov while upgrading the system through a buildworld. 53247a657d1SRuslan Ermilov 53347a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 53447a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 53547a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 53647a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 53747a657d1SRuslan Ermilov 53847a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 53947a657d1SRuslan Ermilov make cleandir && make obj && \ 54047a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 54147a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 54247a657d1SRuslan Ermilov 5435d2af00cSGregory Neil Shapiro20030208: 5445d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 5455d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 5465d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 5475d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 5485d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 5495d2af00cSGregory Neil Shapiro 5505d2af00cSGregory Neil Shapiro20030128: 5519db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 552ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 5539db58771SPoul-Henning Kamp be removed when convenient. 5549db58771SPoul-Henning Kamp 5558d9b3f57SJake Burkholder20030126: 5568d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 5578d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 5588d9b3f57SJake Burkholder 5591c5efda5SJeff Roberson20030125: 5601c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 5611c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 562ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 5631c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 5641c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 5651c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 5661c5efda5SJeff Roberson 5679d1d64f5SWarner Losh20030115: 5689d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 5699d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 5709d1d64f5SWarner Losh properly. 5719d1d64f5SWarner Losh 572c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 573c9fdb80aSWarner Losh configured for point to point links to bring it more in line 574c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 575c9fdb80aSWarner Losh with NetBSD. 576c9fdb80aSWarner Losh 577161dc364SAlexander Kabaev20021222: 578161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 579161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 580161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 581161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 582161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 583161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 58484cc83efSAlexander Kabaev rebuilt. 585161dc364SAlexander Kabaev 586fb4c8061SMartin Blapp20021216: 587fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 58889056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 589fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 5909d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 591fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 592fb4c8061SMartin Blapp 59317d47eb3SGiorgos Keramidas20021202: 59417d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 59517d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 59617d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 59717d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 59817d47eb3SGiorgos Keramidas 599a4459294SBill Fenner20021029: 600a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 601a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 602a4459294SBill Fenner consumers in sync. 603a4459294SBill Fenner 604fc8c157fSWarner Losh20021024: 605c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 606c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 607c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 608c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 609c57404feSRuslan Ermilov partition really is on. The old device names have gone 610c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 611c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 612c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 61369f7bcf3SWarner Losh 614fd9e8bdaSAndrew Gallatin20021023: 615fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 616fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 617fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 618fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 619fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 620fd9e8bdaSAndrew Gallatin 621fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 622fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 623fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 624fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 625fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 626fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 627fd9e8bdaSAndrew Gallatin 628f8a4c901SWarner Losh20020831: 629f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 630f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 631f8a4c901SWarner Losh programs and libraries need to be recompiled. 632f8a4c901SWarner Losh 633f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 634f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 635f8a4c901SWarner Losh 636c2248fa2SJens Schweikhardt20020827: 637c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 638c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 639c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 640c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 641c2248fa2SJens Schweikhardt 6420d533e43SRuslan Ermilov20020815: 6430d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 6440d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 6450d533e43SRuslan Ermilov again. 6460d533e43SRuslan Ermilov 64733c1de7dSRuslan Ermilov20020729: 64833c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 64933c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 65033c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 65133c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 65233c1de7dSRuslan Ermilov 6532b877facSJulian Elischer20020702: 6542b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 6552b877facSJulian Elischer There are still some minor problems with some signals but the 6562b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 6572b877facSJulian Elischer but each can successfully complete multiple buildworlds. 6582b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 6592b877facSJulian Elischer 66006596d37SWarner Losh20020701: 66106596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 66206596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 66306596d37SWarner Losh GNOME. 66406596d37SWarner Losh 66595ba4330SJacques Vidrine20020511: 66695ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 66795ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 66895ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 66995ba4330SJacques Vidrine with the set-user-ID bit set. 67095ba4330SJacques Vidrine 671a81da3c9SDavid E. O'Brien20020510: 672f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 673f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 6744b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 675f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 676f50caf6fSDavid E. O'Brien 677f50caf6fSDavid E. O'Brien20020510: 678a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 679a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 680a81da3c9SDavid E. O'Brien and then do a cvs update. 681a81da3c9SDavid E. O'Brien 682528a0ef5SJacques Vidrine20020421: 683528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 684528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 685528a0ef5SJacques Vidrine 68685aa5a2eSGregory Neil Shapiro20020404: 68785aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 68885aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 68985aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 69085aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 69185aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 69285aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 69385aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 69485aa5a2eSGregory Neil Shapiro 6958f1e4358SRuslan Ermilov20020403: 6968f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 6978f1e4358SRuslan Ermilov 6982292c02eSWarner Losh20020315: 6992292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 7002292c02eSWarner Losh 70169f7bcf3SWarner Losh20020225: 70269f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 70369f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 70469f7bcf3SWarner Losh 7058f35c493SWarner Losh20020217: 7068f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 7078f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 7088f35c493SWarner Losh command line mail submission has changed. Be sure to run 7098f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 7108f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 7118f35c493SWarner Losh 712835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 713835284beSWarner Losh required in order for sendmail to run as a set-group-ID 714835284beSWarner Losh binary. A 'make installworld' will use the new user and group 715835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 716835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 717835284beSWarner Losh and group must be merged from src/etc/group and 718835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 719835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 720835284beSWarner Losh mergemaster before this will work if you are updating from a 721835284beSWarner Losh very old version of current. The updating recipe has changed 722835284beSWarner Losh as of this date. 723835284beSWarner Losh 724fa9401c1SWarner Losh20020112: 725fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 726fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 727fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 728fa9401c1SWarner Losh you have local modifications, you can use 729fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 730fa9401c1SWarner Losh /etc/pam.d. 731fa9401c1SWarner Losh 732fa9401c1SWarner Losh Please see the following url for more details: 733fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 73447d0d01fSWarner Losh20011229: 73547d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 73647d0d01fSWarner Losh networkfs_types, please note that it has changed 73747d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 73847d0d01fSWarner Losh 739514318a8SWarner Losh20011220: 740514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 741514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 742514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 743514318a8SWarner Losh own. All the accumulated features and bug fixes of the i4b 744514318a8SWarner Losh version have now been merged back into the base system's 745514318a8SWarner Losh version now. The only user-visible change resulting from this 746514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 747514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 748514318a8SWarner Losh as well. (There has never been rc file support for 749514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 750514318a8SWarner Losh reverted by the time the changes are MFCed.) 751514318a8SWarner Losh 752514318a8SWarner Losh20011215: 753514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 754514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 755514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 756514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 757514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 758514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 759514318a8SWarner Losh will need to be customized then for `odd' densities using 760514318a8SWarner Losh fdcontrol(8). 761514318a8SWarner Losh 7622d22e2bfSWarner Losh20011209: 7632d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 7642d22e2bfSWarner Losh and truss(1) now works again. 7652d22e2bfSWarner Losh 7669e0428e2SWarner Losh20011207: 7679e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 7689e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 7699e0428e2SWarner Losh see 7709e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 7719e0428e2SWarner Losh for details. 7729e0428e2SWarner Losh 7739bab8c59SWarner Losh20011204: 7749bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 7759bab8c59SWarner Losh kernel and burncd to be in sync. 7769bab8c59SWarner Losh 777e57d8b01SWarner Losh20011203: 778e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 779e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 780e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 781e57d8b01SWarner Losh not there already. 782e57d8b01SWarner Losh 783e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 784e57d8b01SWarner Losh until the issue has been resolved. 785e57d8b01SWarner Losh 786b001d36fSJacques Vidrine20011202: 787b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 788b001d36fSJacques Vidrine patched. 789b001d36fSJacques Vidrine 7904b676ec1SWarner Losh20011126: 7914b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 7925ebbf43eSWarner Losh after this date. You need to do this only once. 7934b676ec1SWarner Losh 794d961e462SWarner Losh20011103: 795d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 796d961e462SWarner Losh edges may be left, but for the most part things should be 7974b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 798d961e462SWarner Losh 799d961e462SWarner Losh20011030: 800d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 801d961e462SWarner Losh choppy waves in the upgrade process. 802d961e462SWarner Losh 8031fe003b6SWarner Losh20011030: 804a4b6fda0SWarner Losh The asr driver problem has been resolved. 8051fe003b6SWarner Losh 8061fe003b6SWarner Losh20011027: 8071fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 8081fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 8091fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 8101fe003b6SWarner Losh try to use from this date forward. 8111fe003b6SWarner Losh 8121fe003b6SWarner Losh20011025: 8131fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 8141fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 8151fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 8161fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 8171fe003b6SWarner Losh TARGET_ARCH=i386. 8181fe003b6SWarner Losh 819d05f9643SWarner Losh20011001: 820d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 821d05f9643SWarner Losh You must recompile both the kernel and userland applications 822d05f9643SWarner Losh at the same time. 823d05f9643SWarner Losh 82458970f85SWarner Losh20010929: 82558970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 82658970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 82758970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 82858970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 8299d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 83058970f85SWarner Losh 83158970f85SWarner Losh20010927: 83258970f85SWarner Losh Some weird problems result from using ACPI on some machines. 83358970f85SWarner Losh To disable ACPI you can add 83466ff0e67SMax Khon hint.acpi.0.disabled="1" 83558970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 83658970f85SWarner Losh loader "ok" prompt). 83758970f85SWarner Losh 83858970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 83958970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 84058970f85SWarner Losh file and not list acpi in that list. 841378f4486SAlfred Perlstein 8425119d237SWarner Losh20010924: 8435119d237SWarner Losh The buildworld has been fixed. You may need to install 8445119d237SWarner Losh the 4.x compatibility libraries for some old binaries 8458b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 8468b039fffSWarner Losh get them installed on every installworld, or execute the 8478b039fffSWarner Losh following to get them installed only once: 8488b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 84958970f85SWarner Losh make all install 8508b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 8515119d237SWarner Losh 8523c293725SWarner Losh20010919: 8533c293725SWarner Losh There's a bug in the world build process. The cross-tools 8543c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 8553c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 856772730c7SWarner Losh workaround is to add 8573c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 8583c293725SWarner Losh before building world when upgrading from 4.x to current. This 8593c293725SWarner Losh can be removed afterwards. 8603c293725SWarner Losh 8613c293725SWarner Losh A proper fix to the buildworld target is needed. 8623c293725SWarner Losh 8633c293725SWarner Losh20010918: 8643c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 8653c293725SWarner Losh NFS may be unstable after this date. 8663c293725SWarner Losh 8673c293725SWarner Losh20010912: 8683c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 8693c293725SWarner Losh the kernel. While a few problems were introduced in the 8703c293725SWarner Losh initial commit, most of the major ones have been found and 8713c293725SWarner Losh corrected. 8723c293725SWarner Losh 8733c293725SWarner Losh20010901: 8743c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 8753c293725SWarner Losh arounds described in the 20010604 entry are now no longer 8763c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 8773c293725SWarner Losh have been rectified around this date. 8783c293725SWarner Losh 87998b17b95SWarner Losh20010823: 88098b17b95SWarner Losh named now runs as user bind and group bind rather than as 88198b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 88298b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 88398b17b95SWarner Losh and that group bind is available in /etc/group. Also make 88498b17b95SWarner Losh sure that user or group bind has read (and not write) 88598b17b95SWarner Losh permission for your name server configuration and that it 88698b17b95SWarner Losh has read and write permission for your slave zone files and 88798b17b95SWarner Losh directory. 88898b17b95SWarner Losh 88998b17b95SWarner Losh If you wish to continue to run named as root (a less secure 89098b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 89198b17b95SWarner Losh 89298b17b95SWarner Losh named_flags= 89398b17b95SWarner Losh 8947b9786edSMark Murray20010709: 8957b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 8967b9786edSMark Murray the ability of the shared library major number to handle. 8977b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 8987b9786edSMark Murray solution is to rebuild those ports. 8997b9786edSMark Murray 9001d28950eSWarner Losh20010628: 9011d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 9021d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 9031d28950eSWarner Losh 904e72fd46aSWarner Losh20010625: 90598b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 90698b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 90798b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 90898b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 90998b17b95SWarner Losh IRQ configuration needs more safety belts. 91016de1a07SWarner Losh 9110d415dffSWarner Losh20010617: 912e72fd46aSWarner Losh Softupdates problems have been corrected. 9130d415dffSWarner Losh 9140d415dffSWarner Losh20010614: 9150d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 9160d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 9170d415dffSWarner Losh kernel building methods. 9180d415dffSWarner Losh 9198b9959adSWarner Losh20010613: 9208b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 9218b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 922e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 923e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 9248b9959adSWarner Losh 925e72fd46aSWarner Losh20010613: 9268b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 927e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 928e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 9298b9959adSWarner Losh 9300d415dffSWarner Losh20010612: 9310d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 9320d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 9330d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 9340d415dffSWarner Losh work around this issue, please use only one or the other mechanism 9350d415dffSWarner Losh until this bug is fixed. 9360d415dffSWarner Losh 937e72fd46aSWarner Losh Please note that a feature of config is that if you have config 938e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 939ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 940e72fd46aSWarner Losh 9410d415dffSWarner Losh20010610: 9420d415dffSWarner Losh Locale names have changed to match other systems better. 9430d415dffSWarner Losh 9446ccdb5e4SWarner Losh20010604: 9456ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 9466ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 9476ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 9483590182eSWarner Losh Interrupt storms look a lot like a hang. 9493590182eSWarner Losh 9503590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 9513590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 9523590182eSWarner Losh it is). 9533590182eSWarner Losh 9543590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 9553590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 9563590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 9573590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 9586ccdb5e4SWarner Losh 9590bc62786SWarner Losh20010530: 9600bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 9610bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 9620bc62786SWarner Losh a limited time. If you see 9630bc62786SWarner Losh 9640bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 9650bc62786SWarner Losh 9660bc62786SWarner Losh in your makeworld, then you need to migrate towards using 9670bc62786SWarner Losh COPY=-C. 9680bc62786SWarner Losh 96968a38c6cSWarner Losh20010525: 970b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 971c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 972c4f4a728SWarner Losh definitely is in bad shape. 97368a38c6cSWarner Losh 974ed0f29caSWarner Losh20010521: 975ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 976ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 977ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 978ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 979ed0f29caSWarner Losh is 980ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 981ed0f29caSWarner Losh 98280c16af9SWarner Losh20010520: 98368a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 98480c16af9SWarner Losh 98580c16af9SWarner Losh20010519: 98680c16af9SWarner Losh pccard has had much reorganizational work done to it over 98780c16af9SWarner Losh the past few days. Everything should still work, but if 98880c16af9SWarner Losh not, please contact imp@freebsd.org. 98980c16af9SWarner Losh 990a45f2d05SWarner Losh20010517: 991a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 992a45f2d05SWarner Losh userland at the same time. 993a45f2d05SWarner Losh 994a45f2d05SWarner Losh20010517: 995a45f2d05SWarner Losh New ncurses imported. 996a45f2d05SWarner Losh 9972988afcaSWarner Losh20010512: 9982988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 9992988afcaSWarner Losh will be the only way to go starting July 1. 10002988afcaSWarner Losh 10011a33dba7SWarner Losh20010504: 10021a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 10031a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 10041a33dba7SWarner Losh 100509946a51SWarner Losh20010502: 100609946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 100709946a51SWarner Losh 100809946a51SWarner Losh20010501: 100909946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 101009946a51SWarner Losh 101109946a51SWarner Losh20010430: 1012a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 101309946a51SWarner Losh go back in the water. 101409946a51SWarner Losh 101509946a51SWarner Losh20010429: 101609946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 101709946a51SWarner Losh this date, but before the correction date. 101809946a51SWarner Losh 101991dd3b53SWarner Losh20010423: 102091dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 102191dd3b53SWarner Losh 102291dd3b53SWarner Losh20010411: 102391dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 102491dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 102591dd3b53SWarner Losh Update only if you understand that you must not use the old 102691dd3b53SWarner Losh fsck with the new kernel ever. 102791dd3b53SWarner Losh 1028933b3269SWarner Losh20010330: 1029933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 1030c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 1031933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 1032933b3269SWarner Losh 1033933b3269SWarner Losh20010319: 1034933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 1035933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 1036933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 1037f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 103809946a51SWarner Losh 103909946a51SWarner Losh20010315: 104009946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 1041ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 104209946a51SWarner Losh been replaced by tunables. See ata.4 for details. 1043933b3269SWarner Losh 1044933b3269SWarner Losh20010312: 1045933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 1046933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 1047933b3269SWarner Losh 1048933b3269SWarner Losh20010312: 1049933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 1050933b3269SWarner Losh instead of ad-hoc. 1051933b3269SWarner Losh 1052933b3269SWarner Losh20010310: 1053f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 1054933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 1055933b3269SWarner Losh ssh might not work if you don't. 1056933b3269SWarner Losh 105762353691SWarner Losh20010303: 105862353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 105962353691SWarner Losh which means that you must include the miibus in your kernel if 106062353691SWarner Losh you use the ed driver. 106162353691SWarner Losh 1062d325cf65SWarner Losh20010220: 1063d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 1064d325cf65SWarner Losh safe to go back into the water. 1065d325cf65SWarner Losh 1066024daae6SWarner Losh20010211: 1067024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 1068024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 1069024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 1070024daae6SWarner Losh that before upgrading would be a good time to do a level 0 1071024daae6SWarner Losh dump of your system. No, really, I mean it this time. 1072024daae6SWarner Losh 1073024daae6SWarner Losh To get to the new system, you'll need to use the following 1074024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 1075024daae6SWarner Losh don't have to move this to the updating section. 1076024daae6SWarner Losh 1077024daae6SWarner Losh To get around the installworld problem, do: 1078024daae6SWarner Losh # cd /usr/src/usr.bin/sed 1079024daae6SWarner Losh # make install 1080024daae6SWarner Losh # cd /usr/src 1081024daae6SWarner Losh # make installworld 1082024daae6SWarner Losh If that doesn't work, then try: 1083024daae6SWarner Losh # make -k installworld 1084024daae6SWarner Losh # make installworld 1085024daae6SWarner Losh 1086024daae6SWarner Losh20010207: 1087024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 1088024daae6SWarner Losh do not include devfs in your kernel as problems result. 1089024daae6SWarner Losh 1090024daae6SWarner Losh20010205: 10917595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 1092024daae6SWarner Losh Remove them from your config. 1093024daae6SWarner Losh 10941e159248SWarner Losh20010122: 10951e159248SWarner Losh ****************************** WARNING ****************************** 10961e159248SWarner Losh buildkernel has been changed slightly 10971e159248SWarner Losh ****************************** WARNING ****************************** 10981e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 10991e159248SWarner Losh should update your scripts and make.conf accordingly. 11001e159248SWarner Losh 11011e159248SWarner Losh20010119: 11021e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 11031e159248SWarner Losh This requires a new config to build correctly. 11041e159248SWarner Losh 1105aac7dfeaSWarner Losh20010116: 1106ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 1107aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 1108aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 1109aac7dfeaSWarner Losh 1110aac7dfeaSWarner Losh20010110: 1111aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 1112aac7dfeaSWarner Losh 1113aac7dfeaSWarner Losh20010102: 1114aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 1115aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 1116aac7dfeaSWarner Losh 111763c90c9eSWarner Losh20010101: 111863c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 111963c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 11205fd2a895SWarner Losh dump while building termcap. You can work around this problem 112163c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 112263c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 112363c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 112463c90c9eSWarner Losh might have been ignored by the -k option. 112563c90c9eSWarner Losh 11265fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 11275fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 11285fd2a895SWarner Losh of this working. 11295fd2a895SWarner Losh 1130aac7dfeaSWarner Losh20001228: 1131aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 1132ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 1133aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 1134aac7dfeaSWarner Losh 1135de2bcc63SWarner Losh20001218: 1136de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 1137de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 1138de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 1139de2bcc63SWarner Losh cards will not be recognized without it. 1140de2bcc63SWarner Losh 1141960773f7SWarner Losh20001205: 1142960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 1143960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 1144960773f7SWarner Losh adding the following in pam.conf: 1145960773f7SWarner Losh 1146960773f7SWarner Losh sshd auth sufficient pam_skey.so 1147960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 1148960773f7SWarner Losh sshd session required pam_permit.so 1149960773f7SWarner Losh 11500acc635eSWarner Losh20001031: 11510acc635eSWarner Losh cvs updated to 1.11. 11520acc635eSWarner Losh 11530acc635eSWarner Losh20001020: 11540acc635eSWarner Losh The random device needs more entropy, so you need to make sure 11550acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 11560acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 11570acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 11580acc635eSWarner Losh workaround. 11590acc635eSWarner Losh 11600acc635eSWarner Losh20001010: 11610acc635eSWarner Losh ****************************** WARNING ****************************** 11620acc635eSWarner Losh Sendmail has been updated. 11630acc635eSWarner Losh ****************************** WARNING ****************************** 11640acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 11650acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 11660acc635eSWarner Losh is set. 11670acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 11680acc635eSWarner Losh commands. 11690acc635eSWarner Losh o Now using sendmail's version of vacation(1). 11700acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 11710acc635eSWarner Losh in /usr/share/sendmail/cf. 11720acc635eSWarner Losh o sendmail.cw changed to local-host-names 11730acc635eSWarner Losh 11740acc635eSWarner Losh More details can be found at 11750acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 11760acc635eSWarner Losh 11776e98a146SWarner Losh20001009: 11786e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 11796e98a146SWarner Losh your entire ports tree, or you will have problems. 11806e98a146SWarner Losh 11816e98a146SWarner Losh20001006: 1182685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 11836e98a146SWarner Losh the installed miniperl. It is recommended that you delete 11846e98a146SWarner Losh /usr/bin/miniperl. 11856e98a146SWarner Losh 1186073113a4SWarner Losh20001005: 1187073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 1188685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 1189073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 1190073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 1191073113a4SWarner Losh tree for anything to work. 1192073113a4SWarner Losh 11930acc635eSWarner Losh20000928: 11940acc635eSWarner Losh There was a change in the passwd format. Need more information. 11950acc635eSWarner Losh 1196be3885b3SWarner Losh20000916: 1197be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 1198be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 1199be3885b3SWarner Losh same time as your kernel. 1200be3885b3SWarner Losh 120176ec9675SWarner Losh20000914: 120276ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 120376ec9675SWarner Losh include the device will cause suspended laptops losing time 120476ec9675SWarner Losh when they resume. Include 120576ec9675SWarner Losh device pmtimer 120676ec9675SWarner Losh in your config file and 120701b9a434SWarner Losh hint.pmtimer.0.at="isa" 120876ec9675SWarner Losh to your /boot/device.hints file. 120976ec9675SWarner Losh 1210f4865386SMark Murray20000911: 1211f4865386SMark Murray The random device has been turned into a (pseudo-)device, 1212f4865386SMark Murray rather than an option. The supplied kernel config files have 1213f4865386SMark Murray been updated. You will need to do something similar in your 1214f4865386SMark Murray own kernel config file. 1215f4865386SMark Murray Remove: 1216f4865386SMark Murray options RANDOMDEV 1217f4865386SMark Murray Add: 1218f4865386SMark Murray device random 1219f4865386SMark Murray If you prefer to load the loadable module, you need to do 1220f4865386SMark Murray nothing. 1221f4865386SMark Murray 1222d594498fSWarner Losh20000909: 1223d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 1224d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 1225d594498fSWarner Losh reflect this if you load this module at boot time. 1226d594498fSWarner Losh The line should read: 1227d594498fSWarner Losh random_load="YES" 1228d594498fSWarner Losh 12290deb7ddcSWarner Losh20000907: 12300deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 123116eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 123216eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 123316eb772dSWarner Losh sure you don't have model loading problems which might at 123416eb772dSWarner Losh first blush appear related to SMP. 123552bf24e7SWarner Losh 12365a01880bSWarner Losh20000906: 12375a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 12385a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 12395a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 12405a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 12415a01880bSWarner Losh don't have one, and you have host.conf. 12425a01880bSWarner Losh 12432b41163cSWarner Losh20000905: 124438d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 124538d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 124638d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 124738d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 124838d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 124938d6ecd2SWarner Losh 125038d6ecd2SWarner Losh20000905: 12518aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 12528aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 12538aab4bc7SWarner Losh is /boot/kernel. 12548aab4bc7SWarner Losh 12558aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 125638d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 125738d6ecd2SWarner Losh installkernel/installworld dance. 12582b41163cSWarner Losh 1259d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 1260d594498fSWarner Losh before booting the new kernel, since kldload will find stale 1261d594498fSWarner Losh modules in that directory instead of finding them in the correct 1262d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 1263d594498fSWarner Losh is that the linux module crashes your machine after the update. 1264d594498fSWarner Losh 1265d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 1266d594498fSWarner Losh mv /modules.old /boot/kernel.old 1267d594498fSWarner Losh chflags noschg /kernel.old 1268d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 1269d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 1270d594498fSWarner Losh fi 1271d594498fSWarner Losh 1272c22a309cSWarner Losh20000904: 1273c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 1274c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1275c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 1276c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 1277c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 1278c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 1279c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 1280c22a309cSWarner Losh is not likely to be generated. 1281c22a309cSWarner Losh 1282fdb9f54dSWarner Losh20000825: 1283fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 12849c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 12859c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 12869c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 12879c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 12889c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 12899c1a7444SWarner Losh messages will appear after the boot loader tries to start the 12909c1a7444SWarner Losh kernel. 12919c1a7444SWarner Losh 12929c1a7444SWarner Losh20000821: 12939c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 12949c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 12959c1a7444SWarner Losh /boot/loader.conf. 1296fdb9f54dSWarner Losh 12978f250aa7SWarner Losh20000812: 12985da0d091SWarner Losh suidperl is now always built and installed on the system, but 12995da0d091SWarner Losh with permissions of 511. If you have applications that use 13005da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 13015da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 13025da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 13035da0d091SWarner Losh will fix this until the next build. 13045da0d091SWarner Losh 13055da0d091SWarner Losh20000812: 13068f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 13078f250aa7SWarner Losh visible changes that may immediately affect your configuration 13088f250aa7SWarner Losh include: 13098f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 13108f250aa7SWarner Losh - newaliases limited to root and trusted users 13118f250aa7SWarner Losh - MSA port (587) turned on by default 13128f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 13138f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 13148f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 13158f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 13168f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 13178f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 13188f250aa7SWarner Losh 131971c38472SWarner Losh20000810: 132071c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 132171c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 132271c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 132371c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 132471c38472SWarner Losh specific use for it. 132571c38472SWarner Losh 132671c38472SWarner Losh20000729: 132771c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 132871c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 132971c38472SWarner Losh /etc/rc.conf if they want to have the same setup 133071c38472SWarner Losh afterwards (unless the variables already are set, of course): 133171c38472SWarner Losh # Enable network daemons for user convenience. 133271c38472SWarner Losh inetd_enable="YES" 133371c38472SWarner Losh portmap_enable="YES" 133471c38472SWarner Losh sendmail_enable="YES" 133571c38472SWarner Losh 133671c38472SWarner Losh20000728: 133771c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 133871c38472SWarner Losh will need to change that to nullfs_load="YES". 133971c38472SWarner Losh 13401dece4a9SWarner Losh20000728: 13411dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 13421dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 13431dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 13441dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 13451dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 13461dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 13471dece4a9SWarner Losh to /MYKERNEL. 13481dece4a9SWarner Losh 1349409e887cSWarner Losh20000711: 1350409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1351409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1352409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1353409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1354409e887cSWarner Losh for details on potential problems that you might have and how 1355409e887cSWarner Losh to get around them. 1356409e887cSWarner Losh 1357409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1358409e887cSWarner Losh clauses above, you needn't worry. 1359409e887cSWarner Losh 1360409e887cSWarner Losh20000711: 1361409e887cSWarner Losh /etc/security has been updated to print the inode number of 1362409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1363409e887cSWarner Losh in the number of changed programs the first time when you run 1364409e887cSWarner Losh mergemaster to get a new /etc/security. 1365409e887cSWarner Losh 1366673d13f2SWarner Losh20000710: 1367673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1368673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1369673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1370673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1371673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1372673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1373673d13f2SWarner Losh errors. (see below, 20000624). 1374673d13f2SWarner Losh 1375bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 13761dece4a9SWarner Losh 1377673d13f2SWarner Losh20000709: 1378c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1379c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1380c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1381673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1382673d13f2SWarner Losh 1383e98e26cdSWarner Losh20000706: 1384e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1385e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1386e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1387f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1388e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 13892c021c6cSMark Ovens interim if needed. 1390e98e26cdSWarner Losh 1391e98e26cdSWarner Losh20000705: 1392e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1393e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1394e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1395e98e26cdSWarner Losh details. 1396e98e26cdSWarner Losh 1397c373950eSWarner Losh20000704: 13982f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 13992f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 14002f961bc8SWarner Losh 14012f961bc8SWarner Losh20000704: 1402c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1403c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1404c373950eSWarner Losh rc.d scripts that haven't been updated. 1405c373950eSWarner Losh 140627dc3a2bSWarner Losh20000630: 140727dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 140827dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 140927dc3a2bSWarner Losh which should be reported to des@freebsd.org. 141027dc3a2bSWarner Losh 1411b8c215acSWarner Losh20000625: 1412b8c215acSWarner Losh From approximately this date forward, one must have the crypto 141327dc3a2bSWarner Losh system installed in order to build the system and kernel. 141427dc3a2bSWarner Losh While not technically strictly true, one should treat it as 141527dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 141627dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 141727dc3a2bSWarner Losh were required. You should check with the latest collections 141827dc3a2bSWarner Losh to make sure that these haven't changed. 1419b8c215acSWarner Losh 14207b990719SWarner Losh20000624: 14217b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 14227b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 14237b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 14241a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 14257b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 14267b990719SWarner Losh openssh and openssl should not be used to generate keys from this 14277b990719SWarner Losh date to the completion of the work. 14287b990719SWarner Losh 142927dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 143027dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 143127dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 143227dc3a2bSWarner Losh recreate the random and urandom devices. 143327dc3a2bSWarner Losh 143481e54c50SWarner Losh20000622: 143581e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 143681e54c50SWarner Losh BSD license. You may need to remove your symbolic links 143781e54c50SWarner Losh that used to be required when updating. 143881e54c50SWarner Losh 143939943833SWarner Losh20000621: 14402c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 14412a2f33fbSDaniel Baker the config file update procedure. 14422a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1443c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 144459df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 144559df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 144639943833SWarner Losh 1447290f9ad8SWarner Losh20000620: 1448290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1449290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1450290f9ad8SWarner Losh that workaround will no longer be required. 1451290f9ad8SWarner Losh 145290fb6346SWarner Losh20000615: 145390fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 145490fb6346SWarner Losh ad driver. If you haven't done so already, you must update 145590fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 145690fb6346SWarner Losh devices. 145790fb6346SWarner Losh 1458f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1459f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1460f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1461f75f65bbSWarner Losh may work). 1462f75f65bbSWarner Losh 1463ba26da8eSWarner Losh20000612: 1464ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1465290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1466c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1467290f9ad8SWarner Losh to your config file to compile them in statically. The format 1468f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1469f54a3542SWarner Losh NEWCARD for examples of the new format. 1470290f9ad8SWarner Losh 14719698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 14729698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 14739698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 14749698f2c0SWarner Losh in it. 1475bbcc5149SWarner Losh 1476d65850ebSWarner Losh20000522: 1477ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1478d65850ebSWarner Losh building a kernel after this point is advised that they need 1479d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1480d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1481d65850ebSWarner Losh 1482d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1483d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1484d9583a00SWarner Losh is recommended that you don't set this option until the problem 1485d9583a00SWarner Losh is resolved. 1486d9583a00SWarner Losh 14878039cedeSWarner Losh20000513: 14888039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 14898039cedeSWarner Losh 1490d65850ebSWarner Losh20000510: 14918039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 14928039cedeSWarner Losh This will require some care in updating alphas. A new libstand 14938039cedeSWarner Losh is requires for the boot blocks to build properly. 14948039cedeSWarner Losh 14958039cedeSWarner Losh20000503: 14968039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 14978039cedeSWarner Losh is now available. 14988039cedeSWarner Losh 1499d65850ebSWarner Losh20000502: 1500d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1501d65850ebSWarner Losh connected to the kernel building instead. 1502d65850ebSWarner Losh 1503be149406SNik Clayton20000427: 15048039cedeSWarner Losh You may need to build gperf 15058039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 15068039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 15078039cedeSWarner Losh an option only in -current. 15088039cedeSWarner Losh 15092b8dd5f4SWarner Losh20000417: 15102b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1511f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 15122b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 15132b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 15142c021c6cSMark Ovens before you reboot, you'll need to issue: 15152b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 15162b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 15172b8dd5f4SWarner Losh 15188d9f1945SWarner Losh20000320: 15192b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 15202b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 15212b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1522ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 15232b8dd5f4SWarner Losh to the start of /etc/rc.conf. 15248d9f1945SWarner Losh 1525f8ab1dd6SWarner Losh20000319: 1526f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1527f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1528f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1529f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1530f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1531f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1532f8ab1dd6SWarner Losh 153319cada77SWarner Losh20000318: 1534f699bbbbSMark Ovens We've entered the traditional post release dumping party. 153519cada77SWarner Losh Large kernel changes are being committed and are in the 153619cada77SWarner Losh works. It is important to keep the systems' klds and kernel 153719cada77SWarner Losh in sync as kernel interfaces and structures are changing. 153819cada77SWarner Losh Before reporting kernel panics, make sure that all modules 153919cada77SWarner Losh that you are loading are up to date. 1540ba228352SWarner Losh 154119cada77SWarner Losh20000315: 15426d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 15436d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 15446d23c382SWarner Losh will do the trick. This isn't critical until you remove your 15456d23c382SWarner Losh wd device entries in /dev, at which point your system will not 15466d23c382SWarner Losh boot. 15476d23c382SWarner Losh 15486d23c382SWarner Losh20000315: 154919cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 155019cada77SWarner Losh to upgrade to 4.0 from 3.x. 155157199806SWarner Losh 1552dc0dbf5cSWarner LoshCOMMON ITEMS: 1553dc0dbf5cSWarner Losh 1554a24eff53SWarner Losh General Notes 1555a24eff53SWarner Losh ------------- 1556a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1557a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1558a24eff53SWarner Losh installworld. This is especially true when upgrading between 1559a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1560a24eff53SWarner Losh or several minor releases, or when several months have passed 1561a24eff53SWarner Losh on the -current branch). 1562a24eff53SWarner Losh 15635780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 15645780f3baSWarner Losh poisoning. This can happen because the make utility reads its 15655780f3baSWarner Losh environment when searching for values for global variables. 15665780f3baSWarner Losh To run your build attempts in an "environmental clean room", 15675780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 15685780f3baSWarner Losh page for more details. 15695780f3baSWarner Losh 1570dc0dbf5cSWarner Losh To build a kernel 1571dc0dbf5cSWarner Losh ----------------- 1572ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1573f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1574ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1575282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1576282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1577dc0dbf5cSWarner Losh 1578ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1579ba01eb20SWarner Losh -------------------------------------------------------------- 15800fbd2da9SKen Smith This assumes you are already running a 5.X system. Replace 15810fbd2da9SKen Smith ${arch} with the architecture of your machine (e.g. "i386", 15820fbd2da9SKen Smith "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 15830fbd2da9SKen Smith 15840fbd2da9SKen Smith cd src/sys/${arch}/conf 158547d0d01fSWarner Losh config KERNEL_NAME_HERE 15860fbd2da9SKen Smith cd ../compile/KERNEL_NAME_HERE 1587ba01eb20SWarner Losh make depend 1588ba01eb20SWarner Losh make 1589ba01eb20SWarner Losh make install 1590ba01eb20SWarner Losh 1591ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1592ba01eb20SWarner Losh 1593ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1594ba01eb20SWarner Losh ----------------------------------------------------------- 159563cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 159663cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 159763cb445eSWarner Losh 1598f643de42SWarner Losh <make sure you have good level 0 dumps> 159963cb445eSWarner Losh <maybe fix /etc/fstab> [7] 160063cb445eSWarner Losh make buildworld 160163cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 160263cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 160363cb445eSWarner Losh [1] 160463cb445eSWarner Losh <reboot in single user> [3] 16058633bbeaSBrooks Davis /etc/rc.d/preseedrandom [10] 160663cb445eSWarner Losh mergemaster -p [5] 160763cb445eSWarner Losh make installworld 160863cb445eSWarner Losh mergemaster [4] 160963cb445eSWarner Losh <reboot> 161063cb445eSWarner Losh 1611759f0aefSWarner Losh 1612f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1613f27b1fceSJoseph Koshy -------------------------------------------------- 1614f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1615f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1616f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1617f27b1fceSJoseph Koshy # size. 1618f27b1fceSJoseph Koshy 1619f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1620f27b1fceSJoseph Koshy <boot into -stable> 1621f27b1fceSJoseph Koshy make buildworld 1622f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1623f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1624f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1625f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1626f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1627f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1628f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1629f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1630f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1631f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1632f27b1fceSJoseph Koshy <reboot into current> 1633f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1634f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1635f27b1fceSJoseph Koshy <reboot> 1636f27b1fceSJoseph Koshy 1637f27b1fceSJoseph Koshy 1638f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1639f27b1fceSJoseph Koshy ---------------------------------------------- 16405c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 16415c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 16425c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 16435c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1644ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1645f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1646f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1647f643de42SWarner Losh # space on /. 1648f643de42SWarner Losh 1649f643de42SWarner Losh <make sure you have good level 0 dumps> 1650fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 165121c075eaSWarner Losh make buildworld [9] 1652c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1653802fc49dSBrian Feldman cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1654be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1655802fc49dSBrian Feldman cd sys/boot ; make STRIP="" install [6] 1656fc8c157fSWarner Losh [1] 1657fc8c157fSWarner Losh <reboot in single user> [3] 1658802fc49dSBrian Feldman /usr/src/etc/rc.d/preseedrandom [10] 1659835284beSWarner Losh mergemaster -p [5] 1660f8a4c901SWarner Losh rm -rf /usr/include/g++ 1661ba26da8eSWarner Losh make installworld 1662802fc49dSBrian Feldman mergemaster -i [4] 1663ba26da8eSWarner Losh <reboot> 1664ba26da8eSWarner Losh 1665fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1666fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1667fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1668fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1669fdb9f54dSWarner Losh the UPDATING entries. 1670ba26da8eSWarner Losh 16711dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 16721dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 16731dece4a9SWarner Losh your sources that you have read and understood all the recent 16741dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 16751dece4a9SWarner Losh much fewer pitfalls. 16761dece4a9SWarner Losh 1677134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1678134d2e86SWarner Losh should disable them at this point so they don't crash your 1679134d2e86SWarner Losh system on reboot. 1680134d2e86SWarner Losh 16819c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 16829c1a7444SWarner Losh your own device.hints to reflect your unique hardware 16839c1a7444SWarner Losh configuration. 16849c1a7444SWarner Losh 1685ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1686ee6e1fc3SWarner Losh fsck -p 1687ee6e1fc3SWarner Losh mount -u / 1688ee6e1fc3SWarner Losh mount -a 1689ee6e1fc3SWarner Losh cd /usr/src 169047d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1691f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1692f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 169366986952SRuslan Ermilov For the 4.x -> 5.x upgrade, you will also see many messages about 1694b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1695b705ae10SWarner Losh be ignored while you proceed to the next step. 1696ee6e1fc3SWarner Losh 1697a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1698a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1699a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1700a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1701a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1702a6cd4f9dSWarner Losh for potential gotchas. 1703a6cd4f9dSWarner Losh 1704835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1705835284beSWarner Losh you may need to do this if you get unknown user in the following 1706835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1707835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1708835284beSWarner Losh install) after the buildworld before this step if you last updated 1709835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1710835284beSWarner Losh 1711bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1712bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1713bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1714bd79cf40SWarner Losh ok unload 1715bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1716bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1717bd79cf40SWarner Losh described here. 1718fc8c157fSWarner Losh 1719fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1720fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1721fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1722fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1723fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1724fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1725fc8c157fSWarner Losh 1726c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1727c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1728c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1729c74fe6afSWarner Losh that is hard to boot to recover. 1730c74fe6afSWarner Losh 173121c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 1732802fc49dSBrian Feldman cvs prune empty directories. Also, if CPUTYPE is defined in your 1733802fc49dSBrian Feldman /etc/make.conf, make sure to use the "?=" instead of the "=" assignment 1734802fc49dSBrian Feldman operator, so that buildworld can override the CPUTYPE if it needs to. 1735802fc49dSBrian Feldman In case you would like to avoid installing new packages of everything, 1736802fc49dSBrian Feldman you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 173766986952SRuslan Ermilov compatibility libraries are built which should allow you to continue 1738802fc49dSBrian Feldman using your existing software for a while. 17398633bbeaSBrooks Davis 17408633bbeaSBrooks Davis [10] In order to create temporary files, /dev/random must be 174166986952SRuslan Ermilov initialized by feeding data into it. /usr/src/etc/rc.d/preseedrandom 17428633bbeaSBrooks Davis takes care of this. 1743dc0dbf5cSWarner LoshFORMAT: 1744dc0dbf5cSWarner Losh 1745f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 17461fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1747f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1748f8ab1dd6SWarner Loshprevious releases if your system is older than this. 17491fc1a0dcSWarner Losh 1750e72fd46aSWarner LoshCopyright information: 1751e72fd46aSWarner Losh 17529698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1753e72fd46aSWarner Losh 1754772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1755772730c7SWarner Loshmodification, in full or in part, in any form or format of this 17569698f2c0SWarner Loshdocument are permitted without further permission from the author. 1757e72fd46aSWarner Losh 1758e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1759e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1760e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1761e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1762e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1763e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1764e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1765e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1766e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1767e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1768e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1769e72fd46aSWarner Losh 1770e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1771e72fd46aSWarner Loshauthor a beer. 1772e72fd46aSWarner Losh 177322306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1774772730c7SWarner Loshthis document. 1775772730c7SWarner Losh 177697d92980SPeter Wemm$FreeBSD$ 1777