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 20c09d2c2bSMike Makonnen20030829: 21c09d2c2bSMike Makonnen The following rc.d scripts have been removed and should be 22c09d2c2bSMike Makonnen deleted from your installation: atm2.sh atm3.sh devdb 23c09d2c2bSMike Makonnen localdaemons network1 network2 network3. Depending on when 24c09d2c2bSMike Makonnen you last updated world and used mergemaster(8) you may or 25c09d2c2bSMike Makonnen may not have problems during the rc boot sequence. The simplest 26c09d2c2bSMike Makonnen solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 27c09d2c2bSMike Makonnen The atm2.sh atm3.sh and devdb scripts were removed some time 28c09d2c2bSMike Makonnen ago, so depending on when you installed -CURRENT these scripts 29c09d2c2bSMike Makonnen may or may not exist on your system. 30c09d2c2bSMike Makonnen 3117c159dcSSøren Schmidt20030824: 3217c159dcSSøren Schmidt ATAng has been committed. You need to build world as sys/ata.h 3317c159dcSSøren Schmidt has changed, and userland atacontrol depends on it. 34f240812bSSøren Schmidt If you use ATA SW raids you need "device ataraid" in your 35f240812bSSøren Schmidt kernel config file, as it is no longer pulled in automatically. 3617c159dcSSøren Schmidt 37c1f61aa9SDavid E. O'Brien20030819: 38c1f61aa9SDavid E. O'Brien The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 39c1f61aa9SDavid E. O'Brien Among other things, this changes the device enumeration to be 40c1f61aa9SDavid E. O'Brien closer to Solaris. Be aware that, this can even cause the machine 41c1f61aa9SDavid E. O'Brien to not boot without manual intervention before the fstab is adjusted. 4269f7bcf3SWarner Losh 4338c962e7SNate Lawson20030728: 4438c962e7SNate Lawson All current USB and Firewire quirks in da(4) have been deprecated 4538c962e7SNate Lawson and will be removed for 5.2. If this causes failure for your 4638c962e7SNate Lawson umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 4738c962e7SNate Lawson and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 4838c962e7SNate Lawson so the quirk can be re-enabled. 4938c962e7SNate Lawson 50178cf4e9SWarner Losh20030722: 51178cf4e9SWarner Losh FPU-less support has been removed from FreeBSD. Chances are you won't 52178cf4e9SWarner Losh notice. 386+387 support should still work after this change, but 53178cf4e9SWarner Losh it is now a minimum requirement for the i386 port that you have real 54178cf4e9SWarner Losh FPU hardware. 55178cf4e9SWarner Losh 56178cf4e9SWarner Losh20030714: 57178cf4e9SWarner Losh Some people are having problems with changes related to /rescue. 58178cf4e9SWarner Losh If you are building -j N, you will need to define NO_RESCUE. Others 59178cf4e9SWarner Losh will need to define it if /rescue has issues with their environment. 60178cf4e9SWarner Losh People should report those issues to current@. 61178cf4e9SWarner Losh 62157c629aSWarner Losh20030711: 63157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 648b71efcaSCeri Davies across this point. Further, it might be a good idea to remove 6505538fa9SWarner Losh /usr/obj. 66157c629aSWarner Losh 676cc6353fSMarcel Moolenaar20030613: [retrospective] 686cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 696cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 706cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 716cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 726cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 736cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 746cc6353fSMarcel Moolenaar 756cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 766cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 776cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 786cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 796cc6353fSMarcel Moolenaar : 806cc6353fSMarcel Moolenaar 816cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 826cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 836cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 846cc6353fSMarcel Moolenaar 85766c34e4SAndrey A. Chernov20030610: 86766c34e4SAndrey A. Chernov Remove deprecated locale names and transition period code 87766c34e4SAndrey A. Chernov for them, finishing switching to the new scheme. Check your 88766c34e4SAndrey A. Chernov LANG environment variable. 89766c34e4SAndrey A. Chernov 907ddc2528SPoul-Henning Kamp20030609: 91df622d54SPoul-Henning Kamp CCD has been changed to be a fully GEOMified class. Kernel 92df622d54SPoul-Henning Kamp and ccdconfig(8) needs to be in sync, this is particularly 93df622d54SPoul-Henning Kamp important to remember beforehand if your source tree is on 94df622d54SPoul-Henning Kamp a ccd device. Consider making a copy of the old ccdconfig 95df622d54SPoul-Henning Kamp into /boot/kernel.good or wherever you keep your backup 96df622d54SPoul-Henning Kamp kernel. 97df622d54SPoul-Henning Kamp 9852b47445SMark Murray20030505: 9952b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 10052b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 10152b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 10252b47445SMark Murray 103a26df538SWarner Losh20030502: 104a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 105a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 106a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 107a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 108a26df538SWarner Losh 1094b065e2cSDoug Barton20030501: 1104b065e2cSDoug Barton The old rc system has been removed. Please report any problems 1114b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 1124b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 1134b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 1144b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 1154b065e2cSDoug Barton utilizes these old scripts has also been removed. 1164b065e2cSDoug Barton 11781cda3d9SWarner Losh20030423: 11881cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 11981cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 12081cda3d9SWarner Losh work around in devd will be removed around 20030507. You 12181cda3d9SWarner Losh have until then to upgrade your kernel before updating 12281cda3d9SWarner Losh userland. In general, you should have a userland and 12381cda3d9SWarner Losh kernel that's in sync with each other. However, given the 12481cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 12581cda3d9SWarner Losh allowances are made. 12681cda3d9SWarner Losh 12747a657d1SRuslan Ermilov20030329: 12847a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 12947a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 13047a657d1SRuslan Ermilov while upgrading the system through a buildworld. 13147a657d1SRuslan Ermilov 13247a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 13347a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 13447a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 13547a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 13647a657d1SRuslan Ermilov 13747a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 13847a657d1SRuslan Ermilov make cleandir && make obj && \ 13947a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 14047a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 14147a657d1SRuslan Ermilov 1425d2af00cSGregory Neil Shapiro20030208: 1435d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 1445d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 1455d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 1465d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 1475d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 1485d2af00cSGregory Neil Shapiro 1495d2af00cSGregory Neil Shapiro20030128: 1509db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 151ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 1529db58771SPoul-Henning Kamp be removed when convenient. 1539db58771SPoul-Henning Kamp 1548d9b3f57SJake Burkholder20030126: 1558d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 1568d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 1578d9b3f57SJake Burkholder 1581c5efda5SJeff Roberson20030125: 1591c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 1601c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 161ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 1621c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 1631c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 1641c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 1651c5efda5SJeff Roberson 1669d1d64f5SWarner Losh20030115: 1679d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 1689d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 1699d1d64f5SWarner Losh properly. 1709d1d64f5SWarner Losh 171c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 172c9fdb80aSWarner Losh configured for point to point links to bring it more in line 173c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 174c9fdb80aSWarner Losh with NetBSD. 175c9fdb80aSWarner Losh 176161dc364SAlexander Kabaev20021222: 177161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 178161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 179161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 180161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 181161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 182161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 18384cc83efSAlexander Kabaev rebuilt. 184161dc364SAlexander Kabaev 185fb4c8061SMartin Blapp20021216: 186fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 18789056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 188fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 1899d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 190fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 191fb4c8061SMartin Blapp 19217d47eb3SGiorgos Keramidas20021202: 19317d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 19417d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 19517d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 19617d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 19717d47eb3SGiorgos Keramidas 198a4459294SBill Fenner20021029: 199a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 200a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 201a4459294SBill Fenner consumers in sync. 202a4459294SBill Fenner 203fc8c157fSWarner Losh20021024: 204c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 205c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 206c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 207c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 208c57404feSRuslan Ermilov partition really is on. The old device names have gone 209c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 210c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 211c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 21269f7bcf3SWarner Losh 213fd9e8bdaSAndrew Gallatin20021023: 214fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 215fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 216fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 217fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 218fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 219fd9e8bdaSAndrew Gallatin 220fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 221fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 222fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 223fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 224fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 225fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 226fd9e8bdaSAndrew Gallatin 227f8a4c901SWarner Losh20020831: 228f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 229f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 230f8a4c901SWarner Losh programs and libraries need to be recompiled. 231f8a4c901SWarner Losh 232f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 233f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 234f8a4c901SWarner Losh 235c2248fa2SJens Schweikhardt20020827: 236c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 237c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 238c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 239c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 240c2248fa2SJens Schweikhardt 2410d533e43SRuslan Ermilov20020815: 2420d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 2430d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 2440d533e43SRuslan Ermilov again. 2450d533e43SRuslan Ermilov 24633c1de7dSRuslan Ermilov20020729: 24733c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 24833c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 24933c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 25033c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 25133c1de7dSRuslan Ermilov 2522b877facSJulian Elischer20020702: 2532b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 2542b877facSJulian Elischer There are still some minor problems with some signals but the 2552b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 2562b877facSJulian Elischer but each can successfully complete multiple buildworlds. 2572b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 2582b877facSJulian Elischer 25906596d37SWarner Losh20020701: 26006596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 26106596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 26206596d37SWarner Losh GNOME. 26306596d37SWarner Losh 26495ba4330SJacques Vidrine20020511: 26595ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 26695ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 26795ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 26895ba4330SJacques Vidrine with the set-user-ID bit set. 26995ba4330SJacques Vidrine 270a81da3c9SDavid E. O'Brien20020510: 271f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 272f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 2734b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 274f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 275f50caf6fSDavid E. O'Brien 276f50caf6fSDavid E. O'Brien20020510: 277a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 278a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 279a81da3c9SDavid E. O'Brien and then do a cvs update. 280a81da3c9SDavid E. O'Brien 281528a0ef5SJacques Vidrine20020421: 282528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 283528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 284528a0ef5SJacques Vidrine 28585aa5a2eSGregory Neil Shapiro20020404: 28685aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 28785aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 28885aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 28985aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 29085aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 29185aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 29285aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 29385aa5a2eSGregory Neil Shapiro 2948f1e4358SRuslan Ermilov20020403: 2958f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 2968f1e4358SRuslan Ermilov 2972292c02eSWarner Losh20020315: 2982292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 2992292c02eSWarner Losh 30069f7bcf3SWarner Losh20020225: 30169f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 30269f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 30369f7bcf3SWarner Losh 3048f35c493SWarner Losh20020217: 3058f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 3068f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 3078f35c493SWarner Losh command line mail submission has changed. Be sure to run 3088f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 3098f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 3108f35c493SWarner Losh 311835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 312835284beSWarner Losh required in order for sendmail to run as a set-group-ID 313835284beSWarner Losh binary. A 'make installworld' will use the new user and group 314835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 315835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 316835284beSWarner Losh and group must be merged from src/etc/group and 317835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 318835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 319835284beSWarner Losh mergemaster before this will work if you are updating from a 320835284beSWarner Losh very old version of current. The updating recipe has changed 321835284beSWarner Losh as of this date. 322835284beSWarner Losh 323fa9401c1SWarner Losh20020112: 324fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 325fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 326fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 327fa9401c1SWarner Losh you have local modifications, you can use 328fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 329fa9401c1SWarner Losh /etc/pam.d. 330fa9401c1SWarner Losh 331fa9401c1SWarner Losh Please see the following url for more details: 332fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 33347d0d01fSWarner Losh20011229: 33447d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 33547d0d01fSWarner Losh networkfs_types, please note that it has changed 33647d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 33747d0d01fSWarner Losh 338514318a8SWarner Losh20011220: 339514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 340514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 341514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 342514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 343514318a8SWarner Losh version have now been merged back into the base system's 344514318a8SWarner Losh version now. The only user-visible change resulting from this 345514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 346514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 347514318a8SWarner Losh as well. (There has never been rc file support for 348514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 349514318a8SWarner Losh reverted by the time the changes are MFCed.) 350514318a8SWarner Losh 351514318a8SWarner Losh20011215: 352514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 353514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 354514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 355514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 356514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 357514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 358514318a8SWarner Losh will need to be customized then for `odd' densities using 359514318a8SWarner Losh fdcontrol(8). 360514318a8SWarner Losh 3612d22e2bfSWarner Losh20011209: 3622d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 3632d22e2bfSWarner Losh and truss(1) now works again. 3642d22e2bfSWarner Losh 3659e0428e2SWarner Losh20011207: 3669e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 3679e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 3689e0428e2SWarner Losh see 3699e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 3709e0428e2SWarner Losh for details. 3719e0428e2SWarner Losh 3729bab8c59SWarner Losh20011204: 3739bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 3749bab8c59SWarner Losh kernel and burncd to be in sync. 3759bab8c59SWarner Losh 376e57d8b01SWarner Losh20011203: 377e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 378e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 379e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 380e57d8b01SWarner Losh not there already. 381e57d8b01SWarner Losh 382e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 383e57d8b01SWarner Losh until the issue has been resolved. 384e57d8b01SWarner Losh 385b001d36fSJacques Vidrine20011202: 386b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 387b001d36fSJacques Vidrine patched. 388b001d36fSJacques Vidrine 3894b676ec1SWarner Losh20011126: 3904b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 3915ebbf43eSWarner Losh after this date. You need to do this only once. 3924b676ec1SWarner Losh 393d961e462SWarner Losh20011103: 394d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 395d961e462SWarner Losh edges may be left, but for the most part things should be 3964b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 397d961e462SWarner Losh 398d961e462SWarner Losh20011030: 399d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 400d961e462SWarner Losh choppy waves in the upgrade process. 401d961e462SWarner Losh 4021fe003b6SWarner Losh20011030: 403a4b6fda0SWarner Losh The asr driver problem has been resolved. 4041fe003b6SWarner Losh 4051fe003b6SWarner Losh20011027: 4061fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 4071fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 4081fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 4091fe003b6SWarner Losh try to use from this date forward. 4101fe003b6SWarner Losh 4111fe003b6SWarner Losh20011025: 4121fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 4131fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 4141fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 4151fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 4161fe003b6SWarner Losh TARGET_ARCH=i386. 4171fe003b6SWarner Losh 418d05f9643SWarner Losh20011001: 419d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 420d05f9643SWarner Losh You must recompile both the kernel and userland applications 421d05f9643SWarner Losh at the same time. 422d05f9643SWarner Losh 42358970f85SWarner Losh20010929: 42458970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 42558970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 42658970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 42758970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 4289d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 42958970f85SWarner Losh 43058970f85SWarner Losh20010927: 43158970f85SWarner Losh Some weird problems result from using ACPI on some machines. 43258970f85SWarner Losh To disable ACPI you can add 43366ff0e67SMax Khon hint.acpi.0.disabled="1" 43458970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 43558970f85SWarner Losh loader "ok" prompt). 43658970f85SWarner Losh 43758970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 43858970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 43958970f85SWarner Losh file and not list acpi in that list. 440378f4486SAlfred Perlstein 4415119d237SWarner Losh20010924: 4425119d237SWarner Losh The buildworld has been fixed. You may need to install 4435119d237SWarner Losh the 4.x compatibility libraries for some old binaries 4448b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 4458b039fffSWarner Losh get them installed on every installworld, or execute the 4468b039fffSWarner Losh following to get them installed only once: 4478b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 44858970f85SWarner Losh make all install 4498b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 4505119d237SWarner Losh 4513c293725SWarner Losh20010919: 4523c293725SWarner Losh There's a bug in the world build process. The cross-tools 4533c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 4543c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 455772730c7SWarner Losh workaround is to add 4563c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 4573c293725SWarner Losh before building world when upgrading from 4.x to current. This 4583c293725SWarner Losh can be removed afterwards. 4593c293725SWarner Losh 4603c293725SWarner Losh A proper fix to the buildworld target is needed. 4613c293725SWarner Losh 4623c293725SWarner Losh20010918: 4633c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 4643c293725SWarner Losh NFS may be unstable after this date. 4653c293725SWarner Losh 4663c293725SWarner Losh20010912: 4673c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 4683c293725SWarner Losh the kernel. While a few problems were introduced in the 4693c293725SWarner Losh initial commit, most of the major ones have been found and 4703c293725SWarner Losh corrected. 4713c293725SWarner Losh 4723c293725SWarner Losh20010901: 4733c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 4743c293725SWarner Losh arounds described in the 20010604 entry are now no longer 4753c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 4763c293725SWarner Losh have been rectified around this date. 4773c293725SWarner Losh 47898b17b95SWarner Losh20010823: 47998b17b95SWarner Losh named now runs as user bind and group bind rather than as 48098b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 48198b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 48298b17b95SWarner Losh and that group bind is available in /etc/group. Also make 48398b17b95SWarner Losh sure that user or group bind has read (and not write) 48498b17b95SWarner Losh permission for your name server configuration and that it 48598b17b95SWarner Losh has read and write permission for your slave zone files and 48698b17b95SWarner Losh directory. 48798b17b95SWarner Losh 48898b17b95SWarner Losh If you wish to continue to run named as root (a less secure 48998b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 49098b17b95SWarner Losh 49198b17b95SWarner Losh named_flags= 49298b17b95SWarner Losh 4937b9786edSMark Murray20010709: 4947b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 4957b9786edSMark Murray the ability of the shared library major number to handle. 4967b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 4977b9786edSMark Murray solution is to rebuild those ports. 4987b9786edSMark Murray 4991d28950eSWarner Losh20010628: 5001d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 5011d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 5021d28950eSWarner Losh 503e72fd46aSWarner Losh20010625: 50498b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 50598b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 50698b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 50798b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 50898b17b95SWarner Losh IRQ configuration needs more safety belts. 50916de1a07SWarner Losh 5100d415dffSWarner Losh20010617: 511e72fd46aSWarner Losh Softupdates problems have been corrected. 5120d415dffSWarner Losh 5130d415dffSWarner Losh20010614: 5140d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 5150d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 5160d415dffSWarner Losh kernel building methods. 5170d415dffSWarner Losh 5188b9959adSWarner Losh20010613: 5198b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 5208b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 521e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 522e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 5238b9959adSWarner Losh 524e72fd46aSWarner Losh20010613: 5258b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 526e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 527e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 5288b9959adSWarner Losh 5290d415dffSWarner Losh20010612: 5300d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 5310d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 5320d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 5330d415dffSWarner Losh work around this issue, please use only one or the other mechanism 5340d415dffSWarner Losh until this bug is fixed. 5350d415dffSWarner Losh 536e72fd46aSWarner Losh Please note that a feature of config is that if you have config 537e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 538ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 539e72fd46aSWarner Losh 5400d415dffSWarner Losh20010610: 5410d415dffSWarner Losh Locale names have changed to match other systems better. 5420d415dffSWarner Losh 5436ccdb5e4SWarner Losh20010604: 5446ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 5456ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 5466ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 5473590182eSWarner Losh Interrupt storms look a lot like a hang. 5483590182eSWarner Losh 5493590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 5503590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 5513590182eSWarner Losh it is). 5523590182eSWarner Losh 5533590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 5543590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 5553590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 5563590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 5576ccdb5e4SWarner Losh 5580bc62786SWarner Losh20010530: 5590bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 5600bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 5610bc62786SWarner Losh a limited time. If you see 5620bc62786SWarner Losh 5630bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 5640bc62786SWarner Losh 5650bc62786SWarner Losh in your makeworld, then you need to migrate towards using 5660bc62786SWarner Losh COPY=-C. 5670bc62786SWarner Losh 56868a38c6cSWarner Losh20010525: 569b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 570c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 571c4f4a728SWarner Losh definitely is in bad shape. 57268a38c6cSWarner Losh 573ed0f29caSWarner Losh20010521: 574ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 575ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 576ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 577ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 578ed0f29caSWarner Losh is 579ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 580ed0f29caSWarner Losh 58180c16af9SWarner Losh20010520: 58268a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 58380c16af9SWarner Losh 58480c16af9SWarner Losh20010519: 58580c16af9SWarner Losh pccard has had much reorganizational work done to it over 58680c16af9SWarner Losh the past few days. Everything should still work, but if 58780c16af9SWarner Losh not, please contact imp@freebsd.org. 58880c16af9SWarner Losh 589a45f2d05SWarner Losh20010517: 590a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 591a45f2d05SWarner Losh userland at the same time. 592a45f2d05SWarner Losh 593a45f2d05SWarner Losh20010517: 594a45f2d05SWarner Losh New ncurses imported. 595a45f2d05SWarner Losh 5962988afcaSWarner Losh20010512: 5972988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 5982988afcaSWarner Losh will be the only way to go starting July 1. 5992988afcaSWarner Losh 6001a33dba7SWarner Losh20010504: 6011a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 6021a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 6031a33dba7SWarner Losh 60409946a51SWarner Losh20010502: 60509946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 60609946a51SWarner Losh 60709946a51SWarner Losh20010501: 60809946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 60909946a51SWarner Losh 61009946a51SWarner Losh20010430: 611a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 61209946a51SWarner Losh go back in the water. 61309946a51SWarner Losh 61409946a51SWarner Losh20010429: 61509946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 61609946a51SWarner Losh this date, but before the correction date. 61709946a51SWarner Losh 61891dd3b53SWarner Losh20010423: 61991dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 62091dd3b53SWarner Losh 62191dd3b53SWarner Losh20010411: 62291dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 62391dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 62491dd3b53SWarner Losh Update only if you understand that you must not use the old 62591dd3b53SWarner Losh fsck with the new kernel ever. 62691dd3b53SWarner Losh 627933b3269SWarner Losh20010330: 628933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 629c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 630933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 631933b3269SWarner Losh 632933b3269SWarner Losh20010319: 633933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 634933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 635933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 636f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 63709946a51SWarner Losh 63809946a51SWarner Losh20010315: 63909946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 640ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 64109946a51SWarner Losh been replaced by tunables. See ata.4 for details. 642933b3269SWarner Losh 643933b3269SWarner Losh20010312: 644933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 645933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 646933b3269SWarner Losh 647933b3269SWarner Losh20010312: 648933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 649933b3269SWarner Losh instead of ad-hoc. 650933b3269SWarner Losh 651933b3269SWarner Losh20010310: 652f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 653933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 654933b3269SWarner Losh ssh might not work if you don't. 655933b3269SWarner Losh 65662353691SWarner Losh20010303: 65762353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 65862353691SWarner Losh which means that you must include the miibus in your kernel if 65962353691SWarner Losh you use the ed driver. 66062353691SWarner Losh 661d325cf65SWarner Losh20010220: 662d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 663d325cf65SWarner Losh safe to go back into the water. 664d325cf65SWarner Losh 665024daae6SWarner Losh20010211: 666024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 667024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 668024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 669024daae6SWarner Losh that before upgrading would be a good time to do a level 0 670024daae6SWarner Losh dump of your system. No, really, I mean it this time. 671024daae6SWarner Losh 672024daae6SWarner Losh To get to the new system, you'll need to use the following 673024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 674024daae6SWarner Losh don't have to move this to the updating section. 675024daae6SWarner Losh 676024daae6SWarner Losh To get around the installworld problem, do: 677024daae6SWarner Losh # cd /usr/src/usr.bin/sed 678024daae6SWarner Losh # make install 679024daae6SWarner Losh # cd /usr/src 680024daae6SWarner Losh # make installworld 681024daae6SWarner Losh If that doesn't work, then try: 682024daae6SWarner Losh # make -k installworld 683024daae6SWarner Losh # make installworld 684024daae6SWarner Losh 685024daae6SWarner Losh20010207: 686024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 687024daae6SWarner Losh do not include devfs in your kernel as problems result. 688024daae6SWarner Losh 689024daae6SWarner Losh20010205: 6907595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 691024daae6SWarner Losh Remove them from your config. 692024daae6SWarner Losh 6931e159248SWarner Losh20010122: 6941e159248SWarner Losh ****************************** WARNING ****************************** 6951e159248SWarner Losh buildkernel has been changed slightly 6961e159248SWarner Losh ****************************** WARNING ****************************** 6971e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 6981e159248SWarner Losh should update your scripts and make.conf accordingly. 6991e159248SWarner Losh 7001e159248SWarner Losh20010119: 7011e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 7021e159248SWarner Losh This requires a new config to build correctly. 7031e159248SWarner Losh 704aac7dfeaSWarner Losh20010116: 705ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 706aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 707aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 708aac7dfeaSWarner Losh 709aac7dfeaSWarner Losh20010110: 710aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 711aac7dfeaSWarner Losh 712aac7dfeaSWarner Losh20010102: 713aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 714aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 715aac7dfeaSWarner Losh 71663c90c9eSWarner Losh20010101: 71763c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 71863c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 7195fd2a895SWarner Losh dump while building termcap. You can work around this problem 72063c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 72163c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 72263c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 72363c90c9eSWarner Losh might have been ignored by the -k option. 72463c90c9eSWarner Losh 7255fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 7265fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 7275fd2a895SWarner Losh of this working. 7285fd2a895SWarner Losh 729aac7dfeaSWarner Losh20001228: 730aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 731ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 732aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 733aac7dfeaSWarner Losh 734de2bcc63SWarner Losh20001218: 735de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 736de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 737de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 738de2bcc63SWarner Losh cards will not be recognized without it. 739de2bcc63SWarner Losh 740960773f7SWarner Losh20001205: 741960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 742960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 743960773f7SWarner Losh adding the following in pam.conf: 744960773f7SWarner Losh 745960773f7SWarner Losh sshd auth sufficient pam_skey.so 746960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 747960773f7SWarner Losh sshd session required pam_permit.so 748960773f7SWarner Losh 7490acc635eSWarner Losh20001031: 7500acc635eSWarner Losh cvs updated to 1.11. 7510acc635eSWarner Losh 7520acc635eSWarner Losh20001020: 7530acc635eSWarner Losh The random device needs more entropy, so you need to make sure 7540acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 7550acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 7560acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 7570acc635eSWarner Losh workaround. 7580acc635eSWarner Losh 7590acc635eSWarner Losh20001010: 7600acc635eSWarner Losh ****************************** WARNING ****************************** 7610acc635eSWarner Losh Sendmail has been updated. 7620acc635eSWarner Losh ****************************** WARNING ****************************** 7630acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 7640acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 7650acc635eSWarner Losh is set. 7660acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 7670acc635eSWarner Losh commands. 7680acc635eSWarner Losh o Now using sendmail's version of vacation(1). 7690acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 7700acc635eSWarner Losh in /usr/share/sendmail/cf. 7710acc635eSWarner Losh o sendmail.cw changed to local-host-names 7720acc635eSWarner Losh 7730acc635eSWarner Losh More details can be found at 7740acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 7750acc635eSWarner Losh 7766e98a146SWarner Losh20001009: 7776e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 7786e98a146SWarner Losh your entire ports tree, or you will have problems. 7796e98a146SWarner Losh 7806e98a146SWarner Losh20001006: 781685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 7826e98a146SWarner Losh the installed miniperl. It is recommended that you delete 7836e98a146SWarner Losh /usr/bin/miniperl. 7846e98a146SWarner Losh 785073113a4SWarner Losh20001005: 786073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 787685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 788073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 789073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 790073113a4SWarner Losh tree for anything to work. 791073113a4SWarner Losh 7920acc635eSWarner Losh20000928: 7930acc635eSWarner Losh There was a change in the passwd format. Need more information. 7940acc635eSWarner Losh 795be3885b3SWarner Losh20000916: 796be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 797be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 798be3885b3SWarner Losh same time as your kernel. 799be3885b3SWarner Losh 80076ec9675SWarner Losh20000914: 80176ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 80276ec9675SWarner Losh include the device will cause suspended laptops losing time 80376ec9675SWarner Losh when they resume. Include 80476ec9675SWarner Losh device pmtimer 80576ec9675SWarner Losh in your config file and 80601b9a434SWarner Losh hint.pmtimer.0.at="isa" 80776ec9675SWarner Losh to your /boot/device.hints file. 80876ec9675SWarner Losh 809f4865386SMark Murray20000911: 810f4865386SMark Murray The random device has been turned into a (pseudo-)device, 811f4865386SMark Murray rather than an option. The supplied kernel config files have 812f4865386SMark Murray been updated. You will need to do something similar in your 813f4865386SMark Murray own kernel config file. 814f4865386SMark Murray Remove: 815f4865386SMark Murray options RANDOMDEV 816f4865386SMark Murray Add: 817f4865386SMark Murray device random 818f4865386SMark Murray If you prefer to load the loadable module, you need to do 819f4865386SMark Murray nothing. 820f4865386SMark Murray 821d594498fSWarner Losh20000909: 822d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 823d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 824d594498fSWarner Losh reflect this if you load this module at boot time. 825d594498fSWarner Losh The line should read: 826d594498fSWarner Losh random_load="YES" 827d594498fSWarner Losh 8280deb7ddcSWarner Losh20000907: 8290deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 83016eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 83116eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 83216eb772dSWarner Losh sure you don't have model loading problems which might at 83316eb772dSWarner Losh first blush appear related to SMP. 83452bf24e7SWarner Losh 8355a01880bSWarner Losh20000906: 8365a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 8375a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 8385a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 8395a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 8405a01880bSWarner Losh don't have one, and you have host.conf. 8415a01880bSWarner Losh 8422b41163cSWarner Losh20000905: 84338d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 84438d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 84538d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 84638d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 84738d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 84838d6ecd2SWarner Losh 84938d6ecd2SWarner Losh20000905: 8508aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 8518aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 8528aab4bc7SWarner Losh is /boot/kernel. 8538aab4bc7SWarner Losh 8548aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 85538d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 85638d6ecd2SWarner Losh installkernel/installworld dance. 8572b41163cSWarner Losh 858d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 859d594498fSWarner Losh before booting the new kernel, since kldload will find stale 860d594498fSWarner Losh modules in that directory instead of finding them in the correct 861d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 862d594498fSWarner Losh is that the linux module crashes your machine after the update. 863d594498fSWarner Losh 864d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 865d594498fSWarner Losh mv /modules.old /boot/kernel.old 866d594498fSWarner Losh chflags noschg /kernel.old 867d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 868d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 869d594498fSWarner Losh fi 870d594498fSWarner Losh 871c22a309cSWarner Losh20000904: 872c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 873c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 874c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 875c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 876c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 877c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 878c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 879c22a309cSWarner Losh is not likely to be generated. 880c22a309cSWarner Losh 881fdb9f54dSWarner Losh20000825: 882fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 8839c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 8849c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 8859c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 8869c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 8879c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 8889c1a7444SWarner Losh messages will appear after the boot loader tries to start the 8899c1a7444SWarner Losh kernel. 8909c1a7444SWarner Losh 8919c1a7444SWarner Losh20000821: 8929c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 8939c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 8949c1a7444SWarner Losh /boot/loader.conf. 895fdb9f54dSWarner Losh 8968f250aa7SWarner Losh20000812: 8975da0d091SWarner Losh suidperl is now always built and installed on the system, but 8985da0d091SWarner Losh with permissions of 511. If you have applications that use 8995da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 9005da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 9015da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 9025da0d091SWarner Losh will fix this until the next build. 9035da0d091SWarner Losh 9045da0d091SWarner Losh20000812: 9058f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 9068f250aa7SWarner Losh visible changes that may immediately affect your configuration 9078f250aa7SWarner Losh include: 9088f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 9098f250aa7SWarner Losh - newaliases limited to root and trusted users 9108f250aa7SWarner Losh - MSA port (587) turned on by default 9118f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 9128f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 9138f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 9148f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 9158f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 9168f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 9178f250aa7SWarner Losh 91871c38472SWarner Losh20000810: 91971c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 92071c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 92171c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 92271c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 92371c38472SWarner Losh specific use for it. 92471c38472SWarner Losh 92571c38472SWarner Losh20000729: 92671c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 92771c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 92871c38472SWarner Losh /etc/rc.conf if they want to have the same setup 92971c38472SWarner Losh afterwards (unless the variables already are set, of course): 93071c38472SWarner Losh # Enable network daemons for user convenience. 93171c38472SWarner Losh inetd_enable="YES" 93271c38472SWarner Losh portmap_enable="YES" 93371c38472SWarner Losh sendmail_enable="YES" 93471c38472SWarner Losh 93571c38472SWarner Losh20000728: 93671c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 93771c38472SWarner Losh will need to change that to nullfs_load="YES". 93871c38472SWarner Losh 9391dece4a9SWarner Losh20000728: 9401dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 9411dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 9421dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 9431dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 9441dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 9451dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 9461dece4a9SWarner Losh to /MYKERNEL. 9471dece4a9SWarner Losh 948409e887cSWarner Losh20000711: 949409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 950409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 951409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 952409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 953409e887cSWarner Losh for details on potential problems that you might have and how 954409e887cSWarner Losh to get around them. 955409e887cSWarner Losh 956409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 957409e887cSWarner Losh clauses above, you needn't worry. 958409e887cSWarner Losh 959409e887cSWarner Losh20000711: 960409e887cSWarner Losh /etc/security has been updated to print the inode number of 961409e887cSWarner Losh setuid programs that have changed. You will see a large spike 962409e887cSWarner Losh in the number of changed programs the first time when you run 963409e887cSWarner Losh mergemaster to get a new /etc/security. 964409e887cSWarner Losh 965673d13f2SWarner Losh20000710: 966673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 967673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 968673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 969673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 970673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 971673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 972673d13f2SWarner Losh errors. (see below, 20000624). 973673d13f2SWarner Losh 974bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 9751dece4a9SWarner Losh 976673d13f2SWarner Losh20000709: 977c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 978c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 979c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 980673d13f2SWarner Losh ln -s aj /etc/malloc.conf 981673d13f2SWarner Losh 982e98e26cdSWarner Losh20000706: 983e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 984e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 985e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 986f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 987e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 9882c021c6cSMark Ovens interim if needed. 989e98e26cdSWarner Losh 990e98e26cdSWarner Losh20000705: 991e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 992e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 993e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 994e98e26cdSWarner Losh details. 995e98e26cdSWarner Losh 996c373950eSWarner Losh20000704: 9972f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 9982f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 9992f961bc8SWarner Losh 10002f961bc8SWarner Losh20000704: 1001c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 1002c373950eSWarner Losh or stop. This may cause some harmless warnings from older 1003c373950eSWarner Losh rc.d scripts that haven't been updated. 1004c373950eSWarner Losh 100527dc3a2bSWarner Losh20000630: 100627dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 100727dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 100827dc3a2bSWarner Losh which should be reported to des@freebsd.org. 100927dc3a2bSWarner Losh 1010b8c215acSWarner Losh20000625: 1011b8c215acSWarner Losh From approximately this date forward, one must have the crypto 101227dc3a2bSWarner Losh system installed in order to build the system and kernel. 101327dc3a2bSWarner Losh While not technically strictly true, one should treat it as 101427dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 101527dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 101627dc3a2bSWarner Losh were required. You should check with the latest collections 101727dc3a2bSWarner Losh to make sure that these haven't changed. 1018b8c215acSWarner Losh 10197b990719SWarner Losh20000624: 10207b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 10217b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 10227b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 10231a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 10247b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 10257b990719SWarner Losh openssh and openssl should not be used to generate keys from this 10267b990719SWarner Losh date to the completion of the work. 10277b990719SWarner Losh 102827dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 102927dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 103027dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 103127dc3a2bSWarner Losh recreate the random and urandom devices. 103227dc3a2bSWarner Losh 103381e54c50SWarner Losh20000622: 103481e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 103581e54c50SWarner Losh BSD license. You may need to remove your symbolic links 103681e54c50SWarner Losh that used to be required when updating. 103781e54c50SWarner Losh 103839943833SWarner Losh20000621: 10392c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 10402a2f33fbSDaniel Baker the config file update procedure. 10412a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1042c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 104359df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 104459df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 104539943833SWarner Losh 1046290f9ad8SWarner Losh20000620: 1047290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1048290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1049290f9ad8SWarner Losh that workaround will no longer be required. 1050290f9ad8SWarner Losh 105190fb6346SWarner Losh20000615: 105290fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 105390fb6346SWarner Losh ad driver. If you haven't done so already, you must update 105490fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 105590fb6346SWarner Losh devices. 105690fb6346SWarner Losh 1057f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1058f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1059f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1060f75f65bbSWarner Losh may work). 1061f75f65bbSWarner Losh 1062ba26da8eSWarner Losh20000612: 1063ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1064290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1065c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1066290f9ad8SWarner Losh to your config file to compile them in statically. The format 1067f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1068f54a3542SWarner Losh NEWCARD for examples of the new format. 1069290f9ad8SWarner Losh 10709698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 10719698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 10729698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 10739698f2c0SWarner Losh in it. 1074bbcc5149SWarner Losh 1075d65850ebSWarner Losh20000522: 1076ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1077d65850ebSWarner Losh building a kernel after this point is advised that they need 1078d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1079d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1080d65850ebSWarner Losh 1081d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1082d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1083d9583a00SWarner Losh is recommended that you don't set this option until the problem 1084d9583a00SWarner Losh is resolved. 1085d9583a00SWarner Losh 10868039cedeSWarner Losh20000513: 10878039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 10888039cedeSWarner Losh 1089d65850ebSWarner Losh20000510: 10908039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 10918039cedeSWarner Losh This will require some care in updating alphas. A new libstand 10928039cedeSWarner Losh is requires for the boot blocks to build properly. 10938039cedeSWarner Losh 10948039cedeSWarner Losh20000503: 10958039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 10968039cedeSWarner Losh is now available. 10978039cedeSWarner Losh 1098d65850ebSWarner Losh20000502: 1099d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1100d65850ebSWarner Losh connected to the kernel building instead. 1101d65850ebSWarner Losh 1102be149406SNik Clayton20000427: 11038039cedeSWarner Losh You may need to build gperf 11048039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 11058039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 11068039cedeSWarner Losh an option only in -current. 11078039cedeSWarner Losh 11082b8dd5f4SWarner Losh20000417: 11092b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1110f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 11112b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 11122b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 11132c021c6cSMark Ovens before you reboot, you'll need to issue: 11142b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 11152b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 11162b8dd5f4SWarner Losh 11178d9f1945SWarner Losh20000320: 11182b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 11192b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 11202b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1121ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 11222b8dd5f4SWarner Losh to the start of /etc/rc.conf. 11238d9f1945SWarner Losh 1124f8ab1dd6SWarner Losh20000319: 1125f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1126f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1127f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1128f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1129f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1130f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1131f8ab1dd6SWarner Losh 113219cada77SWarner Losh20000318: 1133f699bbbbSMark Ovens We've entered the traditional post release dumping party. 113419cada77SWarner Losh Large kernel changes are being committed and are in the 113519cada77SWarner Losh works. It is important to keep the systems' klds and kernel 113619cada77SWarner Losh in sync as kernel interfaces and structures are changing. 113719cada77SWarner Losh Before reporting kernel panics, make sure that all modules 113819cada77SWarner Losh that you are loading are up to date. 1139ba228352SWarner Losh 114019cada77SWarner Losh20000315: 11416d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 11426d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 11436d23c382SWarner Losh will do the trick. This isn't critical until you remove your 11446d23c382SWarner Losh wd device entries in /dev, at which point your system will not 11456d23c382SWarner Losh boot. 11466d23c382SWarner Losh 11476d23c382SWarner Losh20000315: 114819cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 114919cada77SWarner Losh to upgrade to 4.0 from 3.x. 115057199806SWarner Losh 1151dc0dbf5cSWarner LoshCOMMON ITEMS: 1152dc0dbf5cSWarner Losh 1153a24eff53SWarner Losh General Notes 1154a24eff53SWarner Losh ------------- 1155a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1156a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1157a24eff53SWarner Losh installworld. This is especially true when upgrading between 1158a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1159a24eff53SWarner Losh or several minor releases, or when several months have passed 1160a24eff53SWarner Losh on the -current branch). 1161a24eff53SWarner Losh 11625780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 11635780f3baSWarner Losh poisoning. This can happen because the make utility reads its 11645780f3baSWarner Losh environment when searching for values for global variables. 11655780f3baSWarner Losh To run your build attempts in an "environmental clean room", 11665780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 11675780f3baSWarner Losh page for more details. 11685780f3baSWarner Losh 1169dc0dbf5cSWarner Losh To build a kernel 1170dc0dbf5cSWarner Losh ----------------- 1171ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1172f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1173ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 11741e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 11751e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 1176dc0dbf5cSWarner Losh 1177ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1178ba01eb20SWarner Losh -------------------------------------------------------------- 1179ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 118047d0d01fSWarner Losh config KERNEL_NAME_HERE 1181ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1182ba01eb20SWarner Losh make depend 1183ba01eb20SWarner Losh make 1184ba01eb20SWarner Losh make install 1185ba01eb20SWarner Losh 1186ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1187ba01eb20SWarner Losh 1188ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1189ba01eb20SWarner Losh ----------------------------------------------------------- 119063cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 119163cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 119263cb445eSWarner Losh 1193f643de42SWarner Losh <make sure you have good level 0 dumps> 119463cb445eSWarner Losh <maybe fix /etc/fstab> [7] 119563cb445eSWarner Losh make buildworld 119663cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 119763cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 119863cb445eSWarner Losh [1] 119963cb445eSWarner Losh <reboot in single user> [3] 120063cb445eSWarner Losh mergemaster -p [5] 120163cb445eSWarner Losh make installworld 120263cb445eSWarner Losh mergemaster [4] 120363cb445eSWarner Losh <reboot> 120463cb445eSWarner Losh 1205759f0aefSWarner Losh 1206f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1207f27b1fceSJoseph Koshy -------------------------------------------------- 1208f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1209f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1210f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1211f27b1fceSJoseph Koshy # size. 1212f27b1fceSJoseph Koshy 1213f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1214f27b1fceSJoseph Koshy <boot into -stable> 1215f27b1fceSJoseph Koshy make buildworld 1216f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1217f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1218f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1219f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1220f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1221f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1222f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1223f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1224f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1225f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1226f27b1fceSJoseph Koshy <reboot into current> 1227f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1228f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1229f27b1fceSJoseph Koshy <reboot> 1230f27b1fceSJoseph Koshy 1231f27b1fceSJoseph Koshy 1232f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1233f27b1fceSJoseph Koshy ---------------------------------------------- 12345c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 12355c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 12365c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 12375c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1238ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1239f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1240f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1241f643de42SWarner Losh # space on /. 1242f643de42SWarner Losh 1243f643de42SWarner Losh <make sure you have good level 0 dumps> 1244fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 124521c075eaSWarner Losh make buildworld [9] 1246c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1247d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1248be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1249fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1250fc8c157fSWarner Losh [1] 1251fc8c157fSWarner Losh <reboot in single user> [3] 1252835284beSWarner Losh mergemaster -p [5] 1253f8a4c901SWarner Losh rm -rf /usr/include/g++ 1254ba26da8eSWarner Losh make installworld 1255a6cd4f9dSWarner Losh mergemaster [4] 1256ba26da8eSWarner Losh <reboot> 1257ba26da8eSWarner Losh 1258fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1259fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1260fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1261fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1262fdb9f54dSWarner Losh the UPDATING entries. 1263ba26da8eSWarner Losh 12641dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 12651dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 12661dece4a9SWarner Losh your sources that you have read and understood all the recent 12671dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 12681dece4a9SWarner Losh much fewer pitfalls. 12691dece4a9SWarner Losh 1270134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1271134d2e86SWarner Losh should disable them at this point so they don't crash your 1272134d2e86SWarner Losh system on reboot. 1273134d2e86SWarner Losh 12749c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 12759c1a7444SWarner Losh your own device.hints to reflect your unique hardware 12769c1a7444SWarner Losh configuration. 12779c1a7444SWarner Losh 1278ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1279ee6e1fc3SWarner Losh fsck -p 1280ee6e1fc3SWarner Losh mount -u / 1281ee6e1fc3SWarner Losh mount -a 1282ee6e1fc3SWarner Losh cd /usr/src 128347d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1284f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1285f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1286b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1287b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1288b705ae10SWarner Losh be ignored while you proceed to the next step. 1289ee6e1fc3SWarner Losh 1290a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1291a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1292a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1293a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1294a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1295a6cd4f9dSWarner Losh for potential gotchas. 1296a6cd4f9dSWarner Losh 1297835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1298835284beSWarner Losh you may need to do this if you get unknown user in the following 1299835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1300835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1301835284beSWarner Losh install) after the buildworld before this step if you last updated 1302835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1303835284beSWarner Losh 1304bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1305bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1306bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1307bd79cf40SWarner Losh ok unload 1308bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1309bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1310bd79cf40SWarner Losh described here. 1311fc8c157fSWarner Losh 1312fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1313fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1314fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1315fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1316fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1317fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1318fc8c157fSWarner Losh 1319c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1320c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1321c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1322c74fe6afSWarner Losh that is hard to boot to recover. 1323c74fe6afSWarner Losh 132421c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 132521c075eaSWarner Losh cvs prune empty directories. 1326dc0dbf5cSWarner LoshFORMAT: 1327dc0dbf5cSWarner Losh 1328f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 13291fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1330f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1331f8ab1dd6SWarner Loshprevious releases if your system is older than this. 13321fc1a0dcSWarner Losh 1333e72fd46aSWarner LoshCopyright information: 1334e72fd46aSWarner Losh 13359698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1336e72fd46aSWarner Losh 1337772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1338772730c7SWarner Loshmodification, in full or in part, in any form or format of this 13399698f2c0SWarner Loshdocument are permitted without further permission from the author. 1340e72fd46aSWarner Losh 1341e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1342e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1343e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1344e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1345e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1346e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1347e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1348e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1349e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1350e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1351e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1352e72fd46aSWarner Losh 1353e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1354e72fd46aSWarner Loshauthor a beer. 1355e72fd46aSWarner Losh 135622306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1357772730c7SWarner Loshthis document. 1358772730c7SWarner Losh 135997d92980SPeter Wemm$FreeBSD$ 1360