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 8*91dd3b53SWarner Losh20010423: 9*91dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 10*91dd3b53SWarner Losh 11*91dd3b53SWarner Losh20010411: 12*91dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 13*91dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 14*91dd3b53SWarner Losh Update only if you understand that you must not use the old 15*91dd3b53SWarner Losh fsck with the new kernel ever. 16*91dd3b53SWarner Losh 17933b3269SWarner Losh20010330: 18933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 19933b3269SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page fora 20933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 21933b3269SWarner Losh 22933b3269SWarner Losh20010319: 23933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 24933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 25933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 26933b3269SWarner Losh without updates to /etc/hosts.{allow,deny}. 27933b3269SWarner Losh 28933b3269SWarner Losh20010312: 29933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 30933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 31933b3269SWarner Losh 32933b3269SWarner Losh20010312: 33933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 34933b3269SWarner Losh instead of ad-hoc. 35933b3269SWarner Losh 36933b3269SWarner Losh20010310: 37933b3269SWarner Losh /dev/urandmon should be a sumbolic link to /dev/random now. 38933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 39933b3269SWarner Losh ssh might not work if you don't. 40933b3269SWarner Losh 41d325cf65SWarner Losh20010220: 42d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 43d325cf65SWarner Losh safe to go back into the water. 44d325cf65SWarner Losh 45024daae6SWarner Losh20010211: 46024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 47024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 48024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 49024daae6SWarner Losh that before upgrading would be a good time to do a level 0 50024daae6SWarner Losh dump of your system. No, really, I mean it this time. 51024daae6SWarner Losh 52024daae6SWarner Losh To get to the new system, you'll need to use the following 53024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 54024daae6SWarner Losh don't have to move this to the updating section. 55024daae6SWarner Losh 56024daae6SWarner Losh To get around the installworld problem, do: 57024daae6SWarner Losh # cd /usr/src/usr.bin/sed 58024daae6SWarner Losh # make install 59024daae6SWarner Losh # cd /usr/src 60024daae6SWarner Losh # make installworld 61024daae6SWarner Losh If that doesn't work, then try: 62024daae6SWarner Losh # make -k installworld 63024daae6SWarner Losh # make installworld 64024daae6SWarner Losh 65024daae6SWarner Losh20010207: 66024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 67024daae6SWarner Losh do not include devfs in your kernel as problems result. 68024daae6SWarner Losh 69024daae6SWarner Losh20010205: 707595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 71024daae6SWarner Losh Remove them from your config. 72024daae6SWarner Losh 731e159248SWarner Losh20010122: 741e159248SWarner Losh ****************************** WARNING ****************************** 751e159248SWarner Losh buildkernel has been changed slightly 761e159248SWarner Losh ****************************** WARNING ****************************** 771e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 781e159248SWarner Losh should update your scripts and make.conf accordingly. 791e159248SWarner Losh 801e159248SWarner Losh20010119: 811e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 821e159248SWarner Losh This requires a new config to build correctly. 831e159248SWarner Losh 84aac7dfeaSWarner Losh20010116: 85aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 86aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 87aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 88aac7dfeaSWarner Losh 89aac7dfeaSWarner Losh20010110: 90aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 91aac7dfeaSWarner Losh 92aac7dfeaSWarner Losh20010102: 93aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 94aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 95aac7dfeaSWarner Losh 9663c90c9eSWarner Losh20010101: 9763c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 9863c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 995fd2a895SWarner Losh dump while building termcap. You can work around this problem 10063c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 10163c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 10263c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 10363c90c9eSWarner Losh might have been ignored by the -k option. 10463c90c9eSWarner Losh 1055fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 1065fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 1075fd2a895SWarner Losh of this working. 1085fd2a895SWarner Losh 109aac7dfeaSWarner Losh20001228: 110aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 111aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 112aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 113aac7dfeaSWarner Losh 114de2bcc63SWarner Losh20001218: 115de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 116de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 117de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 118de2bcc63SWarner Losh cards will not be recognized without it. 119de2bcc63SWarner Losh 120960773f7SWarner Losh20001205: 121960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 122960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 123960773f7SWarner Losh adding the following in pam.conf: 124960773f7SWarner Losh 125960773f7SWarner Losh sshd auth sufficient pam_skey.so 126960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 127960773f7SWarner Losh sshd session required pam_permit.so 128960773f7SWarner Losh 1290acc635eSWarner Losh20001031: 1300acc635eSWarner Losh cvs updated to 1.11. 1310acc635eSWarner Losh 1320acc635eSWarner Losh20001020: 1330acc635eSWarner Losh The random device needs more entropy, so you need to make sure 1340acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 1350acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 1360acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 1370acc635eSWarner Losh workaround. 1380acc635eSWarner Losh 1390acc635eSWarner Losh20001010: 1400acc635eSWarner Losh ****************************** WARNING ****************************** 1410acc635eSWarner Losh Sendmail has been updated. 1420acc635eSWarner Losh ****************************** WARNING ****************************** 1430acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 1440acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 1450acc635eSWarner Losh is set. 1460acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 1470acc635eSWarner Losh commands. 1480acc635eSWarner Losh o Now using sendmail's version of vacation(1). 1490acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 1500acc635eSWarner Losh in /usr/share/sendmail/cf. 1510acc635eSWarner Losh o sendmail.cw changed to local-host-names 1520acc635eSWarner Losh 1530acc635eSWarner Losh More details can be found at 1540acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 1550acc635eSWarner Losh 1566e98a146SWarner Losh20001009: 1576e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 1586e98a146SWarner Losh your entire ports tree, or you will have problems. 1596e98a146SWarner Losh 1606e98a146SWarner Losh20001006: 161685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 1626e98a146SWarner Losh the installed miniperl. It is recommended that you delete 1636e98a146SWarner Losh /usr/bin/miniperl. 1646e98a146SWarner Losh 165073113a4SWarner Losh20001005: 166073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 167685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 168073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 169073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 170073113a4SWarner Losh tree for anything to work. 171073113a4SWarner Losh 1720acc635eSWarner Losh20000928: 1730acc635eSWarner Losh There was a change in the passwd format. Need more information. 1740acc635eSWarner Losh 175be3885b3SWarner Losh20000916: 176be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 177be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 178be3885b3SWarner Losh same time as your kernel. 179be3885b3SWarner Losh 18076ec9675SWarner Losh20000914: 18176ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 18276ec9675SWarner Losh include the device will cause suspended laptops losing time 18376ec9675SWarner Losh when they resume. Include 18476ec9675SWarner Losh device pmtimer 18576ec9675SWarner Losh in your config file and 18601b9a434SWarner Losh hint.pmtimer.0.at="isa" 18776ec9675SWarner Losh to your /boot/device.hints file. 18876ec9675SWarner Losh 189f4865386SMark Murray20000911: 190f4865386SMark Murray The random device has been turned into a (pseudo-)device, 191f4865386SMark Murray rather than an option. The supplied kernel config files have 192f4865386SMark Murray been updated. You will need to do something similar in your 193f4865386SMark Murray own kernel config file. 194f4865386SMark Murray Remove: 195f4865386SMark Murray options RANDOMDEV 196f4865386SMark Murray Add: 197f4865386SMark Murray device random 198f4865386SMark Murray If you prefer to load the loadable module, you need to do 199f4865386SMark Murray nothing. 200f4865386SMark Murray 201d594498fSWarner Losh20000909: 202d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 203d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 204d594498fSWarner Losh reflect this if you load this module at boot time. 205d594498fSWarner Losh The line should read: 206d594498fSWarner Losh random_load="YES" 207d594498fSWarner Losh 2080deb7ddcSWarner Losh20000907: 2090deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 21016eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 21116eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 21216eb772dSWarner Losh sure you don't have model loading problems which might at 21316eb772dSWarner Losh first blush appear related to SMP. 21452bf24e7SWarner Losh 2155a01880bSWarner Losh20000906: 2165a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 2175a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 2185a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 2195a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 2205a01880bSWarner Losh don't have one, and you have host.conf. 2215a01880bSWarner Losh 2222b41163cSWarner Losh20000905: 22338d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 22438d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 22538d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 22638d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 22738d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 22838d6ecd2SWarner Losh 22938d6ecd2SWarner Losh20000905: 2308aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 2318aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 2328aab4bc7SWarner Losh is /boot/kernel. 2338aab4bc7SWarner Losh 2348aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 23538d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 23638d6ecd2SWarner Losh installkernel/installworld dance. 2372b41163cSWarner Losh 238d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 239d594498fSWarner Losh before booting the new kernel, since kldload will find stale 240d594498fSWarner Losh modules in that directory instead of finding them in the correct 241d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 242d594498fSWarner Losh is that the linux module crashes your machine after the update. 243d594498fSWarner Losh 244d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 245d594498fSWarner Losh mv /modules.old /boot/kernel.old 246d594498fSWarner Losh chflags noschg /kernel.old 247d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 248d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 249d594498fSWarner Losh fi 250d594498fSWarner Losh 251c22a309cSWarner Losh20000904: 252c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 253c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 254c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 255c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 256c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 257c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 258c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 259c22a309cSWarner Losh is not likely to be generated. 260c22a309cSWarner Losh 261fdb9f54dSWarner Losh20000825: 262fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 2639c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 2649c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 2659c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 2669c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 2679c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 2689c1a7444SWarner Losh messages will appear after the boot loader tries to start the 2699c1a7444SWarner Losh kernel. 2709c1a7444SWarner Losh 2719c1a7444SWarner Losh20000821: 2729c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 2739c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 2749c1a7444SWarner Losh /boot/loader.conf. 275fdb9f54dSWarner Losh 2768f250aa7SWarner Losh20000812: 2775da0d091SWarner Losh suidperl is now always built and installed on the system, but 2785da0d091SWarner Losh with permissions of 511. If you have applications that use 2795da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 2805da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 2815da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 2825da0d091SWarner Losh will fix this until the next build. 2835da0d091SWarner Losh 2845da0d091SWarner Losh20000812: 2858f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 2868f250aa7SWarner Losh visible changes that may immediately affect your configuration 2878f250aa7SWarner Losh include: 2888f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 2898f250aa7SWarner Losh - newaliases limited to root and trusted users 2908f250aa7SWarner Losh - MSA port (587) turned on by default 2918f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 2928f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 2938f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 2948f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 2958f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 2968f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 2978f250aa7SWarner Losh 29871c38472SWarner Losh20000810: 29971c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 30071c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 30171c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 30271c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 30371c38472SWarner Losh specific use for it. 30471c38472SWarner Losh 30571c38472SWarner Losh20000729: 30671c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 30771c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 30871c38472SWarner Losh /etc/rc.conf if they want to have the same setup 30971c38472SWarner Losh afterwards (unless the variables already are set, of course): 31071c38472SWarner Losh # Enable network daemons for user convenience. 31171c38472SWarner Losh inetd_enable="YES" 31271c38472SWarner Losh portmap_enable="YES" 31371c38472SWarner Losh sendmail_enable="YES" 31471c38472SWarner Losh 31571c38472SWarner Losh20000728: 31671c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 31771c38472SWarner Losh will need to change that to nullfs_load="YES". 31871c38472SWarner Losh 3191dece4a9SWarner Losh20000728: 3201dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 3211dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 3221dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 3231dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 3241dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 3251dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 3261dece4a9SWarner Losh to /MYKERNEL. 3271dece4a9SWarner Losh 328409e887cSWarner Losh20000711: 329409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 330409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 331409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 332409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 333409e887cSWarner Losh for details on potential problems that you might have and how 334409e887cSWarner Losh to get around them. 335409e887cSWarner Losh 336409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 337409e887cSWarner Losh clauses above, you needn't worry. 338409e887cSWarner Losh 339409e887cSWarner Losh20000711: 340409e887cSWarner Losh /etc/security has been updated to print the inode number of 341409e887cSWarner Losh setuid programs that have changed. You will see a large spike 342409e887cSWarner Losh in the number of changed programs the first time when you run 343409e887cSWarner Losh mergemaster to get a new /etc/security. 344409e887cSWarner Losh 345673d13f2SWarner Losh20000710: 346673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 347673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 348673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 349673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 350673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 351673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 352673d13f2SWarner Losh errors. (see below, 20000624). 353673d13f2SWarner Losh 354bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 3551dece4a9SWarner Losh 356673d13f2SWarner Losh20000709: 357c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 358c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 359c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 360673d13f2SWarner Losh ln -s aj /etc/malloc.conf 361673d13f2SWarner Losh 362e98e26cdSWarner Losh20000706: 363e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 364e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 365e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 366f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 367e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 3682c021c6cSMark Ovens interim if needed. 369e98e26cdSWarner Losh 370e98e26cdSWarner Losh20000705: 371e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 372e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 373e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 374e98e26cdSWarner Losh details. 375e98e26cdSWarner Losh 376c373950eSWarner Losh20000704: 3772f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 3782f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 3792f961bc8SWarner Losh 3802f961bc8SWarner Losh20000704: 381c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 382c373950eSWarner Losh or stop. This may cause some harmless warnings from older 383c373950eSWarner Losh rc.d scripts that haven't been updated. 384c373950eSWarner Losh 38527dc3a2bSWarner Losh20000630: 38627dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 38727dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 38827dc3a2bSWarner Losh which should be reported to des@freebsd.org. 38927dc3a2bSWarner Losh 390b8c215acSWarner Losh20000625: 391b8c215acSWarner Losh From approximately this date forward, one must have the crypto 39227dc3a2bSWarner Losh system installed in order to build the system and kernel. 39327dc3a2bSWarner Losh While not technically strictly true, one should treat it as 39427dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 39527dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 39627dc3a2bSWarner Losh were required. You should check with the latest collections 39727dc3a2bSWarner Losh to make sure that these haven't changed. 398b8c215acSWarner Losh 3997b990719SWarner Losh20000624: 4007b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 4017b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 4027b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 4037b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 4047b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 4057b990719SWarner Losh openssh and openssl should not be used to generate keys from this 4067b990719SWarner Losh date to the completion of the work. 4077b990719SWarner Losh 40827dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 40927dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 41027dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 41127dc3a2bSWarner Losh recreate the random and urandom devices. 41227dc3a2bSWarner Losh 41381e54c50SWarner Losh20000622: 41481e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 41581e54c50SWarner Losh BSD license. You may need to remove your symbolic links 41681e54c50SWarner Losh that used to be required when updating. 41781e54c50SWarner Losh 41839943833SWarner Losh20000621: 4192c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 4202a2f33fbSDaniel Baker the config file update procedure. 4212a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 422c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 423a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 42439943833SWarner Losh 425290f9ad8SWarner Losh20000620: 426290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 427290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 428290f9ad8SWarner Losh that workaround will no longer be required. 429290f9ad8SWarner Losh 43090fb6346SWarner Losh20000615: 43190fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 43290fb6346SWarner Losh ad driver. If you haven't done so already, you must update 43390fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 43490fb6346SWarner Losh devices. 43590fb6346SWarner Losh 436f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 437f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 438f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 439f75f65bbSWarner Losh may work). 440f75f65bbSWarner Losh 441ba26da8eSWarner Losh20000612: 442ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 443290f9ad8SWarner Losh on the topic before even thinking about updating. You will 444c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 445290f9ad8SWarner Losh to your config file to compile them in statically. The format 446f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 447f54a3542SWarner Losh NEWCARD for examples of the new format. 448290f9ad8SWarner Losh 449d65850ebSWarner Losh20000522: 450ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 451d65850ebSWarner Losh building a kernel after this point is advised that they need 452d65850ebSWarner Losh to rebuild their binutils (or better yet do a 453d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 454d65850ebSWarner Losh 455d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 456d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 457d9583a00SWarner Losh is recommended that you don't set this option until the problem 458d9583a00SWarner Losh is resolved. 459d9583a00SWarner Losh 4608039cedeSWarner Losh20000513: 4618039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 4628039cedeSWarner Losh 463d65850ebSWarner Losh20000510: 4648039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 4658039cedeSWarner Losh This will require some care in updating alphas. A new libstand 4668039cedeSWarner Losh is requires for the boot blocks to build properly. 4678039cedeSWarner Losh 4688039cedeSWarner Losh20000503: 4698039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 4708039cedeSWarner Losh is now available. 4718039cedeSWarner Losh 472d65850ebSWarner Losh20000502: 473d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 474d65850ebSWarner Losh connected to the kernel building instead. 475d65850ebSWarner Losh 476be149406SNik Clayton20000427: 4778039cedeSWarner Losh You may need to build gperf 4788039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 4798039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 4808039cedeSWarner Losh an option only in -current. 4818039cedeSWarner Losh 4822b8dd5f4SWarner Losh20000417: 4832b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 484f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 4852b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 4862b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 4872c021c6cSMark Ovens before you reboot, you'll need to issue: 4882b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 4892b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 4902b8dd5f4SWarner Losh 4918d9f1945SWarner Losh20000320: 4922b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 4932b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 4942b8dd5f4SWarner Losh cope if you have a problem combination is to add: 4958d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 4962b8dd5f4SWarner Losh to the start of /etc/rc.conf. 4978d9f1945SWarner Losh 498f8ab1dd6SWarner Losh20000319: 499f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 500f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 501f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 502f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 503f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 504f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 505f8ab1dd6SWarner Losh 50619cada77SWarner Losh20000318: 507f699bbbbSMark Ovens We've entered the traditional post release dumping party. 50819cada77SWarner Losh Large kernel changes are being committed and are in the 50919cada77SWarner Losh works. It is important to keep the systems' klds and kernel 51019cada77SWarner Losh in sync as kernel interfaces and structures are changing. 51119cada77SWarner Losh Before reporting kernel panics, make sure that all modules 51219cada77SWarner Losh that you are loading are up to date. 513ba228352SWarner Losh 51419cada77SWarner Losh20000315: 5156d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 5166d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 5176d23c382SWarner Losh will do the trick. This isn't critical until you remove your 5186d23c382SWarner Losh wd device entries in /dev, at which point your system will not 5196d23c382SWarner Losh boot. 5206d23c382SWarner Losh 5216d23c382SWarner Losh20000315: 52219cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 52319cada77SWarner Losh to upgrade to 4.0 from 3.x. 52457199806SWarner Losh 525dc0dbf5cSWarner LoshCOMMON ITEMS: 526dc0dbf5cSWarner Losh 527a24eff53SWarner Losh General Notes 528a24eff53SWarner Losh ------------- 529a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 530a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 531a24eff53SWarner Losh installworld. This is especially true when upgrading between 532a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 533a24eff53SWarner Losh or several minor releases, or when several months have passed 534a24eff53SWarner Losh on the -current branch). 535a24eff53SWarner Losh 536dc0dbf5cSWarner Losh To build a kernel 537dc0dbf5cSWarner Losh ----------------- 538ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 539f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 540ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 5411e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 5421e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 543dc0dbf5cSWarner Losh 544ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 545ba01eb20SWarner Losh -------------------------------------------------------------- 546ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 547ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 548ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 549ba01eb20SWarner Losh make depend 550ba01eb20SWarner Losh make 551ba01eb20SWarner Losh make install 552ba01eb20SWarner Losh 553ba01eb20SWarner Losh [1] If in doubt, -r might help here. 554ba01eb20SWarner Losh 555ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 556ba01eb20SWarner Losh 557ba01eb20SWarner Losh To rebuild everything and install it on the current system. 558ba01eb20SWarner Losh ----------------------------------------------------------- 559759f0aefSWarner Losh make world 560fdb9f54dSWarner Losh Build a new kernel, see above. 561759f0aefSWarner Losh 5621dece4a9SWarner Losh To upgrade from 4.x-stable to current 563ba26da8eSWarner Losh ------------------------------------- 564ba26da8eSWarner Losh make buildworld 5651e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 5667595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 5671e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 568ba26da8eSWarner Losh make installworld 5697595222aSWarner Losh mergemaster 570134d2e86SWarner Losh [1] 571ba26da8eSWarner Losh <reboot> 572ba26da8eSWarner Losh 573fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 574fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 575fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 576fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 577fdb9f54dSWarner Losh the UPDATING entries. 578ba26da8eSWarner Losh 5791dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 5801dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 5811dece4a9SWarner Losh your sources that you have read and understood all the recent 5821dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 5831dece4a9SWarner Losh much fewer pitfalls. 5841dece4a9SWarner Losh 585134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 586134d2e86SWarner Losh should disable them at this point so they don't crash your 587134d2e86SWarner Losh system on reboot. 588134d2e86SWarner Losh 5899c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 5909c1a7444SWarner Losh your own device.hints to reflect your unique hardware 5919c1a7444SWarner Losh configuration. 5929c1a7444SWarner Losh 593dc0dbf5cSWarner LoshFORMAT: 594dc0dbf5cSWarner Losh 595f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 5961fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 597f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 598f8ab1dd6SWarner Loshprevious releases if your system is older than this. 5991fc1a0dcSWarner Losh 6003645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 6013645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 602f8c77507SWarner Losh 60397d92980SPeter Wemm$FreeBSD$ 604