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