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