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