UPDATING revision 126195
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 2020040224: 21 The tcpcb structure has changed and makes a recompile of libkvm 22 and related userland network utilities neccessary. 23 2420040222: 25 The cdevsw structure has changed in two externally visible ways. 26 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT. 27 Second, the d_version field must be filled in with D_VERSION. 28 Drivers outside the tree will need to be updated. 29 3020040207: 31 The /etc/rc.d/ttys script has been removed. It is no longer 32 necessary since devfs has been mandatory for some time. 33 3420040130: 35 libkse has been renamed back to libpthread and is now the 36 default threads library. The gcc -pthread option has also 37 been changed to link to libpthread instead of libc_r. For 38 alpha and sparc64 machines, libkse is not renamed and links 39 are installed so that libpthread points to libc_r. Until 40 the ports system is updated to handle this change, it is 41 recommended that folks install an /etc/libmap.conf(5) that 42 maps libc_r to libpthread. If you have any binaries or 43 libraries linked to libkse, then it is also recommended 44 that you map libkse to libpthread. Anyone that is using 45 nvidia supplied drivers and libraries should use a libmap.conf 46 that maps libpthread to libc_r since their drivers/libraries 47 do not work with libpthread. 48 4920040125: 50 ULE has entered into its probationary period as the default scheduler 51 in GENERIC. For the average user, interactivity is reported to be 52 better in many cases. On SMP machines ULE will be able to make more 53 efficient use of the available parallel resources. If you are not 54 running it now, please switch over, replacing the kernel option 55 SCHED_4BSD with SCHED_ULE. 56 5720040125: 58 Move LongRun support out of identcpu.c, where it hardly 59 belongs, into its own file and make it opt-in, not mandatory, 60 depending on CPU_ENABLE_LONGRUN config(8) option. 61 6220031213: 63 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail 64 if the login process is unable to successfully set the 65 process credentials to include all groups defined for the 66 user. The current kernel limit is 16 groups; administrators 67 may wish to check that users do not have over 16 groups 68 defined, or they will be unable to log in. 69 7020031203: 71 The ACPI module has been reactivated. It is no longer required 72 to compile ACPI support into kernels statically. 73 7420031112: 75 The statfs structure has been updated with 64-bit fields to 76 allow accurate reporting of multi-terabyte filesystem 77 sizes. You should build world, then build and boot the new kernel 78 BEFORE doing a `installworld' as the new kernel will know about 79 binaries using the old statfs structure, but an old kernel will 80 not know about the new system calls that support the new statfs 81 structure. 82 Note that the backwards compatibility is only present when the 83 kernel is configured with the COMPAT_FREEBSD4 option. Since 84 even /bin/sh will not run with a new kernel without said option 85 you're pretty much dead in the water without it. Make sure you 86 have COMPAT_FREEBSD4! 87 Running an old kernel after a `make world' will cause programs 88 such as `df' that do a statfs system call to fail with a bad 89 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports 90 that cfsd (ports/security/cfs) needs to be recompiled after 91 these changes are installed. 92 93 ****************************DANGER******************************* 94 95 DO NOT make installworld after the buildworld w/o building and 96 installing a new kernel FIRST. You will be unable to build a 97 new kernel otherwise on a system with new binaries and an old 98 kernel. 99 10020031112: 101 Some netgraph string length constants have been changed. This 102 change requires the netgraph kernel modules and all netgraph 103 userland components to be in sync. Especially users who require 104 netgraph to boot need to make sure to have world and kernel in 105 sync before rebooting. 106 10720031111: 108 Hyperthreading logical CPU's are no longer probed by default 109 when using the MP Table. If ACPI is being used, then logical 110 CPUs will be probed if hyperthreading is enabled in the BIOS. 111 If ACPI is not being used and hyperthreading is enabled in the 112 BIOS, logical CPUs can be enabled by building a custom kernel 113 with the option MPTABLE_FORCE_HTT enabled. 114 11520031103: 116 The i386 APIC_IO kernel option has been replaced by 117 'device apic'. The ACPI module has also been temporarily 118 disabled, so ACPI must be statically compiled into your 119 kernel using 'device acpi' if you wish to use the ACPI driver. 120 12120031031: 122 The API and ABI of struct ifnet have been changed by removing 123 the if_name and if_unit members and replacing them with 124 if_xname, if_dname, and if_dunit. All network drivers and most 125 userland programs which include net/if_var.h must be updated 126 and recompiled. __FreeBSD_version has been bumped to 501113 to 127 reflect this change. 128 12920030928: 130 Changes to the cdevsw default functions have been made to remove 131 the need to specify nullopen() and nullclose() explicitly. 132 __FreeBSD_version bumpted to 501110. 133 13420030926: 135 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and 136 mount_cd9660(8) need to be in sync with kernel. 137 13820030925: 139 Configuring a system to use IPFILTER now requires that PFIL_HOOKS 140 also be explicitly configured. Previously this dependency was 141 magically handled through some cruft in net/pfil.h; but that has 142 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS 143 will fail with obtuse errors in ip_fil.c. 144 14520030923: 146 Fix a bug in arplookup(), whereby a hostile party on a locally 147 attached network could exhaust kernel memory, and cause a system 148 panic, by sending a flood of spoofed ARP requests. See 149 FreeBSD-SA-03:14.arp. 150 15120030915: 152 A change to /etc/defaults/rc.conf now causes inetd to be started 153 with `-C 60' if it is not overridden in /etc/rc.conf. This 154 causes inetd to stop accepting connections from an IP address 155 that exceeds the rate of 60 connections per minute. 156 15720030829: 158 The following rc.d scripts have been removed and should be 159 deleted from your installation: atm2.sh atm3.sh devdb 160 localdaemons network1 network2 network3. Depending on when 161 you last updated world and used mergemaster(8) you may or 162 may not have problems during the rc boot sequence. The simplest 163 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'. 164 The atm2.sh atm3.sh and devdb scripts were removed some time 165 ago, so depending on when you installed -CURRENT these scripts 166 may or may not exist on your system. 167 16820030824: 169 ATAng has been committed. You need to build world as sys/ata.h 170 has changed, and userland atacontrol depends on it. 171 If you use ATA SW raids you need "device ataraid" in your 172 kernel config file, as it is no longer pulled in automatically. 173 17420030819: 175 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel. 176 Among other things, this changes the device enumeration to be 177 closer to Solaris. Be aware that, this can even cause the machine 178 to not boot without manual intervention before the fstab is adjusted. 179 18020030728: 181 All current USB and Firewire quirks in da(4) have been deprecated 182 and will be removed for 5.2. If this causes failure for your 183 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel 184 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org 185 so the quirk can be re-enabled. 186 18720030724: 188 Problems with entry 20030714 have been corrected and no known issues 189 with /rescue and -j exist for host systems after this point in time. 190 19120030722: 192 FPU-less support has been removed from FreeBSD. Chances are you won't 193 notice. 386+387 support should still work after this change, but 194 it is now a minimum requirement for the i386 port that you have real 195 FPU hardware. 196 19720030714: 198 Some people are having problems with changes related to /rescue. 199 If you are building -j N, you will need to define NO_RESCUE. Others 200 will need to define it if /rescue has issues with their environment. 201 People should report those issues to current@. 202 20320030711: 204 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN 205 across this point. Further, it might be a good idea to remove 206 /usr/obj. 207 20820030610: 209 Remove deprecated locale names and transition period code 210 for them, finishing switching to the new scheme. Check your 211 LANG environment variable. 212 21320030609: 214 CCD has been changed to be a fully GEOMified class. Kernel 215 and ccdconfig(8) needs to be in sync, this is particularly 216 important to remember beforehand if your source tree is on 217 a ccd device. Consider making a copy of the old ccdconfig 218 into /boot/kernel.good or wherever you keep your backup 219 kernel. 220 22120030605: 222 There was a small window in which sed(1) was broken. If you 223 happen to have sed(1) installed during that window, which is 224 evidenced by an inability to build world with the failure 225 given below, you need to manually build and install sed(1) 226 (and only sed(1)) before doing anything else. This is a one- 227 time snafu. Typical failure mode: 228 229 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: 230 targmatch.h:7:1: null character(s) ignored 231 targmatch.h:12:1: null character(s) ignored 232 targmatch.h:16:1: null character(s) ignored 233 : 234 235 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC 236 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of 237 usr.bin/sed/process.c). 238 23920030505: 240 Kerberos 5 (Heimdal) is now built by default. Setting 241 MAKE_KERBEROS5 no longer has any effect. If you do NOT 242 want the "base" Kerberos 5, you need to set NO_KERBEROS. 243 24420030502: 245 groff has been updated. If you try to do a buildworld and 246 get an infinite loop in troff, update to May 4th or newer. If you 247 have a newer kernel than userland, you may need to set the OSRELDATE 248 to 500110 in your environment before starting a buildworld. 249 25020030501: 251 The old rc system has been removed. Please report any problems 252 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org. 253 Your personal versions of these files will not be removed, so you can 254 continue to use them. However, you should take great care when updating, 255 especially when using mergemaster, since the compatibility code that 256 utilizes these old scripts has also been removed. 257 25820030423: 259 A bug has been fixed in /dev/devctl which would cause devd 260 to hang on boot, were it not for a workaround in devd. The 261 work around in devd will be removed around 20030507. You 262 have until then to upgrade your kernel before updating 263 userland. In general, you should have a userland and 264 kernel that's in sync with each other. However, given the 265 effects of this bug (hang on boot when starting devd), some 266 allowances are made. 267 26820030329: 269 Alphas with libc from between 20030312 and 20030329 exhibit 270 floating point exceptions (FPEs), most notably in awk(1) 271 while upgrading the system through a buildworld. 272 273 So, to successfully upgrade your Alpha, you must either 274 downgrade your libc.so to a pre-20030312 version, or update 275 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee 276 to CFLAGS, then forcibly rebuild and install libc: 277 278 cd /usr/src/lib/libc && \ 279 make cleandir && make obj && \ 280 make -DNOMAN -DNOPROFILE all && \ 281 make -DNOMAN -DNOPROFILE install 282 28320030208: 284 sendmail 8.12.7 has been imported. It has one important 285 change for IPv6 users. The default submit.mc now uses 286 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is 287 used to connect to the MTA. Users on IPv6-only machines 288 will need to edit /etc/mail/submit.mc appropriately. 289 29020030128: 291 NODEVFS option has been removed and DEVFS thereby made standard. 292 This makes all references to MAKEDEV obsolete, and they should 293 be removed when convenient. 294 29520030126: 296 The name of the device for the ofw console has changed, sparc64 users 297 must run mergemaster to update their installed /etc/ttys. 298 29920030125: 300 The scheduler framework has grown a second scheduler and consequently 301 you must specify one and only one scheduler in your kernel config. 302 The cvs config files have been updated to use the old scheduler 303 which may be selected via 'options SCHED_4BSD'. If you would like 304 to try the new, much more experimental, scheduler please try 305 'options SCHED_ULE' and contribute to the arch@ discussion. 306 30720030115: 308 A new version of the wi driver has been imported into the tree. 309 One now must have device wlan in the config file for it to operate 310 properly. 311 312 In addition, there have been some changes to how wi devices are 313 configured for point to point links to bring it more in line 314 with the former way of doing things, as well as compatibility 315 with NetBSD. 316 31720021222: 318 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC 319 used an incompatible form of ABI for returning structures and unions 320 which FreeBSD's GCC maintainers were not aware of relative to previous 321 versions of FreeBSD. We have gone back to the ABI for now, and any 322 code compiled which is required to interoperate with other code (not 323 built at the same time) returning structs or unions should be 324 rebuilt. 325 32620021216: 327 A name change in /etc/netconfig has been reverted to stay 328 compatible with suns TIRPC and also with NetBSD. You need 329 to run mergemaster after make world. A new libc does still work 330 with an outdated /etc/netconfig for some time, but you'll get 331 a warning. This warning will be removed in 20030301. 332 33320021202: 334 The recent binutils upgrade marks a kernel flag day on 335 sparc64: modules built with the old binutils will not work 336 with new kernels and vice versa. Mismatches will result in 337 panics. Make sure your kernel and modules are in sync. 338 33920021029: 340 The value of IPPROTO_DIVERT has changed. Make sure to keep 341 your kernel, netstat, natd and any third-party DIVERT 342 consumers in sync. 343 34420021024: 345 Old, compatibility slices have been removed in GEOM kernels. 346 This means that you will have to update your /etc/fstab to 347 not use disk devices of the form /dev/ad0a. Instead, you 348 now must specify /dev/ad0s1a, or whatever slice your FreeBSD 349 partition really is on. The old device names have gone 350 away, so if you use them anywhere else, you must also adjust 351 those uses. (This doesn't affect the disks formatted in 352 the ``dangerously-dedicated'' mode.) 353 35420021023: 355 Alphas with kernels from between 20020830 and 20021023 and/or 356 rtld (ld-elf.so.1) older than 20021023 may experience problems 357 with groff while doing a buildworld (kernel: "out of memory", 358 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD 359 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c). 360 361 So, to successfully upgrade your Alpha, you must either 362 upgrade your kernel and rtld first (which might be a bit 363 tricky), or avoid running the bootstrapped groff during the 364 "transitional" buildworld. To avoid running groff during the 365 transitional upgrade run make buildworld with -DNOMAN, 366 -DNO_SHAREDOCS, and -DNO_LPR. 367 36820020831: 369 gcc has been upgraded to 3.2. It is not all binary compatible 370 with earlier versions of gcc for c++ programs. All c++ 371 programs and libraries need to be recompiled. 372 373 Also, if you encounter g++ issues, rm /usr/include/g++/* before 374 doing an installworld to make sure that stale files are removed. 375 37620020827: 377 Our /etc/termcap now has all the entries from the XFree86 xterm 378 almost unchanged. This means xterm now supports color by default. 379 If you used TERM=xterm-color in the past you now should use 380 TERM=xterm. (xterm-color will lead to benign warnings). 381 38220020815: 383 A "bug" in gcc(1) that was hiding warning in system headers was 384 fixed. It's probably time to add -DNO_WERROR to your make line 385 again. 386 38720020729: 388 COPY is being deprecated. The 20010530 change was reverted, as 389 it causes far more pain than was expected, and to always compare 390 before installing, please use INSTALL="install -C" again. The 391 -C option is now silently ignored when used with the -d option. 392 39320020702: 394 Problems with libc_r clients like KDE and GNOME have been resolved. 395 There are still some minor problems with some signals but the 396 system is stable enough for general use again. SMP is less so than UP 397 but each can successfully complete multiple buildworlds. 398 Libkvm needs to be recompiled due to KSE. 399 40020020701: 401 Now would be a bad time to upgrade. Something in or near the 402 KSE commit totally broke programs using libc_r like KDE and 403 GNOME. 404 40520020511: 406 The k5su utility installed as part of Kerberos 5 is no longer 407 installed with the set-user-ID bit set by default. Add 408 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed 409 with the set-user-ID bit set. 410 41120020510: 412 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2. 413 Unfortunately our native GDB (at version 4.18) does not understand 414 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to 415 generated debugging information for our native GDB. 416 41720020510: 418 Due to the way CVS works, it may not properly update src/contrib/gcc 419 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc 420 and then do a cvs update. 421 42220020421: 423 When exec'ing set[ug]id executables, the kernel now ensures that the 424 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio. 425 42620020404: 427 New sendmail startup scripts have been installed to make it 428 easier to use alternative MTAs with FreeBSD. Setting the rc.conf 429 variable sendmail_enable to "NO" no longer prevents any sendmail 430 daemons from starting. Instead, either set sendmail_enable to 431 "NONE" or change mta_start_script to a script for starting 432 an alternative MTA. Setting mta_start_script to "" will 433 also prevent any MTA from being started at boot. 434 43520020403: 436 UCONSOLE is no longer a valid kernel option. 437 43820020315: 439 FreeBSD 5.0 DP-1 was basically branched today. 440 44120020225: 442 Warnings are now errors in the kernel. Unless you are a developer, 443 you should add -DNO_WERROR to your make line. 444 44520020217: 446 sendmail 8.12.2 has been imported. The sendmail binary is no 447 longer a set-user-ID root binary and the infrastructure to support 448 command line mail submission has changed. Be sure to run 449 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 450 and /etc/mail) and read /etc/mail/README for more details. 451 452 Due to the import of sendmail 8.12.2, a new user and group are 453 required in order for sendmail to run as a set-group-ID 454 binary. A 'make installworld' will use the new user and group 455 to set the owner and group of /var/spool/clientmqueue and will 456 fail if the new user and group do not exist. The 'smmsp' user 457 and group must be merged from src/etc/group and 458 src/etc/master.passwd before using 'make installworld'. 459 'mergemaster -p' will do this. You may need to install 460 mergemaster before this will work if you are updating from a 461 very old version of current. The updating recipe has changed 462 as of this date. 463 46420020112: 465 The preferred configuration method for PAM is now /etc/pam.d/ 466 rather than /etc/pam.conf. If you have an unmodified 467 pam.conf, just delete it after your next mergemaster run. If 468 you have local modifications, you can use 469 /usr/src/etc/pam.d/convert.pl to incorporate them into your 470 /etc/pam.d. 471 472 Please see the following url for more details: 473http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 47420011229: 475 If anyone here is already using the new rc.conf(5) variable 476 networkfs_types, please note that it has changed 477http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 478 47920011220: 480 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 481 started out its life in the ISDN4BSD project as an offspring 482 from sys/net/if_spppsubr.c, which eventually got a life of its 483 own. All the accumulated features and bugfixes of the i4b 484 version have now been merged back into the base system's 485 version now. The only user-visible change resulting from this 486 is that i4b's sppp(4) interfaces are to be managed with 487 spppcontrol(8) again, since ispppcontrol(8) has been retired 488 as well. (There has never been rc file support for 489 ispppcontrol in -current, but only in -stable. That will be 490 reverted by the time the changes are MFCed.) 491 49220011215: 493 The fdc(4) driver has been updated and now automatically 494 recognizes media in `standard' formats (like 1440 KB and 495 720 KB for a 3.5" high-density drive) when accessing the 496 default device node (e. g. /dev/fd0). The old variety of 497 floppy device nodes /dev/fd*.* is no longer present by 498 default, devices can be created (in DEVFS) on demand. They 499 will need to be customized then for `odd' densities using 500 fdcontrol(8). 501 50220011209: 503 The bugs in procfs' debugging support code have been fixed, 504 and truss(1) now works again. 505 50620011207: 507 Daily security checks have been split out to use the periodic(8) 508 scripts. Some change in configuration may be necessary. Please 509 see 510http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 511 for details. 512 51320011204: 514 sos added VCD/SVCD support to ata driver and that needs the 515 kernel and burncd to be in sync. 516 51720011203: 518 The procfs pseudo-filesystem has now been converted to use the 519 pseudofs framework. If you have 'options PROCFS' in your 520 kernel config, you'll need to add 'options PSEUDOFS' if it's 521 not there already. 522 523 This change temporarily breaks truss(1); use ktrace(1) instead 524 until the issue has been resolved. 525 52620011202: 527 A security hole in OpenSSH involving `UseLogin yes' has been 528 patched. 529 53020011126: 531 You need to remove /usr/obj/.../usr.bin/tip before rebuilding 532 after this date. You need to do this only once. 533 53420011103: 535 Most of the awk issues have been resolved. Some rough 536 edges may be left, but for the most part things should be 537 back to "normal." For CURRENT's usual definition of "normal." 538 53920011030: 540 Awk has been upgraded to the one true awk from bell labs. Expect 541 choppy waves in the upgrade process. 542 54320011030: 544 The asr driver problem has been resolved. 545 54620011027: 547 Due to changes in other parts of the system, the asr driver 548 now causes the system to panic on boot. Do not use it pending 549 correction. Comment it out of any kernel config file that you 550 try to use from this date forward. 551 55220011025: 553 When crossbuilding, use TARGET=xxx where you used to use 554 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 555 unless you are changing both of them. To cross build pc98 on 556 an alpha, for example, you need to set TARGET=pc98 and 557 TARGET_ARCH=i386. 558 55920011001: 560 The kernel interface that burncd depends on has changed. 561 You must recompile both the kernel and userland applications 562 at the same time. 563 56420010929: 565 When crossbuilding, please set TARGET_ARCH rather than 566 MACHINE_ARCH to indicate the target. In the future, one will 567 set TARGET_MACHINE where you set MACHINE now. At the moment, 568 setting MACHINE alone for same MACHINE_ARCH machines works 569 (eg, you can build pc98 on an i386 machine and vice versa). 570 57120010927: 572 Some weird problems result from using ACPI on some machines. 573 To disable ACPI you can add 574 hint.acpi.0.disabled="1" 575 to /boot/loader.conf (or by putting set X=Y at the boot 576 loader "ok" prompt). 577 578 Alternatively, you can remove it from /boot/kernel/acpi.ko 579 or use the MODULES_OVERRIDE function in your kernel config 580 file and not list acpi in that list. 581 58220010924: 583 The buildworld has been fixed. You may need to install 584 the 4.x compatibility libraries for some old binaries 585 to work. Add COMPAT4X=true to your /etc/make.conf to 586 get them installed on every installworld, or execute the 587 following to get them installed only once: 588 cd src/lib/compat/compat4x.<arch> 589 make all install 590 You will see ``__stdoutp undefined'' until you do this. 591 59220010919: 593 There's a bug in the world build process. The cross-tools 594 are build with the NEW headers, but the OLD libc.a. This 595 leads to all kinds of problems with the new libc. A temporary 596 workaround is to add 597 CFLAGS="-O -pipe -D_OLD_STDIO" 598 before building world when upgrading from 4.x to current. This 599 can be removed afterwards. 600 601 A proper fix to the buildworld target is needed. 602 60320010918: 604 Peter has committed his new kthread nfs client/server code. 605 NFS may be unstable after this date. 606 60720010912: 608 KSE has hit the tree. Lots of things are now different in 609 the kernel. While a few problems were introduced in the 610 initial commit, most of the major ones have been found and 611 corrected. 612 61320010901: 614 In OLDCARD, CardBus bridges appear to be stable. The work 615 arounds described in the 20010604 entry are now no longer 616 necessary and will be ignored. Most insert/remove problems 617 have been rectified around this date. 618 61920010823: 620 named now runs as user bind and group bind rather than as 621 root. If named_enable is set to YES in /etc/rc.conf, ensure 622 that user bind is available in /etc/passwd (using vipw(8)) 623 and that group bind is available in /etc/group. Also make 624 sure that user or group bind has read (and not write) 625 permission for your name server configuration and that it 626 has read and write permission for your slave zone files and 627 directory. 628 629 If you wish to continue to run named as root (a less secure 630 alternative), add a line to /etc/rc.conf saying 631 632 named_flags= 633 63420010709: 635 The PAM libraries have had an API upgrade that is beyond 636 the ability of the shared library major number to handle. 637 It is manifested by PAM-using ports dumping core. The 638 solution is to rebuild those ports. 639 64020010628: 641 The kernel compile module has moved from src/sys/compile/FOO 642 to src/sys/${MACHINE}/compile/FOO. 643 64420010625: 645 The pccard modem issue from 20010613 has been corrected. 646 OLDCARD support is still a little weak in -current. slot 1 is 647 known not to work on some TI based cardbus bridges. Some 648 cardbus bridges do not properly detect insert/removal events. 649 IRQ configuration needs more safety belts. 650 65120010617: 652 Softupdates problems have been corrected. 653 65420010614: 655 Peter ripped out the linkerset support. You must, as always, 656 rerun config after you cvsup if you are using the traditional 657 kernel building methods. 658 65920010613: 660 pccard modems may not work with current after 20010604 date. Some 661 do, others result in panics. *MAKE*SURE* that you update your 662 config and /etc/rc.conf ala the 20010604 entry, or you will have 663 problems (this issue will be fixed, it just hasn't been yet). 664 66520010613: 666 SOFTUPDATES seem to be broken since the middle of May or so. Do not 667 use them in current. You can disable softupdates on all mounted 668 partitions, or remove SOFTUPDATES the kernel config file. 669 67020010612: 671 After Peter's commits to the hints code, people have been noticing 672 that certain devices are attached (or try to) twice. This is due 673 to having both static hints as well as a /boot/device.hints. To 674 work around this issue, please use only one or the other mechanism 675 until this bug is fixed. 676 677 Please note that a feature of config is that if you have config 678 file FOO and FOO.hints, it automatically adds FOO.hints to the 679 hints.c file, whether you want it to or not. 680 68120010610: 682 Locale names have changed to match other systems better. 683 68420010604: 685 pccard support for pci cards has been committed. You must change 686 your /etc/pccard.conf irq lines. It must match the irq used by 687 pcic device. Interrupt storms may result if you fail to do this. 688 Interrupt storms look a lot like a hang. 689 690 You must also install a new pccardd, otherwise you will get an 691 interrupt storm at card reset time (just after it tells you what 692 it is). 693 694 pccardd_flags="-I" is necessary for the time being. It tells pccardd 695 not to ask the kernel if the interrupt is really free or not before 696 using it. You can either change the /etc/pccard.conf irq lines to 697 match pcic, or add "-i X" to the pccardd_flags. 698 69920010530: 700 INSTALL=install -C is being deprecated. If you want to do this, 701 use COPY=-C instead. The former method will be supported for only 702 a limited time. If you see 703 704install: warning: the -d and -C options may not be specified together 705 706 in your makeworld, then you need to migrate towards using 707 COPY=-C. 708 70920010525: 710 It appears that vm is now stable enough to use again. However, 711 there may be other problems, so caution is still urged. alpha 712 definitely is in bad shape. 713 71420010521: 715 Minor repo damage has happened. This may cause problems 716 with cvsup of ports. If you get errors, please see 717 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 718 at the bottom for details on a workaround. The error message 719 is 720Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 721 72220010520: 723 Vm and/or swapping are busted on -current. Please be patient. 724 72520010519: 726 pccard has had much reorganizational work done to it over 727 the past few days. Everything should still work, but if 728 not, please contact imp@freebsd.org. 729 73020010517: 731 ata ioctl changed. Make sure to recompile both kernel and 732 userland at the same time. 733 73420010517: 735 New ncurses imported. 736 73720010512: 738 DEVFS is now opt out, not opt in. Barring major problems, this 739 will be the only way to go starting July 1. 740 74120010504: 742 OpenSSH has been updated to 2.9. Some defaults are different, 743 including RhostsRSAAuthentication, which changes from yes to no. 744 74520010502: 746 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 747 74820010501: 749 Building perl was broken at 02:25:25 PDT. 750 75120010430: 752 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 753 go back in the water. 754 75520010429: 756 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 757 this date, but before the correction date. 758 75920010423: 760 old fsck and new kernel interactions appear to have been fixed. 761 76220010411: 763 fsck and the kernel were changed to handle some optimizations 764 to directory layout. This breaks backward compatibility. 765 Update only if you understand that you must not use the old 766 fsck with the new kernel ever. 767 76820010330: 769 fsck has changed the meaning of the pass column in /etc/fstab. 770 Please see the cvs commit to fsck.8 or the fsck.8 man page for 771 details. It is unclear if changes to /etc/fstab are necessary. 772 77320010319: 774 portmap had changed name to rpcbind for maximum POLA in your 775 current world. /etc/hosts.{allow,deny} needs changes. nfs and 776 other rpc based programs that rely on portmapper will not work 777 without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 778 77920010315: 780 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 781 and ATA_ENABLE_TAGS are no longer kernel options. They have 782 been replaced by tunables. See ata.4 for details. 783 78420010312: 785 The fxp driver was converted to use miibus. If you compile 786 fxp into your kernel statically, you will need to add miibus. 787 78820010312: 789 The wi device now defaults to BSS (infrastructure) mode 790 instead of ad-hoc. 791 79220010310: 793 /dev/urandom should be a symbolic link to /dev/random now. 794 Users of current not using DEVFS need to run MAKEDEV std. 795 ssh might not work if you don't. 796 79720010303: 798 The ed driver has been updated. It now allows mii attachments, 799 which means that you must include the miibus in your kernel if 800 you use the ed driver. 801 80220010220: 803 The problems with libc have been corrected. It is now mostly 804 safe to go back into the water. 805 80620010211: 807 The size of FILE was changed. This breaks upgrading. If 808 you must upgrade, be prepared for pain. It also breaks almost 809 all binaries that you've compiled on -current. You are warned 810 that before upgrading would be a good time to do a level 0 811 dump of your system. No, really, I mean it this time. 812 813 To get to the new system, you'll need to use the following 814 workaround. Hopefully this can be sorted out so that we 815 don't have to move this to the updating section. 816 817 To get around the installworld problem, do: 818 # cd /usr/src/usr.bin/sed 819 # make install 820 # cd /usr/src 821 # make installworld 822 If that doesn't work, then try: 823 # make -k installworld 824 # make installworld 825 82620010207: 827 DEVFS is now the default. If you use vinum, make sure that you 828 do not include devfs in your kernel as problems result. 829 83020010205: 831 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 832 Remove them from your config. 833 83420010122: 835 ****************************** WARNING ****************************** 836 buildkernel has been changed slightly 837 ****************************** WARNING ****************************** 838 KERNCONF replaces the variable KERNEL for buildkernel. You 839 should update your scripts and make.conf accordingly. 840 84120010119: 842 config has changed to allow DEV_FOO as a replacement for NFOO. 843 This requires a new config to build correctly. 844 84520010116: 846 The kernel option I386_CPU is now mutually exclusive with the 847 other cpu types. If you have an i386 system, be sure that it 848 only had this line. Remove it for all other configurations. 849 85020010110: 851 Changes to the kernel require it and burncd be in sync. 852 85320010102: 854 Everyone who has hw.sndunit set to something in 855 /etc/sysctl.conf, it is now hw.snd.unit. 856 85720010101: 858 ex and vi were broken by some changes to sys/queue.h. If you 859 have a bad vi, you will see make buildworld fail with a core 860 dump while building termcap. You can work around this problem 861 by adding -k to your make buildworld. This will cause the 862 build to complete and install a new vi. Once that's done, you 863 can rebuild again without the -k to pick up anything that 864 might have been ignored by the -k option. 865 866 Others have suggested that you can just rebuild libc if your 867 vi/ex is dynamically linked, but I've not received any reports 868 of this working. 869 87020001228: 871 There have been some changes to libcrypt in -current. The 872 libscrypt/libdescrypt symlink silliness is gone and the installed 873 libcrypt is fully functional. Be aware of this. 874 87520001218: 876 Linksys Fast Ethernet PCCARD cards supported by the ed driver 877 now require the addition of flag 0x80000 to their config line 878 in pccard.conf(5). This flag is not optional. These Linksys 879 cards will not be recognized without it. 880 88120001205: 882 Important new FreeBSD-version stuff: PAM support has been worked 883 in, partially from the "Unix" OpenSSH version. This requires 884 adding the following in pam.conf: 885 886 sshd auth sufficient pam_skey.so 887 sshd auth required pam_unix.so try_first_pass 888 sshd session required pam_permit.so 889 89020001031: 891 cvs updated to 1.11. 892 89320001020: 894 The random device needs more entropy, so you need to make sure 895 that you've run mergemaster to get a /etc/rc which will seed 896 /dev/random. If you don't and the system hangs after ldconfig, 897 then banging on the keyboard randomly until it unhangs is one 898 workaround. 899 90020001010: 901 ****************************** WARNING ****************************** 902 Sendmail has been updated. 903 ****************************** WARNING ****************************** 904 o mail.local(8) is no longer installed as a set-user-id binary. 905 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 906 is set. 907 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 908 commands. 909 o Now using sendmail's version of vacation(1). 910 o The sendmail cf building tools (contrib/sendmail/cf) are installed 911 in /usr/share/sendmail/cf. 912 o sendmail.cw changed to local-host-names 913 914 More details can be found at 915 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 916 91720001009: 918 The ports tree's new layout is in place. Be sure to update 919 your entire ports tree, or you will have problems. 920 92120001006: 922 The perl build procedure no longer installs miniperl, nor uses 923 the installed miniperl. It is recommended that you delete 924 /usr/bin/miniperl. 925 92620001005: 927 This weekend the ports tree will be updated to a new layout. 928 It will be in an inconsistent state until noted in the UPDATING 929 file, or with asami-san's message to the relevant mailing 930 lists. With this new layout, you'll need to update the whole 931 tree for anything to work. 932 93320000928: 934 There was a change in the passwd format. Need more information. 935 93620000916: 937 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 938 place. Please update boot loader (not the boot blocks) at the 939 same time as your kernel. 940 94120000914: 942 The new pmtimer device is necessary for laptops. Failure to 943 include the device will cause suspended laptops losing time 944 when they resume. Include 945 device pmtimer 946 in your config file and 947 hint.pmtimer.0.at="isa" 948 to your /boot/device.hints file. 949 95020000911: 951 The random device has been turned into a (pseudo-)device, 952 rather than an option. The supplied kernel config files have 953 been updated. You will need to do something similar in your 954 own kernel config file. 955 Remove: 956 options RANDOMDEV 957 Add: 958 device random 959 If you prefer to load the loadable module, you need to do 960 nothing. 961 96220000909: 963 The random device module has been renamed from randomdev.ko to 964 random.ko. You will need to edit your /boot/loader.conf to 965 reflect this if you load this module at boot time. 966 The line should read: 967 random_load="YES" 968 96920000907: 970 The SMPNG commit has happened. It should work, but if it 971 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 972 to be a variety of minor issues. Please see 20000905 to make 973 sure you don't have model loading problems which might at 974 first blush appear related to SMP. 975 97620000906: 977 nsswitch has been imported from NetBSD. Among other things, 978 this means that /etc/host.conf is no longer used. See 979 nsswitch.conf(5) instead. Note that at boot time rc.network 980 will attempt to produce a new nsswitch.conf file for you if you 981 don't have one, and you have host.conf. 982 98320000905: 984 The ucred structure changed size. This breaks the interface 985 that mountd uses. Trying to use an older mountd with a newer 986 kernel guarantees a panic. This means that you need to use 987 kernels newer than today only with matching mountd, but you 988 needed to do that anyway with the boot loader changes. 989 99020000905: 991 The boot loader has been updated. The new default kernel is 992 now /boot/kernel/kernel.ko. The new default module location 993 is /boot/kernel. 994 995 You *MUST* upgrade your boot loader and kernel at the same time. 996 The easiest way to do this is to do the buildworld/buildkernel/ 997 installkernel/installworld dance. 998 999 Furthermore, you are urged to delete your old /modules directory 1000 before booting the new kernel, since kldload will find stale 1001 modules in that directory instead of finding them in the correct 1002 path, /boot/kernel. The most common complaint that this cures 1003 is that the linux module crashes your machine after the update. 1004 1005 if [ ! -d /boot/kernel.old ]; then 1006 mv /modules.old /boot/kernel.old 1007 chflags noschg /kernel.old 1008 mv /kernel.old /boot/kernel.old/kernel.ko 1009 chflags schg /boot/kernel.old/kernel.ko 1010 fi 1011 101220000904: 1013 A new issue with the sendmail upgrade has come to light. 1014 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 1015 incorrectly install the default aliases in /etc/mail rather than 1016 move the old one from /etc. So you'll need to manually move the 1017 file, create a symbolic link, remove the old /etc/aliases.db and 1018 run newaliases. For safety sake, you should stop sendmail 1019 while doing this and run the upgrade when locally sourced email 1020 is not likely to be generated. 1021 102220000825: 1023 /boot/device.hints is now required for installkernel to 1024 succeed. You should copy GENERIC.hints for your architecture 1025 into /boot/device.hints. If and only if you compile hints 1026 into your kernel, then this file may be empty. Please note, 1027 if you have an empty or missing /boot/device.hints file and 1028 you neglected to compile hints into your kernel, no boot 1029 messages will appear after the boot loader tries to start the 1030 kernel. 1031 103220000821: 1033 If you do NOT have ``options RANDOMDEV'' in your kernel and 1034 you DO want the random device then add randomdev_load="YES" to 1035 /boot/loader.conf. 1036 103720000812: 1038 suidperl is now always built and installed on the system, but 1039 with permissions of 511. If you have applications that use 1040 this program, you are now required to add ENABLE_SUIDPERL=true 1041 to /etc/make.conf. If you forget to do this, 1042 chmod 4511 /usr/bin/suidperl 1043 will fix this until the next build. 1044 104520000812: 1046 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 1047 visible changes that may immediately affect your configuration 1048 include: 1049 - New default file locations from src/contrib/sendmail/cf/README 1050 - newaliases limited to root and trusted users 1051 - MSA port (587) turned on by default 1052 - New queue file naming system so can't go from 8.11 -> 8.9 1053 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 1054 - FEATURE(`nullclient') is more full featured 1055 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 1056 - mail.local FreeBSD-only -b option changed to -B 1057 - See src/contrib/sendmail/RELEASE_NOTES for more info 1058 105920000810: 1060 suidperl (aka sperl) is no longer build by default. You must 1061 specifically define BUILD_SUIDPERL to "true" for it to be build. 1062 Furthermore, we recommend that you remove /usr/bin/sperl* and 1063 /usr/bin/suidperl files from your system unless you have a 1064 specific use for it. 1065 106620000729: 1067 Networking defaults have been tightened. Anybody upgrading 1068 /etc/defaults/rc.conf needs to add the following lines to 1069 /etc/rc.conf if they want to have the same setup 1070 afterwards (unless the variables already are set, of course): 1071 # Enable network daemons for user convenience. 1072 inetd_enable="YES" 1073 portmap_enable="YES" 1074 sendmail_enable="YES" 1075 107620000728: 1077 If you have null_load="YES" in your /boot/loader.conf, you 1078 will need to change that to nullfs_load="YES". 1079 108020000728: 1081 The "installkernel" target has changed slightly. Now even if 1082 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 1083 it will install the MYKERNEL file (built with the buildkernel 1084 target) as /kernel rather than /MYKERNEL. Those who have 1085 updated their /boot/loader.conf files to point to /MYKERNEL 1086 should remove that entry or perform manual rename of /kernel 1087 to /MYKERNEL. 1088 108920000711: 1090 If you use CVSUP or CTM to get CVS trees, AND you used to get 1091 the old crypto files from internat.freebsd.org AND you check 1092 out files from the CVS tree with the cvs command, please read 1093 http://people.freebsd.org/~imp/internat.txt 1094 for details on potential problems that you might have and how 1095 to get around them. 1096 1097 If you are merely a mirror, or don't answer yes to each of the 1098 clauses above, you needn't worry. 1099 110020000711: 1101 /etc/security has been updated to print the inode number of 1102 setuid programs that have changed. You will see a large spike 1103 in the number of changed programs the first time when you run 1104 mergemaster to get a new /etc/security. 1105 110620000710: 1107 /dev/random now has good entropy collection (from the keyboard 1108 and sysmouse drivers). Please ensure that either `options 1109 RANDOMDEV' is present in your kernel config file or that 1110 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 1111 not have the /dev/random driver, OpenSSL (and consequently 1112 lots of crypto tools (like SSH)) will fail with strange 1113 errors. (see below, 20000624). 1114 1115 FreeBSD-current is safe again to run Crypto. 1116 111720000709: 1118 phk made the malloc default options AJ. This may slow things 1119 down and uncover other latent bugs in the code. If you need to 1120 run at full speed, you can disable this by doing the following: 1121 ln -s aj /etc/malloc.conf 1122 112320000706: 1124 libftpio's version was accidentally bumped a few days ago. This 1125 has been corrected. You may need to remove /usr/lib/libftpio.so.6 1126 before doing your next buildworld/installworld pair. It certainly 1127 won't hurt to remove it before the update procedure. It will 1128 break fetch until a new one is built, but ftp can be used in the 1129 interim if needed. 1130 113120000705: 1132 The crypto packages have changed for the cvsup. This has been done 1133 in a backward compatible way, but the old packages will go away at 1134 some point in the future. Look at /usr/share/examples/cvsup for 1135 details. 1136 113720000704: 1138 With the new sys/modules/sound/drivers/*, you will need to 1139 set SYSDIR until you do an installworld after July 7th. 1140 114120000704: 1142 rc.shutdown and rc will now call the rc.d scripts with start 1143 or stop. This may cause some harmless warnings from older 1144 rc.d scripts that haven't been updated. 1145 114620000630: 1147 The libfetch based version of fetch has gone into the tree. 1148 Minor problems may result on some of the less popular sites, 1149 which should be reported to des@freebsd.org. 1150 115120000625: 1152 From approximately this date forward, one must have the crypto 1153 system installed in order to build the system and kernel. 1154 While not technically strictly true, one should treat it as 1155 required and grab the crypto bits. If you are grabbing CVS 1156 trees, src-all and cvs-crypto should be treated as if they 1157 were required. You should check with the latest collections 1158 to make sure that these haven't changed. 1159 116020000624: 1161 Mark Murray just committed the first parts of a cleanup of 1162 /dev/zero, et al. This is also cleaning up /dev/random. 1163 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 1164 -CURRENT FROM THIS POINT to 2000710 for cryptographic services 1165 until Mark can merge in the fixes to this work in progress. 1166 openssh and openssl should not be used to generate keys from this 1167 date to the completion of the work. 1168 1169 If you must operate at this reduced level of security, add ' 1170 options RANDOMDEV' to your kernel or modload the randomdev 1171 module. You may also need to copy a new MAKEDEV to /dev and 1172 recreate the random and urandom devices. 1173 117420000622: 1175 The license on the softupdates is now a standard 2 clause 1176 BSD license. You may need to remove your symbolic links 1177 that used to be required when updating. 1178 117920000621: 1180 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 1181 the config file update procedure. 1182 http://people.freebsd.org/~imp/config-upd.html 1183 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 1184 isn't buildable. However, you can generate a LINT file: 1185 cd /sys/<ARCH>/conf && make LINT 1186 118720000620: 1188 Binutils 2.10 have hit the tree, or will shortly. As soon 1189 as they do, the problem noted in 20000522 will be resolved and 1190 that workaround will no longer be required. 1191 119220000615: 1193 phk removed the compatibility creation of wd devices in the 1194 ad driver. If you haven't done so already, you must update 1195 your fstab, etc to use the ad devices instead of the wd 1196 devices. 1197 1198 In addition, you'll need to update your boot blocks to a 1199 more modern version, if you haven't already done so. Modern 1200 here means 4.0 release or newer (although older releases 1201 may work). 1202 120320000612: 1204 Peter took an axe to config(8). Be sure that you read his mail 1205 on the topic before even thinking about updating. You will 1206 need to create a /boot/device.hints or add a hints directive 1207 to your config file to compile them in statically. The format 1208 of the config file has changed as well. Please see GENERIC or 1209 NEWCARD for examples of the new format. 1210 1211 Indirectly, this also breaks USERCONFIG. Unless a newer entry 1212 says that it has been fixed, assume that must use the hints mechanism 1213 in the loader if you need to use a machine with very old ISA cards 1214 in it. 1215 121620000522: 1217 A new set of binutils went into the tree today. Anybody 1218 building a kernel after this point is advised that they need 1219 to rebuild their binutils (or better yet do a 1220 buildworld/installworld) before building a new kernel. 1221 1222 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 1223 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 1224 is recommended that you don't set this option until the problem 1225 is resolved. 1226 122720000513: 1228 The ethernet drivers were all updated to clean up the BPF handling. 1229 123020000510: 1231 The problems with boot blocks on the alphas have been corrected. 1232 This will require some care in updating alphas. A new libstand 1233 is requires for the boot blocks to build properly. 1234 123520000503: 1236 Recompile all kld modules. Proper version dependency info 1237 is now available. 1238 123920000502: 1240 Modules have been disconnected from the buildworld tree and 1241 connected to the kernel building instead. 1242 124320000427: 1244 You may need to build gperf 1245 cd /usr/src/gnu/usr.bin/gperf && make depend all install 1246 when upgrading from 4.0 -> current. The build system now uses 1247 an option only in -current. 1248 124920000417: 1250 The method that we brand ELF binaries has changed to be more 1251 acceptable to the binutils maintainers. You will need to 1252 rebrand your ELF binaries that aren't native. One problem 1253 binary is the Linux ldconfig. After your make world, but 1254 before you reboot, you'll need to issue: 1255 brandelf -t Linux /compat/linux/sbin/ldconfig 1256 if you have Linux compatibility enabled on your machine. 1257 125820000320: 1259 If you have really bad/marginal IDE drives, you may find they 1260 don't work well. Use pio mode instead. The easiest way to 1261 cope if you have a problem combination is to add: 1262 /sbin/sysctl hw.ata.ata_dma=0 1263 to the start of /etc/rc.conf. 1264 126520000319: 1266 The ISA and PCI compatibility shims have been connected to the 1267 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 1268 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 1269 include the appropriate option in your kernel config. Drivers 1270 using the shims should be updated or they won't ship with 1271 5.0-RELEASE, targeted for 2001. 1272 127320000318: 1274 We've entered the traditional post release dumping party. 1275 Large kernel changes are being committed and are in the 1276 works. It is important to keep the systems' klds and kernel 1277 in sync as kernel interfaces and structures are changing. 1278 Before reporting kernel panics, make sure that all modules 1279 that you are loading are up to date. 1280 128120000315: 1282 If you are upgrading from an older version of FreeBSD, you 1283 need to update your boot blocks as well. 'disklabel -B ad0' 1284 will do the trick. This isn't critical until you remove your 1285 wd device entries in /dev, at which point your system will not 1286 boot. 1287 128820000315: 1289 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 1290 to upgrade to 4.0 from 3.x. 1291 1292COMMON ITEMS: 1293 1294 General Notes 1295 ------------- 1296 Avoid using make -j when upgrading. From time to time in the 1297 past there have been problems using -j with buildworld and/or 1298 installworld. This is especially true when upgrading between 1299 "distant" versions (eg one that cross a major release boundary 1300 or several minor releases, or when several months have passed 1301 on the -current branch). 1302 1303 Sometimes, obscure build problems are the result of environment 1304 poisoning. This can happen because the make utility reads its 1305 environment when searching for values for global variables. 1306 To run your build attempts in an "environmental clean room", 1307 prefix all make commands with 'env -i '. See the env(1) manual 1308 page for more details. 1309 1310 To build a kernel 1311 ----------------- 1312 If you are updating from a prior version of FreeBSD (even one just 1313 a few days old), you should follow this procedure. With a 1314 /usr/obj tree with a fresh buildworld, 1315 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1316 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1317 1318 To just build a kernel when you know that it won't mess you up 1319 -------------------------------------------------------------- 1320 cd src/sys/{i386,alpha}/conf 1321 config KERNEL_NAME_HERE 1322 cd ../../compile/KERNEL_NAME_HERE 1323 make depend 1324 make 1325 make install 1326 1327 If this fails, go to the "To build a kernel" section. 1328 1329 To rebuild everything and install it on the current system. 1330 ----------------------------------------------------------- 1331 # Note: sometimes if you are running current you gotta do more than 1332 # is listed here if you are upgrading from a really old current. 1333 1334 <make sure you have good level 0 dumps> 1335 <maybe fix /etc/fstab> [7] 1336 make buildworld 1337 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1338 make installkernel KERNCONF=YOUR_KERNEL_HERE 1339 [1] 1340 <reboot in single user> [3] 1341 mergemaster -p [5] 1342 make installworld 1343 mergemaster [4] 1344 <reboot> 1345 1346 1347 To cross-install current onto a separate partition 1348 -------------------------------------------------- 1349 # In this approach we use a separate partition to hold 1350 # current's root, 'usr', and 'var' directories. A partition 1351 # holding "/", "/usr" and "/var" should be about 2GB in 1352 # size. 1353 1354 <make sure you have good level 0 dumps> 1355 <boot into -stable> 1356 make buildworld 1357 <maybe newfs current's root partition> 1358 <mount current's root partition on directory ${CURRENT_ROOT}> 1359 make installworld DESTDIR=${CURRENT_ROOT} 1360 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1361 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \ 1362 ${CURRENT_ROOT}/boot/device.hints # as needed 1363 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1364 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1365 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1366 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1367 <reboot into current> 1368 <do a "native" rebuild/install as described in the previous section> 1369 <maybe install compatibility libraries from /usr/src/lib/compat> 1370 <reboot> 1371 1372 1373 To upgrade in-place from 4.x-stable to current 1374 ---------------------------------------------- 1375 # 5.x uses more space than 4.x. Also, the location of kernel 1376 # modules has changed. If you are installing 5.0 onto a 4.x 1377 # system, you'll need about 30MB of free disk space on your / 1378 # partition. If you have less than this, you may encounter difficult 1379 # to back out of problems with this procedure. If /tmp is on 1380 # the / partition, you may want to completely remove all its content 1381 # before upgrading, as this can be a common source of shortage of 1382 # space on /. 1383 1384 <make sure you have good level 0 dumps> 1385 <maybe fix /etc/fstab> [7] 1386 make buildworld [9] 1387 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 1388 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 1389 make installkernel KERNCONF=YOUR_KERNEL_HERE 1390 cd src/sys/boot ; make install [6] 1391 [1] 1392 <reboot in single user> [3] 1393 mergemaster -p [5] 1394 rm -rf /usr/include/g++ 1395 make installworld 1396 mergemaster [4] 1397 <reboot> 1398 1399 Make sure that you've read the UPDATING file to understand the 1400 tweaks to various things you need. At this point in the life 1401 cycle of current, things change often and you are on your own 1402 to cope. The defaults can also change, so please read ALL of 1403 the UPDATING entries. 1404 1405 Also, if you are tracking -current, you must be subscribed to 1406 freebsd-current@freebsd.org. Make sure that before you update 1407 your sources that you have read and understood all the recent 1408 messages there. If in doubt, please track -stable which has 1409 much fewer pitfalls. 1410 1411 [1] If you have third party modules, such as vmware, you 1412 should disable them at this point so they don't crash your 1413 system on reboot. 1414 1415 [2] If you have legacy ISA devices, you may need to create 1416 your own device.hints to reflect your unique hardware 1417 configuration. 1418 1419 [3] From the bootblocks, boot -s, and then do 1420 fsck -p 1421 mount -u / 1422 mount -a 1423 cd /usr/src 1424 adjkerntz -i # if CMOS is wall time 1425 Also, when doing a major release upgrade, it is required that 1426 you boot into single user mode to do the installworld. 1427 For the 4.x -> 5.0 upgrade, you will also see many messages about 1428 needing to recompile your userland. These are harmless and can 1429 be ignored while you proceed to the next step. 1430 1431 [4] Note: This step is non-optional. Failure to do this step 1432 can result in a significant reduction in the functionality of the 1433 system. Attempting to do it by hand is not recommended and those 1434 that pursue this avenue should read this file carefully, as well 1435 as the archives of freebsd-current and freebsd-hackers mailing lists 1436 for potential gotchas. 1437 1438 [5] Usually this step is a noop. However, from time to time 1439 you may need to do this if you get unknown user in the following 1440 step. It never hurts to do it all the time. You may need to 1441 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1442 install) after the buildworld before this step if you last updated 1443 from current before 20020224 or from -stable before 20020408. 1444 1445 [6] 4.x boot loader can be used to boot a 5.x system, however 1446 it is difficult to do that at best. If you wish to try, then 1447 you should interrupt the boot and at the ok prompt type: 1448 ok unload 1449 ok boot /boot/kernel/kernel 1450 If this fails to work, you must install a new boot loader as 1451 described here. 1452 1453 [7] Before you upgrade, please make sure that you are not using 1454 compatibility slices. These are device names of the form, on i386 1455 and other architectures that use MBR slicing, /dev/ad0a without the 1456 actual slice name. Chances are excellent that these will break. 1457 You generally must update these entries to use the post FreeBSD 1458 2.x form of /dev/ad0s1a. 1459 1460 [8] In order to have a kernel that can run the 4.x binaries 1461 needed to do an installworld, you must include the COMPAT_FREEBSD4 1462 option in your kernel. Failure to do so may leave you with a system 1463 that is hard to boot to recover. 1464 1465 [9] When checking out sources, you must include the -P flag to have 1466 cvs prune empty directories. 1467FORMAT: 1468 1469This file contains a list, in reverse chronological order, of major 1470breakages in tracking -current. Not all things will be listed here, 1471and it only starts on March 15, 2000. Updating files can found in 1472previous releases if your system is older than this. 1473 1474Copyright information: 1475 1476Copyright 1998, 2002 M. Warner Losh. All Rights Reserved. 1477 1478Redistribution, publication, translation and use, with or without 1479modification, in full or in part, in any form or format of this 1480document are permitted without further permission from the author. 1481 1482THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1483IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1484WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1485DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1486INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1487(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1488SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1489HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1490STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1491IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1492POSSIBILITY OF SUCH DAMAGE. 1493 1494If you find this document useful, and you want to, you may buy the 1495author a beer. 1496 1497Contact Warner Losh if you have any questions about your use of 1498this document. 1499 1500$FreeBSD: head/UPDATING 126195 2004-02-24 16:12:09Z andre $ 1501