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 25528a0ef5SJacques Vidrine20020421: 26528a0ef5SJacques Vidrine When exec'ing set[ug]id executables, the kernel now ensures that the 27528a0ef5SJacques Vidrine stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 28528a0ef5SJacques Vidrine 2985aa5a2eSGregory Neil Shapiro20020404: 3085aa5a2eSGregory Neil Shapiro New sendmail startup scripts have been installed to make it 3185aa5a2eSGregory Neil Shapiro easier to use alternative MTAs with FreeBSD. Setting the rc.conf 3285aa5a2eSGregory Neil Shapiro variable sendmail_enable to "NO" no longer prevents any sendmail 3385aa5a2eSGregory Neil Shapiro daemons from starting. Instead, either set sendmail_enable to 3485aa5a2eSGregory Neil Shapiro "NONE" or change mta_start_script to a script for starting 3585aa5a2eSGregory Neil Shapiro an alternative MTA. Setting mta_start_script to "" will 3685aa5a2eSGregory Neil Shapiro also prevent any MTA from being started at boot. 3785aa5a2eSGregory Neil Shapiro 388f1e4358SRuslan Ermilov20020403: 398f1e4358SRuslan Ermilov UCONSOLE is no longer a valid kernel option. 408f1e4358SRuslan Ermilov 412292c02eSWarner Losh20020315: 422292c02eSWarner Losh FreeBSD 5.0 DP-1 was basically branched today. 432292c02eSWarner Losh 4469f7bcf3SWarner Losh20020225: 4569f7bcf3SWarner Losh Warnings are now errors in the kernel. Unless you are a developer, 4669f7bcf3SWarner Losh you should add -DNO_WERROR to your make line. 4769f7bcf3SWarner Losh 488f35c493SWarner Losh20020217: 498f35c493SWarner Losh sendmail 8.12.2 has been imported. The sendmail binary is no 508f35c493SWarner Losh longer a set-user-ID root binary and the infrastructure to support 518f35c493SWarner Losh command line mail submission has changed. Be sure to run 528f35c493SWarner Losh mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 538f35c493SWarner Losh and /etc/mail) and read /etc/mail/README for more details. 548f35c493SWarner Losh 55835284beSWarner Losh Due to the import of sendmail 8.12.2, a new user and group are 56835284beSWarner Losh required in order for sendmail to run as a set-group-ID 57835284beSWarner Losh binary. A 'make installworld' will use the new user and group 58835284beSWarner Losh to set the owner and group of /var/spool/clientmqueue and will 59835284beSWarner Losh fail if the new user and group do not exist. The 'smmsp' user 60835284beSWarner Losh and group must be merged from src/etc/group and 61835284beSWarner Losh src/etc/master.passwd before using 'make installworld'. 62835284beSWarner Losh 'mergemaster -p' will do this. You may need to install 63835284beSWarner Losh mergemaster before this will work if you are updating from a 64835284beSWarner Losh very old version of current. The updating recipe has changed 65835284beSWarner Losh as of this date. 66835284beSWarner Losh 67fa9401c1SWarner Losh20020112: 68fa9401c1SWarner Losh The preferred configuration method for PAM is now /etc/pam.d/ 69fa9401c1SWarner Losh rather than /etc/pam.conf. If you have an unmodified 70fa9401c1SWarner Losh pam.conf, just delete it after your next mergemaster run. If 71fa9401c1SWarner Losh you have local modifications, you can use 72fa9401c1SWarner Losh /usr/src/etc/pam.d/convert.pl to incorporate them into your 73fa9401c1SWarner Losh /etc/pam.d. 74fa9401c1SWarner Losh 75fa9401c1SWarner Losh Please see the following url for more details: 76fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 7747d0d01fSWarner Losh20011229: 7847d0d01fSWarner Losh If anyone here is already using the new rc.conf(5) variable 7947d0d01fSWarner Losh networkfs_types, please note that it has changed 8047d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 8147d0d01fSWarner Losh 82514318a8SWarner Losh20011220: 83514318a8SWarner Losh sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 84514318a8SWarner Losh started out its life in the ISDN4BSD project as an offspring 85514318a8SWarner Losh from sys/net/if_spppsubr.c, which eventually got a life of its 86514318a8SWarner Losh own. All the accumulated features and bugfixes of the i4b 87514318a8SWarner Losh version have now been merged back into the base system's 88514318a8SWarner Losh version now. The only user-visible change resulting from this 89514318a8SWarner Losh is that i4b's sppp(4) interfaces are to be managed with 90514318a8SWarner Losh spppcontrol(8) again, since ispppcontrol(8) has been retired 91514318a8SWarner Losh as well. (There has never been rc file support for 92514318a8SWarner Losh ispppcontrol in -current, but only in -stable. That will be 93514318a8SWarner Losh reverted by the time the changes are MFCed.) 94514318a8SWarner Losh 95514318a8SWarner Losh20011215: 96514318a8SWarner Losh The fdc(4) driver has been updated and now automatically 97514318a8SWarner Losh recognizes media in `standard' formats (like 1440 KB and 98514318a8SWarner Losh 720 KB for a 3.5" high-density drive) when accessing the 99514318a8SWarner Losh default device node (e. g. /dev/fd0). The old variety of 100514318a8SWarner Losh floppy device nodes /dev/fd*.* is no longer present by 101514318a8SWarner Losh default, devices can be created (in DEVFS) on demand. They 102514318a8SWarner Losh will need to be customized then for `odd' densities using 103514318a8SWarner Losh fdcontrol(8). 104514318a8SWarner Losh 1052d22e2bfSWarner Losh20011209: 1062d22e2bfSWarner Losh The bugs in procfs' debugging support code have been fixed, 1072d22e2bfSWarner Losh and truss(1) now works again. 1082d22e2bfSWarner Losh 1099e0428e2SWarner Losh20011207: 1109e0428e2SWarner Losh Daily security checks have been split out to use the periodic(8) 1119e0428e2SWarner Losh scripts. Some change in configuration may be necessary. Please 1129e0428e2SWarner Losh see 1139e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 1149e0428e2SWarner Losh for details. 1159e0428e2SWarner Losh 1169bab8c59SWarner Losh20011204: 1179bab8c59SWarner Losh sos added VCD/SVCD support to ata driver and that needs the 1189bab8c59SWarner Losh kernel and burncd to be in sync. 1199bab8c59SWarner Losh 120e57d8b01SWarner Losh20011203: 121e57d8b01SWarner Losh The procfs pseudo-filesystem has now been converted to use the 122e57d8b01SWarner Losh pseudofs framework. If you have 'options PROCFS' in your 123e57d8b01SWarner Losh kernel config, you'll need to add 'options PSEUDOFS' if it's 124e57d8b01SWarner Losh not there already. 125e57d8b01SWarner Losh 126e57d8b01SWarner Losh This change temporarily breaks truss(1); use ktrace(1) instead 127e57d8b01SWarner Losh until the issue has been resolved. 128e57d8b01SWarner Losh 129b001d36fSJacques Vidrine20011202: 130b001d36fSJacques Vidrine A security hole in OpenSSH involving `UseLogin yes' has been 131b001d36fSJacques Vidrine patched. 132b001d36fSJacques Vidrine 1334b676ec1SWarner Losh20011126: 1344b676ec1SWarner Losh You need to remove /usr/obj/.../usr.bin/tip before rebuilding 1355ebbf43eSWarner Losh after this date. You need to do this only once. 1364b676ec1SWarner Losh 137d961e462SWarner Losh20011103: 138d961e462SWarner Losh Most of the awk issues have been resolved. Some rough 139d961e462SWarner Losh edges may be left, but for the most part things should be 1404b676ec1SWarner Losh back to "normal." For CURRENT's usual definition of "normal." 141d961e462SWarner Losh 142d961e462SWarner Losh20011030: 143d961e462SWarner Losh Awk has been upgraded to the one true awk from bell labs. Expect 144d961e462SWarner Losh choppy waves in the upgrade process. 145d961e462SWarner Losh 1461fe003b6SWarner Losh20011030: 147a4b6fda0SWarner Losh The asr driver problem has been resolved. 1481fe003b6SWarner Losh 1491fe003b6SWarner Losh20011027: 1501fe003b6SWarner Losh Due to changes in other parts of the system, the asr driver 1511fe003b6SWarner Losh now causes the system to panic on boot. Do not use it pending 1521fe003b6SWarner Losh correction. Comment it out of any kernel config file that you 1531fe003b6SWarner Losh try to use from this date forward. 1541fe003b6SWarner Losh 1551fe003b6SWarner Losh20011025: 1561fe003b6SWarner Losh When crossbuilding, use TARGET=xxx where you used to use 1571fe003b6SWarner Losh MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 1581fe003b6SWarner Losh unless you are changing both of them. To cross build pc98 on 1591fe003b6SWarner Losh an alpha, for example, you need to set TARGET=pc98 and 1601fe003b6SWarner Losh TARGET_ARCH=i386. 1611fe003b6SWarner Losh 162d05f9643SWarner Losh20011001: 163d05f9643SWarner Losh The kernel interface that burncd depends on has changed. 164d05f9643SWarner Losh You must recompile both the kernel and userland applications 165d05f9643SWarner Losh at the same time. 166d05f9643SWarner Losh 16758970f85SWarner Losh20010929: 16858970f85SWarner Losh When crossbuilding, please set TARGET_ARCH rather than 16958970f85SWarner Losh MACHINE_ARCH to indicate the target. In the future, one will 17058970f85SWarner Losh set TARGET_MACHINE where you set MACHINE now. At the moment, 17158970f85SWarner Losh setting MACHINE alone for same MACHINE_ARCH machines works 17258970f85SWarner Losh (eg, you can build pc98 on a i386 machine and vice versa). 17358970f85SWarner Losh 17458970f85SWarner Losh20010927: 17558970f85SWarner Losh Some weird problems result from using ACPI on some machines. 17658970f85SWarner Losh To disable ACPI you can add 177378f4486SAlfred Perlstein hint.acpi.0.disable="1" 17858970f85SWarner Losh to /boot/loader.conf (or by putting set X=Y at the boot 17958970f85SWarner Losh loader "ok" prompt). 18058970f85SWarner Losh 18158970f85SWarner Losh Alternatively, you can remove it from /boot/kernel/acpi.ko 18258970f85SWarner Losh or use the MODULES_OVERRIDE function in your kernel config 18358970f85SWarner Losh file and not list acpi in that list. 184378f4486SAlfred Perlstein 1855119d237SWarner Losh20010924: 1865119d237SWarner Losh The buildworld has been fixed. You may need to install 1875119d237SWarner Losh the 4.x compatibility libraries for some old binaries 1888b039fffSWarner Losh to work. Add COMPAT4X=true to your /etc/make.conf to 1898b039fffSWarner Losh get them installed on every installworld, or execute the 1908b039fffSWarner Losh following to get them installed only once: 1918b039fffSWarner Losh cd src/lib/compat/compat4x.<arch> 19258970f85SWarner Losh make all install 1938b039fffSWarner Losh You will see ``__stdoutp undefined'' until you do this. 1945119d237SWarner Losh 1953c293725SWarner Losh20010919: 1963c293725SWarner Losh There's a bug in the world build process. The cross-tools 1973c293725SWarner Losh are build with the NEW headers, but the OLD libc.a. This 1983c293725SWarner Losh leads to all kinds of problems with the new libc. A temporary 199772730c7SWarner Losh workaround is to add 2003c293725SWarner Losh CFLAGS="-O -pipe -D_OLD_STDIO" 2013c293725SWarner Losh before building world when upgrading from 4.x to current. This 2023c293725SWarner Losh can be removed afterwards. 2033c293725SWarner Losh 2043c293725SWarner Losh A proper fix to the buildworld target is needed. 2053c293725SWarner Losh 2063c293725SWarner Losh20010918: 2073c293725SWarner Losh Peter has committed his new kthread nfs client/server code. 2083c293725SWarner Losh NFS may be unstable after this date. 2093c293725SWarner Losh 2103c293725SWarner Losh20010912: 2113c293725SWarner Losh KSE has hit the tree. Lots of things are now different in 2123c293725SWarner Losh the kernel. While a few problems were introduced in the 2133c293725SWarner Losh initial commit, most of the major ones have been found and 2143c293725SWarner Losh corrected. 2153c293725SWarner Losh 2163c293725SWarner Losh20010901: 2173c293725SWarner Losh In OLDCARD, CardBus bridges appear to be stable. The work 2183c293725SWarner Losh arounds described in the 20010604 entry are now no longer 2193c293725SWarner Losh necessary and will be ignored. Most insert/remove problems 2203c293725SWarner Losh have been rectified around this date. 2213c293725SWarner Losh 22298b17b95SWarner Losh20010823: 22398b17b95SWarner Losh named now runs as user bind and group bind rather than as 22498b17b95SWarner Losh root. If named_enable is set to YES in /etc/rc.conf, ensure 22598b17b95SWarner Losh that user bind is available in /etc/passwd (using vipw(8)) 22698b17b95SWarner Losh and that group bind is available in /etc/group. Also make 22798b17b95SWarner Losh sure that user or group bind has read (and not write) 22898b17b95SWarner Losh permission for your name server configuration and that it 22998b17b95SWarner Losh has read and write permission for your slave zone files and 23098b17b95SWarner Losh directory. 23198b17b95SWarner Losh 23298b17b95SWarner Losh If you wish to continue to run named as root (a less secure 23398b17b95SWarner Losh alternative), add a line to /etc/rc.conf saying 23498b17b95SWarner Losh 23598b17b95SWarner Losh named_flags= 23698b17b95SWarner Losh 2377b9786edSMark Murray20010709: 2387b9786edSMark Murray The PAM libraries have had an API upgrade that is beyond 2397b9786edSMark Murray the ability of the shared library major number to handle. 2407b9786edSMark Murray It is manifested by PAM-using ports dumping core. The 2417b9786edSMark Murray solution is to rebuild those ports. 2427b9786edSMark Murray 2431d28950eSWarner Losh20010628: 2441d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 2451d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 2461d28950eSWarner Losh 247e72fd46aSWarner Losh20010625: 24898b17b95SWarner Losh The pccard modem issue from 20010613 has been corrected. 24998b17b95SWarner Losh OLDCARD support is still a little weak in -current. slot 1 is 25098b17b95SWarner Losh known not to work on some TI based cardbus bridges. Some 25198b17b95SWarner Losh cardbus bridges do not properly detect insert/removal events. 25298b17b95SWarner Losh IRQ configuration needs more safety belts. 25316de1a07SWarner Losh 2540d415dffSWarner Losh20010617: 255e72fd46aSWarner Losh Softupdates problems have been corrected. 2560d415dffSWarner Losh 2570d415dffSWarner Losh20010614: 2580d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 2590d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 2600d415dffSWarner Losh kernel building methods. 2610d415dffSWarner Losh 2628b9959adSWarner Losh20010613: 2638b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 2648b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 265e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 266e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 2678b9959adSWarner Losh 268e72fd46aSWarner Losh20010613: 2698b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 270e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 271e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 2728b9959adSWarner Losh 2730d415dffSWarner Losh20010612: 2740d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 2750d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 2760d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 2770d415dffSWarner Losh work around this issue, please use only one or the other mechanism 2780d415dffSWarner Losh until this bug is fixed. 2790d415dffSWarner Losh 280e72fd46aSWarner Losh Please note that a feature of config is that if you have config 281e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 282e72fd46aSWarner Losh hints.c file, wheather you want it to or not. 283e72fd46aSWarner Losh 2840d415dffSWarner Losh20010610: 2850d415dffSWarner Losh Locale names have changed to match other systems better. 2860d415dffSWarner Losh 2876ccdb5e4SWarner Losh20010604: 2886ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 2896ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 2906ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 2913590182eSWarner Losh Interrupt storms look a lot like a hang. 2923590182eSWarner Losh 2933590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 2943590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 2953590182eSWarner Losh it is). 2963590182eSWarner Losh 2973590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 2983590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 2993590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 3003590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 3016ccdb5e4SWarner Losh 3020bc62786SWarner Losh20010530: 3030bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 3040bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 3050bc62786SWarner Losh a limited time. If you see 3060bc62786SWarner Losh 3070bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 3080bc62786SWarner Losh 3090bc62786SWarner Losh in your makeworld, then you need to migrate towards using 3100bc62786SWarner Losh COPY=-C. 3110bc62786SWarner Losh 31268a38c6cSWarner Losh20010525: 313b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 314c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 315c4f4a728SWarner Losh definitely is in bad shape. 31668a38c6cSWarner Losh 317ed0f29caSWarner Losh20010521: 318f10d3145SWarner Losh Minor repo damange has happened. This may cause problems 319ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 320ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 321ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 322ed0f29caSWarner Losh is 323ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 324ed0f29caSWarner Losh 32580c16af9SWarner Losh20010520: 32668a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 32780c16af9SWarner Losh 32880c16af9SWarner Losh20010519: 32980c16af9SWarner Losh pccard has had much reorganizational work done to it over 33080c16af9SWarner Losh the past few days. Everything should still work, but if 33180c16af9SWarner Losh not, please contact imp@freebsd.org. 33280c16af9SWarner Losh 333a45f2d05SWarner Losh20010517: 334a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 335a45f2d05SWarner Losh userland at the same time. 336a45f2d05SWarner Losh 337a45f2d05SWarner Losh20010517: 338a45f2d05SWarner Losh New ncurses imported. 339a45f2d05SWarner Losh 3402988afcaSWarner Losh20010512: 3412988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 3422988afcaSWarner Losh will be the only way to go starting July 1. 3432988afcaSWarner Losh 3441a33dba7SWarner Losh20010504: 3451a33dba7SWarner Losh OpenSSH has been updated to 2.9. Some defaults are different, 3461a33dba7SWarner Losh including RhostsRSAAuthentication, which changes from yes to no. 3471a33dba7SWarner Losh 34809946a51SWarner Losh20010502: 34909946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 35009946a51SWarner Losh 35109946a51SWarner Losh20010501: 35209946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 35309946a51SWarner Losh 35409946a51SWarner Losh20010430: 355a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 35609946a51SWarner Losh go back in the water. 35709946a51SWarner Losh 35809946a51SWarner Losh20010429: 35909946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 36009946a51SWarner Losh this date, but before the correction date. 36109946a51SWarner Losh 36291dd3b53SWarner Losh20010423: 36391dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 36491dd3b53SWarner Losh 36591dd3b53SWarner Losh20010411: 36691dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 36791dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 36891dd3b53SWarner Losh Update only if you understand that you must not use the old 36991dd3b53SWarner Losh fsck with the new kernel ever. 37091dd3b53SWarner Losh 371933b3269SWarner Losh20010330: 372933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 373c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 374933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 375933b3269SWarner Losh 376933b3269SWarner Losh20010319: 377933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 378933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 379933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 380f34a9421SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 38109946a51SWarner Losh 38209946a51SWarner Losh20010315: 38309946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 38409946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 38509946a51SWarner Losh been replaced by tunables. See ata.4 for details. 386933b3269SWarner Losh 387933b3269SWarner Losh20010312: 388933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 389933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 390933b3269SWarner Losh 391933b3269SWarner Losh20010312: 392933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 393933b3269SWarner Losh instead of ad-hoc. 394933b3269SWarner Losh 395933b3269SWarner Losh20010310: 396f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 397933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 398933b3269SWarner Losh ssh might not work if you don't. 399933b3269SWarner Losh 40062353691SWarner Losh20010303: 40162353691SWarner Losh The ed driver has been updated. It now allows mii attachments, 40262353691SWarner Losh which means that you must include the miibus in your kernel if 40362353691SWarner Losh you use the ed driver. 40462353691SWarner Losh 405d325cf65SWarner Losh20010220: 406d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 407d325cf65SWarner Losh safe to go back into the water. 408d325cf65SWarner Losh 409024daae6SWarner Losh20010211: 410024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 411024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 412024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 413024daae6SWarner Losh that before upgrading would be a good time to do a level 0 414024daae6SWarner Losh dump of your system. No, really, I mean it this time. 415024daae6SWarner Losh 416024daae6SWarner Losh To get to the new system, you'll need to use the following 417024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 418024daae6SWarner Losh don't have to move this to the updating section. 419024daae6SWarner Losh 420024daae6SWarner Losh To get around the installworld problem, do: 421024daae6SWarner Losh # cd /usr/src/usr.bin/sed 422024daae6SWarner Losh # make install 423024daae6SWarner Losh # cd /usr/src 424024daae6SWarner Losh # make installworld 425024daae6SWarner Losh If that doesn't work, then try: 426024daae6SWarner Losh # make -k installworld 427024daae6SWarner Losh # make installworld 428024daae6SWarner Losh 429024daae6SWarner Losh20010207: 430024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 431024daae6SWarner Losh do not include devfs in your kernel as problems result. 432024daae6SWarner Losh 433024daae6SWarner Losh20010205: 4347595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 435024daae6SWarner Losh Remove them from your config. 436024daae6SWarner Losh 4371e159248SWarner Losh20010122: 4381e159248SWarner Losh ****************************** WARNING ****************************** 4391e159248SWarner Losh buildkernel has been changed slightly 4401e159248SWarner Losh ****************************** WARNING ****************************** 4411e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 4421e159248SWarner Losh should update your scripts and make.conf accordingly. 4431e159248SWarner Losh 4441e159248SWarner Losh20010119: 4451e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 4461e159248SWarner Losh This requires a new config to build correctly. 4471e159248SWarner Losh 448aac7dfeaSWarner Losh20010116: 449aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 450aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 451aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 452aac7dfeaSWarner Losh 453aac7dfeaSWarner Losh20010110: 454aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 455aac7dfeaSWarner Losh 456aac7dfeaSWarner Losh20010102: 457aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 458aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 459aac7dfeaSWarner Losh 46063c90c9eSWarner Losh20010101: 46163c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 46263c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 4635fd2a895SWarner Losh dump while building termcap. You can work around this problem 46463c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 46563c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 46663c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 46763c90c9eSWarner Losh might have been ignored by the -k option. 46863c90c9eSWarner Losh 4695fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 4705fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 4715fd2a895SWarner Losh of this working. 4725fd2a895SWarner Losh 473aac7dfeaSWarner Losh20001228: 474aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 475aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 476aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 477aac7dfeaSWarner Losh 478de2bcc63SWarner Losh20001218: 479de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 480de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 481de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 482de2bcc63SWarner Losh cards will not be recognized without it. 483de2bcc63SWarner Losh 484960773f7SWarner Losh20001205: 485960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 486960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 487960773f7SWarner Losh adding the following in pam.conf: 488960773f7SWarner Losh 489960773f7SWarner Losh sshd auth sufficient pam_skey.so 490960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 491960773f7SWarner Losh sshd session required pam_permit.so 492960773f7SWarner Losh 4930acc635eSWarner Losh20001031: 4940acc635eSWarner Losh cvs updated to 1.11. 4950acc635eSWarner Losh 4960acc635eSWarner Losh20001020: 4970acc635eSWarner Losh The random device needs more entropy, so you need to make sure 4980acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 4990acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 5000acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 5010acc635eSWarner Losh workaround. 5020acc635eSWarner Losh 5030acc635eSWarner Losh20001010: 5040acc635eSWarner Losh ****************************** WARNING ****************************** 5050acc635eSWarner Losh Sendmail has been updated. 5060acc635eSWarner Losh ****************************** WARNING ****************************** 5070acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 5080acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 5090acc635eSWarner Losh is set. 5100acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 5110acc635eSWarner Losh commands. 5120acc635eSWarner Losh o Now using sendmail's version of vacation(1). 5130acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 5140acc635eSWarner Losh in /usr/share/sendmail/cf. 5150acc635eSWarner Losh o sendmail.cw changed to local-host-names 5160acc635eSWarner Losh 5170acc635eSWarner Losh More details can be found at 5180acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 5190acc635eSWarner Losh 5206e98a146SWarner Losh20001009: 5216e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 5226e98a146SWarner Losh your entire ports tree, or you will have problems. 5236e98a146SWarner Losh 5246e98a146SWarner Losh20001006: 525685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 5266e98a146SWarner Losh the installed miniperl. It is recommended that you delete 5276e98a146SWarner Losh /usr/bin/miniperl. 5286e98a146SWarner Losh 529073113a4SWarner Losh20001005: 530073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 531685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 532073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 533073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 534073113a4SWarner Losh tree for anything to work. 535073113a4SWarner Losh 5360acc635eSWarner Losh20000928: 5370acc635eSWarner Losh There was a change in the passwd format. Need more information. 5380acc635eSWarner Losh 539be3885b3SWarner Losh20000916: 540be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 541be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 542be3885b3SWarner Losh same time as your kernel. 543be3885b3SWarner Losh 54476ec9675SWarner Losh20000914: 54576ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 54676ec9675SWarner Losh include the device will cause suspended laptops losing time 54776ec9675SWarner Losh when they resume. Include 54876ec9675SWarner Losh device pmtimer 54976ec9675SWarner Losh in your config file and 55001b9a434SWarner Losh hint.pmtimer.0.at="isa" 55176ec9675SWarner Losh to your /boot/device.hints file. 55276ec9675SWarner Losh 553f4865386SMark Murray20000911: 554f4865386SMark Murray The random device has been turned into a (pseudo-)device, 555f4865386SMark Murray rather than an option. The supplied kernel config files have 556f4865386SMark Murray been updated. You will need to do something similar in your 557f4865386SMark Murray own kernel config file. 558f4865386SMark Murray Remove: 559f4865386SMark Murray options RANDOMDEV 560f4865386SMark Murray Add: 561f4865386SMark Murray device random 562f4865386SMark Murray If you prefer to load the loadable module, you need to do 563f4865386SMark Murray nothing. 564f4865386SMark Murray 565d594498fSWarner Losh20000909: 566d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 567d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 568d594498fSWarner Losh reflect this if you load this module at boot time. 569d594498fSWarner Losh The line should read: 570d594498fSWarner Losh random_load="YES" 571d594498fSWarner Losh 5720deb7ddcSWarner Losh20000907: 5730deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 57416eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 57516eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 57616eb772dSWarner Losh sure you don't have model loading problems which might at 57716eb772dSWarner Losh first blush appear related to SMP. 57852bf24e7SWarner Losh 5795a01880bSWarner Losh20000906: 5805a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 5815a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 5825a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 5835a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 5845a01880bSWarner Losh don't have one, and you have host.conf. 5855a01880bSWarner Losh 5862b41163cSWarner Losh20000905: 58738d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 58838d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 58938d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 59038d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 59138d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 59238d6ecd2SWarner Losh 59338d6ecd2SWarner Losh20000905: 5948aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 5958aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 5968aab4bc7SWarner Losh is /boot/kernel. 5978aab4bc7SWarner Losh 5988aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 59938d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 60038d6ecd2SWarner Losh installkernel/installworld dance. 6012b41163cSWarner Losh 602d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 603d594498fSWarner Losh before booting the new kernel, since kldload will find stale 604d594498fSWarner Losh modules in that directory instead of finding them in the correct 605d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 606d594498fSWarner Losh is that the linux module crashes your machine after the update. 607d594498fSWarner Losh 608d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 609d594498fSWarner Losh mv /modules.old /boot/kernel.old 610d594498fSWarner Losh chflags noschg /kernel.old 611d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 612d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 613d594498fSWarner Losh fi 614d594498fSWarner Losh 615c22a309cSWarner Losh20000904: 616c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 617c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 618c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 619c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 620c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 621c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 622c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 623c22a309cSWarner Losh is not likely to be generated. 624c22a309cSWarner Losh 625fdb9f54dSWarner Losh20000825: 626fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 6279c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 6289c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 6299c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 6309c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 6319c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 6329c1a7444SWarner Losh messages will appear after the boot loader tries to start the 6339c1a7444SWarner Losh kernel. 6349c1a7444SWarner Losh 6359c1a7444SWarner Losh20000821: 6369c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 6379c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 6389c1a7444SWarner Losh /boot/loader.conf. 639fdb9f54dSWarner Losh 6408f250aa7SWarner Losh20000812: 6415da0d091SWarner Losh suidperl is now always built and installed on the system, but 6425da0d091SWarner Losh with permissions of 511. If you have applications that use 6435da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 6445da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 6455da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 6465da0d091SWarner Losh will fix this until the next build. 6475da0d091SWarner Losh 6485da0d091SWarner Losh20000812: 6498f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 6508f250aa7SWarner Losh visible changes that may immediately affect your configuration 6518f250aa7SWarner Losh include: 6528f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 6538f250aa7SWarner Losh - newaliases limited to root and trusted users 6548f250aa7SWarner Losh - MSA port (587) turned on by default 6558f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 6568f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 6578f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 6588f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 6598f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 6608f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 6618f250aa7SWarner Losh 66271c38472SWarner Losh20000810: 66371c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 66471c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 66571c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 66671c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 66771c38472SWarner Losh specific use for it. 66871c38472SWarner Losh 66971c38472SWarner Losh20000729: 67071c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 67171c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 67271c38472SWarner Losh /etc/rc.conf if they want to have the same setup 67371c38472SWarner Losh afterwards (unless the variables already are set, of course): 67471c38472SWarner Losh # Enable network daemons for user convenience. 67571c38472SWarner Losh inetd_enable="YES" 67671c38472SWarner Losh portmap_enable="YES" 67771c38472SWarner Losh sendmail_enable="YES" 67871c38472SWarner Losh 67971c38472SWarner Losh20000728: 68071c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 68171c38472SWarner Losh will need to change that to nullfs_load="YES". 68271c38472SWarner Losh 6831dece4a9SWarner Losh20000728: 6841dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 6851dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 6861dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 6871dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 6881dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 6891dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 6901dece4a9SWarner Losh to /MYKERNEL. 6911dece4a9SWarner Losh 692409e887cSWarner Losh20000711: 693409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 694409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 695409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 696409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 697409e887cSWarner Losh for details on potential problems that you might have and how 698409e887cSWarner Losh to get around them. 699409e887cSWarner Losh 700409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 701409e887cSWarner Losh clauses above, you needn't worry. 702409e887cSWarner Losh 703409e887cSWarner Losh20000711: 704409e887cSWarner Losh /etc/security has been updated to print the inode number of 705409e887cSWarner Losh setuid programs that have changed. You will see a large spike 706409e887cSWarner Losh in the number of changed programs the first time when you run 707409e887cSWarner Losh mergemaster to get a new /etc/security. 708409e887cSWarner Losh 709673d13f2SWarner Losh20000710: 710673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 711673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 712673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 713673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 714673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 715673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 716673d13f2SWarner Losh errors. (see below, 20000624). 717673d13f2SWarner Losh 718bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 7191dece4a9SWarner Losh 720673d13f2SWarner Losh20000709: 721c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 722c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 723c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 724673d13f2SWarner Losh ln -s aj /etc/malloc.conf 725673d13f2SWarner Losh 726e98e26cdSWarner Losh20000706: 727e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 728e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 729e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 730f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 731e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 7322c021c6cSMark Ovens interim if needed. 733e98e26cdSWarner Losh 734e98e26cdSWarner Losh20000705: 735e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 736e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 737e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 738e98e26cdSWarner Losh details. 739e98e26cdSWarner Losh 740c373950eSWarner Losh20000704: 7412f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 7422f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 7432f961bc8SWarner Losh 7442f961bc8SWarner Losh20000704: 745c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 746c373950eSWarner Losh or stop. This may cause some harmless warnings from older 747c373950eSWarner Losh rc.d scripts that haven't been updated. 748c373950eSWarner Losh 74927dc3a2bSWarner Losh20000630: 75027dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 75127dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 75227dc3a2bSWarner Losh which should be reported to des@freebsd.org. 75327dc3a2bSWarner Losh 754b8c215acSWarner Losh20000625: 755b8c215acSWarner Losh From approximately this date forward, one must have the crypto 75627dc3a2bSWarner Losh system installed in order to build the system and kernel. 75727dc3a2bSWarner Losh While not technically strictly true, one should treat it as 75827dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 75927dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 76027dc3a2bSWarner Losh were required. You should check with the latest collections 76127dc3a2bSWarner Losh to make sure that these haven't changed. 762b8c215acSWarner Losh 7637b990719SWarner Losh20000624: 7647b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 7657b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 7667b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 7671a33dba7SWarner Losh -CURRENT FROM THIS POINT to 2000710 for cryptographic services 7687b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 7697b990719SWarner Losh openssh and openssl should not be used to generate keys from this 7707b990719SWarner Losh date to the completion of the work. 7717b990719SWarner Losh 77227dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 77327dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 77427dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 77527dc3a2bSWarner Losh recreate the random and urandom devices. 77627dc3a2bSWarner Losh 77781e54c50SWarner Losh20000622: 77881e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 77981e54c50SWarner Losh BSD license. You may need to remove your symbolic links 78081e54c50SWarner Losh that used to be required when updating. 78181e54c50SWarner Losh 78239943833SWarner Losh20000621: 7832c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 7842a2f33fbSDaniel Baker the config file update procedure. 7852a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 786c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 787a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 78839943833SWarner Losh 789290f9ad8SWarner Losh20000620: 790290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 791290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 792290f9ad8SWarner Losh that workaround will no longer be required. 793290f9ad8SWarner Losh 79490fb6346SWarner Losh20000615: 79590fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 79690fb6346SWarner Losh ad driver. If you haven't done so already, you must update 79790fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 79890fb6346SWarner Losh devices. 79990fb6346SWarner Losh 800f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 801f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 802f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 803f75f65bbSWarner Losh may work). 804f75f65bbSWarner Losh 805ba26da8eSWarner Losh20000612: 806ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 807290f9ad8SWarner Losh on the topic before even thinking about updating. You will 808c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 809290f9ad8SWarner Losh to your config file to compile them in statically. The format 810f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 811f54a3542SWarner Losh NEWCARD for examples of the new format. 812290f9ad8SWarner Losh 8139698f2c0SWarner Losh Indirectly, this also breaks USERCONFIG. Unless a newer entry 8149698f2c0SWarner Losh says that it has been fixed, assume that must use the hints mechanism 8159698f2c0SWarner Losh in the loader if you need to use a machine with very old ISA cards 8169698f2c0SWarner Losh in it. 817bbcc5149SWarner Losh 818d65850ebSWarner Losh20000522: 819ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 820d65850ebSWarner Losh building a kernel after this point is advised that they need 821d65850ebSWarner Losh to rebuild their binutils (or better yet do a 822d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 823d65850ebSWarner Losh 824d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 825d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 826d9583a00SWarner Losh is recommended that you don't set this option until the problem 827d9583a00SWarner Losh is resolved. 828d9583a00SWarner Losh 8298039cedeSWarner Losh20000513: 8308039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 8318039cedeSWarner Losh 832d65850ebSWarner Losh20000510: 8338039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 8348039cedeSWarner Losh This will require some care in updating alphas. A new libstand 8358039cedeSWarner Losh is requires for the boot blocks to build properly. 8368039cedeSWarner Losh 8378039cedeSWarner Losh20000503: 8388039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 8398039cedeSWarner Losh is now available. 8408039cedeSWarner Losh 841d65850ebSWarner Losh20000502: 842d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 843d65850ebSWarner Losh connected to the kernel building instead. 844d65850ebSWarner Losh 845be149406SNik Clayton20000427: 8468039cedeSWarner Losh You may need to build gperf 8478039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 8488039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 8498039cedeSWarner Losh an option only in -current. 8508039cedeSWarner Losh 8512b8dd5f4SWarner Losh20000417: 8522b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 853f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 8542b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 8552b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 8562c021c6cSMark Ovens before you reboot, you'll need to issue: 8572b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 8582b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 8592b8dd5f4SWarner Losh 8608d9f1945SWarner Losh20000320: 8612b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 8622b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 8632b8dd5f4SWarner Losh cope if you have a problem combination is to add: 864ae20a1b8SDima Dorfman /sbin/sysctl hw.ata.ata_dma=0 8652b8dd5f4SWarner Losh to the start of /etc/rc.conf. 8668d9f1945SWarner Losh 867f8ab1dd6SWarner Losh20000319: 868f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 869f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 870f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 871f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 872f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 873f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 874f8ab1dd6SWarner Losh 87519cada77SWarner Losh20000318: 876f699bbbbSMark Ovens We've entered the traditional post release dumping party. 87719cada77SWarner Losh Large kernel changes are being committed and are in the 87819cada77SWarner Losh works. It is important to keep the systems' klds and kernel 87919cada77SWarner Losh in sync as kernel interfaces and structures are changing. 88019cada77SWarner Losh Before reporting kernel panics, make sure that all modules 88119cada77SWarner Losh that you are loading are up to date. 882ba228352SWarner Losh 88319cada77SWarner Losh20000315: 8846d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 8856d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 8866d23c382SWarner Losh will do the trick. This isn't critical until you remove your 8876d23c382SWarner Losh wd device entries in /dev, at which point your system will not 8886d23c382SWarner Losh boot. 8896d23c382SWarner Losh 8906d23c382SWarner Losh20000315: 89119cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 89219cada77SWarner Losh to upgrade to 4.0 from 3.x. 89357199806SWarner Losh 894dc0dbf5cSWarner LoshCOMMON ITEMS: 895dc0dbf5cSWarner Losh 896a24eff53SWarner Losh General Notes 897a24eff53SWarner Losh ------------- 898a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 899a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 900a24eff53SWarner Losh installworld. This is especially true when upgrading between 901a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 902a24eff53SWarner Losh or several minor releases, or when several months have passed 903a24eff53SWarner Losh on the -current branch). 904a24eff53SWarner Losh 9055780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 9065780f3baSWarner Losh poisoning. This can happen because the make utility reads its 9075780f3baSWarner Losh environment when searching for values for global variables. 9085780f3baSWarner Losh To run your build attempts in an "environmental clean room", 9095780f3baSWarner Losh prefix all make commands with 'env -i '. See the env(1) manual 9105780f3baSWarner Losh page for more details. 9115780f3baSWarner Losh 912dc0dbf5cSWarner Losh To build a kernel 913dc0dbf5cSWarner Losh ----------------- 914ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 915f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 916ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 9171e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 9181e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 919dc0dbf5cSWarner Losh 920ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 921ba01eb20SWarner Losh -------------------------------------------------------------- 922ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 92347d0d01fSWarner Losh config KERNEL_NAME_HERE 924ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 925ba01eb20SWarner Losh make depend 926ba01eb20SWarner Losh make 927ba01eb20SWarner Losh make install 928ba01eb20SWarner Losh 929ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 930ba01eb20SWarner Losh 931ba01eb20SWarner Losh To rebuild everything and install it on the current system. 932ba01eb20SWarner Losh ----------------------------------------------------------- 933759f0aefSWarner Losh make world 934fdb9f54dSWarner Losh Build a new kernel, see above. 935759f0aefSWarner Losh 9361dece4a9SWarner Losh To upgrade from 4.x-stable to current 937ba26da8eSWarner Losh ------------------------------------- 938ba26da8eSWarner Losh make buildworld 9391e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 9407595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 941f6a0ef01SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE [6] 942ee6e1fc3SWarner Losh reboot in single user [3] 943835284beSWarner Losh mergemaster -p [5] 944ba26da8eSWarner Losh make installworld 945a6cd4f9dSWarner Losh mergemaster [4] 946134d2e86SWarner Losh [1] 947ba26da8eSWarner Losh <reboot> 948ba26da8eSWarner Losh 949fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 950fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 951fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 952fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 953fdb9f54dSWarner Losh the UPDATING entries. 954ba26da8eSWarner Losh 9551dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 9561dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 9571dece4a9SWarner Losh your sources that you have read and understood all the recent 9581dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 9591dece4a9SWarner Losh much fewer pitfalls. 9601dece4a9SWarner Losh 961134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 962134d2e86SWarner Losh should disable them at this point so they don't crash your 963134d2e86SWarner Losh system on reboot. 964134d2e86SWarner Losh 9659c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 9669c1a7444SWarner Losh your own device.hints to reflect your unique hardware 9679c1a7444SWarner Losh configuration. 9689c1a7444SWarner Losh 969ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 970ee6e1fc3SWarner Losh fsck -p 971ee6e1fc3SWarner Losh mount -u / 972ee6e1fc3SWarner Losh mount -a 973ee6e1fc3SWarner Losh cd /usr/src 97447d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 975f6a0ef01SWarner Losh Also, when doing a major release upgrade, it is required that 976f6a0ef01SWarner Losh you boot into single user mode to do the installworld. 977ee6e1fc3SWarner Losh 978a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 979a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 980a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 981a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 982a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 983a6cd4f9dSWarner Losh for potential gotchas. 984a6cd4f9dSWarner Losh 985835284beSWarner Losh [5] Usually this step is a noop. However, from time to time 986835284beSWarner Losh you may need to do this if you get unknown user in the following 987835284beSWarner Losh step. It never hurts to do it all the time. You may need to 988835284beSWarner Losh install a new mergemaster (cd src/usr.sbin/mergemaster && make 989835284beSWarner Losh install) after the buildworld before this step if you last updated 990835284beSWarner Losh from current before 20020224 or from -stable before 20020408. 991835284beSWarner Losh 992f6a0ef01SWarner Losh [6] You may get a warning from kldxref. Ignore it. It doesn't 993f6a0ef01SWarner Losh matter. 994f6a0ef01SWarner Losh 995dc0dbf5cSWarner LoshFORMAT: 996dc0dbf5cSWarner Losh 997f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 9981fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 999f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 1000f8ab1dd6SWarner Loshprevious releases if your system is older than this. 10011fc1a0dcSWarner Losh 1002e72fd46aSWarner LoshCopyright information: 1003e72fd46aSWarner Losh 10049698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1005e72fd46aSWarner Losh 1006772730c7SWarner LoshRedistribution, publication, translation and use, with or without 1007772730c7SWarner Loshmodification, in full or in part, in any form or format of this 10089698f2c0SWarner Loshdocument are permitted without further permission from the author. 1009e72fd46aSWarner Losh 1010e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1011e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1012e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1013e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1014e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1015e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1016e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1017e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1018e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1019e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1020e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 1021e72fd46aSWarner Losh 1022e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 1023e72fd46aSWarner Loshauthor a beer. 1024e72fd46aSWarner Losh 102522306abcSWarner LoshContact Warner Losh if you have any questions about your use of 1026772730c7SWarner Loshthis document. 1027772730c7SWarner Losh 102897d92980SPeter Wemm$FreeBSD$ 1029