UPDATING revision 66004
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 820000916: 9 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken 10 place. Please update boot loader (not the boot blocks) at the 11 same time as your kernel. 12 1320000914: 14 The new pmtimer device is necessary for laptops. Failure to 15 include the device will cause suspended laptops losing time 16 when they resume. Include 17 device pmtimer 18 in your config file and 19 hint.pmtimer.0.at="isa" 20 to your /boot/device.hints file. 21 2220000911: 23 The random device has been turned into a (pseudo-)device, 24 rather than an option. The supplied kernel config files have 25 been updated. You will need to do something similar in your 26 own kernel config file. 27 Remove: 28 options RANDOMDEV 29 Add: 30 device random 31 If you prefer to load the loadable module, you need to do 32 nothing. 33 3420000909: 35 The random device module has been renamed from randomdev.ko to 36 random.ko. You will need to edit your /boot/loader.conf to 37 reflect this if you load this module at boot time. 38 The line should read: 39 random_load="YES" 40 4120000907: 42 The SMPNG commit has happened. It should work, but if it 43 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely 44 to be a variety of minor issues. Please see 20000905 to make 45 sure you don't have model loading problems which might at 46 first blush appear related to SMP. 47 4820000906: 49 nsswitch has been imported from NetBSD. Among other things, 50 this means that /etc/host.conf is no longer used. See 51 nsswitch.conf(5) instead. Note that at boot time rc.network 52 will attempt to produce a new nsswitch.conf file for you if you 53 don't have one, and you have host.conf. 54 5520000905: 56 The ucred structure changed size. This breaks the interface 57 that mountd uses. Trying to use an older mountd with a newer 58 kernel guarantees a panic. This means that you need to use 59 kernels newer than today only with matching mountd, but you 60 needed to do that anyway with the boot loader changes. 61 6220000905: 63 The boot loader has been updated. The new default kernel is 64 now /boot/kernel/kernel.ko. The new default module location 65 is /boot/kernel. 66 67 You *MUST* upgrade your boot loader and kernel at the same time. 68 The easiest way to do this is to do the buildworld/buildkernel/ 69 installkernel/installworld dance. 70 71 Furthermore, you are urged to delete your old /modules directory 72 before booting the new kernel, since kldload will find stale 73 modules in that directory instead of finding them in the correct 74 path, /boot/kernel. The most common complaint that this cures 75 is that the linux module crashes your machine after the update. 76 77 if [ ! -d /boot/kernel.old ]; then 78 mv /modules.old /boot/kernel.old 79 chflags noschg /kernel.old 80 mv /kernel.old /boot/kernel.old/kernel.ko 81 chflags schg /boot/kernel.old/kernel.ko 82 fi 83 8420000904: 85 A new issue with the sendmail upgrade has come to light. 86 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will 87 incorrectly install the default aliases in /etc/mail rather than 88 move the old one from /etc. So you'll need to manually move the 89 file, create a symbolic link, remove the old /etc/aliases.db and 90 run newaliases. For safety sake, you should stop sendmail 91 while doing this and run the upgrade when locally sourced email 92 is not likely to be generated. 93 9420000825: 95 /boot/device.hints is now required for installkernel to 96 succeed. You should copy GENERIC.hints for your architecture 97 into /boot/device.hints. If and only if you compile hints 98 into your kernel, then this file may be empty. Please note, 99 if you have an empty or missing /boot/device.hints file and 100 you neglected to compile hints into your kernel, no boot 101 messages will appear after the boot loader tries to start the 102 kernel. 103 10420000821: 105 If you do NOT have ``options RANDOMDEV'' in your kernel and 106 you DO want the random device then add randomdev_load="YES" to 107 /boot/loader.conf. 108 10920000812: 110 suidperl is now always built and installed on the system, but 111 with permissions of 511. If you have applications that use 112 this program, you are now required to add ENABLE_SUIDPERL=true 113 to /etc/make.conf. If you forget to do this, 114 chmod 4511 /usr/bin/suidperl 115 will fix this until the next build. 116 11720000812: 118 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more 119 visible changes that may immediately affect your configuration 120 include: 121 - New default file locations from src/contrib/sendmail/cf/README 122 - newaliases limited to root and trusted users 123 - MSA port (587) turned on by default 124 - New queue file naming system so can't go from 8.11 -> 8.9 125 - FEATURE(`rbl') renamed to FEATURE(`dnsbl') 126 - FEATURE(`nullclient') is more full featured 127 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' 128 - mail.local FreeBSD-only -b option changed to -B 129 - See src/contrib/sendmail/RELEASE_NOTES for more info 130 13120000810: 132 suidperl (aka sperl) is no longer build by default. You must 133 specifically define BUILD_SUIDPERL to "true" for it to be build. 134 Furthermore, we recommend that you remove /usr/bin/sperl* and 135 /usr/bin/suidperl files from your system unless you have a 136 specific use for it. 137 13820000729: 139 Networking defaults have been tightened. Anybody upgrading 140 /etc/defaults/rc.conf needs to add the following lines to 141 /etc/rc.conf if they want to have the same setup 142 afterwards (unless the variables already are set, of course): 143 # Enable network daemons for user convenience. 144 inetd_enable="YES" 145 portmap_enable="YES" 146 sendmail_enable="YES" 147 14820000728: 149 If you have null_load="YES" in your /boot/loader.conf, you 150 will need to change that to nullfs_load="YES". 151 15220000728: 153 The "installkernel" target has changed slightly. Now even if 154 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL' 155 it will install the MYKERNEL file (built with the buildkernel 156 target) as /kernel rather than /MYKERNEL. Those who have 157 updated their /boot/loader.conf files to point to /MYKERNEL 158 should remove that entry or perform manual rename of /kernel 159 to /MYKERNEL. 160 16120000711: 162 If you use CVSUP or CTM to get CVS trees, AND you used to get 163 the old crypto files from internat.freebsd.org AND you check 164 out files from the CVS tree with the cvs command, please read 165 http://people.freebsd.org/~imp/internat.txt 166 for details on potential problems that you might have and how 167 to get around them. 168 169 If you are merely a mirror, or don't answer yes to each of the 170 clauses above, you needn't worry. 171 17220000711: 173 /etc/security has been updated to print the inode number of 174 setuid programs that have changed. You will see a large spike 175 in the number of changed programs the first time when you run 176 mergemaster to get a new /etc/security. 177 17820000710: 179 /dev/random now has good entropy collection (from the keyboard 180 and sysmouse drivers). Please ensure that either `options 181 RANDOMDEV' is present in your kernel config file or that 182 `randomdev_load="YES"' is in your /boot/loader.conf. If you do 183 not have the /dev/random driver, OpenSSL (and consequently 184 lots of crypto tools (like SSH)) will fail with strange 185 errors. (see below, 20000624). 186 187 FreeBSD-current is safe again to run Crypto. 188 18920000709: 190 phk made the malloc default options AJ. This may slow things 191 down and uncover other latent bugs in the code. If you need to 192 run at full speed, you can disable this by doing the following: 193 ln -s aj /etc/malloc.conf 194 19520000706: 196 libftpio's version was accidentally bumped a few days ago. This 197 has been corrected. You may need to remove /usr/lib/libftpio.so.6 198 before doing your next buildworld/installworld pair. It certainly 199 won't hurt to remove it before the update procedure. It will 200 break fetch until a new one is built, but ftp can be used in the 201 interim if needed. 202 20320000705: 204 The crypto packages have changed for the cvsup. This has been done 205 in a backward compatible way, but the old packages will go away at 206 some point in the future. Look at /usr/share/examples/cvsup for 207 details. 208 20920000704: 210 With the new sys/modules/sound/drivers/*, you will need to 211 set SYSDIR until you do an installworld after July 7th. 212 21320000704: 214 rc.shutdown and rc will now call the rc.d scripts with start 215 or stop. This may cause some harmless warnings from older 216 rc.d scripts that haven't been updated. 217 21820000630: 219 The libfetch based version of fetch has gone into the tree. 220 Minor problems may result on some of the less popular sites, 221 which should be reported to des@freebsd.org. 222 22320000625: 224 From approximately this date forward, one must have the crypto 225 system installed in order to build the system and kernel. 226 While not technically strictly true, one should treat it as 227 required and grab the crypto bits. If you are grabbing CVS 228 trees, src-all and cvs-crypto should be treated as if they 229 were required. You should check with the latest collections 230 to make sure that these haven't changed. 231 23220000624: 233 Mark Murray just committed the first parts of a cleanup of 234 /dev/zero, et al. This is also cleaning up /dev/random. 235 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD 236 -CURRENT FROM THIS POINT FORWARD for cryptographic services 237 until Mark can merge in the fixes to this work in progress. 238 openssh and openssl should not be used to generate keys from this 239 date to the completion of the work. 240 241 If you must operate at this reduced level of security, add ' 242 options RANDOMDEV' to your kernel or modload the randomdev 243 module. You may also need to copy a new MAKEDEV to /dev and 244 recreate the random and urandom devices. 245 24620000622: 247 The license on the softupdates is now a standard 2 clause 248 BSD license. You may need to remove your symbolic links 249 that used to be required when updating. 250 25120000621: 252 Scott Flatman <sf@aracnet.com> sent in a decent write-up on 253 the config file update procedure. 254 http://people.freebsd.org/~imp/config-upd.html 255 NOTE: LINT is gone. It has been replaced with NOTES. NOTES 256 isn't buildable. However, you can generate a LINT file. 257 25820000620: 259 Binutils 2.10 have hit the tree, or will shortly. As soon 260 as they do, the problem noted in 20000522 will be resolved and 261 that workaround will no longer be required. 262 26320000615: 264 phk removed the compatibility creation of wd devices in the 265 ad driver. If you haven't done so already, you must update 266 your fstab, etc to use the ad devices instead of the wd 267 devices. 268 269 In addition, you'll need to update your boot blocks to a 270 more modern version, if you haven't already done so. Modern 271 here means 4.0 release or newer (although older releases 272 may work). 273 27420000612: 275 Peter took an axe to config(8). Be sure that you read his mail 276 on the topic before even thinking about updating. You will 277 need to create a /boot/device.hints or add a hints directive 278 to your config file to compile them in statically. The format 279 of the config file has changed as well. Please see GENERIC or 280 NEWCARD for examples of the new format. 281 28220000522: 283 A new set of binutils went into the tree today. Anybody 284 building a kernel after this point is advised that they need 285 to rebuild their binutils (or better yet do a 286 buildworld/installworld) before building a new kernel. 287 288 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf 289 or MALLOC_OPTIONS env var) J will cause ld to dump core. It 290 is recommended that you don't set this option until the problem 291 is resolved. 292 29320000513: 294 The ethernet drivers were all updated to clean up the BPF handling. 295 29620000510: 297 The problems with boot blocks on the alphas have been corrected. 298 This will require some care in updating alphas. A new libstand 299 is requires for the boot blocks to build properly. 300 30120000503: 302 Recompile all kld modules. Proper version dependency info 303 is now available. 304 30520000502: 306 Modules have been disconnected from the buildworld tree and 307 connected to the kernel building instead. 308 3092000427: 310 You may need to build gperf 311 cd /usr/src/gnu/usr.bin/gperf && make depend all install 312 when upgrading from 4.0 -> current. The build system now uses 313 an option only in -current. 314 31520000417: 316 The method that we brand ELF binaries has changed to be more 317 acceptable to the binutils maintainers. You will need to 318 rebrand your ELF binaries that aren't native. One problem 319 binary is the Linux ldconfig. After your make world, but 320 before you reboot, you'll need to issue: 321 brandelf -t Linux /compat/linux/sbin/ldconfig 322 if you have Linux compatibility enabled on your machine. 323 32420000320: 325 If you have really bad/marginal IDE drives, you may find they 326 don't work well. Use pio mode instead. The easiest way to 327 cope if you have a problem combination is to add: 328 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio 329 to the start of /etc/rc.conf. 330 33120000319: 332 The ISA and PCI compatibility shims have been connected to the 333 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old 334 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must 335 include the appropriate option in your kernel config. Drivers 336 using the shims should be updated or they won't ship with 337 5.0-RELEASE, targeted for 2001. 338 33920000318: 340 We've entered the traditional post release dumping party. 341 Large kernel changes are being committed and are in the 342 works. It is important to keep the systems' klds and kernel 343 in sync as kernel interfaces and structures are changing. 344 Before reporting kernel panics, make sure that all modules 345 that you are loading are up to date. 346 34720000315: 348 If you are upgrading from an older version of FreeBSD, you 349 need to update your boot blocks as well. 'disklabel -B ad0' 350 will do the trick. This isn't critical until you remove your 351 wd device entries in /dev, at which point your system will not 352 boot. 353 35420000315: 355 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how 356 to upgrade to 4.0 from 3.x. 357 358COMMON ITEMS: 359 360 General Notes 361 ------------- 362 Avoid using make -j when upgrading. From time to time in the 363 past there have been problems using -j with buildworld and/or 364 installworld. This is especially true when upgrading between 365 "distant" versions (eg one that cross a major release boundary 366 or several minor releases, or when several months have passed 367 on the -current branch). 368 369 To build a kernel 370 ----------------- 371 If you are updating from a prior version of FreeBSD (even one just 372 a few days old), you should follow this procedure. With a 373 /usr/obj tree with a fresh buildworld, 374 make buildkernel KERNEL=YOUR_KERNEL_HERE 375 make installkernel KERNEL=YOUR_KERNEL_HERE 376 377 To just build a kernel when you know that it won't mess you up 378 -------------------------------------------------------------- 379 cd src/sys/{i386,alpha}/conf 380 config KERNEL_NAME_HERE [1] 381 cd ../../compile/KERNEL_NAME_HERE 382 make depend 383 make 384 make install 385 386 [1] If in doubt, -r might help here. 387 388 If this fails, go to the "To build a kernel" section. 389 390 To rebuild everything and install it on the current system. 391 ----------------------------------------------------------- 392 make world 393 Build a new kernel, see above. 394 395 To upgrade from 4.x-stable to current 396 ------------------------------------- 397 make buildworld 398 make buildkernel KERNEL=YOUR_KERNEL_HERE 399 cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2] 400 make installkernel KERNEL=YOUR_KERNEL_HERE 401 make installworld 402 [1] 403 <reboot> 404 405 Make sure that you've read the UPDATING file to understand the 406 tweaks to various things you need. At this point in the life 407 cycle of current, things change often and you are on your own 408 to cope. The defaults can also change, so please read ALL of 409 the UPDATING entries. 410 411 Also, if you are tracking -current, you must be subscribed to 412 freebsd-current@freebsd.org. Make sure that before you update 413 your sources that you have read and understood all the recent 414 messages there. If in doubt, please track -stable which has 415 much fewer pitfalls. 416 417 [1] If you have third party modules, such as vmware, you 418 should disable them at this point so they don't crash your 419 system on reboot. 420 421 [2] If you have legacy ISA devices, you may need to create 422 your own device.hints to reflect your unique hardware 423 configuration. 424 425FORMAT: 426 427This file contains a list, in reverse chronological order, of major 428breakages in tracking -current. Not all things will be listed here, 429and it only starts on March 15, 2000. Updating files can found in 430previous releases if your system is older than this. 431 432Please filter your entries through Warner Losh (imp@village.org) so 433that the style, formatting, etc of this file can be maintained. 434 435$FreeBSD: head/UPDATING 66004 2000-09-17 21:01:30Z imp $ 436