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 2047a42c7aSPoul-Henning Kamp20030928: 2147a42c7aSPoul-Henning Kamp Changes to the cdevsw default functions have been made to remove 2247a42c7aSPoul-Henning Kamp the need to specify nullopen() and nullclose() explicitly. 2347a42c7aSPoul-Henning Kamp __FreeBSD_version bumpted to 501110. 2447a42c7aSPoul-Henning Kamp 2507105342SMax Khon20030926: 2607105342SMax Khon kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 2707105342SMax Khon mount_cd9660(8) need to be in sync with kernel. 2807105342SMax Khon 2917dcd026SSam Leffler20030925: 3017dcd026SSam Leffler Configuring a system to use IPFILTER now requires that PFIL_HOOKS 3117dcd026SSam Leffler also be explicitly configured. Previously this dependency was 3217dcd026SSam Leffler magically handled through some cruft in net/pfil.h; but that has 3317dcd026SSam Leffler been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 3417dcd026SSam Leffler will fail with obtuse errors in ip_fil.c. 3517dcd026SSam Leffler 36fedf1d01SBruce M Simpson20030923: 37fedf1d01SBruce M Simpson Fix a bug in arplookup(), whereby a hostile party on a locally 38fedf1d01SBruce M Simpson attached network could exhaust kernel memory, and cause a system 39fedf1d01SBruce M Simpson panic, by sending a flood of spoofed ARP requests. See 40fedf1d01SBruce M Simpson FreeBSD-SA-03:14.arp. 41fedf1d01SBruce M Simpson 42db38f9cbSJacques Vidrine20030915: 43db38f9cbSJacques Vidrine A change to /etc/defaults/rc.conf now causes inetd to be started 44db38f9cbSJacques Vidrine with `-C 60' if it is not overridden in /etc/rc.conf. This 45db38f9cbSJacques Vidrine causes inetd to stop accepting connections from an IP address 46db38f9cbSJacques Vidrine that exceeds the rate of 60 connections per minute. 47db38f9cbSJacques Vidrine 48c09d2c2bSMike Makonnen20030829: 49c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 50c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 51c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 52c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 53c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 54c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 55c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 56c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 57c09d2c2bSMike Makonnen may or may not exist on your system. 58c09d2c2bSMike Makonnen 5917c159dcSSøren Schmidt20030824: 6017c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 6117c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 62f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 63f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 6417c159dcSSøren Schmidt 65c1f61aa9SDavid E. O'Brien20030819: 66c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 67c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 68c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 69c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 7069f7bcf3SWarner Losh 7138c962e7SNate Lawson20030728: 7238c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 7338c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 7438c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 7538c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 7638c962e7SNate Lawson so the quirk can be re-enabled. 7738c962e7SNate Lawson 78178cf4e9SWarner Losh20030722: 79178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 80178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 81178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 82178cf4e9SWarner Losh FPU hardware. 83178cf4e9SWarner Losh 84178cf4e9SWarner Losh20030714: 85178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 86178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 87178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 88178cf4e9SWarner Losh People should report those issues to current@. 89178cf4e9SWarner Losh 90157c629aSWarner Losh20030711: 91157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 928b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 9305538fa9SWarner Losh /usr/obj. 94157c629aSWarner Losh 956cc6353fSMarcel Moolenaar20030613: [retrospective] 966cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 976cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 986cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 996cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 1006cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 1016cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 1026cc6353fSMarcel Moolenaar 1036cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 1046cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 1056cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 1066cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 1076cc6353fSMarcel Moolenaar : 1086cc6353fSMarcel Moolenaar 1096cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 1106cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 1116cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 1126cc6353fSMarcel Moolenaar 113766c34e4SAndrey A. Chernov20030610: 114766c34e4SAndrey A. Chernov Remove deprecated locale names and transition period code 115766c34e4SAndrey A. Chernov for them, finishing switching to the new scheme. Check your 116766c34e4SAndrey A. Chernov LANG environment variable. 117766c34e4SAndrey A. Chernov 1187ddc2528SPoul-Henning Kamp20030609: 119df622d54SPoul-Henning Kamp CCD has been changed to be a fully GEOMified class. Kernel 120df622d54SPoul-Henning Kamp and ccdconfig(8) needs to be in sync, this is particularly 121df622d54SPoul-Henning Kamp important to remember beforehand if your source tree is on 122df622d54SPoul-Henning Kamp a ccd device. Consider making a copy of the old ccdconfig 123df622d54SPoul-Henning Kamp into /boot/kernel.good or wherever you keep your backup 124df622d54SPoul-Henning Kamp kernel. 125df622d54SPoul-Henning Kamp 12652b47445SMark Murray20030505: 12752b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 12852b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 12952b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 13052b47445SMark Murray 131a26df538SWarner Losh20030502: 132a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 133a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 134a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 135a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 136a26df538SWarner Losh 1374b065e2cSDoug Barton20030501: 1384b065e2cSDoug Barton The old rc system has been removed. Please report any problems 1394b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 1404b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 1414b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 1424b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 1434b065e2cSDoug Barton utilizes these old scripts has also been removed. 1444b065e2cSDoug Barton 14581cda3d9SWarner Losh20030423: 14681cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 14781cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 14881cda3d9SWarner Losh work around in devd will be removed around 20030507. You 14981cda3d9SWarner Losh have until then to upgrade your kernel before updating 15081cda3d9SWarner Losh userland. In general, you should have a userland and 15181cda3d9SWarner Losh kernel that's in sync with each other. However, given the 15281cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 15381cda3d9SWarner Losh allowances are made. 15481cda3d9SWarner Losh 15547a657d1SRuslan Ermilov20030329: 15647a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 15747a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 15847a657d1SRuslan Ermilov while upgrading the system through a buildworld. 15947a657d1SRuslan Ermilov 16047a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 16147a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 16247a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 16347a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 16447a657d1SRuslan Ermilov 16547a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 16647a657d1SRuslan Ermilov make cleandir && make obj && \ 16747a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 16847a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 16947a657d1SRuslan Ermilov 1705d2af00cSGregory Neil Shapiro20030208: 1715d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 1725d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 1735d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 1745d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 1755d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 1765d2af00cSGregory Neil Shapiro 1775d2af00cSGregory Neil Shapiro20030128: 1789db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 179ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 1809db58771SPoul-Henning Kamp be removed when convenient. 1819db58771SPoul-Henning Kamp 1828d9b3f57SJake Burkholder20030126: 1838d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 1848d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 1858d9b3f57SJake Burkholder 1861c5efda5SJeff Roberson20030125: 1871c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 1881c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 189ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 1901c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 1911c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 1921c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 1931c5efda5SJeff Roberson 1949d1d64f5SWarner Losh20030115: 1959d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 1969d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 1979d1d64f5SWarner Losh properly. 1989d1d64f5SWarner Losh 199c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 200c9fdb80aSWarner Losh configured for point to point links to bring it more in line 201c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 202c9fdb80aSWarner Losh with NetBSD. 203c9fdb80aSWarner Losh 204161dc364SAlexander Kabaev20021222: 205161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 206161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 207161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 208161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 209161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 210161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 21184cc83efSAlexander Kabaev rebuilt. 212161dc364SAlexander Kabaev 213fb4c8061SMartin Blapp20021216: 214fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 21589056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 216fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 2179d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 218fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 219fb4c8061SMartin Blapp 22017d47eb3SGiorgos Keramidas20021202: 22117d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 22217d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 22317d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 22417d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 22517d47eb3SGiorgos Keramidas 226a4459294SBill Fenner20021029: 227a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 228a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 229a4459294SBill Fenner consumers in sync. 230a4459294SBill Fenner 231fc8c157fSWarner Losh20021024: 232c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 233c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 234c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 235c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 236c57404feSRuslan Ermilov partition really is on. The old device names have gone 237c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 238c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 239c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 24069f7bcf3SWarner Losh 241fd9e8bdaSAndrew Gallatin20021023: 242fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 243fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 244fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 245fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 246fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 247fd9e8bdaSAndrew Gallatin 248fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 249fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 250fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 251fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 252fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 253fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 254fd9e8bdaSAndrew Gallatin 255f8a4c901SWarner Losh20020831: 256f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 257f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 258f8a4c901SWarner Losh programs and libraries need to be recompiled. 259f8a4c901SWarner Losh 260f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 261f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 262f8a4c901SWarner Losh 263c2248fa2SJens Schweikhardt20020827: 264c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 265c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 266c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 267c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 268c2248fa2SJens Schweikhardt 2690d533e43SRuslan Ermilov20020815: 2700d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 2710d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 2720d533e43SRuslan Ermilov again. 2730d533e43SRuslan Ermilov 27433c1de7dSRuslan Ermilov20020729: 27533c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 27633c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 27733c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 27833c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 27933c1de7dSRuslan Ermilov 2802b877facSJulian Elischer20020702: 2812b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 2822b877facSJulian Elischer There are still some minor problems with some signals but the 2832b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 2842b877facSJulian Elischer but each can successfully complete multiple buildworlds. 2852b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 2862b877facSJulian Elischer 28706596d37SWarner Losh20020701: 28806596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 28906596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 29006596d37SWarner Losh GNOME. 29106596d37SWarner Losh 29295ba4330SJacques Vidrine20020511: 29395ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 29495ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 29595ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 29695ba4330SJacques Vidrine with the set-user-ID bit set. 29795ba4330SJacques Vidrine 298a81da3c9SDavid E. O'Brien20020510: 299f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 300f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 3014b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 302f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 303f50caf6fSDavid E. O'Brien 304f50caf6fSDavid E. O'Brien20020510: 305a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 306a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 307a81da3c9SDavid E. O'Brien and then do a cvs update. 308a81da3c9SDavid E. O'Brien 309528a0ef5SJacques Vidrine20020421: 310528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 311528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 312528a0ef5SJacques Vidrine 31385aa5a2eSGregory Neil Shapiro20020404: 31485aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 31585aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 31685aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 31785aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 31885aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 31985aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 32085aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 32185aa5a2eSGregory Neil Shapiro 3228f1e4358SRuslan Ermilov20020403: 3238f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 3248f1e4358SRuslan Ermilov 3252292c02eSWarner Losh20020315: 3262292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 3272292c02eSWarner Losh 32869f7bcf3SWarner Losh20020225: 32969f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 33069f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 33169f7bcf3SWarner Losh 3328f35c493SWarner Losh20020217: 3338f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 3348f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 3358f35c493SWarner Losh command line mail submission has changed. Be sure to run 3368f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 3378f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 3388f35c493SWarner Losh 339835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 340835284beSWarner Losh required in order for sendmail to run as a set-group-ID 341835284beSWarner Losh binary. A 'make installworld' will use the new user and group 342835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 343835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 344835284beSWarner Losh and group must be merged from src/etc/group and 345835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 346835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 347835284beSWarner Losh mergemaster before this will work if you are updating from a 348835284beSWarner Losh very old version of current. The updating recipe has changed 349835284beSWarner Losh as of this date. 350835284beSWarner Losh 351fa9401c1SWarner Losh20020112: 352fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 353fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 354fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 355fa9401c1SWarner Losh you have local modifications, you can use 356fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 357fa9401c1SWarner Losh /etc/pam.d. 358fa9401c1SWarner Losh 359fa9401c1SWarner Losh Please see the following url for more details: 360fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 36147d0d01fSWarner Losh20011229: 36247d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 36347d0d01fSWarner Losh networkfs_types, please note that it has changed 36447d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 36547d0d01fSWarner Losh 366514318a8SWarner Losh20011220: 367514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 368514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 369514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 370514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 371514318a8SWarner Losh version have now been merged back into the base system's 372514318a8SWarner Losh version now. The only user-visible change resulting from this 373514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 374514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 375514318a8SWarner Losh as well. (There has never been rc file support for 376514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 377514318a8SWarner Losh reverted by the time the changes are MFCed.) 378514318a8SWarner Losh 379514318a8SWarner Losh20011215: 380514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 381514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 382514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 383514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 384514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 385514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 386514318a8SWarner Losh will need to be customized then for `odd' densities using 387514318a8SWarner Losh fdcontrol(8). 388514318a8SWarner Losh 3892d22e2bfSWarner Losh20011209: 3902d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 3912d22e2bfSWarner Losh and truss(1) now works again. 3922d22e2bfSWarner Losh 3939e0428e2SWarner Losh20011207: 3949e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 3959e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 3969e0428e2SWarner Losh see 3979e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 3989e0428e2SWarner Losh for details. 3999e0428e2SWarner Losh 4009bab8c59SWarner Losh20011204: 4019bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 4029bab8c59SWarner Losh kernel and burncd to be in sync. 4039bab8c59SWarner Losh 404e57d8b01SWarner Losh20011203: 405e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 406e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 407e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 408e57d8b01SWarner Losh not there already. 409e57d8b01SWarner Losh 410e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 411e57d8b01SWarner Losh until the issue has been resolved. 412e57d8b01SWarner Losh 413b001d36fSJacques Vidrine20011202: 414b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 415b001d36fSJacques Vidrine patched. 416b001d36fSJacques Vidrine 4174b676ec1SWarner Losh20011126: 4184b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 4195ebbf43eSWarner Losh after this date. You need to do this only once. 4204b676ec1SWarner Losh 421d961e462SWarner Losh20011103: 422d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 423d961e462SWarner Losh edges may be left, but for the most part things should be 4244b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 425d961e462SWarner Losh 426d961e462SWarner Losh20011030: 427d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 428d961e462SWarner Losh choppy waves in the upgrade process. 429d961e462SWarner Losh 4301fe003b6SWarner Losh20011030: 431a4b6fda0SWarner Losh The asr driver problem has been resolved. 4321fe003b6SWarner Losh 4331fe003b6SWarner Losh20011027: 4341fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 4351fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 4361fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 4371fe003b6SWarner Losh try to use from this date forward. 4381fe003b6SWarner Losh 4391fe003b6SWarner Losh20011025: 4401fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 4411fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 4421fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 4431fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 4441fe003b6SWarner Losh TARGET_ARCH=i386. 4451fe003b6SWarner Losh 446d05f9643SWarner Losh20011001: 447d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 448d05f9643SWarner Losh You must recompile both the kernel and userland applications 449d05f9643SWarner Losh at the same time. 450d05f9643SWarner Losh 45158970f85SWarner Losh20010929: 45258970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 45358970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 45458970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 45558970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 4569d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 45758970f85SWarner Losh 45858970f85SWarner Losh20010927: 45958970f85SWarner Losh Some weird problems result from using ACPI on some machines. 46058970f85SWarner Losh To disable ACPI you can add 46166ff0e67SMax Khon hint.acpi.0.disabled="1" 46258970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 46358970f85SWarner Losh loader "ok" prompt). 46458970f85SWarner Losh 46558970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 46658970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 46758970f85SWarner Losh file and not list acpi in that list. 468378f4486SAlfred Perlstein 4695119d237SWarner Losh20010924: 4705119d237SWarner Losh The buildworld has been fixed. You may need to install 4715119d237SWarner Losh the 4.x compatibility libraries for some old binaries 4728b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 4738b039fffSWarner Losh get them installed on every installworld, or execute the 4748b039fffSWarner Losh following to get them installed only once: 4758b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 47658970f85SWarner Losh make all install 4778b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 4785119d237SWarner Losh 4793c293725SWarner Losh20010919: 4803c293725SWarner Losh There's a bug in the world build process. The cross-tools 4813c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 4823c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 483772730c7SWarner Losh workaround is to add 4843c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 4853c293725SWarner Losh before building world when upgrading from 4.x to current. This 4863c293725SWarner Losh can be removed afterwards. 4873c293725SWarner Losh 4883c293725SWarner Losh A proper fix to the buildworld target is needed. 4893c293725SWarner Losh 4903c293725SWarner Losh20010918: 4913c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 4923c293725SWarner Losh NFS may be unstable after this date. 4933c293725SWarner Losh 4943c293725SWarner Losh20010912: 4953c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 4963c293725SWarner Losh the kernel. While a few problems were introduced in the 4973c293725SWarner Losh initial commit, most of the major ones have been found and 4983c293725SWarner Losh corrected. 4993c293725SWarner Losh 5003c293725SWarner Losh20010901: 5013c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 5023c293725SWarner Losh arounds described in the 20010604 entry are now no longer 5033c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 5043c293725SWarner Losh have been rectified around this date. 5053c293725SWarner Losh 50698b17b95SWarner Losh20010823: 50798b17b95SWarner Losh named now runs as user bind and group bind rather than as 50898b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 50998b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 51098b17b95SWarner Losh and that group bind is available in /etc/group. Also make 51198b17b95SWarner Losh sure that user or group bind has read (and not write) 51298b17b95SWarner Losh permission for your name server configuration and that it 51398b17b95SWarner Losh has read and write permission for your slave zone files and 51498b17b95SWarner Losh directory. 51598b17b95SWarner Losh 51698b17b95SWarner Losh If you wish to continue to run named as root (a less secure 51798b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 51898b17b95SWarner Losh 51998b17b95SWarner Losh named_flags= 52098b17b95SWarner Losh 5217b9786edSMark Murray20010709: 5227b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 5237b9786edSMark Murray the ability of the shared library major number to handle. 5247b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 5257b9786edSMark Murray solution is to rebuild those ports. 5267b9786edSMark Murray 5271d28950eSWarner Losh20010628: 5281d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 5291d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 5301d28950eSWarner Losh 531e72fd46aSWarner Losh20010625: 53298b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 53398b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 53498b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 53598b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 53698b17b95SWarner Losh IRQ configuration needs more safety belts. 53716de1a07SWarner Losh 5380d415dffSWarner Losh20010617: 539e72fd46aSWarner Losh Softupdates problems have been corrected. 5400d415dffSWarner Losh 5410d415dffSWarner Losh20010614: 5420d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 5430d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 5440d415dffSWarner Losh kernel building methods. 5450d415dffSWarner Losh 5468b9959adSWarner Losh20010613: 5478b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 5488b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 549e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 550e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 5518b9959adSWarner Losh 552e72fd46aSWarner Losh20010613: 5538b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 554e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 555e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 5568b9959adSWarner Losh 5570d415dffSWarner Losh20010612: 5580d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 5590d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 5600d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 5610d415dffSWarner Losh work around this issue, please use only one or the other mechanism 5620d415dffSWarner Losh until this bug is fixed. 5630d415dffSWarner Losh 564e72fd46aSWarner Losh Please note that a feature of config is that if you have config 565e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 566ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 567e72fd46aSWarner Losh 5680d415dffSWarner Losh20010610: 5690d415dffSWarner Losh Locale names have changed to match other systems better. 5700d415dffSWarner Losh 5716ccdb5e4SWarner Losh20010604: 5726ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 5736ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 5746ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 5753590182eSWarner Losh Interrupt storms look a lot like a hang. 5763590182eSWarner Losh 5773590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 5783590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 5793590182eSWarner Losh it is). 5803590182eSWarner Losh 5813590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 5823590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 5833590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 5843590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 5856ccdb5e4SWarner Losh 5860bc62786SWarner Losh20010530: 5870bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 5880bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 5890bc62786SWarner Losh a limited time. If you see 5900bc62786SWarner Losh 5910bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 5920bc62786SWarner Losh 5930bc62786SWarner Losh in your makeworld, then you need to migrate towards using 5940bc62786SWarner Losh COPY=-C. 5950bc62786SWarner Losh 59668a38c6cSWarner Losh20010525: 597b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 598c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 599c4f4a728SWarner Losh definitely is in bad shape. 60068a38c6cSWarner Losh 601ed0f29caSWarner Losh20010521: 602ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 603ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 604ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 605ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 606ed0f29caSWarner Losh is 607ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 608ed0f29caSWarner Losh 60980c16af9SWarner Losh20010520: 61068a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 61180c16af9SWarner Losh 61280c16af9SWarner Losh20010519: 61380c16af9SWarner Losh pccard has had much reorganizational work done to it over 61480c16af9SWarner Losh the past few days. Everything should still work, but if 61580c16af9SWarner Losh not, please contact imp@freebsd.org. 61680c16af9SWarner Losh 617a45f2d05SWarner Losh20010517: 618a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 619a45f2d05SWarner Losh userland at the same time. 620a45f2d05SWarner Losh 621a45f2d05SWarner Losh20010517: 622a45f2d05SWarner Losh New ncurses imported. 623a45f2d05SWarner Losh 6242988afcaSWarner Losh20010512: 6252988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 6262988afcaSWarner Losh will be the only way to go starting July 1. 6272988afcaSWarner Losh 6281a33dba7SWarner Losh20010504: 6291a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 6301a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 6311a33dba7SWarner Losh 63209946a51SWarner Losh20010502: 63309946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 63409946a51SWarner Losh 63509946a51SWarner Losh20010501: 63609946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 63709946a51SWarner Losh 63809946a51SWarner Losh20010430: 639a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 64009946a51SWarner Losh go back in the water. 64109946a51SWarner Losh 64209946a51SWarner Losh20010429: 64309946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 64409946a51SWarner Losh this date, but before the correction date. 64509946a51SWarner Losh 64691dd3b53SWarner Losh20010423: 64791dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 64891dd3b53SWarner Losh 64991dd3b53SWarner Losh20010411: 65091dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 65191dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 65291dd3b53SWarner Losh Update only if you understand that you must not use the old 65391dd3b53SWarner Losh fsck with the new kernel ever. 65491dd3b53SWarner Losh 655933b3269SWarner Losh20010330: 656933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 657c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 658933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 659933b3269SWarner Losh 660933b3269SWarner Losh20010319: 661933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 662933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 663933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 664f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 66509946a51SWarner Losh 66609946a51SWarner Losh20010315: 66709946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 668ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 66909946a51SWarner Losh been replaced by tunables. See ata.4 for details. 670933b3269SWarner Losh 671933b3269SWarner Losh20010312: 672933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 673933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 674933b3269SWarner Losh 675933b3269SWarner Losh20010312: 676933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 677933b3269SWarner Losh instead of ad-hoc. 678933b3269SWarner Losh 679933b3269SWarner Losh20010310: 680f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 681933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 682933b3269SWarner Losh ssh might not work if you don't. 683933b3269SWarner Losh 68462353691SWarner Losh20010303: 68562353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 68662353691SWarner Losh which means that you must include the miibus in your kernel if 68762353691SWarner Losh you use the ed driver. 68862353691SWarner Losh 689d325cf65SWarner Losh20010220: 690d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 691d325cf65SWarner Losh safe to go back into the water. 692d325cf65SWarner Losh 693024daae6SWarner Losh20010211: 694024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 695024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 696024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 697024daae6SWarner Losh that before upgrading would be a good time to do a level 0 698024daae6SWarner Losh dump of your system. No, really, I mean it this time. 699024daae6SWarner Losh 700024daae6SWarner Losh To get to the new system, you'll need to use the following 701024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 702024daae6SWarner Losh don't have to move this to the updating section. 703024daae6SWarner Losh 704024daae6SWarner Losh To get around the installworld problem, do: 705024daae6SWarner Losh # cd /usr/src/usr.bin/sed 706024daae6SWarner Losh # make install 707024daae6SWarner Losh # cd /usr/src 708024daae6SWarner Losh # make installworld 709024daae6SWarner Losh If that doesn't work, then try: 710024daae6SWarner Losh # make -k installworld 711024daae6SWarner Losh # make installworld 712024daae6SWarner Losh 713024daae6SWarner Losh20010207: 714024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 715024daae6SWarner Losh do not include devfs in your kernel as problems result. 716024daae6SWarner Losh 717024daae6SWarner Losh20010205: 7187595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 719024daae6SWarner Losh Remove them from your config. 720024daae6SWarner Losh 7211e159248SWarner Losh20010122: 7221e159248SWarner Losh ****************************** WARNING ****************************** 7231e159248SWarner Losh buildkernel has been changed slightly 7241e159248SWarner Losh ****************************** WARNING ****************************** 7251e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 7261e159248SWarner Losh should update your scripts and make.conf accordingly. 7271e159248SWarner Losh 7281e159248SWarner Losh20010119: 7291e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 7301e159248SWarner Losh This requires a new config to build correctly. 7311e159248SWarner Losh 732aac7dfeaSWarner Losh20010116: 733ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 734aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 735aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 736aac7dfeaSWarner Losh 737aac7dfeaSWarner Losh20010110: 738aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 739aac7dfeaSWarner Losh 740aac7dfeaSWarner Losh20010102: 741aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 742aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 743aac7dfeaSWarner Losh 74463c90c9eSWarner Losh20010101: 74563c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 74663c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 7475fd2a895SWarner Losh dump while building termcap. You can work around this problem 74863c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 74963c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 75063c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 75163c90c9eSWarner Losh might have been ignored by the -k option. 75263c90c9eSWarner Losh 7535fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 7545fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 7555fd2a895SWarner Losh of this working. 7565fd2a895SWarner Losh 757aac7dfeaSWarner Losh20001228: 758aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 759ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 760aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 761aac7dfeaSWarner Losh 762de2bcc63SWarner Losh20001218: 763de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 764de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 765de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 766de2bcc63SWarner Losh cards will not be recognized without it. 767de2bcc63SWarner Losh 768960773f7SWarner Losh20001205: 769960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 770960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 771960773f7SWarner Losh adding the following in pam.conf: 772960773f7SWarner Losh 773960773f7SWarner Losh sshd auth sufficient pam_skey.so 774960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 775960773f7SWarner Losh sshd session required pam_permit.so 776960773f7SWarner Losh 7770acc635eSWarner Losh20001031: 7780acc635eSWarner Losh cvs updated to 1.11. 7790acc635eSWarner Losh 7800acc635eSWarner Losh20001020: 7810acc635eSWarner Losh The random device needs more entropy, so you need to make sure 7820acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 7830acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 7840acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 7850acc635eSWarner Losh workaround. 7860acc635eSWarner Losh 7870acc635eSWarner Losh20001010: 7880acc635eSWarner Losh ****************************** WARNING ****************************** 7890acc635eSWarner Losh Sendmail has been updated. 7900acc635eSWarner Losh ****************************** WARNING ****************************** 7910acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 7920acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 7930acc635eSWarner Losh is set. 7940acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 7950acc635eSWarner Losh commands. 7960acc635eSWarner Losh o Now using sendmail's version of vacation(1). 7970acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 7980acc635eSWarner Losh in /usr/share/sendmail/cf. 7990acc635eSWarner Losh o sendmail.cw changed to local-host-names 8000acc635eSWarner Losh 8010acc635eSWarner Losh More details can be found at 8020acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 8030acc635eSWarner Losh 8046e98a146SWarner Losh20001009: 8056e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 8066e98a146SWarner Losh your entire ports tree, or you will have problems. 8076e98a146SWarner Losh 8086e98a146SWarner Losh20001006: 809685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 8106e98a146SWarner Losh the installed miniperl. It is recommended that you delete 8116e98a146SWarner Losh /usr/bin/miniperl. 8126e98a146SWarner Losh 813073113a4SWarner Losh20001005: 814073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 815685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 816073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 817073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 818073113a4SWarner Losh tree for anything to work. 819073113a4SWarner Losh 8200acc635eSWarner Losh20000928: 8210acc635eSWarner Losh There was a change in the passwd format. Need more information. 8220acc635eSWarner Losh 823be3885b3SWarner Losh20000916: 824be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 825be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 826be3885b3SWarner Losh same time as your kernel. 827be3885b3SWarner Losh 82876ec9675SWarner Losh20000914: 82976ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 83076ec9675SWarner Losh include the device will cause suspended laptops losing time 83176ec9675SWarner Losh when they resume. Include 83276ec9675SWarner Losh device pmtimer 83376ec9675SWarner Losh in your config file and 83401b9a434SWarner Losh hint.pmtimer.0.at="isa" 83576ec9675SWarner Losh to your /boot/device.hints file. 83676ec9675SWarner Losh 837f4865386SMark Murray20000911: 838f4865386SMark Murray The random device has been turned into a (pseudo-)device, 839f4865386SMark Murray rather than an option. The supplied kernel config files have 840f4865386SMark Murray been updated. You will need to do something similar in your 841f4865386SMark Murray own kernel config file. 842f4865386SMark Murray Remove: 843f4865386SMark Murray options RANDOMDEV 844f4865386SMark Murray Add: 845f4865386SMark Murray device random 846f4865386SMark Murray If you prefer to load the loadable module, you need to do 847f4865386SMark Murray nothing. 848f4865386SMark Murray 849d594498fSWarner Losh20000909: 850d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 851d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 852d594498fSWarner Losh reflect this if you load this module at boot time. 853d594498fSWarner Losh The line should read: 854d594498fSWarner Losh random_load="YES" 855d594498fSWarner Losh 8560deb7ddcSWarner Losh20000907: 8570deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 85816eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 85916eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 86016eb772dSWarner Losh sure you don't have model loading problems which might at 86116eb772dSWarner Losh first blush appear related to SMP. 86252bf24e7SWarner Losh 8635a01880bSWarner Losh20000906: 8645a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 8655a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 8665a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 8675a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 8685a01880bSWarner Losh don't have one, and you have host.conf. 8695a01880bSWarner Losh 8702b41163cSWarner Losh20000905: 87138d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 87238d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 87338d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 87438d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 87538d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 87638d6ecd2SWarner Losh 87738d6ecd2SWarner Losh20000905: 8788aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 8798aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 8808aab4bc7SWarner Losh is /boot/kernel. 8818aab4bc7SWarner Losh 8828aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 88338d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 88438d6ecd2SWarner Losh installkernel/installworld dance. 8852b41163cSWarner Losh 886d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 887d594498fSWarner Losh before booting the new kernel, since kldload will find stale 888d594498fSWarner Losh modules in that directory instead of finding them in the correct 889d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 890d594498fSWarner Losh is that the linux module crashes your machine after the update. 891d594498fSWarner Losh 892d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 893d594498fSWarner Losh mv /modules.old /boot/kernel.old 894d594498fSWarner Losh chflags noschg /kernel.old 895d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 896d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 897d594498fSWarner Losh fi 898d594498fSWarner Losh 899c22a309cSWarner Losh20000904: 900c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 901c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 902c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 903c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 904c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 905c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 906c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 907c22a309cSWarner Losh is not likely to be generated. 908c22a309cSWarner Losh 909fdb9f54dSWarner Losh20000825: 910fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 9119c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 9129c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 9139c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 9149c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 9159c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 9169c1a7444SWarner Losh messages will appear after the boot loader tries to start the 9179c1a7444SWarner Losh kernel. 9189c1a7444SWarner Losh 9199c1a7444SWarner Losh20000821: 9209c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 9219c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 9229c1a7444SWarner Losh /boot/loader.conf. 923fdb9f54dSWarner Losh 9248f250aa7SWarner Losh20000812: 9255da0d091SWarner Losh suidperl is now always built and installed on the system, but 9265da0d091SWarner Losh with permissions of 511. If you have applications that use 9275da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 9285da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 9295da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 9305da0d091SWarner Losh will fix this until the next build. 9315da0d091SWarner Losh 9325da0d091SWarner Losh20000812: 9338f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 9348f250aa7SWarner Losh visible changes that may immediately affect your configuration 9358f250aa7SWarner Losh include: 9368f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 9378f250aa7SWarner Losh - newaliases limited to root and trusted users 9388f250aa7SWarner Losh - MSA port (587) turned on by default 9398f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 9408f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 9418f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 9428f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 9438f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 9448f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 9458f250aa7SWarner Losh 94671c38472SWarner Losh20000810: 94771c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 94871c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 94971c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 95071c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 95171c38472SWarner Losh specific use for it. 95271c38472SWarner Losh 95371c38472SWarner Losh20000729: 95471c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 95571c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 95671c38472SWarner Losh /etc/rc.conf if they want to have the same setup 95771c38472SWarner Losh afterwards (unless the variables already are set, of course): 95871c38472SWarner Losh # Enable network daemons for user convenience. 95971c38472SWarner Losh inetd_enable="YES" 96071c38472SWarner Losh portmap_enable="YES" 96171c38472SWarner Losh sendmail_enable="YES" 96271c38472SWarner Losh 96371c38472SWarner Losh20000728: 96471c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 96571c38472SWarner Losh will need to change that to nullfs_load="YES". 96671c38472SWarner Losh 9671dece4a9SWarner Losh20000728: 9681dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 9691dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 9701dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 9711dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 9721dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 9731dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 9741dece4a9SWarner Losh to /MYKERNEL. 9751dece4a9SWarner Losh 976409e887cSWarner Losh20000711: 977409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 978409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 979409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 980409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 981409e887cSWarner Losh for details on potential problems that you might have and how 982409e887cSWarner Losh to get around them. 983409e887cSWarner Losh 984409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 985409e887cSWarner Losh clauses above, you needn't worry. 986409e887cSWarner Losh 987409e887cSWarner Losh20000711: 988409e887cSWarner Losh /etc/security has been updated to print the inode number of 989409e887cSWarner Losh setuid programs that have changed. You will see a large spike 990409e887cSWarner Losh in the number of changed programs the first time when you run 991409e887cSWarner Losh mergemaster to get a new /etc/security. 992409e887cSWarner Losh 993673d13f2SWarner Losh20000710: 994673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 995673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 996673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 997673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 998673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 999673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 1000673d13f2SWarner Losh errors. (see below, 20000624). 1001673d13f2SWarner Losh 1002bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 10031dece4a9SWarner Losh 1004673d13f2SWarner Losh20000709: 1005c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 1006c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 1007c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 1008673d13f2SWarner Losh ln -s aj /etc/malloc.conf 1009673d13f2SWarner Losh 1010e98e26cdSWarner Losh20000706: 1011e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 1012e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 1013e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 1014f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 1015e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 10162c021c6cSMark Ovens interim if needed. 1017e98e26cdSWarner Losh 1018e98e26cdSWarner Losh20000705: 1019e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 1020e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 1021e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 1022e98e26cdSWarner Losh details. 1023e98e26cdSWarner Losh 1024c373950eSWarner Losh20000704: 10252f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 10262f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 10272f961bc8SWarner Losh 10282f961bc8SWarner Losh20000704: 1029c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1030c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1031c373950eSWarner Losh rc.d scripts that haven't been updated. 1032c373950eSWarner Losh 103327dc3a2bSWarner Losh20000630: 103427dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 103527dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 103627dc3a2bSWarner Losh which should be reported to des@freebsd.org. 103727dc3a2bSWarner Losh 1038b8c215acSWarner Losh20000625: 1039b8c215acSWarner Losh From approximately this date forward, one must have the crypto 104027dc3a2bSWarner Losh system installed in order to build the system and kernel. 104127dc3a2bSWarner Losh While not technically strictly true, one should treat it as 104227dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 104327dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 104427dc3a2bSWarner Losh were required. You should check with the latest collections 104527dc3a2bSWarner Losh to make sure that these haven't changed. 1046b8c215acSWarner Losh 10477b990719SWarner Losh20000624: 10487b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 10497b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 10507b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 10511a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 10527b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 10537b990719SWarner Losh openssh and openssl should not be used to generate keys from this 10547b990719SWarner Losh date to the completion of the work. 10557b990719SWarner Losh 105627dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 105727dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 105827dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 105927dc3a2bSWarner Losh recreate the random and urandom devices. 106027dc3a2bSWarner Losh 106181e54c50SWarner Losh20000622: 106281e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 106381e54c50SWarner Losh BSD license. You may need to remove your symbolic links 106481e54c50SWarner Losh that used to be required when updating. 106581e54c50SWarner Losh 106639943833SWarner Losh20000621: 10672c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 10682a2f33fbSDaniel Baker the config file update procedure. 10692a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1070c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 107159df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 107259df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 107339943833SWarner Losh 1074290f9ad8SWarner Losh20000620: 1075290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1076290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1077290f9ad8SWarner Losh that workaround will no longer be required. 1078290f9ad8SWarner Losh 107990fb6346SWarner Losh20000615: 108090fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 108190fb6346SWarner Losh ad driver. If you haven't done so already, you must update 108290fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 108390fb6346SWarner Losh devices. 108490fb6346SWarner Losh 1085f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1086f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1087f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1088f75f65bbSWarner Losh may work). 1089f75f65bbSWarner Losh 1090ba26da8eSWarner Losh20000612: 1091ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1092290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1093c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1094290f9ad8SWarner Losh to your config file to compile them in statically. The format 1095f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1096f54a3542SWarner Losh NEWCARD for examples of the new format. 1097290f9ad8SWarner Losh 10989698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 10999698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 11009698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 11019698f2c0SWarner Losh in it. 1102bbcc5149SWarner Losh 1103d65850ebSWarner Losh20000522: 1104ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1105d65850ebSWarner Losh building a kernel after this point is advised that they need 1106d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1107d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1108d65850ebSWarner Losh 1109d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1110d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1111d9583a00SWarner Losh is recommended that you don't set this option until the problem 1112d9583a00SWarner Losh is resolved. 1113d9583a00SWarner Losh 11148039cedeSWarner Losh20000513: 11158039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 11168039cedeSWarner Losh 1117d65850ebSWarner Losh20000510: 11188039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 11198039cedeSWarner Losh This will require some care in updating alphas. A new libstand 11208039cedeSWarner Losh is requires for the boot blocks to build properly. 11218039cedeSWarner Losh 11228039cedeSWarner Losh20000503: 11238039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 11248039cedeSWarner Losh is now available. 11258039cedeSWarner Losh 1126d65850ebSWarner Losh20000502: 1127d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1128d65850ebSWarner Losh connected to the kernel building instead. 1129d65850ebSWarner Losh 1130be149406SNik Clayton20000427: 11318039cedeSWarner Losh You may need to build gperf 11328039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 11338039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 11348039cedeSWarner Losh an option only in -current. 11358039cedeSWarner Losh 11362b8dd5f4SWarner Losh20000417: 11372b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1138f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 11392b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 11402b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 11412c021c6cSMark Ovens before you reboot, you'll need to issue: 11422b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 11432b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 11442b8dd5f4SWarner Losh 11458d9f1945SWarner Losh20000320: 11462b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 11472b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 11482b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1149ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 11502b8dd5f4SWarner Losh to the start of /etc/rc.conf. 11518d9f1945SWarner Losh 1152f8ab1dd6SWarner Losh20000319: 1153f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1154f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1155f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1156f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1157f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1158f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1159f8ab1dd6SWarner Losh 116019cada77SWarner Losh20000318: 1161f699bbbbSMark Ovens We've entered the traditional post release dumping party. 116219cada77SWarner Losh Large kernel changes are being committed and are in the 116319cada77SWarner Losh works. It is important to keep the systems' klds and kernel 116419cada77SWarner Losh in sync as kernel interfaces and structures are changing. 116519cada77SWarner Losh Before reporting kernel panics, make sure that all modules 116619cada77SWarner Losh that you are loading are up to date. 1167ba228352SWarner Losh 116819cada77SWarner Losh20000315: 11696d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 11706d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 11716d23c382SWarner Losh will do the trick. This isn't critical until you remove your 11726d23c382SWarner Losh wd device entries in /dev, at which point your system will not 11736d23c382SWarner Losh boot. 11746d23c382SWarner Losh 11756d23c382SWarner Losh20000315: 117619cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 117719cada77SWarner Losh to upgrade to 4.0 from 3.x. 117857199806SWarner Losh 1179dc0dbf5cSWarner LoshCOMMON ITEMS: 1180dc0dbf5cSWarner Losh 1181a24eff53SWarner Losh General Notes 1182a24eff53SWarner Losh ------------- 1183a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1184a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1185a24eff53SWarner Losh installworld. This is especially true when upgrading between 1186a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1187a24eff53SWarner Losh or several minor releases, or when several months have passed 1188a24eff53SWarner Losh on the -current branch). 1189a24eff53SWarner Losh 11905780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 11915780f3baSWarner Losh poisoning. This can happen because the make utility reads its 11925780f3baSWarner Losh environment when searching for values for global variables. 11935780f3baSWarner Losh To run your build attempts in an "environmental clean room", 11945780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 11955780f3baSWarner Losh page for more details. 11965780f3baSWarner Losh 1197dc0dbf5cSWarner Losh To build a kernel 1198dc0dbf5cSWarner Losh ----------------- 1199ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1200f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1201ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 1202282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1203282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1204dc0dbf5cSWarner Losh 1205ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1206ba01eb20SWarner Losh -------------------------------------------------------------- 1207ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 120847d0d01fSWarner Losh config KERNEL_NAME_HERE 1209ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1210ba01eb20SWarner Losh make depend 1211ba01eb20SWarner Losh make 1212ba01eb20SWarner Losh make install 1213ba01eb20SWarner Losh 1214ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1215ba01eb20SWarner Losh 1216ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1217ba01eb20SWarner Losh ----------------------------------------------------------- 121863cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 121963cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 122063cb445eSWarner Losh 1221f643de42SWarner Losh <make sure you have good level 0 dumps> 122263cb445eSWarner Losh <maybe fix /etc/fstab> [7] 122363cb445eSWarner Losh make buildworld 122463cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 122563cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 122663cb445eSWarner Losh [1] 122763cb445eSWarner Losh <reboot in single user> [3] 122863cb445eSWarner Losh mergemaster -p [5] 122963cb445eSWarner Losh make installworld 123063cb445eSWarner Losh mergemaster [4] 123163cb445eSWarner Losh <reboot> 123263cb445eSWarner Losh 1233759f0aefSWarner Losh 1234f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1235f27b1fceSJoseph Koshy -------------------------------------------------- 1236f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1237f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1238f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1239f27b1fceSJoseph Koshy # size. 1240f27b1fceSJoseph Koshy 1241f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1242f27b1fceSJoseph Koshy <boot into -stable> 1243f27b1fceSJoseph Koshy make buildworld 1244f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1245f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1246f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1247f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1248f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1249f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1250f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1251f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1252f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1253f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1254f27b1fceSJoseph Koshy <reboot into current> 1255f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1256f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1257f27b1fceSJoseph Koshy <reboot> 1258f27b1fceSJoseph Koshy 1259f27b1fceSJoseph Koshy 1260f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1261f27b1fceSJoseph Koshy ---------------------------------------------- 12625c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 12635c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 12645c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 12655c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1266ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1267f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1268f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1269f643de42SWarner Losh # space on /. 1270f643de42SWarner Losh 1271f643de42SWarner Losh <make sure you have good level 0 dumps> 1272fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 127321c075eaSWarner Losh make buildworld [9] 1274c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1275d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1276be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1277fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1278fc8c157fSWarner Losh [1] 1279fc8c157fSWarner Losh <reboot in single user> [3] 1280835284beSWarner Losh mergemaster -p [5] 1281f8a4c901SWarner Losh rm -rf /usr/include/g++ 1282ba26da8eSWarner Losh make installworld 1283a6cd4f9dSWarner Losh mergemaster [4] 1284ba26da8eSWarner Losh <reboot> 1285ba26da8eSWarner Losh 1286fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1287fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1288fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1289fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1290fdb9f54dSWarner Losh the UPDATING entries. 1291ba26da8eSWarner Losh 12921dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 12931dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 12941dece4a9SWarner Losh your sources that you have read and understood all the recent 12951dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 12961dece4a9SWarner Losh much fewer pitfalls. 12971dece4a9SWarner Losh 1298134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1299134d2e86SWarner Losh should disable them at this point so they don't crash your 1300134d2e86SWarner Losh system on reboot. 1301134d2e86SWarner Losh 13029c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 13039c1a7444SWarner Losh your own device.hints to reflect your unique hardware 13049c1a7444SWarner Losh configuration. 13059c1a7444SWarner Losh 1306ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1307ee6e1fc3SWarner Losh fsck -p 1308ee6e1fc3SWarner Losh mount -u / 1309ee6e1fc3SWarner Losh mount -a 1310ee6e1fc3SWarner Losh cd /usr/src 131147d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1312f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1313f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1314b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1315b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1316b705ae10SWarner Losh be ignored while you proceed to the next step. 1317ee6e1fc3SWarner Losh 1318a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1319a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1320a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1321a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1322a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1323a6cd4f9dSWarner Losh for potential gotchas. 1324a6cd4f9dSWarner Losh 1325835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1326835284beSWarner Losh you may need to do this if you get unknown user in the following 1327835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1328835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1329835284beSWarner Losh install) after the buildworld before this step if you last updated 1330835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1331835284beSWarner Losh 1332bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1333bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1334bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1335bd79cf40SWarner Losh ok unload 1336bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1337bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1338bd79cf40SWarner Losh described here. 1339fc8c157fSWarner Losh 1340fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1341fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1342fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1343fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1344fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1345fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1346fc8c157fSWarner Losh 1347c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1348c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1349c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1350c74fe6afSWarner Losh that is hard to boot to recover. 1351c74fe6afSWarner Losh 135221c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 135321c075eaSWarner Losh cvs prune empty directories. 1354dc0dbf5cSWarner LoshFORMAT: 1355dc0dbf5cSWarner Losh 1356f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 13571fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1358f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1359f8ab1dd6SWarner Loshprevious releases if your system is older than this. 13601fc1a0dcSWarner Losh 1361e72fd46aSWarner LoshCopyright information: 1362e72fd46aSWarner Losh 13639698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1364e72fd46aSWarner Losh 1365772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1366772730c7SWarner Loshmodification, in full or in part, in any form or format of this 13679698f2c0SWarner Loshdocument are permitted without further permission from the author. 1368e72fd46aSWarner Losh 1369e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1370e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1371e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1372e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1373e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1374e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1375e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1376e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1377e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1378e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1379e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1380e72fd46aSWarner Losh 1381e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1382e72fd46aSWarner Loshauthor a beer. 1383e72fd46aSWarner Losh 138422306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1385772730c7SWarner Loshthis document. 1386772730c7SWarner Losh 138797d92980SPeter Wemm$FreeBSD$ 1388