1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 NOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW:
8 FreeBSD 5.0-CURRENT has many debugging features turned on, in
9 both the kernel and userland. These features attempt to detect
10 incorrect use of system primitives, and encourage loud failure
11 through extra sanity checking and fail stop semantics. They
12 also substantially impact system performance. If you want to
13 do performance measurement, benchmarking, and optimization,
14 you'll want to turn them off. This includes various WITNESS-
15 related kernel options, INVARIANTS, malloc debugging flags
16 in userland, and various verbose features in the kernel. Many
17 developers choose to disable these features on build machines
18 to maximize performance.
20 In addition, IDE write caching is currently disabled by default
21 due to on-going concerns about disk write order and file system
22 integrity. Re-enabling write caching can substantially improve
26 Our /etc/termcap now has all the entries from the XFree86 xterm
27 almost unchanged. This means xterm now supports color by default.
28 If you used TERM=xterm-color in the past you now should use
29 TERM=xterm. (xterm-color will lead to benign warnings).
32 A "bug" in gcc(1) that was hiding warning in system headers was
33 fixed. It's probably time to add -DNO_WERROR to your make line
37 COPY is being deprecated. The 20010530 change was reverted, as
38 it causes far more pain than was expected, and to always compare
39 before installing, please use INSTALL="install -C" again. The
40 -C option is now silently ignored when used with the -d option.
43 Problems with libc_r clients like KDE and GNOME have been resolved.
44 There are still some minor problems with some signals but the
45 system is stable enough for general use again. SMP is less so than UP
46 but each can successfully complete multiple buildworlds.
47 Libkvm needs to be recompiled due to KSE.
50 Now would be a bad time to upgrade. Something in or near the
51 KSE commit totally broke programs using libc_r like KDE and
55 The k5su utility installed as part of Kerberos 5 is no longer
56 installed with the set-user-ID bit set by default. Add
57 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
58 with the set-user-ID bit set.
61 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
62 Unfortunately our native GDB (at version 4.18) does not understand
63 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
64 generated debugging information for our native GDB.
67 Due to the way CVS works, it may not properly update src/contrib/gcc
68 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
69 and then do a cvs update.
72 When exec'ing set[ug]id executables, the kernel now ensures that the
73 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
76 New sendmail startup scripts have been installed to make it
77 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
78 variable sendmail_enable to "NO" no longer prevents any sendmail
79 daemons from starting. Instead, either set sendmail_enable to
80 "NONE" or change mta_start_script to a script for starting
81 an alternative MTA. Setting mta_start_script to "" will
82 also prevent any MTA from being started at boot.
85 UCONSOLE is no longer a valid kernel option.
88 FreeBSD 5.0 DP-1 was basically branched today.
91 Warnings are now errors in the kernel. Unless you are a developer,
92 you should add -DNO_WERROR to your make line.
95 sendmail 8.12.2 has been imported. The sendmail binary is no
96 longer a set-user-ID root binary and the infrastructure to support
97 command line mail submission has changed. Be sure to run
98 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
99 and /etc/mail) and read /etc/mail/README for more details.
101 Due to the import of sendmail 8.12.2, a new user and group are
102 required in order for sendmail to run as a set-group-ID
103 binary. A 'make installworld' will use the new user and group
104 to set the owner and group of /var/spool/clientmqueue and will
105 fail if the new user and group do not exist. The 'smmsp' user
106 and group must be merged from src/etc/group and
107 src/etc/master.passwd before using 'make installworld'.
108 'mergemaster -p' will do this. You may need to install
109 mergemaster before this will work if you are updating from a
110 very old version of current. The updating recipe has changed
114 The preferred configuration method for PAM is now /etc/pam.d/
115 rather than /etc/pam.conf. If you have an unmodified
116 pam.conf, just delete it after your next mergemaster run. If
117 you have local modifications, you can use
118 /usr/src/etc/pam.d/convert.pl to incorporate them into your
121 Please see the following url for more details:
122 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
124 If anyone here is already using the new rc.conf(5) variable
125 networkfs_types, please note that it has changed
126 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
129 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
130 started out its life in the ISDN4BSD project as an offspring
131 from sys/net/if_spppsubr.c, which eventually got a life of its
132 own. All the accumulated features and bugfixes of the i4b
133 version have now been merged back into the base system's
134 version now. The only user-visible change resulting from this
135 is that i4b's sppp(4) interfaces are to be managed with
136 spppcontrol(8) again, since ispppcontrol(8) has been retired
137 as well. (There has never been rc file support for
138 ispppcontrol in -current, but only in -stable. That will be
139 reverted by the time the changes are MFCed.)
142 The fdc(4) driver has been updated and now automatically
143 recognizes media in `standard' formats (like 1440 KB and
144 720 KB for a 3.5" high-density drive) when accessing the
145 default device node (e. g. /dev/fd0). The old variety of
146 floppy device nodes /dev/fd*.* is no longer present by
147 default, devices can be created (in DEVFS) on demand. They
148 will need to be customized then for `odd' densities using
152 The bugs in procfs' debugging support code have been fixed,
153 and truss(1) now works again.
156 Daily security checks have been split out to use the periodic(8)
157 scripts. Some change in configuration may be necessary. Please
159 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
163 sos added VCD/SVCD support to ata driver and that needs the
164 kernel and burncd to be in sync.
167 The procfs pseudo-filesystem has now been converted to use the
168 pseudofs framework. If you have 'options PROCFS' in your
169 kernel config, you'll need to add 'options PSEUDOFS' if it's
172 This change temporarily breaks truss(1); use ktrace(1) instead
173 until the issue has been resolved.
176 A security hole in OpenSSH involving `UseLogin yes' has been
180 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
181 after this date. You need to do this only once.
184 Most of the awk issues have been resolved. Some rough
185 edges may be left, but for the most part things should be
186 back to "normal." For CURRENT's usual definition of "normal."
189 Awk has been upgraded to the one true awk from bell labs. Expect
190 choppy waves in the upgrade process.
193 The asr driver problem has been resolved.
196 Due to changes in other parts of the system, the asr driver
197 now causes the system to panic on boot. Do not use it pending
198 correction. Comment it out of any kernel config file that you
199 try to use from this date forward.
202 When crossbuilding, use TARGET=xxx where you used to use
203 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
204 unless you are changing both of them. To cross build pc98 on
205 an alpha, for example, you need to set TARGET=pc98 and
209 The kernel interface that burncd depends on has changed.
210 You must recompile both the kernel and userland applications
214 When crossbuilding, please set TARGET_ARCH rather than
215 MACHINE_ARCH to indicate the target. In the future, one will
216 set TARGET_MACHINE where you set MACHINE now. At the moment,
217 setting MACHINE alone for same MACHINE_ARCH machines works
218 (eg, you can build pc98 on a i386 machine and vice versa).
221 Some weird problems result from using ACPI on some machines.
222 To disable ACPI you can add
223 hint.acpi.0.disable="1"
224 to /boot/loader.conf (or by putting set X=Y at the boot
227 Alternatively, you can remove it from /boot/kernel/acpi.ko
228 or use the MODULES_OVERRIDE function in your kernel config
229 file and not list acpi in that list.
232 The buildworld has been fixed. You may need to install
233 the 4.x compatibility libraries for some old binaries
234 to work. Add COMPAT4X=true to your /etc/make.conf to
235 get them installed on every installworld, or execute the
236 following to get them installed only once:
237 cd src/lib/compat/compat4x.<arch>
239 You will see ``__stdoutp undefined'' until you do this.
242 There's a bug in the world build process. The cross-tools
243 are build with the NEW headers, but the OLD libc.a. This
244 leads to all kinds of problems with the new libc. A temporary
246 CFLAGS="-O -pipe -D_OLD_STDIO"
247 before building world when upgrading from 4.x to current. This
248 can be removed afterwards.
250 A proper fix to the buildworld target is needed.
253 Peter has committed his new kthread nfs client/server code.
254 NFS may be unstable after this date.
257 KSE has hit the tree. Lots of things are now different in
258 the kernel. While a few problems were introduced in the
259 initial commit, most of the major ones have been found and
263 In OLDCARD, CardBus bridges appear to be stable. The work
264 arounds described in the 20010604 entry are now no longer
265 necessary and will be ignored. Most insert/remove problems
266 have been rectified around this date.
269 named now runs as user bind and group bind rather than as
270 root. If named_enable is set to YES in /etc/rc.conf, ensure
271 that user bind is available in /etc/passwd (using vipw(8))
272 and that group bind is available in /etc/group. Also make
273 sure that user or group bind has read (and not write)
274 permission for your name server configuration and that it
275 has read and write permission for your slave zone files and
278 If you wish to continue to run named as root (a less secure
279 alternative), add a line to /etc/rc.conf saying
284 The PAM libraries have had an API upgrade that is beyond
285 the ability of the shared library major number to handle.
286 It is manifested by PAM-using ports dumping core. The
287 solution is to rebuild those ports.
290 The kernel compile module has moved from src/sys/compile/FOO
291 to src/sys/${MACHINE}/compile/FOO.
294 The pccard modem issue from 20010613 has been corrected.
295 OLDCARD support is still a little weak in -current. slot 1 is
296 known not to work on some TI based cardbus bridges. Some
297 cardbus bridges do not properly detect insert/removal events.
298 IRQ configuration needs more safety belts.
301 Softupdates problems have been corrected.
304 Peter ripped out the linkerset support. You must, as always,
305 rerun config after you cvsup if you are using the traditional
306 kernel building methods.
309 pccard modems may not work with current after 20010604 date. Some
310 do, others result in panics. *MAKE*SURE* that you update your
311 config and /etc/rc.conf ala the 20010604 entry, or you will have
312 problems (this issue will be fixed, it just hasn't been yet).
315 SOFTUPDATES seem to be broken since the middle of May or so. Do not
316 use them in current. You can disable softupdates on all mounted
317 partitions, or remove SOFTUPDATES the kernel config file.
320 After Peter's commits to the hints code, people have been noticing
321 that certain devices are attached (or try to) twice. This is due
322 to having both static hints as well as a /boot/device.hints. To
323 work around this issue, please use only one or the other mechanism
324 until this bug is fixed.
326 Please note that a feature of config is that if you have config
327 file FOO and FOO.hints, it automatically adds FOO.hints to the
328 hints.c file, wheather you want it to or not.
331 Locale names have changed to match other systems better.
334 pccard support for pci cards has been committed. You must change
335 your /etc/pccard.conf irq lines. It must match the irq used by
336 pcic device. Interrupt storms may result if you fail to do this.
337 Interrupt storms look a lot like a hang.
339 You must also install a new pccardd, otherwise you will get an
340 interrupt storm at card reset time (just after it tells you what
343 pccardd_flags="-I" is necessary for the time being. It tells pccardd
344 not to ask the kernel if the interrupt is really free or not before
345 using it. You can either change the /etc/pccard.conf irq lines to
346 match pcic, or add "-i X" to the pccardd_flags.
349 INSTALL=install -C is being deprecated. If you want to do this,
350 use COPY=-C instead. The former method will be supported for only
351 a limited time. If you see
353 install: warning: the -d and -C options may not be specified together
355 in your makeworld, then you need to migrate towards using
359 It appears that vm is now stable enough to use again. However,
360 there may be other problems, so caution is still urged. alpha
361 definitely is in bad shape.
364 Minor repo damange has happened. This may cause problems
365 with cvsup of ports. If you get errors, please see
366 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
367 at the bottom for details on a workaround. The error message
369 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
372 Vm and/or swapping are busted on -current. Please be patient.
375 pccard has had much reorganizational work done to it over
376 the past few days. Everything should still work, but if
377 not, please contact imp@freebsd.org.
380 ata ioctl changed. Make sure to recompile both kernel and
381 userland at the same time.
384 New ncurses imported.
387 DEVFS is now opt out, not opt in. Barring major problems, this
388 will be the only way to go starting July 1.
391 OpenSSH has been updated to 2.9. Some defaults are different,
392 including RhostsRSAAuthentication, which changes from yes to no.
395 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
398 Building perl was broken at 02:25:25 PDT.
401 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
402 go back in the water.
405 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
406 this date, but before the correction date.
409 old fsck and new kernel interactions appear to have been fixed.
412 fsck and the kernel were changed to handle some optimizations
413 to directory layout. This breaks backward compatibility.
414 Update only if you understand that you must not use the old
415 fsck with the new kernel ever.
418 fsck has changed the meaning of the pass column in /etc/fstab.
419 Please see the cvs commit to fsck.8 or the fsck.8 man page for
420 details. It is unclear if changes to /etc/fstab are necessary.
423 portmap had changed name to rpcbind for maximum POLA in your
424 current world. /etc/hosts.{allow,deny} needs changes. nfs and
425 other rpc based programs that rely on portmapper will not work
426 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
429 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
430 and ATA_ENABEL_TAGS are no longer kernel options. They have
431 been replaced by tunables. See ata.4 for details.
434 The fxp driver was converted to use miibus. If you compile
435 fxp into your kernel statically, you will need to add miibus.
438 The wi device now defaults to BSS (infrastructure) mode
442 /dev/urandom should be a symbolic link to /dev/random now.
443 Users of current not using DEVFS need to run MAKEDEV std.
444 ssh might not work if you don't.
447 The ed driver has been updated. It now allows mii attachments,
448 which means that you must include the miibus in your kernel if
449 you use the ed driver.
452 The problems with libc have been corrected. It is now mostly
453 safe to go back into the water.
456 The size of FILE was changed. This breaks upgrading. If
457 you must upgrade, be prepared for pain. It also breaks almost
458 all binaries that you've compiled on -current. You are warned
459 that before upgrading would be a good time to do a level 0
460 dump of your system. No, really, I mean it this time.
462 To get to the new system, you'll need to use the following
463 workaround. Hopefully this can be sorted out so that we
464 don't have to move this to the updating section.
466 To get around the installworld problem, do:
467 # cd /usr/src/usr.bin/sed
471 If that doesn't work, then try:
472 # make -k installworld
476 DEVFS is now the default. If you use vinum, make sure that you
477 do not include devfs in your kernel as problems result.
480 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
481 Remove them from your config.
484 ****************************** WARNING ******************************
485 buildkernel has been changed slightly
486 ****************************** WARNING ******************************
487 KERNCONF replaces the variable KERNEL for buildkernel. You
488 should update your scripts and make.conf accordingly.
491 config has changed to allow DEV_FOO as a replacement for NFOO.
492 This requires a new config to build correctly.
495 The kerrnel option I386_CPU is now mutually exclusive with the
496 other cpu types. If you have an i386 system, be sure that it
497 only had this line. Remove it for all other configurations.
500 Changes to the kernel require it and burncd be in sync.
503 Everyone who has hw.sndunit set to something in
504 /etc/sysctl.conf, it is now hw.snd.unit.
507 ex and vi were broken by some changes to sys/queue.h. If you
508 have a bad vi, you will see make buildworld fail with a core
509 dump while building termcap. You can work around this problem
510 by adding -k to your make buildworld. This will cause the
511 build to complete and install a new vi. Once that's done, you
512 can rebuild again without the -k to pick up anything that
513 might have been ignored by the -k option.
515 Others have suggested that you can just rebuild libc if your
516 vi/ex is dynamically linked, but I've not received any reports
520 There have been some changes to libcrypt in -current. The
521 libscrypt/libdescrypt symlink sillyness is gone and the installed
522 libcrypt is fully functional. Be aware of this.
525 Linksys Fast Ethernet PCCARD cards supported by the ed driver
526 now require the addition of flag 0x80000 to their config line
527 in pccard.conf(5). This flag is not optional. These Linksys
528 cards will not be recognized without it.
531 Important new FreeBSD-version stuff: PAM support has been worked
532 in, partially from the "Unix" OpenSSH version. This requires
533 adding the following in pam.conf:
535 sshd auth sufficient pam_skey.so
536 sshd auth required pam_unix.so try_first_pass
537 sshd session required pam_permit.so
543 The random device needs more entropy, so you need to make sure
544 that you've run mergemaster to get a /etc/rc which will seed
545 /dev/random. If you don't and the system hangs after ldconfig,
546 then banging on the keyboard randomly until it unhangs is one
550 ****************************** WARNING ******************************
551 Sendmail has been updated.
552 ****************************** WARNING ******************************
553 o mail.local(8) is no longer installed as a set-user-id binary.
554 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
556 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
558 o Now using sendmail's version of vacation(1).
559 o The sendmail cf building tools (contrib/sendmail/cf) are installed
560 in /usr/share/sendmail/cf.
561 o sendmail.cw changed to local-host-names
563 More details can be found at
564 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
567 The ports tree's new layout is in place. Be sure to update
568 your entire ports tree, or you will have problems.
571 The perl build procedure no longer installs miniperl, nor uses
572 the installed miniperl. It is recommended that you delete
576 This weekend the ports tree will be updated to a new layout.
577 It will be in an inconsistent state until noted in the UPDATING
578 file, or with asami-san's message to the relevant mailing
579 lists. With this new layout, you'll need to update the whole
580 tree for anything to work.
583 There was a change in the passwd format. Need more information.
586 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
587 place. Please update boot loader (not the boot blocks) at the
588 same time as your kernel.
591 The new pmtimer device is necessary for laptops. Failure to
592 include the device will cause suspended laptops losing time
593 when they resume. Include
595 in your config file and
596 hint.pmtimer.0.at="isa"
597 to your /boot/device.hints file.
600 The random device has been turned into a (pseudo-)device,
601 rather than an option. The supplied kernel config files have
602 been updated. You will need to do something similar in your
603 own kernel config file.
608 If you prefer to load the loadable module, you need to do
612 The random device module has been renamed from randomdev.ko to
613 random.ko. You will need to edit your /boot/loader.conf to
614 reflect this if you load this module at boot time.
615 The line should read:
619 The SMPNG commit has happened. It should work, but if it
620 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
621 to be a variety of minor issues. Please see 20000905 to make
622 sure you don't have model loading problems which might at
623 first blush appear related to SMP.
626 nsswitch has been imported from NetBSD. Among other things,
627 this means that /etc/host.conf is no longer used. See
628 nsswitch.conf(5) instead. Note that at boot time rc.network
629 will attempt to produce a new nsswitch.conf file for you if you
630 don't have one, and you have host.conf.
633 The ucred structure changed size. This breaks the interface
634 that mountd uses. Trying to use an older mountd with a newer
635 kernel guarantees a panic. This means that you need to use
636 kernels newer than today only with matching mountd, but you
637 needed to do that anyway with the boot loader changes.
640 The boot loader has been updated. The new default kernel is
641 now /boot/kernel/kernel.ko. The new default module location
644 You *MUST* upgrade your boot loader and kernel at the same time.
645 The easiest way to do this is to do the buildworld/buildkernel/
646 installkernel/installworld dance.
648 Furthermore, you are urged to delete your old /modules directory
649 before booting the new kernel, since kldload will find stale
650 modules in that directory instead of finding them in the correct
651 path, /boot/kernel. The most common complaint that this cures
652 is that the linux module crashes your machine after the update.
654 if [ ! -d /boot/kernel.old ]; then
655 mv /modules.old /boot/kernel.old
656 chflags noschg /kernel.old
657 mv /kernel.old /boot/kernel.old/kernel.ko
658 chflags schg /boot/kernel.old/kernel.ko
662 A new issue with the sendmail upgrade has come to light.
663 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
664 incorrectly install the default aliases in /etc/mail rather than
665 move the old one from /etc. So you'll need to manually move the
666 file, create a symbolic link, remove the old /etc/aliases.db and
667 run newaliases. For safety sake, you should stop sendmail
668 while doing this and run the upgrade when locally sourced email
669 is not likely to be generated.
672 /boot/device.hints is now required for installkernel to
673 succeed. You should copy GENERIC.hints for your architecture
674 into /boot/device.hints. If and only if you compile hints
675 into your kernel, then this file may be empty. Please note,
676 if you have an empty or missing /boot/device.hints file and
677 you neglected to compile hints into your kernel, no boot
678 messages will appear after the boot loader tries to start the
682 If you do NOT have ``options RANDOMDEV'' in your kernel and
683 you DO want the random device then add randomdev_load="YES" to
687 suidperl is now always built and installed on the system, but
688 with permissions of 511. If you have applications that use
689 this program, you are now required to add ENABLE_SUIDPERL=true
690 to /etc/make.conf. If you forget to do this,
691 chmod 4511 /usr/bin/suidperl
692 will fix this until the next build.
695 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
696 visible changes that may immediately affect your configuration
698 - New default file locations from src/contrib/sendmail/cf/README
699 - newaliases limited to root and trusted users
700 - MSA port (587) turned on by default
701 - New queue file naming system so can't go from 8.11 -> 8.9
702 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
703 - FEATURE(`nullclient') is more full featured
704 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
705 - mail.local FreeBSD-only -b option changed to -B
706 - See src/contrib/sendmail/RELEASE_NOTES for more info
709 suidperl (aka sperl) is no longer build by default. You must
710 specifically define BUILD_SUIDPERL to "true" for it to be build.
711 Furthermore, we recommend that you remove /usr/bin/sperl* and
712 /usr/bin/suidperl files from your system unless you have a
716 Networking defaults have been tightened. Anybody upgrading
717 /etc/defaults/rc.conf needs to add the following lines to
718 /etc/rc.conf if they want to have the same setup
719 afterwards (unless the variables already are set, of course):
720 # Enable network daemons for user convenience.
723 sendmail_enable="YES"
726 If you have null_load="YES" in your /boot/loader.conf, you
727 will need to change that to nullfs_load="YES".
730 The "installkernel" target has changed slightly. Now even if
731 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
732 it will install the MYKERNEL file (built with the buildkernel
733 target) as /kernel rather than /MYKERNEL. Those who have
734 updated their /boot/loader.conf files to point to /MYKERNEL
735 should remove that entry or perform manual rename of /kernel
739 If you use CVSUP or CTM to get CVS trees, AND you used to get
740 the old crypto files from internat.freebsd.org AND you check
741 out files from the CVS tree with the cvs command, please read
742 http://people.freebsd.org/~imp/internat.txt
743 for details on potential problems that you might have and how
746 If you are merely a mirror, or don't answer yes to each of the
747 clauses above, you needn't worry.
750 /etc/security has been updated to print the inode number of
751 setuid programs that have changed. You will see a large spike
752 in the number of changed programs the first time when you run
753 mergemaster to get a new /etc/security.
756 /dev/random now has good entropy collection (from the keyboard
757 and sysmouse drivers). Please ensure that either `options
758 RANDOMDEV' is present in your kernel config file or that
759 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
760 not have the /dev/random driver, OpenSSL (and consequently
761 lots of crypto tools (like SSH)) will fail with strange
762 errors. (see below, 20000624).
764 FreeBSD-current is safe again to run Crypto.
767 phk made the malloc default options AJ. This may slow things
768 down and uncover other latent bugs in the code. If you need to
769 run at full speed, you can disable this by doing the following:
770 ln -s aj /etc/malloc.conf
773 libftpio's version was accidentally bumped a few days ago. This
774 has been corrected. You may need to remove /usr/lib/libftpio.so.6
775 before doing your next buildworld/installworld pair. It certainly
776 won't hurt to remove it before the update procedure. It will
777 break fetch until a new one is built, but ftp can be used in the
781 The crypto packages have changed for the cvsup. This has been done
782 in a backward compatible way, but the old packages will go away at
783 some point in the future. Look at /usr/share/examples/cvsup for
787 With the new sys/modules/sound/drivers/*, you will need to
788 set SYSDIR until you do an installworld after July 7th.
791 rc.shutdown and rc will now call the rc.d scripts with start
792 or stop. This may cause some harmless warnings from older
793 rc.d scripts that haven't been updated.
796 The libfetch based version of fetch has gone into the tree.
797 Minor problems may result on some of the less popular sites,
798 which should be reported to des@freebsd.org.
801 From approximately this date forward, one must have the crypto
802 system installed in order to build the system and kernel.
803 While not technically strictly true, one should treat it as
804 required and grab the crypto bits. If you are grabbing CVS
805 trees, src-all and cvs-crypto should be treated as if they
806 were required. You should check with the latest collections
807 to make sure that these haven't changed.
810 Mark Murray just committed the first parts of a cleanup of
811 /dev/zero, et al. This is also cleaning up /dev/random.
812 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
813 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
814 until Mark can merge in the fixes to this work in progress.
815 openssh and openssl should not be used to generate keys from this
816 date to the completion of the work.
818 If you must operate at this reduced level of security, add '
819 options RANDOMDEV' to your kernel or modload the randomdev
820 module. You may also need to copy a new MAKEDEV to /dev and
821 recreate the random and urandom devices.
824 The license on the softupdates is now a standard 2 clause
825 BSD license. You may need to remove your symbolic links
826 that used to be required when updating.
829 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
830 the config file update procedure.
831 http://people.freebsd.org/~imp/config-upd.html
832 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
833 isn't buildable. However, you can generate a LINT file.
836 Binutils 2.10 have hit the tree, or will shortly. As soon
837 as they do, the problem noted in 20000522 will be resolved and
838 that workaround will no longer be required.
841 phk removed the compatibility creation of wd devices in the
842 ad driver. If you haven't done so already, you must update
843 your fstab, etc to use the ad devices instead of the wd
846 In addition, you'll need to update your boot blocks to a
847 more modern version, if you haven't already done so. Modern
848 here means 4.0 release or newer (although older releases
852 Peter took an axe to config(8). Be sure that you read his mail
853 on the topic before even thinking about updating. You will
854 need to create a /boot/device.hints or add a hints directive
855 to your config file to compile them in statically. The format
856 of the config file has changed as well. Please see GENERIC or
857 NEWCARD for examples of the new format.
859 Indirectly, this also breaks USERCONFIG. Unless a newer entry
860 says that it has been fixed, assume that must use the hints mechanism
861 in the loader if you need to use a machine with very old ISA cards
865 A new set of binutils went into the tree today. Anybody
866 building a kernel after this point is advised that they need
867 to rebuild their binutils (or better yet do a
868 buildworld/installworld) before building a new kernel.
870 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
871 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
872 is recommended that you don't set this option until the problem
876 The ethernet drivers were all updated to clean up the BPF handling.
879 The problems with boot blocks on the alphas have been corrected.
880 This will require some care in updating alphas. A new libstand
881 is requires for the boot blocks to build properly.
884 Recompile all kld modules. Proper version dependency info
888 Modules have been disconnected from the buildworld tree and
889 connected to the kernel building instead.
892 You may need to build gperf
893 cd /usr/src/gnu/usr.bin/gperf && make depend all install
894 when upgrading from 4.0 -> current. The build system now uses
895 an option only in -current.
898 The method that we brand ELF binaries has changed to be more
899 acceptable to the binutils maintainers. You will need to
900 rebrand your ELF binaries that aren't native. One problem
901 binary is the Linux ldconfig. After your make world, but
902 before you reboot, you'll need to issue:
903 brandelf -t Linux /compat/linux/sbin/ldconfig
904 if you have Linux compatibility enabled on your machine.
907 If you have really bad/marginal IDE drives, you may find they
908 don't work well. Use pio mode instead. The easiest way to
909 cope if you have a problem combination is to add:
910 /sbin/sysctl hw.ata.ata_dma=0
911 to the start of /etc/rc.conf.
914 The ISA and PCI compatibility shims have been connected to the
915 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
916 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
917 include the appropriate option in your kernel config. Drivers
918 using the shims should be updated or they won't ship with
919 5.0-RELEASE, targeted for 2001.
922 We've entered the traditional post release dumping party.
923 Large kernel changes are being committed and are in the
924 works. It is important to keep the systems' klds and kernel
925 in sync as kernel interfaces and structures are changing.
926 Before reporting kernel panics, make sure that all modules
927 that you are loading are up to date.
930 If you are upgrading from an older version of FreeBSD, you
931 need to update your boot blocks as well. 'disklabel -B ad0'
932 will do the trick. This isn't critical until you remove your
933 wd device entries in /dev, at which point your system will not
937 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
938 to upgrade to 4.0 from 3.x.
944 Avoid using make -j when upgrading. From time to time in the
945 past there have been problems using -j with buildworld and/or
946 installworld. This is especially true when upgrading between
947 "distant" versions (eg one that cross a major release boundary
948 or several minor releases, or when several months have passed
949 on the -current branch).
951 Sometimes, obscure build problems are the result of environment
952 poisoning. This can happen because the make utility reads its
953 environment when searching for values for global variables.
954 To run your build attempts in an "environmental clean room",
955 prefix all make commands with 'env -i '. See the env(1) manual
956 page for more details.
960 If you are updating from a prior version of FreeBSD (even one just
961 a few days old), you should follow this procedure. With a
962 /usr/obj tree with a fresh buildworld,
963 make buildkernel KERNCONF=YOUR_KERNEL_HERE
964 make installkernel KERNCONF=YOUR_KERNEL_HERE
966 To just build a kernel when you know that it won't mess you up
967 --------------------------------------------------------------
968 cd src/sys/{i386,alpha}/conf
969 config KERNEL_NAME_HERE
970 cd ../../compile/KERNEL_NAME_HERE
975 If this fails, go to the "To build a kernel" section.
977 To rebuild everything and install it on the current system.
978 -----------------------------------------------------------
980 Build a new kernel, see above.
982 To upgrade from 4.x-stable to current
983 -------------------------------------
985 make buildkernel KERNCONF=YOUR_KERNEL_HERE
986 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
987 make installkernel KERNCONF=YOUR_KERNEL_HERE
988 reboot in single user [3]
995 Make sure that you've read the UPDATING file to understand the
996 tweaks to various things you need. At this point in the life
997 cycle of current, things change often and you are on your own
998 to cope. The defaults can also change, so please read ALL of
999 the UPDATING entries.
1001 Also, if you are tracking -current, you must be subscribed to
1002 freebsd-current@freebsd.org. Make sure that before you update
1003 your sources that you have read and understood all the recent
1004 messages there. If in doubt, please track -stable which has
1005 much fewer pitfalls.
1007 [1] If you have third party modules, such as vmware, you
1008 should disable them at this point so they don't crash your
1011 [2] If you have legacy ISA devices, you may need to create
1012 your own device.hints to reflect your unique hardware
1015 [3] From the bootblocks, boot -s, and then do
1020 adjkerntz -i # if CMOS is wall time
1021 Also, when doing a major release upgrade, it is required that
1022 you boot into single user mode to do the installworld.
1024 [4] Note: This step is non-optional. Failure to do this step
1025 can result in a significant reduction in the functionality of the
1026 system. Attempting to do it by hand is not recommended and those
1027 that pursue this avenue should read this file carefully, as well
1028 as the archives of freebsd-current and freebsd-hackers mailing lists
1029 for potential gotchas.
1031 [5] Usually this step is a noop. However, from time to time
1032 you may need to do this if you get unknown user in the following
1033 step. It never hurts to do it all the time. You may need to
1034 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1035 install) after the buildworld before this step if you last updated
1036 from current before 20020224 or from -stable before 20020408.
1040 This file contains a list, in reverse chronological order, of major
1041 breakages in tracking -current. Not all things will be listed here,
1042 and it only starts on March 15, 2000. Updating files can found in
1043 previous releases if your system is older than this.
1045 Copyright information:
1047 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1049 Redistribution, publication, translation and use, with or without
1050 modification, in full or in part, in any form or format of this
1051 document are permitted without further permission from the author.
1053 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1054 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1055 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1056 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1057 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1058 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1059 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1060 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1061 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1062 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1063 POSSIBILITY OF SUCH DAMAGE.
1065 If you find this document useful, and you want to, you may buy the
1068 Contact Warner Losh if you have any questions about your use of