157199806SWarner LoshUpdating Information for FreeBSD current users 253dfde79SWarner Losh 3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh 4e72fd46aSWarner Losh<imp@village.org>. Please send new entries directly to him. See end 5e72fd46aSWarner Loshof file for further details. For commonly done items, please see the 6e72fd46aSWarner LoshCOMMON ITEMS: section later in the file. 7e72fd46aSWarner Losh 8*1d28950eSWarner Losh20010628: 9*1d28950eSWarner Losh The kernel compile module has moved from src/sys/compile/FOO 10*1d28950eSWarner Losh to src/sys/${MACHINE}/compile/FOO. 11*1d28950eSWarner Losh 12e72fd46aSWarner Losh20010625: 13e72fd46aSWarner Losh The pccard modem issue has been corrected. OLDCARD support is 14e72fd46aSWarner Losh still a little weak in -current. slot 1 is known not to work 15e72fd46aSWarner Losh on some TI based cardbus bridges. Some cardbus bridges do not 16e72fd46aSWarner Losh properly detect insert/removal events. IRQ configuration needs 17e72fd46aSWarner Losh more safety belts. 1816de1a07SWarner Losh 190d415dffSWarner Losh20010617: 20e72fd46aSWarner Losh Softupdates problems have been corrected. 210d415dffSWarner Losh 220d415dffSWarner Losh20010614: 230d415dffSWarner Losh Peter ripped out the linkerset support. You must, as always, 240d415dffSWarner Losh rerun config after you cvsup if you are using the traditional 250d415dffSWarner Losh kernel building methods. 260d415dffSWarner Losh 278b9959adSWarner Losh20010613: 288b9959adSWarner Losh pccard modems may not work with current after 20010604 date. Some 298b9959adSWarner Losh do, others result in panics. *MAKE*SURE* that you update your 30e72fd46aSWarner Losh config and /etc/rc.conf ala the 20010604 entry, or you will have 31e72fd46aSWarner Losh problems (this issue will be fixed, it just hasn't been yet). 328b9959adSWarner Losh 33e72fd46aSWarner Losh20010613: 348b9959adSWarner Losh SOFTUPDATES seem to be broken since the middle of May or so. Do not 35e72fd46aSWarner Losh use them in current. You can disable softupdates on all mounted 36e72fd46aSWarner Losh partitions, or remove SOFTUPDATES the kernel config file. 378b9959adSWarner Losh 380d415dffSWarner Losh20010612: 390d415dffSWarner Losh After Peter's commits to the hints code, people have been noticing 400d415dffSWarner Losh that certain devices are attached (or try to) twice. This is due 410d415dffSWarner Losh to having both static hints as well as a /boot/device.hints. To 420d415dffSWarner Losh work around this issue, please use only one or the other mechanism 430d415dffSWarner Losh until this bug is fixed. 440d415dffSWarner Losh 45e72fd46aSWarner Losh Please note that a feature of config is that if you have config 46e72fd46aSWarner Losh file FOO and FOO.hints, it automatically adds FOO.hints to the 47e72fd46aSWarner Losh hints.c file, wheather you want it to or not. 48e72fd46aSWarner Losh 490d415dffSWarner Losh20010610: 500d415dffSWarner Losh Locale names have changed to match other systems better. 510d415dffSWarner Losh 526ccdb5e4SWarner Losh20010604: 536ccdb5e4SWarner Losh pccard support for pci cards has been committed. You must change 546ccdb5e4SWarner Losh your /etc/pccard.conf irq lines. It must match the irq used by 556ccdb5e4SWarner Losh pcic device. Interrupt storms may result if you fail to do this. 563590182eSWarner Losh Interrupt storms look a lot like a hang. 573590182eSWarner Losh 583590182eSWarner Losh You must also install a new pccardd, otherwise you will get an 593590182eSWarner Losh interrupt storm at card reset time (just after it tells you what 603590182eSWarner Losh it is). 613590182eSWarner Losh 623590182eSWarner Losh pccardd_flags="-I" is necessary for the time being. It tells pccardd 633590182eSWarner Losh not to ask the kernel if the interrupt is really free or not before 643590182eSWarner Losh using it. You can either change the /etc/pccard.conf irq lines to 653590182eSWarner Losh match pcic, or add "-i X" to the pccardd_flags. 666ccdb5e4SWarner Losh 670bc62786SWarner Losh20010530: 680bc62786SWarner Losh INSTALL=install -C is being deprecated. If you want to do this, 690bc62786SWarner Losh use COPY=-C instead. The former method will be supported for only 700bc62786SWarner Losh a limited time. If you see 710bc62786SWarner Losh 720bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together 730bc62786SWarner Losh 740bc62786SWarner Losh in your makeworld, then you need to migrate towards using 750bc62786SWarner Losh COPY=-C. 760bc62786SWarner Losh 7768a38c6cSWarner Losh20010525: 78b6609bbbSWarner Losh It appears that vm is now stable enough to use again. However, 79c4f4a728SWarner Losh there may be other problems, so caution is still urged. alpha 80c4f4a728SWarner Losh definitely is in bad shape. 8168a38c6cSWarner Losh 82ed0f29caSWarner Losh20010521: 83ed0f29caSWarner Losh Minor repo damanged has happened. This may cause problems 84ed0f29caSWarner Losh with cvsup of ports. If you get errors, please see 85ed0f29caSWarner Losh http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 86ed0f29caSWarner Losh at the bottom for details on a workaround. The error message 87ed0f29caSWarner Losh is 88ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 89ed0f29caSWarner Losh 9080c16af9SWarner Losh20010520: 9168a38c6cSWarner Losh Vm and/or swapping are busted on -current. Please be patient. 9280c16af9SWarner Losh 9380c16af9SWarner Losh20010519: 9480c16af9SWarner Losh pccard has had much reorganizational work done to it over 9580c16af9SWarner Losh the past few days. Everything should still work, but if 9680c16af9SWarner Losh not, please contact imp@freebsd.org. 9780c16af9SWarner Losh 98a45f2d05SWarner Losh20010517: 99a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 100a45f2d05SWarner Losh userland at the same time. 101a45f2d05SWarner Losh 102a45f2d05SWarner Losh20010517: 103a45f2d05SWarner Losh New ncurses imported. 104a45f2d05SWarner Losh 1052988afcaSWarner Losh20010512: 1062988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 1072988afcaSWarner Losh will be the only way to go starting July 1. 1082988afcaSWarner Losh 10909946a51SWarner Losh20010502: 11009946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 11109946a51SWarner Losh 11209946a51SWarner Losh20010501: 11309946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 11409946a51SWarner Losh 11509946a51SWarner Losh20010430: 116a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 11709946a51SWarner Losh go back in the water. 11809946a51SWarner Losh 11909946a51SWarner Losh20010429: 12009946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 12109946a51SWarner Losh this date, but before the correction date. 12209946a51SWarner Losh 12391dd3b53SWarner Losh20010423: 12491dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 12591dd3b53SWarner Losh 12691dd3b53SWarner Losh20010411: 12791dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 12891dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 12991dd3b53SWarner Losh Update only if you understand that you must not use the old 13091dd3b53SWarner Losh fsck with the new kernel ever. 13191dd3b53SWarner Losh 132933b3269SWarner Losh20010330: 133933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 134c4e215d3SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page for 135933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 136933b3269SWarner Losh 137933b3269SWarner Losh20010319: 138933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 139933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 140933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 14109946a51SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netcofnig. 14209946a51SWarner Losh 14309946a51SWarner Losh20010315: 14409946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 14509946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 14609946a51SWarner Losh been replaced by tunables. See ata.4 for details. 147933b3269SWarner Losh 148933b3269SWarner Losh20010312: 149933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 150933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 151933b3269SWarner Losh 152933b3269SWarner Losh20010312: 153933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 154933b3269SWarner Losh instead of ad-hoc. 155933b3269SWarner Losh 156933b3269SWarner Losh20010310: 157f5260d32SWarner Losh /dev/urandom should be a symbolic link to /dev/random now. 158933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 159933b3269SWarner Losh ssh might not work if you don't. 160933b3269SWarner Losh 161d325cf65SWarner Losh20010220: 162d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 163d325cf65SWarner Losh safe to go back into the water. 164d325cf65SWarner Losh 165024daae6SWarner Losh20010211: 166024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 167024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 168024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 169024daae6SWarner Losh that before upgrading would be a good time to do a level 0 170024daae6SWarner Losh dump of your system. No, really, I mean it this time. 171024daae6SWarner Losh 172024daae6SWarner Losh To get to the new system, you'll need to use the following 173024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 174024daae6SWarner Losh don't have to move this to the updating section. 175024daae6SWarner Losh 176024daae6SWarner Losh To get around the installworld problem, do: 177024daae6SWarner Losh # cd /usr/src/usr.bin/sed 178024daae6SWarner Losh # make install 179024daae6SWarner Losh # cd /usr/src 180024daae6SWarner Losh # make installworld 181024daae6SWarner Losh If that doesn't work, then try: 182024daae6SWarner Losh # make -k installworld 183024daae6SWarner Losh # make installworld 184024daae6SWarner Losh 185024daae6SWarner Losh20010207: 186024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 187024daae6SWarner Losh do not include devfs in your kernel as problems result. 188024daae6SWarner Losh 189024daae6SWarner Losh20010205: 1907595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 191024daae6SWarner Losh Remove them from your config. 192024daae6SWarner Losh 1931e159248SWarner Losh20010122: 1941e159248SWarner Losh ****************************** WARNING ****************************** 1951e159248SWarner Losh buildkernel has been changed slightly 1961e159248SWarner Losh ****************************** WARNING ****************************** 1971e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 1981e159248SWarner Losh should update your scripts and make.conf accordingly. 1991e159248SWarner Losh 2001e159248SWarner Losh20010119: 2011e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 2021e159248SWarner Losh This requires a new config to build correctly. 2031e159248SWarner Losh 204aac7dfeaSWarner Losh20010116: 205aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 206aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 207aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 208aac7dfeaSWarner Losh 209aac7dfeaSWarner Losh20010110: 210aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 211aac7dfeaSWarner Losh 212aac7dfeaSWarner Losh20010102: 213aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 214aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 215aac7dfeaSWarner Losh 21663c90c9eSWarner Losh20010101: 21763c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 21863c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 2195fd2a895SWarner Losh dump while building termcap. You can work around this problem 22063c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 22163c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 22263c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 22363c90c9eSWarner Losh might have been ignored by the -k option. 22463c90c9eSWarner Losh 2255fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 2265fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 2275fd2a895SWarner Losh of this working. 2285fd2a895SWarner Losh 229aac7dfeaSWarner Losh20001228: 230aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 231aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 232aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 233aac7dfeaSWarner Losh 234de2bcc63SWarner Losh20001218: 235de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 236de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 237de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 238de2bcc63SWarner Losh cards will not be recognized without it. 239de2bcc63SWarner Losh 240960773f7SWarner Losh20001205: 241960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 242960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 243960773f7SWarner Losh adding the following in pam.conf: 244960773f7SWarner Losh 245960773f7SWarner Losh sshd auth sufficient pam_skey.so 246960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 247960773f7SWarner Losh sshd session required pam_permit.so 248960773f7SWarner Losh 2490acc635eSWarner Losh20001031: 2500acc635eSWarner Losh cvs updated to 1.11. 2510acc635eSWarner Losh 2520acc635eSWarner Losh20001020: 2530acc635eSWarner Losh The random device needs more entropy, so you need to make sure 2540acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 2550acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 2560acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 2570acc635eSWarner Losh workaround. 2580acc635eSWarner Losh 2590acc635eSWarner Losh20001010: 2600acc635eSWarner Losh ****************************** WARNING ****************************** 2610acc635eSWarner Losh Sendmail has been updated. 2620acc635eSWarner Losh ****************************** WARNING ****************************** 2630acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 2640acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 2650acc635eSWarner Losh is set. 2660acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 2670acc635eSWarner Losh commands. 2680acc635eSWarner Losh o Now using sendmail's version of vacation(1). 2690acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 2700acc635eSWarner Losh in /usr/share/sendmail/cf. 2710acc635eSWarner Losh o sendmail.cw changed to local-host-names 2720acc635eSWarner Losh 2730acc635eSWarner Losh More details can be found at 2740acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 2750acc635eSWarner Losh 2766e98a146SWarner Losh20001009: 2776e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 2786e98a146SWarner Losh your entire ports tree, or you will have problems. 2796e98a146SWarner Losh 2806e98a146SWarner Losh20001006: 281685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 2826e98a146SWarner Losh the installed miniperl. It is recommended that you delete 2836e98a146SWarner Losh /usr/bin/miniperl. 2846e98a146SWarner Losh 285073113a4SWarner Losh20001005: 286073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 287685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 288073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 289073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 290073113a4SWarner Losh tree for anything to work. 291073113a4SWarner Losh 2920acc635eSWarner Losh20000928: 2930acc635eSWarner Losh There was a change in the passwd format. Need more information. 2940acc635eSWarner Losh 295be3885b3SWarner Losh20000916: 296be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 297be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 298be3885b3SWarner Losh same time as your kernel. 299be3885b3SWarner Losh 30076ec9675SWarner Losh20000914: 30176ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 30276ec9675SWarner Losh include the device will cause suspended laptops losing time 30376ec9675SWarner Losh when they resume. Include 30476ec9675SWarner Losh device pmtimer 30576ec9675SWarner Losh in your config file and 30601b9a434SWarner Losh hint.pmtimer.0.at="isa" 30776ec9675SWarner Losh to your /boot/device.hints file. 30876ec9675SWarner Losh 309f4865386SMark Murray20000911: 310f4865386SMark Murray The random device has been turned into a (pseudo-)device, 311f4865386SMark Murray rather than an option. The supplied kernel config files have 312f4865386SMark Murray been updated. You will need to do something similar in your 313f4865386SMark Murray own kernel config file. 314f4865386SMark Murray Remove: 315f4865386SMark Murray options RANDOMDEV 316f4865386SMark Murray Add: 317f4865386SMark Murray device random 318f4865386SMark Murray If you prefer to load the loadable module, you need to do 319f4865386SMark Murray nothing. 320f4865386SMark Murray 321d594498fSWarner Losh20000909: 322d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 323d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 324d594498fSWarner Losh reflect this if you load this module at boot time. 325d594498fSWarner Losh The line should read: 326d594498fSWarner Losh random_load="YES" 327d594498fSWarner Losh 3280deb7ddcSWarner Losh20000907: 3290deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 33016eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 33116eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 33216eb772dSWarner Losh sure you don't have model loading problems which might at 33316eb772dSWarner Losh first blush appear related to SMP. 33452bf24e7SWarner Losh 3355a01880bSWarner Losh20000906: 3365a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 3375a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 3385a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 3395a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 3405a01880bSWarner Losh don't have one, and you have host.conf. 3415a01880bSWarner Losh 3422b41163cSWarner Losh20000905: 34338d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 34438d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 34538d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 34638d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 34738d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 34838d6ecd2SWarner Losh 34938d6ecd2SWarner Losh20000905: 3508aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 3518aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 3528aab4bc7SWarner Losh is /boot/kernel. 3538aab4bc7SWarner Losh 3548aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 35538d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 35638d6ecd2SWarner Losh installkernel/installworld dance. 3572b41163cSWarner Losh 358d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 359d594498fSWarner Losh before booting the new kernel, since kldload will find stale 360d594498fSWarner Losh modules in that directory instead of finding them in the correct 361d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 362d594498fSWarner Losh is that the linux module crashes your machine after the update. 363d594498fSWarner Losh 364d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 365d594498fSWarner Losh mv /modules.old /boot/kernel.old 366d594498fSWarner Losh chflags noschg /kernel.old 367d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 368d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 369d594498fSWarner Losh fi 370d594498fSWarner Losh 371c22a309cSWarner Losh20000904: 372c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 373c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 374c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 375c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 376c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 377c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 378c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 379c22a309cSWarner Losh is not likely to be generated. 380c22a309cSWarner Losh 381fdb9f54dSWarner Losh20000825: 382fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 3839c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 3849c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 3859c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 3869c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 3879c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 3889c1a7444SWarner Losh messages will appear after the boot loader tries to start the 3899c1a7444SWarner Losh kernel. 3909c1a7444SWarner Losh 3919c1a7444SWarner Losh20000821: 3929c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 3939c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 3949c1a7444SWarner Losh /boot/loader.conf. 395fdb9f54dSWarner Losh 3968f250aa7SWarner Losh20000812: 3975da0d091SWarner Losh suidperl is now always built and installed on the system, but 3985da0d091SWarner Losh with permissions of 511. If you have applications that use 3995da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 4005da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 4015da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 4025da0d091SWarner Losh will fix this until the next build. 4035da0d091SWarner Losh 4045da0d091SWarner Losh20000812: 4058f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 4068f250aa7SWarner Losh visible changes that may immediately affect your configuration 4078f250aa7SWarner Losh include: 4088f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 4098f250aa7SWarner Losh - newaliases limited to root and trusted users 4108f250aa7SWarner Losh - MSA port (587) turned on by default 4118f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 4128f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 4138f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 4148f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 4158f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 4168f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 4178f250aa7SWarner Losh 41871c38472SWarner Losh20000810: 41971c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 42071c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 42171c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 42271c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 42371c38472SWarner Losh specific use for it. 42471c38472SWarner Losh 42571c38472SWarner Losh20000729: 42671c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 42771c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 42871c38472SWarner Losh /etc/rc.conf if they want to have the same setup 42971c38472SWarner Losh afterwards (unless the variables already are set, of course): 43071c38472SWarner Losh # Enable network daemons for user convenience. 43171c38472SWarner Losh inetd_enable="YES" 43271c38472SWarner Losh portmap_enable="YES" 43371c38472SWarner Losh sendmail_enable="YES" 43471c38472SWarner Losh 43571c38472SWarner Losh20000728: 43671c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 43771c38472SWarner Losh will need to change that to nullfs_load="YES". 43871c38472SWarner Losh 4391dece4a9SWarner Losh20000728: 4401dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 4411dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 4421dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 4431dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 4441dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 4451dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 4461dece4a9SWarner Losh to /MYKERNEL. 4471dece4a9SWarner Losh 448409e887cSWarner Losh20000711: 449409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 450409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 451409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 452409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 453409e887cSWarner Losh for details on potential problems that you might have and how 454409e887cSWarner Losh to get around them. 455409e887cSWarner Losh 456409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 457409e887cSWarner Losh clauses above, you needn't worry. 458409e887cSWarner Losh 459409e887cSWarner Losh20000711: 460409e887cSWarner Losh /etc/security has been updated to print the inode number of 461409e887cSWarner Losh setuid programs that have changed. You will see a large spike 462409e887cSWarner Losh in the number of changed programs the first time when you run 463409e887cSWarner Losh mergemaster to get a new /etc/security. 464409e887cSWarner Losh 465673d13f2SWarner Losh20000710: 466673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 467673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 468673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 469673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 470673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 471673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 472673d13f2SWarner Losh errors. (see below, 20000624). 473673d13f2SWarner Losh 474bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 4751dece4a9SWarner Losh 476673d13f2SWarner Losh20000709: 477c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 478c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 479c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 480673d13f2SWarner Losh ln -s aj /etc/malloc.conf 481673d13f2SWarner Losh 482e98e26cdSWarner Losh20000706: 483e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 484e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 485e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 486f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 487e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 4882c021c6cSMark Ovens interim if needed. 489e98e26cdSWarner Losh 490e98e26cdSWarner Losh20000705: 491e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 492e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 493e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 494e98e26cdSWarner Losh details. 495e98e26cdSWarner Losh 496c373950eSWarner Losh20000704: 4972f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 4982f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 4992f961bc8SWarner Losh 5002f961bc8SWarner Losh20000704: 501c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 502c373950eSWarner Losh or stop. This may cause some harmless warnings from older 503c373950eSWarner Losh rc.d scripts that haven't been updated. 504c373950eSWarner Losh 50527dc3a2bSWarner Losh20000630: 50627dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 50727dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 50827dc3a2bSWarner Losh which should be reported to des@freebsd.org. 50927dc3a2bSWarner Losh 510b8c215acSWarner Losh20000625: 511b8c215acSWarner Losh From approximately this date forward, one must have the crypto 51227dc3a2bSWarner Losh system installed in order to build the system and kernel. 51327dc3a2bSWarner Losh While not technically strictly true, one should treat it as 51427dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 51527dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 51627dc3a2bSWarner Losh were required. You should check with the latest collections 51727dc3a2bSWarner Losh to make sure that these haven't changed. 518b8c215acSWarner Losh 5197b990719SWarner Losh20000624: 5207b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 5217b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 5227b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 5237b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 5247b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 5257b990719SWarner Losh openssh and openssl should not be used to generate keys from this 5267b990719SWarner Losh date to the completion of the work. 5277b990719SWarner Losh 52827dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 52927dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 53027dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 53127dc3a2bSWarner Losh recreate the random and urandom devices. 53227dc3a2bSWarner Losh 53381e54c50SWarner Losh20000622: 53481e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 53581e54c50SWarner Losh BSD license. You may need to remove your symbolic links 53681e54c50SWarner Losh that used to be required when updating. 53781e54c50SWarner Losh 53839943833SWarner Losh20000621: 5392c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 5402a2f33fbSDaniel Baker the config file update procedure. 5412a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 542c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 543a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 54439943833SWarner Losh 545290f9ad8SWarner Losh20000620: 546290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 547290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 548290f9ad8SWarner Losh that workaround will no longer be required. 549290f9ad8SWarner Losh 55090fb6346SWarner Losh20000615: 55190fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 55290fb6346SWarner Losh ad driver. If you haven't done so already, you must update 55390fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 55490fb6346SWarner Losh devices. 55590fb6346SWarner Losh 556f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 557f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 558f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 559f75f65bbSWarner Losh may work). 560f75f65bbSWarner Losh 561ba26da8eSWarner Losh20000612: 562ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 563290f9ad8SWarner Losh on the topic before even thinking about updating. You will 564c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 565290f9ad8SWarner Losh to your config file to compile them in statically. The format 566f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 567f54a3542SWarner Losh NEWCARD for examples of the new format. 568290f9ad8SWarner Losh 569d65850ebSWarner Losh20000522: 570ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 571d65850ebSWarner Losh building a kernel after this point is advised that they need 572d65850ebSWarner Losh to rebuild their binutils (or better yet do a 573d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 574d65850ebSWarner Losh 575d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 576d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 577d9583a00SWarner Losh is recommended that you don't set this option until the problem 578d9583a00SWarner Losh is resolved. 579d9583a00SWarner Losh 5808039cedeSWarner Losh20000513: 5818039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 5828039cedeSWarner Losh 583d65850ebSWarner Losh20000510: 5848039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 5858039cedeSWarner Losh This will require some care in updating alphas. A new libstand 5868039cedeSWarner Losh is requires for the boot blocks to build properly. 5878039cedeSWarner Losh 5888039cedeSWarner Losh20000503: 5898039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 5908039cedeSWarner Losh is now available. 5918039cedeSWarner Losh 592d65850ebSWarner Losh20000502: 593d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 594d65850ebSWarner Losh connected to the kernel building instead. 595d65850ebSWarner Losh 596be149406SNik Clayton20000427: 5978039cedeSWarner Losh You may need to build gperf 5988039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 5998039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 6008039cedeSWarner Losh an option only in -current. 6018039cedeSWarner Losh 6022b8dd5f4SWarner Losh20000417: 6032b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 604f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 6052b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 6062b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 6072c021c6cSMark Ovens before you reboot, you'll need to issue: 6082b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 6092b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 6102b8dd5f4SWarner Losh 6118d9f1945SWarner Losh20000320: 6122b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 6132b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 6142b8dd5f4SWarner Losh cope if you have a problem combination is to add: 6158d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 6162b8dd5f4SWarner Losh to the start of /etc/rc.conf. 6178d9f1945SWarner Losh 618f8ab1dd6SWarner Losh20000319: 619f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 620f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 621f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 622f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 623f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 624f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 625f8ab1dd6SWarner Losh 62619cada77SWarner Losh20000318: 627f699bbbbSMark Ovens We've entered the traditional post release dumping party. 62819cada77SWarner Losh Large kernel changes are being committed and are in the 62919cada77SWarner Losh works. It is important to keep the systems' klds and kernel 63019cada77SWarner Losh in sync as kernel interfaces and structures are changing. 63119cada77SWarner Losh Before reporting kernel panics, make sure that all modules 63219cada77SWarner Losh that you are loading are up to date. 633ba228352SWarner Losh 63419cada77SWarner Losh20000315: 6356d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 6366d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 6376d23c382SWarner Losh will do the trick. This isn't critical until you remove your 6386d23c382SWarner Losh wd device entries in /dev, at which point your system will not 6396d23c382SWarner Losh boot. 6406d23c382SWarner Losh 6416d23c382SWarner Losh20000315: 64219cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 64319cada77SWarner Losh to upgrade to 4.0 from 3.x. 64457199806SWarner Losh 645dc0dbf5cSWarner LoshCOMMON ITEMS: 646dc0dbf5cSWarner Losh 647a24eff53SWarner Losh General Notes 648a24eff53SWarner Losh ------------- 649a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 650a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 651a24eff53SWarner Losh installworld. This is especially true when upgrading between 652a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 653a24eff53SWarner Losh or several minor releases, or when several months have passed 654a24eff53SWarner Losh on the -current branch). 655a24eff53SWarner Losh 656dc0dbf5cSWarner Losh To build a kernel 657dc0dbf5cSWarner Losh ----------------- 658ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 659f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 660ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 6611e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 6621e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 663dc0dbf5cSWarner Losh 664ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 665ba01eb20SWarner Losh -------------------------------------------------------------- 666ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 667ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 668ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 669ba01eb20SWarner Losh make depend 670ba01eb20SWarner Losh make 671ba01eb20SWarner Losh make install 672ba01eb20SWarner Losh 673ba01eb20SWarner Losh [1] If in doubt, -r might help here. 674ba01eb20SWarner Losh 675ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 676ba01eb20SWarner Losh 677ba01eb20SWarner Losh To rebuild everything and install it on the current system. 678ba01eb20SWarner Losh ----------------------------------------------------------- 679759f0aefSWarner Losh make world 680fdb9f54dSWarner Losh Build a new kernel, see above. 681759f0aefSWarner Losh 6821dece4a9SWarner Losh To upgrade from 4.x-stable to current 683ba26da8eSWarner Losh ------------------------------------- 684ba26da8eSWarner Losh make buildworld 6851e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 6867595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 6871e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 688ee6e1fc3SWarner Losh reboot in single user [3] 689ba26da8eSWarner Losh make installworld 6907595222aSWarner Losh mergemaster 691134d2e86SWarner Losh [1] 692ba26da8eSWarner Losh <reboot> 693ba26da8eSWarner Losh 694fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 695fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 696fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 697fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 698fdb9f54dSWarner Losh the UPDATING entries. 699ba26da8eSWarner Losh 7001dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 7011dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 7021dece4a9SWarner Losh your sources that you have read and understood all the recent 7031dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 7041dece4a9SWarner Losh much fewer pitfalls. 7051dece4a9SWarner Losh 706134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 707134d2e86SWarner Losh should disable them at this point so they don't crash your 708134d2e86SWarner Losh system on reboot. 709134d2e86SWarner Losh 7109c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 7119c1a7444SWarner Losh your own device.hints to reflect your unique hardware 7129c1a7444SWarner Losh configuration. 7139c1a7444SWarner Losh 714ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 715ee6e1fc3SWarner Losh fsck -p 716ee6e1fc3SWarner Losh mount -u / 717ee6e1fc3SWarner Losh mount -a 718ee6e1fc3SWarner Losh cd /usr/src 719ee6e1fc3SWarner Losh adjkerntz -i # if COMS is wall time 720ee6e1fc3SWarner Losh 721dc0dbf5cSWarner LoshFORMAT: 722dc0dbf5cSWarner Losh 723f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 7241fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 725f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 726f8ab1dd6SWarner Loshprevious releases if your system is older than this. 7271fc1a0dcSWarner Losh 7283645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 7293645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 730f8c77507SWarner Losh 731e72fd46aSWarner LoshCopyright information: 732e72fd46aSWarner Losh 733e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh. All Rights Reserved. 734e72fd46aSWarner Losh 735e72fd46aSWarner LoshRedistribution, translation and use, with or without modification, in 736e72fd46aSWarner Loshfull or in part, are permitted provided that the above copyright 737e72fd46aSWarner Loshnotice is retained. 738e72fd46aSWarner Losh 739e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 740e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 741e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 742e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 743e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 744e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 745e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 746e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 747e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 748e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 749e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 750e72fd46aSWarner Losh 751e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the 752e72fd46aSWarner Loshauthor a beer. 753e72fd46aSWarner Losh 75497d92980SPeter Wemm$FreeBSD$ 755