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 statfs structure has been updated with 64-bit fields to
22 allow accurate reporting of multi-terabyte filesystem
23 sizes. You should build world, then build and boot the new kernel
24 BEFORE doing a `installworld' as the new kernel will know about
25 binaries using the old statfs structure, but an old kernel will
26 not know about the new system calls that support the new statfs
28 Note that the backwards compatibility is only present when the
29 kernel is configured with the COMPAT_FREEBSD4 option. Since
30 even /bin/sh will not run with a new kernel without said option
31 you're pretty much dead in the water without it. Make sure you
33 Running an old kernel after a `make world' will cause programs
34 such as `df' that do a statfs system call to fail with a bad
35 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
36 that cfsd (ports/security/cfs) needs to be recompiled after
37 these changes are installed.
39 ****************************DANGER*******************************
41 DO NOT make installworld after the buildworld w/o building and
42 installing a new kernel FIRST. You will be unable to build a
43 new kernel otherwise on a system with new binaries and an old
47 Some netgraph string length constants have been changed. This
48 change requires the netgraph kernel modules and all netgraph
49 userland components to be in sync. Especially users who require
50 netgraph to boot need to make sure to have world and kernel in
51 sync before rebooting.
54 The i386 APIC_IO kernel option has been replaced by
55 'device apic'. The ACPI module has also been temporarily
56 disabled, so ACPI must be statically compiled into your
57 kernel using 'device acpi' if you wish to use the ACPI driver.
60 The API and ABI of struct ifnet have been changed by removing
61 the if_name and if_unit members and replacing them with
62 if_xname, if_dname, and if_dunit. All network drivers and most
63 userland programs which include net/if_var.h must be updated
64 and recompiled. __FreeBSD_version has been bumped to 501113 to
68 Changes to the cdevsw default functions have been made to remove
69 the need to specify nullopen() and nullclose() explicitly.
70 __FreeBSD_version bumpted to 501110.
73 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
74 mount_cd9660(8) need to be in sync with kernel.
77 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
78 also be explicitly configured. Previously this dependency was
79 magically handled through some cruft in net/pfil.h; but that has
80 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
81 will fail with obtuse errors in ip_fil.c.
84 Fix a bug in arplookup(), whereby a hostile party on a locally
85 attached network could exhaust kernel memory, and cause a system
86 panic, by sending a flood of spoofed ARP requests. See
90 A change to /etc/defaults/rc.conf now causes inetd to be started
91 with `-C 60' if it is not overridden in /etc/rc.conf. This
92 causes inetd to stop accepting connections from an IP address
93 that exceeds the rate of 60 connections per minute.
96 The following rc.d scripts have been removed and should be
97 deleted from your installation: atm2.sh atm3.sh devdb
98 localdaemons network1 network2 network3. Depending on when
99 you last updated world and used mergemaster(8) you may or
100 may not have problems during the rc boot sequence. The simplest
101 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
102 The atm2.sh atm3.sh and devdb scripts were removed some time
103 ago, so depending on when you installed -CURRENT these scripts
104 may or may not exist on your system.
107 ATAng has been committed. You need to build world as sys/ata.h
108 has changed, and userland atacontrol depends on it.
109 If you use ATA SW raids you need "device ataraid" in your
110 kernel config file, as it is no longer pulled in automatically.
113 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
114 Among other things, this changes the device enumeration to be
115 closer to Solaris. Be aware that, this can even cause the machine
116 to not boot without manual intervention before the fstab is adjusted.
119 All current USB and Firewire quirks in da(4) have been deprecated
120 and will be removed for 5.2. If this causes failure for your
121 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
122 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
123 so the quirk can be re-enabled.
126 FPU-less support has been removed from FreeBSD. Chances are you won't
127 notice. 386+387 support should still work after this change, but
128 it is now a minimum requirement for the i386 port that you have real
132 Some people are having problems with changes related to /rescue.
133 If you are building -j N, you will need to define NO_RESCUE. Others
134 will need to define it if /rescue has issues with their environment.
135 People should report those issues to current@.
138 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
139 across this point. Further, it might be a good idea to remove
142 20030613: [retrospective]
143 There was a small window in which sed(1) was broken. If you
144 happen to have sed(1) installed during that window, which is
145 evidenced by an inability to build world with the failure
146 given below, you need to manually build and install sed(1)
147 (and only sed(1)) before doing anything else. This is a one-
148 time snafu. Typical failure mode:
150 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
151 targmatch.h:7:1: null character(s) ignored
152 targmatch.h:12:1: null character(s) ignored
153 targmatch.h:16:1: null character(s) ignored
156 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
157 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
158 usr.bin/sed/process.c).
161 Remove deprecated locale names and transition period code
162 for them, finishing switching to the new scheme. Check your
163 LANG environment variable.
166 CCD has been changed to be a fully GEOMified class. Kernel
167 and ccdconfig(8) needs to be in sync, this is particularly
168 important to remember beforehand if your source tree is on
169 a ccd device. Consider making a copy of the old ccdconfig
170 into /boot/kernel.good or wherever you keep your backup
174 Kerberos 5 (Heimdal) is now built by default. Setting
175 MAKE_KERBEROS5 no longer has any effect. If you do NOT
176 want the "base" Kerberos 5, you need to set NO_KERBEROS.
179 groff has been updated. If you try to do a buildworld and
180 get an infinite loop in troff, update to May 4th or newer. If you
181 have a newer kernel than userland, you may need to set the OSRELDATE
182 to 500110 in your environment before starting a buildworld.
185 The old rc system has been removed. Please report any problems
186 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
187 Your personal versions of these files will not be removed, so you can
188 continue to use them. However, you should take great care when updating,
189 especially when using mergemaster, since the compatibility code that
190 utilizes these old scripts has also been removed.
193 A bug has been fixed in /dev/devctl which would cause devd
194 to hang on boot, were it not for a workaround in devd. The
195 work around in devd will be removed around 20030507. You
196 have until then to upgrade your kernel before updating
197 userland. In general, you should have a userland and
198 kernel that's in sync with each other. However, given the
199 effects of this bug (hang on boot when starting devd), some
203 Alphas with libc from between 20030312 and 20030329 exhibit
204 floating point exceptions (FPEs), most notably in awk(1)
205 while upgrading the system through a buildworld.
207 So, to successfully upgrade your Alpha, you must either
208 downgrade your libc.so to a pre-20030312 version, or update
209 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
210 to CFLAGS, then forcibly rebuild and install libc:
212 cd /usr/src/lib/libc && \
213 make cleandir && make obj && \
214 make -DNOMAN -DNOPROFILE all && \
215 make -DNOMAN -DNOPROFILE install
218 sendmail 8.12.7 has been imported. It has one important
219 change for IPv6 users. The default submit.mc now uses
220 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
221 used to connect to the MTA. Users on IPv6-only machines
222 will need to edit /etc/mail/submit.mc appropriately.
225 NODEVFS option has been removed and DEVFS thereby made standard.
226 This makes all references to MAKEDEV obsolete, and they should
227 be removed when convenient.
230 The name of the device for the ofw console has changed, sparc64 users
231 must run mergemaster to update their installed /etc/ttys.
234 The scheduler framework has grown a second scheduler and consequently
235 you must specify one and only one scheduler in your kernel config.
236 The cvs config files have been updated to use the old scheduler
237 which may be selected via 'options SCHED_4BSD'. If you would like
238 to try the new, much more experimental, scheduler please try
239 'options SCHED_ULE' and contribute to the arch@ discussion.
242 A new version of the wi driver has been imported into the tree.
243 One now must have device wlan in the config file for it to operate
246 In addition, there have been some changes to how wi devices are
247 configured for point to point links to bring it more in line
248 with the former way of doing things, as well as compatibility
252 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
253 used an incompatible form of ABI for returning structures and unions
254 which FreeBSD's GCC maintainers were not aware of relative to previous
255 versions of FreeBSD. We have gone back to the ABI for now, and any
256 code compiled which is required to interoperate with other code (not
257 built at the same time) returning structs or unions should be
261 A name change in /etc/netconfig has been reverted to stay
262 compatible with suns TIRPC and also with NetBSD. You need
263 to run mergemaster after make world. A new libc does still work
264 with an outdated /etc/netconfig for some time, but you'll get
265 a warning. This warning will be removed in 20030301.
268 The recent binutils upgrade marks a kernel flag day on
269 sparc64: modules built with the old binutils will not work
270 with new kernels and vice versa. Mismatches will result in
271 panics. Make sure your kernel and modules are in sync.
274 The value of IPPROTO_DIVERT has changed. Make sure to keep
275 your kernel, netstat, natd and any third-party DIVERT
279 Old, compatibility slices have been removed in GEOM kernels.
280 This means that you will have to update your /etc/fstab to
281 not use disk devices of the form /dev/ad0a. Instead, you
282 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
283 partition really is on. The old device names have gone
284 away, so if you use them anywhere else, you must also adjust
285 those uses. (This doesn't affect the disks formatted in
286 the ``dangerously-dedicated'' mode.)
289 Alphas with kernels from between 20020830 and 20021023 and/or
290 rtld (ld-elf.so.1) older than 20021023 may experience problems
291 with groff while doing a buildworld (kernel: "out of memory",
292 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
293 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
295 So, to successfully upgrade your Alpha, you must either
296 upgrade your kernel and rtld first (which might be a bit
297 tricky), or avoid running the bootstrapped groff during the
298 "transitional" buildworld. To avoid running groff during the
299 transitional upgrade run make buildworld with -DNOMAN,
300 -DNO_SHAREDOCS, and -DNO_LPR.
303 gcc has been upgraded to 3.2. It is not all binary compatible
304 with earlier versions of gcc for c++ programs. All c++
305 programs and libraries need to be recompiled.
307 Also, if you encounter g++ issues, rm /usr/include/g++/* before
308 doing an installworld to make sure that stale files are removed.
311 Our /etc/termcap now has all the entries from the XFree86 xterm
312 almost unchanged. This means xterm now supports color by default.
313 If you used TERM=xterm-color in the past you now should use
314 TERM=xterm. (xterm-color will lead to benign warnings).
317 A "bug" in gcc(1) that was hiding warning in system headers was
318 fixed. It's probably time to add -DNO_WERROR to your make line
322 COPY is being deprecated. The 20010530 change was reverted, as
323 it causes far more pain than was expected, and to always compare
324 before installing, please use INSTALL="install -C" again. The
325 -C option is now silently ignored when used with the -d option.
328 Problems with libc_r clients like KDE and GNOME have been resolved.
329 There are still some minor problems with some signals but the
330 system is stable enough for general use again. SMP is less so than UP
331 but each can successfully complete multiple buildworlds.
332 Libkvm needs to be recompiled due to KSE.
335 Now would be a bad time to upgrade. Something in or near the
336 KSE commit totally broke programs using libc_r like KDE and
340 The k5su utility installed as part of Kerberos 5 is no longer
341 installed with the set-user-ID bit set by default. Add
342 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
343 with the set-user-ID bit set.
346 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
347 Unfortunately our native GDB (at version 4.18) does not understand
348 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
349 generated debugging information for our native GDB.
352 Due to the way CVS works, it may not properly update src/contrib/gcc
353 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
354 and then do a cvs update.
357 When exec'ing set[ug]id executables, the kernel now ensures that the
358 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
361 New sendmail startup scripts have been installed to make it
362 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
363 variable sendmail_enable to "NO" no longer prevents any sendmail
364 daemons from starting. Instead, either set sendmail_enable to
365 "NONE" or change mta_start_script to a script for starting
366 an alternative MTA. Setting mta_start_script to "" will
367 also prevent any MTA from being started at boot.
370 UCONSOLE is no longer a valid kernel option.
373 FreeBSD 5.0 DP-1 was basically branched today.
376 Warnings are now errors in the kernel. Unless you are a developer,
377 you should add -DNO_WERROR to your make line.
380 sendmail 8.12.2 has been imported. The sendmail binary is no
381 longer a set-user-ID root binary and the infrastructure to support
382 command line mail submission has changed. Be sure to run
383 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
384 and /etc/mail) and read /etc/mail/README for more details.
386 Due to the import of sendmail 8.12.2, a new user and group are
387 required in order for sendmail to run as a set-group-ID
388 binary. A 'make installworld' will use the new user and group
389 to set the owner and group of /var/spool/clientmqueue and will
390 fail if the new user and group do not exist. The 'smmsp' user
391 and group must be merged from src/etc/group and
392 src/etc/master.passwd before using 'make installworld'.
393 'mergemaster -p' will do this. You may need to install
394 mergemaster before this will work if you are updating from a
395 very old version of current. The updating recipe has changed
399 The preferred configuration method for PAM is now /etc/pam.d/
400 rather than /etc/pam.conf. If you have an unmodified
401 pam.conf, just delete it after your next mergemaster run. If
402 you have local modifications, you can use
403 /usr/src/etc/pam.d/convert.pl to incorporate them into your
406 Please see the following url for more details:
407 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
409 If anyone here is already using the new rc.conf(5) variable
410 networkfs_types, please note that it has changed
411 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
414 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
415 started out its life in the ISDN4BSD project as an offspring
416 from sys/net/if_spppsubr.c, which eventually got a life of its
417 own. All the accumulated features and bugfixes of the i4b
418 version have now been merged back into the base system's
419 version now. The only user-visible change resulting from this
420 is that i4b's sppp(4) interfaces are to be managed with
421 spppcontrol(8) again, since ispppcontrol(8) has been retired
422 as well. (There has never been rc file support for
423 ispppcontrol in -current, but only in -stable. That will be
424 reverted by the time the changes are MFCed.)
427 The fdc(4) driver has been updated and now automatically
428 recognizes media in `standard' formats (like 1440 KB and
429 720 KB for a 3.5" high-density drive) when accessing the
430 default device node (e. g. /dev/fd0). The old variety of
431 floppy device nodes /dev/fd*.* is no longer present by
432 default, devices can be created (in DEVFS) on demand. They
433 will need to be customized then for `odd' densities using
437 The bugs in procfs' debugging support code have been fixed,
438 and truss(1) now works again.
441 Daily security checks have been split out to use the periodic(8)
442 scripts. Some change in configuration may be necessary. Please
444 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
448 sos added VCD/SVCD support to ata driver and that needs the
449 kernel and burncd to be in sync.
452 The procfs pseudo-filesystem has now been converted to use the
453 pseudofs framework. If you have 'options PROCFS' in your
454 kernel config, you'll need to add 'options PSEUDOFS' if it's
457 This change temporarily breaks truss(1); use ktrace(1) instead
458 until the issue has been resolved.
461 A security hole in OpenSSH involving `UseLogin yes' has been
465 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
466 after this date. You need to do this only once.
469 Most of the awk issues have been resolved. Some rough
470 edges may be left, but for the most part things should be
471 back to "normal." For CURRENT's usual definition of "normal."
474 Awk has been upgraded to the one true awk from bell labs. Expect
475 choppy waves in the upgrade process.
478 The asr driver problem has been resolved.
481 Due to changes in other parts of the system, the asr driver
482 now causes the system to panic on boot. Do not use it pending
483 correction. Comment it out of any kernel config file that you
484 try to use from this date forward.
487 When crossbuilding, use TARGET=xxx where you used to use
488 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
489 unless you are changing both of them. To cross build pc98 on
490 an alpha, for example, you need to set TARGET=pc98 and
494 The kernel interface that burncd depends on has changed.
495 You must recompile both the kernel and userland applications
499 When crossbuilding, please set TARGET_ARCH rather than
500 MACHINE_ARCH to indicate the target. In the future, one will
501 set TARGET_MACHINE where you set MACHINE now. At the moment,
502 setting MACHINE alone for same MACHINE_ARCH machines works
503 (eg, you can build pc98 on an i386 machine and vice versa).
506 Some weird problems result from using ACPI on some machines.
507 To disable ACPI you can add
508 hint.acpi.0.disabled="1"
509 to /boot/loader.conf (or by putting set X=Y at the boot
512 Alternatively, you can remove it from /boot/kernel/acpi.ko
513 or use the MODULES_OVERRIDE function in your kernel config
514 file and not list acpi in that list.
517 The buildworld has been fixed. You may need to install
518 the 4.x compatibility libraries for some old binaries
519 to work. Add COMPAT4X=true to your /etc/make.conf to
520 get them installed on every installworld, or execute the
521 following to get them installed only once:
522 cd src/lib/compat/compat4x.<arch>
524 You will see ``__stdoutp undefined'' until you do this.
527 There's a bug in the world build process. The cross-tools
528 are build with the NEW headers, but the OLD libc.a. This
529 leads to all kinds of problems with the new libc. A temporary
531 CFLAGS="-O -pipe -D_OLD_STDIO"
532 before building world when upgrading from 4.x to current. This
533 can be removed afterwards.
535 A proper fix to the buildworld target is needed.
538 Peter has committed his new kthread nfs client/server code.
539 NFS may be unstable after this date.
542 KSE has hit the tree. Lots of things are now different in
543 the kernel. While a few problems were introduced in the
544 initial commit, most of the major ones have been found and
548 In OLDCARD, CardBus bridges appear to be stable. The work
549 arounds described in the 20010604 entry are now no longer
550 necessary and will be ignored. Most insert/remove problems
551 have been rectified around this date.
554 named now runs as user bind and group bind rather than as
555 root. If named_enable is set to YES in /etc/rc.conf, ensure
556 that user bind is available in /etc/passwd (using vipw(8))
557 and that group bind is available in /etc/group. Also make
558 sure that user or group bind has read (and not write)
559 permission for your name server configuration and that it
560 has read and write permission for your slave zone files and
563 If you wish to continue to run named as root (a less secure
564 alternative), add a line to /etc/rc.conf saying
569 The PAM libraries have had an API upgrade that is beyond
570 the ability of the shared library major number to handle.
571 It is manifested by PAM-using ports dumping core. The
572 solution is to rebuild those ports.
575 The kernel compile module has moved from src/sys/compile/FOO
576 to src/sys/${MACHINE}/compile/FOO.
579 The pccard modem issue from 20010613 has been corrected.
580 OLDCARD support is still a little weak in -current. slot 1 is
581 known not to work on some TI based cardbus bridges. Some
582 cardbus bridges do not properly detect insert/removal events.
583 IRQ configuration needs more safety belts.
586 Softupdates problems have been corrected.
589 Peter ripped out the linkerset support. You must, as always,
590 rerun config after you cvsup if you are using the traditional
591 kernel building methods.
594 pccard modems may not work with current after 20010604 date. Some
595 do, others result in panics. *MAKE*SURE* that you update your
596 config and /etc/rc.conf ala the 20010604 entry, or you will have
597 problems (this issue will be fixed, it just hasn't been yet).
600 SOFTUPDATES seem to be broken since the middle of May or so. Do not
601 use them in current. You can disable softupdates on all mounted
602 partitions, or remove SOFTUPDATES the kernel config file.
605 After Peter's commits to the hints code, people have been noticing
606 that certain devices are attached (or try to) twice. This is due
607 to having both static hints as well as a /boot/device.hints. To
608 work around this issue, please use only one or the other mechanism
609 until this bug is fixed.
611 Please note that a feature of config is that if you have config
612 file FOO and FOO.hints, it automatically adds FOO.hints to the
613 hints.c file, whether you want it to or not.
616 Locale names have changed to match other systems better.
619 pccard support for pci cards has been committed. You must change
620 your /etc/pccard.conf irq lines. It must match the irq used by
621 pcic device. Interrupt storms may result if you fail to do this.
622 Interrupt storms look a lot like a hang.
624 You must also install a new pccardd, otherwise you will get an
625 interrupt storm at card reset time (just after it tells you what
628 pccardd_flags="-I" is necessary for the time being. It tells pccardd
629 not to ask the kernel if the interrupt is really free or not before
630 using it. You can either change the /etc/pccard.conf irq lines to
631 match pcic, or add "-i X" to the pccardd_flags.
634 INSTALL=install -C is being deprecated. If you want to do this,
635 use COPY=-C instead. The former method will be supported for only
636 a limited time. If you see
638 install: warning: the -d and -C options may not be specified together
640 in your makeworld, then you need to migrate towards using
644 It appears that vm is now stable enough to use again. However,
645 there may be other problems, so caution is still urged. alpha
646 definitely is in bad shape.
649 Minor repo damage has happened. This may cause problems
650 with cvsup of ports. If you get errors, please see
651 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
652 at the bottom for details on a workaround. The error message
654 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
657 Vm and/or swapping are busted on -current. Please be patient.
660 pccard has had much reorganizational work done to it over
661 the past few days. Everything should still work, but if
662 not, please contact imp@freebsd.org.
665 ata ioctl changed. Make sure to recompile both kernel and
666 userland at the same time.
669 New ncurses imported.
672 DEVFS is now opt out, not opt in. Barring major problems, this
673 will be the only way to go starting July 1.
676 OpenSSH has been updated to 2.9. Some defaults are different,
677 including RhostsRSAAuthentication, which changes from yes to no.
680 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
683 Building perl was broken at 02:25:25 PDT.
686 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
687 go back in the water.
690 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
691 this date, but before the correction date.
694 old fsck and new kernel interactions appear to have been fixed.
697 fsck and the kernel were changed to handle some optimizations
698 to directory layout. This breaks backward compatibility.
699 Update only if you understand that you must not use the old
700 fsck with the new kernel ever.
703 fsck has changed the meaning of the pass column in /etc/fstab.
704 Please see the cvs commit to fsck.8 or the fsck.8 man page for
705 details. It is unclear if changes to /etc/fstab are necessary.
708 portmap had changed name to rpcbind for maximum POLA in your
709 current world. /etc/hosts.{allow,deny} needs changes. nfs and
710 other rpc based programs that rely on portmapper will not work
711 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
714 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
715 and ATA_ENABLE_TAGS are no longer kernel options. They have
716 been replaced by tunables. See ata.4 for details.
719 The fxp driver was converted to use miibus. If you compile
720 fxp into your kernel statically, you will need to add miibus.
723 The wi device now defaults to BSS (infrastructure) mode
727 /dev/urandom should be a symbolic link to /dev/random now.
728 Users of current not using DEVFS need to run MAKEDEV std.
729 ssh might not work if you don't.
732 The ed driver has been updated. It now allows mii attachments,
733 which means that you must include the miibus in your kernel if
734 you use the ed driver.
737 The problems with libc have been corrected. It is now mostly
738 safe to go back into the water.
741 The size of FILE was changed. This breaks upgrading. If
742 you must upgrade, be prepared for pain. It also breaks almost
743 all binaries that you've compiled on -current. You are warned
744 that before upgrading would be a good time to do a level 0
745 dump of your system. No, really, I mean it this time.
747 To get to the new system, you'll need to use the following
748 workaround. Hopefully this can be sorted out so that we
749 don't have to move this to the updating section.
751 To get around the installworld problem, do:
752 # cd /usr/src/usr.bin/sed
756 If that doesn't work, then try:
757 # make -k installworld
761 DEVFS is now the default. If you use vinum, make sure that you
762 do not include devfs in your kernel as problems result.
765 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
766 Remove them from your config.
769 ****************************** WARNING ******************************
770 buildkernel has been changed slightly
771 ****************************** WARNING ******************************
772 KERNCONF replaces the variable KERNEL for buildkernel. You
773 should update your scripts and make.conf accordingly.
776 config has changed to allow DEV_FOO as a replacement for NFOO.
777 This requires a new config to build correctly.
780 The kernel option I386_CPU is now mutually exclusive with the
781 other cpu types. If you have an i386 system, be sure that it
782 only had this line. Remove it for all other configurations.
785 Changes to the kernel require it and burncd be in sync.
788 Everyone who has hw.sndunit set to something in
789 /etc/sysctl.conf, it is now hw.snd.unit.
792 ex and vi were broken by some changes to sys/queue.h. If you
793 have a bad vi, you will see make buildworld fail with a core
794 dump while building termcap. You can work around this problem
795 by adding -k to your make buildworld. This will cause the
796 build to complete and install a new vi. Once that's done, you
797 can rebuild again without the -k to pick up anything that
798 might have been ignored by the -k option.
800 Others have suggested that you can just rebuild libc if your
801 vi/ex is dynamically linked, but I've not received any reports
805 There have been some changes to libcrypt in -current. The
806 libscrypt/libdescrypt symlink silliness is gone and the installed
807 libcrypt is fully functional. Be aware of this.
810 Linksys Fast Ethernet PCCARD cards supported by the ed driver
811 now require the addition of flag 0x80000 to their config line
812 in pccard.conf(5). This flag is not optional. These Linksys
813 cards will not be recognized without it.
816 Important new FreeBSD-version stuff: PAM support has been worked
817 in, partially from the "Unix" OpenSSH version. This requires
818 adding the following in pam.conf:
820 sshd auth sufficient pam_skey.so
821 sshd auth required pam_unix.so try_first_pass
822 sshd session required pam_permit.so
828 The random device needs more entropy, so you need to make sure
829 that you've run mergemaster to get a /etc/rc which will seed
830 /dev/random. If you don't and the system hangs after ldconfig,
831 then banging on the keyboard randomly until it unhangs is one
835 ****************************** WARNING ******************************
836 Sendmail has been updated.
837 ****************************** WARNING ******************************
838 o mail.local(8) is no longer installed as a set-user-id binary.
839 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
841 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
843 o Now using sendmail's version of vacation(1).
844 o The sendmail cf building tools (contrib/sendmail/cf) are installed
845 in /usr/share/sendmail/cf.
846 o sendmail.cw changed to local-host-names
848 More details can be found at
849 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
852 The ports tree's new layout is in place. Be sure to update
853 your entire ports tree, or you will have problems.
856 The perl build procedure no longer installs miniperl, nor uses
857 the installed miniperl. It is recommended that you delete
861 This weekend the ports tree will be updated to a new layout.
862 It will be in an inconsistent state until noted in the UPDATING
863 file, or with asami-san's message to the relevant mailing
864 lists. With this new layout, you'll need to update the whole
865 tree for anything to work.
868 There was a change in the passwd format. Need more information.
871 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
872 place. Please update boot loader (not the boot blocks) at the
873 same time as your kernel.
876 The new pmtimer device is necessary for laptops. Failure to
877 include the device will cause suspended laptops losing time
878 when they resume. Include
880 in your config file and
881 hint.pmtimer.0.at="isa"
882 to your /boot/device.hints file.
885 The random device has been turned into a (pseudo-)device,
886 rather than an option. The supplied kernel config files have
887 been updated. You will need to do something similar in your
888 own kernel config file.
893 If you prefer to load the loadable module, you need to do
897 The random device module has been renamed from randomdev.ko to
898 random.ko. You will need to edit your /boot/loader.conf to
899 reflect this if you load this module at boot time.
900 The line should read:
904 The SMPNG commit has happened. It should work, but if it
905 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
906 to be a variety of minor issues. Please see 20000905 to make
907 sure you don't have model loading problems which might at
908 first blush appear related to SMP.
911 nsswitch has been imported from NetBSD. Among other things,
912 this means that /etc/host.conf is no longer used. See
913 nsswitch.conf(5) instead. Note that at boot time rc.network
914 will attempt to produce a new nsswitch.conf file for you if you
915 don't have one, and you have host.conf.
918 The ucred structure changed size. This breaks the interface
919 that mountd uses. Trying to use an older mountd with a newer
920 kernel guarantees a panic. This means that you need to use
921 kernels newer than today only with matching mountd, but you
922 needed to do that anyway with the boot loader changes.
925 The boot loader has been updated. The new default kernel is
926 now /boot/kernel/kernel.ko. The new default module location
929 You *MUST* upgrade your boot loader and kernel at the same time.
930 The easiest way to do this is to do the buildworld/buildkernel/
931 installkernel/installworld dance.
933 Furthermore, you are urged to delete your old /modules directory
934 before booting the new kernel, since kldload will find stale
935 modules in that directory instead of finding them in the correct
936 path, /boot/kernel. The most common complaint that this cures
937 is that the linux module crashes your machine after the update.
939 if [ ! -d /boot/kernel.old ]; then
940 mv /modules.old /boot/kernel.old
941 chflags noschg /kernel.old
942 mv /kernel.old /boot/kernel.old/kernel.ko
943 chflags schg /boot/kernel.old/kernel.ko
947 A new issue with the sendmail upgrade has come to light.
948 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
949 incorrectly install the default aliases in /etc/mail rather than
950 move the old one from /etc. So you'll need to manually move the
951 file, create a symbolic link, remove the old /etc/aliases.db and
952 run newaliases. For safety sake, you should stop sendmail
953 while doing this and run the upgrade when locally sourced email
954 is not likely to be generated.
957 /boot/device.hints is now required for installkernel to
958 succeed. You should copy GENERIC.hints for your architecture
959 into /boot/device.hints. If and only if you compile hints
960 into your kernel, then this file may be empty. Please note,
961 if you have an empty or missing /boot/device.hints file and
962 you neglected to compile hints into your kernel, no boot
963 messages will appear after the boot loader tries to start the
967 If you do NOT have ``options RANDOMDEV'' in your kernel and
968 you DO want the random device then add randomdev_load="YES" to
972 suidperl is now always built and installed on the system, but
973 with permissions of 511. If you have applications that use
974 this program, you are now required to add ENABLE_SUIDPERL=true
975 to /etc/make.conf. If you forget to do this,
976 chmod 4511 /usr/bin/suidperl
977 will fix this until the next build.
980 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
981 visible changes that may immediately affect your configuration
983 - New default file locations from src/contrib/sendmail/cf/README
984 - newaliases limited to root and trusted users
985 - MSA port (587) turned on by default
986 - New queue file naming system so can't go from 8.11 -> 8.9
987 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
988 - FEATURE(`nullclient') is more full featured
989 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
990 - mail.local FreeBSD-only -b option changed to -B
991 - See src/contrib/sendmail/RELEASE_NOTES for more info
994 suidperl (aka sperl) is no longer build by default. You must
995 specifically define BUILD_SUIDPERL to "true" for it to be build.
996 Furthermore, we recommend that you remove /usr/bin/sperl* and
997 /usr/bin/suidperl files from your system unless you have a
1001 Networking defaults have been tightened. Anybody upgrading
1002 /etc/defaults/rc.conf needs to add the following lines to
1003 /etc/rc.conf if they want to have the same setup
1004 afterwards (unless the variables already are set, of course):
1005 # Enable network daemons for user convenience.
1007 portmap_enable="YES"
1008 sendmail_enable="YES"
1011 If you have null_load="YES" in your /boot/loader.conf, you
1012 will need to change that to nullfs_load="YES".
1015 The "installkernel" target has changed slightly. Now even if
1016 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1017 it will install the MYKERNEL file (built with the buildkernel
1018 target) as /kernel rather than /MYKERNEL. Those who have
1019 updated their /boot/loader.conf files to point to /MYKERNEL
1020 should remove that entry or perform manual rename of /kernel
1024 If you use CVSUP or CTM to get CVS trees, AND you used to get
1025 the old crypto files from internat.freebsd.org AND you check
1026 out files from the CVS tree with the cvs command, please read
1027 http://people.freebsd.org/~imp/internat.txt
1028 for details on potential problems that you might have and how
1031 If you are merely a mirror, or don't answer yes to each of the
1032 clauses above, you needn't worry.
1035 /etc/security has been updated to print the inode number of
1036 setuid programs that have changed. You will see a large spike
1037 in the number of changed programs the first time when you run
1038 mergemaster to get a new /etc/security.
1041 /dev/random now has good entropy collection (from the keyboard
1042 and sysmouse drivers). Please ensure that either `options
1043 RANDOMDEV' is present in your kernel config file or that
1044 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1045 not have the /dev/random driver, OpenSSL (and consequently
1046 lots of crypto tools (like SSH)) will fail with strange
1047 errors. (see below, 20000624).
1049 FreeBSD-current is safe again to run Crypto.
1052 phk made the malloc default options AJ. This may slow things
1053 down and uncover other latent bugs in the code. If you need to
1054 run at full speed, you can disable this by doing the following:
1055 ln -s aj /etc/malloc.conf
1058 libftpio's version was accidentally bumped a few days ago. This
1059 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1060 before doing your next buildworld/installworld pair. It certainly
1061 won't hurt to remove it before the update procedure. It will
1062 break fetch until a new one is built, but ftp can be used in the
1066 The crypto packages have changed for the cvsup. This has been done
1067 in a backward compatible way, but the old packages will go away at
1068 some point in the future. Look at /usr/share/examples/cvsup for
1072 With the new sys/modules/sound/drivers/*, you will need to
1073 set SYSDIR until you do an installworld after July 7th.
1076 rc.shutdown and rc will now call the rc.d scripts with start
1077 or stop. This may cause some harmless warnings from older
1078 rc.d scripts that haven't been updated.
1081 The libfetch based version of fetch has gone into the tree.
1082 Minor problems may result on some of the less popular sites,
1083 which should be reported to des@freebsd.org.
1086 From approximately this date forward, one must have the crypto
1087 system installed in order to build the system and kernel.
1088 While not technically strictly true, one should treat it as
1089 required and grab the crypto bits. If you are grabbing CVS
1090 trees, src-all and cvs-crypto should be treated as if they
1091 were required. You should check with the latest collections
1092 to make sure that these haven't changed.
1095 Mark Murray just committed the first parts of a cleanup of
1096 /dev/zero, et al. This is also cleaning up /dev/random.
1097 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1098 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1099 until Mark can merge in the fixes to this work in progress.
1100 openssh and openssl should not be used to generate keys from this
1101 date to the completion of the work.
1103 If you must operate at this reduced level of security, add '
1104 options RANDOMDEV' to your kernel or modload the randomdev
1105 module. You may also need to copy a new MAKEDEV to /dev and
1106 recreate the random and urandom devices.
1109 The license on the softupdates is now a standard 2 clause
1110 BSD license. You may need to remove your symbolic links
1111 that used to be required when updating.
1114 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1115 the config file update procedure.
1116 http://people.freebsd.org/~imp/config-upd.html
1117 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1118 isn't buildable. However, you can generate a LINT file:
1119 cd /sys/<ARCH>/conf && make LINT
1122 Binutils 2.10 have hit the tree, or will shortly. As soon
1123 as they do, the problem noted in 20000522 will be resolved and
1124 that workaround will no longer be required.
1127 phk removed the compatibility creation of wd devices in the
1128 ad driver. If you haven't done so already, you must update
1129 your fstab, etc to use the ad devices instead of the wd
1132 In addition, you'll need to update your boot blocks to a
1133 more modern version, if you haven't already done so. Modern
1134 here means 4.0 release or newer (although older releases
1138 Peter took an axe to config(8). Be sure that you read his mail
1139 on the topic before even thinking about updating. You will
1140 need to create a /boot/device.hints or add a hints directive
1141 to your config file to compile them in statically. The format
1142 of the config file has changed as well. Please see GENERIC or
1143 NEWCARD for examples of the new format.
1145 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1146 says that it has been fixed, assume that must use the hints mechanism
1147 in the loader if you need to use a machine with very old ISA cards
1151 A new set of binutils went into the tree today. Anybody
1152 building a kernel after this point is advised that they need
1153 to rebuild their binutils (or better yet do a
1154 buildworld/installworld) before building a new kernel.
1156 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1157 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1158 is recommended that you don't set this option until the problem
1162 The ethernet drivers were all updated to clean up the BPF handling.
1165 The problems with boot blocks on the alphas have been corrected.
1166 This will require some care in updating alphas. A new libstand
1167 is requires for the boot blocks to build properly.
1170 Recompile all kld modules. Proper version dependency info
1174 Modules have been disconnected from the buildworld tree and
1175 connected to the kernel building instead.
1178 You may need to build gperf
1179 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1180 when upgrading from 4.0 -> current. The build system now uses
1181 an option only in -current.
1184 The method that we brand ELF binaries has changed to be more
1185 acceptable to the binutils maintainers. You will need to
1186 rebrand your ELF binaries that aren't native. One problem
1187 binary is the Linux ldconfig. After your make world, but
1188 before you reboot, you'll need to issue:
1189 brandelf -t Linux /compat/linux/sbin/ldconfig
1190 if you have Linux compatibility enabled on your machine.
1193 If you have really bad/marginal IDE drives, you may find they
1194 don't work well. Use pio mode instead. The easiest way to
1195 cope if you have a problem combination is to add:
1196 /sbin/sysctl hw.ata.ata_dma=0
1197 to the start of /etc/rc.conf.
1200 The ISA and PCI compatibility shims have been connected to the
1201 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1202 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1203 include the appropriate option in your kernel config. Drivers
1204 using the shims should be updated or they won't ship with
1205 5.0-RELEASE, targeted for 2001.
1208 We've entered the traditional post release dumping party.
1209 Large kernel changes are being committed and are in the
1210 works. It is important to keep the systems' klds and kernel
1211 in sync as kernel interfaces and structures are changing.
1212 Before reporting kernel panics, make sure that all modules
1213 that you are loading are up to date.
1216 If you are upgrading from an older version of FreeBSD, you
1217 need to update your boot blocks as well. 'disklabel -B ad0'
1218 will do the trick. This isn't critical until you remove your
1219 wd device entries in /dev, at which point your system will not
1223 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1224 to upgrade to 4.0 from 3.x.
1230 Avoid using make -j when upgrading. From time to time in the
1231 past there have been problems using -j with buildworld and/or
1232 installworld. This is especially true when upgrading between
1233 "distant" versions (eg one that cross a major release boundary
1234 or several minor releases, or when several months have passed
1235 on the -current branch).
1237 Sometimes, obscure build problems are the result of environment
1238 poisoning. This can happen because the make utility reads its
1239 environment when searching for values for global variables.
1240 To run your build attempts in an "environmental clean room",
1241 prefix all make commands with 'env -i '. See the env(1) manual
1242 page for more details.
1246 If you are updating from a prior version of FreeBSD (even one just
1247 a few days old), you should follow this procedure. With a
1248 /usr/obj tree with a fresh buildworld,
1249 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1250 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1252 To just build a kernel when you know that it won't mess you up
1253 --------------------------------------------------------------
1254 cd src/sys/{i386,alpha}/conf
1255 config KERNEL_NAME_HERE
1256 cd ../../compile/KERNEL_NAME_HERE
1261 If this fails, go to the "To build a kernel" section.
1263 To rebuild everything and install it on the current system.
1264 -----------------------------------------------------------
1265 # Note: sometimes if you are running current you gotta do more than
1266 # is listed here if you are upgrading from a really old current.
1268 <make sure you have good level 0 dumps>
1269 <maybe fix /etc/fstab> [7]
1271 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1272 make installkernel KERNCONF=YOUR_KERNEL_HERE
1274 <reboot in single user> [3]
1281 To cross-install current onto a separate partition
1282 --------------------------------------------------
1283 # In this approach we use a separate partition to hold
1284 # current's root, 'usr', and 'var' directories. A partition
1285 # holding "/", "/usr" and "/var" should be about 2GB in
1288 <make sure you have good level 0 dumps>
1291 <maybe newfs current's root partition>
1292 <mount current's root partition on directory ${CURRENT_ROOT}>
1293 make installworld DESTDIR=${CURRENT_ROOT}
1294 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1295 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1296 ${CURRENT_ROOT}/boot/device.hints # as needed
1297 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1298 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1299 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1300 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1301 <reboot into current>
1302 <do a "native" rebuild/install as described in the previous section>
1303 <maybe install compatibility libraries from /usr/src/lib/compat>
1307 To upgrade in-place from 4.x-stable to current
1308 ----------------------------------------------
1309 # 5.x uses more space than 4.x. Also, the location of kernel
1310 # modules has changed. If you are installing 5.0 onto a 4.x
1311 # system, you'll need about 30MB of free disk space on your /
1312 # partition. If you have less than this, you may encounter difficult
1313 # to back out of problems with this procedure. If /tmp is on
1314 # the / partition, you may want to completely remove all its content
1315 # before upgrading, as this can be a common source of shortage of
1318 <make sure you have good level 0 dumps>
1319 <maybe fix /etc/fstab> [7]
1321 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1322 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1323 make installkernel KERNCONF=YOUR_KERNEL_HERE
1324 cd src/sys/boot ; make install [6]
1326 <reboot in single user> [3]
1328 rm -rf /usr/include/g++
1333 Make sure that you've read the UPDATING file to understand the
1334 tweaks to various things you need. At this point in the life
1335 cycle of current, things change often and you are on your own
1336 to cope. The defaults can also change, so please read ALL of
1337 the UPDATING entries.
1339 Also, if you are tracking -current, you must be subscribed to
1340 freebsd-current@freebsd.org. Make sure that before you update
1341 your sources that you have read and understood all the recent
1342 messages there. If in doubt, please track -stable which has
1343 much fewer pitfalls.
1345 [1] If you have third party modules, such as vmware, you
1346 should disable them at this point so they don't crash your
1349 [2] If you have legacy ISA devices, you may need to create
1350 your own device.hints to reflect your unique hardware
1353 [3] From the bootblocks, boot -s, and then do
1358 adjkerntz -i # if CMOS is wall time
1359 Also, when doing a major release upgrade, it is required that
1360 you boot into single user mode to do the installworld.
1361 For the 4.x -> 5.0 upgrade, you will also see many messages about
1362 needing to recompile your userland. These are harmless and can
1363 be ignored while you proceed to the next step.
1365 [4] Note: This step is non-optional. Failure to do this step
1366 can result in a significant reduction in the functionality of the
1367 system. Attempting to do it by hand is not recommended and those
1368 that pursue this avenue should read this file carefully, as well
1369 as the archives of freebsd-current and freebsd-hackers mailing lists
1370 for potential gotchas.
1372 [5] Usually this step is a noop. However, from time to time
1373 you may need to do this if you get unknown user in the following
1374 step. It never hurts to do it all the time. You may need to
1375 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1376 install) after the buildworld before this step if you last updated
1377 from current before 20020224 or from -stable before 20020408.
1379 [6] 4.x boot loader can be used to boot a 5.x system, however
1380 it is difficult to do that at best. If you wish to try, then
1381 you should interrupt the boot and at the ok prompt type:
1383 ok boot /boot/kernel/kernel
1384 If this fails to work, you must install a new boot loader as
1387 [7] Before you upgrade, please make sure that you are not using
1388 compatibility slices. These are device names of the form, on i386
1389 and other architectures that use MBR slicing, /dev/ad0a without the
1390 actual slice name. Chances are excellent that these will break.
1391 You generally must update these entries to use the post FreeBSD
1392 2.x form of /dev/ad0s1a.
1394 [8] In order to have a kernel that can run the 4.x binaries
1395 needed to do an installworld, you must include the COMPAT_FREEBSD4
1396 option in your kernel. Failure to do so may leave you with a system
1397 that is hard to boot to recover.
1399 [9] When checking out sources, you must include the -P flag to have
1400 cvs prune empty directories.
1403 This file contains a list, in reverse chronological order, of major
1404 breakages in tracking -current. Not all things will be listed here,
1405 and it only starts on March 15, 2000. Updating files can found in
1406 previous releases if your system is older than this.
1408 Copyright information:
1410 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1412 Redistribution, publication, translation and use, with or without
1413 modification, in full or in part, in any form or format of this
1414 document are permitted without further permission from the author.
1416 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1417 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1418 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1419 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1420 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1421 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1422 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1423 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1424 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1425 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1426 POSSIBILITY OF SUCH DAMAGE.
1428 If you find this document useful, and you want to, you may buy the
1431 Contact Warner Losh if you have any questions about your use of