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 FreeBSD 5.x IS SLOW:
8 FreeBSD 5.x 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 The API and ABI of struct ifnet have been changed by removing
22 the if_name and if_unit members and replacing them with
23 if_xname, if_dname, and if_dunit. All network drivers and most
24 userland programs which include net/if_var.h must be updated
25 and recompiled. __FreeBSD_version has been bumped to 501113 to
29 Changes to the cdevsw default functions have been made to remove
30 the need to specify nullopen() and nullclose() explicitly.
31 __FreeBSD_version bumpted to 501110.
34 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
35 mount_cd9660(8) need to be in sync with kernel.
38 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
39 also be explicitly configured. Previously this dependency was
40 magically handled through some cruft in net/pfil.h; but that has
41 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
42 will fail with obtuse errors in ip_fil.c.
45 Fix a bug in arplookup(), whereby a hostile party on a locally
46 attached network could exhaust kernel memory, and cause a system
47 panic, by sending a flood of spoofed ARP requests. See
51 A change to /etc/defaults/rc.conf now causes inetd to be started
52 with `-C 60' if it is not overridden in /etc/rc.conf. This
53 causes inetd to stop accepting connections from an IP address
54 that exceeds the rate of 60 connections per minute.
57 The following rc.d scripts have been removed and should be
58 deleted from your installation: atm2.sh atm3.sh devdb
59 localdaemons network1 network2 network3. Depending on when
60 you last updated world and used mergemaster(8) you may or
61 may not have problems during the rc boot sequence. The simplest
62 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
63 The atm2.sh atm3.sh and devdb scripts were removed some time
64 ago, so depending on when you installed -CURRENT these scripts
65 may or may not exist on your system.
68 ATAng has been committed. You need to build world as sys/ata.h
69 has changed, and userland atacontrol depends on it.
70 If you use ATA SW raids you need "device ataraid" in your
71 kernel config file, as it is no longer pulled in automatically.
74 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
75 Among other things, this changes the device enumeration to be
76 closer to Solaris. Be aware that, this can even cause the machine
77 to not boot without manual intervention before the fstab is adjusted.
80 All current USB and Firewire quirks in da(4) have been deprecated
81 and will be removed for 5.2. If this causes failure for your
82 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
83 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
84 so the quirk can be re-enabled.
87 FPU-less support has been removed from FreeBSD. Chances are you won't
88 notice. 386+387 support should still work after this change, but
89 it is now a minimum requirement for the i386 port that you have real
93 Some people are having problems with changes related to /rescue.
94 If you are building -j N, you will need to define NO_RESCUE. Others
95 will need to define it if /rescue has issues with their environment.
96 People should report those issues to current@.
99 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
100 across this point. Further, it might be a good idea to remove
103 20030613: [retrospective]
104 There was a small window in which sed(1) was broken. If you
105 happen to have sed(1) installed during that window, which is
106 evidenced by an inability to build world with the failure
107 given below, you need to manually build and install sed(1)
108 (and only sed(1)) before doing anything else. This is a one-
109 time snafu. Typical failure mode:
111 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
112 targmatch.h:7:1: null character(s) ignored
113 targmatch.h:12:1: null character(s) ignored
114 targmatch.h:16:1: null character(s) ignored
117 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
118 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
119 usr.bin/sed/process.c).
122 Remove deprecated locale names and transition period code
123 for them, finishing switching to the new scheme. Check your
124 LANG environment variable.
127 CCD has been changed to be a fully GEOMified class. Kernel
128 and ccdconfig(8) needs to be in sync, this is particularly
129 important to remember beforehand if your source tree is on
130 a ccd device. Consider making a copy of the old ccdconfig
131 into /boot/kernel.good or wherever you keep your backup
135 Kerberos 5 (Heimdal) is now built by default. Setting
136 MAKE_KERBEROS5 no longer has any effect. If you do NOT
137 want the "base" Kerberos 5, you need to set NO_KERBEROS.
140 groff has been updated. If you try to do a buildworld and
141 get an infinite loop in troff, update to May 4th or newer. If you
142 have a newer kernel than userland, you may need to set the OSRELDATE
143 to 500110 in your environment before starting a buildworld.
146 The old rc system has been removed. Please report any problems
147 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
148 Your personal versions of these files will not be removed, so you can
149 continue to use them. However, you should take great care when updating,
150 especially when using mergemaster, since the compatibility code that
151 utilizes these old scripts has also been removed.
154 A bug has been fixed in /dev/devctl which would cause devd
155 to hang on boot, were it not for a workaround in devd. The
156 work around in devd will be removed around 20030507. You
157 have until then to upgrade your kernel before updating
158 userland. In general, you should have a userland and
159 kernel that's in sync with each other. However, given the
160 effects of this bug (hang on boot when starting devd), some
164 Alphas with libc from between 20030312 and 20030329 exhibit
165 floating point exceptions (FPEs), most notably in awk(1)
166 while upgrading the system through a buildworld.
168 So, to successfully upgrade your Alpha, you must either
169 downgrade your libc.so to a pre-20030312 version, or update
170 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
171 to CFLAGS, then forcibly rebuild and install libc:
173 cd /usr/src/lib/libc && \
174 make cleandir && make obj && \
175 make -DNOMAN -DNOPROFILE all && \
176 make -DNOMAN -DNOPROFILE install
179 sendmail 8.12.7 has been imported. It has one important
180 change for IPv6 users. The default submit.mc now uses
181 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
182 used to connect to the MTA. Users on IPv6-only machines
183 will need to edit /etc/mail/submit.mc appropriately.
186 NODEVFS option has been removed and DEVFS thereby made standard.
187 This makes all references to MAKEDEV obsolete, and they should
188 be removed when convenient.
191 The name of the device for the ofw console has changed, sparc64 users
192 must run mergemaster to update their installed /etc/ttys.
195 The scheduler framework has grown a second scheduler and consequently
196 you must specify one and only one scheduler in your kernel config.
197 The cvs config files have been updated to use the old scheduler
198 which may be selected via 'options SCHED_4BSD'. If you would like
199 to try the new, much more experimental, scheduler please try
200 'options SCHED_ULE' and contribute to the arch@ discussion.
203 A new version of the wi driver has been imported into the tree.
204 One now must have device wlan in the config file for it to operate
207 In addition, there have been some changes to how wi devices are
208 configured for point to point links to bring it more in line
209 with the former way of doing things, as well as compatibility
213 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
214 used an incompatible form of ABI for returning structures and unions
215 which FreeBSD's GCC maintainers were not aware of relative to previous
216 versions of FreeBSD. We have gone back to the ABI for now, and any
217 code compiled which is required to interoperate with other code (not
218 built at the same time) returning structs or unions should be
222 A name change in /etc/netconfig has been reverted to stay
223 compatible with suns TIRPC and also with NetBSD. You need
224 to run mergemaster after make world. A new libc does still work
225 with an outdated /etc/netconfig for some time, but you'll get
226 a warning. This warning will be removed in 20030301.
229 The recent binutils upgrade marks a kernel flag day on
230 sparc64: modules built with the old binutils will not work
231 with new kernels and vice versa. Mismatches will result in
232 panics. Make sure your kernel and modules are in sync.
235 The value of IPPROTO_DIVERT has changed. Make sure to keep
236 your kernel, netstat, natd and any third-party DIVERT
240 Old, compatibility slices have been removed in GEOM kernels.
241 This means that you will have to update your /etc/fstab to
242 not use disk devices of the form /dev/ad0a. Instead, you
243 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
244 partition really is on. The old device names have gone
245 away, so if you use them anywhere else, you must also adjust
246 those uses. (This doesn't affect the disks formatted in
247 the ``dangerously-dedicated'' mode.)
250 Alphas with kernels from between 20020830 and 20021023 and/or
251 rtld (ld-elf.so.1) older than 20021023 may experience problems
252 with groff while doing a buildworld (kernel: "out of memory",
253 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
254 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
256 So, to successfully upgrade your Alpha, you must either
257 upgrade your kernel and rtld first (which might be a bit
258 tricky), or avoid running the bootstrapped groff during the
259 "transitional" buildworld. To avoid running groff during the
260 transitional upgrade run make buildworld with -DNOMAN,
261 -DNO_SHAREDOCS, and -DNO_LPR.
264 gcc has been upgraded to 3.2. It is not all binary compatible
265 with earlier versions of gcc for c++ programs. All c++
266 programs and libraries need to be recompiled.
268 Also, if you encounter g++ issues, rm /usr/include/g++/* before
269 doing an installworld to make sure that stale files are removed.
272 Our /etc/termcap now has all the entries from the XFree86 xterm
273 almost unchanged. This means xterm now supports color by default.
274 If you used TERM=xterm-color in the past you now should use
275 TERM=xterm. (xterm-color will lead to benign warnings).
278 A "bug" in gcc(1) that was hiding warning in system headers was
279 fixed. It's probably time to add -DNO_WERROR to your make line
283 COPY is being deprecated. The 20010530 change was reverted, as
284 it causes far more pain than was expected, and to always compare
285 before installing, please use INSTALL="install -C" again. The
286 -C option is now silently ignored when used with the -d option.
289 Problems with libc_r clients like KDE and GNOME have been resolved.
290 There are still some minor problems with some signals but the
291 system is stable enough for general use again. SMP is less so than UP
292 but each can successfully complete multiple buildworlds.
293 Libkvm needs to be recompiled due to KSE.
296 Now would be a bad time to upgrade. Something in or near the
297 KSE commit totally broke programs using libc_r like KDE and
301 The k5su utility installed as part of Kerberos 5 is no longer
302 installed with the set-user-ID bit set by default. Add
303 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
304 with the set-user-ID bit set.
307 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
308 Unfortunately our native GDB (at version 4.18) does not understand
309 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
310 generated debugging information for our native GDB.
313 Due to the way CVS works, it may not properly update src/contrib/gcc
314 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
315 and then do a cvs update.
318 When exec'ing set[ug]id executables, the kernel now ensures that the
319 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
322 New sendmail startup scripts have been installed to make it
323 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
324 variable sendmail_enable to "NO" no longer prevents any sendmail
325 daemons from starting. Instead, either set sendmail_enable to
326 "NONE" or change mta_start_script to a script for starting
327 an alternative MTA. Setting mta_start_script to "" will
328 also prevent any MTA from being started at boot.
331 UCONSOLE is no longer a valid kernel option.
334 FreeBSD 5.0 DP-1 was basically branched today.
337 Warnings are now errors in the kernel. Unless you are a developer,
338 you should add -DNO_WERROR to your make line.
341 sendmail 8.12.2 has been imported. The sendmail binary is no
342 longer a set-user-ID root binary and the infrastructure to support
343 command line mail submission has changed. Be sure to run
344 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
345 and /etc/mail) and read /etc/mail/README for more details.
347 Due to the import of sendmail 8.12.2, a new user and group are
348 required in order for sendmail to run as a set-group-ID
349 binary. A 'make installworld' will use the new user and group
350 to set the owner and group of /var/spool/clientmqueue and will
351 fail if the new user and group do not exist. The 'smmsp' user
352 and group must be merged from src/etc/group and
353 src/etc/master.passwd before using 'make installworld'.
354 'mergemaster -p' will do this. You may need to install
355 mergemaster before this will work if you are updating from a
356 very old version of current. The updating recipe has changed
360 The preferred configuration method for PAM is now /etc/pam.d/
361 rather than /etc/pam.conf. If you have an unmodified
362 pam.conf, just delete it after your next mergemaster run. If
363 you have local modifications, you can use
364 /usr/src/etc/pam.d/convert.pl to incorporate them into your
367 Please see the following url for more details:
368 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
370 If anyone here is already using the new rc.conf(5) variable
371 networkfs_types, please note that it has changed
372 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
375 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
376 started out its life in the ISDN4BSD project as an offspring
377 from sys/net/if_spppsubr.c, which eventually got a life of its
378 own. All the accumulated features and bugfixes of the i4b
379 version have now been merged back into the base system's
380 version now. The only user-visible change resulting from this
381 is that i4b's sppp(4) interfaces are to be managed with
382 spppcontrol(8) again, since ispppcontrol(8) has been retired
383 as well. (There has never been rc file support for
384 ispppcontrol in -current, but only in -stable. That will be
385 reverted by the time the changes are MFCed.)
388 The fdc(4) driver has been updated and now automatically
389 recognizes media in `standard' formats (like 1440 KB and
390 720 KB for a 3.5" high-density drive) when accessing the
391 default device node (e. g. /dev/fd0). The old variety of
392 floppy device nodes /dev/fd*.* is no longer present by
393 default, devices can be created (in DEVFS) on demand. They
394 will need to be customized then for `odd' densities using
398 The bugs in procfs' debugging support code have been fixed,
399 and truss(1) now works again.
402 Daily security checks have been split out to use the periodic(8)
403 scripts. Some change in configuration may be necessary. Please
405 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
409 sos added VCD/SVCD support to ata driver and that needs the
410 kernel and burncd to be in sync.
413 The procfs pseudo-filesystem has now been converted to use the
414 pseudofs framework. If you have 'options PROCFS' in your
415 kernel config, you'll need to add 'options PSEUDOFS' if it's
418 This change temporarily breaks truss(1); use ktrace(1) instead
419 until the issue has been resolved.
422 A security hole in OpenSSH involving `UseLogin yes' has been
426 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
427 after this date. You need to do this only once.
430 Most of the awk issues have been resolved. Some rough
431 edges may be left, but for the most part things should be
432 back to "normal." For CURRENT's usual definition of "normal."
435 Awk has been upgraded to the one true awk from bell labs. Expect
436 choppy waves in the upgrade process.
439 The asr driver problem has been resolved.
442 Due to changes in other parts of the system, the asr driver
443 now causes the system to panic on boot. Do not use it pending
444 correction. Comment it out of any kernel config file that you
445 try to use from this date forward.
448 When crossbuilding, use TARGET=xxx where you used to use
449 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
450 unless you are changing both of them. To cross build pc98 on
451 an alpha, for example, you need to set TARGET=pc98 and
455 The kernel interface that burncd depends on has changed.
456 You must recompile both the kernel and userland applications
460 When crossbuilding, please set TARGET_ARCH rather than
461 MACHINE_ARCH to indicate the target. In the future, one will
462 set TARGET_MACHINE where you set MACHINE now. At the moment,
463 setting MACHINE alone for same MACHINE_ARCH machines works
464 (eg, you can build pc98 on an i386 machine and vice versa).
467 Some weird problems result from using ACPI on some machines.
468 To disable ACPI you can add
469 hint.acpi.0.disabled="1"
470 to /boot/loader.conf (or by putting set X=Y at the boot
473 Alternatively, you can remove it from /boot/kernel/acpi.ko
474 or use the MODULES_OVERRIDE function in your kernel config
475 file and not list acpi in that list.
478 The buildworld has been fixed. You may need to install
479 the 4.x compatibility libraries for some old binaries
480 to work. Add COMPAT4X=true to your /etc/make.conf to
481 get them installed on every installworld, or execute the
482 following to get them installed only once:
483 cd src/lib/compat/compat4x.<arch>
485 You will see ``__stdoutp undefined'' until you do this.
488 There's a bug in the world build process. The cross-tools
489 are build with the NEW headers, but the OLD libc.a. This
490 leads to all kinds of problems with the new libc. A temporary
492 CFLAGS="-O -pipe -D_OLD_STDIO"
493 before building world when upgrading from 4.x to current. This
494 can be removed afterwards.
496 A proper fix to the buildworld target is needed.
499 Peter has committed his new kthread nfs client/server code.
500 NFS may be unstable after this date.
503 KSE has hit the tree. Lots of things are now different in
504 the kernel. While a few problems were introduced in the
505 initial commit, most of the major ones have been found and
509 In OLDCARD, CardBus bridges appear to be stable. The work
510 arounds described in the 20010604 entry are now no longer
511 necessary and will be ignored. Most insert/remove problems
512 have been rectified around this date.
515 named now runs as user bind and group bind rather than as
516 root. If named_enable is set to YES in /etc/rc.conf, ensure
517 that user bind is available in /etc/passwd (using vipw(8))
518 and that group bind is available in /etc/group. Also make
519 sure that user or group bind has read (and not write)
520 permission for your name server configuration and that it
521 has read and write permission for your slave zone files and
524 If you wish to continue to run named as root (a less secure
525 alternative), add a line to /etc/rc.conf saying
530 The PAM libraries have had an API upgrade that is beyond
531 the ability of the shared library major number to handle.
532 It is manifested by PAM-using ports dumping core. The
533 solution is to rebuild those ports.
536 The kernel compile module has moved from src/sys/compile/FOO
537 to src/sys/${MACHINE}/compile/FOO.
540 The pccard modem issue from 20010613 has been corrected.
541 OLDCARD support is still a little weak in -current. slot 1 is
542 known not to work on some TI based cardbus bridges. Some
543 cardbus bridges do not properly detect insert/removal events.
544 IRQ configuration needs more safety belts.
547 Softupdates problems have been corrected.
550 Peter ripped out the linkerset support. You must, as always,
551 rerun config after you cvsup if you are using the traditional
552 kernel building methods.
555 pccard modems may not work with current after 20010604 date. Some
556 do, others result in panics. *MAKE*SURE* that you update your
557 config and /etc/rc.conf ala the 20010604 entry, or you will have
558 problems (this issue will be fixed, it just hasn't been yet).
561 SOFTUPDATES seem to be broken since the middle of May or so. Do not
562 use them in current. You can disable softupdates on all mounted
563 partitions, or remove SOFTUPDATES the kernel config file.
566 After Peter's commits to the hints code, people have been noticing
567 that certain devices are attached (or try to) twice. This is due
568 to having both static hints as well as a /boot/device.hints. To
569 work around this issue, please use only one or the other mechanism
570 until this bug is fixed.
572 Please note that a feature of config is that if you have config
573 file FOO and FOO.hints, it automatically adds FOO.hints to the
574 hints.c file, whether you want it to or not.
577 Locale names have changed to match other systems better.
580 pccard support for pci cards has been committed. You must change
581 your /etc/pccard.conf irq lines. It must match the irq used by
582 pcic device. Interrupt storms may result if you fail to do this.
583 Interrupt storms look a lot like a hang.
585 You must also install a new pccardd, otherwise you will get an
586 interrupt storm at card reset time (just after it tells you what
589 pccardd_flags="-I" is necessary for the time being. It tells pccardd
590 not to ask the kernel if the interrupt is really free or not before
591 using it. You can either change the /etc/pccard.conf irq lines to
592 match pcic, or add "-i X" to the pccardd_flags.
595 INSTALL=install -C is being deprecated. If you want to do this,
596 use COPY=-C instead. The former method will be supported for only
597 a limited time. If you see
599 install: warning: the -d and -C options may not be specified together
601 in your makeworld, then you need to migrate towards using
605 It appears that vm is now stable enough to use again. However,
606 there may be other problems, so caution is still urged. alpha
607 definitely is in bad shape.
610 Minor repo damage has happened. This may cause problems
611 with cvsup of ports. If you get errors, please see
612 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
613 at the bottom for details on a workaround. The error message
615 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
618 Vm and/or swapping are busted on -current. Please be patient.
621 pccard has had much reorganizational work done to it over
622 the past few days. Everything should still work, but if
623 not, please contact imp@freebsd.org.
626 ata ioctl changed. Make sure to recompile both kernel and
627 userland at the same time.
630 New ncurses imported.
633 DEVFS is now opt out, not opt in. Barring major problems, this
634 will be the only way to go starting July 1.
637 OpenSSH has been updated to 2.9. Some defaults are different,
638 including RhostsRSAAuthentication, which changes from yes to no.
641 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
644 Building perl was broken at 02:25:25 PDT.
647 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
648 go back in the water.
651 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
652 this date, but before the correction date.
655 old fsck and new kernel interactions appear to have been fixed.
658 fsck and the kernel were changed to handle some optimizations
659 to directory layout. This breaks backward compatibility.
660 Update only if you understand that you must not use the old
661 fsck with the new kernel ever.
664 fsck has changed the meaning of the pass column in /etc/fstab.
665 Please see the cvs commit to fsck.8 or the fsck.8 man page for
666 details. It is unclear if changes to /etc/fstab are necessary.
669 portmap had changed name to rpcbind for maximum POLA in your
670 current world. /etc/hosts.{allow,deny} needs changes. nfs and
671 other rpc based programs that rely on portmapper will not work
672 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
675 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
676 and ATA_ENABLE_TAGS are no longer kernel options. They have
677 been replaced by tunables. See ata.4 for details.
680 The fxp driver was converted to use miibus. If you compile
681 fxp into your kernel statically, you will need to add miibus.
684 The wi device now defaults to BSS (infrastructure) mode
688 /dev/urandom should be a symbolic link to /dev/random now.
689 Users of current not using DEVFS need to run MAKEDEV std.
690 ssh might not work if you don't.
693 The ed driver has been updated. It now allows mii attachments,
694 which means that you must include the miibus in your kernel if
695 you use the ed driver.
698 The problems with libc have been corrected. It is now mostly
699 safe to go back into the water.
702 The size of FILE was changed. This breaks upgrading. If
703 you must upgrade, be prepared for pain. It also breaks almost
704 all binaries that you've compiled on -current. You are warned
705 that before upgrading would be a good time to do a level 0
706 dump of your system. No, really, I mean it this time.
708 To get to the new system, you'll need to use the following
709 workaround. Hopefully this can be sorted out so that we
710 don't have to move this to the updating section.
712 To get around the installworld problem, do:
713 # cd /usr/src/usr.bin/sed
717 If that doesn't work, then try:
718 # make -k installworld
722 DEVFS is now the default. If you use vinum, make sure that you
723 do not include devfs in your kernel as problems result.
726 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
727 Remove them from your config.
730 ****************************** WARNING ******************************
731 buildkernel has been changed slightly
732 ****************************** WARNING ******************************
733 KERNCONF replaces the variable KERNEL for buildkernel. You
734 should update your scripts and make.conf accordingly.
737 config has changed to allow DEV_FOO as a replacement for NFOO.
738 This requires a new config to build correctly.
741 The kernel option I386_CPU is now mutually exclusive with the
742 other cpu types. If you have an i386 system, be sure that it
743 only had this line. Remove it for all other configurations.
746 Changes to the kernel require it and burncd be in sync.
749 Everyone who has hw.sndunit set to something in
750 /etc/sysctl.conf, it is now hw.snd.unit.
753 ex and vi were broken by some changes to sys/queue.h. If you
754 have a bad vi, you will see make buildworld fail with a core
755 dump while building termcap. You can work around this problem
756 by adding -k to your make buildworld. This will cause the
757 build to complete and install a new vi. Once that's done, you
758 can rebuild again without the -k to pick up anything that
759 might have been ignored by the -k option.
761 Others have suggested that you can just rebuild libc if your
762 vi/ex is dynamically linked, but I've not received any reports
766 There have been some changes to libcrypt in -current. The
767 libscrypt/libdescrypt symlink silliness is gone and the installed
768 libcrypt is fully functional. Be aware of this.
771 Linksys Fast Ethernet PCCARD cards supported by the ed driver
772 now require the addition of flag 0x80000 to their config line
773 in pccard.conf(5). This flag is not optional. These Linksys
774 cards will not be recognized without it.
777 Important new FreeBSD-version stuff: PAM support has been worked
778 in, partially from the "Unix" OpenSSH version. This requires
779 adding the following in pam.conf:
781 sshd auth sufficient pam_skey.so
782 sshd auth required pam_unix.so try_first_pass
783 sshd session required pam_permit.so
789 The random device needs more entropy, so you need to make sure
790 that you've run mergemaster to get a /etc/rc which will seed
791 /dev/random. If you don't and the system hangs after ldconfig,
792 then banging on the keyboard randomly until it unhangs is one
796 ****************************** WARNING ******************************
797 Sendmail has been updated.
798 ****************************** WARNING ******************************
799 o mail.local(8) is no longer installed as a set-user-id binary.
800 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
802 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
804 o Now using sendmail's version of vacation(1).
805 o The sendmail cf building tools (contrib/sendmail/cf) are installed
806 in /usr/share/sendmail/cf.
807 o sendmail.cw changed to local-host-names
809 More details can be found at
810 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
813 The ports tree's new layout is in place. Be sure to update
814 your entire ports tree, or you will have problems.
817 The perl build procedure no longer installs miniperl, nor uses
818 the installed miniperl. It is recommended that you delete
822 This weekend the ports tree will be updated to a new layout.
823 It will be in an inconsistent state until noted in the UPDATING
824 file, or with asami-san's message to the relevant mailing
825 lists. With this new layout, you'll need to update the whole
826 tree for anything to work.
829 There was a change in the passwd format. Need more information.
832 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
833 place. Please update boot loader (not the boot blocks) at the
834 same time as your kernel.
837 The new pmtimer device is necessary for laptops. Failure to
838 include the device will cause suspended laptops losing time
839 when they resume. Include
841 in your config file and
842 hint.pmtimer.0.at="isa"
843 to your /boot/device.hints file.
846 The random device has been turned into a (pseudo-)device,
847 rather than an option. The supplied kernel config files have
848 been updated. You will need to do something similar in your
849 own kernel config file.
854 If you prefer to load the loadable module, you need to do
858 The random device module has been renamed from randomdev.ko to
859 random.ko. You will need to edit your /boot/loader.conf to
860 reflect this if you load this module at boot time.
861 The line should read:
865 The SMPNG commit has happened. It should work, but if it
866 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
867 to be a variety of minor issues. Please see 20000905 to make
868 sure you don't have model loading problems which might at
869 first blush appear related to SMP.
872 nsswitch has been imported from NetBSD. Among other things,
873 this means that /etc/host.conf is no longer used. See
874 nsswitch.conf(5) instead. Note that at boot time rc.network
875 will attempt to produce a new nsswitch.conf file for you if you
876 don't have one, and you have host.conf.
879 The ucred structure changed size. This breaks the interface
880 that mountd uses. Trying to use an older mountd with a newer
881 kernel guarantees a panic. This means that you need to use
882 kernels newer than today only with matching mountd, but you
883 needed to do that anyway with the boot loader changes.
886 The boot loader has been updated. The new default kernel is
887 now /boot/kernel/kernel.ko. The new default module location
890 You *MUST* upgrade your boot loader and kernel at the same time.
891 The easiest way to do this is to do the buildworld/buildkernel/
892 installkernel/installworld dance.
894 Furthermore, you are urged to delete your old /modules directory
895 before booting the new kernel, since kldload will find stale
896 modules in that directory instead of finding them in the correct
897 path, /boot/kernel. The most common complaint that this cures
898 is that the linux module crashes your machine after the update.
900 if [ ! -d /boot/kernel.old ]; then
901 mv /modules.old /boot/kernel.old
902 chflags noschg /kernel.old
903 mv /kernel.old /boot/kernel.old/kernel.ko
904 chflags schg /boot/kernel.old/kernel.ko
908 A new issue with the sendmail upgrade has come to light.
909 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
910 incorrectly install the default aliases in /etc/mail rather than
911 move the old one from /etc. So you'll need to manually move the
912 file, create a symbolic link, remove the old /etc/aliases.db and
913 run newaliases. For safety sake, you should stop sendmail
914 while doing this and run the upgrade when locally sourced email
915 is not likely to be generated.
918 /boot/device.hints is now required for installkernel to
919 succeed. You should copy GENERIC.hints for your architecture
920 into /boot/device.hints. If and only if you compile hints
921 into your kernel, then this file may be empty. Please note,
922 if you have an empty or missing /boot/device.hints file and
923 you neglected to compile hints into your kernel, no boot
924 messages will appear after the boot loader tries to start the
928 If you do NOT have ``options RANDOMDEV'' in your kernel and
929 you DO want the random device then add randomdev_load="YES" to
933 suidperl is now always built and installed on the system, but
934 with permissions of 511. If you have applications that use
935 this program, you are now required to add ENABLE_SUIDPERL=true
936 to /etc/make.conf. If you forget to do this,
937 chmod 4511 /usr/bin/suidperl
938 will fix this until the next build.
941 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
942 visible changes that may immediately affect your configuration
944 - New default file locations from src/contrib/sendmail/cf/README
945 - newaliases limited to root and trusted users
946 - MSA port (587) turned on by default
947 - New queue file naming system so can't go from 8.11 -> 8.9
948 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
949 - FEATURE(`nullclient') is more full featured
950 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
951 - mail.local FreeBSD-only -b option changed to -B
952 - See src/contrib/sendmail/RELEASE_NOTES for more info
955 suidperl (aka sperl) is no longer build by default. You must
956 specifically define BUILD_SUIDPERL to "true" for it to be build.
957 Furthermore, we recommend that you remove /usr/bin/sperl* and
958 /usr/bin/suidperl files from your system unless you have a
962 Networking defaults have been tightened. Anybody upgrading
963 /etc/defaults/rc.conf needs to add the following lines to
964 /etc/rc.conf if they want to have the same setup
965 afterwards (unless the variables already are set, of course):
966 # Enable network daemons for user convenience.
969 sendmail_enable="YES"
972 If you have null_load="YES" in your /boot/loader.conf, you
973 will need to change that to nullfs_load="YES".
976 The "installkernel" target has changed slightly. Now even if
977 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
978 it will install the MYKERNEL file (built with the buildkernel
979 target) as /kernel rather than /MYKERNEL. Those who have
980 updated their /boot/loader.conf files to point to /MYKERNEL
981 should remove that entry or perform manual rename of /kernel
985 If you use CVSUP or CTM to get CVS trees, AND you used to get
986 the old crypto files from internat.freebsd.org AND you check
987 out files from the CVS tree with the cvs command, please read
988 http://people.freebsd.org/~imp/internat.txt
989 for details on potential problems that you might have and how
992 If you are merely a mirror, or don't answer yes to each of the
993 clauses above, you needn't worry.
996 /etc/security has been updated to print the inode number of
997 setuid programs that have changed. You will see a large spike
998 in the number of changed programs the first time when you run
999 mergemaster to get a new /etc/security.
1002 /dev/random now has good entropy collection (from the keyboard
1003 and sysmouse drivers). Please ensure that either `options
1004 RANDOMDEV' is present in your kernel config file or that
1005 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1006 not have the /dev/random driver, OpenSSL (and consequently
1007 lots of crypto tools (like SSH)) will fail with strange
1008 errors. (see below, 20000624).
1010 FreeBSD-current is safe again to run Crypto.
1013 phk made the malloc default options AJ. This may slow things
1014 down and uncover other latent bugs in the code. If you need to
1015 run at full speed, you can disable this by doing the following:
1016 ln -s aj /etc/malloc.conf
1019 libftpio's version was accidentally bumped a few days ago. This
1020 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1021 before doing your next buildworld/installworld pair. It certainly
1022 won't hurt to remove it before the update procedure. It will
1023 break fetch until a new one is built, but ftp can be used in the
1027 The crypto packages have changed for the cvsup. This has been done
1028 in a backward compatible way, but the old packages will go away at
1029 some point in the future. Look at /usr/share/examples/cvsup for
1033 With the new sys/modules/sound/drivers/*, you will need to
1034 set SYSDIR until you do an installworld after July 7th.
1037 rc.shutdown and rc will now call the rc.d scripts with start
1038 or stop. This may cause some harmless warnings from older
1039 rc.d scripts that haven't been updated.
1042 The libfetch based version of fetch has gone into the tree.
1043 Minor problems may result on some of the less popular sites,
1044 which should be reported to des@freebsd.org.
1047 From approximately this date forward, one must have the crypto
1048 system installed in order to build the system and kernel.
1049 While not technically strictly true, one should treat it as
1050 required and grab the crypto bits. If you are grabbing CVS
1051 trees, src-all and cvs-crypto should be treated as if they
1052 were required. You should check with the latest collections
1053 to make sure that these haven't changed.
1056 Mark Murray just committed the first parts of a cleanup of
1057 /dev/zero, et al. This is also cleaning up /dev/random.
1058 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1059 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1060 until Mark can merge in the fixes to this work in progress.
1061 openssh and openssl should not be used to generate keys from this
1062 date to the completion of the work.
1064 If you must operate at this reduced level of security, add '
1065 options RANDOMDEV' to your kernel or modload the randomdev
1066 module. You may also need to copy a new MAKEDEV to /dev and
1067 recreate the random and urandom devices.
1070 The license on the softupdates is now a standard 2 clause
1071 BSD license. You may need to remove your symbolic links
1072 that used to be required when updating.
1075 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1076 the config file update procedure.
1077 http://people.freebsd.org/~imp/config-upd.html
1078 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1079 isn't buildable. However, you can generate a LINT file:
1080 cd /sys/<ARCH>/conf && make LINT
1083 Binutils 2.10 have hit the tree, or will shortly. As soon
1084 as they do, the problem noted in 20000522 will be resolved and
1085 that workaround will no longer be required.
1088 phk removed the compatibility creation of wd devices in the
1089 ad driver. If you haven't done so already, you must update
1090 your fstab, etc to use the ad devices instead of the wd
1093 In addition, you'll need to update your boot blocks to a
1094 more modern version, if you haven't already done so. Modern
1095 here means 4.0 release or newer (although older releases
1099 Peter took an axe to config(8). Be sure that you read his mail
1100 on the topic before even thinking about updating. You will
1101 need to create a /boot/device.hints or add a hints directive
1102 to your config file to compile them in statically. The format
1103 of the config file has changed as well. Please see GENERIC or
1104 NEWCARD for examples of the new format.
1106 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1107 says that it has been fixed, assume that must use the hints mechanism
1108 in the loader if you need to use a machine with very old ISA cards
1112 A new set of binutils went into the tree today. Anybody
1113 building a kernel after this point is advised that they need
1114 to rebuild their binutils (or better yet do a
1115 buildworld/installworld) before building a new kernel.
1117 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1118 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1119 is recommended that you don't set this option until the problem
1123 The ethernet drivers were all updated to clean up the BPF handling.
1126 The problems with boot blocks on the alphas have been corrected.
1127 This will require some care in updating alphas. A new libstand
1128 is requires for the boot blocks to build properly.
1131 Recompile all kld modules. Proper version dependency info
1135 Modules have been disconnected from the buildworld tree and
1136 connected to the kernel building instead.
1139 You may need to build gperf
1140 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1141 when upgrading from 4.0 -> current. The build system now uses
1142 an option only in -current.
1145 The method that we brand ELF binaries has changed to be more
1146 acceptable to the binutils maintainers. You will need to
1147 rebrand your ELF binaries that aren't native. One problem
1148 binary is the Linux ldconfig. After your make world, but
1149 before you reboot, you'll need to issue:
1150 brandelf -t Linux /compat/linux/sbin/ldconfig
1151 if you have Linux compatibility enabled on your machine.
1154 If you have really bad/marginal IDE drives, you may find they
1155 don't work well. Use pio mode instead. The easiest way to
1156 cope if you have a problem combination is to add:
1157 /sbin/sysctl hw.ata.ata_dma=0
1158 to the start of /etc/rc.conf.
1161 The ISA and PCI compatibility shims have been connected to the
1162 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1163 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1164 include the appropriate option in your kernel config. Drivers
1165 using the shims should be updated or they won't ship with
1166 5.0-RELEASE, targeted for 2001.
1169 We've entered the traditional post release dumping party.
1170 Large kernel changes are being committed and are in the
1171 works. It is important to keep the systems' klds and kernel
1172 in sync as kernel interfaces and structures are changing.
1173 Before reporting kernel panics, make sure that all modules
1174 that you are loading are up to date.
1177 If you are upgrading from an older version of FreeBSD, you
1178 need to update your boot blocks as well. 'disklabel -B ad0'
1179 will do the trick. This isn't critical until you remove your
1180 wd device entries in /dev, at which point your system will not
1184 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1185 to upgrade to 4.0 from 3.x.
1191 Avoid using make -j when upgrading. From time to time in the
1192 past there have been problems using -j with buildworld and/or
1193 installworld. This is especially true when upgrading between
1194 "distant" versions (eg one that cross a major release boundary
1195 or several minor releases, or when several months have passed
1196 on the -current branch).
1198 Sometimes, obscure build problems are the result of environment
1199 poisoning. This can happen because the make utility reads its
1200 environment when searching for values for global variables.
1201 To run your build attempts in an "environmental clean room",
1202 prefix all make commands with 'env -i '. See the env(1) manual
1203 page for more details.
1207 If you are updating from a prior version of FreeBSD (even one just
1208 a few days old), you should follow this procedure. With a
1209 /usr/obj tree with a fresh buildworld,
1210 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1211 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1213 To just build a kernel when you know that it won't mess you up
1214 --------------------------------------------------------------
1215 cd src/sys/{i386,alpha}/conf
1216 config KERNEL_NAME_HERE
1217 cd ../../compile/KERNEL_NAME_HERE
1222 If this fails, go to the "To build a kernel" section.
1224 To rebuild everything and install it on the current system.
1225 -----------------------------------------------------------
1226 # Note: sometimes if you are running current you gotta do more than
1227 # is listed here if you are upgrading from a really old current.
1229 <make sure you have good level 0 dumps>
1230 <maybe fix /etc/fstab> [7]
1232 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1233 make installkernel KERNCONF=YOUR_KERNEL_HERE
1235 <reboot in single user> [3]
1242 To cross-install current onto a separate partition
1243 --------------------------------------------------
1244 # In this approach we use a separate partition to hold
1245 # current's root, 'usr', and 'var' directories. A partition
1246 # holding "/", "/usr" and "/var" should be about 2GB in
1249 <make sure you have good level 0 dumps>
1252 <maybe newfs current's root partition>
1253 <mount current's root partition on directory ${CURRENT_ROOT}>
1254 make installworld DESTDIR=${CURRENT_ROOT}
1255 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1256 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1257 ${CURRENT_ROOT}/boot/device.hints # as needed
1258 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1259 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1260 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1261 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1262 <reboot into current>
1263 <do a "native" rebuild/install as described in the previous section>
1264 <maybe install compatibility libraries from /usr/src/lib/compat>
1268 To upgrade in-place from 4.x-stable to current
1269 ----------------------------------------------
1270 # 5.x uses more space than 4.x. Also, the location of kernel
1271 # modules has changed. If you are installing 5.0 onto a 4.x
1272 # system, you'll need about 30MB of free disk space on your /
1273 # partition. If you have less than this, you may encounter difficult
1274 # to back out of problems with this procedure. If /tmp is on
1275 # the / partition, you may want to completely remove all its content
1276 # before upgrading, as this can be a common source of shortage of
1279 <make sure you have good level 0 dumps>
1280 <maybe fix /etc/fstab> [7]
1282 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1283 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1284 make installkernel KERNCONF=YOUR_KERNEL_HERE
1285 cd src/sys/boot ; make install [6]
1287 <reboot in single user> [3]
1289 rm -rf /usr/include/g++
1294 Make sure that you've read the UPDATING file to understand the
1295 tweaks to various things you need. At this point in the life
1296 cycle of current, things change often and you are on your own
1297 to cope. The defaults can also change, so please read ALL of
1298 the UPDATING entries.
1300 Also, if you are tracking -current, you must be subscribed to
1301 freebsd-current@freebsd.org. Make sure that before you update
1302 your sources that you have read and understood all the recent
1303 messages there. If in doubt, please track -stable which has
1304 much fewer pitfalls.
1306 [1] If you have third party modules, such as vmware, you
1307 should disable them at this point so they don't crash your
1310 [2] If you have legacy ISA devices, you may need to create
1311 your own device.hints to reflect your unique hardware
1314 [3] From the bootblocks, boot -s, and then do
1319 adjkerntz -i # if CMOS is wall time
1320 Also, when doing a major release upgrade, it is required that
1321 you boot into single user mode to do the installworld.
1322 For the 4.x -> 5.0 upgrade, you will also see many messages about
1323 needing to recompile your userland. These are harmless and can
1324 be ignored while you proceed to the next step.
1326 [4] Note: This step is non-optional. Failure to do this step
1327 can result in a significant reduction in the functionality of the
1328 system. Attempting to do it by hand is not recommended and those
1329 that pursue this avenue should read this file carefully, as well
1330 as the archives of freebsd-current and freebsd-hackers mailing lists
1331 for potential gotchas.
1333 [5] Usually this step is a noop. However, from time to time
1334 you may need to do this if you get unknown user in the following
1335 step. It never hurts to do it all the time. You may need to
1336 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1337 install) after the buildworld before this step if you last updated
1338 from current before 20020224 or from -stable before 20020408.
1340 [6] 4.x boot loader can be used to boot a 5.x system, however
1341 it is difficult to do that at best. If you wish to try, then
1342 you should interrupt the boot and at the ok prompt type:
1344 ok boot /boot/kernel/kernel
1345 If this fails to work, you must install a new boot loader as
1348 [7] Before you upgrade, please make sure that you are not using
1349 compatibility slices. These are device names of the form, on i386
1350 and other architectures that use MBR slicing, /dev/ad0a without the
1351 actual slice name. Chances are excellent that these will break.
1352 You generally must update these entries to use the post FreeBSD
1353 2.x form of /dev/ad0s1a.
1355 [8] In order to have a kernel that can run the 4.x binaries
1356 needed to do an installworld, you must include the COMPAT_FREEBSD4
1357 option in your kernel. Failure to do so may leave you with a system
1358 that is hard to boot to recover.
1360 [9] When checking out sources, you must include the -P flag to have
1361 cvs prune empty directories.
1364 This file contains a list, in reverse chronological order, of major
1365 breakages in tracking -current. Not all things will be listed here,
1366 and it only starts on March 15, 2000. Updating files can found in
1367 previous releases if your system is older than this.
1369 Copyright information:
1371 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1373 Redistribution, publication, translation and use, with or without
1374 modification, in full or in part, in any form or format of this
1375 document are permitted without further permission from the author.
1377 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1378 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1379 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1380 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1381 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1382 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1383 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1384 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1385 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1386 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1387 POSSIBILITY OF SUCH DAMAGE.
1389 If you find this document useful, and you want to, you may buy the
1392 Contact Warner Losh if you have any questions about your use of