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