UPDATING revision 118141
1Updating Information for FreeBSD current users 2 3This file is maintained and copyrighted by M. Warner Losh 4<imp@village.org>. See end of file for further details. For commonly 5done items, please see the COMMON ITEMS: section later in the file. 6 7NOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW: 8 FreeBSD 5.0-CURRENT has many debugging features turned on, in 9 both the kernel and userland. These features attempt to detect 10 incorrect use of system primitives, and encourage loud failure 11 through extra sanity checking and fail stop semantics. They 12 also substantially impact system performance. If you want to 13 do performance measurement, benchmarking, and optimization, 14 you'll want to turn them off. This includes various WITNESS- 15 related kernel options, INVARIANTS, malloc debugging flags 16 in userland, and various verbose features in the kernel. Many 17 developers choose to disable these features on build machines 18 to maximize performance. 19 2020030728: 21 All current USB and Firewire quirks in da(4) have been deprecated 22 and will be removed for 5.2. If this causes failure for your 23 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 24 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 25 so the quirk can be re-enabled. 26 2720030722: 28 FPU-less support has been removed from FreeBSD. Chances are you won't 29 notice. 386+387 support should still work after this change, but 30 it is now a minimum requirement for the i386 port that you have real 31 FPU hardware. 32 3320030714: 34 Some people are having problems with changes related to /rescue. 35 If you are building -j N, you will need to define NO_RESCUE. Others 36 will need to define it if /rescue has issues with their environment. 37 People should report those issues to current@. 38 3920030711: 40 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 41 across this point. Further, it might be a good idea to remove 42 /usr/obj. 43 4420030613: [retrospective] 45 There was a small window in which sed(1) was broken. If you 46 happen to have sed(1) installed during that window, which is 47 evidenced by an inability to build world with the failure 48 given below, you need to manually build and install sed(1) 49 (and only sed(1)) before doing anything else. This is a one- 50 time snafu. Typical failure mode: 51 52 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 53 targmatch.h:7:1: null character(s) ignored 54 targmatch.h:12:1: null character(s) ignored 55 targmatch.h:16:1: null character(s) ignored 56 : 57 58 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 59 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 60 usr.bin/sed/process.c). 61 6220030610: 63 Remove deprecated locale names and transition period code 64 for them, finishing switching to the new scheme. Check your 65 LANG environment variable. 66 6720030609: 68 CCD has been changed to be a fully GEOMified class. Kernel 69 and ccdconfig(8) needs to be in sync, this is particularly 70 important to remember beforehand if your source tree is on 71 a ccd device. Consider making a copy of the old ccdconfig 72 into /boot/kernel.good or wherever you keep your backup 73 kernel. 74 7520030505: 76 Kerberos 5 (Heimdal) is now built by default. Setting 77 MAKE_KERBEROS5 no longer has any effect. If you do NOT 78 want the "base" Kerberos 5, you need to set NO_KERBEROS. 79 8020030502: 81 groff has been updated. If you try to do a buildworld and 82 get an infinite loop in troff, update to May 4th or newer. If you 83 have a newer kernel than userland, you may need to set the OSRELDATE 84 to 500110 in your environment before starting a buildworld. 85 8620030501: 87 The old rc system has been removed. Please report any problems 88 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 89 Your personal versions of these files will not be removed, so you can 90 continue to use them. However, you should take great care when updating, 91 especially when using mergemaster, since the compatibility code that 92 utilizes these old scripts has also been removed. 93 9420030423: 95 A bug has been fixed in /dev/devctl which would cause devd 96 to hang on boot, were it not for a workaround in devd. The 97 work around in devd will be removed around 20030507. You 98 have until then to upgrade your kernel before updating 99 userland. In general, you should have a userland and 100 kernel that's in sync with each other. However, given the 101 effects of this bug (hang on boot when starting devd), some 102 allowances are made. 103 10420030329: 105 Alphas with libc from between 20030312 and 20030329 exhibit 106 floating point exceptions (FPEs), most notably in awk(1) 107 while upgrading the system through a buildworld. 108 109 So, to successfully upgrade your Alpha, you must either 110 downgrade your libc.so to a pre-20030312 version, or update 111 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 112 to CFLAGS, then forcibly rebuild and install libc: 113 114 cd /usr/src/lib/libc && \ 115 make cleandir && make obj && \ 116 make -DNOMAN -DNOPROFILE all && \ 117 make -DNOMAN -DNOPROFILE install 118 11920030208: 120 sendmail 8.12.7 has been imported. It has one important 121 change for IPv6 users. The default submit.mc now uses 122 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 123 used to connect to the MTA. Users on IPv6-only machines 124 will need to edit /etc/mail/submit.mc appropriately. 125 12620030128: 127 NODEVFS option has been removed and DEVFS thereby made standard. 128 This makes all references to MAKEDEV obsolete, and they should 129 be removed when convenient. 130 13120030126: 132 The name of the device for the ofw console has changed, sparc64 users 133 must run mergemaster to update their installed /etc/ttys. 134 13520030125: 136 The scheduler framework has grown a second scheduler and consequently 137 you must specify one and only one scheduler in your kernel config. 138 The cvs config files have been updated to use the old scheduler 139 which may be selected via 'options SCHED_4BSD'. If you would like 140 to try the new, much more experimental, scheduler please try 141 'options SCHED_ULE' and contribute to the arch@ discussion. 142 14320030115: 144 A new version of the wi driver has been imported into the tree. 145 One now must have device wlan in the config file for it to operate 146 properly. 147 148 In addition, there have been some changes to how wi devices are 149 configured for point to point links to bring it more in line 150 with the former way of doing things, as well as compatibility 151 with NetBSD. 152 15320021222: 154 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 155 used an incompatible form of ABI for returning structures and unions 156 which FreeBSD's GCC maintainers were not aware of relative to previous 157 versions of FreeBSD. We have gone back to the ABI for now, and any 158 code compiled which is required to interoperate with other code (not 159 built at the same time) returning structs or unions should be 160 rebuilt. 161 16220021216: 163 A name change in /etc/netconfig has been reverted to stay 164 compatible with suns TIRPC and also with NetBSD. You need 165 to run mergemaster after make world. A new libc does still work 166 with an outdated /etc/netconfig for some time, but you'll get 167 a warning. This warning will be removed in 20030301. 168 16920021202: 170 The recent binutils upgrade marks a kernel flag day on 171 sparc64: modules built with the old binutils will not work 172 with new kernels and vice versa. Mismatches will result in 173 panics. Make sure your kernel and modules are in sync. 174 17520021029: 176 The value of IPPROTO_DIVERT has changed. Make sure to keep 177 your kernel, netstat, natd and any third-party DIVERT 178 consumers in sync. 179 18020021024: 181 Old, compatibility slices have been removed in GEOM kernels. 182 This means that you will have to update your /etc/fstab to 183 not use disk devices of the form /dev/ad0a. Instead, you 184 now must specify /dev/ad0s1a, or whatever slice your FreeBSD 185 partition really is on. The old device names have gone 186 away, so if you use them anywhere else, you must also adjust 187 those uses. (This doesn't affect the disks formatted in 188 the ``dangerously-dedicated'' mode.) 189 19020021023: 191 Alphas with kernels from between 20020830 and 20021023 and/or 192 rtld (ld-elf.so.1) older than 20021023 may experience problems 193 with groff while doing a buildworld (kernel: "out of memory", 194 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 195 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 196 197 So, to successfully upgrade your Alpha, you must either 198 upgrade your kernel and rtld first (which might be a bit 199 tricky), or avoid running the bootstrapped groff during the 200 "transitional" buildworld. To avoid running groff during the 201 transitional upgrade run make buildworld with -DNOMAN, 202 -DNO_SHAREDOCS, and -DNO_LPR. 203 20420020831: 205 gcc has been upgraded to 3.2. It is not all binary compatible 206 with earlier versions of gcc for c++ programs. All c++ 207 programs and libraries need to be recompiled. 208 209 Also, if you encounter g++ issues, rm /usr/include/g++/* before 210 doing an installworld to make sure that stale files are removed. 211 21220020827: 213 Our /etc/termcap now has all the entries from the XFree86 xterm 214 almost unchanged. This means xterm now supports color by default. 215 If you used TERM=xterm-color in the past you now should use 216 TERM=xterm. (xterm-color will lead to benign warnings). 217 21820020815: 219 A "bug" in gcc(1) that was hiding warning in system headers was 220 fixed. It's probably time to add -DNO_WERROR to your make line 221 again. 222 22320020729: 224 COPY is being deprecated. The 20010530 change was reverted, as 225 it causes far more pain than was expected, and to always compare 226 before installing, please use INSTALL="install -C" again. The 227 -C option is now silently ignored when used with the -d option. 228 22920020702: 230 Problems with libc_r clients like KDE and GNOME have been resolved. 231 There are still some minor problems with some signals but the 232 system is stable enough for general use again. SMP is less so than UP 233 but each can successfully complete multiple buildworlds. 234 Libkvm needs to be recompiled due to KSE. 235 23620020701: 237 Now would be a bad time to upgrade. Something in or near the 238 KSE commit totally broke programs using libc_r like KDE and 239 GNOME. 240 24120020511: 242 The k5su utility installed as part of Kerberos 5 is no longer 243 installed with the set-user-ID bit set by default. Add 244 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 245 with the set-user-ID bit set. 246 24720020510: 248 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 249 Unfortunately our native GDB (at version 4.18) does not understand 250 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 251 generated debugging information for our native GDB. 252 25320020510: 254 Due to the way CVS works, it may not properly update src/contrib/gcc 255 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 256 and then do a cvs update. 257 25820020421: 259 When exec'ing set[ug]id executables, the kernel now ensures that the 260 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 261 26220020404: 263 New sendmail startup scripts have been installed to make it 264 easier to use alternative MTAs with FreeBSD. Setting the rc.conf 265 variable sendmail_enable to "NO" no longer prevents any sendmail 266 daemons from starting. Instead, either set sendmail_enable to 267 "NONE" or change mta_start_script to a script for starting 268 an alternative MTA. Setting mta_start_script to "" will 269 also prevent any MTA from being started at boot. 270 27120020403: 272 UCONSOLE is no longer a valid kernel option. 273 27420020315: 275 FreeBSD 5.0 DP-1 was basically branched today. 276 27720020225: 278 Warnings are now errors in the kernel. Unless you are a developer, 279 you should add -DNO_WERROR to your make line. 280 28120020217: 282 sendmail 8.12.2 has been imported. The sendmail binary is no 283 longer a set-user-ID root binary and the infrastructure to support 284 command line mail submission has changed. Be sure to run 285 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 286 and /etc/mail) and read /etc/mail/README for more details. 287 288 Due to the import of sendmail 8.12.2, a new user and group are 289 required in order for sendmail to run as a set-group-ID 290 binary. A 'make installworld' will use the new user and group 291 to set the owner and group of /var/spool/clientmqueue and will 292 fail if the new user and group do not exist. The 'smmsp' user 293 and group must be merged from src/etc/group and 294 src/etc/master.passwd before using 'make installworld'. 295 'mergemaster -p' will do this. You may need to install 296 mergemaster before this will work if you are updating from a 297 very old version of current. The updating recipe has changed 298 as of this date. 299 30020020112: 301 The preferred configuration method for PAM is now /etc/pam.d/ 302 rather than /etc/pam.conf. If you have an unmodified 303 pam.conf, just delete it after your next mergemaster run. If 304 you have local modifications, you can use 305 /usr/src/etc/pam.d/convert.pl to incorporate them into your 306 /etc/pam.d. 307 308 Please see the following url for more details: 309http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 31020011229: 311 If anyone here is already using the new rc.conf(5) variable 312 networkfs_types, please note that it has changed 313http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 314 31520011220: 316 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 317 started out its life in the ISDN4BSD project as an offspring 318 from sys/net/if_spppsubr.c, which eventually got a life of its 319 own. All the accumulated features and bugfixes of the i4b 320 version have now been merged back into the base system's 321 version now. The only user-visible change resulting from this 322 is that i4b's sppp(4) interfaces are to be managed with 323 spppcontrol(8) again, since ispppcontrol(8) has been retired 324 as well. (There has never been rc file support for 325 ispppcontrol in -current, but only in -stable. That will be 326 reverted by the time the changes are MFCed.) 327 32820011215: 329 The fdc(4) driver has been updated and now automatically 330 recognizes media in `standard' formats (like 1440 KB and 331 720 KB for a 3.5" high-density drive) when accessing the 332 default device node (e. g. /dev/fd0). The old variety of 333 floppy device nodes /dev/fd*.* is no longer present by 334 default, devices can be created (in DEVFS) on demand. They 335 will need to be customized then for `odd' densities using 336 fdcontrol(8). 337 33820011209: 339 The bugs in procfs' debugging support code have been fixed, 340 and truss(1) now works again. 341 34220011207: 343 Daily security checks have been split out to use the periodic(8) 344 scripts. Some change in configuration may be necessary. Please 345 see 346http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 347 for details. 348 34920011204: 350 sos added VCD/SVCD support to ata driver and that needs the 351 kernel and burncd to be in sync. 352 35320011203: 354 The procfs pseudo-filesystem has now been converted to use the 355 pseudofs framework. If you have 'options PROCFS' in your 356 kernel config, you'll need to add 'options PSEUDOFS' if it's 357 not there already. 358 359 This change temporarily breaks truss(1); use ktrace(1) instead 360 until the issue has been resolved. 361 36220011202: 363 A security hole in OpenSSH involving `UseLogin yes' has been 364 patched. 365 36620011126: 367 You need to remove /usr/obj/.../usr.bin/tip before rebuilding 368 after this date. You need to do this only once. 369 37020011103: 371 Most of the awk issues have been resolved. Some rough 372 edges may be left, but for the most part things should be 373 back to "normal." For CURRENT's usual definition of "normal." 374 37520011030: 376 Awk has been upgraded to the one true awk from bell labs. Expect 377 choppy waves in the upgrade process. 378 37920011030: 380 The asr driver problem has been resolved. 381 38220011027: 383 Due to changes in other parts of the system, the asr driver 384 now causes the system to panic on boot. Do not use it pending 385 correction. Comment it out of any kernel config file that you 386 try to use from this date forward. 387 38820011025: 389 When crossbuilding, use TARGET=xxx where you used to use 390 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 391 unless you are changing both of them. To cross build pc98 on 392 an alpha, for example, you need to set TARGET=pc98 and 393 TARGET_ARCH=i386. 394 39520011001: 396 The kernel interface that burncd depends on has changed. 397 You must recompile both the kernel and userland applications 398 at the same time. 399 40020010929: 401 When crossbuilding, please set TARGET_ARCH rather than 402 MACHINE_ARCH to indicate the target. In the future, one will 403 set TARGET_MACHINE where you set MACHINE now. At the moment, 404 setting MACHINE alone for same MACHINE_ARCH machines works 405 (eg, you can build pc98 on an i386 machine and vice versa). 406 40720010927: 408 Some weird problems result from using ACPI on some machines. 409 To disable ACPI you can add 410 hint.acpi.0.disabled="1" 411 to /boot/loader.conf (or by putting set X=Y at the boot 412 loader "ok" prompt). 413 414 Alternatively, you can remove it from /boot/kernel/acpi.ko 415 or use the MODULES_OVERRIDE function in your kernel config 416 file and not list acpi in that list. 417 41820010924: 419 The buildworld has been fixed. You may need to install 420 the 4.x compatibility libraries for some old binaries 421 to work. Add COMPAT4X=true to your /etc/make.conf to 422 get them installed on every installworld, or execute the 423 following to get them installed only once: 424 cd src/lib/compat/compat4x.<arch> 425 make all install 426 You will see ``__stdoutp undefined'' until you do this. 427 42820010919: 429 There's a bug in the world build process. The cross-tools 430 are build with the NEW headers, but the OLD libc.a. This 431 leads to all kinds of problems with the new libc. A temporary 432 workaround is to add 433 CFLAGS="-O -pipe -D_OLD_STDIO" 434 before building world when upgrading from 4.x to current. This 435 can be removed afterwards. 436 437 A proper fix to the buildworld target is needed. 438 43920010918: 440 Peter has committed his new kthread nfs client/server code. 441 NFS may be unstable after this date. 442 44320010912: 444 KSE has hit the tree. Lots of things are now different in 445 the kernel. While a few problems were introduced in the 446 initial commit, most of the major ones have been found and 447 corrected. 448 44920010901: 450 In OLDCARD, CardBus bridges appear to be stable. The work 451 arounds described in the 20010604 entry are now no longer 452 necessary and will be ignored. Most insert/remove problems 453 have been rectified around this date. 454 45520010823: 456 named now runs as user bind and group bind rather than as 457 root. If named_enable is set to YES in /etc/rc.conf, ensure 458 that user bind is available in /etc/passwd (using vipw(8)) 459 and that group bind is available in /etc/group. Also make 460 sure that user or group bind has read (and not write) 461 permission for your name server configuration and that it 462 has read and write permission for your slave zone files and 463 directory. 464 465 If you wish to continue to run named as root (a less secure 466 alternative), add a line to /etc/rc.conf saying 467 468 named_flags= 469 47020010709: 471 The PAM libraries have had an API upgrade that is beyond 472 the ability of the shared library major number to handle. 473 It is manifested by PAM-using ports dumping core. The 474 solution is to rebuild those ports. 475 47620010628: 477 The kernel compile module has moved from src/sys/compile/FOO 478 to src/sys/${MACHINE}/compile/FOO. 479 48020010625: 481 The pccard modem issue from 20010613 has been corrected. 482 OLDCARD support is still a little weak in -current. slot 1 is 483 known not to work on some TI based cardbus bridges. Some 484 cardbus bridges do not properly detect insert/removal events. 485 IRQ configuration needs more safety belts. 486 48720010617: 488 Softupdates problems have been corrected. 489 49020010614: 491 Peter ripped out the linkerset support. You must, as always, 492 rerun config after you cvsup if you are using the traditional 493 kernel building methods. 494 49520010613: 496 pccard modems may not work with current after 20010604 date. Some 497 do, others result in panics. *MAKE*SURE* that you update your 498 config and /etc/rc.conf ala the 20010604 entry, or you will have 499 problems (this issue will be fixed, it just hasn't been yet). 500 50120010613: 502 SOFTUPDATES seem to be broken since the middle of May or so. Do not 503 use them in current. You can disable softupdates on all mounted 504 partitions, or remove SOFTUPDATES the kernel config file. 505 50620010612: 507 After Peter's commits to the hints code, people have been noticing 508 that certain devices are attached (or try to) twice. This is due 509 to having both static hints as well as a /boot/device.hints. To 510 work around this issue, please use only one or the other mechanism 511 until this bug is fixed. 512 513 Please note that a feature of config is that if you have config 514 file FOO and FOO.hints, it automatically adds FOO.hints to the 515 hints.c file, whether you want it to or not. 516 51720010610: 518 Locale names have changed to match other systems better. 519 52020010604: 521 pccard support for pci cards has been committed. You must change 522 your /etc/pccard.conf irq lines. It must match the irq used by 523 pcic device. Interrupt storms may result if you fail to do this. 524 Interrupt storms look a lot like a hang. 525 526 You must also install a new pccardd, otherwise you will get an 527 interrupt storm at card reset time (just after it tells you what 528 it is). 529 530 pccardd_flags="-I" is necessary for the time being. It tells pccardd 531 not to ask the kernel if the interrupt is really free or not before 532 using it. You can either change the /etc/pccard.conf irq lines to 533 match pcic, or add "-i X" to the pccardd_flags. 534 53520010530: 536 INSTALL=install -C is being deprecated. If you want to do this, 537 use COPY=-C instead. The former method will be supported for only 538 a limited time. If you see 539 540install: warning: the -d and -C options may not be specified together 541 542 in your makeworld, then you need to migrate towards using 543 COPY=-C. 544 54520010525: 546 It appears that vm is now stable enough to use again. However, 547 there may be other problems, so caution is still urged. alpha 548 definitely is in bad shape. 549 55020010521: 551 Minor repo damage has happened. This may cause problems 552 with cvsup of ports. If you get errors, please see 553 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 554 at the bottom for details on a workaround. The error message 555 is 556Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 557 55820010520: 559 Vm and/or swapping are busted on -current. Please be patient. 560 56120010519: 562 pccard has had much reorganizational work done to it over 563 the past few days. Everything should still work, but if 564 not, please contact imp@freebsd.org. 565 56620010517: 567 ata ioctl changed. Make sure to recompile both kernel and 568 userland at the same time. 569 57020010517: 571 New ncurses imported. 572 57320010512: 574 DEVFS is now opt out, not opt in. Barring major problems, this 575 will be the only way to go starting July 1. 576 57720010504: 578 OpenSSH has been updated to 2.9. Some defaults are different, 579 including RhostsRSAAuthentication, which changes from yes to no. 580 58120010502: 582 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 583 58420010501: 585 Building perl was broken at 02:25:25 PDT. 586 58720010430: 588 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 589 go back in the water. 590 59120010429: 592 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 593 this date, but before the correction date. 594 59520010423: 596 old fsck and new kernel interactions appear to have been fixed. 597 59820010411: 599 fsck and the kernel were changed to handle some optimizations 600 to directory layout. This breaks backward compatibility. 601 Update only if you understand that you must not use the old 602 fsck with the new kernel ever. 603 60420010330: 605 fsck has changed the meaning of the pass column in /etc/fstab. 606 Please see the cvs commit to fsck.8 or the fsck.8 man page for 607 details. It is unclear if changes to /etc/fstab are necessary. 608 60920010319: 610 portmap had changed name to rpcbind for maximum POLA in your 611 current world. /etc/hosts.{allow,deny} needs changes. nfs and 612 other rpc based programs that rely on portmapper will not work 613 without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 614 61520010315: 616 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 617 and ATA_ENABLE_TAGS are no longer kernel options. They have 618 been replaced by tunables. See ata.4 for details. 619 62020010312: 621 The fxp driver was converted to use miibus. If you compile 622 fxp into your kernel statically, you will need to add miibus. 623 62420010312: 625 The wi device now defaults to BSS (infrastructure) mode 626 instead of ad-hoc. 627 62820010310: 629 /dev/urandom should be a symbolic link to /dev/random now. 630 Users of current not using DEVFS need to run MAKEDEV std. 631 ssh might not work if you don't. 632 63320010303: 634 The ed driver has been updated. It now allows mii attachments, 635 which means that you must include the miibus in your kernel if 636 you use the ed driver. 637 63820010220: 639 The problems with libc have been corrected. It is now mostly 640 safe to go back into the water. 641 64220010211: 643 The size of FILE was changed. This breaks upgrading. If 644 you must upgrade, be prepared for pain. It also breaks almost 645 all binaries that you've compiled on -current. You are warned 646 that before upgrading would be a good time to do a level 0 647 dump of your system. No, really, I mean it this time. 648 649 To get to the new system, you'll need to use the following 650 workaround. Hopefully this can be sorted out so that we 651 don't have to move this to the updating section. 652 653 To get around the installworld problem, do: 654 # cd /usr/src/usr.bin/sed 655 # make install 656 # cd /usr/src 657 # make installworld 658 If that doesn't work, then try: 659 # make -k installworld 660 # make installworld 661 66220010207: 663 DEVFS is now the default. If you use vinum, make sure that you 664 do not include devfs in your kernel as problems result. 665 66620010205: 667 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 668 Remove them from your config. 669 67020010122: 671 ****************************** WARNING ****************************** 672 buildkernel has been changed slightly 673 ****************************** WARNING ****************************** 674 KERNCONF replaces the variable KERNEL for buildkernel. You 675 should update your scripts and make.conf accordingly. 676 67720010119: 678 config has changed to allow DEV_FOO as a replacement for NFOO. 679 This requires a new config to build correctly. 680 68120010116: 682 The kernel option I386_CPU is now mutually exclusive with the 683 other cpu types. If you have an i386 system, be sure that it 684 only had this line. Remove it for all other configurations. 685 68620010110: 687 Changes to the kernel require it and burncd be in sync. 688 68920010102: 690 Everyone who has hw.sndunit set to something in 691 /etc/sysctl.conf, it is now hw.snd.unit. 692 69320010101: 694 ex and vi were broken by some changes to sys/queue.h. If you 695 have a bad vi, you will see make buildworld fail with a core 696 dump while building termcap. You can work around this problem 697 by adding -k to your make buildworld. This will cause the 698 build to complete and install a new vi. Once that's done, you 699 can rebuild again without the -k to pick up anything that 700 might have been ignored by the -k option. 701 702 Others have suggested that you can just rebuild libc if your 703 vi/ex is dynamically linked, but I've not received any reports 704 of this working. 705 70620001228: 707 There have been some changes to libcrypt in -current. The 708 libscrypt/libdescrypt symlink silliness is gone and the installed 709 libcrypt is fully functional. Be aware of this. 710 71120001218: 712 Linksys Fast Ethernet PCCARD cards supported by the ed driver 713 now require the addition of flag 0x80000 to their config line 714 in pccard.conf(5). This flag is not optional. These Linksys 715 cards will not be recognized without it. 716 71720001205: 718 Important new FreeBSD-version stuff: PAM support has been worked 719 in, partially from the "Unix" OpenSSH version. This requires 720 adding the following in pam.conf: 721 722 sshd auth sufficient pam_skey.so 723 sshd auth required pam_unix.so try_first_pass 724 sshd session required pam_permit.so 725 72620001031: 727 cvs updated to 1.11. 728 72920001020: 730 The random device needs more entropy, so you need to make sure 731 that you've run mergemaster to get a /etc/rc which will seed 732 /dev/random. If you don't and the system hangs after ldconfig, 733 then banging on the keyboard randomly until it unhangs is one 734 workaround. 735 73620001010: 737 ****************************** WARNING ****************************** 738 Sendmail has been updated. 739 ****************************** WARNING ****************************** 740 o mail.local(8) is no longer installed as a set-user-id binary. 741 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 742 is set. 743 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 744 commands. 745 o Now using sendmail's version of vacation(1). 746 o The sendmail cf building tools (contrib/sendmail/cf) are installed 747 in /usr/share/sendmail/cf. 748 o sendmail.cw changed to local-host-names 749 750 More details can be found at 751 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 752 75320001009: 754 The ports tree's new layout is in place. Be sure to update 755 your entire ports tree, or you will have problems. 756 75720001006: 758 The perl build procedure no longer installs miniperl, nor uses 759 the installed miniperl. It is recommended that you delete 760 /usr/bin/miniperl. 761 76220001005: 763 This weekend the ports tree will be updated to a new layout. 764 It will be in an inconsistent state until noted in the UPDATING 765 file, or with asami-san's message to the relevant mailing 766 lists. With this new layout, you'll need to update the whole 767 tree for anything to work. 768 76920000928: 770 There was a change in the passwd format. Need more information. 771 77220000916: 773 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 774 place. Please update boot loader (not the boot blocks) at the 775 same time as your kernel. 776 77720000914: 778 The new pmtimer device is necessary for laptops. Failure to 779 include the device will cause suspended laptops losing time 780 when they resume. Include 781 device pmtimer 782 in your config file and 783 hint.pmtimer.0.at="isa" 784 to your /boot/device.hints file. 785 78620000911: 787 The random device has been turned into a (pseudo-)device, 788 rather than an option. The supplied kernel config files have 789 been updated. You will need to do something similar in your 790 own kernel config file. 791 Remove: 792 options RANDOMDEV 793 Add: 794 device random 795 If you prefer to load the loadable module, you need to do 796 nothing. 797 79820000909: 799 The random device module has been renamed from randomdev.ko to 800 random.ko. You will need to edit your /boot/loader.conf to 801 reflect this if you load this module at boot time. 802 The line should read: 803 random_load="YES" 804 80520000907: 806 The SMPNG commit has happened. It should work, but if it 807 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 808 to be a variety of minor issues. Please see 20000905 to make 809 sure you don't have model loading problems which might at 810 first blush appear related to SMP. 811 81220000906: 813 nsswitch has been imported from NetBSD. Among other things, 814 this means that /etc/host.conf is no longer used. See 815 nsswitch.conf(5) instead. Note that at boot time rc.network 816 will attempt to produce a new nsswitch.conf file for you if you 817 don't have one, and you have host.conf. 818 81920000905: 820 The ucred structure changed size. This breaks the interface 821 that mountd uses. Trying to use an older mountd with a newer 822 kernel guarantees a panic. This means that you need to use 823 kernels newer than today only with matching mountd, but you 824 needed to do that anyway with the boot loader changes. 825 82620000905: 827 The boot loader has been updated. The new default kernel is 828 now /boot/kernel/kernel.ko. The new default module location 829 is /boot/kernel. 830 831 You *MUST* upgrade your boot loader and kernel at the same time. 832 The easiest way to do this is to do the buildworld/buildkernel/ 833 installkernel/installworld dance. 834 835 Furthermore, you are urged to delete your old /modules directory 836 before booting the new kernel, since kldload will find stale 837 modules in that directory instead of finding them in the correct 838 path, /boot/kernel. The most common complaint that this cures 839 is that the linux module crashes your machine after the update. 840 841 if [ ! -d /boot/kernel.old ]; then 842 mv /modules.old /boot/kernel.old 843 chflags noschg /kernel.old 844 mv /kernel.old /boot/kernel.old/kernel.ko 845 chflags schg /boot/kernel.old/kernel.ko 846 fi 847 84820000904: 849 A new issue with the sendmail upgrade has come to light. 850 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 851 incorrectly install the default aliases in /etc/mail rather than 852 move the old one from /etc. So you'll need to manually move the 853 file, create a symbolic link, remove the old /etc/aliases.db and 854 run newaliases. For safety sake, you should stop sendmail 855 while doing this and run the upgrade when locally sourced email 856 is not likely to be generated. 857 85820000825: 859 /boot/device.hints is now required for installkernel to 860 succeed. You should copy GENERIC.hints for your architecture 861 into /boot/device.hints. If and only if you compile hints 862 into your kernel, then this file may be empty. Please note, 863 if you have an empty or missing /boot/device.hints file and 864 you neglected to compile hints into your kernel, no boot 865 messages will appear after the boot loader tries to start the 866 kernel. 867 86820000821: 869 If you do NOT have ``options RANDOMDEV'' in your kernel and 870 you DO want the random device then add randomdev_load="YES" to 871 /boot/loader.conf. 872 87320000812: 874 suidperl is now always built and installed on the system, but 875 with permissions of 511. If you have applications that use 876 this program, you are now required to add ENABLE_SUIDPERL=true 877 to /etc/make.conf. If you forget to do this, 878 chmod 4511 /usr/bin/suidperl 879 will fix this until the next build. 880 88120000812: 882 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 883 visible changes that may immediately affect your configuration 884 include: 885 - New default file locations from src/contrib/sendmail/cf/README 886 - newaliases limited to root and trusted users 887 - MSA port (587) turned on by default 888 - New queue file naming system so can't go from 8.11 -> 8.9 889 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 890 - FEATURE(`nullclient') is more full featured 891 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 892 - mail.local FreeBSD-only -b option changed to -B 893 - See src/contrib/sendmail/RELEASE_NOTES for more info 894 89520000810: 896 suidperl (aka sperl) is no longer build by default. You must 897 specifically define BUILD_SUIDPERL to "true" for it to be build. 898 Furthermore, we recommend that you remove /usr/bin/sperl* and 899 /usr/bin/suidperl files from your system unless you have a 900 specific use for it. 901 90220000729: 903 Networking defaults have been tightened. Anybody upgrading 904 /etc/defaults/rc.conf needs to add the following lines to 905 /etc/rc.conf if they want to have the same setup 906 afterwards (unless the variables already are set, of course): 907 # Enable network daemons for user convenience. 908 inetd_enable="YES" 909 portmap_enable="YES" 910 sendmail_enable="YES" 911 91220000728: 913 If you have null_load="YES" in your /boot/loader.conf, you 914 will need to change that to nullfs_load="YES". 915 91620000728: 917 The "installkernel" target has changed slightly. Now even if 918 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 919 it will install the MYKERNEL file (built with the buildkernel 920 target) as /kernel rather than /MYKERNEL. Those who have 921 updated their /boot/loader.conf files to point to /MYKERNEL 922 should remove that entry or perform manual rename of /kernel 923 to /MYKERNEL. 924 92520000711: 926 If you use CVSUP or CTM to get CVS trees, AND you used to get 927 the old crypto files from internat.freebsd.org AND you check 928 out files from the CVS tree with the cvs command, please read 929 http://people.freebsd.org/~imp/internat.txt 930 for details on potential problems that you might have and how 931 to get around them. 932 933 If you are merely a mirror, or don't answer yes to each of the 934 clauses above, you needn't worry. 935 93620000711: 937 /etc/security has been updated to print the inode number of 938 setuid programs that have changed. You will see a large spike 939 in the number of changed programs the first time when you run 940 mergemaster to get a new /etc/security. 941 94220000710: 943 /dev/random now has good entropy collection (from the keyboard 944 and sysmouse drivers). Please ensure that either `options 945 RANDOMDEV' is present in your kernel config file or that 946 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 947 not have the /dev/random driver, OpenSSL (and consequently 948 lots of crypto tools (like SSH)) will fail with strange 949 errors. (see below, 20000624). 950 951 FreeBSD-current is safe again to run Crypto. 952 95320000709: 954 phk made the malloc default options AJ. This may slow things 955 down and uncover other latent bugs in the code. If you need to 956 run at full speed, you can disable this by doing the following: 957 ln -s aj /etc/malloc.conf 958 95920000706: 960 libftpio's version was accidentally bumped a few days ago. This 961 has been corrected. You may need to remove /usr/lib/libftpio.so.6 962 before doing your next buildworld/installworld pair. It certainly 963 won't hurt to remove it before the update procedure. It will 964 break fetch until a new one is built, but ftp can be used in the 965 interim if needed. 966 96720000705: 968 The crypto packages have changed for the cvsup. This has been done 969 in a backward compatible way, but the old packages will go away at 970 some point in the future. Look at /usr/share/examples/cvsup for 971 details. 972 97320000704: 974 With the new sys/modules/sound/drivers/*, you will need to 975 set SYSDIR until you do an installworld after July 7th. 976 97720000704: 978 rc.shutdown and rc will now call the rc.d scripts with start 979 or stop. This may cause some harmless warnings from older 980 rc.d scripts that haven't been updated. 981 98220000630: 983 The libfetch based version of fetch has gone into the tree. 984 Minor problems may result on some of the less popular sites, 985 which should be reported to des@freebsd.org. 986 98720000625: 988 From approximately this date forward, one must have the crypto 989 system installed in order to build the system and kernel. 990 While not technically strictly true, one should treat it as 991 required and grab the crypto bits. If you are grabbing CVS 992 trees, src-all and cvs-crypto should be treated as if they 993 were required. You should check with the latest collections 994 to make sure that these haven't changed. 995 99620000624: 997 Mark Murray just committed the first parts of a cleanup of 998 /dev/zero, et al. This is also cleaning up /dev/random. 999 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 1000 -CURRENT FROM THIS POINT to 2000710 for cryptographic services 1001 until Mark can merge in the fixes to this work in progress. 1002 openssh and openssl should not be used to generate keys from this 1003 date to the completion of the work. 1004 1005 If you must operate at this reduced level of security, add ' 1006 options RANDOMDEV' to your kernel or modload the randomdev 1007 module. You may also need to copy a new MAKEDEV to /dev and 1008 recreate the random and urandom devices. 1009 101020000622: 1011 The license on the softupdates is now a standard 2 clause 1012 BSD license. You may need to remove your symbolic links 1013 that used to be required when updating. 1014 101520000621: 1016 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 1017 the config file update procedure. 1018 http://people.freebsd.org/~imp/config-upd.html 1019 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 1020 isn't buildable. However, you can generate a LINT file: 1021 cd /sys/<ARCH>/conf && make LINT 1022 102320000620: 1024 Binutils 2.10 have hit the tree, or will shortly. As soon 1025 as they do, the problem noted in 20000522 will be resolved and 1026 that workaround will no longer be required. 1027 102820000615: 1029 phk removed the compatibility creation of wd devices in the 1030 ad driver. If you haven't done so already, you must update 1031 your fstab, etc to use the ad devices instead of the wd 1032 devices. 1033 1034 In addition, you'll need to update your boot blocks to a 1035 more modern version, if you haven't already done so. Modern 1036 here means 4.0 release or newer (although older releases 1037 may work). 1038 103920000612: 1040 Peter took an axe to config(8). Be sure that you read his mail 1041 on the topic before even thinking about updating. You will 1042 need to create a /boot/device.hints or add a hints directive 1043 to your config file to compile them in statically. The format 1044 of the config file has changed as well. Please see GENERIC or 1045 NEWCARD for examples of the new format. 1046 1047 Indirectly, this also breaks USERCONFIG. Unless a newer entry 1048 says that it has been fixed, assume that must use the hints mechanism 1049 in the loader if you need to use a machine with very old ISA cards 1050 in it. 1051 105220000522: 1053 A new set of binutils went into the tree today. Anybody 1054 building a kernel after this point is advised that they need 1055 to rebuild their binutils (or better yet do a 1056 buildworld/installworld) before building a new kernel. 1057 1058 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1059 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1060 is recommended that you don't set this option until the problem 1061 is resolved. 1062 106320000513: 1064 The ethernet drivers were all updated to clean up the BPF handling. 1065 106620000510: 1067 The problems with boot blocks on the alphas have been corrected. 1068 This will require some care in updating alphas. A new libstand 1069 is requires for the boot blocks to build properly. 1070 107120000503: 1072 Recompile all kld modules. Proper version dependency info 1073 is now available. 1074 107520000502: 1076 Modules have been disconnected from the buildworld tree and 1077 connected to the kernel building instead. 1078 107920000427: 1080 You may need to build gperf 1081 cd /usr/src/gnu/usr.bin/gperf && make depend all install 1082 when upgrading from 4.0 -> current. The build system now uses 1083 an option only in -current. 1084 108520000417: 1086 The method that we brand ELF binaries has changed to be more 1087 acceptable to the binutils maintainers. You will need to 1088 rebrand your ELF binaries that aren't native. One problem 1089 binary is the Linux ldconfig. After your make world, but 1090 before you reboot, you'll need to issue: 1091 brandelf -t Linux /compat/linux/sbin/ldconfig 1092 if you have Linux compatibility enabled on your machine. 1093 109420000320: 1095 If you have really bad/marginal IDE drives, you may find they 1096 don't work well. Use pio mode instead. The easiest way to 1097 cope if you have a problem combination is to add: 1098 /sbin/sysctl hw.ata.ata_dma=0 1099 to the start of /etc/rc.conf. 1100 110120000319: 1102 The ISA and PCI compatibility shims have been connected to the 1103 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1104 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1105 include the appropriate option in your kernel config. Drivers 1106 using the shims should be updated or they won't ship with 1107 5.0-RELEASE, targeted for 2001. 1108 110920000318: 1110 We've entered the traditional post release dumping party. 1111 Large kernel changes are being committed and are in the 1112 works. It is important to keep the systems' klds and kernel 1113 in sync as kernel interfaces and structures are changing. 1114 Before reporting kernel panics, make sure that all modules 1115 that you are loading are up to date. 1116 111720000315: 1118 If you are upgrading from an older version of FreeBSD, you 1119 need to update your boot blocks as well. 'disklabel -B ad0' 1120 will do the trick. This isn't critical until you remove your 1121 wd device entries in /dev, at which point your system will not 1122 boot. 1123 112420000315: 1125 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 1126 to upgrade to 4.0 from 3.x. 1127 1128COMMON ITEMS: 1129 1130 General Notes 1131 ------------- 1132 Avoid using make -j when upgrading. From time to time in the 1133 past there have been problems using -j with buildworld and/or 1134 installworld. This is especially true when upgrading between 1135 "distant" versions (eg one that cross a major release boundary 1136 or several minor releases, or when several months have passed 1137 on the -current branch). 1138 1139 Sometimes, obscure build problems are the result of environment 1140 poisoning. This can happen because the make utility reads its 1141 environment when searching for values for global variables. 1142 To run your build attempts in an "environmental clean room", 1143 prefix all make commands with 'env -i '. See the env(1) manual 1144 page for more details. 1145 1146 To build a kernel 1147 ----------------- 1148 If you are updating from a prior version of FreeBSD (even one just 1149 a few days old), you should follow this procedure. With a 1150 /usr/obj tree with a fresh buildworld, 1151 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1152 make installkernel KERNCONF=YOUR_KERNEL_HERE 1153 1154 To just build a kernel when you know that it won't mess you up 1155 -------------------------------------------------------------- 1156 cd src/sys/{i386,alpha}/conf 1157 config KERNEL_NAME_HERE 1158 cd ../../compile/KERNEL_NAME_HERE 1159 make depend 1160 make 1161 make install 1162 1163 If this fails, go to the "To build a kernel" section. 1164 1165 To rebuild everything and install it on the current system. 1166 ----------------------------------------------------------- 1167 # Note: sometimes if you are running current you gotta do more than 1168 # is listed here if you are upgrading from a really old current. 1169 1170 <make sure you have good level 0 dumps> 1171 <maybe fix /etc/fstab> [7] 1172 make buildworld 1173 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1174 make installkernel KERNCONF=YOUR_KERNEL_HERE 1175 [1] 1176 <reboot in single user> [3] 1177 mergemaster -p [5] 1178 make installworld 1179 mergemaster [4] 1180 <reboot> 1181 1182 1183 To cross-install current onto a separate partition 1184 -------------------------------------------------- 1185 # In this approach we use a separate partition to hold 1186 # current's root, 'usr', and 'var' directories. A partition 1187 # holding "/", "/usr" and "/var" should be about 2GB in 1188 # size. 1189 1190 <make sure you have good level 0 dumps> 1191 <boot into -stable> 1192 make buildworld 1193 <maybe newfs current's root partition> 1194 <mount current's root partition on directory ${CURRENT_ROOT}> 1195 make installworld DESTDIR=${CURRENT_ROOT} 1196 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1197 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1198 ${CURRENT_ROOT}/boot/device.hints # as needed 1199 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1200 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1201 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1202 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1203 <reboot into current> 1204 <do a "native" rebuild/install as described in the previous section> 1205 <maybe install compatibility libraries from /usr/src/lib/compat> 1206 <reboot> 1207 1208 1209 To upgrade in-place from 4.x-stable to current 1210 ---------------------------------------------- 1211 # 5.x uses more space than 4.x. Also, the location of kernel 1212 # modules has changed. If you are installing 5.0 onto a 4.x 1213 # system, you'll need about 30MB of free disk space on your / 1214 # partition. If you have less than this, you may encounter difficult 1215 # to back out of problems with this procedure. If /tmp is on 1216 # the / partition, you may want to completely remove all its content 1217 # before upgrading, as this can be a common source of shortage of 1218 # space on /. 1219 1220 <make sure you have good level 0 dumps> 1221 <maybe fix /etc/fstab> [7] 1222 make buildworld [9] 1223 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1224 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1225 make installkernel KERNCONF=YOUR_KERNEL_HERE 1226 cd src/sys/boot ; make install [6] 1227 [1] 1228 <reboot in single user> [3] 1229 mergemaster -p [5] 1230 rm -rf /usr/include/g++ 1231 make installworld 1232 mergemaster [4] 1233 <reboot> 1234 1235 Make sure that you've read the UPDATING file to understand the 1236 tweaks to various things you need. At this point in the life 1237 cycle of current, things change often and you are on your own 1238 to cope. The defaults can also change, so please read ALL of 1239 the UPDATING entries. 1240 1241 Also, if you are tracking -current, you must be subscribed to 1242 freebsd-current@freebsd.org. Make sure that before you update 1243 your sources that you have read and understood all the recent 1244 messages there. If in doubt, please track -stable which has 1245 much fewer pitfalls. 1246 1247 [1] If you have third party modules, such as vmware, you 1248 should disable them at this point so they don't crash your 1249 system on reboot. 1250 1251 [2] If you have legacy ISA devices, you may need to create 1252 your own device.hints to reflect your unique hardware 1253 configuration. 1254 1255 [3] From the bootblocks, boot -s, and then do 1256 fsck -p 1257 mount -u / 1258 mount -a 1259 cd /usr/src 1260 adjkerntz -i # if CMOS is wall time 1261 Also, when doing a major release upgrade, it is required that 1262 you boot into single user mode to do the installworld. 1263 For the 4.x -> 5.0 upgrade, you will also see many messages about 1264 needing to recompile your userland. These are harmless and can 1265 be ignored while you proceed to the next step. 1266 1267 [4] Note: This step is non-optional. Failure to do this step 1268 can result in a significant reduction in the functionality of the 1269 system. Attempting to do it by hand is not recommended and those 1270 that pursue this avenue should read this file carefully, as well 1271 as the archives of freebsd-current and freebsd-hackers mailing lists 1272 for potential gotchas. 1273 1274 [5] Usually this step is a noop. However, from time to time 1275 you may need to do this if you get unknown user in the following 1276 step. It never hurts to do it all the time. You may need to 1277 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1278 install) after the buildworld before this step if you last updated 1279 from current before 20020224 or from -stable before 20020408. 1280 1281 [6] 4.x boot loader can be used to boot a 5.x system, however 1282 it is difficult to do that at best. If you wish to try, then 1283 you should interrupt the boot and at the ok prompt type: 1284 ok unload 1285 ok boot /boot/kernel/kernel 1286 If this fails to work, you must install a new boot loader as 1287 described here. 1288 1289 [7] Before you upgrade, please make sure that you are not using 1290 compatibility slices. These are device names of the form, on i386 1291 and other architectures that use MBR slicing, /dev/ad0a without the 1292 actual slice name. Chances are excellent that these will break. 1293 You generally must update these entries to use the post FreeBSD 1294 2.x form of /dev/ad0s1a. 1295 1296 [8] In order to have a kernel that can run the 4.x binaries 1297 needed to do an installworld, you must include the COMPAT_FREEBSD4 1298 option in your kernel. Failure to do so may leave you with a system 1299 that is hard to boot to recover. 1300 1301 [9] When checking out sources, you must include the -P flag to have 1302 cvs prune empty directories. 1303FORMAT: 1304 1305This file contains a list, in reverse chronological order, of major 1306breakages in tracking -current. Not all things will be listed here, 1307and it only starts on March 15, 2000. Updating files can found in 1308previous releases if your system is older than this. 1309 1310Copyright information: 1311 1312Copyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1313 1314Redistribution, publication, translation and use, with or without 1315modification, in full or in part, in any form or format of this 1316document are permitted without further permission from the author. 1317 1318THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1319IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1320WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1321DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1322INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1323(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1324SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1325HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1326STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1327IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1328POSSIBILITY OF SUCH DAMAGE. 1329 1330If you find this document useful, and you want to, you may buy the 1331author a beer. 1332 1333Contact Warner Losh if you have any questions about your use of 1334this document. 1335 1336$FreeBSD: head/UPDATING 118141 2003-07-29 04:40:33Z njl $ 1337