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 20150902: p25 FreeBSD-SA-15:23.bind
16 Fix BIND remote denial of service vulnerability. [SA-15:23]
18 20150825: p24 FreeBSD-SA-15:21.amd64
19 FreeBSD-SA-15:22.openssh
22 Fix local privilege escalation in IRET handler. [SA-15:21]
24 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
26 Fix insufficient check of unsupported pkg(7) signature methods.
29 20150818: p23 FreeBSD-SA-15:20.expat
31 Fix multiple integer overflows in expat (libbsdxml) XML parser.
34 20150805: p22 FreeBSD-SA-15:19.routed
36 Fix routed remote denial of service vulnerability.
38 20150728: p21 FreeBSD-SA-15:15.tcp
39 FreeBSD-SA-15:16.openssh
42 Fix resource exhaustion in TCP reassembly. [SA-15:15]
44 Fix OpenSSH multiple vulnerabilities. [SA-15:16]
46 Fix BIND remote denial of service vulnerability. [SA-15:17]
48 20150721: p20 FreeBSD-SA-15:13.tcp
50 Fix resource exhaustion due to sessions stuck in LAST_ACK state.
53 20150707: p19 FreeBSD-SA-15:11.bind
54 Fix BIND resolver remote denial of service when validating.
56 20150630: p18 FreeBSD-EN-15:08.sendmail [revised]
57 FreeBSD-EN-15:09.xlocale
59 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
61 Fix inconsistency between locale and rune locale states.
64 20150618: p17 FreeBSD-EN-15:08.sendmail
65 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
67 20150612: p16 FreeBSD-SA-15:10.openssl
68 Fix multiple vulnerabilities in OpenSSL. [SA-15:10]
70 20150609: p15 FreeBSD-EN-15:06.file
72 Updated base system file(1) to 5.22 to address multiple denial
75 20150513: p14 FreeBSD-EN-15:04.freebsd-update
77 Fix bug with freebsd-update(8) that does not ensure the previous
78 upgrade was completed. [EN-15:04]
80 20150407: p13 FreeBSD-SA-15:04.igmp [revised]
84 Improved patch for SA-15:04.igmp.
86 Fix multiple vulnerabilities of ntp. [SA-15:07]
88 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
91 Fix patch for SA-15:06.openssl.
93 20150319: p11 FreeBSD-SA-15:06.openssl
94 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
96 20150225: p10 FreeBSD-SA-15:04.igmp
99 FreeBSD-EN-15:02.openssl
100 FreeBSD-EN-15:03.freebsd-update
102 Fix integer overflow in IGMP protocol. [SA-15:04]
104 Fix BIND remote denial of service vulnerability. [SA-15:05]
106 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
108 Updated base system OpenSSL to 0.9.8zd. [EN-15:02]
110 Fix freebsd-update libraries update ordering issue. [EN-15:03]
112 20150127: p9 FreeBSD-SA-15:02.kmem
113 FreeBSD-SA-15:03.sctp
115 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
116 vulnerability. [SA-15:02]
118 Fix SCTP stream reset vulnerability. [SA-15:03]
120 20150114: p8 FreeBSD-SA-15:01.openssl
121 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
123 20141223: p7 FreeBSD-SA-14:31.ntp
124 FreeBSD-EN-14:13.freebsd-update
126 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
127 Fix directory deletion issue in freebsd-update. [EN-14:13]
129 20141210: p6 FreeBSD-SA-14:28.file
130 FreeBSD-SA-14:29.bind
132 Fix multiple vulnerabilities in file(1) and libmagic(3).
135 Fix BIND remote denial of service vulnerability. [SA-14:29]
137 20141104: p5 FreeBSD-SA-14:25.setlogin
141 Fix kernel stack disclosure in setlogin(2) / getlogin(2).
144 Fix remote command execution in ftp(1). [SA-14:26]
146 Fix NFSv4 and ZFS cache consistency issue. [EN-14:12]
148 20141022: p4 FreeBSD-EN-14:10.tzdata
149 FreeBSD-EN-14:11.crypt
151 Time zone data file update. [EN-14:10]
153 Change crypt(3) default hashing algorithm back to DES. [EN-14:11]
155 20141021: p3 FreeBSD-SA-14:20.rtsold
156 FreeBSD-SA-14:21.routed
157 FreeBSD-SA-14:22.namei
158 FreeBSD-SA-14:23.openssl
160 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
162 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
164 Fix memory leak in sandboxed namei lookup. [SA-14:22]
166 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
168 20140916: p2 FreeBSD-SA-14:19.tcp
169 Fix Denial of Service in TCP packet processing. [SA-14:19]
171 20140909: p1 FreeBSD-SA-14:18.openssl
172 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
178 On i386 and amd64 systems, the onifconsole flag is now set by default
179 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
180 as a login TTY if it is set in the bootloader as an active kernel
181 console. No changes in behavior should result otherwise. To revert to
182 the previous behavior, set ttyu0 to "off" in /etc/ttys.
185 Clang and llvm have been upgraded to 3.4.1 release.
188 Clang and llvm have been upgraded to 3.4 release.
191 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
192 been deprecated and will not be part of FreeBSD 11.0 and later
193 releases. If you use this driver, please consider switching to
194 the nfe(4) driver instead.
197 The behavior of gss_pseudo_random() for the krb5 mechanism
198 has changed, for applications requesting a longer random string
199 than produced by the underlying enctype's pseudo-random() function.
200 In particular, the random string produced from a session key of
201 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
202 be different at the 17th octet and later, after this change.
203 The counter used in the PRF+ construction is now encoded as a
204 big-endian integer in accordance with RFC 4402.
205 __FreeBSD_version is bumped to 902505.
211 Behavior of devfs rules path matching has been changed.
212 Pattern is now always matched against fully qualified devfs
213 path and slash characters must be explicitly matched by
214 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
215 subdirectories must be reviewed.
218 hastctl(8)'s `status' command output changed to terse one-liner format.
219 Scripts using this should switch to `list' command or be rewritten.
222 Fix a bug that allowed a tracing process (e.g. gdb) to write
223 to a memory-mapped file in the traced process's address space
224 even if neither the traced process nor the tracing process had
225 write access to that file.
228 Added ZFS TRIM support which is enabled by default. To disable
229 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
231 Creating new ZFS pools and adding new devices to existing pools
232 first performs a full device level TRIM which can take a significant
233 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
234 to disable this behaviour.
236 ZFS TRIM requires the underlying device support BIO_DELETE which
237 is currently provided by methods such as ATA TRIM and SCSI UNMAP
238 via CAM, which are typically supported by SSD's.
240 Stats for ZFS TRIM can be monitored by looking at the sysctl's
241 under kstat.zfs.misc.zio_trim.
244 `list' command has been added to hastctl(8). For now, it is full
245 equivalent of `status' command.
246 WARNING: in the near future the output of hastctl's status command
247 will change to more terse format. If you use `hastctl status'
248 for parsing in your scripts, switch to `hastctl list'.
251 The mergemaster command now uses the default MAKEOBJDIRPREFIX
252 rather than creating it's own in the temporary directory in
253 order allow access to bootstrapped versions of tools such as
254 install and mtree. When upgrading from version of FreeBSD where
255 the install command does not support -l, you will need to
256 install a new mergemaster command if mergemaster -p is required.
257 This can be accomplished with the command (cd src/usr.sbin/mergemaster
260 Due to the use of the new -l option to install(1) during build
261 and install, you must take care not to directly set the INSTALL
262 make variable in your /etc/make.conf, /etc/src.conf, or on the
263 command line. If you wish to use the -C flag for all installs
264 you may be able to add INSTALL+=-C to /etc/make.conf or
268 Fix a bug that allows NFS clients to issue READDIR on files.
271 The install(1) option -M has changed meaning and now takes an
272 argument that is a file or path to append logs to. In the
273 unlikely event that -M was the last option on the command line
274 and the command line contained at least two files and a target
275 directory the first file will have logs appended to it. The -M
276 option served little practical purpose in the last decade so it's
277 used expected to be extremely rare.
280 A new compression method (lz4) has been merged to. Please refer to
281 zpool-features(7) for more information.
283 Please refer to the "ZFS notes" section of this file for information
284 on upgrading boot ZFS pools.
287 The VFS KBI was changed with the merge of several nullfs
288 optimizations and fixes. All filesystem modules must be
292 With the addition of auditdistd(8), a new auditdistd user is now
293 depended on during installworld. "mergemaster -p" can be used to add
294 the user prior to installworld, as documented in the handbook.
300 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
301 Starting with this version the old system of ZFS pool versioning
302 is superseded by "feature flags". This concept enables forward
303 compatibility against certain future changes in functionality of ZFS
304 pools. The first two read-only compatible "feature flags" for ZFS
305 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
306 For more information read the new zpool-features(7) manual page.
307 Please refer to the "ZFS notes" section of this file for information
308 on upgrading boot ZFS pools.
311 The commit introducing bsd.compiler.mk breaks the traditional
312 building of kernels before this point. Add -m ${SRC}/share/mk
313 (for the right value of SRC) to your command lines to work
314 around; update your useland to a point after this; or use the
315 buildkernel/installkernel top-level targets. See also 20120829.
318 The IPFIREWALL_FORWARD kernel option has been removed. Its
319 functionality now turned on by default.
322 The random(4) support for the VIA hardware random number
323 generator (`PADLOCK') is no longer enabled unconditionally.
324 Add the PADLOCK_RNG option in the custom kernel config if
325 needed. The GENERIC kernels on i386 and amd64 do include the
326 option, so the change only affects the custom kernel
330 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
331 the traditional method, you must update your system with an installworld
332 before the kernel will build. The documented make buildkernel/installkernel
333 interfaces (coupled with fresh make kernel-toolchain) continue to work.
336 The sparc64 ZFS loader has been changed to no longer try to auto-
337 detect ZFS providers based on diskN aliases but now requires these
338 to be explicitly listed in the OFW boot-device environment variable.
341 Now unix domain sockets behave "as expected" on nullfs(5). Previously
342 nullfs(5) did not pass through all behaviours to the underlying layer,
343 as a result if we bound to a socket on the lower layer we could connect
344 only to the lower path; if we bound to the upper layer we could connect
345 only to the upper path. The new behavior is one can connect to both the
346 lower and the upper paths regardless what layer path one binds to.
349 The acpi_wmi(4) status device /dev/wmistat has been renamed to
353 A new VOP_ADVISE() was added to support posix_fadvise(2). All
354 filesystem modules must be recompiled.
357 The interface of the VOP_VPTOCNP(9) changed, now the returned
358 vnode shall be referenced, previously it was required to be
359 only held. All in-tree filesystems are converted.
365 The broken amd(4) driver has been replaced with esp(4) in the amd64,
366 i386 and pc98 GENERIC kernel configuration files.
369 This commit modifies vfs_register() so that it uses a hash
370 calculation to set vfc_typenum, which is enabled by default.
371 The first time a system is booted after this change, the
372 vfc_typenum values will change for all file systems. The
373 main effect of this is a change to the NFS server file handles
374 for file systems that use vfc_typenum in their fsid, such as ZFS.
375 It will, however, prevent vfc_typenum from changing when file
376 systems are loaded in a different order for subsequent reboots.
377 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
378 until you are ready to remount all NFS clients after a reboot.
381 Bump the shared library version numbers for libraries that
382 do not use symbol versioning, have changed the ABI compared
383 to stable/8 and which shared library version was not bumped.
384 Done as part of 9.0-RELEASE cycle.
387 During the merge of Capsicum features, the fget(9) KPI was modified.
388 This may require the rebuilding of out-of-tree device drivers --
389 issues have been reported specifically with the nVidia device driver.
390 __FreeBSD_version is bumped to 900041.
392 Also, there is a period between 20110811 and 20110814 where the
393 special devices /dev/{stdin,stdout,stderr} did not work correctly.
394 Building world from a kernel during that window may not work.
397 The packet filter (pf) code has been updated to OpenBSD 4.5.
398 You need to update userland tools to be in sync with kernel.
399 This update breaks backward compatibility with earlier pfsync(4)
400 versions. Care must be taken when updating redundant firewall setups.
403 The following sysctls and tunables are retired on x86 platforms:
405 machdep.hlt_logical_cpus
406 The following sysctl is retired:
407 machdep.hyperthreading_allowed
408 The sysctls were supposed to provide a way to dynamically offline and
409 online selected CPUs on x86 platforms, but the implementation has not
410 been reliable especially with SCHED_ULE scheduler.
411 machdep.hyperthreading_allowed tunable is still available to ignore
412 hyperthreading CPUs at OS level.
413 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
414 where X is an APIC ID of a CPU. Be advised, though, that disabling
415 CPUs in non-uniform fashion will result in non-uniform topology and
416 may lead to sub-optimal system performance with SCHED_ULE, which is
420 cpumask_t type is retired and cpuset_t is used in order to describe
424 Changes to ifconfig(8) for dynamic address family detection mandate
425 that you are running a kernel of 20110525 or later. Make sure to
426 follow the update procedure to boot a new kernel before installing
430 Support for sun4v architecture is officially dropped
433 Several KPI breaking changes have been committed to the mii(4) layer,
434 the PHY drivers and consequently some Ethernet drivers using mii(4).
435 This means that miibus.ko and the modules of the affected Ethernet
436 drivers need to be recompiled.
438 Note to kernel developers: Given that the OUI bit reversion problem
439 was fixed as part of these changes all mii(4) commits related to OUIs,
440 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
441 handling, no longer can be merged verbatim to stable/8 and previous
445 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
446 into their kernel configurations along with 'device pci'.
449 The default NFS client is now the new NFS client, so fstype "newnfs"
450 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
451 Although mounts via fstype "nfs" will usually work without userland
452 changes, it is recommended that the mount(8) and mount_nfs(8)
453 commands be rebuilt from sources and that a link to mount_nfs called
454 mount_oldnfs be created. The new client is compiled into the
455 kernel with "options NFSCL" and this is needed for diskless root
456 file systems. The GENERIC kernel configs have been changed to use
457 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
458 To use the regular/old client, you can "mount -t oldnfs ...". For
459 a diskless root file system, you must also include a line like:
461 vfs.root.mountfrom="oldnfs:"
463 in the boot/loader.conf on the root fs on the NFS server to make
464 a diskless root fs use the old client.
467 The GENERIC kernels for all architectures now default to the new
468 CAM-based ATA stack. It means that all legacy ATA drivers were
469 removed and replaced by respective CAM drivers. If you are using
470 ATA device names in /etc/fstab or other places, make sure to update
471 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
472 where 'Y's are the sequential numbers starting from zero for each type
473 in order of detection, unless configured otherwise with tunables,
474 see cam(4)). There will be symbolic links created in /dev/ to map
475 old adX devices to the respective adaY. They should provide basic
476 compatibility for file systems mounting in most cases, but they do
477 not support old user-level APIs and do not have respective providers
478 in GEOM. Consider using updated management tools with new device names.
480 It is possible to load devices ahci, ata, siis and mvs as modules,
481 but option ATA_CAM should remain in kernel configuration to make ata
482 module work as CAM driver supporting legacy ATA controllers. Device ata
483 still can be used in modular fashion (atacore + ...). Modules atadisk
484 and atapi* are not used and won't affect operation in ATA_CAM mode.
485 Note that to use CAM-based ATA kernel should include CAM devices
486 scbus, pass, da (or explicitly ada), cd and optionally others. All of
487 them are parts of the cam module.
489 ataraid(4) functionality is now supported by the RAID GEOM class.
490 To use it you can load geom_raid kernel module and use graid(8) tool
491 for management. Instead of /dev/arX device names, use /dev/raid/rX.
493 No kernel config options or code have been removed, so if a problem
494 arises, please report it and optionally revert to the old ATA stack.
495 In order to do it you can remove from the kernel config:
500 , and instead add back:
501 device atadisk # ATA disk drives
502 device ataraid # ATA RAID drives
503 device atapicd # ATAPI CDROM drives
504 device atapifd # ATAPI floppy drives
505 device atapist # ATAPI tape drives
508 The default NFS server has been changed to the new server, which
509 was referred to as the experimental server. If you need to switch
510 back to the old NFS server, you must now put the "-o" option on
511 both the mountd and nfsd commands. This can be done using the
512 mountd_flags and nfs_server_flags rc.conf variables until an
513 update to the rc scripts is committed, which is coming soon.
516 The GNU Objective-C runtime library (libobjc), and other Objective-C
517 related components have been removed from the base system. If you
518 require an Objective-C library, please use one of the available ports.
521 ath(4) has been split into bus- and device- modules. if_ath contains
522 the HAL, the TX rate control and the network device code. if_ath_pci
523 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
524 contains the AHB glue. Users need to load both if_ath_pci and if_ath
525 in order to use ath on everything else.
527 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
528 need to load if_ath and if_ath_pci for ath(4) operation.
531 As part of the replacement of sysinstall, the process of building
532 release media has changed significantly. For details, please re-read
533 release(7), which has been updated to reflect the new build process.
536 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
537 is the last available version under GPLv2. It brings a number of new
538 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
539 4.1 and SSE 4.2), better support for powerpc64, a number of new
540 directives, and lots of other small improvements. See the ChangeLog
541 file in contrib/binutils for the full details.
544 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
545 compliant, and will now use half of hash for authentication.
546 This will break interoperability with all stacks (including all
547 actual FreeBSD versions) who implement
548 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
550 The only workaround with such peers is to use another HMAC
551 algorithm for IPsec ("phase 2") authentication.
554 Remove the uio_yield prototype and symbol. This function has
555 been misnamed since it was introduced and should not be
556 globally exposed with this name. The equivalent functionality
557 is now available using kern_yield(curthread->td_user_pri).
558 The function remains undocumented.
561 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
562 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
563 for scalar sysctls is defined but disabled. Code that needs
564 UQUAD to pass the type checking that must compile on older
565 systems where the define is not present can check against
566 __FreeBSD_version >= 900030.
568 The system dialog(1) has been replaced with a new version previously
569 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
570 with the previous version, but the libdialog associated with it has
571 a largely incompatible API. As such, the original version of libdialog
572 will be kept temporarily as libodialog, until its base system consumers
573 are replaced or updated. Bump __FreeBSD_version to 900030.
576 If you are trying to run make universe on a -stable system, and you get
577 the following warning:
578 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
579 unknown. config(8) likely too old."
580 or something similar to it, then you must upgrade your -stable system
581 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
582 stable/8) or build the config from the latest stable/8 branch and
583 install it on your system.
585 Prior to this date, building a current universe on 8-stable system from
586 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
587 error in the first kernel build phase. A new config on those old
588 systems will fix that problem for older versions of -current.
591 The TCP stack has been modified to allow Khelp modules to interact with
592 it via helper hook points and store per-connection data in the TCP
593 control block. Bump __FreeBSD_version to 900029. User space tools that
594 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
598 Generic IEEE 802.3 annex 31B full duplex flow control support has been
599 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
600 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
601 to take advantage of it instead of using custom implementations. This
602 means that these drivers now no longer unconditionally advertise
603 support for flow control but only do so if flow control is a selected
604 media option. This was implemented in the generic support that way in
605 order to allow flow control to be switched on and off via ifconfig(8)
606 with the PHY specific default to typically off in order to protect
607 from unwanted effects. Consequently, if you used flow control with
608 one of the above mentioned drivers you now need to explicitly enable
610 ifconfig bge0 media auto mediaopt flowcontrol
612 Along with the above mentioned changes generic support for setting
613 1000baseT master mode also has been added and brgphy(4), ciphy(4),
614 e1000phy(4) as well as ip1000phy(4) have been converted to take
615 advantage of it. This means that these drivers now no longer take the
616 link0 parameter for selecting master mode but the master media option
617 has to be used instead, for example like in the following:
618 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
620 Selection of master mode now is also available with all other PHY
621 drivers supporting 1000baseT.
624 The TCP stack has received a significant update to add support for
625 modularised congestion control and generally improve the clarity of
626 congestion control decisions. Bump __FreeBSD_version to 900025. User
627 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
628 sockstat) need to be recompiled.
631 The man(1) utility has been replaced by a new version that no longer
632 uses /etc/manpath.config. Please consult man.conf(5) for how to
633 migrate local entries to the new format.
636 The copyright strings printed by login(1) and sshd(8) at the time of a
637 new connection have been removed to follow other operating systems and
641 A workaround for a fixed ld bug has been removed in kernel code,
642 so make sure that your system ld is built from sources after
643 revision 210245 from 2010-07-19 (r211583 if building head kernel
644 on stable/8, r211584 for stable/7; both from 2010-08-21).
645 A symptom of incorrect ld version is different addresses for
646 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
649 The $ipv6_prefer variable in rc.conf(5) has been split into
650 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
652 The $ip6addrctl_policy is a variable to choose a pre-defined
653 address selection policy set by ip6addrctl(8). A value
654 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
657 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
658 flag (see an entry of 20090926) is set on an interface with no
659 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
660 security reason. If you want IPv6 link-local address on all
661 interfaces by default, set this to "YES".
663 The old ipv6_prefer="YES" is equivalent to
664 ipv6_activate_all_interfaces="YES" and
665 ip6addrctl_policy="ipv6_prefer".
668 DTrace has grown support for userland tracing. Due to this, DTrace is
669 now i386 and amd64 only.
670 dtruss(1) is now installed by default on those systems and a new
671 kernel module is needed for userland tracing: fasttrap.
672 No changes to your kernel config file are necessary to enable
673 userland tracing, but you might consider adding 'STRIP=' and
674 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
675 to have informative userland stack traces in DTrace (ustack).
678 The acpi_aiboost(4) driver has been removed in favor of the new
679 aibs(4) driver. You should update your kernel configuration file.
682 BSD grep has been imported to the base system and it is built by
683 default. It is completely BSD licensed, highly GNU-compatible, uses
684 less memory than its GNU counterpart and has a small codebase.
685 However, it is slower than its GNU counterpart, which is mostly
686 noticeable for larger searches, for smaller ones it is measurable
687 but not significant. The reason is complex, the most important factor
688 is that we lack a modern and efficient regex library and GNU
689 overcomes this by optimizing the searches internally. Future work
690 on improving the regex performance is planned, for the meantime,
691 users that need better performance, can build GNU grep instead by
692 setting the WITH_GNU_GREP knob.
695 Due to the import of powerpc64 support, all existing powerpc kernel
696 configuration files must be updated with a machine directive like this:
697 machine powerpc powerpc
699 In addition, an updated config(8) is required to build powerpc kernels
703 A new version of ZFS (version 15) has been merged to -HEAD.
704 This version uses a python library for the following subcommands:
705 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
706 For full functionality of these commands the following port must
707 be installed: sysutils/py-zfs
710 'vm_page's are now hashed by physical address to an array of mutexes.
711 Currently this is only used to serialize access to hold_count. Over
712 time the page queue mutex will be peeled away. This changes the size
713 of pmap on every architecture. And requires all callers of vm_page_hold
714 and vm_page_unhold to be updated.
717 WITH_CTF can now be specified in src.conf (not recommended, there
718 are some problems with static executables), make.conf (would also
719 affect ports which do not use GNU make and do not override the
720 compile targets) or in the kernel config (via "makeoptions
722 When WITH_CTF was specified there before this was silently ignored,
723 so make sure that WITH_CTF is not used in places which could lead
724 to unwanted behavior.
727 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
728 to allow 32-bit compatibility on non-x86 platforms. All kernel
729 configurations on amd64 and ia64 platforms using these options must
730 be modified accordingly.
733 The utmp user accounting database has been replaced with utmpx,
734 the user accounting interface standardized by POSIX.
735 Unfortunately the semantics of utmp and utmpx don't match,
736 making it practically impossible to support both interfaces.
737 The user accounting database is used by tools like finger(1),
738 last(1), talk(1), w(1) and ac(8).
740 All applications in the base system use utmpx. This means only
741 local binaries (e.g. from the ports tree) may still use these
742 utmp database files. These applications must be rebuilt to make
745 After the system has been upgraded, it is safe to remove the old
746 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
747 assuming their contents is of no importance anymore. Old wtmp
748 databases can only be used by last(1) and ac(8) after they have
749 been converted to the new format using wtmpcvt(1).
752 Introduce the kernel thread "deadlock resolver" (which can be enabled
753 via the DEADLKRES option, see NOTES for more details) and the
754 sleepq_type() function for sleepqueues.
757 The rc.firewall and rc.firewall6 were unified, and
758 rc.firewall6 and rc.d/ip6fw were removed.
759 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
760 variables are obsoleted. Instead, the following new rc
761 variables are added to rc.d/ipfw:
763 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
764 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
765 firewall_simple_onet_ipv6, firewall_trusted_ipv6
767 The meanings correspond to the relevant IPv4 variables.
773 The default terminal emulation for syscons(4) has been changed
774 from cons25 to xterm on all platforms except pc98. This means
775 that the /etc/ttys file needs to be updated to ensure correct
776 operation of applications on the console.
778 The terminal emulation style can be toggled per window by using
779 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
780 options can be used to change the compile-time default back to
783 To prevent graphical artifacts, make sure the TERM environment
784 variable is set to match the terminal emulation that is being
785 performed by syscons(4).
788 The layout of the structure ieee80211req_scan_result has changed.
789 Applications that require wireless scan results (e.g. ifconfig(8))
790 from net80211 need to be recompiled.
792 Applications such as wpa_supplicant(8) may require a full world
793 build without using NO_CLEAN in order to get synchronized with the
797 The iwn(4) driver has been updated to support the 5000 and 5150 series.
798 There's one kernel module for each firmware. Adding "device iwnfw"
799 to the kernel configuration file means including all three firmware
800 images inside the kernel. If you want to include just the one for
801 your wireless card, use the devices iwn4965fw, iwn5000fw or
805 The rc.d/network_ipv6, IPv6 configuration script has been integrated
806 into rc.d/netif. The changes are the following:
808 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
809 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
810 Note that both variables need the "inet6" keyword at the head.
812 Do not set $ipv6_network_interfaces manually if you do not
813 understand what you are doing. It is not needed in most cases.
815 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
818 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
819 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
821 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
822 all configured interfaces have "inet6 accept_rtadv" in the
823 $ifconfig_IF_ipv6. These are for backward compatibility.
825 3. A new variable $ipv6_prefer has been added. If NO, IPv6
826 functionality of interfaces with no corresponding
827 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
828 and the default address selection policy of ip6addrctl(8)
829 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
830 Note that if you want to configure IPv6 functionality on the
831 disabled interfaces after boot, first you need to clear the flag by
832 using ifconfig(8) like:
834 ifconfig em0 inet6 -ifdisabled
836 If YES, the default address selection policy is set as
839 The default value of $ipv6_prefer is NO.
841 4. If your system need to receive Router Advertisement messages,
842 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
843 scripts automatically invoke rtsol(8) when the interface becomes
844 UP. The Router Advertisement messages are used for SLAAC
845 (State-Less Address AutoConfiguration).
848 802.11s D3.03 support was committed. This is incompatible with the
849 previous code, which was based on D3.0.
852 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
853 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
854 control whether accepting Router Advertisement messages or not.
855 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
856 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
857 The ifconfig(8) utility now supports these flags.
860 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
861 mount(8) and -a option for df(1) to see them.
864 The old tunable hw.bus.devctl_disable has been superseded by
865 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
866 replaced by hw.bus.devctl_queue=0. The default for this new tunable
870 Remove the option STOP_NMI. The default action is now to use NMI only
871 for KDB via the newly introduced function stop_cpus_hard() and
872 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
875 The stable/8 branch created in subversion. This corresponds to the
876 RELENG_8 branch in CVS.
879 Bump the shared library version numbers for all libraries that do not
880 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
881 __FreeBSD_version to 800105.
884 Due to changes in the implementation of virtual network stack support,
885 all network-related kernel modules must be recompiled. As this change
886 breaks the ABI, bump __FreeBSD_version to 800104.
889 The TOE interface to the TCP syncache has been modified to remove
890 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
891 The cxgb driver is the only TOE consumer affected by this change, and
892 needs to be recompiled along with the kernel. As this change breaks
893 the ABI, bump __FreeBSD_version to 800103.
896 Padding has been added to struct tcpcb, sackhint and tcpstat in
897 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
898 maintaining the ABI. However, this change breaks the ABI, so bump
899 __FreeBSD_version to 800102. User space tools that rely on the size of
900 any of these structs (e.g. sockstat) need to be recompiled.
903 The NFS_LEGACYRPC option has been removed along with the old kernel
904 RPC implementation that this option selected. Kernel configurations
905 may need to be adjusted.
908 The network interface device nodes at /dev/net/<interface> have been
909 removed. All ioctl operations can be performed the normal way using
910 routing sockets. The kqueue functionality can generally be replaced
911 with routing sockets.
914 The documentation from the FreeBSD Documentation Project (Handbook,
915 FAQ, etc.) is now installed via packages by sysinstall(8) and under
916 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
919 The ABI of various structures related to the SYSV IPC API have been
920 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
921 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
925 Layout of struct vnet has changed as routing related variables were
926 moved to their own Vimage module. Modules need to be recompiled. Bump
927 __FreeBSD_version to 800099.
930 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
931 respectively. As long as no more than 16 groups per process are used,
932 no changes should be visible. When more than 16 groups are used, old
933 binaries may fail if they call getgroups() or getgrouplist() with
934 statically sized storage. Recompiling will work around this, but
935 applications should be modified to use dynamically allocated storage
936 for group arrays as POSIX.1-2008 does not cap an implementation's
937 number of supported groups at NGROUPS_MAX+1 as previous versions did.
939 NFS and portalfs mounts may also be affected as the list of groups is
940 truncated to 16. Users of NFS who use more than 16 groups, should
941 take care that negative group permissions are not used on the exported
942 file systems as they will not be reliable unless a GSSAPI based
943 authentication method is used.
946 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
947 option compiles in the support for adaptive spinning for lockmgrs
948 which want to enable it. The lockinit() function now accepts the flag
949 LK_ADAPTIVE in order to make the lock object subject to adaptive
950 spinning when both held in write and read mode.
953 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
954 changed. User applications that use this ioctl need to be rebuilt.
957 The layout of struct thread has changed. Kernel and modules need to
961 The layout of structs ifnet, domain, protosw and vnet_net has changed.
962 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
965 window(1) has been removed from the base system. It can now be
966 installed from ports. The port is called misc/window.
969 The way we are storing and accessing `routing table' entries has
970 changed. Programs reading the FIB, like netstat, need to be
974 A new netisr implementation has been added for FreeBSD 8. Network
975 file system modules, such as igmp, ipdivert, and others, should be
977 Bump __FreeBSD_version to 800096.
980 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
984 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
985 Bump __FreeBSD_version to 800094.
988 Add mnt_xflag field to 'struct mount'. File system modules need to be
990 Bump __FreeBSD_version to 800093.
993 The compiling option ADAPTIVE_SX has been retired while it has been
994 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
995 The KPI for sx_init_flags() changes as accepting flags:
996 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
997 been introduced in order to handle the reversed logic.
998 Bump __FreeBSD_version to 800092.
1001 Add support for hierarchical jails. Remove global securelevel.
1002 Bump __FreeBSD_version to 800091.
1005 The layout of struct vnet_net has changed, therefore modules
1007 Bump __FreeBSD_version to 800090.
1010 The newly imported zic(8) produces a new format in the output. Please
1011 run tzsetup(8) to install the newly created data to /etc/localtime.
1014 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1015 hw.usb.* and is now consistent again with previous releases.
1018 802.11 monitor mode support was revised and driver api's were changed.
1019 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1020 of DLT_IEEE802_11. No user-visible data structures were changed but
1021 applications that use DLT_IEEE802_11 may require changes.
1022 Bump __FreeBSD_version to 800088.
1025 The layout of the following structs has changed: sysctl_oid,
1026 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1027 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1028 panics may be experienced. World rebuild is required for
1029 correctly checking networking state from userland.
1030 Bump __FreeBSD_version to 800085.
1033 MLDv2 and Source-Specific Multicast (SSM) have been merged
1034 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1035 The implementation of SSM within FreeBSD's IPv6 stack closely
1036 follows the IPv4 implementation.
1038 For kernel developers:
1040 * The most important changes are that the ip6_output() and
1041 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1042 and this lock has been downgraded to a non-recursive mutex.
1044 * As with the changes to the IPv4 stack to support SSM, filtering
1045 of inbound multicast traffic must now be performed by transport
1046 protocols within the IPv6 stack. This does not apply to TCP and
1047 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1049 * The KPIs used by IPv6 multicast are similar to those used by
1050 the IPv4 stack, with the following differences:
1051 * im6o_mc_filter() is analogous to imo_multicast_filter().
1052 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1053 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1054 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1055 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1056 for MLDv1 have an additional 'timer' argument which is used to
1057 jitter the initial membership report for the solicited-node
1058 multicast membership on-link.
1059 * This is not strictly needed for MLDv2, which already jitters
1060 its report transmissions. However, the 'timer' argument is
1061 preserved in case MLDv1 is active on the interface.
1063 * The KAME linked-list based IPv6 membership implementation has
1064 been refactored to use a vector similar to that used by the IPv4
1066 Code which maintains a list of its own multicast memberships
1067 internally, e.g. carp, has been updated to reflect the new
1070 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1071 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1072 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1073 implementation constraint which needs to be addressed in HEAD.
1075 For application developers:
1077 * The changes are broadly similar to those made for the IPv4
1080 * The use of IPv4 and IPv6 multicast socket options on the same
1081 socket, using mapped addresses, HAS NOT been tested or supported.
1083 * There are a number of issues with the implementation of various
1084 IPv6 multicast APIs which need to be resolved in the API surface
1085 before the implementation is fully compatible with KAME userland
1086 use, and these are mostly to do with interface index treatment.
1088 * The literature available discusses the use of either the delta / ASM
1089 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1090 using setsourcefilter(3)/getsourcefilter(3). For more information
1091 please refer to RFC 3768, 'Socket Interface Extensions for
1092 Multicast Source Filters'.
1094 * Applications which use the published RFC 3678 APIs should be fine.
1096 For systems administrators:
1098 * The mtest(8) utility has been refactored to support IPv6, in
1099 addition to IPv4. Interface addresses are no longer accepted
1100 as arguments, their names must be used instead. The utility
1101 will map the interface name to its first IPv4 address as
1102 returned by getifaddrs(3).
1104 * The ifmcstat(8) utility has also been updated to print the MLDv2
1105 endpoint state and source filter lists via sysctl(3).
1107 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1108 loopback of IPv6 multicast datagrams by default; it defaults to 1
1109 to preserve the existing behaviour. Disabling multicast loopback is
1110 recommended for optimal system performance.
1112 * The IPv6 MROUTING code has been changed to examine this sysctl
1113 instead of attempting to perform a group lookup before looping
1114 back forwarded datagrams.
1116 Bump __FreeBSD_version to 800084.
1119 Implement low-level Bluetooth HCI API.
1120 Bump __FreeBSD_version to 800083.
1123 The layout of struct malloc_type, used by modules to register new
1124 memory allocation types, has changed. Most modules will need to
1125 be rebuilt or panics may be experienced.
1126 Bump __FreeBSD_version to 800081.
1129 Anticipate overflowing inp_flags - add inp_flags2.
1130 This changes most offsets in inpcb, so checking v4 connection
1131 state will require a world rebuild.
1132 Bump __FreeBSD_version to 800080.
1135 Add an llentry to struct route and struct route_in6. Modules
1136 embedding a struct route will need to be recompiled.
1137 Bump __FreeBSD_version to 800079.
1140 The size of rt_metrics_lite and by extension rtentry has changed.
1141 Networking administration apps will need to be recompiled.
1142 The route command now supports show as an alias for get, weighting
1143 of routes, sticky and nostick flags to alter the behavior of stateful
1145 Bump __FreeBSD_version to 800078.
1148 Do not use Giant for kbdmux(4) locking. This is wrong and
1149 apparently causing more problems than it solves. This will
1150 re-open the issue where interrupt handlers may race with
1151 kbdmux(4) in polling mode. Typical symptoms include (but
1152 not limited to) duplicated and/or missing characters when
1153 low level console functions (such as gets) are used while
1154 interrupts are enabled (for example geli password prompt,
1155 mountroot prompt etc.). Disabling kbdmux(4) may help.
1158 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1159 kernel modules referencing any of the above need to be recompiled.
1160 Bump __FreeBSD_version to 800075.
1163 GEOM_PART has become the default partition slicer for storage devices,
1164 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1165 introduces some changes:
1167 MSDOS/EBR: the devices created from MSDOS extended partition entries
1168 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1169 to devices with offset-based names. fstabs may need to be modified.
1171 BSD: the "geometry does not match label" warning is harmless in most
1172 cases but it points to problems in file system misalignment with
1173 disk geometry. The "c" partition is now implicit, covers the whole
1174 top-level drive and cannot be (mis)used by users.
1176 General: Kernel dumps are now not allowed to be written to devices
1177 whose partition types indicate they are meant to be used for file
1178 systems (or, in case of MSDOS partitions, as something else than
1181 Most of these changes date approximately from 200812.
1184 The uscanner(4) driver has been removed from the kernel. This follows
1185 Linux removing theirs in 2.6 and making libusb the default interface
1186 (supported by sane).
1189 The multicast forwarding code has been cleaned up. netstat(1)
1190 only relies on KVM now for printing bandwidth upcall meters.
1191 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1192 ip6_mroute_mod respectively. The config(5) options for statically
1193 compiling this code remain the same, i.e. 'options MROUTING'.
1196 Support for the IFF_NEEDSGIANT network interface flag has been
1197 removed, which means that non-MPSAFE network device drivers are no
1198 longer supported. In particular, if_ar, if_sr, and network device
1199 drivers from the old (legacy) USB stack can no longer be built or
1203 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1204 a bunch of new language catalog files have also been added.
1205 This means that some common libc messages are now localized and
1206 they depend on the LC_MESSAGES environmental variable.
1209 The k8temp(4) driver has been renamed to amdtemp(4) since
1210 support for Family 10 and Family 11 CPU families was added.
1213 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1214 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1216 For kernel developers, the most important changes are that the
1217 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1218 and this lock has been downgraded to a non-recursive mutex.
1220 Transport protocols (UDP, Raw IP) are now responsible for filtering
1221 inbound multicast traffic according to group membership and source
1222 filters. The imo_multicast_filter() KPI exists for this purpose.
1223 Transports which do not use multicast (SCTP, TCP) already reject
1224 multicast by default. Forwarding and receive performance may improve
1225 as a mutex acquisition is no longer needed in the ip_input()
1226 low-level input path. in_addmulti() and in_delmulti() are shimmed
1227 to new KPIs which exist to support SSM in-kernel.
1229 For application developers, it is recommended that loopback of
1230 multicast datagrams be disabled for best performance, as this
1231 will still cause the lock to be taken for each looped-back
1232 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1233 be tuned to 0 to disable loopback by default; it defaults to 1
1234 to preserve the existing behaviour.
1236 For systems administrators, to obtain best performance with
1237 multicast reception and multiple groups, it is always recommended
1238 that a card with a suitably precise hash filter is used. Hash
1239 collisions will still result in the lock being taken within the
1240 transport protocol input path to check group membership.
1242 If deploying FreeBSD in an environment with IGMP snooping switches,
1243 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1244 enabled; this forces 224.0.0.0/24 group membership to be announced
1247 The size of 'struct igmpstat' has changed; netstat needs to be
1248 recompiled to reflect this.
1249 Bump __FreeBSD_version to 800070.
1252 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1253 updated to use it. This requires a buildworld/installworld in order to
1254 update the library and dependencies (usbconfig, etc). Its advisable to
1255 rebuild all ports which uses libusb. More specific directions are given
1256 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1257 libusb are no longer required and can be removed.
1260 A workaround is committed to allow the creation of System V shared
1261 memory segment of size > 2 GB on the 64-bit architectures.
1262 Due to a limitation of the existing ABI, the shm_segsz member
1263 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1264 wrong for large segments. Note that limits must be explicitly
1265 raised to allow such segments to be created.
1268 The layout of struct ifnet has changed, requiring a rebuild of all
1269 network device driver modules.
1272 The /dev handling for the new USB stack has changed, a
1273 buildworld/installworld is required for libusb20.
1276 The new USB2 stack has now been permanently moved in and all kernel and
1277 module names reverted to their previous values (eg, usb, ehci, ohci,
1278 ums, ...). The old usb stack can be compiled in by prefixing the name
1279 with the letter 'o', the old usb modules have been removed.
1280 Updating entry 20090216 for xorg and 20090215 for libmap may still
1284 The rc.conf(5) option if_up_delay has been renamed to
1285 defaultroute_delay to better reflect its purpose. If you have
1286 customized this setting in /etc/rc.conf you need to update it to
1290 xorg 7.4 wants to configure its input devices via hald which does not
1291 yet work with USB2. If the keyboard/mouse does not work in xorg then
1293 Option "AllowEmptyInput" "off"
1294 to your ServerLayout section. This will cause X to use the configured
1295 kbd and mouse sections from your xorg.conf.
1298 The GENERIC kernels for all architectures now default to the new USB2
1299 stack. No kernel config options or code have been removed so if a
1300 problem arises please report it and optionally revert to the old USB
1301 stack. If you are loading USB kernel modules or have a custom kernel
1302 that includes GENERIC then ensure that usb names are also changed over,
1303 eg uftdi -> usb2_serial_ftdi.
1305 Older programs linked against the ports libusb 0.1 need to be
1306 redirected to the new stack's libusb20. /etc/libmap.conf can
1308 # Map old usb library to new one for usb2 stack
1309 libusb-0.1.so.8 libusb20.so.1
1312 All USB ethernet devices now attach as interfaces under the name ueN
1313 (eg. ue0). This is to provide a predictable name as vendors often
1314 change usb chipsets in a product without notice.
1317 The ichsmb(4) driver has been changed to require SMBus slave
1318 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1319 All of the other SMBus controller drivers require left-justified
1320 slave addresses, so this change makes all the drivers provide the
1324 INET6 statistics (struct ip6stat) was updated.
1325 netstat(1) needs to be recompiled.
1328 NTFS has been removed from GENERIC kernel on amd64 to match
1329 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1330 will load ntfs.ko module automatically when NTFS support is
1331 actually needed, unless ntfs.ko is not installed or security
1332 level prohibits loading kernel modules. If either is the case,
1333 "options NTFS" has to be added into kernel config.
1336 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1337 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1338 800061. User space tools that rely on the size of struct tcpcb in
1339 tcp_var.h (e.g. sockstat) need to be recompiled.
1342 ng_tty(4) module updated to match the new TTY subsystem.
1343 Due to API change, user-level applications must be updated.
1344 New API support added to mpd5 CVS and expected to be present
1345 in next mpd5.3 release.
1348 With __FreeBSD_version 800060 the makefs tool is part of
1349 the base system (it was a port).
1352 The afdata and ifnet locks have been changed from mutexes to
1353 rwlocks, network modules will need to be re-compiled.
1356 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1357 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1358 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1359 architecture and 40 bytes on 64-bit architecture. The userland
1360 applications "arp" and "ndp" have been updated accordingly.
1361 The output from "netstat -r" shows only routing entries and
1362 none of the L2 information.
1365 __FreeBSD_version 800057 marks the switchover from the
1366 binary ath hal to source code. Users must add the line:
1368 options AH_SUPPORT_AR5416
1370 to their kernel config files when specifying:
1374 The ath_hal module no longer exists; the code is now compiled
1375 together with the driver in the ath module. It is now
1376 possible to tailor chip support (i.e. reduce the set of chips
1377 and thereby the code size); consult ath_hal(4) for details.
1380 __FreeBSD_version 800054 adds memory barriers to
1381 <machine/atomic.h>, new interfaces to ifnet to facilitate
1382 multiple hardware transmit queues for cards that support
1383 them, and a lock-less ring-buffer implementation to
1384 enable drivers to more efficiently manage queueing of
1388 A new version of ZFS (version 13) has been merged to -HEAD.
1389 This version has zpool attribute "listsnapshots" off by
1390 default, which means "zfs list" does not show snapshots,
1391 and is the same as Solaris behavior.
1394 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1397 The uhci, ohci, ehci and slhci USB Host controller drivers have
1398 been put into separate modules. If you load the usb module
1399 separately through loader.conf you will need to load the
1400 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1401 controller add the following to loader.conf:
1407 The ABI used by the PMC toolset has changed. Please keep
1408 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1412 atapci kernel module now includes only generic PCI ATA
1413 driver. AHCI driver moved to ataahci kernel module.
1414 All vendor-specific code moved into separate kernel modules:
1415 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1416 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1417 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1418 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1421 The TTY subsystem of the kernel has been replaced by a new
1422 implementation, which provides better scalability and an
1423 improved driver model. Most common drivers have been migrated to
1424 the new TTY subsystem, while others have not. The following
1425 drivers have not yet been ported to the new TTY layer:
1428 cy, digi, rc, rp, sio
1434 ng_h4, ng_tty, ppp, sl, snp
1436 Adding these drivers to your kernel configuration file shall
1437 cause compilation to fail.
1440 ntpd has been upgraded to 4.2.4p5.
1443 OpenSSH has been upgraded to 5.1p1.
1445 For many years, FreeBSD's version of OpenSSH preferred DSA
1446 over RSA for host and user authentication keys. With this
1447 upgrade, we've switched to the vendor's default of RSA over
1448 DSA. This may cause upgraded clients to warn about unknown
1449 host keys even for previously known hosts. Users should
1450 follow the usual procedure for verifying host keys before
1451 accepting the RSA key.
1453 This can be circumvented by setting the "HostKeyAlgorithms"
1454 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1457 Please note that the sequence of keys offered for
1458 authentication has been changed as well. You may want to
1459 specify IdentityFile in a different order to revert this
1463 The sio(4) driver has been removed from the i386 and amd64
1464 kernel configuration files. This means uart(4) is now the
1465 default serial port driver on those platforms as well.
1467 To prevent collisions with the sio(4) driver, the uart(4) driver
1468 uses different names for its device nodes. This means the
1469 onboard serial port will now most likely be called "ttyu0"
1470 instead of "ttyd0". You may need to reconfigure applications to
1471 use the new device names.
1473 When using the serial port as a boot console, be sure to update
1474 /boot/device.hints and /etc/ttys before booting the new kernel.
1475 If you forget to do so, you can still manually specify the hints
1476 at the loader prompt:
1478 set hint.uart.0.at="isa"
1479 set hint.uart.0.port="0x3F8"
1480 set hint.uart.0.flags="0x10"
1481 set hint.uart.0.irq="4"
1485 The gpt(8) utility has been removed. Use gpart(8) to partition
1489 The version that Linuxulator emulates was changed from 2.4.2
1490 to 2.6.16. If you experience any problems with Linux binaries
1491 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1492 if it fixes the problem contact emulation mailing list.
1495 ISDN4BSD (I4B) was removed from the src tree. You may need to
1496 update a your kernel configuration and remove relevant entries.
1499 I have checked in code to support multiple routing tables.
1500 See the man pages setfib(1) and setfib(2).
1501 This is a hopefully backwards compatible version,
1502 but to make use of it you need to compile your kernel
1503 with options ROUTETABLES=2 (or more up to 16).
1506 The 802.11 wireless support was redone to enable multi-bss
1507 operation on devices that are capable. The underlying device
1508 is no longer used directly but instead wlanX devices are
1509 cloned with ifconfig. This requires changes to rc.conf files.
1510 For example, change:
1511 ifconfig_ath0="WPA DHCP"
1514 ifconfig_wlan0="WPA DHCP"
1515 see rc.conf(5) for more details. In addition, mergemaster of
1516 /etc/rc.d is highly recommended. Simultaneous update of userland
1517 and kernel wouldn't hurt either.
1519 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1520 modules were merged into the base wlan module. All references
1521 to these modules (e.g. in kernel config files) must be removed.
1524 psm(4) has gained write(2) support in native operation level.
1525 Arbitrary commands can be written to /dev/psm%d and status can
1526 be read back from it. Therefore, an application is responsible
1527 for status validation and error recovery. It is a no-op in
1528 other operation levels.
1531 Support for KSE threading has been removed from the kernel. To
1532 run legacy applications linked against KSE libmap.conf may
1533 be used. The following libmap.conf may be used to ensure
1534 compatibility with any prior release:
1536 libpthread.so.1 libthr.so.1
1537 libpthread.so.2 libthr.so.2
1538 libkse.so.3 libthr.so.3
1541 The layout of struct vmspace has changed. This affects libkvm
1542 and any executables that link against libkvm and use the
1543 kvm_getprocs() function. In particular, but not exclusively,
1544 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1545 The effects are minimal, but it's advisable to upgrade world
1549 The latest em driver no longer has support in it for the
1550 82575 adapter, this is now moved to the igb driver. The
1551 split was done to make new features that are incompatible
1552 with older hardware easier to do.
1555 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1556 likewise the kernel option is now GEOM_LINUX_LVM.
1559 The default NFS mount mode has changed from UDP to TCP for
1560 increased reliability. If you rely on (insecurely) NFS
1561 mounting across a firewall you may need to update your
1565 Belatedly note the addition of m_collapse for compacting
1569 The fts(3) structures have been changed to use adequate
1570 integer types for their members and so to be able to cope
1571 with huge file trees. The old fts(3) ABI is preserved
1572 through symbol versioning in libc, so third-party binaries
1573 using fts(3) should still work, although they will not take
1574 advantage of the extended types. At the same time, some
1575 third-party software might fail to build after this change
1576 due to unportable assumptions made in its source code about
1577 fts(3) structure members. Such software should be fixed
1578 by its vendor or, in the worst case, in the ports tree.
1579 FreeBSD_version 800015 marks this change for the unlikely
1580 case that a portable fix is impossible.
1583 To upgrade to -current after this date, you must be running
1584 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1585 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1588 The ADAPTIVE_GIANT kernel option has been retired because its
1589 functionality is the default now.
1592 The AT keyboard emulation of sunkbd(4) has been turned on
1593 by default. In order to make the special symbols of the Sun
1594 keyboards driven by sunkbd(4) work under X these now have
1595 to be configured the same way as Sun USB keyboards driven
1596 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1598 Option "XkbLayout" "us"
1599 Option "XkbRules" "xorg"
1600 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1603 It has been decided that it is desirable to provide ABI
1604 backwards compatibility to the FreeBSD 4/5/6 versions of the
1605 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1606 broken with the introduction of PCI domain support (see the
1607 20070930 entry). Unfortunately, this required the ABI of
1608 PCIOCGETCONF to be broken again in order to be able to
1609 provide backwards compatibility to the old version of that
1610 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1611 again. As for prominent ports this affects neither pciutils
1612 nor xorg-server this time, the hal port needs to be rebuilt
1616 The misnamed kthread_create() and friends have been renamed
1617 to kproc_create() etc. Many of the callers already
1618 used kproc_start()..
1619 I will return kthread_create() and friends in a while
1620 with implementations that actually create threads, not procs.
1621 Renaming corresponds with version 800002.
1630 Avoid using make -j when upgrading. While generally safe, there are
1631 sometimes problems using -j to upgrade. If your upgrade fails with
1632 -j, please try again without -j. From time to time in the past there
1633 have been problems using -j with buildworld and/or installworld. This
1634 is especially true when upgrading between "distant" versions (eg one
1635 that cross a major release boundary or several minor releases, or when
1636 several months have passed on the -current branch).
1638 Sometimes, obscure build problems are the result of environment
1639 poisoning. This can happen because the make utility reads its
1640 environment when searching for values for global variables. To run
1641 your build attempts in an "environmental clean room", prefix all make
1642 commands with 'env -i '. See the env(1) manual page for more details.
1644 When upgrading from one major version to another it is generally best
1645 to upgrade to the latest code in the currently installed branch first,
1646 then do an upgrade to the new branch. This is the best-tested upgrade
1647 path, and has the highest probability of being successful. Please try
1648 this approach before reporting problems with a major version upgrade.
1652 When upgrading the boot ZFS pool to a new version, always follow
1655 1.) recompile and reinstall the ZFS boot loader and boot block
1656 (this is part of "make buildworld" and "make installworld")
1658 2.) update the ZFS boot block on your boot drive
1660 The following example updates the ZFS boot block on the first
1661 partition (freebsd-boot) of a GPT partitioned drive ad0:
1662 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1664 Non-boot pools do not need these updates.
1668 If you are updating from a prior version of FreeBSD (even one just
1669 a few days old), you should follow this procedure. It is the most
1670 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1672 make kernel-toolchain
1673 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1674 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1676 To test a kernel once
1677 ---------------------
1678 If you just want to boot a kernel once (because you are not sure
1679 if it works, or if you want to boot a known bad kernel to provide
1680 debugging information) run
1681 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1682 nextboot -k testkernel
1684 To just build a kernel when you know that it won't mess you up
1685 --------------------------------------------------------------
1686 This assumes you are already running a CURRENT system. Replace
1687 ${arch} with the architecture of your machine (e.g. "i386",
1688 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1690 cd src/sys/${arch}/conf
1691 config KERNEL_NAME_HERE
1692 cd ../compile/KERNEL_NAME_HERE
1697 If this fails, go to the "To build a kernel" section.
1699 To rebuild everything and install it on the current system.
1700 -----------------------------------------------------------
1701 # Note: sometimes if you are running current you gotta do more than
1702 # is listed here if you are upgrading from a really old current.
1704 <make sure you have good level 0 dumps>
1706 make kernel KERNCONF=YOUR_KERNEL_HERE
1708 <reboot in single user> [3]
1716 To cross-install current onto a separate partition
1717 --------------------------------------------------
1718 # In this approach we use a separate partition to hold
1719 # current's root, 'usr', and 'var' directories. A partition
1720 # holding "/", "/usr" and "/var" should be about 2GB in
1723 <make sure you have good level 0 dumps>
1726 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1727 <maybe newfs current's root partition>
1728 <mount current's root partition on directory ${CURRENT_ROOT}>
1729 make installworld DESTDIR=${CURRENT_ROOT}
1730 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1731 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1732 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1733 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1734 <reboot into current>
1735 <do a "native" rebuild/install as described in the previous section>
1736 <maybe install compatibility libraries from ports/misc/compat*>
1740 To upgrade in-place from stable to current
1741 ----------------------------------------------
1742 <make sure you have good level 0 dumps>
1744 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1746 <reboot in single user> [3]
1753 Make sure that you've read the UPDATING file to understand the
1754 tweaks to various things you need. At this point in the life
1755 cycle of current, things change often and you are on your own
1756 to cope. The defaults can also change, so please read ALL of
1757 the UPDATING entries.
1759 Also, if you are tracking -current, you must be subscribed to
1760 freebsd-current@freebsd.org. Make sure that before you update
1761 your sources that you have read and understood all the recent
1762 messages there. If in doubt, please track -stable which has
1763 much fewer pitfalls.
1765 [1] If you have third party modules, such as vmware, you
1766 should disable them at this point so they don't crash your
1769 [3] From the bootblocks, boot -s, and then do
1774 adjkerntz -i # if CMOS is wall time
1775 Also, when doing a major release upgrade, it is required that
1776 you boot into single user mode to do the installworld.
1778 [4] Note: This step is non-optional. Failure to do this step
1779 can result in a significant reduction in the functionality of the
1780 system. Attempting to do it by hand is not recommended and those
1781 that pursue this avenue should read this file carefully, as well
1782 as the archives of freebsd-current and freebsd-hackers mailing lists
1783 for potential gotchas. The -U option is also useful to consider.
1784 See mergemaster(8) for more information.
1786 [5] Usually this step is a noop. However, from time to time
1787 you may need to do this if you get unknown user in the following
1788 step. It never hurts to do it all the time. You may need to
1789 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1790 install) after the buildworld before this step if you last updated
1791 from [78]-stable or 9-stable before 20130430.
1793 [6] This only deletes old files and directories. Old libraries
1794 can be deleted by "make delete-old-libs", but you have to make
1795 sure that no program is using those libraries anymore.
1797 [8] In order to have a kernel that can run the 4.x binaries needed to
1798 do an installworld, you must include the COMPAT_FREEBSD4 option in
1799 your kernel. Failure to do so may leave you with a system that is
1800 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1801 required to run the 5.x binaries on more recent kernels. And so on
1802 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1804 Make sure that you merge any new devices from GENERIC since the
1805 last time you updated your kernel config file.
1807 [9] When checking out sources, you must include the -P flag to have
1808 cvs prune empty directories.
1810 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1811 "?=" instead of the "=" assignment operator, so that buildworld can
1812 override the CPUTYPE if it needs to.
1814 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1815 not on the command line, or in /etc/make.conf. buildworld will
1816 warn if it is improperly defined.
1819 This file contains a list, in reverse chronological order, of major
1820 breakages in tracking -current. It is not guaranteed to be a complete
1821 list of such breakages, and only contains entries since October 10, 2007.
1822 If you need to see UPDATING entries from before that date, you will need
1823 to fetch an UPDATING file from an older FreeBSD release.
1825 Copyright information:
1827 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1829 Redistribution, publication, translation and use, with or without
1830 modification, in full or in part, in any form or format of this
1831 document are permitted without further permission from the author.
1833 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1834 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1835 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1836 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1837 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1838 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1839 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1840 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1841 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1842 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1843 POSSIBILITY OF SUCH DAMAGE.
1845 Contact Warner Losh if you have any questions about your use of