UPDATING revision 78588
1Updating Information for FreeBSD current users 2 3This file is maintained by imp@village.org. Please send new entries 4directly to him. See end of file for further details. For commonly 5done items, please see the end of the file. Search for 'COMMON 6ITEMS:' 7 820010617: 9 It appears that soft updates are working again. 10 1120010614: 12 Peter ripped out the linkerset support. You must, as always, 13 rerun config after you cvsup if you are using the traditional 14 kernel building methods. 15 1620010613: 17 Two items that have been biting people: 18 19 pccard modems may not work with current after 20010604 date. Some 20 do, others result in panics. *MAKE*SURE* that you update your 21 config ala the 20010604 entry, or you will have problems (this issue 22 will be fixed, it just hasn't been yet). 23 24 SOFTUPDATES seem to be broken since the middle of May or so. Do not 25 use them in current. Resolution unknown. 26 2720010612: 28 After Peter's commits to the hints code, people have been noticing 29 that certain devices are attached (or try to) twice. This is due 30 to having both static hints as well as a /boot/device.hints. To 31 work around this issue, please use only one or the other mechanism 32 until this bug is fixed. 33 3420010610: 35 Locale names have changed to match other systems better. 36 3720010604: 38 pccard support for pci cards has been committed. You must change 39 your /etc/pccard.conf irq lines. It must match the irq used by 40 pcic device. Interrupt storms may result if you fail to do this. 41 Interrupt storms look a lot like a hang. 42 43 You must also install a new pccardd, otherwise you will get an 44 interrupt storm at card reset time (just after it tells you what 45 it is). 46 47 pccardd_flags="-I" is necessary for the time being. It tells pccardd 48 not to ask the kernel if the interrupt is really free or not before 49 using it. You can either change the /etc/pccard.conf irq lines to 50 match pcic, or add "-i X" to the pccardd_flags. 51 5220010530: 53 INSTALL=install -C is being deprecated. If you want to do this, 54 use COPY=-C instead. The former method will be supported for only 55 a limited time. If you see 56 57install: warning: the -d and -C options may not be specified together 58 59 in your makeworld, then you need to migrate towards using 60 COPY=-C. 61 6220010525: 63 It appears that vm is now stable enough to use again. However, 64 there may be other problems, so caution is still urged. alpha 65 definitely is in bad shape. 66 6720010521: 68 Minor repo damanged has happened. This may cause problems 69 with cvsup of ports. If you get errors, please see 70 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 71 at the bottom for details on a workaround. The error message 72 is 73Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 74 7520010520: 76 Vm and/or swapping are busted on -current. Please be patient. 77 7820010519: 79 pccard has had much reorganizational work done to it over 80 the past few days. Everything should still work, but if 81 not, please contact imp@freebsd.org. 82 8320010517: 84 ata ioctl changed. Make sure to recompile both kernel and 85 userland at the same time. 86 8720010517: 88 New ncurses imported. 89 9020010512: 91 DEVFS is now opt out, not opt in. Barring major problems, this 92 will be the only way to go starting July 1. 93 9420010502: 95 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 96 9720010501: 98 Building perl was broken at 02:25:25 PDT. 99 10020010430: 101 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 102 go back in the water. 103 10420010429: 105 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 106 this date, but before the correction date. 107 10820010423: 109 old fsck and new kernel interactions appear to have been fixed. 110 11120010411: 112 fsck and the kernel were changed to handle some optimizations 113 to directory layout. This breaks backward compatibility. 114 Update only if you understand that you must not use the old 115 fsck with the new kernel ever. 116 11720010330: 118 fsck has changed the meaning of the pass column in /etc/fstab. 119 Please see the cvs commit to fsck.8 or the fsck.8 man page for 120 details. It is unclear if changes to /etc/fstab are necessary. 121 12220010319: 123 portmap had changed name to rpcbind for maximum POLA in your 124 current world. /etc/hosts.{allow,deny} needs changes. nfs and 125 other rpc based programs that rely on portmapper will not work 126 without updates to /etc/hosts.{allow,deny} and /etc/netcofnig. 127 12820010315: 129 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 130 and ATA_ENABEL_TAGS are no longer kernel options. They have 131 been replaced by tunables. See ata.4 for details. 132 13320010312: 134 The fxp driver was converted to use miibus. If you compile 135 fxp into your kernel statically, you will need to add miibus. 136 13720010312: 138 The wi device now defaults to BSS (infrastructure) mode 139 instead of ad-hoc. 140 14120010310: 142 /dev/urandom should be a symbolic link to /dev/random now. 143 Users of current not using DEVFS need to run MAKEDEV std. 144 ssh might not work if you don't. 145 14620010220: 147 The problems with libc have been corrected. It is now mostly 148 safe to go back into the water. 149 15020010211: 151 The size of FILE was changed. This breaks upgrading. If 152 you must upgrade, be prepared for pain. It also breaks almost 153 all binaries that you've compiled on -current. You are warned 154 that before upgrading would be a good time to do a level 0 155 dump of your system. No, really, I mean it this time. 156 157 To get to the new system, you'll need to use the following 158 workaround. Hopefully this can be sorted out so that we 159 don't have to move this to the updating section. 160 161 To get around the installworld problem, do: 162 # cd /usr/src/usr.bin/sed 163 # make install 164 # cd /usr/src 165 # make installworld 166 If that doesn't work, then try: 167 # make -k installworld 168 # make installworld 169 17020010207: 171 DEVFS is now the default. If you use vinum, make sure that you 172 do not include devfs in your kernel as problems result. 173 17420010205: 175 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 176 Remove them from your config. 177 17820010122: 179 ****************************** WARNING ****************************** 180 buildkernel has been changed slightly 181 ****************************** WARNING ****************************** 182 KERNCONF replaces the variable KERNEL for buildkernel. You 183 should update your scripts and make.conf accordingly. 184 18520010119: 186 config has changed to allow DEV_FOO as a replacement for NFOO. 187 This requires a new config to build correctly. 188 18920010116: 190 The kerrnel option I386_CPU is now mutually exclusive with the 191 other cpu types. If you have an i386 system, be sure that it 192 only had this line. Remove it for all other configurations. 193 19420010110: 195 Changes to the kernel require it and burncd be in sync. 196 19720010102: 198 Everyone who has hw.sndunit set to something in 199 /etc/sysctl.conf, it is now hw.snd.unit. 200 20120010101: 202 ex and vi were broken by some changes to sys/queue.h. If you 203 have a bad vi, you will see make buildworld fail with a core 204 dump while building termcap. You can work around this problem 205 by adding -k to your make buildworld. This will cause the 206 build to complete and install a new vi. Once that's done, you 207 can rebuild again without the -k to pick up anything that 208 might have been ignored by the -k option. 209 210 Others have suggested that you can just rebuild libc if your 211 vi/ex is dynamically linked, but I've not received any reports 212 of this working. 213 21420001228: 215 There have been some changes to libcrypt in -current. The 216 libscrypt/libdescrypt symlink sillyness is gone and the installed 217 libcrypt is fully functional. Be aware of this. 218 21920001218: 220 Linksys Fast Ethernet PCCARD cards supported by the ed driver 221 now require the addition of flag 0x80000 to their config line 222 in pccard.conf(5). This flag is not optional. These Linksys 223 cards will not be recognized without it. 224 22520001205: 226 Important new FreeBSD-version stuff: PAM support has been worked 227 in, partially from the "Unix" OpenSSH version. This requires 228 adding the following in pam.conf: 229 230 sshd auth sufficient pam_skey.so 231 sshd auth required pam_unix.so try_first_pass 232 sshd session required pam_permit.so 233 23420001031: 235 cvs updated to 1.11. 236 23720001020: 238 The random device needs more entropy, so you need to make sure 239 that you've run mergemaster to get a /etc/rc which will seed 240 /dev/random. If you don't and the system hangs after ldconfig, 241 then banging on the keyboard randomly until it unhangs is one 242 workaround. 243 24420001010: 245 ****************************** WARNING ****************************** 246 Sendmail has been updated. 247 ****************************** WARNING ****************************** 248 o mail.local(8) is no longer installed as a set-user-id binary. 249 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 250 is set. 251 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 252 commands. 253 o Now using sendmail's version of vacation(1). 254 o The sendmail cf building tools (contrib/sendmail/cf) are installed 255 in /usr/share/sendmail/cf. 256 o sendmail.cw changed to local-host-names 257 258 More details can be found at 259 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 260 26120001009: 262 The ports tree's new layout is in place. Be sure to update 263 your entire ports tree, or you will have problems. 264 26520001006: 266 The perl build procedure no longer installs miniperl, nor uses 267 the installed miniperl. It is recommended that you delete 268 /usr/bin/miniperl. 269 27020001005: 271 This weekend the ports tree will be updated to a new layout. 272 It will be in an inconsistent state until noted in the UPDATING 273 file, or with asami-san's message to the relevant mailing 274 lists. With this new layout, you'll need to update the whole 275 tree for anything to work. 276 27720000928: 278 There was a change in the passwd format. Need more information. 279 28020000916: 281 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 282 place. Please update boot loader (not the boot blocks) at the 283 same time as your kernel. 284 28520000914: 286 The new pmtimer device is necessary for laptops. Failure to 287 include the device will cause suspended laptops losing time 288 when they resume. Include 289 device pmtimer 290 in your config file and 291 hint.pmtimer.0.at="isa" 292 to your /boot/device.hints file. 293 29420000911: 295 The random device has been turned into a (pseudo-)device, 296 rather than an option. The supplied kernel config files have 297 been updated. You will need to do something similar in your 298 own kernel config file. 299 Remove: 300 options RANDOMDEV 301 Add: 302 device random 303 If you prefer to load the loadable module, you need to do 304 nothing. 305 30620000909: 307 The random device module has been renamed from randomdev.ko to 308 random.ko. You will need to edit your /boot/loader.conf to 309 reflect this if you load this module at boot time. 310 The line should read: 311 random_load="YES" 312 31320000907: 314 The SMPNG commit has happened. It should work, but if it 315 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 316 to be a variety of minor issues. Please see 20000905 to make 317 sure you don't have model loading problems which might at 318 first blush appear related to SMP. 319 32020000906: 321 nsswitch has been imported from NetBSD. Among other things, 322 this means that /etc/host.conf is no longer used. See 323 nsswitch.conf(5) instead. Note that at boot time rc.network 324 will attempt to produce a new nsswitch.conf file for you if you 325 don't have one, and you have host.conf. 326 32720000905: 328 The ucred structure changed size. This breaks the interface 329 that mountd uses. Trying to use an older mountd with a newer 330 kernel guarantees a panic. This means that you need to use 331 kernels newer than today only with matching mountd, but you 332 needed to do that anyway with the boot loader changes. 333 33420000905: 335 The boot loader has been updated. The new default kernel is 336 now /boot/kernel/kernel.ko. The new default module location 337 is /boot/kernel. 338 339 You *MUST* upgrade your boot loader and kernel at the same time. 340 The easiest way to do this is to do the buildworld/buildkernel/ 341 installkernel/installworld dance. 342 343 Furthermore, you are urged to delete your old /modules directory 344 before booting the new kernel, since kldload will find stale 345 modules in that directory instead of finding them in the correct 346 path, /boot/kernel. The most common complaint that this cures 347 is that the linux module crashes your machine after the update. 348 349 if [ ! -d /boot/kernel.old ]; then 350 mv /modules.old /boot/kernel.old 351 chflags noschg /kernel.old 352 mv /kernel.old /boot/kernel.old/kernel.ko 353 chflags schg /boot/kernel.old/kernel.ko 354 fi 355 35620000904: 357 A new issue with the sendmail upgrade has come to light. 358 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 359 incorrectly install the default aliases in /etc/mail rather than 360 move the old one from /etc. So you'll need to manually move the 361 file, create a symbolic link, remove the old /etc/aliases.db and 362 run newaliases. For safety sake, you should stop sendmail 363 while doing this and run the upgrade when locally sourced email 364 is not likely to be generated. 365 36620000825: 367 /boot/device.hints is now required for installkernel to 368 succeed. You should copy GENERIC.hints for your architecture 369 into /boot/device.hints. If and only if you compile hints 370 into your kernel, then this file may be empty. Please note, 371 if you have an empty or missing /boot/device.hints file and 372 you neglected to compile hints into your kernel, no boot 373 messages will appear after the boot loader tries to start the 374 kernel. 375 37620000821: 377 If you do NOT have ``options RANDOMDEV'' in your kernel and 378 you DO want the random device then add randomdev_load="YES" to 379 /boot/loader.conf. 380 38120000812: 382 suidperl is now always built and installed on the system, but 383 with permissions of 511. If you have applications that use 384 this program, you are now required to add ENABLE_SUIDPERL=true 385 to /etc/make.conf. If you forget to do this, 386 chmod 4511 /usr/bin/suidperl 387 will fix this until the next build. 388 38920000812: 390 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 391 visible changes that may immediately affect your configuration 392 include: 393 - New default file locations from src/contrib/sendmail/cf/README 394 - newaliases limited to root and trusted users 395 - MSA port (587) turned on by default 396 - New queue file naming system so can't go from 8.11 -> 8.9 397 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 398 - FEATURE(`nullclient') is more full featured 399 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 400 - mail.local FreeBSD-only -b option changed to -B 401 - See src/contrib/sendmail/RELEASE_NOTES for more info 402 40320000810: 404 suidperl (aka sperl) is no longer build by default. You must 405 specifically define BUILD_SUIDPERL to "true" for it to be build. 406 Furthermore, we recommend that you remove /usr/bin/sperl* and 407 /usr/bin/suidperl files from your system unless you have a 408 specific use for it. 409 41020000729: 411 Networking defaults have been tightened. Anybody upgrading 412 /etc/defaults/rc.conf needs to add the following lines to 413 /etc/rc.conf if they want to have the same setup 414 afterwards (unless the variables already are set, of course): 415 # Enable network daemons for user convenience. 416 inetd_enable="YES" 417 portmap_enable="YES" 418 sendmail_enable="YES" 419 42020000728: 421 If you have null_load="YES" in your /boot/loader.conf, you 422 will need to change that to nullfs_load="YES". 423 42420000728: 425 The "installkernel" target has changed slightly. Now even if 426 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 427 it will install the MYKERNEL file (built with the buildkernel 428 target) as /kernel rather than /MYKERNEL. Those who have 429 updated their /boot/loader.conf files to point to /MYKERNEL 430 should remove that entry or perform manual rename of /kernel 431 to /MYKERNEL. 432 43320000711: 434 If you use CVSUP or CTM to get CVS trees, AND you used to get 435 the old crypto files from internat.freebsd.org AND you check 436 out files from the CVS tree with the cvs command, please read 437 http://people.freebsd.org/~imp/internat.txt 438 for details on potential problems that you might have and how 439 to get around them. 440 441 If you are merely a mirror, or don't answer yes to each of the 442 clauses above, you needn't worry. 443 44420000711: 445 /etc/security has been updated to print the inode number of 446 setuid programs that have changed. You will see a large spike 447 in the number of changed programs the first time when you run 448 mergemaster to get a new /etc/security. 449 45020000710: 451 /dev/random now has good entropy collection (from the keyboard 452 and sysmouse drivers). Please ensure that either `options 453 RANDOMDEV' is present in your kernel config file or that 454 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 455 not have the /dev/random driver, OpenSSL (and consequently 456 lots of crypto tools (like SSH)) will fail with strange 457 errors. (see below, 20000624). 458 459 FreeBSD-current is safe again to run Crypto. 460 46120000709: 462 phk made the malloc default options AJ. This may slow things 463 down and uncover other latent bugs in the code. If you need to 464 run at full speed, you can disable this by doing the following: 465 ln -s aj /etc/malloc.conf 466 46720000706: 468 libftpio's version was accidentally bumped a few days ago. This 469 has been corrected. You may need to remove /usr/lib/libftpio.so.6 470 before doing your next buildworld/installworld pair. It certainly 471 won't hurt to remove it before the update procedure. It will 472 break fetch until a new one is built, but ftp can be used in the 473 interim if needed. 474 47520000705: 476 The crypto packages have changed for the cvsup. This has been done 477 in a backward compatible way, but the old packages will go away at 478 some point in the future. Look at /usr/share/examples/cvsup for 479 details. 480 48120000704: 482 With the new sys/modules/sound/drivers/*, you will need to 483 set SYSDIR until you do an installworld after July 7th. 484 48520000704: 486 rc.shutdown and rc will now call the rc.d scripts with start 487 or stop. This may cause some harmless warnings from older 488 rc.d scripts that haven't been updated. 489 49020000630: 491 The libfetch based version of fetch has gone into the tree. 492 Minor problems may result on some of the less popular sites, 493 which should be reported to des@freebsd.org. 494 49520000625: 496 From approximately this date forward, one must have the crypto 497 system installed in order to build the system and kernel. 498 While not technically strictly true, one should treat it as 499 required and grab the crypto bits. If you are grabbing CVS 500 trees, src-all and cvs-crypto should be treated as if they 501 were required. You should check with the latest collections 502 to make sure that these haven't changed. 503 50420000624: 505 Mark Murray just committed the first parts of a cleanup of 506 /dev/zero, et al. This is also cleaning up /dev/random. 507 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 508 -CURRENT FROM THIS POINT FORWARD for cryptographic services 509 until Mark can merge in the fixes to this work in progress. 510 openssh and openssl should not be used to generate keys from this 511 date to the completion of the work. 512 513 If you must operate at this reduced level of security, add ' 514 options RANDOMDEV' to your kernel or modload the randomdev 515 module. You may also need to copy a new MAKEDEV to /dev and 516 recreate the random and urandom devices. 517 51820000622: 519 The license on the softupdates is now a standard 2 clause 520 BSD license. You may need to remove your symbolic links 521 that used to be required when updating. 522 52320000621: 524 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 525 the config file update procedure. 526 http://people.freebsd.org/~imp/config-upd.html 527 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 528 isn't buildable. However, you can generate a LINT file. 529 53020000620: 531 Binutils 2.10 have hit the tree, or will shortly. As soon 532 as they do, the problem noted in 20000522 will be resolved and 533 that workaround will no longer be required. 534 53520000615: 536 phk removed the compatibility creation of wd devices in the 537 ad driver. If you haven't done so already, you must update 538 your fstab, etc to use the ad devices instead of the wd 539 devices. 540 541 In addition, you'll need to update your boot blocks to a 542 more modern version, if you haven't already done so. Modern 543 here means 4.0 release or newer (although older releases 544 may work). 545 54620000612: 547 Peter took an axe to config(8). Be sure that you read his mail 548 on the topic before even thinking about updating. You will 549 need to create a /boot/device.hints or add a hints directive 550 to your config file to compile them in statically. The format 551 of the config file has changed as well. Please see GENERIC or 552 NEWCARD for examples of the new format. 553 55420000522: 555 A new set of binutils went into the tree today. Anybody 556 building a kernel after this point is advised that they need 557 to rebuild their binutils (or better yet do a 558 buildworld/installworld) before building a new kernel. 559 560 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 561 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 562 is recommended that you don't set this option until the problem 563 is resolved. 564 56520000513: 566 The ethernet drivers were all updated to clean up the BPF handling. 567 56820000510: 569 The problems with boot blocks on the alphas have been corrected. 570 This will require some care in updating alphas. A new libstand 571 is requires for the boot blocks to build properly. 572 57320000503: 574 Recompile all kld modules. Proper version dependency info 575 is now available. 576 57720000502: 578 Modules have been disconnected from the buildworld tree and 579 connected to the kernel building instead. 580 58120000427: 582 You may need to build gperf 583 cd /usr/src/gnu/usr.bin/gperf && make depend all install 584 when upgrading from 4.0 -> current. The build system now uses 585 an option only in -current. 586 58720000417: 588 The method that we brand ELF binaries has changed to be more 589 acceptable to the binutils maintainers. You will need to 590 rebrand your ELF binaries that aren't native. One problem 591 binary is the Linux ldconfig. After your make world, but 592 before you reboot, you'll need to issue: 593 brandelf -t Linux /compat/linux/sbin/ldconfig 594 if you have Linux compatibility enabled on your machine. 595 59620000320: 597 If you have really bad/marginal IDE drives, you may find they 598 don't work well. Use pio mode instead. The easiest way to 599 cope if you have a problem combination is to add: 600 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 601 to the start of /etc/rc.conf. 602 60320000319: 604 The ISA and PCI compatibility shims have been connected to the 605 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 606 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 607 include the appropriate option in your kernel config. Drivers 608 using the shims should be updated or they won't ship with 609 5.0-RELEASE, targeted for 2001. 610 61120000318: 612 We've entered the traditional post release dumping party. 613 Large kernel changes are being committed and are in the 614 works. It is important to keep the systems' klds and kernel 615 in sync as kernel interfaces and structures are changing. 616 Before reporting kernel panics, make sure that all modules 617 that you are loading are up to date. 618 61920000315: 620 If you are upgrading from an older version of FreeBSD, you 621 need to update your boot blocks as well. 'disklabel -B ad0' 622 will do the trick. This isn't critical until you remove your 623 wd device entries in /dev, at which point your system will not 624 boot. 625 62620000315: 627 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 628 to upgrade to 4.0 from 3.x. 629 630COMMON ITEMS: 631 632 General Notes 633 ------------- 634 Avoid using make -j when upgrading. From time to time in the 635 past there have been problems using -j with buildworld and/or 636 installworld. This is especially true when upgrading between 637 "distant" versions (eg one that cross a major release boundary 638 or several minor releases, or when several months have passed 639 on the -current branch). 640 641 To build a kernel 642 ----------------- 643 If you are updating from a prior version of FreeBSD (even one just 644 a few days old), you should follow this procedure. With a 645 /usr/obj tree with a fresh buildworld, 646 make buildkernel KERNCONF=YOUR_KERNEL_HERE 647 make installkernel KERNCONF=YOUR_KERNEL_HERE 648 649 To just build a kernel when you know that it won't mess you up 650 -------------------------------------------------------------- 651 cd src/sys/{i386,alpha}/conf 652 config KERNEL_NAME_HERE [1] 653 cd ../../compile/KERNEL_NAME_HERE 654 make depend 655 make 656 make install 657 658 [1] If in doubt, -r might help here. 659 660 If this fails, go to the "To build a kernel" section. 661 662 To rebuild everything and install it on the current system. 663 ----------------------------------------------------------- 664 make world 665 Build a new kernel, see above. 666 667 To upgrade from 4.x-stable to current 668 ------------------------------------- 669 make buildworld 670 make buildkernel KERNCONF=YOUR_KERNEL_HERE 671 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 672 make installkernel KERNCONF=YOUR_KERNEL_HERE 673 reboot in single user [3] 674 make installworld 675 mergemaster 676 [1] 677 <reboot> 678 679 Make sure that you've read the UPDATING file to understand the 680 tweaks to various things you need. At this point in the life 681 cycle of current, things change often and you are on your own 682 to cope. The defaults can also change, so please read ALL of 683 the UPDATING entries. 684 685 Also, if you are tracking -current, you must be subscribed to 686 freebsd-current@freebsd.org. Make sure that before you update 687 your sources that you have read and understood all the recent 688 messages there. If in doubt, please track -stable which has 689 much fewer pitfalls. 690 691 [1] If you have third party modules, such as vmware, you 692 should disable them at this point so they don't crash your 693 system on reboot. 694 695 [2] If you have legacy ISA devices, you may need to create 696 your own device.hints to reflect your unique hardware 697 configuration. 698 699 [3] From the bootblocks, boot -s, and then do 700 fsck -p 701 mount -u / 702 mount -a 703 cd /usr/src 704 adjkerntz -i # if COMS is wall time 705 706FORMAT: 707 708This file contains a list, in reverse chronological order, of major 709breakages in tracking -current. Not all things will be listed here, 710and it only starts on March 15, 2000. Updating files can found in 711previous releases if your system is older than this. 712 713Please filter your entries through Warner Losh (imp@village.org) so 714that the style, formatting, etc of this file can be maintained. 715 716$FreeBSD: head/UPDATING 78588 2001-06-22 04:50:11Z imp $ 717