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 8d325cf65SWarner Losh20010220: 9d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 10d325cf65SWarner Losh safe to go back into the water. 11d325cf65SWarner Losh 12024daae6SWarner Losh20010211: 13024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 14024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 15024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 16024daae6SWarner Losh that before upgrading would be a good time to do a level 0 17024daae6SWarner Losh dump of your system. No, really, I mean it this time. 18024daae6SWarner Losh 19024daae6SWarner Losh To get to the new system, you'll need to use the following 20024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 21024daae6SWarner Losh don't have to move this to the updating section. 22024daae6SWarner Losh 23024daae6SWarner Losh To get around the installworld problem, do: 24024daae6SWarner Losh # cd /usr/src/usr.bin/sed 25024daae6SWarner Losh # make install 26024daae6SWarner Losh # cd /usr/src 27024daae6SWarner Losh # make installworld 28024daae6SWarner Losh If that doesn't work, then try: 29024daae6SWarner Losh # make -k installworld 30024daae6SWarner Losh # make installworld 31024daae6SWarner Losh 32024daae6SWarner Losh20010207: 33024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 34024daae6SWarner Losh do not include devfs in your kernel as problems result. 35024daae6SWarner Losh 36024daae6SWarner Losh20010205: 377595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 38024daae6SWarner Losh Remove them from your config. 39024daae6SWarner Losh 401e159248SWarner Losh20010122: 411e159248SWarner Losh ****************************** WARNING ****************************** 421e159248SWarner Losh buildkernel has been changed slightly 431e159248SWarner Losh ****************************** WARNING ****************************** 441e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 451e159248SWarner Losh should update your scripts and make.conf accordingly. 461e159248SWarner Losh 471e159248SWarner Losh20010119: 481e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 491e159248SWarner Losh This requires a new config to build correctly. 501e159248SWarner Losh 51aac7dfeaSWarner Losh20010116: 52aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 53aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 54aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 55aac7dfeaSWarner Losh 56aac7dfeaSWarner Losh20010110: 57aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 58aac7dfeaSWarner Losh 59aac7dfeaSWarner Losh20010102: 60aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 61aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 62aac7dfeaSWarner Losh 6363c90c9eSWarner Losh20010101: 6463c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 6563c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 665fd2a895SWarner Losh dump while building termcap. You can work around this problem 6763c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 6863c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 6963c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 7063c90c9eSWarner Losh might have been ignored by the -k option. 7163c90c9eSWarner Losh 725fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 735fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 745fd2a895SWarner Losh of this working. 755fd2a895SWarner Losh 76aac7dfeaSWarner Losh20001228: 77aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 78aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 79aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 80aac7dfeaSWarner Losh 81de2bcc63SWarner Losh20001218: 82de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 83de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 84de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 85de2bcc63SWarner Losh cards will not be recognized without it. 86de2bcc63SWarner Losh 87960773f7SWarner Losh20001205: 88960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 89960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 90960773f7SWarner Losh adding the following in pam.conf: 91960773f7SWarner Losh 92960773f7SWarner Losh sshd auth sufficient pam_skey.so 93960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 94960773f7SWarner Losh sshd session required pam_permit.so 95960773f7SWarner Losh 960acc635eSWarner Losh20001031: 970acc635eSWarner Losh cvs updated to 1.11. 980acc635eSWarner Losh 990acc635eSWarner Losh20001020: 1000acc635eSWarner Losh The random device needs more entropy, so you need to make sure 1010acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 1020acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 1030acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 1040acc635eSWarner Losh workaround. 1050acc635eSWarner Losh 1060acc635eSWarner Losh20001010: 1070acc635eSWarner Losh ****************************** WARNING ****************************** 1080acc635eSWarner Losh Sendmail has been updated. 1090acc635eSWarner Losh ****************************** WARNING ****************************** 1100acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 1110acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 1120acc635eSWarner Losh is set. 1130acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 1140acc635eSWarner Losh commands. 1150acc635eSWarner Losh o Now using sendmail's version of vacation(1). 1160acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 1170acc635eSWarner Losh in /usr/share/sendmail/cf. 1180acc635eSWarner Losh o sendmail.cw changed to local-host-names 1190acc635eSWarner Losh 1200acc635eSWarner Losh More details can be found at 1210acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 1220acc635eSWarner Losh 1236e98a146SWarner Losh20001009: 1246e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 1256e98a146SWarner Losh your entire ports tree, or you will have problems. 1266e98a146SWarner Losh 1276e98a146SWarner Losh20001006: 128685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 1296e98a146SWarner Losh the installed miniperl. It is recommended that you delete 1306e98a146SWarner Losh /usr/bin/miniperl. 1316e98a146SWarner Losh 132073113a4SWarner Losh20001005: 133073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 134685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 135073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 136073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 137073113a4SWarner Losh tree for anything to work. 138073113a4SWarner Losh 1390acc635eSWarner Losh20000928: 1400acc635eSWarner Losh There was a change in the passwd format. Need more information. 1410acc635eSWarner Losh 142be3885b3SWarner Losh20000916: 143be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 144be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 145be3885b3SWarner Losh same time as your kernel. 146be3885b3SWarner Losh 14776ec9675SWarner Losh20000914: 14876ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 14976ec9675SWarner Losh include the device will cause suspended laptops losing time 15076ec9675SWarner Losh when they resume. Include 15176ec9675SWarner Losh device pmtimer 15276ec9675SWarner Losh in your config file and 15301b9a434SWarner Losh hint.pmtimer.0.at="isa" 15476ec9675SWarner Losh to your /boot/device.hints file. 15576ec9675SWarner Losh 156f4865386SMark Murray20000911: 157f4865386SMark Murray The random device has been turned into a (pseudo-)device, 158f4865386SMark Murray rather than an option. The supplied kernel config files have 159f4865386SMark Murray been updated. You will need to do something similar in your 160f4865386SMark Murray own kernel config file. 161f4865386SMark Murray Remove: 162f4865386SMark Murray options RANDOMDEV 163f4865386SMark Murray Add: 164f4865386SMark Murray device random 165f4865386SMark Murray If you prefer to load the loadable module, you need to do 166f4865386SMark Murray nothing. 167f4865386SMark Murray 168d594498fSWarner Losh20000909: 169d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 170d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 171d594498fSWarner Losh reflect this if you load this module at boot time. 172d594498fSWarner Losh The line should read: 173d594498fSWarner Losh random_load="YES" 174d594498fSWarner Losh 1750deb7ddcSWarner Losh20000907: 1760deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 17716eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 17816eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 17916eb772dSWarner Losh sure you don't have model loading problems which might at 18016eb772dSWarner Losh first blush appear related to SMP. 18152bf24e7SWarner Losh 1825a01880bSWarner Losh20000906: 1835a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 1845a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 1855a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 1865a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 1875a01880bSWarner Losh don't have one, and you have host.conf. 1885a01880bSWarner Losh 1892b41163cSWarner Losh20000905: 19038d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 19138d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 19238d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 19338d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 19438d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 19538d6ecd2SWarner Losh 19638d6ecd2SWarner Losh20000905: 1978aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 1988aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 1998aab4bc7SWarner Losh is /boot/kernel. 2008aab4bc7SWarner Losh 2018aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 20238d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 20338d6ecd2SWarner Losh installkernel/installworld dance. 2042b41163cSWarner Losh 205d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 206d594498fSWarner Losh before booting the new kernel, since kldload will find stale 207d594498fSWarner Losh modules in that directory instead of finding them in the correct 208d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 209d594498fSWarner Losh is that the linux module crashes your machine after the update. 210d594498fSWarner Losh 211d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 212d594498fSWarner Losh mv /modules.old /boot/kernel.old 213d594498fSWarner Losh chflags noschg /kernel.old 214d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 215d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 216d594498fSWarner Losh fi 217d594498fSWarner Losh 218c22a309cSWarner Losh20000904: 219c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 220c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 221c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 222c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 223c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 224c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 225c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 226c22a309cSWarner Losh is not likely to be generated. 227c22a309cSWarner Losh 228fdb9f54dSWarner Losh20000825: 229fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 2309c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 2319c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 2329c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 2339c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 2349c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 2359c1a7444SWarner Losh messages will appear after the boot loader tries to start the 2369c1a7444SWarner Losh kernel. 2379c1a7444SWarner Losh 2389c1a7444SWarner Losh20000821: 2399c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 2409c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 2419c1a7444SWarner Losh /boot/loader.conf. 242fdb9f54dSWarner Losh 2438f250aa7SWarner Losh20000812: 2445da0d091SWarner Losh suidperl is now always built and installed on the system, but 2455da0d091SWarner Losh with permissions of 511. If you have applications that use 2465da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 2475da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 2485da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 2495da0d091SWarner Losh will fix this until the next build. 2505da0d091SWarner Losh 2515da0d091SWarner Losh20000812: 2528f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 2538f250aa7SWarner Losh visible changes that may immediately affect your configuration 2548f250aa7SWarner Losh include: 2558f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 2568f250aa7SWarner Losh - newaliases limited to root and trusted users 2578f250aa7SWarner Losh - MSA port (587) turned on by default 2588f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 2598f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 2608f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 2618f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 2628f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 2638f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 2648f250aa7SWarner Losh 26571c38472SWarner Losh20000810: 26671c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 26771c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 26871c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 26971c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 27071c38472SWarner Losh specific use for it. 27171c38472SWarner Losh 27271c38472SWarner Losh20000729: 27371c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 27471c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 27571c38472SWarner Losh /etc/rc.conf if they want to have the same setup 27671c38472SWarner Losh afterwards (unless the variables already are set, of course): 27771c38472SWarner Losh # Enable network daemons for user convenience. 27871c38472SWarner Losh inetd_enable="YES" 27971c38472SWarner Losh portmap_enable="YES" 28071c38472SWarner Losh sendmail_enable="YES" 28171c38472SWarner Losh 28271c38472SWarner Losh20000728: 28371c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 28471c38472SWarner Losh will need to change that to nullfs_load="YES". 28571c38472SWarner Losh 2861dece4a9SWarner Losh20000728: 2871dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 2881dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 2891dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 2901dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 2911dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 2921dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 2931dece4a9SWarner Losh to /MYKERNEL. 2941dece4a9SWarner Losh 295409e887cSWarner Losh20000711: 296409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 297409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 298409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 299409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 300409e887cSWarner Losh for details on potential problems that you might have and how 301409e887cSWarner Losh to get around them. 302409e887cSWarner Losh 303409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 304409e887cSWarner Losh clauses above, you needn't worry. 305409e887cSWarner Losh 306409e887cSWarner Losh20000711: 307409e887cSWarner Losh /etc/security has been updated to print the inode number of 308409e887cSWarner Losh setuid programs that have changed. You will see a large spike 309409e887cSWarner Losh in the number of changed programs the first time when you run 310409e887cSWarner Losh mergemaster to get a new /etc/security. 311409e887cSWarner Losh 312673d13f2SWarner Losh20000710: 313673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 314673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 315673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 316673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 317673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 318673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 319673d13f2SWarner Losh errors. (see below, 20000624). 320673d13f2SWarner Losh 321bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 3221dece4a9SWarner Losh 323673d13f2SWarner Losh20000709: 324c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 325c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 326c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 327673d13f2SWarner Losh ln -s aj /etc/malloc.conf 328673d13f2SWarner Losh 329e98e26cdSWarner Losh20000706: 330e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 331e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 332e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 333f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 334e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 3352c021c6cSMark Ovens interim if needed. 336e98e26cdSWarner Losh 337e98e26cdSWarner Losh20000705: 338e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 339e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 340e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 341e98e26cdSWarner Losh details. 342e98e26cdSWarner Losh 343c373950eSWarner Losh20000704: 3442f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 3452f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 3462f961bc8SWarner Losh 3472f961bc8SWarner Losh20000704: 348c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 349c373950eSWarner Losh or stop. This may cause some harmless warnings from older 350c373950eSWarner Losh rc.d scripts that haven't been updated. 351c373950eSWarner Losh 35227dc3a2bSWarner Losh20000630: 35327dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 35427dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 35527dc3a2bSWarner Losh which should be reported to des@freebsd.org. 35627dc3a2bSWarner Losh 357b8c215acSWarner Losh20000625: 358b8c215acSWarner Losh From approximately this date forward, one must have the crypto 35927dc3a2bSWarner Losh system installed in order to build the system and kernel. 36027dc3a2bSWarner Losh While not technically strictly true, one should treat it as 36127dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 36227dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 36327dc3a2bSWarner Losh were required. You should check with the latest collections 36427dc3a2bSWarner Losh to make sure that these haven't changed. 365b8c215acSWarner Losh 3667b990719SWarner Losh20000624: 3677b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 3687b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 3697b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 3707b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 3717b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 3727b990719SWarner Losh openssh and openssl should not be used to generate keys from this 3737b990719SWarner Losh date to the completion of the work. 3747b990719SWarner Losh 37527dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 37627dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 37727dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 37827dc3a2bSWarner Losh recreate the random and urandom devices. 37927dc3a2bSWarner Losh 38081e54c50SWarner Losh20000622: 38181e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 38281e54c50SWarner Losh BSD license. You may need to remove your symbolic links 38381e54c50SWarner Losh that used to be required when updating. 38481e54c50SWarner Losh 38539943833SWarner Losh20000621: 3862c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 3872a2f33fbSDaniel Baker the config file update procedure. 3882a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 389c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 390a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 39139943833SWarner Losh 392290f9ad8SWarner Losh20000620: 393290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 394290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 395290f9ad8SWarner Losh that workaround will no longer be required. 396290f9ad8SWarner Losh 39790fb6346SWarner Losh20000615: 39890fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 39990fb6346SWarner Losh ad driver. If you haven't done so already, you must update 40090fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 40190fb6346SWarner Losh devices. 40290fb6346SWarner Losh 403f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 404f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 405f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 406f75f65bbSWarner Losh may work). 407f75f65bbSWarner Losh 408ba26da8eSWarner Losh20000612: 409ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 410290f9ad8SWarner Losh on the topic before even thinking about updating. You will 411c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 412290f9ad8SWarner Losh to your config file to compile them in statically. The format 413f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 414f54a3542SWarner Losh NEWCARD for examples of the new format. 415290f9ad8SWarner Losh 416d65850ebSWarner Losh20000522: 417ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 418d65850ebSWarner Losh building a kernel after this point is advised that they need 419d65850ebSWarner Losh to rebuild their binutils (or better yet do a 420d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 421d65850ebSWarner Losh 422d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 423d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 424d9583a00SWarner Losh is recommended that you don't set this option until the problem 425d9583a00SWarner Losh is resolved. 426d9583a00SWarner Losh 4278039cedeSWarner Losh20000513: 4288039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 4298039cedeSWarner Losh 430d65850ebSWarner Losh20000510: 4318039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 4328039cedeSWarner Losh This will require some care in updating alphas. A new libstand 4338039cedeSWarner Losh is requires for the boot blocks to build properly. 4348039cedeSWarner Losh 4358039cedeSWarner Losh20000503: 4368039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 4378039cedeSWarner Losh is now available. 4388039cedeSWarner Losh 439d65850ebSWarner Losh20000502: 440d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 441d65850ebSWarner Losh connected to the kernel building instead. 442d65850ebSWarner Losh 443be149406SNik Clayton20000427: 4448039cedeSWarner Losh You may need to build gperf 4458039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 4468039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 4478039cedeSWarner Losh an option only in -current. 4488039cedeSWarner Losh 4492b8dd5f4SWarner Losh20000417: 4502b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 451f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 4522b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 4532b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 4542c021c6cSMark Ovens before you reboot, you'll need to issue: 4552b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 4562b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 4572b8dd5f4SWarner Losh 4588d9f1945SWarner Losh20000320: 4592b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 4602b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 4612b8dd5f4SWarner Losh cope if you have a problem combination is to add: 4628d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 4632b8dd5f4SWarner Losh to the start of /etc/rc.conf. 4648d9f1945SWarner Losh 465f8ab1dd6SWarner Losh20000319: 466f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 467f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 468f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 469f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 470f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 471f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 472f8ab1dd6SWarner Losh 47319cada77SWarner Losh20000318: 474f699bbbbSMark Ovens We've entered the traditional post release dumping party. 47519cada77SWarner Losh Large kernel changes are being committed and are in the 47619cada77SWarner Losh works. It is important to keep the systems' klds and kernel 47719cada77SWarner Losh in sync as kernel interfaces and structures are changing. 47819cada77SWarner Losh Before reporting kernel panics, make sure that all modules 47919cada77SWarner Losh that you are loading are up to date. 480ba228352SWarner Losh 48119cada77SWarner Losh20000315: 4826d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 4836d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 4846d23c382SWarner Losh will do the trick. This isn't critical until you remove your 4856d23c382SWarner Losh wd device entries in /dev, at which point your system will not 4866d23c382SWarner Losh boot. 4876d23c382SWarner Losh 4886d23c382SWarner Losh20000315: 48919cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 49019cada77SWarner Losh to upgrade to 4.0 from 3.x. 49157199806SWarner Losh 492dc0dbf5cSWarner LoshCOMMON ITEMS: 493dc0dbf5cSWarner Losh 494a24eff53SWarner Losh General Notes 495a24eff53SWarner Losh ------------- 496a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 497a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 498a24eff53SWarner Losh installworld. This is especially true when upgrading between 499a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 500a24eff53SWarner Losh or several minor releases, or when several months have passed 501a24eff53SWarner Losh on the -current branch). 502a24eff53SWarner Losh 503dc0dbf5cSWarner Losh To build a kernel 504dc0dbf5cSWarner Losh ----------------- 505ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 506f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 507ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 5081e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 5091e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 510dc0dbf5cSWarner Losh 511ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 512ba01eb20SWarner Losh -------------------------------------------------------------- 513ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 514ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 515ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 516ba01eb20SWarner Losh make depend 517ba01eb20SWarner Losh make 518ba01eb20SWarner Losh make install 519ba01eb20SWarner Losh 520ba01eb20SWarner Losh [1] If in doubt, -r might help here. 521ba01eb20SWarner Losh 522ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 523ba01eb20SWarner Losh 524ba01eb20SWarner Losh To rebuild everything and install it on the current system. 525ba01eb20SWarner Losh ----------------------------------------------------------- 526759f0aefSWarner Losh make world 527fdb9f54dSWarner Losh Build a new kernel, see above. 528759f0aefSWarner Losh 5291dece4a9SWarner Losh To upgrade from 4.x-stable to current 530ba26da8eSWarner Losh ------------------------------------- 531ba26da8eSWarner Losh make buildworld 5321e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 5337595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 5341e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 535ba26da8eSWarner Losh make installworld 5367595222aSWarner Losh mergemaster 537134d2e86SWarner Losh [1] 538ba26da8eSWarner Losh <reboot> 539ba26da8eSWarner Losh 540fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 541fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 542fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 543fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 544fdb9f54dSWarner Losh the UPDATING entries. 545ba26da8eSWarner Losh 5461dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 5471dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 5481dece4a9SWarner Losh your sources that you have read and understood all the recent 5491dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 5501dece4a9SWarner Losh much fewer pitfalls. 5511dece4a9SWarner Losh 552134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 553134d2e86SWarner Losh should disable them at this point so they don't crash your 554134d2e86SWarner Losh system on reboot. 555134d2e86SWarner Losh 5569c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 5579c1a7444SWarner Losh your own device.hints to reflect your unique hardware 5589c1a7444SWarner Losh configuration. 5599c1a7444SWarner Losh 560dc0dbf5cSWarner LoshFORMAT: 561dc0dbf5cSWarner Losh 562f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 5631fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 564f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 565f8ab1dd6SWarner Loshprevious releases if your system is older than this. 5661fc1a0dcSWarner Losh 5673645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 5683645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 569f8c77507SWarner Losh 57097d92980SPeter Wemm$FreeBSD$ 571