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