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