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 20150114: p8 FreeBSD-SA-15:01.openssl
15 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
17 20141223: p7 FreeBSD-SA-14:31.ntp
18 FreeBSD-EN-14:13.freebsd-update
20 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
21 Fix directory deletion issue in freebsd-update. [EN-14:13]
23 20141210: p6 FreeBSD-SA-14:28.file
26 Fix multiple vulnerabilities in file(1) and libmagic(3).
29 Fix BIND remote denial of service vulnerability. [SA-14:29]
31 20141104: p5 FreeBSD-SA-14:25.setlogin
35 Fix kernel stack disclosure in setlogin(2) / getlogin(2).
38 Fix remote command execution in ftp(1). [SA-14:26]
40 Fix NFSv4 and ZFS cache consistency issue. [EN-14:12]
42 20141022: p4 FreeBSD-EN-14:10.tzdata
43 FreeBSD-EN-14:11.crypt
45 Time zone data file update. [EN-14:10]
47 Change crypt(3) default hashing algorithm back to DES. [EN-14:11]
49 20141021: p3 FreeBSD-SA-14:20.rtsold
50 FreeBSD-SA-14:21.routed
51 FreeBSD-SA-14:22.namei
52 FreeBSD-SA-14:23.openssl
54 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
56 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
58 Fix memory leak in sandboxed namei lookup. [SA-14:22]
60 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
62 20140916: p2 FreeBSD-SA-14:19.tcp
63 Fix Denial of Service in TCP packet processing. [SA-14:19]
65 20140909: p1 FreeBSD-SA-14:18.openssl
66 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
72 On i386 and amd64 systems, the onifconsole flag is now set by default
73 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
74 as a login TTY if it is set in the bootloader as an active kernel
75 console. No changes in behavior should result otherwise. To revert to
76 the previous behavior, set ttyu0 to "off" in /etc/ttys.
79 Clang and llvm have been upgraded to 3.4.1 release.
82 Clang and llvm have been upgraded to 3.4 release.
85 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
86 been deprecated and will not be part of FreeBSD 11.0 and later
87 releases. If you use this driver, please consider switching to
88 the nfe(4) driver instead.
91 The behavior of gss_pseudo_random() for the krb5 mechanism
92 has changed, for applications requesting a longer random string
93 than produced by the underlying enctype's pseudo-random() function.
94 In particular, the random string produced from a session key of
95 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
96 be different at the 17th octet and later, after this change.
97 The counter used in the PRF+ construction is now encoded as a
98 big-endian integer in accordance with RFC 4402.
99 __FreeBSD_version is bumped to 902505.
105 Behavior of devfs rules path matching has been changed.
106 Pattern is now always matched against fully qualified devfs
107 path and slash characters must be explicitly matched by
108 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
109 subdirectories must be reviewed.
112 hastctl(8)'s `status' command output changed to terse one-liner format.
113 Scripts using this should switch to `list' command or be rewritten.
116 Fix a bug that allowed a tracing process (e.g. gdb) to write
117 to a memory-mapped file in the traced process's address space
118 even if neither the traced process nor the tracing process had
119 write access to that file.
122 Added ZFS TRIM support which is enabled by default. To disable
123 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
125 Creating new ZFS pools and adding new devices to existing pools
126 first performs a full device level TRIM which can take a significant
127 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
128 to disable this behaviour.
130 ZFS TRIM requires the underlying device support BIO_DELETE which
131 is currently provided by methods such as ATA TRIM and SCSI UNMAP
132 via CAM, which are typically supported by SSD's.
134 Stats for ZFS TRIM can be monitored by looking at the sysctl's
135 under kstat.zfs.misc.zio_trim.
138 `list' command has been added to hastctl(8). For now, it is full
139 equivalent of `status' command.
140 WARNING: in the near future the output of hastctl's status command
141 will change to more terse format. If you use `hastctl status'
142 for parsing in your scripts, switch to `hastctl list'.
145 The mergemaster command now uses the default MAKEOBJDIRPREFIX
146 rather than creating it's own in the temporary directory in
147 order allow access to bootstrapped versions of tools such as
148 install and mtree. When upgrading from version of FreeBSD where
149 the install command does not support -l, you will need to
150 install a new mergemaster command if mergemaster -p is required.
151 This can be accomplished with the command (cd src/usr.sbin/mergemaster
154 Due to the use of the new -l option to install(1) during build
155 and install, you must take care not to directly set the INSTALL
156 make variable in your /etc/make.conf, /etc/src.conf, or on the
157 command line. If you wish to use the -C flag for all installs
158 you may be able to add INSTALL+=-C to /etc/make.conf or
162 Fix a bug that allows NFS clients to issue READDIR on files.
165 The install(1) option -M has changed meaning and now takes an
166 argument that is a file or path to append logs to. In the
167 unlikely event that -M was the last option on the command line
168 and the command line contained at least two files and a target
169 directory the first file will have logs appended to it. The -M
170 option served little practical purpose in the last decade so it's
171 used expected to be extremely rare.
174 A new compression method (lz4) has been merged to. Please refer to
175 zpool-features(7) for more information.
177 Please refer to the "ZFS notes" section of this file for information
178 on upgrading boot ZFS pools.
181 The VFS KBI was changed with the merge of several nullfs
182 optimizations and fixes. All filesystem modules must be
186 With the addition of auditdistd(8), a new auditdistd user is now
187 depended on during installworld. "mergemaster -p" can be used to add
188 the user prior to installworld, as documented in the handbook.
194 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
195 Starting with this version the old system of ZFS pool versioning
196 is superseded by "feature flags". This concept enables forward
197 compatibility against certain future changes in functionality of ZFS
198 pools. The first two read-only compatible "feature flags" for ZFS
199 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
200 For more information read the new zpool-features(7) manual page.
201 Please refer to the "ZFS notes" section of this file for information
202 on upgrading boot ZFS pools.
205 The commit introducing bsd.compiler.mk breaks the traditional
206 building of kernels before this point. Add -m ${SRC}/share/mk
207 (for the right value of SRC) to your command lines to work
208 around; update your useland to a point after this; or use the
209 buildkernel/installkernel top-level targets. See also 20120829.
212 The IPFIREWALL_FORWARD kernel option has been removed. Its
213 functionality now turned on by default.
216 The random(4) support for the VIA hardware random number
217 generator (`PADLOCK') is no longer enabled unconditionally.
218 Add the PADLOCK_RNG option in the custom kernel config if
219 needed. The GENERIC kernels on i386 and amd64 do include the
220 option, so the change only affects the custom kernel
224 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
225 the traditional method, you must update your system with an installworld
226 before the kernel will build. The documented make buildkernel/installkernel
227 interfaces (coupled with fresh make kernel-toolchain) continue to work.
230 The sparc64 ZFS loader has been changed to no longer try to auto-
231 detect ZFS providers based on diskN aliases but now requires these
232 to be explicitly listed in the OFW boot-device environment variable.
235 Now unix domain sockets behave "as expected" on nullfs(5). Previously
236 nullfs(5) did not pass through all behaviours to the underlying layer,
237 as a result if we bound to a socket on the lower layer we could connect
238 only to the lower path; if we bound to the upper layer we could connect
239 only to the upper path. The new behavior is one can connect to both the
240 lower and the upper paths regardless what layer path one binds to.
243 The acpi_wmi(4) status device /dev/wmistat has been renamed to
247 A new VOP_ADVISE() was added to support posix_fadvise(2). All
248 filesystem modules must be recompiled.
251 The interface of the VOP_VPTOCNP(9) changed, now the returned
252 vnode shall be referenced, previously it was required to be
253 only held. All in-tree filesystems are converted.
259 The broken amd(4) driver has been replaced with esp(4) in the amd64,
260 i386 and pc98 GENERIC kernel configuration files.
263 This commit modifies vfs_register() so that it uses a hash
264 calculation to set vfc_typenum, which is enabled by default.
265 The first time a system is booted after this change, the
266 vfc_typenum values will change for all file systems. The
267 main effect of this is a change to the NFS server file handles
268 for file systems that use vfc_typenum in their fsid, such as ZFS.
269 It will, however, prevent vfc_typenum from changing when file
270 systems are loaded in a different order for subsequent reboots.
271 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
272 until you are ready to remount all NFS clients after a reboot.
275 Bump the shared library version numbers for libraries that
276 do not use symbol versioning, have changed the ABI compared
277 to stable/8 and which shared library version was not bumped.
278 Done as part of 9.0-RELEASE cycle.
281 During the merge of Capsicum features, the fget(9) KPI was modified.
282 This may require the rebuilding of out-of-tree device drivers --
283 issues have been reported specifically with the nVidia device driver.
284 __FreeBSD_version is bumped to 900041.
286 Also, there is a period between 20110811 and 20110814 where the
287 special devices /dev/{stdin,stdout,stderr} did not work correctly.
288 Building world from a kernel during that window may not work.
291 The packet filter (pf) code has been updated to OpenBSD 4.5.
292 You need to update userland tools to be in sync with kernel.
293 This update breaks backward compatibility with earlier pfsync(4)
294 versions. Care must be taken when updating redundant firewall setups.
297 The following sysctls and tunables are retired on x86 platforms:
299 machdep.hlt_logical_cpus
300 The following sysctl is retired:
301 machdep.hyperthreading_allowed
302 The sysctls were supposed to provide a way to dynamically offline and
303 online selected CPUs on x86 platforms, but the implementation has not
304 been reliable especially with SCHED_ULE scheduler.
305 machdep.hyperthreading_allowed tunable is still available to ignore
306 hyperthreading CPUs at OS level.
307 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
308 where X is an APIC ID of a CPU. Be advised, though, that disabling
309 CPUs in non-uniform fashion will result in non-uniform topology and
310 may lead to sub-optimal system performance with SCHED_ULE, which is
314 cpumask_t type is retired and cpuset_t is used in order to describe
318 Changes to ifconfig(8) for dynamic address family detection mandate
319 that you are running a kernel of 20110525 or later. Make sure to
320 follow the update procedure to boot a new kernel before installing
324 Support for sun4v architecture is officially dropped
327 Several KPI breaking changes have been committed to the mii(4) layer,
328 the PHY drivers and consequently some Ethernet drivers using mii(4).
329 This means that miibus.ko and the modules of the affected Ethernet
330 drivers need to be recompiled.
332 Note to kernel developers: Given that the OUI bit reversion problem
333 was fixed as part of these changes all mii(4) commits related to OUIs,
334 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
335 handling, no longer can be merged verbatim to stable/8 and previous
339 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
340 into their kernel configurations along with 'device pci'.
343 The default NFS client is now the new NFS client, so fstype "newnfs"
344 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
345 Although mounts via fstype "nfs" will usually work without userland
346 changes, it is recommended that the mount(8) and mount_nfs(8)
347 commands be rebuilt from sources and that a link to mount_nfs called
348 mount_oldnfs be created. The new client is compiled into the
349 kernel with "options NFSCL" and this is needed for diskless root
350 file systems. The GENERIC kernel configs have been changed to use
351 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
352 To use the regular/old client, you can "mount -t oldnfs ...". For
353 a diskless root file system, you must also include a line like:
355 vfs.root.mountfrom="oldnfs:"
357 in the boot/loader.conf on the root fs on the NFS server to make
358 a diskless root fs use the old client.
361 The GENERIC kernels for all architectures now default to the new
362 CAM-based ATA stack. It means that all legacy ATA drivers were
363 removed and replaced by respective CAM drivers. If you are using
364 ATA device names in /etc/fstab or other places, make sure to update
365 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
366 where 'Y's are the sequential numbers starting from zero for each type
367 in order of detection, unless configured otherwise with tunables,
368 see cam(4)). There will be symbolic links created in /dev/ to map
369 old adX devices to the respective adaY. They should provide basic
370 compatibility for file systems mounting in most cases, but they do
371 not support old user-level APIs and do not have respective providers
372 in GEOM. Consider using updated management tools with new device names.
374 It is possible to load devices ahci, ata, siis and mvs as modules,
375 but option ATA_CAM should remain in kernel configuration to make ata
376 module work as CAM driver supporting legacy ATA controllers. Device ata
377 still can be used in modular fashion (atacore + ...). Modules atadisk
378 and atapi* are not used and won't affect operation in ATA_CAM mode.
379 Note that to use CAM-based ATA kernel should include CAM devices
380 scbus, pass, da (or explicitly ada), cd and optionally others. All of
381 them are parts of the cam module.
383 ataraid(4) functionality is now supported by the RAID GEOM class.
384 To use it you can load geom_raid kernel module and use graid(8) tool
385 for management. Instead of /dev/arX device names, use /dev/raid/rX.
387 No kernel config options or code have been removed, so if a problem
388 arises, please report it and optionally revert to the old ATA stack.
389 In order to do it you can remove from the kernel config:
394 , and instead add back:
395 device atadisk # ATA disk drives
396 device ataraid # ATA RAID drives
397 device atapicd # ATAPI CDROM drives
398 device atapifd # ATAPI floppy drives
399 device atapist # ATAPI tape drives
402 The default NFS server has been changed to the new server, which
403 was referred to as the experimental server. If you need to switch
404 back to the old NFS server, you must now put the "-o" option on
405 both the mountd and nfsd commands. This can be done using the
406 mountd_flags and nfs_server_flags rc.conf variables until an
407 update to the rc scripts is committed, which is coming soon.
410 The GNU Objective-C runtime library (libobjc), and other Objective-C
411 related components have been removed from the base system. If you
412 require an Objective-C library, please use one of the available ports.
415 ath(4) has been split into bus- and device- modules. if_ath contains
416 the HAL, the TX rate control and the network device code. if_ath_pci
417 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
418 contains the AHB glue. Users need to load both if_ath_pci and if_ath
419 in order to use ath on everything else.
421 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
422 need to load if_ath and if_ath_pci for ath(4) operation.
425 As part of the replacement of sysinstall, the process of building
426 release media has changed significantly. For details, please re-read
427 release(7), which has been updated to reflect the new build process.
430 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
431 is the last available version under GPLv2. It brings a number of new
432 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
433 4.1 and SSE 4.2), better support for powerpc64, a number of new
434 directives, and lots of other small improvements. See the ChangeLog
435 file in contrib/binutils for the full details.
438 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
439 compliant, and will now use half of hash for authentication.
440 This will break interoperability with all stacks (including all
441 actual FreeBSD versions) who implement
442 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
444 The only workaround with such peers is to use another HMAC
445 algorithm for IPsec ("phase 2") authentication.
448 Remove the uio_yield prototype and symbol. This function has
449 been misnamed since it was introduced and should not be
450 globally exposed with this name. The equivalent functionality
451 is now available using kern_yield(curthread->td_user_pri).
452 The function remains undocumented.
455 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
456 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
457 for scalar sysctls is defined but disabled. Code that needs
458 UQUAD to pass the type checking that must compile on older
459 systems where the define is not present can check against
460 __FreeBSD_version >= 900030.
462 The system dialog(1) has been replaced with a new version previously
463 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
464 with the previous version, but the libdialog associated with it has
465 a largely incompatible API. As such, the original version of libdialog
466 will be kept temporarily as libodialog, until its base system consumers
467 are replaced or updated. Bump __FreeBSD_version to 900030.
470 If you are trying to run make universe on a -stable system, and you get
471 the following warning:
472 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
473 unknown. config(8) likely too old."
474 or something similar to it, then you must upgrade your -stable system
475 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
476 stable/8) or build the config from the latest stable/8 branch and
477 install it on your system.
479 Prior to this date, building a current universe on 8-stable system from
480 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
481 error in the first kernel build phase. A new config on those old
482 systems will fix that problem for older versions of -current.
485 The TCP stack has been modified to allow Khelp modules to interact with
486 it via helper hook points and store per-connection data in the TCP
487 control block. Bump __FreeBSD_version to 900029. User space tools that
488 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
492 Generic IEEE 802.3 annex 31B full duplex flow control support has been
493 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
494 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
495 to take advantage of it instead of using custom implementations. This
496 means that these drivers now no longer unconditionally advertise
497 support for flow control but only do so if flow control is a selected
498 media option. This was implemented in the generic support that way in
499 order to allow flow control to be switched on and off via ifconfig(8)
500 with the PHY specific default to typically off in order to protect
501 from unwanted effects. Consequently, if you used flow control with
502 one of the above mentioned drivers you now need to explicitly enable
504 ifconfig bge0 media auto mediaopt flowcontrol
506 Along with the above mentioned changes generic support for setting
507 1000baseT master mode also has been added and brgphy(4), ciphy(4),
508 e1000phy(4) as well as ip1000phy(4) have been converted to take
509 advantage of it. This means that these drivers now no longer take the
510 link0 parameter for selecting master mode but the master media option
511 has to be used instead, for example like in the following:
512 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
514 Selection of master mode now is also available with all other PHY
515 drivers supporting 1000baseT.
518 The TCP stack has received a significant update to add support for
519 modularised congestion control and generally improve the clarity of
520 congestion control decisions. Bump __FreeBSD_version to 900025. User
521 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
522 sockstat) need to be recompiled.
525 The man(1) utility has been replaced by a new version that no longer
526 uses /etc/manpath.config. Please consult man.conf(5) for how to
527 migrate local entries to the new format.
530 The copyright strings printed by login(1) and sshd(8) at the time of a
531 new connection have been removed to follow other operating systems and
535 A workaround for a fixed ld bug has been removed in kernel code,
536 so make sure that your system ld is built from sources after
537 revision 210245 from 2010-07-19 (r211583 if building head kernel
538 on stable/8, r211584 for stable/7; both from 2010-08-21).
539 A symptom of incorrect ld version is different addresses for
540 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
543 The $ipv6_prefer variable in rc.conf(5) has been split into
544 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
546 The $ip6addrctl_policy is a variable to choose a pre-defined
547 address selection policy set by ip6addrctl(8). A value
548 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
551 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
552 flag (see an entry of 20090926) is set on an interface with no
553 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
554 security reason. If you want IPv6 link-local address on all
555 interfaces by default, set this to "YES".
557 The old ipv6_prefer="YES" is equivalent to
558 ipv6_activate_all_interfaces="YES" and
559 ip6addrctl_policy="ipv6_prefer".
562 DTrace has grown support for userland tracing. Due to this, DTrace is
563 now i386 and amd64 only.
564 dtruss(1) is now installed by default on those systems and a new
565 kernel module is needed for userland tracing: fasttrap.
566 No changes to your kernel config file are necessary to enable
567 userland tracing, but you might consider adding 'STRIP=' and
568 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
569 to have informative userland stack traces in DTrace (ustack).
572 The acpi_aiboost(4) driver has been removed in favor of the new
573 aibs(4) driver. You should update your kernel configuration file.
576 BSD grep has been imported to the base system and it is built by
577 default. It is completely BSD licensed, highly GNU-compatible, uses
578 less memory than its GNU counterpart and has a small codebase.
579 However, it is slower than its GNU counterpart, which is mostly
580 noticeable for larger searches, for smaller ones it is measurable
581 but not significant. The reason is complex, the most important factor
582 is that we lack a modern and efficient regex library and GNU
583 overcomes this by optimizing the searches internally. Future work
584 on improving the regex performance is planned, for the meantime,
585 users that need better performance, can build GNU grep instead by
586 setting the WITH_GNU_GREP knob.
589 Due to the import of powerpc64 support, all existing powerpc kernel
590 configuration files must be updated with a machine directive like this:
591 machine powerpc powerpc
593 In addition, an updated config(8) is required to build powerpc kernels
597 A new version of ZFS (version 15) has been merged to -HEAD.
598 This version uses a python library for the following subcommands:
599 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
600 For full functionality of these commands the following port must
601 be installed: sysutils/py-zfs
604 'vm_page's are now hashed by physical address to an array of mutexes.
605 Currently this is only used to serialize access to hold_count. Over
606 time the page queue mutex will be peeled away. This changes the size
607 of pmap on every architecture. And requires all callers of vm_page_hold
608 and vm_page_unhold to be updated.
611 WITH_CTF can now be specified in src.conf (not recommended, there
612 are some problems with static executables), make.conf (would also
613 affect ports which do not use GNU make and do not override the
614 compile targets) or in the kernel config (via "makeoptions
616 When WITH_CTF was specified there before this was silently ignored,
617 so make sure that WITH_CTF is not used in places which could lead
618 to unwanted behavior.
621 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
622 to allow 32-bit compatibility on non-x86 platforms. All kernel
623 configurations on amd64 and ia64 platforms using these options must
624 be modified accordingly.
627 The utmp user accounting database has been replaced with utmpx,
628 the user accounting interface standardized by POSIX.
629 Unfortunately the semantics of utmp and utmpx don't match,
630 making it practically impossible to support both interfaces.
631 The user accounting database is used by tools like finger(1),
632 last(1), talk(1), w(1) and ac(8).
634 All applications in the base system use utmpx. This means only
635 local binaries (e.g. from the ports tree) may still use these
636 utmp database files. These applications must be rebuilt to make
639 After the system has been upgraded, it is safe to remove the old
640 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
641 assuming their contents is of no importance anymore. Old wtmp
642 databases can only be used by last(1) and ac(8) after they have
643 been converted to the new format using wtmpcvt(1).
646 Introduce the kernel thread "deadlock resolver" (which can be enabled
647 via the DEADLKRES option, see NOTES for more details) and the
648 sleepq_type() function for sleepqueues.
651 The rc.firewall and rc.firewall6 were unified, and
652 rc.firewall6 and rc.d/ip6fw were removed.
653 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
654 variables are obsoleted. Instead, the following new rc
655 variables are added to rc.d/ipfw:
657 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
658 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
659 firewall_simple_onet_ipv6, firewall_trusted_ipv6
661 The meanings correspond to the relevant IPv4 variables.
667 The default terminal emulation for syscons(4) has been changed
668 from cons25 to xterm on all platforms except pc98. This means
669 that the /etc/ttys file needs to be updated to ensure correct
670 operation of applications on the console.
672 The terminal emulation style can be toggled per window by using
673 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
674 options can be used to change the compile-time default back to
677 To prevent graphical artifacts, make sure the TERM environment
678 variable is set to match the terminal emulation that is being
679 performed by syscons(4).
682 The layout of the structure ieee80211req_scan_result has changed.
683 Applications that require wireless scan results (e.g. ifconfig(8))
684 from net80211 need to be recompiled.
686 Applications such as wpa_supplicant(8) may require a full world
687 build without using NO_CLEAN in order to get synchronized with the
691 The iwn(4) driver has been updated to support the 5000 and 5150 series.
692 There's one kernel module for each firmware. Adding "device iwnfw"
693 to the kernel configuration file means including all three firmware
694 images inside the kernel. If you want to include just the one for
695 your wireless card, use the devices iwn4965fw, iwn5000fw or
699 The rc.d/network_ipv6, IPv6 configuration script has been integrated
700 into rc.d/netif. The changes are the following:
702 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
703 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
704 Note that both variables need the "inet6" keyword at the head.
706 Do not set $ipv6_network_interfaces manually if you do not
707 understand what you are doing. It is not needed in most cases.
709 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
712 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
713 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
715 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
716 all configured interfaces have "inet6 accept_rtadv" in the
717 $ifconfig_IF_ipv6. These are for backward compatibility.
719 3. A new variable $ipv6_prefer has been added. If NO, IPv6
720 functionality of interfaces with no corresponding
721 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
722 and the default address selection policy of ip6addrctl(8)
723 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
724 Note that if you want to configure IPv6 functionality on the
725 disabled interfaces after boot, first you need to clear the flag by
726 using ifconfig(8) like:
728 ifconfig em0 inet6 -ifdisabled
730 If YES, the default address selection policy is set as
733 The default value of $ipv6_prefer is NO.
735 4. If your system need to receive Router Advertisement messages,
736 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
737 scripts automatically invoke rtsol(8) when the interface becomes
738 UP. The Router Advertisement messages are used for SLAAC
739 (State-Less Address AutoConfiguration).
742 802.11s D3.03 support was committed. This is incompatible with the
743 previous code, which was based on D3.0.
746 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
747 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
748 control whether accepting Router Advertisement messages or not.
749 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
750 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
751 The ifconfig(8) utility now supports these flags.
754 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
755 mount(8) and -a option for df(1) to see them.
758 The old tunable hw.bus.devctl_disable has been superseded by
759 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
760 replaced by hw.bus.devctl_queue=0. The default for this new tunable
764 Remove the option STOP_NMI. The default action is now to use NMI only
765 for KDB via the newly introduced function stop_cpus_hard() and
766 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
769 The stable/8 branch created in subversion. This corresponds to the
770 RELENG_8 branch in CVS.
773 Bump the shared library version numbers for all libraries that do not
774 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
775 __FreeBSD_version to 800105.
778 Due to changes in the implementation of virtual network stack support,
779 all network-related kernel modules must be recompiled. As this change
780 breaks the ABI, bump __FreeBSD_version to 800104.
783 The TOE interface to the TCP syncache has been modified to remove
784 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
785 The cxgb driver is the only TOE consumer affected by this change, and
786 needs to be recompiled along with the kernel. As this change breaks
787 the ABI, bump __FreeBSD_version to 800103.
790 Padding has been added to struct tcpcb, sackhint and tcpstat in
791 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
792 maintaining the ABI. However, this change breaks the ABI, so bump
793 __FreeBSD_version to 800102. User space tools that rely on the size of
794 any of these structs (e.g. sockstat) need to be recompiled.
797 The NFS_LEGACYRPC option has been removed along with the old kernel
798 RPC implementation that this option selected. Kernel configurations
799 may need to be adjusted.
802 The network interface device nodes at /dev/net/<interface> have been
803 removed. All ioctl operations can be performed the normal way using
804 routing sockets. The kqueue functionality can generally be replaced
805 with routing sockets.
808 The documentation from the FreeBSD Documentation Project (Handbook,
809 FAQ, etc.) is now installed via packages by sysinstall(8) and under
810 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
813 The ABI of various structures related to the SYSV IPC API have been
814 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
815 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
819 Layout of struct vnet has changed as routing related variables were
820 moved to their own Vimage module. Modules need to be recompiled. Bump
821 __FreeBSD_version to 800099.
824 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
825 respectively. As long as no more than 16 groups per process are used,
826 no changes should be visible. When more than 16 groups are used, old
827 binaries may fail if they call getgroups() or getgrouplist() with
828 statically sized storage. Recompiling will work around this, but
829 applications should be modified to use dynamically allocated storage
830 for group arrays as POSIX.1-2008 does not cap an implementation's
831 number of supported groups at NGROUPS_MAX+1 as previous versions did.
833 NFS and portalfs mounts may also be affected as the list of groups is
834 truncated to 16. Users of NFS who use more than 16 groups, should
835 take care that negative group permissions are not used on the exported
836 file systems as they will not be reliable unless a GSSAPI based
837 authentication method is used.
840 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
841 option compiles in the support for adaptive spinning for lockmgrs
842 which want to enable it. The lockinit() function now accepts the flag
843 LK_ADAPTIVE in order to make the lock object subject to adaptive
844 spinning when both held in write and read mode.
847 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
848 changed. User applications that use this ioctl need to be rebuilt.
851 The layout of struct thread has changed. Kernel and modules need to
855 The layout of structs ifnet, domain, protosw and vnet_net has changed.
856 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
859 window(1) has been removed from the base system. It can now be
860 installed from ports. The port is called misc/window.
863 The way we are storing and accessing `routing table' entries has
864 changed. Programs reading the FIB, like netstat, need to be
868 A new netisr implementation has been added for FreeBSD 8. Network
869 file system modules, such as igmp, ipdivert, and others, should be
871 Bump __FreeBSD_version to 800096.
874 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
878 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
879 Bump __FreeBSD_version to 800094.
882 Add mnt_xflag field to 'struct mount'. File system modules need to be
884 Bump __FreeBSD_version to 800093.
887 The compiling option ADAPTIVE_SX has been retired while it has been
888 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
889 The KPI for sx_init_flags() changes as accepting flags:
890 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
891 been introduced in order to handle the reversed logic.
892 Bump __FreeBSD_version to 800092.
895 Add support for hierarchical jails. Remove global securelevel.
896 Bump __FreeBSD_version to 800091.
899 The layout of struct vnet_net has changed, therefore modules
901 Bump __FreeBSD_version to 800090.
904 The newly imported zic(8) produces a new format in the output. Please
905 run tzsetup(8) to install the newly created data to /etc/localtime.
908 The sysctl tree for the usb stack has renamed from hw.usb2.* to
909 hw.usb.* and is now consistent again with previous releases.
912 802.11 monitor mode support was revised and driver api's were changed.
913 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
914 of DLT_IEEE802_11. No user-visible data structures were changed but
915 applications that use DLT_IEEE802_11 may require changes.
916 Bump __FreeBSD_version to 800088.
919 The layout of the following structs has changed: sysctl_oid,
920 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
921 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
922 panics may be experienced. World rebuild is required for
923 correctly checking networking state from userland.
924 Bump __FreeBSD_version to 800085.
927 MLDv2 and Source-Specific Multicast (SSM) have been merged
928 to the IPv6 stack. VIMAGE hooks are in but not yet used.
929 The implementation of SSM within FreeBSD's IPv6 stack closely
930 follows the IPv4 implementation.
932 For kernel developers:
934 * The most important changes are that the ip6_output() and
935 ip6_input() paths no longer take the IN6_MULTI_LOCK,
936 and this lock has been downgraded to a non-recursive mutex.
938 * As with the changes to the IPv4 stack to support SSM, filtering
939 of inbound multicast traffic must now be performed by transport
940 protocols within the IPv6 stack. This does not apply to TCP and
941 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
943 * The KPIs used by IPv6 multicast are similar to those used by
944 the IPv4 stack, with the following differences:
945 * im6o_mc_filter() is analogous to imo_multicast_filter().
946 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
947 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
948 * IN6_LOOKUP_MULTI() has been deprecated and removed.
949 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
950 for MLDv1 have an additional 'timer' argument which is used to
951 jitter the initial membership report for the solicited-node
952 multicast membership on-link.
953 * This is not strictly needed for MLDv2, which already jitters
954 its report transmissions. However, the 'timer' argument is
955 preserved in case MLDv1 is active on the interface.
957 * The KAME linked-list based IPv6 membership implementation has
958 been refactored to use a vector similar to that used by the IPv4
960 Code which maintains a list of its own multicast memberships
961 internally, e.g. carp, has been updated to reflect the new
964 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
965 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
966 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
967 implementation constraint which needs to be addressed in HEAD.
969 For application developers:
971 * The changes are broadly similar to those made for the IPv4
974 * The use of IPv4 and IPv6 multicast socket options on the same
975 socket, using mapped addresses, HAS NOT been tested or supported.
977 * There are a number of issues with the implementation of various
978 IPv6 multicast APIs which need to be resolved in the API surface
979 before the implementation is fully compatible with KAME userland
980 use, and these are mostly to do with interface index treatment.
982 * The literature available discusses the use of either the delta / ASM
983 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
984 using setsourcefilter(3)/getsourcefilter(3). For more information
985 please refer to RFC 3768, 'Socket Interface Extensions for
986 Multicast Source Filters'.
988 * Applications which use the published RFC 3678 APIs should be fine.
990 For systems administrators:
992 * The mtest(8) utility has been refactored to support IPv6, in
993 addition to IPv4. Interface addresses are no longer accepted
994 as arguments, their names must be used instead. The utility
995 will map the interface name to its first IPv4 address as
996 returned by getifaddrs(3).
998 * The ifmcstat(8) utility has also been updated to print the MLDv2
999 endpoint state and source filter lists via sysctl(3).
1001 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1002 loopback of IPv6 multicast datagrams by default; it defaults to 1
1003 to preserve the existing behaviour. Disabling multicast loopback is
1004 recommended for optimal system performance.
1006 * The IPv6 MROUTING code has been changed to examine this sysctl
1007 instead of attempting to perform a group lookup before looping
1008 back forwarded datagrams.
1010 Bump __FreeBSD_version to 800084.
1013 Implement low-level Bluetooth HCI API.
1014 Bump __FreeBSD_version to 800083.
1017 The layout of struct malloc_type, used by modules to register new
1018 memory allocation types, has changed. Most modules will need to
1019 be rebuilt or panics may be experienced.
1020 Bump __FreeBSD_version to 800081.
1023 Anticipate overflowing inp_flags - add inp_flags2.
1024 This changes most offsets in inpcb, so checking v4 connection
1025 state will require a world rebuild.
1026 Bump __FreeBSD_version to 800080.
1029 Add an llentry to struct route and struct route_in6. Modules
1030 embedding a struct route will need to be recompiled.
1031 Bump __FreeBSD_version to 800079.
1034 The size of rt_metrics_lite and by extension rtentry has changed.
1035 Networking administration apps will need to be recompiled.
1036 The route command now supports show as an alias for get, weighting
1037 of routes, sticky and nostick flags to alter the behavior of stateful
1039 Bump __FreeBSD_version to 800078.
1042 Do not use Giant for kbdmux(4) locking. This is wrong and
1043 apparently causing more problems than it solves. This will
1044 re-open the issue where interrupt handlers may race with
1045 kbdmux(4) in polling mode. Typical symptoms include (but
1046 not limited to) duplicated and/or missing characters when
1047 low level console functions (such as gets) are used while
1048 interrupts are enabled (for example geli password prompt,
1049 mountroot prompt etc.). Disabling kbdmux(4) may help.
1052 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1053 kernel modules referencing any of the above need to be recompiled.
1054 Bump __FreeBSD_version to 800075.
1057 GEOM_PART has become the default partition slicer for storage devices,
1058 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1059 introduces some changes:
1061 MSDOS/EBR: the devices created from MSDOS extended partition entries
1062 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1063 to devices with offset-based names. fstabs may need to be modified.
1065 BSD: the "geometry does not match label" warning is harmless in most
1066 cases but it points to problems in file system misalignment with
1067 disk geometry. The "c" partition is now implicit, covers the whole
1068 top-level drive and cannot be (mis)used by users.
1070 General: Kernel dumps are now not allowed to be written to devices
1071 whose partition types indicate they are meant to be used for file
1072 systems (or, in case of MSDOS partitions, as something else than
1075 Most of these changes date approximately from 200812.
1078 The uscanner(4) driver has been removed from the kernel. This follows
1079 Linux removing theirs in 2.6 and making libusb the default interface
1080 (supported by sane).
1083 The multicast forwarding code has been cleaned up. netstat(1)
1084 only relies on KVM now for printing bandwidth upcall meters.
1085 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1086 ip6_mroute_mod respectively. The config(5) options for statically
1087 compiling this code remain the same, i.e. 'options MROUTING'.
1090 Support for the IFF_NEEDSGIANT network interface flag has been
1091 removed, which means that non-MPSAFE network device drivers are no
1092 longer supported. In particular, if_ar, if_sr, and network device
1093 drivers from the old (legacy) USB stack can no longer be built or
1097 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1098 a bunch of new language catalog files have also been added.
1099 This means that some common libc messages are now localized and
1100 they depend on the LC_MESSAGES environmental variable.
1103 The k8temp(4) driver has been renamed to amdtemp(4) since
1104 support for Family 10 and Family 11 CPU families was added.
1107 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1108 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1110 For kernel developers, the most important changes are that the
1111 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1112 and this lock has been downgraded to a non-recursive mutex.
1114 Transport protocols (UDP, Raw IP) are now responsible for filtering
1115 inbound multicast traffic according to group membership and source
1116 filters. The imo_multicast_filter() KPI exists for this purpose.
1117 Transports which do not use multicast (SCTP, TCP) already reject
1118 multicast by default. Forwarding and receive performance may improve
1119 as a mutex acquisition is no longer needed in the ip_input()
1120 low-level input path. in_addmulti() and in_delmulti() are shimmed
1121 to new KPIs which exist to support SSM in-kernel.
1123 For application developers, it is recommended that loopback of
1124 multicast datagrams be disabled for best performance, as this
1125 will still cause the lock to be taken for each looped-back
1126 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1127 be tuned to 0 to disable loopback by default; it defaults to 1
1128 to preserve the existing behaviour.
1130 For systems administrators, to obtain best performance with
1131 multicast reception and multiple groups, it is always recommended
1132 that a card with a suitably precise hash filter is used. Hash
1133 collisions will still result in the lock being taken within the
1134 transport protocol input path to check group membership.
1136 If deploying FreeBSD in an environment with IGMP snooping switches,
1137 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1138 enabled; this forces 224.0.0.0/24 group membership to be announced
1141 The size of 'struct igmpstat' has changed; netstat needs to be
1142 recompiled to reflect this.
1143 Bump __FreeBSD_version to 800070.
1146 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1147 updated to use it. This requires a buildworld/installworld in order to
1148 update the library and dependencies (usbconfig, etc). Its advisable to
1149 rebuild all ports which uses libusb. More specific directions are given
1150 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1151 libusb are no longer required and can be removed.
1154 A workaround is committed to allow the creation of System V shared
1155 memory segment of size > 2 GB on the 64-bit architectures.
1156 Due to a limitation of the existing ABI, the shm_segsz member
1157 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1158 wrong for large segments. Note that limits must be explicitly
1159 raised to allow such segments to be created.
1162 The layout of struct ifnet has changed, requiring a rebuild of all
1163 network device driver modules.
1166 The /dev handling for the new USB stack has changed, a
1167 buildworld/installworld is required for libusb20.
1170 The new USB2 stack has now been permanently moved in and all kernel and
1171 module names reverted to their previous values (eg, usb, ehci, ohci,
1172 ums, ...). The old usb stack can be compiled in by prefixing the name
1173 with the letter 'o', the old usb modules have been removed.
1174 Updating entry 20090216 for xorg and 20090215 for libmap may still
1178 The rc.conf(5) option if_up_delay has been renamed to
1179 defaultroute_delay to better reflect its purpose. If you have
1180 customized this setting in /etc/rc.conf you need to update it to
1184 xorg 7.4 wants to configure its input devices via hald which does not
1185 yet work with USB2. If the keyboard/mouse does not work in xorg then
1187 Option "AllowEmptyInput" "off"
1188 to your ServerLayout section. This will cause X to use the configured
1189 kbd and mouse sections from your xorg.conf.
1192 The GENERIC kernels for all architectures now default to the new USB2
1193 stack. No kernel config options or code have been removed so if a
1194 problem arises please report it and optionally revert to the old USB
1195 stack. If you are loading USB kernel modules or have a custom kernel
1196 that includes GENERIC then ensure that usb names are also changed over,
1197 eg uftdi -> usb2_serial_ftdi.
1199 Older programs linked against the ports libusb 0.1 need to be
1200 redirected to the new stack's libusb20. /etc/libmap.conf can
1202 # Map old usb library to new one for usb2 stack
1203 libusb-0.1.so.8 libusb20.so.1
1206 All USB ethernet devices now attach as interfaces under the name ueN
1207 (eg. ue0). This is to provide a predictable name as vendors often
1208 change usb chipsets in a product without notice.
1211 The ichsmb(4) driver has been changed to require SMBus slave
1212 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1213 All of the other SMBus controller drivers require left-justified
1214 slave addresses, so this change makes all the drivers provide the
1218 INET6 statistics (struct ip6stat) was updated.
1219 netstat(1) needs to be recompiled.
1222 NTFS has been removed from GENERIC kernel on amd64 to match
1223 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1224 will load ntfs.ko module automatically when NTFS support is
1225 actually needed, unless ntfs.ko is not installed or security
1226 level prohibits loading kernel modules. If either is the case,
1227 "options NTFS" has to be added into kernel config.
1230 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1231 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1232 800061. User space tools that rely on the size of struct tcpcb in
1233 tcp_var.h (e.g. sockstat) need to be recompiled.
1236 ng_tty(4) module updated to match the new TTY subsystem.
1237 Due to API change, user-level applications must be updated.
1238 New API support added to mpd5 CVS and expected to be present
1239 in next mpd5.3 release.
1242 With __FreeBSD_version 800060 the makefs tool is part of
1243 the base system (it was a port).
1246 The afdata and ifnet locks have been changed from mutexes to
1247 rwlocks, network modules will need to be re-compiled.
1250 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1251 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1252 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1253 architecture and 40 bytes on 64-bit architecture. The userland
1254 applications "arp" and "ndp" have been updated accordingly.
1255 The output from "netstat -r" shows only routing entries and
1256 none of the L2 information.
1259 __FreeBSD_version 800057 marks the switchover from the
1260 binary ath hal to source code. Users must add the line:
1262 options AH_SUPPORT_AR5416
1264 to their kernel config files when specifying:
1268 The ath_hal module no longer exists; the code is now compiled
1269 together with the driver in the ath module. It is now
1270 possible to tailor chip support (i.e. reduce the set of chips
1271 and thereby the code size); consult ath_hal(4) for details.
1274 __FreeBSD_version 800054 adds memory barriers to
1275 <machine/atomic.h>, new interfaces to ifnet to facilitate
1276 multiple hardware transmit queues for cards that support
1277 them, and a lock-less ring-buffer implementation to
1278 enable drivers to more efficiently manage queueing of
1282 A new version of ZFS (version 13) has been merged to -HEAD.
1283 This version has zpool attribute "listsnapshots" off by
1284 default, which means "zfs list" does not show snapshots,
1285 and is the same as Solaris behavior.
1288 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1291 The uhci, ohci, ehci and slhci USB Host controller drivers have
1292 been put into separate modules. If you load the usb module
1293 separately through loader.conf you will need to load the
1294 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1295 controller add the following to loader.conf:
1301 The ABI used by the PMC toolset has changed. Please keep
1302 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1306 atapci kernel module now includes only generic PCI ATA
1307 driver. AHCI driver moved to ataahci kernel module.
1308 All vendor-specific code moved into separate kernel modules:
1309 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1310 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1311 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1312 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1315 The TTY subsystem of the kernel has been replaced by a new
1316 implementation, which provides better scalability and an
1317 improved driver model. Most common drivers have been migrated to
1318 the new TTY subsystem, while others have not. The following
1319 drivers have not yet been ported to the new TTY layer:
1322 cy, digi, rc, rp, sio
1328 ng_h4, ng_tty, ppp, sl, snp
1330 Adding these drivers to your kernel configuration file shall
1331 cause compilation to fail.
1334 ntpd has been upgraded to 4.2.4p5.
1337 OpenSSH has been upgraded to 5.1p1.
1339 For many years, FreeBSD's version of OpenSSH preferred DSA
1340 over RSA for host and user authentication keys. With this
1341 upgrade, we've switched to the vendor's default of RSA over
1342 DSA. This may cause upgraded clients to warn about unknown
1343 host keys even for previously known hosts. Users should
1344 follow the usual procedure for verifying host keys before
1345 accepting the RSA key.
1347 This can be circumvented by setting the "HostKeyAlgorithms"
1348 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1351 Please note that the sequence of keys offered for
1352 authentication has been changed as well. You may want to
1353 specify IdentityFile in a different order to revert this
1357 The sio(4) driver has been removed from the i386 and amd64
1358 kernel configuration files. This means uart(4) is now the
1359 default serial port driver on those platforms as well.
1361 To prevent collisions with the sio(4) driver, the uart(4) driver
1362 uses different names for its device nodes. This means the
1363 onboard serial port will now most likely be called "ttyu0"
1364 instead of "ttyd0". You may need to reconfigure applications to
1365 use the new device names.
1367 When using the serial port as a boot console, be sure to update
1368 /boot/device.hints and /etc/ttys before booting the new kernel.
1369 If you forget to do so, you can still manually specify the hints
1370 at the loader prompt:
1372 set hint.uart.0.at="isa"
1373 set hint.uart.0.port="0x3F8"
1374 set hint.uart.0.flags="0x10"
1375 set hint.uart.0.irq="4"
1379 The gpt(8) utility has been removed. Use gpart(8) to partition
1383 The version that Linuxulator emulates was changed from 2.4.2
1384 to 2.6.16. If you experience any problems with Linux binaries
1385 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1386 if it fixes the problem contact emulation mailing list.
1389 ISDN4BSD (I4B) was removed from the src tree. You may need to
1390 update a your kernel configuration and remove relevant entries.
1393 I have checked in code to support multiple routing tables.
1394 See the man pages setfib(1) and setfib(2).
1395 This is a hopefully backwards compatible version,
1396 but to make use of it you need to compile your kernel
1397 with options ROUTETABLES=2 (or more up to 16).
1400 The 802.11 wireless support was redone to enable multi-bss
1401 operation on devices that are capable. The underlying device
1402 is no longer used directly but instead wlanX devices are
1403 cloned with ifconfig. This requires changes to rc.conf files.
1404 For example, change:
1405 ifconfig_ath0="WPA DHCP"
1408 ifconfig_wlan0="WPA DHCP"
1409 see rc.conf(5) for more details. In addition, mergemaster of
1410 /etc/rc.d is highly recommended. Simultaneous update of userland
1411 and kernel wouldn't hurt either.
1413 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1414 modules were merged into the base wlan module. All references
1415 to these modules (e.g. in kernel config files) must be removed.
1418 psm(4) has gained write(2) support in native operation level.
1419 Arbitrary commands can be written to /dev/psm%d and status can
1420 be read back from it. Therefore, an application is responsible
1421 for status validation and error recovery. It is a no-op in
1422 other operation levels.
1425 Support for KSE threading has been removed from the kernel. To
1426 run legacy applications linked against KSE libmap.conf may
1427 be used. The following libmap.conf may be used to ensure
1428 compatibility with any prior release:
1430 libpthread.so.1 libthr.so.1
1431 libpthread.so.2 libthr.so.2
1432 libkse.so.3 libthr.so.3
1435 The layout of struct vmspace has changed. This affects libkvm
1436 and any executables that link against libkvm and use the
1437 kvm_getprocs() function. In particular, but not exclusively,
1438 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1439 The effects are minimal, but it's advisable to upgrade world
1443 The latest em driver no longer has support in it for the
1444 82575 adapter, this is now moved to the igb driver. The
1445 split was done to make new features that are incompatible
1446 with older hardware easier to do.
1449 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1450 likewise the kernel option is now GEOM_LINUX_LVM.
1453 The default NFS mount mode has changed from UDP to TCP for
1454 increased reliability. If you rely on (insecurely) NFS
1455 mounting across a firewall you may need to update your
1459 Belatedly note the addition of m_collapse for compacting
1463 The fts(3) structures have been changed to use adequate
1464 integer types for their members and so to be able to cope
1465 with huge file trees. The old fts(3) ABI is preserved
1466 through symbol versioning in libc, so third-party binaries
1467 using fts(3) should still work, although they will not take
1468 advantage of the extended types. At the same time, some
1469 third-party software might fail to build after this change
1470 due to unportable assumptions made in its source code about
1471 fts(3) structure members. Such software should be fixed
1472 by its vendor or, in the worst case, in the ports tree.
1473 FreeBSD_version 800015 marks this change for the unlikely
1474 case that a portable fix is impossible.
1477 To upgrade to -current after this date, you must be running
1478 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1479 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1482 The ADAPTIVE_GIANT kernel option has been retired because its
1483 functionality is the default now.
1486 The AT keyboard emulation of sunkbd(4) has been turned on
1487 by default. In order to make the special symbols of the Sun
1488 keyboards driven by sunkbd(4) work under X these now have
1489 to be configured the same way as Sun USB keyboards driven
1490 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1492 Option "XkbLayout" "us"
1493 Option "XkbRules" "xorg"
1494 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1497 It has been decided that it is desirable to provide ABI
1498 backwards compatibility to the FreeBSD 4/5/6 versions of the
1499 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1500 broken with the introduction of PCI domain support (see the
1501 20070930 entry). Unfortunately, this required the ABI of
1502 PCIOCGETCONF to be broken again in order to be able to
1503 provide backwards compatibility to the old version of that
1504 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1505 again. As for prominent ports this affects neither pciutils
1506 nor xorg-server this time, the hal port needs to be rebuilt
1510 The misnamed kthread_create() and friends have been renamed
1511 to kproc_create() etc. Many of the callers already
1512 used kproc_start()..
1513 I will return kthread_create() and friends in a while
1514 with implementations that actually create threads, not procs.
1515 Renaming corresponds with version 800002.
1524 Avoid using make -j when upgrading. While generally safe, there are
1525 sometimes problems using -j to upgrade. If your upgrade fails with
1526 -j, please try again without -j. From time to time in the past there
1527 have been problems using -j with buildworld and/or installworld. This
1528 is especially true when upgrading between "distant" versions (eg one
1529 that cross a major release boundary or several minor releases, or when
1530 several months have passed on the -current branch).
1532 Sometimes, obscure build problems are the result of environment
1533 poisoning. This can happen because the make utility reads its
1534 environment when searching for values for global variables. To run
1535 your build attempts in an "environmental clean room", prefix all make
1536 commands with 'env -i '. See the env(1) manual page for more details.
1538 When upgrading from one major version to another it is generally best
1539 to upgrade to the latest code in the currently installed branch first,
1540 then do an upgrade to the new branch. This is the best-tested upgrade
1541 path, and has the highest probability of being successful. Please try
1542 this approach before reporting problems with a major version upgrade.
1546 When upgrading the boot ZFS pool to a new version, always follow
1549 1.) recompile and reinstall the ZFS boot loader and boot block
1550 (this is part of "make buildworld" and "make installworld")
1552 2.) update the ZFS boot block on your boot drive
1554 The following example updates the ZFS boot block on the first
1555 partition (freebsd-boot) of a GPT partitioned drive ad0:
1556 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1558 Non-boot pools do not need these updates.
1562 If you are updating from a prior version of FreeBSD (even one just
1563 a few days old), you should follow this procedure. It is the most
1564 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1566 make kernel-toolchain
1567 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1568 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1570 To test a kernel once
1571 ---------------------
1572 If you just want to boot a kernel once (because you are not sure
1573 if it works, or if you want to boot a known bad kernel to provide
1574 debugging information) run
1575 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1576 nextboot -k testkernel
1578 To just build a kernel when you know that it won't mess you up
1579 --------------------------------------------------------------
1580 This assumes you are already running a CURRENT system. Replace
1581 ${arch} with the architecture of your machine (e.g. "i386",
1582 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1584 cd src/sys/${arch}/conf
1585 config KERNEL_NAME_HERE
1586 cd ../compile/KERNEL_NAME_HERE
1591 If this fails, go to the "To build a kernel" section.
1593 To rebuild everything and install it on the current system.
1594 -----------------------------------------------------------
1595 # Note: sometimes if you are running current you gotta do more than
1596 # is listed here if you are upgrading from a really old current.
1598 <make sure you have good level 0 dumps>
1600 make kernel KERNCONF=YOUR_KERNEL_HERE
1602 <reboot in single user> [3]
1610 To cross-install current onto a separate partition
1611 --------------------------------------------------
1612 # In this approach we use a separate partition to hold
1613 # current's root, 'usr', and 'var' directories. A partition
1614 # holding "/", "/usr" and "/var" should be about 2GB in
1617 <make sure you have good level 0 dumps>
1620 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1621 <maybe newfs current's root partition>
1622 <mount current's root partition on directory ${CURRENT_ROOT}>
1623 make installworld DESTDIR=${CURRENT_ROOT}
1624 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1625 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1626 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1627 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1628 <reboot into current>
1629 <do a "native" rebuild/install as described in the previous section>
1630 <maybe install compatibility libraries from ports/misc/compat*>
1634 To upgrade in-place from stable to current
1635 ----------------------------------------------
1636 <make sure you have good level 0 dumps>
1638 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1640 <reboot in single user> [3]
1647 Make sure that you've read the UPDATING file to understand the
1648 tweaks to various things you need. At this point in the life
1649 cycle of current, things change often and you are on your own
1650 to cope. The defaults can also change, so please read ALL of
1651 the UPDATING entries.
1653 Also, if you are tracking -current, you must be subscribed to
1654 freebsd-current@freebsd.org. Make sure that before you update
1655 your sources that you have read and understood all the recent
1656 messages there. If in doubt, please track -stable which has
1657 much fewer pitfalls.
1659 [1] If you have third party modules, such as vmware, you
1660 should disable them at this point so they don't crash your
1663 [3] From the bootblocks, boot -s, and then do
1668 adjkerntz -i # if CMOS is wall time
1669 Also, when doing a major release upgrade, it is required that
1670 you boot into single user mode to do the installworld.
1672 [4] Note: This step is non-optional. Failure to do this step
1673 can result in a significant reduction in the functionality of the
1674 system. Attempting to do it by hand is not recommended and those
1675 that pursue this avenue should read this file carefully, as well
1676 as the archives of freebsd-current and freebsd-hackers mailing lists
1677 for potential gotchas. The -U option is also useful to consider.
1678 See mergemaster(8) for more information.
1680 [5] Usually this step is a noop. However, from time to time
1681 you may need to do this if you get unknown user in the following
1682 step. It never hurts to do it all the time. You may need to
1683 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1684 install) after the buildworld before this step if you last updated
1685 from [78]-stable or 9-stable before 20130430.
1687 [6] This only deletes old files and directories. Old libraries
1688 can be deleted by "make delete-old-libs", but you have to make
1689 sure that no program is using those libraries anymore.
1691 [8] In order to have a kernel that can run the 4.x binaries needed to
1692 do an installworld, you must include the COMPAT_FREEBSD4 option in
1693 your kernel. Failure to do so may leave you with a system that is
1694 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1695 required to run the 5.x binaries on more recent kernels. And so on
1696 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1698 Make sure that you merge any new devices from GENERIC since the
1699 last time you updated your kernel config file.
1701 [9] When checking out sources, you must include the -P flag to have
1702 cvs prune empty directories.
1704 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1705 "?=" instead of the "=" assignment operator, so that buildworld can
1706 override the CPUTYPE if it needs to.
1708 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1709 not on the command line, or in /etc/make.conf. buildworld will
1710 warn if it is improperly defined.
1713 This file contains a list, in reverse chronological order, of major
1714 breakages in tracking -current. It is not guaranteed to be a complete
1715 list of such breakages, and only contains entries since October 10, 2007.
1716 If you need to see UPDATING entries from before that date, you will need
1717 to fetch an UPDATING file from an older FreeBSD release.
1719 Copyright information:
1721 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1723 Redistribution, publication, translation and use, with or without
1724 modification, in full or in part, in any form or format of this
1725 document are permitted without further permission from the author.
1727 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1728 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1729 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1730 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1731 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1732 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1733 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1734 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1735 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1736 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1737 POSSIBILITY OF SUCH DAMAGE.
1739 Contact Warner Losh if you have any questions about your use of