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