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 769f7bcf3SWarner LoshNOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW: 869f7bcf3SWarner Losh FreeBSD 5.0-CURRENT 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 20db38f9cbSJacques Vidrine20030915: 21db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 22db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 23db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 24db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 25db38f9cbSJacques Vidrine 26c09d2c2bSMike Makonnen20030829: 27c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 28c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 29c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 30c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 31c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 32c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 33c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 34c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 35c09d2c2bSMike Makonnen may or may not exist on your system. 36c09d2c2bSMike Makonnen 3717c159dcSSøren Schmidt20030824: 3817c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 3917c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 40f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 41f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 4217c159dcSSøren Schmidt 43c1f61aa9SDavid E. O'Brien20030819: 44c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 45c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 46c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 47c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 4869f7bcf3SWarner Losh 4938c962e7SNate Lawson20030728: 5038c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 5138c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 5238c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 5338c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 5438c962e7SNate Lawson so the quirk can be re-enabled. 5538c962e7SNate Lawson 56178cf4e9SWarner Losh20030722: 57178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 58178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 59178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 60178cf4e9SWarner Losh FPU hardware. 61178cf4e9SWarner Losh 62178cf4e9SWarner Losh20030714: 63178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 64178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 65178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 66178cf4e9SWarner Losh People should report those issues to current@. 67178cf4e9SWarner Losh 68157c629aSWarner Losh20030711: 69157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 708b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 7105538fa9SWarner Losh /usr/obj. 72157c629aSWarner Losh 736cc6353fSMarcel Moolenaar20030613: [retrospective] 746cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 756cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 766cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 776cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 786cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 796cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 806cc6353fSMarcel Moolenaar 816cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 826cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 836cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 846cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 856cc6353fSMarcel Moolenaar : 866cc6353fSMarcel Moolenaar 876cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 886cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 896cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 906cc6353fSMarcel Moolenaar 91766c34e4SAndrey A. Chernov20030610: 92766c34e4SAndrey A. Chernov Remove deprecated locale names and transition period code 93766c34e4SAndrey A. Chernov for them, finishing switching to the new scheme. Check your 94766c34e4SAndrey A. Chernov LANG environment variable. 95766c34e4SAndrey A. Chernov 967ddc2528SPoul-Henning Kamp20030609: 97df622d54SPoul-Henning Kamp CCD has been changed to be a fully GEOMified class. Kernel 98df622d54SPoul-Henning Kamp and ccdconfig(8) needs to be in sync, this is particularly 99df622d54SPoul-Henning Kamp important to remember beforehand if your source tree is on 100df622d54SPoul-Henning Kamp a ccd device. Consider making a copy of the old ccdconfig 101df622d54SPoul-Henning Kamp into /boot/kernel.good or wherever you keep your backup 102df622d54SPoul-Henning Kamp kernel. 103df622d54SPoul-Henning Kamp 10452b47445SMark Murray20030505: 10552b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 10652b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 10752b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 10852b47445SMark Murray 109a26df538SWarner Losh20030502: 110a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 111a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 112a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 113a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 114a26df538SWarner Losh 1154b065e2cSDoug Barton20030501: 1164b065e2cSDoug Barton The old rc system has been removed. Please report any problems 1174b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 1184b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 1194b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 1204b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 1214b065e2cSDoug Barton utilizes these old scripts has also been removed. 1224b065e2cSDoug Barton 12381cda3d9SWarner Losh20030423: 12481cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 12581cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 12681cda3d9SWarner Losh work around in devd will be removed around 20030507. You 12781cda3d9SWarner Losh have until then to upgrade your kernel before updating 12881cda3d9SWarner Losh userland. In general, you should have a userland and 12981cda3d9SWarner Losh kernel that's in sync with each other. However, given the 13081cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 13181cda3d9SWarner Losh allowances are made. 13281cda3d9SWarner Losh 13347a657d1SRuslan Ermilov20030329: 13447a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 13547a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 13647a657d1SRuslan Ermilov while upgrading the system through a buildworld. 13747a657d1SRuslan Ermilov 13847a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 13947a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 14047a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 14147a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 14247a657d1SRuslan Ermilov 14347a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 14447a657d1SRuslan Ermilov make cleandir && make obj && \ 14547a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 14647a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 14747a657d1SRuslan Ermilov 1485d2af00cSGregory Neil Shapiro20030208: 1495d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 1505d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 1515d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 1525d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 1535d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 1545d2af00cSGregory Neil Shapiro 1555d2af00cSGregory Neil Shapiro20030128: 1569db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 157ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 1589db58771SPoul-Henning Kamp be removed when convenient. 1599db58771SPoul-Henning Kamp 1608d9b3f57SJake Burkholder20030126: 1618d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 1628d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 1638d9b3f57SJake Burkholder 1641c5efda5SJeff Roberson20030125: 1651c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 1661c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 167ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 1681c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 1691c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 1701c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 1711c5efda5SJeff Roberson 1729d1d64f5SWarner Losh20030115: 1739d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 1749d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 1759d1d64f5SWarner Losh properly. 1769d1d64f5SWarner Losh 177c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 178c9fdb80aSWarner Losh configured for point to point links to bring it more in line 179c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 180c9fdb80aSWarner Losh with NetBSD. 181c9fdb80aSWarner Losh 182161dc364SAlexander Kabaev20021222: 183161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 184161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 185161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 186161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 187161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 188161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 18984cc83efSAlexander Kabaev rebuilt. 190161dc364SAlexander Kabaev 191fb4c8061SMartin Blapp20021216: 192fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 19389056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 194fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 1959d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 196fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 197fb4c8061SMartin Blapp 19817d47eb3SGiorgos Keramidas20021202: 19917d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 20017d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 20117d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 20217d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 20317d47eb3SGiorgos Keramidas 204a4459294SBill Fenner20021029: 205a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 206a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 207a4459294SBill Fenner consumers in sync. 208a4459294SBill Fenner 209fc8c157fSWarner Losh20021024: 210c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 211c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 212c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 213c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 214c57404feSRuslan Ermilov partition really is on. The old device names have gone 215c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 216c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 217c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 21869f7bcf3SWarner Losh 219fd9e8bdaSAndrew Gallatin20021023: 220fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 221fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 222fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 223fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 224fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 225fd9e8bdaSAndrew Gallatin 226fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 227fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 228fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 229fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 230fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 231fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 232fd9e8bdaSAndrew Gallatin 233f8a4c901SWarner Losh20020831: 234f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 235f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 236f8a4c901SWarner Losh programs and libraries need to be recompiled. 237f8a4c901SWarner Losh 238f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 239f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 240f8a4c901SWarner Losh 241c2248fa2SJens Schweikhardt20020827: 242c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 243c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 244c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 245c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 246c2248fa2SJens Schweikhardt 2470d533e43SRuslan Ermilov20020815: 2480d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 2490d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 2500d533e43SRuslan Ermilov again. 2510d533e43SRuslan Ermilov 25233c1de7dSRuslan Ermilov20020729: 25333c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 25433c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 25533c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 25633c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 25733c1de7dSRuslan Ermilov 2582b877facSJulian Elischer20020702: 2592b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 2602b877facSJulian Elischer There are still some minor problems with some signals but the 2612b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 2622b877facSJulian Elischer but each can successfully complete multiple buildworlds. 2632b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 2642b877facSJulian Elischer 26506596d37SWarner Losh20020701: 26606596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 26706596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 26806596d37SWarner Losh GNOME. 26906596d37SWarner Losh 27095ba4330SJacques Vidrine20020511: 27195ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 27295ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 27395ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 27495ba4330SJacques Vidrine with the set-user-ID bit set. 27595ba4330SJacques Vidrine 276a81da3c9SDavid E. O'Brien20020510: 277f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 278f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 2794b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 280f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 281f50caf6fSDavid E. O'Brien 282f50caf6fSDavid E. O'Brien20020510: 283a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 284a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 285a81da3c9SDavid E. O'Brien and then do a cvs update. 286a81da3c9SDavid E. O'Brien 287528a0ef5SJacques Vidrine20020421: 288528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 289528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 290528a0ef5SJacques Vidrine 29185aa5a2eSGregory Neil Shapiro20020404: 29285aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 29385aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 29485aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 29585aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 29685aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 29785aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 29885aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 29985aa5a2eSGregory Neil Shapiro 3008f1e4358SRuslan Ermilov20020403: 3018f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 3028f1e4358SRuslan Ermilov 3032292c02eSWarner Losh20020315: 3042292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 3052292c02eSWarner Losh 30669f7bcf3SWarner Losh20020225: 30769f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 30869f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 30969f7bcf3SWarner Losh 3108f35c493SWarner Losh20020217: 3118f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 3128f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 3138f35c493SWarner Losh command line mail submission has changed. Be sure to run 3148f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 3158f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 3168f35c493SWarner Losh 317835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 318835284beSWarner Losh required in order for sendmail to run as a set-group-ID 319835284beSWarner Losh binary. A 'make installworld' will use the new user and group 320835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 321835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 322835284beSWarner Losh and group must be merged from src/etc/group and 323835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 324835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 325835284beSWarner Losh mergemaster before this will work if you are updating from a 326835284beSWarner Losh very old version of current. The updating recipe has changed 327835284beSWarner Losh as of this date. 328835284beSWarner Losh 329fa9401c1SWarner Losh20020112: 330fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 331fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 332fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 333fa9401c1SWarner Losh you have local modifications, you can use 334fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 335fa9401c1SWarner Losh /etc/pam.d. 336fa9401c1SWarner Losh 337fa9401c1SWarner Losh Please see the following url for more details: 338fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 33947d0d01fSWarner Losh20011229: 34047d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 34147d0d01fSWarner Losh networkfs_types, please note that it has changed 34247d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 34347d0d01fSWarner Losh 344514318a8SWarner Losh20011220: 345514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 346514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 347514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 348514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 349514318a8SWarner Losh version have now been merged back into the base system's 350514318a8SWarner Losh version now. The only user-visible change resulting from this 351514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 352514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 353514318a8SWarner Losh as well. (There has never been rc file support for 354514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 355514318a8SWarner Losh reverted by the time the changes are MFCed.) 356514318a8SWarner Losh 357514318a8SWarner Losh20011215: 358514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 359514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 360514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 361514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 362514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 363514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 364514318a8SWarner Losh will need to be customized then for `odd' densities using 365514318a8SWarner Losh fdcontrol(8). 366514318a8SWarner Losh 3672d22e2bfSWarner Losh20011209: 3682d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 3692d22e2bfSWarner Losh and truss(1) now works again. 3702d22e2bfSWarner Losh 3719e0428e2SWarner Losh20011207: 3729e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 3739e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 3749e0428e2SWarner Losh see 3759e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 3769e0428e2SWarner Losh for details. 3779e0428e2SWarner Losh 3789bab8c59SWarner Losh20011204: 3799bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 3809bab8c59SWarner Losh kernel and burncd to be in sync. 3819bab8c59SWarner Losh 382e57d8b01SWarner Losh20011203: 383e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 384e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 385e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 386e57d8b01SWarner Losh not there already. 387e57d8b01SWarner Losh 388e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 389e57d8b01SWarner Losh until the issue has been resolved. 390e57d8b01SWarner Losh 391b001d36fSJacques Vidrine20011202: 392b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 393b001d36fSJacques Vidrine patched. 394b001d36fSJacques Vidrine 3954b676ec1SWarner Losh20011126: 3964b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 3975ebbf43eSWarner Losh after this date. You need to do this only once. 3984b676ec1SWarner Losh 399d961e462SWarner Losh20011103: 400d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 401d961e462SWarner Losh edges may be left, but for the most part things should be 4024b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 403d961e462SWarner Losh 404d961e462SWarner Losh20011030: 405d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 406d961e462SWarner Losh choppy waves in the upgrade process. 407d961e462SWarner Losh 4081fe003b6SWarner Losh20011030: 409a4b6fda0SWarner Losh The asr driver problem has been resolved. 4101fe003b6SWarner Losh 4111fe003b6SWarner Losh20011027: 4121fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 4131fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 4141fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 4151fe003b6SWarner Losh try to use from this date forward. 4161fe003b6SWarner Losh 4171fe003b6SWarner Losh20011025: 4181fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 4191fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 4201fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 4211fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 4221fe003b6SWarner Losh TARGET_ARCH=i386. 4231fe003b6SWarner Losh 424d05f9643SWarner Losh20011001: 425d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 426d05f9643SWarner Losh You must recompile both the kernel and userland applications 427d05f9643SWarner Losh at the same time. 428d05f9643SWarner Losh 42958970f85SWarner Losh20010929: 43058970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 43158970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 43258970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 43358970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 4349d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 43558970f85SWarner Losh 43658970f85SWarner Losh20010927: 43758970f85SWarner Losh Some weird problems result from using ACPI on some machines. 43858970f85SWarner Losh To disable ACPI you can add 43966ff0e67SMax Khon hint.acpi.0.disabled="1" 44058970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 44158970f85SWarner Losh loader "ok" prompt). 44258970f85SWarner Losh 44358970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 44458970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 44558970f85SWarner Losh file and not list acpi in that list. 446378f4486SAlfred Perlstein 4475119d237SWarner Losh20010924: 4485119d237SWarner Losh The buildworld has been fixed. You may need to install 4495119d237SWarner Losh the 4.x compatibility libraries for some old binaries 4508b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 4518b039fffSWarner Losh get them installed on every installworld, or execute the 4528b039fffSWarner Losh following to get them installed only once: 4538b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 45458970f85SWarner Losh make all install 4558b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 4565119d237SWarner Losh 4573c293725SWarner Losh20010919: 4583c293725SWarner Losh There's a bug in the world build process. The cross-tools 4593c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 4603c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 461772730c7SWarner Losh workaround is to add 4623c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 4633c293725SWarner Losh before building world when upgrading from 4.x to current. This 4643c293725SWarner Losh can be removed afterwards. 4653c293725SWarner Losh 4663c293725SWarner Losh A proper fix to the buildworld target is needed. 4673c293725SWarner Losh 4683c293725SWarner Losh20010918: 4693c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 4703c293725SWarner Losh NFS may be unstable after this date. 4713c293725SWarner Losh 4723c293725SWarner Losh20010912: 4733c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 4743c293725SWarner Losh the kernel. While a few problems were introduced in the 4753c293725SWarner Losh initial commit, most of the major ones have been found and 4763c293725SWarner Losh corrected. 4773c293725SWarner Losh 4783c293725SWarner Losh20010901: 4793c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 4803c293725SWarner Losh arounds described in the 20010604 entry are now no longer 4813c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 4823c293725SWarner Losh have been rectified around this date. 4833c293725SWarner Losh 48498b17b95SWarner Losh20010823: 48598b17b95SWarner Losh named now runs as user bind and group bind rather than as 48698b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 48798b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 48898b17b95SWarner Losh and that group bind is available in /etc/group. Also make 48998b17b95SWarner Losh sure that user or group bind has read (and not write) 49098b17b95SWarner Losh permission for your name server configuration and that it 49198b17b95SWarner Losh has read and write permission for your slave zone files and 49298b17b95SWarner Losh directory. 49398b17b95SWarner Losh 49498b17b95SWarner Losh If you wish to continue to run named as root (a less secure 49598b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 49698b17b95SWarner Losh 49798b17b95SWarner Losh named_flags= 49898b17b95SWarner Losh 4997b9786edSMark Murray20010709: 5007b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 5017b9786edSMark Murray the ability of the shared library major number to handle. 5027b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 5037b9786edSMark Murray solution is to rebuild those ports. 5047b9786edSMark Murray 5051d28950eSWarner Losh20010628: 5061d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 5071d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 5081d28950eSWarner Losh 509e72fd46aSWarner Losh20010625: 51098b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 51198b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 51298b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 51398b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 51498b17b95SWarner Losh IRQ configuration needs more safety belts. 51516de1a07SWarner Losh 5160d415dffSWarner Losh20010617: 517e72fd46aSWarner Losh Softupdates problems have been corrected. 5180d415dffSWarner Losh 5190d415dffSWarner Losh20010614: 5200d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 5210d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 5220d415dffSWarner Losh kernel building methods. 5230d415dffSWarner Losh 5248b9959adSWarner Losh20010613: 5258b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 5268b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 527e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 528e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 5298b9959adSWarner Losh 530e72fd46aSWarner Losh20010613: 5318b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 532e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 533e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 5348b9959adSWarner Losh 5350d415dffSWarner Losh20010612: 5360d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 5370d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 5380d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 5390d415dffSWarner Losh work around this issue, please use only one or the other mechanism 5400d415dffSWarner Losh until this bug is fixed. 5410d415dffSWarner Losh 542e72fd46aSWarner Losh Please note that a feature of config is that if you have config 543e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 544ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 545e72fd46aSWarner Losh 5460d415dffSWarner Losh20010610: 5470d415dffSWarner Losh Locale names have changed to match other systems better. 5480d415dffSWarner Losh 5496ccdb5e4SWarner Losh20010604: 5506ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 5516ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 5526ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 5533590182eSWarner Losh Interrupt storms look a lot like a hang. 5543590182eSWarner Losh 5553590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 5563590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 5573590182eSWarner Losh it is). 5583590182eSWarner Losh 5593590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 5603590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 5613590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 5623590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 5636ccdb5e4SWarner Losh 5640bc62786SWarner Losh20010530: 5650bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 5660bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 5670bc62786SWarner Losh a limited time. If you see 5680bc62786SWarner Losh 5690bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 5700bc62786SWarner Losh 5710bc62786SWarner Losh in your makeworld, then you need to migrate towards using 5720bc62786SWarner Losh COPY=-C. 5730bc62786SWarner Losh 57468a38c6cSWarner Losh20010525: 575b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 576c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 577c4f4a728SWarner Losh definitely is in bad shape. 57868a38c6cSWarner Losh 579ed0f29caSWarner Losh20010521: 580ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 581ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 582ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 583ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 584ed0f29caSWarner Losh is 585ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 586ed0f29caSWarner Losh 58780c16af9SWarner Losh20010520: 58868a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 58980c16af9SWarner Losh 59080c16af9SWarner Losh20010519: 59180c16af9SWarner Losh pccard has had much reorganizational work done to it over 59280c16af9SWarner Losh the past few days. Everything should still work, but if 59380c16af9SWarner Losh not, please contact imp@freebsd.org. 59480c16af9SWarner Losh 595a45f2d05SWarner Losh20010517: 596a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 597a45f2d05SWarner Losh userland at the same time. 598a45f2d05SWarner Losh 599a45f2d05SWarner Losh20010517: 600a45f2d05SWarner Losh New ncurses imported. 601a45f2d05SWarner Losh 6022988afcaSWarner Losh20010512: 6032988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 6042988afcaSWarner Losh will be the only way to go starting July 1. 6052988afcaSWarner Losh 6061a33dba7SWarner Losh20010504: 6071a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 6081a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 6091a33dba7SWarner Losh 61009946a51SWarner Losh20010502: 61109946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 61209946a51SWarner Losh 61309946a51SWarner Losh20010501: 61409946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 61509946a51SWarner Losh 61609946a51SWarner Losh20010430: 617a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 61809946a51SWarner Losh go back in the water. 61909946a51SWarner Losh 62009946a51SWarner Losh20010429: 62109946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 62209946a51SWarner Losh this date, but before the correction date. 62309946a51SWarner Losh 62491dd3b53SWarner Losh20010423: 62591dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 62691dd3b53SWarner Losh 62791dd3b53SWarner Losh20010411: 62891dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 62991dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 63091dd3b53SWarner Losh Update only if you understand that you must not use the old 63191dd3b53SWarner Losh fsck with the new kernel ever. 63291dd3b53SWarner Losh 633933b3269SWarner Losh20010330: 634933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 635c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 636933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 637933b3269SWarner Losh 638933b3269SWarner Losh20010319: 639933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 640933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 641933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 642f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 64309946a51SWarner Losh 64409946a51SWarner Losh20010315: 64509946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 646ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 64709946a51SWarner Losh been replaced by tunables. See ata.4 for details. 648933b3269SWarner Losh 649933b3269SWarner Losh20010312: 650933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 651933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 652933b3269SWarner Losh 653933b3269SWarner Losh20010312: 654933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 655933b3269SWarner Losh instead of ad-hoc. 656933b3269SWarner Losh 657933b3269SWarner Losh20010310: 658f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 659933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 660933b3269SWarner Losh ssh might not work if you don't. 661933b3269SWarner Losh 66262353691SWarner Losh20010303: 66362353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 66462353691SWarner Losh which means that you must include the miibus in your kernel if 66562353691SWarner Losh you use the ed driver. 66662353691SWarner Losh 667d325cf65SWarner Losh20010220: 668d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 669d325cf65SWarner Losh safe to go back into the water. 670d325cf65SWarner Losh 671024daae6SWarner Losh20010211: 672024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 673024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 674024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 675024daae6SWarner Losh that before upgrading would be a good time to do a level 0 676024daae6SWarner Losh dump of your system. No, really, I mean it this time. 677024daae6SWarner Losh 678024daae6SWarner Losh To get to the new system, you'll need to use the following 679024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 680024daae6SWarner Losh don't have to move this to the updating section. 681024daae6SWarner Losh 682024daae6SWarner Losh To get around the installworld problem, do: 683024daae6SWarner Losh # cd /usr/src/usr.bin/sed 684024daae6SWarner Losh # make install 685024daae6SWarner Losh # cd /usr/src 686024daae6SWarner Losh # make installworld 687024daae6SWarner Losh If that doesn't work, then try: 688024daae6SWarner Losh # make -k installworld 689024daae6SWarner Losh # make installworld 690024daae6SWarner Losh 691024daae6SWarner Losh20010207: 692024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 693024daae6SWarner Losh do not include devfs in your kernel as problems result. 694024daae6SWarner Losh 695024daae6SWarner Losh20010205: 6967595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 697024daae6SWarner Losh Remove them from your config. 698024daae6SWarner Losh 6991e159248SWarner Losh20010122: 7001e159248SWarner Losh ****************************** WARNING ****************************** 7011e159248SWarner Losh buildkernel has been changed slightly 7021e159248SWarner Losh ****************************** WARNING ****************************** 7031e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 7041e159248SWarner Losh should update your scripts and make.conf accordingly. 7051e159248SWarner Losh 7061e159248SWarner Losh20010119: 7071e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 7081e159248SWarner Losh This requires a new config to build correctly. 7091e159248SWarner Losh 710aac7dfeaSWarner Losh20010116: 711ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 712aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 713aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 714aac7dfeaSWarner Losh 715aac7dfeaSWarner Losh20010110: 716aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 717aac7dfeaSWarner Losh 718aac7dfeaSWarner Losh20010102: 719aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 720aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 721aac7dfeaSWarner Losh 72263c90c9eSWarner Losh20010101: 72363c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 72463c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 7255fd2a895SWarner Losh dump while building termcap. You can work around this problem 72663c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 72763c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 72863c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 72963c90c9eSWarner Losh might have been ignored by the -k option. 73063c90c9eSWarner Losh 7315fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 7325fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 7335fd2a895SWarner Losh of this working. 7345fd2a895SWarner Losh 735aac7dfeaSWarner Losh20001228: 736aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 737ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 738aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 739aac7dfeaSWarner Losh 740de2bcc63SWarner Losh20001218: 741de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 742de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 743de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 744de2bcc63SWarner Losh cards will not be recognized without it. 745de2bcc63SWarner Losh 746960773f7SWarner Losh20001205: 747960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 748960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 749960773f7SWarner Losh adding the following in pam.conf: 750960773f7SWarner Losh 751960773f7SWarner Losh sshd auth sufficient pam_skey.so 752960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 753960773f7SWarner Losh sshd session required pam_permit.so 754960773f7SWarner Losh 7550acc635eSWarner Losh20001031: 7560acc635eSWarner Losh cvs updated to 1.11. 7570acc635eSWarner Losh 7580acc635eSWarner Losh20001020: 7590acc635eSWarner Losh The random device needs more entropy, so you need to make sure 7600acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 7610acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 7620acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 7630acc635eSWarner Losh workaround. 7640acc635eSWarner Losh 7650acc635eSWarner Losh20001010: 7660acc635eSWarner Losh ****************************** WARNING ****************************** 7670acc635eSWarner Losh Sendmail has been updated. 7680acc635eSWarner Losh ****************************** WARNING ****************************** 7690acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 7700acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 7710acc635eSWarner Losh is set. 7720acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 7730acc635eSWarner Losh commands. 7740acc635eSWarner Losh o Now using sendmail's version of vacation(1). 7750acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 7760acc635eSWarner Losh in /usr/share/sendmail/cf. 7770acc635eSWarner Losh o sendmail.cw changed to local-host-names 7780acc635eSWarner Losh 7790acc635eSWarner Losh More details can be found at 7800acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 7810acc635eSWarner Losh 7826e98a146SWarner Losh20001009: 7836e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 7846e98a146SWarner Losh your entire ports tree, or you will have problems. 7856e98a146SWarner Losh 7866e98a146SWarner Losh20001006: 787685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 7886e98a146SWarner Losh the installed miniperl. It is recommended that you delete 7896e98a146SWarner Losh /usr/bin/miniperl. 7906e98a146SWarner Losh 791073113a4SWarner Losh20001005: 792073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 793685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 794073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 795073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 796073113a4SWarner Losh tree for anything to work. 797073113a4SWarner Losh 7980acc635eSWarner Losh20000928: 7990acc635eSWarner Losh There was a change in the passwd format. Need more information. 8000acc635eSWarner Losh 801be3885b3SWarner Losh20000916: 802be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 803be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 804be3885b3SWarner Losh same time as your kernel. 805be3885b3SWarner Losh 80676ec9675SWarner Losh20000914: 80776ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 80876ec9675SWarner Losh include the device will cause suspended laptops losing time 80976ec9675SWarner Losh when they resume. Include 81076ec9675SWarner Losh device pmtimer 81176ec9675SWarner Losh in your config file and 81201b9a434SWarner Losh hint.pmtimer.0.at="isa" 81376ec9675SWarner Losh to your /boot/device.hints file. 81476ec9675SWarner Losh 815f4865386SMark Murray20000911: 816f4865386SMark Murray The random device has been turned into a (pseudo-)device, 817f4865386SMark Murray rather than an option. The supplied kernel config files have 818f4865386SMark Murray been updated. You will need to do something similar in your 819f4865386SMark Murray own kernel config file. 820f4865386SMark Murray Remove: 821f4865386SMark Murray options RANDOMDEV 822f4865386SMark Murray Add: 823f4865386SMark Murray device random 824f4865386SMark Murray If you prefer to load the loadable module, you need to do 825f4865386SMark Murray nothing. 826f4865386SMark Murray 827d594498fSWarner Losh20000909: 828d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 829d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 830d594498fSWarner Losh reflect this if you load this module at boot time. 831d594498fSWarner Losh The line should read: 832d594498fSWarner Losh random_load="YES" 833d594498fSWarner Losh 8340deb7ddcSWarner Losh20000907: 8350deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 83616eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 83716eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 83816eb772dSWarner Losh sure you don't have model loading problems which might at 83916eb772dSWarner Losh first blush appear related to SMP. 84052bf24e7SWarner Losh 8415a01880bSWarner Losh20000906: 8425a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 8435a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 8445a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 8455a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 8465a01880bSWarner Losh don't have one, and you have host.conf. 8475a01880bSWarner Losh 8482b41163cSWarner Losh20000905: 84938d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 85038d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 85138d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 85238d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 85338d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 85438d6ecd2SWarner Losh 85538d6ecd2SWarner Losh20000905: 8568aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 8578aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 8588aab4bc7SWarner Losh is /boot/kernel. 8598aab4bc7SWarner Losh 8608aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 86138d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 86238d6ecd2SWarner Losh installkernel/installworld dance. 8632b41163cSWarner Losh 864d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 865d594498fSWarner Losh before booting the new kernel, since kldload will find stale 866d594498fSWarner Losh modules in that directory instead of finding them in the correct 867d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 868d594498fSWarner Losh is that the linux module crashes your machine after the update. 869d594498fSWarner Losh 870d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 871d594498fSWarner Losh mv /modules.old /boot/kernel.old 872d594498fSWarner Losh chflags noschg /kernel.old 873d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 874d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 875d594498fSWarner Losh fi 876d594498fSWarner Losh 877c22a309cSWarner Losh20000904: 878c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 879c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 880c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 881c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 882c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 883c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 884c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 885c22a309cSWarner Losh is not likely to be generated. 886c22a309cSWarner Losh 887fdb9f54dSWarner Losh20000825: 888fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 8899c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 8909c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 8919c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 8929c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 8939c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 8949c1a7444SWarner Losh messages will appear after the boot loader tries to start the 8959c1a7444SWarner Losh kernel. 8969c1a7444SWarner Losh 8979c1a7444SWarner Losh20000821: 8989c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 8999c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 9009c1a7444SWarner Losh /boot/loader.conf. 901fdb9f54dSWarner Losh 9028f250aa7SWarner Losh20000812: 9035da0d091SWarner Losh suidperl is now always built and installed on the system, but 9045da0d091SWarner Losh with permissions of 511. If you have applications that use 9055da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 9065da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 9075da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 9085da0d091SWarner Losh will fix this until the next build. 9095da0d091SWarner Losh 9105da0d091SWarner Losh20000812: 9118f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 9128f250aa7SWarner Losh visible changes that may immediately affect your configuration 9138f250aa7SWarner Losh include: 9148f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 9158f250aa7SWarner Losh - newaliases limited to root and trusted users 9168f250aa7SWarner Losh - MSA port (587) turned on by default 9178f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 9188f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 9198f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 9208f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 9218f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 9228f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 9238f250aa7SWarner Losh 92471c38472SWarner Losh20000810: 92571c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 92671c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 92771c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 92871c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 92971c38472SWarner Losh specific use for it. 93071c38472SWarner Losh 93171c38472SWarner Losh20000729: 93271c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 93371c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 93471c38472SWarner Losh /etc/rc.conf if they want to have the same setup 93571c38472SWarner Losh afterwards (unless the variables already are set, of course): 93671c38472SWarner Losh # Enable network daemons for user convenience. 93771c38472SWarner Losh inetd_enable="YES" 93871c38472SWarner Losh portmap_enable="YES" 93971c38472SWarner Losh sendmail_enable="YES" 94071c38472SWarner Losh 94171c38472SWarner Losh20000728: 94271c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 94371c38472SWarner Losh will need to change that to nullfs_load="YES". 94471c38472SWarner Losh 9451dece4a9SWarner Losh20000728: 9461dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 9471dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 9481dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 9491dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 9501dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 9511dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 9521dece4a9SWarner Losh to /MYKERNEL. 9531dece4a9SWarner Losh 954409e887cSWarner Losh20000711: 955409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 956409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 957409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 958409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 959409e887cSWarner Losh for details on potential problems that you might have and how 960409e887cSWarner Losh to get around them. 961409e887cSWarner Losh 962409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 963409e887cSWarner Losh clauses above, you needn't worry. 964409e887cSWarner Losh 965409e887cSWarner Losh20000711: 966409e887cSWarner Losh /etc/security has been updated to print the inode number of 967409e887cSWarner Losh setuid programs that have changed. You will see a large spike 968409e887cSWarner Losh in the number of changed programs the first time when you run 969409e887cSWarner Losh mergemaster to get a new /etc/security. 970409e887cSWarner Losh 971673d13f2SWarner Losh20000710: 972673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 973673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 974673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 975673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 976673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 977673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 978673d13f2SWarner Losh errors. (see below, 20000624). 979673d13f2SWarner Losh 980bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 9811dece4a9SWarner Losh 982673d13f2SWarner Losh20000709: 983c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 984c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 985c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 986673d13f2SWarner Losh ln -s aj /etc/malloc.conf 987673d13f2SWarner Losh 988e98e26cdSWarner Losh20000706: 989e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 990e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 991e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 992f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 993e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 9942c021c6cSMark Ovens interim if needed. 995e98e26cdSWarner Losh 996e98e26cdSWarner Losh20000705: 997e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 998e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 999e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1000e98e26cdSWarner Losh details. 1001e98e26cdSWarner Losh 1002c373950eSWarner Losh20000704: 10032f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 10042f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 10052f961bc8SWarner Losh 10062f961bc8SWarner Losh20000704: 1007c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1008c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1009c373950eSWarner Losh rc.d scripts that haven't been updated. 1010c373950eSWarner Losh 101127dc3a2bSWarner Losh20000630: 101227dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 101327dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 101427dc3a2bSWarner Losh which should be reported to des@freebsd.org. 101527dc3a2bSWarner Losh 1016b8c215acSWarner Losh20000625: 1017b8c215acSWarner Losh From approximately this date forward, one must have the crypto 101827dc3a2bSWarner Losh system installed in order to build the system and kernel. 101927dc3a2bSWarner Losh While not technically strictly true, one should treat it as 102027dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 102127dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 102227dc3a2bSWarner Losh were required. You should check with the latest collections 102327dc3a2bSWarner Losh to make sure that these haven't changed. 1024b8c215acSWarner Losh 10257b990719SWarner Losh20000624: 10267b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 10277b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 10287b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 10291a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 10307b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 10317b990719SWarner Losh openssh and openssl should not be used to generate keys from this 10327b990719SWarner Losh date to the completion of the work. 10337b990719SWarner Losh 103427dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 103527dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 103627dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 103727dc3a2bSWarner Losh recreate the random and urandom devices. 103827dc3a2bSWarner Losh 103981e54c50SWarner Losh20000622: 104081e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 104181e54c50SWarner Losh BSD license. You may need to remove your symbolic links 104281e54c50SWarner Losh that used to be required when updating. 104381e54c50SWarner Losh 104439943833SWarner Losh20000621: 10452c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 10462a2f33fbSDaniel Baker the config file update procedure. 10472a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1048c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 104959df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 105059df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 105139943833SWarner Losh 1052290f9ad8SWarner Losh20000620: 1053290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1054290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1055290f9ad8SWarner Losh that workaround will no longer be required. 1056290f9ad8SWarner Losh 105790fb6346SWarner Losh20000615: 105890fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 105990fb6346SWarner Losh ad driver. If you haven't done so already, you must update 106090fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 106190fb6346SWarner Losh devices. 106290fb6346SWarner Losh 1063f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1064f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1065f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1066f75f65bbSWarner Losh may work). 1067f75f65bbSWarner Losh 1068ba26da8eSWarner Losh20000612: 1069ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1070290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1071c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1072290f9ad8SWarner Losh to your config file to compile them in statically. The format 1073f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1074f54a3542SWarner Losh NEWCARD for examples of the new format. 1075290f9ad8SWarner Losh 10769698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 10779698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 10789698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 10799698f2c0SWarner Losh in it. 1080bbcc5149SWarner Losh 1081d65850ebSWarner Losh20000522: 1082ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1083d65850ebSWarner Losh building a kernel after this point is advised that they need 1084d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1085d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1086d65850ebSWarner Losh 1087d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1088d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1089d9583a00SWarner Losh is recommended that you don't set this option until the problem 1090d9583a00SWarner Losh is resolved. 1091d9583a00SWarner Losh 10928039cedeSWarner Losh20000513: 10938039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 10948039cedeSWarner Losh 1095d65850ebSWarner Losh20000510: 10968039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 10978039cedeSWarner Losh This will require some care in updating alphas. A new libstand 10988039cedeSWarner Losh is requires for the boot blocks to build properly. 10998039cedeSWarner Losh 11008039cedeSWarner Losh20000503: 11018039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 11028039cedeSWarner Losh is now available. 11038039cedeSWarner Losh 1104d65850ebSWarner Losh20000502: 1105d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1106d65850ebSWarner Losh connected to the kernel building instead. 1107d65850ebSWarner Losh 1108be149406SNik Clayton20000427: 11098039cedeSWarner Losh You may need to build gperf 11108039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 11118039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 11128039cedeSWarner Losh an option only in -current. 11138039cedeSWarner Losh 11142b8dd5f4SWarner Losh20000417: 11152b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1116f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 11172b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 11182b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 11192c021c6cSMark Ovens before you reboot, you'll need to issue: 11202b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 11212b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 11222b8dd5f4SWarner Losh 11238d9f1945SWarner Losh20000320: 11242b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 11252b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 11262b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1127ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 11282b8dd5f4SWarner Losh to the start of /etc/rc.conf. 11298d9f1945SWarner Losh 1130f8ab1dd6SWarner Losh20000319: 1131f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1132f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1133f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1134f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1135f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1136f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1137f8ab1dd6SWarner Losh 113819cada77SWarner Losh20000318: 1139f699bbbbSMark Ovens We've entered the traditional post release dumping party. 114019cada77SWarner Losh Large kernel changes are being committed and are in the 114119cada77SWarner Losh works. It is important to keep the systems' klds and kernel 114219cada77SWarner Losh in sync as kernel interfaces and structures are changing. 114319cada77SWarner Losh Before reporting kernel panics, make sure that all modules 114419cada77SWarner Losh that you are loading are up to date. 1145ba228352SWarner Losh 114619cada77SWarner Losh20000315: 11476d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 11486d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 11496d23c382SWarner Losh will do the trick. This isn't critical until you remove your 11506d23c382SWarner Losh wd device entries in /dev, at which point your system will not 11516d23c382SWarner Losh boot. 11526d23c382SWarner Losh 11536d23c382SWarner Losh20000315: 115419cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 115519cada77SWarner Losh to upgrade to 4.0 from 3.x. 115657199806SWarner Losh 1157dc0dbf5cSWarner LoshCOMMON ITEMS: 1158dc0dbf5cSWarner Losh 1159a24eff53SWarner Losh General Notes 1160a24eff53SWarner Losh ------------- 1161a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1162a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1163a24eff53SWarner Losh installworld. This is especially true when upgrading between 1164a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1165a24eff53SWarner Losh or several minor releases, or when several months have passed 1166a24eff53SWarner Losh on the -current branch). 1167a24eff53SWarner Losh 11685780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 11695780f3baSWarner Losh poisoning. This can happen because the make utility reads its 11705780f3baSWarner Losh environment when searching for values for global variables. 11715780f3baSWarner Losh To run your build attempts in an "environmental clean room", 11725780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 11735780f3baSWarner Losh page for more details. 11745780f3baSWarner Losh 1175dc0dbf5cSWarner Losh To build a kernel 1176dc0dbf5cSWarner Losh ----------------- 1177ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1178f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1179ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 11801e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 11811e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 1182dc0dbf5cSWarner Losh 1183ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1184ba01eb20SWarner Losh -------------------------------------------------------------- 1185ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 118647d0d01fSWarner Losh config KERNEL_NAME_HERE 1187ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1188ba01eb20SWarner Losh make depend 1189ba01eb20SWarner Losh make 1190ba01eb20SWarner Losh make install 1191ba01eb20SWarner Losh 1192ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1193ba01eb20SWarner Losh 1194ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1195ba01eb20SWarner Losh ----------------------------------------------------------- 119663cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 119763cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 119863cb445eSWarner Losh 1199f643de42SWarner Losh <make sure you have good level 0 dumps> 120063cb445eSWarner Losh <maybe fix /etc/fstab> [7] 120163cb445eSWarner Losh make buildworld 120263cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 120363cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 120463cb445eSWarner Losh [1] 120563cb445eSWarner Losh <reboot in single user> [3] 120663cb445eSWarner Losh mergemaster -p [5] 120763cb445eSWarner Losh make installworld 120863cb445eSWarner Losh mergemaster [4] 120963cb445eSWarner Losh <reboot> 121063cb445eSWarner Losh 1211759f0aefSWarner Losh 1212f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1213f27b1fceSJoseph Koshy -------------------------------------------------- 1214f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1215f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1216f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1217f27b1fceSJoseph Koshy # size. 1218f27b1fceSJoseph Koshy 1219f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1220f27b1fceSJoseph Koshy <boot into -stable> 1221f27b1fceSJoseph Koshy make buildworld 1222f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1223f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1224f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1225f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1226f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1227f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1228f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1229f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1230f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1231f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1232f27b1fceSJoseph Koshy <reboot into current> 1233f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1234f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1235f27b1fceSJoseph Koshy <reboot> 1236f27b1fceSJoseph Koshy 1237f27b1fceSJoseph Koshy 1238f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1239f27b1fceSJoseph Koshy ---------------------------------------------- 12405c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 12415c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 12425c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 12435c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1244ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1245f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1246f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1247f643de42SWarner Losh # space on /. 1248f643de42SWarner Losh 1249f643de42SWarner Losh <make sure you have good level 0 dumps> 1250fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 125121c075eaSWarner Losh make buildworld [9] 1252c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1253d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1254be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1255fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1256fc8c157fSWarner Losh [1] 1257fc8c157fSWarner Losh <reboot in single user> [3] 1258835284beSWarner Losh mergemaster -p [5] 1259f8a4c901SWarner Losh rm -rf /usr/include/g++ 1260ba26da8eSWarner Losh make installworld 1261a6cd4f9dSWarner Losh mergemaster [4] 1262ba26da8eSWarner Losh <reboot> 1263ba26da8eSWarner Losh 1264fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1265fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1266fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1267fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1268fdb9f54dSWarner Losh the UPDATING entries. 1269ba26da8eSWarner Losh 12701dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 12711dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 12721dece4a9SWarner Losh your sources that you have read and understood all the recent 12731dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 12741dece4a9SWarner Losh much fewer pitfalls. 12751dece4a9SWarner Losh 1276134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1277134d2e86SWarner Losh should disable them at this point so they don't crash your 1278134d2e86SWarner Losh system on reboot. 1279134d2e86SWarner Losh 12809c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 12819c1a7444SWarner Losh your own device.hints to reflect your unique hardware 12829c1a7444SWarner Losh configuration. 12839c1a7444SWarner Losh 1284ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1285ee6e1fc3SWarner Losh fsck -p 1286ee6e1fc3SWarner Losh mount -u / 1287ee6e1fc3SWarner Losh mount -a 1288ee6e1fc3SWarner Losh cd /usr/src 128947d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1290f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1291f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1292b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1293b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1294b705ae10SWarner Losh be ignored while you proceed to the next step. 1295ee6e1fc3SWarner Losh 1296a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1297a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1298a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1299a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1300a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1301a6cd4f9dSWarner Losh for potential gotchas. 1302a6cd4f9dSWarner Losh 1303835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1304835284beSWarner Losh you may need to do this if you get unknown user in the following 1305835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1306835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1307835284beSWarner Losh install) after the buildworld before this step if you last updated 1308835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1309835284beSWarner Losh 1310bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1311bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1312bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1313bd79cf40SWarner Losh ok unload 1314bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1315bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1316bd79cf40SWarner Losh described here. 1317fc8c157fSWarner Losh 1318fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1319fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1320fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1321fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1322fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1323fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1324fc8c157fSWarner Losh 1325c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1326c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1327c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1328c74fe6afSWarner Losh that is hard to boot to recover. 1329c74fe6afSWarner Losh 133021c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 133121c075eaSWarner Losh cvs prune empty directories. 1332dc0dbf5cSWarner LoshFORMAT: 1333dc0dbf5cSWarner Losh 1334f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 13351fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1336f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1337f8ab1dd6SWarner Loshprevious releases if your system is older than this. 13381fc1a0dcSWarner Losh 1339e72fd46aSWarner LoshCopyright information: 1340e72fd46aSWarner Losh 13419698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1342e72fd46aSWarner Losh 1343772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1344772730c7SWarner Loshmodification, in full or in part, in any form or format of this 13459698f2c0SWarner Loshdocument are permitted without further permission from the author. 1346e72fd46aSWarner Losh 1347e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1348e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1349e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1350e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1351e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1352e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1353e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1354e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1355e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1356e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1357e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1358e72fd46aSWarner Losh 1359e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1360e72fd46aSWarner Loshauthor a beer. 1361e72fd46aSWarner Losh 136222306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1363772730c7SWarner Loshthis document. 1364772730c7SWarner Losh 136597d92980SPeter Wemm$FreeBSD$ 1366