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