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