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