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