UPDATING revision 114647
1Updating Information for FreeBSD current users 2 3This file is maintained and copyrighted by M. Warner Losh 4<imp@village.org>. See end of file for further details. For commonly 5done items, please see the COMMON ITEMS: section later in the file. 6 7NOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW: 8 FreeBSD 5.0-CURRENT has many debugging features turned on, in 9 both the kernel and userland. These features attempt to detect 10 incorrect use of system primitives, and encourage loud failure 11 through extra sanity checking and fail stop semantics. They 12 also substantially impact system performance. If you want to 13 do performance measurement, benchmarking, and optimization, 14 you'll want to turn them off. This includes various WITNESS- 15 related kernel options, INVARIANTS, malloc debugging flags 16 in userland, and various verbose features in the kernel. Many 17 developers choose to disable these features on build machines 18 to maximize performance. 19 2020030502: 21 groff has been updated. If you try to do a buildworld and 22 get an infinite loop in troff, update to May 4th or newer. If you 23 have a newer kernel than userland, you may need to set the OSRELDATE 24 to 500110 in your environment before starting a buildworld. 25 2620030501: 27 The old rc system has been removed. Please report any problems 28 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 29 Your personal versions of these files will not be removed, so you can 30 continue to use them. However, you should take great care when updating, 31 especially when using mergemaster, since the compatibility code that 32 utilizes these old scripts has also been removed. 33 3420030423: 35 A bug has been fixed in /dev/devctl which would cause devd 36 to hang on boot, were it not for a workaround in devd. The 37 work around in devd will be removed around 20030507. You 38 have until then to upgrade your kernel before updating 39 userland. In general, you should have a userland and 40 kernel that's in sync with each other. However, given the 41 effects of this bug (hang on boot when starting devd), some 42 allowances are made. 43 4420030329: 45 Alphas with libc from between 20030312 and 20030329 exhibit 46 floating point exceptions (FPEs), most notably in awk(1) 47 while upgrading the system through a buildworld. 48 49 So, to successfully upgrade your Alpha, you must either 50 downgrade your libc.so to a pre-20030312 version, or update 51 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 52 to CFLAGS, then forcibly rebuild and install libc: 53 54 cd /usr/src/lib/libc && \ 55 make cleandir && make obj && \ 56 make -DNOMAN -DNOPROFILE all && \ 57 make -DNOMAN -DNOPROFILE install 58 5920030208: 60 sendmail 8.12.7 has been imported. It has one important 61 change for IPv6 users. The default submit.mc now uses 62 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 63 used to connect to the MTA. Users on IPv6-only machines 64 will need to edit /etc/mail/submit.mc appropriately. 65 6620030128: 67 NODEVFS option has been removed and DEVFS thereby made standard. 68 This makes all references to MAKEDEV obsolete, and they should 69 be removed when convenient. 70 7120030126: 72 The name of the device for the ofw console has changed, sparc64 users 73 must run mergemaster to update their installed /etc/ttys. 74 7520030125: 76 The scheduler framework has grown a second scheduler and consequently 77 you must specify one and only one scheduler in your kernel config. 78 The cvs config files have been updated to use the old scheduler 79 which may be selected via 'options SCHED_4BSD'. If you would like 80 to try the new, much more experimental, scheduler please try 81 'options SCHED_ULE' and contribute to the arch@ discussion. 82 8320030115: 84 A new version of the wi driver has been imported into the tree. 85 One now must have device wlan in the config file for it to operate 86 properly. 87 88 In addition, there have been some changes to how wi devices are 89 configured for point to point links to bring it more in line 90 with the former way of doing things, as well as compatibility 91 with NetBSD. 92 9320021222: 94 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 95 used an incompatible form of ABI for returning structures and unions 96 which FreeBSD's GCC maintainers were not aware of relative to previous 97 versions of FreeBSD. We have gone back to the ABI for now, and any 98 code compiled which is required to interoperate with other code (not 99 built at the same time) returning structs or unions should be 100 rebuilt. 101 10220021216: 103 A name change in /etc/netconfig has been reverted to stay 104 compatible with suns TIRPC and also with NetBSD. You need 105 to run mergemaster after make world. A new libc does still work 106 with an outdated /etc/netconfig for some time, but you'll get 107 a warning. This warning will be removed in 20030301. 108 10920021202: 110 The recent binutils upgrade marks a kernel flag day on 111 sparc64: modules built with the old binutils will not work 112 with new kernels and vice versa. Mismatches will result in 113 panics. Make sure your kernel and modules are in sync. 114 11520021029: 116 The value of IPPROTO_DIVERT has changed. Make sure to keep 117 your kernel, netstat, natd and any third-party DIVERT 118 consumers in sync. 119 12020021024: 121 Old, compatibility slices have been removed in GEOM kernels. 122 This means that you will have to update your /etc/fstab to 123 not use disk devices of the form /dev/ad0a. Instead, you 124 now must specify /dev/ad0s1a, or whatever slice your FreeBSD 125 partition really is on. The old device names have gone 126 away, so if you use them anywhere else, you must also adjust 127 those uses. (This doesn't affect the disks formatted in 128 the ``dangerously-dedicated'' mode.) 129 13020021023: 131 Alphas with kernels from between 20020830 and 20021023 and/or 132 rtld (ld-elf.so.1) older than 20021023 may experience problems 133 with groff while doing a buildworld (kernel: "out of memory", 134 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 135 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 136 137 So, to successfully upgrade your Alpha, you must either 138 upgrade your kernel and rtld first (which might be a bit 139 tricky), or avoid running the bootstrapped groff during the 140 "transitional" buildworld. To avoid running groff during the 141 transitional upgrade run make buildworld with -DNOMAN, 142 -DNO_SHAREDOCS, and -DNO_LPR. 143 14420020831: 145 gcc has been upgraded to 3.2. It is not all binary compatible 146 with earlier versions of gcc for c++ programs. All c++ 147 programs and libraries need to be recompiled. 148 149 Also, if you encounter g++ issues, rm /usr/include/g++/* before 150 doing an installworld to make sure that stale files are removed. 151 15220020827: 153 Our /etc/termcap now has all the entries from the XFree86 xterm 154 almost unchanged. This means xterm now supports color by default. 155 If you used TERM=xterm-color in the past you now should use 156 TERM=xterm. (xterm-color will lead to benign warnings). 157 15820020815: 159 A "bug" in gcc(1) that was hiding warning in system headers was 160 fixed. It's probably time to add -DNO_WERROR to your make line 161 again. 162 16320020729: 164 COPY is being deprecated. The 20010530 change was reverted, as 165 it causes far more pain than was expected, and to always compare 166 before installing, please use INSTALL="install -C" again. The 167 -C option is now silently ignored when used with the -d option. 168 16920020702: 170 Problems with libc_r clients like KDE and GNOME have been resolved. 171 There are still some minor problems with some signals but the 172 system is stable enough for general use again. SMP is less so than UP 173 but each can successfully complete multiple buildworlds. 174 Libkvm needs to be recompiled due to KSE. 175 17620020701: 177 Now would be a bad time to upgrade. Something in or near the 178 KSE commit totally broke programs using libc_r like KDE and 179 GNOME. 180 18120020511: 182 The k5su utility installed as part of Kerberos 5 is no longer 183 installed with the set-user-ID bit set by default. Add 184 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 185 with the set-user-ID bit set. 186 18720020510: 188 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 189 Unfortunately our native GDB (at version 4.18) does not understand 190 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 191 generated debugging information for our native GDB. 192 19320020510: 194 Due to the way CVS works, it may not properly update src/contrib/gcc 195 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 196 and then do a cvs update. 197 19820020421: 199 When exec'ing set[ug]id executables, the kernel now ensures that the 200 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 201 20220020404: 203 New sendmail startup scripts have been installed to make it 204 easier to use alternative MTAs with FreeBSD. Setting the rc.conf 205 variable sendmail_enable to "NO" no longer prevents any sendmail 206 daemons from starting. Instead, either set sendmail_enable to 207 "NONE" or change mta_start_script to a script for starting 208 an alternative MTA. Setting mta_start_script to "" will 209 also prevent any MTA from being started at boot. 210 21120020403: 212 UCONSOLE is no longer a valid kernel option. 213 21420020315: 215 FreeBSD 5.0 DP-1 was basically branched today. 216 21720020225: 218 Warnings are now errors in the kernel. Unless you are a developer, 219 you should add -DNO_WERROR to your make line. 220 22120020217: 222 sendmail 8.12.2 has been imported. The sendmail binary is no 223 longer a set-user-ID root binary and the infrastructure to support 224 command line mail submission has changed. Be sure to run 225 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 226 and /etc/mail) and read /etc/mail/README for more details. 227 228 Due to the import of sendmail 8.12.2, a new user and group are 229 required in order for sendmail to run as a set-group-ID 230 binary. A 'make installworld' will use the new user and group 231 to set the owner and group of /var/spool/clientmqueue and will 232 fail if the new user and group do not exist. The 'smmsp' user 233 and group must be merged from src/etc/group and 234 src/etc/master.passwd before using 'make installworld'. 235 'mergemaster -p' will do this. You may need to install 236 mergemaster before this will work if you are updating from a 237 very old version of current. The updating recipe has changed 238 as of this date. 239 24020020112: 241 The preferred configuration method for PAM is now /etc/pam.d/ 242 rather than /etc/pam.conf. If you have an unmodified 243 pam.conf, just delete it after your next mergemaster run. If 244 you have local modifications, you can use 245 /usr/src/etc/pam.d/convert.pl to incorporate them into your 246 /etc/pam.d. 247 248 Please see the following url for more details: 249http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 25020011229: 251 If anyone here is already using the new rc.conf(5) variable 252 networkfs_types, please note that it has changed 253http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 254 25520011220: 256 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 257 started out its life in the ISDN4BSD project as an offspring 258 from sys/net/if_spppsubr.c, which eventually got a life of its 259 own. All the accumulated features and bugfixes of the i4b 260 version have now been merged back into the base system's 261 version now. The only user-visible change resulting from this 262 is that i4b's sppp(4) interfaces are to be managed with 263 spppcontrol(8) again, since ispppcontrol(8) has been retired 264 as well. (There has never been rc file support for 265 ispppcontrol in -current, but only in -stable. That will be 266 reverted by the time the changes are MFCed.) 267 26820011215: 269 The fdc(4) driver has been updated and now automatically 270 recognizes media in `standard' formats (like 1440 KB and 271 720 KB for a 3.5" high-density drive) when accessing the 272 default device node (e. g. /dev/fd0). The old variety of 273 floppy device nodes /dev/fd*.* is no longer present by 274 default, devices can be created (in DEVFS) on demand. They 275 will need to be customized then for `odd' densities using 276 fdcontrol(8). 277 27820011209: 279 The bugs in procfs' debugging support code have been fixed, 280 and truss(1) now works again. 281 28220011207: 283 Daily security checks have been split out to use the periodic(8) 284 scripts. Some change in configuration may be necessary. Please 285 see 286http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 287 for details. 288 28920011204: 290 sos added VCD/SVCD support to ata driver and that needs the 291 kernel and burncd to be in sync. 292 29320011203: 294 The procfs pseudo-filesystem has now been converted to use the 295 pseudofs framework. If you have 'options PROCFS' in your 296 kernel config, you'll need to add 'options PSEUDOFS' if it's 297 not there already. 298 299 This change temporarily breaks truss(1); use ktrace(1) instead 300 until the issue has been resolved. 301 30220011202: 303 A security hole in OpenSSH involving `UseLogin yes' has been 304 patched. 305 30620011126: 307 You need to remove /usr/obj/.../usr.bin/tip before rebuilding 308 after this date. You need to do this only once. 309 31020011103: 311 Most of the awk issues have been resolved. Some rough 312 edges may be left, but for the most part things should be 313 back to "normal." For CURRENT's usual definition of "normal." 314 31520011030: 316 Awk has been upgraded to the one true awk from bell labs. Expect 317 choppy waves in the upgrade process. 318 31920011030: 320 The asr driver problem has been resolved. 321 32220011027: 323 Due to changes in other parts of the system, the asr driver 324 now causes the system to panic on boot. Do not use it pending 325 correction. Comment it out of any kernel config file that you 326 try to use from this date forward. 327 32820011025: 329 When crossbuilding, use TARGET=xxx where you used to use 330 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 331 unless you are changing both of them. To cross build pc98 on 332 an alpha, for example, you need to set TARGET=pc98 and 333 TARGET_ARCH=i386. 334 33520011001: 336 The kernel interface that burncd depends on has changed. 337 You must recompile both the kernel and userland applications 338 at the same time. 339 34020010929: 341 When crossbuilding, please set TARGET_ARCH rather than 342 MACHINE_ARCH to indicate the target. In the future, one will 343 set TARGET_MACHINE where you set MACHINE now. At the moment, 344 setting MACHINE alone for same MACHINE_ARCH machines works 345 (eg, you can build pc98 on an i386 machine and vice versa). 346 34720010927: 348 Some weird problems result from using ACPI on some machines. 349 To disable ACPI you can add 350 hint.acpi.0.disabled="1" 351 to /boot/loader.conf (or by putting set X=Y at the boot 352 loader "ok" prompt). 353 354 Alternatively, you can remove it from /boot/kernel/acpi.ko 355 or use the MODULES_OVERRIDE function in your kernel config 356 file and not list acpi in that list. 357 35820010924: 359 The buildworld has been fixed. You may need to install 360 the 4.x compatibility libraries for some old binaries 361 to work. Add COMPAT4X=true to your /etc/make.conf to 362 get them installed on every installworld, or execute the 363 following to get them installed only once: 364 cd src/lib/compat/compat4x.<arch> 365 make all install 366 You will see ``__stdoutp undefined'' until you do this. 367 36820010919: 369 There's a bug in the world build process. The cross-tools 370 are build with the NEW headers, but the OLD libc.a. This 371 leads to all kinds of problems with the new libc. A temporary 372 workaround is to add 373 CFLAGS="-O -pipe -D_OLD_STDIO" 374 before building world when upgrading from 4.x to current. This 375 can be removed afterwards. 376 377 A proper fix to the buildworld target is needed. 378 37920010918: 380 Peter has committed his new kthread nfs client/server code. 381 NFS may be unstable after this date. 382 38320010912: 384 KSE has hit the tree. Lots of things are now different in 385 the kernel. While a few problems were introduced in the 386 initial commit, most of the major ones have been found and 387 corrected. 388 38920010901: 390 In OLDCARD, CardBus bridges appear to be stable. The work 391 arounds described in the 20010604 entry are now no longer 392 necessary and will be ignored. Most insert/remove problems 393 have been rectified around this date. 394 39520010823: 396 named now runs as user bind and group bind rather than as 397 root. If named_enable is set to YES in /etc/rc.conf, ensure 398 that user bind is available in /etc/passwd (using vipw(8)) 399 and that group bind is available in /etc/group. Also make 400 sure that user or group bind has read (and not write) 401 permission for your name server configuration and that it 402 has read and write permission for your slave zone files and 403 directory. 404 405 If you wish to continue to run named as root (a less secure 406 alternative), add a line to /etc/rc.conf saying 407 408 named_flags= 409 41020010709: 411 The PAM libraries have had an API upgrade that is beyond 412 the ability of the shared library major number to handle. 413 It is manifested by PAM-using ports dumping core. The 414 solution is to rebuild those ports. 415 41620010628: 417 The kernel compile module has moved from src/sys/compile/FOO 418 to src/sys/${MACHINE}/compile/FOO. 419 42020010625: 421 The pccard modem issue from 20010613 has been corrected. 422 OLDCARD support is still a little weak in -current. slot 1 is 423 known not to work on some TI based cardbus bridges. Some 424 cardbus bridges do not properly detect insert/removal events. 425 IRQ configuration needs more safety belts. 426 42720010617: 428 Softupdates problems have been corrected. 429 43020010614: 431 Peter ripped out the linkerset support. You must, as always, 432 rerun config after you cvsup if you are using the traditional 433 kernel building methods. 434 43520010613: 436 pccard modems may not work with current after 20010604 date. Some 437 do, others result in panics. *MAKE*SURE* that you update your 438 config and /etc/rc.conf ala the 20010604 entry, or you will have 439 problems (this issue will be fixed, it just hasn't been yet). 440 44120010613: 442 SOFTUPDATES seem to be broken since the middle of May or so. Do not 443 use them in current. You can disable softupdates on all mounted 444 partitions, or remove SOFTUPDATES the kernel config file. 445 44620010612: 447 After Peter's commits to the hints code, people have been noticing 448 that certain devices are attached (or try to) twice. This is due 449 to having both static hints as well as a /boot/device.hints. To 450 work around this issue, please use only one or the other mechanism 451 until this bug is fixed. 452 453 Please note that a feature of config is that if you have config 454 file FOO and FOO.hints, it automatically adds FOO.hints to the 455 hints.c file, whether you want it to or not. 456 45720010610: 458 Locale names have changed to match other systems better. 459 46020010604: 461 pccard support for pci cards has been committed. You must change 462 your /etc/pccard.conf irq lines. It must match the irq used by 463 pcic device. Interrupt storms may result if you fail to do this. 464 Interrupt storms look a lot like a hang. 465 466 You must also install a new pccardd, otherwise you will get an 467 interrupt storm at card reset time (just after it tells you what 468 it is). 469 470 pccardd_flags="-I" is necessary for the time being. It tells pccardd 471 not to ask the kernel if the interrupt is really free or not before 472 using it. You can either change the /etc/pccard.conf irq lines to 473 match pcic, or add "-i X" to the pccardd_flags. 474 47520010530: 476 INSTALL=install -C is being deprecated. If you want to do this, 477 use COPY=-C instead. The former method will be supported for only 478 a limited time. If you see 479 480install: warning: the -d and -C options may not be specified together 481 482 in your makeworld, then you need to migrate towards using 483 COPY=-C. 484 48520010525: 486 It appears that vm is now stable enough to use again. However, 487 there may be other problems, so caution is still urged. alpha 488 definitely is in bad shape. 489 49020010521: 491 Minor repo damage has happened. This may cause problems 492 with cvsup of ports. If you get errors, please see 493 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 494 at the bottom for details on a workaround. The error message 495 is 496Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 497 49820010520: 499 Vm and/or swapping are busted on -current. Please be patient. 500 50120010519: 502 pccard has had much reorganizational work done to it over 503 the past few days. Everything should still work, but if 504 not, please contact imp@freebsd.org. 505 50620010517: 507 ata ioctl changed. Make sure to recompile both kernel and 508 userland at the same time. 509 51020010517: 511 New ncurses imported. 512 51320010512: 514 DEVFS is now opt out, not opt in. Barring major problems, this 515 will be the only way to go starting July 1. 516 51720010504: 518 OpenSSH has been updated to 2.9. Some defaults are different, 519 including RhostsRSAAuthentication, which changes from yes to no. 520 52120010502: 522 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 523 52420010501: 525 Building perl was broken at 02:25:25 PDT. 526 52720010430: 528 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 529 go back in the water. 530 53120010429: 532 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 533 this date, but before the correction date. 534 53520010423: 536 old fsck and new kernel interactions appear to have been fixed. 537 53820010411: 539 fsck and the kernel were changed to handle some optimizations 540 to directory layout. This breaks backward compatibility. 541 Update only if you understand that you must not use the old 542 fsck with the new kernel ever. 543 54420010330: 545 fsck has changed the meaning of the pass column in /etc/fstab. 546 Please see the cvs commit to fsck.8 or the fsck.8 man page for 547 details. It is unclear if changes to /etc/fstab are necessary. 548 54920010319: 550 portmap had changed name to rpcbind for maximum POLA in your 551 current world. /etc/hosts.{allow,deny} needs changes. nfs and 552 other rpc based programs that rely on portmapper will not work 553 without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 554 55520010315: 556 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 557 and ATA_ENABLE_TAGS are no longer kernel options. They have 558 been replaced by tunables. See ata.4 for details. 559 56020010312: 561 The fxp driver was converted to use miibus. If you compile 562 fxp into your kernel statically, you will need to add miibus. 563 56420010312: 565 The wi device now defaults to BSS (infrastructure) mode 566 instead of ad-hoc. 567 56820010310: 569 /dev/urandom should be a symbolic link to /dev/random now. 570 Users of current not using DEVFS need to run MAKEDEV std. 571 ssh might not work if you don't. 572 57320010303: 574 The ed driver has been updated. It now allows mii attachments, 575 which means that you must include the miibus in your kernel if 576 you use the ed driver. 577 57820010220: 579 The problems with libc have been corrected. It is now mostly 580 safe to go back into the water. 581 58220010211: 583 The size of FILE was changed. This breaks upgrading. If 584 you must upgrade, be prepared for pain. It also breaks almost 585 all binaries that you've compiled on -current. You are warned 586 that before upgrading would be a good time to do a level 0 587 dump of your system. No, really, I mean it this time. 588 589 To get to the new system, you'll need to use the following 590 workaround. Hopefully this can be sorted out so that we 591 don't have to move this to the updating section. 592 593 To get around the installworld problem, do: 594 # cd /usr/src/usr.bin/sed 595 # make install 596 # cd /usr/src 597 # make installworld 598 If that doesn't work, then try: 599 # make -k installworld 600 # make installworld 601 60220010207: 603 DEVFS is now the default. If you use vinum, make sure that you 604 do not include devfs in your kernel as problems result. 605 60620010205: 607 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 608 Remove them from your config. 609 61020010122: 611 ****************************** WARNING ****************************** 612 buildkernel has been changed slightly 613 ****************************** WARNING ****************************** 614 KERNCONF replaces the variable KERNEL for buildkernel. You 615 should update your scripts and make.conf accordingly. 616 61720010119: 618 config has changed to allow DEV_FOO as a replacement for NFOO. 619 This requires a new config to build correctly. 620 62120010116: 622 The kernel option I386_CPU is now mutually exclusive with the 623 other cpu types. If you have an i386 system, be sure that it 624 only had this line. Remove it for all other configurations. 625 62620010110: 627 Changes to the kernel require it and burncd be in sync. 628 62920010102: 630 Everyone who has hw.sndunit set to something in 631 /etc/sysctl.conf, it is now hw.snd.unit. 632 63320010101: 634 ex and vi were broken by some changes to sys/queue.h. If you 635 have a bad vi, you will see make buildworld fail with a core 636 dump while building termcap. You can work around this problem 637 by adding -k to your make buildworld. This will cause the 638 build to complete and install a new vi. Once that's done, you 639 can rebuild again without the -k to pick up anything that 640 might have been ignored by the -k option. 641 642 Others have suggested that you can just rebuild libc if your 643 vi/ex is dynamically linked, but I've not received any reports 644 of this working. 645 64620001228: 647 There have been some changes to libcrypt in -current. The 648 libscrypt/libdescrypt symlink silliness is gone and the installed 649 libcrypt is fully functional. Be aware of this. 650 65120001218: 652 Linksys Fast Ethernet PCCARD cards supported by the ed driver 653 now require the addition of flag 0x80000 to their config line 654 in pccard.conf(5). This flag is not optional. These Linksys 655 cards will not be recognized without it. 656 65720001205: 658 Important new FreeBSD-version stuff: PAM support has been worked 659 in, partially from the "Unix" OpenSSH version. This requires 660 adding the following in pam.conf: 661 662 sshd auth sufficient pam_skey.so 663 sshd auth required pam_unix.so try_first_pass 664 sshd session required pam_permit.so 665 66620001031: 667 cvs updated to 1.11. 668 66920001020: 670 The random device needs more entropy, so you need to make sure 671 that you've run mergemaster to get a /etc/rc which will seed 672 /dev/random. If you don't and the system hangs after ldconfig, 673 then banging on the keyboard randomly until it unhangs is one 674 workaround. 675 67620001010: 677 ****************************** WARNING ****************************** 678 Sendmail has been updated. 679 ****************************** WARNING ****************************** 680 o mail.local(8) is no longer installed as a set-user-id binary. 681 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 682 is set. 683 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 684 commands. 685 o Now using sendmail's version of vacation(1). 686 o The sendmail cf building tools (contrib/sendmail/cf) are installed 687 in /usr/share/sendmail/cf. 688 o sendmail.cw changed to local-host-names 689 690 More details can be found at 691 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 692 69320001009: 694 The ports tree's new layout is in place. Be sure to update 695 your entire ports tree, or you will have problems. 696 69720001006: 698 The perl build procedure no longer installs miniperl, nor uses 699 the installed miniperl. It is recommended that you delete 700 /usr/bin/miniperl. 701 70220001005: 703 This weekend the ports tree will be updated to a new layout. 704 It will be in an inconsistent state until noted in the UPDATING 705 file, or with asami-san's message to the relevant mailing 706 lists. With this new layout, you'll need to update the whole 707 tree for anything to work. 708 70920000928: 710 There was a change in the passwd format. Need more information. 711 71220000916: 713 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 714 place. Please update boot loader (not the boot blocks) at the 715 same time as your kernel. 716 71720000914: 718 The new pmtimer device is necessary for laptops. Failure to 719 include the device will cause suspended laptops losing time 720 when they resume. Include 721 device pmtimer 722 in your config file and 723 hint.pmtimer.0.at="isa" 724 to your /boot/device.hints file. 725 72620000911: 727 The random device has been turned into a (pseudo-)device, 728 rather than an option. The supplied kernel config files have 729 been updated. You will need to do something similar in your 730 own kernel config file. 731 Remove: 732 options RANDOMDEV 733 Add: 734 device random 735 If you prefer to load the loadable module, you need to do 736 nothing. 737 73820000909: 739 The random device module has been renamed from randomdev.ko to 740 random.ko. You will need to edit your /boot/loader.conf to 741 reflect this if you load this module at boot time. 742 The line should read: 743 random_load="YES" 744 74520000907: 746 The SMPNG commit has happened. It should work, but if it 747 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 748 to be a variety of minor issues. Please see 20000905 to make 749 sure you don't have model loading problems which might at 750 first blush appear related to SMP. 751 75220000906: 753 nsswitch has been imported from NetBSD. Among other things, 754 this means that /etc/host.conf is no longer used. See 755 nsswitch.conf(5) instead. Note that at boot time rc.network 756 will attempt to produce a new nsswitch.conf file for you if you 757 don't have one, and you have host.conf. 758 75920000905: 760 The ucred structure changed size. This breaks the interface 761 that mountd uses. Trying to use an older mountd with a newer 762 kernel guarantees a panic. This means that you need to use 763 kernels newer than today only with matching mountd, but you 764 needed to do that anyway with the boot loader changes. 765 76620000905: 767 The boot loader has been updated. The new default kernel is 768 now /boot/kernel/kernel.ko. The new default module location 769 is /boot/kernel. 770 771 You *MUST* upgrade your boot loader and kernel at the same time. 772 The easiest way to do this is to do the buildworld/buildkernel/ 773 installkernel/installworld dance. 774 775 Furthermore, you are urged to delete your old /modules directory 776 before booting the new kernel, since kldload will find stale 777 modules in that directory instead of finding them in the correct 778 path, /boot/kernel. The most common complaint that this cures 779 is that the linux module crashes your machine after the update. 780 781 if [ ! -d /boot/kernel.old ]; then 782 mv /modules.old /boot/kernel.old 783 chflags noschg /kernel.old 784 mv /kernel.old /boot/kernel.old/kernel.ko 785 chflags schg /boot/kernel.old/kernel.ko 786 fi 787 78820000904: 789 A new issue with the sendmail upgrade has come to light. 790 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 791 incorrectly install the default aliases in /etc/mail rather than 792 move the old one from /etc. So you'll need to manually move the 793 file, create a symbolic link, remove the old /etc/aliases.db and 794 run newaliases. For safety sake, you should stop sendmail 795 while doing this and run the upgrade when locally sourced email 796 is not likely to be generated. 797 79820000825: 799 /boot/device.hints is now required for installkernel to 800 succeed. You should copy GENERIC.hints for your architecture 801 into /boot/device.hints. If and only if you compile hints 802 into your kernel, then this file may be empty. Please note, 803 if you have an empty or missing /boot/device.hints file and 804 you neglected to compile hints into your kernel, no boot 805 messages will appear after the boot loader tries to start the 806 kernel. 807 80820000821: 809 If you do NOT have ``options RANDOMDEV'' in your kernel and 810 you DO want the random device then add randomdev_load="YES" to 811 /boot/loader.conf. 812 81320000812: 814 suidperl is now always built and installed on the system, but 815 with permissions of 511. If you have applications that use 816 this program, you are now required to add ENABLE_SUIDPERL=true 817 to /etc/make.conf. If you forget to do this, 818 chmod 4511 /usr/bin/suidperl 819 will fix this until the next build. 820 82120000812: 822 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 823 visible changes that may immediately affect your configuration 824 include: 825 - New default file locations from src/contrib/sendmail/cf/README 826 - newaliases limited to root and trusted users 827 - MSA port (587) turned on by default 828 - New queue file naming system so can't go from 8.11 -> 8.9 829 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 830 - FEATURE(`nullclient') is more full featured 831 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 832 - mail.local FreeBSD-only -b option changed to -B 833 - See src/contrib/sendmail/RELEASE_NOTES for more info 834 83520000810: 836 suidperl (aka sperl) is no longer build by default. You must 837 specifically define BUILD_SUIDPERL to "true" for it to be build. 838 Furthermore, we recommend that you remove /usr/bin/sperl* and 839 /usr/bin/suidperl files from your system unless you have a 840 specific use for it. 841 84220000729: 843 Networking defaults have been tightened. Anybody upgrading 844 /etc/defaults/rc.conf needs to add the following lines to 845 /etc/rc.conf if they want to have the same setup 846 afterwards (unless the variables already are set, of course): 847 # Enable network daemons for user convenience. 848 inetd_enable="YES" 849 portmap_enable="YES" 850 sendmail_enable="YES" 851 85220000728: 853 If you have null_load="YES" in your /boot/loader.conf, you 854 will need to change that to nullfs_load="YES". 855 85620000728: 857 The "installkernel" target has changed slightly. Now even if 858 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 859 it will install the MYKERNEL file (built with the buildkernel 860 target) as /kernel rather than /MYKERNEL. Those who have 861 updated their /boot/loader.conf files to point to /MYKERNEL 862 should remove that entry or perform manual rename of /kernel 863 to /MYKERNEL. 864 86520000711: 866 If you use CVSUP or CTM to get CVS trees, AND you used to get 867 the old crypto files from internat.freebsd.org AND you check 868 out files from the CVS tree with the cvs command, please read 869 http://people.freebsd.org/~imp/internat.txt 870 for details on potential problems that you might have and how 871 to get around them. 872 873 If you are merely a mirror, or don't answer yes to each of the 874 clauses above, you needn't worry. 875 87620000711: 877 /etc/security has been updated to print the inode number of 878 setuid programs that have changed. You will see a large spike 879 in the number of changed programs the first time when you run 880 mergemaster to get a new /etc/security. 881 88220000710: 883 /dev/random now has good entropy collection (from the keyboard 884 and sysmouse drivers). Please ensure that either `options 885 RANDOMDEV' is present in your kernel config file or that 886 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 887 not have the /dev/random driver, OpenSSL (and consequently 888 lots of crypto tools (like SSH)) will fail with strange 889 errors. (see below, 20000624). 890 891 FreeBSD-current is safe again to run Crypto. 892 89320000709: 894 phk made the malloc default options AJ. This may slow things 895 down and uncover other latent bugs in the code. If you need to 896 run at full speed, you can disable this by doing the following: 897 ln -s aj /etc/malloc.conf 898 89920000706: 900 libftpio's version was accidentally bumped a few days ago. This 901 has been corrected. You may need to remove /usr/lib/libftpio.so.6 902 before doing your next buildworld/installworld pair. It certainly 903 won't hurt to remove it before the update procedure. It will 904 break fetch until a new one is built, but ftp can be used in the 905 interim if needed. 906 90720000705: 908 The crypto packages have changed for the cvsup. This has been done 909 in a backward compatible way, but the old packages will go away at 910 some point in the future. Look at /usr/share/examples/cvsup for 911 details. 912 91320000704: 914 With the new sys/modules/sound/drivers/*, you will need to 915 set SYSDIR until you do an installworld after July 7th. 916 91720000704: 918 rc.shutdown and rc will now call the rc.d scripts with start 919 or stop. This may cause some harmless warnings from older 920 rc.d scripts that haven't been updated. 921 92220000630: 923 The libfetch based version of fetch has gone into the tree. 924 Minor problems may result on some of the less popular sites, 925 which should be reported to des@freebsd.org. 926 92720000625: 928 From approximately this date forward, one must have the crypto 929 system installed in order to build the system and kernel. 930 While not technically strictly true, one should treat it as 931 required and grab the crypto bits. If you are grabbing CVS 932 trees, src-all and cvs-crypto should be treated as if they 933 were required. You should check with the latest collections 934 to make sure that these haven't changed. 935 93620000624: 937 Mark Murray just committed the first parts of a cleanup of 938 /dev/zero, et al. This is also cleaning up /dev/random. 939 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 940 -CURRENT FROM THIS POINT to 2000710 for cryptographic services 941 until Mark can merge in the fixes to this work in progress. 942 openssh and openssl should not be used to generate keys from this 943 date to the completion of the work. 944 945 If you must operate at this reduced level of security, add ' 946 options RANDOMDEV' to your kernel or modload the randomdev 947 module. You may also need to copy a new MAKEDEV to /dev and 948 recreate the random and urandom devices. 949 95020000622: 951 The license on the softupdates is now a standard 2 clause 952 BSD license. You may need to remove your symbolic links 953 that used to be required when updating. 954 95520000621: 956 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 957 the config file update procedure. 958 http://people.freebsd.org/~imp/config-upd.html 959 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 960 isn't buildable. However, you can generate a LINT file: 961 cd /sys/<ARCH>/conf && make LINT 962 96320000620: 964 Binutils 2.10 have hit the tree, or will shortly. As soon 965 as they do, the problem noted in 20000522 will be resolved and 966 that workaround will no longer be required. 967 96820000615: 969 phk removed the compatibility creation of wd devices in the 970 ad driver. If you haven't done so already, you must update 971 your fstab, etc to use the ad devices instead of the wd 972 devices. 973 974 In addition, you'll need to update your boot blocks to a 975 more modern version, if you haven't already done so. Modern 976 here means 4.0 release or newer (although older releases 977 may work). 978 97920000612: 980 Peter took an axe to config(8). Be sure that you read his mail 981 on the topic before even thinking about updating. You will 982 need to create a /boot/device.hints or add a hints directive 983 to your config file to compile them in statically. The format 984 of the config file has changed as well. Please see GENERIC or 985 NEWCARD for examples of the new format. 986 987 Indirectly, this also breaks USERCONFIG. Unless a newer entry 988 says that it has been fixed, assume that must use the hints mechanism 989 in the loader if you need to use a machine with very old ISA cards 990 in it. 991 99220000522: 993 A new set of binutils went into the tree today. Anybody 994 building a kernel after this point is advised that they need 995 to rebuild their binutils (or better yet do a 996 buildworld/installworld) before building a new kernel. 997 998 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 999 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1000 is recommended that you don't set this option until the problem 1001 is resolved. 1002 100320000513: 1004 The ethernet drivers were all updated to clean up the BPF handling. 1005 100620000510: 1007 The problems with boot blocks on the alphas have been corrected. 1008 This will require some care in updating alphas. A new libstand 1009 is requires for the boot blocks to build properly. 1010 101120000503: 1012 Recompile all kld modules. Proper version dependency info 1013 is now available. 1014 101520000502: 1016 Modules have been disconnected from the buildworld tree and 1017 connected to the kernel building instead. 1018 101920000427: 1020 You may need to build gperf 1021 cd /usr/src/gnu/usr.bin/gperf && make depend all install 1022 when upgrading from 4.0 -> current. The build system now uses 1023 an option only in -current. 1024 102520000417: 1026 The method that we brand ELF binaries has changed to be more 1027 acceptable to the binutils maintainers. You will need to 1028 rebrand your ELF binaries that aren't native. One problem 1029 binary is the Linux ldconfig. After your make world, but 1030 before you reboot, you'll need to issue: 1031 brandelf -t Linux /compat/linux/sbin/ldconfig 1032 if you have Linux compatibility enabled on your machine. 1033 103420000320: 1035 If you have really bad/marginal IDE drives, you may find they 1036 don't work well. Use pio mode instead. The easiest way to 1037 cope if you have a problem combination is to add: 1038 /sbin/sysctl hw.ata.ata_dma=0 1039 to the start of /etc/rc.conf. 1040 104120000319: 1042 The ISA and PCI compatibility shims have been connected to the 1043 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1044 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1045 include the appropriate option in your kernel config. Drivers 1046 using the shims should be updated or they won't ship with 1047 5.0-RELEASE, targeted for 2001. 1048 104920000318: 1050 We've entered the traditional post release dumping party. 1051 Large kernel changes are being committed and are in the 1052 works. It is important to keep the systems' klds and kernel 1053 in sync as kernel interfaces and structures are changing. 1054 Before reporting kernel panics, make sure that all modules 1055 that you are loading are up to date. 1056 105720000315: 1058 If you are upgrading from an older version of FreeBSD, you 1059 need to update your boot blocks as well. 'disklabel -B ad0' 1060 will do the trick. This isn't critical until you remove your 1061 wd device entries in /dev, at which point your system will not 1062 boot. 1063 106420000315: 1065 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 1066 to upgrade to 4.0 from 3.x. 1067 1068COMMON ITEMS: 1069 1070 General Notes 1071 ------------- 1072 Avoid using make -j when upgrading. From time to time in the 1073 past there have been problems using -j with buildworld and/or 1074 installworld. This is especially true when upgrading between 1075 "distant" versions (eg one that cross a major release boundary 1076 or several minor releases, or when several months have passed 1077 on the -current branch). 1078 1079 Sometimes, obscure build problems are the result of environment 1080 poisoning. This can happen because the make utility reads its 1081 environment when searching for values for global variables. 1082 To run your build attempts in an "environmental clean room", 1083 prefix all make commands with 'env -i '. See the env(1) manual 1084 page for more details. 1085 1086 To build a kernel 1087 ----------------- 1088 If you are updating from a prior version of FreeBSD (even one just 1089 a few days old), you should follow this procedure. With a 1090 /usr/obj tree with a fresh buildworld, 1091 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1092 make installkernel KERNCONF=YOUR_KERNEL_HERE 1093 1094 To just build a kernel when you know that it won't mess you up 1095 -------------------------------------------------------------- 1096 cd src/sys/{i386,alpha}/conf 1097 config KERNEL_NAME_HERE 1098 cd ../../compile/KERNEL_NAME_HERE 1099 make depend 1100 make 1101 make install 1102 1103 If this fails, go to the "To build a kernel" section. 1104 1105 To rebuild everything and install it on the current system. 1106 ----------------------------------------------------------- 1107 # Note: sometimes if you are running current you gotta do more than 1108 # is listed here if you are upgrading from a really old current. 1109 1110 <make sure you have good level 0 dumps> 1111 <maybe fix /etc/fstab> [7] 1112 make buildworld 1113 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1114 make installkernel KERNCONF=YOUR_KERNEL_HERE 1115 [1] 1116 <reboot in single user> [3] 1117 mergemaster -p [5] 1118 make installworld 1119 mergemaster [4] 1120 <reboot> 1121 1122 1123 To cross-install current onto a separate partition 1124 -------------------------------------------------- 1125 # In this approach we use a separate partition to hold 1126 # current's root, 'usr', and 'var' directories. A partition 1127 # holding "/", "/usr" and "/var" should be about 2GB in 1128 # size. 1129 1130 <make sure you have good level 0 dumps> 1131 <boot into -stable> 1132 make buildworld 1133 <maybe newfs current's root partition> 1134 <mount current's root partition on directory ${CURRENT_ROOT}> 1135 make installworld DESTDIR=${CURRENT_ROOT} 1136 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1137 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1138 ${CURRENT_ROOT}/boot/device.hints # as needed 1139 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1140 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1141 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1142 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1143 <reboot into current> 1144 <do a "native" rebuild/install as described in the previous section> 1145 <maybe install compatibility libraries from /usr/src/lib/compat> 1146 <reboot> 1147 1148 1149 To upgrade in-place from 4.x-stable to current 1150 ---------------------------------------------- 1151 # 5.x uses more space than 4.x. Also, the location of kernel 1152 # modules has changed. If you are installing 5.0 onto a 4.x 1153 # system, you'll need about 30MB of free disk space on your / 1154 # partition. If you have less than this, you may encounter difficult 1155 # to back out of problems with this procedure. If /tmp is on 1156 # the / partition, you may want to completely remove all its content 1157 # before upgrading, as this can be a common source of shortage of 1158 # space on /. 1159 1160 <make sure you have good level 0 dumps> 1161 <maybe fix /etc/fstab> [7] 1162 make buildworld [9] 1163 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1164 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1165 make installkernel KERNCONF=YOUR_KERNEL_HERE 1166 cd src/sys/boot ; make install [6] 1167 [1] 1168 <reboot in single user> [3] 1169 mergemaster -p [5] 1170 rm -rf /usr/include/g++ 1171 make installworld 1172 mergemaster [4] 1173 <reboot> 1174 1175 Make sure that you've read the UPDATING file to understand the 1176 tweaks to various things you need. At this point in the life 1177 cycle of current, things change often and you are on your own 1178 to cope. The defaults can also change, so please read ALL of 1179 the UPDATING entries. 1180 1181 Also, if you are tracking -current, you must be subscribed to 1182 freebsd-current@freebsd.org. Make sure that before you update 1183 your sources that you have read and understood all the recent 1184 messages there. If in doubt, please track -stable which has 1185 much fewer pitfalls. 1186 1187 [1] If you have third party modules, such as vmware, you 1188 should disable them at this point so they don't crash your 1189 system on reboot. 1190 1191 [2] If you have legacy ISA devices, you may need to create 1192 your own device.hints to reflect your unique hardware 1193 configuration. 1194 1195 [3] From the bootblocks, boot -s, and then do 1196 fsck -p 1197 mount -u / 1198 mount -a 1199 cd /usr/src 1200 adjkerntz -i # if CMOS is wall time 1201 Also, when doing a major release upgrade, it is required that 1202 you boot into single user mode to do the installworld. 1203 For the 4.x -> 5.0 upgrade, you will also see many messages about 1204 needing to recompile your userland. These are harmless and can 1205 be ignored while you proceed to the next step. 1206 1207 [4] Note: This step is non-optional. Failure to do this step 1208 can result in a significant reduction in the functionality of the 1209 system. Attempting to do it by hand is not recommended and those 1210 that pursue this avenue should read this file carefully, as well 1211 as the archives of freebsd-current and freebsd-hackers mailing lists 1212 for potential gotchas. 1213 1214 [5] Usually this step is a noop. However, from time to time 1215 you may need to do this if you get unknown user in the following 1216 step. It never hurts to do it all the time. You may need to 1217 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1218 install) after the buildworld before this step if you last updated 1219 from current before 20020224 or from -stable before 20020408. 1220 1221 [6] 4.x boot loader can be used to boot a 5.x system, however 1222 it is difficult to do that at best. If you wish to try, then 1223 you should interrupt the boot and at the ok prompt type: 1224 ok unload 1225 ok boot /boot/kernel/kernel 1226 If this fails to work, you must install a new boot loader as 1227 described here. 1228 1229 [7] Before you upgrade, please make sure that you are not using 1230 compatibility slices. These are device names of the form, on i386 1231 and other architectures that use MBR slicing, /dev/ad0a without the 1232 actual slice name. Chances are excellent that these will break. 1233 You generally must update these entries to use the post FreeBSD 1234 2.x form of /dev/ad0s1a. 1235 1236 [8] In order to have a kernel that can run the 4.x binaries 1237 needed to do an installworld, you must include the COMPAT_FREEBSD4 1238 option in your kernel. Failure to do so may leave you with a system 1239 that is hard to boot to recover. 1240 1241 [9] When checking out sources, you must include the -P flag to have 1242 cvs prune empty directories. 1243FORMAT: 1244 1245This file contains a list, in reverse chronological order, of major 1246breakages in tracking -current. Not all things will be listed here, 1247and it only starts on March 15, 2000. Updating files can found in 1248previous releases if your system is older than this. 1249 1250Copyright information: 1251 1252Copyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1253 1254Redistribution, publication, translation and use, with or without 1255modification, in full or in part, in any form or format of this 1256document are permitted without further permission from the author. 1257 1258THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1259IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1260WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1261DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1262INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1263(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1264SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1265HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1266STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1267IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1268POSSIBILITY OF SUCH DAMAGE. 1269 1270If you find this document useful, and you want to, you may buy the 1271author a beer. 1272 1273Contact Warner Losh if you have any questions about your use of 1274this document. 1275 1276$FreeBSD: head/UPDATING 114647 2003-05-04 06:26:30Z imp $ 1277