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 2081cda3d9SWarner Losh20030423: 2181cda3d9SWarner Losh A bug has been fixed in /dev/devctl which would cause devd 2281cda3d9SWarner Losh to hang on boot, were it not for a workaround in devd. The 2381cda3d9SWarner Losh work around in devd will be removed around 20030507. You 2481cda3d9SWarner Losh have until then to upgrade your kernel before updating 2581cda3d9SWarner Losh userland. In general, you should have a userland and 2681cda3d9SWarner Losh kernel that's in sync with each other. However, given the 2781cda3d9SWarner Losh effects of this bug (hang on boot when starting devd), some 2881cda3d9SWarner Losh allowances are made. 2981cda3d9SWarner Losh 3047a657d1SRuslan Ermilov20030329: 3147a657d1SRuslan Ermilov Alphas with libc from between 20030312 and 20030329 exhibit 3247a657d1SRuslan Ermilov floating point exceptions (FPEs), most notably in awk(1) 3347a657d1SRuslan Ermilov while upgrading the system through a buildworld. 3447a657d1SRuslan Ermilov 3547a657d1SRuslan Ermilov So, to successfully upgrade your Alpha, you must either 3647a657d1SRuslan Ermilov downgrade your libc.so to a pre-20030312 version, or update 3747a657d1SRuslan Ermilov /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 3847a657d1SRuslan Ermilov to CFLAGS, then forcibly rebuild and install libc: 3947a657d1SRuslan Ermilov 4047a657d1SRuslan Ermilov cd /usr/src/lib/libc && \ 4147a657d1SRuslan Ermilov make cleandir && make obj && \ 4247a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE all && \ 4347a657d1SRuslan Ermilov make -DNOMAN -DNOPROFILE install 4447a657d1SRuslan Ermilov 455d2af00cSGregory Neil Shapiro20030208: 465d2af00cSGregory Neil Shapiro sendmail 8.12.7 has been imported. It has one important 475d2af00cSGregory Neil Shapiro change for IPv6 users. The default submit.mc now uses 485d2af00cSGregory Neil Shapiro '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 495d2af00cSGregory Neil Shapiro used to connect to the MTA. Users on IPv6-only machines 505d2af00cSGregory Neil Shapiro will need to edit /etc/mail/submit.mc appropriately. 515d2af00cSGregory Neil Shapiro 525d2af00cSGregory Neil Shapiro20030128: 539db58771SPoul-Henning Kamp NODEVFS option has been removed and DEVFS thereby made standard. 54ca22e652SJens Schweikhardt This makes all references to MAKEDEV obsolete, and they should 559db58771SPoul-Henning Kamp be removed when convenient. 569db58771SPoul-Henning Kamp 578d9b3f57SJake Burkholder20030126: 588d9b3f57SJake Burkholder The name of the device for the ofw console has changed, sparc64 users 598d9b3f57SJake Burkholder must run mergemaster to update their installed /etc/ttys. 608d9b3f57SJake Burkholder 611c5efda5SJeff Roberson20030125: 621c5efda5SJeff Roberson The scheduler framework has grown a second scheduler and consequently 631c5efda5SJeff Roberson you must specify one and only one scheduler in your kernel config. 64ca22e652SJens Schweikhardt The cvs config files have been updated to use the old scheduler 651c5efda5SJeff Roberson which may be selected via 'options SCHED_4BSD'. If you would like 661c5efda5SJeff Roberson to try the new, much more experimental, scheduler please try 671c5efda5SJeff Roberson 'options SCHED_ULE' and contribute to the arch@ discussion. 681c5efda5SJeff Roberson 699d1d64f5SWarner Losh20030115: 709d1d64f5SWarner Losh A new version of the wi driver has been imported into the tree. 719d1d64f5SWarner Losh One now must have device wlan in the config file for it to operate 729d1d64f5SWarner Losh properly. 739d1d64f5SWarner Losh 74c9fdb80aSWarner Losh In addition, there have been some changes to how wi devices are 75c9fdb80aSWarner Losh configured for point to point links to bring it more in line 76c9fdb80aSWarner Losh with the former way of doing things, as well as compatibility 77c9fdb80aSWarner Losh with NetBSD. 78c9fdb80aSWarner Losh 79161dc364SAlexander Kabaev20021222: 80161dc364SAlexander Kabaev For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 81161dc364SAlexander Kabaev used an incompatible form of ABI for returning structures and unions 82161dc364SAlexander Kabaev which FreeBSD's GCC maintainers were not aware of relative to previous 83161dc364SAlexander Kabaev versions of FreeBSD. We have gone back to the ABI for now, and any 84161dc364SAlexander Kabaev code compiled which is required to interoperate with other code (not 85161dc364SAlexander Kabaev built at the same time) returning structs or unions should be 8684cc83efSAlexander Kabaev rebuilt. 87161dc364SAlexander Kabaev 88fb4c8061SMartin Blapp20021216: 89fb4c8061SMartin Blapp A name change in /etc/netconfig has been reverted to stay 9089056245SJens Schweikhardt compatible with suns TIRPC and also with NetBSD. You need 91fb4c8061SMartin Blapp to run mergemaster after make world. A new libc does still work 929d5abbddSJens Schweikhardt with an outdated /etc/netconfig for some time, but you'll get 93fb4c8061SMartin Blapp a warning. This warning will be removed in 20030301. 94fb4c8061SMartin Blapp 9517d47eb3SGiorgos Keramidas20021202: 9617d47eb3SGiorgos Keramidas The recent binutils upgrade marks a kernel flag day on 9717d47eb3SGiorgos Keramidas sparc64: modules built with the old binutils will not work 9817d47eb3SGiorgos Keramidas with new kernels and vice versa. Mismatches will result in 9917d47eb3SGiorgos Keramidas panics. Make sure your kernel and modules are in sync. 10017d47eb3SGiorgos Keramidas 101a4459294SBill Fenner20021029: 102a4459294SBill Fenner The value of IPPROTO_DIVERT has changed. Make sure to keep 103a4459294SBill Fenner your kernel, netstat, natd and any third-party DIVERT 104a4459294SBill Fenner consumers in sync. 105a4459294SBill Fenner 106fc8c157fSWarner Losh20021024: 107c57404feSRuslan Ermilov Old, compatibility slices have been removed in GEOM kernels. 108c57404feSRuslan Ermilov This means that you will have to update your /etc/fstab to 109c57404feSRuslan Ermilov not use disk devices of the form /dev/ad0a. Instead, you 110c57404feSRuslan Ermilov now must specify /dev/ad0s1a, or whatever slice your FreeBSD 111c57404feSRuslan Ermilov partition really is on. The old device names have gone 112c57404feSRuslan Ermilov away, so if you use them anywhere else, you must also adjust 113c57404feSRuslan Ermilov those uses. (This doesn't affect the disks formatted in 114c57404feSRuslan Ermilov the ``dangerously-dedicated'' mode.) 11569f7bcf3SWarner Losh 116fd9e8bdaSAndrew Gallatin20021023: 117fd9e8bdaSAndrew Gallatin Alphas with kernels from between 20020830 and 20021023 and/or 118fd9e8bdaSAndrew Gallatin rtld (ld-elf.so.1) older than 20021023 may experience problems 119fd9e8bdaSAndrew Gallatin with groff while doing a buildworld (kernel: "out of memory", 120fd9e8bdaSAndrew Gallatin fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 121fd9e8bdaSAndrew Gallatin segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 122fd9e8bdaSAndrew Gallatin 123fd9e8bdaSAndrew Gallatin So, to successfully upgrade your Alpha, you must either 124fd9e8bdaSAndrew Gallatin upgrade your kernel and rtld first (which might be a bit 125fd9e8bdaSAndrew Gallatin tricky), or avoid running the bootstrapped groff during the 126fd9e8bdaSAndrew Gallatin "transitional" buildworld. To avoid running groff during the 127fd9e8bdaSAndrew Gallatin transitional upgrade run make buildworld with -DNOMAN, 128fd9e8bdaSAndrew Gallatin -DNO_SHAREDOCS, and -DNO_LPR. 129fd9e8bdaSAndrew Gallatin 130f8a4c901SWarner Losh20020831: 131f8a4c901SWarner Losh gcc has been upgraded to 3.2. It is not all binary compatible 132f8a4c901SWarner Losh with earlier versions of gcc for c++ programs. All c++ 133f8a4c901SWarner Losh programs and libraries need to be recompiled. 134f8a4c901SWarner Losh 135f8a4c901SWarner Losh Also, if you encounter g++ issues, rm /usr/include/g++/* before 136f8a4c901SWarner Losh doing an installworld to make sure that stale files are removed. 137f8a4c901SWarner Losh 138c2248fa2SJens Schweikhardt20020827: 139c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 140c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 141c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 142c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 143c2248fa2SJens Schweikhardt 1440d533e43SRuslan Ermilov20020815: 1450d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 1460d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 1470d533e43SRuslan Ermilov again. 1480d533e43SRuslan Ermilov 14933c1de7dSRuslan Ermilov20020729: 15033c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 15133c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 15233c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 15333c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 15433c1de7dSRuslan Ermilov 1552b877facSJulian Elischer20020702: 1562b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 1572b877facSJulian Elischer There are still some minor problems with some signals but the 1582b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 1592b877facSJulian Elischer but each can successfully complete multiple buildworlds. 1602b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 1612b877facSJulian Elischer 16206596d37SWarner Losh20020701: 16306596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 16406596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 16506596d37SWarner Losh GNOME. 16606596d37SWarner Losh 16795ba4330SJacques Vidrine20020511: 16895ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 16995ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 17095ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 17195ba4330SJacques Vidrine with the set-user-ID bit set. 17295ba4330SJacques Vidrine 173a81da3c9SDavid E. O'Brien20020510: 174f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 175f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 1764b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 177f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 178f50caf6fSDavid E. O'Brien 179f50caf6fSDavid E. O'Brien20020510: 180a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 181a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 182a81da3c9SDavid E. O'Brien and then do a cvs update. 183a81da3c9SDavid E. O'Brien 184528a0ef5SJacques Vidrine20020421: 185528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 186528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 187528a0ef5SJacques Vidrine 18885aa5a2eSGregory Neil Shapiro20020404: 18985aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 19085aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 19185aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 19285aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 19385aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 19485aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 19585aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 19685aa5a2eSGregory Neil Shapiro 1978f1e4358SRuslan Ermilov20020403: 1988f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 1998f1e4358SRuslan Ermilov 2002292c02eSWarner Losh20020315: 2012292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 2022292c02eSWarner Losh 20369f7bcf3SWarner Losh20020225: 20469f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 20569f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 20669f7bcf3SWarner Losh 2078f35c493SWarner Losh20020217: 2088f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 2098f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 2108f35c493SWarner Losh command line mail submission has changed. Be sure to run 2118f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 2128f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 2138f35c493SWarner Losh 214835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 215835284beSWarner Losh required in order for sendmail to run as a set-group-ID 216835284beSWarner Losh binary. A 'make installworld' will use the new user and group 217835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 218835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 219835284beSWarner Losh and group must be merged from src/etc/group and 220835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 221835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 222835284beSWarner Losh mergemaster before this will work if you are updating from a 223835284beSWarner Losh very old version of current. The updating recipe has changed 224835284beSWarner Losh as of this date. 225835284beSWarner Losh 226fa9401c1SWarner Losh20020112: 227fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 228fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 229fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 230fa9401c1SWarner Losh you have local modifications, you can use 231fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 232fa9401c1SWarner Losh /etc/pam.d. 233fa9401c1SWarner Losh 234fa9401c1SWarner Losh Please see the following url for more details: 235fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 23647d0d01fSWarner Losh20011229: 23747d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 23847d0d01fSWarner Losh networkfs_types, please note that it has changed 23947d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 24047d0d01fSWarner Losh 241514318a8SWarner Losh20011220: 242514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 243514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 244514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 245514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 246514318a8SWarner Losh version have now been merged back into the base system's 247514318a8SWarner Losh version now. The only user-visible change resulting from this 248514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 249514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 250514318a8SWarner Losh as well. (There has never been rc file support for 251514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 252514318a8SWarner Losh reverted by the time the changes are MFCed.) 253514318a8SWarner Losh 254514318a8SWarner Losh20011215: 255514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 256514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 257514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 258514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 259514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 260514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 261514318a8SWarner Losh will need to be customized then for `odd' densities using 262514318a8SWarner Losh fdcontrol(8). 263514318a8SWarner Losh 2642d22e2bfSWarner Losh20011209: 2652d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 2662d22e2bfSWarner Losh and truss(1) now works again. 2672d22e2bfSWarner Losh 2689e0428e2SWarner Losh20011207: 2699e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 2709e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 2719e0428e2SWarner Losh see 2729e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 2739e0428e2SWarner Losh for details. 2749e0428e2SWarner Losh 2759bab8c59SWarner Losh20011204: 2769bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 2779bab8c59SWarner Losh kernel and burncd to be in sync. 2789bab8c59SWarner Losh 279e57d8b01SWarner Losh20011203: 280e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 281e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 282e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 283e57d8b01SWarner Losh not there already. 284e57d8b01SWarner Losh 285e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 286e57d8b01SWarner Losh until the issue has been resolved. 287e57d8b01SWarner Losh 288b001d36fSJacques Vidrine20011202: 289b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 290b001d36fSJacques Vidrine patched. 291b001d36fSJacques Vidrine 2924b676ec1SWarner Losh20011126: 2934b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 2945ebbf43eSWarner Losh after this date. You need to do this only once. 2954b676ec1SWarner Losh 296d961e462SWarner Losh20011103: 297d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 298d961e462SWarner Losh edges may be left, but for the most part things should be 2994b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 300d961e462SWarner Losh 301d961e462SWarner Losh20011030: 302d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 303d961e462SWarner Losh choppy waves in the upgrade process. 304d961e462SWarner Losh 3051fe003b6SWarner Losh20011030: 306a4b6fda0SWarner Losh The asr driver problem has been resolved. 3071fe003b6SWarner Losh 3081fe003b6SWarner Losh20011027: 3091fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 3101fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 3111fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 3121fe003b6SWarner Losh try to use from this date forward. 3131fe003b6SWarner Losh 3141fe003b6SWarner Losh20011025: 3151fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 3161fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 3171fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 3181fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 3191fe003b6SWarner Losh TARGET_ARCH=i386. 3201fe003b6SWarner Losh 321d05f9643SWarner Losh20011001: 322d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 323d05f9643SWarner Losh You must recompile both the kernel and userland applications 324d05f9643SWarner Losh at the same time. 325d05f9643SWarner Losh 32658970f85SWarner Losh20010929: 32758970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 32858970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 32958970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 33058970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 3319d5abbddSJens Schweikhardt (eg, you can build pc98 on an i386 machine and vice versa). 33258970f85SWarner Losh 33358970f85SWarner Losh20010927: 33458970f85SWarner Losh Some weird problems result from using ACPI on some machines. 33558970f85SWarner Losh To disable ACPI you can add 33666ff0e67SMax Khon hint.acpi.0.disabled="1" 33758970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 33858970f85SWarner Losh loader "ok" prompt). 33958970f85SWarner Losh 34058970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 34158970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 34258970f85SWarner Losh file and not list acpi in that list. 343378f4486SAlfred Perlstein 3445119d237SWarner Losh20010924: 3455119d237SWarner Losh The buildworld has been fixed. You may need to install 3465119d237SWarner Losh the 4.x compatibility libraries for some old binaries 3478b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 3488b039fffSWarner Losh get them installed on every installworld, or execute the 3498b039fffSWarner Losh following to get them installed only once: 3508b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 35158970f85SWarner Losh make all install 3528b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 3535119d237SWarner Losh 3543c293725SWarner Losh20010919: 3553c293725SWarner Losh There's a bug in the world build process. The cross-tools 3563c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 3573c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 358772730c7SWarner Losh workaround is to add 3593c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 3603c293725SWarner Losh before building world when upgrading from 4.x to current. This 3613c293725SWarner Losh can be removed afterwards. 3623c293725SWarner Losh 3633c293725SWarner Losh A proper fix to the buildworld target is needed. 3643c293725SWarner Losh 3653c293725SWarner Losh20010918: 3663c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 3673c293725SWarner Losh NFS may be unstable after this date. 3683c293725SWarner Losh 3693c293725SWarner Losh20010912: 3703c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 3713c293725SWarner Losh the kernel. While a few problems were introduced in the 3723c293725SWarner Losh initial commit, most of the major ones have been found and 3733c293725SWarner Losh corrected. 3743c293725SWarner Losh 3753c293725SWarner Losh20010901: 3763c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 3773c293725SWarner Losh arounds described in the 20010604 entry are now no longer 3783c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 3793c293725SWarner Losh have been rectified around this date. 3803c293725SWarner Losh 38198b17b95SWarner Losh20010823: 38298b17b95SWarner Losh named now runs as user bind and group bind rather than as 38398b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 38498b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 38598b17b95SWarner Losh and that group bind is available in /etc/group. Also make 38698b17b95SWarner Losh sure that user or group bind has read (and not write) 38798b17b95SWarner Losh permission for your name server configuration and that it 38898b17b95SWarner Losh has read and write permission for your slave zone files and 38998b17b95SWarner Losh directory. 39098b17b95SWarner Losh 39198b17b95SWarner Losh If you wish to continue to run named as root (a less secure 39298b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 39398b17b95SWarner Losh 39498b17b95SWarner Losh named_flags= 39598b17b95SWarner Losh 3967b9786edSMark Murray20010709: 3977b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 3987b9786edSMark Murray the ability of the shared library major number to handle. 3997b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 4007b9786edSMark Murray solution is to rebuild those ports. 4017b9786edSMark Murray 4021d28950eSWarner Losh20010628: 4031d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 4041d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 4051d28950eSWarner Losh 406e72fd46aSWarner Losh20010625: 40798b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 40898b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 40998b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 41098b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 41198b17b95SWarner Losh IRQ configuration needs more safety belts. 41216de1a07SWarner Losh 4130d415dffSWarner Losh20010617: 414e72fd46aSWarner Losh Softupdates problems have been corrected. 4150d415dffSWarner Losh 4160d415dffSWarner Losh20010614: 4170d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 4180d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 4190d415dffSWarner Losh kernel building methods. 4200d415dffSWarner Losh 4218b9959adSWarner Losh20010613: 4228b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 4238b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 424e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 425e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 4268b9959adSWarner Losh 427e72fd46aSWarner Losh20010613: 4288b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 429e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 430e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 4318b9959adSWarner Losh 4320d415dffSWarner Losh20010612: 4330d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 4340d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 4350d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 4360d415dffSWarner Losh work around this issue, please use only one or the other mechanism 4370d415dffSWarner Losh until this bug is fixed. 4380d415dffSWarner Losh 439e72fd46aSWarner Losh Please note that a feature of config is that if you have config 440e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 441ca22e652SJens Schweikhardt hints.c file, whether you want it to or not. 442e72fd46aSWarner Losh 4430d415dffSWarner Losh20010610: 4440d415dffSWarner Losh Locale names have changed to match other systems better. 4450d415dffSWarner Losh 4466ccdb5e4SWarner Losh20010604: 4476ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 4486ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 4496ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 4503590182eSWarner Losh Interrupt storms look a lot like a hang. 4513590182eSWarner Losh 4523590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 4533590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 4543590182eSWarner Losh it is). 4553590182eSWarner Losh 4563590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 4573590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 4583590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 4593590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 4606ccdb5e4SWarner Losh 4610bc62786SWarner Losh20010530: 4620bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 4630bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 4640bc62786SWarner Losh a limited time. If you see 4650bc62786SWarner Losh 4660bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 4670bc62786SWarner Losh 4680bc62786SWarner Losh in your makeworld, then you need to migrate towards using 4690bc62786SWarner Losh COPY=-C. 4700bc62786SWarner Losh 47168a38c6cSWarner Losh20010525: 472b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 473c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 474c4f4a728SWarner Losh definitely is in bad shape. 47568a38c6cSWarner Losh 476ed0f29caSWarner Losh20010521: 477ca22e652SJens Schweikhardt Minor repo damage has happened. This may cause problems 478ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 479ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 480ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 481ed0f29caSWarner Losh is 482ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 483ed0f29caSWarner Losh 48480c16af9SWarner Losh20010520: 48568a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 48680c16af9SWarner Losh 48780c16af9SWarner Losh20010519: 48880c16af9SWarner Losh pccard has had much reorganizational work done to it over 48980c16af9SWarner Losh the past few days. Everything should still work, but if 49080c16af9SWarner Losh not, please contact imp@freebsd.org. 49180c16af9SWarner Losh 492a45f2d05SWarner Losh20010517: 493a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 494a45f2d05SWarner Losh userland at the same time. 495a45f2d05SWarner Losh 496a45f2d05SWarner Losh20010517: 497a45f2d05SWarner Losh New ncurses imported. 498a45f2d05SWarner Losh 4992988afcaSWarner Losh20010512: 5002988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 5012988afcaSWarner Losh will be the only way to go starting July 1. 5022988afcaSWarner Losh 5031a33dba7SWarner Losh20010504: 5041a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 5051a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 5061a33dba7SWarner Losh 50709946a51SWarner Losh20010502: 50809946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 50909946a51SWarner Losh 51009946a51SWarner Losh20010501: 51109946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 51209946a51SWarner Losh 51309946a51SWarner Losh20010430: 514a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 51509946a51SWarner Losh go back in the water. 51609946a51SWarner Losh 51709946a51SWarner Losh20010429: 51809946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 51909946a51SWarner Losh this date, but before the correction date. 52009946a51SWarner Losh 52191dd3b53SWarner Losh20010423: 52291dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 52391dd3b53SWarner Losh 52491dd3b53SWarner Losh20010411: 52591dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 52691dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 52791dd3b53SWarner Losh Update only if you understand that you must not use the old 52891dd3b53SWarner Losh fsck with the new kernel ever. 52991dd3b53SWarner Losh 530933b3269SWarner Losh20010330: 531933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 532c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 533933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 534933b3269SWarner Losh 535933b3269SWarner Losh20010319: 536933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 537933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 538933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 539f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 54009946a51SWarner Losh 54109946a51SWarner Losh20010315: 54209946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 543ca22e652SJens Schweikhardt and ATA_ENABLE_TAGS are no longer kernel options. They have 54409946a51SWarner Losh been replaced by tunables. See ata.4 for details. 545933b3269SWarner Losh 546933b3269SWarner Losh20010312: 547933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 548933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 549933b3269SWarner Losh 550933b3269SWarner Losh20010312: 551933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 552933b3269SWarner Losh instead of ad-hoc. 553933b3269SWarner Losh 554933b3269SWarner Losh20010310: 555f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 556933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 557933b3269SWarner Losh ssh might not work if you don't. 558933b3269SWarner Losh 55962353691SWarner Losh20010303: 56062353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 56162353691SWarner Losh which means that you must include the miibus in your kernel if 56262353691SWarner Losh you use the ed driver. 56362353691SWarner Losh 564d325cf65SWarner Losh20010220: 565d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 566d325cf65SWarner Losh safe to go back into the water. 567d325cf65SWarner Losh 568024daae6SWarner Losh20010211: 569024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 570024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 571024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 572024daae6SWarner Losh that before upgrading would be a good time to do a level 0 573024daae6SWarner Losh dump of your system. No, really, I mean it this time. 574024daae6SWarner Losh 575024daae6SWarner Losh To get to the new system, you'll need to use the following 576024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 577024daae6SWarner Losh don't have to move this to the updating section. 578024daae6SWarner Losh 579024daae6SWarner Losh To get around the installworld problem, do: 580024daae6SWarner Losh # cd /usr/src/usr.bin/sed 581024daae6SWarner Losh # make install 582024daae6SWarner Losh # cd /usr/src 583024daae6SWarner Losh # make installworld 584024daae6SWarner Losh If that doesn't work, then try: 585024daae6SWarner Losh # make -k installworld 586024daae6SWarner Losh # make installworld 587024daae6SWarner Losh 588024daae6SWarner Losh20010207: 589024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 590024daae6SWarner Losh do not include devfs in your kernel as problems result. 591024daae6SWarner Losh 592024daae6SWarner Losh20010205: 5937595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 594024daae6SWarner Losh Remove them from your config. 595024daae6SWarner Losh 5961e159248SWarner Losh20010122: 5971e159248SWarner Losh ****************************** WARNING ****************************** 5981e159248SWarner Losh buildkernel has been changed slightly 5991e159248SWarner Losh ****************************** WARNING ****************************** 6001e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 6011e159248SWarner Losh should update your scripts and make.conf accordingly. 6021e159248SWarner Losh 6031e159248SWarner Losh20010119: 6041e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 6051e159248SWarner Losh This requires a new config to build correctly. 6061e159248SWarner Losh 607aac7dfeaSWarner Losh20010116: 608ca22e652SJens Schweikhardt The kernel option I386_CPU is now mutually exclusive with the 609aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 610aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 611aac7dfeaSWarner Losh 612aac7dfeaSWarner Losh20010110: 613aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 614aac7dfeaSWarner Losh 615aac7dfeaSWarner Losh20010102: 616aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 617aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 618aac7dfeaSWarner Losh 61963c90c9eSWarner Losh20010101: 62063c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 62163c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 6225fd2a895SWarner Losh dump while building termcap. You can work around this problem 62363c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 62463c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 62563c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 62663c90c9eSWarner Losh might have been ignored by the -k option. 62763c90c9eSWarner Losh 6285fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 6295fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 6305fd2a895SWarner Losh of this working. 6315fd2a895SWarner Losh 632aac7dfeaSWarner Losh20001228: 633aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 634ca22e652SJens Schweikhardt libscrypt/libdescrypt symlink silliness is gone and the installed 635aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 636aac7dfeaSWarner Losh 637de2bcc63SWarner Losh20001218: 638de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 639de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 640de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 641de2bcc63SWarner Losh cards will not be recognized without it. 642de2bcc63SWarner Losh 643960773f7SWarner Losh20001205: 644960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 645960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 646960773f7SWarner Losh adding the following in pam.conf: 647960773f7SWarner Losh 648960773f7SWarner Losh sshd auth sufficient pam_skey.so 649960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 650960773f7SWarner Losh sshd session required pam_permit.so 651960773f7SWarner Losh 6520acc635eSWarner Losh20001031: 6530acc635eSWarner Losh cvs updated to 1.11. 6540acc635eSWarner Losh 6550acc635eSWarner Losh20001020: 6560acc635eSWarner Losh The random device needs more entropy, so you need to make sure 6570acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 6580acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 6590acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 6600acc635eSWarner Losh workaround. 6610acc635eSWarner Losh 6620acc635eSWarner Losh20001010: 6630acc635eSWarner Losh ****************************** WARNING ****************************** 6640acc635eSWarner Losh Sendmail has been updated. 6650acc635eSWarner Losh ****************************** WARNING ****************************** 6660acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 6670acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 6680acc635eSWarner Losh is set. 6690acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 6700acc635eSWarner Losh commands. 6710acc635eSWarner Losh o Now using sendmail's version of vacation(1). 6720acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 6730acc635eSWarner Losh in /usr/share/sendmail/cf. 6740acc635eSWarner Losh o sendmail.cw changed to local-host-names 6750acc635eSWarner Losh 6760acc635eSWarner Losh More details can be found at 6770acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 6780acc635eSWarner Losh 6796e98a146SWarner Losh20001009: 6806e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 6816e98a146SWarner Losh your entire ports tree, or you will have problems. 6826e98a146SWarner Losh 6836e98a146SWarner Losh20001006: 684685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 6856e98a146SWarner Losh the installed miniperl. It is recommended that you delete 6866e98a146SWarner Losh /usr/bin/miniperl. 6876e98a146SWarner Losh 688073113a4SWarner Losh20001005: 689073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 690685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 691073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 692073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 693073113a4SWarner Losh tree for anything to work. 694073113a4SWarner Losh 6950acc635eSWarner Losh20000928: 6960acc635eSWarner Losh There was a change in the passwd format. Need more information. 6970acc635eSWarner Losh 698be3885b3SWarner Losh20000916: 699be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 700be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 701be3885b3SWarner Losh same time as your kernel. 702be3885b3SWarner Losh 70376ec9675SWarner Losh20000914: 70476ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 70576ec9675SWarner Losh include the device will cause suspended laptops losing time 70676ec9675SWarner Losh when they resume. Include 70776ec9675SWarner Losh device pmtimer 70876ec9675SWarner Losh in your config file and 70901b9a434SWarner Losh hint.pmtimer.0.at="isa" 71076ec9675SWarner Losh to your /boot/device.hints file. 71176ec9675SWarner Losh 712f4865386SMark Murray20000911: 713f4865386SMark Murray The random device has been turned into a (pseudo-)device, 714f4865386SMark Murray rather than an option. The supplied kernel config files have 715f4865386SMark Murray been updated. You will need to do something similar in your 716f4865386SMark Murray own kernel config file. 717f4865386SMark Murray Remove: 718f4865386SMark Murray options RANDOMDEV 719f4865386SMark Murray Add: 720f4865386SMark Murray device random 721f4865386SMark Murray If you prefer to load the loadable module, you need to do 722f4865386SMark Murray nothing. 723f4865386SMark Murray 724d594498fSWarner Losh20000909: 725d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 726d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 727d594498fSWarner Losh reflect this if you load this module at boot time. 728d594498fSWarner Losh The line should read: 729d594498fSWarner Losh random_load="YES" 730d594498fSWarner Losh 7310deb7ddcSWarner Losh20000907: 7320deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 73316eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 73416eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 73516eb772dSWarner Losh sure you don't have model loading problems which might at 73616eb772dSWarner Losh first blush appear related to SMP. 73752bf24e7SWarner Losh 7385a01880bSWarner Losh20000906: 7395a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 7405a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 7415a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 7425a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 7435a01880bSWarner Losh don't have one, and you have host.conf. 7445a01880bSWarner Losh 7452b41163cSWarner Losh20000905: 74638d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 74738d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 74838d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 74938d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 75038d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 75138d6ecd2SWarner Losh 75238d6ecd2SWarner Losh20000905: 7538aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 7548aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 7558aab4bc7SWarner Losh is /boot/kernel. 7568aab4bc7SWarner Losh 7578aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 75838d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 75938d6ecd2SWarner Losh installkernel/installworld dance. 7602b41163cSWarner Losh 761d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 762d594498fSWarner Losh before booting the new kernel, since kldload will find stale 763d594498fSWarner Losh modules in that directory instead of finding them in the correct 764d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 765d594498fSWarner Losh is that the linux module crashes your machine after the update. 766d594498fSWarner Losh 767d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 768d594498fSWarner Losh mv /modules.old /boot/kernel.old 769d594498fSWarner Losh chflags noschg /kernel.old 770d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 771d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 772d594498fSWarner Losh fi 773d594498fSWarner Losh 774c22a309cSWarner Losh20000904: 775c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 776c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 777c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 778c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 779c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 780c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 781c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 782c22a309cSWarner Losh is not likely to be generated. 783c22a309cSWarner Losh 784fdb9f54dSWarner Losh20000825: 785fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 7869c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 7879c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 7889c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 7899c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 7909c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 7919c1a7444SWarner Losh messages will appear after the boot loader tries to start the 7929c1a7444SWarner Losh kernel. 7939c1a7444SWarner Losh 7949c1a7444SWarner Losh20000821: 7959c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 7969c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 7979c1a7444SWarner Losh /boot/loader.conf. 798fdb9f54dSWarner Losh 7998f250aa7SWarner Losh20000812: 8005da0d091SWarner Losh suidperl is now always built and installed on the system, but 8015da0d091SWarner Losh with permissions of 511. If you have applications that use 8025da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 8035da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 8045da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 8055da0d091SWarner Losh will fix this until the next build. 8065da0d091SWarner Losh 8075da0d091SWarner Losh20000812: 8088f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 8098f250aa7SWarner Losh visible changes that may immediately affect your configuration 8108f250aa7SWarner Losh include: 8118f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 8128f250aa7SWarner Losh - newaliases limited to root and trusted users 8138f250aa7SWarner Losh - MSA port (587) turned on by default 8148f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 8158f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 8168f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 8178f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 8188f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 8198f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 8208f250aa7SWarner Losh 82171c38472SWarner Losh20000810: 82271c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 82371c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 82471c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 82571c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 82671c38472SWarner Losh specific use for it. 82771c38472SWarner Losh 82871c38472SWarner Losh20000729: 82971c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 83071c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 83171c38472SWarner Losh /etc/rc.conf if they want to have the same setup 83271c38472SWarner Losh afterwards (unless the variables already are set, of course): 83371c38472SWarner Losh # Enable network daemons for user convenience. 83471c38472SWarner Losh inetd_enable="YES" 83571c38472SWarner Losh portmap_enable="YES" 83671c38472SWarner Losh sendmail_enable="YES" 83771c38472SWarner Losh 83871c38472SWarner Losh20000728: 83971c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 84071c38472SWarner Losh will need to change that to nullfs_load="YES". 84171c38472SWarner Losh 8421dece4a9SWarner Losh20000728: 8431dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 8441dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 8451dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 8461dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 8471dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 8481dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 8491dece4a9SWarner Losh to /MYKERNEL. 8501dece4a9SWarner Losh 851409e887cSWarner Losh20000711: 852409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 853409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 854409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 855409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 856409e887cSWarner Losh for details on potential problems that you might have and how 857409e887cSWarner Losh to get around them. 858409e887cSWarner Losh 859409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 860409e887cSWarner Losh clauses above, you needn't worry. 861409e887cSWarner Losh 862409e887cSWarner Losh20000711: 863409e887cSWarner Losh /etc/security has been updated to print the inode number of 864409e887cSWarner Losh setuid programs that have changed. You will see a large spike 865409e887cSWarner Losh in the number of changed programs the first time when you run 866409e887cSWarner Losh mergemaster to get a new /etc/security. 867409e887cSWarner Losh 868673d13f2SWarner Losh20000710: 869673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 870673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 871673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 872673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 873673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 874673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 875673d13f2SWarner Losh errors. (see below, 20000624). 876673d13f2SWarner Losh 877bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 8781dece4a9SWarner Losh 879673d13f2SWarner Losh20000709: 880c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 881c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 882c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 883673d13f2SWarner Losh ln -s aj /etc/malloc.conf 884673d13f2SWarner Losh 885e98e26cdSWarner Losh20000706: 886e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 887e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 888e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 889f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 890e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 8912c021c6cSMark Ovens interim if needed. 892e98e26cdSWarner Losh 893e98e26cdSWarner Losh20000705: 894e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 895e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 896e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 897e98e26cdSWarner Losh details. 898e98e26cdSWarner Losh 899c373950eSWarner Losh20000704: 9002f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 9012f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 9022f961bc8SWarner Losh 9032f961bc8SWarner Losh20000704: 904c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 905c373950eSWarner Losh or stop. This may cause some harmless warnings from older 906c373950eSWarner Losh rc.d scripts that haven't been updated. 907c373950eSWarner Losh 90827dc3a2bSWarner Losh20000630: 90927dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 91027dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 91127dc3a2bSWarner Losh which should be reported to des@freebsd.org. 91227dc3a2bSWarner Losh 913b8c215acSWarner Losh20000625: 914b8c215acSWarner Losh From approximately this date forward, one must have the crypto 91527dc3a2bSWarner Losh system installed in order to build the system and kernel. 91627dc3a2bSWarner Losh While not technically strictly true, one should treat it as 91727dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 91827dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 91927dc3a2bSWarner Losh were required. You should check with the latest collections 92027dc3a2bSWarner Losh to make sure that these haven't changed. 921b8c215acSWarner Losh 9227b990719SWarner Losh20000624: 9237b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 9247b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 9257b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 9261a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 9277b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 9287b990719SWarner Losh openssh and openssl should not be used to generate keys from this 9297b990719SWarner Losh date to the completion of the work. 9307b990719SWarner Losh 93127dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 93227dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 93327dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 93427dc3a2bSWarner Losh recreate the random and urandom devices. 93527dc3a2bSWarner Losh 93681e54c50SWarner Losh20000622: 93781e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 93881e54c50SWarner Losh BSD license. You may need to remove your symbolic links 93981e54c50SWarner Losh that used to be required when updating. 94081e54c50SWarner Losh 94139943833SWarner Losh20000621: 9422c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 9432a2f33fbSDaniel Baker the config file update procedure. 9442a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 945c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 94659df1173SDavid E. O'Brien isn't buildable. However, you can generate a LINT file: 94759df1173SDavid E. O'Brien cd /sys/<ARCH>/conf && make LINT 94839943833SWarner Losh 949290f9ad8SWarner Losh20000620: 950290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 951290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 952290f9ad8SWarner Losh that workaround will no longer be required. 953290f9ad8SWarner Losh 95490fb6346SWarner Losh20000615: 95590fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 95690fb6346SWarner Losh ad driver. If you haven't done so already, you must update 95790fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 95890fb6346SWarner Losh devices. 95990fb6346SWarner Losh 960f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 961f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 962f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 963f75f65bbSWarner Losh may work). 964f75f65bbSWarner Losh 965ba26da8eSWarner Losh20000612: 966ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 967290f9ad8SWarner Losh on the topic before even thinking about updating. You will 968c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 969290f9ad8SWarner Losh to your config file to compile them in statically. The format 970f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 971f54a3542SWarner Losh NEWCARD for examples of the new format. 972290f9ad8SWarner Losh 9739698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 9749698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 9759698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 9769698f2c0SWarner Losh in it. 977bbcc5149SWarner Losh 978d65850ebSWarner Losh20000522: 979ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 980d65850ebSWarner Losh building a kernel after this point is advised that they need 981d65850ebSWarner Losh to rebuild their binutils (or better yet do a 982d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 983d65850ebSWarner Losh 984d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 985d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 986d9583a00SWarner Losh is recommended that you don't set this option until the problem 987d9583a00SWarner Losh is resolved. 988d9583a00SWarner Losh 9898039cedeSWarner Losh20000513: 9908039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 9918039cedeSWarner Losh 992d65850ebSWarner Losh20000510: 9938039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 9948039cedeSWarner Losh This will require some care in updating alphas. A new libstand 9958039cedeSWarner Losh is requires for the boot blocks to build properly. 9968039cedeSWarner Losh 9978039cedeSWarner Losh20000503: 9988039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 9998039cedeSWarner Losh is now available. 10008039cedeSWarner Losh 1001d65850ebSWarner Losh20000502: 1002d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 1003d65850ebSWarner Losh connected to the kernel building instead. 1004d65850ebSWarner Losh 1005be149406SNik Clayton20000427: 10068039cedeSWarner Losh You may need to build gperf 10078039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 10088039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 10098039cedeSWarner Losh an option only in -current. 10108039cedeSWarner Losh 10112b8dd5f4SWarner Losh20000417: 10122b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1013f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 10142b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 10152b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 10162c021c6cSMark Ovens before you reboot, you'll need to issue: 10172b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 10182b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 10192b8dd5f4SWarner Losh 10208d9f1945SWarner Losh20000320: 10212b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 10222b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 10232b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1024ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 10252b8dd5f4SWarner Losh to the start of /etc/rc.conf. 10268d9f1945SWarner Losh 1027f8ab1dd6SWarner Losh20000319: 1028f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 1029f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1030f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1031f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 1032f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 1033f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 1034f8ab1dd6SWarner Losh 103519cada77SWarner Losh20000318: 1036f699bbbbSMark Ovens We've entered the traditional post release dumping party. 103719cada77SWarner Losh Large kernel changes are being committed and are in the 103819cada77SWarner Losh works. It is important to keep the systems' klds and kernel 103919cada77SWarner Losh in sync as kernel interfaces and structures are changing. 104019cada77SWarner Losh Before reporting kernel panics, make sure that all modules 104119cada77SWarner Losh that you are loading are up to date. 1042ba228352SWarner Losh 104319cada77SWarner Losh20000315: 10446d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 10456d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 10466d23c382SWarner Losh will do the trick. This isn't critical until you remove your 10476d23c382SWarner Losh wd device entries in /dev, at which point your system will not 10486d23c382SWarner Losh boot. 10496d23c382SWarner Losh 10506d23c382SWarner Losh20000315: 105119cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 105219cada77SWarner Losh to upgrade to 4.0 from 3.x. 105357199806SWarner Losh 1054dc0dbf5cSWarner LoshCOMMON ITEMS: 1055dc0dbf5cSWarner Losh 1056a24eff53SWarner Losh General Notes 1057a24eff53SWarner Losh ------------- 1058a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 1059a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 1060a24eff53SWarner Losh installworld. This is especially true when upgrading between 1061a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 1062a24eff53SWarner Losh or several minor releases, or when several months have passed 1063a24eff53SWarner Losh on the -current branch). 1064a24eff53SWarner Losh 10655780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 10665780f3baSWarner Losh poisoning. This can happen because the make utility reads its 10675780f3baSWarner Losh environment when searching for values for global variables. 10685780f3baSWarner Losh To run your build attempts in an "environmental clean room", 10695780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 10705780f3baSWarner Losh page for more details. 10715780f3baSWarner Losh 1072dc0dbf5cSWarner Losh To build a kernel 1073dc0dbf5cSWarner Losh ----------------- 1074ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 1075f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 1076ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 10771e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 10781e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 1079dc0dbf5cSWarner Losh 1080ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 1081ba01eb20SWarner Losh -------------------------------------------------------------- 1082ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 108347d0d01fSWarner Losh config KERNEL_NAME_HERE 1084ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 1085ba01eb20SWarner Losh make depend 1086ba01eb20SWarner Losh make 1087ba01eb20SWarner Losh make install 1088ba01eb20SWarner Losh 1089ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 1090ba01eb20SWarner Losh 1091ba01eb20SWarner Losh To rebuild everything and install it on the current system. 1092ba01eb20SWarner Losh ----------------------------------------------------------- 109363cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 109463cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 109563cb445eSWarner Losh 1096f643de42SWarner Losh <make sure you have good level 0 dumps> 109763cb445eSWarner Losh <maybe fix /etc/fstab> [7] 109863cb445eSWarner Losh make buildworld 109963cb445eSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 110063cb445eSWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 110163cb445eSWarner Losh [1] 110263cb445eSWarner Losh <reboot in single user> [3] 110363cb445eSWarner Losh mergemaster -p [5] 110463cb445eSWarner Losh make installworld 110563cb445eSWarner Losh mergemaster [4] 110663cb445eSWarner Losh <reboot> 110763cb445eSWarner Losh 1108759f0aefSWarner Losh 1109f27b1fceSJoseph Koshy To cross-install current onto a separate partition 1110f27b1fceSJoseph Koshy -------------------------------------------------- 1111f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 1112f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 1113f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 1114f27b1fceSJoseph Koshy # size. 1115f27b1fceSJoseph Koshy 1116f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 1117f27b1fceSJoseph Koshy <boot into -stable> 1118f27b1fceSJoseph Koshy make buildworld 1119f27b1fceSJoseph Koshy <maybe newfs current's root partition> 1120f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 1121f27b1fceSJoseph Koshy make installworld DESTDIR=${CURRENT_ROOT} 1122f27b1fceSJoseph Koshy make buildkernel KERNCONF=YOUR_KERNEL_HERE 1123f27b1fceSJoseph Koshy cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1124f27b1fceSJoseph Koshy ${CURRENT_ROOT}/boot/device.hints # as needed 1125f27b1fceSJoseph Koshy make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1126f27b1fceSJoseph Koshy cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1127f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1128f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1129f27b1fceSJoseph Koshy <reboot into current> 1130f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 1131f27b1fceSJoseph Koshy <maybe install compatibility libraries from /usr/src/lib/compat> 1132f27b1fceSJoseph Koshy <reboot> 1133f27b1fceSJoseph Koshy 1134f27b1fceSJoseph Koshy 1135f27b1fceSJoseph Koshy To upgrade in-place from 4.x-stable to current 1136f27b1fceSJoseph Koshy ---------------------------------------------- 11375c195f59SWarner Losh # 5.x uses more space than 4.x. Also, the location of kernel 11385c195f59SWarner Losh # modules has changed. If you are installing 5.0 onto a 4.x 11395c195f59SWarner Losh # system, you'll need about 30MB of free disk space on your / 11405c195f59SWarner Losh # partition. If you have less than this, you may encounter difficult 1141ca22e652SJens Schweikhardt # to back out of problems with this procedure. If /tmp is on 1142f643de42SWarner Losh # the / partition, you may want to completely remove all its content 1143f643de42SWarner Losh # before upgrading, as this can be a common source of shortage of 1144f643de42SWarner Losh # space on /. 1145f643de42SWarner Losh 1146f643de42SWarner Losh <make sure you have good level 0 dumps> 1147fc8c157fSWarner Losh <maybe fix /etc/fstab> [7] 114821c075eaSWarner Losh make buildworld [9] 1149c74fe6afSWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1150d2125802SWarner Losh cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1151be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 1152fc8c157fSWarner Losh cd src/sys/boot ; make install [6] 1153fc8c157fSWarner Losh [1] 1154fc8c157fSWarner Losh <reboot in single user> [3] 1155835284beSWarner Losh mergemaster -p [5] 1156f8a4c901SWarner Losh rm -rf /usr/include/g++ 1157ba26da8eSWarner Losh make installworld 1158a6cd4f9dSWarner Losh mergemaster [4] 1159ba26da8eSWarner Losh <reboot> 1160ba26da8eSWarner Losh 1161fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 1162fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 1163fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 1164fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 1165fdb9f54dSWarner Losh the UPDATING entries. 1166ba26da8eSWarner Losh 11671dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 11681dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 11691dece4a9SWarner Losh your sources that you have read and understood all the recent 11701dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 11711dece4a9SWarner Losh much fewer pitfalls. 11721dece4a9SWarner Losh 1173134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1174134d2e86SWarner Losh should disable them at this point so they don't crash your 1175134d2e86SWarner Losh system on reboot. 1176134d2e86SWarner Losh 11779c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 11789c1a7444SWarner Losh your own device.hints to reflect your unique hardware 11799c1a7444SWarner Losh configuration. 11809c1a7444SWarner Losh 1181ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1182ee6e1fc3SWarner Losh fsck -p 1183ee6e1fc3SWarner Losh mount -u / 1184ee6e1fc3SWarner Losh mount -a 1185ee6e1fc3SWarner Losh cd /usr/src 118647d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1187f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1188f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1189b705ae10SWarner Losh For the 4.x -> 5.0 upgrade, you will also see many messages about 1190b705ae10SWarner Losh needing to recompile your userland. These are harmless and can 1191b705ae10SWarner Losh be ignored while you proceed to the next step. 1192ee6e1fc3SWarner Losh 1193a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1194a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1195a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1196a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1197a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1198a6cd4f9dSWarner Losh for potential gotchas. 1199a6cd4f9dSWarner Losh 1200835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1201835284beSWarner Losh you may need to do this if you get unknown user in the following 1202835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1203835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1204835284beSWarner Losh install) after the buildworld before this step if you last updated 1205835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1206835284beSWarner Losh 1207bd79cf40SWarner Losh [6] 4.x boot loader can be used to boot a 5.x system, however 1208bd79cf40SWarner Losh it is difficult to do that at best. If you wish to try, then 1209bd79cf40SWarner Losh you should interrupt the boot and at the ok prompt type: 1210bd79cf40SWarner Losh ok unload 1211bd79cf40SWarner Losh ok boot /boot/kernel/kernel 1212bd79cf40SWarner Losh If this fails to work, you must install a new boot loader as 1213bd79cf40SWarner Losh described here. 1214fc8c157fSWarner Losh 1215fc8c157fSWarner Losh [7] Before you upgrade, please make sure that you are not using 1216fc8c157fSWarner Losh compatibility slices. These are device names of the form, on i386 1217fc8c157fSWarner Losh and other architectures that use MBR slicing, /dev/ad0a without the 1218fc8c157fSWarner Losh actual slice name. Chances are excellent that these will break. 1219fc8c157fSWarner Losh You generally must update these entries to use the post FreeBSD 1220fc8c157fSWarner Losh 2.x form of /dev/ad0s1a. 1221fc8c157fSWarner Losh 1222c74fe6afSWarner Losh [8] In order to have a kernel that can run the 4.x binaries 1223c74fe6afSWarner Losh needed to do an installworld, you must include the COMPAT_FREEBSD4 1224c74fe6afSWarner Losh option in your kernel. Failure to do so may leave you with a system 1225c74fe6afSWarner Losh that is hard to boot to recover. 1226c74fe6afSWarner Losh 122721c075eaSWarner Losh [9] When checking out sources, you must include the -P flag to have 122821c075eaSWarner Losh cvs prune empty directories. 1229dc0dbf5cSWarner LoshFORMAT: 1230dc0dbf5cSWarner Losh 1231f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 12321fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1233f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1234f8ab1dd6SWarner Loshprevious releases if your system is older than this. 12351fc1a0dcSWarner Losh 1236e72fd46aSWarner LoshCopyright information: 1237e72fd46aSWarner Losh 12389698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1239e72fd46aSWarner Losh 1240772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1241772730c7SWarner Loshmodification, in full or in part, in any form or format of this 12429698f2c0SWarner Loshdocument are permitted without further permission from the author. 1243e72fd46aSWarner Losh 1244e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1245e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1246e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1247e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1248e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1249e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1250e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1251e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1252e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1253e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1254e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1255e72fd46aSWarner Losh 1256e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1257e72fd46aSWarner Loshauthor a beer. 1258e72fd46aSWarner Losh 125922306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1260772730c7SWarner Loshthis document. 1261772730c7SWarner Losh 126297d92980SPeter Wemm$FreeBSD$ 1263