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 2069f7bcf3SWarner Losh In addition, IDE write caching is currently disabled by default 2169f7bcf3SWarner Losh due to on-going concerns about disk write order and file system 2269f7bcf3SWarner Losh integrity. Re-enabling write caching can substantially improve 2369f7bcf3SWarner Losh performance. 2469f7bcf3SWarner Losh 25c2248fa2SJens Schweikhardt20020827: 26c2248fa2SJens Schweikhardt Our /etc/termcap now has all the entries from the XFree86 xterm 27c2248fa2SJens Schweikhardt almost unchanged. This means xterm now supports color by default. 28c2248fa2SJens Schweikhardt If you used TERM=xterm-color in the past you now should use 29c2248fa2SJens Schweikhardt TERM=xterm. (xterm-color will lead to benign warnings). 30c2248fa2SJens Schweikhardt 310d533e43SRuslan Ermilov20020815: 320d533e43SRuslan Ermilov A "bug" in gcc(1) that was hiding warning in system headers was 330d533e43SRuslan Ermilov fixed. It's probably time to add -DNO_WERROR to your make line 340d533e43SRuslan Ermilov again. 350d533e43SRuslan Ermilov 3633c1de7dSRuslan Ermilov20020729: 3733c1de7dSRuslan Ermilov COPY is being deprecated. The 20010530 change was reverted, as 3833c1de7dSRuslan Ermilov it causes far more pain than was expected, and to always compare 3933c1de7dSRuslan Ermilov before installing, please use INSTALL="install -C" again. The 4033c1de7dSRuslan Ermilov -C option is now silently ignored when used with the -d option. 4133c1de7dSRuslan Ermilov 422b877facSJulian Elischer20020702: 432b877facSJulian Elischer Problems with libc_r clients like KDE and GNOME have been resolved. 442b877facSJulian Elischer There are still some minor problems with some signals but the 452b877facSJulian Elischer system is stable enough for general use again. SMP is less so than UP 462b877facSJulian Elischer but each can successfully complete multiple buildworlds. 472b877facSJulian Elischer Libkvm needs to be recompiled due to KSE. 482b877facSJulian Elischer 4906596d37SWarner Losh20020701: 5006596d37SWarner Losh Now would be a bad time to upgrade. Something in or near the 5106596d37SWarner Losh KSE commit totally broke programs using libc_r like KDE and 5206596d37SWarner Losh GNOME. 5306596d37SWarner Losh 5495ba4330SJacques Vidrine20020511: 5595ba4330SJacques Vidrine The k5su utility installed as part of Kerberos 5 is no longer 5695ba4330SJacques Vidrine installed with the set-user-ID bit set by default. Add 5795ba4330SJacques Vidrine ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 5895ba4330SJacques Vidrine with the set-user-ID bit set. 5995ba4330SJacques Vidrine 60a81da3c9SDavid E. O'Brien20020510: 61f50caf6fSDavid E. O'Brien Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 62f50caf6fSDavid E. O'Brien Unfortunately our native GDB (at version 4.18) does not understand 634b683fb2SRobert Watson the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 64f50caf6fSDavid E. O'Brien generated debugging information for our native GDB. 65f50caf6fSDavid E. O'Brien 66f50caf6fSDavid E. O'Brien20020510: 67a81da3c9SDavid E. O'Brien Due to the way CVS works, it may not properly update src/contrib/gcc 68a81da3c9SDavid E. O'Brien to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 69a81da3c9SDavid E. O'Brien and then do a cvs update. 70a81da3c9SDavid E. O'Brien 71528a0ef5SJacques Vidrine20020421: 72528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 73528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 74528a0ef5SJacques Vidrine 7585aa5a2eSGregory Neil Shapiro20020404: 7685aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 7785aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 7885aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 7985aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 8085aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 8185aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 8285aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 8385aa5a2eSGregory Neil Shapiro 848f1e4358SRuslan Ermilov20020403: 858f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 868f1e4358SRuslan Ermilov 872292c02eSWarner Losh20020315: 882292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 892292c02eSWarner Losh 9069f7bcf3SWarner Losh20020225: 9169f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 9269f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 9369f7bcf3SWarner Losh 948f35c493SWarner Losh20020217: 958f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 968f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 978f35c493SWarner Losh command line mail submission has changed. Be sure to run 988f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 998f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 1008f35c493SWarner Losh 101835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 102835284beSWarner Losh required in order for sendmail to run as a set-group-ID 103835284beSWarner Losh binary. A 'make installworld' will use the new user and group 104835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 105835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 106835284beSWarner Losh and group must be merged from src/etc/group and 107835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 108835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 109835284beSWarner Losh mergemaster before this will work if you are updating from a 110835284beSWarner Losh very old version of current. The updating recipe has changed 111835284beSWarner Losh as of this date. 112835284beSWarner Losh 113fa9401c1SWarner Losh20020112: 114fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 115fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 116fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 117fa9401c1SWarner Losh you have local modifications, you can use 118fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 119fa9401c1SWarner Losh /etc/pam.d. 120fa9401c1SWarner Losh 121fa9401c1SWarner Losh Please see the following url for more details: 122fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 12347d0d01fSWarner Losh20011229: 12447d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 12547d0d01fSWarner Losh networkfs_types, please note that it has changed 12647d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 12747d0d01fSWarner Losh 128514318a8SWarner Losh20011220: 129514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 130514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 131514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 132514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 133514318a8SWarner Losh version have now been merged back into the base system's 134514318a8SWarner Losh version now. The only user-visible change resulting from this 135514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 136514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 137514318a8SWarner Losh as well. (There has never been rc file support for 138514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 139514318a8SWarner Losh reverted by the time the changes are MFCed.) 140514318a8SWarner Losh 141514318a8SWarner Losh20011215: 142514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 143514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 144514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 145514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 146514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 147514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 148514318a8SWarner Losh will need to be customized then for `odd' densities using 149514318a8SWarner Losh fdcontrol(8). 150514318a8SWarner Losh 1512d22e2bfSWarner Losh20011209: 1522d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 1532d22e2bfSWarner Losh and truss(1) now works again. 1542d22e2bfSWarner Losh 1559e0428e2SWarner Losh20011207: 1569e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 1579e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 1589e0428e2SWarner Losh see 1599e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 1609e0428e2SWarner Losh for details. 1619e0428e2SWarner Losh 1629bab8c59SWarner Losh20011204: 1639bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 1649bab8c59SWarner Losh kernel and burncd to be in sync. 1659bab8c59SWarner Losh 166e57d8b01SWarner Losh20011203: 167e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 168e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 169e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 170e57d8b01SWarner Losh not there already. 171e57d8b01SWarner Losh 172e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 173e57d8b01SWarner Losh until the issue has been resolved. 174e57d8b01SWarner Losh 175b001d36fSJacques Vidrine20011202: 176b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 177b001d36fSJacques Vidrine patched. 178b001d36fSJacques Vidrine 1794b676ec1SWarner Losh20011126: 1804b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 1815ebbf43eSWarner Losh after this date. You need to do this only once. 1824b676ec1SWarner Losh 183d961e462SWarner Losh20011103: 184d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 185d961e462SWarner Losh edges may be left, but for the most part things should be 1864b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 187d961e462SWarner Losh 188d961e462SWarner Losh20011030: 189d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 190d961e462SWarner Losh choppy waves in the upgrade process. 191d961e462SWarner Losh 1921fe003b6SWarner Losh20011030: 193a4b6fda0SWarner Losh The asr driver problem has been resolved. 1941fe003b6SWarner Losh 1951fe003b6SWarner Losh20011027: 1961fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 1971fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 1981fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 1991fe003b6SWarner Losh try to use from this date forward. 2001fe003b6SWarner Losh 2011fe003b6SWarner Losh20011025: 2021fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 2031fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 2041fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 2051fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 2061fe003b6SWarner Losh TARGET_ARCH=i386. 2071fe003b6SWarner Losh 208d05f9643SWarner Losh20011001: 209d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 210d05f9643SWarner Losh You must recompile both the kernel and userland applications 211d05f9643SWarner Losh at the same time. 212d05f9643SWarner Losh 21358970f85SWarner Losh20010929: 21458970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 21558970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 21658970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 21758970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 21858970f85SWarner Losh (eg, you can build pc98 on a i386 machine and vice versa). 21958970f85SWarner Losh 22058970f85SWarner Losh20010927: 22158970f85SWarner Losh Some weird problems result from using ACPI on some machines. 22258970f85SWarner Losh To disable ACPI you can add 223378f4486SAlfred Perlstein hint.acpi.0.disable="1" 22458970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 22558970f85SWarner Losh loader "ok" prompt). 22658970f85SWarner Losh 22758970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 22858970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 22958970f85SWarner Losh file and not list acpi in that list. 230378f4486SAlfred Perlstein 2315119d237SWarner Losh20010924: 2325119d237SWarner Losh The buildworld has been fixed. You may need to install 2335119d237SWarner Losh the 4.x compatibility libraries for some old binaries 2348b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 2358b039fffSWarner Losh get them installed on every installworld, or execute the 2368b039fffSWarner Losh following to get them installed only once: 2378b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 23858970f85SWarner Losh make all install 2398b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 2405119d237SWarner Losh 2413c293725SWarner Losh20010919: 2423c293725SWarner Losh There's a bug in the world build process. The cross-tools 2433c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 2443c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 245772730c7SWarner Losh workaround is to add 2463c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 2473c293725SWarner Losh before building world when upgrading from 4.x to current. This 2483c293725SWarner Losh can be removed afterwards. 2493c293725SWarner Losh 2503c293725SWarner Losh A proper fix to the buildworld target is needed. 2513c293725SWarner Losh 2523c293725SWarner Losh20010918: 2533c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 2543c293725SWarner Losh NFS may be unstable after this date. 2553c293725SWarner Losh 2563c293725SWarner Losh20010912: 2573c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 2583c293725SWarner Losh the kernel. While a few problems were introduced in the 2593c293725SWarner Losh initial commit, most of the major ones have been found and 2603c293725SWarner Losh corrected. 2613c293725SWarner Losh 2623c293725SWarner Losh20010901: 2633c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 2643c293725SWarner Losh arounds described in the 20010604 entry are now no longer 2653c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 2663c293725SWarner Losh have been rectified around this date. 2673c293725SWarner Losh 26898b17b95SWarner Losh20010823: 26998b17b95SWarner Losh named now runs as user bind and group bind rather than as 27098b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 27198b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 27298b17b95SWarner Losh and that group bind is available in /etc/group. Also make 27398b17b95SWarner Losh sure that user or group bind has read (and not write) 27498b17b95SWarner Losh permission for your name server configuration and that it 27598b17b95SWarner Losh has read and write permission for your slave zone files and 27698b17b95SWarner Losh directory. 27798b17b95SWarner Losh 27898b17b95SWarner Losh If you wish to continue to run named as root (a less secure 27998b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 28098b17b95SWarner Losh 28198b17b95SWarner Losh named_flags= 28298b17b95SWarner Losh 2837b9786edSMark Murray20010709: 2847b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 2857b9786edSMark Murray the ability of the shared library major number to handle. 2867b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 2877b9786edSMark Murray solution is to rebuild those ports. 2887b9786edSMark Murray 2891d28950eSWarner Losh20010628: 2901d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 2911d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 2921d28950eSWarner Losh 293e72fd46aSWarner Losh20010625: 29498b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 29598b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 29698b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 29798b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 29898b17b95SWarner Losh IRQ configuration needs more safety belts. 29916de1a07SWarner Losh 3000d415dffSWarner Losh20010617: 301e72fd46aSWarner Losh Softupdates problems have been corrected. 3020d415dffSWarner Losh 3030d415dffSWarner Losh20010614: 3040d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 3050d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 3060d415dffSWarner Losh kernel building methods. 3070d415dffSWarner Losh 3088b9959adSWarner Losh20010613: 3098b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 3108b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 311e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 312e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 3138b9959adSWarner Losh 314e72fd46aSWarner Losh20010613: 3158b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 316e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 317e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 3188b9959adSWarner Losh 3190d415dffSWarner Losh20010612: 3200d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 3210d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 3220d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 3230d415dffSWarner Losh work around this issue, please use only one or the other mechanism 3240d415dffSWarner Losh until this bug is fixed. 3250d415dffSWarner Losh 326e72fd46aSWarner Losh Please note that a feature of config is that if you have config 327e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 328e72fd46aSWarner Losh hints.c file, wheather you want it to or not. 329e72fd46aSWarner Losh 3300d415dffSWarner Losh20010610: 3310d415dffSWarner Losh Locale names have changed to match other systems better. 3320d415dffSWarner Losh 3336ccdb5e4SWarner Losh20010604: 3346ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 3356ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 3366ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 3373590182eSWarner Losh Interrupt storms look a lot like a hang. 3383590182eSWarner Losh 3393590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 3403590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 3413590182eSWarner Losh it is). 3423590182eSWarner Losh 3433590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 3443590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 3453590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 3463590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 3476ccdb5e4SWarner Losh 3480bc62786SWarner Losh20010530: 3490bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 3500bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 3510bc62786SWarner Losh a limited time. If you see 3520bc62786SWarner Losh 3530bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 3540bc62786SWarner Losh 3550bc62786SWarner Losh in your makeworld, then you need to migrate towards using 3560bc62786SWarner Losh COPY=-C. 3570bc62786SWarner Losh 35868a38c6cSWarner Losh20010525: 359b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 360c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 361c4f4a728SWarner Losh definitely is in bad shape. 36268a38c6cSWarner Losh 363ed0f29caSWarner Losh20010521: 364f10d3145SWarner Losh Minor repo damange has happened. This may cause problems 365ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 366ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 367ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 368ed0f29caSWarner Losh is 369ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 370ed0f29caSWarner Losh 37180c16af9SWarner Losh20010520: 37268a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 37380c16af9SWarner Losh 37480c16af9SWarner Losh20010519: 37580c16af9SWarner Losh pccard has had much reorganizational work done to it over 37680c16af9SWarner Losh the past few days. Everything should still work, but if 37780c16af9SWarner Losh not, please contact imp@freebsd.org. 37880c16af9SWarner Losh 379a45f2d05SWarner Losh20010517: 380a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 381a45f2d05SWarner Losh userland at the same time. 382a45f2d05SWarner Losh 383a45f2d05SWarner Losh20010517: 384a45f2d05SWarner Losh New ncurses imported. 385a45f2d05SWarner Losh 3862988afcaSWarner Losh20010512: 3872988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 3882988afcaSWarner Losh will be the only way to go starting July 1. 3892988afcaSWarner Losh 3901a33dba7SWarner Losh20010504: 3911a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 3921a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 3931a33dba7SWarner Losh 39409946a51SWarner Losh20010502: 39509946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 39609946a51SWarner Losh 39709946a51SWarner Losh20010501: 39809946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 39909946a51SWarner Losh 40009946a51SWarner Losh20010430: 401a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 40209946a51SWarner Losh go back in the water. 40309946a51SWarner Losh 40409946a51SWarner Losh20010429: 40509946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 40609946a51SWarner Losh this date, but before the correction date. 40709946a51SWarner Losh 40891dd3b53SWarner Losh20010423: 40991dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 41091dd3b53SWarner Losh 41191dd3b53SWarner Losh20010411: 41291dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 41391dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 41491dd3b53SWarner Losh Update only if you understand that you must not use the old 41591dd3b53SWarner Losh fsck with the new kernel ever. 41691dd3b53SWarner Losh 417933b3269SWarner Losh20010330: 418933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 419c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 420933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 421933b3269SWarner Losh 422933b3269SWarner Losh20010319: 423933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 424933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 425933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 426f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 42709946a51SWarner Losh 42809946a51SWarner Losh20010315: 42909946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 43009946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 43109946a51SWarner Losh been replaced by tunables. See ata.4 for details. 432933b3269SWarner Losh 433933b3269SWarner Losh20010312: 434933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 435933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 436933b3269SWarner Losh 437933b3269SWarner Losh20010312: 438933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 439933b3269SWarner Losh instead of ad-hoc. 440933b3269SWarner Losh 441933b3269SWarner Losh20010310: 442f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 443933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 444933b3269SWarner Losh ssh might not work if you don't. 445933b3269SWarner Losh 44662353691SWarner Losh20010303: 44762353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 44862353691SWarner Losh which means that you must include the miibus in your kernel if 44962353691SWarner Losh you use the ed driver. 45062353691SWarner Losh 451d325cf65SWarner Losh20010220: 452d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 453d325cf65SWarner Losh safe to go back into the water. 454d325cf65SWarner Losh 455024daae6SWarner Losh20010211: 456024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 457024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 458024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 459024daae6SWarner Losh that before upgrading would be a good time to do a level 0 460024daae6SWarner Losh dump of your system. No, really, I mean it this time. 461024daae6SWarner Losh 462024daae6SWarner Losh To get to the new system, you'll need to use the following 463024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 464024daae6SWarner Losh don't have to move this to the updating section. 465024daae6SWarner Losh 466024daae6SWarner Losh To get around the installworld problem, do: 467024daae6SWarner Losh # cd /usr/src/usr.bin/sed 468024daae6SWarner Losh # make install 469024daae6SWarner Losh # cd /usr/src 470024daae6SWarner Losh # make installworld 471024daae6SWarner Losh If that doesn't work, then try: 472024daae6SWarner Losh # make -k installworld 473024daae6SWarner Losh # make installworld 474024daae6SWarner Losh 475024daae6SWarner Losh20010207: 476024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 477024daae6SWarner Losh do not include devfs in your kernel as problems result. 478024daae6SWarner Losh 479024daae6SWarner Losh20010205: 4807595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 481024daae6SWarner Losh Remove them from your config. 482024daae6SWarner Losh 4831e159248SWarner Losh20010122: 4841e159248SWarner Losh ****************************** WARNING ****************************** 4851e159248SWarner Losh buildkernel has been changed slightly 4861e159248SWarner Losh ****************************** WARNING ****************************** 4871e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 4881e159248SWarner Losh should update your scripts and make.conf accordingly. 4891e159248SWarner Losh 4901e159248SWarner Losh20010119: 4911e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 4921e159248SWarner Losh This requires a new config to build correctly. 4931e159248SWarner Losh 494aac7dfeaSWarner Losh20010116: 495aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 496aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 497aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 498aac7dfeaSWarner Losh 499aac7dfeaSWarner Losh20010110: 500aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 501aac7dfeaSWarner Losh 502aac7dfeaSWarner Losh20010102: 503aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 504aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 505aac7dfeaSWarner Losh 50663c90c9eSWarner Losh20010101: 50763c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 50863c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 5095fd2a895SWarner Losh dump while building termcap. You can work around this problem 51063c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 51163c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 51263c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 51363c90c9eSWarner Losh might have been ignored by the -k option. 51463c90c9eSWarner Losh 5155fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 5165fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 5175fd2a895SWarner Losh of this working. 5185fd2a895SWarner Losh 519aac7dfeaSWarner Losh20001228: 520aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 521aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 522aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 523aac7dfeaSWarner Losh 524de2bcc63SWarner Losh20001218: 525de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 526de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 527de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 528de2bcc63SWarner Losh cards will not be recognized without it. 529de2bcc63SWarner Losh 530960773f7SWarner Losh20001205: 531960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 532960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 533960773f7SWarner Losh adding the following in pam.conf: 534960773f7SWarner Losh 535960773f7SWarner Losh sshd auth sufficient pam_skey.so 536960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 537960773f7SWarner Losh sshd session required pam_permit.so 538960773f7SWarner Losh 5390acc635eSWarner Losh20001031: 5400acc635eSWarner Losh cvs updated to 1.11. 5410acc635eSWarner Losh 5420acc635eSWarner Losh20001020: 5430acc635eSWarner Losh The random device needs more entropy, so you need to make sure 5440acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 5450acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 5460acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 5470acc635eSWarner Losh workaround. 5480acc635eSWarner Losh 5490acc635eSWarner Losh20001010: 5500acc635eSWarner Losh ****************************** WARNING ****************************** 5510acc635eSWarner Losh Sendmail has been updated. 5520acc635eSWarner Losh ****************************** WARNING ****************************** 5530acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 5540acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 5550acc635eSWarner Losh is set. 5560acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 5570acc635eSWarner Losh commands. 5580acc635eSWarner Losh o Now using sendmail's version of vacation(1). 5590acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 5600acc635eSWarner Losh in /usr/share/sendmail/cf. 5610acc635eSWarner Losh o sendmail.cw changed to local-host-names 5620acc635eSWarner Losh 5630acc635eSWarner Losh More details can be found at 5640acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 5650acc635eSWarner Losh 5666e98a146SWarner Losh20001009: 5676e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 5686e98a146SWarner Losh your entire ports tree, or you will have problems. 5696e98a146SWarner Losh 5706e98a146SWarner Losh20001006: 571685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 5726e98a146SWarner Losh the installed miniperl. It is recommended that you delete 5736e98a146SWarner Losh /usr/bin/miniperl. 5746e98a146SWarner Losh 575073113a4SWarner Losh20001005: 576073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 577685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 578073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 579073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 580073113a4SWarner Losh tree for anything to work. 581073113a4SWarner Losh 5820acc635eSWarner Losh20000928: 5830acc635eSWarner Losh There was a change in the passwd format. Need more information. 5840acc635eSWarner Losh 585be3885b3SWarner Losh20000916: 586be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 587be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 588be3885b3SWarner Losh same time as your kernel. 589be3885b3SWarner Losh 59076ec9675SWarner Losh20000914: 59176ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 59276ec9675SWarner Losh include the device will cause suspended laptops losing time 59376ec9675SWarner Losh when they resume. Include 59476ec9675SWarner Losh device pmtimer 59576ec9675SWarner Losh in your config file and 59601b9a434SWarner Losh hint.pmtimer.0.at="isa" 59776ec9675SWarner Losh to your /boot/device.hints file. 59876ec9675SWarner Losh 599f4865386SMark Murray20000911: 600f4865386SMark Murray The random device has been turned into a (pseudo-)device, 601f4865386SMark Murray rather than an option. The supplied kernel config files have 602f4865386SMark Murray been updated. You will need to do something similar in your 603f4865386SMark Murray own kernel config file. 604f4865386SMark Murray Remove: 605f4865386SMark Murray options RANDOMDEV 606f4865386SMark Murray Add: 607f4865386SMark Murray device random 608f4865386SMark Murray If you prefer to load the loadable module, you need to do 609f4865386SMark Murray nothing. 610f4865386SMark Murray 611d594498fSWarner Losh20000909: 612d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 613d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 614d594498fSWarner Losh reflect this if you load this module at boot time. 615d594498fSWarner Losh The line should read: 616d594498fSWarner Losh random_load="YES" 617d594498fSWarner Losh 6180deb7ddcSWarner Losh20000907: 6190deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 62016eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 62116eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 62216eb772dSWarner Losh sure you don't have model loading problems which might at 62316eb772dSWarner Losh first blush appear related to SMP. 62452bf24e7SWarner Losh 6255a01880bSWarner Losh20000906: 6265a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 6275a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 6285a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 6295a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 6305a01880bSWarner Losh don't have one, and you have host.conf. 6315a01880bSWarner Losh 6322b41163cSWarner Losh20000905: 63338d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 63438d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 63538d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 63638d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 63738d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 63838d6ecd2SWarner Losh 63938d6ecd2SWarner Losh20000905: 6408aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 6418aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 6428aab4bc7SWarner Losh is /boot/kernel. 6438aab4bc7SWarner Losh 6448aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 64538d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 64638d6ecd2SWarner Losh installkernel/installworld dance. 6472b41163cSWarner Losh 648d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 649d594498fSWarner Losh before booting the new kernel, since kldload will find stale 650d594498fSWarner Losh modules in that directory instead of finding them in the correct 651d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 652d594498fSWarner Losh is that the linux module crashes your machine after the update. 653d594498fSWarner Losh 654d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 655d594498fSWarner Losh mv /modules.old /boot/kernel.old 656d594498fSWarner Losh chflags noschg /kernel.old 657d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 658d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 659d594498fSWarner Losh fi 660d594498fSWarner Losh 661c22a309cSWarner Losh20000904: 662c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 663c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 664c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 665c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 666c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 667c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 668c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 669c22a309cSWarner Losh is not likely to be generated. 670c22a309cSWarner Losh 671fdb9f54dSWarner Losh20000825: 672fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 6739c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 6749c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 6759c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 6769c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 6779c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 6789c1a7444SWarner Losh messages will appear after the boot loader tries to start the 6799c1a7444SWarner Losh kernel. 6809c1a7444SWarner Losh 6819c1a7444SWarner Losh20000821: 6829c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 6839c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 6849c1a7444SWarner Losh /boot/loader.conf. 685fdb9f54dSWarner Losh 6868f250aa7SWarner Losh20000812: 6875da0d091SWarner Losh suidperl is now always built and installed on the system, but 6885da0d091SWarner Losh with permissions of 511. If you have applications that use 6895da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 6905da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 6915da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 6925da0d091SWarner Losh will fix this until the next build. 6935da0d091SWarner Losh 6945da0d091SWarner Losh20000812: 6958f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 6968f250aa7SWarner Losh visible changes that may immediately affect your configuration 6978f250aa7SWarner Losh include: 6988f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 6998f250aa7SWarner Losh - newaliases limited to root and trusted users 7008f250aa7SWarner Losh - MSA port (587) turned on by default 7018f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 7028f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 7038f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 7048f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 7058f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 7068f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 7078f250aa7SWarner Losh 70871c38472SWarner Losh20000810: 70971c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 71071c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 71171c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 71271c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 71371c38472SWarner Losh specific use for it. 71471c38472SWarner Losh 71571c38472SWarner Losh20000729: 71671c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 71771c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 71871c38472SWarner Losh /etc/rc.conf if they want to have the same setup 71971c38472SWarner Losh afterwards (unless the variables already are set, of course): 72071c38472SWarner Losh # Enable network daemons for user convenience. 72171c38472SWarner Losh inetd_enable="YES" 72271c38472SWarner Losh portmap_enable="YES" 72371c38472SWarner Losh sendmail_enable="YES" 72471c38472SWarner Losh 72571c38472SWarner Losh20000728: 72671c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 72771c38472SWarner Losh will need to change that to nullfs_load="YES". 72871c38472SWarner Losh 7291dece4a9SWarner Losh20000728: 7301dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 7311dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 7321dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 7331dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 7341dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 7351dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 7361dece4a9SWarner Losh to /MYKERNEL. 7371dece4a9SWarner Losh 738409e887cSWarner Losh20000711: 739409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 740409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 741409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 742409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 743409e887cSWarner Losh for details on potential problems that you might have and how 744409e887cSWarner Losh to get around them. 745409e887cSWarner Losh 746409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 747409e887cSWarner Losh clauses above, you needn't worry. 748409e887cSWarner Losh 749409e887cSWarner Losh20000711: 750409e887cSWarner Losh /etc/security has been updated to print the inode number of 751409e887cSWarner Losh setuid programs that have changed. You will see a large spike 752409e887cSWarner Losh in the number of changed programs the first time when you run 753409e887cSWarner Losh mergemaster to get a new /etc/security. 754409e887cSWarner Losh 755673d13f2SWarner Losh20000710: 756673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 757673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 758673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 759673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 760673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 761673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 762673d13f2SWarner Losh errors. (see below, 20000624). 763673d13f2SWarner Losh 764bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 7651dece4a9SWarner Losh 766673d13f2SWarner Losh20000709: 767c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 768c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 769c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 770673d13f2SWarner Losh ln -s aj /etc/malloc.conf 771673d13f2SWarner Losh 772e98e26cdSWarner Losh20000706: 773e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 774e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 775e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 776f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 777e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 7782c021c6cSMark Ovens interim if needed. 779e98e26cdSWarner Losh 780e98e26cdSWarner Losh20000705: 781e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 782e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 783e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 784e98e26cdSWarner Losh details. 785e98e26cdSWarner Losh 786c373950eSWarner Losh20000704: 7872f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 7882f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 7892f961bc8SWarner Losh 7902f961bc8SWarner Losh20000704: 791c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 792c373950eSWarner Losh or stop. This may cause some harmless warnings from older 793c373950eSWarner Losh rc.d scripts that haven't been updated. 794c373950eSWarner Losh 79527dc3a2bSWarner Losh20000630: 79627dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 79727dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 79827dc3a2bSWarner Losh which should be reported to des@freebsd.org. 79927dc3a2bSWarner Losh 800b8c215acSWarner Losh20000625: 801b8c215acSWarner Losh From approximately this date forward, one must have the crypto 80227dc3a2bSWarner Losh system installed in order to build the system and kernel. 80327dc3a2bSWarner Losh While not technically strictly true, one should treat it as 80427dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 80527dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 80627dc3a2bSWarner Losh were required. You should check with the latest collections 80727dc3a2bSWarner Losh to make sure that these haven't changed. 808b8c215acSWarner Losh 8097b990719SWarner Losh20000624: 8107b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 8117b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 8127b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 8131a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 8147b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 8157b990719SWarner Losh openssh and openssl should not be used to generate keys from this 8167b990719SWarner Losh date to the completion of the work. 8177b990719SWarner Losh 81827dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 81927dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 82027dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 82127dc3a2bSWarner Losh recreate the random and urandom devices. 82227dc3a2bSWarner Losh 82381e54c50SWarner Losh20000622: 82481e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 82581e54c50SWarner Losh BSD license. You may need to remove your symbolic links 82681e54c50SWarner Losh that used to be required when updating. 82781e54c50SWarner Losh 82839943833SWarner Losh20000621: 8292c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 8302a2f33fbSDaniel Baker the config file update procedure. 8312a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 832c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 833a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 83439943833SWarner Losh 835290f9ad8SWarner Losh20000620: 836290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 837290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 838290f9ad8SWarner Losh that workaround will no longer be required. 839290f9ad8SWarner Losh 84090fb6346SWarner Losh20000615: 84190fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 84290fb6346SWarner Losh ad driver. If you haven't done so already, you must update 84390fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 84490fb6346SWarner Losh devices. 84590fb6346SWarner Losh 846f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 847f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 848f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 849f75f65bbSWarner Losh may work). 850f75f65bbSWarner Losh 851ba26da8eSWarner Losh20000612: 852ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 853290f9ad8SWarner Losh on the topic before even thinking about updating. You will 854c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 855290f9ad8SWarner Losh to your config file to compile them in statically. The format 856f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 857f54a3542SWarner Losh NEWCARD for examples of the new format. 858290f9ad8SWarner Losh 8599698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 8609698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 8619698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 8629698f2c0SWarner Losh in it. 863bbcc5149SWarner Losh 864d65850ebSWarner Losh20000522: 865ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 866d65850ebSWarner Losh building a kernel after this point is advised that they need 867d65850ebSWarner Losh to rebuild their binutils (or better yet do a 868d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 869d65850ebSWarner Losh 870d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 871d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 872d9583a00SWarner Losh is recommended that you don't set this option until the problem 873d9583a00SWarner Losh is resolved. 874d9583a00SWarner Losh 8758039cedeSWarner Losh20000513: 8768039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 8778039cedeSWarner Losh 878d65850ebSWarner Losh20000510: 8798039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 8808039cedeSWarner Losh This will require some care in updating alphas. A new libstand 8818039cedeSWarner Losh is requires for the boot blocks to build properly. 8828039cedeSWarner Losh 8838039cedeSWarner Losh20000503: 8848039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 8858039cedeSWarner Losh is now available. 8868039cedeSWarner Losh 887d65850ebSWarner Losh20000502: 888d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 889d65850ebSWarner Losh connected to the kernel building instead. 890d65850ebSWarner Losh 891be149406SNik Clayton20000427: 8928039cedeSWarner Losh You may need to build gperf 8938039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 8948039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 8958039cedeSWarner Losh an option only in -current. 8968039cedeSWarner Losh 8972b8dd5f4SWarner Losh20000417: 8982b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 899f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 9002b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 9012b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 9022c021c6cSMark Ovens before you reboot, you'll need to issue: 9032b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 9042b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 9052b8dd5f4SWarner Losh 9068d9f1945SWarner Losh20000320: 9072b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 9082b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 9092b8dd5f4SWarner Losh cope if you have a problem combination is to add: 910ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 9112b8dd5f4SWarner Losh to the start of /etc/rc.conf. 9128d9f1945SWarner Losh 913f8ab1dd6SWarner Losh20000319: 914f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 915f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 916f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 917f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 918f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 919f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 920f8ab1dd6SWarner Losh 92119cada77SWarner Losh20000318: 922f699bbbbSMark Ovens We've entered the traditional post release dumping party. 92319cada77SWarner Losh Large kernel changes are being committed and are in the 92419cada77SWarner Losh works. It is important to keep the systems' klds and kernel 92519cada77SWarner Losh in sync as kernel interfaces and structures are changing. 92619cada77SWarner Losh Before reporting kernel panics, make sure that all modules 92719cada77SWarner Losh that you are loading are up to date. 928ba228352SWarner Losh 92919cada77SWarner Losh20000315: 9306d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 9316d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 9326d23c382SWarner Losh will do the trick. This isn't critical until you remove your 9336d23c382SWarner Losh wd device entries in /dev, at which point your system will not 9346d23c382SWarner Losh boot. 9356d23c382SWarner Losh 9366d23c382SWarner Losh20000315: 93719cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 93819cada77SWarner Losh to upgrade to 4.0 from 3.x. 93957199806SWarner Losh 940dc0dbf5cSWarner LoshCOMMON ITEMS: 941dc0dbf5cSWarner Losh 942a24eff53SWarner Losh General Notes 943a24eff53SWarner Losh ------------- 944a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 945a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 946a24eff53SWarner Losh installworld. This is especially true when upgrading between 947a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 948a24eff53SWarner Losh or several minor releases, or when several months have passed 949a24eff53SWarner Losh on the -current branch). 950a24eff53SWarner Losh 9515780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 9525780f3baSWarner Losh poisoning. This can happen because the make utility reads its 9535780f3baSWarner Losh environment when searching for values for global variables. 9545780f3baSWarner Losh To run your build attempts in an "environmental clean room", 9555780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 9565780f3baSWarner Losh page for more details. 9575780f3baSWarner Losh 958dc0dbf5cSWarner Losh To build a kernel 959dc0dbf5cSWarner Losh ----------------- 960ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 961f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 962ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 9631e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 9641e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 965dc0dbf5cSWarner Losh 966ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 967ba01eb20SWarner Losh -------------------------------------------------------------- 968ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 96947d0d01fSWarner Losh config KERNEL_NAME_HERE 970ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 971ba01eb20SWarner Losh make depend 972ba01eb20SWarner Losh make 973ba01eb20SWarner Losh make install 974ba01eb20SWarner Losh 975ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 976ba01eb20SWarner Losh 977ba01eb20SWarner Losh To rebuild everything and install it on the current system. 978ba01eb20SWarner Losh ----------------------------------------------------------- 979759f0aefSWarner Losh make world 980fdb9f54dSWarner Losh Build a new kernel, see above. 981759f0aefSWarner Losh 9821dece4a9SWarner Losh To upgrade from 4.x-stable to current 983ba26da8eSWarner Losh ------------------------------------- 984ba26da8eSWarner Losh make buildworld 9851e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 9867595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 987be1d673dSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE 988ee6e1fc3SWarner Losh reboot in single user [3] 989835284beSWarner Losh mergemaster -p [5] 990ba26da8eSWarner Losh make installworld 991a6cd4f9dSWarner Losh mergemaster [4] 992134d2e86SWarner Losh [1] 993ba26da8eSWarner Losh <reboot> 994ba26da8eSWarner Losh 995fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 996fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 997fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 998fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 999fdb9f54dSWarner Losh the UPDATING entries. 1000ba26da8eSWarner Losh 10011dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 10021dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 10031dece4a9SWarner Losh your sources that you have read and understood all the recent 10041dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 10051dece4a9SWarner Losh much fewer pitfalls. 10061dece4a9SWarner Losh 1007134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 1008134d2e86SWarner Losh should disable them at this point so they don't crash your 1009134d2e86SWarner Losh system on reboot. 1010134d2e86SWarner Losh 10119c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 10129c1a7444SWarner Losh your own device.hints to reflect your unique hardware 10139c1a7444SWarner Losh configuration. 10149c1a7444SWarner Losh 1015ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 1016ee6e1fc3SWarner Losh fsck -p 1017ee6e1fc3SWarner Losh mount -u / 1018ee6e1fc3SWarner Losh mount -a 1019ee6e1fc3SWarner Losh cd /usr/src 102047d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 1021f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 1022f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 1023ee6e1fc3SWarner Losh 1024a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 1025a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 1026a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 1027a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 1028a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 1029a6cd4f9dSWarner Losh for potential gotchas. 1030a6cd4f9dSWarner Losh 1031835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 1032835284beSWarner Losh you may need to do this if you get unknown user in the following 1033835284beSWarner Losh step. It never hurts to do it all the time. You may need to 1034835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 1035835284beSWarner Losh install) after the buildworld before this step if you last updated 1036835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 1037835284beSWarner Losh 1038dc0dbf5cSWarner LoshFORMAT: 1039dc0dbf5cSWarner Losh 1040f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 10411fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 1042f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1043f8ab1dd6SWarner Loshprevious releases if your system is older than this. 10441fc1a0dcSWarner Losh 1045e72fd46aSWarner LoshCopyright information: 1046e72fd46aSWarner Losh 10479698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1048e72fd46aSWarner Losh 1049772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1050772730c7SWarner Loshmodification, in full or in part, in any form or format of this 10519698f2c0SWarner Loshdocument are permitted without further permission from the author. 1052e72fd46aSWarner Losh 1053e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1054e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1055e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1056e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1057e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1058e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1059e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1060e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1061e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1062e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1063e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1064e72fd46aSWarner Losh 1065e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1066e72fd46aSWarner Loshauthor a beer. 1067e72fd46aSWarner Losh 106822306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1069772730c7SWarner Loshthis document. 1070772730c7SWarner Losh 107197d92980SPeter Wemm$FreeBSD$ 1072