UPDATING revision 84351
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 820011001: 9 The kernel interface that burncd depends on has changed. 10 You must recompile both the kernel and userland applications 11 at the same time. 12 1320010929: 14 When crossbuilding, please set TARGET_ARCH rather than 15 MACHINE_ARCH to indicate the target. In the future, one will 16 set TARGET_MACHINE where you set MACHINE now. At the moment, 17 setting MACHINE alone for same MACHINE_ARCH machines works 18 (eg, you can build pc98 on a i386 machine and vice versa). 19 2020010927: 21 Some weird problems result from using ACPI on some machines. 22 To disable ACPI you can add 23 hint.acpi.0.disable="1" 24 to /boot/loader.conf (or by putting set X=Y at the boot 25 loader "ok" prompt). 26 27 Alternatively, you can remove it from /boot/kernel/acpi.ko 28 or use the MODULES_OVERRIDE function in your kernel config 29 file and not list acpi in that list. 30 3120010924: 32 The buildworld has been fixed. You may need to install 33 the 4.x compatibility libraries for some old binaries 34 to work. 35 cd src/lib/compat/compat4x.i386 36 make all install 37 3820010919: 39 There's a bug in the world build process. The cross-tools 40 are build with the NEW headers, but the OLD libc.a. This 41 leads to all kinds of problems with the new libc. A temporary 42 workaround is to add 43 CFLAGS="-O -pipe -D_OLD_STDIO" 44 before building world when upgrading from 4.x to current. This 45 can be removed afterwards. 46 47 A proper fix to the buildworld target is needed. 48 4920010918: 50 Peter has committed his new kthread nfs client/server code. 51 NFS may be unstable after this date. 52 5320010912: 54 KSE has hit the tree. Lots of things are now different in 55 the kernel. While a few problems were introduced in the 56 initial commit, most of the major ones have been found and 57 corrected. 58 5920010901: 60 In OLDCARD, CardBus bridges appear to be stable. The work 61 arounds described in the 20010604 entry are now no longer 62 necessary and will be ignored. Most insert/remove problems 63 have been rectified around this date. 64 6520010823: 66 named now runs as user bind and group bind rather than as 67 root. If named_enable is set to YES in /etc/rc.conf, ensure 68 that user bind is available in /etc/passwd (using vipw(8)) 69 and that group bind is available in /etc/group. Also make 70 sure that user or group bind has read (and not write) 71 permission for your name server configuration and that it 72 has read and write permission for your slave zone files and 73 directory. 74 75 If you wish to continue to run named as root (a less secure 76 alternative), add a line to /etc/rc.conf saying 77 78 named_flags= 79 8020010709: 81 The PAM libraries have had an API upgrade that is beyond 82 the ability of the shared library major number to handle. 83 It is manifested by PAM-using ports dumping core. The 84 solution is to rebuild those ports. 85 8620010628: 87 The kernel compile module has moved from src/sys/compile/FOO 88 to src/sys/${MACHINE}/compile/FOO. 89 9020010625: 91 The pccard modem issue from 20010613 has been corrected. 92 OLDCARD support is still a little weak in -current. slot 1 is 93 known not to work on some TI based cardbus bridges. Some 94 cardbus bridges do not properly detect insert/removal events. 95 IRQ configuration needs more safety belts. 96 9720010617: 98 Softupdates problems have been corrected. 99 10020010614: 101 Peter ripped out the linkerset support. You must, as always, 102 rerun config after you cvsup if you are using the traditional 103 kernel building methods. 104 10520010613: 106 pccard modems may not work with current after 20010604 date. Some 107 do, others result in panics. *MAKE*SURE* that you update your 108 config and /etc/rc.conf ala the 20010604 entry, or you will have 109 problems (this issue will be fixed, it just hasn't been yet). 110 11120010613: 112 SOFTUPDATES seem to be broken since the middle of May or so. Do not 113 use them in current. You can disable softupdates on all mounted 114 partitions, or remove SOFTUPDATES the kernel config file. 115 11620010612: 117 After Peter's commits to the hints code, people have been noticing 118 that certain devices are attached (or try to) twice. This is due 119 to having both static hints as well as a /boot/device.hints. To 120 work around this issue, please use only one or the other mechanism 121 until this bug is fixed. 122 123 Please note that a feature of config is that if you have config 124 file FOO and FOO.hints, it automatically adds FOO.hints to the 125 hints.c file, wheather you want it to or not. 126 12720010610: 128 Locale names have changed to match other systems better. 129 13020010604: 131 pccard support for pci cards has been committed. You must change 132 your /etc/pccard.conf irq lines. It must match the irq used by 133 pcic device. Interrupt storms may result if you fail to do this. 134 Interrupt storms look a lot like a hang. 135 136 You must also install a new pccardd, otherwise you will get an 137 interrupt storm at card reset time (just after it tells you what 138 it is). 139 140 pccardd_flags="-I" is necessary for the time being. It tells pccardd 141 not to ask the kernel if the interrupt is really free or not before 142 using it. You can either change the /etc/pccard.conf irq lines to 143 match pcic, or add "-i X" to the pccardd_flags. 144 14520010530: 146 INSTALL=install -C is being deprecated. If you want to do this, 147 use COPY=-C instead. The former method will be supported for only 148 a limited time. If you see 149 150install: warning: the -d and -C options may not be specified together 151 152 in your makeworld, then you need to migrate towards using 153 COPY=-C. 154 15520010525: 156 It appears that vm is now stable enough to use again. However, 157 there may be other problems, so caution is still urged. alpha 158 definitely is in bad shape. 159 16020010521: 161 Minor repo damange has happened. This may cause problems 162 with cvsup of ports. If you get errors, please see 163 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 164 at the bottom for details on a workaround. The error message 165 is 166Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 167 16820010520: 169 Vm and/or swapping are busted on -current. Please be patient. 170 17120010519: 172 pccard has had much reorganizational work done to it over 173 the past few days. Everything should still work, but if 174 not, please contact imp@freebsd.org. 175 17620010517: 177 ata ioctl changed. Make sure to recompile both kernel and 178 userland at the same time. 179 18020010517: 181 New ncurses imported. 182 18320010512: 184 DEVFS is now opt out, not opt in. Barring major problems, this 185 will be the only way to go starting July 1. 186 18720010502: 188 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 189 19020010501: 191 Building perl was broken at 02:25:25 PDT. 192 19320010430: 194 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 195 go back in the water. 196 19720010429: 198 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 199 this date, but before the correction date. 200 20120010423: 202 old fsck and new kernel interactions appear to have been fixed. 203 20420010411: 205 fsck and the kernel were changed to handle some optimizations 206 to directory layout. This breaks backward compatibility. 207 Update only if you understand that you must not use the old 208 fsck with the new kernel ever. 209 21020010330: 211 fsck has changed the meaning of the pass column in /etc/fstab. 212 Please see the cvs commit to fsck.8 or the fsck.8 man page for 213 details. It is unclear if changes to /etc/fstab are necessary. 214 21520010319: 216 portmap had changed name to rpcbind for maximum POLA in your 217 current world. /etc/hosts.{allow,deny} needs changes. nfs and 218 other rpc based programs that rely on portmapper will not work 219 without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 220 22120010315: 222 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 223 and ATA_ENABEL_TAGS are no longer kernel options. They have 224 been replaced by tunables. See ata.4 for details. 225 22620010312: 227 The fxp driver was converted to use miibus. If you compile 228 fxp into your kernel statically, you will need to add miibus. 229 23020010312: 231 The wi device now defaults to BSS (infrastructure) mode 232 instead of ad-hoc. 233 23420010310: 235 /dev/urandom should be a symbolic link to /dev/random now. 236 Users of current not using DEVFS need to run MAKEDEV std. 237 ssh might not work if you don't. 238 23920010303: 240 The ed driver has been updated. It now allows mii attachments, 241 which means that you must include the miibus in your kernel if 242 you use the ed driver. 243 24420010220: 245 The problems with libc have been corrected. It is now mostly 246 safe to go back into the water. 247 24820010211: 249 The size of FILE was changed. This breaks upgrading. If 250 you must upgrade, be prepared for pain. It also breaks almost 251 all binaries that you've compiled on -current. You are warned 252 that before upgrading would be a good time to do a level 0 253 dump of your system. No, really, I mean it this time. 254 255 To get to the new system, you'll need to use the following 256 workaround. Hopefully this can be sorted out so that we 257 don't have to move this to the updating section. 258 259 To get around the installworld problem, do: 260 # cd /usr/src/usr.bin/sed 261 # make install 262 # cd /usr/src 263 # make installworld 264 If that doesn't work, then try: 265 # make -k installworld 266 # make installworld 267 26820010207: 269 DEVFS is now the default. If you use vinum, make sure that you 270 do not include devfs in your kernel as problems result. 271 27220010205: 273 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 274 Remove them from your config. 275 27620010122: 277 ****************************** WARNING ****************************** 278 buildkernel has been changed slightly 279 ****************************** WARNING ****************************** 280 KERNCONF replaces the variable KERNEL for buildkernel. You 281 should update your scripts and make.conf accordingly. 282 28320010119: 284 config has changed to allow DEV_FOO as a replacement for NFOO. 285 This requires a new config to build correctly. 286 28720010116: 288 The kerrnel option I386_CPU is now mutually exclusive with the 289 other cpu types. If you have an i386 system, be sure that it 290 only had this line. Remove it for all other configurations. 291 29220010110: 293 Changes to the kernel require it and burncd be in sync. 294 29520010102: 296 Everyone who has hw.sndunit set to something in 297 /etc/sysctl.conf, it is now hw.snd.unit. 298 29920010101: 300 ex and vi were broken by some changes to sys/queue.h. If you 301 have a bad vi, you will see make buildworld fail with a core 302 dump while building termcap. You can work around this problem 303 by adding -k to your make buildworld. This will cause the 304 build to complete and install a new vi. Once that's done, you 305 can rebuild again without the -k to pick up anything that 306 might have been ignored by the -k option. 307 308 Others have suggested that you can just rebuild libc if your 309 vi/ex is dynamically linked, but I've not received any reports 310 of this working. 311 31220001228: 313 There have been some changes to libcrypt in -current. The 314 libscrypt/libdescrypt symlink sillyness is gone and the installed 315 libcrypt is fully functional. Be aware of this. 316 31720001218: 318 Linksys Fast Ethernet PCCARD cards supported by the ed driver 319 now require the addition of flag 0x80000 to their config line 320 in pccard.conf(5). This flag is not optional. These Linksys 321 cards will not be recognized without it. 322 32320001205: 324 Important new FreeBSD-version stuff: PAM support has been worked 325 in, partially from the "Unix" OpenSSH version. This requires 326 adding the following in pam.conf: 327 328 sshd auth sufficient pam_skey.so 329 sshd auth required pam_unix.so try_first_pass 330 sshd session required pam_permit.so 331 33220001031: 333 cvs updated to 1.11. 334 33520001020: 336 The random device needs more entropy, so you need to make sure 337 that you've run mergemaster to get a /etc/rc which will seed 338 /dev/random. If you don't and the system hangs after ldconfig, 339 then banging on the keyboard randomly until it unhangs is one 340 workaround. 341 34220001010: 343 ****************************** WARNING ****************************** 344 Sendmail has been updated. 345 ****************************** WARNING ****************************** 346 o mail.local(8) is no longer installed as a set-user-id binary. 347 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 348 is set. 349 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 350 commands. 351 o Now using sendmail's version of vacation(1). 352 o The sendmail cf building tools (contrib/sendmail/cf) are installed 353 in /usr/share/sendmail/cf. 354 o sendmail.cw changed to local-host-names 355 356 More details can be found at 357 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 358 35920001009: 360 The ports tree's new layout is in place. Be sure to update 361 your entire ports tree, or you will have problems. 362 36320001006: 364 The perl build procedure no longer installs miniperl, nor uses 365 the installed miniperl. It is recommended that you delete 366 /usr/bin/miniperl. 367 36820001005: 369 This weekend the ports tree will be updated to a new layout. 370 It will be in an inconsistent state until noted in the UPDATING 371 file, or with asami-san's message to the relevant mailing 372 lists. With this new layout, you'll need to update the whole 373 tree for anything to work. 374 37520000928: 376 There was a change in the passwd format. Need more information. 377 37820000916: 379 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 380 place. Please update boot loader (not the boot blocks) at the 381 same time as your kernel. 382 38320000914: 384 The new pmtimer device is necessary for laptops. Failure to 385 include the device will cause suspended laptops losing time 386 when they resume. Include 387 device pmtimer 388 in your config file and 389 hint.pmtimer.0.at="isa" 390 to your /boot/device.hints file. 391 39220000911: 393 The random device has been turned into a (pseudo-)device, 394 rather than an option. The supplied kernel config files have 395 been updated. You will need to do something similar in your 396 own kernel config file. 397 Remove: 398 options RANDOMDEV 399 Add: 400 device random 401 If you prefer to load the loadable module, you need to do 402 nothing. 403 40420000909: 405 The random device module has been renamed from randomdev.ko to 406 random.ko. You will need to edit your /boot/loader.conf to 407 reflect this if you load this module at boot time. 408 The line should read: 409 random_load="YES" 410 41120000907: 412 The SMPNG commit has happened. It should work, but if it 413 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 414 to be a variety of minor issues. Please see 20000905 to make 415 sure you don't have model loading problems which might at 416 first blush appear related to SMP. 417 41820000906: 419 nsswitch has been imported from NetBSD. Among other things, 420 this means that /etc/host.conf is no longer used. See 421 nsswitch.conf(5) instead. Note that at boot time rc.network 422 will attempt to produce a new nsswitch.conf file for you if you 423 don't have one, and you have host.conf. 424 42520000905: 426 The ucred structure changed size. This breaks the interface 427 that mountd uses. Trying to use an older mountd with a newer 428 kernel guarantees a panic. This means that you need to use 429 kernels newer than today only with matching mountd, but you 430 needed to do that anyway with the boot loader changes. 431 43220000905: 433 The boot loader has been updated. The new default kernel is 434 now /boot/kernel/kernel.ko. The new default module location 435 is /boot/kernel. 436 437 You *MUST* upgrade your boot loader and kernel at the same time. 438 The easiest way to do this is to do the buildworld/buildkernel/ 439 installkernel/installworld dance. 440 441 Furthermore, you are urged to delete your old /modules directory 442 before booting the new kernel, since kldload will find stale 443 modules in that directory instead of finding them in the correct 444 path, /boot/kernel. The most common complaint that this cures 445 is that the linux module crashes your machine after the update. 446 447 if [ ! -d /boot/kernel.old ]; then 448 mv /modules.old /boot/kernel.old 449 chflags noschg /kernel.old 450 mv /kernel.old /boot/kernel.old/kernel.ko 451 chflags schg /boot/kernel.old/kernel.ko 452 fi 453 45420000904: 455 A new issue with the sendmail upgrade has come to light. 456 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 457 incorrectly install the default aliases in /etc/mail rather than 458 move the old one from /etc. So you'll need to manually move the 459 file, create a symbolic link, remove the old /etc/aliases.db and 460 run newaliases. For safety sake, you should stop sendmail 461 while doing this and run the upgrade when locally sourced email 462 is not likely to be generated. 463 46420000825: 465 /boot/device.hints is now required for installkernel to 466 succeed. You should copy GENERIC.hints for your architecture 467 into /boot/device.hints. If and only if you compile hints 468 into your kernel, then this file may be empty. Please note, 469 if you have an empty or missing /boot/device.hints file and 470 you neglected to compile hints into your kernel, no boot 471 messages will appear after the boot loader tries to start the 472 kernel. 473 47420000821: 475 If you do NOT have ``options RANDOMDEV'' in your kernel and 476 you DO want the random device then add randomdev_load="YES" to 477 /boot/loader.conf. 478 47920000812: 480 suidperl is now always built and installed on the system, but 481 with permissions of 511. If you have applications that use 482 this program, you are now required to add ENABLE_SUIDPERL=true 483 to /etc/make.conf. If you forget to do this, 484 chmod 4511 /usr/bin/suidperl 485 will fix this until the next build. 486 48720000812: 488 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 489 visible changes that may immediately affect your configuration 490 include: 491 - New default file locations from src/contrib/sendmail/cf/README 492 - newaliases limited to root and trusted users 493 - MSA port (587) turned on by default 494 - New queue file naming system so can't go from 8.11 -> 8.9 495 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 496 - FEATURE(`nullclient') is more full featured 497 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 498 - mail.local FreeBSD-only -b option changed to -B 499 - See src/contrib/sendmail/RELEASE_NOTES for more info 500 50120000810: 502 suidperl (aka sperl) is no longer build by default. You must 503 specifically define BUILD_SUIDPERL to "true" for it to be build. 504 Furthermore, we recommend that you remove /usr/bin/sperl* and 505 /usr/bin/suidperl files from your system unless you have a 506 specific use for it. 507 50820000729: 509 Networking defaults have been tightened. Anybody upgrading 510 /etc/defaults/rc.conf needs to add the following lines to 511 /etc/rc.conf if they want to have the same setup 512 afterwards (unless the variables already are set, of course): 513 # Enable network daemons for user convenience. 514 inetd_enable="YES" 515 portmap_enable="YES" 516 sendmail_enable="YES" 517 51820000728: 519 If you have null_load="YES" in your /boot/loader.conf, you 520 will need to change that to nullfs_load="YES". 521 52220000728: 523 The "installkernel" target has changed slightly. Now even if 524 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 525 it will install the MYKERNEL file (built with the buildkernel 526 target) as /kernel rather than /MYKERNEL. Those who have 527 updated their /boot/loader.conf files to point to /MYKERNEL 528 should remove that entry or perform manual rename of /kernel 529 to /MYKERNEL. 530 53120000711: 532 If you use CVSUP or CTM to get CVS trees, AND you used to get 533 the old crypto files from internat.freebsd.org AND you check 534 out files from the CVS tree with the cvs command, please read 535 http://people.freebsd.org/~imp/internat.txt 536 for details on potential problems that you might have and how 537 to get around them. 538 539 If you are merely a mirror, or don't answer yes to each of the 540 clauses above, you needn't worry. 541 54220000711: 543 /etc/security has been updated to print the inode number of 544 setuid programs that have changed. You will see a large spike 545 in the number of changed programs the first time when you run 546 mergemaster to get a new /etc/security. 547 54820000710: 549 /dev/random now has good entropy collection (from the keyboard 550 and sysmouse drivers). Please ensure that either `options 551 RANDOMDEV' is present in your kernel config file or that 552 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 553 not have the /dev/random driver, OpenSSL (and consequently 554 lots of crypto tools (like SSH)) will fail with strange 555 errors. (see below, 20000624). 556 557 FreeBSD-current is safe again to run Crypto. 558 55920000709: 560 phk made the malloc default options AJ. This may slow things 561 down and uncover other latent bugs in the code. If you need to 562 run at full speed, you can disable this by doing the following: 563 ln -s aj /etc/malloc.conf 564 56520000706: 566 libftpio's version was accidentally bumped a few days ago. This 567 has been corrected. You may need to remove /usr/lib/libftpio.so.6 568 before doing your next buildworld/installworld pair. It certainly 569 won't hurt to remove it before the update procedure. It will 570 break fetch until a new one is built, but ftp can be used in the 571 interim if needed. 572 57320000705: 574 The crypto packages have changed for the cvsup. This has been done 575 in a backward compatible way, but the old packages will go away at 576 some point in the future. Look at /usr/share/examples/cvsup for 577 details. 578 57920000704: 580 With the new sys/modules/sound/drivers/*, you will need to 581 set SYSDIR until you do an installworld after July 7th. 582 58320000704: 584 rc.shutdown and rc will now call the rc.d scripts with start 585 or stop. This may cause some harmless warnings from older 586 rc.d scripts that haven't been updated. 587 58820000630: 589 The libfetch based version of fetch has gone into the tree. 590 Minor problems may result on some of the less popular sites, 591 which should be reported to des@freebsd.org. 592 59320000625: 594 From approximately this date forward, one must have the crypto 595 system installed in order to build the system and kernel. 596 While not technically strictly true, one should treat it as 597 required and grab the crypto bits. If you are grabbing CVS 598 trees, src-all and cvs-crypto should be treated as if they 599 were required. You should check with the latest collections 600 to make sure that these haven't changed. 601 60220000624: 603 Mark Murray just committed the first parts of a cleanup of 604 /dev/zero, et al. This is also cleaning up /dev/random. 605 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 606 -CURRENT FROM THIS POINT FORWARD for cryptographic services 607 until Mark can merge in the fixes to this work in progress. 608 openssh and openssl should not be used to generate keys from this 609 date to the completion of the work. 610 611 If you must operate at this reduced level of security, add ' 612 options RANDOMDEV' to your kernel or modload the randomdev 613 module. You may also need to copy a new MAKEDEV to /dev and 614 recreate the random and urandom devices. 615 61620000622: 617 The license on the softupdates is now a standard 2 clause 618 BSD license. You may need to remove your symbolic links 619 that used to be required when updating. 620 62120000621: 622 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 623 the config file update procedure. 624 http://people.freebsd.org/~imp/config-upd.html 625 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 626 isn't buildable. However, you can generate a LINT file. 627 62820000620: 629 Binutils 2.10 have hit the tree, or will shortly. As soon 630 as they do, the problem noted in 20000522 will be resolved and 631 that workaround will no longer be required. 632 63320000615: 634 phk removed the compatibility creation of wd devices in the 635 ad driver. If you haven't done so already, you must update 636 your fstab, etc to use the ad devices instead of the wd 637 devices. 638 639 In addition, you'll need to update your boot blocks to a 640 more modern version, if you haven't already done so. Modern 641 here means 4.0 release or newer (although older releases 642 may work). 643 64420000612: 645 Peter took an axe to config(8). Be sure that you read his mail 646 on the topic before even thinking about updating. You will 647 need to create a /boot/device.hints or add a hints directive 648 to your config file to compile them in statically. The format 649 of the config file has changed as well. Please see GENERIC or 650 NEWCARD for examples of the new format. 651 65220000522: 653 A new set of binutils went into the tree today. Anybody 654 building a kernel after this point is advised that they need 655 to rebuild their binutils (or better yet do a 656 buildworld/installworld) before building a new kernel. 657 658 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 659 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 660 is recommended that you don't set this option until the problem 661 is resolved. 662 66320000513: 664 The ethernet drivers were all updated to clean up the BPF handling. 665 66620000510: 667 The problems with boot blocks on the alphas have been corrected. 668 This will require some care in updating alphas. A new libstand 669 is requires for the boot blocks to build properly. 670 67120000503: 672 Recompile all kld modules. Proper version dependency info 673 is now available. 674 67520000502: 676 Modules have been disconnected from the buildworld tree and 677 connected to the kernel building instead. 678 67920000427: 680 You may need to build gperf 681 cd /usr/src/gnu/usr.bin/gperf && make depend all install 682 when upgrading from 4.0 -> current. The build system now uses 683 an option only in -current. 684 68520000417: 686 The method that we brand ELF binaries has changed to be more 687 acceptable to the binutils maintainers. You will need to 688 rebrand your ELF binaries that aren't native. One problem 689 binary is the Linux ldconfig. After your make world, but 690 before you reboot, you'll need to issue: 691 brandelf -t Linux /compat/linux/sbin/ldconfig 692 if you have Linux compatibility enabled on your machine. 693 69420000320: 695 If you have really bad/marginal IDE drives, you may find they 696 don't work well. Use pio mode instead. The easiest way to 697 cope if you have a problem combination is to add: 698 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 699 to the start of /etc/rc.conf. 700 70120000319: 702 The ISA and PCI compatibility shims have been connected to the 703 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 704 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 705 include the appropriate option in your kernel config. Drivers 706 using the shims should be updated or they won't ship with 707 5.0-RELEASE, targeted for 2001. 708 70920000318: 710 We've entered the traditional post release dumping party. 711 Large kernel changes are being committed and are in the 712 works. It is important to keep the systems' klds and kernel 713 in sync as kernel interfaces and structures are changing. 714 Before reporting kernel panics, make sure that all modules 715 that you are loading are up to date. 716 71720000315: 718 If you are upgrading from an older version of FreeBSD, you 719 need to update your boot blocks as well. 'disklabel -B ad0' 720 will do the trick. This isn't critical until you remove your 721 wd device entries in /dev, at which point your system will not 722 boot. 723 72420000315: 725 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 726 to upgrade to 4.0 from 3.x. 727 728COMMON ITEMS: 729 730 General Notes 731 ------------- 732 Avoid using make -j when upgrading. From time to time in the 733 past there have been problems using -j with buildworld and/or 734 installworld. This is especially true when upgrading between 735 "distant" versions (eg one that cross a major release boundary 736 or several minor releases, or when several months have passed 737 on the -current branch). 738 739 To build a kernel 740 ----------------- 741 If you are updating from a prior version of FreeBSD (even one just 742 a few days old), you should follow this procedure. With a 743 /usr/obj tree with a fresh buildworld, 744 make buildkernel KERNCONF=YOUR_KERNEL_HERE 745 make installkernel KERNCONF=YOUR_KERNEL_HERE 746 747 To just build a kernel when you know that it won't mess you up 748 -------------------------------------------------------------- 749 cd src/sys/{i386,alpha}/conf 750 config KERNEL_NAME_HERE [1] 751 cd ../../compile/KERNEL_NAME_HERE 752 make depend 753 make 754 make install 755 756 [1] If in doubt, -r might help here. 757 758 If this fails, go to the "To build a kernel" section. 759 760 To rebuild everything and install it on the current system. 761 ----------------------------------------------------------- 762 make world 763 Build a new kernel, see above. 764 765 To upgrade from 4.x-stable to current 766 ------------------------------------- 767 make buildworld 768 make buildkernel KERNCONF=YOUR_KERNEL_HERE 769 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 770 make installkernel KERNCONF=YOUR_KERNEL_HERE 771 reboot in single user [3] 772 make installworld 773 mergemaster [4] 774 [1] 775 <reboot> 776 777 Make sure that you've read the UPDATING file to understand the 778 tweaks to various things you need. At this point in the life 779 cycle of current, things change often and you are on your own 780 to cope. The defaults can also change, so please read ALL of 781 the UPDATING entries. 782 783 Also, if you are tracking -current, you must be subscribed to 784 freebsd-current@freebsd.org. Make sure that before you update 785 your sources that you have read and understood all the recent 786 messages there. If in doubt, please track -stable which has 787 much fewer pitfalls. 788 789 [1] If you have third party modules, such as vmware, you 790 should disable them at this point so they don't crash your 791 system on reboot. 792 793 [2] If you have legacy ISA devices, you may need to create 794 your own device.hints to reflect your unique hardware 795 configuration. 796 797 [3] From the bootblocks, boot -s, and then do 798 fsck -p 799 mount -u / 800 mount -a 801 cd /usr/src 802 adjkerntz -i # if COMS is wall time 803 804 [4] Note: This step is non-optional. Failure to do this step 805 can result in a significant reduction in the functionality of the 806 system. Attempting to do it by hand is not recommended and those 807 that pursue this avenue should read this file carefully, as well 808 as the archives of freebsd-current and freebsd-hackers mailing lists 809 for potential gotchas. 810 811FORMAT: 812 813This file contains a list, in reverse chronological order, of major 814breakages in tracking -current. Not all things will be listed here, 815and it only starts on March 15, 2000. Updating files can found in 816previous releases if your system is older than this. 817 818Please filter your entries through Warner Losh (imp@village.org) so 819that the style, formatting, etc of this file can be maintained. 820 821Copyright information: 822 823Copyright 1998, 2001 M. Warner Losh. All Rights Reserved. 824 825Redistribution, publication, translation and use, with or without 826modification, in full or in part, in any form or format of this 827document are permitted. 828 829THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 830IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 831WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 832DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 833INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 834(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 835SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 836HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 837STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 838IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 839POSSIBILITY OF SUCH DAMAGE. 840 841If you find this document useful, and you want to, you may buy the 842author a beer. 843 844Contact Warner Losh if you have any questions about your use of 845this document. 846 847$FreeBSD: head/UPDATING 84351 2001-10-02 07:01:27Z imp $ 848