UPDATING revision 113999
1Updating Information for FreeBSD current users 2 3This file is maintained and copyrighted by M. Warner Losh 4<imp@village.org>. See end of file for further details. For commonly 5done items, please see the COMMON ITEMS: section later in the file. 6 7NOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW: 8 FreeBSD 5.0-CURRENT has many debugging features turned on, in 9 both the kernel and userland. These features attempt to detect 10 incorrect use of system primitives, and encourage loud failure 11 through extra sanity checking and fail stop semantics. They 12 also substantially impact system performance. If you want to 13 do performance measurement, benchmarking, and optimization, 14 you'll want to turn them off. This includes various WITNESS- 15 related kernel options, INVARIANTS, malloc debugging flags 16 in userland, and various verbose features in the kernel. Many 17 developers choose to disable these features on build machines 18 to maximize performance. 19 2020030423: 21 A bug has been fixed in /dev/devctl which would cause devd 22 to hang on boot, were it not for a workaround in devd. The 23 work around in devd will be removed around 20030507. You 24 have until then to upgrade your kernel before updating 25 userland. In general, you should have a userland and 26 kernel that's in sync with each other. However, given the 27 effects of this bug (hang on boot when starting devd), some 28 allowances are made. 29 3020030208: 31 sendmail 8.12.7 has been imported. It has one important 32 change for IPv6 users. The default submit.mc now uses 33 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 34 used to connect to the MTA. Users on IPv6-only machines 35 will need to edit /etc/mail/submit.mc appropriately. 36 3720030128: 38 NODEVFS option has been removed and DEVFS thereby made standard. 39 This makes all references to MAKEDEV obsolete, and they should 40 be removed when convenient. 41 4220030126: 43 The name of the device for the ofw console has changed, sparc64 users 44 must run mergemaster to update their installed /etc/ttys. 45 4620030125: 47 The scheduler framework has grown a second scheduler and consequently 48 you must specify one and only one scheduler in your kernel config. 49 The cvs config files have been updated to use the old scheduler 50 which may be selected via 'options SCHED_4BSD'. If you would like 51 to try the new, much more experimental, scheduler please try 52 'options SCHED_ULE' and contribute to the arch@ discussion. 53 5420030115: 55 A new version of the wi driver has been imported into the tree. 56 One now must have device wlan in the config file for it to operate 57 properly. 58 59 In addition, there have been some changes to how wi devices are 60 configured for point to point links to bring it more in line 61 with the former way of doing things, as well as compatibility 62 with NetBSD. 63 6420021222: 65 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 66 used an incompatible form of ABI for returning structures and unions 67 which FreeBSD's GCC maintainers were not aware of relative to previous 68 versions of FreeBSD. We have gone back to the ABI for now, and any 69 code compiled which is required to interoperate with other code (not 70 built at the same time) returning structs or unions should be 71 rebuilt. 72 7320021216: 74 A name change in /etc/netconfig has been reverted to stay 75 compatible with suns TIRPC and also with NetBSD. You need 76 to run mergemaster after make world. A new libc does still work 77 with an outdated /etc/netconfig for some time, but you'll get 78 a warning. This warning will be removed in 20030301. 79 8020021202: 81 The recent binutils upgrade marks a kernel flag day on 82 sparc64: modules built with the old binutils will not work 83 with new kernels and vice versa. Mismatches will result in 84 panics. Make sure your kernel and modules are in sync. 85 8620021029: 87 The value of IPPROTO_DIVERT has changed. Make sure to keep 88 your kernel, netstat, natd and any third-party DIVERT 89 consumers in sync. 90 9120021024: 92 Old, compatibility slices have been removed in GEOM kernels. 93 This means that you will have to update your /etc/fstab to 94 not use disk devices of the form /dev/ad0a. Instead, you 95 now must specify /dev/ad0s1a, or whatever slice your FreeBSD 96 partition really is on. The old device names have gone 97 away, so if you use them anywhere else, you must also adjust 98 those uses. (This doesn't affect the disks formatted in 99 the ``dangerously-dedicated'' mode.) 100 10120021023: 102 Alphas with kernels from between 20020830 and 20021023 and/or 103 rtld (ld-elf.so.1) older than 20021023 may experience problems 104 with groff while doing a buildworld (kernel: "out of memory", 105 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 106 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 107 108 So, to successfully upgrade your Alpha, you must either 109 upgrade your kernel and rtld first (which might be a bit 110 tricky), or avoid running the bootstrapped groff during the 111 "transitional" buildworld. To avoid running groff during the 112 transitional upgrade run make buildworld with -DNOMAN, 113 -DNO_SHAREDOCS, and -DNO_LPR. 114 11520020831: 116 gcc has been upgraded to 3.2. It is not all binary compatible 117 with earlier versions of gcc for c++ programs. All c++ 118 programs and libraries need to be recompiled. 119 120 Also, if you encounter g++ issues, rm /usr/include/g++/* before 121 doing an installworld to make sure that stale files are removed. 122 12320020827: 124 Our /etc/termcap now has all the entries from the XFree86 xterm 125 almost unchanged. This means xterm now supports color by default. 126 If you used TERM=xterm-color in the past you now should use 127 TERM=xterm. (xterm-color will lead to benign warnings). 128 12920020815: 130 A "bug" in gcc(1) that was hiding warning in system headers was 131 fixed. It's probably time to add -DNO_WERROR to your make line 132 again. 133 13420020729: 135 COPY is being deprecated. The 20010530 change was reverted, as 136 it causes far more pain than was expected, and to always compare 137 before installing, please use INSTALL="install -C" again. The 138 -C option is now silently ignored when used with the -d option. 139 14020020702: 141 Problems with libc_r clients like KDE and GNOME have been resolved. 142 There are still some minor problems with some signals but the 143 system is stable enough for general use again. SMP is less so than UP 144 but each can successfully complete multiple buildworlds. 145 Libkvm needs to be recompiled due to KSE. 146 14720020701: 148 Now would be a bad time to upgrade. Something in or near the 149 KSE commit totally broke programs using libc_r like KDE and 150 GNOME. 151 15220020511: 153 The k5su utility installed as part of Kerberos 5 is no longer 154 installed with the set-user-ID bit set by default. Add 155 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 156 with the set-user-ID bit set. 157 15820020510: 159 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 160 Unfortunately our native GDB (at version 4.18) does not understand 161 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 162 generated debugging information for our native GDB. 163 16420020510: 165 Due to the way CVS works, it may not properly update src/contrib/gcc 166 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 167 and then do a cvs update. 168 16920020421: 170 When exec'ing set[ug]id executables, the kernel now ensures that the 171 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 172 17320020404: 174 New sendmail startup scripts have been installed to make it 175 easier to use alternative MTAs with FreeBSD. Setting the rc.conf 176 variable sendmail_enable to "NO" no longer prevents any sendmail 177 daemons from starting. Instead, either set sendmail_enable to 178 "NONE" or change mta_start_script to a script for starting 179 an alternative MTA. Setting mta_start_script to "" will 180 also prevent any MTA from being started at boot. 181 18220020403: 183 UCONSOLE is no longer a valid kernel option. 184 18520020315: 186 FreeBSD 5.0 DP-1 was basically branched today. 187 18820020225: 189 Warnings are now errors in the kernel. Unless you are a developer, 190 you should add -DNO_WERROR to your make line. 191 19220020217: 193 sendmail 8.12.2 has been imported. The sendmail binary is no 194 longer a set-user-ID root binary and the infrastructure to support 195 command line mail submission has changed. Be sure to run 196 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 197 and /etc/mail) and read /etc/mail/README for more details. 198 199 Due to the import of sendmail 8.12.2, a new user and group are 200 required in order for sendmail to run as a set-group-ID 201 binary. A 'make installworld' will use the new user and group 202 to set the owner and group of /var/spool/clientmqueue and will 203 fail if the new user and group do not exist. The 'smmsp' user 204 and group must be merged from src/etc/group and 205 src/etc/master.passwd before using 'make installworld'. 206 'mergemaster -p' will do this. You may need to install 207 mergemaster before this will work if you are updating from a 208 very old version of current. The updating recipe has changed 209 as of this date. 210 21120020112: 212 The preferred configuration method for PAM is now /etc/pam.d/ 213 rather than /etc/pam.conf. If you have an unmodified 214 pam.conf, just delete it after your next mergemaster run. If 215 you have local modifications, you can use 216 /usr/src/etc/pam.d/convert.pl to incorporate them into your 217 /etc/pam.d. 218 219 Please see the following url for more details: 220http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 22120011229: 222 If anyone here is already using the new rc.conf(5) variable 223 networkfs_types, please note that it has changed 224http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 225 22620011220: 227 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 228 started out its life in the ISDN4BSD project as an offspring 229 from sys/net/if_spppsubr.c, which eventually got a life of its 230 own. All the accumulated features and bugfixes of the i4b 231 version have now been merged back into the base system's 232 version now. The only user-visible change resulting from this 233 is that i4b's sppp(4) interfaces are to be managed with 234 spppcontrol(8) again, since ispppcontrol(8) has been retired 235 as well. (There has never been rc file support for 236 ispppcontrol in -current, but only in -stable. That will be 237 reverted by the time the changes are MFCed.) 238 23920011215: 240 The fdc(4) driver has been updated and now automatically 241 recognizes media in `standard' formats (like 1440 KB and 242 720 KB for a 3.5" high-density drive) when accessing the 243 default device node (e. g. /dev/fd0). The old variety of 244 floppy device nodes /dev/fd*.* is no longer present by 245 default, devices can be created (in DEVFS) on demand. They 246 will need to be customized then for `odd' densities using 247 fdcontrol(8). 248 24920011209: 250 The bugs in procfs' debugging support code have been fixed, 251 and truss(1) now works again. 252 25320011207: 254 Daily security checks have been split out to use the periodic(8) 255 scripts. Some change in configuration may be necessary. Please 256 see 257http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 258 for details. 259 26020011204: 261 sos added VCD/SVCD support to ata driver and that needs the 262 kernel and burncd to be in sync. 263 26420011203: 265 The procfs pseudo-filesystem has now been converted to use the 266 pseudofs framework. If you have 'options PROCFS' in your 267 kernel config, you'll need to add 'options PSEUDOFS' if it's 268 not there already. 269 270 This change temporarily breaks truss(1); use ktrace(1) instead 271 until the issue has been resolved. 272 27320011202: 274 A security hole in OpenSSH involving `UseLogin yes' has been 275 patched. 276 27720011126: 278 You need to remove /usr/obj/.../usr.bin/tip before rebuilding 279 after this date. You need to do this only once. 280 28120011103: 282 Most of the awk issues have been resolved. Some rough 283 edges may be left, but for the most part things should be 284 back to "normal." For CURRENT's usual definition of "normal." 285 28620011030: 287 Awk has been upgraded to the one true awk from bell labs. Expect 288 choppy waves in the upgrade process. 289 29020011030: 291 The asr driver problem has been resolved. 292 29320011027: 294 Due to changes in other parts of the system, the asr driver 295 now causes the system to panic on boot. Do not use it pending 296 correction. Comment it out of any kernel config file that you 297 try to use from this date forward. 298 29920011025: 300 When crossbuilding, use TARGET=xxx where you used to use 301 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 302 unless you are changing both of them. To cross build pc98 on 303 an alpha, for example, you need to set TARGET=pc98 and 304 TARGET_ARCH=i386. 305 30620011001: 307 The kernel interface that burncd depends on has changed. 308 You must recompile both the kernel and userland applications 309 at the same time. 310 31120010929: 312 When crossbuilding, please set TARGET_ARCH rather than 313 MACHINE_ARCH to indicate the target. In the future, one will 314 set TARGET_MACHINE where you set MACHINE now. At the moment, 315 setting MACHINE alone for same MACHINE_ARCH machines works 316 (eg, you can build pc98 on an i386 machine and vice versa). 317 31820010927: 319 Some weird problems result from using ACPI on some machines. 320 To disable ACPI you can add 321 hint.acpi.0.disabled="1" 322 to /boot/loader.conf (or by putting set X=Y at the boot 323 loader "ok" prompt). 324 325 Alternatively, you can remove it from /boot/kernel/acpi.ko 326 or use the MODULES_OVERRIDE function in your kernel config 327 file and not list acpi in that list. 328 32920010924: 330 The buildworld has been fixed. You may need to install 331 the 4.x compatibility libraries for some old binaries 332 to work. Add COMPAT4X=true to your /etc/make.conf to 333 get them installed on every installworld, or execute the 334 following to get them installed only once: 335 cd src/lib/compat/compat4x.<arch> 336 make all install 337 You will see ``__stdoutp undefined'' until you do this. 338 33920010919: 340 There's a bug in the world build process. The cross-tools 341 are build with the NEW headers, but the OLD libc.a. This 342 leads to all kinds of problems with the new libc. A temporary 343 workaround is to add 344 CFLAGS="-O -pipe -D_OLD_STDIO" 345 before building world when upgrading from 4.x to current. This 346 can be removed afterwards. 347 348 A proper fix to the buildworld target is needed. 349 35020010918: 351 Peter has committed his new kthread nfs client/server code. 352 NFS may be unstable after this date. 353 35420010912: 355 KSE has hit the tree. Lots of things are now different in 356 the kernel. While a few problems were introduced in the 357 initial commit, most of the major ones have been found and 358 corrected. 359 36020010901: 361 In OLDCARD, CardBus bridges appear to be stable. The work 362 arounds described in the 20010604 entry are now no longer 363 necessary and will be ignored. Most insert/remove problems 364 have been rectified around this date. 365 36620010823: 367 named now runs as user bind and group bind rather than as 368 root. If named_enable is set to YES in /etc/rc.conf, ensure 369 that user bind is available in /etc/passwd (using vipw(8)) 370 and that group bind is available in /etc/group. Also make 371 sure that user or group bind has read (and not write) 372 permission for your name server configuration and that it 373 has read and write permission for your slave zone files and 374 directory. 375 376 If you wish to continue to run named as root (a less secure 377 alternative), add a line to /etc/rc.conf saying 378 379 named_flags= 380 38120010709: 382 The PAM libraries have had an API upgrade that is beyond 383 the ability of the shared library major number to handle. 384 It is manifested by PAM-using ports dumping core. The 385 solution is to rebuild those ports. 386 38720010628: 388 The kernel compile module has moved from src/sys/compile/FOO 389 to src/sys/${MACHINE}/compile/FOO. 390 39120010625: 392 The pccard modem issue from 20010613 has been corrected. 393 OLDCARD support is still a little weak in -current. slot 1 is 394 known not to work on some TI based cardbus bridges. Some 395 cardbus bridges do not properly detect insert/removal events. 396 IRQ configuration needs more safety belts. 397 39820010617: 399 Softupdates problems have been corrected. 400 40120010614: 402 Peter ripped out the linkerset support. You must, as always, 403 rerun config after you cvsup if you are using the traditional 404 kernel building methods. 405 40620010613: 407 pccard modems may not work with current after 20010604 date. Some 408 do, others result in panics. *MAKE*SURE* that you update your 409 config and /etc/rc.conf ala the 20010604 entry, or you will have 410 problems (this issue will be fixed, it just hasn't been yet). 411 41220010613: 413 SOFTUPDATES seem to be broken since the middle of May or so. Do not 414 use them in current. You can disable softupdates on all mounted 415 partitions, or remove SOFTUPDATES the kernel config file. 416 41720010612: 418 After Peter's commits to the hints code, people have been noticing 419 that certain devices are attached (or try to) twice. This is due 420 to having both static hints as well as a /boot/device.hints. To 421 work around this issue, please use only one or the other mechanism 422 until this bug is fixed. 423 424 Please note that a feature of config is that if you have config 425 file FOO and FOO.hints, it automatically adds FOO.hints to the 426 hints.c file, whether you want it to or not. 427 42820010610: 429 Locale names have changed to match other systems better. 430 43120010604: 432 pccard support for pci cards has been committed. You must change 433 your /etc/pccard.conf irq lines. It must match the irq used by 434 pcic device. Interrupt storms may result if you fail to do this. 435 Interrupt storms look a lot like a hang. 436 437 You must also install a new pccardd, otherwise you will get an 438 interrupt storm at card reset time (just after it tells you what 439 it is). 440 441 pccardd_flags="-I" is necessary for the time being. It tells pccardd 442 not to ask the kernel if the interrupt is really free or not before 443 using it. You can either change the /etc/pccard.conf irq lines to 444 match pcic, or add "-i X" to the pccardd_flags. 445 44620010530: 447 INSTALL=install -C is being deprecated. If you want to do this, 448 use COPY=-C instead. The former method will be supported for only 449 a limited time. If you see 450 451install: warning: the -d and -C options may not be specified together 452 453 in your makeworld, then you need to migrate towards using 454 COPY=-C. 455 45620010525: 457 It appears that vm is now stable enough to use again. However, 458 there may be other problems, so caution is still urged. alpha 459 definitely is in bad shape. 460 46120010521: 462 Minor repo damage has happened. This may cause problems 463 with cvsup of ports. If you get errors, please see 464 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 465 at the bottom for details on a workaround. The error message 466 is 467Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 468 46920010520: 470 Vm and/or swapping are busted on -current. Please be patient. 471 47220010519: 473 pccard has had much reorganizational work done to it over 474 the past few days. Everything should still work, but if 475 not, please contact imp@freebsd.org. 476 47720010517: 478 ata ioctl changed. Make sure to recompile both kernel and 479 userland at the same time. 480 48120010517: 482 New ncurses imported. 483 48420010512: 485 DEVFS is now opt out, not opt in. Barring major problems, this 486 will be the only way to go starting July 1. 487 48820010504: 489 OpenSSH has been updated to 2.9. Some defaults are different, 490 including RhostsRSAAuthentication, which changes from yes to no. 491 49220010502: 493 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 494 49520010501: 496 Building perl was broken at 02:25:25 PDT. 497 49820010430: 499 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 500 go back in the water. 501 50220010429: 503 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 504 this date, but before the correction date. 505 50620010423: 507 old fsck and new kernel interactions appear to have been fixed. 508 50920010411: 510 fsck and the kernel were changed to handle some optimizations 511 to directory layout. This breaks backward compatibility. 512 Update only if you understand that you must not use the old 513 fsck with the new kernel ever. 514 51520010330: 516 fsck has changed the meaning of the pass column in /etc/fstab. 517 Please see the cvs commit to fsck.8 or the fsck.8 man page for 518 details. It is unclear if changes to /etc/fstab are necessary. 519 52020010319: 521 portmap had changed name to rpcbind for maximum POLA in your 522 current world. /etc/hosts.{allow,deny} needs changes. nfs and 523 other rpc based programs that rely on portmapper will not work 524 without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 525 52620010315: 527 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 528 and ATA_ENABLE_TAGS are no longer kernel options. They have 529 been replaced by tunables. See ata.4 for details. 530 53120010312: 532 The fxp driver was converted to use miibus. If you compile 533 fxp into your kernel statically, you will need to add miibus. 534 53520010312: 536 The wi device now defaults to BSS (infrastructure) mode 537 instead of ad-hoc. 538 53920010310: 540 /dev/urandom should be a symbolic link to /dev/random now. 541 Users of current not using DEVFS need to run MAKEDEV std. 542 ssh might not work if you don't. 543 54420010303: 545 The ed driver has been updated. It now allows mii attachments, 546 which means that you must include the miibus in your kernel if 547 you use the ed driver. 548 54920010220: 550 The problems with libc have been corrected. It is now mostly 551 safe to go back into the water. 552 55320010211: 554 The size of FILE was changed. This breaks upgrading. If 555 you must upgrade, be prepared for pain. It also breaks almost 556 all binaries that you've compiled on -current. You are warned 557 that before upgrading would be a good time to do a level 0 558 dump of your system. No, really, I mean it this time. 559 560 To get to the new system, you'll need to use the following 561 workaround. Hopefully this can be sorted out so that we 562 don't have to move this to the updating section. 563 564 To get around the installworld problem, do: 565 # cd /usr/src/usr.bin/sed 566 # make install 567 # cd /usr/src 568 # make installworld 569 If that doesn't work, then try: 570 # make -k installworld 571 # make installworld 572 57320010207: 574 DEVFS is now the default. If you use vinum, make sure that you 575 do not include devfs in your kernel as problems result. 576 57720010205: 578 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 579 Remove them from your config. 580 58120010122: 582 ****************************** WARNING ****************************** 583 buildkernel has been changed slightly 584 ****************************** WARNING ****************************** 585 KERNCONF replaces the variable KERNEL for buildkernel. You 586 should update your scripts and make.conf accordingly. 587 58820010119: 589 config has changed to allow DEV_FOO as a replacement for NFOO. 590 This requires a new config to build correctly. 591 59220010116: 593 The kernel option I386_CPU is now mutually exclusive with the 594 other cpu types. If you have an i386 system, be sure that it 595 only had this line. Remove it for all other configurations. 596 59720010110: 598 Changes to the kernel require it and burncd be in sync. 599 60020010102: 601 Everyone who has hw.sndunit set to something in 602 /etc/sysctl.conf, it is now hw.snd.unit. 603 60420010101: 605 ex and vi were broken by some changes to sys/queue.h. If you 606 have a bad vi, you will see make buildworld fail with a core 607 dump while building termcap. You can work around this problem 608 by adding -k to your make buildworld. This will cause the 609 build to complete and install a new vi. Once that's done, you 610 can rebuild again without the -k to pick up anything that 611 might have been ignored by the -k option. 612 613 Others have suggested that you can just rebuild libc if your 614 vi/ex is dynamically linked, but I've not received any reports 615 of this working. 616 61720001228: 618 There have been some changes to libcrypt in -current. The 619 libscrypt/libdescrypt symlink silliness is gone and the installed 620 libcrypt is fully functional. Be aware of this. 621 62220001218: 623 Linksys Fast Ethernet PCCARD cards supported by the ed driver 624 now require the addition of flag 0x80000 to their config line 625 in pccard.conf(5). This flag is not optional. These Linksys 626 cards will not be recognized without it. 627 62820001205: 629 Important new FreeBSD-version stuff: PAM support has been worked 630 in, partially from the "Unix" OpenSSH version. This requires 631 adding the following in pam.conf: 632 633 sshd auth sufficient pam_skey.so 634 sshd auth required pam_unix.so try_first_pass 635 sshd session required pam_permit.so 636 63720001031: 638 cvs updated to 1.11. 639 64020001020: 641 The random device needs more entropy, so you need to make sure 642 that you've run mergemaster to get a /etc/rc which will seed 643 /dev/random. If you don't and the system hangs after ldconfig, 644 then banging on the keyboard randomly until it unhangs is one 645 workaround. 646 64720001010: 648 ****************************** WARNING ****************************** 649 Sendmail has been updated. 650 ****************************** WARNING ****************************** 651 o mail.local(8) is no longer installed as a set-user-id binary. 652 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 653 is set. 654 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 655 commands. 656 o Now using sendmail's version of vacation(1). 657 o The sendmail cf building tools (contrib/sendmail/cf) are installed 658 in /usr/share/sendmail/cf. 659 o sendmail.cw changed to local-host-names 660 661 More details can be found at 662 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 663 66420001009: 665 The ports tree's new layout is in place. Be sure to update 666 your entire ports tree, or you will have problems. 667 66820001006: 669 The perl build procedure no longer installs miniperl, nor uses 670 the installed miniperl. It is recommended that you delete 671 /usr/bin/miniperl. 672 67320001005: 674 This weekend the ports tree will be updated to a new layout. 675 It will be in an inconsistent state until noted in the UPDATING 676 file, or with asami-san's message to the relevant mailing 677 lists. With this new layout, you'll need to update the whole 678 tree for anything to work. 679 68020000928: 681 There was a change in the passwd format. Need more information. 682 68320000916: 684 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 685 place. Please update boot loader (not the boot blocks) at the 686 same time as your kernel. 687 68820000914: 689 The new pmtimer device is necessary for laptops. Failure to 690 include the device will cause suspended laptops losing time 691 when they resume. Include 692 device pmtimer 693 in your config file and 694 hint.pmtimer.0.at="isa" 695 to your /boot/device.hints file. 696 69720000911: 698 The random device has been turned into a (pseudo-)device, 699 rather than an option. The supplied kernel config files have 700 been updated. You will need to do something similar in your 701 own kernel config file. 702 Remove: 703 options RANDOMDEV 704 Add: 705 device random 706 If you prefer to load the loadable module, you need to do 707 nothing. 708 70920000909: 710 The random device module has been renamed from randomdev.ko to 711 random.ko. You will need to edit your /boot/loader.conf to 712 reflect this if you load this module at boot time. 713 The line should read: 714 random_load="YES" 715 71620000907: 717 The SMPNG commit has happened. It should work, but if it 718 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 719 to be a variety of minor issues. Please see 20000905 to make 720 sure you don't have model loading problems which might at 721 first blush appear related to SMP. 722 72320000906: 724 nsswitch has been imported from NetBSD. Among other things, 725 this means that /etc/host.conf is no longer used. See 726 nsswitch.conf(5) instead. Note that at boot time rc.network 727 will attempt to produce a new nsswitch.conf file for you if you 728 don't have one, and you have host.conf. 729 73020000905: 731 The ucred structure changed size. This breaks the interface 732 that mountd uses. Trying to use an older mountd with a newer 733 kernel guarantees a panic. This means that you need to use 734 kernels newer than today only with matching mountd, but you 735 needed to do that anyway with the boot loader changes. 736 73720000905: 738 The boot loader has been updated. The new default kernel is 739 now /boot/kernel/kernel.ko. The new default module location 740 is /boot/kernel. 741 742 You *MUST* upgrade your boot loader and kernel at the same time. 743 The easiest way to do this is to do the buildworld/buildkernel/ 744 installkernel/installworld dance. 745 746 Furthermore, you are urged to delete your old /modules directory 747 before booting the new kernel, since kldload will find stale 748 modules in that directory instead of finding them in the correct 749 path, /boot/kernel. The most common complaint that this cures 750 is that the linux module crashes your machine after the update. 751 752 if [ ! -d /boot/kernel.old ]; then 753 mv /modules.old /boot/kernel.old 754 chflags noschg /kernel.old 755 mv /kernel.old /boot/kernel.old/kernel.ko 756 chflags schg /boot/kernel.old/kernel.ko 757 fi 758 75920000904: 760 A new issue with the sendmail upgrade has come to light. 761 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 762 incorrectly install the default aliases in /etc/mail rather than 763 move the old one from /etc. So you'll need to manually move the 764 file, create a symbolic link, remove the old /etc/aliases.db and 765 run newaliases. For safety sake, you should stop sendmail 766 while doing this and run the upgrade when locally sourced email 767 is not likely to be generated. 768 76920000825: 770 /boot/device.hints is now required for installkernel to 771 succeed. You should copy GENERIC.hints for your architecture 772 into /boot/device.hints. If and only if you compile hints 773 into your kernel, then this file may be empty. Please note, 774 if you have an empty or missing /boot/device.hints file and 775 you neglected to compile hints into your kernel, no boot 776 messages will appear after the boot loader tries to start the 777 kernel. 778 77920000821: 780 If you do NOT have ``options RANDOMDEV'' in your kernel and 781 you DO want the random device then add randomdev_load="YES" to 782 /boot/loader.conf. 783 78420000812: 785 suidperl is now always built and installed on the system, but 786 with permissions of 511. If you have applications that use 787 this program, you are now required to add ENABLE_SUIDPERL=true 788 to /etc/make.conf. If you forget to do this, 789 chmod 4511 /usr/bin/suidperl 790 will fix this until the next build. 791 79220000812: 793 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 794 visible changes that may immediately affect your configuration 795 include: 796 - New default file locations from src/contrib/sendmail/cf/README 797 - newaliases limited to root and trusted users 798 - MSA port (587) turned on by default 799 - New queue file naming system so can't go from 8.11 -> 8.9 800 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 801 - FEATURE(`nullclient') is more full featured 802 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 803 - mail.local FreeBSD-only -b option changed to -B 804 - See src/contrib/sendmail/RELEASE_NOTES for more info 805 80620000810: 807 suidperl (aka sperl) is no longer build by default. You must 808 specifically define BUILD_SUIDPERL to "true" for it to be build. 809 Furthermore, we recommend that you remove /usr/bin/sperl* and 810 /usr/bin/suidperl files from your system unless you have a 811 specific use for it. 812 81320000729: 814 Networking defaults have been tightened. Anybody upgrading 815 /etc/defaults/rc.conf needs to add the following lines to 816 /etc/rc.conf if they want to have the same setup 817 afterwards (unless the variables already are set, of course): 818 # Enable network daemons for user convenience. 819 inetd_enable="YES" 820 portmap_enable="YES" 821 sendmail_enable="YES" 822 82320000728: 824 If you have null_load="YES" in your /boot/loader.conf, you 825 will need to change that to nullfs_load="YES". 826 82720000728: 828 The "installkernel" target has changed slightly. Now even if 829 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 830 it will install the MYKERNEL file (built with the buildkernel 831 target) as /kernel rather than /MYKERNEL. Those who have 832 updated their /boot/loader.conf files to point to /MYKERNEL 833 should remove that entry or perform manual rename of /kernel 834 to /MYKERNEL. 835 83620000711: 837 If you use CVSUP or CTM to get CVS trees, AND you used to get 838 the old crypto files from internat.freebsd.org AND you check 839 out files from the CVS tree with the cvs command, please read 840 http://people.freebsd.org/~imp/internat.txt 841 for details on potential problems that you might have and how 842 to get around them. 843 844 If you are merely a mirror, or don't answer yes to each of the 845 clauses above, you needn't worry. 846 84720000711: 848 /etc/security has been updated to print the inode number of 849 setuid programs that have changed. You will see a large spike 850 in the number of changed programs the first time when you run 851 mergemaster to get a new /etc/security. 852 85320000710: 854 /dev/random now has good entropy collection (from the keyboard 855 and sysmouse drivers). Please ensure that either `options 856 RANDOMDEV' is present in your kernel config file or that 857 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 858 not have the /dev/random driver, OpenSSL (and consequently 859 lots of crypto tools (like SSH)) will fail with strange 860 errors. (see below, 20000624). 861 862 FreeBSD-current is safe again to run Crypto. 863 86420000709: 865 phk made the malloc default options AJ. This may slow things 866 down and uncover other latent bugs in the code. If you need to 867 run at full speed, you can disable this by doing the following: 868 ln -s aj /etc/malloc.conf 869 87020000706: 871 libftpio's version was accidentally bumped a few days ago. This 872 has been corrected. You may need to remove /usr/lib/libftpio.so.6 873 before doing your next buildworld/installworld pair. It certainly 874 won't hurt to remove it before the update procedure. It will 875 break fetch until a new one is built, but ftp can be used in the 876 interim if needed. 877 87820000705: 879 The crypto packages have changed for the cvsup. This has been done 880 in a backward compatible way, but the old packages will go away at 881 some point in the future. Look at /usr/share/examples/cvsup for 882 details. 883 88420000704: 885 With the new sys/modules/sound/drivers/*, you will need to 886 set SYSDIR until you do an installworld after July 7th. 887 88820000704: 889 rc.shutdown and rc will now call the rc.d scripts with start 890 or stop. This may cause some harmless warnings from older 891 rc.d scripts that haven't been updated. 892 89320000630: 894 The libfetch based version of fetch has gone into the tree. 895 Minor problems may result on some of the less popular sites, 896 which should be reported to des@freebsd.org. 897 89820000625: 899 From approximately this date forward, one must have the crypto 900 system installed in order to build the system and kernel. 901 While not technically strictly true, one should treat it as 902 required and grab the crypto bits. If you are grabbing CVS 903 trees, src-all and cvs-crypto should be treated as if they 904 were required. You should check with the latest collections 905 to make sure that these haven't changed. 906 90720000624: 908 Mark Murray just committed the first parts of a cleanup of 909 /dev/zero, et al. This is also cleaning up /dev/random. 910 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 911 -CURRENT FROM THIS POINT to 2000710 for cryptographic services 912 until Mark can merge in the fixes to this work in progress. 913 openssh and openssl should not be used to generate keys from this 914 date to the completion of the work. 915 916 If you must operate at this reduced level of security, add ' 917 options RANDOMDEV' to your kernel or modload the randomdev 918 module. You may also need to copy a new MAKEDEV to /dev and 919 recreate the random and urandom devices. 920 92120000622: 922 The license on the softupdates is now a standard 2 clause 923 BSD license. You may need to remove your symbolic links 924 that used to be required when updating. 925 92620000621: 927 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 928 the config file update procedure. 929 http://people.freebsd.org/~imp/config-upd.html 930 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 931 isn't buildable. However, you can generate a LINT file: 932 cd /sys/<ARCH>/conf && make LINT 933 93420000620: 935 Binutils 2.10 have hit the tree, or will shortly. As soon 936 as they do, the problem noted in 20000522 will be resolved and 937 that workaround will no longer be required. 938 93920000615: 940 phk removed the compatibility creation of wd devices in the 941 ad driver. If you haven't done so already, you must update 942 your fstab, etc to use the ad devices instead of the wd 943 devices. 944 945 In addition, you'll need to update your boot blocks to a 946 more modern version, if you haven't already done so. Modern 947 here means 4.0 release or newer (although older releases 948 may work). 949 95020000612: 951 Peter took an axe to config(8). Be sure that you read his mail 952 on the topic before even thinking about updating. You will 953 need to create a /boot/device.hints or add a hints directive 954 to your config file to compile them in statically. The format 955 of the config file has changed as well. Please see GENERIC or 956 NEWCARD for examples of the new format. 957 958 Indirectly, this also breaks USERCONFIG. Unless a newer entry 959 says that it has been fixed, assume that must use the hints mechanism 960 in the loader if you need to use a machine with very old ISA cards 961 in it. 962 96320000522: 964 A new set of binutils went into the tree today. Anybody 965 building a kernel after this point is advised that they need 966 to rebuild their binutils (or better yet do a 967 buildworld/installworld) before building a new kernel. 968 969 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 970 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 971 is recommended that you don't set this option until the problem 972 is resolved. 973 97420000513: 975 The ethernet drivers were all updated to clean up the BPF handling. 976 97720000510: 978 The problems with boot blocks on the alphas have been corrected. 979 This will require some care in updating alphas. A new libstand 980 is requires for the boot blocks to build properly. 981 98220000503: 983 Recompile all kld modules. Proper version dependency info 984 is now available. 985 98620000502: 987 Modules have been disconnected from the buildworld tree and 988 connected to the kernel building instead. 989 99020000427: 991 You may need to build gperf 992 cd /usr/src/gnu/usr.bin/gperf && make depend all install 993 when upgrading from 4.0 -> current. The build system now uses 994 an option only in -current. 995 99620000417: 997 The method that we brand ELF binaries has changed to be more 998 acceptable to the binutils maintainers. You will need to 999 rebrand your ELF binaries that aren't native. One problem 1000 binary is the Linux ldconfig. After your make world, but 1001 before you reboot, you'll need to issue: 1002 brandelf -t Linux /compat/linux/sbin/ldconfig 1003 if you have Linux compatibility enabled on your machine. 1004 100520000320: 1006 If you have really bad/marginal IDE drives, you may find they 1007 don't work well. Use pio mode instead. The easiest way to 1008 cope if you have a problem combination is to add: 1009 /sbin/sysctl hw.ata.ata_dma=0 1010 to the start of /etc/rc.conf. 1011 101220000319: 1013 The ISA and PCI compatibility shims have been connected to the 1014 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1015 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1016 include the appropriate option in your kernel config. Drivers 1017 using the shims should be updated or they won't ship with 1018 5.0-RELEASE, targeted for 2001. 1019 102020000318: 1021 We've entered the traditional post release dumping party. 1022 Large kernel changes are being committed and are in the 1023 works. It is important to keep the systems' klds and kernel 1024 in sync as kernel interfaces and structures are changing. 1025 Before reporting kernel panics, make sure that all modules 1026 that you are loading are up to date. 1027 102820000315: 1029 If you are upgrading from an older version of FreeBSD, you 1030 need to update your boot blocks as well. 'disklabel -B ad0' 1031 will do the trick. This isn't critical until you remove your 1032 wd device entries in /dev, at which point your system will not 1033 boot. 1034 103520000315: 1036 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 1037 to upgrade to 4.0 from 3.x. 1038 1039COMMON ITEMS: 1040 1041 General Notes 1042 ------------- 1043 Avoid using make -j when upgrading. From time to time in the 1044 past there have been problems using -j with buildworld and/or 1045 installworld. This is especially true when upgrading between 1046 "distant" versions (eg one that cross a major release boundary 1047 or several minor releases, or when several months have passed 1048 on the -current branch). 1049 1050 Sometimes, obscure build problems are the result of environment 1051 poisoning. This can happen because the make utility reads its 1052 environment when searching for values for global variables. 1053 To run your build attempts in an "environmental clean room", 1054 prefix all make commands with 'env -i '. See the env(1) manual 1055 page for more details. 1056 1057 To build a kernel 1058 ----------------- 1059 If you are updating from a prior version of FreeBSD (even one just 1060 a few days old), you should follow this procedure. With a 1061 /usr/obj tree with a fresh buildworld, 1062 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1063 make installkernel KERNCONF=YOUR_KERNEL_HERE 1064 1065 To just build a kernel when you know that it won't mess you up 1066 -------------------------------------------------------------- 1067 cd src/sys/{i386,alpha}/conf 1068 config KERNEL_NAME_HERE 1069 cd ../../compile/KERNEL_NAME_HERE 1070 make depend 1071 make 1072 make install 1073 1074 If this fails, go to the "To build a kernel" section. 1075 1076 To rebuild everything and install it on the current system. 1077 ----------------------------------------------------------- 1078 # Note: sometimes if you are running current you gotta do more than 1079 # is listed here if you are upgrading from a really old current. 1080 1081 <make sure you have good level 0 dumps> 1082 <maybe fix /etc/fstab> [7] 1083 make buildworld 1084 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1085 make installkernel KERNCONF=YOUR_KERNEL_HERE 1086 [1] 1087 <reboot in single user> [3] 1088 mergemaster -p [5] 1089 make installworld 1090 mergemaster [4] 1091 <reboot> 1092 1093 1094 To cross-install current onto a separate partition 1095 -------------------------------------------------- 1096 # In this approach we use a separate partition to hold 1097 # current's root, 'usr', and 'var' directories. A partition 1098 # holding "/", "/usr" and "/var" should be about 2GB in 1099 # size. 1100 1101 <make sure you have good level 0 dumps> 1102 <boot into -stable> 1103 make buildworld 1104 <maybe newfs current's root partition> 1105 <mount current's root partition on directory ${CURRENT_ROOT}> 1106 make installworld DESTDIR=${CURRENT_ROOT} 1107 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1108 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1109 ${CURRENT_ROOT}/boot/device.hints # as needed 1110 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1111 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1112 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1113 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1114 <reboot into current> 1115 <do a "native" rebuild/install as described in the previous section> 1116 <maybe install compatibility libraries from /usr/src/lib/compat> 1117 <reboot> 1118 1119 1120 To upgrade in-place from 4.x-stable to current 1121 ---------------------------------------------- 1122 # 5.x uses more space than 4.x. Also, the location of kernel 1123 # modules has changed. If you are installing 5.0 onto a 4.x 1124 # system, you'll need about 30MB of free disk space on your / 1125 # partition. If you have less than this, you may encounter difficult 1126 # to back out of problems with this procedure. If /tmp is on 1127 # the / partition, you may want to completely remove all its content 1128 # before upgrading, as this can be a common source of shortage of 1129 # space on /. 1130 1131 <make sure you have good level 0 dumps> 1132 <maybe fix /etc/fstab> [7] 1133 make buildworld [9] 1134 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1135 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1136 make installkernel KERNCONF=YOUR_KERNEL_HERE 1137 cd src/sys/boot ; make install [6] 1138 [1] 1139 <reboot in single user> [3] 1140 mergemaster -p [5] 1141 rm -rf /usr/include/g++ 1142 make installworld 1143 mergemaster [4] 1144 <reboot> 1145 1146 Make sure that you've read the UPDATING file to understand the 1147 tweaks to various things you need. At this point in the life 1148 cycle of current, things change often and you are on your own 1149 to cope. The defaults can also change, so please read ALL of 1150 the UPDATING entries. 1151 1152 Also, if you are tracking -current, you must be subscribed to 1153 freebsd-current@freebsd.org. Make sure that before you update 1154 your sources that you have read and understood all the recent 1155 messages there. If in doubt, please track -stable which has 1156 much fewer pitfalls. 1157 1158 [1] If you have third party modules, such as vmware, you 1159 should disable them at this point so they don't crash your 1160 system on reboot. 1161 1162 [2] If you have legacy ISA devices, you may need to create 1163 your own device.hints to reflect your unique hardware 1164 configuration. 1165 1166 [3] From the bootblocks, boot -s, and then do 1167 fsck -p 1168 mount -u / 1169 mount -a 1170 cd /usr/src 1171 adjkerntz -i # if CMOS is wall time 1172 Also, when doing a major release upgrade, it is required that 1173 you boot into single user mode to do the installworld. 1174 For the 4.x -> 5.0 upgrade, you will also see many messages about 1175 needing to recompile your userland. These are harmless and can 1176 be ignored while you proceed to the next step. 1177 1178 [4] Note: This step is non-optional. Failure to do this step 1179 can result in a significant reduction in the functionality of the 1180 system. Attempting to do it by hand is not recommended and those 1181 that pursue this avenue should read this file carefully, as well 1182 as the archives of freebsd-current and freebsd-hackers mailing lists 1183 for potential gotchas. 1184 1185 [5] Usually this step is a noop. However, from time to time 1186 you may need to do this if you get unknown user in the following 1187 step. It never hurts to do it all the time. You may need to 1188 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1189 install) after the buildworld before this step if you last updated 1190 from current before 20020224 or from -stable before 20020408. 1191 1192 [6] 4.x boot loader can be used to boot a 5.x system, however 1193 it is difficult to do that at best. If you wish to try, then 1194 you should interrupt the boot and at the ok prompt type: 1195 ok unload 1196 ok boot /boot/kernel/kernel 1197 If this fails to work, you must install a new boot loader as 1198 described here. 1199 1200 [7] Before you upgrade, please make sure that you are not using 1201 compatibility slices. These are device names of the form, on i386 1202 and other architectures that use MBR slicing, /dev/ad0a without the 1203 actual slice name. Chances are excellent that these will break. 1204 You generally must update these entries to use the post FreeBSD 1205 2.x form of /dev/ad0s1a. 1206 1207 [8] In order to have a kernel that can run the 4.x binaries 1208 needed to do an installworld, you must include the COMPAT_FREEBSD4 1209 option in your kernel. Failure to do so may leave you with a system 1210 that is hard to boot to recover. 1211 1212 [9] When checking out sources, you must include the -P flag to have 1213 cvs prune empty directories. 1214FORMAT: 1215 1216This file contains a list, in reverse chronological order, of major 1217breakages in tracking -current. Not all things will be listed here, 1218and it only starts on March 15, 2000. Updating files can found in 1219previous releases if your system is older than this. 1220 1221Copyright information: 1222 1223Copyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1224 1225Redistribution, publication, translation and use, with or without 1226modification, in full or in part, in any form or format of this 1227document are permitted without further permission from the author. 1228 1229THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1230IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1231WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1232DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1233INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1234(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1235SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1236HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1237STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1238IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1239POSSIBILITY OF SUCH DAMAGE. 1240 1241If you find this document useful, and you want to, you may buy the 1242author a beer. 1243 1244Contact Warner Losh if you have any questions about your use of 1245this document. 1246 1247$FreeBSD: head/UPDATING 113999 2003-04-25 02:10:17Z imp $ 1248