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