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 80d415dffSWarner Losh20010617: 90d415dffSWarner Losh It appears that soft updates are working again. 100d415dffSWarner Losh 110d415dffSWarner Losh20010614: 120d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 130d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 140d415dffSWarner Losh kernel building methods. 150d415dffSWarner Losh 168b9959adSWarner Losh20010613: 178b9959adSWarner Losh Two items that have been biting people: 188b9959adSWarner Losh 198b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 208b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 218b9959adSWarner Losh config ala the 20010604 entry, or you will have problems (this issue 228b9959adSWarner Losh will be fixed, it just hasn't been yet). 238b9959adSWarner Losh 248b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 258b9959adSWarner Losh use them in current. Resolution unknown. 268b9959adSWarner Losh 270d415dffSWarner Losh20010612: 280d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 290d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 300d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 310d415dffSWarner Losh work around this issue, please use only one or the other mechanism 320d415dffSWarner Losh until this bug is fixed. 330d415dffSWarner Losh 340d415dffSWarner Losh20010610: 350d415dffSWarner Losh Locale names have changed to match other systems better. 360d415dffSWarner Losh 376ccdb5e4SWarner Losh20010604: 386ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 396ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 406ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 413590182eSWarner Losh Interrupt storms look a lot like a hang. 423590182eSWarner Losh 433590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 443590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 453590182eSWarner Losh it is). 463590182eSWarner Losh 473590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 483590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 493590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 503590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 516ccdb5e4SWarner Losh 520bc62786SWarner Losh20010530: 530bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 540bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 550bc62786SWarner Losh a limited time. If you see 560bc62786SWarner Losh 570bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 580bc62786SWarner Losh 590bc62786SWarner Losh in your makeworld, then you need to migrate towards using 600bc62786SWarner Losh COPY=-C. 610bc62786SWarner Losh 6268a38c6cSWarner Losh20010525: 63b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 64c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 65c4f4a728SWarner Losh definitely is in bad shape. 6668a38c6cSWarner Losh 67ed0f29caSWarner Losh20010521: 68ed0f29caSWarner Losh Minor repo damanged has happened. This may cause problems 69ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 70ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 71ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 72ed0f29caSWarner Losh is 73ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 74ed0f29caSWarner Losh 7580c16af9SWarner Losh20010520: 7668a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 7780c16af9SWarner Losh 7880c16af9SWarner Losh20010519: 7980c16af9SWarner Losh pccard has had much reorganizational work done to it over 8080c16af9SWarner Losh the past few days. Everything should still work, but if 8180c16af9SWarner Losh not, please contact imp@freebsd.org. 8280c16af9SWarner Losh 83a45f2d05SWarner Losh20010517: 84a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 85a45f2d05SWarner Losh userland at the same time. 86a45f2d05SWarner Losh 87a45f2d05SWarner Losh20010517: 88a45f2d05SWarner Losh New ncurses imported. 89a45f2d05SWarner Losh 902988afcaSWarner Losh20010512: 912988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 922988afcaSWarner Losh will be the only way to go starting July 1. 932988afcaSWarner Losh 9409946a51SWarner Losh20010502: 9509946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 9609946a51SWarner Losh 9709946a51SWarner Losh20010501: 9809946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 9909946a51SWarner Losh 10009946a51SWarner Losh20010430: 101a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 10209946a51SWarner Losh go back in the water. 10309946a51SWarner Losh 10409946a51SWarner Losh20010429: 10509946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 10609946a51SWarner Losh this date, but before the correction date. 10709946a51SWarner Losh 10891dd3b53SWarner Losh20010423: 10991dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 11091dd3b53SWarner Losh 11191dd3b53SWarner Losh20010411: 11291dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 11391dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 11491dd3b53SWarner Losh Update only if you understand that you must not use the old 11591dd3b53SWarner Losh fsck with the new kernel ever. 11691dd3b53SWarner Losh 117933b3269SWarner Losh20010330: 118933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 119c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 120933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 121933b3269SWarner Losh 122933b3269SWarner Losh20010319: 123933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 124933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 125933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 12609946a51SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netcofnig. 12709946a51SWarner Losh 12809946a51SWarner Losh20010315: 12909946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 13009946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 13109946a51SWarner Losh been replaced by tunables. See ata.4 for details. 132933b3269SWarner Losh 133933b3269SWarner Losh20010312: 134933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 135933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 136933b3269SWarner Losh 137933b3269SWarner Losh20010312: 138933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 139933b3269SWarner Losh instead of ad-hoc. 140933b3269SWarner Losh 141933b3269SWarner Losh20010310: 142f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 143933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 144933b3269SWarner Losh ssh might not work if you don't. 145933b3269SWarner Losh 146d325cf65SWarner Losh20010220: 147d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 148d325cf65SWarner Losh safe to go back into the water. 149d325cf65SWarner Losh 150024daae6SWarner Losh20010211: 151024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 152024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 153024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 154024daae6SWarner Losh that before upgrading would be a good time to do a level 0 155024daae6SWarner Losh dump of your system. No, really, I mean it this time. 156024daae6SWarner Losh 157024daae6SWarner Losh To get to the new system, you'll need to use the following 158024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 159024daae6SWarner Losh don't have to move this to the updating section. 160024daae6SWarner Losh 161024daae6SWarner Losh To get around the installworld problem, do: 162024daae6SWarner Losh # cd /usr/src/usr.bin/sed 163024daae6SWarner Losh # make install 164024daae6SWarner Losh # cd /usr/src 165024daae6SWarner Losh # make installworld 166024daae6SWarner Losh If that doesn't work, then try: 167024daae6SWarner Losh # make -k installworld 168024daae6SWarner Losh # make installworld 169024daae6SWarner Losh 170024daae6SWarner Losh20010207: 171024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 172024daae6SWarner Losh do not include devfs in your kernel as problems result. 173024daae6SWarner Losh 174024daae6SWarner Losh20010205: 1757595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 176024daae6SWarner Losh Remove them from your config. 177024daae6SWarner Losh 1781e159248SWarner Losh20010122: 1791e159248SWarner Losh ****************************** WARNING ****************************** 1801e159248SWarner Losh buildkernel has been changed slightly 1811e159248SWarner Losh ****************************** WARNING ****************************** 1821e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 1831e159248SWarner Losh should update your scripts and make.conf accordingly. 1841e159248SWarner Losh 1851e159248SWarner Losh20010119: 1861e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 1871e159248SWarner Losh This requires a new config to build correctly. 1881e159248SWarner Losh 189aac7dfeaSWarner Losh20010116: 190aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 191aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 192aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 193aac7dfeaSWarner Losh 194aac7dfeaSWarner Losh20010110: 195aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 196aac7dfeaSWarner Losh 197aac7dfeaSWarner Losh20010102: 198aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 199aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 200aac7dfeaSWarner Losh 20163c90c9eSWarner Losh20010101: 20263c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 20363c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 2045fd2a895SWarner Losh dump while building termcap. You can work around this problem 20563c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 20663c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 20763c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 20863c90c9eSWarner Losh might have been ignored by the -k option. 20963c90c9eSWarner Losh 2105fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 2115fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 2125fd2a895SWarner Losh of this working. 2135fd2a895SWarner Losh 214aac7dfeaSWarner Losh20001228: 215aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 216aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 217aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 218aac7dfeaSWarner Losh 219de2bcc63SWarner Losh20001218: 220de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 221de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 222de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 223de2bcc63SWarner Losh cards will not be recognized without it. 224de2bcc63SWarner Losh 225960773f7SWarner Losh20001205: 226960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 227960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 228960773f7SWarner Losh adding the following in pam.conf: 229960773f7SWarner Losh 230960773f7SWarner Losh sshd auth sufficient pam_skey.so 231960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 232960773f7SWarner Losh sshd session required pam_permit.so 233960773f7SWarner Losh 2340acc635eSWarner Losh20001031: 2350acc635eSWarner Losh cvs updated to 1.11. 2360acc635eSWarner Losh 2370acc635eSWarner Losh20001020: 2380acc635eSWarner Losh The random device needs more entropy, so you need to make sure 2390acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 2400acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 2410acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 2420acc635eSWarner Losh workaround. 2430acc635eSWarner Losh 2440acc635eSWarner Losh20001010: 2450acc635eSWarner Losh ****************************** WARNING ****************************** 2460acc635eSWarner Losh Sendmail has been updated. 2470acc635eSWarner Losh ****************************** WARNING ****************************** 2480acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 2490acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 2500acc635eSWarner Losh is set. 2510acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 2520acc635eSWarner Losh commands. 2530acc635eSWarner Losh o Now using sendmail's version of vacation(1). 2540acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 2550acc635eSWarner Losh in /usr/share/sendmail/cf. 2560acc635eSWarner Losh o sendmail.cw changed to local-host-names 2570acc635eSWarner Losh 2580acc635eSWarner Losh More details can be found at 2590acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 2600acc635eSWarner Losh 2616e98a146SWarner Losh20001009: 2626e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 2636e98a146SWarner Losh your entire ports tree, or you will have problems. 2646e98a146SWarner Losh 2656e98a146SWarner Losh20001006: 266685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 2676e98a146SWarner Losh the installed miniperl. It is recommended that you delete 2686e98a146SWarner Losh /usr/bin/miniperl. 2696e98a146SWarner Losh 270073113a4SWarner Losh20001005: 271073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 272685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 273073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 274073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 275073113a4SWarner Losh tree for anything to work. 276073113a4SWarner Losh 2770acc635eSWarner Losh20000928: 2780acc635eSWarner Losh There was a change in the passwd format. Need more information. 2790acc635eSWarner Losh 280be3885b3SWarner Losh20000916: 281be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 282be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 283be3885b3SWarner Losh same time as your kernel. 284be3885b3SWarner Losh 28576ec9675SWarner Losh20000914: 28676ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 28776ec9675SWarner Losh include the device will cause suspended laptops losing time 28876ec9675SWarner Losh when they resume. Include 28976ec9675SWarner Losh device pmtimer 29076ec9675SWarner Losh in your config file and 29101b9a434SWarner Losh hint.pmtimer.0.at="isa" 29276ec9675SWarner Losh to your /boot/device.hints file. 29376ec9675SWarner Losh 294f4865386SMark Murray20000911: 295f4865386SMark Murray The random device has been turned into a (pseudo-)device, 296f4865386SMark Murray rather than an option. The supplied kernel config files have 297f4865386SMark Murray been updated. You will need to do something similar in your 298f4865386SMark Murray own kernel config file. 299f4865386SMark Murray Remove: 300f4865386SMark Murray options RANDOMDEV 301f4865386SMark Murray Add: 302f4865386SMark Murray device random 303f4865386SMark Murray If you prefer to load the loadable module, you need to do 304f4865386SMark Murray nothing. 305f4865386SMark Murray 306d594498fSWarner Losh20000909: 307d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 308d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 309d594498fSWarner Losh reflect this if you load this module at boot time. 310d594498fSWarner Losh The line should read: 311d594498fSWarner Losh random_load="YES" 312d594498fSWarner Losh 3130deb7ddcSWarner Losh20000907: 3140deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 31516eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 31616eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 31716eb772dSWarner Losh sure you don't have model loading problems which might at 31816eb772dSWarner Losh first blush appear related to SMP. 31952bf24e7SWarner Losh 3205a01880bSWarner Losh20000906: 3215a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 3225a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 3235a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 3245a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 3255a01880bSWarner Losh don't have one, and you have host.conf. 3265a01880bSWarner Losh 3272b41163cSWarner Losh20000905: 32838d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 32938d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 33038d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 33138d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 33238d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 33338d6ecd2SWarner Losh 33438d6ecd2SWarner Losh20000905: 3358aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 3368aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 3378aab4bc7SWarner Losh is /boot/kernel. 3388aab4bc7SWarner Losh 3398aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 34038d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 34138d6ecd2SWarner Losh installkernel/installworld dance. 3422b41163cSWarner Losh 343d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 344d594498fSWarner Losh before booting the new kernel, since kldload will find stale 345d594498fSWarner Losh modules in that directory instead of finding them in the correct 346d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 347d594498fSWarner Losh is that the linux module crashes your machine after the update. 348d594498fSWarner Losh 349d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 350d594498fSWarner Losh mv /modules.old /boot/kernel.old 351d594498fSWarner Losh chflags noschg /kernel.old 352d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 353d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 354d594498fSWarner Losh fi 355d594498fSWarner Losh 356c22a309cSWarner Losh20000904: 357c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 358c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 359c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 360c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 361c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 362c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 363c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 364c22a309cSWarner Losh is not likely to be generated. 365c22a309cSWarner Losh 366fdb9f54dSWarner Losh20000825: 367fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 3689c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 3699c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 3709c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 3719c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 3729c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 3739c1a7444SWarner Losh messages will appear after the boot loader tries to start the 3749c1a7444SWarner Losh kernel. 3759c1a7444SWarner Losh 3769c1a7444SWarner Losh20000821: 3779c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 3789c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 3799c1a7444SWarner Losh /boot/loader.conf. 380fdb9f54dSWarner Losh 3818f250aa7SWarner Losh20000812: 3825da0d091SWarner Losh suidperl is now always built and installed on the system, but 3835da0d091SWarner Losh with permissions of 511. If you have applications that use 3845da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 3855da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 3865da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 3875da0d091SWarner Losh will fix this until the next build. 3885da0d091SWarner Losh 3895da0d091SWarner Losh20000812: 3908f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 3918f250aa7SWarner Losh visible changes that may immediately affect your configuration 3928f250aa7SWarner Losh include: 3938f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 3948f250aa7SWarner Losh - newaliases limited to root and trusted users 3958f250aa7SWarner Losh - MSA port (587) turned on by default 3968f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 3978f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 3988f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 3998f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 4008f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 4018f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 4028f250aa7SWarner Losh 40371c38472SWarner Losh20000810: 40471c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 40571c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 40671c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 40771c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 40871c38472SWarner Losh specific use for it. 40971c38472SWarner Losh 41071c38472SWarner Losh20000729: 41171c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 41271c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 41371c38472SWarner Losh /etc/rc.conf if they want to have the same setup 41471c38472SWarner Losh afterwards (unless the variables already are set, of course): 41571c38472SWarner Losh # Enable network daemons for user convenience. 41671c38472SWarner Losh inetd_enable="YES" 41771c38472SWarner Losh portmap_enable="YES" 41871c38472SWarner Losh sendmail_enable="YES" 41971c38472SWarner Losh 42071c38472SWarner Losh20000728: 42171c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 42271c38472SWarner Losh will need to change that to nullfs_load="YES". 42371c38472SWarner Losh 4241dece4a9SWarner Losh20000728: 4251dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 4261dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 4271dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 4281dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 4291dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 4301dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 4311dece4a9SWarner Losh to /MYKERNEL. 4321dece4a9SWarner Losh 433409e887cSWarner Losh20000711: 434409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 435409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 436409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 437409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 438409e887cSWarner Losh for details on potential problems that you might have and how 439409e887cSWarner Losh to get around them. 440409e887cSWarner Losh 441409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 442409e887cSWarner Losh clauses above, you needn't worry. 443409e887cSWarner Losh 444409e887cSWarner Losh20000711: 445409e887cSWarner Losh /etc/security has been updated to print the inode number of 446409e887cSWarner Losh setuid programs that have changed. You will see a large spike 447409e887cSWarner Losh in the number of changed programs the first time when you run 448409e887cSWarner Losh mergemaster to get a new /etc/security. 449409e887cSWarner Losh 450673d13f2SWarner Losh20000710: 451673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 452673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 453673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 454673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 455673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 456673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 457673d13f2SWarner Losh errors. (see below, 20000624). 458673d13f2SWarner Losh 459bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 4601dece4a9SWarner Losh 461673d13f2SWarner Losh20000709: 462c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 463c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 464c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 465673d13f2SWarner Losh ln -s aj /etc/malloc.conf 466673d13f2SWarner Losh 467e98e26cdSWarner Losh20000706: 468e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 469e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 470e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 471f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 472e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 4732c021c6cSMark Ovens interim if needed. 474e98e26cdSWarner Losh 475e98e26cdSWarner Losh20000705: 476e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 477e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 478e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 479e98e26cdSWarner Losh details. 480e98e26cdSWarner Losh 481c373950eSWarner Losh20000704: 4822f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 4832f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 4842f961bc8SWarner Losh 4852f961bc8SWarner Losh20000704: 486c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 487c373950eSWarner Losh or stop. This may cause some harmless warnings from older 488c373950eSWarner Losh rc.d scripts that haven't been updated. 489c373950eSWarner Losh 49027dc3a2bSWarner Losh20000630: 49127dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 49227dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 49327dc3a2bSWarner Losh which should be reported to des@freebsd.org. 49427dc3a2bSWarner Losh 495b8c215acSWarner Losh20000625: 496b8c215acSWarner Losh From approximately this date forward, one must have the crypto 49727dc3a2bSWarner Losh system installed in order to build the system and kernel. 49827dc3a2bSWarner Losh While not technically strictly true, one should treat it as 49927dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 50027dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 50127dc3a2bSWarner Losh were required. You should check with the latest collections 50227dc3a2bSWarner Losh to make sure that these haven't changed. 503b8c215acSWarner Losh 5047b990719SWarner Losh20000624: 5057b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 5067b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 5077b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 5087b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 5097b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 5107b990719SWarner Losh openssh and openssl should not be used to generate keys from this 5117b990719SWarner Losh date to the completion of the work. 5127b990719SWarner Losh 51327dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 51427dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 51527dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 51627dc3a2bSWarner Losh recreate the random and urandom devices. 51727dc3a2bSWarner Losh 51881e54c50SWarner Losh20000622: 51981e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 52081e54c50SWarner Losh BSD license. You may need to remove your symbolic links 52181e54c50SWarner Losh that used to be required when updating. 52281e54c50SWarner Losh 52339943833SWarner Losh20000621: 5242c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 5252a2f33fbSDaniel Baker the config file update procedure. 5262a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 527c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 528a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 52939943833SWarner Losh 530290f9ad8SWarner Losh20000620: 531290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 532290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 533290f9ad8SWarner Losh that workaround will no longer be required. 534290f9ad8SWarner Losh 53590fb6346SWarner Losh20000615: 53690fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 53790fb6346SWarner Losh ad driver. If you haven't done so already, you must update 53890fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 53990fb6346SWarner Losh devices. 54090fb6346SWarner Losh 541f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 542f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 543f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 544f75f65bbSWarner Losh may work). 545f75f65bbSWarner Losh 546ba26da8eSWarner Losh20000612: 547ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 548290f9ad8SWarner Losh on the topic before even thinking about updating. You will 549c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 550290f9ad8SWarner Losh to your config file to compile them in statically. The format 551f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 552f54a3542SWarner Losh NEWCARD for examples of the new format. 553290f9ad8SWarner Losh 554d65850ebSWarner Losh20000522: 555ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 556d65850ebSWarner Losh building a kernel after this point is advised that they need 557d65850ebSWarner Losh to rebuild their binutils (or better yet do a 558d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 559d65850ebSWarner Losh 560d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 561d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 562d9583a00SWarner Losh is recommended that you don't set this option until the problem 563d9583a00SWarner Losh is resolved. 564d9583a00SWarner Losh 5658039cedeSWarner Losh20000513: 5668039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 5678039cedeSWarner Losh 568d65850ebSWarner Losh20000510: 5698039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 5708039cedeSWarner Losh This will require some care in updating alphas. A new libstand 5718039cedeSWarner Losh is requires for the boot blocks to build properly. 5728039cedeSWarner Losh 5738039cedeSWarner Losh20000503: 5748039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 5758039cedeSWarner Losh is now available. 5768039cedeSWarner Losh 577d65850ebSWarner Losh20000502: 578d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 579d65850ebSWarner Losh connected to the kernel building instead. 580d65850ebSWarner Losh 581be149406SNik Clayton20000427: 5828039cedeSWarner Losh You may need to build gperf 5838039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 5848039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 5858039cedeSWarner Losh an option only in -current. 5868039cedeSWarner Losh 5872b8dd5f4SWarner Losh20000417: 5882b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 589f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 5902b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 5912b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 5922c021c6cSMark Ovens before you reboot, you'll need to issue: 5932b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 5942b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 5952b8dd5f4SWarner Losh 5968d9f1945SWarner Losh20000320: 5972b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 5982b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 5992b8dd5f4SWarner Losh cope if you have a problem combination is to add: 6008d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 6012b8dd5f4SWarner Losh to the start of /etc/rc.conf. 6028d9f1945SWarner Losh 603f8ab1dd6SWarner Losh20000319: 604f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 605f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 606f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 607f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 608f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 609f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 610f8ab1dd6SWarner Losh 61119cada77SWarner Losh20000318: 612f699bbbbSMark Ovens We've entered the traditional post release dumping party. 61319cada77SWarner Losh Large kernel changes are being committed and are in the 61419cada77SWarner Losh works. It is important to keep the systems' klds and kernel 61519cada77SWarner Losh in sync as kernel interfaces and structures are changing. 61619cada77SWarner Losh Before reporting kernel panics, make sure that all modules 61719cada77SWarner Losh that you are loading are up to date. 618ba228352SWarner Losh 61919cada77SWarner Losh20000315: 6206d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 6216d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 6226d23c382SWarner Losh will do the trick. This isn't critical until you remove your 6236d23c382SWarner Losh wd device entries in /dev, at which point your system will not 6246d23c382SWarner Losh boot. 6256d23c382SWarner Losh 6266d23c382SWarner Losh20000315: 62719cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 62819cada77SWarner Losh to upgrade to 4.0 from 3.x. 62957199806SWarner Losh 630dc0dbf5cSWarner LoshCOMMON ITEMS: 631dc0dbf5cSWarner Losh 632a24eff53SWarner Losh General Notes 633a24eff53SWarner Losh ------------- 634a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 635a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 636a24eff53SWarner Losh installworld. This is especially true when upgrading between 637a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 638a24eff53SWarner Losh or several minor releases, or when several months have passed 639a24eff53SWarner Losh on the -current branch). 640a24eff53SWarner Losh 641dc0dbf5cSWarner Losh To build a kernel 642dc0dbf5cSWarner Losh ----------------- 643ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 644f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 645ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 6461e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 6471e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 648dc0dbf5cSWarner Losh 649ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 650ba01eb20SWarner Losh -------------------------------------------------------------- 651ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 652ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 653ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 654ba01eb20SWarner Losh make depend 655ba01eb20SWarner Losh make 656ba01eb20SWarner Losh make install 657ba01eb20SWarner Losh 658ba01eb20SWarner Losh [1] If in doubt, -r might help here. 659ba01eb20SWarner Losh 660ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 661ba01eb20SWarner Losh 662ba01eb20SWarner Losh To rebuild everything and install it on the current system. 663ba01eb20SWarner Losh ----------------------------------------------------------- 664759f0aefSWarner Losh make world 665fdb9f54dSWarner Losh Build a new kernel, see above. 666759f0aefSWarner Losh 6671dece4a9SWarner Losh To upgrade from 4.x-stable to current 668ba26da8eSWarner Losh ------------------------------------- 669ba26da8eSWarner Losh make buildworld 6701e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 6717595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 6721e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 673ee6e1fc3SWarner Losh reboot in single user [3] 674ba26da8eSWarner Losh make installworld 6757595222aSWarner Losh mergemaster 676134d2e86SWarner Losh [1] 677ba26da8eSWarner Losh <reboot> 678ba26da8eSWarner Losh 679fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 680fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 681fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 682fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 683fdb9f54dSWarner Losh the UPDATING entries. 684ba26da8eSWarner Losh 6851dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 6861dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 6871dece4a9SWarner Losh your sources that you have read and understood all the recent 6881dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 6891dece4a9SWarner Losh much fewer pitfalls. 6901dece4a9SWarner Losh 691134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 692134d2e86SWarner Losh should disable them at this point so they don't crash your 693134d2e86SWarner Losh system on reboot. 694134d2e86SWarner Losh 6959c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 6969c1a7444SWarner Losh your own device.hints to reflect your unique hardware 6979c1a7444SWarner Losh configuration. 6989c1a7444SWarner Losh 699ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 700ee6e1fc3SWarner Losh fsck -p 701ee6e1fc3SWarner Losh mount -u / 702ee6e1fc3SWarner Losh mount -a 703ee6e1fc3SWarner Losh cd /usr/src 704ee6e1fc3SWarner Losh adjkerntz -i # if COMS is wall time 705ee6e1fc3SWarner Losh 706dc0dbf5cSWarner LoshFORMAT: 707dc0dbf5cSWarner Losh 708f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 7091fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 710f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 711f8ab1dd6SWarner Loshprevious releases if your system is older than this. 7121fc1a0dcSWarner Losh 7133645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 7143645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 715f8c77507SWarner Losh 71697d92980SPeter Wemm$FreeBSD$ 717