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 871c38472SWarner Losh20000810: 971c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 1071c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 1171c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 1271c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 1371c38472SWarner Losh specific use for it. 1471c38472SWarner Losh 1571c38472SWarner Losh20000729: 1671c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 1771c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 1871c38472SWarner Losh /etc/rc.conf if they want to have the same setup 1971c38472SWarner Losh afterwards (unless the variables already are set, of course): 2071c38472SWarner Losh # Enable network daemons for user convenience. 2171c38472SWarner Losh inetd_enable="YES" 2271c38472SWarner Losh portmap_enable="YES" 2371c38472SWarner Losh sendmail_enable="YES" 2471c38472SWarner Losh 2571c38472SWarner Losh20000728: 2671c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 2771c38472SWarner Losh will need to change that to nullfs_load="YES". 2871c38472SWarner Losh 291dece4a9SWarner Losh20000728: 301dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 311dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 321dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 331dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 341dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 351dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 361dece4a9SWarner Losh to /MYKERNEL. 371dece4a9SWarner Losh 38409e887cSWarner Losh20000711: 39409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 40409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 41409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 42409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 43409e887cSWarner Losh for details on potential problems that you might have and how 44409e887cSWarner Losh to get around them. 45409e887cSWarner Losh 46409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 47409e887cSWarner Losh clauses above, you needn't worry. 48409e887cSWarner Losh 49409e887cSWarner Losh20000711: 50409e887cSWarner Losh /etc/security has been updated to print the inode number of 51409e887cSWarner Losh setuid programs that have changed. You will see a large spike 52409e887cSWarner Losh in the number of changed programs the first time when you run 53409e887cSWarner Losh mergemaster to get a new /etc/security. 54409e887cSWarner Losh 55673d13f2SWarner Losh20000710: 56673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 57673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 58673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 59673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 60673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 61673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 62673d13f2SWarner Losh errors. (see below, 20000624). 63673d13f2SWarner Losh 64bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 651dece4a9SWarner Losh 66673d13f2SWarner Losh20000709: 67c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 68c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 69c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 70673d13f2SWarner Losh ln -s aj /etc/malloc.conf 71673d13f2SWarner Losh 72e98e26cdSWarner Losh20000706: 73e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 74e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 75e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 76e98e26cdSWarner Losh won't hurt to remove it before the update proceedure. It will 77e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 78e98e26cdSWarner Losh interrum if needed. 79e98e26cdSWarner Losh 80e98e26cdSWarner Losh20000705: 81e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 82e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 83e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 84e98e26cdSWarner Losh details. 85e98e26cdSWarner Losh 86c373950eSWarner Losh20000704: 872f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 882f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 892f961bc8SWarner Losh 902f961bc8SWarner Losh20000704: 91c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 92c373950eSWarner Losh or stop. This may cause some harmless warnings from older 93c373950eSWarner Losh rc.d scripts that haven't been updated. 94c373950eSWarner Losh 9527dc3a2bSWarner Losh20000630: 9627dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 9727dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 9827dc3a2bSWarner Losh which should be reported to des@freebsd.org. 9927dc3a2bSWarner Losh 100b8c215acSWarner Losh20000625: 101b8c215acSWarner Losh From approximately this date forward, one must have the crypto 10227dc3a2bSWarner Losh system installed in order to build the system and kernel. 10327dc3a2bSWarner Losh While not technically strictly true, one should treat it as 10427dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 10527dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 10627dc3a2bSWarner Losh were required. You should check with the latest collections 10727dc3a2bSWarner Losh to make sure that these haven't changed. 108b8c215acSWarner Losh 1097b990719SWarner Losh20000624: 1107b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 1117b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 1127b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 1137b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 1147b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 1157b990719SWarner Losh openssh and openssl should not be used to generate keys from this 1167b990719SWarner Losh date to the completion of the work. 1177b990719SWarner Losh 11827dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 11927dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 12027dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 12127dc3a2bSWarner Losh recreate the random and urandom devices. 12227dc3a2bSWarner Losh 12381e54c50SWarner Losh20000622: 12481e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 12581e54c50SWarner Losh BSD license. You may need to remove your symbolic links 12681e54c50SWarner Losh that used to be required when updating. 12781e54c50SWarner Losh 12839943833SWarner Losh20000621: 12939943833SWarner Losh Scott Flatman <sf@aracnet.com> sent in a decent writeup on 1302a2f33fbSDaniel Baker the config file update procedure. 1312a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 132c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 133c373950eSWarner Losh isn't buildable. 13439943833SWarner Losh 135290f9ad8SWarner Losh20000620: 136290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 137290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 138290f9ad8SWarner Losh that workaround will no longer be required. 139290f9ad8SWarner Losh 14090fb6346SWarner Losh20000615: 14190fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 14290fb6346SWarner Losh ad driver. If you haven't done so already, you must update 14390fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 14490fb6346SWarner Losh devices. 14590fb6346SWarner Losh 146f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 147f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 148f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 149f75f65bbSWarner Losh may work). 150f75f65bbSWarner Losh 151ba26da8eSWarner Losh20000612: 152ba26da8eSWarner Losh Peter took an axe to config(8). Besure that you read his mail 153290f9ad8SWarner Losh on the topic before even thinking about updating. You will 154c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 155290f9ad8SWarner Losh to your config file to compile them in statically. The format 156f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 157f54a3542SWarner Losh NEWCARD for examples of the new format. 158290f9ad8SWarner Losh 159d65850ebSWarner Losh20000522: 160ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 161d65850ebSWarner Losh building a kernel after this point is advised that they need 162d65850ebSWarner Losh to rebuild their binutils (or better yet do a 163d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 164d65850ebSWarner Losh 165d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 166d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 167d9583a00SWarner Losh is recommended that you don't set this option until the problem 168d9583a00SWarner Losh is resolved. 169d9583a00SWarner Losh 1708039cedeSWarner Losh20000513: 1718039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 1728039cedeSWarner Losh 173d65850ebSWarner Losh20000510: 1748039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 1758039cedeSWarner Losh This will require some care in updating alphas. A new libstand 1768039cedeSWarner Losh is requires for the boot blocks to build properly. 1778039cedeSWarner Losh 1788039cedeSWarner Losh20000503: 1798039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 1808039cedeSWarner Losh is now available. 1818039cedeSWarner Losh 182d65850ebSWarner Losh20000502: 183d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 184d65850ebSWarner Losh connected to the kernel building instead. 185d65850ebSWarner Losh 1868039cedeSWarner Losh2000427: 1878039cedeSWarner Losh You may need to build gperf 1888039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 1898039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 1908039cedeSWarner Losh an option only in -current. 1918039cedeSWarner Losh 1922b8dd5f4SWarner Losh20000417: 1932b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1942b8dd5f4SWarner Losh acceptible to the binutils maintainers. You will need to 1952b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 1962b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 1972b8dd5f4SWarner Losh before you reboot, you'll neeed to issue: 1982b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 1992b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 2002b8dd5f4SWarner Losh 2018d9f1945SWarner Losh20000320: 2022b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 2032b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 2042b8dd5f4SWarner Losh cope if you have a problem combination is to add: 2058d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 2062b8dd5f4SWarner Losh to the start of /etc/rc.conf. 2078d9f1945SWarner Losh 208f8ab1dd6SWarner Losh20000319: 209f8ab1dd6SWarner Losh The ISA and PCI compatability shims have been connected to the 210f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 211f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 212f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 213f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 214f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 215f8ab1dd6SWarner Losh 21619cada77SWarner Losh20000318: 21719cada77SWarner Losh We've entered the tradtional post release dumping party. 21819cada77SWarner Losh Large kernel changes are being committed and are in the 21919cada77SWarner Losh works. It is important to keep the systems' klds and kernel 22019cada77SWarner Losh in sync as kernel interfaces and structures are changing. 22119cada77SWarner Losh Before reporting kernel panics, make sure that all modules 22219cada77SWarner Losh that you are loading are up to date. 223ba228352SWarner Losh 22419cada77SWarner Losh20000315: 2256d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 2266d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 2276d23c382SWarner Losh will do the trick. This isn't critical until you remove your 2286d23c382SWarner Losh wd device entries in /dev, at which point your system will not 2296d23c382SWarner Losh boot. 2306d23c382SWarner Losh 2316d23c382SWarner Losh20000315: 23219cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 23319cada77SWarner Losh to upgrade to 4.0 from 3.x. 23457199806SWarner Losh 235dc0dbf5cSWarner LoshCOMMON ITEMS: 236dc0dbf5cSWarner Losh 237dc0dbf5cSWarner Losh To build a kernel 238dc0dbf5cSWarner Losh ----------------- 239ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 240ba01eb20SWarner Losh a few days old), you should follow this proceedure. With a 241ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 242ba01eb20SWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 243ba01eb20SWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 244dc0dbf5cSWarner Losh 245ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 246ba01eb20SWarner Losh -------------------------------------------------------------- 247ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 248ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 249ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 250ba01eb20SWarner Losh make depend 251ba01eb20SWarner Losh make 252ba01eb20SWarner Losh make install 253ba01eb20SWarner Losh 254ba01eb20SWarner Losh [1] If in doubt, -r might help here. 255ba01eb20SWarner Losh 256ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 257ba01eb20SWarner Losh 258ba01eb20SWarner Losh To rebuild everything and install it on the current system. 259ba01eb20SWarner Losh ----------------------------------------------------------- 260759f0aefSWarner Losh make world 261759f0aefSWarner Losh 2621dece4a9SWarner Losh To upgrade from 4.x-stable to current 263ba26da8eSWarner Losh ------------------------------------- 264ba26da8eSWarner Losh make buildworld 265ba26da8eSWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 266ba26da8eSWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 267ba26da8eSWarner Losh make installworld 268134d2e86SWarner Losh [1] 269ba26da8eSWarner Losh <reboot> 270ba26da8eSWarner Losh 271ba26da8eSWarner Losh Make sure that you've read the UPDATING file to understand 272ba26da8eSWarner Losh the tweaks to various things you need. At this point in the 273ba26da8eSWarner Losh life cycloe of current, things change often and you are on 274ba26da8eSWarner Losh your own to cope. 275ba26da8eSWarner Losh 2761dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 2771dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 2781dece4a9SWarner Losh your sources that you have read and understood all the recent 2791dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 2801dece4a9SWarner Losh much fewer pitfalls. 2811dece4a9SWarner Losh 282134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 283134d2e86SWarner Losh should disable them at this point so they don't crash your 284134d2e86SWarner Losh system on reboot. 285134d2e86SWarner Losh 286dc0dbf5cSWarner LoshFORMAT: 287dc0dbf5cSWarner Losh 2881fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major 2891fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 290f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 291f8ab1dd6SWarner Loshprevious releases if your system is older than this. 2921fc1a0dcSWarner Losh 2933645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 2943645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 295f8c77507SWarner Losh 29697d92980SPeter Wemm$FreeBSD$ 297