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