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 208ad1f5e4SHartmut Brandt20031112: 2130093b05SWarner Losh The statfs structure has been updated with 64-bit fields to 2230093b05SWarner Losh allow accurate reporting of multi-terabyte filesystem 2330093b05SWarner Losh sizes. You should build and boot a new kernel BEFORE doing a 2430093b05SWarner Losh `make world' as the new kernel will know about binaries using 2530093b05SWarner Losh the old statfs structure, but an old kernel will not know 2630093b05SWarner Losh about the new system calls that support the new statfs 273f631d52SMarcel Moolenaar structure. 283f631d52SMarcel Moolenaar Note that the backwards compatibility is only present when the 293f631d52SMarcel Moolenaar kernel is configured with the COMPAT_FREEBSD4 option. Since 303f631d52SMarcel Moolenaar even /bin/sh will not run with a new kernel without said option 313f631d52SMarcel Moolenaar you're pretty much dead in the water without it. Make sure you 323f631d52SMarcel Moolenaar have COMPAT_FREEBSD4! 333f631d52SMarcel Moolenaar Running an old kernel after a `make world' will cause programs 343f631d52SMarcel Moolenaar such as `df' that do a statfs system call to fail with a bad 353f631d52SMarcel Moolenaar system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 363f631d52SMarcel Moolenaar that cfsd (ports/security/cfs) needs to be recompiled after 373f631d52SMarcel Moolenaar these changes are installed. 3830093b05SWarner Losh 3930093b05SWarner Losh ****************************DANGER******************************* 4030093b05SWarner Losh 4130093b05SWarner Losh DO NOT make installworld after the buildworld w/o building and 4230093b05SWarner Losh installing a new kernel FIRST. You will be unable to build a 4330093b05SWarner Losh new kernel otherwise on a system with new binaries and an old 4430093b05SWarner Losh kernel. 4564a18d6fSKirk McKusick 4664a18d6fSKirk McKusick20031112: 478ad1f5e4SHartmut Brandt Some netgraph string length constants have been changed. This 488ad1f5e4SHartmut Brandt change requires the netgraph kernel modules and all netgraph 498ad1f5e4SHartmut Brandt userland components to be in sync. Especially users who require 508ad1f5e4SHartmut Brandt netgraph to boot need to make sure to have world and kernel in 518ad1f5e4SHartmut Brandt sync before rebooting. 528ad1f5e4SHartmut Brandt 538bf455a5SJohn Baldwin20031103: 548bf455a5SJohn Baldwin The i386 APIC_IO kernel option has been replaced by 558bf455a5SJohn Baldwin 'device apic'. The ACPI module has also been temporarily 562a2cfa95SCeri Davies disabled, so ACPI must be statically compiled into your 578bf455a5SJohn Baldwin kernel using 'device acpi' if you wish to use the ACPI driver. 588bf455a5SJohn Baldwin 599bf40edeSBrooks Davis20031031: 609bf40edeSBrooks Davis The API and ABI of struct ifnet have been changed by removing 619bf40edeSBrooks Davis the if_name and if_unit members and replacing them with 629bf40edeSBrooks Davis if_xname, if_dname, and if_dunit. All network drivers and most 639bf40edeSBrooks Davis userland programs which include net/if_var.h must be updated 649bf40edeSBrooks Davis and recompiled. __FreeBSD_version has been bumped to 501113 to 659bf40edeSBrooks Davis reflect this change. 669bf40edeSBrooks Davis 6747a42c7aSPoul-Henning Kamp20030928: 6847a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 6947a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 7047a42c7aSPoul-Henning Kamp __FreeBSD_version bumpted to 501110. 7147a42c7aSPoul-Henning Kamp 7207105342SMax Khon20030926: 7307105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 7407105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 7507105342SMax Khon 7617dcd026SSam Leffler20030925: 7717dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 7817dcd026SSam Leffler also be explicitly configured. Previously this dependency was 7917dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 8017dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 8117dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 8217dcd026SSam Leffler 83fedf1d01SBruce M Simpson20030923: 84fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 85fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 86fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 87fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 88fedf1d01SBruce M Simpson 89db38f9cbSJacques Vidrine20030915: 90db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 91db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 92db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 93db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 94db38f9cbSJacques Vidrine 95c09d2c2bSMike Makonnen20030829: 96c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 97c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 98c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 99c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 100c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 101c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 102c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 103c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 104c09d2c2bSMike Makonnen may or may not exist on your system. 105c09d2c2bSMike Makonnen 10617c159dcSSøren Schmidt20030824: 10717c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 10817c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 109f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 110f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 11117c159dcSSøren Schmidt 112c1f61aa9SDavid E. O'Brien20030819: 113c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 114c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 115c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 116c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 11769f7bcf3SWarner Losh 11838c962e7SNate Lawson20030728: 11938c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 12038c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 12138c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 12238c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 12338c962e7SNate Lawson so the quirk can be re-enabled. 12438c962e7SNate Lawson 125178cf4e9SWarner Losh20030722: 126178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 127178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 128178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 129178cf4e9SWarner Losh FPU hardware. 130178cf4e9SWarner Losh 131178cf4e9SWarner Losh20030714: 132178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 133178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 134178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 135178cf4e9SWarner Losh People should report those issues to current@. 136178cf4e9SWarner Losh 137157c629aSWarner Losh20030711: 138157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 1398b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 14005538fa9SWarner Losh /usr/obj. 141157c629aSWarner Losh 1426cc6353fSMarcel Moolenaar20030613: [retrospective] 1436cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 1446cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 1456cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 1466cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 1476cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 1486cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 1496cc6353fSMarcel Moolenaar 1506cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 1516cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 1526cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 1536cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 1546cc6353fSMarcel Moolenaar : 1556cc6353fSMarcel Moolenaar 1566cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 1576cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 1586cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 1596cc6353fSMarcel Moolenaar 160766c34e4SAndrey A. Chernov20030610: 161766c34e4SAndrey A. Chernov Remove deprecated locale names and transition period code 162766c34e4SAndrey A. Chernov for them, finishing switching to the new scheme. Check your 163766c34e4SAndrey A. Chernov LANG environment variable. 164766c34e4SAndrey A. Chernov 1657ddc2528SPoul-Henning Kamp20030609: 166df622d54SPoul-Henning Kamp CCD has been changed to be a fully GEOMified class. Kernel 167df622d54SPoul-Henning Kamp and ccdconfig(8) needs to be in sync, this is particularly 168df622d54SPoul-Henning Kamp important to remember beforehand if your source tree is on 169df622d54SPoul-Henning Kamp a ccd device. Consider making a copy of the old ccdconfig 170df622d54SPoul-Henning Kamp into /boot/kernel.good or wherever you keep your backup 171df622d54SPoul-Henning Kamp kernel. 172df622d54SPoul-Henning Kamp 17352b47445SMark Murray20030505: 17452b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 17552b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 17652b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 17752b47445SMark Murray 178a26df538SWarner Losh20030502: 179a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 180a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 181a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 182a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 183a26df538SWarner Losh 1844b065e2cSDoug Barton20030501: 1854b065e2cSDoug Barton The old rc system has been removed. Please report any problems 1864b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 1874b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 1884b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 1894b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 1904b065e2cSDoug Barton utilizes these old scripts has also been removed. 1914b065e2cSDoug Barton 19281cda3d9SWarner Losh20030423: 19381cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 19481cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 19581cda3d9SWarner Losh work around in devd will be removed around 20030507. You 19681cda3d9SWarner Losh have until then to upgrade your kernel before updating 19781cda3d9SWarner Losh userland. In general, you should have a userland and 19881cda3d9SWarner Losh kernel that's in sync with each other. However, given the 19981cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 20081cda3d9SWarner Losh allowances are made. 20181cda3d9SWarner Losh 20247a657d1SRuslan Ermilov20030329: 20347a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 20447a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 20547a657d1SRuslan Ermilov while upgrading the system through a buildworld. 20647a657d1SRuslan Ermilov 20747a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 20847a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 20947a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 21047a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 21147a657d1SRuslan Ermilov 21247a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 21347a657d1SRuslan Ermilov make cleandir && make obj && \ 21447a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 21547a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 21647a657d1SRuslan Ermilov 2175d2af00cSGregory Neil Shapiro20030208: 2185d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 2195d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 2205d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 2215d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 2225d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 2235d2af00cSGregory Neil Shapiro 2245d2af00cSGregory Neil Shapiro20030128: 2259db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 226ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 2279db58771SPoul-Henning Kamp be removed when convenient. 2289db58771SPoul-Henning Kamp 2298d9b3f57SJake Burkholder20030126: 2308d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 2318d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 2328d9b3f57SJake Burkholder 2331c5efda5SJeff Roberson20030125: 2341c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 2351c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 236ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 2371c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 2381c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 2391c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 2401c5efda5SJeff Roberson 2419d1d64f5SWarner Losh20030115: 2429d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 2439d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 2449d1d64f5SWarner Losh properly. 2459d1d64f5SWarner Losh 246c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 247c9fdb80aSWarner Losh configured for point to point links to bring it more in line 248c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 249c9fdb80aSWarner Losh with NetBSD. 250c9fdb80aSWarner Losh 251161dc364SAlexander Kabaev20021222: 252161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 253161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 254161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 255161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 256161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 257161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 25884cc83efSAlexander Kabaev rebuilt. 259161dc364SAlexander Kabaev 260fb4c8061SMartin Blapp20021216: 261fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 26289056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 263fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 2649d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 265fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 266fb4c8061SMartin Blapp 26717d47eb3SGiorgos Keramidas20021202: 26817d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 26917d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 27017d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 27117d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 27217d47eb3SGiorgos Keramidas 273a4459294SBill Fenner20021029: 274a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 275a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 276a4459294SBill Fenner consumers in sync. 277a4459294SBill Fenner 278fc8c157fSWarner Losh20021024: 279c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 280c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 281c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 282c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 283c57404feSRuslan Ermilov partition really is on. The old device names have gone 284c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 285c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 286c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 28769f7bcf3SWarner Losh 288fd9e8bdaSAndrew Gallatin20021023: 289fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 290fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 291fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 292fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 293fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 294fd9e8bdaSAndrew Gallatin 295fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 296fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 297fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 298fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 299fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 300fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 301fd9e8bdaSAndrew Gallatin 302f8a4c901SWarner Losh20020831: 303f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 304f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 305f8a4c901SWarner Losh programs and libraries need to be recompiled. 306f8a4c901SWarner Losh 307f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 308f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 309f8a4c901SWarner Losh 310c2248fa2SJens Schweikhardt20020827: 311c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 312c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 313c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 314c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 315c2248fa2SJens Schweikhardt 3160d533e43SRuslan Ermilov20020815: 3170d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 3180d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 3190d533e43SRuslan Ermilov again. 3200d533e43SRuslan Ermilov 32133c1de7dSRuslan Ermilov20020729: 32233c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 32333c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 32433c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 32533c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 32633c1de7dSRuslan Ermilov 3272b877facSJulian Elischer20020702: 3282b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 3292b877facSJulian Elischer There are still some minor problems with some signals but the 3302b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 3312b877facSJulian Elischer but each can successfully complete multiple buildworlds. 3322b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 3332b877facSJulian Elischer 33406596d37SWarner Losh20020701: 33506596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 33606596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 33706596d37SWarner Losh GNOME. 33806596d37SWarner Losh 33995ba4330SJacques Vidrine20020511: 34095ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 34195ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 34295ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 34395ba4330SJacques Vidrine with the set-user-ID bit set. 34495ba4330SJacques Vidrine 345a81da3c9SDavid E. O'Brien20020510: 346f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 347f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 3484b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 349f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 350f50caf6fSDavid E. O'Brien 351f50caf6fSDavid E. O'Brien20020510: 352a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 353a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 354a81da3c9SDavid E. O'Brien and then do a cvs update. 355a81da3c9SDavid E. O'Brien 356528a0ef5SJacques Vidrine20020421: 357528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 358528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 359528a0ef5SJacques Vidrine 36085aa5a2eSGregory Neil Shapiro20020404: 36185aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 36285aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 36385aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 36485aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 36585aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 36685aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 36785aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 36885aa5a2eSGregory Neil Shapiro 3698f1e4358SRuslan Ermilov20020403: 3708f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 3718f1e4358SRuslan Ermilov 3722292c02eSWarner Losh20020315: 3732292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 3742292c02eSWarner Losh 37569f7bcf3SWarner Losh20020225: 37669f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 37769f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 37869f7bcf3SWarner Losh 3798f35c493SWarner Losh20020217: 3808f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 3818f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 3828f35c493SWarner Losh command line mail submission has changed. Be sure to run 3838f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 3848f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 3858f35c493SWarner Losh 386835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 387835284beSWarner Losh required in order for sendmail to run as a set-group-ID 388835284beSWarner Losh binary. A 'make installworld' will use the new user and group 389835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 390835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 391835284beSWarner Losh and group must be merged from src/etc/group and 392835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 393835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 394835284beSWarner Losh mergemaster before this will work if you are updating from a 395835284beSWarner Losh very old version of current. The updating recipe has changed 396835284beSWarner Losh as of this date. 397835284beSWarner Losh 398fa9401c1SWarner Losh20020112: 399fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 400fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 401fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 402fa9401c1SWarner Losh you have local modifications, you can use 403fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 404fa9401c1SWarner Losh /etc/pam.d. 405fa9401c1SWarner Losh 406fa9401c1SWarner Losh Please see the following url for more details: 407fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 40847d0d01fSWarner Losh20011229: 40947d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 41047d0d01fSWarner Losh networkfs_types, please note that it has changed 41147d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 41247d0d01fSWarner Losh 413514318a8SWarner Losh20011220: 414514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 415514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 416514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 417514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 418514318a8SWarner Losh version have now been merged back into the base system's 419514318a8SWarner Losh version now. The only user-visible change resulting from this 420514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 421514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 422514318a8SWarner Losh as well. (There has never been rc file support for 423514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 424514318a8SWarner Losh reverted by the time the changes are MFCed.) 425514318a8SWarner Losh 426514318a8SWarner Losh20011215: 427514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 428514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 429514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 430514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 431514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 432514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 433514318a8SWarner Losh will need to be customized then for `odd' densities using 434514318a8SWarner Losh fdcontrol(8). 435514318a8SWarner Losh 4362d22e2bfSWarner Losh20011209: 4372d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 4382d22e2bfSWarner Losh and truss(1) now works again. 4392d22e2bfSWarner Losh 4409e0428e2SWarner Losh20011207: 4419e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 4429e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 4439e0428e2SWarner Losh see 4449e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 4459e0428e2SWarner Losh for details. 4469e0428e2SWarner Losh 4479bab8c59SWarner Losh20011204: 4489bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 4499bab8c59SWarner Losh kernel and burncd to be in sync. 4509bab8c59SWarner Losh 451e57d8b01SWarner Losh20011203: 452e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 453e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 454e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 455e57d8b01SWarner Losh not there already. 456e57d8b01SWarner Losh 457e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 458e57d8b01SWarner Losh until the issue has been resolved. 459e57d8b01SWarner Losh 460b001d36fSJacques Vidrine20011202: 461b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 462b001d36fSJacques Vidrine patched. 463b001d36fSJacques Vidrine 4644b676ec1SWarner Losh20011126: 4654b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 4665ebbf43eSWarner Losh after this date. You need to do this only once. 4674b676ec1SWarner Losh 468d961e462SWarner Losh20011103: 469d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 470d961e462SWarner Losh edges may be left, but for the most part things should be 4714b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 472d961e462SWarner Losh 473d961e462SWarner Losh20011030: 474d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 475d961e462SWarner Losh choppy waves in the upgrade process. 476d961e462SWarner Losh 4771fe003b6SWarner Losh20011030: 478a4b6fda0SWarner Losh The asr driver problem has been resolved. 4791fe003b6SWarner Losh 4801fe003b6SWarner Losh20011027: 4811fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 4821fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 4831fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 4841fe003b6SWarner Losh try to use from this date forward. 4851fe003b6SWarner Losh 4861fe003b6SWarner Losh20011025: 4871fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 4881fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 4891fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 4901fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 4911fe003b6SWarner Losh TARGET_ARCH=i386. 4921fe003b6SWarner Losh 493d05f9643SWarner Losh20011001: 494d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 495d05f9643SWarner Losh You must recompile both the kernel and userland applications 496d05f9643SWarner Losh at the same time. 497d05f9643SWarner Losh 49858970f85SWarner Losh20010929: 49958970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 50058970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 50158970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 50258970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 5039d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 50458970f85SWarner Losh 50558970f85SWarner Losh20010927: 50658970f85SWarner Losh Some weird problems result from using ACPI on some machines. 50758970f85SWarner Losh To disable ACPI you can add 50866ff0e67SMax Khon hint.acpi.0.disabled="1" 50958970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 51058970f85SWarner Losh loader "ok" prompt). 51158970f85SWarner Losh 51258970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 51358970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 51458970f85SWarner Losh file and not list acpi in that list. 515378f4486SAlfred Perlstein 5165119d237SWarner Losh20010924: 5175119d237SWarner Losh The buildworld has been fixed. You may need to install 5185119d237SWarner Losh the 4.x compatibility libraries for some old binaries 5198b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 5208b039fffSWarner Losh get them installed on every installworld, or execute the 5218b039fffSWarner Losh following to get them installed only once: 5228b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 52358970f85SWarner Losh make all install 5248b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 5255119d237SWarner Losh 5263c293725SWarner Losh20010919: 5273c293725SWarner Losh There's a bug in the world build process. The cross-tools 5283c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 5293c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 530772730c7SWarner Losh workaround is to add 5313c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 5323c293725SWarner Losh before building world when upgrading from 4.x to current. This 5333c293725SWarner Losh can be removed afterwards. 5343c293725SWarner Losh 5353c293725SWarner Losh A proper fix to the buildworld target is needed. 5363c293725SWarner Losh 5373c293725SWarner Losh20010918: 5383c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 5393c293725SWarner Losh NFS may be unstable after this date. 5403c293725SWarner Losh 5413c293725SWarner Losh20010912: 5423c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 5433c293725SWarner Losh the kernel. While a few problems were introduced in the 5443c293725SWarner Losh initial commit, most of the major ones have been found and 5453c293725SWarner Losh corrected. 5463c293725SWarner Losh 5473c293725SWarner Losh20010901: 5483c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 5493c293725SWarner Losh arounds described in the 20010604 entry are now no longer 5503c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 5513c293725SWarner Losh have been rectified around this date. 5523c293725SWarner Losh 55398b17b95SWarner Losh20010823: 55498b17b95SWarner Losh named now runs as user bind and group bind rather than as 55598b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 55698b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 55798b17b95SWarner Losh and that group bind is available in /etc/group. Also make 55898b17b95SWarner Losh sure that user or group bind has read (and not write) 55998b17b95SWarner Losh permission for your name server configuration and that it 56098b17b95SWarner Losh has read and write permission for your slave zone files and 56198b17b95SWarner Losh directory. 56298b17b95SWarner Losh 56398b17b95SWarner Losh If you wish to continue to run named as root (a less secure 56498b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 56598b17b95SWarner Losh 56698b17b95SWarner Losh named_flags= 56798b17b95SWarner Losh 5687b9786edSMark Murray20010709: 5697b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 5707b9786edSMark Murray the ability of the shared library major number to handle. 5717b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 5727b9786edSMark Murray solution is to rebuild those ports. 5737b9786edSMark Murray 5741d28950eSWarner Losh20010628: 5751d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 5761d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 5771d28950eSWarner Losh 578e72fd46aSWarner Losh20010625: 57998b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 58098b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 58198b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 58298b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 58398b17b95SWarner Losh IRQ configuration needs more safety belts. 58416de1a07SWarner Losh 5850d415dffSWarner Losh20010617: 586e72fd46aSWarner Losh Softupdates problems have been corrected. 5870d415dffSWarner Losh 5880d415dffSWarner Losh20010614: 5890d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 5900d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 5910d415dffSWarner Losh kernel building methods. 5920d415dffSWarner Losh 5938b9959adSWarner Losh20010613: 5948b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 5958b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 596e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 597e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 5988b9959adSWarner Losh 599e72fd46aSWarner Losh20010613: 6008b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 601e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 602e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 6038b9959adSWarner Losh 6040d415dffSWarner Losh20010612: 6050d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 6060d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 6070d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 6080d415dffSWarner Losh work around this issue, please use only one or the other mechanism 6090d415dffSWarner Losh until this bug is fixed. 6100d415dffSWarner Losh 611e72fd46aSWarner Losh Please note that a feature of config is that if you have config 612e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 613ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 614e72fd46aSWarner Losh 6150d415dffSWarner Losh20010610: 6160d415dffSWarner Losh Locale names have changed to match other systems better. 6170d415dffSWarner Losh 6186ccdb5e4SWarner Losh20010604: 6196ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 6206ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 6216ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 6223590182eSWarner Losh Interrupt storms look a lot like a hang. 6233590182eSWarner Losh 6243590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 6253590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 6263590182eSWarner Losh it is). 6273590182eSWarner Losh 6283590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 6293590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 6303590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 6313590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 6326ccdb5e4SWarner Losh 6330bc62786SWarner Losh20010530: 6340bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 6350bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 6360bc62786SWarner Losh a limited time. If you see 6370bc62786SWarner Losh 6380bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 6390bc62786SWarner Losh 6400bc62786SWarner Losh in your makeworld, then you need to migrate towards using 6410bc62786SWarner Losh COPY=-C. 6420bc62786SWarner Losh 64368a38c6cSWarner Losh20010525: 644b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 645c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 646c4f4a728SWarner Losh definitely is in bad shape. 64768a38c6cSWarner Losh 648ed0f29caSWarner Losh20010521: 649ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 650ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 651ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 652ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 653ed0f29caSWarner Losh is 654ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 655ed0f29caSWarner Losh 65680c16af9SWarner Losh20010520: 65768a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 65880c16af9SWarner Losh 65980c16af9SWarner Losh20010519: 66080c16af9SWarner Losh pccard has had much reorganizational work done to it over 66180c16af9SWarner Losh the past few days. Everything should still work, but if 66280c16af9SWarner Losh not, please contact imp@freebsd.org. 66380c16af9SWarner Losh 664a45f2d05SWarner Losh20010517: 665a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 666a45f2d05SWarner Losh userland at the same time. 667a45f2d05SWarner Losh 668a45f2d05SWarner Losh20010517: 669a45f2d05SWarner Losh New ncurses imported. 670a45f2d05SWarner Losh 6712988afcaSWarner Losh20010512: 6722988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 6732988afcaSWarner Losh will be the only way to go starting July 1. 6742988afcaSWarner Losh 6751a33dba7SWarner Losh20010504: 6761a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 6771a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 6781a33dba7SWarner Losh 67909946a51SWarner Losh20010502: 68009946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 68109946a51SWarner Losh 68209946a51SWarner Losh20010501: 68309946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 68409946a51SWarner Losh 68509946a51SWarner Losh20010430: 686a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 68709946a51SWarner Losh go back in the water. 68809946a51SWarner Losh 68909946a51SWarner Losh20010429: 69009946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 69109946a51SWarner Losh this date, but before the correction date. 69209946a51SWarner Losh 69391dd3b53SWarner Losh20010423: 69491dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 69591dd3b53SWarner Losh 69691dd3b53SWarner Losh20010411: 69791dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 69891dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 69991dd3b53SWarner Losh Update only if you understand that you must not use the old 70091dd3b53SWarner Losh fsck with the new kernel ever. 70191dd3b53SWarner Losh 702933b3269SWarner Losh20010330: 703933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 704c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 705933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 706933b3269SWarner Losh 707933b3269SWarner Losh20010319: 708933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 709933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 710933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 711f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 71209946a51SWarner Losh 71309946a51SWarner Losh20010315: 71409946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 715ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 71609946a51SWarner Losh been replaced by tunables. See ata.4 for details. 717933b3269SWarner Losh 718933b3269SWarner Losh20010312: 719933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 720933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 721933b3269SWarner Losh 722933b3269SWarner Losh20010312: 723933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 724933b3269SWarner Losh instead of ad-hoc. 725933b3269SWarner Losh 726933b3269SWarner Losh20010310: 727f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 728933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 729933b3269SWarner Losh ssh might not work if you don't. 730933b3269SWarner Losh 73162353691SWarner Losh20010303: 73262353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 73362353691SWarner Losh which means that you must include the miibus in your kernel if 73462353691SWarner Losh you use the ed driver. 73562353691SWarner Losh 736d325cf65SWarner Losh20010220: 737d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 738d325cf65SWarner Losh safe to go back into the water. 739d325cf65SWarner Losh 740024daae6SWarner Losh20010211: 741024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 742024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 743024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 744024daae6SWarner Losh that before upgrading would be a good time to do a level 0 745024daae6SWarner Losh dump of your system. No, really, I mean it this time. 746024daae6SWarner Losh 747024daae6SWarner Losh To get to the new system, you'll need to use the following 748024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 749024daae6SWarner Losh don't have to move this to the updating section. 750024daae6SWarner Losh 751024daae6SWarner Losh To get around the installworld problem, do: 752024daae6SWarner Losh # cd /usr/src/usr.bin/sed 753024daae6SWarner Losh # make install 754024daae6SWarner Losh # cd /usr/src 755024daae6SWarner Losh # make installworld 756024daae6SWarner Losh If that doesn't work, then try: 757024daae6SWarner Losh # make -k installworld 758024daae6SWarner Losh # make installworld 759024daae6SWarner Losh 760024daae6SWarner Losh20010207: 761024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 762024daae6SWarner Losh do not include devfs in your kernel as problems result. 763024daae6SWarner Losh 764024daae6SWarner Losh20010205: 7657595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 766024daae6SWarner Losh Remove them from your config. 767024daae6SWarner Losh 7681e159248SWarner Losh20010122: 7691e159248SWarner Losh ****************************** WARNING ****************************** 7701e159248SWarner Losh buildkernel has been changed slightly 7711e159248SWarner Losh ****************************** WARNING ****************************** 7721e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 7731e159248SWarner Losh should update your scripts and make.conf accordingly. 7741e159248SWarner Losh 7751e159248SWarner Losh20010119: 7761e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 7771e159248SWarner Losh This requires a new config to build correctly. 7781e159248SWarner Losh 779aac7dfeaSWarner Losh20010116: 780ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 781aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 782aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 783aac7dfeaSWarner Losh 784aac7dfeaSWarner Losh20010110: 785aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 786aac7dfeaSWarner Losh 787aac7dfeaSWarner Losh20010102: 788aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 789aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 790aac7dfeaSWarner Losh 79163c90c9eSWarner Losh20010101: 79263c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 79363c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 7945fd2a895SWarner Losh dump while building termcap. You can work around this problem 79563c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 79663c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 79763c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 79863c90c9eSWarner Losh might have been ignored by the -k option. 79963c90c9eSWarner Losh 8005fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 8015fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 8025fd2a895SWarner Losh of this working. 8035fd2a895SWarner Losh 804aac7dfeaSWarner Losh20001228: 805aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 806ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 807aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 808aac7dfeaSWarner Losh 809de2bcc63SWarner Losh20001218: 810de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 811de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 812de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 813de2bcc63SWarner Losh cards will not be recognized without it. 814de2bcc63SWarner Losh 815960773f7SWarner Losh20001205: 816960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 817960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 818960773f7SWarner Losh adding the following in pam.conf: 819960773f7SWarner Losh 820960773f7SWarner Losh sshd auth sufficient pam_skey.so 821960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 822960773f7SWarner Losh sshd session required pam_permit.so 823960773f7SWarner Losh 8240acc635eSWarner Losh20001031: 8250acc635eSWarner Losh cvs updated to 1.11. 8260acc635eSWarner Losh 8270acc635eSWarner Losh20001020: 8280acc635eSWarner Losh The random device needs more entropy, so you need to make sure 8290acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 8300acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 8310acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 8320acc635eSWarner Losh workaround. 8330acc635eSWarner Losh 8340acc635eSWarner Losh20001010: 8350acc635eSWarner Losh ****************************** WARNING ****************************** 8360acc635eSWarner Losh Sendmail has been updated. 8370acc635eSWarner Losh ****************************** WARNING ****************************** 8380acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 8390acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 8400acc635eSWarner Losh is set. 8410acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 8420acc635eSWarner Losh commands. 8430acc635eSWarner Losh o Now using sendmail's version of vacation(1). 8440acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 8450acc635eSWarner Losh in /usr/share/sendmail/cf. 8460acc635eSWarner Losh o sendmail.cw changed to local-host-names 8470acc635eSWarner Losh 8480acc635eSWarner Losh More details can be found at 8490acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 8500acc635eSWarner Losh 8516e98a146SWarner Losh20001009: 8526e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 8536e98a146SWarner Losh your entire ports tree, or you will have problems. 8546e98a146SWarner Losh 8556e98a146SWarner Losh20001006: 856685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 8576e98a146SWarner Losh the installed miniperl. It is recommended that you delete 8586e98a146SWarner Losh /usr/bin/miniperl. 8596e98a146SWarner Losh 860073113a4SWarner Losh20001005: 861073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 862685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 863073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 864073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 865073113a4SWarner Losh tree for anything to work. 866073113a4SWarner Losh 8670acc635eSWarner Losh20000928: 8680acc635eSWarner Losh There was a change in the passwd format. Need more information. 8690acc635eSWarner Losh 870be3885b3SWarner Losh20000916: 871be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 872be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 873be3885b3SWarner Losh same time as your kernel. 874be3885b3SWarner Losh 87576ec9675SWarner Losh20000914: 87676ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 87776ec9675SWarner Losh include the device will cause suspended laptops losing time 87876ec9675SWarner Losh when they resume. Include 87976ec9675SWarner Losh device pmtimer 88076ec9675SWarner Losh in your config file and 88101b9a434SWarner Losh hint.pmtimer.0.at="isa" 88276ec9675SWarner Losh to your /boot/device.hints file. 88376ec9675SWarner Losh 884f4865386SMark Murray20000911: 885f4865386SMark Murray The random device has been turned into a (pseudo-)device, 886f4865386SMark Murray rather than an option. The supplied kernel config files have 887f4865386SMark Murray been updated. You will need to do something similar in your 888f4865386SMark Murray own kernel config file. 889f4865386SMark Murray Remove: 890f4865386SMark Murray options RANDOMDEV 891f4865386SMark Murray Add: 892f4865386SMark Murray device random 893f4865386SMark Murray If you prefer to load the loadable module, you need to do 894f4865386SMark Murray nothing. 895f4865386SMark Murray 896d594498fSWarner Losh20000909: 897d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 898d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 899d594498fSWarner Losh reflect this if you load this module at boot time. 900d594498fSWarner Losh The line should read: 901d594498fSWarner Losh random_load="YES" 902d594498fSWarner Losh 9030deb7ddcSWarner Losh20000907: 9040deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 90516eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 90616eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 90716eb772dSWarner Losh sure you don't have model loading problems which might at 90816eb772dSWarner Losh first blush appear related to SMP. 90952bf24e7SWarner Losh 9105a01880bSWarner Losh20000906: 9115a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 9125a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 9135a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 9145a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 9155a01880bSWarner Losh don't have one, and you have host.conf. 9165a01880bSWarner Losh 9172b41163cSWarner Losh20000905: 91838d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 91938d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 92038d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 92138d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 92238d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 92338d6ecd2SWarner Losh 92438d6ecd2SWarner Losh20000905: 9258aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 9268aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 9278aab4bc7SWarner Losh is /boot/kernel. 9288aab4bc7SWarner Losh 9298aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 93038d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 93138d6ecd2SWarner Losh installkernel/installworld dance. 9322b41163cSWarner Losh 933d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 934d594498fSWarner Losh before booting the new kernel, since kldload will find stale 935d594498fSWarner Losh modules in that directory instead of finding them in the correct 936d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 937d594498fSWarner Losh is that the linux module crashes your machine after the update. 938d594498fSWarner Losh 939d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 940d594498fSWarner Losh mv /modules.old /boot/kernel.old 941d594498fSWarner Losh chflags noschg /kernel.old 942d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 943d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 944d594498fSWarner Losh fi 945d594498fSWarner Losh 946c22a309cSWarner Losh20000904: 947c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 948c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 949c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 950c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 951c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 952c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 953c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 954c22a309cSWarner Losh is not likely to be generated. 955c22a309cSWarner Losh 956fdb9f54dSWarner Losh20000825: 957fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 9589c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 9599c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 9609c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 9619c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 9629c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 9639c1a7444SWarner Losh messages will appear after the boot loader tries to start the 9649c1a7444SWarner Losh kernel. 9659c1a7444SWarner Losh 9669c1a7444SWarner Losh20000821: 9679c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 9689c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 9699c1a7444SWarner Losh /boot/loader.conf. 970fdb9f54dSWarner Losh 9718f250aa7SWarner Losh20000812: 9725da0d091SWarner Losh suidperl is now always built and installed on the system, but 9735da0d091SWarner Losh with permissions of 511. If you have applications that use 9745da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 9755da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 9765da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 9775da0d091SWarner Losh will fix this until the next build. 9785da0d091SWarner Losh 9795da0d091SWarner Losh20000812: 9808f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 9818f250aa7SWarner Losh visible changes that may immediately affect your configuration 9828f250aa7SWarner Losh include: 9838f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 9848f250aa7SWarner Losh - newaliases limited to root and trusted users 9858f250aa7SWarner Losh - MSA port (587) turned on by default 9868f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 9878f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 9888f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 9898f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 9908f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 9918f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 9928f250aa7SWarner Losh 99371c38472SWarner Losh20000810: 99471c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 99571c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 99671c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 99771c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 99871c38472SWarner Losh specific use for it. 99971c38472SWarner Losh 100071c38472SWarner Losh20000729: 100171c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 100271c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 100371c38472SWarner Losh /etc/rc.conf if they want to have the same setup 100471c38472SWarner Losh afterwards (unless the variables already are set, of course): 100571c38472SWarner Losh # Enable network daemons for user convenience. 100671c38472SWarner Losh inetd_enable="YES" 100771c38472SWarner Losh portmap_enable="YES" 100871c38472SWarner Losh sendmail_enable="YES" 100971c38472SWarner Losh 101071c38472SWarner Losh20000728: 101171c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 101271c38472SWarner Losh will need to change that to nullfs_load="YES". 101371c38472SWarner Losh 10141dece4a9SWarner Losh20000728: 10151dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 10161dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 10171dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 10181dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 10191dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 10201dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 10211dece4a9SWarner Losh to /MYKERNEL. 10221dece4a9SWarner Losh 1023409e887cSWarner Losh20000711: 1024409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 1025409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 1026409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 1027409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 1028409e887cSWarner Losh for details on potential problems that you might have and how 1029409e887cSWarner Losh to get around them. 1030409e887cSWarner Losh 1031409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 1032409e887cSWarner Losh clauses above, you needn't worry. 1033409e887cSWarner Losh 1034409e887cSWarner Losh20000711: 1035409e887cSWarner Losh /etc/security has been updated to print the inode number of 1036409e887cSWarner Losh setuid programs that have changed. You will see a large spike 1037409e887cSWarner Losh in the number of changed programs the first time when you run 1038409e887cSWarner Losh mergemaster to get a new /etc/security. 1039409e887cSWarner Losh 1040673d13f2SWarner Losh20000710: 1041673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 1042673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 1043673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 1044673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1045673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 1046673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1047673d13f2SWarner Losh errors. (see below, 20000624). 1048673d13f2SWarner Losh 1049bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 10501dece4a9SWarner Losh 1051673d13f2SWarner Losh20000709: 1052c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1053c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1054c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1055673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1056673d13f2SWarner Losh 1057e98e26cdSWarner Losh20000706: 1058e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1059e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1060e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1061f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1062e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 10632c021c6cSMark Ovens interim if needed. 1064e98e26cdSWarner Losh 1065e98e26cdSWarner Losh20000705: 1066e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1067e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1068e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1069e98e26cdSWarner Losh details. 1070e98e26cdSWarner Losh 1071c373950eSWarner Losh20000704: 10722f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 10732f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 10742f961bc8SWarner Losh 10752f961bc8SWarner Losh20000704: 1076c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1077c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1078c373950eSWarner Losh rc.d scripts that haven't been updated. 1079c373950eSWarner Losh 108027dc3a2bSWarner Losh20000630: 108127dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 108227dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 108327dc3a2bSWarner Losh which should be reported to des@freebsd.org. 108427dc3a2bSWarner Losh 1085b8c215acSWarner Losh20000625: 1086b8c215acSWarner Losh From approximately this date forward, one must have the crypto 108727dc3a2bSWarner Losh system installed in order to build the system and kernel. 108827dc3a2bSWarner Losh While not technically strictly true, one should treat it as 108927dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 109027dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 109127dc3a2bSWarner Losh were required. You should check with the latest collections 109227dc3a2bSWarner Losh to make sure that these haven't changed. 1093b8c215acSWarner Losh 10947b990719SWarner Losh20000624: 10957b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 10967b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 10977b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 10981a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 10997b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 11007b990719SWarner Losh openssh and openssl should not be used to generate keys from this 11017b990719SWarner Losh date to the completion of the work. 11027b990719SWarner Losh 110327dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 110427dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 110527dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 110627dc3a2bSWarner Losh recreate the random and urandom devices. 110727dc3a2bSWarner Losh 110881e54c50SWarner Losh20000622: 110981e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 111081e54c50SWarner Losh BSD license. You may need to remove your symbolic links 111181e54c50SWarner Losh that used to be required when updating. 111281e54c50SWarner Losh 111339943833SWarner Losh20000621: 11142c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 11152a2f33fbSDaniel Baker the config file update procedure. 11162a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1117c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 111859df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 111959df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 112039943833SWarner Losh 1121290f9ad8SWarner Losh20000620: 1122290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1123290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1124290f9ad8SWarner Losh that workaround will no longer be required. 1125290f9ad8SWarner Losh 112690fb6346SWarner Losh20000615: 112790fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 112890fb6346SWarner Losh ad driver. If you haven't done so already, you must update 112990fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 113090fb6346SWarner Losh devices. 113190fb6346SWarner Losh 1132f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1133f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1134f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1135f75f65bbSWarner Losh may work). 1136f75f65bbSWarner Losh 1137ba26da8eSWarner Losh20000612: 1138ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1139290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1140c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1141290f9ad8SWarner Losh to your config file to compile them in statically. The format 1142f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1143f54a3542SWarner Losh NEWCARD for examples of the new format. 1144290f9ad8SWarner Losh 11459698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 11469698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 11479698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 11489698f2c0SWarner Losh in it. 1149bbcc5149SWarner Losh 1150d65850ebSWarner Losh20000522: 1151ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1152d65850ebSWarner Losh building a kernel after this point is advised that they need 1153d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1154d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1155d65850ebSWarner Losh 1156d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1157d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1158d9583a00SWarner Losh is recommended that you don't set this option until the problem 1159d9583a00SWarner Losh is resolved. 1160d9583a00SWarner Losh 11618039cedeSWarner Losh20000513: 11628039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 11638039cedeSWarner Losh 1164d65850ebSWarner Losh20000510: 11658039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 11668039cedeSWarner Losh This will require some care in updating alphas. A new libstand 11678039cedeSWarner Losh is requires for the boot blocks to build properly. 11688039cedeSWarner Losh 11698039cedeSWarner Losh20000503: 11708039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 11718039cedeSWarner Losh is now available. 11728039cedeSWarner Losh 1173d65850ebSWarner Losh20000502: 1174d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1175d65850ebSWarner Losh connected to the kernel building instead. 1176d65850ebSWarner Losh 1177be149406SNik Clayton20000427: 11788039cedeSWarner Losh You may need to build gperf 11798039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 11808039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 11818039cedeSWarner Losh an option only in -current. 11828039cedeSWarner Losh 11832b8dd5f4SWarner Losh20000417: 11842b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1185f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 11862b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 11872b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 11882c021c6cSMark Ovens before you reboot, you'll need to issue: 11892b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 11902b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 11912b8dd5f4SWarner Losh 11928d9f1945SWarner Losh20000320: 11932b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 11942b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 11952b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1196ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 11972b8dd5f4SWarner Losh to the start of /etc/rc.conf. 11988d9f1945SWarner Losh 1199f8ab1dd6SWarner Losh20000319: 1200f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1201f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1202f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1203f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1204f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1205f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1206f8ab1dd6SWarner Losh 120719cada77SWarner Losh20000318: 1208f699bbbbSMark Ovens We've entered the traditional post release dumping party. 120919cada77SWarner Losh Large kernel changes are being committed and are in the 121019cada77SWarner Losh works. It is important to keep the systems' klds and kernel 121119cada77SWarner Losh in sync as kernel interfaces and structures are changing. 121219cada77SWarner Losh Before reporting kernel panics, make sure that all modules 121319cada77SWarner Losh that you are loading are up to date. 1214ba228352SWarner Losh 121519cada77SWarner Losh20000315: 12166d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 12176d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 12186d23c382SWarner Losh will do the trick. This isn't critical until you remove your 12196d23c382SWarner Losh wd device entries in /dev, at which point your system will not 12206d23c382SWarner Losh boot. 12216d23c382SWarner Losh 12226d23c382SWarner Losh20000315: 122319cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 122419cada77SWarner Losh to upgrade to 4.0 from 3.x. 122557199806SWarner Losh 1226dc0dbf5cSWarner LoshCOMMON ITEMS: 1227dc0dbf5cSWarner Losh 1228a24eff53SWarner Losh General Notes 1229a24eff53SWarner Losh ------------- 1230a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1231a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1232a24eff53SWarner Losh installworld. This is especially true when upgrading between 1233a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1234a24eff53SWarner Losh or several minor releases, or when several months have passed 1235a24eff53SWarner Losh on the -current branch). 1236a24eff53SWarner Losh 12375780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 12385780f3baSWarner Losh poisoning. This can happen because the make utility reads its 12395780f3baSWarner Losh environment when searching for values for global variables. 12405780f3baSWarner Losh To run your build attempts in an "environmental clean room", 12415780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 12425780f3baSWarner Losh page for more details. 12435780f3baSWarner Losh 1244dc0dbf5cSWarner Losh To build a kernel 1245dc0dbf5cSWarner Losh ----------------- 1246ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1247f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1248ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1249282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1250282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1251dc0dbf5cSWarner Losh 1252ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1253ba01eb20SWarner Losh -------------------------------------------------------------- 1254ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 125547d0d01fSWarner Losh config KERNEL_NAME_HERE 1256ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1257ba01eb20SWarner Losh make depend 1258ba01eb20SWarner Losh make 1259ba01eb20SWarner Losh make install 1260ba01eb20SWarner Losh 1261ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1262ba01eb20SWarner Losh 1263ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1264ba01eb20SWarner Losh ----------------------------------------------------------- 126563cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 126663cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 126763cb445eSWarner Losh 1268f643de42SWarner Losh <make sure you have good level 0 dumps> 126963cb445eSWarner Losh <maybe fix /etc/fstab> [7] 127063cb445eSWarner Losh make buildworld 127163cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 127263cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 127363cb445eSWarner Losh [1] 127463cb445eSWarner Losh <reboot in single user> [3] 127563cb445eSWarner Losh mergemaster -p [5] 127663cb445eSWarner Losh make installworld 127763cb445eSWarner Losh mergemaster [4] 127863cb445eSWarner Losh <reboot> 127963cb445eSWarner Losh 1280759f0aefSWarner Losh 1281f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1282f27b1fceSJoseph Koshy -------------------------------------------------- 1283f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1284f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1285f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1286f27b1fceSJoseph Koshy # size. 1287f27b1fceSJoseph Koshy 1288f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1289f27b1fceSJoseph Koshy <boot into -stable> 1290f27b1fceSJoseph Koshy make buildworld 1291f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1292f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1293f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1294f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1295f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1296f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1297f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1298f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1299f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1300f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1301f27b1fceSJoseph Koshy <reboot into current> 1302f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1303f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1304f27b1fceSJoseph Koshy <reboot> 1305f27b1fceSJoseph Koshy 1306f27b1fceSJoseph Koshy 1307f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1308f27b1fceSJoseph Koshy ---------------------------------------------- 13095c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 13105c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 13115c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 13125c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1313ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1314f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1315f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1316f643de42SWarner Losh # space on /. 1317f643de42SWarner Losh 1318f643de42SWarner Losh <make sure you have good level 0 dumps> 1319fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 132021c075eaSWarner Losh make buildworld [9] 1321c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1322d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1323be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1324fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1325fc8c157fSWarner Losh [1] 1326fc8c157fSWarner Losh <reboot in single user> [3] 1327835284beSWarner Losh mergemaster -p [5] 1328f8a4c901SWarner Losh rm -rf /usr/include/g++ 1329ba26da8eSWarner Losh make installworld 1330a6cd4f9dSWarner Losh mergemaster [4] 1331ba26da8eSWarner Losh <reboot> 1332ba26da8eSWarner Losh 1333fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1334fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1335fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1336fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1337fdb9f54dSWarner Losh the UPDATING entries. 1338ba26da8eSWarner Losh 13391dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 13401dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 13411dece4a9SWarner Losh your sources that you have read and understood all the recent 13421dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 13431dece4a9SWarner Losh much fewer pitfalls. 13441dece4a9SWarner Losh 1345134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1346134d2e86SWarner Losh should disable them at this point so they don't crash your 1347134d2e86SWarner Losh system on reboot. 1348134d2e86SWarner Losh 13499c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 13509c1a7444SWarner Losh your own device.hints to reflect your unique hardware 13519c1a7444SWarner Losh configuration. 13529c1a7444SWarner Losh 1353ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1354ee6e1fc3SWarner Losh fsck -p 1355ee6e1fc3SWarner Losh mount -u / 1356ee6e1fc3SWarner Losh mount -a 1357ee6e1fc3SWarner Losh cd /usr/src 135847d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1359f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1360f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1361b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1362b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1363b705ae10SWarner Losh be ignored while you proceed to the next step. 1364ee6e1fc3SWarner Losh 1365a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1366a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1367a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1368a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1369a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1370a6cd4f9dSWarner Losh for potential gotchas. 1371a6cd4f9dSWarner Losh 1372835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1373835284beSWarner Losh you may need to do this if you get unknown user in the following 1374835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1375835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1376835284beSWarner Losh install) after the buildworld before this step if you last updated 1377835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1378835284beSWarner Losh 1379bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1380bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1381bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1382bd79cf40SWarner Losh ok unload 1383bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1384bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1385bd79cf40SWarner Losh described here. 1386fc8c157fSWarner Losh 1387fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1388fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1389fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1390fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1391fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1392fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1393fc8c157fSWarner Losh 1394c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1395c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1396c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1397c74fe6afSWarner Losh that is hard to boot to recover. 1398c74fe6afSWarner Losh 139921c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 140021c075eaSWarner Losh cvs prune empty directories. 1401dc0dbf5cSWarner LoshFORMAT: 1402dc0dbf5cSWarner Losh 1403f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 14041fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1405f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1406f8ab1dd6SWarner Loshprevious releases if your system is older than this. 14071fc1a0dcSWarner Losh 1408e72fd46aSWarner LoshCopyright information: 1409e72fd46aSWarner Losh 14109698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1411e72fd46aSWarner Losh 1412772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1413772730c7SWarner Loshmodification, in full or in part, in any form or format of this 14149698f2c0SWarner Loshdocument are permitted without further permission from the author. 1415e72fd46aSWarner Losh 1416e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1417e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1418e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1419e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1420e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1421e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1422e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1423e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1424e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1425e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1426e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1427e72fd46aSWarner Losh 1428e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1429e72fd46aSWarner Loshauthor a beer. 1430e72fd46aSWarner Losh 143122306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1432772730c7SWarner Loshthis document. 1433772730c7SWarner Losh 143497d92980SPeter Wemm$FreeBSD$ 1435