UPDATING revision 94393
1Updating Information for FreeBSD current users 2 3This file is maintained and copyrighted by M. Warner Losh 4<imp@village.org>. Please send new entries directly to him. See end 5of file for further details. For commonly done items, please see the 6COMMON ITEMS: section later in the file. 7 8NOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW: 9 FreeBSD 5.0-CURRENT has many debugging features turned on, in 10 both the kernel and userland. These features attempt to detect 11 incorrect use of system primitives, and encourage loud failure 12 through extra sanity checking and fail stop semantics. They 13 also substantially impact system performance. If you want to 14 do performance measurement, benchmarking, and optimization, 15 you'll want to turn them off. This includes various WITNESS- 16 related kernel options, INVARIANTS, malloc debugging flags 17 in userland, and various verbose features in the kernel. Many 18 developers choose to disable these features on build machines 19 to maximize performance. 20 21 In addition, IDE write caching is currently disabled by default 22 due to on-going concerns about disk write order and file system 23 integrity. Re-enabling write caching can substantially improve 24 performance. 25 2620020404: 27 New sendmail startup scripts have been installed to make it 28 easier to use alternative MTAs with FreeBSD. Setting the rc.conf 29 variable sendmail_enable to "NO" no longer prevents any sendmail 30 daemons from starting. Instead, either set sendmail_enable to 31 "NONE" or change mta_start_script to a script for starting 32 an alternative MTA. Setting mta_start_script to "" will 33 also prevent any MTA from being started at boot. 34 3520020404: 36 Due to the import of sendmail 8.12.2 (see 20020217 entry), a new 37 user and group are required in order for sendmail to run as a 38 set-group-ID binary. A 'make installworld' will use the new user 39 and group to set the owner and group of /var/spool/clientmqueue 40 and will fail if the new user and group do not exist. The 'smmsp' 41 user and group must be merged from src/etc/group and 42 src/etc/master.passwd before using 'make installworld'. 43 4420020315: 45 FreeBSD 5.0 DP-1 was basically branched today. 46 4720020225: 48 Warnings are now errors in the kernel. Unless you are a developer, 49 you should add -DNO_WERROR to your make line. 50 5120020217: 52 sendmail 8.12.2 has been imported. The sendmail binary is no 53 longer a set-user-ID root binary and the infrastructure to support 54 command line mail submission has changed. Be sure to run 55 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 56 and /etc/mail) and read /etc/mail/README for more details. 57 5820020112: 59 The preferred configuration method for PAM is now /etc/pam.d/ 60 rather than /etc/pam.conf. If you have an unmodified 61 pam.conf, just delete it after your next mergemaster run. If 62 you have local modifications, you can use 63 /usr/src/etc/pam.d/convert.pl to incorporate them into your 64 /etc/pam.d. 65 66 Please see the following url for more details: 67http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 68 6920011229: 70 If anyone here is already using the new rc.conf(5) variable 71 networkfs_types, please note that it has changed 72http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 73 7420011220: 75 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 76 started out its life in the ISDN4BSD project as an offspring 77 from sys/net/if_spppsubr.c, which eventually got a life of its 78 own. All the accumulated features and bugfixes of the i4b 79 version have now been merged back into the base system's 80 version now. The only user-visible change resulting from this 81 is that i4b's sppp(4) interfaces are to be managed with 82 spppcontrol(8) again, since ispppcontrol(8) has been retired 83 as well. (There has never been rc file support for 84 ispppcontrol in -current, but only in -stable. That will be 85 reverted by the time the changes are MFCed.) 86 8720011215: 88 The fdc(4) driver has been updated and now automatically 89 recognizes media in `standard' formats (like 1440 KB and 90 720 KB for a 3.5" high-density drive) when accessing the 91 default device node (e. g. /dev/fd0). The old variety of 92 floppy device nodes /dev/fd*.* is no longer present by 93 default, devices can be created (in DEVFS) on demand. They 94 will need to be customized then for `odd' densities using 95 fdcontrol(8). 96 9720011209: 98 The bugs in procfs' debugging support code have been fixed, 99 and truss(1) now works again. 100 10120011207: 102 Daily security checks have been split out to use the periodic(8) 103 scripts. Some change in configuration may be necessary. Please 104 see 105http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 106 for details. 107 10820011204: 109 sos added VCD/SVCD support to ata driver and that needs the 110 kernel and burncd to be in sync. 111 11220011203: 113 The procfs pseudo-filesystem has now been converted to use the 114 pseudofs framework. If you have 'options PROCFS' in your 115 kernel config, you'll need to add 'options PSEUDOFS' if it's 116 not there already. 117 118 This change temporarily breaks truss(1); use ktrace(1) instead 119 until the issue has been resolved. 120 12120011202: 122 A security hole in OpenSSH involving `UseLogin yes' has been 123 patched. 124 12520011126: 126 You need to remove /usr/obj/.../usr.bin/tip before rebuilding 127 after this date. You need to do this only once. 128 12920011103: 130 Most of the awk issues have been resolved. Some rough 131 edges may be left, but for the most part things should be 132 back to "normal." For CURRENT's usual definition of "normal." 133 13420011030: 135 Awk has been upgraded to the one true awk from bell labs. Expect 136 choppy waves in the upgrade process. 137 13820011030: 139 The asr driver problem has been resolved. 140 14120011027: 142 Due to changes in other parts of the system, the asr driver 143 now causes the system to panic on boot. Do not use it pending 144 correction. Comment it out of any kernel config file that you 145 try to use from this date forward. 146 14720011025: 148 When crossbuilding, use TARGET=xxx where you used to use 149 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 150 unless you are changing both of them. To cross build pc98 on 151 an alpha, for example, you need to set TARGET=pc98 and 152 TARGET_ARCH=i386. 153 15420011001: 155 The kernel interface that burncd depends on has changed. 156 You must recompile both the kernel and userland applications 157 at the same time. 158 15920010929: 160 When crossbuilding, please set TARGET_ARCH rather than 161 MACHINE_ARCH to indicate the target. In the future, one will 162 set TARGET_MACHINE where you set MACHINE now. At the moment, 163 setting MACHINE alone for same MACHINE_ARCH machines works 164 (eg, you can build pc98 on a i386 machine and vice versa). 165 16620010927: 167 Some weird problems result from using ACPI on some machines. 168 To disable ACPI you can add 169 hint.acpi.0.disable="1" 170 to /boot/loader.conf (or by putting set X=Y at the boot 171 loader "ok" prompt). 172 173 Alternatively, you can remove it from /boot/kernel/acpi.ko 174 or use the MODULES_OVERRIDE function in your kernel config 175 file and not list acpi in that list. 176 17720010924: 178 The buildworld has been fixed. You may need to install 179 the 4.x compatibility libraries for some old binaries 180 to work. Add COMPAT4X=true to your /etc/make.conf to 181 get them installed on every installworld, or execute the 182 following to get them installed only once: 183 cd src/lib/compat/compat4x.<arch> 184 make all install 185 You will see ``__stdoutp undefined'' until you do this. 186 18720010919: 188 There's a bug in the world build process. The cross-tools 189 are build with the NEW headers, but the OLD libc.a. This 190 leads to all kinds of problems with the new libc. A temporary 191 workaround is to add 192 CFLAGS="-O -pipe -D_OLD_STDIO" 193 before building world when upgrading from 4.x to current. This 194 can be removed afterwards. 195 196 A proper fix to the buildworld target is needed. 197 19820010918: 199 Peter has committed his new kthread nfs client/server code. 200 NFS may be unstable after this date. 201 20220010912: 203 KSE has hit the tree. Lots of things are now different in 204 the kernel. While a few problems were introduced in the 205 initial commit, most of the major ones have been found and 206 corrected. 207 20820010901: 209 In OLDCARD, CardBus bridges appear to be stable. The work 210 arounds described in the 20010604 entry are now no longer 211 necessary and will be ignored. Most insert/remove problems 212 have been rectified around this date. 213 21420010823: 215 named now runs as user bind and group bind rather than as 216 root. If named_enable is set to YES in /etc/rc.conf, ensure 217 that user bind is available in /etc/passwd (using vipw(8)) 218 and that group bind is available in /etc/group. Also make 219 sure that user or group bind has read (and not write) 220 permission for your name server configuration and that it 221 has read and write permission for your slave zone files and 222 directory. 223 224 If you wish to continue to run named as root (a less secure 225 alternative), add a line to /etc/rc.conf saying 226 227 named_flags= 228 22920010709: 230 The PAM libraries have had an API upgrade that is beyond 231 the ability of the shared library major number to handle. 232 It is manifested by PAM-using ports dumping core. The 233 solution is to rebuild those ports. 234 23520010628: 236 The kernel compile module has moved from src/sys/compile/FOO 237 to src/sys/${MACHINE}/compile/FOO. 238 23920010625: 240 The pccard modem issue from 20010613 has been corrected. 241 OLDCARD support is still a little weak in -current. slot 1 is 242 known not to work on some TI based cardbus bridges. Some 243 cardbus bridges do not properly detect insert/removal events. 244 IRQ configuration needs more safety belts. 245 24620010617: 247 Softupdates problems have been corrected. 248 24920010614: 250 Peter ripped out the linkerset support. You must, as always, 251 rerun config after you cvsup if you are using the traditional 252 kernel building methods. 253 25420010613: 255 pccard modems may not work with current after 20010604 date. Some 256 do, others result in panics. *MAKE*SURE* that you update your 257 config and /etc/rc.conf ala the 20010604 entry, or you will have 258 problems (this issue will be fixed, it just hasn't been yet). 259 26020010613: 261 SOFTUPDATES seem to be broken since the middle of May or so. Do not 262 use them in current. You can disable softupdates on all mounted 263 partitions, or remove SOFTUPDATES the kernel config file. 264 26520010612: 266 After Peter's commits to the hints code, people have been noticing 267 that certain devices are attached (or try to) twice. This is due 268 to having both static hints as well as a /boot/device.hints. To 269 work around this issue, please use only one or the other mechanism 270 until this bug is fixed. 271 272 Please note that a feature of config is that if you have config 273 file FOO and FOO.hints, it automatically adds FOO.hints to the 274 hints.c file, wheather you want it to or not. 275 27620010610: 277 Locale names have changed to match other systems better. 278 27920010604: 280 pccard support for pci cards has been committed. You must change 281 your /etc/pccard.conf irq lines. It must match the irq used by 282 pcic device. Interrupt storms may result if you fail to do this. 283 Interrupt storms look a lot like a hang. 284 285 You must also install a new pccardd, otherwise you will get an 286 interrupt storm at card reset time (just after it tells you what 287 it is). 288 289 pccardd_flags="-I" is necessary for the time being. It tells pccardd 290 not to ask the kernel if the interrupt is really free or not before 291 using it. You can either change the /etc/pccard.conf irq lines to 292 match pcic, or add "-i X" to the pccardd_flags. 293 29420010530: 295 INSTALL=install -C is being deprecated. If you want to do this, 296 use COPY=-C instead. The former method will be supported for only 297 a limited time. If you see 298 299install: warning: the -d and -C options may not be specified together 300 301 in your makeworld, then you need to migrate towards using 302 COPY=-C. 303 30420010525: 305 It appears that vm is now stable enough to use again. However, 306 there may be other problems, so caution is still urged. alpha 307 definitely is in bad shape. 308 30920010521: 310 Minor repo damange has happened. This may cause problems 311 with cvsup of ports. If you get errors, please see 312 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 313 at the bottom for details on a workaround. The error message 314 is 315Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 316 31720010520: 318 Vm and/or swapping are busted on -current. Please be patient. 319 32020010519: 321 pccard has had much reorganizational work done to it over 322 the past few days. Everything should still work, but if 323 not, please contact imp@freebsd.org. 324 32520010517: 326 ata ioctl changed. Make sure to recompile both kernel and 327 userland at the same time. 328 32920010517: 330 New ncurses imported. 331 33220010512: 333 DEVFS is now opt out, not opt in. Barring major problems, this 334 will be the only way to go starting July 1. 335 33620010504: 337 OpenSSH has been updated to 2.9. Some defaults are different, 338 including RhostsRSAAuthentication, which changes from yes to no. 339 34020010502: 341 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 342 34320010501: 344 Building perl was broken at 02:25:25 PDT. 345 34620010430: 347 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 348 go back in the water. 349 35020010429: 351 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 352 this date, but before the correction date. 353 35420010423: 355 old fsck and new kernel interactions appear to have been fixed. 356 35720010411: 358 fsck and the kernel were changed to handle some optimizations 359 to directory layout. This breaks backward compatibility. 360 Update only if you understand that you must not use the old 361 fsck with the new kernel ever. 362 36320010330: 364 fsck has changed the meaning of the pass column in /etc/fstab. 365 Please see the cvs commit to fsck.8 or the fsck.8 man page for 366 details. It is unclear if changes to /etc/fstab are necessary. 367 36820010319: 369 portmap had changed name to rpcbind for maximum POLA in your 370 current world. /etc/hosts.{allow,deny} needs changes. nfs and 371 other rpc based programs that rely on portmapper will not work 372 without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 373 37420010315: 375 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 376 and ATA_ENABEL_TAGS are no longer kernel options. They have 377 been replaced by tunables. See ata.4 for details. 378 37920010312: 380 The fxp driver was converted to use miibus. If you compile 381 fxp into your kernel statically, you will need to add miibus. 382 38320010312: 384 The wi device now defaults to BSS (infrastructure) mode 385 instead of ad-hoc. 386 38720010310: 388 /dev/urandom should be a symbolic link to /dev/random now. 389 Users of current not using DEVFS need to run MAKEDEV std. 390 ssh might not work if you don't. 391 39220010303: 393 The ed driver has been updated. It now allows mii attachments, 394 which means that you must include the miibus in your kernel if 395 you use the ed driver. 396 39720010220: 398 The problems with libc have been corrected. It is now mostly 399 safe to go back into the water. 400 40120010211: 402 The size of FILE was changed. This breaks upgrading. If 403 you must upgrade, be prepared for pain. It also breaks almost 404 all binaries that you've compiled on -current. You are warned 405 that before upgrading would be a good time to do a level 0 406 dump of your system. No, really, I mean it this time. 407 408 To get to the new system, you'll need to use the following 409 workaround. Hopefully this can be sorted out so that we 410 don't have to move this to the updating section. 411 412 To get around the installworld problem, do: 413 # cd /usr/src/usr.bin/sed 414 # make install 415 # cd /usr/src 416 # make installworld 417 If that doesn't work, then try: 418 # make -k installworld 419 # make installworld 420 42120010207: 422 DEVFS is now the default. If you use vinum, make sure that you 423 do not include devfs in your kernel as problems result. 424 42520010205: 426 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 427 Remove them from your config. 428 42920010122: 430 ****************************** WARNING ****************************** 431 buildkernel has been changed slightly 432 ****************************** WARNING ****************************** 433 KERNCONF replaces the variable KERNEL for buildkernel. You 434 should update your scripts and make.conf accordingly. 435 43620010119: 437 config has changed to allow DEV_FOO as a replacement for NFOO. 438 This requires a new config to build correctly. 439 44020010116: 441 The kerrnel option I386_CPU is now mutually exclusive with the 442 other cpu types. If you have an i386 system, be sure that it 443 only had this line. Remove it for all other configurations. 444 44520010110: 446 Changes to the kernel require it and burncd be in sync. 447 44820010102: 449 Everyone who has hw.sndunit set to something in 450 /etc/sysctl.conf, it is now hw.snd.unit. 451 45220010101: 453 ex and vi were broken by some changes to sys/queue.h. If you 454 have a bad vi, you will see make buildworld fail with a core 455 dump while building termcap. You can work around this problem 456 by adding -k to your make buildworld. This will cause the 457 build to complete and install a new vi. Once that's done, you 458 can rebuild again without the -k to pick up anything that 459 might have been ignored by the -k option. 460 461 Others have suggested that you can just rebuild libc if your 462 vi/ex is dynamically linked, but I've not received any reports 463 of this working. 464 46520001228: 466 There have been some changes to libcrypt in -current. The 467 libscrypt/libdescrypt symlink sillyness is gone and the installed 468 libcrypt is fully functional. Be aware of this. 469 47020001218: 471 Linksys Fast Ethernet PCCARD cards supported by the ed driver 472 now require the addition of flag 0x80000 to their config line 473 in pccard.conf(5). This flag is not optional. These Linksys 474 cards will not be recognized without it. 475 47620001205: 477 Important new FreeBSD-version stuff: PAM support has been worked 478 in, partially from the "Unix" OpenSSH version. This requires 479 adding the following in pam.conf: 480 481 sshd auth sufficient pam_skey.so 482 sshd auth required pam_unix.so try_first_pass 483 sshd session required pam_permit.so 484 48520001031: 486 cvs updated to 1.11. 487 48820001020: 489 The random device needs more entropy, so you need to make sure 490 that you've run mergemaster to get a /etc/rc which will seed 491 /dev/random. If you don't and the system hangs after ldconfig, 492 then banging on the keyboard randomly until it unhangs is one 493 workaround. 494 49520001010: 496 ****************************** WARNING ****************************** 497 Sendmail has been updated. 498 ****************************** WARNING ****************************** 499 o mail.local(8) is no longer installed as a set-user-id binary. 500 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 501 is set. 502 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 503 commands. 504 o Now using sendmail's version of vacation(1). 505 o The sendmail cf building tools (contrib/sendmail/cf) are installed 506 in /usr/share/sendmail/cf. 507 o sendmail.cw changed to local-host-names 508 509 More details can be found at 510 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 511 51220001009: 513 The ports tree's new layout is in place. Be sure to update 514 your entire ports tree, or you will have problems. 515 51620001006: 517 The perl build procedure no longer installs miniperl, nor uses 518 the installed miniperl. It is recommended that you delete 519 /usr/bin/miniperl. 520 52120001005: 522 This weekend the ports tree will be updated to a new layout. 523 It will be in an inconsistent state until noted in the UPDATING 524 file, or with asami-san's message to the relevant mailing 525 lists. With this new layout, you'll need to update the whole 526 tree for anything to work. 527 52820000928: 529 There was a change in the passwd format. Need more information. 530 53120000916: 532 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 533 place. Please update boot loader (not the boot blocks) at the 534 same time as your kernel. 535 53620000914: 537 The new pmtimer device is necessary for laptops. Failure to 538 include the device will cause suspended laptops losing time 539 when they resume. Include 540 device pmtimer 541 in your config file and 542 hint.pmtimer.0.at="isa" 543 to your /boot/device.hints file. 544 54520000911: 546 The random device has been turned into a (pseudo-)device, 547 rather than an option. The supplied kernel config files have 548 been updated. You will need to do something similar in your 549 own kernel config file. 550 Remove: 551 options RANDOMDEV 552 Add: 553 device random 554 If you prefer to load the loadable module, you need to do 555 nothing. 556 55720000909: 558 The random device module has been renamed from randomdev.ko to 559 random.ko. You will need to edit your /boot/loader.conf to 560 reflect this if you load this module at boot time. 561 The line should read: 562 random_load="YES" 563 56420000907: 565 The SMPNG commit has happened. It should work, but if it 566 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 567 to be a variety of minor issues. Please see 20000905 to make 568 sure you don't have model loading problems which might at 569 first blush appear related to SMP. 570 57120000906: 572 nsswitch has been imported from NetBSD. Among other things, 573 this means that /etc/host.conf is no longer used. See 574 nsswitch.conf(5) instead. Note that at boot time rc.network 575 will attempt to produce a new nsswitch.conf file for you if you 576 don't have one, and you have host.conf. 577 57820000905: 579 The ucred structure changed size. This breaks the interface 580 that mountd uses. Trying to use an older mountd with a newer 581 kernel guarantees a panic. This means that you need to use 582 kernels newer than today only with matching mountd, but you 583 needed to do that anyway with the boot loader changes. 584 58520000905: 586 The boot loader has been updated. The new default kernel is 587 now /boot/kernel/kernel.ko. The new default module location 588 is /boot/kernel. 589 590 You *MUST* upgrade your boot loader and kernel at the same time. 591 The easiest way to do this is to do the buildworld/buildkernel/ 592 installkernel/installworld dance. 593 594 Furthermore, you are urged to delete your old /modules directory 595 before booting the new kernel, since kldload will find stale 596 modules in that directory instead of finding them in the correct 597 path, /boot/kernel. The most common complaint that this cures 598 is that the linux module crashes your machine after the update. 599 600 if [ ! -d /boot/kernel.old ]; then 601 mv /modules.old /boot/kernel.old 602 chflags noschg /kernel.old 603 mv /kernel.old /boot/kernel.old/kernel.ko 604 chflags schg /boot/kernel.old/kernel.ko 605 fi 606 60720000904: 608 A new issue with the sendmail upgrade has come to light. 609 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 610 incorrectly install the default aliases in /etc/mail rather than 611 move the old one from /etc. So you'll need to manually move the 612 file, create a symbolic link, remove the old /etc/aliases.db and 613 run newaliases. For safety sake, you should stop sendmail 614 while doing this and run the upgrade when locally sourced email 615 is not likely to be generated. 616 61720000825: 618 /boot/device.hints is now required for installkernel to 619 succeed. You should copy GENERIC.hints for your architecture 620 into /boot/device.hints. If and only if you compile hints 621 into your kernel, then this file may be empty. Please note, 622 if you have an empty or missing /boot/device.hints file and 623 you neglected to compile hints into your kernel, no boot 624 messages will appear after the boot loader tries to start the 625 kernel. 626 62720000821: 628 If you do NOT have ``options RANDOMDEV'' in your kernel and 629 you DO want the random device then add randomdev_load="YES" to 630 /boot/loader.conf. 631 63220000812: 633 suidperl is now always built and installed on the system, but 634 with permissions of 511. If you have applications that use 635 this program, you are now required to add ENABLE_SUIDPERL=true 636 to /etc/make.conf. If you forget to do this, 637 chmod 4511 /usr/bin/suidperl 638 will fix this until the next build. 639 64020000812: 641 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 642 visible changes that may immediately affect your configuration 643 include: 644 - New default file locations from src/contrib/sendmail/cf/README 645 - newaliases limited to root and trusted users 646 - MSA port (587) turned on by default 647 - New queue file naming system so can't go from 8.11 -> 8.9 648 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 649 - FEATURE(`nullclient') is more full featured 650 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 651 - mail.local FreeBSD-only -b option changed to -B 652 - See src/contrib/sendmail/RELEASE_NOTES for more info 653 65420000810: 655 suidperl (aka sperl) is no longer build by default. You must 656 specifically define BUILD_SUIDPERL to "true" for it to be build. 657 Furthermore, we recommend that you remove /usr/bin/sperl* and 658 /usr/bin/suidperl files from your system unless you have a 659 specific use for it. 660 66120000729: 662 Networking defaults have been tightened. Anybody upgrading 663 /etc/defaults/rc.conf needs to add the following lines to 664 /etc/rc.conf if they want to have the same setup 665 afterwards (unless the variables already are set, of course): 666 # Enable network daemons for user convenience. 667 inetd_enable="YES" 668 portmap_enable="YES" 669 sendmail_enable="YES" 670 67120000728: 672 If you have null_load="YES" in your /boot/loader.conf, you 673 will need to change that to nullfs_load="YES". 674 67520000728: 676 The "installkernel" target has changed slightly. Now even if 677 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 678 it will install the MYKERNEL file (built with the buildkernel 679 target) as /kernel rather than /MYKERNEL. Those who have 680 updated their /boot/loader.conf files to point to /MYKERNEL 681 should remove that entry or perform manual rename of /kernel 682 to /MYKERNEL. 683 68420000711: 685 If you use CVSUP or CTM to get CVS trees, AND you used to get 686 the old crypto files from internat.freebsd.org AND you check 687 out files from the CVS tree with the cvs command, please read 688 http://people.freebsd.org/~imp/internat.txt 689 for details on potential problems that you might have and how 690 to get around them. 691 692 If you are merely a mirror, or don't answer yes to each of the 693 clauses above, you needn't worry. 694 69520000711: 696 /etc/security has been updated to print the inode number of 697 setuid programs that have changed. You will see a large spike 698 in the number of changed programs the first time when you run 699 mergemaster to get a new /etc/security. 700 70120000710: 702 /dev/random now has good entropy collection (from the keyboard 703 and sysmouse drivers). Please ensure that either `options 704 RANDOMDEV' is present in your kernel config file or that 705 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 706 not have the /dev/random driver, OpenSSL (and consequently 707 lots of crypto tools (like SSH)) will fail with strange 708 errors. (see below, 20000624). 709 710 FreeBSD-current is safe again to run Crypto. 711 71220000709: 713 phk made the malloc default options AJ. This may slow things 714 down and uncover other latent bugs in the code. If you need to 715 run at full speed, you can disable this by doing the following: 716 ln -s aj /etc/malloc.conf 717 71820000706: 719 libftpio's version was accidentally bumped a few days ago. This 720 has been corrected. You may need to remove /usr/lib/libftpio.so.6 721 before doing your next buildworld/installworld pair. It certainly 722 won't hurt to remove it before the update procedure. It will 723 break fetch until a new one is built, but ftp can be used in the 724 interim if needed. 725 72620000705: 727 The crypto packages have changed for the cvsup. This has been done 728 in a backward compatible way, but the old packages will go away at 729 some point in the future. Look at /usr/share/examples/cvsup for 730 details. 731 73220000704: 733 With the new sys/modules/sound/drivers/*, you will need to 734 set SYSDIR until you do an installworld after July 7th. 735 73620000704: 737 rc.shutdown and rc will now call the rc.d scripts with start 738 or stop. This may cause some harmless warnings from older 739 rc.d scripts that haven't been updated. 740 74120000630: 742 The libfetch based version of fetch has gone into the tree. 743 Minor problems may result on some of the less popular sites, 744 which should be reported to des@freebsd.org. 745 74620000625: 747 From approximately this date forward, one must have the crypto 748 system installed in order to build the system and kernel. 749 While not technically strictly true, one should treat it as 750 required and grab the crypto bits. If you are grabbing CVS 751 trees, src-all and cvs-crypto should be treated as if they 752 were required. You should check with the latest collections 753 to make sure that these haven't changed. 754 75520000624: 756 Mark Murray just committed the first parts of a cleanup of 757 /dev/zero, et al. This is also cleaning up /dev/random. 758 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 759 -CURRENT FROM THIS POINT to 2000710 for cryptographic services 760 until Mark can merge in the fixes to this work in progress. 761 openssh and openssl should not be used to generate keys from this 762 date to the completion of the work. 763 764 If you must operate at this reduced level of security, add ' 765 options RANDOMDEV' to your kernel or modload the randomdev 766 module. You may also need to copy a new MAKEDEV to /dev and 767 recreate the random and urandom devices. 768 76920000622: 770 The license on the softupdates is now a standard 2 clause 771 BSD license. You may need to remove your symbolic links 772 that used to be required when updating. 773 77420000621: 775 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 776 the config file update procedure. 777 http://people.freebsd.org/~imp/config-upd.html 778 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 779 isn't buildable. However, you can generate a LINT file. 780 78120000620: 782 Binutils 2.10 have hit the tree, or will shortly. As soon 783 as they do, the problem noted in 20000522 will be resolved and 784 that workaround will no longer be required. 785 78620000615: 787 phk removed the compatibility creation of wd devices in the 788 ad driver. If you haven't done so already, you must update 789 your fstab, etc to use the ad devices instead of the wd 790 devices. 791 792 In addition, you'll need to update your boot blocks to a 793 more modern version, if you haven't already done so. Modern 794 here means 4.0 release or newer (although older releases 795 may work). 796 79720000612: 798 Peter took an axe to config(8). Be sure that you read his mail 799 on the topic before even thinking about updating. You will 800 need to create a /boot/device.hints or add a hints directive 801 to your config file to compile them in statically. The format 802 of the config file has changed as well. Please see GENERIC or 803 NEWCARD for examples of the new format. 804 805 Indirectly, this also breaks USERCONFIG 806 80720000522: 808 A new set of binutils went into the tree today. Anybody 809 building a kernel after this point is advised that they need 810 to rebuild their binutils (or better yet do a 811 buildworld/installworld) before building a new kernel. 812 813 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 814 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 815 is recommended that you don't set this option until the problem 816 is resolved. 817 81820000513: 819 The ethernet drivers were all updated to clean up the BPF handling. 820 82120000510: 822 The problems with boot blocks on the alphas have been corrected. 823 This will require some care in updating alphas. A new libstand 824 is requires for the boot blocks to build properly. 825 82620000503: 827 Recompile all kld modules. Proper version dependency info 828 is now available. 829 83020000502: 831 Modules have been disconnected from the buildworld tree and 832 connected to the kernel building instead. 833 83420000427: 835 You may need to build gperf 836 cd /usr/src/gnu/usr.bin/gperf && make depend all install 837 when upgrading from 4.0 -> current. The build system now uses 838 an option only in -current. 839 84020000417: 841 The method that we brand ELF binaries has changed to be more 842 acceptable to the binutils maintainers. You will need to 843 rebrand your ELF binaries that aren't native. One problem 844 binary is the Linux ldconfig. After your make world, but 845 before you reboot, you'll need to issue: 846 brandelf -t Linux /compat/linux/sbin/ldconfig 847 if you have Linux compatibility enabled on your machine. 848 84920000320: 850 If you have really bad/marginal IDE drives, you may find they 851 don't work well. Use pio mode instead. The easiest way to 852 cope if you have a problem combination is to add: 853 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 854 to the start of /etc/rc.conf. 855 85620000319: 857 The ISA and PCI compatibility shims have been connected to the 858 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 859 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 860 include the appropriate option in your kernel config. Drivers 861 using the shims should be updated or they won't ship with 862 5.0-RELEASE, targeted for 2001. 863 86420000318: 865 We've entered the traditional post release dumping party. 866 Large kernel changes are being committed and are in the 867 works. It is important to keep the systems' klds and kernel 868 in sync as kernel interfaces and structures are changing. 869 Before reporting kernel panics, make sure that all modules 870 that you are loading are up to date. 871 87220000315: 873 If you are upgrading from an older version of FreeBSD, you 874 need to update your boot blocks as well. 'disklabel -B ad0' 875 will do the trick. This isn't critical until you remove your 876 wd device entries in /dev, at which point your system will not 877 boot. 878 87920000315: 880 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 881 to upgrade to 4.0 from 3.x. 882 883COMMON ITEMS: 884 885 General Notes 886 ------------- 887 Avoid using make -j when upgrading. From time to time in the 888 past there have been problems using -j with buildworld and/or 889 installworld. This is especially true when upgrading between 890 "distant" versions (eg one that cross a major release boundary 891 or several minor releases, or when several months have passed 892 on the -current branch). 893 894 Sometimes, obscure build problems are the result of environment 895 poisoning. This can happen because the make utility reads its 896 environment when searching for values for global variables. 897 To run your build attempts in an "environmental clean room", 898 prefix all make commands with 'env -i '. See the env(1) manual 899 page for more details. 900 901 To build a kernel 902 ----------------- 903 If you are updating from a prior version of FreeBSD (even one just 904 a few days old), you should follow this procedure. With a 905 /usr/obj tree with a fresh buildworld, 906 make buildkernel KERNCONF=YOUR_KERNEL_HERE 907 make installkernel KERNCONF=YOUR_KERNEL_HERE 908 909 To just build a kernel when you know that it won't mess you up 910 -------------------------------------------------------------- 911 cd src/sys/{i386,alpha}/conf 912 config KERNEL_NAME_HERE 913 cd ../../compile/KERNEL_NAME_HERE 914 make depend 915 make 916 make install 917 918 If this fails, go to the "To build a kernel" section. 919 920 To rebuild everything and install it on the current system. 921 ----------------------------------------------------------- 922 make world 923 Build a new kernel, see above. 924 925 To upgrade from 4.x-stable to current 926 ------------------------------------- 927 make buildworld 928 make buildkernel KERNCONF=YOUR_KERNEL_HERE 929 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 930 make installkernel KERNCONF=YOUR_KERNEL_HERE 931 reboot in single user [3] 932 make installworld 933 mergemaster [4] 934 [1] 935 <reboot> 936 937 Make sure that you've read the UPDATING file to understand the 938 tweaks to various things you need. At this point in the life 939 cycle of current, things change often and you are on your own 940 to cope. The defaults can also change, so please read ALL of 941 the UPDATING entries. 942 943 Also, if you are tracking -current, you must be subscribed to 944 freebsd-current@freebsd.org. Make sure that before you update 945 your sources that you have read and understood all the recent 946 messages there. If in doubt, please track -stable which has 947 much fewer pitfalls. 948 949 [1] If you have third party modules, such as vmware, you 950 should disable them at this point so they don't crash your 951 system on reboot. 952 953 [2] If you have legacy ISA devices, you may need to create 954 your own device.hints to reflect your unique hardware 955 configuration. 956 957 [3] From the bootblocks, boot -s, and then do 958 fsck -p 959 mount -u / 960 mount -a 961 cd /usr/src 962 adjkerntz -i # if CMOS is wall time 963 964 [4] Note: This step is non-optional. Failure to do this step 965 can result in a significant reduction in the functionality of the 966 system. Attempting to do it by hand is not recommended and those 967 that pursue this avenue should read this file carefully, as well 968 as the archives of freebsd-current and freebsd-hackers mailing lists 969 for potential gotchas. 970 971FORMAT: 972 973This file contains a list, in reverse chronological order, of major 974breakages in tracking -current. Not all things will be listed here, 975and it only starts on March 15, 2000. Updating files can found in 976previous releases if your system is older than this. 977 978Please filter your entries through Warner Losh (imp@village.org) so 979that the style, formatting, etc of this file can be maintained. 980 981Copyright information: 982 983Copyright 1998, 2001 M. Warner Losh. All Rights Reserved. 984 985Redistribution, publication, translation and use, with or without 986modification, in full or in part, in any form or format of this 987document are permitted. 988 989THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 990IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 991WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 992DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 993INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 994(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 995SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 996HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 997STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 998IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 999POSSIBILITY OF SUCH DAMAGE. 1000 1001If you find this document useful, and you want to, you may buy the 1002author a beer. 1003 1004Contact Warner Losh if you have any questions about your use of 1005this document. 1006 1007$FreeBSD: head/UPDATING 94393 2002-04-11 01:39:16Z imp $ 1008