157199806SWarner LoshUpdating Information for FreeBSD current users 253dfde79SWarner Losh 3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh 4e72fd46aSWarner Losh<imp@village.org>. Please send new entries directly to him. See end 5e72fd46aSWarner Loshof file for further details. For commonly done items, please see the 6e72fd46aSWarner LoshCOMMON ITEMS: section later in the file. 7e72fd46aSWarner Losh 87b9786edSMark Murray20010709: 97b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 107b9786edSMark Murray the ability of the shared library major number to handle. 117b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 127b9786edSMark Murray solution is to rebuild those ports. 137b9786edSMark Murray 141d28950eSWarner Losh20010628: 151d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 161d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 171d28950eSWarner Losh 18e72fd46aSWarner Losh20010625: 19e72fd46aSWarner Losh The pccard modem issue has been corrected. OLDCARD support is 20e72fd46aSWarner Losh still a little weak in -current. slot 1 is known not to work 21e72fd46aSWarner Losh on some TI based cardbus bridges. Some cardbus bridges do not 22e72fd46aSWarner Losh properly detect insert/removal events. IRQ configuration needs 23e72fd46aSWarner Losh more safety belts. 2416de1a07SWarner Losh 250d415dffSWarner Losh20010617: 26e72fd46aSWarner Losh Softupdates problems have been corrected. 270d415dffSWarner Losh 280d415dffSWarner Losh20010614: 290d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 300d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 310d415dffSWarner Losh kernel building methods. 320d415dffSWarner Losh 338b9959adSWarner Losh20010613: 348b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 358b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 36e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 37e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 388b9959adSWarner Losh 39e72fd46aSWarner Losh20010613: 408b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 41e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 42e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 438b9959adSWarner Losh 440d415dffSWarner Losh20010612: 450d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 460d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 470d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 480d415dffSWarner Losh work around this issue, please use only one or the other mechanism 490d415dffSWarner Losh until this bug is fixed. 500d415dffSWarner Losh 51e72fd46aSWarner Losh Please note that a feature of config is that if you have config 52e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 53e72fd46aSWarner Losh hints.c file, wheather you want it to or not. 54e72fd46aSWarner Losh 550d415dffSWarner Losh20010610: 560d415dffSWarner Losh Locale names have changed to match other systems better. 570d415dffSWarner Losh 586ccdb5e4SWarner Losh20010604: 596ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 606ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 616ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 623590182eSWarner Losh Interrupt storms look a lot like a hang. 633590182eSWarner Losh 643590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 653590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 663590182eSWarner Losh it is). 673590182eSWarner Losh 683590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 693590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 703590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 713590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 726ccdb5e4SWarner Losh 730bc62786SWarner Losh20010530: 740bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 750bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 760bc62786SWarner Losh a limited time. If you see 770bc62786SWarner Losh 780bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 790bc62786SWarner Losh 800bc62786SWarner Losh in your makeworld, then you need to migrate towards using 810bc62786SWarner Losh COPY=-C. 820bc62786SWarner Losh 8368a38c6cSWarner Losh20010525: 84b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 85c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 86c4f4a728SWarner Losh definitely is in bad shape. 8768a38c6cSWarner Losh 88ed0f29caSWarner Losh20010521: 89ed0f29caSWarner Losh Minor repo damanged has happened. This may cause problems 90ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 91ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 92ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 93ed0f29caSWarner Losh is 94ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 95ed0f29caSWarner Losh 9680c16af9SWarner Losh20010520: 9768a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 9880c16af9SWarner Losh 9980c16af9SWarner Losh20010519: 10080c16af9SWarner Losh pccard has had much reorganizational work done to it over 10180c16af9SWarner Losh the past few days. Everything should still work, but if 10280c16af9SWarner Losh not, please contact imp@freebsd.org. 10380c16af9SWarner Losh 104a45f2d05SWarner Losh20010517: 105a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 106a45f2d05SWarner Losh userland at the same time. 107a45f2d05SWarner Losh 108a45f2d05SWarner Losh20010517: 109a45f2d05SWarner Losh New ncurses imported. 110a45f2d05SWarner Losh 1112988afcaSWarner Losh20010512: 1122988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 1132988afcaSWarner Losh will be the only way to go starting July 1. 1142988afcaSWarner Losh 11509946a51SWarner Losh20010502: 11609946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 11709946a51SWarner Losh 11809946a51SWarner Losh20010501: 11909946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 12009946a51SWarner Losh 12109946a51SWarner Losh20010430: 122a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 12309946a51SWarner Losh go back in the water. 12409946a51SWarner Losh 12509946a51SWarner Losh20010429: 12609946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 12709946a51SWarner Losh this date, but before the correction date. 12809946a51SWarner Losh 12991dd3b53SWarner Losh20010423: 13091dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 13191dd3b53SWarner Losh 13291dd3b53SWarner Losh20010411: 13391dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 13491dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 13591dd3b53SWarner Losh Update only if you understand that you must not use the old 13691dd3b53SWarner Losh fsck with the new kernel ever. 13791dd3b53SWarner Losh 138933b3269SWarner Losh20010330: 139933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 140c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 141933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 142933b3269SWarner Losh 143933b3269SWarner Losh20010319: 144933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 145933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 146933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 14709946a51SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netcofnig. 14809946a51SWarner Losh 14909946a51SWarner Losh20010315: 15009946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 15109946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 15209946a51SWarner Losh been replaced by tunables. See ata.4 for details. 153933b3269SWarner Losh 154933b3269SWarner Losh20010312: 155933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 156933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 157933b3269SWarner Losh 158933b3269SWarner Losh20010312: 159933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 160933b3269SWarner Losh instead of ad-hoc. 161933b3269SWarner Losh 162933b3269SWarner Losh20010310: 163f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 164933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 165933b3269SWarner Losh ssh might not work if you don't. 166933b3269SWarner Losh 16762353691SWarner Losh20010303: 16862353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 16962353691SWarner Losh which means that you must include the miibus in your kernel if 17062353691SWarner Losh you use the ed driver. 17162353691SWarner Losh 172d325cf65SWarner Losh20010220: 173d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 174d325cf65SWarner Losh safe to go back into the water. 175d325cf65SWarner Losh 176024daae6SWarner Losh20010211: 177024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 178024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 179024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 180024daae6SWarner Losh that before upgrading would be a good time to do a level 0 181024daae6SWarner Losh dump of your system. No, really, I mean it this time. 182024daae6SWarner Losh 183024daae6SWarner Losh To get to the new system, you'll need to use the following 184024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 185024daae6SWarner Losh don't have to move this to the updating section. 186024daae6SWarner Losh 187024daae6SWarner Losh To get around the installworld problem, do: 188024daae6SWarner Losh # cd /usr/src/usr.bin/sed 189024daae6SWarner Losh # make install 190024daae6SWarner Losh # cd /usr/src 191024daae6SWarner Losh # make installworld 192024daae6SWarner Losh If that doesn't work, then try: 193024daae6SWarner Losh # make -k installworld 194024daae6SWarner Losh # make installworld 195024daae6SWarner Losh 196024daae6SWarner Losh20010207: 197024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 198024daae6SWarner Losh do not include devfs in your kernel as problems result. 199024daae6SWarner Losh 200024daae6SWarner Losh20010205: 2017595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 202024daae6SWarner Losh Remove them from your config. 203024daae6SWarner Losh 2041e159248SWarner Losh20010122: 2051e159248SWarner Losh ****************************** WARNING ****************************** 2061e159248SWarner Losh buildkernel has been changed slightly 2071e159248SWarner Losh ****************************** WARNING ****************************** 2081e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 2091e159248SWarner Losh should update your scripts and make.conf accordingly. 2101e159248SWarner Losh 2111e159248SWarner Losh20010119: 2121e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 2131e159248SWarner Losh This requires a new config to build correctly. 2141e159248SWarner Losh 215aac7dfeaSWarner Losh20010116: 216aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 217aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 218aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 219aac7dfeaSWarner Losh 220aac7dfeaSWarner Losh20010110: 221aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 222aac7dfeaSWarner Losh 223aac7dfeaSWarner Losh20010102: 224aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 225aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 226aac7dfeaSWarner Losh 22763c90c9eSWarner Losh20010101: 22863c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 22963c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 2305fd2a895SWarner Losh dump while building termcap. You can work around this problem 23163c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 23263c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 23363c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 23463c90c9eSWarner Losh might have been ignored by the -k option. 23563c90c9eSWarner Losh 2365fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 2375fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 2385fd2a895SWarner Losh of this working. 2395fd2a895SWarner Losh 240aac7dfeaSWarner Losh20001228: 241aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 242aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 243aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 244aac7dfeaSWarner Losh 245de2bcc63SWarner Losh20001218: 246de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 247de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 248de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 249de2bcc63SWarner Losh cards will not be recognized without it. 250de2bcc63SWarner Losh 251960773f7SWarner Losh20001205: 252960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 253960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 254960773f7SWarner Losh adding the following in pam.conf: 255960773f7SWarner Losh 256960773f7SWarner Losh sshd auth sufficient pam_skey.so 257960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 258960773f7SWarner Losh sshd session required pam_permit.so 259960773f7SWarner Losh 2600acc635eSWarner Losh20001031: 2610acc635eSWarner Losh cvs updated to 1.11. 2620acc635eSWarner Losh 2630acc635eSWarner Losh20001020: 2640acc635eSWarner Losh The random device needs more entropy, so you need to make sure 2650acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 2660acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 2670acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 2680acc635eSWarner Losh workaround. 2690acc635eSWarner Losh 2700acc635eSWarner Losh20001010: 2710acc635eSWarner Losh ****************************** WARNING ****************************** 2720acc635eSWarner Losh Sendmail has been updated. 2730acc635eSWarner Losh ****************************** WARNING ****************************** 2740acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 2750acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 2760acc635eSWarner Losh is set. 2770acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 2780acc635eSWarner Losh commands. 2790acc635eSWarner Losh o Now using sendmail's version of vacation(1). 2800acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 2810acc635eSWarner Losh in /usr/share/sendmail/cf. 2820acc635eSWarner Losh o sendmail.cw changed to local-host-names 2830acc635eSWarner Losh 2840acc635eSWarner Losh More details can be found at 2850acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 2860acc635eSWarner Losh 2876e98a146SWarner Losh20001009: 2886e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 2896e98a146SWarner Losh your entire ports tree, or you will have problems. 2906e98a146SWarner Losh 2916e98a146SWarner Losh20001006: 292685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 2936e98a146SWarner Losh the installed miniperl. It is recommended that you delete 2946e98a146SWarner Losh /usr/bin/miniperl. 2956e98a146SWarner Losh 296073113a4SWarner Losh20001005: 297073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 298685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 299073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 300073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 301073113a4SWarner Losh tree for anything to work. 302073113a4SWarner Losh 3030acc635eSWarner Losh20000928: 3040acc635eSWarner Losh There was a change in the passwd format. Need more information. 3050acc635eSWarner Losh 306be3885b3SWarner Losh20000916: 307be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 308be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 309be3885b3SWarner Losh same time as your kernel. 310be3885b3SWarner Losh 31176ec9675SWarner Losh20000914: 31276ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 31376ec9675SWarner Losh include the device will cause suspended laptops losing time 31476ec9675SWarner Losh when they resume. Include 31576ec9675SWarner Losh device pmtimer 31676ec9675SWarner Losh in your config file and 31701b9a434SWarner Losh hint.pmtimer.0.at="isa" 31876ec9675SWarner Losh to your /boot/device.hints file. 31976ec9675SWarner Losh 320f4865386SMark Murray20000911: 321f4865386SMark Murray The random device has been turned into a (pseudo-)device, 322f4865386SMark Murray rather than an option. The supplied kernel config files have 323f4865386SMark Murray been updated. You will need to do something similar in your 324f4865386SMark Murray own kernel config file. 325f4865386SMark Murray Remove: 326f4865386SMark Murray options RANDOMDEV 327f4865386SMark Murray Add: 328f4865386SMark Murray device random 329f4865386SMark Murray If you prefer to load the loadable module, you need to do 330f4865386SMark Murray nothing. 331f4865386SMark Murray 332d594498fSWarner Losh20000909: 333d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 334d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 335d594498fSWarner Losh reflect this if you load this module at boot time. 336d594498fSWarner Losh The line should read: 337d594498fSWarner Losh random_load="YES" 338d594498fSWarner Losh 3390deb7ddcSWarner Losh20000907: 3400deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 34116eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 34216eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 34316eb772dSWarner Losh sure you don't have model loading problems which might at 34416eb772dSWarner Losh first blush appear related to SMP. 34552bf24e7SWarner Losh 3465a01880bSWarner Losh20000906: 3475a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 3485a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 3495a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 3505a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 3515a01880bSWarner Losh don't have one, and you have host.conf. 3525a01880bSWarner Losh 3532b41163cSWarner Losh20000905: 35438d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 35538d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 35638d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 35738d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 35838d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 35938d6ecd2SWarner Losh 36038d6ecd2SWarner Losh20000905: 3618aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 3628aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 3638aab4bc7SWarner Losh is /boot/kernel. 3648aab4bc7SWarner Losh 3658aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 36638d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 36738d6ecd2SWarner Losh installkernel/installworld dance. 3682b41163cSWarner Losh 369d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 370d594498fSWarner Losh before booting the new kernel, since kldload will find stale 371d594498fSWarner Losh modules in that directory instead of finding them in the correct 372d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 373d594498fSWarner Losh is that the linux module crashes your machine after the update. 374d594498fSWarner Losh 375d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 376d594498fSWarner Losh mv /modules.old /boot/kernel.old 377d594498fSWarner Losh chflags noschg /kernel.old 378d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 379d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 380d594498fSWarner Losh fi 381d594498fSWarner Losh 382c22a309cSWarner Losh20000904: 383c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 384c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 385c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 386c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 387c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 388c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 389c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 390c22a309cSWarner Losh is not likely to be generated. 391c22a309cSWarner Losh 392fdb9f54dSWarner Losh20000825: 393fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 3949c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 3959c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 3969c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 3979c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 3989c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 3999c1a7444SWarner Losh messages will appear after the boot loader tries to start the 4009c1a7444SWarner Losh kernel. 4019c1a7444SWarner Losh 4029c1a7444SWarner Losh20000821: 4039c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 4049c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 4059c1a7444SWarner Losh /boot/loader.conf. 406fdb9f54dSWarner Losh 4078f250aa7SWarner Losh20000812: 4085da0d091SWarner Losh suidperl is now always built and installed on the system, but 4095da0d091SWarner Losh with permissions of 511. If you have applications that use 4105da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 4115da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 4125da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 4135da0d091SWarner Losh will fix this until the next build. 4145da0d091SWarner Losh 4155da0d091SWarner Losh20000812: 4168f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 4178f250aa7SWarner Losh visible changes that may immediately affect your configuration 4188f250aa7SWarner Losh include: 4198f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 4208f250aa7SWarner Losh - newaliases limited to root and trusted users 4218f250aa7SWarner Losh - MSA port (587) turned on by default 4228f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 4238f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 4248f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 4258f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 4268f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 4278f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 4288f250aa7SWarner Losh 42971c38472SWarner Losh20000810: 43071c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 43171c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 43271c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 43371c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 43471c38472SWarner Losh specific use for it. 43571c38472SWarner Losh 43671c38472SWarner Losh20000729: 43771c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 43871c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 43971c38472SWarner Losh /etc/rc.conf if they want to have the same setup 44071c38472SWarner Losh afterwards (unless the variables already are set, of course): 44171c38472SWarner Losh # Enable network daemons for user convenience. 44271c38472SWarner Losh inetd_enable="YES" 44371c38472SWarner Losh portmap_enable="YES" 44471c38472SWarner Losh sendmail_enable="YES" 44571c38472SWarner Losh 44671c38472SWarner Losh20000728: 44771c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 44871c38472SWarner Losh will need to change that to nullfs_load="YES". 44971c38472SWarner Losh 4501dece4a9SWarner Losh20000728: 4511dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 4521dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 4531dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 4541dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 4551dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 4561dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 4571dece4a9SWarner Losh to /MYKERNEL. 4581dece4a9SWarner Losh 459409e887cSWarner Losh20000711: 460409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 461409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 462409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 463409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 464409e887cSWarner Losh for details on potential problems that you might have and how 465409e887cSWarner Losh to get around them. 466409e887cSWarner Losh 467409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 468409e887cSWarner Losh clauses above, you needn't worry. 469409e887cSWarner Losh 470409e887cSWarner Losh20000711: 471409e887cSWarner Losh /etc/security has been updated to print the inode number of 472409e887cSWarner Losh setuid programs that have changed. You will see a large spike 473409e887cSWarner Losh in the number of changed programs the first time when you run 474409e887cSWarner Losh mergemaster to get a new /etc/security. 475409e887cSWarner Losh 476673d13f2SWarner Losh20000710: 477673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 478673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 479673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 480673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 481673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 482673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 483673d13f2SWarner Losh errors. (see below, 20000624). 484673d13f2SWarner Losh 485bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 4861dece4a9SWarner Losh 487673d13f2SWarner Losh20000709: 488c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 489c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 490c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 491673d13f2SWarner Losh ln -s aj /etc/malloc.conf 492673d13f2SWarner Losh 493e98e26cdSWarner Losh20000706: 494e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 495e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 496e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 497f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 498e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 4992c021c6cSMark Ovens interim if needed. 500e98e26cdSWarner Losh 501e98e26cdSWarner Losh20000705: 502e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 503e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 504e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 505e98e26cdSWarner Losh details. 506e98e26cdSWarner Losh 507c373950eSWarner Losh20000704: 5082f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 5092f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 5102f961bc8SWarner Losh 5112f961bc8SWarner Losh20000704: 512c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 513c373950eSWarner Losh or stop. This may cause some harmless warnings from older 514c373950eSWarner Losh rc.d scripts that haven't been updated. 515c373950eSWarner Losh 51627dc3a2bSWarner Losh20000630: 51727dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 51827dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 51927dc3a2bSWarner Losh which should be reported to des@freebsd.org. 52027dc3a2bSWarner Losh 521b8c215acSWarner Losh20000625: 522b8c215acSWarner Losh From approximately this date forward, one must have the crypto 52327dc3a2bSWarner Losh system installed in order to build the system and kernel. 52427dc3a2bSWarner Losh While not technically strictly true, one should treat it as 52527dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 52627dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 52727dc3a2bSWarner Losh were required. You should check with the latest collections 52827dc3a2bSWarner Losh to make sure that these haven't changed. 529b8c215acSWarner Losh 5307b990719SWarner Losh20000624: 5317b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 5327b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 5337b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 5347b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 5357b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 5367b990719SWarner Losh openssh and openssl should not be used to generate keys from this 5377b990719SWarner Losh date to the completion of the work. 5387b990719SWarner Losh 53927dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 54027dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 54127dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 54227dc3a2bSWarner Losh recreate the random and urandom devices. 54327dc3a2bSWarner Losh 54481e54c50SWarner Losh20000622: 54581e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 54681e54c50SWarner Losh BSD license. You may need to remove your symbolic links 54781e54c50SWarner Losh that used to be required when updating. 54881e54c50SWarner Losh 54939943833SWarner Losh20000621: 5502c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 5512a2f33fbSDaniel Baker the config file update procedure. 5522a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 553c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 554a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 55539943833SWarner Losh 556290f9ad8SWarner Losh20000620: 557290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 558290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 559290f9ad8SWarner Losh that workaround will no longer be required. 560290f9ad8SWarner Losh 56190fb6346SWarner Losh20000615: 56290fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 56390fb6346SWarner Losh ad driver. If you haven't done so already, you must update 56490fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 56590fb6346SWarner Losh devices. 56690fb6346SWarner Losh 567f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 568f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 569f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 570f75f65bbSWarner Losh may work). 571f75f65bbSWarner Losh 572ba26da8eSWarner Losh20000612: 573ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 574290f9ad8SWarner Losh on the topic before even thinking about updating. You will 575c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 576290f9ad8SWarner Losh to your config file to compile them in statically. The format 577f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 578f54a3542SWarner Losh NEWCARD for examples of the new format. 579290f9ad8SWarner Losh 580d65850ebSWarner Losh20000522: 581ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 582d65850ebSWarner Losh building a kernel after this point is advised that they need 583d65850ebSWarner Losh to rebuild their binutils (or better yet do a 584d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 585d65850ebSWarner Losh 586d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 587d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 588d9583a00SWarner Losh is recommended that you don't set this option until the problem 589d9583a00SWarner Losh is resolved. 590d9583a00SWarner Losh 5918039cedeSWarner Losh20000513: 5928039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 5938039cedeSWarner Losh 594d65850ebSWarner Losh20000510: 5958039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 5968039cedeSWarner Losh This will require some care in updating alphas. A new libstand 5978039cedeSWarner Losh is requires for the boot blocks to build properly. 5988039cedeSWarner Losh 5998039cedeSWarner Losh20000503: 6008039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 6018039cedeSWarner Losh is now available. 6028039cedeSWarner Losh 603d65850ebSWarner Losh20000502: 604d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 605d65850ebSWarner Losh connected to the kernel building instead. 606d65850ebSWarner Losh 607be149406SNik Clayton20000427: 6088039cedeSWarner Losh You may need to build gperf 6098039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 6108039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 6118039cedeSWarner Losh an option only in -current. 6128039cedeSWarner Losh 6132b8dd5f4SWarner Losh20000417: 6142b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 615f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 6162b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 6172b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 6182c021c6cSMark Ovens before you reboot, you'll need to issue: 6192b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 6202b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 6212b8dd5f4SWarner Losh 6228d9f1945SWarner Losh20000320: 6232b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 6242b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 6252b8dd5f4SWarner Losh cope if you have a problem combination is to add: 6268d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 6272b8dd5f4SWarner Losh to the start of /etc/rc.conf. 6288d9f1945SWarner Losh 629f8ab1dd6SWarner Losh20000319: 630f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 631f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 632f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 633f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 634f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 635f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 636f8ab1dd6SWarner Losh 63719cada77SWarner Losh20000318: 638f699bbbbSMark Ovens We've entered the traditional post release dumping party. 63919cada77SWarner Losh Large kernel changes are being committed and are in the 64019cada77SWarner Losh works. It is important to keep the systems' klds and kernel 64119cada77SWarner Losh in sync as kernel interfaces and structures are changing. 64219cada77SWarner Losh Before reporting kernel panics, make sure that all modules 64319cada77SWarner Losh that you are loading are up to date. 644ba228352SWarner Losh 64519cada77SWarner Losh20000315: 6466d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 6476d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 6486d23c382SWarner Losh will do the trick. This isn't critical until you remove your 6496d23c382SWarner Losh wd device entries in /dev, at which point your system will not 6506d23c382SWarner Losh boot. 6516d23c382SWarner Losh 6526d23c382SWarner Losh20000315: 65319cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 65419cada77SWarner Losh to upgrade to 4.0 from 3.x. 65557199806SWarner Losh 656dc0dbf5cSWarner LoshCOMMON ITEMS: 657dc0dbf5cSWarner Losh 658a24eff53SWarner Losh General Notes 659a24eff53SWarner Losh ------------- 660a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 661a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 662a24eff53SWarner Losh installworld. This is especially true when upgrading between 663a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 664a24eff53SWarner Losh or several minor releases, or when several months have passed 665a24eff53SWarner Losh on the -current branch). 666a24eff53SWarner Losh 667dc0dbf5cSWarner Losh To build a kernel 668dc0dbf5cSWarner Losh ----------------- 669ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 670f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 671ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 6721e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 6731e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 674dc0dbf5cSWarner Losh 675ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 676ba01eb20SWarner Losh -------------------------------------------------------------- 677ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 678ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 679ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 680ba01eb20SWarner Losh make depend 681ba01eb20SWarner Losh make 682ba01eb20SWarner Losh make install 683ba01eb20SWarner Losh 684ba01eb20SWarner Losh [1] If in doubt, -r might help here. 685ba01eb20SWarner Losh 686ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 687ba01eb20SWarner Losh 688ba01eb20SWarner Losh To rebuild everything and install it on the current system. 689ba01eb20SWarner Losh ----------------------------------------------------------- 690759f0aefSWarner Losh make world 691fdb9f54dSWarner Losh Build a new kernel, see above. 692759f0aefSWarner Losh 6931dece4a9SWarner Losh To upgrade from 4.x-stable to current 694ba26da8eSWarner Losh ------------------------------------- 695ba26da8eSWarner Losh make buildworld 6961e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 6977595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 6981e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 699ee6e1fc3SWarner Losh reboot in single user [3] 700ba26da8eSWarner Losh make installworld 7017595222aSWarner Losh mergemaster 702134d2e86SWarner Losh [1] 703ba26da8eSWarner Losh <reboot> 704ba26da8eSWarner Losh 705fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 706fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 707fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 708fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 709fdb9f54dSWarner Losh the UPDATING entries. 710ba26da8eSWarner Losh 7111dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 7121dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 7131dece4a9SWarner Losh your sources that you have read and understood all the recent 7141dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 7151dece4a9SWarner Losh much fewer pitfalls. 7161dece4a9SWarner Losh 717134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 718134d2e86SWarner Losh should disable them at this point so they don't crash your 719134d2e86SWarner Losh system on reboot. 720134d2e86SWarner Losh 7219c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 7229c1a7444SWarner Losh your own device.hints to reflect your unique hardware 7239c1a7444SWarner Losh configuration. 7249c1a7444SWarner Losh 725ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 726ee6e1fc3SWarner Losh fsck -p 727ee6e1fc3SWarner Losh mount -u / 728ee6e1fc3SWarner Losh mount -a 729ee6e1fc3SWarner Losh cd /usr/src 730ee6e1fc3SWarner Losh adjkerntz -i # if COMS is wall time 731ee6e1fc3SWarner Losh 732dc0dbf5cSWarner LoshFORMAT: 733dc0dbf5cSWarner Losh 734f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 7351fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 736f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 737f8ab1dd6SWarner Loshprevious releases if your system is older than this. 7381fc1a0dcSWarner Losh 7393645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 7403645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 741f8c77507SWarner Losh 742e72fd46aSWarner LoshCopyright information: 743e72fd46aSWarner Losh 744e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh. All Rights Reserved. 745e72fd46aSWarner Losh 746e72fd46aSWarner LoshRedistribution, translation and use, with or without modification, in 747e72fd46aSWarner Loshfull or in part, are permitted provided that the above copyright 748e72fd46aSWarner Loshnotice is retained. 749e72fd46aSWarner Losh 750e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 751e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 752e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 753e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 754e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 755e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 756e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 757e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 758e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 759e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 760e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 761e72fd46aSWarner Losh 762e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 763e72fd46aSWarner Loshauthor a beer. 764e72fd46aSWarner Losh 76597d92980SPeter Wemm$FreeBSD$ 766