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 20160310 p38 FreeBSD-SA-16:13.bind
15 FreeBSD-SA-16:12.openssl [revised]
17 Fix multiple vulnerabilities of BIND. [SA-16:13]
19 Fix a regression with OpenSSL patch. [SA-16:12]
21 20160303 p37 FreeBSD-SA-16:12.openssl
23 Fix multiple vulnerabilities of OpenSSL.
25 20160130 p36 FreeBSD-SA-16:11.openssl
27 Fix OpenSSL SSLv2 ciphersuite downgrade vulnerability. [SA-16:11]
29 20160127 p35 FreeBSD-SA-16:08.bind
31 FreeBSD-SA-16:10.linux
33 Fix BIND remote denial of service vulnerability. [SA-16:08]
35 Fix multiple vulnerabilities of ntp. [SA-16:09]
37 Fix Linux compatibility layer issetugid(2) system call
38 vulnerability. [SA-16:10]
40 20160114 p34 FreeBSD-SA-16:07.openssh
42 Fix OpenSSH client information leak. [SA-16:07]
44 20160114 p33 FreeBSD-EN-16:02.pf
45 FreeBSD-EN-16:03.yplib
48 FreeBSD-SA-16:03.linux
49 FreeBSD-SA-16:04.linux
51 FreeBSD-SA-16:06.bsnmpd
53 Fix pf(4) generating bad TCP checksums. [EN-16:02]
54 Fix infinite loop in YP/NIS client library. [EN-16:03]
55 Fix remote denial of service in SCTP. [SA-16:01]
56 Update NTP to 4.2.8p5. [SA-16:02]
57 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
58 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
59 Fix crash in TCP MD5 signatures. [SA-16:05]
60 Fix insecure default permissions for snmpd.config. [SA-16:06]
62 20151216 p32 FreeBSD-SA-15:27.bind
63 Fix BIND remote denial of service vulnerability. [SA-15:27]
65 20151205 p31 FreeBSD-SA-15:26.openssl
67 Fix OpenSSL X509_ATTRIBUTE memory leak. [SA-15:26]
69 20151104 p30 FreeBSD-SA-15:25.ntp [revised]
70 FreeBSD-EN-15:19.kqueue
73 Fix regression of ntpq(8) utility exiting due to trap 6 in
74 9.3-RELEASE-p29. [SA-15:25]
76 Fix regression in ntpd(8) lacking support for RAWDCF reference
77 clock in 9.3-RELEASE-p29. [SA-15:25]
79 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
81 Fix applications exiting due to segmentation violation on a correct
82 memory address. [EN-15:20]
84 20151026: p29 FreeBSD-SA-15:25.ntp
86 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
88 The configuration file syntax has been changed, thus mergemaster
89 run is recommended. Now the "kod" parameter requires "limited"
90 parameter. If the ntp.conf is not updated, the ntpd will run
91 successfully, but with KoD disabled.
93 20151002: p28 FreeBSD-SA-15:24.rpcbind [revised]
94 Revised patch to address a regression that prevents NIS from working.
96 20150929: p27 FreeBSD-SA-15:24.rpcbind
98 Fix rpcbind(8) remote denial of service. [SA-15:24]
100 20150916: p26 FreeBSD-EN-15:18.pkg
102 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
104 20150902: p25 FreeBSD-SA-15:23.bind
106 Fix BIND remote denial of service vulnerability. [SA-15:23]
108 20150825: p24 FreeBSD-SA-15:21.amd64
109 FreeBSD-SA-15:22.openssh
112 Fix local privilege escalation in IRET handler. [SA-15:21]
114 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
116 Fix insufficient check of unsupported pkg(7) signature methods.
119 20150818: p23 FreeBSD-SA-15:20.expat
121 Fix multiple integer overflows in expat (libbsdxml) XML parser.
124 20150805: p22 FreeBSD-SA-15:19.routed
126 Fix routed remote denial of service vulnerability.
128 20150728: p21 FreeBSD-SA-15:15.tcp
129 FreeBSD-SA-15:16.openssh
130 FreeBSD-SA-15:17.bind
132 Fix resource exhaustion in TCP reassembly. [SA-15:15]
134 Fix OpenSSH multiple vulnerabilities. [SA-15:16]
136 Fix BIND remote denial of service vulnerability. [SA-15:17]
138 20150721: p20 FreeBSD-SA-15:13.tcp
140 Fix resource exhaustion due to sessions stuck in LAST_ACK state.
143 20150707: p19 FreeBSD-SA-15:11.bind
144 Fix BIND resolver remote denial of service when validating.
146 20150630: p18 FreeBSD-EN-15:08.sendmail [revised]
147 FreeBSD-EN-15:09.xlocale
149 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
151 Fix inconsistency between locale and rune locale states.
154 20150618: p17 FreeBSD-EN-15:08.sendmail
155 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
157 20150612: p16 FreeBSD-SA-15:10.openssl
158 Fix multiple vulnerabilities in OpenSSL. [SA-15:10]
160 20150609: p15 FreeBSD-EN-15:06.file
162 Updated base system file(1) to 5.22 to address multiple denial
165 20150513: p14 FreeBSD-EN-15:04.freebsd-update
167 Fix bug with freebsd-update(8) that does not ensure the previous
168 upgrade was completed. [EN-15:04]
170 20150407: p13 FreeBSD-SA-15:04.igmp [revised]
172 FreeBSD-SA-15:09.ipv6
174 Improved patch for SA-15:04.igmp.
176 Fix multiple vulnerabilities of ntp. [SA-15:07]
178 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
181 Fix patch for SA-15:06.openssl.
183 20150319: p11 FreeBSD-SA-15:06.openssl
184 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
186 20150225: p10 FreeBSD-SA-15:04.igmp
187 FreeBSD-SA-15:05.bind
189 FreeBSD-EN-15:02.openssl
190 FreeBSD-EN-15:03.freebsd-update
192 Fix integer overflow in IGMP protocol. [SA-15:04]
194 Fix BIND remote denial of service vulnerability. [SA-15:05]
196 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
198 Updated base system OpenSSL to 0.9.8zd. [EN-15:02]
200 Fix freebsd-update libraries update ordering issue. [EN-15:03]
202 20150127: p9 FreeBSD-SA-15:02.kmem
203 FreeBSD-SA-15:03.sctp
205 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
206 vulnerability. [SA-15:02]
208 Fix SCTP stream reset vulnerability. [SA-15:03]
210 20150114: p8 FreeBSD-SA-15:01.openssl
211 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
213 20141223: p7 FreeBSD-SA-14:31.ntp
214 FreeBSD-EN-14:13.freebsd-update
216 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
217 Fix directory deletion issue in freebsd-update. [EN-14:13]
219 20141210: p6 FreeBSD-SA-14:28.file
220 FreeBSD-SA-14:29.bind
222 Fix multiple vulnerabilities in file(1) and libmagic(3).
225 Fix BIND remote denial of service vulnerability. [SA-14:29]
227 20141104: p5 FreeBSD-SA-14:25.setlogin
231 Fix kernel stack disclosure in setlogin(2) / getlogin(2).
234 Fix remote command execution in ftp(1). [SA-14:26]
236 Fix NFSv4 and ZFS cache consistency issue. [EN-14:12]
238 20141022: p4 FreeBSD-EN-14:10.tzdata
239 FreeBSD-EN-14:11.crypt
241 Time zone data file update. [EN-14:10]
243 Change crypt(3) default hashing algorithm back to DES. [EN-14:11]
245 20141021: p3 FreeBSD-SA-14:20.rtsold
246 FreeBSD-SA-14:21.routed
247 FreeBSD-SA-14:22.namei
248 FreeBSD-SA-14:23.openssl
250 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
252 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
254 Fix memory leak in sandboxed namei lookup. [SA-14:22]
256 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
258 20140916: p2 FreeBSD-SA-14:19.tcp
259 Fix Denial of Service in TCP packet processing. [SA-14:19]
261 20140909: p1 FreeBSD-SA-14:18.openssl
262 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
268 On i386 and amd64 systems, the onifconsole flag is now set by default
269 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
270 as a login TTY if it is set in the bootloader as an active kernel
271 console. No changes in behavior should result otherwise. To revert to
272 the previous behavior, set ttyu0 to "off" in /etc/ttys.
275 Clang and llvm have been upgraded to 3.4.1 release.
278 Clang and llvm have been upgraded to 3.4 release.
281 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
282 been deprecated and will not be part of FreeBSD 11.0 and later
283 releases. If you use this driver, please consider switching to
284 the nfe(4) driver instead.
287 The behavior of gss_pseudo_random() for the krb5 mechanism
288 has changed, for applications requesting a longer random string
289 than produced by the underlying enctype's pseudo-random() function.
290 In particular, the random string produced from a session key of
291 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
292 be different at the 17th octet and later, after this change.
293 The counter used in the PRF+ construction is now encoded as a
294 big-endian integer in accordance with RFC 4402.
295 __FreeBSD_version is bumped to 902505.
301 Behavior of devfs rules path matching has been changed.
302 Pattern is now always matched against fully qualified devfs
303 path and slash characters must be explicitly matched by
304 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
305 subdirectories must be reviewed.
308 hastctl(8)'s `status' command output changed to terse one-liner format.
309 Scripts using this should switch to `list' command or be rewritten.
312 Fix a bug that allowed a tracing process (e.g. gdb) to write
313 to a memory-mapped file in the traced process's address space
314 even if neither the traced process nor the tracing process had
315 write access to that file.
318 Added ZFS TRIM support which is enabled by default. To disable
319 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
321 Creating new ZFS pools and adding new devices to existing pools
322 first performs a full device level TRIM which can take a significant
323 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
324 to disable this behaviour.
326 ZFS TRIM requires the underlying device support BIO_DELETE which
327 is currently provided by methods such as ATA TRIM and SCSI UNMAP
328 via CAM, which are typically supported by SSD's.
330 Stats for ZFS TRIM can be monitored by looking at the sysctl's
331 under kstat.zfs.misc.zio_trim.
334 `list' command has been added to hastctl(8). For now, it is full
335 equivalent of `status' command.
336 WARNING: in the near future the output of hastctl's status command
337 will change to more terse format. If you use `hastctl status'
338 for parsing in your scripts, switch to `hastctl list'.
341 The mergemaster command now uses the default MAKEOBJDIRPREFIX
342 rather than creating it's own in the temporary directory in
343 order allow access to bootstrapped versions of tools such as
344 install and mtree. When upgrading from version of FreeBSD where
345 the install command does not support -l, you will need to
346 install a new mergemaster command if mergemaster -p is required.
347 This can be accomplished with the command (cd src/usr.sbin/mergemaster
350 Due to the use of the new -l option to install(1) during build
351 and install, you must take care not to directly set the INSTALL
352 make variable in your /etc/make.conf, /etc/src.conf, or on the
353 command line. If you wish to use the -C flag for all installs
354 you may be able to add INSTALL+=-C to /etc/make.conf or
358 Fix a bug that allows NFS clients to issue READDIR on files.
361 The install(1) option -M has changed meaning and now takes an
362 argument that is a file or path to append logs to. In the
363 unlikely event that -M was the last option on the command line
364 and the command line contained at least two files and a target
365 directory the first file will have logs appended to it. The -M
366 option served little practical purpose in the last decade so it's
367 used expected to be extremely rare.
370 A new compression method (lz4) has been merged to. Please refer to
371 zpool-features(7) for more information.
373 Please refer to the "ZFS notes" section of this file for information
374 on upgrading boot ZFS pools.
377 The VFS KBI was changed with the merge of several nullfs
378 optimizations and fixes. All filesystem modules must be
382 With the addition of auditdistd(8), a new auditdistd user is now
383 depended on during installworld. "mergemaster -p" can be used to add
384 the user prior to installworld, as documented in the handbook.
390 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
391 Starting with this version the old system of ZFS pool versioning
392 is superseded by "feature flags". This concept enables forward
393 compatibility against certain future changes in functionality of ZFS
394 pools. The first two read-only compatible "feature flags" for ZFS
395 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
396 For more information read the new zpool-features(7) manual page.
397 Please refer to the "ZFS notes" section of this file for information
398 on upgrading boot ZFS pools.
401 The commit introducing bsd.compiler.mk breaks the traditional
402 building of kernels before this point. Add -m ${SRC}/share/mk
403 (for the right value of SRC) to your command lines to work
404 around; update your useland to a point after this; or use the
405 buildkernel/installkernel top-level targets. See also 20120829.
408 The IPFIREWALL_FORWARD kernel option has been removed. Its
409 functionality now turned on by default.
412 The random(4) support for the VIA hardware random number
413 generator (`PADLOCK') is no longer enabled unconditionally.
414 Add the PADLOCK_RNG option in the custom kernel config if
415 needed. The GENERIC kernels on i386 and amd64 do include the
416 option, so the change only affects the custom kernel
420 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
421 the traditional method, you must update your system with an installworld
422 before the kernel will build. The documented make buildkernel/installkernel
423 interfaces (coupled with fresh make kernel-toolchain) continue to work.
426 The sparc64 ZFS loader has been changed to no longer try to auto-
427 detect ZFS providers based on diskN aliases but now requires these
428 to be explicitly listed in the OFW boot-device environment variable.
431 Now unix domain sockets behave "as expected" on nullfs(5). Previously
432 nullfs(5) did not pass through all behaviours to the underlying layer,
433 as a result if we bound to a socket on the lower layer we could connect
434 only to the lower path; if we bound to the upper layer we could connect
435 only to the upper path. The new behavior is one can connect to both the
436 lower and the upper paths regardless what layer path one binds to.
439 The acpi_wmi(4) status device /dev/wmistat has been renamed to
443 A new VOP_ADVISE() was added to support posix_fadvise(2). All
444 filesystem modules must be recompiled.
447 The interface of the VOP_VPTOCNP(9) changed, now the returned
448 vnode shall be referenced, previously it was required to be
449 only held. All in-tree filesystems are converted.
455 The broken amd(4) driver has been replaced with esp(4) in the amd64,
456 i386 and pc98 GENERIC kernel configuration files.
459 This commit modifies vfs_register() so that it uses a hash
460 calculation to set vfc_typenum, which is enabled by default.
461 The first time a system is booted after this change, the
462 vfc_typenum values will change for all file systems. The
463 main effect of this is a change to the NFS server file handles
464 for file systems that use vfc_typenum in their fsid, such as ZFS.
465 It will, however, prevent vfc_typenum from changing when file
466 systems are loaded in a different order for subsequent reboots.
467 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
468 until you are ready to remount all NFS clients after a reboot.
471 Bump the shared library version numbers for libraries that
472 do not use symbol versioning, have changed the ABI compared
473 to stable/8 and which shared library version was not bumped.
474 Done as part of 9.0-RELEASE cycle.
477 During the merge of Capsicum features, the fget(9) KPI was modified.
478 This may require the rebuilding of out-of-tree device drivers --
479 issues have been reported specifically with the nVidia device driver.
480 __FreeBSD_version is bumped to 900041.
482 Also, there is a period between 20110811 and 20110814 where the
483 special devices /dev/{stdin,stdout,stderr} did not work correctly.
484 Building world from a kernel during that window may not work.
487 The packet filter (pf) code has been updated to OpenBSD 4.5.
488 You need to update userland tools to be in sync with kernel.
489 This update breaks backward compatibility with earlier pfsync(4)
490 versions. Care must be taken when updating redundant firewall setups.
493 The following sysctls and tunables are retired on x86 platforms:
495 machdep.hlt_logical_cpus
496 The following sysctl is retired:
497 machdep.hyperthreading_allowed
498 The sysctls were supposed to provide a way to dynamically offline and
499 online selected CPUs on x86 platforms, but the implementation has not
500 been reliable especially with SCHED_ULE scheduler.
501 machdep.hyperthreading_allowed tunable is still available to ignore
502 hyperthreading CPUs at OS level.
503 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
504 where X is an APIC ID of a CPU. Be advised, though, that disabling
505 CPUs in non-uniform fashion will result in non-uniform topology and
506 may lead to sub-optimal system performance with SCHED_ULE, which is
510 cpumask_t type is retired and cpuset_t is used in order to describe
514 Changes to ifconfig(8) for dynamic address family detection mandate
515 that you are running a kernel of 20110525 or later. Make sure to
516 follow the update procedure to boot a new kernel before installing
520 Support for sun4v architecture is officially dropped
523 Several KPI breaking changes have been committed to the mii(4) layer,
524 the PHY drivers and consequently some Ethernet drivers using mii(4).
525 This means that miibus.ko and the modules of the affected Ethernet
526 drivers need to be recompiled.
528 Note to kernel developers: Given that the OUI bit reversion problem
529 was fixed as part of these changes all mii(4) commits related to OUIs,
530 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
531 handling, no longer can be merged verbatim to stable/8 and previous
535 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
536 into their kernel configurations along with 'device pci'.
539 The default NFS client is now the new NFS client, so fstype "newnfs"
540 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
541 Although mounts via fstype "nfs" will usually work without userland
542 changes, it is recommended that the mount(8) and mount_nfs(8)
543 commands be rebuilt from sources and that a link to mount_nfs called
544 mount_oldnfs be created. The new client is compiled into the
545 kernel with "options NFSCL" and this is needed for diskless root
546 file systems. The GENERIC kernel configs have been changed to use
547 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
548 To use the regular/old client, you can "mount -t oldnfs ...". For
549 a diskless root file system, you must also include a line like:
551 vfs.root.mountfrom="oldnfs:"
553 in the boot/loader.conf on the root fs on the NFS server to make
554 a diskless root fs use the old client.
557 The GENERIC kernels for all architectures now default to the new
558 CAM-based ATA stack. It means that all legacy ATA drivers were
559 removed and replaced by respective CAM drivers. If you are using
560 ATA device names in /etc/fstab or other places, make sure to update
561 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
562 where 'Y's are the sequential numbers starting from zero for each type
563 in order of detection, unless configured otherwise with tunables,
564 see cam(4)). There will be symbolic links created in /dev/ to map
565 old adX devices to the respective adaY. They should provide basic
566 compatibility for file systems mounting in most cases, but they do
567 not support old user-level APIs and do not have respective providers
568 in GEOM. Consider using updated management tools with new device names.
570 It is possible to load devices ahci, ata, siis and mvs as modules,
571 but option ATA_CAM should remain in kernel configuration to make ata
572 module work as CAM driver supporting legacy ATA controllers. Device ata
573 still can be used in modular fashion (atacore + ...). Modules atadisk
574 and atapi* are not used and won't affect operation in ATA_CAM mode.
575 Note that to use CAM-based ATA kernel should include CAM devices
576 scbus, pass, da (or explicitly ada), cd and optionally others. All of
577 them are parts of the cam module.
579 ataraid(4) functionality is now supported by the RAID GEOM class.
580 To use it you can load geom_raid kernel module and use graid(8) tool
581 for management. Instead of /dev/arX device names, use /dev/raid/rX.
583 No kernel config options or code have been removed, so if a problem
584 arises, please report it and optionally revert to the old ATA stack.
585 In order to do it you can remove from the kernel config:
590 , and instead add back:
591 device atadisk # ATA disk drives
592 device ataraid # ATA RAID drives
593 device atapicd # ATAPI CDROM drives
594 device atapifd # ATAPI floppy drives
595 device atapist # ATAPI tape drives
598 The default NFS server has been changed to the new server, which
599 was referred to as the experimental server. If you need to switch
600 back to the old NFS server, you must now put the "-o" option on
601 both the mountd and nfsd commands. This can be done using the
602 mountd_flags and nfs_server_flags rc.conf variables until an
603 update to the rc scripts is committed, which is coming soon.
606 The GNU Objective-C runtime library (libobjc), and other Objective-C
607 related components have been removed from the base system. If you
608 require an Objective-C library, please use one of the available ports.
611 ath(4) has been split into bus- and device- modules. if_ath contains
612 the HAL, the TX rate control and the network device code. if_ath_pci
613 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
614 contains the AHB glue. Users need to load both if_ath_pci and if_ath
615 in order to use ath on everything else.
617 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
618 need to load if_ath and if_ath_pci for ath(4) operation.
621 As part of the replacement of sysinstall, the process of building
622 release media has changed significantly. For details, please re-read
623 release(7), which has been updated to reflect the new build process.
626 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
627 is the last available version under GPLv2. It brings a number of new
628 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
629 4.1 and SSE 4.2), better support for powerpc64, a number of new
630 directives, and lots of other small improvements. See the ChangeLog
631 file in contrib/binutils for the full details.
634 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
635 compliant, and will now use half of hash for authentication.
636 This will break interoperability with all stacks (including all
637 actual FreeBSD versions) who implement
638 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
640 The only workaround with such peers is to use another HMAC
641 algorithm for IPsec ("phase 2") authentication.
644 Remove the uio_yield prototype and symbol. This function has
645 been misnamed since it was introduced and should not be
646 globally exposed with this name. The equivalent functionality
647 is now available using kern_yield(curthread->td_user_pri).
648 The function remains undocumented.
651 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
652 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
653 for scalar sysctls is defined but disabled. Code that needs
654 UQUAD to pass the type checking that must compile on older
655 systems where the define is not present can check against
656 __FreeBSD_version >= 900030.
658 The system dialog(1) has been replaced with a new version previously
659 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
660 with the previous version, but the libdialog associated with it has
661 a largely incompatible API. As such, the original version of libdialog
662 will be kept temporarily as libodialog, until its base system consumers
663 are replaced or updated. Bump __FreeBSD_version to 900030.
666 If you are trying to run make universe on a -stable system, and you get
667 the following warning:
668 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
669 unknown. config(8) likely too old."
670 or something similar to it, then you must upgrade your -stable system
671 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
672 stable/8) or build the config from the latest stable/8 branch and
673 install it on your system.
675 Prior to this date, building a current universe on 8-stable system from
676 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
677 error in the first kernel build phase. A new config on those old
678 systems will fix that problem for older versions of -current.
681 The TCP stack has been modified to allow Khelp modules to interact with
682 it via helper hook points and store per-connection data in the TCP
683 control block. Bump __FreeBSD_version to 900029. User space tools that
684 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
688 Generic IEEE 802.3 annex 31B full duplex flow control support has been
689 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
690 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
691 to take advantage of it instead of using custom implementations. This
692 means that these drivers now no longer unconditionally advertise
693 support for flow control but only do so if flow control is a selected
694 media option. This was implemented in the generic support that way in
695 order to allow flow control to be switched on and off via ifconfig(8)
696 with the PHY specific default to typically off in order to protect
697 from unwanted effects. Consequently, if you used flow control with
698 one of the above mentioned drivers you now need to explicitly enable
700 ifconfig bge0 media auto mediaopt flowcontrol
702 Along with the above mentioned changes generic support for setting
703 1000baseT master mode also has been added and brgphy(4), ciphy(4),
704 e1000phy(4) as well as ip1000phy(4) have been converted to take
705 advantage of it. This means that these drivers now no longer take the
706 link0 parameter for selecting master mode but the master media option
707 has to be used instead, for example like in the following:
708 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
710 Selection of master mode now is also available with all other PHY
711 drivers supporting 1000baseT.
714 The TCP stack has received a significant update to add support for
715 modularised congestion control and generally improve the clarity of
716 congestion control decisions. Bump __FreeBSD_version to 900025. User
717 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
718 sockstat) need to be recompiled.
721 The man(1) utility has been replaced by a new version that no longer
722 uses /etc/manpath.config. Please consult man.conf(5) for how to
723 migrate local entries to the new format.
726 The copyright strings printed by login(1) and sshd(8) at the time of a
727 new connection have been removed to follow other operating systems and
731 A workaround for a fixed ld bug has been removed in kernel code,
732 so make sure that your system ld is built from sources after
733 revision 210245 from 2010-07-19 (r211583 if building head kernel
734 on stable/8, r211584 for stable/7; both from 2010-08-21).
735 A symptom of incorrect ld version is different addresses for
736 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
739 The $ipv6_prefer variable in rc.conf(5) has been split into
740 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
742 The $ip6addrctl_policy is a variable to choose a pre-defined
743 address selection policy set by ip6addrctl(8). A value
744 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
747 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
748 flag (see an entry of 20090926) is set on an interface with no
749 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
750 security reason. If you want IPv6 link-local address on all
751 interfaces by default, set this to "YES".
753 The old ipv6_prefer="YES" is equivalent to
754 ipv6_activate_all_interfaces="YES" and
755 ip6addrctl_policy="ipv6_prefer".
758 DTrace has grown support for userland tracing. Due to this, DTrace is
759 now i386 and amd64 only.
760 dtruss(1) is now installed by default on those systems and a new
761 kernel module is needed for userland tracing: fasttrap.
762 No changes to your kernel config file are necessary to enable
763 userland tracing, but you might consider adding 'STRIP=' and
764 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
765 to have informative userland stack traces in DTrace (ustack).
768 The acpi_aiboost(4) driver has been removed in favor of the new
769 aibs(4) driver. You should update your kernel configuration file.
772 BSD grep has been imported to the base system and it is built by
773 default. It is completely BSD licensed, highly GNU-compatible, uses
774 less memory than its GNU counterpart and has a small codebase.
775 However, it is slower than its GNU counterpart, which is mostly
776 noticeable for larger searches, for smaller ones it is measurable
777 but not significant. The reason is complex, the most important factor
778 is that we lack a modern and efficient regex library and GNU
779 overcomes this by optimizing the searches internally. Future work
780 on improving the regex performance is planned, for the meantime,
781 users that need better performance, can build GNU grep instead by
782 setting the WITH_GNU_GREP knob.
785 Due to the import of powerpc64 support, all existing powerpc kernel
786 configuration files must be updated with a machine directive like this:
787 machine powerpc powerpc
789 In addition, an updated config(8) is required to build powerpc kernels
793 A new version of ZFS (version 15) has been merged to -HEAD.
794 This version uses a python library for the following subcommands:
795 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
796 For full functionality of these commands the following port must
797 be installed: sysutils/py-zfs
800 'vm_page's are now hashed by physical address to an array of mutexes.
801 Currently this is only used to serialize access to hold_count. Over
802 time the page queue mutex will be peeled away. This changes the size
803 of pmap on every architecture. And requires all callers of vm_page_hold
804 and vm_page_unhold to be updated.
807 WITH_CTF can now be specified in src.conf (not recommended, there
808 are some problems with static executables), make.conf (would also
809 affect ports which do not use GNU make and do not override the
810 compile targets) or in the kernel config (via "makeoptions
812 When WITH_CTF was specified there before this was silently ignored,
813 so make sure that WITH_CTF is not used in places which could lead
814 to unwanted behavior.
817 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
818 to allow 32-bit compatibility on non-x86 platforms. All kernel
819 configurations on amd64 and ia64 platforms using these options must
820 be modified accordingly.
823 The utmp user accounting database has been replaced with utmpx,
824 the user accounting interface standardized by POSIX.
825 Unfortunately the semantics of utmp and utmpx don't match,
826 making it practically impossible to support both interfaces.
827 The user accounting database is used by tools like finger(1),
828 last(1), talk(1), w(1) and ac(8).
830 All applications in the base system use utmpx. This means only
831 local binaries (e.g. from the ports tree) may still use these
832 utmp database files. These applications must be rebuilt to make
835 After the system has been upgraded, it is safe to remove the old
836 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
837 assuming their contents is of no importance anymore. Old wtmp
838 databases can only be used by last(1) and ac(8) after they have
839 been converted to the new format using wtmpcvt(1).
842 Introduce the kernel thread "deadlock resolver" (which can be enabled
843 via the DEADLKRES option, see NOTES for more details) and the
844 sleepq_type() function for sleepqueues.
847 The rc.firewall and rc.firewall6 were unified, and
848 rc.firewall6 and rc.d/ip6fw were removed.
849 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
850 variables are obsoleted. Instead, the following new rc
851 variables are added to rc.d/ipfw:
853 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
854 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
855 firewall_simple_onet_ipv6, firewall_trusted_ipv6
857 The meanings correspond to the relevant IPv4 variables.
863 The default terminal emulation for syscons(4) has been changed
864 from cons25 to xterm on all platforms except pc98. This means
865 that the /etc/ttys file needs to be updated to ensure correct
866 operation of applications on the console.
868 The terminal emulation style can be toggled per window by using
869 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
870 options can be used to change the compile-time default back to
873 To prevent graphical artifacts, make sure the TERM environment
874 variable is set to match the terminal emulation that is being
875 performed by syscons(4).
878 The layout of the structure ieee80211req_scan_result has changed.
879 Applications that require wireless scan results (e.g. ifconfig(8))
880 from net80211 need to be recompiled.
882 Applications such as wpa_supplicant(8) may require a full world
883 build without using NO_CLEAN in order to get synchronized with the
887 The iwn(4) driver has been updated to support the 5000 and 5150 series.
888 There's one kernel module for each firmware. Adding "device iwnfw"
889 to the kernel configuration file means including all three firmware
890 images inside the kernel. If you want to include just the one for
891 your wireless card, use the devices iwn4965fw, iwn5000fw or
895 The rc.d/network_ipv6, IPv6 configuration script has been integrated
896 into rc.d/netif. The changes are the following:
898 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
899 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
900 Note that both variables need the "inet6" keyword at the head.
902 Do not set $ipv6_network_interfaces manually if you do not
903 understand what you are doing. It is not needed in most cases.
905 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
908 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
909 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
911 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
912 all configured interfaces have "inet6 accept_rtadv" in the
913 $ifconfig_IF_ipv6. These are for backward compatibility.
915 3. A new variable $ipv6_prefer has been added. If NO, IPv6
916 functionality of interfaces with no corresponding
917 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
918 and the default address selection policy of ip6addrctl(8)
919 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
920 Note that if you want to configure IPv6 functionality on the
921 disabled interfaces after boot, first you need to clear the flag by
922 using ifconfig(8) like:
924 ifconfig em0 inet6 -ifdisabled
926 If YES, the default address selection policy is set as
929 The default value of $ipv6_prefer is NO.
931 4. If your system need to receive Router Advertisement messages,
932 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
933 scripts automatically invoke rtsol(8) when the interface becomes
934 UP. The Router Advertisement messages are used for SLAAC
935 (State-Less Address AutoConfiguration).
938 802.11s D3.03 support was committed. This is incompatible with the
939 previous code, which was based on D3.0.
942 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
943 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
944 control whether accepting Router Advertisement messages or not.
945 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
946 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
947 The ifconfig(8) utility now supports these flags.
950 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
951 mount(8) and -a option for df(1) to see them.
954 The old tunable hw.bus.devctl_disable has been superseded by
955 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
956 replaced by hw.bus.devctl_queue=0. The default for this new tunable
960 Remove the option STOP_NMI. The default action is now to use NMI only
961 for KDB via the newly introduced function stop_cpus_hard() and
962 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
965 The stable/8 branch created in subversion. This corresponds to the
966 RELENG_8 branch in CVS.
969 Bump the shared library version numbers for all libraries that do not
970 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
971 __FreeBSD_version to 800105.
974 Due to changes in the implementation of virtual network stack support,
975 all network-related kernel modules must be recompiled. As this change
976 breaks the ABI, bump __FreeBSD_version to 800104.
979 The TOE interface to the TCP syncache has been modified to remove
980 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
981 The cxgb driver is the only TOE consumer affected by this change, and
982 needs to be recompiled along with the kernel. As this change breaks
983 the ABI, bump __FreeBSD_version to 800103.
986 Padding has been added to struct tcpcb, sackhint and tcpstat in
987 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
988 maintaining the ABI. However, this change breaks the ABI, so bump
989 __FreeBSD_version to 800102. User space tools that rely on the size of
990 any of these structs (e.g. sockstat) need to be recompiled.
993 The NFS_LEGACYRPC option has been removed along with the old kernel
994 RPC implementation that this option selected. Kernel configurations
995 may need to be adjusted.
998 The network interface device nodes at /dev/net/<interface> have been
999 removed. All ioctl operations can be performed the normal way using
1000 routing sockets. The kqueue functionality can generally be replaced
1001 with routing sockets.
1004 The documentation from the FreeBSD Documentation Project (Handbook,
1005 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1006 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1009 The ABI of various structures related to the SYSV IPC API have been
1010 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1011 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1015 Layout of struct vnet has changed as routing related variables were
1016 moved to their own Vimage module. Modules need to be recompiled. Bump
1017 __FreeBSD_version to 800099.
1020 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1021 respectively. As long as no more than 16 groups per process are used,
1022 no changes should be visible. When more than 16 groups are used, old
1023 binaries may fail if they call getgroups() or getgrouplist() with
1024 statically sized storage. Recompiling will work around this, but
1025 applications should be modified to use dynamically allocated storage
1026 for group arrays as POSIX.1-2008 does not cap an implementation's
1027 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1029 NFS and portalfs mounts may also be affected as the list of groups is
1030 truncated to 16. Users of NFS who use more than 16 groups, should
1031 take care that negative group permissions are not used on the exported
1032 file systems as they will not be reliable unless a GSSAPI based
1033 authentication method is used.
1036 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1037 option compiles in the support for adaptive spinning for lockmgrs
1038 which want to enable it. The lockinit() function now accepts the flag
1039 LK_ADAPTIVE in order to make the lock object subject to adaptive
1040 spinning when both held in write and read mode.
1043 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1044 changed. User applications that use this ioctl need to be rebuilt.
1047 The layout of struct thread has changed. Kernel and modules need to
1051 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1052 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1055 window(1) has been removed from the base system. It can now be
1056 installed from ports. The port is called misc/window.
1059 The way we are storing and accessing `routing table' entries has
1060 changed. Programs reading the FIB, like netstat, need to be
1064 A new netisr implementation has been added for FreeBSD 8. Network
1065 file system modules, such as igmp, ipdivert, and others, should be
1067 Bump __FreeBSD_version to 800096.
1070 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1074 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1075 Bump __FreeBSD_version to 800094.
1078 Add mnt_xflag field to 'struct mount'. File system modules need to be
1080 Bump __FreeBSD_version to 800093.
1083 The compiling option ADAPTIVE_SX has been retired while it has been
1084 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1085 The KPI for sx_init_flags() changes as accepting flags:
1086 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1087 been introduced in order to handle the reversed logic.
1088 Bump __FreeBSD_version to 800092.
1091 Add support for hierarchical jails. Remove global securelevel.
1092 Bump __FreeBSD_version to 800091.
1095 The layout of struct vnet_net has changed, therefore modules
1097 Bump __FreeBSD_version to 800090.
1100 The newly imported zic(8) produces a new format in the output. Please
1101 run tzsetup(8) to install the newly created data to /etc/localtime.
1104 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1105 hw.usb.* and is now consistent again with previous releases.
1108 802.11 monitor mode support was revised and driver api's were changed.
1109 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1110 of DLT_IEEE802_11. No user-visible data structures were changed but
1111 applications that use DLT_IEEE802_11 may require changes.
1112 Bump __FreeBSD_version to 800088.
1115 The layout of the following structs has changed: sysctl_oid,
1116 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1117 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1118 panics may be experienced. World rebuild is required for
1119 correctly checking networking state from userland.
1120 Bump __FreeBSD_version to 800085.
1123 MLDv2 and Source-Specific Multicast (SSM) have been merged
1124 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1125 The implementation of SSM within FreeBSD's IPv6 stack closely
1126 follows the IPv4 implementation.
1128 For kernel developers:
1130 * The most important changes are that the ip6_output() and
1131 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1132 and this lock has been downgraded to a non-recursive mutex.
1134 * As with the changes to the IPv4 stack to support SSM, filtering
1135 of inbound multicast traffic must now be performed by transport
1136 protocols within the IPv6 stack. This does not apply to TCP and
1137 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1139 * The KPIs used by IPv6 multicast are similar to those used by
1140 the IPv4 stack, with the following differences:
1141 * im6o_mc_filter() is analogous to imo_multicast_filter().
1142 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1143 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1144 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1145 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1146 for MLDv1 have an additional 'timer' argument which is used to
1147 jitter the initial membership report for the solicited-node
1148 multicast membership on-link.
1149 * This is not strictly needed for MLDv2, which already jitters
1150 its report transmissions. However, the 'timer' argument is
1151 preserved in case MLDv1 is active on the interface.
1153 * The KAME linked-list based IPv6 membership implementation has
1154 been refactored to use a vector similar to that used by the IPv4
1156 Code which maintains a list of its own multicast memberships
1157 internally, e.g. carp, has been updated to reflect the new
1160 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1161 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1162 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1163 implementation constraint which needs to be addressed in HEAD.
1165 For application developers:
1167 * The changes are broadly similar to those made for the IPv4
1170 * The use of IPv4 and IPv6 multicast socket options on the same
1171 socket, using mapped addresses, HAS NOT been tested or supported.
1173 * There are a number of issues with the implementation of various
1174 IPv6 multicast APIs which need to be resolved in the API surface
1175 before the implementation is fully compatible with KAME userland
1176 use, and these are mostly to do with interface index treatment.
1178 * The literature available discusses the use of either the delta / ASM
1179 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1180 using setsourcefilter(3)/getsourcefilter(3). For more information
1181 please refer to RFC 3768, 'Socket Interface Extensions for
1182 Multicast Source Filters'.
1184 * Applications which use the published RFC 3678 APIs should be fine.
1186 For systems administrators:
1188 * The mtest(8) utility has been refactored to support IPv6, in
1189 addition to IPv4. Interface addresses are no longer accepted
1190 as arguments, their names must be used instead. The utility
1191 will map the interface name to its first IPv4 address as
1192 returned by getifaddrs(3).
1194 * The ifmcstat(8) utility has also been updated to print the MLDv2
1195 endpoint state and source filter lists via sysctl(3).
1197 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1198 loopback of IPv6 multicast datagrams by default; it defaults to 1
1199 to preserve the existing behaviour. Disabling multicast loopback is
1200 recommended for optimal system performance.
1202 * The IPv6 MROUTING code has been changed to examine this sysctl
1203 instead of attempting to perform a group lookup before looping
1204 back forwarded datagrams.
1206 Bump __FreeBSD_version to 800084.
1209 Implement low-level Bluetooth HCI API.
1210 Bump __FreeBSD_version to 800083.
1213 The layout of struct malloc_type, used by modules to register new
1214 memory allocation types, has changed. Most modules will need to
1215 be rebuilt or panics may be experienced.
1216 Bump __FreeBSD_version to 800081.
1219 Anticipate overflowing inp_flags - add inp_flags2.
1220 This changes most offsets in inpcb, so checking v4 connection
1221 state will require a world rebuild.
1222 Bump __FreeBSD_version to 800080.
1225 Add an llentry to struct route and struct route_in6. Modules
1226 embedding a struct route will need to be recompiled.
1227 Bump __FreeBSD_version to 800079.
1230 The size of rt_metrics_lite and by extension rtentry has changed.
1231 Networking administration apps will need to be recompiled.
1232 The route command now supports show as an alias for get, weighting
1233 of routes, sticky and nostick flags to alter the behavior of stateful
1235 Bump __FreeBSD_version to 800078.
1238 Do not use Giant for kbdmux(4) locking. This is wrong and
1239 apparently causing more problems than it solves. This will
1240 re-open the issue where interrupt handlers may race with
1241 kbdmux(4) in polling mode. Typical symptoms include (but
1242 not limited to) duplicated and/or missing characters when
1243 low level console functions (such as gets) are used while
1244 interrupts are enabled (for example geli password prompt,
1245 mountroot prompt etc.). Disabling kbdmux(4) may help.
1248 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1249 kernel modules referencing any of the above need to be recompiled.
1250 Bump __FreeBSD_version to 800075.
1253 GEOM_PART has become the default partition slicer for storage devices,
1254 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1255 introduces some changes:
1257 MSDOS/EBR: the devices created from MSDOS extended partition entries
1258 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1259 to devices with offset-based names. fstabs may need to be modified.
1261 BSD: the "geometry does not match label" warning is harmless in most
1262 cases but it points to problems in file system misalignment with
1263 disk geometry. The "c" partition is now implicit, covers the whole
1264 top-level drive and cannot be (mis)used by users.
1266 General: Kernel dumps are now not allowed to be written to devices
1267 whose partition types indicate they are meant to be used for file
1268 systems (or, in case of MSDOS partitions, as something else than
1271 Most of these changes date approximately from 200812.
1274 The uscanner(4) driver has been removed from the kernel. This follows
1275 Linux removing theirs in 2.6 and making libusb the default interface
1276 (supported by sane).
1279 The multicast forwarding code has been cleaned up. netstat(1)
1280 only relies on KVM now for printing bandwidth upcall meters.
1281 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1282 ip6_mroute_mod respectively. The config(5) options for statically
1283 compiling this code remain the same, i.e. 'options MROUTING'.
1286 Support for the IFF_NEEDSGIANT network interface flag has been
1287 removed, which means that non-MPSAFE network device drivers are no
1288 longer supported. In particular, if_ar, if_sr, and network device
1289 drivers from the old (legacy) USB stack can no longer be built or
1293 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1294 a bunch of new language catalog files have also been added.
1295 This means that some common libc messages are now localized and
1296 they depend on the LC_MESSAGES environmental variable.
1299 The k8temp(4) driver has been renamed to amdtemp(4) since
1300 support for Family 10 and Family 11 CPU families was added.
1303 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1304 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1306 For kernel developers, the most important changes are that the
1307 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1308 and this lock has been downgraded to a non-recursive mutex.
1310 Transport protocols (UDP, Raw IP) are now responsible for filtering
1311 inbound multicast traffic according to group membership and source
1312 filters. The imo_multicast_filter() KPI exists for this purpose.
1313 Transports which do not use multicast (SCTP, TCP) already reject
1314 multicast by default. Forwarding and receive performance may improve
1315 as a mutex acquisition is no longer needed in the ip_input()
1316 low-level input path. in_addmulti() and in_delmulti() are shimmed
1317 to new KPIs which exist to support SSM in-kernel.
1319 For application developers, it is recommended that loopback of
1320 multicast datagrams be disabled for best performance, as this
1321 will still cause the lock to be taken for each looped-back
1322 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1323 be tuned to 0 to disable loopback by default; it defaults to 1
1324 to preserve the existing behaviour.
1326 For systems administrators, to obtain best performance with
1327 multicast reception and multiple groups, it is always recommended
1328 that a card with a suitably precise hash filter is used. Hash
1329 collisions will still result in the lock being taken within the
1330 transport protocol input path to check group membership.
1332 If deploying FreeBSD in an environment with IGMP snooping switches,
1333 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1334 enabled; this forces 224.0.0.0/24 group membership to be announced
1337 The size of 'struct igmpstat' has changed; netstat needs to be
1338 recompiled to reflect this.
1339 Bump __FreeBSD_version to 800070.
1342 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1343 updated to use it. This requires a buildworld/installworld in order to
1344 update the library and dependencies (usbconfig, etc). Its advisable to
1345 rebuild all ports which uses libusb. More specific directions are given
1346 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1347 libusb are no longer required and can be removed.
1350 A workaround is committed to allow the creation of System V shared
1351 memory segment of size > 2 GB on the 64-bit architectures.
1352 Due to a limitation of the existing ABI, the shm_segsz member
1353 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1354 wrong for large segments. Note that limits must be explicitly
1355 raised to allow such segments to be created.
1358 The layout of struct ifnet has changed, requiring a rebuild of all
1359 network device driver modules.
1362 The /dev handling for the new USB stack has changed, a
1363 buildworld/installworld is required for libusb20.
1366 The new USB2 stack has now been permanently moved in and all kernel and
1367 module names reverted to their previous values (eg, usb, ehci, ohci,
1368 ums, ...). The old usb stack can be compiled in by prefixing the name
1369 with the letter 'o', the old usb modules have been removed.
1370 Updating entry 20090216 for xorg and 20090215 for libmap may still
1374 The rc.conf(5) option if_up_delay has been renamed to
1375 defaultroute_delay to better reflect its purpose. If you have
1376 customized this setting in /etc/rc.conf you need to update it to
1380 xorg 7.4 wants to configure its input devices via hald which does not
1381 yet work with USB2. If the keyboard/mouse does not work in xorg then
1383 Option "AllowEmptyInput" "off"
1384 to your ServerLayout section. This will cause X to use the configured
1385 kbd and mouse sections from your xorg.conf.
1388 The GENERIC kernels for all architectures now default to the new USB2
1389 stack. No kernel config options or code have been removed so if a
1390 problem arises please report it and optionally revert to the old USB
1391 stack. If you are loading USB kernel modules or have a custom kernel
1392 that includes GENERIC then ensure that usb names are also changed over,
1393 eg uftdi -> usb2_serial_ftdi.
1395 Older programs linked against the ports libusb 0.1 need to be
1396 redirected to the new stack's libusb20. /etc/libmap.conf can
1398 # Map old usb library to new one for usb2 stack
1399 libusb-0.1.so.8 libusb20.so.1
1402 All USB ethernet devices now attach as interfaces under the name ueN
1403 (eg. ue0). This is to provide a predictable name as vendors often
1404 change usb chipsets in a product without notice.
1407 The ichsmb(4) driver has been changed to require SMBus slave
1408 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1409 All of the other SMBus controller drivers require left-justified
1410 slave addresses, so this change makes all the drivers provide the
1414 INET6 statistics (struct ip6stat) was updated.
1415 netstat(1) needs to be recompiled.
1418 NTFS has been removed from GENERIC kernel on amd64 to match
1419 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1420 will load ntfs.ko module automatically when NTFS support is
1421 actually needed, unless ntfs.ko is not installed or security
1422 level prohibits loading kernel modules. If either is the case,
1423 "options NTFS" has to be added into kernel config.
1426 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1427 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1428 800061. User space tools that rely on the size of struct tcpcb in
1429 tcp_var.h (e.g. sockstat) need to be recompiled.
1432 ng_tty(4) module updated to match the new TTY subsystem.
1433 Due to API change, user-level applications must be updated.
1434 New API support added to mpd5 CVS and expected to be present
1435 in next mpd5.3 release.
1438 With __FreeBSD_version 800060 the makefs tool is part of
1439 the base system (it was a port).
1442 The afdata and ifnet locks have been changed from mutexes to
1443 rwlocks, network modules will need to be re-compiled.
1446 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1447 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1448 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1449 architecture and 40 bytes on 64-bit architecture. The userland
1450 applications "arp" and "ndp" have been updated accordingly.
1451 The output from "netstat -r" shows only routing entries and
1452 none of the L2 information.
1455 __FreeBSD_version 800057 marks the switchover from the
1456 binary ath hal to source code. Users must add the line:
1458 options AH_SUPPORT_AR5416
1460 to their kernel config files when specifying:
1464 The ath_hal module no longer exists; the code is now compiled
1465 together with the driver in the ath module. It is now
1466 possible to tailor chip support (i.e. reduce the set of chips
1467 and thereby the code size); consult ath_hal(4) for details.
1470 __FreeBSD_version 800054 adds memory barriers to
1471 <machine/atomic.h>, new interfaces to ifnet to facilitate
1472 multiple hardware transmit queues for cards that support
1473 them, and a lock-less ring-buffer implementation to
1474 enable drivers to more efficiently manage queueing of
1478 A new version of ZFS (version 13) has been merged to -HEAD.
1479 This version has zpool attribute "listsnapshots" off by
1480 default, which means "zfs list" does not show snapshots,
1481 and is the same as Solaris behavior.
1484 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1487 The uhci, ohci, ehci and slhci USB Host controller drivers have
1488 been put into separate modules. If you load the usb module
1489 separately through loader.conf you will need to load the
1490 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1491 controller add the following to loader.conf:
1497 The ABI used by the PMC toolset has changed. Please keep
1498 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1502 atapci kernel module now includes only generic PCI ATA
1503 driver. AHCI driver moved to ataahci kernel module.
1504 All vendor-specific code moved into separate kernel modules:
1505 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1506 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1507 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1508 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1511 The TTY subsystem of the kernel has been replaced by a new
1512 implementation, which provides better scalability and an
1513 improved driver model. Most common drivers have been migrated to
1514 the new TTY subsystem, while others have not. The following
1515 drivers have not yet been ported to the new TTY layer:
1518 cy, digi, rc, rp, sio
1524 ng_h4, ng_tty, ppp, sl, snp
1526 Adding these drivers to your kernel configuration file shall
1527 cause compilation to fail.
1530 ntpd has been upgraded to 4.2.4p5.
1533 OpenSSH has been upgraded to 5.1p1.
1535 For many years, FreeBSD's version of OpenSSH preferred DSA
1536 over RSA for host and user authentication keys. With this
1537 upgrade, we've switched to the vendor's default of RSA over
1538 DSA. This may cause upgraded clients to warn about unknown
1539 host keys even for previously known hosts. Users should
1540 follow the usual procedure for verifying host keys before
1541 accepting the RSA key.
1543 This can be circumvented by setting the "HostKeyAlgorithms"
1544 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1547 Please note that the sequence of keys offered for
1548 authentication has been changed as well. You may want to
1549 specify IdentityFile in a different order to revert this
1553 The sio(4) driver has been removed from the i386 and amd64
1554 kernel configuration files. This means uart(4) is now the
1555 default serial port driver on those platforms as well.
1557 To prevent collisions with the sio(4) driver, the uart(4) driver
1558 uses different names for its device nodes. This means the
1559 onboard serial port will now most likely be called "ttyu0"
1560 instead of "ttyd0". You may need to reconfigure applications to
1561 use the new device names.
1563 When using the serial port as a boot console, be sure to update
1564 /boot/device.hints and /etc/ttys before booting the new kernel.
1565 If you forget to do so, you can still manually specify the hints
1566 at the loader prompt:
1568 set hint.uart.0.at="isa"
1569 set hint.uart.0.port="0x3F8"
1570 set hint.uart.0.flags="0x10"
1571 set hint.uart.0.irq="4"
1575 The gpt(8) utility has been removed. Use gpart(8) to partition
1579 The version that Linuxulator emulates was changed from 2.4.2
1580 to 2.6.16. If you experience any problems with Linux binaries
1581 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1582 if it fixes the problem contact emulation mailing list.
1585 ISDN4BSD (I4B) was removed from the src tree. You may need to
1586 update a your kernel configuration and remove relevant entries.
1589 I have checked in code to support multiple routing tables.
1590 See the man pages setfib(1) and setfib(2).
1591 This is a hopefully backwards compatible version,
1592 but to make use of it you need to compile your kernel
1593 with options ROUTETABLES=2 (or more up to 16).
1596 The 802.11 wireless support was redone to enable multi-bss
1597 operation on devices that are capable. The underlying device
1598 is no longer used directly but instead wlanX devices are
1599 cloned with ifconfig. This requires changes to rc.conf files.
1600 For example, change:
1601 ifconfig_ath0="WPA DHCP"
1604 ifconfig_wlan0="WPA DHCP"
1605 see rc.conf(5) for more details. In addition, mergemaster of
1606 /etc/rc.d is highly recommended. Simultaneous update of userland
1607 and kernel wouldn't hurt either.
1609 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1610 modules were merged into the base wlan module. All references
1611 to these modules (e.g. in kernel config files) must be removed.
1614 psm(4) has gained write(2) support in native operation level.
1615 Arbitrary commands can be written to /dev/psm%d and status can
1616 be read back from it. Therefore, an application is responsible
1617 for status validation and error recovery. It is a no-op in
1618 other operation levels.
1621 Support for KSE threading has been removed from the kernel. To
1622 run legacy applications linked against KSE libmap.conf may
1623 be used. The following libmap.conf may be used to ensure
1624 compatibility with any prior release:
1626 libpthread.so.1 libthr.so.1
1627 libpthread.so.2 libthr.so.2
1628 libkse.so.3 libthr.so.3
1631 The layout of struct vmspace has changed. This affects libkvm
1632 and any executables that link against libkvm and use the
1633 kvm_getprocs() function. In particular, but not exclusively,
1634 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1635 The effects are minimal, but it's advisable to upgrade world
1639 The latest em driver no longer has support in it for the
1640 82575 adapter, this is now moved to the igb driver. The
1641 split was done to make new features that are incompatible
1642 with older hardware easier to do.
1645 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1646 likewise the kernel option is now GEOM_LINUX_LVM.
1649 The default NFS mount mode has changed from UDP to TCP for
1650 increased reliability. If you rely on (insecurely) NFS
1651 mounting across a firewall you may need to update your
1655 Belatedly note the addition of m_collapse for compacting
1659 The fts(3) structures have been changed to use adequate
1660 integer types for their members and so to be able to cope
1661 with huge file trees. The old fts(3) ABI is preserved
1662 through symbol versioning in libc, so third-party binaries
1663 using fts(3) should still work, although they will not take
1664 advantage of the extended types. At the same time, some
1665 third-party software might fail to build after this change
1666 due to unportable assumptions made in its source code about
1667 fts(3) structure members. Such software should be fixed
1668 by its vendor or, in the worst case, in the ports tree.
1669 FreeBSD_version 800015 marks this change for the unlikely
1670 case that a portable fix is impossible.
1673 To upgrade to -current after this date, you must be running
1674 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1675 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1678 The ADAPTIVE_GIANT kernel option has been retired because its
1679 functionality is the default now.
1682 The AT keyboard emulation of sunkbd(4) has been turned on
1683 by default. In order to make the special symbols of the Sun
1684 keyboards driven by sunkbd(4) work under X these now have
1685 to be configured the same way as Sun USB keyboards driven
1686 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1688 Option "XkbLayout" "us"
1689 Option "XkbRules" "xorg"
1690 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1693 It has been decided that it is desirable to provide ABI
1694 backwards compatibility to the FreeBSD 4/5/6 versions of the
1695 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1696 broken with the introduction of PCI domain support (see the
1697 20070930 entry). Unfortunately, this required the ABI of
1698 PCIOCGETCONF to be broken again in order to be able to
1699 provide backwards compatibility to the old version of that
1700 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1701 again. As for prominent ports this affects neither pciutils
1702 nor xorg-server this time, the hal port needs to be rebuilt
1706 The misnamed kthread_create() and friends have been renamed
1707 to kproc_create() etc. Many of the callers already
1708 used kproc_start()..
1709 I will return kthread_create() and friends in a while
1710 with implementations that actually create threads, not procs.
1711 Renaming corresponds with version 800002.
1720 Avoid using make -j when upgrading. While generally safe, there are
1721 sometimes problems using -j to upgrade. If your upgrade fails with
1722 -j, please try again without -j. From time to time in the past there
1723 have been problems using -j with buildworld and/or installworld. This
1724 is especially true when upgrading between "distant" versions (eg one
1725 that cross a major release boundary or several minor releases, or when
1726 several months have passed on the -current branch).
1728 Sometimes, obscure build problems are the result of environment
1729 poisoning. This can happen because the make utility reads its
1730 environment when searching for values for global variables. To run
1731 your build attempts in an "environmental clean room", prefix all make
1732 commands with 'env -i '. See the env(1) manual page for more details.
1734 When upgrading from one major version to another it is generally best
1735 to upgrade to the latest code in the currently installed branch first,
1736 then do an upgrade to the new branch. This is the best-tested upgrade
1737 path, and has the highest probability of being successful. Please try
1738 this approach before reporting problems with a major version upgrade.
1742 When upgrading the boot ZFS pool to a new version, always follow
1745 1.) recompile and reinstall the ZFS boot loader and boot block
1746 (this is part of "make buildworld" and "make installworld")
1748 2.) update the ZFS boot block on your boot drive
1750 The following example updates the ZFS boot block on the first
1751 partition (freebsd-boot) of a GPT partitioned drive ad0:
1752 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1754 Non-boot pools do not need these updates.
1758 If you are updating from a prior version of FreeBSD (even one just
1759 a few days old), you should follow this procedure. It is the most
1760 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1762 make kernel-toolchain
1763 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1764 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1766 To test a kernel once
1767 ---------------------
1768 If you just want to boot a kernel once (because you are not sure
1769 if it works, or if you want to boot a known bad kernel to provide
1770 debugging information) run
1771 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1772 nextboot -k testkernel
1774 To just build a kernel when you know that it won't mess you up
1775 --------------------------------------------------------------
1776 This assumes you are already running a CURRENT system. Replace
1777 ${arch} with the architecture of your machine (e.g. "i386",
1778 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1780 cd src/sys/${arch}/conf
1781 config KERNEL_NAME_HERE
1782 cd ../compile/KERNEL_NAME_HERE
1787 If this fails, go to the "To build a kernel" section.
1789 To rebuild everything and install it on the current system.
1790 -----------------------------------------------------------
1791 # Note: sometimes if you are running current you gotta do more than
1792 # is listed here if you are upgrading from a really old current.
1794 <make sure you have good level 0 dumps>
1796 make kernel KERNCONF=YOUR_KERNEL_HERE
1798 <reboot in single user> [3]
1806 To cross-install current onto a separate partition
1807 --------------------------------------------------
1808 # In this approach we use a separate partition to hold
1809 # current's root, 'usr', and 'var' directories. A partition
1810 # holding "/", "/usr" and "/var" should be about 2GB in
1813 <make sure you have good level 0 dumps>
1816 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1817 <maybe newfs current's root partition>
1818 <mount current's root partition on directory ${CURRENT_ROOT}>
1819 make installworld DESTDIR=${CURRENT_ROOT}
1820 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1821 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1822 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1823 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1824 <reboot into current>
1825 <do a "native" rebuild/install as described in the previous section>
1826 <maybe install compatibility libraries from ports/misc/compat*>
1830 To upgrade in-place from stable to current
1831 ----------------------------------------------
1832 <make sure you have good level 0 dumps>
1834 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1836 <reboot in single user> [3]
1843 Make sure that you've read the UPDATING file to understand the
1844 tweaks to various things you need. At this point in the life
1845 cycle of current, things change often and you are on your own
1846 to cope. The defaults can also change, so please read ALL of
1847 the UPDATING entries.
1849 Also, if you are tracking -current, you must be subscribed to
1850 freebsd-current@freebsd.org. Make sure that before you update
1851 your sources that you have read and understood all the recent
1852 messages there. If in doubt, please track -stable which has
1853 much fewer pitfalls.
1855 [1] If you have third party modules, such as vmware, you
1856 should disable them at this point so they don't crash your
1859 [3] From the bootblocks, boot -s, and then do
1864 adjkerntz -i # if CMOS is wall time
1865 Also, when doing a major release upgrade, it is required that
1866 you boot into single user mode to do the installworld.
1868 [4] Note: This step is non-optional. Failure to do this step
1869 can result in a significant reduction in the functionality of the
1870 system. Attempting to do it by hand is not recommended and those
1871 that pursue this avenue should read this file carefully, as well
1872 as the archives of freebsd-current and freebsd-hackers mailing lists
1873 for potential gotchas. The -U option is also useful to consider.
1874 See mergemaster(8) for more information.
1876 [5] Usually this step is a noop. However, from time to time
1877 you may need to do this if you get unknown user in the following
1878 step. It never hurts to do it all the time. You may need to
1879 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1880 install) after the buildworld before this step if you last updated
1881 from [78]-stable or 9-stable before 20130430.
1883 [6] This only deletes old files and directories. Old libraries
1884 can be deleted by "make delete-old-libs", but you have to make
1885 sure that no program is using those libraries anymore.
1887 [8] In order to have a kernel that can run the 4.x binaries needed to
1888 do an installworld, you must include the COMPAT_FREEBSD4 option in
1889 your kernel. Failure to do so may leave you with a system that is
1890 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1891 required to run the 5.x binaries on more recent kernels. And so on
1892 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1894 Make sure that you merge any new devices from GENERIC since the
1895 last time you updated your kernel config file.
1897 [9] When checking out sources, you must include the -P flag to have
1898 cvs prune empty directories.
1900 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1901 "?=" instead of the "=" assignment operator, so that buildworld can
1902 override the CPUTYPE if it needs to.
1904 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1905 not on the command line, or in /etc/make.conf. buildworld will
1906 warn if it is improperly defined.
1909 This file contains a list, in reverse chronological order, of major
1910 breakages in tracking -current. It is not guaranteed to be a complete
1911 list of such breakages, and only contains entries since October 10, 2007.
1912 If you need to see UPDATING entries from before that date, you will need
1913 to fetch an UPDATING file from an older FreeBSD release.
1915 Copyright information:
1917 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1919 Redistribution, publication, translation and use, with or without
1920 modification, in full or in part, in any form or format of this
1921 document are permitted without further permission from the author.
1923 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1924 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1925 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1926 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1927 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1928 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1929 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1930 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1931 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1932 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1933 POSSIBILITY OF SUCH DAMAGE.
1935 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / releng / 9.3.git / blob