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 827dc3a2bSWarner Losh20000630: 927dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 1027dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 1127dc3a2bSWarner Losh which should be reported to des@freebsd.org. 1227dc3a2bSWarner Losh 13b8c215acSWarner Losh20000625: 14b8c215acSWarner Losh From approximately this date forward, one must have the crypto 1527dc3a2bSWarner Losh system installed in order to build the system and kernel. 1627dc3a2bSWarner Losh While not technically strictly true, one should treat it as 1727dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 1827dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 1927dc3a2bSWarner Losh were required. You should check with the latest collections 2027dc3a2bSWarner Losh to make sure that these haven't changed. 21b8c215acSWarner Losh 227b990719SWarner Losh20000624: 237b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 247b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 257b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 267b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 277b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 287b990719SWarner Losh openssh and openssl should not be used to generate keys from this 297b990719SWarner Losh date to the completion of the work. 307b990719SWarner Losh 3127dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 3227dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 3327dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 3427dc3a2bSWarner Losh recreate the random and urandom devices. 3527dc3a2bSWarner Losh 3681e54c50SWarner Losh20000622: 3781e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 3881e54c50SWarner Losh BSD license. You may need to remove your symbolic links 3981e54c50SWarner Losh that used to be required when updating. 4081e54c50SWarner Losh 4139943833SWarner Losh20000621: 4239943833SWarner Losh Scott Flatman <sf@aracnet.com> sent in a decent writeup on 432a2f33fbSDaniel Baker the config file update procedure. 442a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 4539943833SWarner Losh 46290f9ad8SWarner Losh20000620: 47290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 48290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 49290f9ad8SWarner Losh that workaround will no longer be required. 50290f9ad8SWarner Losh 5190fb6346SWarner Losh20000615: 5290fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 5390fb6346SWarner Losh ad driver. If you haven't done so already, you must update 5490fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 5590fb6346SWarner Losh devices. 5690fb6346SWarner Losh 57f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 58f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 59f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 60f75f65bbSWarner Losh may work). 61f75f65bbSWarner Losh 62ba26da8eSWarner Losh20000612: 63ba26da8eSWarner Losh Peter took an axe to config(8). Besure that you read his mail 64290f9ad8SWarner Losh on the topic before even thinking about updating. You will 65290f9ad8SWarner Losh need to create a /boot/devices.hints or add a hints directive 66290f9ad8SWarner Losh to your config file to compile them in statically. The format 67290f9ad8SWarner Losh of the config file has changed as well. Please see LINT, 68290f9ad8SWarner Losh GENERIC or NEWCARD for examples of the new format. 69290f9ad8SWarner Losh 70d65850ebSWarner Losh20000522: 71ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 72d65850ebSWarner Losh building a kernel after this point is advised that they need 73d65850ebSWarner Losh to rebuild their binutils (or better yet do a 74d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 75d65850ebSWarner Losh 76d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 77d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 78d9583a00SWarner Losh is recommended that you don't set this option until the problem 79d9583a00SWarner Losh is resolved. 80d9583a00SWarner Losh 818039cedeSWarner Losh20000513: 828039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 838039cedeSWarner Losh 84d65850ebSWarner Losh20000510: 858039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 868039cedeSWarner Losh This will require some care in updating alphas. A new libstand 878039cedeSWarner Losh is requires for the boot blocks to build properly. 888039cedeSWarner Losh 898039cedeSWarner Losh20000503: 908039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 918039cedeSWarner Losh is now available. 928039cedeSWarner Losh 93d65850ebSWarner Losh20000502: 94d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 95d65850ebSWarner Losh connected to the kernel building instead. 96d65850ebSWarner Losh 978039cedeSWarner Losh2000427: 988039cedeSWarner Losh You may need to build gperf 998039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 1008039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 1018039cedeSWarner Losh an option only in -current. 1028039cedeSWarner Losh 1032b8dd5f4SWarner Losh20000417: 1042b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 1052b8dd5f4SWarner Losh acceptible to the binutils maintainers. You will need to 1062b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 1072b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 1082b8dd5f4SWarner Losh before you reboot, you'll neeed to issue: 1092b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 1102b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 1112b8dd5f4SWarner Losh 1128d9f1945SWarner Losh20000320: 1132b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 1142b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 1152b8dd5f4SWarner Losh cope if you have a problem combination is to add: 1168d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 1172b8dd5f4SWarner Losh to the start of /etc/rc.conf. 1188d9f1945SWarner Losh 119f8ab1dd6SWarner Losh20000319: 120f8ab1dd6SWarner Losh The ISA and PCI compatability shims have been connected to the 121f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 122f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 123f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 124f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 125f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 126f8ab1dd6SWarner Losh 12719cada77SWarner Losh20000318: 12819cada77SWarner Losh We've entered the tradtional post release dumping party. 12919cada77SWarner Losh Large kernel changes are being committed and are in the 13019cada77SWarner Losh works. It is important to keep the systems' klds and kernel 13119cada77SWarner Losh in sync as kernel interfaces and structures are changing. 13219cada77SWarner Losh Before reporting kernel panics, make sure that all modules 13319cada77SWarner Losh that you are loading are up to date. 134ba228352SWarner Losh 13519cada77SWarner Losh20000315: 1366d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 1376d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 1386d23c382SWarner Losh will do the trick. This isn't critical until you remove your 1396d23c382SWarner Losh wd device entries in /dev, at which point your system will not 1406d23c382SWarner Losh boot. 1416d23c382SWarner Losh 1426d23c382SWarner Losh20000315: 14319cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 14419cada77SWarner Losh to upgrade to 4.0 from 3.x. 14557199806SWarner Losh 146dc0dbf5cSWarner LoshCOMMON ITEMS: 147dc0dbf5cSWarner Losh 148dc0dbf5cSWarner Losh To build a kernel 149dc0dbf5cSWarner Losh ----------------- 150dc0dbf5cSWarner Losh Update config, genassym and go: 151ba26da8eSWarner Losh config YOUR_KERNEL_HERE [1] 152dc0dbf5cSWarner Losh cd ../../compile/YOUR_KERNEL_HERE 153dc0dbf5cSWarner Losh make depend && make 1543645fc1cSWarner Losh make install 155ba26da8eSWarner Losh [1] If upgrading, add -r won't hurt and sometimes helps. 156dc0dbf5cSWarner Losh 15716de1a07SWarner Losh To rebuild everything 15816de1a07SWarner Losh --------------------- 159759f0aefSWarner Losh make world 160759f0aefSWarner Losh 161ba26da8eSWarner Losh To upgrade from 4.0-stable to current 162ba26da8eSWarner Losh ------------------------------------- 163ba26da8eSWarner Losh make buildworld 164ba26da8eSWarner Losh make buildkernel KERNEL=YOUR_KERNEL_HERE 165ba26da8eSWarner Losh make installkernel KERNEL=YOUR_KERNEL_HERE 166ba26da8eSWarner Losh make installworld 167ba26da8eSWarner Losh <reboot> 168ba26da8eSWarner Losh 169ba26da8eSWarner Losh Make sure that you've read the UPDATING file to understand 170ba26da8eSWarner Losh the tweaks to various things you need. At this point in the 171ba26da8eSWarner Losh life cycloe of current, things change often and you are on 172ba26da8eSWarner Losh your own to cope. 173ba26da8eSWarner Losh 174dc0dbf5cSWarner LoshFORMAT: 175dc0dbf5cSWarner Losh 1761fc1a0dcSWarner LoshThis file contains a list, in reverse chronologocal order, of major 1771fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 178f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 179f8ab1dd6SWarner Loshprevious releases if your system is older than this. 1801fc1a0dcSWarner Losh 1813645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 1823645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 183f8c77507SWarner Losh 18497d92980SPeter Wemm$FreeBSD$ 185