UPDATING revision 109866
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 2020030125: 21 The scheduler framework has grown a second scheduler and consequently 22 you must specify one and only one scheduler in your kernel config. 23 The in cvs config files have been updated to use the old scheduler 24 which may be selected via 'options SCHED_4BSD'. If you would like 25 to try the new, much more experimental, scheduler please try 26 'options SCHED_ULE' and contribute to the arch@ discussion. 27 2820030115: 29 A new version of the wi driver has been imported into the tree. 30 One now must have device wlan in the config file for it to operate 31 properly. 32 33 In addition, there have been some changes to how wi devices are 34 configured for point to point links to bring it more in line 35 with the former way of doing things, as well as compatibility 36 with NetBSD. 37 3820021222: 39 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 40 used an incompatible form of ABI for returning structures and unions 41 which FreeBSD's GCC maintainers were not aware of relative to previous 42 versions of FreeBSD. We have gone back to the ABI for now, and any 43 code compiled which is required to interoperate with other code (not 44 built at the same time) returning structs or unions should be 45 rebuilt. 46 4720021216: 48 A name change in /etc/netconfig has been reverted to stay 49 compatible with with suns TIRPC and also with NetBSD. You need 50 to run mergemaster after make world. A new libc does still work 51 with an outdated /etc/netconfig for some time, but you'll get 52 a warning. This warning will be removed in 20030301. 53 5420021202: 55 The recent binutils upgrade marks a kernel flag day on 56 sparc64: modules built with the old binutils will not work 57 with new kernels and vice versa. Mismatches will result in 58 panics. Make sure your kernel and modules are in sync. 59 6020021029: 61 The value of IPPROTO_DIVERT has changed. Make sure to keep 62 your kernel, netstat, natd and any third-party DIVERT 63 consumers in sync. 64 6520021024: 66 Old, compatibility slices have been removed in GEOM kernels. This 67 means that you will have to update your /etc/fstab to not use 68 disk devices of the form /dev/ad0a. Instead, you now must 69 specify /dev/ad0s1a, or whatever slice your FreeBSD partition 70 really is on. The old device names have gone away, so if you 71 use them anywhere else, you must also adjust those uses. 72 7320021023: 74 Alphas with kernels from between 20020830 and 20021023 and/or 75 rtld (ld-elf.so.1) older than 20021023 may experience problems 76 with groff while doing a buildworld (kernel: "out of memory", 77 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 78 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 79 80 So, to successfully upgrade your Alpha, you must either 81 upgrade your kernel and rtld first (which might be a bit 82 tricky), or avoid running the bootstrapped groff during the 83 "transitional" buildworld. To avoid running groff during the 84 transitional upgrade run make buildworld with -DNOMAN, 85 -DNO_SHAREDOCS, and -DNO_LPR. 86 8720020831: 88 gcc has been upgraded to 3.2. It is not all binary compatible 89 with earlier versions of gcc for c++ programs. All c++ 90 programs and libraries need to be recompiled. 91 92 Also, if you encounter g++ issues, rm /usr/include/g++/* before 93 doing an installworld to make sure that stale files are removed. 94 9520020827: 96 Our /etc/termcap now has all the entries from the XFree86 xterm 97 almost unchanged. This means xterm now supports color by default. 98 If you used TERM=xterm-color in the past you now should use 99 TERM=xterm. (xterm-color will lead to benign warnings). 100 10120020815: 102 A "bug" in gcc(1) that was hiding warning in system headers was 103 fixed. It's probably time to add -DNO_WERROR to your make line 104 again. 105 10620020729: 107 COPY is being deprecated. The 20010530 change was reverted, as 108 it causes far more pain than was expected, and to always compare 109 before installing, please use INSTALL="install -C" again. The 110 -C option is now silently ignored when used with the -d option. 111 11220020702: 113 Problems with libc_r clients like KDE and GNOME have been resolved. 114 There are still some minor problems with some signals but the 115 system is stable enough for general use again. SMP is less so than UP 116 but each can successfully complete multiple buildworlds. 117 Libkvm needs to be recompiled due to KSE. 118 11920020701: 120 Now would be a bad time to upgrade. Something in or near the 121 KSE commit totally broke programs using libc_r like KDE and 122 GNOME. 123 12420020511: 125 The k5su utility installed as part of Kerberos 5 is no longer 126 installed with the set-user-ID bit set by default. Add 127 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 128 with the set-user-ID bit set. 129 13020020510: 131 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 132 Unfortunately our native GDB (at version 4.18) does not understand 133 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 134 generated debugging information for our native GDB. 135 13620020510: 137 Due to the way CVS works, it may not properly update src/contrib/gcc 138 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 139 and then do a cvs update. 140 14120020421: 142 When exec'ing set[ug]id executables, the kernel now ensures that the 143 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 144 14520020404: 146 New sendmail startup scripts have been installed to make it 147 easier to use alternative MTAs with FreeBSD. Setting the rc.conf 148 variable sendmail_enable to "NO" no longer prevents any sendmail 149 daemons from starting. Instead, either set sendmail_enable to 150 "NONE" or change mta_start_script to a script for starting 151 an alternative MTA. Setting mta_start_script to "" will 152 also prevent any MTA from being started at boot. 153 15420020403: 155 UCONSOLE is no longer a valid kernel option. 156 15720020315: 158 FreeBSD 5.0 DP-1 was basically branched today. 159 16020020225: 161 Warnings are now errors in the kernel. Unless you are a developer, 162 you should add -DNO_WERROR to your make line. 163 16420020217: 165 sendmail 8.12.2 has been imported. The sendmail binary is no 166 longer a set-user-ID root binary and the infrastructure to support 167 command line mail submission has changed. Be sure to run 168 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 169 and /etc/mail) and read /etc/mail/README for more details. 170 171 Due to the import of sendmail 8.12.2, a new user and group are 172 required in order for sendmail to run as a set-group-ID 173 binary. A 'make installworld' will use the new user and group 174 to set the owner and group of /var/spool/clientmqueue and will 175 fail if the new user and group do not exist. The 'smmsp' user 176 and group must be merged from src/etc/group and 177 src/etc/master.passwd before using 'make installworld'. 178 'mergemaster -p' will do this. You may need to install 179 mergemaster before this will work if you are updating from a 180 very old version of current. The updating recipe has changed 181 as of this date. 182 18320020112: 184 The preferred configuration method for PAM is now /etc/pam.d/ 185 rather than /etc/pam.conf. If you have an unmodified 186 pam.conf, just delete it after your next mergemaster run. If 187 you have local modifications, you can use 188 /usr/src/etc/pam.d/convert.pl to incorporate them into your 189 /etc/pam.d. 190 191 Please see the following url for more details: 192http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 19320011229: 194 If anyone here is already using the new rc.conf(5) variable 195 networkfs_types, please note that it has changed 196http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 197 19820011220: 199 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 200 started out its life in the ISDN4BSD project as an offspring 201 from sys/net/if_spppsubr.c, which eventually got a life of its 202 own. All the accumulated features and bugfixes of the i4b 203 version have now been merged back into the base system's 204 version now. The only user-visible change resulting from this 205 is that i4b's sppp(4) interfaces are to be managed with 206 spppcontrol(8) again, since ispppcontrol(8) has been retired 207 as well. (There has never been rc file support for 208 ispppcontrol in -current, but only in -stable. That will be 209 reverted by the time the changes are MFCed.) 210 21120011215: 212 The fdc(4) driver has been updated and now automatically 213 recognizes media in `standard' formats (like 1440 KB and 214 720 KB for a 3.5" high-density drive) when accessing the 215 default device node (e. g. /dev/fd0). The old variety of 216 floppy device nodes /dev/fd*.* is no longer present by 217 default, devices can be created (in DEVFS) on demand. They 218 will need to be customized then for `odd' densities using 219 fdcontrol(8). 220 22120011209: 222 The bugs in procfs' debugging support code have been fixed, 223 and truss(1) now works again. 224 22520011207: 226 Daily security checks have been split out to use the periodic(8) 227 scripts. Some change in configuration may be necessary. Please 228 see 229http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 230 for details. 231 23220011204: 233 sos added VCD/SVCD support to ata driver and that needs the 234 kernel and burncd to be in sync. 235 23620011203: 237 The procfs pseudo-filesystem has now been converted to use the 238 pseudofs framework. If you have 'options PROCFS' in your 239 kernel config, you'll need to add 'options PSEUDOFS' if it's 240 not there already. 241 242 This change temporarily breaks truss(1); use ktrace(1) instead 243 until the issue has been resolved. 244 24520011202: 246 A security hole in OpenSSH involving `UseLogin yes' has been 247 patched. 248 24920011126: 250 You need to remove /usr/obj/.../usr.bin/tip before rebuilding 251 after this date. You need to do this only once. 252 25320011103: 254 Most of the awk issues have been resolved. Some rough 255 edges may be left, but for the most part things should be 256 back to "normal." For CURRENT's usual definition of "normal." 257 25820011030: 259 Awk has been upgraded to the one true awk from bell labs. Expect 260 choppy waves in the upgrade process. 261 26220011030: 263 The asr driver problem has been resolved. 264 26520011027: 266 Due to changes in other parts of the system, the asr driver 267 now causes the system to panic on boot. Do not use it pending 268 correction. Comment it out of any kernel config file that you 269 try to use from this date forward. 270 27120011025: 272 When crossbuilding, use TARGET=xxx where you used to use 273 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 274 unless you are changing both of them. To cross build pc98 on 275 an alpha, for example, you need to set TARGET=pc98 and 276 TARGET_ARCH=i386. 277 27820011001: 279 The kernel interface that burncd depends on has changed. 280 You must recompile both the kernel and userland applications 281 at the same time. 282 28320010929: 284 When crossbuilding, please set TARGET_ARCH rather than 285 MACHINE_ARCH to indicate the target. In the future, one will 286 set TARGET_MACHINE where you set MACHINE now. At the moment, 287 setting MACHINE alone for same MACHINE_ARCH machines works 288 (eg, you can build pc98 on an i386 machine and vice versa). 289 29020010927: 291 Some weird problems result from using ACPI on some machines. 292 To disable ACPI you can add 293 hint.acpi.0.disable="1" 294 to /boot/loader.conf (or by putting set X=Y at the boot 295 loader "ok" prompt). 296 297 Alternatively, you can remove it from /boot/kernel/acpi.ko 298 or use the MODULES_OVERRIDE function in your kernel config 299 file and not list acpi in that list. 300 30120010924: 302 The buildworld has been fixed. You may need to install 303 the 4.x compatibility libraries for some old binaries 304 to work. Add COMPAT4X=true to your /etc/make.conf to 305 get them installed on every installworld, or execute the 306 following to get them installed only once: 307 cd src/lib/compat/compat4x.<arch> 308 make all install 309 You will see ``__stdoutp undefined'' until you do this. 310 31120010919: 312 There's a bug in the world build process. The cross-tools 313 are build with the NEW headers, but the OLD libc.a. This 314 leads to all kinds of problems with the new libc. A temporary 315 workaround is to add 316 CFLAGS="-O -pipe -D_OLD_STDIO" 317 before building world when upgrading from 4.x to current. This 318 can be removed afterwards. 319 320 A proper fix to the buildworld target is needed. 321 32220010918: 323 Peter has committed his new kthread nfs client/server code. 324 NFS may be unstable after this date. 325 32620010912: 327 KSE has hit the tree. Lots of things are now different in 328 the kernel. While a few problems were introduced in the 329 initial commit, most of the major ones have been found and 330 corrected. 331 33220010901: 333 In OLDCARD, CardBus bridges appear to be stable. The work 334 arounds described in the 20010604 entry are now no longer 335 necessary and will be ignored. Most insert/remove problems 336 have been rectified around this date. 337 33820010823: 339 named now runs as user bind and group bind rather than as 340 root. If named_enable is set to YES in /etc/rc.conf, ensure 341 that user bind is available in /etc/passwd (using vipw(8)) 342 and that group bind is available in /etc/group. Also make 343 sure that user or group bind has read (and not write) 344 permission for your name server configuration and that it 345 has read and write permission for your slave zone files and 346 directory. 347 348 If you wish to continue to run named as root (a less secure 349 alternative), add a line to /etc/rc.conf saying 350 351 named_flags= 352 35320010709: 354 The PAM libraries have had an API upgrade that is beyond 355 the ability of the shared library major number to handle. 356 It is manifested by PAM-using ports dumping core. The 357 solution is to rebuild those ports. 358 35920010628: 360 The kernel compile module has moved from src/sys/compile/FOO 361 to src/sys/${MACHINE}/compile/FOO. 362 36320010625: 364 The pccard modem issue from 20010613 has been corrected. 365 OLDCARD support is still a little weak in -current. slot 1 is 366 known not to work on some TI based cardbus bridges. Some 367 cardbus bridges do not properly detect insert/removal events. 368 IRQ configuration needs more safety belts. 369 37020010617: 371 Softupdates problems have been corrected. 372 37320010614: 374 Peter ripped out the linkerset support. You must, as always, 375 rerun config after you cvsup if you are using the traditional 376 kernel building methods. 377 37820010613: 379 pccard modems may not work with current after 20010604 date. Some 380 do, others result in panics. *MAKE*SURE* that you update your 381 config and /etc/rc.conf ala the 20010604 entry, or you will have 382 problems (this issue will be fixed, it just hasn't been yet). 383 38420010613: 385 SOFTUPDATES seem to be broken since the middle of May or so. Do not 386 use them in current. You can disable softupdates on all mounted 387 partitions, or remove SOFTUPDATES the kernel config file. 388 38920010612: 390 After Peter's commits to the hints code, people have been noticing 391 that certain devices are attached (or try to) twice. This is due 392 to having both static hints as well as a /boot/device.hints. To 393 work around this issue, please use only one or the other mechanism 394 until this bug is fixed. 395 396 Please note that a feature of config is that if you have config 397 file FOO and FOO.hints, it automatically adds FOO.hints to the 398 hints.c file, wheather you want it to or not. 399 40020010610: 401 Locale names have changed to match other systems better. 402 40320010604: 404 pccard support for pci cards has been committed. You must change 405 your /etc/pccard.conf irq lines. It must match the irq used by 406 pcic device. Interrupt storms may result if you fail to do this. 407 Interrupt storms look a lot like a hang. 408 409 You must also install a new pccardd, otherwise you will get an 410 interrupt storm at card reset time (just after it tells you what 411 it is). 412 413 pccardd_flags="-I" is necessary for the time being. It tells pccardd 414 not to ask the kernel if the interrupt is really free or not before 415 using it. You can either change the /etc/pccard.conf irq lines to 416 match pcic, or add "-i X" to the pccardd_flags. 417 41820010530: 419 INSTALL=install -C is being deprecated. If you want to do this, 420 use COPY=-C instead. The former method will be supported for only 421 a limited time. If you see 422 423install: warning: the -d and -C options may not be specified together 424 425 in your makeworld, then you need to migrate towards using 426 COPY=-C. 427 42820010525: 429 It appears that vm is now stable enough to use again. However, 430 there may be other problems, so caution is still urged. alpha 431 definitely is in bad shape. 432 43320010521: 434 Minor repo damange has happened. This may cause problems 435 with cvsup of ports. If you get errors, please see 436 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 437 at the bottom for details on a workaround. The error message 438 is 439Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 440 44120010520: 442 Vm and/or swapping are busted on -current. Please be patient. 443 44420010519: 445 pccard has had much reorganizational work done to it over 446 the past few days. Everything should still work, but if 447 not, please contact imp@freebsd.org. 448 44920010517: 450 ata ioctl changed. Make sure to recompile both kernel and 451 userland at the same time. 452 45320010517: 454 New ncurses imported. 455 45620010512: 457 DEVFS is now opt out, not opt in. Barring major problems, this 458 will be the only way to go starting July 1. 459 46020010504: 461 OpenSSH has been updated to 2.9. Some defaults are different, 462 including RhostsRSAAuthentication, which changes from yes to no. 463 46420010502: 465 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 466 46720010501: 468 Building perl was broken at 02:25:25 PDT. 469 47020010430: 471 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 472 go back in the water. 473 47420010429: 475 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 476 this date, but before the correction date. 477 47820010423: 479 old fsck and new kernel interactions appear to have been fixed. 480 48120010411: 482 fsck and the kernel were changed to handle some optimizations 483 to directory layout. This breaks backward compatibility. 484 Update only if you understand that you must not use the old 485 fsck with the new kernel ever. 486 48720010330: 488 fsck has changed the meaning of the pass column in /etc/fstab. 489 Please see the cvs commit to fsck.8 or the fsck.8 man page for 490 details. It is unclear if changes to /etc/fstab are necessary. 491 49220010319: 493 portmap had changed name to rpcbind for maximum POLA in your 494 current world. /etc/hosts.{allow,deny} needs changes. nfs and 495 other rpc based programs that rely on portmapper will not work 496 without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 497 49820010315: 499 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 500 and ATA_ENABEL_TAGS are no longer kernel options. They have 501 been replaced by tunables. See ata.4 for details. 502 50320010312: 504 The fxp driver was converted to use miibus. If you compile 505 fxp into your kernel statically, you will need to add miibus. 506 50720010312: 508 The wi device now defaults to BSS (infrastructure) mode 509 instead of ad-hoc. 510 51120010310: 512 /dev/urandom should be a symbolic link to /dev/random now. 513 Users of current not using DEVFS need to run MAKEDEV std. 514 ssh might not work if you don't. 515 51620010303: 517 The ed driver has been updated. It now allows mii attachments, 518 which means that you must include the miibus in your kernel if 519 you use the ed driver. 520 52120010220: 522 The problems with libc have been corrected. It is now mostly 523 safe to go back into the water. 524 52520010211: 526 The size of FILE was changed. This breaks upgrading. If 527 you must upgrade, be prepared for pain. It also breaks almost 528 all binaries that you've compiled on -current. You are warned 529 that before upgrading would be a good time to do a level 0 530 dump of your system. No, really, I mean it this time. 531 532 To get to the new system, you'll need to use the following 533 workaround. Hopefully this can be sorted out so that we 534 don't have to move this to the updating section. 535 536 To get around the installworld problem, do: 537 # cd /usr/src/usr.bin/sed 538 # make install 539 # cd /usr/src 540 # make installworld 541 If that doesn't work, then try: 542 # make -k installworld 543 # make installworld 544 54520010207: 546 DEVFS is now the default. If you use vinum, make sure that you 547 do not include devfs in your kernel as problems result. 548 54920010205: 550 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 551 Remove them from your config. 552 55320010122: 554 ****************************** WARNING ****************************** 555 buildkernel has been changed slightly 556 ****************************** WARNING ****************************** 557 KERNCONF replaces the variable KERNEL for buildkernel. You 558 should update your scripts and make.conf accordingly. 559 56020010119: 561 config has changed to allow DEV_FOO as a replacement for NFOO. 562 This requires a new config to build correctly. 563 56420010116: 565 The kerrnel option I386_CPU is now mutually exclusive with the 566 other cpu types. If you have an i386 system, be sure that it 567 only had this line. Remove it for all other configurations. 568 56920010110: 570 Changes to the kernel require it and burncd be in sync. 571 57220010102: 573 Everyone who has hw.sndunit set to something in 574 /etc/sysctl.conf, it is now hw.snd.unit. 575 57620010101: 577 ex and vi were broken by some changes to sys/queue.h. If you 578 have a bad vi, you will see make buildworld fail with a core 579 dump while building termcap. You can work around this problem 580 by adding -k to your make buildworld. This will cause the 581 build to complete and install a new vi. Once that's done, you 582 can rebuild again without the -k to pick up anything that 583 might have been ignored by the -k option. 584 585 Others have suggested that you can just rebuild libc if your 586 vi/ex is dynamically linked, but I've not received any reports 587 of this working. 588 58920001228: 590 There have been some changes to libcrypt in -current. The 591 libscrypt/libdescrypt symlink sillyness is gone and the installed 592 libcrypt is fully functional. Be aware of this. 593 59420001218: 595 Linksys Fast Ethernet PCCARD cards supported by the ed driver 596 now require the addition of flag 0x80000 to their config line 597 in pccard.conf(5). This flag is not optional. These Linksys 598 cards will not be recognized without it. 599 60020001205: 601 Important new FreeBSD-version stuff: PAM support has been worked 602 in, partially from the "Unix" OpenSSH version. This requires 603 adding the following in pam.conf: 604 605 sshd auth sufficient pam_skey.so 606 sshd auth required pam_unix.so try_first_pass 607 sshd session required pam_permit.so 608 60920001031: 610 cvs updated to 1.11. 611 61220001020: 613 The random device needs more entropy, so you need to make sure 614 that you've run mergemaster to get a /etc/rc which will seed 615 /dev/random. If you don't and the system hangs after ldconfig, 616 then banging on the keyboard randomly until it unhangs is one 617 workaround. 618 61920001010: 620 ****************************** WARNING ****************************** 621 Sendmail has been updated. 622 ****************************** WARNING ****************************** 623 o mail.local(8) is no longer installed as a set-user-id binary. 624 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 625 is set. 626 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 627 commands. 628 o Now using sendmail's version of vacation(1). 629 o The sendmail cf building tools (contrib/sendmail/cf) are installed 630 in /usr/share/sendmail/cf. 631 o sendmail.cw changed to local-host-names 632 633 More details can be found at 634 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 635 63620001009: 637 The ports tree's new layout is in place. Be sure to update 638 your entire ports tree, or you will have problems. 639 64020001006: 641 The perl build procedure no longer installs miniperl, nor uses 642 the installed miniperl. It is recommended that you delete 643 /usr/bin/miniperl. 644 64520001005: 646 This weekend the ports tree will be updated to a new layout. 647 It will be in an inconsistent state until noted in the UPDATING 648 file, or with asami-san's message to the relevant mailing 649 lists. With this new layout, you'll need to update the whole 650 tree for anything to work. 651 65220000928: 653 There was a change in the passwd format. Need more information. 654 65520000916: 656 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 657 place. Please update boot loader (not the boot blocks) at the 658 same time as your kernel. 659 66020000914: 661 The new pmtimer device is necessary for laptops. Failure to 662 include the device will cause suspended laptops losing time 663 when they resume. Include 664 device pmtimer 665 in your config file and 666 hint.pmtimer.0.at="isa" 667 to your /boot/device.hints file. 668 66920000911: 670 The random device has been turned into a (pseudo-)device, 671 rather than an option. The supplied kernel config files have 672 been updated. You will need to do something similar in your 673 own kernel config file. 674 Remove: 675 options RANDOMDEV 676 Add: 677 device random 678 If you prefer to load the loadable module, you need to do 679 nothing. 680 68120000909: 682 The random device module has been renamed from randomdev.ko to 683 random.ko. You will need to edit your /boot/loader.conf to 684 reflect this if you load this module at boot time. 685 The line should read: 686 random_load="YES" 687 68820000907: 689 The SMPNG commit has happened. It should work, but if it 690 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 691 to be a variety of minor issues. Please see 20000905 to make 692 sure you don't have model loading problems which might at 693 first blush appear related to SMP. 694 69520000906: 696 nsswitch has been imported from NetBSD. Among other things, 697 this means that /etc/host.conf is no longer used. See 698 nsswitch.conf(5) instead. Note that at boot time rc.network 699 will attempt to produce a new nsswitch.conf file for you if you 700 don't have one, and you have host.conf. 701 70220000905: 703 The ucred structure changed size. This breaks the interface 704 that mountd uses. Trying to use an older mountd with a newer 705 kernel guarantees a panic. This means that you need to use 706 kernels newer than today only with matching mountd, but you 707 needed to do that anyway with the boot loader changes. 708 70920000905: 710 The boot loader has been updated. The new default kernel is 711 now /boot/kernel/kernel.ko. The new default module location 712 is /boot/kernel. 713 714 You *MUST* upgrade your boot loader and kernel at the same time. 715 The easiest way to do this is to do the buildworld/buildkernel/ 716 installkernel/installworld dance. 717 718 Furthermore, you are urged to delete your old /modules directory 719 before booting the new kernel, since kldload will find stale 720 modules in that directory instead of finding them in the correct 721 path, /boot/kernel. The most common complaint that this cures 722 is that the linux module crashes your machine after the update. 723 724 if [ ! -d /boot/kernel.old ]; then 725 mv /modules.old /boot/kernel.old 726 chflags noschg /kernel.old 727 mv /kernel.old /boot/kernel.old/kernel.ko 728 chflags schg /boot/kernel.old/kernel.ko 729 fi 730 73120000904: 732 A new issue with the sendmail upgrade has come to light. 733 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 734 incorrectly install the default aliases in /etc/mail rather than 735 move the old one from /etc. So you'll need to manually move the 736 file, create a symbolic link, remove the old /etc/aliases.db and 737 run newaliases. For safety sake, you should stop sendmail 738 while doing this and run the upgrade when locally sourced email 739 is not likely to be generated. 740 74120000825: 742 /boot/device.hints is now required for installkernel to 743 succeed. You should copy GENERIC.hints for your architecture 744 into /boot/device.hints. If and only if you compile hints 745 into your kernel, then this file may be empty. Please note, 746 if you have an empty or missing /boot/device.hints file and 747 you neglected to compile hints into your kernel, no boot 748 messages will appear after the boot loader tries to start the 749 kernel. 750 75120000821: 752 If you do NOT have ``options RANDOMDEV'' in your kernel and 753 you DO want the random device then add randomdev_load="YES" to 754 /boot/loader.conf. 755 75620000812: 757 suidperl is now always built and installed on the system, but 758 with permissions of 511. If you have applications that use 759 this program, you are now required to add ENABLE_SUIDPERL=true 760 to /etc/make.conf. If you forget to do this, 761 chmod 4511 /usr/bin/suidperl 762 will fix this until the next build. 763 76420000812: 765 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 766 visible changes that may immediately affect your configuration 767 include: 768 - New default file locations from src/contrib/sendmail/cf/README 769 - newaliases limited to root and trusted users 770 - MSA port (587) turned on by default 771 - New queue file naming system so can't go from 8.11 -> 8.9 772 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 773 - FEATURE(`nullclient') is more full featured 774 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 775 - mail.local FreeBSD-only -b option changed to -B 776 - See src/contrib/sendmail/RELEASE_NOTES for more info 777 77820000810: 779 suidperl (aka sperl) is no longer build by default. You must 780 specifically define BUILD_SUIDPERL to "true" for it to be build. 781 Furthermore, we recommend that you remove /usr/bin/sperl* and 782 /usr/bin/suidperl files from your system unless you have a 783 specific use for it. 784 78520000729: 786 Networking defaults have been tightened. Anybody upgrading 787 /etc/defaults/rc.conf needs to add the following lines to 788 /etc/rc.conf if they want to have the same setup 789 afterwards (unless the variables already are set, of course): 790 # Enable network daemons for user convenience. 791 inetd_enable="YES" 792 portmap_enable="YES" 793 sendmail_enable="YES" 794 79520000728: 796 If you have null_load="YES" in your /boot/loader.conf, you 797 will need to change that to nullfs_load="YES". 798 79920000728: 800 The "installkernel" target has changed slightly. Now even if 801 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 802 it will install the MYKERNEL file (built with the buildkernel 803 target) as /kernel rather than /MYKERNEL. Those who have 804 updated their /boot/loader.conf files to point to /MYKERNEL 805 should remove that entry or perform manual rename of /kernel 806 to /MYKERNEL. 807 80820000711: 809 If you use CVSUP or CTM to get CVS trees, AND you used to get 810 the old crypto files from internat.freebsd.org AND you check 811 out files from the CVS tree with the cvs command, please read 812 http://people.freebsd.org/~imp/internat.txt 813 for details on potential problems that you might have and how 814 to get around them. 815 816 If you are merely a mirror, or don't answer yes to each of the 817 clauses above, you needn't worry. 818 81920000711: 820 /etc/security has been updated to print the inode number of 821 setuid programs that have changed. You will see a large spike 822 in the number of changed programs the first time when you run 823 mergemaster to get a new /etc/security. 824 82520000710: 826 /dev/random now has good entropy collection (from the keyboard 827 and sysmouse drivers). Please ensure that either `options 828 RANDOMDEV' is present in your kernel config file or that 829 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 830 not have the /dev/random driver, OpenSSL (and consequently 831 lots of crypto tools (like SSH)) will fail with strange 832 errors. (see below, 20000624). 833 834 FreeBSD-current is safe again to run Crypto. 835 83620000709: 837 phk made the malloc default options AJ. This may slow things 838 down and uncover other latent bugs in the code. If you need to 839 run at full speed, you can disable this by doing the following: 840 ln -s aj /etc/malloc.conf 841 84220000706: 843 libftpio's version was accidentally bumped a few days ago. This 844 has been corrected. You may need to remove /usr/lib/libftpio.so.6 845 before doing your next buildworld/installworld pair. It certainly 846 won't hurt to remove it before the update procedure. It will 847 break fetch until a new one is built, but ftp can be used in the 848 interim if needed. 849 85020000705: 851 The crypto packages have changed for the cvsup. This has been done 852 in a backward compatible way, but the old packages will go away at 853 some point in the future. Look at /usr/share/examples/cvsup for 854 details. 855 85620000704: 857 With the new sys/modules/sound/drivers/*, you will need to 858 set SYSDIR until you do an installworld after July 7th. 859 86020000704: 861 rc.shutdown and rc will now call the rc.d scripts with start 862 or stop. This may cause some harmless warnings from older 863 rc.d scripts that haven't been updated. 864 86520000630: 866 The libfetch based version of fetch has gone into the tree. 867 Minor problems may result on some of the less popular sites, 868 which should be reported to des@freebsd.org. 869 87020000625: 871 From approximately this date forward, one must have the crypto 872 system installed in order to build the system and kernel. 873 While not technically strictly true, one should treat it as 874 required and grab the crypto bits. If you are grabbing CVS 875 trees, src-all and cvs-crypto should be treated as if they 876 were required. You should check with the latest collections 877 to make sure that these haven't changed. 878 87920000624: 880 Mark Murray just committed the first parts of a cleanup of 881 /dev/zero, et al. This is also cleaning up /dev/random. 882 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 883 -CURRENT FROM THIS POINT to 2000710 for cryptographic services 884 until Mark can merge in the fixes to this work in progress. 885 openssh and openssl should not be used to generate keys from this 886 date to the completion of the work. 887 888 If you must operate at this reduced level of security, add ' 889 options RANDOMDEV' to your kernel or modload the randomdev 890 module. You may also need to copy a new MAKEDEV to /dev and 891 recreate the random and urandom devices. 892 89320000622: 894 The license on the softupdates is now a standard 2 clause 895 BSD license. You may need to remove your symbolic links 896 that used to be required when updating. 897 89820000621: 899 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 900 the config file update procedure. 901 http://people.freebsd.org/~imp/config-upd.html 902 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 903 isn't buildable. However, you can generate a LINT file. 904 90520000620: 906 Binutils 2.10 have hit the tree, or will shortly. As soon 907 as they do, the problem noted in 20000522 will be resolved and 908 that workaround will no longer be required. 909 91020000615: 911 phk removed the compatibility creation of wd devices in the 912 ad driver. If you haven't done so already, you must update 913 your fstab, etc to use the ad devices instead of the wd 914 devices. 915 916 In addition, you'll need to update your boot blocks to a 917 more modern version, if you haven't already done so. Modern 918 here means 4.0 release or newer (although older releases 919 may work). 920 92120000612: 922 Peter took an axe to config(8). Be sure that you read his mail 923 on the topic before even thinking about updating. You will 924 need to create a /boot/device.hints or add a hints directive 925 to your config file to compile them in statically. The format 926 of the config file has changed as well. Please see GENERIC or 927 NEWCARD for examples of the new format. 928 929 Indirectly, this also breaks USERCONFIG. Unless a newer entry 930 says that it has been fixed, assume that must use the hints mechanism 931 in the loader if you need to use a machine with very old ISA cards 932 in it. 933 93420000522: 935 A new set of binutils went into the tree today. Anybody 936 building a kernel after this point is advised that they need 937 to rebuild their binutils (or better yet do a 938 buildworld/installworld) before building a new kernel. 939 940 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 941 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 942 is recommended that you don't set this option until the problem 943 is resolved. 944 94520000513: 946 The ethernet drivers were all updated to clean up the BPF handling. 947 94820000510: 949 The problems with boot blocks on the alphas have been corrected. 950 This will require some care in updating alphas. A new libstand 951 is requires for the boot blocks to build properly. 952 95320000503: 954 Recompile all kld modules. Proper version dependency info 955 is now available. 956 95720000502: 958 Modules have been disconnected from the buildworld tree and 959 connected to the kernel building instead. 960 96120000427: 962 You may need to build gperf 963 cd /usr/src/gnu/usr.bin/gperf && make depend all install 964 when upgrading from 4.0 -> current. The build system now uses 965 an option only in -current. 966 96720000417: 968 The method that we brand ELF binaries has changed to be more 969 acceptable to the binutils maintainers. You will need to 970 rebrand your ELF binaries that aren't native. One problem 971 binary is the Linux ldconfig. After your make world, but 972 before you reboot, you'll need to issue: 973 brandelf -t Linux /compat/linux/sbin/ldconfig 974 if you have Linux compatibility enabled on your machine. 975 97620000320: 977 If you have really bad/marginal IDE drives, you may find they 978 don't work well. Use pio mode instead. The easiest way to 979 cope if you have a problem combination is to add: 980 /sbin/sysctl hw.ata.ata_dma=0 981 to the start of /etc/rc.conf. 982 98320000319: 984 The ISA and PCI compatibility shims have been connected to the 985 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 986 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 987 include the appropriate option in your kernel config. Drivers 988 using the shims should be updated or they won't ship with 989 5.0-RELEASE, targeted for 2001. 990 99120000318: 992 We've entered the traditional post release dumping party. 993 Large kernel changes are being committed and are in the 994 works. It is important to keep the systems' klds and kernel 995 in sync as kernel interfaces and structures are changing. 996 Before reporting kernel panics, make sure that all modules 997 that you are loading are up to date. 998 99920000315: 1000 If you are upgrading from an older version of FreeBSD, you 1001 need to update your boot blocks as well. 'disklabel -B ad0' 1002 will do the trick. This isn't critical until you remove your 1003 wd device entries in /dev, at which point your system will not 1004 boot. 1005 100620000315: 1007 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 1008 to upgrade to 4.0 from 3.x. 1009 1010COMMON ITEMS: 1011 1012 General Notes 1013 ------------- 1014 Avoid using make -j when upgrading. From time to time in the 1015 past there have been problems using -j with buildworld and/or 1016 installworld. This is especially true when upgrading between 1017 "distant" versions (eg one that cross a major release boundary 1018 or several minor releases, or when several months have passed 1019 on the -current branch). 1020 1021 Sometimes, obscure build problems are the result of environment 1022 poisoning. This can happen because the make utility reads its 1023 environment when searching for values for global variables. 1024 To run your build attempts in an "environmental clean room", 1025 prefix all make commands with 'env -i '. See the env(1) manual 1026 page for more details. 1027 1028 To build a kernel 1029 ----------------- 1030 If you are updating from a prior version of FreeBSD (even one just 1031 a few days old), you should follow this procedure. With a 1032 /usr/obj tree with a fresh buildworld, 1033 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1034 make installkernel KERNCONF=YOUR_KERNEL_HERE 1035 1036 To just build a kernel when you know that it won't mess you up 1037 -------------------------------------------------------------- 1038 cd src/sys/{i386,alpha}/conf 1039 config KERNEL_NAME_HERE 1040 cd ../../compile/KERNEL_NAME_HERE 1041 make depend 1042 make 1043 make install 1044 1045 If this fails, go to the "To build a kernel" section. 1046 1047 To rebuild everything and install it on the current system. 1048 ----------------------------------------------------------- 1049 # Note: sometimes if you are running current you gotta do more than 1050 # is listed here if you are upgrading from a really old current. 1051 1052 <make sure you have good level 0 dumps> 1053 <maybe fix /etc/fstab> [7] 1054 make buildworld 1055 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1056 make installkernel KERNCONF=YOUR_KERNEL_HERE 1057 [1] 1058 <reboot in single user> [3] 1059 mergemaster -p [5] 1060 make installworld 1061 mergemaster [4] 1062 <reboot> 1063 1064 1065 To upgrade from 4.x-stable to current 1066 ------------------------------------- 1067 # 5.x uses more space than 4.x. Also, the location of kernel 1068 # modules has changed. If you are installing 5.0 onto a 4.x 1069 # system, you'll need about 30MB of free disk space on your / 1070 # partition. If you have less than this, you may encounter difficult 1071 # to back out of problems with this proceedure. If /tmp is on 1072 # the / partition, you may want to completely remove all its content 1073 # before upgrading, as this can be a common source of shortage of 1074 # space on /. 1075 1076 <make sure you have good level 0 dumps> 1077 <maybe fix /etc/fstab> [7] 1078 make buildworld [9] 1079 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1080 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1081 make installkernel KERNCONF=YOUR_KERNEL_HERE 1082 cd src/sys/boot ; make install [6] 1083 [1] 1084 <reboot in single user> [3] 1085 mergemaster -p [5] 1086 rm -rf /usr/include/g++ 1087 make installworld 1088 mergemaster [4] 1089 <reboot> 1090 1091 Make sure that you've read the UPDATING file to understand the 1092 tweaks to various things you need. At this point in the life 1093 cycle of current, things change often and you are on your own 1094 to cope. The defaults can also change, so please read ALL of 1095 the UPDATING entries. 1096 1097 Also, if you are tracking -current, you must be subscribed to 1098 freebsd-current@freebsd.org. Make sure that before you update 1099 your sources that you have read and understood all the recent 1100 messages there. If in doubt, please track -stable which has 1101 much fewer pitfalls. 1102 1103 [1] If you have third party modules, such as vmware, you 1104 should disable them at this point so they don't crash your 1105 system on reboot. 1106 1107 [2] If you have legacy ISA devices, you may need to create 1108 your own device.hints to reflect your unique hardware 1109 configuration. 1110 1111 [3] From the bootblocks, boot -s, and then do 1112 fsck -p 1113 mount -u / 1114 mount -a 1115 cd /usr/src 1116 adjkerntz -i # if CMOS is wall time 1117 Also, when doing a major release upgrade, it is required that 1118 you boot into single user mode to do the installworld. 1119 For the 4.x -> 5.0 upgrade, you will also see many messages about 1120 needing to recompile your userland. These are harmless and can 1121 be ignored while you proceed to the next step. 1122 1123 [4] Note: This step is non-optional. Failure to do this step 1124 can result in a significant reduction in the functionality of the 1125 system. Attempting to do it by hand is not recommended and those 1126 that pursue this avenue should read this file carefully, as well 1127 as the archives of freebsd-current and freebsd-hackers mailing lists 1128 for potential gotchas. 1129 1130 [5] Usually this step is a noop. However, from time to time 1131 you may need to do this if you get unknown user in the following 1132 step. It never hurts to do it all the time. You may need to 1133 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1134 install) after the buildworld before this step if you last updated 1135 from current before 20020224 or from -stable before 20020408. 1136 1137 [6] 4.x boot loader can be used to boot a 5.x system, however 1138 it is difficult to do that at best. If you wish to try, then 1139 you should interrupt the boot and at the ok prompt type: 1140 ok unload 1141 ok boot /boot/kernel/kernel 1142 If this fails to work, you must install a new boot loader as 1143 described here. 1144 1145 [7] Before you upgrade, please make sure that you are not using 1146 compatibility slices. These are device names of the form, on i386 1147 and other architectures that use MBR slicing, /dev/ad0a without the 1148 actual slice name. Chances are excellent that these will break. 1149 You generally must update these entries to use the post FreeBSD 1150 2.x form of /dev/ad0s1a. 1151 1152 [8] In order to have a kernel that can run the 4.x binaries 1153 needed to do an installworld, you must include the COMPAT_FREEBSD4 1154 option in your kernel. Failure to do so may leave you with a system 1155 that is hard to boot to recover. 1156 1157 [9] When checking out sources, you must include the -P flag to have 1158 cvs prune empty directories. 1159FORMAT: 1160 1161This file contains a list, in reverse chronological order, of major 1162breakages in tracking -current. Not all things will be listed here, 1163and it only starts on March 15, 2000. Updating files can found in 1164previous releases if your system is older than this. 1165 1166Copyright information: 1167 1168Copyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1169 1170Redistribution, publication, translation and use, with or without 1171modification, in full or in part, in any form or format of this 1172document are permitted without further permission from the author. 1173 1174THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1175IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1176WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1177DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1178INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1179(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1180SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1181HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1182STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1183IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1184POSSIBILITY OF SUCH DAMAGE. 1185 1186If you find this document useful, and you want to, you may buy the 1187author a beer. 1188 1189Contact Warner Losh if you have any questions about your use of 1190this document. 1191 1192$FreeBSD: head/UPDATING 109866 2003-01-26 05:29:48Z jeff $ 1193