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