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