1 Updating Information for FreeBSD current users
3 This file is maintained by imp@village.org. Please send new entries
4 directly to him. See end of file for further details. For commonly
5 done items, please see the end of the file. Search for 'COMMON
9 DEVFS is now opt out, not opt in. Barring major problems, this
10 will be the only way to go starting July 1.
13 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
16 Building perl was broken at 02:25:25 PDT.
19 The bug in 20010429 was corrected at 07:35:37 PDF. It is safe to
23 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
24 this date, but before the correction date.
27 old fsck and new kernel interactions appear to have been fixed.
30 fsck and the kernel were changed to handle some optimizations
31 to directory layout. This breaks backward compatibility.
32 Update only if you understand that you must not use the old
33 fsck with the new kernel ever.
36 fsck has changed the meaning of the pass column in /etc/fstab.
37 Please see the cvs commit to fsck.8 or the fsck.8 man page fora
38 details. It is unclear if changes to /etc/fstab are necessary.
41 portmap had changed name to rpcbind for maximum POLA in your
42 current world. /etc/hosts.{allow,deny} needs changes. nfs and
43 other rpc based programs that rely on portmapper will not work
44 without updates to /etc/hosts.{allow,deny} and /etc/netcofnig.
47 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
48 and ATA_ENABEL_TAGS are no longer kernel options. They have
49 been replaced by tunables. See ata.4 for details.
52 The fxp driver was converted to use miibus. If you compile
53 fxp into your kernel statically, you will need to add miibus.
56 The wi device now defaults to BSS (infrastructure) mode
60 /dev/urandmon should be a sumbolic link to /dev/random now.
61 Users of current not using DEVFS need to run MAKEDEV std.
62 ssh might not work if you don't.
65 The problems with libc have been corrected. It is now mostly
66 safe to go back into the water.
69 The size of FILE was changed. This breaks upgrading. If
70 you must upgrade, be prepared for pain. It also breaks almost
71 all binaries that you've compiled on -current. You are warned
72 that before upgrading would be a good time to do a level 0
73 dump of your system. No, really, I mean it this time.
75 To get to the new system, you'll need to use the following
76 workaround. Hopefully this can be sorted out so that we
77 don't have to move this to the updating section.
79 To get around the installworld problem, do:
80 # cd /usr/src/usr.bin/sed
84 If that doesn't work, then try:
85 # make -k installworld
89 DEVFS is now the default. If you use vinum, make sure that you
90 do not include devfs in your kernel as problems result.
93 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
94 Remove them from your config.
97 ****************************** WARNING ******************************
98 buildkernel has been changed slightly
99 ****************************** WARNING ******************************
100 KERNCONF replaces the variable KERNEL for buildkernel. You
101 should update your scripts and make.conf accordingly.
104 config has changed to allow DEV_FOO as a replacement for NFOO.
105 This requires a new config to build correctly.
108 The kerrnel option I386_CPU is now mutually exclusive with the
109 other cpu types. If you have an i386 system, be sure that it
110 only had this line. Remove it for all other configurations.
113 Changes to the kernel require it and burncd be in sync.
116 Everyone who has hw.sndunit set to something in
117 /etc/sysctl.conf, it is now hw.snd.unit.
120 ex and vi were broken by some changes to sys/queue.h. If you
121 have a bad vi, you will see make buildworld fail with a core
122 dump while building termcap. You can work around this problem
123 by adding -k to your make buildworld. This will cause the
124 build to complete and install a new vi. Once that's done, you
125 can rebuild again without the -k to pick up anything that
126 might have been ignored by the -k option.
128 Others have suggested that you can just rebuild libc if your
129 vi/ex is dynamically linked, but I've not received any reports
133 There have been some changes to libcrypt in -current. The
134 libscrypt/libdescrypt symlink sillyness is gone and the installed
135 libcrypt is fully functional. Be aware of this.
138 Linksys Fast Ethernet PCCARD cards supported by the ed driver
139 now require the addition of flag 0x80000 to their config line
140 in pccard.conf(5). This flag is not optional. These Linksys
141 cards will not be recognized without it.
144 Important new FreeBSD-version stuff: PAM support has been worked
145 in, partially from the "Unix" OpenSSH version. This requires
146 adding the following in pam.conf:
148 sshd auth sufficient pam_skey.so
149 sshd auth required pam_unix.so try_first_pass
150 sshd session required pam_permit.so
156 The random device needs more entropy, so you need to make sure
157 that you've run mergemaster to get a /etc/rc which will seed
158 /dev/random. If you don't and the system hangs after ldconfig,
159 then banging on the keyboard randomly until it unhangs is one
163 ****************************** WARNING ******************************
164 Sendmail has been updated.
165 ****************************** WARNING ******************************
166 o mail.local(8) is no longer installed as a set-user-id binary.
167 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
169 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
171 o Now using sendmail's version of vacation(1).
172 o The sendmail cf building tools (contrib/sendmail/cf) are installed
173 in /usr/share/sendmail/cf.
174 o sendmail.cw changed to local-host-names
176 More details can be found at
177 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
180 The ports tree's new layout is in place. Be sure to update
181 your entire ports tree, or you will have problems.
184 The perl build procedure no longer installs miniperl, nor uses
185 the installed miniperl. It is recommended that you delete
189 This weekend the ports tree will be updated to a new layout.
190 It will be in an inconsistent state until noted in the UPDATING
191 file, or with asami-san's message to the relevant mailing
192 lists. With this new layout, you'll need to update the whole
193 tree for anything to work.
196 There was a change in the passwd format. Need more information.
199 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
200 place. Please update boot loader (not the boot blocks) at the
201 same time as your kernel.
204 The new pmtimer device is necessary for laptops. Failure to
205 include the device will cause suspended laptops losing time
206 when they resume. Include
208 in your config file and
209 hint.pmtimer.0.at="isa"
210 to your /boot/device.hints file.
213 The random device has been turned into a (pseudo-)device,
214 rather than an option. The supplied kernel config files have
215 been updated. You will need to do something similar in your
216 own kernel config file.
221 If you prefer to load the loadable module, you need to do
225 The random device module has been renamed from randomdev.ko to
226 random.ko. You will need to edit your /boot/loader.conf to
227 reflect this if you load this module at boot time.
228 The line should read:
232 The SMPNG commit has happened. It should work, but if it
233 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
234 to be a variety of minor issues. Please see 20000905 to make
235 sure you don't have model loading problems which might at
236 first blush appear related to SMP.
239 nsswitch has been imported from NetBSD. Among other things,
240 this means that /etc/host.conf is no longer used. See
241 nsswitch.conf(5) instead. Note that at boot time rc.network
242 will attempt to produce a new nsswitch.conf file for you if you
243 don't have one, and you have host.conf.
246 The ucred structure changed size. This breaks the interface
247 that mountd uses. Trying to use an older mountd with a newer
248 kernel guarantees a panic. This means that you need to use
249 kernels newer than today only with matching mountd, but you
250 needed to do that anyway with the boot loader changes.
253 The boot loader has been updated. The new default kernel is
254 now /boot/kernel/kernel.ko. The new default module location
257 You *MUST* upgrade your boot loader and kernel at the same time.
258 The easiest way to do this is to do the buildworld/buildkernel/
259 installkernel/installworld dance.
261 Furthermore, you are urged to delete your old /modules directory
262 before booting the new kernel, since kldload will find stale
263 modules in that directory instead of finding them in the correct
264 path, /boot/kernel. The most common complaint that this cures
265 is that the linux module crashes your machine after the update.
267 if [ ! -d /boot/kernel.old ]; then
268 mv /modules.old /boot/kernel.old
269 chflags noschg /kernel.old
270 mv /kernel.old /boot/kernel.old/kernel.ko
271 chflags schg /boot/kernel.old/kernel.ko
275 A new issue with the sendmail upgrade has come to light.
276 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
277 incorrectly install the default aliases in /etc/mail rather than
278 move the old one from /etc. So you'll need to manually move the
279 file, create a symbolic link, remove the old /etc/aliases.db and
280 run newaliases. For safety sake, you should stop sendmail
281 while doing this and run the upgrade when locally sourced email
282 is not likely to be generated.
285 /boot/device.hints is now required for installkernel to
286 succeed. You should copy GENERIC.hints for your architecture
287 into /boot/device.hints. If and only if you compile hints
288 into your kernel, then this file may be empty. Please note,
289 if you have an empty or missing /boot/device.hints file and
290 you neglected to compile hints into your kernel, no boot
291 messages will appear after the boot loader tries to start the
295 If you do NOT have ``options RANDOMDEV'' in your kernel and
296 you DO want the random device then add randomdev_load="YES" to
300 suidperl is now always built and installed on the system, but
301 with permissions of 511. If you have applications that use
302 this program, you are now required to add ENABLE_SUIDPERL=true
303 to /etc/make.conf. If you forget to do this,
304 chmod 4511 /usr/bin/suidperl
305 will fix this until the next build.
308 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
309 visible changes that may immediately affect your configuration
311 - New default file locations from src/contrib/sendmail/cf/README
312 - newaliases limited to root and trusted users
313 - MSA port (587) turned on by default
314 - New queue file naming system so can't go from 8.11 -> 8.9
315 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
316 - FEATURE(`nullclient') is more full featured
317 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
318 - mail.local FreeBSD-only -b option changed to -B
319 - See src/contrib/sendmail/RELEASE_NOTES for more info
322 suidperl (aka sperl) is no longer build by default. You must
323 specifically define BUILD_SUIDPERL to "true" for it to be build.
324 Furthermore, we recommend that you remove /usr/bin/sperl* and
325 /usr/bin/suidperl files from your system unless you have a
329 Networking defaults have been tightened. Anybody upgrading
330 /etc/defaults/rc.conf needs to add the following lines to
331 /etc/rc.conf if they want to have the same setup
332 afterwards (unless the variables already are set, of course):
333 # Enable network daemons for user convenience.
336 sendmail_enable="YES"
339 If you have null_load="YES" in your /boot/loader.conf, you
340 will need to change that to nullfs_load="YES".
343 The "installkernel" target has changed slightly. Now even if
344 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
345 it will install the MYKERNEL file (built with the buildkernel
346 target) as /kernel rather than /MYKERNEL. Those who have
347 updated their /boot/loader.conf files to point to /MYKERNEL
348 should remove that entry or perform manual rename of /kernel
352 If you use CVSUP or CTM to get CVS trees, AND you used to get
353 the old crypto files from internat.freebsd.org AND you check
354 out files from the CVS tree with the cvs command, please read
355 http://people.freebsd.org/~imp/internat.txt
356 for details on potential problems that you might have and how
359 If you are merely a mirror, or don't answer yes to each of the
360 clauses above, you needn't worry.
363 /etc/security has been updated to print the inode number of
364 setuid programs that have changed. You will see a large spike
365 in the number of changed programs the first time when you run
366 mergemaster to get a new /etc/security.
369 /dev/random now has good entropy collection (from the keyboard
370 and sysmouse drivers). Please ensure that either `options
371 RANDOMDEV' is present in your kernel config file or that
372 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
373 not have the /dev/random driver, OpenSSL (and consequently
374 lots of crypto tools (like SSH)) will fail with strange
375 errors. (see below, 20000624).
377 FreeBSD-current is safe again to run Crypto.
380 phk made the malloc default options AJ. This may slow things
381 down and uncover other latent bugs in the code. If you need to
382 run at full speed, you can disable this by doing the following:
383 ln -s aj /etc/malloc.conf
386 libftpio's version was accidentally bumped a few days ago. This
387 has been corrected. You may need to remove /usr/lib/libftpio.so.6
388 before doing your next buildworld/installworld pair. It certainly
389 won't hurt to remove it before the update procedure. It will
390 break fetch until a new one is built, but ftp can be used in the
394 The crypto packages have changed for the cvsup. This has been done
395 in a backward compatible way, but the old packages will go away at
396 some point in the future. Look at /usr/share/examples/cvsup for
400 With the new sys/modules/sound/drivers/*, you will need to
401 set SYSDIR until you do an installworld after July 7th.
404 rc.shutdown and rc will now call the rc.d scripts with start
405 or stop. This may cause some harmless warnings from older
406 rc.d scripts that haven't been updated.
409 The libfetch based version of fetch has gone into the tree.
410 Minor problems may result on some of the less popular sites,
411 which should be reported to des@freebsd.org.
414 From approximately this date forward, one must have the crypto
415 system installed in order to build the system and kernel.
416 While not technically strictly true, one should treat it as
417 required and grab the crypto bits. If you are grabbing CVS
418 trees, src-all and cvs-crypto should be treated as if they
419 were required. You should check with the latest collections
420 to make sure that these haven't changed.
423 Mark Murray just committed the first parts of a cleanup of
424 /dev/zero, et al. This is also cleaning up /dev/random.
425 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
426 -CURRENT FROM THIS POINT FORWARD for cryptographic services
427 until Mark can merge in the fixes to this work in progress.
428 openssh and openssl should not be used to generate keys from this
429 date to the completion of the work.
431 If you must operate at this reduced level of security, add '
432 options RANDOMDEV' to your kernel or modload the randomdev
433 module. You may also need to copy a new MAKEDEV to /dev and
434 recreate the random and urandom devices.
437 The license on the softupdates is now a standard 2 clause
438 BSD license. You may need to remove your symbolic links
439 that used to be required when updating.
442 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
443 the config file update procedure.
444 http://people.freebsd.org/~imp/config-upd.html
445 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
446 isn't buildable. However, you can generate a LINT file.
449 Binutils 2.10 have hit the tree, or will shortly. As soon
450 as they do, the problem noted in 20000522 will be resolved and
451 that workaround will no longer be required.
454 phk removed the compatibility creation of wd devices in the
455 ad driver. If you haven't done so already, you must update
456 your fstab, etc to use the ad devices instead of the wd
459 In addition, you'll need to update your boot blocks to a
460 more modern version, if you haven't already done so. Modern
461 here means 4.0 release or newer (although older releases
465 Peter took an axe to config(8). Be sure that you read his mail
466 on the topic before even thinking about updating. You will
467 need to create a /boot/device.hints or add a hints directive
468 to your config file to compile them in statically. The format
469 of the config file has changed as well. Please see GENERIC or
470 NEWCARD for examples of the new format.
473 A new set of binutils went into the tree today. Anybody
474 building a kernel after this point is advised that they need
475 to rebuild their binutils (or better yet do a
476 buildworld/installworld) before building a new kernel.
478 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
479 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
480 is recommended that you don't set this option until the problem
484 The ethernet drivers were all updated to clean up the BPF handling.
487 The problems with boot blocks on the alphas have been corrected.
488 This will require some care in updating alphas. A new libstand
489 is requires for the boot blocks to build properly.
492 Recompile all kld modules. Proper version dependency info
496 Modules have been disconnected from the buildworld tree and
497 connected to the kernel building instead.
500 You may need to build gperf
501 cd /usr/src/gnu/usr.bin/gperf && make depend all install
502 when upgrading from 4.0 -> current. The build system now uses
503 an option only in -current.
506 The method that we brand ELF binaries has changed to be more
507 acceptable to the binutils maintainers. You will need to
508 rebrand your ELF binaries that aren't native. One problem
509 binary is the Linux ldconfig. After your make world, but
510 before you reboot, you'll need to issue:
511 brandelf -t Linux /compat/linux/sbin/ldconfig
512 if you have Linux compatibility enabled on your machine.
515 If you have really bad/marginal IDE drives, you may find they
516 don't work well. Use pio mode instead. The easiest way to
517 cope if you have a problem combination is to add:
518 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
519 to the start of /etc/rc.conf.
522 The ISA and PCI compatibility shims have been connected to the
523 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
524 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
525 include the appropriate option in your kernel config. Drivers
526 using the shims should be updated or they won't ship with
527 5.0-RELEASE, targeted for 2001.
530 We've entered the traditional post release dumping party.
531 Large kernel changes are being committed and are in the
532 works. It is important to keep the systems' klds and kernel
533 in sync as kernel interfaces and structures are changing.
534 Before reporting kernel panics, make sure that all modules
535 that you are loading are up to date.
538 If you are upgrading from an older version of FreeBSD, you
539 need to update your boot blocks as well. 'disklabel -B ad0'
540 will do the trick. This isn't critical until you remove your
541 wd device entries in /dev, at which point your system will not
545 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
546 to upgrade to 4.0 from 3.x.
552 Avoid using make -j when upgrading. From time to time in the
553 past there have been problems using -j with buildworld and/or
554 installworld. This is especially true when upgrading between
555 "distant" versions (eg one that cross a major release boundary
556 or several minor releases, or when several months have passed
557 on the -current branch).
561 If you are updating from a prior version of FreeBSD (even one just
562 a few days old), you should follow this procedure. With a
563 /usr/obj tree with a fresh buildworld,
564 make buildkernel KERNCONF=YOUR_KERNEL_HERE
565 make installkernel KERNCONF=YOUR_KERNEL_HERE
567 To just build a kernel when you know that it won't mess you up
568 --------------------------------------------------------------
569 cd src/sys/{i386,alpha}/conf
570 config KERNEL_NAME_HERE [1]
571 cd ../../compile/KERNEL_NAME_HERE
576 [1] If in doubt, -r might help here.
578 If this fails, go to the "To build a kernel" section.
580 To rebuild everything and install it on the current system.
581 -----------------------------------------------------------
583 Build a new kernel, see above.
585 To upgrade from 4.x-stable to current
586 -------------------------------------
588 make buildkernel KERNCONF=YOUR_KERNEL_HERE
589 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
590 make installkernel KERNCONF=YOUR_KERNEL_HERE
596 Make sure that you've read the UPDATING file to understand the
597 tweaks to various things you need. At this point in the life
598 cycle of current, things change often and you are on your own
599 to cope. The defaults can also change, so please read ALL of
600 the UPDATING entries.
602 Also, if you are tracking -current, you must be subscribed to
603 freebsd-current@freebsd.org. Make sure that before you update
604 your sources that you have read and understood all the recent
605 messages there. If in doubt, please track -stable which has
608 [1] If you have third party modules, such as vmware, you
609 should disable them at this point so they don't crash your
612 [2] If you have legacy ISA devices, you may need to create
613 your own device.hints to reflect your unique hardware
618 This file contains a list, in reverse chronological order, of major
619 breakages in tracking -current. Not all things will be listed here,
620 and it only starts on March 15, 2000. Updating files can found in
621 previous releases if your system is older than this.
623 Please filter your entries through Warner Losh (imp@village.org) so
624 that the style, formatting, etc of this file can be maintained.