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 87b990719SWarner Losh20000624: 97b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 107b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 117b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 127b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 137b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 147b990719SWarner Losh openssh and openssl should not be used to generate keys from this 157b990719SWarner Losh date to the completion of the work. 167b990719SWarner Losh 1781e54c50SWarner Losh20000622: 1881e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 1981e54c50SWarner Losh BSD license. You may need to remove your symbolic links 2081e54c50SWarner Losh that used to be required when updating. 2181e54c50SWarner Losh 2239943833SWarner Losh20000621: 2339943833SWarner Losh Scott Flatman <sf@aracnet.com> sent in a decent writeup on 242a2f33fbSDaniel Baker the config file update procedure. 252a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 2639943833SWarner Losh 27290f9ad8SWarner Losh20000620: 28290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 29290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 30290f9ad8SWarner Losh that workaround will no longer be required. 31290f9ad8SWarner Losh 3290fb6346SWarner Losh20000615: 3390fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 3490fb6346SWarner Losh ad driver. If you haven't done so already, you must update 3590fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 3690fb6346SWarner Losh devices. 3790fb6346SWarner Losh 38f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 39f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 40f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 41f75f65bbSWarner Losh may work). 42f75f65bbSWarner Losh 43ba26da8eSWarner Losh20000612: 44ba26da8eSWarner Losh Peter took an axe to config(8). Besure that you read his mail 45290f9ad8SWarner Losh on the topic before even thinking about updating. You will 46290f9ad8SWarner Losh need to create a /boot/devices.hints or add a hints directive 47290f9ad8SWarner Losh to your config file to compile them in statically. The format 48290f9ad8SWarner Losh of the config file has changed as well. Please see LINT, 49290f9ad8SWarner Losh GENERIC or NEWCARD for examples of the new format. 50290f9ad8SWarner Losh 51d65850ebSWarner Losh20000522: 52ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 53d65850ebSWarner Losh building a kernel after this point is advised that they need 54d65850ebSWarner Losh to rebuild their binutils (or better yet do a 55d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 56d65850ebSWarner Losh 57d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 58d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 59d9583a00SWarner Losh is recommended that you don't set this option until the problem 60d9583a00SWarner Losh is resolved. 61d9583a00SWarner Losh 628039cedeSWarner Losh20000513: 638039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 648039cedeSWarner Losh 65d65850ebSWarner Losh20000510: 668039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 678039cedeSWarner Losh This will require some care in updating alphas. A new libstand 688039cedeSWarner Losh is requires for the boot blocks to build properly. 698039cedeSWarner Losh 708039cedeSWarner Losh20000503: 718039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 728039cedeSWarner Losh is now available. 738039cedeSWarner Losh 74d65850ebSWarner Losh20000502: 75d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 76d65850ebSWarner Losh connected to the kernel building instead. 77d65850ebSWarner Losh 788039cedeSWarner Losh2000427: 798039cedeSWarner Losh You may need to build gperf 808039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 818039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 828039cedeSWarner Losh an option only in -current. 838039cedeSWarner Losh 842b8dd5f4SWarner Losh20000417: 852b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 862b8dd5f4SWarner Losh acceptible to the binutils maintainers. You will need to 872b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 882b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 892b8dd5f4SWarner Losh before you reboot, you'll neeed to issue: 902b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 912b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 922b8dd5f4SWarner Losh 938d9f1945SWarner Losh20000320: 942b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 952b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 962b8dd5f4SWarner Losh cope if you have a problem combination is to add: 978d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 982b8dd5f4SWarner Losh to the start of /etc/rc.conf. 998d9f1945SWarner Losh 100f8ab1dd6SWarner Losh20000319: 101f8ab1dd6SWarner Losh The ISA and PCI compatability shims have been connected to the 102f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 103f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 104f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 105f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 106f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 107f8ab1dd6SWarner Losh 10819cada77SWarner Losh20000318: 10919cada77SWarner Losh We've entered the tradtional post release dumping party. 11019cada77SWarner Losh Large kernel changes are being committed and are in the 11119cada77SWarner Losh works. It is important to keep the systems' klds and kernel 11219cada77SWarner Losh in sync as kernel interfaces and structures are changing. 11319cada77SWarner Losh Before reporting kernel panics, make sure that all modules 11419cada77SWarner Losh that you are loading are up to date. 115ba228352SWarner Losh 11619cada77SWarner Losh20000315: 1176d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 1186d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 1196d23c382SWarner Losh will do the trick. This isn't critical until you remove your 1206d23c382SWarner Losh wd device entries in /dev, at which point your system will not 1216d23c382SWarner Losh boot. 1226d23c382SWarner Losh 1236d23c382SWarner Losh20000315: 12419cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 12519cada77SWarner Losh to upgrade to 4.0 from 3.x. 12657199806SWarner Losh 127dc0dbf5cSWarner LoshCOMMON ITEMS: 128dc0dbf5cSWarner Losh 129dc0dbf5cSWarner Losh To build a kernel 130dc0dbf5cSWarner Losh ----------------- 131dc0dbf5cSWarner Losh Update config, genassym and go: 132ba26da8eSWarner Losh config YOUR_KERNEL_HERE [1] 133dc0dbf5cSWarner Losh cd ../../compile/YOUR_KERNEL_HERE 134dc0dbf5cSWarner Losh make depend && make 1353645fc1cSWarner Losh make install 136ba26da8eSWarner Losh [1] If upgrading, add -r won't hurt and sometimes helps. 137dc0dbf5cSWarner Losh 13816de1a07SWarner Losh To rebuild everything 13916de1a07SWarner Losh --------------------- 140759f0aefSWarner Losh make world 141759f0aefSWarner Losh 142ba26da8eSWarner Losh To upgrade from 4.0-stable to current 143ba26da8eSWarner Losh ------------------------------------- 144ba26da8eSWarner Losh make buildworld 145ba26da8eSWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 146ba26da8eSWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 147ba26da8eSWarner Losh make installworld 148ba26da8eSWarner Losh <reboot> 149ba26da8eSWarner Losh 150ba26da8eSWarner Losh Make sure that you've read the UPDATING file to understand 151ba26da8eSWarner Losh the tweaks to various things you need. At this point in the 152ba26da8eSWarner Losh life cycloe of current, things change often and you are on 153ba26da8eSWarner Losh your own to cope. 154ba26da8eSWarner Losh 155dc0dbf5cSWarner LoshFORMAT: 156dc0dbf5cSWarner Losh 1571fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major 1581fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 159f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 160f8ab1dd6SWarner Loshprevious releases if your system is older than this. 1611fc1a0dcSWarner Losh 1623645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 1633645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 164f8c77507SWarner Losh 16597d92980SPeter Wemm$FreeBSD$ 166