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 839943833SWarner Losh20000621: 939943833SWarner Losh Scott Flatman <sf@aracnet.com> sent in a decent writeup on 1039943833SWarner Losh the config file update proceedure. 1139943833SWarner Losh http://people.freebsd.org/~imp/config-upd.hmtl 1239943833SWarner Losh 13290f9ad8SWarner Losh20000620: 14290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 15290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 16290f9ad8SWarner Losh that workaround will no longer be required. 17290f9ad8SWarner Losh 1890fb6346SWarner Losh20000615: 1990fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 2090fb6346SWarner Losh ad driver. If you haven't done so already, you must update 2190fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 2290fb6346SWarner Losh devices. 2390fb6346SWarner Losh 24f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 25f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 26f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 27f75f65bbSWarner Losh may work). 28f75f65bbSWarner Losh 29ba26da8eSWarner Losh20000612: 30ba26da8eSWarner Losh Peter took an axe to config(8). Besure that you read his mail 31290f9ad8SWarner Losh on the topic before even thinking about updating. You will 32290f9ad8SWarner Losh need to create a /boot/devices.hints or add a hints directive 33290f9ad8SWarner Losh to your config file to compile them in statically. The format 34290f9ad8SWarner Losh of the config file has changed as well. Please see LINT, 35290f9ad8SWarner Losh GENERIC or NEWCARD for examples of the new format. 36290f9ad8SWarner Losh 37290f9ad8SWarner Losh More details to follow. A better howto would be warmly 38290f9ad8SWarner Losh accepted by the author of UPDATING. 39ba26da8eSWarner Losh 40d65850ebSWarner Losh20000522: 41ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 42d65850ebSWarner Losh building a kernel after this point is advised that they need 43d65850ebSWarner Losh to rebuild their binutils (or better yet do a 44d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 45d65850ebSWarner Losh 46d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 47d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 48d9583a00SWarner Losh is recommended that you don't set this option until the problem 49d9583a00SWarner Losh is resolved. 50d9583a00SWarner Losh 518039cedeSWarner Losh20000513: 528039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 538039cedeSWarner Losh 54d65850ebSWarner Losh20000510: 558039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 568039cedeSWarner Losh This will require some care in updating alphas. A new libstand 578039cedeSWarner Losh is requires for the boot blocks to build properly. 588039cedeSWarner Losh 598039cedeSWarner Losh20000503: 608039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 618039cedeSWarner Losh is now available. 628039cedeSWarner Losh 63d65850ebSWarner Losh20000502: 64d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 65d65850ebSWarner Losh connected to the kernel building instead. 66d65850ebSWarner Losh 678039cedeSWarner Losh2000427: 688039cedeSWarner Losh You may need to build gperf 698039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 708039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 718039cedeSWarner Losh an option only in -current. 728039cedeSWarner Losh 732b8dd5f4SWarner Losh20000417: 742b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 752b8dd5f4SWarner Losh acceptible to the binutils maintainers. You will need to 762b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 772b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 782b8dd5f4SWarner Losh before you reboot, you'll neeed to issue: 792b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 802b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 812b8dd5f4SWarner Losh 828d9f1945SWarner Losh20000320: 832b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 842b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 852b8dd5f4SWarner Losh cope if you have a problem combination is to add: 868d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 872b8dd5f4SWarner Losh to the start of /etc/rc.conf. 888d9f1945SWarner Losh 89f8ab1dd6SWarner Losh20000319: 90f8ab1dd6SWarner Losh The ISA and PCI compatability shims have been connected to the 91f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 92f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 93f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 94f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 95f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 96f8ab1dd6SWarner Losh 9719cada77SWarner Losh20000318: 9819cada77SWarner Losh We've entered the tradtional post release dumping party. 9919cada77SWarner Losh Large kernel changes are being committed and are in the 10019cada77SWarner Losh works. It is important to keep the systems' klds and kernel 10119cada77SWarner Losh in sync as kernel interfaces and structures are changing. 10219cada77SWarner Losh Before reporting kernel panics, make sure that all modules 10319cada77SWarner Losh that you are loading are up to date. 104ba228352SWarner Losh 10519cada77SWarner Losh20000315: 1066d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 1076d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 1086d23c382SWarner Losh will do the trick. This isn't critical until you remove your 1096d23c382SWarner Losh wd device entries in /dev, at which point your system will not 1106d23c382SWarner Losh boot. 1116d23c382SWarner Losh 1126d23c382SWarner Losh20000315: 11319cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 11419cada77SWarner Losh to upgrade to 4.0 from 3.x. 11557199806SWarner Losh 116dc0dbf5cSWarner LoshCOMMON ITEMS: 117dc0dbf5cSWarner Losh 118dc0dbf5cSWarner Losh To build a kernel 119dc0dbf5cSWarner Losh ----------------- 120dc0dbf5cSWarner Losh Update config, genassym and go: 121ba26da8eSWarner Losh config YOUR_KERNEL_HERE [1] 122dc0dbf5cSWarner Losh cd ../../compile/YOUR_KERNEL_HERE 123dc0dbf5cSWarner Losh make depend && make 1243645fc1cSWarner Losh make install 125ba26da8eSWarner Losh [1] If upgrading, add -r won't hurt and sometimes helps. 126dc0dbf5cSWarner Losh 12716de1a07SWarner Losh To rebuild everything 12816de1a07SWarner Losh --------------------- 129759f0aefSWarner Losh make world 130759f0aefSWarner Losh 131ba26da8eSWarner Losh To upgrade from 4.0-stable to current 132ba26da8eSWarner Losh ------------------------------------- 133ba26da8eSWarner Losh make buildworld 134ba26da8eSWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 135ba26da8eSWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 136ba26da8eSWarner Losh make installworld 137ba26da8eSWarner Losh <reboot> 138ba26da8eSWarner Losh 139ba26da8eSWarner Losh Make sure that you've read the UPDATING file to understand 140ba26da8eSWarner Losh the tweaks to various things you need. At this point in the 141ba26da8eSWarner Losh life cycloe of current, things change often and you are on 142ba26da8eSWarner Losh your own to cope. 143ba26da8eSWarner Losh 144dc0dbf5cSWarner LoshFORMAT: 145dc0dbf5cSWarner Losh 1461fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major 1471fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 148f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 149f8ab1dd6SWarner Loshprevious releases if your system is older than this. 1501fc1a0dcSWarner Losh 1513645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 1523645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 153f8c77507SWarner Losh 15497d92980SPeter Wemm$FreeBSD$ 155