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.
21 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
22 used an incompatible form of ABI for returning structures and unions
23 which FreeBSD's GCC maintainers were not aware of relative to previous
24 versions of FreeBSD. We have gone back to the ABI for now, and any
25 code compiled which is required to interoperate with other code (not
26 built at the same time) returning structs or unions should be
30 A name change in /etc/netconfig has been reverted to stay
31 compatible with with suns TIRPC and also with NetBSD. You need
32 to run mergemaster after make world. A new libc does still work
33 with an outdated /etc/netconfig for some time, but you'll get
34 a warning. This warning will be removed in 20030301.
37 The recent binutils upgrade marks a kernel flag day on
38 sparc64: modules built with the old binutils will not work
39 with new kernels and vice versa. Mismatches will result in
40 panics. Make sure your kernel and modules are in sync.
43 The value of IPPROTO_DIVERT has changed. Make sure to keep
44 your kernel, netstat, natd and any third-party DIVERT
48 Old, compatibility slices have been removed in GEOM kernels. This
49 means that you will have to update your /etc/fstab to not use
50 disk devices of the form /dev/ad0a. Instead, you now must
51 specify /dev/ad0s1a, or whatever slice your FreeBSD partition
52 really is on. The old device names have gone away, so if you
53 use them anywhere else, you must also adjust those uses.
56 Alphas with kernels from between 20020830 and 20021023 and/or
57 rtld (ld-elf.so.1) older than 20021023 may experience problems
58 with groff while doing a buildworld (kernel: "out of memory",
59 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
60 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
62 So, to successfully upgrade your Alpha, you must either
63 upgrade your kernel and rtld first (which might be a bit
64 tricky), or avoid running the bootstrapped groff during the
65 "transitional" buildworld. To avoid running groff during the
66 transitional upgrade run make buildworld with -DNOMAN,
67 -DNO_SHAREDOCS, and -DNO_LPR.
70 gcc has been upgraded to 3.2. It is not all binary compatible
71 with earlier versions of gcc for c++ programs. All c++
72 programs and libraries need to be recompiled.
74 Also, if you encounter g++ issues, rm /usr/include/g++/* before
75 doing an installworld to make sure that stale files are removed.
78 Our /etc/termcap now has all the entries from the XFree86 xterm
79 almost unchanged. This means xterm now supports color by default.
80 If you used TERM=xterm-color in the past you now should use
81 TERM=xterm. (xterm-color will lead to benign warnings).
84 A "bug" in gcc(1) that was hiding warning in system headers was
85 fixed. It's probably time to add -DNO_WERROR to your make line
89 COPY is being deprecated. The 20010530 change was reverted, as
90 it causes far more pain than was expected, and to always compare
91 before installing, please use INSTALL="install -C" again. The
92 -C option is now silently ignored when used with the -d option.
95 Problems with libc_r clients like KDE and GNOME have been resolved.
96 There are still some minor problems with some signals but the
97 system is stable enough for general use again. SMP is less so than UP
98 but each can successfully complete multiple buildworlds.
99 Libkvm needs to be recompiled due to KSE.
102 Now would be a bad time to upgrade. Something in or near the
103 KSE commit totally broke programs using libc_r like KDE and
107 The k5su utility installed as part of Kerberos 5 is no longer
108 installed with the set-user-ID bit set by default. Add
109 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
110 with the set-user-ID bit set.
113 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
114 Unfortunately our native GDB (at version 4.18) does not understand
115 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
116 generated debugging information for our native GDB.
119 Due to the way CVS works, it may not properly update src/contrib/gcc
120 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
121 and then do a cvs update.
124 When exec'ing set[ug]id executables, the kernel now ensures that the
125 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
128 New sendmail startup scripts have been installed to make it
129 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
130 variable sendmail_enable to "NO" no longer prevents any sendmail
131 daemons from starting. Instead, either set sendmail_enable to
132 "NONE" or change mta_start_script to a script for starting
133 an alternative MTA. Setting mta_start_script to "" will
134 also prevent any MTA from being started at boot.
137 UCONSOLE is no longer a valid kernel option.
140 FreeBSD 5.0 DP-1 was basically branched today.
143 Warnings are now errors in the kernel. Unless you are a developer,
144 you should add -DNO_WERROR to your make line.
147 sendmail 8.12.2 has been imported. The sendmail binary is no
148 longer a set-user-ID root binary and the infrastructure to support
149 command line mail submission has changed. Be sure to run
150 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
151 and /etc/mail) and read /etc/mail/README for more details.
153 Due to the import of sendmail 8.12.2, a new user and group are
154 required in order for sendmail to run as a set-group-ID
155 binary. A 'make installworld' will use the new user and group
156 to set the owner and group of /var/spool/clientmqueue and will
157 fail if the new user and group do not exist. The 'smmsp' user
158 and group must be merged from src/etc/group and
159 src/etc/master.passwd before using 'make installworld'.
160 'mergemaster -p' will do this. You may need to install
161 mergemaster before this will work if you are updating from a
162 very old version of current. The updating recipe has changed
166 The preferred configuration method for PAM is now /etc/pam.d/
167 rather than /etc/pam.conf. If you have an unmodified
168 pam.conf, just delete it after your next mergemaster run. If
169 you have local modifications, you can use
170 /usr/src/etc/pam.d/convert.pl to incorporate them into your
173 Please see the following url for more details:
174 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
176 If anyone here is already using the new rc.conf(5) variable
177 networkfs_types, please note that it has changed
178 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
181 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
182 started out its life in the ISDN4BSD project as an offspring
183 from sys/net/if_spppsubr.c, which eventually got a life of its
184 own. All the accumulated features and bugfixes of the i4b
185 version have now been merged back into the base system's
186 version now. The only user-visible change resulting from this
187 is that i4b's sppp(4) interfaces are to be managed with
188 spppcontrol(8) again, since ispppcontrol(8) has been retired
189 as well. (There has never been rc file support for
190 ispppcontrol in -current, but only in -stable. That will be
191 reverted by the time the changes are MFCed.)
194 The fdc(4) driver has been updated and now automatically
195 recognizes media in `standard' formats (like 1440 KB and
196 720 KB for a 3.5" high-density drive) when accessing the
197 default device node (e. g. /dev/fd0). The old variety of
198 floppy device nodes /dev/fd*.* is no longer present by
199 default, devices can be created (in DEVFS) on demand. They
200 will need to be customized then for `odd' densities using
204 The bugs in procfs' debugging support code have been fixed,
205 and truss(1) now works again.
208 Daily security checks have been split out to use the periodic(8)
209 scripts. Some change in configuration may be necessary. Please
211 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
215 sos added VCD/SVCD support to ata driver and that needs the
216 kernel and burncd to be in sync.
219 The procfs pseudo-filesystem has now been converted to use the
220 pseudofs framework. If you have 'options PROCFS' in your
221 kernel config, you'll need to add 'options PSEUDOFS' if it's
224 This change temporarily breaks truss(1); use ktrace(1) instead
225 until the issue has been resolved.
228 A security hole in OpenSSH involving `UseLogin yes' has been
232 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
233 after this date. You need to do this only once.
236 Most of the awk issues have been resolved. Some rough
237 edges may be left, but for the most part things should be
238 back to "normal." For CURRENT's usual definition of "normal."
241 Awk has been upgraded to the one true awk from bell labs. Expect
242 choppy waves in the upgrade process.
245 The asr driver problem has been resolved.
248 Due to changes in other parts of the system, the asr driver
249 now causes the system to panic on boot. Do not use it pending
250 correction. Comment it out of any kernel config file that you
251 try to use from this date forward.
254 When crossbuilding, use TARGET=xxx where you used to use
255 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
256 unless you are changing both of them. To cross build pc98 on
257 an alpha, for example, you need to set TARGET=pc98 and
261 The kernel interface that burncd depends on has changed.
262 You must recompile both the kernel and userland applications
266 When crossbuilding, please set TARGET_ARCH rather than
267 MACHINE_ARCH to indicate the target. In the future, one will
268 set TARGET_MACHINE where you set MACHINE now. At the moment,
269 setting MACHINE alone for same MACHINE_ARCH machines works
270 (eg, you can build pc98 on an i386 machine and vice versa).
273 Some weird problems result from using ACPI on some machines.
274 To disable ACPI you can add
275 hint.acpi.0.disable="1"
276 to /boot/loader.conf (or by putting set X=Y at the boot
279 Alternatively, you can remove it from /boot/kernel/acpi.ko
280 or use the MODULES_OVERRIDE function in your kernel config
281 file and not list acpi in that list.
284 The buildworld has been fixed. You may need to install
285 the 4.x compatibility libraries for some old binaries
286 to work. Add COMPAT4X=true to your /etc/make.conf to
287 get them installed on every installworld, or execute the
288 following to get them installed only once:
289 cd src/lib/compat/compat4x.<arch>
291 You will see ``__stdoutp undefined'' until you do this.
294 There's a bug in the world build process. The cross-tools
295 are build with the NEW headers, but the OLD libc.a. This
296 leads to all kinds of problems with the new libc. A temporary
298 CFLAGS="-O -pipe -D_OLD_STDIO"
299 before building world when upgrading from 4.x to current. This
300 can be removed afterwards.
302 A proper fix to the buildworld target is needed.
305 Peter has committed his new kthread nfs client/server code.
306 NFS may be unstable after this date.
309 KSE has hit the tree. Lots of things are now different in
310 the kernel. While a few problems were introduced in the
311 initial commit, most of the major ones have been found and
315 In OLDCARD, CardBus bridges appear to be stable. The work
316 arounds described in the 20010604 entry are now no longer
317 necessary and will be ignored. Most insert/remove problems
318 have been rectified around this date.
321 named now runs as user bind and group bind rather than as
322 root. If named_enable is set to YES in /etc/rc.conf, ensure
323 that user bind is available in /etc/passwd (using vipw(8))
324 and that group bind is available in /etc/group. Also make
325 sure that user or group bind has read (and not write)
326 permission for your name server configuration and that it
327 has read and write permission for your slave zone files and
330 If you wish to continue to run named as root (a less secure
331 alternative), add a line to /etc/rc.conf saying
336 The PAM libraries have had an API upgrade that is beyond
337 the ability of the shared library major number to handle.
338 It is manifested by PAM-using ports dumping core. The
339 solution is to rebuild those ports.
342 The kernel compile module has moved from src/sys/compile/FOO
343 to src/sys/${MACHINE}/compile/FOO.
346 The pccard modem issue from 20010613 has been corrected.
347 OLDCARD support is still a little weak in -current. slot 1 is
348 known not to work on some TI based cardbus bridges. Some
349 cardbus bridges do not properly detect insert/removal events.
350 IRQ configuration needs more safety belts.
353 Softupdates problems have been corrected.
356 Peter ripped out the linkerset support. You must, as always,
357 rerun config after you cvsup if you are using the traditional
358 kernel building methods.
361 pccard modems may not work with current after 20010604 date. Some
362 do, others result in panics. *MAKE*SURE* that you update your
363 config and /etc/rc.conf ala the 20010604 entry, or you will have
364 problems (this issue will be fixed, it just hasn't been yet).
367 SOFTUPDATES seem to be broken since the middle of May or so. Do not
368 use them in current. You can disable softupdates on all mounted
369 partitions, or remove SOFTUPDATES the kernel config file.
372 After Peter's commits to the hints code, people have been noticing
373 that certain devices are attached (or try to) twice. This is due
374 to having both static hints as well as a /boot/device.hints. To
375 work around this issue, please use only one or the other mechanism
376 until this bug is fixed.
378 Please note that a feature of config is that if you have config
379 file FOO and FOO.hints, it automatically adds FOO.hints to the
380 hints.c file, wheather you want it to or not.
383 Locale names have changed to match other systems better.
386 pccard support for pci cards has been committed. You must change
387 your /etc/pccard.conf irq lines. It must match the irq used by
388 pcic device. Interrupt storms may result if you fail to do this.
389 Interrupt storms look a lot like a hang.
391 You must also install a new pccardd, otherwise you will get an
392 interrupt storm at card reset time (just after it tells you what
395 pccardd_flags="-I" is necessary for the time being. It tells pccardd
396 not to ask the kernel if the interrupt is really free or not before
397 using it. You can either change the /etc/pccard.conf irq lines to
398 match pcic, or add "-i X" to the pccardd_flags.
401 INSTALL=install -C is being deprecated. If you want to do this,
402 use COPY=-C instead. The former method will be supported for only
403 a limited time. If you see
405 install: warning: the -d and -C options may not be specified together
407 in your makeworld, then you need to migrate towards using
411 It appears that vm is now stable enough to use again. However,
412 there may be other problems, so caution is still urged. alpha
413 definitely is in bad shape.
416 Minor repo damange has happened. This may cause problems
417 with cvsup of ports. If you get errors, please see
418 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
419 at the bottom for details on a workaround. The error message
421 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
424 Vm and/or swapping are busted on -current. Please be patient.
427 pccard has had much reorganizational work done to it over
428 the past few days. Everything should still work, but if
429 not, please contact imp@freebsd.org.
432 ata ioctl changed. Make sure to recompile both kernel and
433 userland at the same time.
436 New ncurses imported.
439 DEVFS is now opt out, not opt in. Barring major problems, this
440 will be the only way to go starting July 1.
443 OpenSSH has been updated to 2.9. Some defaults are different,
444 including RhostsRSAAuthentication, which changes from yes to no.
447 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
450 Building perl was broken at 02:25:25 PDT.
453 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
454 go back in the water.
457 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
458 this date, but before the correction date.
461 old fsck and new kernel interactions appear to have been fixed.
464 fsck and the kernel were changed to handle some optimizations
465 to directory layout. This breaks backward compatibility.
466 Update only if you understand that you must not use the old
467 fsck with the new kernel ever.
470 fsck has changed the meaning of the pass column in /etc/fstab.
471 Please see the cvs commit to fsck.8 or the fsck.8 man page for
472 details. It is unclear if changes to /etc/fstab are necessary.
475 portmap had changed name to rpcbind for maximum POLA in your
476 current world. /etc/hosts.{allow,deny} needs changes. nfs and
477 other rpc based programs that rely on portmapper will not work
478 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
481 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
482 and ATA_ENABEL_TAGS are no longer kernel options. They have
483 been replaced by tunables. See ata.4 for details.
486 The fxp driver was converted to use miibus. If you compile
487 fxp into your kernel statically, you will need to add miibus.
490 The wi device now defaults to BSS (infrastructure) mode
494 /dev/urandom should be a symbolic link to /dev/random now.
495 Users of current not using DEVFS need to run MAKEDEV std.
496 ssh might not work if you don't.
499 The ed driver has been updated. It now allows mii attachments,
500 which means that you must include the miibus in your kernel if
501 you use the ed driver.
504 The problems with libc have been corrected. It is now mostly
505 safe to go back into the water.
508 The size of FILE was changed. This breaks upgrading. If
509 you must upgrade, be prepared for pain. It also breaks almost
510 all binaries that you've compiled on -current. You are warned
511 that before upgrading would be a good time to do a level 0
512 dump of your system. No, really, I mean it this time.
514 To get to the new system, you'll need to use the following
515 workaround. Hopefully this can be sorted out so that we
516 don't have to move this to the updating section.
518 To get around the installworld problem, do:
519 # cd /usr/src/usr.bin/sed
523 If that doesn't work, then try:
524 # make -k installworld
528 DEVFS is now the default. If you use vinum, make sure that you
529 do not include devfs in your kernel as problems result.
532 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
533 Remove them from your config.
536 ****************************** WARNING ******************************
537 buildkernel has been changed slightly
538 ****************************** WARNING ******************************
539 KERNCONF replaces the variable KERNEL for buildkernel. You
540 should update your scripts and make.conf accordingly.
543 config has changed to allow DEV_FOO as a replacement for NFOO.
544 This requires a new config to build correctly.
547 The kerrnel option I386_CPU is now mutually exclusive with the
548 other cpu types. If you have an i386 system, be sure that it
549 only had this line. Remove it for all other configurations.
552 Changes to the kernel require it and burncd be in sync.
555 Everyone who has hw.sndunit set to something in
556 /etc/sysctl.conf, it is now hw.snd.unit.
559 ex and vi were broken by some changes to sys/queue.h. If you
560 have a bad vi, you will see make buildworld fail with a core
561 dump while building termcap. You can work around this problem
562 by adding -k to your make buildworld. This will cause the
563 build to complete and install a new vi. Once that's done, you
564 can rebuild again without the -k to pick up anything that
565 might have been ignored by the -k option.
567 Others have suggested that you can just rebuild libc if your
568 vi/ex is dynamically linked, but I've not received any reports
572 There have been some changes to libcrypt in -current. The
573 libscrypt/libdescrypt symlink sillyness is gone and the installed
574 libcrypt is fully functional. Be aware of this.
577 Linksys Fast Ethernet PCCARD cards supported by the ed driver
578 now require the addition of flag 0x80000 to their config line
579 in pccard.conf(5). This flag is not optional. These Linksys
580 cards will not be recognized without it.
583 Important new FreeBSD-version stuff: PAM support has been worked
584 in, partially from the "Unix" OpenSSH version. This requires
585 adding the following in pam.conf:
587 sshd auth sufficient pam_skey.so
588 sshd auth required pam_unix.so try_first_pass
589 sshd session required pam_permit.so
595 The random device needs more entropy, so you need to make sure
596 that you've run mergemaster to get a /etc/rc which will seed
597 /dev/random. If you don't and the system hangs after ldconfig,
598 then banging on the keyboard randomly until it unhangs is one
602 ****************************** WARNING ******************************
603 Sendmail has been updated.
604 ****************************** WARNING ******************************
605 o mail.local(8) is no longer installed as a set-user-id binary.
606 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
608 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
610 o Now using sendmail's version of vacation(1).
611 o The sendmail cf building tools (contrib/sendmail/cf) are installed
612 in /usr/share/sendmail/cf.
613 o sendmail.cw changed to local-host-names
615 More details can be found at
616 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
619 The ports tree's new layout is in place. Be sure to update
620 your entire ports tree, or you will have problems.
623 The perl build procedure no longer installs miniperl, nor uses
624 the installed miniperl. It is recommended that you delete
628 This weekend the ports tree will be updated to a new layout.
629 It will be in an inconsistent state until noted in the UPDATING
630 file, or with asami-san's message to the relevant mailing
631 lists. With this new layout, you'll need to update the whole
632 tree for anything to work.
635 There was a change in the passwd format. Need more information.
638 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
639 place. Please update boot loader (not the boot blocks) at the
640 same time as your kernel.
643 The new pmtimer device is necessary for laptops. Failure to
644 include the device will cause suspended laptops losing time
645 when they resume. Include
647 in your config file and
648 hint.pmtimer.0.at="isa"
649 to your /boot/device.hints file.
652 The random device has been turned into a (pseudo-)device,
653 rather than an option. The supplied kernel config files have
654 been updated. You will need to do something similar in your
655 own kernel config file.
660 If you prefer to load the loadable module, you need to do
664 The random device module has been renamed from randomdev.ko to
665 random.ko. You will need to edit your /boot/loader.conf to
666 reflect this if you load this module at boot time.
667 The line should read:
671 The SMPNG commit has happened. It should work, but if it
672 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
673 to be a variety of minor issues. Please see 20000905 to make
674 sure you don't have model loading problems which might at
675 first blush appear related to SMP.
678 nsswitch has been imported from NetBSD. Among other things,
679 this means that /etc/host.conf is no longer used. See
680 nsswitch.conf(5) instead. Note that at boot time rc.network
681 will attempt to produce a new nsswitch.conf file for you if you
682 don't have one, and you have host.conf.
685 The ucred structure changed size. This breaks the interface
686 that mountd uses. Trying to use an older mountd with a newer
687 kernel guarantees a panic. This means that you need to use
688 kernels newer than today only with matching mountd, but you
689 needed to do that anyway with the boot loader changes.
692 The boot loader has been updated. The new default kernel is
693 now /boot/kernel/kernel.ko. The new default module location
696 You *MUST* upgrade your boot loader and kernel at the same time.
697 The easiest way to do this is to do the buildworld/buildkernel/
698 installkernel/installworld dance.
700 Furthermore, you are urged to delete your old /modules directory
701 before booting the new kernel, since kldload will find stale
702 modules in that directory instead of finding them in the correct
703 path, /boot/kernel. The most common complaint that this cures
704 is that the linux module crashes your machine after the update.
706 if [ ! -d /boot/kernel.old ]; then
707 mv /modules.old /boot/kernel.old
708 chflags noschg /kernel.old
709 mv /kernel.old /boot/kernel.old/kernel.ko
710 chflags schg /boot/kernel.old/kernel.ko
714 A new issue with the sendmail upgrade has come to light.
715 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
716 incorrectly install the default aliases in /etc/mail rather than
717 move the old one from /etc. So you'll need to manually move the
718 file, create a symbolic link, remove the old /etc/aliases.db and
719 run newaliases. For safety sake, you should stop sendmail
720 while doing this and run the upgrade when locally sourced email
721 is not likely to be generated.
724 /boot/device.hints is now required for installkernel to
725 succeed. You should copy GENERIC.hints for your architecture
726 into /boot/device.hints. If and only if you compile hints
727 into your kernel, then this file may be empty. Please note,
728 if you have an empty or missing /boot/device.hints file and
729 you neglected to compile hints into your kernel, no boot
730 messages will appear after the boot loader tries to start the
734 If you do NOT have ``options RANDOMDEV'' in your kernel and
735 you DO want the random device then add randomdev_load="YES" to
739 suidperl is now always built and installed on the system, but
740 with permissions of 511. If you have applications that use
741 this program, you are now required to add ENABLE_SUIDPERL=true
742 to /etc/make.conf. If you forget to do this,
743 chmod 4511 /usr/bin/suidperl
744 will fix this until the next build.
747 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
748 visible changes that may immediately affect your configuration
750 - New default file locations from src/contrib/sendmail/cf/README
751 - newaliases limited to root and trusted users
752 - MSA port (587) turned on by default
753 - New queue file naming system so can't go from 8.11 -> 8.9
754 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
755 - FEATURE(`nullclient') is more full featured
756 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
757 - mail.local FreeBSD-only -b option changed to -B
758 - See src/contrib/sendmail/RELEASE_NOTES for more info
761 suidperl (aka sperl) is no longer build by default. You must
762 specifically define BUILD_SUIDPERL to "true" for it to be build.
763 Furthermore, we recommend that you remove /usr/bin/sperl* and
764 /usr/bin/suidperl files from your system unless you have a
768 Networking defaults have been tightened. Anybody upgrading
769 /etc/defaults/rc.conf needs to add the following lines to
770 /etc/rc.conf if they want to have the same setup
771 afterwards (unless the variables already are set, of course):
772 # Enable network daemons for user convenience.
775 sendmail_enable="YES"
778 If you have null_load="YES" in your /boot/loader.conf, you
779 will need to change that to nullfs_load="YES".
782 The "installkernel" target has changed slightly. Now even if
783 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
784 it will install the MYKERNEL file (built with the buildkernel
785 target) as /kernel rather than /MYKERNEL. Those who have
786 updated their /boot/loader.conf files to point to /MYKERNEL
787 should remove that entry or perform manual rename of /kernel
791 If you use CVSUP or CTM to get CVS trees, AND you used to get
792 the old crypto files from internat.freebsd.org AND you check
793 out files from the CVS tree with the cvs command, please read
794 http://people.freebsd.org/~imp/internat.txt
795 for details on potential problems that you might have and how
798 If you are merely a mirror, or don't answer yes to each of the
799 clauses above, you needn't worry.
802 /etc/security has been updated to print the inode number of
803 setuid programs that have changed. You will see a large spike
804 in the number of changed programs the first time when you run
805 mergemaster to get a new /etc/security.
808 /dev/random now has good entropy collection (from the keyboard
809 and sysmouse drivers). Please ensure that either `options
810 RANDOMDEV' is present in your kernel config file or that
811 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
812 not have the /dev/random driver, OpenSSL (and consequently
813 lots of crypto tools (like SSH)) will fail with strange
814 errors. (see below, 20000624).
816 FreeBSD-current is safe again to run Crypto.
819 phk made the malloc default options AJ. This may slow things
820 down and uncover other latent bugs in the code. If you need to
821 run at full speed, you can disable this by doing the following:
822 ln -s aj /etc/malloc.conf
825 libftpio's version was accidentally bumped a few days ago. This
826 has been corrected. You may need to remove /usr/lib/libftpio.so.6
827 before doing your next buildworld/installworld pair. It certainly
828 won't hurt to remove it before the update procedure. It will
829 break fetch until a new one is built, but ftp can be used in the
833 The crypto packages have changed for the cvsup. This has been done
834 in a backward compatible way, but the old packages will go away at
835 some point in the future. Look at /usr/share/examples/cvsup for
839 With the new sys/modules/sound/drivers/*, you will need to
840 set SYSDIR until you do an installworld after July 7th.
843 rc.shutdown and rc will now call the rc.d scripts with start
844 or stop. This may cause some harmless warnings from older
845 rc.d scripts that haven't been updated.
848 The libfetch based version of fetch has gone into the tree.
849 Minor problems may result on some of the less popular sites,
850 which should be reported to des@freebsd.org.
853 From approximately this date forward, one must have the crypto
854 system installed in order to build the system and kernel.
855 While not technically strictly true, one should treat it as
856 required and grab the crypto bits. If you are grabbing CVS
857 trees, src-all and cvs-crypto should be treated as if they
858 were required. You should check with the latest collections
859 to make sure that these haven't changed.
862 Mark Murray just committed the first parts of a cleanup of
863 /dev/zero, et al. This is also cleaning up /dev/random.
864 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
865 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
866 until Mark can merge in the fixes to this work in progress.
867 openssh and openssl should not be used to generate keys from this
868 date to the completion of the work.
870 If you must operate at this reduced level of security, add '
871 options RANDOMDEV' to your kernel or modload the randomdev
872 module. You may also need to copy a new MAKEDEV to /dev and
873 recreate the random and urandom devices.
876 The license on the softupdates is now a standard 2 clause
877 BSD license. You may need to remove your symbolic links
878 that used to be required when updating.
881 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
882 the config file update procedure.
883 http://people.freebsd.org/~imp/config-upd.html
884 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
885 isn't buildable. However, you can generate a LINT file.
888 Binutils 2.10 have hit the tree, or will shortly. As soon
889 as they do, the problem noted in 20000522 will be resolved and
890 that workaround will no longer be required.
893 phk removed the compatibility creation of wd devices in the
894 ad driver. If you haven't done so already, you must update
895 your fstab, etc to use the ad devices instead of the wd
898 In addition, you'll need to update your boot blocks to a
899 more modern version, if you haven't already done so. Modern
900 here means 4.0 release or newer (although older releases
904 Peter took an axe to config(8). Be sure that you read his mail
905 on the topic before even thinking about updating. You will
906 need to create a /boot/device.hints or add a hints directive
907 to your config file to compile them in statically. The format
908 of the config file has changed as well. Please see GENERIC or
909 NEWCARD for examples of the new format.
911 Indirectly, this also breaks USERCONFIG. Unless a newer entry
912 says that it has been fixed, assume that must use the hints mechanism
913 in the loader if you need to use a machine with very old ISA cards
917 A new set of binutils went into the tree today. Anybody
918 building a kernel after this point is advised that they need
919 to rebuild their binutils (or better yet do a
920 buildworld/installworld) before building a new kernel.
922 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
923 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
924 is recommended that you don't set this option until the problem
928 The ethernet drivers were all updated to clean up the BPF handling.
931 The problems with boot blocks on the alphas have been corrected.
932 This will require some care in updating alphas. A new libstand
933 is requires for the boot blocks to build properly.
936 Recompile all kld modules. Proper version dependency info
940 Modules have been disconnected from the buildworld tree and
941 connected to the kernel building instead.
944 You may need to build gperf
945 cd /usr/src/gnu/usr.bin/gperf && make depend all install
946 when upgrading from 4.0 -> current. The build system now uses
947 an option only in -current.
950 The method that we brand ELF binaries has changed to be more
951 acceptable to the binutils maintainers. You will need to
952 rebrand your ELF binaries that aren't native. One problem
953 binary is the Linux ldconfig. After your make world, but
954 before you reboot, you'll need to issue:
955 brandelf -t Linux /compat/linux/sbin/ldconfig
956 if you have Linux compatibility enabled on your machine.
959 If you have really bad/marginal IDE drives, you may find they
960 don't work well. Use pio mode instead. The easiest way to
961 cope if you have a problem combination is to add:
962 /sbin/sysctl hw.ata.ata_dma=0
963 to the start of /etc/rc.conf.
966 The ISA and PCI compatibility shims have been connected to the
967 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
968 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
969 include the appropriate option in your kernel config. Drivers
970 using the shims should be updated or they won't ship with
971 5.0-RELEASE, targeted for 2001.
974 We've entered the traditional post release dumping party.
975 Large kernel changes are being committed and are in the
976 works. It is important to keep the systems' klds and kernel
977 in sync as kernel interfaces and structures are changing.
978 Before reporting kernel panics, make sure that all modules
979 that you are loading are up to date.
982 If you are upgrading from an older version of FreeBSD, you
983 need to update your boot blocks as well. 'disklabel -B ad0'
984 will do the trick. This isn't critical until you remove your
985 wd device entries in /dev, at which point your system will not
989 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
990 to upgrade to 4.0 from 3.x.
996 Avoid using make -j when upgrading. From time to time in the
997 past there have been problems using -j with buildworld and/or
998 installworld. This is especially true when upgrading between
999 "distant" versions (eg one that cross a major release boundary
1000 or several minor releases, or when several months have passed
1001 on the -current branch).
1003 Sometimes, obscure build problems are the result of environment
1004 poisoning. This can happen because the make utility reads its
1005 environment when searching for values for global variables.
1006 To run your build attempts in an "environmental clean room",
1007 prefix all make commands with 'env -i '. See the env(1) manual
1008 page for more details.
1012 If you are updating from a prior version of FreeBSD (even one just
1013 a few days old), you should follow this procedure. With a
1014 /usr/obj tree with a fresh buildworld,
1015 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1016 make installkernel KERNCONF=YOUR_KERNEL_HERE
1018 To just build a kernel when you know that it won't mess you up
1019 --------------------------------------------------------------
1020 cd src/sys/{i386,alpha}/conf
1021 config KERNEL_NAME_HERE
1022 cd ../../compile/KERNEL_NAME_HERE
1027 If this fails, go to the "To build a kernel" section.
1029 To rebuild everything and install it on the current system.
1030 -----------------------------------------------------------
1031 # Note: sometimes if you are running current you gotta do more than
1032 # is listed here if you are upgrading from a really old current.
1034 <make sure you have good level 0 dumps>
1035 <maybe fix /etc/fstab> [7]
1037 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1038 make installkernel KERNCONF=YOUR_KERNEL_HERE
1040 <reboot in single user> [3]
1047 To upgrade from 4.x-stable to current
1048 -------------------------------------
1049 # 5.x uses more space than 4.x. Also, the location of kernel
1050 # modules has changed. If you are installing 5.0 onto a 4.x
1051 # system, you'll need about 30MB of free disk space on your /
1052 # partition. If you have less than this, you may encounter difficult
1053 # to back out of problems with this proceedure. If /tmp is on
1054 # the / partition, you may want to completely remove all its content
1055 # before upgrading, as this can be a common source of shortage of
1058 <make sure you have good level 0 dumps>
1059 <maybe fix /etc/fstab> [7]
1061 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1062 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1063 make installkernel KERNCONF=YOUR_KERNEL_HERE
1064 cd src/sys/boot ; make install [6]
1066 <reboot in single user> [3]
1068 rm -rf /usr/include/g++
1073 Make sure that you've read the UPDATING file to understand the
1074 tweaks to various things you need. At this point in the life
1075 cycle of current, things change often and you are on your own
1076 to cope. The defaults can also change, so please read ALL of
1077 the UPDATING entries.
1079 Also, if you are tracking -current, you must be subscribed to
1080 freebsd-current@freebsd.org. Make sure that before you update
1081 your sources that you have read and understood all the recent
1082 messages there. If in doubt, please track -stable which has
1083 much fewer pitfalls.
1085 [1] If you have third party modules, such as vmware, you
1086 should disable them at this point so they don't crash your
1089 [2] If you have legacy ISA devices, you may need to create
1090 your own device.hints to reflect your unique hardware
1093 [3] From the bootblocks, boot -s, and then do
1098 adjkerntz -i # if CMOS is wall time
1099 Also, when doing a major release upgrade, it is required that
1100 you boot into single user mode to do the installworld.
1101 For the 4.x -> 5.0 upgrade, you will also see many messages about
1102 needing to recompile your userland. These are harmless and can
1103 be ignored while you proceed to the next step.
1105 [4] Note: This step is non-optional. Failure to do this step
1106 can result in a significant reduction in the functionality of the
1107 system. Attempting to do it by hand is not recommended and those
1108 that pursue this avenue should read this file carefully, as well
1109 as the archives of freebsd-current and freebsd-hackers mailing lists
1110 for potential gotchas.
1112 [5] Usually this step is a noop. However, from time to time
1113 you may need to do this if you get unknown user in the following
1114 step. It never hurts to do it all the time. You may need to
1115 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1116 install) after the buildworld before this step if you last updated
1117 from current before 20020224 or from -stable before 20020408.
1119 [6] 4.x boot loader can be used to boot a 5.x system, however
1120 it is difficult to do that at best. If you wish to try, then
1121 you should interrupt the boot and at the ok prompt type:
1123 ok boot /boot/kernel/kernel
1124 If this fails to work, you must install a new boot loader as
1127 [7] Before you upgrade, please make sure that you are not using
1128 compatibility slices. These are device names of the form, on i386
1129 and other architectures that use MBR slicing, /dev/ad0a without the
1130 actual slice name. Chances are excellent that these will break.
1131 You generally must update these entries to use the post FreeBSD
1132 2.x form of /dev/ad0s1a.
1134 [8] In order to have a kernel that can run the 4.x binaries
1135 needed to do an installworld, you must include the COMPAT_FREEBSD4
1136 option in your kernel. Failure to do so may leave you with a system
1137 that is hard to boot to recover.
1139 [9] When checking out sources, you must include the -P flag to have
1140 cvs prune empty directories.
1143 This file contains a list, in reverse chronological order, of major
1144 breakages in tracking -current. Not all things will be listed here,
1145 and it only starts on March 15, 2000. Updating files can found in
1146 previous releases if your system is older than this.
1148 Copyright information:
1150 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1152 Redistribution, publication, translation and use, with or without
1153 modification, in full or in part, in any form or format of this
1154 document are permitted without further permission from the author.
1156 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1157 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1158 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1159 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1160 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1161 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1162 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1163 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1164 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1165 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1166 POSSIBILITY OF SUCH DAMAGE.
1168 If you find this document useful, and you want to, you may buy the
1171 Contact Warner Losh if you have any questions about your use of