UPDATING revision 95042
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 20 In addition, IDE write caching is currently disabled by default 21 due to on-going concerns about disk write order and file system 22 integrity. Re-enabling write caching can substantially improve 23 performance. 24 2520020404: 26 New sendmail startup scripts have been installed to make it 27 easier to use alternative MTAs with FreeBSD. Setting the rc.conf 28 variable sendmail_enable to "NO" no longer prevents any sendmail 29 daemons from starting. Instead, either set sendmail_enable to 30 "NONE" or change mta_start_script to a script for starting 31 an alternative MTA. Setting mta_start_script to "" will 32 also prevent any MTA from being started at boot. 33 3420020403: 35 UCONSOLE is no longer a valid kernel option. 36 3720020315: 38 FreeBSD 5.0 DP-1 was basically branched today. 39 4020020225: 41 Warnings are now errors in the kernel. Unless you are a developer, 42 you should add -DNO_WERROR to your make line. 43 4420020217: 45 sendmail 8.12.2 has been imported. The sendmail binary is no 46 longer a set-user-ID root binary and the infrastructure to support 47 command line mail submission has changed. Be sure to run 48 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf, 49 and /etc/mail) and read /etc/mail/README for more details. 50 51 Due to the import of sendmail 8.12.2, a new user and group are 52 required in order for sendmail to run as a set-group-ID 53 binary. A 'make installworld' will use the new user and group 54 to set the owner and group of /var/spool/clientmqueue and will 55 fail if the new user and group do not exist. The 'smmsp' user 56 and group must be merged from src/etc/group and 57 src/etc/master.passwd before using 'make installworld'. 58 'mergemaster -p' will do this. You may need to install 59 mergemaster before this will work if you are updating from a 60 very old version of current. The updating recipe has changed 61 as of this date. 62 6320020112: 64 The preferred configuration method for PAM is now /etc/pam.d/ 65 rather than /etc/pam.conf. If you have an unmodified 66 pam.conf, just delete it after your next mergemaster run. If 67 you have local modifications, you can use 68 /usr/src/etc/pam.d/convert.pl to incorporate them into your 69 /etc/pam.d. 70 71 Please see the following url for more details: 72http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no> 7320011229: 74 If anyone here is already using the new rc.conf(5) variable 75 networkfs_types, please note that it has changed 76http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za> 77 7820011220: 79 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file 80 started out its life in the ISDN4BSD project as an offspring 81 from sys/net/if_spppsubr.c, which eventually got a life of its 82 own. All the accumulated features and bugfixes of the i4b 83 version have now been merged back into the base system's 84 version now. The only user-visible change resulting from this 85 is that i4b's sppp(4) interfaces are to be managed with 86 spppcontrol(8) again, since ispppcontrol(8) has been retired 87 as well. (There has never been rc file support for 88 ispppcontrol in -current, but only in -stable. That will be 89 reverted by the time the changes are MFCed.) 90 9120011215: 92 The fdc(4) driver has been updated and now automatically 93 recognizes media in `standard' formats (like 1440 KB and 94 720 KB for a 3.5" high-density drive) when accessing the 95 default device node (e. g. /dev/fd0). The old variety of 96 floppy device nodes /dev/fd*.* is no longer present by 97 default, devices can be created (in DEVFS) on demand. They 98 will need to be customized then for `odd' densities using 99 fdcontrol(8). 100 10120011209: 102 The bugs in procfs' debugging support code have been fixed, 103 and truss(1) now works again. 104 10520011207: 106 Daily security checks have been split out to use the periodic(8) 107 scripts. Some change in configuration may be necessary. Please 108 see 109http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org> 110 for details. 111 11220011204: 113 sos added VCD/SVCD support to ata driver and that needs the 114 kernel and burncd to be in sync. 115 11620011203: 117 The procfs pseudo-filesystem has now been converted to use the 118 pseudofs framework. If you have 'options PROCFS' in your 119 kernel config, you'll need to add 'options PSEUDOFS' if it's 120 not there already. 121 122 This change temporarily breaks truss(1); use ktrace(1) instead 123 until the issue has been resolved. 124 12520011202: 126 A security hole in OpenSSH involving `UseLogin yes' has been 127 patched. 128 12920011126: 130 You need to remove /usr/obj/.../usr.bin/tip before rebuilding 131 after this date. You need to do this only once. 132 13320011103: 134 Most of the awk issues have been resolved. Some rough 135 edges may be left, but for the most part things should be 136 back to "normal." For CURRENT's usual definition of "normal." 137 13820011030: 139 Awk has been upgraded to the one true awk from bell labs. Expect 140 choppy waves in the upgrade process. 141 14220011030: 143 The asr driver problem has been resolved. 144 14520011027: 146 Due to changes in other parts of the system, the asr driver 147 now causes the system to panic on boot. Do not use it pending 148 correction. Comment it out of any kernel config file that you 149 try to use from this date forward. 150 15120011025: 152 When crossbuilding, use TARGET=xxx where you used to use 153 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET, 154 unless you are changing both of them. To cross build pc98 on 155 an alpha, for example, you need to set TARGET=pc98 and 156 TARGET_ARCH=i386. 157 15820011001: 159 The kernel interface that burncd depends on has changed. 160 You must recompile both the kernel and userland applications 161 at the same time. 162 16320010929: 164 When crossbuilding, please set TARGET_ARCH rather than 165 MACHINE_ARCH to indicate the target. In the future, one will 166 set TARGET_MACHINE where you set MACHINE now. At the moment, 167 setting MACHINE alone for same MACHINE_ARCH machines works 168 (eg, you can build pc98 on a i386 machine and vice versa). 169 17020010927: 171 Some weird problems result from using ACPI on some machines. 172 To disable ACPI you can add 173 hint.acpi.0.disable="1" 174 to /boot/loader.conf (or by putting set X=Y at the boot 175 loader "ok" prompt). 176 177 Alternatively, you can remove it from /boot/kernel/acpi.ko 178 or use the MODULES_OVERRIDE function in your kernel config 179 file and not list acpi in that list. 180 18120010924: 182 The buildworld has been fixed. You may need to install 183 the 4.x compatibility libraries for some old binaries 184 to work. Add COMPAT4X=true to your /etc/make.conf to 185 get them installed on every installworld, or execute the 186 following to get them installed only once: 187 cd src/lib/compat/compat4x.<arch> 188 make all install 189 You will see ``__stdoutp undefined'' until you do this. 190 19120010919: 192 There's a bug in the world build process. The cross-tools 193 are build with the NEW headers, but the OLD libc.a. This 194 leads to all kinds of problems with the new libc. A temporary 195 workaround is to add 196 CFLAGS="-O -pipe -D_OLD_STDIO" 197 before building world when upgrading from 4.x to current. This 198 can be removed afterwards. 199 200 A proper fix to the buildworld target is needed. 201 20220010918: 203 Peter has committed his new kthread nfs client/server code. 204 NFS may be unstable after this date. 205 20620010912: 207 KSE has hit the tree. Lots of things are now different in 208 the kernel. While a few problems were introduced in the 209 initial commit, most of the major ones have been found and 210 corrected. 211 21220010901: 213 In OLDCARD, CardBus bridges appear to be stable. The work 214 arounds described in the 20010604 entry are now no longer 215 necessary and will be ignored. Most insert/remove problems 216 have been rectified around this date. 217 21820010823: 219 named now runs as user bind and group bind rather than as 220 root. If named_enable is set to YES in /etc/rc.conf, ensure 221 that user bind is available in /etc/passwd (using vipw(8)) 222 and that group bind is available in /etc/group. Also make 223 sure that user or group bind has read (and not write) 224 permission for your name server configuration and that it 225 has read and write permission for your slave zone files and 226 directory. 227 228 If you wish to continue to run named as root (a less secure 229 alternative), add a line to /etc/rc.conf saying 230 231 named_flags= 232 23320010709: 234 The PAM libraries have had an API upgrade that is beyond 235 the ability of the shared library major number to handle. 236 It is manifested by PAM-using ports dumping core. The 237 solution is to rebuild those ports. 238 23920010628: 240 The kernel compile module has moved from src/sys/compile/FOO 241 to src/sys/${MACHINE}/compile/FOO. 242 24320010625: 244 The pccard modem issue from 20010613 has been corrected. 245 OLDCARD support is still a little weak in -current. slot 1 is 246 known not to work on some TI based cardbus bridges. Some 247 cardbus bridges do not properly detect insert/removal events. 248 IRQ configuration needs more safety belts. 249 25020010617: 251 Softupdates problems have been corrected. 252 25320010614: 254 Peter ripped out the linkerset support. You must, as always, 255 rerun config after you cvsup if you are using the traditional 256 kernel building methods. 257 25820010613: 259 pccard modems may not work with current after 20010604 date. Some 260 do, others result in panics. *MAKE*SURE* that you update your 261 config and /etc/rc.conf ala the 20010604 entry, or you will have 262 problems (this issue will be fixed, it just hasn't been yet). 263 26420010613: 265 SOFTUPDATES seem to be broken since the middle of May or so. Do not 266 use them in current. You can disable softupdates on all mounted 267 partitions, or remove SOFTUPDATES the kernel config file. 268 26920010612: 270 After Peter's commits to the hints code, people have been noticing 271 that certain devices are attached (or try to) twice. This is due 272 to having both static hints as well as a /boot/device.hints. To 273 work around this issue, please use only one or the other mechanism 274 until this bug is fixed. 275 276 Please note that a feature of config is that if you have config 277 file FOO and FOO.hints, it automatically adds FOO.hints to the 278 hints.c file, wheather you want it to or not. 279 28020010610: 281 Locale names have changed to match other systems better. 282 28320010604: 284 pccard support for pci cards has been committed. You must change 285 your /etc/pccard.conf irq lines. It must match the irq used by 286 pcic device. Interrupt storms may result if you fail to do this. 287 Interrupt storms look a lot like a hang. 288 289 You must also install a new pccardd, otherwise you will get an 290 interrupt storm at card reset time (just after it tells you what 291 it is). 292 293 pccardd_flags="-I" is necessary for the time being. It tells pccardd 294 not to ask the kernel if the interrupt is really free or not before 295 using it. You can either change the /etc/pccard.conf irq lines to 296 match pcic, or add "-i X" to the pccardd_flags. 297 29820010530: 299 INSTALL=install -C is being deprecated. If you want to do this, 300 use COPY=-C instead. The former method will be supported for only 301 a limited time. If you see 302 303install: warning: the -d and -C options may not be specified together 304 305 in your makeworld, then you need to migrate towards using 306 COPY=-C. 307 30820010525: 309 It appears that vm is now stable enough to use again. However, 310 there may be other problems, so caution is still urged. alpha 311 definitely is in bad shape. 312 31320010521: 314 Minor repo damange has happened. This may cause problems 315 with cvsup of ports. If you get errors, please see 316 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495 317 at the bottom for details on a workaround. The error message 318 is 319Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty 320 32120010520: 322 Vm and/or swapping are busted on -current. Please be patient. 323 32420010519: 325 pccard has had much reorganizational work done to it over 326 the past few days. Everything should still work, but if 327 not, please contact imp@freebsd.org. 328 32920010517: 330 ata ioctl changed. Make sure to recompile both kernel and 331 userland at the same time. 332 33320010517: 334 New ncurses imported. 335 33620010512: 337 DEVFS is now opt out, not opt in. Barring major problems, this 338 will be the only way to go starting July 1. 339 34020010504: 341 OpenSSH has been updated to 2.9. Some defaults are different, 342 including RhostsRSAAuthentication, which changes from yes to no. 343 34420010502: 345 Perl breakage in 20010501 was corrected at 14:18:33 PDT. 346 34720010501: 348 Building perl was broken at 02:25:25 PDT. 349 35020010430: 351 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to 352 go back in the water. 353 35420010429: 355 A bad bug was committed at 04:48:42 PDT. Don't use kernels after 356 this date, but before the correction date. 357 35820010423: 359 old fsck and new kernel interactions appear to have been fixed. 360 36120010411: 362 fsck and the kernel were changed to handle some optimizations 363 to directory layout. This breaks backward compatibility. 364 Update only if you understand that you must not use the old 365 fsck with the new kernel ever. 366 36720010330: 368 fsck has changed the meaning of the pass column in /etc/fstab. 369 Please see the cvs commit to fsck.8 or the fsck.8 man page for 370 details. It is unclear if changes to /etc/fstab are necessary. 371 37220010319: 373 portmap had changed name to rpcbind for maximum POLA in your 374 current world. /etc/hosts.{allow,deny} needs changes. nfs and 375 other rpc based programs that rely on portmapper will not work 376 without updates to /etc/hosts.{allow,deny} and /etc/netconfig. 377 37820010315: 379 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC 380 and ATA_ENABEL_TAGS are no longer kernel options. They have 381 been replaced by tunables. See ata.4 for details. 382 38320010312: 384 The fxp driver was converted to use miibus. If you compile 385 fxp into your kernel statically, you will need to add miibus. 386 38720010312: 388 The wi device now defaults to BSS (infrastructure) mode 389 instead of ad-hoc. 390 39120010310: 392 /dev/urandom should be a symbolic link to /dev/random now. 393 Users of current not using DEVFS need to run MAKEDEV std. 394 ssh might not work if you don't. 395 39620010303: 397 The ed driver has been updated. It now allows mii attachments, 398 which means that you must include the miibus in your kernel if 399 you use the ed driver. 400 40120010220: 402 The problems with libc have been corrected. It is now mostly 403 safe to go back into the water. 404 40520010211: 406 The size of FILE was changed. This breaks upgrading. If 407 you must upgrade, be prepared for pain. It also breaks almost 408 all binaries that you've compiled on -current. You are warned 409 that before upgrading would be a good time to do a level 0 410 dump of your system. No, really, I mean it this time. 411 412 To get to the new system, you'll need to use the following 413 workaround. Hopefully this can be sorted out so that we 414 don't have to move this to the updating section. 415 416 To get around the installworld problem, do: 417 # cd /usr/src/usr.bin/sed 418 # make install 419 # cd /usr/src 420 # make installworld 421 If that doesn't work, then try: 422 # make -k installworld 423 # make installworld 424 42520010207: 426 DEVFS is now the default. If you use vinum, make sure that you 427 do not include devfs in your kernel as problems result. 428 42920010205: 430 FFS_ROOT and CD9660_ROOT have been removed or deprecated. 431 Remove them from your config. 432 43320010122: 434 ****************************** WARNING ****************************** 435 buildkernel has been changed slightly 436 ****************************** WARNING ****************************** 437 KERNCONF replaces the variable KERNEL for buildkernel. You 438 should update your scripts and make.conf accordingly. 439 44020010119: 441 config has changed to allow DEV_FOO as a replacement for NFOO. 442 This requires a new config to build correctly. 443 44420010116: 445 The kerrnel option I386_CPU is now mutually exclusive with the 446 other cpu types. If you have an i386 system, be sure that it 447 only had this line. Remove it for all other configurations. 448 44920010110: 450 Changes to the kernel require it and burncd be in sync. 451 45220010102: 453 Everyone who has hw.sndunit set to something in 454 /etc/sysctl.conf, it is now hw.snd.unit. 455 45620010101: 457 ex and vi were broken by some changes to sys/queue.h. If you 458 have a bad vi, you will see make buildworld fail with a core 459 dump while building termcap. You can work around this problem 460 by adding -k to your make buildworld. This will cause the 461 build to complete and install a new vi. Once that's done, you 462 can rebuild again without the -k to pick up anything that 463 might have been ignored by the -k option. 464 465 Others have suggested that you can just rebuild libc if your 466 vi/ex is dynamically linked, but I've not received any reports 467 of this working. 468 46920001228: 470 There have been some changes to libcrypt in -current. The 471 libscrypt/libdescrypt symlink sillyness is gone and the installed 472 libcrypt is fully functional. Be aware of this. 473 47420001218: 475 Linksys Fast Ethernet PCCARD cards supported by the ed driver 476 now require the addition of flag 0x80000 to their config line 477 in pccard.conf(5). This flag is not optional. These Linksys 478 cards will not be recognized without it. 479 48020001205: 481 Important new FreeBSD-version stuff: PAM support has been worked 482 in, partially from the "Unix" OpenSSH version. This requires 483 adding the following in pam.conf: 484 485 sshd auth sufficient pam_skey.so 486 sshd auth required pam_unix.so try_first_pass 487 sshd session required pam_permit.so 488 48920001031: 490 cvs updated to 1.11. 491 49220001020: 493 The random device needs more entropy, so you need to make sure 494 that you've run mergemaster to get a /etc/rc which will seed 495 /dev/random. If you don't and the system hangs after ldconfig, 496 then banging on the keyboard randomly until it unhangs is one 497 workaround. 498 49920001010: 500 ****************************** WARNING ****************************** 501 Sendmail has been updated. 502 ****************************** WARNING ****************************** 503 o mail.local(8) is no longer installed as a set-user-id binary. 504 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 505 is set. 506 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 507 commands. 508 o Now using sendmail's version of vacation(1). 509 o The sendmail cf building tools (contrib/sendmail/cf) are installed 510 in /usr/share/sendmail/cf. 511 o sendmail.cw changed to local-host-names 512 513 More details can be found at 514 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 515 51620001009: 517 The ports tree's new layout is in place. Be sure to update 518 your entire ports tree, or you will have problems. 519 52020001006: 521 The perl build procedure no longer installs miniperl, nor uses 522 the installed miniperl. It is recommended that you delete 523 /usr/bin/miniperl. 524 52520001005: 526 This weekend the ports tree will be updated to a new layout. 527 It will be in an inconsistent state until noted in the UPDATING 528 file, or with asami-san's message to the relevant mailing 529 lists. With this new layout, you'll need to update the whole 530 tree for anything to work. 531 53220000928: 533 There was a change in the passwd format. Need more information. 534 53520000916: 536 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 537 place. Please update boot loader (not the boot blocks) at the 538 same time as your kernel. 539 54020000914: 541 The new pmtimer device is necessary for laptops. Failure to 542 include the device will cause suspended laptops losing time 543 when they resume. Include 544 device pmtimer 545 in your config file and 546 hint.pmtimer.0.at="isa" 547 to your /boot/device.hints file. 548 54920000911: 550 The random device has been turned into a (pseudo-)device, 551 rather than an option. The supplied kernel config files have 552 been updated. You will need to do something similar in your 553 own kernel config file. 554 Remove: 555 options RANDOMDEV 556 Add: 557 device random 558 If you prefer to load the loadable module, you need to do 559 nothing. 560 56120000909: 562 The random device module has been renamed from randomdev.ko to 563 random.ko. You will need to edit your /boot/loader.conf to 564 reflect this if you load this module at boot time. 565 The line should read: 566 random_load="YES" 567 56820000907: 569 The SMPNG commit has happened. It should work, but if it 570 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 571 to be a variety of minor issues. Please see 20000905 to make 572 sure you don't have model loading problems which might at 573 first blush appear related to SMP. 574 57520000906: 576 nsswitch has been imported from NetBSD. Among other things, 577 this means that /etc/host.conf is no longer used. See 578 nsswitch.conf(5) instead. Note that at boot time rc.network 579 will attempt to produce a new nsswitch.conf file for you if you 580 don't have one, and you have host.conf. 581 58220000905: 583 The ucred structure changed size. This breaks the interface 584 that mountd uses. Trying to use an older mountd with a newer 585 kernel guarantees a panic. This means that you need to use 586 kernels newer than today only with matching mountd, but you 587 needed to do that anyway with the boot loader changes. 588 58920000905: 590 The boot loader has been updated. The new default kernel is 591 now /boot/kernel/kernel.ko. The new default module location 592 is /boot/kernel. 593 594 You *MUST* upgrade your boot loader and kernel at the same time. 595 The easiest way to do this is to do the buildworld/buildkernel/ 596 installkernel/installworld dance. 597 598 Furthermore, you are urged to delete your old /modules directory 599 before booting the new kernel, since kldload will find stale 600 modules in that directory instead of finding them in the correct 601 path, /boot/kernel. The most common complaint that this cures 602 is that the linux module crashes your machine after the update. 603 604 if [ ! -d /boot/kernel.old ]; then 605 mv /modules.old /boot/kernel.old 606 chflags noschg /kernel.old 607 mv /kernel.old /boot/kernel.old/kernel.ko 608 chflags schg /boot/kernel.old/kernel.ko 609 fi 610 61120000904: 612 A new issue with the sendmail upgrade has come to light. 613 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 614 incorrectly install the default aliases in /etc/mail rather than 615 move the old one from /etc. So you'll need to manually move the 616 file, create a symbolic link, remove the old /etc/aliases.db and 617 run newaliases. For safety sake, you should stop sendmail 618 while doing this and run the upgrade when locally sourced email 619 is not likely to be generated. 620 62120000825: 622 /boot/device.hints is now required for installkernel to 623 succeed. You should copy GENERIC.hints for your architecture 624 into /boot/device.hints. If and only if you compile hints 625 into your kernel, then this file may be empty. Please note, 626 if you have an empty or missing /boot/device.hints file and 627 you neglected to compile hints into your kernel, no boot 628 messages will appear after the boot loader tries to start the 629 kernel. 630 63120000821: 632 If you do NOT have ``options RANDOMDEV'' in your kernel and 633 you DO want the random device then add randomdev_load="YES" to 634 /boot/loader.conf. 635 63620000812: 637 suidperl is now always built and installed on the system, but 638 with permissions of 511. If you have applications that use 639 this program, you are now required to add ENABLE_SUIDPERL=true 640 to /etc/make.conf. If you forget to do this, 641 chmod 4511 /usr/bin/suidperl 642 will fix this until the next build. 643 64420000812: 645 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 646 visible changes that may immediately affect your configuration 647 include: 648 - New default file locations from src/contrib/sendmail/cf/README 649 - newaliases limited to root and trusted users 650 - MSA port (587) turned on by default 651 - New queue file naming system so can't go from 8.11 -> 8.9 652 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 653 - FEATURE(`nullclient') is more full featured 654 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 655 - mail.local FreeBSD-only -b option changed to -B 656 - See src/contrib/sendmail/RELEASE_NOTES for more info 657 65820000810: 659 suidperl (aka sperl) is no longer build by default. You must 660 specifically define BUILD_SUIDPERL to "true" for it to be build. 661 Furthermore, we recommend that you remove /usr/bin/sperl* and 662 /usr/bin/suidperl files from your system unless you have a 663 specific use for it. 664 66520000729: 666 Networking defaults have been tightened. Anybody upgrading 667 /etc/defaults/rc.conf needs to add the following lines to 668 /etc/rc.conf if they want to have the same setup 669 afterwards (unless the variables already are set, of course): 670 # Enable network daemons for user convenience. 671 inetd_enable="YES" 672 portmap_enable="YES" 673 sendmail_enable="YES" 674 67520000728: 676 If you have null_load="YES" in your /boot/loader.conf, you 677 will need to change that to nullfs_load="YES". 678 67920000728: 680 The "installkernel" target has changed slightly. Now even if 681 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 682 it will install the MYKERNEL file (built with the buildkernel 683 target) as /kernel rather than /MYKERNEL. Those who have 684 updated their /boot/loader.conf files to point to /MYKERNEL 685 should remove that entry or perform manual rename of /kernel 686 to /MYKERNEL. 687 68820000711: 689 If you use CVSUP or CTM to get CVS trees, AND you used to get 690 the old crypto files from internat.freebsd.org AND you check 691 out files from the CVS tree with the cvs command, please read 692 http://people.freebsd.org/~imp/internat.txt 693 for details on potential problems that you might have and how 694 to get around them. 695 696 If you are merely a mirror, or don't answer yes to each of the 697 clauses above, you needn't worry. 698 69920000711: 700 /etc/security has been updated to print the inode number of 701 setuid programs that have changed. You will see a large spike 702 in the number of changed programs the first time when you run 703 mergemaster to get a new /etc/security. 704 70520000710: 706 /dev/random now has good entropy collection (from the keyboard 707 and sysmouse drivers). Please ensure that either `options 708 RANDOMDEV' is present in your kernel config file or that 709 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 710 not have the /dev/random driver, OpenSSL (and consequently 711 lots of crypto tools (like SSH)) will fail with strange 712 errors. (see below, 20000624). 713 714 FreeBSD-current is safe again to run Crypto. 715 71620000709: 717 phk made the malloc default options AJ. This may slow things 718 down and uncover other latent bugs in the code. If you need to 719 run at full speed, you can disable this by doing the following: 720 ln -s aj /etc/malloc.conf 721 72220000706: 723 libftpio's version was accidentally bumped a few days ago. This 724 has been corrected. You may need to remove /usr/lib/libftpio.so.6 725 before doing your next buildworld/installworld pair. It certainly 726 won't hurt to remove it before the update procedure. It will 727 break fetch until a new one is built, but ftp can be used in the 728 interim if needed. 729 73020000705: 731 The crypto packages have changed for the cvsup. This has been done 732 in a backward compatible way, but the old packages will go away at 733 some point in the future. Look at /usr/share/examples/cvsup for 734 details. 735 73620000704: 737 With the new sys/modules/sound/drivers/*, you will need to 738 set SYSDIR until you do an installworld after July 7th. 739 74020000704: 741 rc.shutdown and rc will now call the rc.d scripts with start 742 or stop. This may cause some harmless warnings from older 743 rc.d scripts that haven't been updated. 744 74520000630: 746 The libfetch based version of fetch has gone into the tree. 747 Minor problems may result on some of the less popular sites, 748 which should be reported to des@freebsd.org. 749 75020000625: 751 From approximately this date forward, one must have the crypto 752 system installed in order to build the system and kernel. 753 While not technically strictly true, one should treat it as 754 required and grab the crypto bits. If you are grabbing CVS 755 trees, src-all and cvs-crypto should be treated as if they 756 were required. You should check with the latest collections 757 to make sure that these haven't changed. 758 75920000624: 760 Mark Murray just committed the first parts of a cleanup of 761 /dev/zero, et al. This is also cleaning up /dev/random. 762 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 763 -CURRENT FROM THIS POINT to 2000710 for cryptographic services 764 until Mark can merge in the fixes to this work in progress. 765 openssh and openssl should not be used to generate keys from this 766 date to the completion of the work. 767 768 If you must operate at this reduced level of security, add ' 769 options RANDOMDEV' to your kernel or modload the randomdev 770 module. You may also need to copy a new MAKEDEV to /dev and 771 recreate the random and urandom devices. 772 77320000622: 774 The license on the softupdates is now a standard 2 clause 775 BSD license. You may need to remove your symbolic links 776 that used to be required when updating. 777 77820000621: 779 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 780 the config file update procedure. 781 http://people.freebsd.org/~imp/config-upd.html 782 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 783 isn't buildable. However, you can generate a LINT file. 784 78520000620: 786 Binutils 2.10 have hit the tree, or will shortly. As soon 787 as they do, the problem noted in 20000522 will be resolved and 788 that workaround will no longer be required. 789 79020000615: 791 phk removed the compatibility creation of wd devices in the 792 ad driver. If you haven't done so already, you must update 793 your fstab, etc to use the ad devices instead of the wd 794 devices. 795 796 In addition, you'll need to update your boot blocks to a 797 more modern version, if you haven't already done so. Modern 798 here means 4.0 release or newer (although older releases 799 may work). 800 80120000612: 802 Peter took an axe to config(8). Be sure that you read his mail 803 on the topic before even thinking about updating. You will 804 need to create a /boot/device.hints or add a hints directive 805 to your config file to compile them in statically. The format 806 of the config file has changed as well. Please see GENERIC or 807 NEWCARD for examples of the new format. 808 809 Indirectly, this also breaks USERCONFIG. Unless a newer entry 810 says that it has been fixed, assume that must use the hints mechanism 811 in the loader if you need to use a machine with very old ISA cards 812 in it. 813 81420000522: 815 A new set of binutils went into the tree today. Anybody 816 building a kernel after this point is advised that they need 817 to rebuild their binutils (or better yet do a 818 buildworld/installworld) before building a new kernel. 819 820 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 821 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 822 is recommended that you don't set this option until the problem 823 is resolved. 824 82520000513: 826 The ethernet drivers were all updated to clean up the BPF handling. 827 82820000510: 829 The problems with boot blocks on the alphas have been corrected. 830 This will require some care in updating alphas. A new libstand 831 is requires for the boot blocks to build properly. 832 83320000503: 834 Recompile all kld modules. Proper version dependency info 835 is now available. 836 83720000502: 838 Modules have been disconnected from the buildworld tree and 839 connected to the kernel building instead. 840 84120000427: 842 You may need to build gperf 843 cd /usr/src/gnu/usr.bin/gperf && make depend all install 844 when upgrading from 4.0 -> current. The build system now uses 845 an option only in -current. 846 84720000417: 848 The method that we brand ELF binaries has changed to be more 849 acceptable to the binutils maintainers. You will need to 850 rebrand your ELF binaries that aren't native. One problem 851 binary is the Linux ldconfig. After your make world, but 852 before you reboot, you'll need to issue: 853 brandelf -t Linux /compat/linux/sbin/ldconfig 854 if you have Linux compatibility enabled on your machine. 855 85620000320: 857 If you have really bad/marginal IDE drives, you may find they 858 don't work well. Use pio mode instead. The easiest way to 859 cope if you have a problem combination is to add: 860 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 861 to the start of /etc/rc.conf. 862 86320000319: 864 The ISA and PCI compatibility shims have been connected to the 865 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 866 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 867 include the appropriate option in your kernel config. Drivers 868 using the shims should be updated or they won't ship with 869 5.0-RELEASE, targeted for 2001. 870 87120000318: 872 We've entered the traditional post release dumping party. 873 Large kernel changes are being committed and are in the 874 works. It is important to keep the systems' klds and kernel 875 in sync as kernel interfaces and structures are changing. 876 Before reporting kernel panics, make sure that all modules 877 that you are loading are up to date. 878 87920000315: 880 If you are upgrading from an older version of FreeBSD, you 881 need to update your boot blocks as well. 'disklabel -B ad0' 882 will do the trick. This isn't critical until you remove your 883 wd device entries in /dev, at which point your system will not 884 boot. 885 88620000315: 887 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 888 to upgrade to 4.0 from 3.x. 889 890COMMON ITEMS: 891 892 General Notes 893 ------------- 894 Avoid using make -j when upgrading. From time to time in the 895 past there have been problems using -j with buildworld and/or 896 installworld. This is especially true when upgrading between 897 "distant" versions (eg one that cross a major release boundary 898 or several minor releases, or when several months have passed 899 on the -current branch). 900 901 Sometimes, obscure build problems are the result of environment 902 poisoning. This can happen because the make utility reads its 903 environment when searching for values for global variables. 904 To run your build attempts in an "environmental clean room", 905 prefix all make commands with 'env -i '. See the env(1) manual 906 page for more details. 907 908 To build a kernel 909 ----------------- 910 If you are updating from a prior version of FreeBSD (even one just 911 a few days old), you should follow this procedure. With a 912 /usr/obj tree with a fresh buildworld, 913 make buildkernel KERNCONF=YOUR_KERNEL_HERE 914 make installkernel KERNCONF=YOUR_KERNEL_HERE 915 916 To just build a kernel when you know that it won't mess you up 917 -------------------------------------------------------------- 918 cd src/sys/{i386,alpha}/conf 919 config KERNEL_NAME_HERE 920 cd ../../compile/KERNEL_NAME_HERE 921 make depend 922 make 923 make install 924 925 If this fails, go to the "To build a kernel" section. 926 927 To rebuild everything and install it on the current system. 928 ----------------------------------------------------------- 929 make world 930 Build a new kernel, see above. 931 932 To upgrade from 4.x-stable to current 933 ------------------------------------- 934 make buildworld 935 make buildkernel KERNCONF=YOUR_KERNEL_HERE 936 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2] 937 make installkernel KERNCONF=YOUR_KERNEL_HERE 938 reboot in single user [3] 939 mergemaster -p [5] 940 make installworld 941 mergemaster [4] 942 [1] 943 <reboot> 944 945 Make sure that you've read the UPDATING file to understand the 946 tweaks to various things you need. At this point in the life 947 cycle of current, things change often and you are on your own 948 to cope. The defaults can also change, so please read ALL of 949 the UPDATING entries. 950 951 Also, if you are tracking -current, you must be subscribed to 952 freebsd-current@freebsd.org. Make sure that before you update 953 your sources that you have read and understood all the recent 954 messages there. If in doubt, please track -stable which has 955 much fewer pitfalls. 956 957 [1] If you have third party modules, such as vmware, you 958 should disable them at this point so they don't crash your 959 system on reboot. 960 961 [2] If you have legacy ISA devices, you may need to create 962 your own device.hints to reflect your unique hardware 963 configuration. 964 965 [3] From the bootblocks, boot -s, and then do 966 fsck -p 967 mount -u / 968 mount -a 969 cd /usr/src 970 adjkerntz -i # if CMOS is wall time 971 972 [4] Note: This step is non-optional. Failure to do this step 973 can result in a significant reduction in the functionality of the 974 system. Attempting to do it by hand is not recommended and those 975 that pursue this avenue should read this file carefully, as well 976 as the archives of freebsd-current and freebsd-hackers mailing lists 977 for potential gotchas. 978 979 [5] Usually this step is a noop. However, from time to time 980 you may need to do this if you get unknown user in the following 981 step. It never hurts to do it all the time. You may need to 982 install a new mergemaster (cd src/usr.sbin/mergemaster && make 983 install) after the buildworld before this step if you last updated 984 from current before 20020224 or from -stable before 20020408. 985 986FORMAT: 987 988This file contains a list, in reverse chronological order, of major 989breakages in tracking -current. Not all things will be listed here, 990and it only starts on March 15, 2000. Updating files can found in 991previous releases if your system is older than this. 992 993Copyright information: 994 995Copyright 1998, 2002 M. Warner Losh. All Rights Reserved. 996 997Redistribution, publication, translation and use, with or without 998modification, in full or in part, in any form or format of this 999document are permitted without further permission from the author. 1000 1001THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1002IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1003WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1004DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1005INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1006(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1007SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1008HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1009STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1010IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1011POSSIBILITY OF SUCH DAMAGE. 1012 1013If you find this document useful, and you want to, you may buy the 1014author a beer. 1015 1016Contact Warner Losh if you have any questions about your use of 1017this document. 1018 1019$FreeBSD: head/UPDATING 95042 2002-04-19 11:37:34Z ru $ 1020