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 Items affecting the ports and packages system can be found in
8 /usr/ports/UPDATING. Please read that file before running
11 NOTE TO PEOPLE WHO THINK THAT FreeBSD 7.x IS SLOW:
12 FreeBSD 7.x has many debugging features turned on, in
13 both the kernel and userland. These features attempt to detect
14 incorrect use of system primitives, and encourage loud failure
15 through extra sanity checking and fail stop semantics. They
16 also substantially impact system performance. If you want to
17 do performance measurement, benchmarking, and optimization,
18 you'll want to turn them off. This includes various WITNESS-
19 related kernel options, INVARIANTS, malloc debugging flags
20 in userland, and various verbose features in the kernel. Many
21 developers choose to disable these features on build machines
22 to maximize performance.
25 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
26 has been removed. Its functionality may be achieved by explicitly
27 configuring gif(4) interfaces and using the 'phyint' keyword in
29 XORP does not support source-routed IPv4 multicast tunnels nor the
30 integrated IPIP tunneling, therefore it is not affected by this
31 change. The __FreeBSD_version macro has been bumped to 700030.
34 Support for PCI Message Signalled Interrupts has been
35 re-enabled in the bge driver, only for those chips which are
36 believed to support it properly. If there are any problems,
37 MSI can be disabled completely by setting the
38 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
42 Support for PCI Message Signalled Interrupts has been
43 disabled again in the bge driver. Many revisions of the
44 hardware fail to support it properly. Support can be
45 re-enabled by removing the #define of BGE_DISABLE_MSI in
46 "src/sys/dev/bge/if_bge.c".
49 Support for PCI Message Signalled Interrupts has been added
50 to the bge driver. If there are any problems, MSI can be
51 disabled completely by setting the 'hw.pci.enable_msi' and
52 'hw.pci.enable_msix' tunables to 0 in the loader.
55 The removal of several facets of the experimental Threading
56 system from the kernel means that the proc and thread structures
57 have changed quite a bit. I suggest all kernel modules that might
58 reference these structures be recompiled.. Especially the
62 Sound infrastructure has been updated with various fixes and
63 improvements. Most of the changes are pretty much transparent,
64 with exceptions of followings:
65 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
66 moved to their own dev sysctl nodes, for example:
67 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
68 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
69 own chardev in the form of "dsp%d.<function>%d", where <function>
70 is p = playback, r = record and v = virtual, respectively. Users
71 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
72 This does not affect those who are using "/dev/dsp".
75 The following binaries have been disconnected from the build:
76 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
77 and mount_std. The functionality of these programs has been
78 moved into the mount program. For example, to mount a devfs
79 filesystem, instead of using mount_devfs, use: "mount -t devfs".
80 This does not affect entries in /etc/fstab, since entries in
81 /etc/fstab are always processed with "mount -t fstype".
84 Support for PCI Message Signalled Interrupts on i386 and amd64
85 has been added to the kernel and various drivers will soon be
86 updated to use MSI when it is available. If there are any problems,
87 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
88 and 'hw.pci.enable_msix' tunables to 0 in the loader.
91 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
92 The lockmgr object layout has been changed as a result of having
93 a lock_object embedded in it. As a consequence all file system
94 kernel modules must be re-compiled. The mutex profiling man page
95 has not yet been updated to reflect this change.
98 KSE in the kernel has now been made optional and turned on by
99 default. Use 'nooption KSE' in your kernel config to turn it
100 off. All kernel modules *must* be recompiled after this change.
101 There-after, modules from a KSE kernel should be compatible with
102 modules from a NOKSE kernel due to the temporary padding fields
103 added to 'struct proc'.
106 mrouted and its utilities have been removed from the base system.
109 Some ioctl(2) command codes have changed. Full backward ABI
110 compatibility is provided if the "options COMPAT_FREEBSD6" is
111 present in the kernel configuration file. Make sure to add
112 this option to your kernel config file, or recompile X.Org
113 and the rest of ports; otherwise they may refuse to work.
116 tcpslice has been removed from the base system.
119 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
120 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
121 systat needs to be rebuilt.
124 libpcap updated to v0.9.4 and tcpdump to v3.9.4
127 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
128 for IPFIREWALL_FORWARD is now as it was before when it was first
129 committed and for years after. The behaviour is now ON.
132 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
133 Now it can decrypt files created from different architectures.
134 Unfortunately, it is no longer able to decrypt a cipher text
135 generated with an older version on 64 bit architectures.
136 If you have such a file, you need old utility to decrypt it.
139 The interface version of the i4b kernel part has changed. So
140 after updating the kernel sources and compiling a new kernel,
141 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
142 be rebuilt, and vice versa.
145 The XBOX kernel now defaults to the nfe(4) driver instead of
146 the nve(4) driver. Please update your configuration
150 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
151 PCnet family of NICs has been removed. The new le(4) driver serves
152 as an equivalent but cross-platform replacement with the pcn(4)
153 driver still providing performance-optimized support for the subset
154 of AMD Am79C971 PCnet-FAST and greater chips as before.
157 The machdep.* sysctls and the adjkerntz utility have been
158 modified a bit. The new adjkerntz utility uses the new
159 sysctl names and sysctlbyname() calls, so it may be impossible
160 to run an old /sbin/adjkerntz utility in single-user mode
161 with a new kernel. Replace the `adjkerntz -i' step before
162 `make installworld' with:
164 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
166 and proceed as usual with the rest of the installworld-stage
167 steps. Otherwise, you risk installing binaries with their
168 timestamp set several hours in the future, especially if
169 you are running with local time set to GMT+X hours.
172 The ip6fw utility has been removed. The behavior provided by
173 ip6fw has been in ipfw2 for a good while and the rc.d scripts
174 have been updated to deal with it. There are some rules that
175 might not migrate cleanly. Use rc.firewall6 as a template to
179 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
180 attachments have been removed. Make sure to configure scc(4)
181 on sparc64. Note also that by default puc(4) will use uart(4)
182 and not sio(4) for serial ports because interrupt handling has
183 been optimized for multi-port serial cards and only uart(4)
184 implements the interface to support it.
187 The scc(4) driver replaces puc(4) for Serial Communications
188 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
189 Z8530. On sparc64, it is advised to add scc(4) to the kernel
190 configuration to make sure that the serial ports remain
194 Most world/kernel related NO_* build options changed names.
195 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
196 after FreeBSD ports) and should be set in /etc/src.conf
197 (the src.conf(5) manpage is provided). Full backwards
198 compatibility is maintained for the time being though it's
199 highly recommended to start moving old options out of the
200 system-wide /etc/make.conf file into the new /etc/src.conf
201 while also properly renaming them. More conversions will
202 likely follow. Posting to current@:
204 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
207 The NETSMBCRYPTO kernel option has been retired because its
208 functionality is always included in NETSMB and smbfs.ko now.
211 The TDFX_LINUX kernel option was retired and replaced by the
212 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
213 kernel module. Loading it alone should suffice to get 3dfx support
214 for Linux apps because it will pull in 3dfx.ko and linux.ko through
218 The 'audit' group was added to support the new auditing functionality
219 in the base system. Be sure to follow the directions for updating,
220 including the requirement to run mergemaster -p.
223 The kernel ABI to file system modules was changed on i386.
224 Please make sure that your kernel and modules are in sync.
227 This actually occured some time ago, but installing the kernel
228 now also installs a bunch of symbol files for the kernel modules.
229 This increases the size of /boot/kernel to about 67Mbytes. You
230 will need twice this if you will eventually back this up to kernel.old
231 on your next install.
232 If you have a shortage of room in your root partition, you should add
233 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
234 to your /etc/make.conf.
237 libc's malloc implementation has been replaced. This change has the
238 potential to uncover application bugs that previously went unnoticed.
239 See the malloc(3) manual page for more details.
242 The generic netgraph(4) cookie has been changed. If you upgrade
243 kernel passing this point, you also need to upgrade userland
244 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
247 si(4)'s device files now contain the unit number.
248 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
251 The kernel ABI was mostly destroyed due to a change in the size
252 of struct lock_object which is nested in other structures such
253 as mutexes which are nested in all sorts of other structures.
254 Make sure your kernel and modules are in sync.
257 The page coloring algorithm in the VM subsystem was converted
258 from tuning with kernel options to autotuning. Please remove
259 any PQ_* option except PQ_NOOPT from your kernel config.
262 The net80211-related tools in the tools/tools/ath directory
263 have been moved to tools/tools/net80211 and renamed with a
264 "wlan" prefix. Scripts that use them should be adjusted
268 Scripts in the local_startup directories (as defined in
269 /etc/defaults/rc.conf) that have the new rc.d semantics will
270 now be run as part of the base system rcorder. If there are
271 errors or problems with one of these local scripts, it could
272 cause boot problems. If you encounter such problems, boot in
273 single user mode, remove that script from the */rc.d directory.
274 Please report the problem to the port's maintainer, and the
275 freebsd-ports@freebsd.org mailing list.
278 The nodev mount option was deprecated in RELENG_6 (where it
279 was a no-op), and is now unsupported. If you have nodev or dev listed
280 in /etc/fstab, remove it, otherwise it will result in a mount error.
283 ABI between ipfw(4) and ipfw(8) has been changed. You need
284 to rebuild ipfw(8) when rebuilding kernel.
287 rp(4)'s device files now contain the unit number.
288 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
291 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
292 Its /etc/rc.conf.d configuration file has been `ppp' from
293 the beginning, and hence there is no need to touch it.
296 Now most modules get their build-time options from the kernel
297 configuration file. A few modules still have fixed options
298 due to their non-conformant implementation, but they will be
299 corrected eventually. You may need to review the options of
300 the modules in use, explicitly specify the non-default options
301 in the kernel configuration file, and rebuild the kernel and
305 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
306 to turn polling(4) on your interfaces.
309 The old bridge(4) implementation was retired. The new
310 if_bridge(4) serves as a full functional replacement.
313 The ai_addrlen of a struct addrinfo was changed to a socklen_t
314 to conform to POSIX-2001. This change broke an ABI
315 compatibility on 64 bit architecture. You have to recompile
316 userland programs that use getaddrinfo(3) on 64 bit
320 RELENG_6 branched here.
323 The pccard_ifconfig rc.conf variable has been removed and a new
324 variable, ifconfig_DEFAULT has been introduced. Unlike
325 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
326 do not have ifconfig_ifn entries rather than just those in
327 removable_interfaces.
330 Some previous versions of PAM have permitted the use of
331 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
332 to third party PAM modules in /usr/local/lib. A change has been
333 made to require the use of absolute paths in order to avoid
334 ambiguity and dependence on library path configuration, which may
335 affect existing configurations.
338 Major changes to network interface API. All drivers must be
339 recompiled. Drivers not in the base system will need to be
340 updated to the new APIs.
343 Changes were made to kinfo_proc in sys/user.h. Please recompile
344 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
345 will not behave correctly.
347 The API and ABI for hwpmc(4) have changed with the addition
348 of sampling support. Please recompile lib/libpmc(3) and
349 usr.sbin/{pmcstat,pmccontrol}.
352 The OpenBSD dhclient was imported in place of the ISC dhclient
353 and the network interface configuration scripts were updated
354 accordingly. If you use DHCP to configure your interfaces, you
355 must now run devd. Also, DNS updating was lost so you will need
356 to find a workaround if you use this feature.
358 The '_dhcp' user was added to support the OpenBSD dhclient. Be
359 sure to run mergemaster -p (like you are supposed to do every time
363 if_bridge was added to the tree. This has changed struct ifnet.
364 Please recompile userland and all network related modules.
367 The n_net of a struct netent was changed to an uint32_t, and
368 1st argument of getnetbyaddr() was changed to an uint32_t, to
369 conform to POSIX-2001. These changes broke an ABI
370 compatibility on 64 bit architecture. With these changes,
371 shlib major of libpcap was bumped. You have to recompile
372 userland programs that use getnetbyaddr(3), getnetbyname(3),
373 getnetent(3) and/or libpcap on 64 bit architecture.
376 Kernel parsing of extra options on '#!' first lines of shell
377 scripts has changed. Lines with multiple options likely will
378 fail after this date. For full details, please see
379 http://people.freebsd.org/~gad/Updating-20050528.txt
382 The packet filter (pf) code has been updated to OpenBSD 3.7
383 Please note the changed anchor syntax and the fact that
384 authpf(8) now needs a mounted fdescfs(5) to function.
387 The NO_MIXED_MODE kernel option has been removed from the i386
388 amd64 platforms as its use has been superceded by the new local
389 APIC timer code. Any kernel config files containing this option
393 The on-disk format of LC_CTYPE files was changed to be machine
394 independent. Please make sure NOT to use NO_CLEAN buildworld
395 when crossing this point. Crossing this point also requires
396 recompile or reinstall of all locale depended packages.
399 The ifi_epoch member of struct if_data has been changed to
400 contain the uptime at which the interface was created or the
401 statistics zeroed rather then the wall clock time because
402 wallclock time may go backwards. This should have no impact
403 unless an snmp implementation is using this value (I know of
407 The acpi_perf and acpi_throttle drivers are now part of the
408 acpi(4) main module. They are no longer built separately.
411 The layout of struct image_params has changed. You have to
412 recompile all compatibility modules (linux, svr4, etc) for use
416 The p4tcc driver has been merged into cpufreq(4). This makes
417 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
418 compile in "device cpufreq" to restore this functionality.
421 The responsibility of recomputing the file system summary of
422 a SoftUpdates-enabled dirty volume has been transferred to the
423 background fsck. A rebuild of fsck(8) utility is recommended
424 if you have updated the kernel.
426 To get the old behavior (recompute file system summary at mount
427 time), you can set vfs.ffs.compute_summary_at_mount=1 before
428 mounting the new volume.
431 The cpufreq import is complete. As part of this, the sysctls for
432 acpi(4) throttling have been removed. The power_profile script
433 has been updated, so you can use performance/economy_cpu_freq in
434 rc.conf(5) to set AC on/offline cpu frequencies.
437 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
438 requires recompiling libnetgraph and userland netgraph utilities.
441 Support for abbreviated forms of a number of ipfw options is
442 now deprecated. Warnings are printed to stderr indicating the
443 correct full form when a match occurs. Some abbreviations may
444 be supported at a later date based on user feedback. To be
445 considered for support, abbreviations must be in use prior to
446 this commit and unlikely to be confused with current key words.
449 By a popular demand, a lot of NOFOO options were renamed
450 to NO_FOO (see bsd.compat.mk for a full list). The old
451 spellings are still supported, but will cause annoying
452 warnings on stderr. Make sure you upgrade properly (see
453 the COMMON ITEMS: section later in this file).
456 Auto-loading of ancillary wlan modules such as wlan_wep has
457 been temporarily disabled; you need to statically configure
458 the modules you need into your kernel or explicitly load them
459 prior to use. Specifically, if you intend to use WEP encryption
460 with an 802.11 device load/configure wlan_wep; if you want to
461 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
462 and wlan_xauth as required.
465 The behaviour of ppp(8) has changed slightly. If lqr is enabled
466 (``enable lqr''), older versions would revert to LCP ECHO mode on
467 negotiation failure. Now, ``enable echo'' is required for this
468 behaviour. The ppp version number has been bumped to 3.4.2 to
472 The wlan support has been updated to split the crypto support
473 into separate modules. For static WEP you must configure the
474 wlan_wep module in your system or build and install the module
475 in place where it can be loaded (the kernel will auto-load
476 the module when a wep key is configured).
479 The ath driver has been updated to split the tx rate control
480 algorithm into a separate module. You need to include either
481 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
484 Support for systems with an 80386 CPU has been removed. Please
485 use FreeBSD 5.x or earlier on systems with an 80386.
488 We have had a hack which would mount the root filesystem
489 R/W if the device were named 'md*'. As part of the vnode
490 work I'm doing I have had to remove this hack. People
491 building systems which use preloaded MD root filesystems
492 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
493 their /etc/rc scripts.
496 FreeBSD 5.3 shipped here.
499 The size of struct tcpcb has changed again due to the removal
500 of RFC1644 T/TCP. You have to recompile userland programs that
501 read kmem for tcp sockets directly (netstat, sockstat, etc.)
504 The size of struct tcpcb has changed. You have to recompile
505 userland programs that read kmem for tcp sockets directly
506 (netstat, sockstat, etc.)
509 RELENG_5 branched here. For older entries, please see updating
510 in the RELENG_5 branch.
516 Avoid using make -j when upgrading. From time to time in the
517 past there have been problems using -j with buildworld and/or
518 installworld. This is especially true when upgrading between
519 "distant" versions (eg one that cross a major release boundary
520 or several minor releases, or when several months have passed
521 on the -current branch).
523 Sometimes, obscure build problems are the result of environment
524 poisoning. This can happen because the make utility reads its
525 environment when searching for values for global variables.
526 To run your build attempts in an "environmental clean room",
527 prefix all make commands with 'env -i '. See the env(1) manual
528 page for more details.
530 When upgrading from one major version to another it is generally
531 best to upgrade to the latest code in the currently installed branch
532 first, then do an upgrade to the new branch. This is the best-tested
533 upgrade path, and has the highest probability of being successful.
534 Please try this approach before reporting problems with a major
539 If you are updating from a prior version of FreeBSD (even one just
540 a few days old), you should follow this procedure. It is the most
541 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
543 make kernel-toolchain
544 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
545 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
547 To test a kernel once
548 ---------------------
549 If you just want to boot a kernel once (because you are not sure
550 if it works, or if you want to boot a known bad kernel to provide
551 debugging information) run
552 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
553 nextboot -k testkernel
555 To just build a kernel when you know that it won't mess you up
556 --------------------------------------------------------------
557 This assumes you are already running a 5.X system. Replace
558 ${arch} with the architecture of your machine (e.g. "i386",
559 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
561 cd src/sys/${arch}/conf
562 config KERNEL_NAME_HERE
563 cd ../compile/KERNEL_NAME_HERE
568 If this fails, go to the "To build a kernel" section.
570 To rebuild everything and install it on the current system.
571 -----------------------------------------------------------
572 # Note: sometimes if you are running current you gotta do more than
573 # is listed here if you are upgrading from a really old current.
575 <make sure you have good level 0 dumps>
577 make kernel KERNCONF=YOUR_KERNEL_HERE
579 <reboot in single user> [3]
587 To cross-install current onto a separate partition
588 --------------------------------------------------
589 # In this approach we use a separate partition to hold
590 # current's root, 'usr', and 'var' directories. A partition
591 # holding "/", "/usr" and "/var" should be about 2GB in
594 <make sure you have good level 0 dumps>
597 make buildkernel KERNCONF=YOUR_KERNEL_HERE
598 <maybe newfs current's root partition>
599 <mount current's root partition on directory ${CURRENT_ROOT}>
600 make installworld DESTDIR=${CURRENT_ROOT}
601 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
602 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
603 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
604 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
605 <reboot into current>
606 <do a "native" rebuild/install as described in the previous section>
607 <maybe install compatibility libraries from src/lib/compat>
611 To upgrade in-place from 5.x-stable to current
612 ----------------------------------------------
613 <make sure you have good level 0 dumps>
615 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
617 <reboot in single user> [3]
624 Make sure that you've read the UPDATING file to understand the
625 tweaks to various things you need. At this point in the life
626 cycle of current, things change often and you are on your own
627 to cope. The defaults can also change, so please read ALL of
628 the UPDATING entries.
630 Also, if you are tracking -current, you must be subscribed to
631 freebsd-current@freebsd.org. Make sure that before you update
632 your sources that you have read and understood all the recent
633 messages there. If in doubt, please track -stable which has
636 [1] If you have third party modules, such as vmware, you
637 should disable them at this point so they don't crash your
640 [3] From the bootblocks, boot -s, and then do
645 adjkerntz -i # if CMOS is wall time
646 Also, when doing a major release upgrade, it is required that
647 you boot into single user mode to do the installworld.
649 [4] Note: This step is non-optional. Failure to do this step
650 can result in a significant reduction in the functionality of the
651 system. Attempting to do it by hand is not recommended and those
652 that pursue this avenue should read this file carefully, as well
653 as the archives of freebsd-current and freebsd-hackers mailing lists
654 for potential gotchas.
656 [5] Usually this step is a noop. However, from time to time
657 you may need to do this if you get unknown user in the following
658 step. It never hurts to do it all the time. You may need to
659 install a new mergemaster (cd src/usr.sbin/mergemaster && make
660 install) after the buildworld before this step if you last updated
661 from current before 20020224 or from -stable before 20020408.
663 [8] In order to have a kernel that can run the 4.x binaries
664 needed to do an installworld, you must include the COMPAT_FREEBSD4
665 option in your kernel. Failure to do so may leave you with a system
666 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
667 is required to run the 5.x binaries on more recent kernels.
669 Make sure that you merge any new devices from GENERIC since the
670 last time you updated your kernel config file.
672 [9] When checking out sources, you must include the -P flag to have
673 cvs prune empty directories.
675 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
676 "?=" instead of the "=" assignment operator, so that buildworld can
677 override the CPUTYPE if it needs to.
679 MAKEOBJDIRPREFIX must be defined in an environment variable, and
680 not on the command line, or in /etc/make.conf. buildworld will
681 warn if it is improperly defined.
684 This file contains a list, in reverse chronological order, of major
685 breakages in tracking -current. Not all things will be listed here,
686 and it only starts on October 16, 2004. Updating files can found in
687 previous releases if your system is older than this.
689 Copyright information:
691 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
693 Redistribution, publication, translation and use, with or without
694 modification, in full or in part, in any form or format of this
695 document are permitted without further permission from the author.
697 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
698 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
699 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
700 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
701 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
702 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
703 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
704 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
705 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
706 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
707 POSSIBILITY OF SUCH DAMAGE.
709 If you find this document useful, and you want to, you may buy the
712 Contact Warner Losh if you have any questions about your use of