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