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 8933b3269SWarner Losh20010330: 9933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 10933b3269SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page fora 11933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 12933b3269SWarner Losh 13933b3269SWarner Losh20010319: 14933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 15933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 16933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 17933b3269SWarner Losh without updates to /etc/hosts.{allow,deny}. 18933b3269SWarner Losh 19933b3269SWarner Losh20010312: 20933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 21933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 22933b3269SWarner Losh 23933b3269SWarner Losh20010312: 24933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 25933b3269SWarner Losh instead of ad-hoc. 26933b3269SWarner Losh 27933b3269SWarner Losh20010310: 28933b3269SWarner Losh /dev/urandmon should be a sumbolic link to /dev/random now. 29933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 30933b3269SWarner Losh ssh might not work if you don't. 31933b3269SWarner Losh 32d325cf65SWarner Losh20010220: 33d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 34d325cf65SWarner Losh safe to go back into the water. 35d325cf65SWarner Losh 36024daae6SWarner Losh20010211: 37024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 38024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 39024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 40024daae6SWarner Losh that before upgrading would be a good time to do a level 0 41024daae6SWarner Losh dump of your system. No, really, I mean it this time. 42024daae6SWarner Losh 43024daae6SWarner Losh To get to the new system, you'll need to use the following 44024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 45024daae6SWarner Losh don't have to move this to the updating section. 46024daae6SWarner Losh 47024daae6SWarner Losh To get around the installworld problem, do: 48024daae6SWarner Losh # cd /usr/src/usr.bin/sed 49024daae6SWarner Losh # make install 50024daae6SWarner Losh # cd /usr/src 51024daae6SWarner Losh # make installworld 52024daae6SWarner Losh If that doesn't work, then try: 53024daae6SWarner Losh # make -k installworld 54024daae6SWarner Losh # make installworld 55024daae6SWarner Losh 56024daae6SWarner Losh20010207: 57024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 58024daae6SWarner Losh do not include devfs in your kernel as problems result. 59024daae6SWarner Losh 60024daae6SWarner Losh20010205: 617595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 62024daae6SWarner Losh Remove them from your config. 63024daae6SWarner Losh 641e159248SWarner Losh20010122: 651e159248SWarner Losh ****************************** WARNING ****************************** 661e159248SWarner Losh buildkernel has been changed slightly 671e159248SWarner Losh ****************************** WARNING ****************************** 681e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 691e159248SWarner Losh should update your scripts and make.conf accordingly. 701e159248SWarner Losh 711e159248SWarner Losh20010119: 721e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 731e159248SWarner Losh This requires a new config to build correctly. 741e159248SWarner Losh 75aac7dfeaSWarner Losh20010116: 76aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 77aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 78aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 79aac7dfeaSWarner Losh 80aac7dfeaSWarner Losh20010110: 81aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 82aac7dfeaSWarner Losh 83aac7dfeaSWarner Losh20010102: 84aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 85aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 86aac7dfeaSWarner Losh 8763c90c9eSWarner Losh20010101: 8863c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 8963c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 905fd2a895SWarner Losh dump while building termcap. You can work around this problem 9163c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 9263c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 9363c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 9463c90c9eSWarner Losh might have been ignored by the -k option. 9563c90c9eSWarner Losh 965fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 975fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 985fd2a895SWarner Losh of this working. 995fd2a895SWarner Losh 100aac7dfeaSWarner Losh20001228: 101aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 102aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 103aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 104aac7dfeaSWarner Losh 105de2bcc63SWarner Losh20001218: 106de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 107de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 108de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 109de2bcc63SWarner Losh cards will not be recognized without it. 110de2bcc63SWarner Losh 111960773f7SWarner Losh20001205: 112960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 113960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 114960773f7SWarner Losh adding the following in pam.conf: 115960773f7SWarner Losh 116960773f7SWarner Losh sshd auth sufficient pam_skey.so 117960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 118960773f7SWarner Losh sshd session required pam_permit.so 119960773f7SWarner Losh 1200acc635eSWarner Losh20001031: 1210acc635eSWarner Losh cvs updated to 1.11. 1220acc635eSWarner Losh 1230acc635eSWarner Losh20001020: 1240acc635eSWarner Losh The random device needs more entropy, so you need to make sure 1250acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 1260acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 1270acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 1280acc635eSWarner Losh workaround. 1290acc635eSWarner Losh 1300acc635eSWarner Losh20001010: 1310acc635eSWarner Losh ****************************** WARNING ****************************** 1320acc635eSWarner Losh Sendmail has been updated. 1330acc635eSWarner Losh ****************************** WARNING ****************************** 1340acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 1350acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 1360acc635eSWarner Losh is set. 1370acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 1380acc635eSWarner Losh commands. 1390acc635eSWarner Losh o Now using sendmail's version of vacation(1). 1400acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 1410acc635eSWarner Losh in /usr/share/sendmail/cf. 1420acc635eSWarner Losh o sendmail.cw changed to local-host-names 1430acc635eSWarner Losh 1440acc635eSWarner Losh More details can be found at 1450acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 1460acc635eSWarner Losh 1476e98a146SWarner Losh20001009: 1486e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 1496e98a146SWarner Losh your entire ports tree, or you will have problems. 1506e98a146SWarner Losh 1516e98a146SWarner Losh20001006: 152685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 1536e98a146SWarner Losh the installed miniperl. It is recommended that you delete 1546e98a146SWarner Losh /usr/bin/miniperl. 1556e98a146SWarner Losh 156073113a4SWarner Losh20001005: 157073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 158685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 159073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 160073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 161073113a4SWarner Losh tree for anything to work. 162073113a4SWarner Losh 1630acc635eSWarner Losh20000928: 1640acc635eSWarner Losh There was a change in the passwd format. Need more information. 1650acc635eSWarner Losh 166be3885b3SWarner Losh20000916: 167be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 168be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 169be3885b3SWarner Losh same time as your kernel. 170be3885b3SWarner Losh 17176ec9675SWarner Losh20000914: 17276ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 17376ec9675SWarner Losh include the device will cause suspended laptops losing time 17476ec9675SWarner Losh when they resume. Include 17576ec9675SWarner Losh device pmtimer 17676ec9675SWarner Losh in your config file and 17701b9a434SWarner Losh hint.pmtimer.0.at="isa" 17876ec9675SWarner Losh to your /boot/device.hints file. 17976ec9675SWarner Losh 180f4865386SMark Murray20000911: 181f4865386SMark Murray The random device has been turned into a (pseudo-)device, 182f4865386SMark Murray rather than an option. The supplied kernel config files have 183f4865386SMark Murray been updated. You will need to do something similar in your 184f4865386SMark Murray own kernel config file. 185f4865386SMark Murray Remove: 186f4865386SMark Murray options RANDOMDEV 187f4865386SMark Murray Add: 188f4865386SMark Murray device random 189f4865386SMark Murray If you prefer to load the loadable module, you need to do 190f4865386SMark Murray nothing. 191f4865386SMark Murray 192d594498fSWarner Losh20000909: 193d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 194d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 195d594498fSWarner Losh reflect this if you load this module at boot time. 196d594498fSWarner Losh The line should read: 197d594498fSWarner Losh random_load="YES" 198d594498fSWarner Losh 1990deb7ddcSWarner Losh20000907: 2000deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 20116eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 20216eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 20316eb772dSWarner Losh sure you don't have model loading problems which might at 20416eb772dSWarner Losh first blush appear related to SMP. 20552bf24e7SWarner Losh 2065a01880bSWarner Losh20000906: 2075a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 2085a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 2095a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 2105a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 2115a01880bSWarner Losh don't have one, and you have host.conf. 2125a01880bSWarner Losh 2132b41163cSWarner Losh20000905: 21438d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 21538d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 21638d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 21738d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 21838d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 21938d6ecd2SWarner Losh 22038d6ecd2SWarner Losh20000905: 2218aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 2228aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 2238aab4bc7SWarner Losh is /boot/kernel. 2248aab4bc7SWarner Losh 2258aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 22638d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 22738d6ecd2SWarner Losh installkernel/installworld dance. 2282b41163cSWarner Losh 229d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 230d594498fSWarner Losh before booting the new kernel, since kldload will find stale 231d594498fSWarner Losh modules in that directory instead of finding them in the correct 232d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 233d594498fSWarner Losh is that the linux module crashes your machine after the update. 234d594498fSWarner Losh 235d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 236d594498fSWarner Losh mv /modules.old /boot/kernel.old 237d594498fSWarner Losh chflags noschg /kernel.old 238d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 239d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 240d594498fSWarner Losh fi 241d594498fSWarner Losh 242c22a309cSWarner Losh20000904: 243c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 244c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 245c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 246c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 247c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 248c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 249c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 250c22a309cSWarner Losh is not likely to be generated. 251c22a309cSWarner Losh 252fdb9f54dSWarner Losh20000825: 253fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 2549c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 2559c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 2569c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 2579c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 2589c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 2599c1a7444SWarner Losh messages will appear after the boot loader tries to start the 2609c1a7444SWarner Losh kernel. 2619c1a7444SWarner Losh 2629c1a7444SWarner Losh20000821: 2639c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 2649c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 2659c1a7444SWarner Losh /boot/loader.conf. 266fdb9f54dSWarner Losh 2678f250aa7SWarner Losh20000812: 2685da0d091SWarner Losh suidperl is now always built and installed on the system, but 2695da0d091SWarner Losh with permissions of 511. If you have applications that use 2705da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 2715da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 2725da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 2735da0d091SWarner Losh will fix this until the next build. 2745da0d091SWarner Losh 2755da0d091SWarner Losh20000812: 2768f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 2778f250aa7SWarner Losh visible changes that may immediately affect your configuration 2788f250aa7SWarner Losh include: 2798f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 2808f250aa7SWarner Losh - newaliases limited to root and trusted users 2818f250aa7SWarner Losh - MSA port (587) turned on by default 2828f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 2838f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 2848f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 2858f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 2868f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 2878f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 2888f250aa7SWarner Losh 28971c38472SWarner Losh20000810: 29071c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 29171c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 29271c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 29371c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 29471c38472SWarner Losh specific use for it. 29571c38472SWarner Losh 29671c38472SWarner Losh20000729: 29771c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 29871c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 29971c38472SWarner Losh /etc/rc.conf if they want to have the same setup 30071c38472SWarner Losh afterwards (unless the variables already are set, of course): 30171c38472SWarner Losh # Enable network daemons for user convenience. 30271c38472SWarner Losh inetd_enable="YES" 30371c38472SWarner Losh portmap_enable="YES" 30471c38472SWarner Losh sendmail_enable="YES" 30571c38472SWarner Losh 30671c38472SWarner Losh20000728: 30771c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 30871c38472SWarner Losh will need to change that to nullfs_load="YES". 30971c38472SWarner Losh 3101dece4a9SWarner Losh20000728: 3111dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 3121dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 3131dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 3141dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 3151dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 3161dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 3171dece4a9SWarner Losh to /MYKERNEL. 3181dece4a9SWarner Losh 319409e887cSWarner Losh20000711: 320409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 321409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 322409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 323409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 324409e887cSWarner Losh for details on potential problems that you might have and how 325409e887cSWarner Losh to get around them. 326409e887cSWarner Losh 327409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 328409e887cSWarner Losh clauses above, you needn't worry. 329409e887cSWarner Losh 330409e887cSWarner Losh20000711: 331409e887cSWarner Losh /etc/security has been updated to print the inode number of 332409e887cSWarner Losh setuid programs that have changed. You will see a large spike 333409e887cSWarner Losh in the number of changed programs the first time when you run 334409e887cSWarner Losh mergemaster to get a new /etc/security. 335409e887cSWarner Losh 336673d13f2SWarner Losh20000710: 337673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 338673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 339673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 340673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 341673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 342673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 343673d13f2SWarner Losh errors. (see below, 20000624). 344673d13f2SWarner Losh 345bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 3461dece4a9SWarner Losh 347673d13f2SWarner Losh20000709: 348c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 349c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 350c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 351673d13f2SWarner Losh ln -s aj /etc/malloc.conf 352673d13f2SWarner Losh 353e98e26cdSWarner Losh20000706: 354e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 355e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 356e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 357f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 358e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 3592c021c6cSMark Ovens interim if needed. 360e98e26cdSWarner Losh 361e98e26cdSWarner Losh20000705: 362e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 363e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 364e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 365e98e26cdSWarner Losh details. 366e98e26cdSWarner Losh 367c373950eSWarner Losh20000704: 3682f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 3692f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 3702f961bc8SWarner Losh 3712f961bc8SWarner Losh20000704: 372c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 373c373950eSWarner Losh or stop. This may cause some harmless warnings from older 374c373950eSWarner Losh rc.d scripts that haven't been updated. 375c373950eSWarner Losh 37627dc3a2bSWarner Losh20000630: 37727dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 37827dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 37927dc3a2bSWarner Losh which should be reported to des@freebsd.org. 38027dc3a2bSWarner Losh 381b8c215acSWarner Losh20000625: 382b8c215acSWarner Losh From approximately this date forward, one must have the crypto 38327dc3a2bSWarner Losh system installed in order to build the system and kernel. 38427dc3a2bSWarner Losh While not technically strictly true, one should treat it as 38527dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 38627dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 38727dc3a2bSWarner Losh were required. You should check with the latest collections 38827dc3a2bSWarner Losh to make sure that these haven't changed. 389b8c215acSWarner Losh 3907b990719SWarner Losh20000624: 3917b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 3927b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 3937b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 3947b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 3957b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 3967b990719SWarner Losh openssh and openssl should not be used to generate keys from this 3977b990719SWarner Losh date to the completion of the work. 3987b990719SWarner Losh 39927dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 40027dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 40127dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 40227dc3a2bSWarner Losh recreate the random and urandom devices. 40327dc3a2bSWarner Losh 40481e54c50SWarner Losh20000622: 40581e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 40681e54c50SWarner Losh BSD license. You may need to remove your symbolic links 40781e54c50SWarner Losh that used to be required when updating. 40881e54c50SWarner Losh 40939943833SWarner Losh20000621: 4102c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 4112a2f33fbSDaniel Baker the config file update procedure. 4122a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 413c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 414a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 41539943833SWarner Losh 416290f9ad8SWarner Losh20000620: 417290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 418290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 419290f9ad8SWarner Losh that workaround will no longer be required. 420290f9ad8SWarner Losh 42190fb6346SWarner Losh20000615: 42290fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 42390fb6346SWarner Losh ad driver. If you haven't done so already, you must update 42490fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 42590fb6346SWarner Losh devices. 42690fb6346SWarner Losh 427f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 428f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 429f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 430f75f65bbSWarner Losh may work). 431f75f65bbSWarner Losh 432ba26da8eSWarner Losh20000612: 433ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 434290f9ad8SWarner Losh on the topic before even thinking about updating. You will 435c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 436290f9ad8SWarner Losh to your config file to compile them in statically. The format 437f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 438f54a3542SWarner Losh NEWCARD for examples of the new format. 439290f9ad8SWarner Losh 440d65850ebSWarner Losh20000522: 441ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 442d65850ebSWarner Losh building a kernel after this point is advised that they need 443d65850ebSWarner Losh to rebuild their binutils (or better yet do a 444d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 445d65850ebSWarner Losh 446d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 447d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 448d9583a00SWarner Losh is recommended that you don't set this option until the problem 449d9583a00SWarner Losh is resolved. 450d9583a00SWarner Losh 4518039cedeSWarner Losh20000513: 4528039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 4538039cedeSWarner Losh 454d65850ebSWarner Losh20000510: 4558039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 4568039cedeSWarner Losh This will require some care in updating alphas. A new libstand 4578039cedeSWarner Losh is requires for the boot blocks to build properly. 4588039cedeSWarner Losh 4598039cedeSWarner Losh20000503: 4608039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 4618039cedeSWarner Losh is now available. 4628039cedeSWarner Losh 463d65850ebSWarner Losh20000502: 464d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 465d65850ebSWarner Losh connected to the kernel building instead. 466d65850ebSWarner Losh 467be149406SNik Clayton20000427: 4688039cedeSWarner Losh You may need to build gperf 4698039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 4708039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 4718039cedeSWarner Losh an option only in -current. 4728039cedeSWarner Losh 4732b8dd5f4SWarner Losh20000417: 4742b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 475f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 4762b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 4772b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 4782c021c6cSMark Ovens before you reboot, you'll need to issue: 4792b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 4802b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 4812b8dd5f4SWarner Losh 4828d9f1945SWarner Losh20000320: 4832b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 4842b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 4852b8dd5f4SWarner Losh cope if you have a problem combination is to add: 4868d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 4872b8dd5f4SWarner Losh to the start of /etc/rc.conf. 4888d9f1945SWarner Losh 489f8ab1dd6SWarner Losh20000319: 490f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 491f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 492f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 493f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 494f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 495f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 496f8ab1dd6SWarner Losh 49719cada77SWarner Losh20000318: 498f699bbbbSMark Ovens We've entered the traditional post release dumping party. 49919cada77SWarner Losh Large kernel changes are being committed and are in the 50019cada77SWarner Losh works. It is important to keep the systems' klds and kernel 50119cada77SWarner Losh in sync as kernel interfaces and structures are changing. 50219cada77SWarner Losh Before reporting kernel panics, make sure that all modules 50319cada77SWarner Losh that you are loading are up to date. 504ba228352SWarner Losh 50519cada77SWarner Losh20000315: 5066d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 5076d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 5086d23c382SWarner Losh will do the trick. This isn't critical until you remove your 5096d23c382SWarner Losh wd device entries in /dev, at which point your system will not 5106d23c382SWarner Losh boot. 5116d23c382SWarner Losh 5126d23c382SWarner Losh20000315: 51319cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 51419cada77SWarner Losh to upgrade to 4.0 from 3.x. 51557199806SWarner Losh 516dc0dbf5cSWarner LoshCOMMON ITEMS: 517dc0dbf5cSWarner Losh 518a24eff53SWarner Losh General Notes 519a24eff53SWarner Losh ------------- 520a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 521a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 522a24eff53SWarner Losh installworld. This is especially true when upgrading between 523a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 524a24eff53SWarner Losh or several minor releases, or when several months have passed 525a24eff53SWarner Losh on the -current branch). 526a24eff53SWarner Losh 527dc0dbf5cSWarner Losh To build a kernel 528dc0dbf5cSWarner Losh ----------------- 529ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 530f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 531ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 5321e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 5331e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 534dc0dbf5cSWarner Losh 535ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 536ba01eb20SWarner Losh -------------------------------------------------------------- 537ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 538ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 539ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 540ba01eb20SWarner Losh make depend 541ba01eb20SWarner Losh make 542ba01eb20SWarner Losh make install 543ba01eb20SWarner Losh 544ba01eb20SWarner Losh [1] If in doubt, -r might help here. 545ba01eb20SWarner Losh 546ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 547ba01eb20SWarner Losh 548ba01eb20SWarner Losh To rebuild everything and install it on the current system. 549ba01eb20SWarner Losh ----------------------------------------------------------- 550759f0aefSWarner Losh make world 551fdb9f54dSWarner Losh Build a new kernel, see above. 552759f0aefSWarner Losh 5531dece4a9SWarner Losh To upgrade from 4.x-stable to current 554ba26da8eSWarner Losh ------------------------------------- 555ba26da8eSWarner Losh make buildworld 5561e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 5577595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 5581e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 559ba26da8eSWarner Losh make installworld 5607595222aSWarner Losh mergemaster 561134d2e86SWarner Losh [1] 562ba26da8eSWarner Losh <reboot> 563ba26da8eSWarner Losh 564fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 565fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 566fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 567fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 568fdb9f54dSWarner Losh the UPDATING entries. 569ba26da8eSWarner Losh 5701dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 5711dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 5721dece4a9SWarner Losh your sources that you have read and understood all the recent 5731dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 5741dece4a9SWarner Losh much fewer pitfalls. 5751dece4a9SWarner Losh 576134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 577134d2e86SWarner Losh should disable them at this point so they don't crash your 578134d2e86SWarner Losh system on reboot. 579134d2e86SWarner Losh 5809c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 5819c1a7444SWarner Losh your own device.hints to reflect your unique hardware 5829c1a7444SWarner Losh configuration. 5839c1a7444SWarner Losh 584dc0dbf5cSWarner LoshFORMAT: 585dc0dbf5cSWarner Losh 586f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 5871fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 588f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 589f8ab1dd6SWarner Loshprevious releases if your system is older than this. 5901fc1a0dcSWarner Losh 5913645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 5923645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 593f8c77507SWarner Losh 59497d92980SPeter Wemm$FreeBSD$ 595