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 2585aa5a2eSGregory Neil Shapiro20020404: 2685aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 2785aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 2885aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 2985aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 3085aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 3185aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 3285aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 3385aa5a2eSGregory Neil Shapiro 3485aa5a2eSGregory Neil Shapiro20020404: 3585aa5a2eSGregory Neil Shapiro Due to the import of sendmail 8.12.2 (see 20020217 entry), a new 3685aa5a2eSGregory Neil Shapiro user and group are required in order for sendmail to run as a 3785aa5a2eSGregory Neil Shapiro set-group-ID binary. A 'make installworld' will use the new user 3885aa5a2eSGregory Neil Shapiro and group to set the owner and group of /var/spool/clientmqueue 3985aa5a2eSGregory Neil Shapiro and will fail if the new user and group do not exist. The 'smmsp' 4085aa5a2eSGregory Neil Shapiro user and group must be merged from src/etc/group and 4185aa5a2eSGregory Neil Shapiro src/etc/master.passwd before using 'make installworld'. 4285aa5a2eSGregory Neil Shapiro 432292c02eSWarner Losh20020315: 442292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 452292c02eSWarner Losh 4669f7bcf3SWarner Losh20020225: 4769f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 4869f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 4969f7bcf3SWarner Losh 508f35c493SWarner Losh20020217: 518f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 528f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 538f35c493SWarner Losh command line mail submission has changed. Be sure to run 548f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 558f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 568f35c493SWarner Losh 57fa9401c1SWarner Losh20020112: 58fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 59fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 60fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 61fa9401c1SWarner Losh you have local modifications, you can use 62fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 63fa9401c1SWarner Losh /etc/pam.d. 64fa9401c1SWarner Losh 65fa9401c1SWarner Losh Please see the following url for more details: 66fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 67fa9401c1SWarner Losh 6847d0d01fSWarner Losh20011229: 6947d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 7047d0d01fSWarner Losh networkfs_types, please note that it has changed 7147d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 7247d0d01fSWarner Losh 73514318a8SWarner Losh20011220: 74514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 75514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 76514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 77514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 78514318a8SWarner Losh version have now been merged back into the base system's 79514318a8SWarner Losh version now. The only user-visible change resulting from this 80514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 81514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 82514318a8SWarner Losh as well. (There has never been rc file support for 83514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 84514318a8SWarner Losh reverted by the time the changes are MFCed.) 85514318a8SWarner Losh 86514318a8SWarner Losh20011215: 87514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 88514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 89514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 90514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 91514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 92514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 93514318a8SWarner Losh will need to be customized then for `odd' densities using 94514318a8SWarner Losh fdcontrol(8). 95514318a8SWarner Losh 962d22e2bfSWarner Losh20011209: 972d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 982d22e2bfSWarner Losh and truss(1) now works again. 992d22e2bfSWarner Losh 1009e0428e2SWarner Losh20011207: 1019e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 1029e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 1039e0428e2SWarner Losh see 1049e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 1059e0428e2SWarner Losh for details. 1069e0428e2SWarner Losh 1079bab8c59SWarner Losh20011204: 1089bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 1099bab8c59SWarner Losh kernel and burncd to be in sync. 1109bab8c59SWarner Losh 111e57d8b01SWarner Losh20011203: 112e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 113e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 114e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 115e57d8b01SWarner Losh not there already. 116e57d8b01SWarner Losh 117e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 118e57d8b01SWarner Losh until the issue has been resolved. 119e57d8b01SWarner Losh 120b001d36fSJacques Vidrine20011202: 121b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 122b001d36fSJacques Vidrine patched. 123b001d36fSJacques Vidrine 1244b676ec1SWarner Losh20011126: 1254b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 1265ebbf43eSWarner Losh after this date. You need to do this only once. 1274b676ec1SWarner Losh 128d961e462SWarner Losh20011103: 129d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 130d961e462SWarner Losh edges may be left, but for the most part things should be 1314b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 132d961e462SWarner Losh 133d961e462SWarner Losh20011030: 134d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 135d961e462SWarner Losh choppy waves in the upgrade process. 136d961e462SWarner Losh 1371fe003b6SWarner Losh20011030: 138a4b6fda0SWarner Losh The asr driver problem has been resolved. 1391fe003b6SWarner Losh 1401fe003b6SWarner Losh20011027: 1411fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 1421fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 1431fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 1441fe003b6SWarner Losh try to use from this date forward. 1451fe003b6SWarner Losh 1461fe003b6SWarner Losh20011025: 1471fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 1481fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 1491fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 1501fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 1511fe003b6SWarner Losh TARGET_ARCH=i386. 1521fe003b6SWarner Losh 153d05f9643SWarner Losh20011001: 154d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 155d05f9643SWarner Losh You must recompile both the kernel and userland applications 156d05f9643SWarner Losh at the same time. 157d05f9643SWarner Losh 15858970f85SWarner Losh20010929: 15958970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 16058970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 16158970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 16258970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 16358970f85SWarner Losh (eg, you can build pc98 on a i386 machine and vice versa). 16458970f85SWarner Losh 16558970f85SWarner Losh20010927: 16658970f85SWarner Losh Some weird problems result from using ACPI on some machines. 16758970f85SWarner Losh To disable ACPI you can add 168378f4486SAlfred Perlstein hint.acpi.0.disable="1" 16958970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 17058970f85SWarner Losh loader "ok" prompt). 17158970f85SWarner Losh 17258970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 17358970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 17458970f85SWarner Losh file and not list acpi in that list. 175378f4486SAlfred Perlstein 1765119d237SWarner Losh20010924: 1775119d237SWarner Losh The buildworld has been fixed. You may need to install 1785119d237SWarner Losh the 4.x compatibility libraries for some old binaries 1798b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 1808b039fffSWarner Losh get them installed on every installworld, or execute the 1818b039fffSWarner Losh following to get them installed only once: 1828b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 18358970f85SWarner Losh make all install 1848b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 1855119d237SWarner Losh 1863c293725SWarner Losh20010919: 1873c293725SWarner Losh There's a bug in the world build process. The cross-tools 1883c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 1893c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 190772730c7SWarner Losh workaround is to add 1913c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 1923c293725SWarner Losh before building world when upgrading from 4.x to current. This 1933c293725SWarner Losh can be removed afterwards. 1943c293725SWarner Losh 1953c293725SWarner Losh A proper fix to the buildworld target is needed. 1963c293725SWarner Losh 1973c293725SWarner Losh20010918: 1983c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 1993c293725SWarner Losh NFS may be unstable after this date. 2003c293725SWarner Losh 2013c293725SWarner Losh20010912: 2023c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 2033c293725SWarner Losh the kernel. While a few problems were introduced in the 2043c293725SWarner Losh initial commit, most of the major ones have been found and 2053c293725SWarner Losh corrected. 2063c293725SWarner Losh 2073c293725SWarner Losh20010901: 2083c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 2093c293725SWarner Losh arounds described in the 20010604 entry are now no longer 2103c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 2113c293725SWarner Losh have been rectified around this date. 2123c293725SWarner Losh 21398b17b95SWarner Losh20010823: 21498b17b95SWarner Losh named now runs as user bind and group bind rather than as 21598b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 21698b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 21798b17b95SWarner Losh and that group bind is available in /etc/group. Also make 21898b17b95SWarner Losh sure that user or group bind has read (and not write) 21998b17b95SWarner Losh permission for your name server configuration and that it 22098b17b95SWarner Losh has read and write permission for your slave zone files and 22198b17b95SWarner Losh directory. 22298b17b95SWarner Losh 22398b17b95SWarner Losh If you wish to continue to run named as root (a less secure 22498b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 22598b17b95SWarner Losh 22698b17b95SWarner Losh named_flags= 22798b17b95SWarner Losh 2287b9786edSMark Murray20010709: 2297b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 2307b9786edSMark Murray the ability of the shared library major number to handle. 2317b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 2327b9786edSMark Murray solution is to rebuild those ports. 2337b9786edSMark Murray 2341d28950eSWarner Losh20010628: 2351d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 2361d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 2371d28950eSWarner Losh 238e72fd46aSWarner Losh20010625: 23998b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 24098b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 24198b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 24298b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 24398b17b95SWarner Losh IRQ configuration needs more safety belts. 24416de1a07SWarner Losh 2450d415dffSWarner Losh20010617: 246e72fd46aSWarner Losh Softupdates problems have been corrected. 2470d415dffSWarner Losh 2480d415dffSWarner Losh20010614: 2490d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 2500d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 2510d415dffSWarner Losh kernel building methods. 2520d415dffSWarner Losh 2538b9959adSWarner Losh20010613: 2548b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 2558b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 256e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 257e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 2588b9959adSWarner Losh 259e72fd46aSWarner Losh20010613: 2608b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 261e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 262e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 2638b9959adSWarner Losh 2640d415dffSWarner Losh20010612: 2650d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 2660d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 2670d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 2680d415dffSWarner Losh work around this issue, please use only one or the other mechanism 2690d415dffSWarner Losh until this bug is fixed. 2700d415dffSWarner Losh 271e72fd46aSWarner Losh Please note that a feature of config is that if you have config 272e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 273e72fd46aSWarner Losh hints.c file, wheather you want it to or not. 274e72fd46aSWarner Losh 2750d415dffSWarner Losh20010610: 2760d415dffSWarner Losh Locale names have changed to match other systems better. 2770d415dffSWarner Losh 2786ccdb5e4SWarner Losh20010604: 2796ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 2806ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 2816ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 2823590182eSWarner Losh Interrupt storms look a lot like a hang. 2833590182eSWarner Losh 2843590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 2853590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 2863590182eSWarner Losh it is). 2873590182eSWarner Losh 2883590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 2893590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 2903590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 2913590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 2926ccdb5e4SWarner Losh 2930bc62786SWarner Losh20010530: 2940bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 2950bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 2960bc62786SWarner Losh a limited time. If you see 2970bc62786SWarner Losh 2980bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 2990bc62786SWarner Losh 3000bc62786SWarner Losh in your makeworld, then you need to migrate towards using 3010bc62786SWarner Losh COPY=-C. 3020bc62786SWarner Losh 30368a38c6cSWarner Losh20010525: 304b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 305c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 306c4f4a728SWarner Losh definitely is in bad shape. 30768a38c6cSWarner Losh 308ed0f29caSWarner Losh20010521: 309f10d3145SWarner Losh Minor repo damange has happened. This may cause problems 310ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 311ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 312ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 313ed0f29caSWarner Losh is 314ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 315ed0f29caSWarner Losh 31680c16af9SWarner Losh20010520: 31768a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 31880c16af9SWarner Losh 31980c16af9SWarner Losh20010519: 32080c16af9SWarner Losh pccard has had much reorganizational work done to it over 32180c16af9SWarner Losh the past few days. Everything should still work, but if 32280c16af9SWarner Losh not, please contact imp@freebsd.org. 32380c16af9SWarner Losh 324a45f2d05SWarner Losh20010517: 325a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 326a45f2d05SWarner Losh userland at the same time. 327a45f2d05SWarner Losh 328a45f2d05SWarner Losh20010517: 329a45f2d05SWarner Losh New ncurses imported. 330a45f2d05SWarner Losh 3312988afcaSWarner Losh20010512: 3322988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 3332988afcaSWarner Losh will be the only way to go starting July 1. 3342988afcaSWarner Losh 3351a33dba7SWarner Losh20010504: 3361a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 3371a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 3381a33dba7SWarner Losh 33909946a51SWarner Losh20010502: 34009946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 34109946a51SWarner Losh 34209946a51SWarner Losh20010501: 34309946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 34409946a51SWarner Losh 34509946a51SWarner Losh20010430: 346a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 34709946a51SWarner Losh go back in the water. 34809946a51SWarner Losh 34909946a51SWarner Losh20010429: 35009946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 35109946a51SWarner Losh this date, but before the correction date. 35209946a51SWarner Losh 35391dd3b53SWarner Losh20010423: 35491dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 35591dd3b53SWarner Losh 35691dd3b53SWarner Losh20010411: 35791dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 35891dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 35991dd3b53SWarner Losh Update only if you understand that you must not use the old 36091dd3b53SWarner Losh fsck with the new kernel ever. 36191dd3b53SWarner Losh 362933b3269SWarner Losh20010330: 363933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 364c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 365933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 366933b3269SWarner Losh 367933b3269SWarner Losh20010319: 368933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 369933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 370933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 371f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 37209946a51SWarner Losh 37309946a51SWarner Losh20010315: 37409946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 37509946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 37609946a51SWarner Losh been replaced by tunables. See ata.4 for details. 377933b3269SWarner Losh 378933b3269SWarner Losh20010312: 379933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 380933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 381933b3269SWarner Losh 382933b3269SWarner Losh20010312: 383933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 384933b3269SWarner Losh instead of ad-hoc. 385933b3269SWarner Losh 386933b3269SWarner Losh20010310: 387f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 388933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 389933b3269SWarner Losh ssh might not work if you don't. 390933b3269SWarner Losh 39162353691SWarner Losh20010303: 39262353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 39362353691SWarner Losh which means that you must include the miibus in your kernel if 39462353691SWarner Losh you use the ed driver. 39562353691SWarner Losh 396d325cf65SWarner Losh20010220: 397d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 398d325cf65SWarner Losh safe to go back into the water. 399d325cf65SWarner Losh 400024daae6SWarner Losh20010211: 401024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 402024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 403024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 404024daae6SWarner Losh that before upgrading would be a good time to do a level 0 405024daae6SWarner Losh dump of your system. No, really, I mean it this time. 406024daae6SWarner Losh 407024daae6SWarner Losh To get to the new system, you'll need to use the following 408024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 409024daae6SWarner Losh don't have to move this to the updating section. 410024daae6SWarner Losh 411024daae6SWarner Losh To get around the installworld problem, do: 412024daae6SWarner Losh # cd /usr/src/usr.bin/sed 413024daae6SWarner Losh # make install 414024daae6SWarner Losh # cd /usr/src 415024daae6SWarner Losh # make installworld 416024daae6SWarner Losh If that doesn't work, then try: 417024daae6SWarner Losh # make -k installworld 418024daae6SWarner Losh # make installworld 419024daae6SWarner Losh 420024daae6SWarner Losh20010207: 421024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 422024daae6SWarner Losh do not include devfs in your kernel as problems result. 423024daae6SWarner Losh 424024daae6SWarner Losh20010205: 4257595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 426024daae6SWarner Losh Remove them from your config. 427024daae6SWarner Losh 4281e159248SWarner Losh20010122: 4291e159248SWarner Losh ****************************** WARNING ****************************** 4301e159248SWarner Losh buildkernel has been changed slightly 4311e159248SWarner Losh ****************************** WARNING ****************************** 4321e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 4331e159248SWarner Losh should update your scripts and make.conf accordingly. 4341e159248SWarner Losh 4351e159248SWarner Losh20010119: 4361e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 4371e159248SWarner Losh This requires a new config to build correctly. 4381e159248SWarner Losh 439aac7dfeaSWarner Losh20010116: 440aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 441aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 442aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 443aac7dfeaSWarner Losh 444aac7dfeaSWarner Losh20010110: 445aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 446aac7dfeaSWarner Losh 447aac7dfeaSWarner Losh20010102: 448aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 449aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 450aac7dfeaSWarner Losh 45163c90c9eSWarner Losh20010101: 45263c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 45363c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 4545fd2a895SWarner Losh dump while building termcap. You can work around this problem 45563c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 45663c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 45763c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 45863c90c9eSWarner Losh might have been ignored by the -k option. 45963c90c9eSWarner Losh 4605fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 4615fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 4625fd2a895SWarner Losh of this working. 4635fd2a895SWarner Losh 464aac7dfeaSWarner Losh20001228: 465aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 466aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 467aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 468aac7dfeaSWarner Losh 469de2bcc63SWarner Losh20001218: 470de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 471de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 472de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 473de2bcc63SWarner Losh cards will not be recognized without it. 474de2bcc63SWarner Losh 475960773f7SWarner Losh20001205: 476960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 477960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 478960773f7SWarner Losh adding the following in pam.conf: 479960773f7SWarner Losh 480960773f7SWarner Losh sshd auth sufficient pam_skey.so 481960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 482960773f7SWarner Losh sshd session required pam_permit.so 483960773f7SWarner Losh 4840acc635eSWarner Losh20001031: 4850acc635eSWarner Losh cvs updated to 1.11. 4860acc635eSWarner Losh 4870acc635eSWarner Losh20001020: 4880acc635eSWarner Losh The random device needs more entropy, so you need to make sure 4890acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 4900acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 4910acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 4920acc635eSWarner Losh workaround. 4930acc635eSWarner Losh 4940acc635eSWarner Losh20001010: 4950acc635eSWarner Losh ****************************** WARNING ****************************** 4960acc635eSWarner Losh Sendmail has been updated. 4970acc635eSWarner Losh ****************************** WARNING ****************************** 4980acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 4990acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 5000acc635eSWarner Losh is set. 5010acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 5020acc635eSWarner Losh commands. 5030acc635eSWarner Losh o Now using sendmail's version of vacation(1). 5040acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 5050acc635eSWarner Losh in /usr/share/sendmail/cf. 5060acc635eSWarner Losh o sendmail.cw changed to local-host-names 5070acc635eSWarner Losh 5080acc635eSWarner Losh More details can be found at 5090acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 5100acc635eSWarner Losh 5116e98a146SWarner Losh20001009: 5126e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 5136e98a146SWarner Losh your entire ports tree, or you will have problems. 5146e98a146SWarner Losh 5156e98a146SWarner Losh20001006: 516685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 5176e98a146SWarner Losh the installed miniperl. It is recommended that you delete 5186e98a146SWarner Losh /usr/bin/miniperl. 5196e98a146SWarner Losh 520073113a4SWarner Losh20001005: 521073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 522685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 523073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 524073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 525073113a4SWarner Losh tree for anything to work. 526073113a4SWarner Losh 5270acc635eSWarner Losh20000928: 5280acc635eSWarner Losh There was a change in the passwd format. Need more information. 5290acc635eSWarner Losh 530be3885b3SWarner Losh20000916: 531be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 532be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 533be3885b3SWarner Losh same time as your kernel. 534be3885b3SWarner Losh 53576ec9675SWarner Losh20000914: 53676ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 53776ec9675SWarner Losh include the device will cause suspended laptops losing time 53876ec9675SWarner Losh when they resume. Include 53976ec9675SWarner Losh device pmtimer 54076ec9675SWarner Losh in your config file and 54101b9a434SWarner Losh hint.pmtimer.0.at="isa" 54276ec9675SWarner Losh to your /boot/device.hints file. 54376ec9675SWarner Losh 544f4865386SMark Murray20000911: 545f4865386SMark Murray The random device has been turned into a (pseudo-)device, 546f4865386SMark Murray rather than an option. The supplied kernel config files have 547f4865386SMark Murray been updated. You will need to do something similar in your 548f4865386SMark Murray own kernel config file. 549f4865386SMark Murray Remove: 550f4865386SMark Murray options RANDOMDEV 551f4865386SMark Murray Add: 552f4865386SMark Murray device random 553f4865386SMark Murray If you prefer to load the loadable module, you need to do 554f4865386SMark Murray nothing. 555f4865386SMark Murray 556d594498fSWarner Losh20000909: 557d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 558d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 559d594498fSWarner Losh reflect this if you load this module at boot time. 560d594498fSWarner Losh The line should read: 561d594498fSWarner Losh random_load="YES" 562d594498fSWarner Losh 5630deb7ddcSWarner Losh20000907: 5640deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 56516eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 56616eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 56716eb772dSWarner Losh sure you don't have model loading problems which might at 56816eb772dSWarner Losh first blush appear related to SMP. 56952bf24e7SWarner Losh 5705a01880bSWarner Losh20000906: 5715a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 5725a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 5735a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 5745a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 5755a01880bSWarner Losh don't have one, and you have host.conf. 5765a01880bSWarner Losh 5772b41163cSWarner Losh20000905: 57838d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 57938d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 58038d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 58138d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 58238d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 58338d6ecd2SWarner Losh 58438d6ecd2SWarner Losh20000905: 5858aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 5868aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 5878aab4bc7SWarner Losh is /boot/kernel. 5888aab4bc7SWarner Losh 5898aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 59038d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 59138d6ecd2SWarner Losh installkernel/installworld dance. 5922b41163cSWarner Losh 593d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 594d594498fSWarner Losh before booting the new kernel, since kldload will find stale 595d594498fSWarner Losh modules in that directory instead of finding them in the correct 596d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 597d594498fSWarner Losh is that the linux module crashes your machine after the update. 598d594498fSWarner Losh 599d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 600d594498fSWarner Losh mv /modules.old /boot/kernel.old 601d594498fSWarner Losh chflags noschg /kernel.old 602d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 603d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 604d594498fSWarner Losh fi 605d594498fSWarner Losh 606c22a309cSWarner Losh20000904: 607c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 608c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 609c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 610c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 611c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 612c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 613c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 614c22a309cSWarner Losh is not likely to be generated. 615c22a309cSWarner Losh 616fdb9f54dSWarner Losh20000825: 617fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 6189c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 6199c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 6209c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 6219c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 6229c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 6239c1a7444SWarner Losh messages will appear after the boot loader tries to start the 6249c1a7444SWarner Losh kernel. 6259c1a7444SWarner Losh 6269c1a7444SWarner Losh20000821: 6279c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 6289c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 6299c1a7444SWarner Losh /boot/loader.conf. 630fdb9f54dSWarner Losh 6318f250aa7SWarner Losh20000812: 6325da0d091SWarner Losh suidperl is now always built and installed on the system, but 6335da0d091SWarner Losh with permissions of 511. If you have applications that use 6345da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 6355da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 6365da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 6375da0d091SWarner Losh will fix this until the next build. 6385da0d091SWarner Losh 6395da0d091SWarner Losh20000812: 6408f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 6418f250aa7SWarner Losh visible changes that may immediately affect your configuration 6428f250aa7SWarner Losh include: 6438f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 6448f250aa7SWarner Losh - newaliases limited to root and trusted users 6458f250aa7SWarner Losh - MSA port (587) turned on by default 6468f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 6478f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 6488f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 6498f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 6508f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 6518f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 6528f250aa7SWarner Losh 65371c38472SWarner Losh20000810: 65471c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 65571c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 65671c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 65771c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 65871c38472SWarner Losh specific use for it. 65971c38472SWarner Losh 66071c38472SWarner Losh20000729: 66171c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 66271c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 66371c38472SWarner Losh /etc/rc.conf if they want to have the same setup 66471c38472SWarner Losh afterwards (unless the variables already are set, of course): 66571c38472SWarner Losh # Enable network daemons for user convenience. 66671c38472SWarner Losh inetd_enable="YES" 66771c38472SWarner Losh portmap_enable="YES" 66871c38472SWarner Losh sendmail_enable="YES" 66971c38472SWarner Losh 67071c38472SWarner Losh20000728: 67171c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 67271c38472SWarner Losh will need to change that to nullfs_load="YES". 67371c38472SWarner Losh 6741dece4a9SWarner Losh20000728: 6751dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 6761dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 6771dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 6781dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 6791dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 6801dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 6811dece4a9SWarner Losh to /MYKERNEL. 6821dece4a9SWarner Losh 683409e887cSWarner Losh20000711: 684409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 685409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 686409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 687409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 688409e887cSWarner Losh for details on potential problems that you might have and how 689409e887cSWarner Losh to get around them. 690409e887cSWarner Losh 691409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 692409e887cSWarner Losh clauses above, you needn't worry. 693409e887cSWarner Losh 694409e887cSWarner Losh20000711: 695409e887cSWarner Losh /etc/security has been updated to print the inode number of 696409e887cSWarner Losh setuid programs that have changed. You will see a large spike 697409e887cSWarner Losh in the number of changed programs the first time when you run 698409e887cSWarner Losh mergemaster to get a new /etc/security. 699409e887cSWarner Losh 700673d13f2SWarner Losh20000710: 701673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 702673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 703673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 704673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 705673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 706673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 707673d13f2SWarner Losh errors. (see below, 20000624). 708673d13f2SWarner Losh 709bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 7101dece4a9SWarner Losh 711673d13f2SWarner Losh20000709: 712c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 713c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 714c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 715673d13f2SWarner Losh ln -s aj /etc/malloc.conf 716673d13f2SWarner Losh 717e98e26cdSWarner Losh20000706: 718e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 719e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 720e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 721f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 722e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 7232c021c6cSMark Ovens interim if needed. 724e98e26cdSWarner Losh 725e98e26cdSWarner Losh20000705: 726e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 727e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 728e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 729e98e26cdSWarner Losh details. 730e98e26cdSWarner Losh 731c373950eSWarner Losh20000704: 7322f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 7332f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 7342f961bc8SWarner Losh 7352f961bc8SWarner Losh20000704: 736c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 737c373950eSWarner Losh or stop. This may cause some harmless warnings from older 738c373950eSWarner Losh rc.d scripts that haven't been updated. 739c373950eSWarner Losh 74027dc3a2bSWarner Losh20000630: 74127dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 74227dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 74327dc3a2bSWarner Losh which should be reported to des@freebsd.org. 74427dc3a2bSWarner Losh 745b8c215acSWarner Losh20000625: 746b8c215acSWarner Losh From approximately this date forward, one must have the crypto 74727dc3a2bSWarner Losh system installed in order to build the system and kernel. 74827dc3a2bSWarner Losh While not technically strictly true, one should treat it as 74927dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 75027dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 75127dc3a2bSWarner Losh were required. You should check with the latest collections 75227dc3a2bSWarner Losh to make sure that these haven't changed. 753b8c215acSWarner Losh 7547b990719SWarner Losh20000624: 7557b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 7567b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 7577b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 7581a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 7597b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 7607b990719SWarner Losh openssh and openssl should not be used to generate keys from this 7617b990719SWarner Losh date to the completion of the work. 7627b990719SWarner Losh 76327dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 76427dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 76527dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 76627dc3a2bSWarner Losh recreate the random and urandom devices. 76727dc3a2bSWarner Losh 76881e54c50SWarner Losh20000622: 76981e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 77081e54c50SWarner Losh BSD license. You may need to remove your symbolic links 77181e54c50SWarner Losh that used to be required when updating. 77281e54c50SWarner Losh 77339943833SWarner Losh20000621: 7742c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 7752a2f33fbSDaniel Baker the config file update procedure. 7762a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 777c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 778a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 77939943833SWarner Losh 780290f9ad8SWarner Losh20000620: 781290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 782290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 783290f9ad8SWarner Losh that workaround will no longer be required. 784290f9ad8SWarner Losh 78590fb6346SWarner Losh20000615: 78690fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 78790fb6346SWarner Losh ad driver. If you haven't done so already, you must update 78890fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 78990fb6346SWarner Losh devices. 79090fb6346SWarner Losh 791f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 792f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 793f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 794f75f65bbSWarner Losh may work). 795f75f65bbSWarner Losh 796ba26da8eSWarner Losh20000612: 797ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 798290f9ad8SWarner Losh on the topic before even thinking about updating. You will 799c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 800290f9ad8SWarner Losh to your config file to compile them in statically. The format 801f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 802f54a3542SWarner Losh NEWCARD for examples of the new format. 803290f9ad8SWarner Losh 8049698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 8059698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 8069698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 8079698f2c0SWarner Losh in it. 808bbcc5149SWarner Losh 809d65850ebSWarner Losh20000522: 810ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 811d65850ebSWarner Losh building a kernel after this point is advised that they need 812d65850ebSWarner Losh to rebuild their binutils (or better yet do a 813d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 814d65850ebSWarner Losh 815d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 816d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 817d9583a00SWarner Losh is recommended that you don't set this option until the problem 818d9583a00SWarner Losh is resolved. 819d9583a00SWarner Losh 8208039cedeSWarner Losh20000513: 8218039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 8228039cedeSWarner Losh 823d65850ebSWarner Losh20000510: 8248039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 8258039cedeSWarner Losh This will require some care in updating alphas. A new libstand 8268039cedeSWarner Losh is requires for the boot blocks to build properly. 8278039cedeSWarner Losh 8288039cedeSWarner Losh20000503: 8298039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 8308039cedeSWarner Losh is now available. 8318039cedeSWarner Losh 832d65850ebSWarner Losh20000502: 833d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 834d65850ebSWarner Losh connected to the kernel building instead. 835d65850ebSWarner Losh 836be149406SNik Clayton20000427: 8378039cedeSWarner Losh You may need to build gperf 8388039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 8398039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 8408039cedeSWarner Losh an option only in -current. 8418039cedeSWarner Losh 8422b8dd5f4SWarner Losh20000417: 8432b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 844f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 8452b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 8462b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 8472c021c6cSMark Ovens before you reboot, you'll need to issue: 8482b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 8492b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 8502b8dd5f4SWarner Losh 8518d9f1945SWarner Losh20000320: 8522b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 8532b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 8542b8dd5f4SWarner Losh cope if you have a problem combination is to add: 8558d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 8562b8dd5f4SWarner Losh to the start of /etc/rc.conf. 8578d9f1945SWarner Losh 858f8ab1dd6SWarner Losh20000319: 859f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 860f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 861f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 862f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 863f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 864f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 865f8ab1dd6SWarner Losh 86619cada77SWarner Losh20000318: 867f699bbbbSMark Ovens We've entered the traditional post release dumping party. 86819cada77SWarner Losh Large kernel changes are being committed and are in the 86919cada77SWarner Losh works. It is important to keep the systems' klds and kernel 87019cada77SWarner Losh in sync as kernel interfaces and structures are changing. 87119cada77SWarner Losh Before reporting kernel panics, make sure that all modules 87219cada77SWarner Losh that you are loading are up to date. 873ba228352SWarner Losh 87419cada77SWarner Losh20000315: 8756d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 8766d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 8776d23c382SWarner Losh will do the trick. This isn't critical until you remove your 8786d23c382SWarner Losh wd device entries in /dev, at which point your system will not 8796d23c382SWarner Losh boot. 8806d23c382SWarner Losh 8816d23c382SWarner Losh20000315: 88219cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 88319cada77SWarner Losh to upgrade to 4.0 from 3.x. 88457199806SWarner Losh 885dc0dbf5cSWarner LoshCOMMON ITEMS: 886dc0dbf5cSWarner Losh 887a24eff53SWarner Losh General Notes 888a24eff53SWarner Losh ------------- 889a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 890a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 891a24eff53SWarner Losh installworld. This is especially true when upgrading between 892a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 893a24eff53SWarner Losh or several minor releases, or when several months have passed 894a24eff53SWarner Losh on the -current branch). 895a24eff53SWarner Losh 8965780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 8975780f3baSWarner Losh poisoning. This can happen because the make utility reads its 8985780f3baSWarner Losh environment when searching for values for global variables. 8995780f3baSWarner Losh To run your build attempts in an "environmental clean room", 9005780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 9015780f3baSWarner Losh page for more details. 9025780f3baSWarner Losh 903dc0dbf5cSWarner Losh To build a kernel 904dc0dbf5cSWarner Losh ----------------- 905ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 906f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 907ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 9081e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 9091e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 910dc0dbf5cSWarner Losh 911ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 912ba01eb20SWarner Losh -------------------------------------------------------------- 913ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 91447d0d01fSWarner Losh config KERNEL_NAME_HERE 915ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 916ba01eb20SWarner Losh make depend 917ba01eb20SWarner Losh make 918ba01eb20SWarner Losh make install 919ba01eb20SWarner Losh 920ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 921ba01eb20SWarner Losh 922ba01eb20SWarner Losh To rebuild everything and install it on the current system. 923ba01eb20SWarner Losh ----------------------------------------------------------- 924759f0aefSWarner Losh make world 925fdb9f54dSWarner Losh Build a new kernel, see above. 926759f0aefSWarner Losh 9271dece4a9SWarner Losh To upgrade from 4.x-stable to current 928ba26da8eSWarner Losh ------------------------------------- 929ba26da8eSWarner Losh make buildworld 9301e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 9317595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 9321e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 933ee6e1fc3SWarner Losh reboot in single user [3] 934ba26da8eSWarner Losh make installworld 935a6cd4f9dSWarner Losh mergemaster [4] 936134d2e86SWarner Losh [1] 937ba26da8eSWarner Losh <reboot> 938ba26da8eSWarner Losh 939fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 940fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 941fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 942fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 943fdb9f54dSWarner Losh the UPDATING entries. 944ba26da8eSWarner Losh 9451dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 9461dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 9471dece4a9SWarner Losh your sources that you have read and understood all the recent 9481dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 9491dece4a9SWarner Losh much fewer pitfalls. 9501dece4a9SWarner Losh 951134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 952134d2e86SWarner Losh should disable them at this point so they don't crash your 953134d2e86SWarner Losh system on reboot. 954134d2e86SWarner Losh 9559c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 9569c1a7444SWarner Losh your own device.hints to reflect your unique hardware 9579c1a7444SWarner Losh configuration. 9589c1a7444SWarner Losh 959ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 960ee6e1fc3SWarner Losh fsck -p 961ee6e1fc3SWarner Losh mount -u / 962ee6e1fc3SWarner Losh mount -a 963ee6e1fc3SWarner Losh cd /usr/src 96447d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 965ee6e1fc3SWarner Losh 966a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 967a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 968a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 969a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 970a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 971a6cd4f9dSWarner Losh for potential gotchas. 972a6cd4f9dSWarner Losh 973dc0dbf5cSWarner LoshFORMAT: 974dc0dbf5cSWarner Losh 975f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 9761fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 977f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 978f8ab1dd6SWarner Loshprevious releases if your system is older than this. 9791fc1a0dcSWarner Losh 980e72fd46aSWarner LoshCopyright information: 981e72fd46aSWarner Losh 9829698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 983e72fd46aSWarner Losh 984772730c7SWarner LoshRedistribution, publication, translation and use, with or without 985772730c7SWarner Loshmodification, in full or in part, in any form or format of this 9869698f2c0SWarner Loshdocument are permitted without further permission from the author. 987e72fd46aSWarner Losh 988e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 989e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 990e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 991e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 992e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 993e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 994e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 995e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 996e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 997e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 998e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 999e72fd46aSWarner Losh 1000e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1001e72fd46aSWarner Loshauthor a beer. 1002e72fd46aSWarner Losh 100322306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1004772730c7SWarner Loshthis document. 1005772730c7SWarner Losh 100697d92980SPeter Wemm$FreeBSD$ 1007