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 1869f7bcf3SWarner Losh to maximize performance. 1969f7bcf3SWarner Losh 20157c629aSWarner Losh20030711: 21157c629aSWarner Losh gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 22157c629aSWarner Losh accross this point. Further, it might be a good idea to remove 23157c629aSWarner Losh /usr/obj. Finally, i386 kernels are currently panicing on boot. 24157c629aSWarner Losh 256cc6353fSMarcel Moolenaar20030613: [retrospective] 266cc6353fSMarcel Moolenaar There was a small window in which sed(1) was broken. If you 276cc6353fSMarcel Moolenaar happen to have sed(1) installed during that window, which is 286cc6353fSMarcel Moolenaar evidenced by an inability to build world with the failure 296cc6353fSMarcel Moolenaar given below, you need to manually build and install sed(1) 306cc6353fSMarcel Moolenaar (and only sed(1)) before doing anything else. This is a one- 316cc6353fSMarcel Moolenaar time snafu. Typical failure mode: 326cc6353fSMarcel Moolenaar 336cc6353fSMarcel Moolenaar In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 346cc6353fSMarcel Moolenaar targmatch.h:7:1: null character(s) ignored 356cc6353fSMarcel Moolenaar targmatch.h:12:1: null character(s) ignored 366cc6353fSMarcel Moolenaar targmatch.h:16:1: null character(s) ignored 376cc6353fSMarcel Moolenaar : 386cc6353fSMarcel Moolenaar 396cc6353fSMarcel Moolenaar The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 406cc6353fSMarcel Moolenaar to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 416cc6353fSMarcel Moolenaar usr.bin/sed/process.c). 426cc6353fSMarcel Moolenaar 43766c34e4SAndrey A. Chernov20030610: 44766c34e4SAndrey A. Chernov Remove deprecated locale names and transition period code 45766c34e4SAndrey A. Chernov for them, finishing switching to the new scheme. Check your 46766c34e4SAndrey A. Chernov LANG environment variable. 47766c34e4SAndrey A. Chernov 487ddc2528SPoul-Henning Kamp20030609: 49df622d54SPoul-Henning Kamp CCD has been changed to be a fully GEOMified class. Kernel 50df622d54SPoul-Henning Kamp and ccdconfig(8) needs to be in sync, this is particularly 51df622d54SPoul-Henning Kamp important to remember beforehand if your source tree is on 52df622d54SPoul-Henning Kamp a ccd device. Consider making a copy of the old ccdconfig 53df622d54SPoul-Henning Kamp into /boot/kernel.good or wherever you keep your backup 54df622d54SPoul-Henning Kamp kernel. 55df622d54SPoul-Henning Kamp 5652b47445SMark Murray20030505: 5752b47445SMark Murray Kerberos 5 (Heimdal) is now built by default. Setting 5852b47445SMark Murray MAKE_KERBEROS5 no longer has any effect. If you do NOT 5952b47445SMark Murray want the "base" Kerberos 5, you need to set NO_KERBEROS. 6052b47445SMark Murray 61a26df538SWarner Losh20030502: 62a26df538SWarner Losh groff has been updated. If you try to do a buildworld and 63a26df538SWarner Losh get an infinite loop in troff, update to May 4th or newer. If you 64a26df538SWarner Losh have a newer kernel than userland, you may need to set the OSRELDATE 65a26df538SWarner Losh to 500110 in your environment before starting a buildworld. 66a26df538SWarner Losh 674b065e2cSDoug Barton20030501: 684b065e2cSDoug Barton The old rc system has been removed. Please report any problems 694b065e2cSDoug Barton to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 704b065e2cSDoug Barton Your personal versions of these files will not be removed, so you can 714b065e2cSDoug Barton continue to use them. However, you should take great care when updating, 724b065e2cSDoug Barton especially when using mergemaster, since the compatibility code that 734b065e2cSDoug Barton utilizes these old scripts has also been removed. 744b065e2cSDoug Barton 7581cda3d9SWarner Losh20030423: 7681cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 7781cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 7881cda3d9SWarner Losh work around in devd will be removed around 20030507. You 7981cda3d9SWarner Losh have until then to upgrade your kernel before updating 8081cda3d9SWarner Losh userland. In general, you should have a userland and 8181cda3d9SWarner Losh kernel that's in sync with each other. However, given the 8281cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 8381cda3d9SWarner Losh allowances are made. 8481cda3d9SWarner Losh 8547a657d1SRuslan Ermilov20030329: 8647a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 8747a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 8847a657d1SRuslan Ermilov while upgrading the system through a buildworld. 8947a657d1SRuslan Ermilov 9047a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 9147a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 9247a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 9347a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 9447a657d1SRuslan Ermilov 9547a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 9647a657d1SRuslan Ermilov make cleandir && make obj && \ 9747a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 9847a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 9947a657d1SRuslan Ermilov 1005d2af00cSGregory Neil Shapiro20030208: 1015d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 1025d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 1035d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 1045d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 1055d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 1065d2af00cSGregory Neil Shapiro 1075d2af00cSGregory Neil Shapiro20030128: 1089db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 109ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 1109db58771SPoul-Henning Kamp be removed when convenient. 1119db58771SPoul-Henning Kamp 1128d9b3f57SJake Burkholder20030126: 1138d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 1148d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 1158d9b3f57SJake Burkholder 1161c5efda5SJeff Roberson20030125: 1171c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 1181c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 119ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 1201c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 1211c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 1221c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 1231c5efda5SJeff Roberson 1249d1d64f5SWarner Losh20030115: 1259d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 1269d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 1279d1d64f5SWarner Losh properly. 1289d1d64f5SWarner Losh 129c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 130c9fdb80aSWarner Losh configured for point to point links to bring it more in line 131c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 132c9fdb80aSWarner Losh with NetBSD. 133c9fdb80aSWarner Losh 134161dc364SAlexander Kabaev20021222: 135161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 136161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 137161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 138161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 139161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 140161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 14184cc83efSAlexander Kabaev rebuilt. 142161dc364SAlexander Kabaev 143fb4c8061SMartin Blapp20021216: 144fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 14589056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 146fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 1479d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 148fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 149fb4c8061SMartin Blapp 15017d47eb3SGiorgos Keramidas20021202: 15117d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 15217d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 15317d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 15417d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 15517d47eb3SGiorgos Keramidas 156a4459294SBill Fenner20021029: 157a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 158a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 159a4459294SBill Fenner consumers in sync. 160a4459294SBill Fenner 161fc8c157fSWarner Losh20021024: 162c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 163c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 164c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 165c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 166c57404feSRuslan Ermilov partition really is on. The old device names have gone 167c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 168c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 169c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 17069f7bcf3SWarner Losh 171fd9e8bdaSAndrew Gallatin20021023: 172fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 173fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 174fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 175fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 176fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 177fd9e8bdaSAndrew Gallatin 178fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 179fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 180fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 181fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 182fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 183fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 184fd9e8bdaSAndrew Gallatin 185f8a4c901SWarner Losh20020831: 186f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 187f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 188f8a4c901SWarner Losh programs and libraries need to be recompiled. 189f8a4c901SWarner Losh 190f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 191f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 192f8a4c901SWarner Losh 193c2248fa2SJens Schweikhardt20020827: 194c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 195c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 196c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 197c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 198c2248fa2SJens Schweikhardt 1990d533e43SRuslan Ermilov20020815: 2000d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 2010d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 2020d533e43SRuslan Ermilov again. 2030d533e43SRuslan Ermilov 20433c1de7dSRuslan Ermilov20020729: 20533c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 20633c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 20733c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 20833c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 20933c1de7dSRuslan Ermilov 2102b877facSJulian Elischer20020702: 2112b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 2122b877facSJulian Elischer There are still some minor problems with some signals but the 2132b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 2142b877facSJulian Elischer but each can successfully complete multiple buildworlds. 2152b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 2162b877facSJulian Elischer 21706596d37SWarner Losh20020701: 21806596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 21906596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 22006596d37SWarner Losh GNOME. 22106596d37SWarner Losh 22295ba4330SJacques Vidrine20020511: 22395ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 22495ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 22595ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 22695ba4330SJacques Vidrine with the set-user-ID bit set. 22795ba4330SJacques Vidrine 228a81da3c9SDavid E. O'Brien20020510: 229f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 230f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 2314b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 232f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 233f50caf6fSDavid E. O'Brien 234f50caf6fSDavid E. O'Brien20020510: 235a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 236a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 237a81da3c9SDavid E. O'Brien and then do a cvs update. 238a81da3c9SDavid E. O'Brien 239528a0ef5SJacques Vidrine20020421: 240528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 241528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 242528a0ef5SJacques Vidrine 24385aa5a2eSGregory Neil Shapiro20020404: 24485aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 24585aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 24685aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 24785aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 24885aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 24985aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 25085aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 25185aa5a2eSGregory Neil Shapiro 2528f1e4358SRuslan Ermilov20020403: 2538f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 2548f1e4358SRuslan Ermilov 2552292c02eSWarner Losh20020315: 2562292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 2572292c02eSWarner Losh 25869f7bcf3SWarner Losh20020225: 25969f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 26069f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 26169f7bcf3SWarner Losh 2628f35c493SWarner Losh20020217: 2638f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 2648f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 2658f35c493SWarner Losh command line mail submission has changed. Be sure to run 2668f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 2678f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 2688f35c493SWarner Losh 269835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 270835284beSWarner Losh required in order for sendmail to run as a set-group-ID 271835284beSWarner Losh binary. A 'make installworld' will use the new user and group 272835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 273835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 274835284beSWarner Losh and group must be merged from src/etc/group and 275835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 276835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 277835284beSWarner Losh mergemaster before this will work if you are updating from a 278835284beSWarner Losh very old version of current. The updating recipe has changed 279835284beSWarner Losh as of this date. 280835284beSWarner Losh 281fa9401c1SWarner Losh20020112: 282fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 283fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 284fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 285fa9401c1SWarner Losh you have local modifications, you can use 286fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 287fa9401c1SWarner Losh /etc/pam.d. 288fa9401c1SWarner Losh 289fa9401c1SWarner Losh Please see the following url for more details: 290fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 29147d0d01fSWarner Losh20011229: 29247d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 29347d0d01fSWarner Losh networkfs_types, please note that it has changed 29447d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 29547d0d01fSWarner Losh 296514318a8SWarner Losh20011220: 297514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 298514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 299514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 300514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 301514318a8SWarner Losh version have now been merged back into the base system's 302514318a8SWarner Losh version now. The only user-visible change resulting from this 303514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 304514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 305514318a8SWarner Losh as well. (There has never been rc file support for 306514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 307514318a8SWarner Losh reverted by the time the changes are MFCed.) 308514318a8SWarner Losh 309514318a8SWarner Losh20011215: 310514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 311514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 312514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 313514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 314514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 315514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 316514318a8SWarner Losh will need to be customized then for `odd' densities using 317514318a8SWarner Losh fdcontrol(8). 318514318a8SWarner Losh 3192d22e2bfSWarner Losh20011209: 3202d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 3212d22e2bfSWarner Losh and truss(1) now works again. 3222d22e2bfSWarner Losh 3239e0428e2SWarner Losh20011207: 3249e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 3259e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 3269e0428e2SWarner Losh see 3279e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 3289e0428e2SWarner Losh for details. 3299e0428e2SWarner Losh 3309bab8c59SWarner Losh20011204: 3319bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 3329bab8c59SWarner Losh kernel and burncd to be in sync. 3339bab8c59SWarner Losh 334e57d8b01SWarner Losh20011203: 335e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 336e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 337e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 338e57d8b01SWarner Losh not there already. 339e57d8b01SWarner Losh 340e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 341e57d8b01SWarner Losh until the issue has been resolved. 342e57d8b01SWarner Losh 343b001d36fSJacques Vidrine20011202: 344b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 345b001d36fSJacques Vidrine patched. 346b001d36fSJacques Vidrine 3474b676ec1SWarner Losh20011126: 3484b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 3495ebbf43eSWarner Losh after this date. You need to do this only once. 3504b676ec1SWarner Losh 351d961e462SWarner Losh20011103: 352d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 353d961e462SWarner Losh edges may be left, but for the most part things should be 3544b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 355d961e462SWarner Losh 356d961e462SWarner Losh20011030: 357d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 358d961e462SWarner Losh choppy waves in the upgrade process. 359d961e462SWarner Losh 3601fe003b6SWarner Losh20011030: 361a4b6fda0SWarner Losh The asr driver problem has been resolved. 3621fe003b6SWarner Losh 3631fe003b6SWarner Losh20011027: 3641fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 3651fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 3661fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 3671fe003b6SWarner Losh try to use from this date forward. 3681fe003b6SWarner Losh 3691fe003b6SWarner Losh20011025: 3701fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 3711fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 3721fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 3731fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 3741fe003b6SWarner Losh TARGET_ARCH=i386. 3751fe003b6SWarner Losh 376d05f9643SWarner Losh20011001: 377d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 378d05f9643SWarner Losh You must recompile both the kernel and userland applications 379d05f9643SWarner Losh at the same time. 380d05f9643SWarner Losh 38158970f85SWarner Losh20010929: 38258970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 38358970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 38458970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 38558970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 3869d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 38758970f85SWarner Losh 38858970f85SWarner Losh20010927: 38958970f85SWarner Losh Some weird problems result from using ACPI on some machines. 39058970f85SWarner Losh To disable ACPI you can add 39166ff0e67SMax Khon hint.acpi.0.disabled="1" 39258970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 39358970f85SWarner Losh loader "ok" prompt). 39458970f85SWarner Losh 39558970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 39658970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 39758970f85SWarner Losh file and not list acpi in that list. 398378f4486SAlfred Perlstein 3995119d237SWarner Losh20010924: 4005119d237SWarner Losh The buildworld has been fixed. You may need to install 4015119d237SWarner Losh the 4.x compatibility libraries for some old binaries 4028b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 4038b039fffSWarner Losh get them installed on every installworld, or execute the 4048b039fffSWarner Losh following to get them installed only once: 4058b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 40658970f85SWarner Losh make all install 4078b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 4085119d237SWarner Losh 4093c293725SWarner Losh20010919: 4103c293725SWarner Losh There's a bug in the world build process. The cross-tools 4113c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 4123c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 413772730c7SWarner Losh workaround is to add 4143c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 4153c293725SWarner Losh before building world when upgrading from 4.x to current. This 4163c293725SWarner Losh can be removed afterwards. 4173c293725SWarner Losh 4183c293725SWarner Losh A proper fix to the buildworld target is needed. 4193c293725SWarner Losh 4203c293725SWarner Losh20010918: 4213c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 4223c293725SWarner Losh NFS may be unstable after this date. 4233c293725SWarner Losh 4243c293725SWarner Losh20010912: 4253c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 4263c293725SWarner Losh the kernel. While a few problems were introduced in the 4273c293725SWarner Losh initial commit, most of the major ones have been found and 4283c293725SWarner Losh corrected. 4293c293725SWarner Losh 4303c293725SWarner Losh20010901: 4313c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 4323c293725SWarner Losh arounds described in the 20010604 entry are now no longer 4333c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 4343c293725SWarner Losh have been rectified around this date. 4353c293725SWarner Losh 43698b17b95SWarner Losh20010823: 43798b17b95SWarner Losh named now runs as user bind and group bind rather than as 43898b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 43998b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 44098b17b95SWarner Losh and that group bind is available in /etc/group. Also make 44198b17b95SWarner Losh sure that user or group bind has read (and not write) 44298b17b95SWarner Losh permission for your name server configuration and that it 44398b17b95SWarner Losh has read and write permission for your slave zone files and 44498b17b95SWarner Losh directory. 44598b17b95SWarner Losh 44698b17b95SWarner Losh If you wish to continue to run named as root (a less secure 44798b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 44898b17b95SWarner Losh 44998b17b95SWarner Losh named_flags= 45098b17b95SWarner Losh 4517b9786edSMark Murray20010709: 4527b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 4537b9786edSMark Murray the ability of the shared library major number to handle. 4547b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 4557b9786edSMark Murray solution is to rebuild those ports. 4567b9786edSMark Murray 4571d28950eSWarner Losh20010628: 4581d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 4591d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 4601d28950eSWarner Losh 461e72fd46aSWarner Losh20010625: 46298b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 46398b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 46498b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 46598b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 46698b17b95SWarner Losh IRQ configuration needs more safety belts. 46716de1a07SWarner Losh 4680d415dffSWarner Losh20010617: 469e72fd46aSWarner Losh Softupdates problems have been corrected. 4700d415dffSWarner Losh 4710d415dffSWarner Losh20010614: 4720d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 4730d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 4740d415dffSWarner Losh kernel building methods. 4750d415dffSWarner Losh 4768b9959adSWarner Losh20010613: 4778b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 4788b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 479e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 480e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 4818b9959adSWarner Losh 482e72fd46aSWarner Losh20010613: 4838b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 484e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 485e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 4868b9959adSWarner Losh 4870d415dffSWarner Losh20010612: 4880d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 4890d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 4900d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 4910d415dffSWarner Losh work around this issue, please use only one or the other mechanism 4920d415dffSWarner Losh until this bug is fixed. 4930d415dffSWarner Losh 494e72fd46aSWarner Losh Please note that a feature of config is that if you have config 495e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 496ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 497e72fd46aSWarner Losh 4980d415dffSWarner Losh20010610: 4990d415dffSWarner Losh Locale names have changed to match other systems better. 5000d415dffSWarner Losh 5016ccdb5e4SWarner Losh20010604: 5026ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 5036ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 5046ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 5053590182eSWarner Losh Interrupt storms look a lot like a hang. 5063590182eSWarner Losh 5073590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 5083590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 5093590182eSWarner Losh it is). 5103590182eSWarner Losh 5113590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 5123590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 5133590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 5143590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 5156ccdb5e4SWarner Losh 5160bc62786SWarner Losh20010530: 5170bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 5180bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 5190bc62786SWarner Losh a limited time. If you see 5200bc62786SWarner Losh 5210bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 5220bc62786SWarner Losh 5230bc62786SWarner Losh in your makeworld, then you need to migrate towards using 5240bc62786SWarner Losh COPY=-C. 5250bc62786SWarner Losh 52668a38c6cSWarner Losh20010525: 527b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 528c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 529c4f4a728SWarner Losh definitely is in bad shape. 53068a38c6cSWarner Losh 531ed0f29caSWarner Losh20010521: 532ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 533ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 534ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 535ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 536ed0f29caSWarner Losh is 537ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 538ed0f29caSWarner Losh 53980c16af9SWarner Losh20010520: 54068a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 54180c16af9SWarner Losh 54280c16af9SWarner Losh20010519: 54380c16af9SWarner Losh pccard has had much reorganizational work done to it over 54480c16af9SWarner Losh the past few days. Everything should still work, but if 54580c16af9SWarner Losh not, please contact imp@freebsd.org. 54680c16af9SWarner Losh 547a45f2d05SWarner Losh20010517: 548a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 549a45f2d05SWarner Losh userland at the same time. 550a45f2d05SWarner Losh 551a45f2d05SWarner Losh20010517: 552a45f2d05SWarner Losh New ncurses imported. 553a45f2d05SWarner Losh 5542988afcaSWarner Losh20010512: 5552988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 5562988afcaSWarner Losh will be the only way to go starting July 1. 5572988afcaSWarner Losh 5581a33dba7SWarner Losh20010504: 5591a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 5601a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 5611a33dba7SWarner Losh 56209946a51SWarner Losh20010502: 56309946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 56409946a51SWarner Losh 56509946a51SWarner Losh20010501: 56609946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 56709946a51SWarner Losh 56809946a51SWarner Losh20010430: 569a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 57009946a51SWarner Losh go back in the water. 57109946a51SWarner Losh 57209946a51SWarner Losh20010429: 57309946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 57409946a51SWarner Losh this date, but before the correction date. 57509946a51SWarner Losh 57691dd3b53SWarner Losh20010423: 57791dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 57891dd3b53SWarner Losh 57991dd3b53SWarner Losh20010411: 58091dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 58191dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 58291dd3b53SWarner Losh Update only if you understand that you must not use the old 58391dd3b53SWarner Losh fsck with the new kernel ever. 58491dd3b53SWarner Losh 585933b3269SWarner Losh20010330: 586933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 587c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 588933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 589933b3269SWarner Losh 590933b3269SWarner Losh20010319: 591933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 592933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 593933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 594f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 59509946a51SWarner Losh 59609946a51SWarner Losh20010315: 59709946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 598ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 59909946a51SWarner Losh been replaced by tunables. See ata.4 for details. 600933b3269SWarner Losh 601933b3269SWarner Losh20010312: 602933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 603933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 604933b3269SWarner Losh 605933b3269SWarner Losh20010312: 606933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 607933b3269SWarner Losh instead of ad-hoc. 608933b3269SWarner Losh 609933b3269SWarner Losh20010310: 610f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 611933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 612933b3269SWarner Losh ssh might not work if you don't. 613933b3269SWarner Losh 61462353691SWarner Losh20010303: 61562353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 61662353691SWarner Losh which means that you must include the miibus in your kernel if 61762353691SWarner Losh you use the ed driver. 61862353691SWarner Losh 619d325cf65SWarner Losh20010220: 620d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 621d325cf65SWarner Losh safe to go back into the water. 622d325cf65SWarner Losh 623024daae6SWarner Losh20010211: 624024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 625024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 626024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 627024daae6SWarner Losh that before upgrading would be a good time to do a level 0 628024daae6SWarner Losh dump of your system. No, really, I mean it this time. 629024daae6SWarner Losh 630024daae6SWarner Losh To get to the new system, you'll need to use the following 631024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 632024daae6SWarner Losh don't have to move this to the updating section. 633024daae6SWarner Losh 634024daae6SWarner Losh To get around the installworld problem, do: 635024daae6SWarner Losh # cd /usr/src/usr.bin/sed 636024daae6SWarner Losh # make install 637024daae6SWarner Losh # cd /usr/src 638024daae6SWarner Losh # make installworld 639024daae6SWarner Losh If that doesn't work, then try: 640024daae6SWarner Losh # make -k installworld 641024daae6SWarner Losh # make installworld 642024daae6SWarner Losh 643024daae6SWarner Losh20010207: 644024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 645024daae6SWarner Losh do not include devfs in your kernel as problems result. 646024daae6SWarner Losh 647024daae6SWarner Losh20010205: 6487595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 649024daae6SWarner Losh Remove them from your config. 650024daae6SWarner Losh 6511e159248SWarner Losh20010122: 6521e159248SWarner Losh ****************************** WARNING ****************************** 6531e159248SWarner Losh buildkernel has been changed slightly 6541e159248SWarner Losh ****************************** WARNING ****************************** 6551e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 6561e159248SWarner Losh should update your scripts and make.conf accordingly. 6571e159248SWarner Losh 6581e159248SWarner Losh20010119: 6591e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 6601e159248SWarner Losh This requires a new config to build correctly. 6611e159248SWarner Losh 662aac7dfeaSWarner Losh20010116: 663ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 664aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 665aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 666aac7dfeaSWarner Losh 667aac7dfeaSWarner Losh20010110: 668aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 669aac7dfeaSWarner Losh 670aac7dfeaSWarner Losh20010102: 671aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 672aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 673aac7dfeaSWarner Losh 67463c90c9eSWarner Losh20010101: 67563c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 67663c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 6775fd2a895SWarner Losh dump while building termcap. You can work around this problem 67863c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 67963c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 68063c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 68163c90c9eSWarner Losh might have been ignored by the -k option. 68263c90c9eSWarner Losh 6835fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 6845fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 6855fd2a895SWarner Losh of this working. 6865fd2a895SWarner Losh 687aac7dfeaSWarner Losh20001228: 688aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 689ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 690aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 691aac7dfeaSWarner Losh 692de2bcc63SWarner Losh20001218: 693de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 694de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 695de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 696de2bcc63SWarner Losh cards will not be recognized without it. 697de2bcc63SWarner Losh 698960773f7SWarner Losh20001205: 699960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 700960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 701960773f7SWarner Losh adding the following in pam.conf: 702960773f7SWarner Losh 703960773f7SWarner Losh sshd auth sufficient pam_skey.so 704960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 705960773f7SWarner Losh sshd session required pam_permit.so 706960773f7SWarner Losh 7070acc635eSWarner Losh20001031: 7080acc635eSWarner Losh cvs updated to 1.11. 7090acc635eSWarner Losh 7100acc635eSWarner Losh20001020: 7110acc635eSWarner Losh The random device needs more entropy, so you need to make sure 7120acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 7130acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 7140acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 7150acc635eSWarner Losh workaround. 7160acc635eSWarner Losh 7170acc635eSWarner Losh20001010: 7180acc635eSWarner Losh ****************************** WARNING ****************************** 7190acc635eSWarner Losh Sendmail has been updated. 7200acc635eSWarner Losh ****************************** WARNING ****************************** 7210acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 7220acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 7230acc635eSWarner Losh is set. 7240acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 7250acc635eSWarner Losh commands. 7260acc635eSWarner Losh o Now using sendmail's version of vacation(1). 7270acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 7280acc635eSWarner Losh in /usr/share/sendmail/cf. 7290acc635eSWarner Losh o sendmail.cw changed to local-host-names 7300acc635eSWarner Losh 7310acc635eSWarner Losh More details can be found at 7320acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 7330acc635eSWarner Losh 7346e98a146SWarner Losh20001009: 7356e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 7366e98a146SWarner Losh your entire ports tree, or you will have problems. 7376e98a146SWarner Losh 7386e98a146SWarner Losh20001006: 739685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 7406e98a146SWarner Losh the installed miniperl. It is recommended that you delete 7416e98a146SWarner Losh /usr/bin/miniperl. 7426e98a146SWarner Losh 743073113a4SWarner Losh20001005: 744073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 745685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 746073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 747073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 748073113a4SWarner Losh tree for anything to work. 749073113a4SWarner Losh 7500acc635eSWarner Losh20000928: 7510acc635eSWarner Losh There was a change in the passwd format. Need more information. 7520acc635eSWarner Losh 753be3885b3SWarner Losh20000916: 754be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 755be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 756be3885b3SWarner Losh same time as your kernel. 757be3885b3SWarner Losh 75876ec9675SWarner Losh20000914: 75976ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 76076ec9675SWarner Losh include the device will cause suspended laptops losing time 76176ec9675SWarner Losh when they resume. Include 76276ec9675SWarner Losh device pmtimer 76376ec9675SWarner Losh in your config file and 76401b9a434SWarner Losh hint.pmtimer.0.at="isa" 76576ec9675SWarner Losh to your /boot/device.hints file. 76676ec9675SWarner Losh 767f4865386SMark Murray20000911: 768f4865386SMark Murray The random device has been turned into a (pseudo-)device, 769f4865386SMark Murray rather than an option. The supplied kernel config files have 770f4865386SMark Murray been updated. You will need to do something similar in your 771f4865386SMark Murray own kernel config file. 772f4865386SMark Murray Remove: 773f4865386SMark Murray options RANDOMDEV 774f4865386SMark Murray Add: 775f4865386SMark Murray device random 776f4865386SMark Murray If you prefer to load the loadable module, you need to do 777f4865386SMark Murray nothing. 778f4865386SMark Murray 779d594498fSWarner Losh20000909: 780d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 781d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 782d594498fSWarner Losh reflect this if you load this module at boot time. 783d594498fSWarner Losh The line should read: 784d594498fSWarner Losh random_load="YES" 785d594498fSWarner Losh 7860deb7ddcSWarner Losh20000907: 7870deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 78816eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 78916eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 79016eb772dSWarner Losh sure you don't have model loading problems which might at 79116eb772dSWarner Losh first blush appear related to SMP. 79252bf24e7SWarner Losh 7935a01880bSWarner Losh20000906: 7945a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 7955a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 7965a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 7975a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 7985a01880bSWarner Losh don't have one, and you have host.conf. 7995a01880bSWarner Losh 8002b41163cSWarner Losh20000905: 80138d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 80238d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 80338d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 80438d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 80538d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 80638d6ecd2SWarner Losh 80738d6ecd2SWarner Losh20000905: 8088aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 8098aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 8108aab4bc7SWarner Losh is /boot/kernel. 8118aab4bc7SWarner Losh 8128aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 81338d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 81438d6ecd2SWarner Losh installkernel/installworld dance. 8152b41163cSWarner Losh 816d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 817d594498fSWarner Losh before booting the new kernel, since kldload will find stale 818d594498fSWarner Losh modules in that directory instead of finding them in the correct 819d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 820d594498fSWarner Losh is that the linux module crashes your machine after the update. 821d594498fSWarner Losh 822d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 823d594498fSWarner Losh mv /modules.old /boot/kernel.old 824d594498fSWarner Losh chflags noschg /kernel.old 825d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 826d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 827d594498fSWarner Losh fi 828d594498fSWarner Losh 829c22a309cSWarner Losh20000904: 830c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 831c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 832c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 833c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 834c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 835c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 836c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 837c22a309cSWarner Losh is not likely to be generated. 838c22a309cSWarner Losh 839fdb9f54dSWarner Losh20000825: 840fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 8419c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 8429c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 8439c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 8449c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 8459c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 8469c1a7444SWarner Losh messages will appear after the boot loader tries to start the 8479c1a7444SWarner Losh kernel. 8489c1a7444SWarner Losh 8499c1a7444SWarner Losh20000821: 8509c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 8519c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 8529c1a7444SWarner Losh /boot/loader.conf. 853fdb9f54dSWarner Losh 8548f250aa7SWarner Losh20000812: 8555da0d091SWarner Losh suidperl is now always built and installed on the system, but 8565da0d091SWarner Losh with permissions of 511. If you have applications that use 8575da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 8585da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 8595da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 8605da0d091SWarner Losh will fix this until the next build. 8615da0d091SWarner Losh 8625da0d091SWarner Losh20000812: 8638f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 8648f250aa7SWarner Losh visible changes that may immediately affect your configuration 8658f250aa7SWarner Losh include: 8668f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 8678f250aa7SWarner Losh - newaliases limited to root and trusted users 8688f250aa7SWarner Losh - MSA port (587) turned on by default 8698f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 8708f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 8718f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 8728f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 8738f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 8748f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 8758f250aa7SWarner Losh 87671c38472SWarner Losh20000810: 87771c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 87871c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 87971c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 88071c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 88171c38472SWarner Losh specific use for it. 88271c38472SWarner Losh 88371c38472SWarner Losh20000729: 88471c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 88571c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 88671c38472SWarner Losh /etc/rc.conf if they want to have the same setup 88771c38472SWarner Losh afterwards (unless the variables already are set, of course): 88871c38472SWarner Losh # Enable network daemons for user convenience. 88971c38472SWarner Losh inetd_enable="YES" 89071c38472SWarner Losh portmap_enable="YES" 89171c38472SWarner Losh sendmail_enable="YES" 89271c38472SWarner Losh 89371c38472SWarner Losh20000728: 89471c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 89571c38472SWarner Losh will need to change that to nullfs_load="YES". 89671c38472SWarner Losh 8971dece4a9SWarner Losh20000728: 8981dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 8991dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 9001dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 9011dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 9021dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 9031dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 9041dece4a9SWarner Losh to /MYKERNEL. 9051dece4a9SWarner Losh 906409e887cSWarner Losh20000711: 907409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 908409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 909409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 910409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 911409e887cSWarner Losh for details on potential problems that you might have and how 912409e887cSWarner Losh to get around them. 913409e887cSWarner Losh 914409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 915409e887cSWarner Losh clauses above, you needn't worry. 916409e887cSWarner Losh 917409e887cSWarner Losh20000711: 918409e887cSWarner Losh /etc/security has been updated to print the inode number of 919409e887cSWarner Losh setuid programs that have changed. You will see a large spike 920409e887cSWarner Losh in the number of changed programs the first time when you run 921409e887cSWarner Losh mergemaster to get a new /etc/security. 922409e887cSWarner Losh 923673d13f2SWarner Losh20000710: 924673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 925673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 926673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 927673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 928673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 929673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 930673d13f2SWarner Losh errors. (see below, 20000624). 931673d13f2SWarner Losh 932bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 9331dece4a9SWarner Losh 934673d13f2SWarner Losh20000709: 935c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 936c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 937c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 938673d13f2SWarner Losh ln -s aj /etc/malloc.conf 939673d13f2SWarner Losh 940e98e26cdSWarner Losh20000706: 941e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 942e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 943e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 944f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 945e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 9462c021c6cSMark Ovens interim if needed. 947e98e26cdSWarner Losh 948e98e26cdSWarner Losh20000705: 949e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 950e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 951e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 952e98e26cdSWarner Losh details. 953e98e26cdSWarner Losh 954c373950eSWarner Losh20000704: 9552f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 9562f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 9572f961bc8SWarner Losh 9582f961bc8SWarner Losh20000704: 959c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 960c373950eSWarner Losh or stop. This may cause some harmless warnings from older 961c373950eSWarner Losh rc.d scripts that haven't been updated. 962c373950eSWarner Losh 96327dc3a2bSWarner Losh20000630: 96427dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 96527dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 96627dc3a2bSWarner Losh which should be reported to des@freebsd.org. 96727dc3a2bSWarner Losh 968b8c215acSWarner Losh20000625: 969b8c215acSWarner Losh From approximately this date forward, one must have the crypto 97027dc3a2bSWarner Losh system installed in order to build the system and kernel. 97127dc3a2bSWarner Losh While not technically strictly true, one should treat it as 97227dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 97327dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 97427dc3a2bSWarner Losh were required. You should check with the latest collections 97527dc3a2bSWarner Losh to make sure that these haven't changed. 976b8c215acSWarner Losh 9777b990719SWarner Losh20000624: 9787b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 9797b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 9807b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 9811a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 9827b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 9837b990719SWarner Losh openssh and openssl should not be used to generate keys from this 9847b990719SWarner Losh date to the completion of the work. 9857b990719SWarner Losh 98627dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 98727dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 98827dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 98927dc3a2bSWarner Losh recreate the random and urandom devices. 99027dc3a2bSWarner Losh 99181e54c50SWarner Losh20000622: 99281e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 99381e54c50SWarner Losh BSD license. You may need to remove your symbolic links 99481e54c50SWarner Losh that used to be required when updating. 99581e54c50SWarner Losh 99639943833SWarner Losh20000621: 9972c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 9982a2f33fbSDaniel Baker the config file update procedure. 9992a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 1000c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 100159df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 100259df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 100339943833SWarner Losh 1004290f9ad8SWarner Losh20000620: 1005290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 1006290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 1007290f9ad8SWarner Losh that workaround will no longer be required. 1008290f9ad8SWarner Losh 100990fb6346SWarner Losh20000615: 101090fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 101190fb6346SWarner Losh ad driver. If you haven't done so already, you must update 101290fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 101390fb6346SWarner Losh devices. 101490fb6346SWarner Losh 1015f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 1016f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 1017f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 1018f75f65bbSWarner Losh may work). 1019f75f65bbSWarner Losh 1020ba26da8eSWarner Losh20000612: 1021ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 1022290f9ad8SWarner Losh on the topic before even thinking about updating. You will 1023c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 1024290f9ad8SWarner Losh to your config file to compile them in statically. The format 1025f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 1026f54a3542SWarner Losh NEWCARD for examples of the new format. 1027290f9ad8SWarner Losh 10289698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 10299698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 10309698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 10319698f2c0SWarner Losh in it. 1032bbcc5149SWarner Losh 1033d65850ebSWarner Losh20000522: 1034ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 1035d65850ebSWarner Losh building a kernel after this point is advised that they need 1036d65850ebSWarner Losh to rebuild their binutils (or better yet do a 1037d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 1038d65850ebSWarner Losh 1039d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1040d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1041d9583a00SWarner Losh is recommended that you don't set this option until the problem 1042d9583a00SWarner Losh is resolved. 1043d9583a00SWarner Losh 10448039cedeSWarner Losh20000513: 10458039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 10468039cedeSWarner Losh 1047d65850ebSWarner Losh20000510: 10488039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 10498039cedeSWarner Losh This will require some care in updating alphas. A new libstand 10508039cedeSWarner Losh is requires for the boot blocks to build properly. 10518039cedeSWarner Losh 10528039cedeSWarner Losh20000503: 10538039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 10548039cedeSWarner Losh is now available. 10558039cedeSWarner Losh 1056d65850ebSWarner Losh20000502: 1057d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1058d65850ebSWarner Losh connected to the kernel building instead. 1059d65850ebSWarner Losh 1060be149406SNik Clayton20000427: 10618039cedeSWarner Losh You may need to build gperf 10628039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 10638039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 10648039cedeSWarner Losh an option only in -current. 10658039cedeSWarner Losh 10662b8dd5f4SWarner Losh20000417: 10672b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1068f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 10692b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 10702b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 10712c021c6cSMark Ovens before you reboot, you'll need to issue: 10722b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 10732b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 10742b8dd5f4SWarner Losh 10758d9f1945SWarner Losh20000320: 10762b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 10772b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 10782b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1079ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 10802b8dd5f4SWarner Losh to the start of /etc/rc.conf. 10818d9f1945SWarner Losh 1082f8ab1dd6SWarner Losh20000319: 1083f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1084f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1085f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1086f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1087f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1088f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1089f8ab1dd6SWarner Losh 109019cada77SWarner Losh20000318: 1091f699bbbbSMark Ovens We've entered the traditional post release dumping party. 109219cada77SWarner Losh Large kernel changes are being committed and are in the 109319cada77SWarner Losh works. It is important to keep the systems' klds and kernel 109419cada77SWarner Losh in sync as kernel interfaces and structures are changing. 109519cada77SWarner Losh Before reporting kernel panics, make sure that all modules 109619cada77SWarner Losh that you are loading are up to date. 1097ba228352SWarner Losh 109819cada77SWarner Losh20000315: 10996d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 11006d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 11016d23c382SWarner Losh will do the trick. This isn't critical until you remove your 11026d23c382SWarner Losh wd device entries in /dev, at which point your system will not 11036d23c382SWarner Losh boot. 11046d23c382SWarner Losh 11056d23c382SWarner Losh20000315: 110619cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 110719cada77SWarner Losh to upgrade to 4.0 from 3.x. 110857199806SWarner Losh 1109dc0dbf5cSWarner LoshCOMMON ITEMS: 1110dc0dbf5cSWarner Losh 1111a24eff53SWarner Losh General Notes 1112a24eff53SWarner Losh ------------- 1113a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1114a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1115a24eff53SWarner Losh installworld. This is especially true when upgrading between 1116a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1117a24eff53SWarner Losh or several minor releases, or when several months have passed 1118a24eff53SWarner Losh on the -current branch). 1119a24eff53SWarner Losh 11205780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 11215780f3baSWarner Losh poisoning. This can happen because the make utility reads its 11225780f3baSWarner Losh environment when searching for values for global variables. 11235780f3baSWarner Losh To run your build attempts in an "environmental clean room", 11245780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 11255780f3baSWarner Losh page for more details. 11265780f3baSWarner Losh 1127dc0dbf5cSWarner Losh To build a kernel 1128dc0dbf5cSWarner Losh ----------------- 1129ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1130f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1131ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 11321e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 11331e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 1134dc0dbf5cSWarner Losh 1135ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1136ba01eb20SWarner Losh -------------------------------------------------------------- 1137ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 113847d0d01fSWarner Losh config KERNEL_NAME_HERE 1139ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1140ba01eb20SWarner Losh make depend 1141ba01eb20SWarner Losh make 1142ba01eb20SWarner Losh make install 1143ba01eb20SWarner Losh 1144ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1145ba01eb20SWarner Losh 1146ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1147ba01eb20SWarner Losh ----------------------------------------------------------- 114863cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 114963cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 115063cb445eSWarner Losh 1151f643de42SWarner Losh <make sure you have good level 0 dumps> 115263cb445eSWarner Losh <maybe fix /etc/fstab> [7] 115363cb445eSWarner Losh make buildworld 115463cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 115563cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 115663cb445eSWarner Losh [1] 115763cb445eSWarner Losh <reboot in single user> [3] 115863cb445eSWarner Losh mergemaster -p [5] 115963cb445eSWarner Losh make installworld 116063cb445eSWarner Losh mergemaster [4] 116163cb445eSWarner Losh <reboot> 116263cb445eSWarner Losh 1163759f0aefSWarner Losh 1164f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1165f27b1fceSJoseph Koshy -------------------------------------------------- 1166f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1167f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1168f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1169f27b1fceSJoseph Koshy # size. 1170f27b1fceSJoseph Koshy 1171f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1172f27b1fceSJoseph Koshy <boot into -stable> 1173f27b1fceSJoseph Koshy make buildworld 1174f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1175f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1176f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1177f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1178f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1179f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1180f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1181f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1182f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1183f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1184f27b1fceSJoseph Koshy <reboot into current> 1185f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1186f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1187f27b1fceSJoseph Koshy <reboot> 1188f27b1fceSJoseph Koshy 1189f27b1fceSJoseph Koshy 1190f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1191f27b1fceSJoseph Koshy ---------------------------------------------- 11925c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 11935c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 11945c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 11955c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1196ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1197f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1198f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1199f643de42SWarner Losh # space on /. 1200f643de42SWarner Losh 1201f643de42SWarner Losh <make sure you have good level 0 dumps> 1202fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 120321c075eaSWarner Losh make buildworld [9] 1204c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1205d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1206be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1207fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1208fc8c157fSWarner Losh [1] 1209fc8c157fSWarner Losh <reboot in single user> [3] 1210835284beSWarner Losh mergemaster -p [5] 1211f8a4c901SWarner Losh rm -rf /usr/include/g++ 1212ba26da8eSWarner Losh make installworld 1213a6cd4f9dSWarner Losh mergemaster [4] 1214ba26da8eSWarner Losh <reboot> 1215ba26da8eSWarner Losh 1216fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1217fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1218fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1219fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1220fdb9f54dSWarner Losh the UPDATING entries. 1221ba26da8eSWarner Losh 12221dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 12231dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 12241dece4a9SWarner Losh your sources that you have read and understood all the recent 12251dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 12261dece4a9SWarner Losh much fewer pitfalls. 12271dece4a9SWarner Losh 1228134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1229134d2e86SWarner Losh should disable them at this point so they don't crash your 1230134d2e86SWarner Losh system on reboot. 1231134d2e86SWarner Losh 12329c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 12339c1a7444SWarner Losh your own device.hints to reflect your unique hardware 12349c1a7444SWarner Losh configuration. 12359c1a7444SWarner Losh 1236ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1237ee6e1fc3SWarner Losh fsck -p 1238ee6e1fc3SWarner Losh mount -u / 1239ee6e1fc3SWarner Losh mount -a 1240ee6e1fc3SWarner Losh cd /usr/src 124147d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1242f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1243f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1244b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1245b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1246b705ae10SWarner Losh be ignored while you proceed to the next step. 1247ee6e1fc3SWarner Losh 1248a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1249a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1250a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1251a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1252a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1253a6cd4f9dSWarner Losh for potential gotchas. 1254a6cd4f9dSWarner Losh 1255835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1256835284beSWarner Losh you may need to do this if you get unknown user in the following 1257835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1258835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1259835284beSWarner Losh install) after the buildworld before this step if you last updated 1260835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1261835284beSWarner Losh 1262bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1263bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1264bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1265bd79cf40SWarner Losh ok unload 1266bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1267bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1268bd79cf40SWarner Losh described here. 1269fc8c157fSWarner Losh 1270fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1271fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1272fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1273fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1274fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1275fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1276fc8c157fSWarner Losh 1277c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1278c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1279c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1280c74fe6afSWarner Losh that is hard to boot to recover. 1281c74fe6afSWarner Losh 128221c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 128321c075eaSWarner Losh cvs prune empty directories. 1284dc0dbf5cSWarner LoshFORMAT: 1285dc0dbf5cSWarner Losh 1286f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 12871fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1288f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1289f8ab1dd6SWarner Loshprevious releases if your system is older than this. 12901fc1a0dcSWarner Losh 1291e72fd46aSWarner LoshCopyright information: 1292e72fd46aSWarner Losh 12939698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1294e72fd46aSWarner Losh 1295772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1296772730c7SWarner Loshmodification, in full or in part, in any form or format of this 12979698f2c0SWarner Loshdocument are permitted without further permission from the author. 1298e72fd46aSWarner Losh 1299e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1300e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1301e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1302e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1303e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1304e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1305e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1306e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1307e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1308e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1309e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1310e72fd46aSWarner Losh 1311e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1312e72fd46aSWarner Loshauthor a beer. 1313e72fd46aSWarner Losh 131422306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1315772730c7SWarner Loshthis document. 1316772730c7SWarner Losh 131797d92980SPeter Wemm$FreeBSD$ 1318