UPDATING revision 73214
1Updating Information for FreeBSD current users 2 3This file is maintained by imp@village.org. Please send new entries 4directly to him. See end of file for further details. For commonly 5done items, please see the end of the file. Search for 'COMMON 6ITEMS:' 7 820010220: 9 The problems with libc have been corrected. It is now mostly 10 safe to go back into the water. 11 1220010211: 13 The size of FILE was changed. This breaks upgrading. If 14 you must upgrade, be prepared for pain. It also breaks almost 15 all binaries that you've compiled on -current. You are warned 16 that before upgrading would be a good time to do a level 0 17 dump of your system. No, really, I mean it this time. 18 19 To get to the new system, you'll need to use the following 20 workaround. Hopefully this can be sorted out so that we 21 don't have to move this to the updating section. 22 23 To get around the installworld problem, do: 24 # cd /usr/src/usr.bin/sed 25 # make install 26 # cd /usr/src 27 # make installworld 28 If that doesn't work, then try: 29 # make -k installworld 30 # make installworld 31 3220010207: 33 DEVFS is now the default. If you use vinum, make sure that you 34 do not include devfs in your kernel as problems result. 35 3620010205: 37 FFS_ROOT and CD9660_ROOT have been removed or depricated. 38 Remove them from your config. 39 4020010122: 41 ****************************** WARNING ****************************** 42 buildkernel has been changed slightly 43 ****************************** WARNING ****************************** 44 KERNCONF replaces the variable KERNEL for buildkernel. You 45 should update your scripts and make.conf accordingly. 46 4720010119: 48 config has changed to allow DEV_FOO as a replacement for NFOO. 49 This requires a new config to build correctly. 50 5120010116: 52 The kerrnel option I386_CPU is now mutually exclusive with the 53 other cpu types. If you have an i386 system, be sure that it 54 only had this line. Remove it for all other configurations. 55 5620010110: 57 Changes to the kernel require it and burncd be in sync. 58 5920010102: 60 Everyone who has hw.sndunit set to something in 61 /etc/sysctl.conf, it is now hw.snd.unit. 62 6320010101: 64 ex and vi were broken by some changes to sys/queue.h. If you 65 have a bad vi, you will see make buildworld fail with a core 66 dump while building termcap. You can work around this problem 67 by adding -k to your make buildworld. This will cause the 68 build to complete and install a new vi. Once that's done, you 69 can rebuild again without the -k to pick up anything that 70 might have been ignored by the -k option. 71 72 Others have suggested that you can just rebuild libc if your 73 vi/ex is dynamically linked, but I've not received any reports 74 of this working. 75 7620001228: 77 There have been some changes to libcrypt in -current. The 78 libscrypt/libdescrypt symlink sillyness is gone and the installed 79 libcrypt is fully functional. Be aware of this. 80 8120001218: 82 Linksys Fast Ethernet PCCARD cards supported by the ed driver 83 now require the addition of flag 0x80000 to their config line 84 in pccard.conf(5). This flag is not optional. These Linksys 85 cards will not be recognized without it. 86 8720001205: 88 Important new FreeBSD-version stuff: PAM support has been worked 89 in, partially from the "Unix" OpenSSH version. This requires 90 adding the following in pam.conf: 91 92 sshd auth sufficient pam_skey.so 93 sshd auth required pam_unix.so try_first_pass 94 sshd session required pam_permit.so 95 9620001031: 97 cvs updated to 1.11. 98 9920001020: 100 The random device needs more entropy, so you need to make sure 101 that you've run mergemaster to get a /etc/rc which will seed 102 /dev/random. If you don't and the system hangs after ldconfig, 103 then banging on the keyboard randomly until it unhangs is one 104 workaround. 105 10620001010: 107 ****************************** WARNING ****************************** 108 Sendmail has been updated. 109 ****************************** WARNING ****************************** 110 o mail.local(8) is no longer installed as a set-user-id binary. 111 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL 112 is set. 113 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY 114 commands. 115 o Now using sendmail's version of vacation(1). 116 o The sendmail cf building tools (contrib/sendmail/cf) are installed 117 in /usr/share/sendmail/cf. 118 o sendmail.cw changed to local-host-names 119 120 More details can be found at 121 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010 122 12320001009: 124 The ports tree's new layout is in place. Be sure to update 125 your entire ports tree, or you will have problems. 126 12720001006: 128 The perl build procedure no longer installs miniperl, nor uses 129 the installed miniperl. It is recommended that you delete 130 /usr/bin/miniperl. 131 13220001005: 133 This weekend the ports tree will be updated to a new layout. 134 It will be in an inconsistent state until noted in the UPDATING 135 file, or with asami-san's message to the relevant mailing 136 lists. With this new layout, you'll need to update the whole 137 tree for anything to work. 138 13920000928: 140 There was a change in the passwd format. Need more information. 141 14220000916: 143 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 144 place. Please update boot loader (not the boot blocks) at the 145 same time as your kernel. 146 14720000914: 148 The new pmtimer device is necessary for laptops. Failure to 149 include the device will cause suspended laptops losing time 150 when they resume. Include 151 device pmtimer 152 in your config file and 153 hint.pmtimer.0.at="isa" 154 to your /boot/device.hints file. 155 15620000911: 157 The random device has been turned into a (pseudo-)device, 158 rather than an option. The supplied kernel config files have 159 been updated. You will need to do something similar in your 160 own kernel config file. 161 Remove: 162 options RANDOMDEV 163 Add: 164 device random 165 If you prefer to load the loadable module, you need to do 166 nothing. 167 16820000909: 169 The random device module has been renamed from randomdev.ko to 170 random.ko. You will need to edit your /boot/loader.conf to 171 reflect this if you load this module at boot time. 172 The line should read: 173 random_load="YES" 174 17520000907: 176 The SMPNG commit has happened. It should work, but if it 177 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 178 to be a variety of minor issues. Please see 20000905 to make 179 sure you don't have model loading problems which might at 180 first blush appear related to SMP. 181 18220000906: 183 nsswitch has been imported from NetBSD. Among other things, 184 this means that /etc/host.conf is no longer used. See 185 nsswitch.conf(5) instead. Note that at boot time rc.network 186 will attempt to produce a new nsswitch.conf file for you if you 187 don't have one, and you have host.conf. 188 18920000905: 190 The ucred structure changed size. This breaks the interface 191 that mountd uses. Trying to use an older mountd with a newer 192 kernel guarantees a panic. This means that you need to use 193 kernels newer than today only with matching mountd, but you 194 needed to do that anyway with the boot loader changes. 195 19620000905: 197 The boot loader has been updated. The new default kernel is 198 now /boot/kernel/kernel.ko. The new default module location 199 is /boot/kernel. 200 201 You *MUST* upgrade your boot loader and kernel at the same time. 202 The easiest way to do this is to do the buildworld/buildkernel/ 203 installkernel/installworld dance. 204 205 Furthermore, you are urged to delete your old /modules directory 206 before booting the new kernel, since kldload will find stale 207 modules in that directory instead of finding them in the correct 208 path, /boot/kernel. The most common complaint that this cures 209 is that the linux module crashes your machine after the update. 210 211 if [ ! -d /boot/kernel.old ]; then 212 mv /modules.old /boot/kernel.old 213 chflags noschg /kernel.old 214 mv /kernel.old /boot/kernel.old/kernel.ko 215 chflags schg /boot/kernel.old/kernel.ko 216 fi 217 21820000904: 219 A new issue with the sendmail upgrade has come to light. 220 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 221 incorrectly install the default aliases in /etc/mail rather than 222 move the old one from /etc. So you'll need to manually move the 223 file, create a symbolic link, remove the old /etc/aliases.db and 224 run newaliases. For safety sake, you should stop sendmail 225 while doing this and run the upgrade when locally sourced email 226 is not likely to be generated. 227 22820000825: 229 /boot/device.hints is now required for installkernel to 230 succeed. You should copy GENERIC.hints for your architecture 231 into /boot/device.hints. If and only if you compile hints 232 into your kernel, then this file may be empty. Please note, 233 if you have an empty or missing /boot/device.hints file and 234 you neglected to compile hints into your kernel, no boot 235 messages will appear after the boot loader tries to start the 236 kernel. 237 23820000821: 239 If you do NOT have ``options RANDOMDEV'' in your kernel and 240 you DO want the random device then add randomdev_load="YES" to 241 /boot/loader.conf. 242 24320000812: 244 suidperl is now always built and installed on the system, but 245 with permissions of 511. If you have applications that use 246 this program, you are now required to add ENABLE_SUIDPERL=true 247 to /etc/make.conf. If you forget to do this, 248 chmod 4511 /usr/bin/suidperl 249 will fix this until the next build. 250 25120000812: 252 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 253 visible changes that may immediately affect your configuration 254 include: 255 - New default file locations from src/contrib/sendmail/cf/README 256 - newaliases limited to root and trusted users 257 - MSA port (587) turned on by default 258 - New queue file naming system so can't go from 8.11 -> 8.9 259 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 260 - FEATURE(`nullclient') is more full featured 261 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 262 - mail.local FreeBSD-only -b option changed to -B 263 - See src/contrib/sendmail/RELEASE_NOTES for more info 264 26520000810: 266 suidperl (aka sperl) is no longer build by default. You must 267 specifically define BUILD_SUIDPERL to "true" for it to be build. 268 Furthermore, we recommend that you remove /usr/bin/sperl* and 269 /usr/bin/suidperl files from your system unless you have a 270 specific use for it. 271 27220000729: 273 Networking defaults have been tightened. Anybody upgrading 274 /etc/defaults/rc.conf needs to add the following lines to 275 /etc/rc.conf if they want to have the same setup 276 afterwards (unless the variables already are set, of course): 277 # Enable network daemons for user convenience. 278 inetd_enable="YES" 279 portmap_enable="YES" 280 sendmail_enable="YES" 281 28220000728: 283 If you have null_load="YES" in your /boot/loader.conf, you 284 will need to change that to nullfs_load="YES". 285 28620000728: 287 The "installkernel" target has changed slightly. Now even if 288 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 289 it will install the MYKERNEL file (built with the buildkernel 290 target) as /kernel rather than /MYKERNEL. Those who have 291 updated their /boot/loader.conf files to point to /MYKERNEL 292 should remove that entry or perform manual rename of /kernel 293 to /MYKERNEL. 294 29520000711: 296 If you use CVSUP or CTM to get CVS trees, AND you used to get 297 the old crypto files from internat.freebsd.org AND you check 298 out files from the CVS tree with the cvs command, please read 299 http://people.freebsd.org/~imp/internat.txt 300 for details on potential problems that you might have and how 301 to get around them. 302 303 If you are merely a mirror, or don't answer yes to each of the 304 clauses above, you needn't worry. 305 30620000711: 307 /etc/security has been updated to print the inode number of 308 setuid programs that have changed. You will see a large spike 309 in the number of changed programs the first time when you run 310 mergemaster to get a new /etc/security. 311 31220000710: 313 /dev/random now has good entropy collection (from the keyboard 314 and sysmouse drivers). Please ensure that either `options 315 RANDOMDEV' is present in your kernel config file or that 316 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 317 not have the /dev/random driver, OpenSSL (and consequently 318 lots of crypto tools (like SSH)) will fail with strange 319 errors. (see below, 20000624). 320 321 FreeBSD-current is safe again to run Crypto. 322 32320000709: 324 phk made the malloc default options AJ. This may slow things 325 down and uncover other latent bugs in the code. If you need to 326 run at full speed, you can disable this by doing the following: 327 ln -s aj /etc/malloc.conf 328 32920000706: 330 libftpio's version was accidentally bumped a few days ago. This 331 has been corrected. You may need to remove /usr/lib/libftpio.so.6 332 before doing your next buildworld/installworld pair. It certainly 333 won't hurt to remove it before the update procedure. It will 334 break fetch until a new one is built, but ftp can be used in the 335 interim if needed. 336 33720000705: 338 The crypto packages have changed for the cvsup. This has been done 339 in a backward compatible way, but the old packages will go away at 340 some point in the future. Look at /usr/share/examples/cvsup for 341 details. 342 34320000704: 344 With the new sys/modules/sound/drivers/*, you will need to 345 set SYSDIR until you do an installworld after July 7th. 346 34720000704: 348 rc.shutdown and rc will now call the rc.d scripts with start 349 or stop. This may cause some harmless warnings from older 350 rc.d scripts that haven't been updated. 351 35220000630: 353 The libfetch based version of fetch has gone into the tree. 354 Minor problems may result on some of the less popular sites, 355 which should be reported to des@freebsd.org. 356 35720000625: 358 From approximately this date forward, one must have the crypto 359 system installed in order to build the system and kernel. 360 While not technically strictly true, one should treat it as 361 required and grab the crypto bits. If you are grabbing CVS 362 trees, src-all and cvs-crypto should be treated as if they 363 were required. You should check with the latest collections 364 to make sure that these haven't changed. 365 36620000624: 367 Mark Murray just committed the first parts of a cleanup of 368 /dev/zero, et al. This is also cleaning up /dev/random. 369 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 370 -CURRENT FROM THIS POINT FORWARD for cryptographic services 371 until Mark can merge in the fixes to this work in progress. 372 openssh and openssl should not be used to generate keys from this 373 date to the completion of the work. 374 375 If you must operate at this reduced level of security, add ' 376 options RANDOMDEV' to your kernel or modload the randomdev 377 module. You may also need to copy a new MAKEDEV to /dev and 378 recreate the random and urandom devices. 379 38020000622: 381 The license on the softupdates is now a standard 2 clause 382 BSD license. You may need to remove your symbolic links 383 that used to be required when updating. 384 38520000621: 386 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 387 the config file update procedure. 388 http://people.freebsd.org/~imp/config-upd.html 389 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 390 isn't buildable. However, you can generate a LINT file. 391 39220000620: 393 Binutils 2.10 have hit the tree, or will shortly. As soon 394 as they do, the problem noted in 20000522 will be resolved and 395 that workaround will no longer be required. 396 39720000615: 398 phk removed the compatibility creation of wd devices in the 399 ad driver. If you haven't done so already, you must update 400 your fstab, etc to use the ad devices instead of the wd 401 devices. 402 403 In addition, you'll need to update your boot blocks to a 404 more modern version, if you haven't already done so. Modern 405 here means 4.0 release or newer (although older releases 406 may work). 407 40820000612: 409 Peter took an axe to config(8). Be sure that you read his mail 410 on the topic before even thinking about updating. You will 411 need to create a /boot/device.hints or add a hints directive 412 to your config file to compile them in statically. The format 413 of the config file has changed as well. Please see GENERIC or 414 NEWCARD for examples of the new format. 415 41620000522: 417 A new set of binutils went into the tree today. Anybody 418 building a kernel after this point is advised that they need 419 to rebuild their binutils (or better yet do a 420 buildworld/installworld) before building a new kernel. 421 422 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 423 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 424 is recommended that you don't set this option until the problem 425 is resolved. 426 42720000513: 428 The ethernet drivers were all updated to clean up the BPF handling. 429 43020000510: 431 The problems with boot blocks on the alphas have been corrected. 432 This will require some care in updating alphas. A new libstand 433 is requires for the boot blocks to build properly. 434 43520000503: 436 Recompile all kld modules. Proper version dependency info 437 is now available. 438 43920000502: 440 Modules have been disconnected from the buildworld tree and 441 connected to the kernel building instead. 442 44320000427: 444 You may need to build gperf 445 cd /usr/src/gnu/usr.bin/gperf && make depend all install 446 when upgrading from 4.0 -> current. The build system now uses 447 an option only in -current. 448 44920000417: 450 The method that we brand ELF binaries has changed to be more 451 acceptable to the binutils maintainers. You will need to 452 rebrand your ELF binaries that aren't native. One problem 453 binary is the Linux ldconfig. After your make world, but 454 before you reboot, you'll need to issue: 455 brandelf -t Linux /compat/linux/sbin/ldconfig 456 if you have Linux compatibility enabled on your machine. 457 45820000320: 459 If you have really bad/marginal IDE drives, you may find they 460 don't work well. Use pio mode instead. The easiest way to 461 cope if you have a problem combination is to add: 462 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 463 to the start of /etc/rc.conf. 464 46520000319: 466 The ISA and PCI compatibility shims have been connected to the 467 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 468 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 469 include the appropriate option in your kernel config. Drivers 470 using the shims should be updated or they won't ship with 471 5.0-RELEASE, targeted for 2001. 472 47320000318: 474 We've entered the traditional post release dumping party. 475 Large kernel changes are being committed and are in the 476 works. It is important to keep the systems' klds and kernel 477 in sync as kernel interfaces and structures are changing. 478 Before reporting kernel panics, make sure that all modules 479 that you are loading are up to date. 480 48120000315: 482 If you are upgrading from an older version of FreeBSD, you 483 need to update your boot blocks as well. 'disklabel -B ad0' 484 will do the trick. This isn't critical until you remove your 485 wd device entries in /dev, at which point your system will not 486 boot. 487 48820000315: 489 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 490 to upgrade to 4.0 from 3.x. 491 492COMMON ITEMS: 493 494 General Notes 495 ------------- 496 Avoid using make -j when upgrading. From time to time in the 497 past there have been problems using -j with buildworld and/or 498 installworld. This is especially true when upgrading between 499 "distant" versions (eg one that cross a major release boundary 500 or several minor releases, or when several months have passed 501 on the -current branch). 502 503 To build a kernel 504 ----------------- 505 If you are updating from a prior version of FreeBSD (even one just 506 a few days old), you should follow this procedure. With a 507 /usr/obj tree with a fresh buildworld, 508 make buildkernel KERNCONF=YOUR_KERNEL_HERE 509 make installkernel KERNCONF=YOUR_KERNEL_HERE 510 511 To just build a kernel when you know that it won't mess you up 512 -------------------------------------------------------------- 513 cd src/sys/{i386,alpha}/conf 514 config KERNEL_NAME_HERE [1] 515 cd ../../compile/KERNEL_NAME_HERE 516 make depend 517 make 518 make install 519 520 [1] If in doubt, -r might help here. 521 522 If this fails, go to the "To build a kernel" section. 523 524 To rebuild everything and install it on the current system. 525 ----------------------------------------------------------- 526 make world 527 Build a new kernel, see above. 528 529 To upgrade from 4.x-stable to current 530 ------------------------------------- 531 make buildworld 532 make buildkernel KERNCONF=YOUR_KERNEL_HERE 533 cp src/sys/${MACHINE_ARCH}/arch/GENERIC.hints /boot/device.hints [2] 534 make installkernel KERNCONF=YOUR_KERNEL_HERE 535 make installworld 536 [1] 537 <reboot> 538 539 Make sure that you've read the UPDATING file to understand the 540 tweaks to various things you need. At this point in the life 541 cycle of current, things change often and you are on your own 542 to cope. The defaults can also change, so please read ALL of 543 the UPDATING entries. 544 545 Also, if you are tracking -current, you must be subscribed to 546 freebsd-current@freebsd.org. Make sure that before you update 547 your sources that you have read and understood all the recent 548 messages there. If in doubt, please track -stable which has 549 much fewer pitfalls. 550 551 [1] If you have third party modules, such as vmware, you 552 should disable them at this point so they don't crash your 553 system on reboot. 554 555 [2] If you have legacy ISA devices, you may need to create 556 your own device.hints to reflect your unique hardware 557 configuration. 558 559FORMAT: 560 561This file contains a list, in reverse chronological order, of major 562breakages in tracking -current. Not all things will be listed here, 563and it only starts on March 15, 2000. Updating files can found in 564previous releases if your system is older than this. 565 566Please filter your entries through Warner Losh (imp@village.org) so 567that the style, formatting, etc of this file can be maintained. 568 569$FreeBSD: head/UPDATING 73214 2001-02-28 05:45:16Z imp $ 570