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