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 880c16af9SWarner Losh20010520: 980c16af9SWarner Losh Swapping is busted on -current. Please be patient. 1080c16af9SWarner Losh 1180c16af9SWarner Losh20010519: 1280c16af9SWarner Losh pccard has had much reorganizational work done to it over 1380c16af9SWarner Losh the past few days. Everything should still work, but if 1480c16af9SWarner Losh not, please contact imp@freebsd.org. 1580c16af9SWarner Losh 16a45f2d05SWarner Losh20010517: 17a45f2d05SWarner Losh ata ioctl changed. Make sure to recompile both kernel and 18a45f2d05SWarner Losh userland at the same time. 19a45f2d05SWarner Losh 20a45f2d05SWarner Losh20010517: 21a45f2d05SWarner Losh New ncurses imported. 22a45f2d05SWarner Losh 232988afcaSWarner Losh20010512: 242988afcaSWarner Losh DEVFS is now opt out, not opt in. Barring major problems, this 252988afcaSWarner Losh will be the only way to go starting July 1. 262988afcaSWarner Losh 2709946a51SWarner Losh20010502: 2809946a51SWarner Losh Perl breakage in 20010501 was corrected at 14:18:33 PDT. 2909946a51SWarner Losh 3009946a51SWarner Losh20010501: 3109946a51SWarner Losh Building perl was broken at 02:25:25 PDT. 3209946a51SWarner Losh 3309946a51SWarner Losh20010430: 34a70a79adSWarner Losh The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 3509946a51SWarner Losh go back in the water. 3609946a51SWarner Losh 3709946a51SWarner Losh20010429: 3809946a51SWarner Losh A bad bug was committed at 04:48:42 PDT. Don't use kernels after 3909946a51SWarner Losh this date, but before the correction date. 4009946a51SWarner Losh 4191dd3b53SWarner Losh20010423: 4291dd3b53SWarner Losh old fsck and new kernel interactions appear to have been fixed. 4391dd3b53SWarner Losh 4491dd3b53SWarner Losh20010411: 4591dd3b53SWarner Losh fsck and the kernel were changed to handle some optimizations 4691dd3b53SWarner Losh to directory layout. This breaks backward compatibility. 4791dd3b53SWarner Losh Update only if you understand that you must not use the old 4891dd3b53SWarner Losh fsck with the new kernel ever. 4991dd3b53SWarner Losh 50933b3269SWarner Losh20010330: 51933b3269SWarner Losh fsck has changed the meaning of the pass column in /etc/fstab. 52933b3269SWarner Losh Please see the cvs commit to fsck.8 or the fsck.8 man page fora 53933b3269SWarner Losh details. It is unclear if changes to /etc/fstab are necessary. 54933b3269SWarner Losh 55933b3269SWarner Losh20010319: 56933b3269SWarner Losh portmap had changed name to rpcbind for maximum POLA in your 57933b3269SWarner Losh current world. /etc/hosts.{allow,deny} needs changes. nfs and 58933b3269SWarner Losh other rpc based programs that rely on portmapper will not work 5909946a51SWarner Losh without updates to /etc/hosts.{allow,deny} and /etc/netcofnig. 6009946a51SWarner Losh 6109946a51SWarner Losh20010315: 6209946a51SWarner Losh ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 6309946a51SWarner Losh and ATA_ENABEL_TAGS are no longer kernel options. They have 6409946a51SWarner Losh been replaced by tunables. See ata.4 for details. 65933b3269SWarner Losh 66933b3269SWarner Losh20010312: 67933b3269SWarner Losh The fxp driver was converted to use miibus. If you compile 68933b3269SWarner Losh fxp into your kernel statically, you will need to add miibus. 69933b3269SWarner Losh 70933b3269SWarner Losh20010312: 71933b3269SWarner Losh The wi device now defaults to BSS (infrastructure) mode 72933b3269SWarner Losh instead of ad-hoc. 73933b3269SWarner Losh 74933b3269SWarner Losh20010310: 75933b3269SWarner Losh /dev/urandmon should be a sumbolic link to /dev/random now. 76933b3269SWarner Losh Users of current not using DEVFS need to run MAKEDEV std. 77933b3269SWarner Losh ssh might not work if you don't. 78933b3269SWarner Losh 79d325cf65SWarner Losh20010220: 80d325cf65SWarner Losh The problems with libc have been corrected. It is now mostly 81d325cf65SWarner Losh safe to go back into the water. 82d325cf65SWarner Losh 83024daae6SWarner Losh20010211: 84024daae6SWarner Losh The size of FILE was changed. This breaks upgrading. If 85024daae6SWarner Losh you must upgrade, be prepared for pain. It also breaks almost 86024daae6SWarner Losh all binaries that you've compiled on -current. You are warned 87024daae6SWarner Losh that before upgrading would be a good time to do a level 0 88024daae6SWarner Losh dump of your system. No, really, I mean it this time. 89024daae6SWarner Losh 90024daae6SWarner Losh To get to the new system, you'll need to use the following 91024daae6SWarner Losh workaround. Hopefully this can be sorted out so that we 92024daae6SWarner Losh don't have to move this to the updating section. 93024daae6SWarner Losh 94024daae6SWarner Losh To get around the installworld problem, do: 95024daae6SWarner Losh # cd /usr/src/usr.bin/sed 96024daae6SWarner Losh # make install 97024daae6SWarner Losh # cd /usr/src 98024daae6SWarner Losh # make installworld 99024daae6SWarner Losh If that doesn't work, then try: 100024daae6SWarner Losh # make -k installworld 101024daae6SWarner Losh # make installworld 102024daae6SWarner Losh 103024daae6SWarner Losh20010207: 104024daae6SWarner Losh DEVFS is now the default. If you use vinum, make sure that you 105024daae6SWarner Losh do not include devfs in your kernel as problems result. 106024daae6SWarner Losh 107024daae6SWarner Losh20010205: 1087595222aSWarner Losh FFS_ROOT and CD9660_ROOT have been removed or deprecated. 109024daae6SWarner Losh Remove them from your config. 110024daae6SWarner Losh 1111e159248SWarner Losh20010122: 1121e159248SWarner Losh ****************************** WARNING ****************************** 1131e159248SWarner Losh buildkernel has been changed slightly 1141e159248SWarner Losh ****************************** WARNING ****************************** 1151e159248SWarner Losh KERNCONF replaces the variable KERNEL for buildkernel. You 1161e159248SWarner Losh should update your scripts and make.conf accordingly. 1171e159248SWarner Losh 1181e159248SWarner Losh20010119: 1191e159248SWarner Losh config has changed to allow DEV_FOO as a replacement for NFOO. 1201e159248SWarner Losh This requires a new config to build correctly. 1211e159248SWarner Losh 122aac7dfeaSWarner Losh20010116: 123aac7dfeaSWarner Losh The kerrnel option I386_CPU is now mutually exclusive with the 124aac7dfeaSWarner Losh other cpu types. If you have an i386 system, be sure that it 125aac7dfeaSWarner Losh only had this line. Remove it for all other configurations. 126aac7dfeaSWarner Losh 127aac7dfeaSWarner Losh20010110: 128aac7dfeaSWarner Losh Changes to the kernel require it and burncd be in sync. 129aac7dfeaSWarner Losh 130aac7dfeaSWarner Losh20010102: 131aac7dfeaSWarner Losh Everyone who has hw.sndunit set to something in 132aac7dfeaSWarner Losh /etc/sysctl.conf, it is now hw.snd.unit. 133aac7dfeaSWarner Losh 13463c90c9eSWarner Losh20010101: 13563c90c9eSWarner Losh ex and vi were broken by some changes to sys/queue.h. If you 13663c90c9eSWarner Losh have a bad vi, you will see make buildworld fail with a core 1375fd2a895SWarner Losh dump while building termcap. You can work around this problem 13863c90c9eSWarner Losh by adding -k to your make buildworld. This will cause the 13963c90c9eSWarner Losh build to complete and install a new vi. Once that's done, you 14063c90c9eSWarner Losh can rebuild again without the -k to pick up anything that 14163c90c9eSWarner Losh might have been ignored by the -k option. 14263c90c9eSWarner Losh 1435fd2a895SWarner Losh Others have suggested that you can just rebuild libc if your 1445fd2a895SWarner Losh vi/ex is dynamically linked, but I've not received any reports 1455fd2a895SWarner Losh of this working. 1465fd2a895SWarner Losh 147aac7dfeaSWarner Losh20001228: 148aac7dfeaSWarner Losh There have been some changes to libcrypt in -current. The 149aac7dfeaSWarner Losh libscrypt/libdescrypt symlink sillyness is gone and the installed 150aac7dfeaSWarner Losh libcrypt is fully functional. Be aware of this. 151aac7dfeaSWarner Losh 152de2bcc63SWarner Losh20001218: 153de2bcc63SWarner Losh Linksys Fast Ethernet PCCARD cards supported by the ed driver 154de2bcc63SWarner Losh now require the addition of flag 0x80000 to their config line 155de2bcc63SWarner Losh in pccard.conf(5). This flag is not optional. These Linksys 156de2bcc63SWarner Losh cards will not be recognized without it. 157de2bcc63SWarner Losh 158960773f7SWarner Losh20001205: 159960773f7SWarner Losh Important new FreeBSD-version stuff: PAM support has been worked 160960773f7SWarner Losh in, partially from the "Unix" OpenSSH version. This requires 161960773f7SWarner Losh adding the following in pam.conf: 162960773f7SWarner Losh 163960773f7SWarner Losh sshd auth sufficient pam_skey.so 164960773f7SWarner Losh sshd auth required pam_unix.so try_first_pass 165960773f7SWarner Losh sshd session required pam_permit.so 166960773f7SWarner Losh 1670acc635eSWarner Losh20001031: 1680acc635eSWarner Losh cvs updated to 1.11. 1690acc635eSWarner Losh 1700acc635eSWarner Losh20001020: 1710acc635eSWarner Losh The random device needs more entropy, so you need to make sure 1720acc635eSWarner Losh that you've run mergemaster to get a /etc/rc which will seed 1730acc635eSWarner Losh /dev/random. If you don't and the system hangs after ldconfig, 1740acc635eSWarner Losh then banging on the keyboard randomly until it unhangs is one 1750acc635eSWarner Losh workaround. 1760acc635eSWarner Losh 1770acc635eSWarner Losh20001010: 1780acc635eSWarner Losh ****************************** WARNING ****************************** 1790acc635eSWarner Losh Sendmail has been updated. 1800acc635eSWarner Losh ****************************** WARNING ****************************** 1810acc635eSWarner Losh o mail.local(8) is no longer installed as a set-user-id binary. 1820acc635eSWarner Losh o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 1830acc635eSWarner Losh is set. 1840acc635eSWarner Losh o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 1850acc635eSWarner Losh commands. 1860acc635eSWarner Losh o Now using sendmail's version of vacation(1). 1870acc635eSWarner Losh o The sendmail cf building tools (contrib/sendmail/cf) are installed 1880acc635eSWarner Losh in /usr/share/sendmail/cf. 1890acc635eSWarner Losh o sendmail.cw changed to local-host-names 1900acc635eSWarner Losh 1910acc635eSWarner Losh More details can be found at 1920acc635eSWarner Losh http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 1930acc635eSWarner Losh 1946e98a146SWarner Losh20001009: 1956e98a146SWarner Losh The ports tree's new layout is in place. Be sure to update 1966e98a146SWarner Losh your entire ports tree, or you will have problems. 1976e98a146SWarner Losh 1986e98a146SWarner Losh20001006: 199685294e7SMark Ovens The perl build procedure no longer installs miniperl, nor uses 2006e98a146SWarner Losh the installed miniperl. It is recommended that you delete 2016e98a146SWarner Losh /usr/bin/miniperl. 2026e98a146SWarner Losh 203073113a4SWarner Losh20001005: 204073113a4SWarner Losh This weekend the ports tree will be updated to a new layout. 205685294e7SMark Ovens It will be in an inconsistent state until noted in the UPDATING 206073113a4SWarner Losh file, or with asami-san's message to the relevant mailing 207073113a4SWarner Losh lists. With this new layout, you'll need to update the whole 208073113a4SWarner Losh tree for anything to work. 209073113a4SWarner Losh 2100acc635eSWarner Losh20000928: 2110acc635eSWarner Losh There was a change in the passwd format. Need more information. 2120acc635eSWarner Losh 213be3885b3SWarner Losh20000916: 214be3885b3SWarner Losh /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 215be3885b3SWarner Losh place. Please update boot loader (not the boot blocks) at the 216be3885b3SWarner Losh same time as your kernel. 217be3885b3SWarner Losh 21876ec9675SWarner Losh20000914: 21976ec9675SWarner Losh The new pmtimer device is necessary for laptops. Failure to 22076ec9675SWarner Losh include the device will cause suspended laptops losing time 22176ec9675SWarner Losh when they resume. Include 22276ec9675SWarner Losh device pmtimer 22376ec9675SWarner Losh in your config file and 22401b9a434SWarner Losh hint.pmtimer.0.at="isa" 22576ec9675SWarner Losh to your /boot/device.hints file. 22676ec9675SWarner Losh 227f4865386SMark Murray20000911: 228f4865386SMark Murray The random device has been turned into a (pseudo-)device, 229f4865386SMark Murray rather than an option. The supplied kernel config files have 230f4865386SMark Murray been updated. You will need to do something similar in your 231f4865386SMark Murray own kernel config file. 232f4865386SMark Murray Remove: 233f4865386SMark Murray options RANDOMDEV 234f4865386SMark Murray Add: 235f4865386SMark Murray device random 236f4865386SMark Murray If you prefer to load the loadable module, you need to do 237f4865386SMark Murray nothing. 238f4865386SMark Murray 239d594498fSWarner Losh20000909: 240d594498fSWarner Losh The random device module has been renamed from randomdev.ko to 241d594498fSWarner Losh random.ko. You will need to edit your /boot/loader.conf to 242d594498fSWarner Losh reflect this if you load this module at boot time. 243d594498fSWarner Losh The line should read: 244d594498fSWarner Losh random_load="YES" 245d594498fSWarner Losh 2460deb7ddcSWarner Losh20000907: 2470deb7ddcSWarner Losh The SMPNG commit has happened. It should work, but if it 24816eb772dSWarner Losh doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 24916eb772dSWarner Losh to be a variety of minor issues. Please see 20000905 to make 25016eb772dSWarner Losh sure you don't have model loading problems which might at 25116eb772dSWarner Losh first blush appear related to SMP. 25252bf24e7SWarner Losh 2535a01880bSWarner Losh20000906: 2545a01880bSWarner Losh nsswitch has been imported from NetBSD. Among other things, 2555a01880bSWarner Losh this means that /etc/host.conf is no longer used. See 2565a01880bSWarner Losh nsswitch.conf(5) instead. Note that at boot time rc.network 2575a01880bSWarner Losh will attempt to produce a new nsswitch.conf file for you if you 2585a01880bSWarner Losh don't have one, and you have host.conf. 2595a01880bSWarner Losh 2602b41163cSWarner Losh20000905: 26138d6ecd2SWarner Losh The ucred structure changed size. This breaks the interface 26238d6ecd2SWarner Losh that mountd uses. Trying to use an older mountd with a newer 26338d6ecd2SWarner Losh kernel guarantees a panic. This means that you need to use 26438d6ecd2SWarner Losh kernels newer than today only with matching mountd, but you 26538d6ecd2SWarner Losh needed to do that anyway with the boot loader changes. 26638d6ecd2SWarner Losh 26738d6ecd2SWarner Losh20000905: 2688aab4bc7SWarner Losh The boot loader has been updated. The new default kernel is 2698aab4bc7SWarner Losh now /boot/kernel/kernel.ko. The new default module location 2708aab4bc7SWarner Losh is /boot/kernel. 2718aab4bc7SWarner Losh 2728aab4bc7SWarner Losh You *MUST* upgrade your boot loader and kernel at the same time. 27338d6ecd2SWarner Losh The easiest way to do this is to do the buildworld/buildkernel/ 27438d6ecd2SWarner Losh installkernel/installworld dance. 2752b41163cSWarner Losh 276d594498fSWarner Losh Furthermore, you are urged to delete your old /modules directory 277d594498fSWarner Losh before booting the new kernel, since kldload will find stale 278d594498fSWarner Losh modules in that directory instead of finding them in the correct 279d594498fSWarner Losh path, /boot/kernel. The most common complaint that this cures 280d594498fSWarner Losh is that the linux module crashes your machine after the update. 281d594498fSWarner Losh 282d594498fSWarner Losh if [ ! -d /boot/kernel.old ]; then 283d594498fSWarner Losh mv /modules.old /boot/kernel.old 284d594498fSWarner Losh chflags noschg /kernel.old 285d594498fSWarner Losh mv /kernel.old /boot/kernel.old/kernel.ko 286d594498fSWarner Losh chflags schg /boot/kernel.old/kernel.ko 287d594498fSWarner Losh fi 288d594498fSWarner Losh 289c22a309cSWarner Losh20000904: 290c22a309cSWarner Losh A new issue with the sendmail upgrade has come to light. 291c22a309cSWarner Losh /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 292c22a309cSWarner Losh incorrectly install the default aliases in /etc/mail rather than 293c22a309cSWarner Losh move the old one from /etc. So you'll need to manually move the 294c22a309cSWarner Losh file, create a symbolic link, remove the old /etc/aliases.db and 295c22a309cSWarner Losh run newaliases. For safety sake, you should stop sendmail 296c22a309cSWarner Losh while doing this and run the upgrade when locally sourced email 297c22a309cSWarner Losh is not likely to be generated. 298c22a309cSWarner Losh 299fdb9f54dSWarner Losh20000825: 300fdb9f54dSWarner Losh /boot/device.hints is now required for installkernel to 3019c1a7444SWarner Losh succeed. You should copy GENERIC.hints for your architecture 3029c1a7444SWarner Losh into /boot/device.hints. If and only if you compile hints 3039c1a7444SWarner Losh into your kernel, then this file may be empty. Please note, 3049c1a7444SWarner Losh if you have an empty or missing /boot/device.hints file and 3059c1a7444SWarner Losh you neglected to compile hints into your kernel, no boot 3069c1a7444SWarner Losh messages will appear after the boot loader tries to start the 3079c1a7444SWarner Losh kernel. 3089c1a7444SWarner Losh 3099c1a7444SWarner Losh20000821: 3109c1a7444SWarner Losh If you do NOT have ``options RANDOMDEV'' in your kernel and 3119c1a7444SWarner Losh you DO want the random device then add randomdev_load="YES" to 3129c1a7444SWarner Losh /boot/loader.conf. 313fdb9f54dSWarner Losh 3148f250aa7SWarner Losh20000812: 3155da0d091SWarner Losh suidperl is now always built and installed on the system, but 3165da0d091SWarner Losh with permissions of 511. If you have applications that use 3175da0d091SWarner Losh this program, you are now required to add ENABLE_SUIDPERL=true 3185da0d091SWarner Losh to /etc/make.conf. If you forget to do this, 3195da0d091SWarner Losh chmod 4511 /usr/bin/suidperl 3205da0d091SWarner Losh will fix this until the next build. 3215da0d091SWarner Losh 3225da0d091SWarner Losh20000812: 3238f250aa7SWarner Losh sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 3248f250aa7SWarner Losh visible changes that may immediately affect your configuration 3258f250aa7SWarner Losh include: 3268f250aa7SWarner Losh - New default file locations from src/contrib/sendmail/cf/README 3278f250aa7SWarner Losh - newaliases limited to root and trusted users 3288f250aa7SWarner Losh - MSA port (587) turned on by default 3298f250aa7SWarner Losh - New queue file naming system so can't go from 8.11 -> 8.9 3308f250aa7SWarner Losh - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 3318f250aa7SWarner Losh - FEATURE(`nullclient') is more full featured 3328f250aa7SWarner Losh - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 3338f250aa7SWarner Losh - mail.local FreeBSD-only -b option changed to -B 3348f250aa7SWarner Losh - See src/contrib/sendmail/RELEASE_NOTES for more info 3358f250aa7SWarner Losh 33671c38472SWarner Losh20000810: 33771c38472SWarner Losh suidperl (aka sperl) is no longer build by default. You must 33871c38472SWarner Losh specifically define BUILD_SUIDPERL to "true" for it to be build. 33971c38472SWarner Losh Furthermore, we recommend that you remove /usr/bin/sperl* and 34071c38472SWarner Losh /usr/bin/suidperl files from your system unless you have a 34171c38472SWarner Losh specific use for it. 34271c38472SWarner Losh 34371c38472SWarner Losh20000729: 34471c38472SWarner Losh Networking defaults have been tightened. Anybody upgrading 34571c38472SWarner Losh /etc/defaults/rc.conf needs to add the following lines to 34671c38472SWarner Losh /etc/rc.conf if they want to have the same setup 34771c38472SWarner Losh afterwards (unless the variables already are set, of course): 34871c38472SWarner Losh # Enable network daemons for user convenience. 34971c38472SWarner Losh inetd_enable="YES" 35071c38472SWarner Losh portmap_enable="YES" 35171c38472SWarner Losh sendmail_enable="YES" 35271c38472SWarner Losh 35371c38472SWarner Losh20000728: 35471c38472SWarner Losh If you have null_load="YES" in your /boot/loader.conf, you 35571c38472SWarner Losh will need to change that to nullfs_load="YES". 35671c38472SWarner Losh 3571dece4a9SWarner Losh20000728: 3581dece4a9SWarner Losh The "installkernel" target has changed slightly. Now even if 3591dece4a9SWarner Losh you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 3601dece4a9SWarner Losh it will install the MYKERNEL file (built with the buildkernel 3611dece4a9SWarner Losh target) as /kernel rather than /MYKERNEL. Those who have 3621dece4a9SWarner Losh updated their /boot/loader.conf files to point to /MYKERNEL 3631dece4a9SWarner Losh should remove that entry or perform manual rename of /kernel 3641dece4a9SWarner Losh to /MYKERNEL. 3651dece4a9SWarner Losh 366409e887cSWarner Losh20000711: 367409e887cSWarner Losh If you use CVSUP or CTM to get CVS trees, AND you used to get 368409e887cSWarner Losh the old crypto files from internat.freebsd.org AND you check 369409e887cSWarner Losh out files from the CVS tree with the cvs command, please read 370409e887cSWarner Losh http://people.freebsd.org/~imp/internat.txt 371409e887cSWarner Losh for details on potential problems that you might have and how 372409e887cSWarner Losh to get around them. 373409e887cSWarner Losh 374409e887cSWarner Losh If you are merely a mirror, or don't answer yes to each of the 375409e887cSWarner Losh clauses above, you needn't worry. 376409e887cSWarner Losh 377409e887cSWarner Losh20000711: 378409e887cSWarner Losh /etc/security has been updated to print the inode number of 379409e887cSWarner Losh setuid programs that have changed. You will see a large spike 380409e887cSWarner Losh in the number of changed programs the first time when you run 381409e887cSWarner Losh mergemaster to get a new /etc/security. 382409e887cSWarner Losh 383673d13f2SWarner Losh20000710: 384673d13f2SWarner Losh /dev/random now has good entropy collection (from the keyboard 385673d13f2SWarner Losh and sysmouse drivers). Please ensure that either `options 386673d13f2SWarner Losh RANDOMDEV' is present in your kernel config file or that 387673d13f2SWarner Losh `randomdev_load="YES"' is in your /boot/loader.conf. If you do 388673d13f2SWarner Losh not have the /dev/random driver, OpenSSL (and consequently 389673d13f2SWarner Losh lots of crypto tools (like SSH)) will fail with strange 390673d13f2SWarner Losh errors. (see below, 20000624). 391673d13f2SWarner Losh 392bed5c5ffSWarner Losh FreeBSD-current is safe again to run Crypto. 3931dece4a9SWarner Losh 394673d13f2SWarner Losh20000709: 395c6dd1430SWarner Losh phk made the malloc default options AJ. This may slow things 396c6dd1430SWarner Losh down and uncover other latent bugs in the code. If you need to 397c6dd1430SWarner Losh run at full speed, you can disable this by doing the following: 398673d13f2SWarner Losh ln -s aj /etc/malloc.conf 399673d13f2SWarner Losh 400e98e26cdSWarner Losh20000706: 401e98e26cdSWarner Losh libftpio's version was accidentally bumped a few days ago. This 402e98e26cdSWarner Losh has been corrected. You may need to remove /usr/lib/libftpio.so.6 403e98e26cdSWarner Losh before doing your next buildworld/installworld pair. It certainly 404f699bbbbSMark Ovens won't hurt to remove it before the update procedure. It will 405e98e26cdSWarner Losh break fetch until a new one is built, but ftp can be used in the 4062c021c6cSMark Ovens interim if needed. 407e98e26cdSWarner Losh 408e98e26cdSWarner Losh20000705: 409e98e26cdSWarner Losh The crypto packages have changed for the cvsup. This has been done 410e98e26cdSWarner Losh in a backward compatible way, but the old packages will go away at 411e98e26cdSWarner Losh some point in the future. Look at /usr/share/examples/cvsup for 412e98e26cdSWarner Losh details. 413e98e26cdSWarner Losh 414c373950eSWarner Losh20000704: 4152f961bc8SWarner Losh With the new sys/modules/sound/drivers/*, you will need to 4162f961bc8SWarner Losh set SYSDIR until you do an installworld after July 7th. 4172f961bc8SWarner Losh 4182f961bc8SWarner Losh20000704: 419c373950eSWarner Losh rc.shutdown and rc will now call the rc.d scripts with start 420c373950eSWarner Losh or stop. This may cause some harmless warnings from older 421c373950eSWarner Losh rc.d scripts that haven't been updated. 422c373950eSWarner Losh 42327dc3a2bSWarner Losh20000630: 42427dc3a2bSWarner Losh The libfetch based version of fetch has gone into the tree. 42527dc3a2bSWarner Losh Minor problems may result on some of the less popular sites, 42627dc3a2bSWarner Losh which should be reported to des@freebsd.org. 42727dc3a2bSWarner Losh 428b8c215acSWarner Losh20000625: 429b8c215acSWarner Losh From approximately this date forward, one must have the crypto 43027dc3a2bSWarner Losh system installed in order to build the system and kernel. 43127dc3a2bSWarner Losh While not technically strictly true, one should treat it as 43227dc3a2bSWarner Losh required and grab the crypto bits. If you are grabbing CVS 43327dc3a2bSWarner Losh trees, src-all and cvs-crypto should be treated as if they 43427dc3a2bSWarner Losh were required. You should check with the latest collections 43527dc3a2bSWarner Losh to make sure that these haven't changed. 436b8c215acSWarner Losh 4377b990719SWarner Losh20000624: 4387b990719SWarner Losh Mark Murray just committed the first parts of a cleanup of 4397b990719SWarner Losh /dev/zero, et al. This is also cleaning up /dev/random. 4407b990719SWarner Losh The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 4417b990719SWarner Losh -CURRENT FROM THIS POINT FORWARD for cryptographic services 4427b990719SWarner Losh until Mark can merge in the fixes to this work in progress. 4437b990719SWarner Losh openssh and openssl should not be used to generate keys from this 4447b990719SWarner Losh date to the completion of the work. 4457b990719SWarner Losh 44627dc3a2bSWarner Losh If you must operate at this reduced level of security, add ' 44727dc3a2bSWarner Losh options RANDOMDEV' to your kernel or modload the randomdev 44827dc3a2bSWarner Losh module. You may also need to copy a new MAKEDEV to /dev and 44927dc3a2bSWarner Losh recreate the random and urandom devices. 45027dc3a2bSWarner Losh 45181e54c50SWarner Losh20000622: 45281e54c50SWarner Losh The license on the softupdates is now a standard 2 clause 45381e54c50SWarner Losh BSD license. You may need to remove your symbolic links 45481e54c50SWarner Losh that used to be required when updating. 45581e54c50SWarner Losh 45639943833SWarner Losh20000621: 4572c021c6cSMark Ovens Scott Flatman <sf@aracnet.com> sent in a decent write-up on 4582a2f33fbSDaniel Baker the config file update procedure. 4592a2f33fbSDaniel Baker http://people.freebsd.org/~imp/config-upd.html 460c373950eSWarner Losh NOTE: LINT is gone. It has been replaced with NOTES. NOTES 461a24eff53SWarner Losh isn't buildable. However, you can generate a LINT file. 46239943833SWarner Losh 463290f9ad8SWarner Losh20000620: 464290f9ad8SWarner Losh Binutils 2.10 have hit the tree, or will shortly. As soon 465290f9ad8SWarner Losh as they do, the problem noted in 20000522 will be resolved and 466290f9ad8SWarner Losh that workaround will no longer be required. 467290f9ad8SWarner Losh 46890fb6346SWarner Losh20000615: 46990fb6346SWarner Losh phk removed the compatibility creation of wd devices in the 47090fb6346SWarner Losh ad driver. If you haven't done so already, you must update 47190fb6346SWarner Losh your fstab, etc to use the ad devices instead of the wd 47290fb6346SWarner Losh devices. 47390fb6346SWarner Losh 474f75f65bbSWarner Losh In addition, you'll need to update your boot blocks to a 475f75f65bbSWarner Losh more modern version, if you haven't already done so. Modern 476f75f65bbSWarner Losh here means 4.0 release or newer (although older releases 477f75f65bbSWarner Losh may work). 478f75f65bbSWarner Losh 479ba26da8eSWarner Losh20000612: 480ba26da8eSWarner Losh Peter took an axe to config(8). Be sure that you read his mail 481290f9ad8SWarner Losh on the topic before even thinking about updating. You will 482c6dd1430SWarner Losh need to create a /boot/device.hints or add a hints directive 483290f9ad8SWarner Losh to your config file to compile them in statically. The format 484f54a3542SWarner Losh of the config file has changed as well. Please see GENERIC or 485f54a3542SWarner Losh NEWCARD for examples of the new format. 486290f9ad8SWarner Losh 487d65850ebSWarner Losh20000522: 488ba26da8eSWarner Losh A new set of binutils went into the tree today. Anybody 489d65850ebSWarner Losh building a kernel after this point is advised that they need 490d65850ebSWarner Losh to rebuild their binutils (or better yet do a 491d65850ebSWarner Losh buildworld/installworld) before building a new kernel. 492d65850ebSWarner Losh 493d9583a00SWarner Losh Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 494d9583a00SWarner Losh or MALLOC_OPTIONS env var) J will cause ld to dump core. It 495d9583a00SWarner Losh is recommended that you don't set this option until the problem 496d9583a00SWarner Losh is resolved. 497d9583a00SWarner Losh 4988039cedeSWarner Losh20000513: 4998039cedeSWarner Losh The ethernet drivers were all updated to clean up the BPF handling. 5008039cedeSWarner Losh 501d65850ebSWarner Losh20000510: 5028039cedeSWarner Losh The problems with boot blocks on the alphas have been corrected. 5038039cedeSWarner Losh This will require some care in updating alphas. A new libstand 5048039cedeSWarner Losh is requires for the boot blocks to build properly. 5058039cedeSWarner Losh 5068039cedeSWarner Losh20000503: 5078039cedeSWarner Losh Recompile all kld modules. Proper version dependency info 5088039cedeSWarner Losh is now available. 5098039cedeSWarner Losh 510d65850ebSWarner Losh20000502: 511d65850ebSWarner Losh Modules have been disconnected from the buildworld tree and 512d65850ebSWarner Losh connected to the kernel building instead. 513d65850ebSWarner Losh 514be149406SNik Clayton20000427: 5158039cedeSWarner Losh You may need to build gperf 5168039cedeSWarner Losh cd /usr/src/gnu/usr.bin/gperf && make depend all install 5178039cedeSWarner Losh when upgrading from 4.0 -> current. The build system now uses 5188039cedeSWarner Losh an option only in -current. 5198039cedeSWarner Losh 5202b8dd5f4SWarner Losh20000417: 5212b8dd5f4SWarner Losh The method that we brand ELF binaries has changed to be more 522f699bbbbSMark Ovens acceptable to the binutils maintainers. You will need to 5232b8dd5f4SWarner Losh rebrand your ELF binaries that aren't native. One problem 5242b8dd5f4SWarner Losh binary is the Linux ldconfig. After your make world, but 5252c021c6cSMark Ovens before you reboot, you'll need to issue: 5262b8dd5f4SWarner Losh brandelf -t Linux /compat/linux/sbin/ldconfig 5272b8dd5f4SWarner Losh if you have Linux compatibility enabled on your machine. 5282b8dd5f4SWarner Losh 5298d9f1945SWarner Losh20000320: 5302b8dd5f4SWarner Losh If you have really bad/marginal IDE drives, you may find they 5312b8dd5f4SWarner Losh don't work well. Use pio mode instead. The easiest way to 5322b8dd5f4SWarner Losh cope if you have a problem combination is to add: 5338d9f1945SWarner Losh /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 5342b8dd5f4SWarner Losh to the start of /etc/rc.conf. 5358d9f1945SWarner Losh 536f8ab1dd6SWarner Losh20000319: 537f699bbbbSMark Ovens The ISA and PCI compatibility shims have been connected to the 538f8ab1dd6SWarner Losh options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 539f8ab1dd6SWarner Losh style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 540f8ab1dd6SWarner Losh include the appropriate option in your kernel config. Drivers 541f8ab1dd6SWarner Losh using the shims should be updated or they won't ship with 542f8ab1dd6SWarner Losh 5.0-RELEASE, targeted for 2001. 543f8ab1dd6SWarner Losh 54419cada77SWarner Losh20000318: 545f699bbbbSMark Ovens We've entered the traditional post release dumping party. 54619cada77SWarner Losh Large kernel changes are being committed and are in the 54719cada77SWarner Losh works. It is important to keep the systems' klds and kernel 54819cada77SWarner Losh in sync as kernel interfaces and structures are changing. 54919cada77SWarner Losh Before reporting kernel panics, make sure that all modules 55019cada77SWarner Losh that you are loading are up to date. 551ba228352SWarner Losh 55219cada77SWarner Losh20000315: 5536d23c382SWarner Losh If you are upgrading from an older version of FreeBSD, you 5546d23c382SWarner Losh need to update your boot blocks as well. 'disklabel -B ad0' 5556d23c382SWarner Losh will do the trick. This isn't critical until you remove your 5566d23c382SWarner Losh wd device entries in /dev, at which point your system will not 5576d23c382SWarner Losh boot. 5586d23c382SWarner Losh 5596d23c382SWarner Losh20000315: 56019cada77SWarner Losh 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 56119cada77SWarner Losh to upgrade to 4.0 from 3.x. 56257199806SWarner Losh 563dc0dbf5cSWarner LoshCOMMON ITEMS: 564dc0dbf5cSWarner Losh 565a24eff53SWarner Losh General Notes 566a24eff53SWarner Losh ------------- 567a24eff53SWarner Losh Avoid using make -j when upgrading. From time to time in the 568a24eff53SWarner Losh past there have been problems using -j with buildworld and/or 569a24eff53SWarner Losh installworld. This is especially true when upgrading between 570a24eff53SWarner Losh "distant" versions (eg one that cross a major release boundary 571a24eff53SWarner Losh or several minor releases, or when several months have passed 572a24eff53SWarner Losh on the -current branch). 573a24eff53SWarner Losh 574dc0dbf5cSWarner Losh To build a kernel 575dc0dbf5cSWarner Losh ----------------- 576ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 577f699bbbbSMark Ovens a few days old), you should follow this procedure. With a 578ba01eb20SWarner Losh /usr/obj tree with a fresh buildworld, 5791e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 5801e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 581dc0dbf5cSWarner Losh 582ba01eb20SWarner Losh To just build a kernel when you know that it won't mess you up 583ba01eb20SWarner Losh -------------------------------------------------------------- 584ba01eb20SWarner Losh cd src/sys/{i386,alpha}/conf 585ba01eb20SWarner Losh config KERNEL_NAME_HERE [1] 586ba01eb20SWarner Losh cd ../../compile/KERNEL_NAME_HERE 587ba01eb20SWarner Losh make depend 588ba01eb20SWarner Losh make 589ba01eb20SWarner Losh make install 590ba01eb20SWarner Losh 591ba01eb20SWarner Losh [1] If in doubt, -r might help here. 592ba01eb20SWarner Losh 593ba01eb20SWarner Losh If this fails, go to the "To build a kernel" section. 594ba01eb20SWarner Losh 595ba01eb20SWarner Losh To rebuild everything and install it on the current system. 596ba01eb20SWarner Losh ----------------------------------------------------------- 597759f0aefSWarner Losh make world 598fdb9f54dSWarner Losh Build a new kernel, see above. 599759f0aefSWarner Losh 6001dece4a9SWarner Losh To upgrade from 4.x-stable to current 601ba26da8eSWarner Losh ------------------------------------- 602ba26da8eSWarner Losh make buildworld 6031e159248SWarner Losh make buildkernel KERNCONF=YOUR_KERNEL_HERE 6047595222aSWarner Losh cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 6051e159248SWarner Losh make installkernel KERNCONF=YOUR_KERNEL_HERE 606ba26da8eSWarner Losh make installworld 6077595222aSWarner Losh mergemaster 608134d2e86SWarner Losh [1] 609ba26da8eSWarner Losh <reboot> 610ba26da8eSWarner Losh 611fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 612fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 613fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 614fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 615fdb9f54dSWarner Losh the UPDATING entries. 616ba26da8eSWarner Losh 6171dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 6181dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 6191dece4a9SWarner Losh your sources that you have read and understood all the recent 6201dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 6211dece4a9SWarner Losh much fewer pitfalls. 6221dece4a9SWarner Losh 623134d2e86SWarner Losh [1] If you have third party modules, such as vmware, you 624134d2e86SWarner Losh should disable them at this point so they don't crash your 625134d2e86SWarner Losh system on reboot. 626134d2e86SWarner Losh 6279c1a7444SWarner Losh [2] If you have legacy ISA devices, you may need to create 6289c1a7444SWarner Losh your own device.hints to reflect your unique hardware 6299c1a7444SWarner Losh configuration. 6309c1a7444SWarner Losh 631dc0dbf5cSWarner LoshFORMAT: 632dc0dbf5cSWarner Losh 633f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 6341fc1a0dcSWarner Loshbreakages in tracking -current. Not all things will be listed here, 635f8ab1dd6SWarner Loshand it only starts on March 15, 2000. Updating files can found in 636f8ab1dd6SWarner Loshprevious releases if your system is older than this. 6371fc1a0dcSWarner Losh 6383645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so 6393645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained. 640f8c77507SWarner Losh 64197d92980SPeter Wemm$FreeBSD$ 642