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