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 82b41163cSWarner Losh20000905: 92b41163cSWarner Losh This just in. The boot loader has been updated. The new 102b41163cSWarner Losh default kernel is /kernel.ko. The new default module location 112b41163cSWarner Losh is /boot/modules. You *MUST* upgrade your boot loader and 122b41163cSWarner Losh kernel at the same time. Film at 11. 132b41163cSWarner Losh 14c22a309cSWarner Losh20000904: 15c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 16c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 17c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 18c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 19c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 20c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 21c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 22c22a309cSWarner Losh is not likely to be generated. 23c22a309cSWarner Losh 24fdb9f54dSWarner Losh20000825: 25fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 269c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 279c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 289c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 299c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 309c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 319c1a7444SWarner Losh messages will appear after the boot loader tries to start the 329c1a7444SWarner Losh kernel. 339c1a7444SWarner Losh 349c1a7444SWarner Losh20000821: 359c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 369c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 379c1a7444SWarner Losh /boot/loader.conf. 38fdb9f54dSWarner Losh 398f250aa7SWarner Losh20000812: 405da0d091SWarner Losh suidperl is now always built and installed on the system, but 415da0d091SWarner Losh with permissions of 511. If you have applications that use 425da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 435da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 445da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 455da0d091SWarner Losh will fix this until the next build. 465da0d091SWarner Losh 475da0d091SWarner Losh20000812: 488f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 498f250aa7SWarner Losh visible changes that may immediately affect your configuration 508f250aa7SWarner Losh include: 518f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 528f250aa7SWarner Losh - newaliases limited to root and trusted users 538f250aa7SWarner Losh - MSA port (587) turned on by default 548f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 558f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 568f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 578f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 588f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 598f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 608f250aa7SWarner Losh 6171c38472SWarner Losh20000810: 6271c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 6371c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 6471c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 6571c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 6671c38472SWarner Losh specific use for it. 6771c38472SWarner Losh 6871c38472SWarner Losh20000729: 6971c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 7071c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 7171c38472SWarner Losh /etc/rc.conf if they want to have the same setup 7271c38472SWarner Losh afterwards (unless the variables already are set, of course): 7371c38472SWarner Losh # Enable network daemons for user convenience. 7471c38472SWarner Losh inetd_enable="YES" 7571c38472SWarner Losh portmap_enable="YES" 7671c38472SWarner Losh sendmail_enable="YES" 7771c38472SWarner Losh 7871c38472SWarner Losh20000728: 7971c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 8071c38472SWarner Losh will need to change that to nullfs_load="YES". 8171c38472SWarner Losh 821dece4a9SWarner Losh20000728: 831dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 841dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 851dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 861dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 871dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 881dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 891dece4a9SWarner Losh to /MYKERNEL. 901dece4a9SWarner Losh 91409e887cSWarner Losh20000711: 92409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 93409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 94409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 95409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 96409e887cSWarner Losh for details on potential problems that you might have and how 97409e887cSWarner Losh to get around them. 98409e887cSWarner Losh 99409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 100409e887cSWarner Losh clauses above, you needn't worry. 101409e887cSWarner Losh 102409e887cSWarner Losh20000711: 103409e887cSWarner Losh /etc/security has been updated to print the inode number of 104409e887cSWarner Losh setuid programs that have changed. You will see a large spike 105409e887cSWarner Losh in the number of changed programs the first time when you run 106409e887cSWarner Losh mergemaster to get a new /etc/security. 107409e887cSWarner Losh 108673d13f2SWarner Losh20000710: 109673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 110673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 111673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 112673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 113673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 114673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 115673d13f2SWarner Losh errors. (see below, 20000624). 116673d13f2SWarner Losh 117bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 1181dece4a9SWarner Losh 119673d13f2SWarner Losh20000709: 120c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 121c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 122c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 123673d13f2SWarner Losh ln -s aj /etc/malloc.conf 124673d13f2SWarner Losh 125e98e26cdSWarner Losh20000706: 126e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 127e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 128e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 129f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 130e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 131e98e26cdSWarner Losh interrum if needed. 132e98e26cdSWarner Losh 133e98e26cdSWarner Losh20000705: 134e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 135e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 136e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 137e98e26cdSWarner Losh details. 138e98e26cdSWarner Losh 139c373950eSWarner Losh20000704: 1402f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 1412f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 1422f961bc8SWarner Losh 1432f961bc8SWarner Losh20000704: 144c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 145c373950eSWarner Losh or stop. This may cause some harmless warnings from older 146c373950eSWarner Losh rc.d scripts that haven't been updated. 147c373950eSWarner Losh 14827dc3a2bSWarner Losh20000630: 14927dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 15027dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 15127dc3a2bSWarner Losh which should be reported to des@freebsd.org. 15227dc3a2bSWarner Losh 153b8c215acSWarner Losh20000625: 154b8c215acSWarner Losh From approximately this date forward, one must have the crypto 15527dc3a2bSWarner Losh system installed in order to build the system and kernel. 15627dc3a2bSWarner Losh While not technically strictly true, one should treat it as 15727dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 15827dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 15927dc3a2bSWarner Losh were required. You should check with the latest collections 16027dc3a2bSWarner Losh to make sure that these haven't changed. 161b8c215acSWarner Losh 1627b990719SWarner Losh20000624: 1637b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 1647b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 1657b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 1667b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 1677b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 1687b990719SWarner Losh openssh and openssl should not be used to generate keys from this 1697b990719SWarner Losh date to the completion of the work. 1707b990719SWarner Losh 17127dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 17227dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 17327dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 17427dc3a2bSWarner Losh recreate the random and urandom devices. 17527dc3a2bSWarner Losh 17681e54c50SWarner Losh20000622: 17781e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 17881e54c50SWarner Losh BSD license. You may need to remove your symbolic links 17981e54c50SWarner Losh that used to be required when updating. 18081e54c50SWarner Losh 18139943833SWarner Losh20000621: 18239943833SWarner Losh Scott Flatman <sf@aracnet.com> sent in a decent writeup on 1832a2f33fbSDaniel Baker the config file update procedure. 1842a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 185c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 186a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 18739943833SWarner Losh 188290f9ad8SWarner Losh20000620: 189290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 190290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 191290f9ad8SWarner Losh that workaround will no longer be required. 192290f9ad8SWarner Losh 19390fb6346SWarner Losh20000615: 19490fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 19590fb6346SWarner Losh ad driver. If you haven't done so already, you must update 19690fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 19790fb6346SWarner Losh devices. 19890fb6346SWarner Losh 199f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 200f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 201f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 202f75f65bbSWarner Losh may work). 203f75f65bbSWarner Losh 204ba26da8eSWarner Losh20000612: 205ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 206290f9ad8SWarner Losh on the topic before even thinking about updating. You will 207c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 208290f9ad8SWarner Losh to your config file to compile them in statically. The format 209f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 210f54a3542SWarner Losh NEWCARD for examples of the new format. 211290f9ad8SWarner Losh 212d65850ebSWarner Losh20000522: 213ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 214d65850ebSWarner Losh building a kernel after this point is advised that they need 215d65850ebSWarner Losh to rebuild their binutils (or better yet do a 216d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 217d65850ebSWarner Losh 218d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 219d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 220d9583a00SWarner Losh is recommended that you don't set this option until the problem 221d9583a00SWarner Losh is resolved. 222d9583a00SWarner Losh 2238039cedeSWarner Losh20000513: 2248039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 2258039cedeSWarner Losh 226d65850ebSWarner Losh20000510: 2278039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 2288039cedeSWarner Losh This will require some care in updating alphas. A new libstand 2298039cedeSWarner Losh is requires for the boot blocks to build properly. 2308039cedeSWarner Losh 2318039cedeSWarner Losh20000503: 2328039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 2338039cedeSWarner Losh is now available. 2348039cedeSWarner Losh 235d65850ebSWarner Losh20000502: 236d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 237d65850ebSWarner Losh connected to the kernel building instead. 238d65850ebSWarner Losh 2398039cedeSWarner Losh2000427: 2408039cedeSWarner Losh You may need to build gperf 2418039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 2428039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 2438039cedeSWarner Losh an option only in -current. 2448039cedeSWarner Losh 2452b8dd5f4SWarner Losh20000417: 2462b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 247f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 2482b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 2492b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 2502b8dd5f4SWarner Losh before you reboot, you'll neeed to issue: 2512b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 2522b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 2532b8dd5f4SWarner Losh 2548d9f1945SWarner Losh20000320: 2552b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 2562b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 2572b8dd5f4SWarner Losh cope if you have a problem combination is to add: 2588d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 2592b8dd5f4SWarner Losh to the start of /etc/rc.conf. 2608d9f1945SWarner Losh 261f8ab1dd6SWarner Losh20000319: 262f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 263f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 264f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 265f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 266f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 267f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 268f8ab1dd6SWarner Losh 26919cada77SWarner Losh20000318: 270f699bbbbSMark Ovens We've entered the traditional post release dumping party. 27119cada77SWarner Losh Large kernel changes are being committed and are in the 27219cada77SWarner Losh works. It is important to keep the systems' klds and kernel 27319cada77SWarner Losh in sync as kernel interfaces and structures are changing. 27419cada77SWarner Losh Before reporting kernel panics, make sure that all modules 27519cada77SWarner Losh that you are loading are up to date. 276ba228352SWarner Losh 27719cada77SWarner Losh20000315: 2786d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 2796d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 2806d23c382SWarner Losh will do the trick. This isn't critical until you remove your 2816d23c382SWarner Losh wd device entries in /dev, at which point your system will not 2826d23c382SWarner Losh boot. 2836d23c382SWarner Losh 2846d23c382SWarner Losh20000315: 28519cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 28619cada77SWarner Losh to upgrade to 4.0 from 3.x. 28757199806SWarner Losh 288dc0dbf5cSWarner LoshCOMMON ITEMS: 289dc0dbf5cSWarner Losh 290a24eff53SWarner Losh General Notes 291a24eff53SWarner Losh ------------- 292a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 293a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 294a24eff53SWarner Losh installworld. This is especially true when upgrading between 295a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 296a24eff53SWarner Losh or several minor releases, or when several months have passed 297a24eff53SWarner Losh on the -current branch). 298a24eff53SWarner Losh 299dc0dbf5cSWarner Losh To build a kernel 300dc0dbf5cSWarner Losh ----------------- 301ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 302f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 303ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 304ba01eb20SWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 305ba01eb20SWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 306dc0dbf5cSWarner Losh 307ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 308ba01eb20SWarner Losh -------------------------------------------------------------- 309ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 310ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 311ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 312ba01eb20SWarner Losh make depend 313ba01eb20SWarner Losh make 314ba01eb20SWarner Losh make install 315ba01eb20SWarner Losh 316ba01eb20SWarner Losh [1] If in doubt, -r might help here. 317ba01eb20SWarner Losh 318ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 319ba01eb20SWarner Losh 320ba01eb20SWarner Losh To rebuild everything and install it on the current system. 321ba01eb20SWarner Losh ----------------------------------------------------------- 322759f0aefSWarner Losh make world 323fdb9f54dSWarner Losh Build a new kernel, see above. 324759f0aefSWarner Losh 3251dece4a9SWarner Losh To upgrade from 4.x-stable to current 326ba26da8eSWarner Losh ------------------------------------- 327ba26da8eSWarner Losh make buildworld 328ba26da8eSWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 3299c1a7444SWarner Losh cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2] 330ba26da8eSWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 331ba26da8eSWarner Losh make installworld 332134d2e86SWarner Losh [1] 333ba26da8eSWarner Losh <reboot> 334ba26da8eSWarner Losh 335fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 336fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 337fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 338fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 339fdb9f54dSWarner Losh the UPDATING entries. 340ba26da8eSWarner Losh 3411dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 3421dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 3431dece4a9SWarner Losh your sources that you have read and understood all the recent 3441dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 3451dece4a9SWarner Losh much fewer pitfalls. 3461dece4a9SWarner Losh 347134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 348134d2e86SWarner Losh should disable them at this point so they don't crash your 349134d2e86SWarner Losh system on reboot. 350134d2e86SWarner Losh 3519c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 3529c1a7444SWarner Losh your own device.hints to reflect your unique hardware 3539c1a7444SWarner Losh configuration. 3549c1a7444SWarner Losh 355dc0dbf5cSWarner LoshFORMAT: 356dc0dbf5cSWarner Losh 357f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 3581fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 359f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 360f8ab1dd6SWarner Loshprevious releases if your system is older than this. 3611fc1a0dcSWarner Losh 3623645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 3633645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 364f8c77507SWarner Losh 36597d92980SPeter Wemm$FreeBSD$ 366