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