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