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