157199806SWarner LoshUpdating Information for FreeBSD current users 253dfde79SWarner Losh 3f8c77507SWarner LoshThis file is maintained by imp@village.org. Please send new entries 4dc0dbf5cSWarner Loshdirectly to him. See end of file for further details. For commonly 516de1a07SWarner Loshdone items, please see the end of the file. Search for 'COMMON 616de1a07SWarner LoshITEMS:' 716de1a07SWarner Losh 8ed0f29caSWarner Losh20010521: 9ed0f29caSWarner Losh Minor repo damanged has happened. This may cause problems 10ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 11ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 12ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 13ed0f29caSWarner Losh is 14ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 15ed0f29caSWarner Losh 1680c16af9SWarner Losh20010520: 1780c16af9SWarner Losh Swapping is busted on -current. Please be patient. 1880c16af9SWarner Losh 1980c16af9SWarner Losh20010519: 2080c16af9SWarner Losh pccard has had much reorganizational work done to it over 2180c16af9SWarner Losh the past few days. Everything should still work, but if 2280c16af9SWarner Losh not, please contact imp@freebsd.org. 2380c16af9SWarner Losh 24a45f2d05SWarner Losh20010517: 25a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 26a45f2d05SWarner Losh userland at the same time. 27a45f2d05SWarner Losh 28a45f2d05SWarner Losh20010517: 29a45f2d05SWarner Losh New ncurses imported. 30a45f2d05SWarner Losh 312988afcaSWarner Losh20010512: 322988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 332988afcaSWarner Losh will be the only way to go starting July 1. 342988afcaSWarner Losh 3509946a51SWarner Losh20010502: 3609946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 3709946a51SWarner Losh 3809946a51SWarner Losh20010501: 3909946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 4009946a51SWarner Losh 4109946a51SWarner Losh20010430: 42a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 4309946a51SWarner Losh go back in the water. 4409946a51SWarner Losh 4509946a51SWarner Losh20010429: 4609946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 4709946a51SWarner Losh this date, but before the correction date. 4809946a51SWarner Losh 4991dd3b53SWarner Losh20010423: 5091dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 5191dd3b53SWarner Losh 5291dd3b53SWarner Losh20010411: 5391dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 5491dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 5591dd3b53SWarner Losh Update only if you understand that you must not use the old 5691dd3b53SWarner Losh fsck with the new kernel ever. 5791dd3b53SWarner Losh 58933b3269SWarner Losh20010330: 59933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 60933b3269SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page fora 61933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 62933b3269SWarner Losh 63933b3269SWarner Losh20010319: 64933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 65933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 66933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 6709946a51SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netcofnig. 6809946a51SWarner Losh 6909946a51SWarner Losh20010315: 7009946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 7109946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 7209946a51SWarner Losh been replaced by tunables. See ata.4 for details. 73933b3269SWarner Losh 74933b3269SWarner Losh20010312: 75933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 76933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 77933b3269SWarner Losh 78933b3269SWarner Losh20010312: 79933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 80933b3269SWarner Losh instead of ad-hoc. 81933b3269SWarner Losh 82933b3269SWarner Losh20010310: 83933b3269SWarner Losh /dev/urandmon should be a sumbolic link to /dev/random now. 84933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 85933b3269SWarner Losh ssh might not work if you don't. 86933b3269SWarner Losh 87d325cf65SWarner Losh20010220: 88d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 89d325cf65SWarner Losh safe to go back into the water. 90d325cf65SWarner Losh 91024daae6SWarner Losh20010211: 92024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 93024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 94024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 95024daae6SWarner Losh that before upgrading would be a good time to do a level 0 96024daae6SWarner Losh dump of your system. No, really, I mean it this time. 97024daae6SWarner Losh 98024daae6SWarner Losh To get to the new system, you'll need to use the following 99024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 100024daae6SWarner Losh don't have to move this to the updating section. 101024daae6SWarner Losh 102024daae6SWarner Losh To get around the installworld problem, do: 103024daae6SWarner Losh # cd /usr/src/usr.bin/sed 104024daae6SWarner Losh # make install 105024daae6SWarner Losh # cd /usr/src 106024daae6SWarner Losh # make installworld 107024daae6SWarner Losh If that doesn't work, then try: 108024daae6SWarner Losh # make -k installworld 109024daae6SWarner Losh # make installworld 110024daae6SWarner Losh 111024daae6SWarner Losh20010207: 112024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 113024daae6SWarner Losh do not include devfs in your kernel as problems result. 114024daae6SWarner Losh 115024daae6SWarner Losh20010205: 1167595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 117024daae6SWarner Losh Remove them from your config. 118024daae6SWarner Losh 1191e159248SWarner Losh20010122: 1201e159248SWarner Losh ****************************** WARNING ****************************** 1211e159248SWarner Losh buildkernel has been changed slightly 1221e159248SWarner Losh ****************************** WARNING ****************************** 1231e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 1241e159248SWarner Losh should update your scripts and make.conf accordingly. 1251e159248SWarner Losh 1261e159248SWarner Losh20010119: 1271e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 1281e159248SWarner Losh This requires a new config to build correctly. 1291e159248SWarner Losh 130aac7dfeaSWarner Losh20010116: 131aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 132aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 133aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 134aac7dfeaSWarner Losh 135aac7dfeaSWarner Losh20010110: 136aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 137aac7dfeaSWarner Losh 138aac7dfeaSWarner Losh20010102: 139aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 140aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 141aac7dfeaSWarner Losh 14263c90c9eSWarner Losh20010101: 14363c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 14463c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 1455fd2a895SWarner Losh dump while building termcap. You can work around this problem 14663c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 14763c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 14863c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 14963c90c9eSWarner Losh might have been ignored by the -k option. 15063c90c9eSWarner Losh 1515fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 1525fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 1535fd2a895SWarner Losh of this working. 1545fd2a895SWarner Losh 155aac7dfeaSWarner Losh20001228: 156aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 157aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 158aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 159aac7dfeaSWarner Losh 160de2bcc63SWarner Losh20001218: 161de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 162de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 163de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 164de2bcc63SWarner Losh cards will not be recognized without it. 165de2bcc63SWarner Losh 166960773f7SWarner Losh20001205: 167960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 168960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 169960773f7SWarner Losh adding the following in pam.conf: 170960773f7SWarner Losh 171960773f7SWarner Losh sshd auth sufficient pam_skey.so 172960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 173960773f7SWarner Losh sshd session required pam_permit.so 174960773f7SWarner Losh 1750acc635eSWarner Losh20001031: 1760acc635eSWarner Losh cvs updated to 1.11. 1770acc635eSWarner Losh 1780acc635eSWarner Losh20001020: 1790acc635eSWarner Losh The random device needs more entropy, so you need to make sure 1800acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 1810acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 1820acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 1830acc635eSWarner Losh workaround. 1840acc635eSWarner Losh 1850acc635eSWarner Losh20001010: 1860acc635eSWarner Losh ****************************** WARNING ****************************** 1870acc635eSWarner Losh Sendmail has been updated. 1880acc635eSWarner Losh ****************************** WARNING ****************************** 1890acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 1900acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 1910acc635eSWarner Losh is set. 1920acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 1930acc635eSWarner Losh commands. 1940acc635eSWarner Losh o Now using sendmail's version of vacation(1). 1950acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 1960acc635eSWarner Losh in /usr/share/sendmail/cf. 1970acc635eSWarner Losh o sendmail.cw changed to local-host-names 1980acc635eSWarner Losh 1990acc635eSWarner Losh More details can be found at 2000acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 2010acc635eSWarner Losh 2026e98a146SWarner Losh20001009: 2036e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 2046e98a146SWarner Losh your entire ports tree, or you will have problems. 2056e98a146SWarner Losh 2066e98a146SWarner Losh20001006: 207685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 2086e98a146SWarner Losh the installed miniperl. It is recommended that you delete 2096e98a146SWarner Losh /usr/bin/miniperl. 2106e98a146SWarner Losh 211073113a4SWarner Losh20001005: 212073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 213685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 214073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 215073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 216073113a4SWarner Losh tree for anything to work. 217073113a4SWarner Losh 2180acc635eSWarner Losh20000928: 2190acc635eSWarner Losh There was a change in the passwd format. Need more information. 2200acc635eSWarner Losh 221be3885b3SWarner Losh20000916: 222be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 223be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 224be3885b3SWarner Losh same time as your kernel. 225be3885b3SWarner Losh 22676ec9675SWarner Losh20000914: 22776ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 22876ec9675SWarner Losh include the device will cause suspended laptops losing time 22976ec9675SWarner Losh when they resume. Include 23076ec9675SWarner Losh device pmtimer 23176ec9675SWarner Losh in your config file and 23201b9a434SWarner Losh hint.pmtimer.0.at="isa" 23376ec9675SWarner Losh to your /boot/device.hints file. 23476ec9675SWarner Losh 235f4865386SMark Murray20000911: 236f4865386SMark Murray The random device has been turned into a (pseudo-)device, 237f4865386SMark Murray rather than an option. The supplied kernel config files have 238f4865386SMark Murray been updated. You will need to do something similar in your 239f4865386SMark Murray own kernel config file. 240f4865386SMark Murray Remove: 241f4865386SMark Murray options RANDOMDEV 242f4865386SMark Murray Add: 243f4865386SMark Murray device random 244f4865386SMark Murray If you prefer to load the loadable module, you need to do 245f4865386SMark Murray nothing. 246f4865386SMark Murray 247d594498fSWarner Losh20000909: 248d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 249d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 250d594498fSWarner Losh reflect this if you load this module at boot time. 251d594498fSWarner Losh The line should read: 252d594498fSWarner Losh random_load="YES" 253d594498fSWarner Losh 2540deb7ddcSWarner Losh20000907: 2550deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 25616eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 25716eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 25816eb772dSWarner Losh sure you don't have model loading problems which might at 25916eb772dSWarner Losh first blush appear related to SMP. 26052bf24e7SWarner Losh 2615a01880bSWarner Losh20000906: 2625a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 2635a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 2645a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 2655a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 2665a01880bSWarner Losh don't have one, and you have host.conf. 2675a01880bSWarner Losh 2682b41163cSWarner Losh20000905: 26938d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 27038d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 27138d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 27238d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 27338d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 27438d6ecd2SWarner Losh 27538d6ecd2SWarner Losh20000905: 2768aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 2778aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 2788aab4bc7SWarner Losh is /boot/kernel. 2798aab4bc7SWarner Losh 2808aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 28138d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 28238d6ecd2SWarner Losh installkernel/installworld dance. 2832b41163cSWarner Losh 284d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 285d594498fSWarner Losh before booting the new kernel, since kldload will find stale 286d594498fSWarner Losh modules in that directory instead of finding them in the correct 287d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 288d594498fSWarner Losh is that the linux module crashes your machine after the update. 289d594498fSWarner Losh 290d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 291d594498fSWarner Losh mv /modules.old /boot/kernel.old 292d594498fSWarner Losh chflags noschg /kernel.old 293d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 294d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 295d594498fSWarner Losh fi 296d594498fSWarner Losh 297c22a309cSWarner Losh20000904: 298c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 299c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 300c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 301c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 302c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 303c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 304c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 305c22a309cSWarner Losh is not likely to be generated. 306c22a309cSWarner Losh 307fdb9f54dSWarner Losh20000825: 308fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 3099c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 3109c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 3119c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 3129c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 3139c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 3149c1a7444SWarner Losh messages will appear after the boot loader tries to start the 3159c1a7444SWarner Losh kernel. 3169c1a7444SWarner Losh 3179c1a7444SWarner Losh20000821: 3189c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 3199c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 3209c1a7444SWarner Losh /boot/loader.conf. 321fdb9f54dSWarner Losh 3228f250aa7SWarner Losh20000812: 3235da0d091SWarner Losh suidperl is now always built and installed on the system, but 3245da0d091SWarner Losh with permissions of 511. If you have applications that use 3255da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 3265da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 3275da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 3285da0d091SWarner Losh will fix this until the next build. 3295da0d091SWarner Losh 3305da0d091SWarner Losh20000812: 3318f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 3328f250aa7SWarner Losh visible changes that may immediately affect your configuration 3338f250aa7SWarner Losh include: 3348f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 3358f250aa7SWarner Losh - newaliases limited to root and trusted users 3368f250aa7SWarner Losh - MSA port (587) turned on by default 3378f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 3388f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 3398f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 3408f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 3418f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 3428f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 3438f250aa7SWarner Losh 34471c38472SWarner Losh20000810: 34571c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 34671c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 34771c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 34871c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 34971c38472SWarner Losh specific use for it. 35071c38472SWarner Losh 35171c38472SWarner Losh20000729: 35271c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 35371c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 35471c38472SWarner Losh /etc/rc.conf if they want to have the same setup 35571c38472SWarner Losh afterwards (unless the variables already are set, of course): 35671c38472SWarner Losh # Enable network daemons for user convenience. 35771c38472SWarner Losh inetd_enable="YES" 35871c38472SWarner Losh portmap_enable="YES" 35971c38472SWarner Losh sendmail_enable="YES" 36071c38472SWarner Losh 36171c38472SWarner Losh20000728: 36271c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 36371c38472SWarner Losh will need to change that to nullfs_load="YES". 36471c38472SWarner Losh 3651dece4a9SWarner Losh20000728: 3661dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 3671dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 3681dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 3691dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 3701dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 3711dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 3721dece4a9SWarner Losh to /MYKERNEL. 3731dece4a9SWarner Losh 374409e887cSWarner Losh20000711: 375409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 376409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 377409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 378409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 379409e887cSWarner Losh for details on potential problems that you might have and how 380409e887cSWarner Losh to get around them. 381409e887cSWarner Losh 382409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 383409e887cSWarner Losh clauses above, you needn't worry. 384409e887cSWarner Losh 385409e887cSWarner Losh20000711: 386409e887cSWarner Losh /etc/security has been updated to print the inode number of 387409e887cSWarner Losh setuid programs that have changed. You will see a large spike 388409e887cSWarner Losh in the number of changed programs the first time when you run 389409e887cSWarner Losh mergemaster to get a new /etc/security. 390409e887cSWarner Losh 391673d13f2SWarner Losh20000710: 392673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 393673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 394673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 395673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 396673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 397673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 398673d13f2SWarner Losh errors. (see below, 20000624). 399673d13f2SWarner Losh 400bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 4011dece4a9SWarner Losh 402673d13f2SWarner Losh20000709: 403c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 404c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 405c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 406673d13f2SWarner Losh ln -s aj /etc/malloc.conf 407673d13f2SWarner Losh 408e98e26cdSWarner Losh20000706: 409e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 410e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 411e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 412f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 413e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 4142c021c6cSMark Ovens interim if needed. 415e98e26cdSWarner Losh 416e98e26cdSWarner Losh20000705: 417e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 418e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 419e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 420e98e26cdSWarner Losh details. 421e98e26cdSWarner Losh 422c373950eSWarner Losh20000704: 4232f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 4242f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 4252f961bc8SWarner Losh 4262f961bc8SWarner Losh20000704: 427c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 428c373950eSWarner Losh or stop. This may cause some harmless warnings from older 429c373950eSWarner Losh rc.d scripts that haven't been updated. 430c373950eSWarner Losh 43127dc3a2bSWarner Losh20000630: 43227dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 43327dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 43427dc3a2bSWarner Losh which should be reported to des@freebsd.org. 43527dc3a2bSWarner Losh 436b8c215acSWarner Losh20000625: 437b8c215acSWarner Losh From approximately this date forward, one must have the crypto 43827dc3a2bSWarner Losh system installed in order to build the system and kernel. 43927dc3a2bSWarner Losh While not technically strictly true, one should treat it as 44027dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 44127dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 44227dc3a2bSWarner Losh were required. You should check with the latest collections 44327dc3a2bSWarner Losh to make sure that these haven't changed. 444b8c215acSWarner Losh 4457b990719SWarner Losh20000624: 4467b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 4477b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 4487b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 4497b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 4507b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 4517b990719SWarner Losh openssh and openssl should not be used to generate keys from this 4527b990719SWarner Losh date to the completion of the work. 4537b990719SWarner Losh 45427dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 45527dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 45627dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 45727dc3a2bSWarner Losh recreate the random and urandom devices. 45827dc3a2bSWarner Losh 45981e54c50SWarner Losh20000622: 46081e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 46181e54c50SWarner Losh BSD license. You may need to remove your symbolic links 46281e54c50SWarner Losh that used to be required when updating. 46381e54c50SWarner Losh 46439943833SWarner Losh20000621: 4652c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 4662a2f33fbSDaniel Baker the config file update procedure. 4672a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 468c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 469a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 47039943833SWarner Losh 471290f9ad8SWarner Losh20000620: 472290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 473290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 474290f9ad8SWarner Losh that workaround will no longer be required. 475290f9ad8SWarner Losh 47690fb6346SWarner Losh20000615: 47790fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 47890fb6346SWarner Losh ad driver. If you haven't done so already, you must update 47990fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 48090fb6346SWarner Losh devices. 48190fb6346SWarner Losh 482f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 483f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 484f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 485f75f65bbSWarner Losh may work). 486f75f65bbSWarner Losh 487ba26da8eSWarner Losh20000612: 488ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 489290f9ad8SWarner Losh on the topic before even thinking about updating. You will 490c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 491290f9ad8SWarner Losh to your config file to compile them in statically. The format 492f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 493f54a3542SWarner Losh NEWCARD for examples of the new format. 494290f9ad8SWarner Losh 495d65850ebSWarner Losh20000522: 496ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 497d65850ebSWarner Losh building a kernel after this point is advised that they need 498d65850ebSWarner Losh to rebuild their binutils (or better yet do a 499d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 500d65850ebSWarner Losh 501d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 502d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 503d9583a00SWarner Losh is recommended that you don't set this option until the problem 504d9583a00SWarner Losh is resolved. 505d9583a00SWarner Losh 5068039cedeSWarner Losh20000513: 5078039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 5088039cedeSWarner Losh 509d65850ebSWarner Losh20000510: 5108039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 5118039cedeSWarner Losh This will require some care in updating alphas. A new libstand 5128039cedeSWarner Losh is requires for the boot blocks to build properly. 5138039cedeSWarner Losh 5148039cedeSWarner Losh20000503: 5158039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 5168039cedeSWarner Losh is now available. 5178039cedeSWarner Losh 518d65850ebSWarner Losh20000502: 519d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 520d65850ebSWarner Losh connected to the kernel building instead. 521d65850ebSWarner Losh 522be149406SNik Clayton20000427: 5238039cedeSWarner Losh You may need to build gperf 5248039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 5258039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 5268039cedeSWarner Losh an option only in -current. 5278039cedeSWarner Losh 5282b8dd5f4SWarner Losh20000417: 5292b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 530f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 5312b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 5322b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 5332c021c6cSMark Ovens before you reboot, you'll need to issue: 5342b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 5352b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 5362b8dd5f4SWarner Losh 5378d9f1945SWarner Losh20000320: 5382b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 5392b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 5402b8dd5f4SWarner Losh cope if you have a problem combination is to add: 5418d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 5422b8dd5f4SWarner Losh to the start of /etc/rc.conf. 5438d9f1945SWarner Losh 544f8ab1dd6SWarner Losh20000319: 545f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 546f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 547f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 548f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 549f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 550f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 551f8ab1dd6SWarner Losh 55219cada77SWarner Losh20000318: 553f699bbbbSMark Ovens We've entered the traditional post release dumping party. 55419cada77SWarner Losh Large kernel changes are being committed and are in the 55519cada77SWarner Losh works. It is important to keep the systems' klds and kernel 55619cada77SWarner Losh in sync as kernel interfaces and structures are changing. 55719cada77SWarner Losh Before reporting kernel panics, make sure that all modules 55819cada77SWarner Losh that you are loading are up to date. 559ba228352SWarner Losh 56019cada77SWarner Losh20000315: 5616d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 5626d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 5636d23c382SWarner Losh will do the trick. This isn't critical until you remove your 5646d23c382SWarner Losh wd device entries in /dev, at which point your system will not 5656d23c382SWarner Losh boot. 5666d23c382SWarner Losh 5676d23c382SWarner Losh20000315: 56819cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 56919cada77SWarner Losh to upgrade to 4.0 from 3.x. 57057199806SWarner Losh 571dc0dbf5cSWarner LoshCOMMON ITEMS: 572dc0dbf5cSWarner Losh 573a24eff53SWarner Losh General Notes 574a24eff53SWarner Losh ------------- 575a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 576a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 577a24eff53SWarner Losh installworld. This is especially true when upgrading between 578a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 579a24eff53SWarner Losh or several minor releases, or when several months have passed 580a24eff53SWarner Losh on the -current branch). 581a24eff53SWarner Losh 582dc0dbf5cSWarner Losh To build a kernel 583dc0dbf5cSWarner Losh ----------------- 584ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 585f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 586ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 5871e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 5881e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 589dc0dbf5cSWarner Losh 590ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 591ba01eb20SWarner Losh -------------------------------------------------------------- 592ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 593ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 594ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 595ba01eb20SWarner Losh make depend 596ba01eb20SWarner Losh make 597ba01eb20SWarner Losh make install 598ba01eb20SWarner Losh 599ba01eb20SWarner Losh [1] If in doubt, -r might help here. 600ba01eb20SWarner Losh 601ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 602ba01eb20SWarner Losh 603ba01eb20SWarner Losh To rebuild everything and install it on the current system. 604ba01eb20SWarner Losh ----------------------------------------------------------- 605759f0aefSWarner Losh make world 606fdb9f54dSWarner Losh Build a new kernel, see above. 607759f0aefSWarner Losh 6081dece4a9SWarner Losh To upgrade from 4.x-stable to current 609ba26da8eSWarner Losh ------------------------------------- 610ba26da8eSWarner Losh make buildworld 6111e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 6127595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 6131e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 614ba26da8eSWarner Losh make installworld 6157595222aSWarner Losh mergemaster 616134d2e86SWarner Losh [1] 617ba26da8eSWarner Losh <reboot> 618ba26da8eSWarner Losh 619fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 620fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 621fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 622fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 623fdb9f54dSWarner Losh the UPDATING entries. 624ba26da8eSWarner Losh 6251dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 6261dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 6271dece4a9SWarner Losh your sources that you have read and understood all the recent 6281dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 6291dece4a9SWarner Losh much fewer pitfalls. 6301dece4a9SWarner Losh 631134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 632134d2e86SWarner Losh should disable them at this point so they don't crash your 633134d2e86SWarner Losh system on reboot. 634134d2e86SWarner Losh 6359c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 6369c1a7444SWarner Losh your own device.hints to reflect your unique hardware 6379c1a7444SWarner Losh configuration. 6389c1a7444SWarner Losh 639dc0dbf5cSWarner LoshFORMAT: 640dc0dbf5cSWarner Losh 641f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 6421fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 643f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 644f8ab1dd6SWarner Loshprevious releases if your system is older than this. 6451fc1a0dcSWarner Losh 6463645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 6473645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 648f8c77507SWarner Losh 64997d92980SPeter Wemm$FreeBSD$ 650