157199806SWarner LoshUpdating Information for FreeBSD current users 253dfde79SWarner Losh 3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh 49698f2c0SWarner Losh<imp@village.org>. See end of file for further details. For commonly 59698f2c0SWarner Loshdone items, please see the COMMON ITEMS: section later in the file. 6e72fd46aSWarner Losh 7f59d5f7aSPoul-Henning KampNOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW: 8f59d5f7aSPoul-Henning Kamp FreeBSD 5.x has many debugging features turned on, in 969f7bcf3SWarner Losh both the kernel and userland. These features attempt to detect 1069f7bcf3SWarner Losh incorrect use of system primitives, and encourage loud failure 1169f7bcf3SWarner Losh through extra sanity checking and fail stop semantics. They 1269f7bcf3SWarner Losh also substantially impact system performance. If you want to 1369f7bcf3SWarner Losh do performance measurement, benchmarking, and optimization, 1469f7bcf3SWarner Losh you'll want to turn them off. This includes various WITNESS- 1569f7bcf3SWarner Losh related kernel options, INVARIANTS, malloc debugging flags 1669f7bcf3SWarner Losh in userland, and various verbose features in the kernel. Many 1769f7bcf3SWarner Losh developers choose to disable these features on build machines 18a19f8ddaSDavid E. O'Brien to maximize performance. 19c1f61aa9SDavid E. O'Brien 20ce41f4bfSRobert Watson20031213: 21ce41f4bfSRobert Watson src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 22ce41f4bfSRobert Watson if the login process is unable to successfully set the 23ce41f4bfSRobert Watson process credentials to include all groups defined for the 24ce41f4bfSRobert Watson user. The current kernel limit is 16 groups; administrators 25ce41f4bfSRobert Watson may wish to check that users do not have over 16 groups 26ce41f4bfSRobert Watson defined, or they will be unable to log in. 27ce41f4bfSRobert Watson 288ad1f5e4SHartmut Brandt20031112: 2930093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 3030093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 3197209ca3SRobert Watson sizes. You should build world, then build and boot the new kernel 3297209ca3SRobert Watson BEFORE doing a `installworld' as the new kernel will know about 3397209ca3SRobert Watson binaries using the old statfs structure, but an old kernel will 3497209ca3SRobert Watson not know about the new system calls that support the new statfs 353f631d52SMarcel Moolenaar structure. 363f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 373f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 383f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 393f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 403f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 413f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 423f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 433f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 443f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 453f631d52SMarcel Moolenaar these changes are installed. 4630093b05SWarner Losh 4730093b05SWarner Losh ****************************DANGER******************************* 4830093b05SWarner Losh 4930093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 5030093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 5130093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 5230093b05SWarner Losh kernel. 5364a18d6fSKirk McKusick 5464a18d6fSKirk McKusick20031112: 558ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 568ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 578ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 588ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 598ad1f5e4SHartmut Brandt sync before rebooting. 608ad1f5e4SHartmut Brandt 61c53a5d8fSJohn Baldwin20031111: 62c53a5d8fSJohn Baldwin Hyperthreading logical CPU's are no longer probed by default 63c53a5d8fSJohn Baldwin when using the MP Table. If ACPI is being used, then logical 64c53a5d8fSJohn Baldwin CPUs will be probed if hyperthreading is enabled in the BIOS. 65c53a5d8fSJohn Baldwin If ACPI is not being used and hyperthreading is enabled in the 66c53a5d8fSJohn Baldwin BIOS, logical CPUs can be enabled by building a custom kernel 67c53a5d8fSJohn Baldwin with the option MPTABLE_FORCE_HTT enabled. 68c53a5d8fSJohn Baldwin 698bf455a5SJohn Baldwin20031103: 708bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 718bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 722a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 738bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 748bf455a5SJohn Baldwin 759bf40edeSBrooks Davis20031031: 769bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 779bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 789bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 799bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 809bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 819bf40edeSBrooks Davis reflect this change. 829bf40edeSBrooks Davis 8347a42c7aSPoul-Henning Kamp20030928: 8447a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 8547a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 8647a42c7aSPoul-Henning Kamp __FreeBSD_version bumpted to 501110. 8747a42c7aSPoul-Henning Kamp 8807105342SMax Khon20030926: 8907105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 9007105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 9107105342SMax Khon 9217dcd026SSam Leffler20030925: 9317dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 9417dcd026SSam Leffler also be explicitly configured. Previously this dependency was 9517dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 9617dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 9717dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 9817dcd026SSam Leffler 99fedf1d01SBruce M Simpson20030923: 100fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 101fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 102fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 103fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 104fedf1d01SBruce M Simpson 105db38f9cbSJacques Vidrine20030915: 106db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 107db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 108db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 109db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 110db38f9cbSJacques Vidrine 111c09d2c2bSMike Makonnen20030829: 112c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 113c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 114c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 115c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 116c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 117c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 118c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 119c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 120c09d2c2bSMike Makonnen may or may not exist on your system. 121c09d2c2bSMike Makonnen 12217c159dcSSøren Schmidt20030824: 12317c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 12417c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 125f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 126f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 12717c159dcSSøren Schmidt 128c1f61aa9SDavid E. O'Brien20030819: 129c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 130c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 131c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 132c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 13369f7bcf3SWarner Losh 13438c962e7SNate Lawson20030728: 13538c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 13638c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 13738c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 13838c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 13938c962e7SNate Lawson so the quirk can be re-enabled. 14038c962e7SNate Lawson 141178cf4e9SWarner Losh20030722: 142178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 143178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 144178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 145178cf4e9SWarner Losh FPU hardware. 146178cf4e9SWarner Losh 147178cf4e9SWarner Losh20030714: 148178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 149178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 150178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 151178cf4e9SWarner Losh People should report those issues to current@. 152178cf4e9SWarner Losh 153157c629aSWarner Losh20030711: 154157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 1558b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 15605538fa9SWarner Losh /usr/obj. 157157c629aSWarner Losh 1586cc6353fSMarcel Moolenaar20030613: [retrospective] 1596cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 1606cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 1616cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 1626cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 1636cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 1646cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 1656cc6353fSMarcel Moolenaar 1666cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 1676cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 1686cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 1696cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 1706cc6353fSMarcel Moolenaar : 1716cc6353fSMarcel Moolenaar 1726cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 1736cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 1746cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 1756cc6353fSMarcel Moolenaar 176766c34e4SAndrey A. Chernov20030610: 177766c34e4SAndrey A. Chernov Remove deprecated locale names and transition period code 178766c34e4SAndrey A. Chernov for them, finishing switching to the new scheme. Check your 179766c34e4SAndrey A. Chernov LANG environment variable. 180766c34e4SAndrey A. Chernov 1817ddc2528SPoul-Henning Kamp20030609: 182df622d54SPoul-Henning Kamp CCD has been changed to be a fully GEOMified class. Kernel 183df622d54SPoul-Henning Kamp and ccdconfig(8) needs to be in sync, this is particularly 184df622d54SPoul-Henning Kamp important to remember beforehand if your source tree is on 185df622d54SPoul-Henning Kamp a ccd device. Consider making a copy of the old ccdconfig 186df622d54SPoul-Henning Kamp into /boot/kernel.good or wherever you keep your backup 187df622d54SPoul-Henning Kamp kernel. 188df622d54SPoul-Henning Kamp 18952b47445SMark Murray20030505: 19052b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 19152b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 19252b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 19352b47445SMark Murray 194a26df538SWarner Losh20030502: 195a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 196a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 197a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 198a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 199a26df538SWarner Losh 2004b065e2cSDoug Barton20030501: 2014b065e2cSDoug Barton The old rc system has been removed. Please report any problems 2024b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 2034b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 2044b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 2054b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 2064b065e2cSDoug Barton utilizes these old scripts has also been removed. 2074b065e2cSDoug Barton 20881cda3d9SWarner Losh20030423: 20981cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 21081cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 21181cda3d9SWarner Losh work around in devd will be removed around 20030507. You 21281cda3d9SWarner Losh have until then to upgrade your kernel before updating 21381cda3d9SWarner Losh userland. In general, you should have a userland and 21481cda3d9SWarner Losh kernel that's in sync with each other. However, given the 21581cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 21681cda3d9SWarner Losh allowances are made. 21781cda3d9SWarner Losh 21847a657d1SRuslan Ermilov20030329: 21947a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 22047a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 22147a657d1SRuslan Ermilov while upgrading the system through a buildworld. 22247a657d1SRuslan Ermilov 22347a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 22447a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 22547a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 22647a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 22747a657d1SRuslan Ermilov 22847a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 22947a657d1SRuslan Ermilov make cleandir && make obj && \ 23047a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 23147a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 23247a657d1SRuslan Ermilov 2335d2af00cSGregory Neil Shapiro20030208: 2345d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 2355d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 2365d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 2375d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 2385d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 2395d2af00cSGregory Neil Shapiro 2405d2af00cSGregory Neil Shapiro20030128: 2419db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 242ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 2439db58771SPoul-Henning Kamp be removed when convenient. 2449db58771SPoul-Henning Kamp 2458d9b3f57SJake Burkholder20030126: 2468d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 2478d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 2488d9b3f57SJake Burkholder 2491c5efda5SJeff Roberson20030125: 2501c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 2511c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 252ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 2531c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 2541c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 2551c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 2561c5efda5SJeff Roberson 2579d1d64f5SWarner Losh20030115: 2589d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 2599d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 2609d1d64f5SWarner Losh properly. 2619d1d64f5SWarner Losh 262c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 263c9fdb80aSWarner Losh configured for point to point links to bring it more in line 264c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 265c9fdb80aSWarner Losh with NetBSD. 266c9fdb80aSWarner Losh 267161dc364SAlexander Kabaev20021222: 268161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 269161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 270161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 271161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 272161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 273161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 27484cc83efSAlexander Kabaev rebuilt. 275161dc364SAlexander Kabaev 276fb4c8061SMartin Blapp20021216: 277fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 27889056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 279fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 2809d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 281fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 282fb4c8061SMartin Blapp 28317d47eb3SGiorgos Keramidas20021202: 28417d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 28517d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 28617d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 28717d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 28817d47eb3SGiorgos Keramidas 289a4459294SBill Fenner20021029: 290a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 291a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 292a4459294SBill Fenner consumers in sync. 293a4459294SBill Fenner 294fc8c157fSWarner Losh20021024: 295c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 296c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 297c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 298c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 299c57404feSRuslan Ermilov partition really is on. The old device names have gone 300c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 301c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 302c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 30369f7bcf3SWarner Losh 304fd9e8bdaSAndrew Gallatin20021023: 305fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 306fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 307fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 308fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 309fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 310fd9e8bdaSAndrew Gallatin 311fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 312fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 313fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 314fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 315fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 316fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 317fd9e8bdaSAndrew Gallatin 318f8a4c901SWarner Losh20020831: 319f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 320f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 321f8a4c901SWarner Losh programs and libraries need to be recompiled. 322f8a4c901SWarner Losh 323f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 324f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 325f8a4c901SWarner Losh 326c2248fa2SJens Schweikhardt20020827: 327c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 328c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 329c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 330c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 331c2248fa2SJens Schweikhardt 3320d533e43SRuslan Ermilov20020815: 3330d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 3340d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 3350d533e43SRuslan Ermilov again. 3360d533e43SRuslan Ermilov 33733c1de7dSRuslan Ermilov20020729: 33833c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 33933c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 34033c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 34133c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 34233c1de7dSRuslan Ermilov 3432b877facSJulian Elischer20020702: 3442b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 3452b877facSJulian Elischer There are still some minor problems with some signals but the 3462b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 3472b877facSJulian Elischer but each can successfully complete multiple buildworlds. 3482b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 3492b877facSJulian Elischer 35006596d37SWarner Losh20020701: 35106596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 35206596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 35306596d37SWarner Losh GNOME. 35406596d37SWarner Losh 35595ba4330SJacques Vidrine20020511: 35695ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 35795ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 35895ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 35995ba4330SJacques Vidrine with the set-user-ID bit set. 36095ba4330SJacques Vidrine 361a81da3c9SDavid E. O'Brien20020510: 362f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 363f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 3644b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 365f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 366f50caf6fSDavid E. O'Brien 367f50caf6fSDavid E. O'Brien20020510: 368a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 369a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 370a81da3c9SDavid E. O'Brien and then do a cvs update. 371a81da3c9SDavid E. O'Brien 372528a0ef5SJacques Vidrine20020421: 373528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 374528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 375528a0ef5SJacques Vidrine 37685aa5a2eSGregory Neil Shapiro20020404: 37785aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 37885aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 37985aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 38085aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 38185aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 38285aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 38385aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 38485aa5a2eSGregory Neil Shapiro 3858f1e4358SRuslan Ermilov20020403: 3868f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 3878f1e4358SRuslan Ermilov 3882292c02eSWarner Losh20020315: 3892292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 3902292c02eSWarner Losh 39169f7bcf3SWarner Losh20020225: 39269f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 39369f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 39469f7bcf3SWarner Losh 3958f35c493SWarner Losh20020217: 3968f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 3978f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 3988f35c493SWarner Losh command line mail submission has changed. Be sure to run 3998f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 4008f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 4018f35c493SWarner Losh 402835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 403835284beSWarner Losh required in order for sendmail to run as a set-group-ID 404835284beSWarner Losh binary. A 'make installworld' will use the new user and group 405835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 406835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 407835284beSWarner Losh and group must be merged from src/etc/group and 408835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 409835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 410835284beSWarner Losh mergemaster before this will work if you are updating from a 411835284beSWarner Losh very old version of current. The updating recipe has changed 412835284beSWarner Losh as of this date. 413835284beSWarner Losh 414fa9401c1SWarner Losh20020112: 415fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 416fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 417fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 418fa9401c1SWarner Losh you have local modifications, you can use 419fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 420fa9401c1SWarner Losh /etc/pam.d. 421fa9401c1SWarner Losh 422fa9401c1SWarner Losh Please see the following url for more details: 423fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 42447d0d01fSWarner Losh20011229: 42547d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 42647d0d01fSWarner Losh networkfs_types, please note that it has changed 42747d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 42847d0d01fSWarner Losh 429514318a8SWarner Losh20011220: 430514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 431514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 432514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 433514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 434514318a8SWarner Losh version have now been merged back into the base system's 435514318a8SWarner Losh version now. The only user-visible change resulting from this 436514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 437514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 438514318a8SWarner Losh as well. (There has never been rc file support for 439514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 440514318a8SWarner Losh reverted by the time the changes are MFCed.) 441514318a8SWarner Losh 442514318a8SWarner Losh20011215: 443514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 444514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 445514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 446514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 447514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 448514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 449514318a8SWarner Losh will need to be customized then for `odd' densities using 450514318a8SWarner Losh fdcontrol(8). 451514318a8SWarner Losh 4522d22e2bfSWarner Losh20011209: 4532d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 4542d22e2bfSWarner Losh and truss(1) now works again. 4552d22e2bfSWarner Losh 4569e0428e2SWarner Losh20011207: 4579e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 4589e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 4599e0428e2SWarner Losh see 4609e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 4619e0428e2SWarner Losh for details. 4629e0428e2SWarner Losh 4639bab8c59SWarner Losh20011204: 4649bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 4659bab8c59SWarner Losh kernel and burncd to be in sync. 4669bab8c59SWarner Losh 467e57d8b01SWarner Losh20011203: 468e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 469e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 470e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 471e57d8b01SWarner Losh not there already. 472e57d8b01SWarner Losh 473e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 474e57d8b01SWarner Losh until the issue has been resolved. 475e57d8b01SWarner Losh 476b001d36fSJacques Vidrine20011202: 477b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 478b001d36fSJacques Vidrine patched. 479b001d36fSJacques Vidrine 4804b676ec1SWarner Losh20011126: 4814b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 4825ebbf43eSWarner Losh after this date. You need to do this only once. 4834b676ec1SWarner Losh 484d961e462SWarner Losh20011103: 485d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 486d961e462SWarner Losh edges may be left, but for the most part things should be 4874b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 488d961e462SWarner Losh 489d961e462SWarner Losh20011030: 490d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 491d961e462SWarner Losh choppy waves in the upgrade process. 492d961e462SWarner Losh 4931fe003b6SWarner Losh20011030: 494a4b6fda0SWarner Losh The asr driver problem has been resolved. 4951fe003b6SWarner Losh 4961fe003b6SWarner Losh20011027: 4971fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 4981fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 4991fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 5001fe003b6SWarner Losh try to use from this date forward. 5011fe003b6SWarner Losh 5021fe003b6SWarner Losh20011025: 5031fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 5041fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 5051fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 5061fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 5071fe003b6SWarner Losh TARGET_ARCH=i386. 5081fe003b6SWarner Losh 509d05f9643SWarner Losh20011001: 510d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 511d05f9643SWarner Losh You must recompile both the kernel and userland applications 512d05f9643SWarner Losh at the same time. 513d05f9643SWarner Losh 51458970f85SWarner Losh20010929: 51558970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 51658970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 51758970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 51858970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 5199d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 52058970f85SWarner Losh 52158970f85SWarner Losh20010927: 52258970f85SWarner Losh Some weird problems result from using ACPI on some machines. 52358970f85SWarner Losh To disable ACPI you can add 52466ff0e67SMax Khon hint.acpi.0.disabled="1" 52558970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 52658970f85SWarner Losh loader "ok" prompt). 52758970f85SWarner Losh 52858970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 52958970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 53058970f85SWarner Losh file and not list acpi in that list. 531378f4486SAlfred Perlstein 5325119d237SWarner Losh20010924: 5335119d237SWarner Losh The buildworld has been fixed. You may need to install 5345119d237SWarner Losh the 4.x compatibility libraries for some old binaries 5358b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 5368b039fffSWarner Losh get them installed on every installworld, or execute the 5378b039fffSWarner Losh following to get them installed only once: 5388b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 53958970f85SWarner Losh make all install 5408b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 5415119d237SWarner Losh 5423c293725SWarner Losh20010919: 5433c293725SWarner Losh There's a bug in the world build process. The cross-tools 5443c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 5453c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 546772730c7SWarner Losh workaround is to add 5473c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 5483c293725SWarner Losh before building world when upgrading from 4.x to current. This 5493c293725SWarner Losh can be removed afterwards. 5503c293725SWarner Losh 5513c293725SWarner Losh A proper fix to the buildworld target is needed. 5523c293725SWarner Losh 5533c293725SWarner Losh20010918: 5543c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 5553c293725SWarner Losh NFS may be unstable after this date. 5563c293725SWarner Losh 5573c293725SWarner Losh20010912: 5583c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 5593c293725SWarner Losh the kernel. While a few problems were introduced in the 5603c293725SWarner Losh initial commit, most of the major ones have been found and 5613c293725SWarner Losh corrected. 5623c293725SWarner Losh 5633c293725SWarner Losh20010901: 5643c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 5653c293725SWarner Losh arounds described in the 20010604 entry are now no longer 5663c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 5673c293725SWarner Losh have been rectified around this date. 5683c293725SWarner Losh 56998b17b95SWarner Losh20010823: 57098b17b95SWarner Losh named now runs as user bind and group bind rather than as 57198b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 57298b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 57398b17b95SWarner Losh and that group bind is available in /etc/group. Also make 57498b17b95SWarner Losh sure that user or group bind has read (and not write) 57598b17b95SWarner Losh permission for your name server configuration and that it 57698b17b95SWarner Losh has read and write permission for your slave zone files and 57798b17b95SWarner Losh directory. 57898b17b95SWarner Losh 57998b17b95SWarner Losh If you wish to continue to run named as root (a less secure 58098b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 58198b17b95SWarner Losh 58298b17b95SWarner Losh named_flags= 58398b17b95SWarner Losh 5847b9786edSMark Murray20010709: 5857b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 5867b9786edSMark Murray the ability of the shared library major number to handle. 5877b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 5887b9786edSMark Murray solution is to rebuild those ports. 5897b9786edSMark Murray 5901d28950eSWarner Losh20010628: 5911d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 5921d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 5931d28950eSWarner Losh 594e72fd46aSWarner Losh20010625: 59598b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 59698b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 59798b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 59898b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 59998b17b95SWarner Losh IRQ configuration needs more safety belts. 60016de1a07SWarner Losh 6010d415dffSWarner Losh20010617: 602e72fd46aSWarner Losh Softupdates problems have been corrected. 6030d415dffSWarner Losh 6040d415dffSWarner Losh20010614: 6050d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 6060d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 6070d415dffSWarner Losh kernel building methods. 6080d415dffSWarner Losh 6098b9959adSWarner Losh20010613: 6108b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 6118b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 612e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 613e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 6148b9959adSWarner Losh 615e72fd46aSWarner Losh20010613: 6168b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 617e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 618e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 6198b9959adSWarner Losh 6200d415dffSWarner Losh20010612: 6210d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 6220d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 6230d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 6240d415dffSWarner Losh work around this issue, please use only one or the other mechanism 6250d415dffSWarner Losh until this bug is fixed. 6260d415dffSWarner Losh 627e72fd46aSWarner Losh Please note that a feature of config is that if you have config 628e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 629ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 630e72fd46aSWarner Losh 6310d415dffSWarner Losh20010610: 6320d415dffSWarner Losh Locale names have changed to match other systems better. 6330d415dffSWarner Losh 6346ccdb5e4SWarner Losh20010604: 6356ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 6366ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 6376ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 6383590182eSWarner Losh Interrupt storms look a lot like a hang. 6393590182eSWarner Losh 6403590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 6413590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 6423590182eSWarner Losh it is). 6433590182eSWarner Losh 6443590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 6453590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 6463590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 6473590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 6486ccdb5e4SWarner Losh 6490bc62786SWarner Losh20010530: 6500bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 6510bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 6520bc62786SWarner Losh a limited time. If you see 6530bc62786SWarner Losh 6540bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 6550bc62786SWarner Losh 6560bc62786SWarner Losh in your makeworld, then you need to migrate towards using 6570bc62786SWarner Losh COPY=-C. 6580bc62786SWarner Losh 65968a38c6cSWarner Losh20010525: 660b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 661c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 662c4f4a728SWarner Losh definitely is in bad shape. 66368a38c6cSWarner Losh 664ed0f29caSWarner Losh20010521: 665ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 666ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 667ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 668ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 669ed0f29caSWarner Losh is 670ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 671ed0f29caSWarner Losh 67280c16af9SWarner Losh20010520: 67368a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 67480c16af9SWarner Losh 67580c16af9SWarner Losh20010519: 67680c16af9SWarner Losh pccard has had much reorganizational work done to it over 67780c16af9SWarner Losh the past few days. Everything should still work, but if 67880c16af9SWarner Losh not, please contact imp@freebsd.org. 67980c16af9SWarner Losh 680a45f2d05SWarner Losh20010517: 681a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 682a45f2d05SWarner Losh userland at the same time. 683a45f2d05SWarner Losh 684a45f2d05SWarner Losh20010517: 685a45f2d05SWarner Losh New ncurses imported. 686a45f2d05SWarner Losh 6872988afcaSWarner Losh20010512: 6882988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 6892988afcaSWarner Losh will be the only way to go starting July 1. 6902988afcaSWarner Losh 6911a33dba7SWarner Losh20010504: 6921a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 6931a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 6941a33dba7SWarner Losh 69509946a51SWarner Losh20010502: 69609946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 69709946a51SWarner Losh 69809946a51SWarner Losh20010501: 69909946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 70009946a51SWarner Losh 70109946a51SWarner Losh20010430: 702a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 70309946a51SWarner Losh go back in the water. 70409946a51SWarner Losh 70509946a51SWarner Losh20010429: 70609946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 70709946a51SWarner Losh this date, but before the correction date. 70809946a51SWarner Losh 70991dd3b53SWarner Losh20010423: 71091dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 71191dd3b53SWarner Losh 71291dd3b53SWarner Losh20010411: 71391dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 71491dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 71591dd3b53SWarner Losh Update only if you understand that you must not use the old 71691dd3b53SWarner Losh fsck with the new kernel ever. 71791dd3b53SWarner Losh 718933b3269SWarner Losh20010330: 719933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 720c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 721933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 722933b3269SWarner Losh 723933b3269SWarner Losh20010319: 724933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 725933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 726933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 727f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 72809946a51SWarner Losh 72909946a51SWarner Losh20010315: 73009946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 731ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 73209946a51SWarner Losh been replaced by tunables. See ata.4 for details. 733933b3269SWarner Losh 734933b3269SWarner Losh20010312: 735933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 736933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 737933b3269SWarner Losh 738933b3269SWarner Losh20010312: 739933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 740933b3269SWarner Losh instead of ad-hoc. 741933b3269SWarner Losh 742933b3269SWarner Losh20010310: 743f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 744933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 745933b3269SWarner Losh ssh might not work if you don't. 746933b3269SWarner Losh 74762353691SWarner Losh20010303: 74862353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 74962353691SWarner Losh which means that you must include the miibus in your kernel if 75062353691SWarner Losh you use the ed driver. 75162353691SWarner Losh 752d325cf65SWarner Losh20010220: 753d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 754d325cf65SWarner Losh safe to go back into the water. 755d325cf65SWarner Losh 756024daae6SWarner Losh20010211: 757024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 758024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 759024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 760024daae6SWarner Losh that before upgrading would be a good time to do a level 0 761024daae6SWarner Losh dump of your system. No, really, I mean it this time. 762024daae6SWarner Losh 763024daae6SWarner Losh To get to the new system, you'll need to use the following 764024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 765024daae6SWarner Losh don't have to move this to the updating section. 766024daae6SWarner Losh 767024daae6SWarner Losh To get around the installworld problem, do: 768024daae6SWarner Losh # cd /usr/src/usr.bin/sed 769024daae6SWarner Losh # make install 770024daae6SWarner Losh # cd /usr/src 771024daae6SWarner Losh # make installworld 772024daae6SWarner Losh If that doesn't work, then try: 773024daae6SWarner Losh # make -k installworld 774024daae6SWarner Losh # make installworld 775024daae6SWarner Losh 776024daae6SWarner Losh20010207: 777024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 778024daae6SWarner Losh do not include devfs in your kernel as problems result. 779024daae6SWarner Losh 780024daae6SWarner Losh20010205: 7817595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 782024daae6SWarner Losh Remove them from your config. 783024daae6SWarner Losh 7841e159248SWarner Losh20010122: 7851e159248SWarner Losh ****************************** WARNING ****************************** 7861e159248SWarner Losh buildkernel has been changed slightly 7871e159248SWarner Losh ****************************** WARNING ****************************** 7881e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 7891e159248SWarner Losh should update your scripts and make.conf accordingly. 7901e159248SWarner Losh 7911e159248SWarner Losh20010119: 7921e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 7931e159248SWarner Losh This requires a new config to build correctly. 7941e159248SWarner Losh 795aac7dfeaSWarner Losh20010116: 796ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 797aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 798aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 799aac7dfeaSWarner Losh 800aac7dfeaSWarner Losh20010110: 801aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 802aac7dfeaSWarner Losh 803aac7dfeaSWarner Losh20010102: 804aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 805aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 806aac7dfeaSWarner Losh 80763c90c9eSWarner Losh20010101: 80863c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 80963c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 8105fd2a895SWarner Losh dump while building termcap. You can work around this problem 81163c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 81263c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 81363c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 81463c90c9eSWarner Losh might have been ignored by the -k option. 81563c90c9eSWarner Losh 8165fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 8175fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 8185fd2a895SWarner Losh of this working. 8195fd2a895SWarner Losh 820aac7dfeaSWarner Losh20001228: 821aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 822ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 823aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 824aac7dfeaSWarner Losh 825de2bcc63SWarner Losh20001218: 826de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 827de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 828de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 829de2bcc63SWarner Losh cards will not be recognized without it. 830de2bcc63SWarner Losh 831960773f7SWarner Losh20001205: 832960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 833960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 834960773f7SWarner Losh adding the following in pam.conf: 835960773f7SWarner Losh 836960773f7SWarner Losh sshd auth sufficient pam_skey.so 837960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 838960773f7SWarner Losh sshd session required pam_permit.so 839960773f7SWarner Losh 8400acc635eSWarner Losh20001031: 8410acc635eSWarner Losh cvs updated to 1.11. 8420acc635eSWarner Losh 8430acc635eSWarner Losh20001020: 8440acc635eSWarner Losh The random device needs more entropy, so you need to make sure 8450acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 8460acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 8470acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 8480acc635eSWarner Losh workaround. 8490acc635eSWarner Losh 8500acc635eSWarner Losh20001010: 8510acc635eSWarner Losh ****************************** WARNING ****************************** 8520acc635eSWarner Losh Sendmail has been updated. 8530acc635eSWarner Losh ****************************** WARNING ****************************** 8540acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 8550acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 8560acc635eSWarner Losh is set. 8570acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 8580acc635eSWarner Losh commands. 8590acc635eSWarner Losh o Now using sendmail's version of vacation(1). 8600acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 8610acc635eSWarner Losh in /usr/share/sendmail/cf. 8620acc635eSWarner Losh o sendmail.cw changed to local-host-names 8630acc635eSWarner Losh 8640acc635eSWarner Losh More details can be found at 8650acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 8660acc635eSWarner Losh 8676e98a146SWarner Losh20001009: 8686e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 8696e98a146SWarner Losh your entire ports tree, or you will have problems. 8706e98a146SWarner Losh 8716e98a146SWarner Losh20001006: 872685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 8736e98a146SWarner Losh the installed miniperl. It is recommended that you delete 8746e98a146SWarner Losh /usr/bin/miniperl. 8756e98a146SWarner Losh 876073113a4SWarner Losh20001005: 877073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 878685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 879073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 880073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 881073113a4SWarner Losh tree for anything to work. 882073113a4SWarner Losh 8830acc635eSWarner Losh20000928: 8840acc635eSWarner Losh There was a change in the passwd format. Need more information. 8850acc635eSWarner Losh 886be3885b3SWarner Losh20000916: 887be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 888be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 889be3885b3SWarner Losh same time as your kernel. 890be3885b3SWarner Losh 89176ec9675SWarner Losh20000914: 89276ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 89376ec9675SWarner Losh include the device will cause suspended laptops losing time 89476ec9675SWarner Losh when they resume. Include 89576ec9675SWarner Losh device pmtimer 89676ec9675SWarner Losh in your config file and 89701b9a434SWarner Losh hint.pmtimer.0.at="isa" 89876ec9675SWarner Losh to your /boot/device.hints file. 89976ec9675SWarner Losh 900f4865386SMark Murray20000911: 901f4865386SMark Murray The random device has been turned into a (pseudo-)device, 902f4865386SMark Murray rather than an option. The supplied kernel config files have 903f4865386SMark Murray been updated. You will need to do something similar in your 904f4865386SMark Murray own kernel config file. 905f4865386SMark Murray Remove: 906f4865386SMark Murray options RANDOMDEV 907f4865386SMark Murray Add: 908f4865386SMark Murray device random 909f4865386SMark Murray If you prefer to load the loadable module, you need to do 910f4865386SMark Murray nothing. 911f4865386SMark Murray 912d594498fSWarner Losh20000909: 913d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 914d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 915d594498fSWarner Losh reflect this if you load this module at boot time. 916d594498fSWarner Losh The line should read: 917d594498fSWarner Losh random_load="YES" 918d594498fSWarner Losh 9190deb7ddcSWarner Losh20000907: 9200deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 92116eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 92216eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 92316eb772dSWarner Losh sure you don't have model loading problems which might at 92416eb772dSWarner Losh first blush appear related to SMP. 92552bf24e7SWarner Losh 9265a01880bSWarner Losh20000906: 9275a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 9285a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 9295a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 9305a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 9315a01880bSWarner Losh don't have one, and you have host.conf. 9325a01880bSWarner Losh 9332b41163cSWarner Losh20000905: 93438d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 93538d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 93638d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 93738d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 93838d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 93938d6ecd2SWarner Losh 94038d6ecd2SWarner Losh20000905: 9418aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 9428aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 9438aab4bc7SWarner Losh is /boot/kernel. 9448aab4bc7SWarner Losh 9458aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 94638d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 94738d6ecd2SWarner Losh installkernel/installworld dance. 9482b41163cSWarner Losh 949d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 950d594498fSWarner Losh before booting the new kernel, since kldload will find stale 951d594498fSWarner Losh modules in that directory instead of finding them in the correct 952d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 953d594498fSWarner Losh is that the linux module crashes your machine after the update. 954d594498fSWarner Losh 955d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 956d594498fSWarner Losh mv /modules.old /boot/kernel.old 957d594498fSWarner Losh chflags noschg /kernel.old 958d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 959d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 960d594498fSWarner Losh fi 961d594498fSWarner Losh 962c22a309cSWarner Losh20000904: 963c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 964c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 965c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 966c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 967c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 968c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 969c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 970c22a309cSWarner Losh is not likely to be generated. 971c22a309cSWarner Losh 972fdb9f54dSWarner Losh20000825: 973fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 9749c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 9759c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 9769c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 9779c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 9789c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 9799c1a7444SWarner Losh messages will appear after the boot loader tries to start the 9809c1a7444SWarner Losh kernel. 9819c1a7444SWarner Losh 9829c1a7444SWarner Losh20000821: 9839c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 9849c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 9859c1a7444SWarner Losh /boot/loader.conf. 986fdb9f54dSWarner Losh 9878f250aa7SWarner Losh20000812: 9885da0d091SWarner Losh suidperl is now always built and installed on the system, but 9895da0d091SWarner Losh with permissions of 511. If you have applications that use 9905da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 9915da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 9925da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 9935da0d091SWarner Losh will fix this until the next build. 9945da0d091SWarner Losh 9955da0d091SWarner Losh20000812: 9968f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 9978f250aa7SWarner Losh visible changes that may immediately affect your configuration 9988f250aa7SWarner Losh include: 9998f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 10008f250aa7SWarner Losh - newaliases limited to root and trusted users 10018f250aa7SWarner Losh - MSA port (587) turned on by default 10028f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 10038f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 10048f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 10058f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 10068f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 10078f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 10088f250aa7SWarner Losh 100971c38472SWarner Losh20000810: 101071c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 101171c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 101271c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 101371c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 101471c38472SWarner Losh specific use for it. 101571c38472SWarner Losh 101671c38472SWarner Losh20000729: 101771c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 101871c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 101971c38472SWarner Losh /etc/rc.conf if they want to have the same setup 102071c38472SWarner Losh afterwards (unless the variables already are set, of course): 102171c38472SWarner Losh # Enable network daemons for user convenience. 102271c38472SWarner Losh inetd_enable="YES" 102371c38472SWarner Losh portmap_enable="YES" 102471c38472SWarner Losh sendmail_enable="YES" 102571c38472SWarner Losh 102671c38472SWarner Losh20000728: 102771c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 102871c38472SWarner Losh will need to change that to nullfs_load="YES". 102971c38472SWarner Losh 10301dece4a9SWarner Losh20000728: 10311dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 10321dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 10331dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 10341dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 10351dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 10361dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 10371dece4a9SWarner Losh to /MYKERNEL. 10381dece4a9SWarner Losh 1039409e887cSWarner Losh20000711: 1040409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1041409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1042409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1043409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1044409e887cSWarner Losh for details on potential problems that you might have and how 1045409e887cSWarner Losh to get around them. 1046409e887cSWarner Losh 1047409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1048409e887cSWarner Losh clauses above, you needn't worry. 1049409e887cSWarner Losh 1050409e887cSWarner Losh20000711: 1051409e887cSWarner Losh /etc/security has been updated to print the inode number of 1052409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1053409e887cSWarner Losh in the number of changed programs the first time when you run 1054409e887cSWarner Losh mergemaster to get a new /etc/security. 1055409e887cSWarner Losh 1056673d13f2SWarner Losh20000710: 1057673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1058673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1059673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1060673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1061673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1062673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1063673d13f2SWarner Losh errors. (see below, 20000624). 1064673d13f2SWarner Losh 1065bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 10661dece4a9SWarner Losh 1067673d13f2SWarner Losh20000709: 1068c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1069c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1070c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1071673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1072673d13f2SWarner Losh 1073e98e26cdSWarner Losh20000706: 1074e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1075e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1076e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1077f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1078e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 10792c021c6cSMark Ovens interim if needed. 1080e98e26cdSWarner Losh 1081e98e26cdSWarner Losh20000705: 1082e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1083e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1084e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1085e98e26cdSWarner Losh details. 1086e98e26cdSWarner Losh 1087c373950eSWarner Losh20000704: 10882f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 10892f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 10902f961bc8SWarner Losh 10912f961bc8SWarner Losh20000704: 1092c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1093c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1094c373950eSWarner Losh rc.d scripts that haven't been updated. 1095c373950eSWarner Losh 109627dc3a2bSWarner Losh20000630: 109727dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 109827dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 109927dc3a2bSWarner Losh which should be reported to des@freebsd.org. 110027dc3a2bSWarner Losh 1101b8c215acSWarner Losh20000625: 1102b8c215acSWarner Losh From approximately this date forward, one must have the crypto 110327dc3a2bSWarner Losh system installed in order to build the system and kernel. 110427dc3a2bSWarner Losh While not technically strictly true, one should treat it as 110527dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 110627dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 110727dc3a2bSWarner Losh were required. You should check with the latest collections 110827dc3a2bSWarner Losh to make sure that these haven't changed. 1109b8c215acSWarner Losh 11107b990719SWarner Losh20000624: 11117b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 11127b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 11137b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 11141a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 11157b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 11167b990719SWarner Losh openssh and openssl should not be used to generate keys from this 11177b990719SWarner Losh date to the completion of the work. 11187b990719SWarner Losh 111927dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 112027dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 112127dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 112227dc3a2bSWarner Losh recreate the random and urandom devices. 112327dc3a2bSWarner Losh 112481e54c50SWarner Losh20000622: 112581e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 112681e54c50SWarner Losh BSD license. You may need to remove your symbolic links 112781e54c50SWarner Losh that used to be required when updating. 112881e54c50SWarner Losh 112939943833SWarner Losh20000621: 11302c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 11312a2f33fbSDaniel Baker the config file update procedure. 11322a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1133c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 113459df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 113559df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 113639943833SWarner Losh 1137290f9ad8SWarner Losh20000620: 1138290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1139290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1140290f9ad8SWarner Losh that workaround will no longer be required. 1141290f9ad8SWarner Losh 114290fb6346SWarner Losh20000615: 114390fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 114490fb6346SWarner Losh ad driver. If you haven't done so already, you must update 114590fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 114690fb6346SWarner Losh devices. 114790fb6346SWarner Losh 1148f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1149f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1150f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1151f75f65bbSWarner Losh may work). 1152f75f65bbSWarner Losh 1153ba26da8eSWarner Losh20000612: 1154ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1155290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1156c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1157290f9ad8SWarner Losh to your config file to compile them in statically. The format 1158f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1159f54a3542SWarner Losh NEWCARD for examples of the new format. 1160290f9ad8SWarner Losh 11619698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 11629698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 11639698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 11649698f2c0SWarner Losh in it. 1165bbcc5149SWarner Losh 1166d65850ebSWarner Losh20000522: 1167ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1168d65850ebSWarner Losh building a kernel after this point is advised that they need 1169d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1170d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1171d65850ebSWarner Losh 1172d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1173d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1174d9583a00SWarner Losh is recommended that you don't set this option until the problem 1175d9583a00SWarner Losh is resolved. 1176d9583a00SWarner Losh 11778039cedeSWarner Losh20000513: 11788039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 11798039cedeSWarner Losh 1180d65850ebSWarner Losh20000510: 11818039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 11828039cedeSWarner Losh This will require some care in updating alphas. A new libstand 11838039cedeSWarner Losh is requires for the boot blocks to build properly. 11848039cedeSWarner Losh 11858039cedeSWarner Losh20000503: 11868039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 11878039cedeSWarner Losh is now available. 11888039cedeSWarner Losh 1189d65850ebSWarner Losh20000502: 1190d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1191d65850ebSWarner Losh connected to the kernel building instead. 1192d65850ebSWarner Losh 1193be149406SNik Clayton20000427: 11948039cedeSWarner Losh You may need to build gperf 11958039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 11968039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 11978039cedeSWarner Losh an option only in -current. 11988039cedeSWarner Losh 11992b8dd5f4SWarner Losh20000417: 12002b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1201f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 12022b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 12032b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 12042c021c6cSMark Ovens before you reboot, you'll need to issue: 12052b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 12062b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 12072b8dd5f4SWarner Losh 12088d9f1945SWarner Losh20000320: 12092b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 12102b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 12112b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1212ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 12132b8dd5f4SWarner Losh to the start of /etc/rc.conf. 12148d9f1945SWarner Losh 1215f8ab1dd6SWarner Losh20000319: 1216f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1217f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1218f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1219f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1220f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1221f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1222f8ab1dd6SWarner Losh 122319cada77SWarner Losh20000318: 1224f699bbbbSMark Ovens We've entered the traditional post release dumping party. 122519cada77SWarner Losh Large kernel changes are being committed and are in the 122619cada77SWarner Losh works. It is important to keep the systems' klds and kernel 122719cada77SWarner Losh in sync as kernel interfaces and structures are changing. 122819cada77SWarner Losh Before reporting kernel panics, make sure that all modules 122919cada77SWarner Losh that you are loading are up to date. 1230ba228352SWarner Losh 123119cada77SWarner Losh20000315: 12326d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 12336d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 12346d23c382SWarner Losh will do the trick. This isn't critical until you remove your 12356d23c382SWarner Losh wd device entries in /dev, at which point your system will not 12366d23c382SWarner Losh boot. 12376d23c382SWarner Losh 12386d23c382SWarner Losh20000315: 123919cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 124019cada77SWarner Losh to upgrade to 4.0 from 3.x. 124157199806SWarner Losh 1242dc0dbf5cSWarner LoshCOMMON ITEMS: 1243dc0dbf5cSWarner Losh 1244a24eff53SWarner Losh General Notes 1245a24eff53SWarner Losh ------------- 1246a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1247a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1248a24eff53SWarner Losh installworld. This is especially true when upgrading between 1249a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1250a24eff53SWarner Losh or several minor releases, or when several months have passed 1251a24eff53SWarner Losh on the -current branch). 1252a24eff53SWarner Losh 12535780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 12545780f3baSWarner Losh poisoning. This can happen because the make utility reads its 12555780f3baSWarner Losh environment when searching for values for global variables. 12565780f3baSWarner Losh To run your build attempts in an "environmental clean room", 12575780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 12585780f3baSWarner Losh page for more details. 12595780f3baSWarner Losh 1260dc0dbf5cSWarner Losh To build a kernel 1261dc0dbf5cSWarner Losh ----------------- 1262ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1263f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1264ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1265282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1266282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1267dc0dbf5cSWarner Losh 1268ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1269ba01eb20SWarner Losh -------------------------------------------------------------- 1270ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 127147d0d01fSWarner Losh config KERNEL_NAME_HERE 1272ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1273ba01eb20SWarner Losh make depend 1274ba01eb20SWarner Losh make 1275ba01eb20SWarner Losh make install 1276ba01eb20SWarner Losh 1277ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1278ba01eb20SWarner Losh 1279ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1280ba01eb20SWarner Losh ----------------------------------------------------------- 128163cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 128263cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 128363cb445eSWarner Losh 1284f643de42SWarner Losh <make sure you have good level 0 dumps> 128563cb445eSWarner Losh <maybe fix /etc/fstab> [7] 128663cb445eSWarner Losh make buildworld 128763cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 128863cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 128963cb445eSWarner Losh [1] 129063cb445eSWarner Losh <reboot in single user> [3] 129163cb445eSWarner Losh mergemaster -p [5] 129263cb445eSWarner Losh make installworld 129363cb445eSWarner Losh mergemaster [4] 129463cb445eSWarner Losh <reboot> 129563cb445eSWarner Losh 1296759f0aefSWarner Losh 1297f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1298f27b1fceSJoseph Koshy -------------------------------------------------- 1299f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1300f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1301f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1302f27b1fceSJoseph Koshy # size. 1303f27b1fceSJoseph Koshy 1304f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1305f27b1fceSJoseph Koshy <boot into -stable> 1306f27b1fceSJoseph Koshy make buildworld 1307f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1308f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1309f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1310f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1311f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1312f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1313f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1314f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1315f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1316f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1317f27b1fceSJoseph Koshy <reboot into current> 1318f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1319f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1320f27b1fceSJoseph Koshy <reboot> 1321f27b1fceSJoseph Koshy 1322f27b1fceSJoseph Koshy 1323f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1324f27b1fceSJoseph Koshy ---------------------------------------------- 13255c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 13265c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 13275c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 13285c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1329ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1330f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1331f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1332f643de42SWarner Losh # space on /. 1333f643de42SWarner Losh 1334f643de42SWarner Losh <make sure you have good level 0 dumps> 1335fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 133621c075eaSWarner Losh make buildworld [9] 1337c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1338d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1339be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1340fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1341fc8c157fSWarner Losh [1] 1342fc8c157fSWarner Losh <reboot in single user> [3] 1343835284beSWarner Losh mergemaster -p [5] 1344f8a4c901SWarner Losh rm -rf /usr/include/g++ 1345ba26da8eSWarner Losh make installworld 1346a6cd4f9dSWarner Losh mergemaster [4] 1347ba26da8eSWarner Losh <reboot> 1348ba26da8eSWarner Losh 1349fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1350fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1351fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1352fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1353fdb9f54dSWarner Losh the UPDATING entries. 1354ba26da8eSWarner Losh 13551dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 13561dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 13571dece4a9SWarner Losh your sources that you have read and understood all the recent 13581dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 13591dece4a9SWarner Losh much fewer pitfalls. 13601dece4a9SWarner Losh 1361134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1362134d2e86SWarner Losh should disable them at this point so they don't crash your 1363134d2e86SWarner Losh system on reboot. 1364134d2e86SWarner Losh 13659c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 13669c1a7444SWarner Losh your own device.hints to reflect your unique hardware 13679c1a7444SWarner Losh configuration. 13689c1a7444SWarner Losh 1369ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1370ee6e1fc3SWarner Losh fsck -p 1371ee6e1fc3SWarner Losh mount -u / 1372ee6e1fc3SWarner Losh mount -a 1373ee6e1fc3SWarner Losh cd /usr/src 137447d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1375f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1376f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1377b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1378b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1379b705ae10SWarner Losh be ignored while you proceed to the next step. 1380ee6e1fc3SWarner Losh 1381a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1382a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1383a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1384a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1385a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1386a6cd4f9dSWarner Losh for potential gotchas. 1387a6cd4f9dSWarner Losh 1388835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1389835284beSWarner Losh you may need to do this if you get unknown user in the following 1390835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1391835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1392835284beSWarner Losh install) after the buildworld before this step if you last updated 1393835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1394835284beSWarner Losh 1395bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1396bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1397bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1398bd79cf40SWarner Losh ok unload 1399bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1400bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1401bd79cf40SWarner Losh described here. 1402fc8c157fSWarner Losh 1403fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1404fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1405fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1406fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1407fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1408fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1409fc8c157fSWarner Losh 1410c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1411c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1412c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1413c74fe6afSWarner Losh that is hard to boot to recover. 1414c74fe6afSWarner Losh 141521c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 141621c075eaSWarner Losh cvs prune empty directories. 1417dc0dbf5cSWarner LoshFORMAT: 1418dc0dbf5cSWarner Losh 1419f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 14201fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1421f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1422f8ab1dd6SWarner Loshprevious releases if your system is older than this. 14231fc1a0dcSWarner Losh 1424e72fd46aSWarner LoshCopyright information: 1425e72fd46aSWarner Losh 14269698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1427e72fd46aSWarner Losh 1428772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1429772730c7SWarner Loshmodification, in full or in part, in any form or format of this 14309698f2c0SWarner Loshdocument are permitted without further permission from the author. 1431e72fd46aSWarner Losh 1432e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1433e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1434e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1435e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1436e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1437e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1438e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1439e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1440e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1441e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1442e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1443e72fd46aSWarner Losh 1444e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1445e72fd46aSWarner Loshauthor a beer. 1446e72fd46aSWarner Losh 144722306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1448772730c7SWarner Loshthis document. 1449772730c7SWarner Losh 145097d92980SPeter Wemm$FreeBSD$ 1451