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