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