1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 head, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW:
20 FreeBSD 10.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 WITH_ICONV has been split into two feature sets. WITH_ICONV now
36 enables just the iconv* functionality and is now on by default.
37 WITH_LIBICONV_COMPAT enables the libiconv api and link time
38 compatability. Set WITHOUT_ICONV to build the old way.
39 If you have been using WITH_ICONV before, you will very likely
40 need to turn on WITH_LIBICONV_COMPAT.
43 INVARIANTS option now enables DEBUG for code with OpenSolaris and
44 Illumos origin, including ZFS. If you have INVARIANTS in your
45 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
47 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
48 locks if WITNESS option was set. Because that generated a lot of
49 witness(9) reports and all of them were believed to be false
50 positives, this is no longer done. New option OPENSOLARIS_WITNESS
51 can be used to achieve the previous behavior.
54 Timer values in IPv6 data structures now use time_uptime instead
55 of time_second. Although this is not a user-visible functional
56 change, userland utilities which directly use them---ndp(8),
57 rtadvd(8), and rtsold(8) in the base system---need to be updated
61 find -delete can now delete the pathnames given as arguments,
62 instead of only files found below them or if the pathname did
63 not contain any slashes. Formerly, the following error message
66 find: -delete: <path>: relative path potentially not safe
68 Deleting the pathnames given as arguments can be prevented
69 without error messages using -mindepth 1 or by changing
70 directory and passing "." as argument to find. This works in the
71 old as well as the new version of find.
74 Behavior of devfs rules path matching has been changed.
75 Pattern is now always matched against fully qualified devfs
76 path and slash characters must be explicitly matched by
77 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
78 subdirectories must be reviewed.
81 The default ARM ABI has changed to the ARM EABI. The old ABI is
82 incompatible with the ARM EABI and all programs and modules will
83 need to be rebuilt to work with a new kernel.
85 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
87 NOTE: Support for the old ABI will be removed in the future and
88 users are advised to upgrade.
91 pkg_install has been disconnected from the build if you really need it
92 you should add WITH_PKGTOOLS in your src.conf(5).
95 Most of network statistics structures were changed to be able
96 keep 64-bits counters. Thus all tools, that work with networking
97 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
100 Fix targets that run multiple make's to use && rather than ;
101 so that subsequent steps depend on success of previous.
103 NOTE: if building 'universe' with -j* on stable/8 or stable/9
104 it would be better to start the build using bmake, to avoid
105 overloading the machine.
108 Fix a bug that allowed a tracing process (e.g. gdb) to write
109 to a memory-mapped file in the traced process's address space
110 even if neither the traced process nor the tracing process had
111 write access to that file.
114 CVS has been removed from the base system. An exact copy
115 of the code is available from the devel/cvs port.
118 Some people report the following error after the switch to bmake:
120 make: illegal option -- J
121 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
123 *** [buildworld] Error code 2
125 this likely due to an old instance of make in
126 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
127 which src/Makefile will use that blindly, if it exists, so if
128 you see the above error:
130 rm -rf `make -V MAKEPATH`
135 Use bmake by default.
136 Whereas before one could choose to build with bmake via
137 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
138 make. The goal is to remove these knobs for 10-RELEASE.
140 It is worth noting that bmake (like gmake) treats the command
141 line as the unit of failure, rather than statements within the
142 command line. Thus '(cd some/where && dosomething)' is safer
143 than 'cd some/where; dosomething'. The '()' allows consistent
144 behavior in parallel build.
147 Fix a bug that allows NFS clients to issue READDIR on files.
150 The WITHOUT_IDEA option has been removed because
151 the IDEA patent expired.
154 The sysctl which controls TRIM support under ZFS has been renamed
155 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
159 The mergemaster command now uses the default MAKEOBJDIRPREFIX
160 rather than creating it's own in the temporary directory in
161 order allow access to bootstrapped versions of tools such as
162 install and mtree. When upgrading from version of FreeBSD where
163 the install command does not support -l, you will need to
164 install a new mergemaster command if mergemaster -p is required.
165 This can be accomplished with the command (cd src/usr.sbin/mergemaster
169 Legacy ATA stack, disabled and replaced by new CAM-based one since
170 FreeBSD 9.0, completely removed from the sources. Kernel modules
171 atadisk and atapi*, user-level tools atacontrol and burncd are
172 removed. Kernel option `options ATA_CAM` is now permanently enabled
176 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
177 and socketpair(2). Software, in particular Kerberos, may
178 automatically detect and use these during building. The resulting
179 binaries will not work on older kernels.
182 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
183 information, see the respective 20130304 entry).
186 Recent commits to callout(9) changed the size of struct callout,
187 so the KBI is probably heavily disturbed. Also, some functions
188 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
189 by macros. Every kernel module using it won't load, so rebuild
192 The ctl device has been re-enabled in GENERIC for i386 and amd64,
193 but does not initialize by default (because of the new CTL_DISABLE
194 option) to save memory. To re-enable it, remove the CTL_DISABLE
195 option from the kernel config file or set kern.cam.ctl.disable=0
196 in /boot/loader.conf.
199 The ctl device has been disabled in GENERIC for i386 and amd64.
200 This was done due to the extra memory being allocated at system
201 initialisation time by the ctl driver which was only used if
202 a CAM target device was created. This makes a FreeBSD system
203 unusable on 128MB or less of RAM.
206 A new compression method (lz4) has been merged to -HEAD. Please
207 refer to zpool-features(7) for more information.
209 Please refer to the "ZFS notes" section of this file for information
210 on upgrading boot ZFS pools.
213 A BSD-licensed patch(1) variant has been added and is installed
214 as bsdpatch, being the GNU version the default patch.
215 To inverse the logic and use the BSD-licensed one as default,
216 while having the GNU version installed as gnupatch, rebuild
217 and install world with the WITH_BSD_PATCH knob set.
220 Due to the use of the new -l option to install(1) during build
221 and install, you must take care not to directly set the INSTALL
222 make variable in your /etc/make.conf, /etc/src.conf, or on the
223 command line. If you wish to use the -C flag for all installs
224 you may be able to add INSTALL+=-C to /etc/make.conf or
228 The install(1) option -M has changed meaning and now takes an
229 argument that is a file or path to append logs to. In the
230 unlikely event that -M was the last option on the command line
231 and the command line contained at least two files and a target
232 directory the first file will have logs appended to it. The -M
233 option served little practical purpose in the last decade so its
234 use is expected to be extremely rare.
237 After switching to Clang as the default compiler some users of ZFS
238 on i386 systems started to experience stack overflow kernel panics.
239 Please consider using 'options KSTACK_PAGES=4' in such configurations.
242 GEOM_LABEL now mangles label names read from file system metadata.
243 Mangling affect labels containing spaces, non-printable characters,
244 '%' or '"'. Device names in /etc/fstab and other places may need to
248 By default, only the 10 most recent kernel dumps will be saved. To
249 restore the previous behaviour (no limit on the number of kernel dumps
250 stored in the dump directory) add the following line to /etc/rc.conf:
255 With the addition of auditdistd(8), a new auditdistd user is now
256 depended on during installworld. "mergemaster -p" can be used to add
257 the user prior to installworld, as documented in the handbook.
260 The sin6_scope_id member variable in struct sockaddr_in6 is now
261 filled by the kernel before passing the structure to the userland via
262 sysctl or routing socket. This means the KAME-specific embedded scope
263 id in sin6_addr.s6_addr[2] is always cleared in userland application.
264 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
265 __FreeBSD_version is bumped to 1000025.
268 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
269 This means that the world and kernel will be compiled with clang
270 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
271 and /usr/bin/cpp. To disable this behavior and revert to building
272 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
273 of current may need to bootstrap WITHOUT_CLANG first if the clang
274 build fails (its compatibility window doesn't extend to the 9 stable
278 The IPFIREWALL_FORWARD kernel option has been removed. Its
279 functionality now turned on by default.
282 The ZERO_COPY_SOCKET kernel option has been removed and
283 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
284 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
285 mechanism which is not safe and may result in kernel crashes.
286 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
287 driver supports disposeable external page sized mbuf storage.
288 Proper replacements for both zero-copy mechanisms are under
289 consideration and will eventually lead to complete removal
290 of the two kernel options.
293 The IPv4 network stack has been converted to network byte
294 order. The following modules need to be recompiled together
295 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
296 pf(4), ipfw(4), ng_ipfw(4), stf(4).
299 Support for non-MPSAFE filesystems was removed from VFS. The
300 VFS_VERSION was bumped, all filesystem modules shall be
304 All the non-MPSAFE filesystems have been disconnected from
305 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
306 portalfs, smbfs, xfs.
309 The interface cloning API and ABI has changed. The following
310 modules need to be recompiled together with kernel:
311 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
312 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
313 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
316 The sdhci driver was split in two parts: sdhci (generic SD Host
317 Controller logic) and sdhci_pci (actual hardware driver).
318 No kernel config modifications are required, but if you
319 load sdhc as a module you must switch to sdhci_pci instead.
322 Import the FUSE kernel and userland support into base system.
325 The GNU sort(1) program has been removed since the BSD-licensed
326 sort(1) has been the default for quite some time and no serious
327 problems have been reported. The corresponding WITH_GNU_SORT
331 The pfil(9) API/ABI for AF_INET family has been changed. Packet
332 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
336 The net80211(4) ABI has been changed to allow for improved driver
337 PS-POLL and power-save support. All wireless drivers need to be
338 recompiled to work with the new kernel.
341 The random(4) support for the VIA hardware random number
342 generator (`PADLOCK') is no longer enabled unconditionally.
343 Add the PADLOCK_RNG option in the custom kernel config if
344 needed. The GENERIC kernels on i386 and amd64 do include the
345 option, so the change only affects the custom kernel
349 The pf(4) packet filter ABI has been changed. pfctl(8) and
350 snmp_pf module need to be recompiled to work with new kernel.
353 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
354 to -HEAD. Pools that have empty_bpobj in active state can not be
355 imported read-write with ZFS implementations that do not support
356 this feature. For more information read the zpool-features(5)
360 The sparc64 ZFS loader has been changed to no longer try to auto-
361 detect ZFS providers based on diskN aliases but now requires these
362 to be explicitly listed in the OFW boot-device environment variable.
365 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
366 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
367 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
370 The following sysctls and tunables have been renamed for consistency
371 with other variables:
372 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
373 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
376 The sort utility has been replaced with BSD sort. For now, GNU sort
377 is also available as "gnusort" or the default can be set back to
378 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
379 installed as "bsdsort".
382 A new version of ZFS (pool version 5000) has been merged to -HEAD.
383 Starting with this version the old system of ZFS pool versioning
384 is superseded by "feature flags". This concept enables forward
385 compatibility against certain future changes in functionality of ZFS
386 pools. The first read-only compatible "feature flag" for ZFS pools
387 is named "com.delphix:async_destroy". For more information
388 read the new zpool-features(5) manual page.
389 Please refer to the "ZFS notes" section of this file for information
390 on upgrading boot ZFS pools.
393 The malloc(3) implementation embedded in libc now uses sources imported
394 as contrib/jemalloc. The most disruptive API change is to
395 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
396 delete it prior to installworld, and optionally re-create it using the
397 new format after rebooting. See malloc.conf(5) for details
398 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
402 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
403 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
404 now spelled mips. This is to aid compatibility with third-party
405 software that expects this naming scheme in uname(3). Little-endian
406 settings are unchanged. If you are updating a big-endian mips64 machine
407 from before this change, you may need to set MACHINE_ARCH=mips64 in
408 your environment before the new build system will recognize your machine.
411 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
415 Now unix domain sockets behave "as expected" on nullfs(5). Previously
416 nullfs(5) did not pass through all behaviours to the underlying layer,
417 as a result if we bound to a socket on the lower layer we could connect
418 only to the lower path; if we bound to the upper layer we could connect
419 only to the upper path. The new behavior is one can connect to both the
420 lower and the upper paths regardless what layer path one binds to.
423 The getifaddrs upgrade path broken with 20111215 has been restored.
424 If you have upgraded in between 20111215 and 20120209 you need to
425 recompile libc again with your kernel. You still need to recompile
426 world to be able to configure CARP but this restriction already
430 The set_rcvar() function has been removed from /etc/rc.subr. All
431 base and ports rc.d scripts have been updated, so if you have a
432 port installed with a script in /usr/local/etc/rc.d you can either
433 hand-edit the rcvar= line, or reinstall the port.
435 An easy way to handle the mass-update of /etc/rc.d:
436 rm /etc/rc.d/* && mergemaster -i
439 panic(9) now stops other CPUs in the SMP systems, disables interrupts
440 on the current CPU and prevents other threads from running.
441 This behavior can be reverted using the kern.stop_scheduler_on_panic
443 The new behavior can be incompatible with kern.sync_on_panic.
446 The carp(4) facility has been changed significantly. Configuration
447 of the CARP protocol via ifconfig(8) has changed, as well as format
448 of CARP events submitted to devd(8) has changed. See manual pages
449 for more information. The arpbalance feature of carp(4) is currently
450 not supported anymore.
452 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
453 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
454 need to be recompiled.
457 The acpi_wmi(4) status device /dev/wmistat has been renamed to
461 The option VFS_ALLOW_NONMPSAFE option has been added in order to
462 explicitely support non-MPSAFE filesystems.
463 It is on by default for all supported platform at this present
467 The broken amd(4) driver has been replaced with esp(4) in the amd64,
468 i386 and pc98 GENERIC kernel configuration files.
471 sysinstall has been removed
474 The stable/9 branch created in subversion. This corresponds to the
475 RELENG_9 branch in CVS.
478 This commit modifies vfs_register() so that it uses a hash
479 calculation to set vfc_typenum, which is enabled by default.
480 The first time a system is booted after this change, the
481 vfc_typenum values will change for all file systems. The
482 main effect of this is a change to the NFS server file handles
483 for file systems that use vfc_typenum in their fsid, such as ZFS.
484 It will, however, prevent vfc_typenum from changing when file
485 systems are loaded in a different order for subsequent reboots.
486 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
487 until you are ready to remount all NFS clients after a reboot.
490 Bump the shared library version numbers for libraries that
491 do not use symbol versioning, have changed the ABI compared
492 to stable/8 and which shared library version was not bumped.
493 Done as part of 9.0-RELEASE cycle.
496 During the merge of Capsicum features, the fget(9) KPI was modified.
497 This may require the rebuilding of out-of-tree device drivers --
498 issues have been reported specifically with the nVidia device driver.
499 __FreeBSD_version is bumped to 900041.
501 Also, there is a period between 20110811 and 20110814 where the
502 special devices /dev/{stdin,stdout,stderr} did not work correctly.
503 Building world from a kernel during that window may not work.
506 The packet filter (pf) code has been updated to OpenBSD 4.5.
507 You need to update userland tools to be in sync with kernel.
508 This update breaks backward compatibility with earlier pfsync(4)
509 versions. Care must be taken when updating redundant firewall setups.
512 The following sysctls and tunables are retired on x86 platforms:
514 machdep.hlt_logical_cpus
515 The following sysctl is retired:
516 machdep.hyperthreading_allowed
517 The sysctls were supposed to provide a way to dynamically offline and
518 online selected CPUs on x86 platforms, but the implementation has not
519 been reliable especially with SCHED_ULE scheduler.
520 machdep.hyperthreading_allowed tunable is still available to ignore
521 hyperthreading CPUs at OS level.
522 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
523 where X is an APIC ID of a CPU. Be advised, though, that disabling
524 CPUs in non-uniform fashion will result in non-uniform topology and
525 may lead to sub-optimal system performance with SCHED_ULE, which is
529 cpumask_t type is retired and cpuset_t is used in order to describe
533 Changes to ifconfig(8) for dynamic address family detection mandate
534 that you are running a kernel of 20110525 or later. Make sure to
535 follow the update procedure to boot a new kernel before installing
539 Support for sun4v architecture is officially dropped
542 Several KPI breaking changes have been committed to the mii(4) layer,
543 the PHY drivers and consequently some Ethernet drivers using mii(4).
544 This means that miibus.ko and the modules of the affected Ethernet
545 drivers need to be recompiled.
547 Note to kernel developers: Given that the OUI bit reversion problem
548 was fixed as part of these changes all mii(4) commits related to OUIs,
549 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
550 handling, no longer can be merged verbatim to stable/8 and previous
554 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
555 into their kernel configurations along with 'device pci'.
558 The default NFS client is now the new NFS client, so fstype "newnfs"
559 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
560 Although mounts via fstype "nfs" will usually work without userland
561 changes, it is recommended that the mount(8) and mount_nfs(8)
562 commands be rebuilt from sources and that a link to mount_nfs called
563 mount_oldnfs be created. The new client is compiled into the
564 kernel with "options NFSCL" and this is needed for diskless root
565 file systems. The GENERIC kernel configs have been changed to use
566 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
567 To use the regular/old client, you can "mount -t oldnfs ...". For
568 a diskless root file system, you must also include a line like:
570 vfs.root.mountfrom="oldnfs:"
572 in the boot/loader.conf on the root fs on the NFS server to make
573 a diskless root fs use the old client.
576 The GENERIC kernels for all architectures now default to the new
577 CAM-based ATA stack. It means that all legacy ATA drivers were
578 removed and replaced by respective CAM drivers. If you are using
579 ATA device names in /etc/fstab or other places, make sure to update
580 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
581 where 'Y's are the sequential numbers starting from zero for each type
582 in order of detection, unless configured otherwise with tunables,
583 see cam(4)). There will be symbolic links created in /dev/ to map
584 old adX devices to the respective adaY. They should provide basic
585 compatibility for file systems mounting in most cases, but they do
586 not support old user-level APIs and do not have respective providers
587 in GEOM. Consider using updated management tools with new device names.
589 It is possible to load devices ahci, ata, siis and mvs as modules,
590 but option ATA_CAM should remain in kernel configuration to make ata
591 module work as CAM driver supporting legacy ATA controllers. Device ata
592 still can be used in modular fashion (atacore + ...). Modules atadisk
593 and atapi* are not used and won't affect operation in ATA_CAM mode.
594 Note that to use CAM-based ATA kernel should include CAM devices
595 scbus, pass, da (or explicitly ada), cd and optionally others. All of
596 them are parts of the cam module.
598 ataraid(4) functionality is now supported by the RAID GEOM class.
599 To use it you can load geom_raid kernel module and use graid(8) tool
600 for management. Instead of /dev/arX device names, use /dev/raid/rX.
602 No kernel config options or code have been removed, so if a problem
603 arises, please report it and optionally revert to the old ATA stack.
604 In order to do it you can remove from the kernel config:
609 , and instead add back:
610 device atadisk # ATA disk drives
611 device ataraid # ATA RAID drives
612 device atapicd # ATAPI CDROM drives
613 device atapifd # ATAPI floppy drives
614 device atapist # ATAPI tape drives
617 The default NFS server has been changed to the new server, which
618 was referred to as the experimental server. If you need to switch
619 back to the old NFS server, you must now put the "-o" option on
620 both the mountd and nfsd commands. This can be done using the
621 mountd_flags and nfs_server_flags rc.conf variables until an
622 update to the rc scripts is committed, which is coming soon.
625 The GNU Objective-C runtime library (libobjc), and other Objective-C
626 related components have been removed from the base system. If you
627 require an Objective-C library, please use one of the available ports.
630 ath(4) has been split into bus- and device- modules. if_ath contains
631 the HAL, the TX rate control and the network device code. if_ath_pci
632 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
633 contains the AHB glue. Users need to load both if_ath_pci and if_ath
634 in order to use ath on everything else.
636 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
637 need to load if_ath and if_ath_pci for ath(4) operation.
640 As part of the replacement of sysinstall, the process of building
641 release media has changed significantly. For details, please re-read
642 release(7), which has been updated to reflect the new build process.
645 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
646 is the last available version under GPLv2. It brings a number of new
647 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
648 4.1 and SSE 4.2), better support for powerpc64, a number of new
649 directives, and lots of other small improvements. See the ChangeLog
650 file in contrib/binutils for the full details.
653 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
654 compliant, and will now use half of hash for authentication.
655 This will break interoperability with all stacks (including all
656 actual FreeBSD versions) who implement
657 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
659 The only workaround with such peers is to use another HMAC
660 algorithm for IPsec ("phase 2") authentication.
663 Remove the uio_yield prototype and symbol. This function has
664 been misnamed since it was introduced and should not be
665 globally exposed with this name. The equivalent functionality
666 is now available using kern_yield(curthread->td_user_pri).
667 The function remains undocumented.
670 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
671 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
672 for scalar sysctls is defined but disabled. Code that needs
673 UQUAD to pass the type checking that must compile on older
674 systems where the define is not present can check against
675 __FreeBSD_version >= 900030.
677 The system dialog(1) has been replaced with a new version previously
678 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
679 with the previous version, but the libdialog associated with it has
680 a largely incompatible API. As such, the original version of libdialog
681 will be kept temporarily as libodialog, until its base system consumers
682 are replaced or updated. Bump __FreeBSD_version to 900030.
685 If you are trying to run make universe on a -stable system, and you get
686 the following warning:
687 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
688 unknown. config(8) likely too old."
689 or something similar to it, then you must upgrade your -stable system
690 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
691 stable/8) or build the config from the latest stable/8 branch and
692 install it on your system.
694 Prior to this date, building a current universe on 8-stable system from
695 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
696 error in the first kernel build phase. A new config on those old
697 systems will fix that problem for older versions of -current.
700 The TCP stack has been modified to allow Khelp modules to interact with
701 it via helper hook points and store per-connection data in the TCP
702 control block. Bump __FreeBSD_version to 900029. User space tools that
703 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
707 Generic IEEE 802.3 annex 31B full duplex flow control support has been
708 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
709 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
710 to take advantage of it instead of using custom implementations. This
711 means that these drivers now no longer unconditionally advertise
712 support for flow control but only do so if flow control is a selected
713 media option. This was implemented in the generic support that way in
714 order to allow flow control to be switched on and off via ifconfig(8)
715 with the PHY specific default to typically off in order to protect
716 from unwanted effects. Consequently, if you used flow control with
717 one of the above mentioned drivers you now need to explicitly enable
719 ifconfig bge0 media auto mediaopt flowcontrol
721 Along with the above mentioned changes generic support for setting
722 1000baseT master mode also has been added and brgphy(4), ciphy(4),
723 e1000phy(4) as well as ip1000phy(4) have been converted to take
724 advantage of it. This means that these drivers now no longer take the
725 link0 parameter for selecting master mode but the master media option
726 has to be used instead, for example like in the following:
727 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
729 Selection of master mode now is also available with all other PHY
730 drivers supporting 1000baseT.
733 The TCP stack has received a significant update to add support for
734 modularised congestion control and generally improve the clarity of
735 congestion control decisions. Bump __FreeBSD_version to 900025. User
736 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
737 sockstat) need to be recompiled.
740 The man(1) utility has been replaced by a new version that no longer
741 uses /etc/manpath.config. Please consult man.conf(5) for how to
742 migrate local entries to the new format.
745 The copyright strings printed by login(1) and sshd(8) at the time of a
746 new connection have been removed to follow other operating systems and
750 A workaround for a fixed ld bug has been removed in kernel code,
751 so make sure that your system ld is built from sources after
752 revision 210245 from 2010-07-19 (r211583 if building head kernel
753 on stable/8, r211584 for stable/7; both from 2010-08-21).
754 A symptom of incorrect ld version is different addresses for
755 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
758 The $ipv6_prefer variable in rc.conf(5) has been split into
759 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
761 The $ip6addrctl_policy is a variable to choose a pre-defined
762 address selection policy set by ip6addrctl(8). A value
763 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
766 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
767 flag (see an entry of 20090926) is set on an interface with no
768 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
769 security reason. If you want IPv6 link-local address on all
770 interfaces by default, set this to "YES".
772 The old ipv6_prefer="YES" is equivalent to
773 ipv6_activate_all_interfaces="YES" and
774 ip6addrctl_policy="ipv6_prefer".
777 DTrace has grown support for userland tracing. Due to this, DTrace is
778 now i386 and amd64 only.
779 dtruss(1) is now installed by default on those systems and a new
780 kernel module is needed for userland tracing: fasttrap.
781 No changes to your kernel config file are necessary to enable
782 userland tracing, but you might consider adding 'STRIP=' and
783 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
784 to have informative userland stack traces in DTrace (ustack).
787 The acpi_aiboost(4) driver has been removed in favor of the new
788 aibs(4) driver. You should update your kernel configuration file.
791 BSD grep has been imported to the base system and it is built by
792 default. It is completely BSD licensed, highly GNU-compatible, uses
793 less memory than its GNU counterpart and has a small codebase.
794 However, it is slower than its GNU counterpart, which is mostly
795 noticeable for larger searches, for smaller ones it is measurable
796 but not significant. The reason is complex, the most important factor
797 is that we lack a modern and efficient regex library and GNU
798 overcomes this by optimizing the searches internally. Future work
799 on improving the regex performance is planned, for the meantime,
800 users that need better performance, can build GNU grep instead by
801 setting the WITH_GNU_GREP knob.
804 Due to the import of powerpc64 support, all existing powerpc kernel
805 configuration files must be updated with a machine directive like this:
806 machine powerpc powerpc
808 In addition, an updated config(8) is required to build powerpc kernels
812 A new version of ZFS (version 15) has been merged to -HEAD.
813 This version uses a python library for the following subcommands:
814 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
815 For full functionality of these commands the following port must
816 be installed: sysutils/py-zfs
819 'vm_page's are now hashed by physical address to an array of mutexes.
820 Currently this is only used to serialize access to hold_count. Over
821 time the page queue mutex will be peeled away. This changes the size
822 of pmap on every architecture. And requires all callers of vm_page_hold
823 and vm_page_unhold to be updated.
826 WITH_CTF can now be specified in src.conf (not recommended, there
827 are some problems with static executables), make.conf (would also
828 affect ports which do not use GNU make and do not override the
829 compile targets) or in the kernel config (via "makeoptions
831 When WITH_CTF was specified there before this was silently ignored,
832 so make sure that WITH_CTF is not used in places which could lead
833 to unwanted behavior.
836 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
837 to allow 32-bit compatibility on non-x86 platforms. All kernel
838 configurations on amd64 and ia64 platforms using these options must
839 be modified accordingly.
842 The utmp user accounting database has been replaced with utmpx,
843 the user accounting interface standardized by POSIX.
844 Unfortunately the semantics of utmp and utmpx don't match,
845 making it practically impossible to support both interfaces.
846 The user accounting database is used by tools like finger(1),
847 last(1), talk(1), w(1) and ac(8).
849 All applications in the base system use utmpx. This means only
850 local binaries (e.g. from the ports tree) may still use these
851 utmp database files. These applications must be rebuilt to make
854 After the system has been upgraded, it is safe to remove the old
855 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
856 assuming their contents is of no importance anymore. Old wtmp
857 databases can only be used by last(1) and ac(8) after they have
858 been converted to the new format using wtmpcvt(1).
861 Introduce the kernel thread "deadlock resolver" (which can be enabled
862 via the DEADLKRES option, see NOTES for more details) and the
863 sleepq_type() function for sleepqueues.
866 The rc.firewall and rc.firewall6 were unified, and
867 rc.firewall6 and rc.d/ip6fw were removed.
868 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
869 variables are obsoleted. Instead, the following new rc
870 variables are added to rc.d/ipfw:
872 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
873 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
874 firewall_simple_onet_ipv6, firewall_trusted_ipv6
876 The meanings correspond to the relevant IPv4 variables.
882 The default terminal emulation for syscons(4) has been changed
883 from cons25 to xterm on all platforms except pc98. This means
884 that the /etc/ttys file needs to be updated to ensure correct
885 operation of applications on the console.
887 The terminal emulation style can be toggled per window by using
888 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
889 options can be used to change the compile-time default back to
892 To prevent graphical artifacts, make sure the TERM environment
893 variable is set to match the terminal emulation that is being
894 performed by syscons(4).
897 The layout of the structure ieee80211req_scan_result has changed.
898 Applications that require wireless scan results (e.g. ifconfig(8))
899 from net80211 need to be recompiled.
901 Applications such as wpa_supplicant(8) may require a full world
902 build without using NO_CLEAN in order to get synchronized with the
906 The iwn(4) driver has been updated to support the 5000 and 5150 series.
907 There's one kernel module for each firmware. Adding "device iwnfw"
908 to the kernel configuration file means including all three firmware
909 images inside the kernel. If you want to include just the one for
910 your wireless card, use the devices iwn4965fw, iwn5000fw or
914 The rc.d/network_ipv6, IPv6 configuration script has been integrated
915 into rc.d/netif. The changes are the following:
917 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
918 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
919 Note that both variables need the "inet6" keyword at the head.
921 Do not set $ipv6_network_interfaces manually if you do not
922 understand what you are doing. It is not needed in most cases.
924 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
927 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
928 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
930 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
931 all configured interfaces have "inet6 accept_rtadv" in the
932 $ifconfig_IF_ipv6. These are for backward compatibility.
934 3. A new variable $ipv6_prefer has been added. If NO, IPv6
935 functionality of interfaces with no corresponding
936 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
937 and the default address selection policy of ip6addrctl(8)
938 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
939 Note that if you want to configure IPv6 functionality on the
940 disabled interfaces after boot, first you need to clear the flag by
941 using ifconfig(8) like:
943 ifconfig em0 inet6 -ifdisabled
945 If YES, the default address selection policy is set as
948 The default value of $ipv6_prefer is NO.
950 4. If your system need to receive Router Advertisement messages,
951 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
952 scripts automatically invoke rtsol(8) when the interface becomes
953 UP. The Router Advertisement messages are used for SLAAC
954 (State-Less Address AutoConfiguration).
957 802.11s D3.03 support was committed. This is incompatible with the
958 previous code, which was based on D3.0.
961 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
962 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
963 control whether accepting Router Advertisement messages or not.
964 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
965 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
966 The ifconfig(8) utility now supports these flags.
969 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
970 mount(8) and -a option for df(1) to see them.
973 The old tunable hw.bus.devctl_disable has been superseded by
974 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
975 replaced by hw.bus.devctl_queue=0. The default for this new tunable
979 Remove the option STOP_NMI. The default action is now to use NMI only
980 for KDB via the newly introduced function stop_cpus_hard() and
981 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
984 The stable/8 branch created in subversion. This corresponds to the
985 RELENG_8 branch in CVS.
988 Bump the shared library version numbers for all libraries that do not
989 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
990 __FreeBSD_version to 800105.
993 Due to changes in the implementation of virtual network stack support,
994 all network-related kernel modules must be recompiled. As this change
995 breaks the ABI, bump __FreeBSD_version to 800104.
998 The TOE interface to the TCP syncache has been modified to remove
999 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1000 The cxgb driver is the only TOE consumer affected by this change, and
1001 needs to be recompiled along with the kernel. As this change breaks
1002 the ABI, bump __FreeBSD_version to 800103.
1005 Padding has been added to struct tcpcb, sackhint and tcpstat in
1006 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1007 maintaining the ABI. However, this change breaks the ABI, so bump
1008 __FreeBSD_version to 800102. User space tools that rely on the size of
1009 any of these structs (e.g. sockstat) need to be recompiled.
1012 The NFS_LEGACYRPC option has been removed along with the old kernel
1013 RPC implementation that this option selected. Kernel configurations
1014 may need to be adjusted.
1017 The network interface device nodes at /dev/net/<interface> have been
1018 removed. All ioctl operations can be performed the normal way using
1019 routing sockets. The kqueue functionality can generally be replaced
1020 with routing sockets.
1023 The documentation from the FreeBSD Documentation Project (Handbook,
1024 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1025 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1028 The ABI of various structures related to the SYSV IPC API have been
1029 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1030 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1034 Layout of struct vnet has changed as routing related variables were
1035 moved to their own Vimage module. Modules need to be recompiled. Bump
1036 __FreeBSD_version to 800099.
1039 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1040 respectively. As long as no more than 16 groups per process are used,
1041 no changes should be visible. When more than 16 groups are used, old
1042 binaries may fail if they call getgroups() or getgrouplist() with
1043 statically sized storage. Recompiling will work around this, but
1044 applications should be modified to use dynamically allocated storage
1045 for group arrays as POSIX.1-2008 does not cap an implementation's
1046 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1048 NFS and portalfs mounts may also be affected as the list of groups is
1049 truncated to 16. Users of NFS who use more than 16 groups, should
1050 take care that negative group permissions are not used on the exported
1051 file systems as they will not be reliable unless a GSSAPI based
1052 authentication method is used.
1055 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1056 option compiles in the support for adaptive spinning for lockmgrs
1057 which want to enable it. The lockinit() function now accepts the flag
1058 LK_ADAPTIVE in order to make the lock object subject to adaptive
1059 spinning when both held in write and read mode.
1062 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1063 changed. User applications that use this ioctl need to be rebuilt.
1066 The layout of struct thread has changed. Kernel and modules need to
1070 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1071 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1074 window(1) has been removed from the base system. It can now be
1075 installed from ports. The port is called misc/window.
1078 The way we are storing and accessing `routing table' entries has
1079 changed. Programs reading the FIB, like netstat, need to be
1083 A new netisr implementation has been added for FreeBSD 8. Network
1084 file system modules, such as igmp, ipdivert, and others, should be
1086 Bump __FreeBSD_version to 800096.
1089 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1093 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1094 Bump __FreeBSD_version to 800094.
1097 Add mnt_xflag field to 'struct mount'. File system modules need to be
1099 Bump __FreeBSD_version to 800093.
1102 The compiling option ADAPTIVE_SX has been retired while it has been
1103 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1104 The KPI for sx_init_flags() changes as accepting flags:
1105 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1106 been introduced in order to handle the reversed logic.
1107 Bump __FreeBSD_version to 800092.
1110 Add support for hierarchical jails. Remove global securelevel.
1111 Bump __FreeBSD_version to 800091.
1114 The layout of struct vnet_net has changed, therefore modules
1116 Bump __FreeBSD_version to 800090.
1119 The newly imported zic(8) produces a new format in the output. Please
1120 run tzsetup(8) to install the newly created data to /etc/localtime.
1123 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1124 hw.usb.* and is now consistent again with previous releases.
1127 802.11 monitor mode support was revised and driver api's were changed.
1128 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1129 of DLT_IEEE802_11. No user-visible data structures were changed but
1130 applications that use DLT_IEEE802_11 may require changes.
1131 Bump __FreeBSD_version to 800088.
1134 The layout of the following structs has changed: sysctl_oid,
1135 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1136 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1137 panics may be experienced. World rebuild is required for
1138 correctly checking networking state from userland.
1139 Bump __FreeBSD_version to 800085.
1142 MLDv2 and Source-Specific Multicast (SSM) have been merged
1143 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1144 The implementation of SSM within FreeBSD's IPv6 stack closely
1145 follows the IPv4 implementation.
1147 For kernel developers:
1149 * The most important changes are that the ip6_output() and
1150 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1151 and this lock has been downgraded to a non-recursive mutex.
1153 * As with the changes to the IPv4 stack to support SSM, filtering
1154 of inbound multicast traffic must now be performed by transport
1155 protocols within the IPv6 stack. This does not apply to TCP and
1156 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1158 * The KPIs used by IPv6 multicast are similar to those used by
1159 the IPv4 stack, with the following differences:
1160 * im6o_mc_filter() is analogous to imo_multicast_filter().
1161 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1162 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1163 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1164 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1165 for MLDv1 have an additional 'timer' argument which is used to
1166 jitter the initial membership report for the solicited-node
1167 multicast membership on-link.
1168 * This is not strictly needed for MLDv2, which already jitters
1169 its report transmissions. However, the 'timer' argument is
1170 preserved in case MLDv1 is active on the interface.
1172 * The KAME linked-list based IPv6 membership implementation has
1173 been refactored to use a vector similar to that used by the IPv4
1175 Code which maintains a list of its own multicast memberships
1176 internally, e.g. carp, has been updated to reflect the new
1179 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1180 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1181 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1182 implementation constraint which needs to be addressed in HEAD.
1184 For application developers:
1186 * The changes are broadly similar to those made for the IPv4
1189 * The use of IPv4 and IPv6 multicast socket options on the same
1190 socket, using mapped addresses, HAS NOT been tested or supported.
1192 * There are a number of issues with the implementation of various
1193 IPv6 multicast APIs which need to be resolved in the API surface
1194 before the implementation is fully compatible with KAME userland
1195 use, and these are mostly to do with interface index treatment.
1197 * The literature available discusses the use of either the delta / ASM
1198 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1199 using setsourcefilter(3)/getsourcefilter(3). For more information
1200 please refer to RFC 3768, 'Socket Interface Extensions for
1201 Multicast Source Filters'.
1203 * Applications which use the published RFC 3678 APIs should be fine.
1205 For systems administrators:
1207 * The mtest(8) utility has been refactored to support IPv6, in
1208 addition to IPv4. Interface addresses are no longer accepted
1209 as arguments, their names must be used instead. The utility
1210 will map the interface name to its first IPv4 address as
1211 returned by getifaddrs(3).
1213 * The ifmcstat(8) utility has also been updated to print the MLDv2
1214 endpoint state and source filter lists via sysctl(3).
1216 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1217 loopback of IPv6 multicast datagrams by default; it defaults to 1
1218 to preserve the existing behaviour. Disabling multicast loopback is
1219 recommended for optimal system performance.
1221 * The IPv6 MROUTING code has been changed to examine this sysctl
1222 instead of attempting to perform a group lookup before looping
1223 back forwarded datagrams.
1225 Bump __FreeBSD_version to 800084.
1228 Implement low-level Bluetooth HCI API.
1229 Bump __FreeBSD_version to 800083.
1232 The layout of struct malloc_type, used by modules to register new
1233 memory allocation types, has changed. Most modules will need to
1234 be rebuilt or panics may be experienced.
1235 Bump __FreeBSD_version to 800081.
1238 Anticipate overflowing inp_flags - add inp_flags2.
1239 This changes most offsets in inpcb, so checking v4 connection
1240 state will require a world rebuild.
1241 Bump __FreeBSD_version to 800080.
1244 Add an llentry to struct route and struct route_in6. Modules
1245 embedding a struct route will need to be recompiled.
1246 Bump __FreeBSD_version to 800079.
1249 The size of rt_metrics_lite and by extension rtentry has changed.
1250 Networking administration apps will need to be recompiled.
1251 The route command now supports show as an alias for get, weighting
1252 of routes, sticky and nostick flags to alter the behavior of stateful
1254 Bump __FreeBSD_version to 800078.
1257 Do not use Giant for kbdmux(4) locking. This is wrong and
1258 apparently causing more problems than it solves. This will
1259 re-open the issue where interrupt handlers may race with
1260 kbdmux(4) in polling mode. Typical symptoms include (but
1261 not limited to) duplicated and/or missing characters when
1262 low level console functions (such as gets) are used while
1263 interrupts are enabled (for example geli password prompt,
1264 mountroot prompt etc.). Disabling kbdmux(4) may help.
1267 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1268 kernel modules referencing any of the above need to be recompiled.
1269 Bump __FreeBSD_version to 800075.
1272 GEOM_PART has become the default partition slicer for storage devices,
1273 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1274 introduces some changes:
1276 MSDOS/EBR: the devices created from MSDOS extended partition entries
1277 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1278 to devices with offset-based names. fstabs may need to be modified.
1280 BSD: the "geometry does not match label" warning is harmless in most
1281 cases but it points to problems in file system misalignment with
1282 disk geometry. The "c" partition is now implicit, covers the whole
1283 top-level drive and cannot be (mis)used by users.
1285 General: Kernel dumps are now not allowed to be written to devices
1286 whose partition types indicate they are meant to be used for file
1287 systems (or, in case of MSDOS partitions, as something else than
1290 Most of these changes date approximately from 200812.
1293 The uscanner(4) driver has been removed from the kernel. This follows
1294 Linux removing theirs in 2.6 and making libusb the default interface
1295 (supported by sane).
1298 The multicast forwarding code has been cleaned up. netstat(1)
1299 only relies on KVM now for printing bandwidth upcall meters.
1300 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1301 ip6_mroute_mod respectively. The config(5) options for statically
1302 compiling this code remain the same, i.e. 'options MROUTING'.
1305 Support for the IFF_NEEDSGIANT network interface flag has been
1306 removed, which means that non-MPSAFE network device drivers are no
1307 longer supported. In particular, if_ar, if_sr, and network device
1308 drivers from the old (legacy) USB stack can no longer be built or
1312 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1313 a bunch of new language catalog files have also been added.
1314 This means that some common libc messages are now localized and
1315 they depend on the LC_MESSAGES environmental variable.
1318 The k8temp(4) driver has been renamed to amdtemp(4) since
1319 support for Family 10 and Family 11 CPU families was added.
1322 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1323 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1325 For kernel developers, the most important changes are that the
1326 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1327 and this lock has been downgraded to a non-recursive mutex.
1329 Transport protocols (UDP, Raw IP) are now responsible for filtering
1330 inbound multicast traffic according to group membership and source
1331 filters. The imo_multicast_filter() KPI exists for this purpose.
1332 Transports which do not use multicast (SCTP, TCP) already reject
1333 multicast by default. Forwarding and receive performance may improve
1334 as a mutex acquisition is no longer needed in the ip_input()
1335 low-level input path. in_addmulti() and in_delmulti() are shimmed
1336 to new KPIs which exist to support SSM in-kernel.
1338 For application developers, it is recommended that loopback of
1339 multicast datagrams be disabled for best performance, as this
1340 will still cause the lock to be taken for each looped-back
1341 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1342 be tuned to 0 to disable loopback by default; it defaults to 1
1343 to preserve the existing behaviour.
1345 For systems administrators, to obtain best performance with
1346 multicast reception and multiple groups, it is always recommended
1347 that a card with a suitably precise hash filter is used. Hash
1348 collisions will still result in the lock being taken within the
1349 transport protocol input path to check group membership.
1351 If deploying FreeBSD in an environment with IGMP snooping switches,
1352 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1353 enabled; this forces 224.0.0.0/24 group membership to be announced
1356 The size of 'struct igmpstat' has changed; netstat needs to be
1357 recompiled to reflect this.
1358 Bump __FreeBSD_version to 800070.
1361 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1362 updated to use it. This requires a buildworld/installworld in order to
1363 update the library and dependencies (usbconfig, etc). Its advisable to
1364 rebuild all ports which uses libusb. More specific directions are given
1365 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1366 libusb are no longer required and can be removed.
1369 A workaround is committed to allow the creation of System V shared
1370 memory segment of size > 2 GB on the 64-bit architectures.
1371 Due to a limitation of the existing ABI, the shm_segsz member
1372 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1373 wrong for large segments. Note that limits must be explicitly
1374 raised to allow such segments to be created.
1377 The layout of struct ifnet has changed, requiring a rebuild of all
1378 network device driver modules.
1381 The /dev handling for the new USB stack has changed, a
1382 buildworld/installworld is required for libusb20.
1385 The new USB2 stack has now been permanently moved in and all kernel and
1386 module names reverted to their previous values (eg, usb, ehci, ohci,
1387 ums, ...). The old usb stack can be compiled in by prefixing the name
1388 with the letter 'o', the old usb modules have been removed.
1389 Updating entry 20090216 for xorg and 20090215 for libmap may still
1393 The rc.conf(5) option if_up_delay has been renamed to
1394 defaultroute_delay to better reflect its purpose. If you have
1395 customized this setting in /etc/rc.conf you need to update it to
1399 xorg 7.4 wants to configure its input devices via hald which does not
1400 yet work with USB2. If the keyboard/mouse does not work in xorg then
1402 Option "AllowEmptyInput" "off"
1403 to your ServerLayout section. This will cause X to use the configured
1404 kbd and mouse sections from your xorg.conf.
1407 The GENERIC kernels for all architectures now default to the new USB2
1408 stack. No kernel config options or code have been removed so if a
1409 problem arises please report it and optionally revert to the old USB
1410 stack. If you are loading USB kernel modules or have a custom kernel
1411 that includes GENERIC then ensure that usb names are also changed over,
1412 eg uftdi -> usb2_serial_ftdi.
1414 Older programs linked against the ports libusb 0.1 need to be
1415 redirected to the new stack's libusb20. /etc/libmap.conf can
1417 # Map old usb library to new one for usb2 stack
1418 libusb-0.1.so.8 libusb20.so.1
1421 All USB ethernet devices now attach as interfaces under the name ueN
1422 (eg. ue0). This is to provide a predictable name as vendors often
1423 change usb chipsets in a product without notice.
1426 The ichsmb(4) driver has been changed to require SMBus slave
1427 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1428 All of the other SMBus controller drivers require left-justified
1429 slave addresses, so this change makes all the drivers provide the
1433 INET6 statistics (struct ip6stat) was updated.
1434 netstat(1) needs to be recompiled.
1437 NTFS has been removed from GENERIC kernel on amd64 to match
1438 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1439 will load ntfs.ko module automatically when NTFS support is
1440 actually needed, unless ntfs.ko is not installed or security
1441 level prohibits loading kernel modules. If either is the case,
1442 "options NTFS" has to be added into kernel config.
1445 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1446 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1447 800061. User space tools that rely on the size of struct tcpcb in
1448 tcp_var.h (e.g. sockstat) need to be recompiled.
1451 ng_tty(4) module updated to match the new TTY subsystem.
1452 Due to API change, user-level applications must be updated.
1453 New API support added to mpd5 CVS and expected to be present
1454 in next mpd5.3 release.
1457 With __FreeBSD_version 800060 the makefs tool is part of
1458 the base system (it was a port).
1461 The afdata and ifnet locks have been changed from mutexes to
1462 rwlocks, network modules will need to be re-compiled.
1465 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1466 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1467 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1468 architecture and 40 bytes on 64-bit architecture. The userland
1469 applications "arp" and "ndp" have been updated accordingly.
1470 The output from "netstat -r" shows only routing entries and
1471 none of the L2 information.
1474 __FreeBSD_version 800057 marks the switchover from the
1475 binary ath hal to source code. Users must add the line:
1477 options AH_SUPPORT_AR5416
1479 to their kernel config files when specifying:
1483 The ath_hal module no longer exists; the code is now compiled
1484 together with the driver in the ath module. It is now
1485 possible to tailor chip support (i.e. reduce the set of chips
1486 and thereby the code size); consult ath_hal(4) for details.
1489 __FreeBSD_version 800054 adds memory barriers to
1490 <machine/atomic.h>, new interfaces to ifnet to facilitate
1491 multiple hardware transmit queues for cards that support
1492 them, and a lock-less ring-buffer implementation to
1493 enable drivers to more efficiently manage queueing of
1497 A new version of ZFS (version 13) has been merged to -HEAD.
1498 This version has zpool attribute "listsnapshots" off by
1499 default, which means "zfs list" does not show snapshots,
1500 and is the same as Solaris behavior.
1503 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1506 The uhci, ohci, ehci and slhci USB Host controller drivers have
1507 been put into separate modules. If you load the usb module
1508 separately through loader.conf you will need to load the
1509 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1510 controller add the following to loader.conf:
1516 The ABI used by the PMC toolset has changed. Please keep
1517 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1521 atapci kernel module now includes only generic PCI ATA
1522 driver. AHCI driver moved to ataahci kernel module.
1523 All vendor-specific code moved into separate kernel modules:
1524 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1525 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1526 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1527 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1530 The TTY subsystem of the kernel has been replaced by a new
1531 implementation, which provides better scalability and an
1532 improved driver model. Most common drivers have been migrated to
1533 the new TTY subsystem, while others have not. The following
1534 drivers have not yet been ported to the new TTY layer:
1537 cy, digi, rc, rp, sio
1543 ng_h4, ng_tty, ppp, sl, snp
1545 Adding these drivers to your kernel configuration file shall
1546 cause compilation to fail.
1549 ntpd has been upgraded to 4.2.4p5.
1552 OpenSSH has been upgraded to 5.1p1.
1554 For many years, FreeBSD's version of OpenSSH preferred DSA
1555 over RSA for host and user authentication keys. With this
1556 upgrade, we've switched to the vendor's default of RSA over
1557 DSA. This may cause upgraded clients to warn about unknown
1558 host keys even for previously known hosts. Users should
1559 follow the usual procedure for verifying host keys before
1560 accepting the RSA key.
1562 This can be circumvented by setting the "HostKeyAlgorithms"
1563 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1566 Please note that the sequence of keys offered for
1567 authentication has been changed as well. You may want to
1568 specify IdentityFile in a different order to revert this
1572 The sio(4) driver has been removed from the i386 and amd64
1573 kernel configuration files. This means uart(4) is now the
1574 default serial port driver on those platforms as well.
1576 To prevent collisions with the sio(4) driver, the uart(4) driver
1577 uses different names for its device nodes. This means the
1578 onboard serial port will now most likely be called "ttyu0"
1579 instead of "ttyd0". You may need to reconfigure applications to
1580 use the new device names.
1582 When using the serial port as a boot console, be sure to update
1583 /boot/device.hints and /etc/ttys before booting the new kernel.
1584 If you forget to do so, you can still manually specify the hints
1585 at the loader prompt:
1587 set hint.uart.0.at="isa"
1588 set hint.uart.0.port="0x3F8"
1589 set hint.uart.0.flags="0x10"
1590 set hint.uart.0.irq="4"
1594 The gpt(8) utility has been removed. Use gpart(8) to partition
1598 The version that Linuxulator emulates was changed from 2.4.2
1599 to 2.6.16. If you experience any problems with Linux binaries
1600 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1601 if it fixes the problem contact emulation mailing list.
1604 ISDN4BSD (I4B) was removed from the src tree. You may need to
1605 update a your kernel configuration and remove relevant entries.
1608 I have checked in code to support multiple routing tables.
1609 See the man pages setfib(1) and setfib(2).
1610 This is a hopefully backwards compatible version,
1611 but to make use of it you need to compile your kernel
1612 with options ROUTETABLES=2 (or more up to 16).
1615 The 802.11 wireless support was redone to enable multi-bss
1616 operation on devices that are capable. The underlying device
1617 is no longer used directly but instead wlanX devices are
1618 cloned with ifconfig. This requires changes to rc.conf files.
1619 For example, change:
1620 ifconfig_ath0="WPA DHCP"
1623 ifconfig_wlan0="WPA DHCP"
1624 see rc.conf(5) for more details. In addition, mergemaster of
1625 /etc/rc.d is highly recommended. Simultaneous update of userland
1626 and kernel wouldn't hurt either.
1628 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1629 modules were merged into the base wlan module. All references
1630 to these modules (e.g. in kernel config files) must be removed.
1633 psm(4) has gained write(2) support in native operation level.
1634 Arbitrary commands can be written to /dev/psm%d and status can
1635 be read back from it. Therefore, an application is responsible
1636 for status validation and error recovery. It is a no-op in
1637 other operation levels.
1640 Support for KSE threading has been removed from the kernel. To
1641 run legacy applications linked against KSE libmap.conf may
1642 be used. The following libmap.conf may be used to ensure
1643 compatibility with any prior release:
1645 libpthread.so.1 libthr.so.1
1646 libpthread.so.2 libthr.so.2
1647 libkse.so.3 libthr.so.3
1650 The layout of struct vmspace has changed. This affects libkvm
1651 and any executables that link against libkvm and use the
1652 kvm_getprocs() function. In particular, but not exclusively,
1653 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1654 The effects are minimal, but it's advisable to upgrade world
1658 The latest em driver no longer has support in it for the
1659 82575 adapter, this is now moved to the igb driver. The
1660 split was done to make new features that are incompatible
1661 with older hardware easier to do.
1664 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1665 likewise the kernel option is now GEOM_LINUX_LVM.
1668 The default NFS mount mode has changed from UDP to TCP for
1669 increased reliability. If you rely on (insecurely) NFS
1670 mounting across a firewall you may need to update your
1674 Belatedly note the addition of m_collapse for compacting
1678 The fts(3) structures have been changed to use adequate
1679 integer types for their members and so to be able to cope
1680 with huge file trees. The old fts(3) ABI is preserved
1681 through symbol versioning in libc, so third-party binaries
1682 using fts(3) should still work, although they will not take
1683 advantage of the extended types. At the same time, some
1684 third-party software might fail to build after this change
1685 due to unportable assumptions made in its source code about
1686 fts(3) structure members. Such software should be fixed
1687 by its vendor or, in the worst case, in the ports tree.
1688 FreeBSD_version 800015 marks this change for the unlikely
1689 case that a portable fix is impossible.
1692 To upgrade to -current after this date, you must be running
1693 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1694 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1697 The ADAPTIVE_GIANT kernel option has been retired because its
1698 functionality is the default now.
1701 The AT keyboard emulation of sunkbd(4) has been turned on
1702 by default. In order to make the special symbols of the Sun
1703 keyboards driven by sunkbd(4) work under X these now have
1704 to be configured the same way as Sun USB keyboards driven
1705 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1707 Option "XkbLayout" "us"
1708 Option "XkbRules" "xorg"
1709 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1712 It has been decided that it is desirable to provide ABI
1713 backwards compatibility to the FreeBSD 4/5/6 versions of the
1714 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1715 broken with the introduction of PCI domain support (see the
1716 20070930 entry). Unfortunately, this required the ABI of
1717 PCIOCGETCONF to be broken again in order to be able to
1718 provide backwards compatibility to the old version of that
1719 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1720 again. As for prominent ports this affects neither pciutils
1721 nor xorg-server this time, the hal port needs to be rebuilt
1725 The misnamed kthread_create() and friends have been renamed
1726 to kproc_create() etc. Many of the callers already
1727 used kproc_start()..
1728 I will return kthread_create() and friends in a while
1729 with implementations that actually create threads, not procs.
1730 Renaming corresponds with version 800002.
1739 Avoid using make -j when upgrading. While generally safe, there are
1740 sometimes problems using -j to upgrade. If your upgrade fails with
1741 -j, please try again without -j. From time to time in the past there
1742 have been problems using -j with buildworld and/or installworld. This
1743 is especially true when upgrading between "distant" versions (eg one
1744 that cross a major release boundary or several minor releases, or when
1745 several months have passed on the -current branch).
1747 Sometimes, obscure build problems are the result of environment
1748 poisoning. This can happen because the make utility reads its
1749 environment when searching for values for global variables. To run
1750 your build attempts in an "environmental clean room", prefix all make
1751 commands with 'env -i '. See the env(1) manual page for more details.
1753 When upgrading from one major version to another it is generally best
1754 to upgrade to the latest code in the currently installed branch first,
1755 then do an upgrade to the new branch. This is the best-tested upgrade
1756 path, and has the highest probability of being successful. Please try
1757 this approach before reporting problems with a major version upgrade.
1759 When upgrading a live system, having a root shell around before
1760 installing anything can help undo problems. Not having a root shell
1761 around can lead to problems if pam has changed too much from your
1762 starting point to allow continued authentication after the upgrade.
1766 When upgrading the boot ZFS pool to a new version, always follow
1769 1.) recompile and reinstall the ZFS boot loader and boot block
1770 (this is part of "make buildworld" and "make installworld")
1772 2.) update the ZFS boot block on your boot drive
1774 The following example updates the ZFS boot block on the first
1775 partition (freebsd-boot) of a GPT partitioned drive ad0:
1776 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1778 Non-boot pools do not need these updates.
1782 If you are updating from a prior version of FreeBSD (even one just
1783 a few days old), you should follow this procedure. It is the most
1784 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1786 make kernel-toolchain
1787 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1788 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1790 To test a kernel once
1791 ---------------------
1792 If you just want to boot a kernel once (because you are not sure
1793 if it works, or if you want to boot a known bad kernel to provide
1794 debugging information) run
1795 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1796 nextboot -k testkernel
1798 To just build a kernel when you know that it won't mess you up
1799 --------------------------------------------------------------
1800 This assumes you are already running a CURRENT system. Replace
1801 ${arch} with the architecture of your machine (e.g. "i386",
1802 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1804 cd src/sys/${arch}/conf
1805 config KERNEL_NAME_HERE
1806 cd ../compile/KERNEL_NAME_HERE
1811 If this fails, go to the "To build a kernel" section.
1813 To rebuild everything and install it on the current system.
1814 -----------------------------------------------------------
1815 # Note: sometimes if you are running current you gotta do more than
1816 # is listed here if you are upgrading from a really old current.
1818 <make sure you have good level 0 dumps>
1820 make kernel KERNCONF=YOUR_KERNEL_HERE
1822 <reboot in single user> [3]
1829 To cross-install current onto a separate partition
1830 --------------------------------------------------
1831 # In this approach we use a separate partition to hold
1832 # current's root, 'usr', and 'var' directories. A partition
1833 # holding "/", "/usr" and "/var" should be about 2GB in
1836 <make sure you have good level 0 dumps>
1839 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1840 <maybe newfs current's root partition>
1841 <mount current's root partition on directory ${CURRENT_ROOT}>
1842 make installworld DESTDIR=${CURRENT_ROOT}
1843 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1844 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1845 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1846 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1847 <reboot into current>
1848 <do a "native" rebuild/install as described in the previous section>
1849 <maybe install compatibility libraries from ports/misc/compat*>
1853 To upgrade in-place from stable to current
1854 ----------------------------------------------
1855 <make sure you have good level 0 dumps>
1857 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1859 <reboot in single user> [3]
1866 Make sure that you've read the UPDATING file to understand the
1867 tweaks to various things you need. At this point in the life
1868 cycle of current, things change often and you are on your own
1869 to cope. The defaults can also change, so please read ALL of
1870 the UPDATING entries.
1872 Also, if you are tracking -current, you must be subscribed to
1873 freebsd-current@freebsd.org. Make sure that before you update
1874 your sources that you have read and understood all the recent
1875 messages there. If in doubt, please track -stable which has
1876 much fewer pitfalls.
1878 [1] If you have third party modules, such as vmware, you
1879 should disable them at this point so they don't crash your
1882 [3] From the bootblocks, boot -s, and then do
1887 adjkerntz -i # if CMOS is wall time
1888 Also, when doing a major release upgrade, it is required that
1889 you boot into single user mode to do the installworld.
1891 [4] Note: This step is non-optional. Failure to do this step
1892 can result in a significant reduction in the functionality of the
1893 system. Attempting to do it by hand is not recommended and those
1894 that pursue this avenue should read this file carefully, as well
1895 as the archives of freebsd-current and freebsd-hackers mailing lists
1896 for potential gotchas. The -U option is also useful to consider.
1897 See mergemaster(8) for more information.
1899 [5] Usually this step is a noop. However, from time to time
1900 you may need to do this if you get unknown user in the following
1901 step. It never hurts to do it all the time. You may need to
1902 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1903 install) after the buildworld before this step if you last updated
1904 from current before 20130425 or from -stable before 20130430.
1906 [6] This only deletes old files and directories. Old libraries
1907 can be deleted by "make delete-old-libs", but you have to make
1908 sure that no program is using those libraries anymore.
1910 [8] In order to have a kernel that can run the 4.x binaries needed to
1911 do an installworld, you must include the COMPAT_FREEBSD4 option in
1912 your kernel. Failure to do so may leave you with a system that is
1913 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1914 required to run the 5.x binaries on more recent kernels. And so on
1915 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1917 Make sure that you merge any new devices from GENERIC since the
1918 last time you updated your kernel config file.
1920 [9] When checking out sources, you must include the -P flag to have
1921 cvs prune empty directories.
1923 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1924 "?=" instead of the "=" assignment operator, so that buildworld can
1925 override the CPUTYPE if it needs to.
1927 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1928 not on the command line, or in /etc/make.conf. buildworld will
1929 warn if it is improperly defined.
1932 This file contains a list, in reverse chronological order, of major
1933 breakages in tracking -current. It is not guaranteed to be a complete
1934 list of such breakages, and only contains entries since October 10, 2007.
1935 If you need to see UPDATING entries from before that date, you will need
1936 to fetch an UPDATING file from an older FreeBSD release.
1938 Copyright information:
1940 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1942 Redistribution, publication, translation and use, with or without
1943 modification, in full or in part, in any form or format of this
1944 document are permitted without further permission from the author.
1946 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1947 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1948 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1949 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1950 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1951 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1952 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1953 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1954 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1955 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1956 POSSIBILITY OF SUCH DAMAGE.
1958 Contact Warner Losh if you have any questions about your use of