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 20141022: p14 FreeBSD-EN-14:10.tzdata
16 Time zone data file update. [EN-14:10]
18 20141021: p13 FreeBSD-SA-14:20.rtsold
19 FreeBSD-SA-14:21.routed
20 FreeBSD-SA-14:22.namei
21 FreeBSD-SA-14:23.openssl
23 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
25 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
27 Fix memory leak in sandboxed namei lookup. [SA-14:22]
29 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
31 20140916: p12 FreeBSD-SA-14:19.tcp
32 Fix Denial of Service in TCP packet processing. [SA-14:19]
34 20140909: p11 FreeBSD-SA-14:18.openssl
35 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
37 20140708: p10 FreeBSD-SA-14:17.kmem
38 Fix kernel memory disclosure in control messages and SCTP
39 notifications. [SA-14:17]
41 20140624: p9 FreeBSD-SA-14:16.file
42 FreeBSD-EN-14:08.heimdal
44 Fix multiple vulnerabilities in file(1) and libmagic(3).
47 Fix gss_pseudo_random interoperability issue. [EN-14:08]
49 20140605: p8 FreeBSD-SA-14:14.openssl
50 Fix OpenSSL multiple vulnerabilities. [SA-14:14]
52 20140603: p7 FreeBSD-SA-14:11.sendmail
53 FreeBSD-SA-14:12.ktrace
57 Fix sendmail improper close-on-exec flag handling. [SA-14:11]
59 Fix ktrace memory disclosure. [SA-14:12]
61 Fix incorrect error handling in PAM policy parser. [SA-14:13]
63 Fix triple-fault when executing from a threaded process.
66 20140513: p6 FreeBSD-EN-14:03.pkg
67 FreeBSD-EN-14:04.kldxref
70 Add pkg bootstrapping, configuration and public keys. [EN-14:03]
72 Improve build repeatability for kldxref(8). [EN-14:04]
74 Fix data corruption with ciss(4). [EN-14:05]
76 20140430: p5 FreeBSD-SA-14:08.tcp
78 Fix TCP reassembly vulnerability. [SA-14:08]
80 20140408: p4 FreeBSD-SA-14:05.nfsserver
81 FreeBSD-SA-14:06.openssl
82 Fix deadlock in the NFS server. [SA-14:05]
84 Fix for ECDSA Cache Side-channel Attack in OpenSSL. [SA-14:06]
86 20140114: p3 FreeBSD-SA-14:01.bsnmpd
89 FreeBSD-EN-14:01.random
91 Fix bsnmpd remote denial of service vulnerability. [SA-14:01]
93 Fix ntpd distributed reflection Denial of Service
94 vulnerability. [SA-14:02]
96 Fix BIND remote denial of service vulnerability. [SA-14:04]
98 Disable hardware RNGs by default. [EN-14:01]
100 Fix incorrect coalescing of stack entry with mmap. [EN-14:02]
102 20131128: p2 FreeBSD-EN-13:05.freebsd-update
103 Fix error in patch for FreeBSD-EN-13:04.freebsd-update.
105 20131026: p1 FreeBSD-EN-13:04.freebsd-update
106 Fix multiple freebsd-update bugs that break upgrading to
110 hastctl(8)'s `status' command output changed to terse one-liner format.
111 Scripts using this should switch to `list' command or be rewritten.
114 Fix a bug that allowed a tracing process (e.g. gdb) to write
115 to a memory-mapped file in the traced process's address space
116 even if neither the traced process nor the tracing process had
117 write access to that file.
120 Added ZFS TRIM support which is enabled by default. To disable
121 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
123 Creating new ZFS pools and adding new devices to existing pools
124 first performs a full device level TRIM which can take a significant
125 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
126 to disable this behaviour.
128 ZFS TRIM requires the underlying device support BIO_DELETE which
129 is currently provided by methods such as ATA TRIM and SCSI UNMAP
130 via CAM, which are typically supported by SSD's.
132 Stats for ZFS TRIM can be monitored by looking at the sysctl's
133 under kstat.zfs.misc.zio_trim.
136 `list' command has been added to hastctl(8). For now, it is full
137 equivalent of `status' command.
138 WARNING: in the near future the output of hastctl's status command
139 will change to more terse format. If you use `hastctl status'
140 for parsing in your scripts, switch to `hastctl list'.
143 The mergemaster command now uses the default MAKEOBJDIRPREFIX
144 rather than creating it's own in the temporary directory in
145 order allow access to bootstrapped versions of tools such as
146 install and mtree. When upgrading from version of FreeBSD where
147 the install command does not support -l, you will need to
148 install a new mergemaster command if mergemaster -p is required.
149 This can be accomplished with the command (cd src/usr.sbin/mergemaster
152 Due to the use of the new -l option to install(1) during build
153 and install, you must take care not to directly set the INSTALL
154 make variable in your /etc/make.conf, /etc/src.conf, or on the
155 command line. If you wish to use the -C flag for all installs
156 you may be able to add INSTALL+=-C to /etc/make.conf or
160 Fix a bug that allows NFS clients to issue READDIR on files.
163 The install(1) option -M has changed meaning and now takes an
164 argument that is a file or path to append logs to. In the
165 unlikely event that -M was the last option on the command line
166 and the command line contained at least two files and a target
167 directory the first file will have logs appended to it. The -M
168 option served little practical purpose in the last decade so it's
169 used expected to be extremely rare.
172 A new compression method (lz4) has been merged to. Please refer to
173 zpool-features(7) for more information.
175 Please refer to the "ZFS notes" section of this file for information
176 on upgrading boot ZFS pools.
179 The VFS KBI was changed with the merge of several nullfs
180 optimizations and fixes. All filesystem modules must be
184 With the addition of auditdistd(8), a new auditdistd user is now
185 depended on during installworld. "mergemaster -p" can be used to add
186 the user prior to installworld, as documented in the handbook.
192 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
193 Starting with this version the old system of ZFS pool versioning
194 is superseded by "feature flags". This concept enables forward
195 compatibility against certain future changes in functionality of ZFS
196 pools. The first two read-only compatible "feature flags" for ZFS
197 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
198 For more information read the new zpool-features(7) manual page.
199 Please refer to the "ZFS notes" section of this file for information
200 on upgrading boot ZFS pools.
203 The commit introducing bsd.compiler.mk breaks the traditional
204 building of kernels before this point. Add -m ${SRC}/share/mk
205 (for the right value of SRC) to your command lines to work
206 around; update your useland to a point after this; or use the
207 buildkernel/installkernel top-level targets. See also 20120829.
210 The IPFIREWALL_FORWARD kernel option has been removed. Its
211 functionality now turned on by default.
214 The random(4) support for the VIA hardware random number
215 generator (`PADLOCK') is no longer enabled unconditionally.
216 Add the PADLOCK_RNG option in the custom kernel config if
217 needed. The GENERIC kernels on i386 and amd64 do include the
218 option, so the change only affects the custom kernel
222 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
223 the traditional method, you must update your system with an installworld
224 before the kernel will build. The documented make buildkernel/installkernel
225 interfaces (coupled with fresh make kernel-toolchain) continue to work.
228 The sparc64 ZFS loader has been changed to no longer try to auto-
229 detect ZFS providers based on diskN aliases but now requires these
230 to be explicitly listed in the OFW boot-device environment variable.
233 Now unix domain sockets behave "as expected" on nullfs(5). Previously
234 nullfs(5) did not pass through all behaviours to the underlying layer,
235 as a result if we bound to a socket on the lower layer we could connect
236 only to the lower path; if we bound to the upper layer we could connect
237 only to the upper path. The new behavior is one can connect to both the
238 lower and the upper paths regardless what layer path one binds to.
241 The acpi_wmi(4) status device /dev/wmistat has been renamed to
245 A new VOP_ADVISE() was added to support posix_fadvise(2). All
246 filesystem modules must be recompiled.
249 The interface of the VOP_VPTOCNP(9) changed, now the returned
250 vnode shall be referenced, previously it was required to be
251 only held. All in-tree filesystems are converted.
257 The broken amd(4) driver has been replaced with esp(4) in the amd64,
258 i386 and pc98 GENERIC kernel configuration files.
261 This commit modifies vfs_register() so that it uses a hash
262 calculation to set vfc_typenum, which is enabled by default.
263 The first time a system is booted after this change, the
264 vfc_typenum values will change for all file systems. The
265 main effect of this is a change to the NFS server file handles
266 for file systems that use vfc_typenum in their fsid, such as ZFS.
267 It will, however, prevent vfc_typenum from changing when file
268 systems are loaded in a different order for subsequent reboots.
269 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
270 until you are ready to remount all NFS clients after a reboot.
273 Bump the shared library version numbers for libraries that
274 do not use symbol versioning, have changed the ABI compared
275 to stable/8 and which shared library version was not bumped.
276 Done as part of 9.0-RELEASE cycle.
279 During the merge of Capsicum features, the fget(9) KPI was modified.
280 This may require the rebuilding of out-of-tree device drivers --
281 issues have been reported specifically with the nVidia device driver.
282 __FreeBSD_version is bumped to 900041.
284 Also, there is a period between 20110811 and 20110814 where the
285 special devices /dev/{stdin,stdout,stderr} did not work correctly.
286 Building world from a kernel during that window may not work.
289 The packet filter (pf) code has been updated to OpenBSD 4.5.
290 You need to update userland tools to be in sync with kernel.
291 This update breaks backward compatibility with earlier pfsync(4)
292 versions. Care must be taken when updating redundant firewall setups.
295 The following sysctls and tunables are retired on x86 platforms:
297 machdep.hlt_logical_cpus
298 The following sysctl is retired:
299 machdep.hyperthreading_allowed
300 The sysctls were supposed to provide a way to dynamically offline and
301 online selected CPUs on x86 platforms, but the implementation has not
302 been reliable especially with SCHED_ULE scheduler.
303 machdep.hyperthreading_allowed tunable is still available to ignore
304 hyperthreading CPUs at OS level.
305 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
306 where X is an APIC ID of a CPU. Be advised, though, that disabling
307 CPUs in non-uniform fashion will result in non-uniform topology and
308 may lead to sub-optimal system performance with SCHED_ULE, which is
312 cpumask_t type is retired and cpuset_t is used in order to describe
316 Changes to ifconfig(8) for dynamic address family detection mandate
317 that you are running a kernel of 20110525 or later. Make sure to
318 follow the update procedure to boot a new kernel before installing
322 Support for sun4v architecture is officially dropped
325 Several KPI breaking changes have been committed to the mii(4) layer,
326 the PHY drivers and consequently some Ethernet drivers using mii(4).
327 This means that miibus.ko and the modules of the affected Ethernet
328 drivers need to be recompiled.
330 Note to kernel developers: Given that the OUI bit reversion problem
331 was fixed as part of these changes all mii(4) commits related to OUIs,
332 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
333 handling, no longer can be merged verbatim to stable/8 and previous
337 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
338 into their kernel configurations along with 'device pci'.
341 The default NFS client is now the new NFS client, so fstype "newnfs"
342 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
343 Although mounts via fstype "nfs" will usually work without userland
344 changes, it is recommended that the mount(8) and mount_nfs(8)
345 commands be rebuilt from sources and that a link to mount_nfs called
346 mount_oldnfs be created. The new client is compiled into the
347 kernel with "options NFSCL" and this is needed for diskless root
348 file systems. The GENERIC kernel configs have been changed to use
349 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
350 To use the regular/old client, you can "mount -t oldnfs ...". For
351 a diskless root file system, you must also include a line like:
353 vfs.root.mountfrom="oldnfs:"
355 in the boot/loader.conf on the root fs on the NFS server to make
356 a diskless root fs use the old client.
359 The GENERIC kernels for all architectures now default to the new
360 CAM-based ATA stack. It means that all legacy ATA drivers were
361 removed and replaced by respective CAM drivers. If you are using
362 ATA device names in /etc/fstab or other places, make sure to update
363 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
364 where 'Y's are the sequential numbers starting from zero for each type
365 in order of detection, unless configured otherwise with tunables,
366 see cam(4)). There will be symbolic links created in /dev/ to map
367 old adX devices to the respective adaY. They should provide basic
368 compatibility for file systems mounting in most cases, but they do
369 not support old user-level APIs and do not have respective providers
370 in GEOM. Consider using updated management tools with new device names.
372 It is possible to load devices ahci, ata, siis and mvs as modules,
373 but option ATA_CAM should remain in kernel configuration to make ata
374 module work as CAM driver supporting legacy ATA controllers. Device ata
375 still can be used in modular fashion (atacore + ...). Modules atadisk
376 and atapi* are not used and won't affect operation in ATA_CAM mode.
377 Note that to use CAM-based ATA kernel should include CAM devices
378 scbus, pass, da (or explicitly ada), cd and optionally others. All of
379 them are parts of the cam module.
381 ataraid(4) functionality is now supported by the RAID GEOM class.
382 To use it you can load geom_raid kernel module and use graid(8) tool
383 for management. Instead of /dev/arX device names, use /dev/raid/rX.
385 No kernel config options or code have been removed, so if a problem
386 arises, please report it and optionally revert to the old ATA stack.
387 In order to do it you can remove from the kernel config:
392 , and instead add back:
393 device atadisk # ATA disk drives
394 device ataraid # ATA RAID drives
395 device atapicd # ATAPI CDROM drives
396 device atapifd # ATAPI floppy drives
397 device atapist # ATAPI tape drives
400 The default NFS server has been changed to the new server, which
401 was referred to as the experimental server. If you need to switch
402 back to the old NFS server, you must now put the "-o" option on
403 both the mountd and nfsd commands. This can be done using the
404 mountd_flags and nfs_server_flags rc.conf variables until an
405 update to the rc scripts is committed, which is coming soon.
408 The GNU Objective-C runtime library (libobjc), and other Objective-C
409 related components have been removed from the base system. If you
410 require an Objective-C library, please use one of the available ports.
413 ath(4) has been split into bus- and device- modules. if_ath contains
414 the HAL, the TX rate control and the network device code. if_ath_pci
415 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
416 contains the AHB glue. Users need to load both if_ath_pci and if_ath
417 in order to use ath on everything else.
419 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
420 need to load if_ath and if_ath_pci for ath(4) operation.
423 As part of the replacement of sysinstall, the process of building
424 release media has changed significantly. For details, please re-read
425 release(7), which has been updated to reflect the new build process.
428 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
429 is the last available version under GPLv2. It brings a number of new
430 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
431 4.1 and SSE 4.2), better support for powerpc64, a number of new
432 directives, and lots of other small improvements. See the ChangeLog
433 file in contrib/binutils for the full details.
436 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
437 compliant, and will now use half of hash for authentication.
438 This will break interoperability with all stacks (including all
439 actual FreeBSD versions) who implement
440 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
442 The only workaround with such peers is to use another HMAC
443 algorithm for IPsec ("phase 2") authentication.
446 Remove the uio_yield prototype and symbol. This function has
447 been misnamed since it was introduced and should not be
448 globally exposed with this name. The equivalent functionality
449 is now available using kern_yield(curthread->td_user_pri).
450 The function remains undocumented.
453 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
454 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
455 for scalar sysctls is defined but disabled. Code that needs
456 UQUAD to pass the type checking that must compile on older
457 systems where the define is not present can check against
458 __FreeBSD_version >= 900030.
460 The system dialog(1) has been replaced with a new version previously
461 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
462 with the previous version, but the libdialog associated with it has
463 a largely incompatible API. As such, the original version of libdialog
464 will be kept temporarily as libodialog, until its base system consumers
465 are replaced or updated. Bump __FreeBSD_version to 900030.
468 If you are trying to run make universe on a -stable system, and you get
469 the following warning:
470 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
471 unknown. config(8) likely too old."
472 or something similar to it, then you must upgrade your -stable system
473 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
474 stable/8) or build the config from the latest stable/8 branch and
475 install it on your system.
477 Prior to this date, building a current universe on 8-stable system from
478 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
479 error in the first kernel build phase. A new config on those old
480 systems will fix that problem for older versions of -current.
483 The TCP stack has been modified to allow Khelp modules to interact with
484 it via helper hook points and store per-connection data in the TCP
485 control block. Bump __FreeBSD_version to 900029. User space tools that
486 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
490 Generic IEEE 802.3 annex 31B full duplex flow control support has been
491 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
492 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
493 to take advantage of it instead of using custom implementations. This
494 means that these drivers now no longer unconditionally advertise
495 support for flow control but only do so if flow control is a selected
496 media option. This was implemented in the generic support that way in
497 order to allow flow control to be switched on and off via ifconfig(8)
498 with the PHY specific default to typically off in order to protect
499 from unwanted effects. Consequently, if you used flow control with
500 one of the above mentioned drivers you now need to explicitly enable
502 ifconfig bge0 media auto mediaopt flowcontrol
504 Along with the above mentioned changes generic support for setting
505 1000baseT master mode also has been added and brgphy(4), ciphy(4),
506 e1000phy(4) as well as ip1000phy(4) have been converted to take
507 advantage of it. This means that these drivers now no longer take the
508 link0 parameter for selecting master mode but the master media option
509 has to be used instead, for example like in the following:
510 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
512 Selection of master mode now is also available with all other PHY
513 drivers supporting 1000baseT.
516 The TCP stack has received a significant update to add support for
517 modularised congestion control and generally improve the clarity of
518 congestion control decisions. Bump __FreeBSD_version to 900025. User
519 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
520 sockstat) need to be recompiled.
523 The man(1) utility has been replaced by a new version that no longer
524 uses /etc/manpath.config. Please consult man.conf(5) for how to
525 migrate local entries to the new format.
528 The copyright strings printed by login(1) and sshd(8) at the time of a
529 new connection have been removed to follow other operating systems and
533 A workaround for a fixed ld bug has been removed in kernel code,
534 so make sure that your system ld is built from sources after
535 revision 210245 from 2010-07-19 (r211583 if building head kernel
536 on stable/8, r211584 for stable/7; both from 2010-08-21).
537 A symptom of incorrect ld version is different addresses for
538 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
541 The $ipv6_prefer variable in rc.conf(5) has been split into
542 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
544 The $ip6addrctl_policy is a variable to choose a pre-defined
545 address selection policy set by ip6addrctl(8). A value
546 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
549 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
550 flag (see an entry of 20090926) is set on an interface with no
551 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
552 security reason. If you want IPv6 link-local address on all
553 interfaces by default, set this to "YES".
555 The old ipv6_prefer="YES" is equivalent to
556 ipv6_activate_all_interfaces="YES" and
557 ip6addrctl_policy="ipv6_prefer".
560 DTrace has grown support for userland tracing. Due to this, DTrace is
561 now i386 and amd64 only.
562 dtruss(1) is now installed by default on those systems and a new
563 kernel module is needed for userland tracing: fasttrap.
564 No changes to your kernel config file are necessary to enable
565 userland tracing, but you might consider adding 'STRIP=' and
566 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
567 to have informative userland stack traces in DTrace (ustack).
570 The acpi_aiboost(4) driver has been removed in favor of the new
571 aibs(4) driver. You should update your kernel configuration file.
574 BSD grep has been imported to the base system and it is built by
575 default. It is completely BSD licensed, highly GNU-compatible, uses
576 less memory than its GNU counterpart and has a small codebase.
577 However, it is slower than its GNU counterpart, which is mostly
578 noticeable for larger searches, for smaller ones it is measurable
579 but not significant. The reason is complex, the most important factor
580 is that we lack a modern and efficient regex library and GNU
581 overcomes this by optimizing the searches internally. Future work
582 on improving the regex performance is planned, for the meantime,
583 users that need better performance, can build GNU grep instead by
584 setting the WITH_GNU_GREP knob.
587 Due to the import of powerpc64 support, all existing powerpc kernel
588 configuration files must be updated with a machine directive like this:
589 machine powerpc powerpc
591 In addition, an updated config(8) is required to build powerpc kernels
595 A new version of ZFS (version 15) has been merged to -HEAD.
596 This version uses a python library for the following subcommands:
597 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
598 For full functionality of these commands the following port must
599 be installed: sysutils/py-zfs
602 'vm_page's are now hashed by physical address to an array of mutexes.
603 Currently this is only used to serialize access to hold_count. Over
604 time the page queue mutex will be peeled away. This changes the size
605 of pmap on every architecture. And requires all callers of vm_page_hold
606 and vm_page_unhold to be updated.
609 WITH_CTF can now be specified in src.conf (not recommended, there
610 are some problems with static executables), make.conf (would also
611 affect ports which do not use GNU make and do not override the
612 compile targets) or in the kernel config (via "makeoptions
614 When WITH_CTF was specified there before this was silently ignored,
615 so make sure that WITH_CTF is not used in places which could lead
616 to unwanted behavior.
619 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
620 to allow 32-bit compatibility on non-x86 platforms. All kernel
621 configurations on amd64 and ia64 platforms using these options must
622 be modified accordingly.
625 The utmp user accounting database has been replaced with utmpx,
626 the user accounting interface standardized by POSIX.
627 Unfortunately the semantics of utmp and utmpx don't match,
628 making it practically impossible to support both interfaces.
629 The user accounting database is used by tools like finger(1),
630 last(1), talk(1), w(1) and ac(8).
632 All applications in the base system use utmpx. This means only
633 local binaries (e.g. from the ports tree) may still use these
634 utmp database files. These applications must be rebuilt to make
637 After the system has been upgraded, it is safe to remove the old
638 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
639 assuming their contents is of no importance anymore. Old wtmp
640 databases can only be used by last(1) and ac(8) after they have
641 been converted to the new format using wtmpcvt(1).
644 Introduce the kernel thread "deadlock resolver" (which can be enabled
645 via the DEADLKRES option, see NOTES for more details) and the
646 sleepq_type() function for sleepqueues.
649 The rc.firewall and rc.firewall6 were unified, and
650 rc.firewall6 and rc.d/ip6fw were removed.
651 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
652 variables are obsoleted. Instead, the following new rc
653 variables are added to rc.d/ipfw:
655 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
656 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
657 firewall_simple_onet_ipv6, firewall_trusted_ipv6
659 The meanings correspond to the relevant IPv4 variables.
665 The default terminal emulation for syscons(4) has been changed
666 from cons25 to xterm on all platforms except pc98. This means
667 that the /etc/ttys file needs to be updated to ensure correct
668 operation of applications on the console.
670 The terminal emulation style can be toggled per window by using
671 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
672 options can be used to change the compile-time default back to
675 To prevent graphical artifacts, make sure the TERM environment
676 variable is set to match the terminal emulation that is being
677 performed by syscons(4).
680 The layout of the structure ieee80211req_scan_result has changed.
681 Applications that require wireless scan results (e.g. ifconfig(8))
682 from net80211 need to be recompiled.
684 Applications such as wpa_supplicant(8) may require a full world
685 build without using NO_CLEAN in order to get synchronized with the
689 The iwn(4) driver has been updated to support the 5000 and 5150 series.
690 There's one kernel module for each firmware. Adding "device iwnfw"
691 to the kernel configuration file means including all three firmware
692 images inside the kernel. If you want to include just the one for
693 your wireless card, use the devices iwn4965fw, iwn5000fw or
697 The rc.d/network_ipv6, IPv6 configuration script has been integrated
698 into rc.d/netif. The changes are the following:
700 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
701 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
702 Note that both variables need the "inet6" keyword at the head.
704 Do not set $ipv6_network_interfaces manually if you do not
705 understand what you are doing. It is not needed in most cases.
707 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
710 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
711 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
713 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
714 all configured interfaces have "inet6 accept_rtadv" in the
715 $ifconfig_IF_ipv6. These are for backward compatibility.
717 3. A new variable $ipv6_prefer has been added. If NO, IPv6
718 functionality of interfaces with no corresponding
719 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
720 and the default address selection policy of ip6addrctl(8)
721 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
722 Note that if you want to configure IPv6 functionality on the
723 disabled interfaces after boot, first you need to clear the flag by
724 using ifconfig(8) like:
726 ifconfig em0 inet6 -ifdisabled
728 If YES, the default address selection policy is set as
731 The default value of $ipv6_prefer is NO.
733 4. If your system need to receive Router Advertisement messages,
734 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
735 scripts automatically invoke rtsol(8) when the interface becomes
736 UP. The Router Advertisement messages are used for SLAAC
737 (State-Less Address AutoConfiguration).
740 802.11s D3.03 support was committed. This is incompatible with the
741 previous code, which was based on D3.0.
744 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
745 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
746 control whether accepting Router Advertisement messages or not.
747 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
748 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
749 The ifconfig(8) utility now supports these flags.
752 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
753 mount(8) and -a option for df(1) to see them.
756 The old tunable hw.bus.devctl_disable has been superseded by
757 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
758 replaced by hw.bus.devctl_queue=0. The default for this new tunable
762 Remove the option STOP_NMI. The default action is now to use NMI only
763 for KDB via the newly introduced function stop_cpus_hard() and
764 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
767 The stable/8 branch created in subversion. This corresponds to the
768 RELENG_8 branch in CVS.
771 Bump the shared library version numbers for all libraries that do not
772 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
773 __FreeBSD_version to 800105.
776 Due to changes in the implementation of virtual network stack support,
777 all network-related kernel modules must be recompiled. As this change
778 breaks the ABI, bump __FreeBSD_version to 800104.
781 The TOE interface to the TCP syncache has been modified to remove
782 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
783 The cxgb driver is the only TOE consumer affected by this change, and
784 needs to be recompiled along with the kernel. As this change breaks
785 the ABI, bump __FreeBSD_version to 800103.
788 Padding has been added to struct tcpcb, sackhint and tcpstat in
789 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
790 maintaining the ABI. However, this change breaks the ABI, so bump
791 __FreeBSD_version to 800102. User space tools that rely on the size of
792 any of these structs (e.g. sockstat) need to be recompiled.
795 The NFS_LEGACYRPC option has been removed along with the old kernel
796 RPC implementation that this option selected. Kernel configurations
797 may need to be adjusted.
800 The network interface device nodes at /dev/net/<interface> have been
801 removed. All ioctl operations can be performed the normal way using
802 routing sockets. The kqueue functionality can generally be replaced
803 with routing sockets.
806 The documentation from the FreeBSD Documentation Project (Handbook,
807 FAQ, etc.) is now installed via packages by sysinstall(8) and under
808 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
811 The ABI of various structures related to the SYSV IPC API have been
812 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
813 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
817 Layout of struct vnet has changed as routing related variables were
818 moved to their own Vimage module. Modules need to be recompiled. Bump
819 __FreeBSD_version to 800099.
822 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
823 respectively. As long as no more than 16 groups per process are used,
824 no changes should be visible. When more than 16 groups are used, old
825 binaries may fail if they call getgroups() or getgrouplist() with
826 statically sized storage. Recompiling will work around this, but
827 applications should be modified to use dynamically allocated storage
828 for group arrays as POSIX.1-2008 does not cap an implementation's
829 number of supported groups at NGROUPS_MAX+1 as previous versions did.
831 NFS and portalfs mounts may also be affected as the list of groups is
832 truncated to 16. Users of NFS who use more than 16 groups, should
833 take care that negative group permissions are not used on the exported
834 file systems as they will not be reliable unless a GSSAPI based
835 authentication method is used.
838 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
839 option compiles in the support for adaptive spinning for lockmgrs
840 which want to enable it. The lockinit() function now accepts the flag
841 LK_ADAPTIVE in order to make the lock object subject to adaptive
842 spinning when both held in write and read mode.
845 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
846 changed. User applications that use this ioctl need to be rebuilt.
849 The layout of struct thread has changed. Kernel and modules need to
853 The layout of structs ifnet, domain, protosw and vnet_net has changed.
854 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
857 window(1) has been removed from the base system. It can now be
858 installed from ports. The port is called misc/window.
861 The way we are storing and accessing `routing table' entries has
862 changed. Programs reading the FIB, like netstat, need to be
866 A new netisr implementation has been added for FreeBSD 8. Network
867 file system modules, such as igmp, ipdivert, and others, should be
869 Bump __FreeBSD_version to 800096.
872 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
876 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
877 Bump __FreeBSD_version to 800094.
880 Add mnt_xflag field to 'struct mount'. File system modules need to be
882 Bump __FreeBSD_version to 800093.
885 The compiling option ADAPTIVE_SX has been retired while it has been
886 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
887 The KPI for sx_init_flags() changes as accepting flags:
888 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
889 been introduced in order to handle the reversed logic.
890 Bump __FreeBSD_version to 800092.
893 Add support for hierarchical jails. Remove global securelevel.
894 Bump __FreeBSD_version to 800091.
897 The layout of struct vnet_net has changed, therefore modules
899 Bump __FreeBSD_version to 800090.
902 The newly imported zic(8) produces a new format in the output. Please
903 run tzsetup(8) to install the newly created data to /etc/localtime.
906 The sysctl tree for the usb stack has renamed from hw.usb2.* to
907 hw.usb.* and is now consistent again with previous releases.
910 802.11 monitor mode support was revised and driver api's were changed.
911 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
912 of DLT_IEEE802_11. No user-visible data structures were changed but
913 applications that use DLT_IEEE802_11 may require changes.
914 Bump __FreeBSD_version to 800088.
917 The layout of the following structs has changed: sysctl_oid,
918 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
919 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
920 panics may be experienced. World rebuild is required for
921 correctly checking networking state from userland.
922 Bump __FreeBSD_version to 800085.
925 MLDv2 and Source-Specific Multicast (SSM) have been merged
926 to the IPv6 stack. VIMAGE hooks are in but not yet used.
927 The implementation of SSM within FreeBSD's IPv6 stack closely
928 follows the IPv4 implementation.
930 For kernel developers:
932 * The most important changes are that the ip6_output() and
933 ip6_input() paths no longer take the IN6_MULTI_LOCK,
934 and this lock has been downgraded to a non-recursive mutex.
936 * As with the changes to the IPv4 stack to support SSM, filtering
937 of inbound multicast traffic must now be performed by transport
938 protocols within the IPv6 stack. This does not apply to TCP and
939 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
941 * The KPIs used by IPv6 multicast are similar to those used by
942 the IPv4 stack, with the following differences:
943 * im6o_mc_filter() is analogous to imo_multicast_filter().
944 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
945 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
946 * IN6_LOOKUP_MULTI() has been deprecated and removed.
947 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
948 for MLDv1 have an additional 'timer' argument which is used to
949 jitter the initial membership report for the solicited-node
950 multicast membership on-link.
951 * This is not strictly needed for MLDv2, which already jitters
952 its report transmissions. However, the 'timer' argument is
953 preserved in case MLDv1 is active on the interface.
955 * The KAME linked-list based IPv6 membership implementation has
956 been refactored to use a vector similar to that used by the IPv4
958 Code which maintains a list of its own multicast memberships
959 internally, e.g. carp, has been updated to reflect the new
962 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
963 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
964 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
965 implementation constraint which needs to be addressed in HEAD.
967 For application developers:
969 * The changes are broadly similar to those made for the IPv4
972 * The use of IPv4 and IPv6 multicast socket options on the same
973 socket, using mapped addresses, HAS NOT been tested or supported.
975 * There are a number of issues with the implementation of various
976 IPv6 multicast APIs which need to be resolved in the API surface
977 before the implementation is fully compatible with KAME userland
978 use, and these are mostly to do with interface index treatment.
980 * The literature available discusses the use of either the delta / ASM
981 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
982 using setsourcefilter(3)/getsourcefilter(3). For more information
983 please refer to RFC 3768, 'Socket Interface Extensions for
984 Multicast Source Filters'.
986 * Applications which use the published RFC 3678 APIs should be fine.
988 For systems administrators:
990 * The mtest(8) utility has been refactored to support IPv6, in
991 addition to IPv4. Interface addresses are no longer accepted
992 as arguments, their names must be used instead. The utility
993 will map the interface name to its first IPv4 address as
994 returned by getifaddrs(3).
996 * The ifmcstat(8) utility has also been updated to print the MLDv2
997 endpoint state and source filter lists via sysctl(3).
999 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1000 loopback of IPv6 multicast datagrams by default; it defaults to 1
1001 to preserve the existing behaviour. Disabling multicast loopback is
1002 recommended for optimal system performance.
1004 * The IPv6 MROUTING code has been changed to examine this sysctl
1005 instead of attempting to perform a group lookup before looping
1006 back forwarded datagrams.
1008 Bump __FreeBSD_version to 800084.
1011 Implement low-level Bluetooth HCI API.
1012 Bump __FreeBSD_version to 800083.
1015 The layout of struct malloc_type, used by modules to register new
1016 memory allocation types, has changed. Most modules will need to
1017 be rebuilt or panics may be experienced.
1018 Bump __FreeBSD_version to 800081.
1021 Anticipate overflowing inp_flags - add inp_flags2.
1022 This changes most offsets in inpcb, so checking v4 connection
1023 state will require a world rebuild.
1024 Bump __FreeBSD_version to 800080.
1027 Add an llentry to struct route and struct route_in6. Modules
1028 embedding a struct route will need to be recompiled.
1029 Bump __FreeBSD_version to 800079.
1032 The size of rt_metrics_lite and by extension rtentry has changed.
1033 Networking administration apps will need to be recompiled.
1034 The route command now supports show as an alias for get, weighting
1035 of routes, sticky and nostick flags to alter the behavior of stateful
1037 Bump __FreeBSD_version to 800078.
1040 Do not use Giant for kbdmux(4) locking. This is wrong and
1041 apparently causing more problems than it solves. This will
1042 re-open the issue where interrupt handlers may race with
1043 kbdmux(4) in polling mode. Typical symptoms include (but
1044 not limited to) duplicated and/or missing characters when
1045 low level console functions (such as gets) are used while
1046 interrupts are enabled (for example geli password prompt,
1047 mountroot prompt etc.). Disabling kbdmux(4) may help.
1050 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1051 kernel modules referencing any of the above need to be recompiled.
1052 Bump __FreeBSD_version to 800075.
1055 GEOM_PART has become the default partition slicer for storage devices,
1056 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1057 introduces some changes:
1059 MSDOS/EBR: the devices created from MSDOS extended partition entries
1060 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1061 to devices with offset-based names. fstabs may need to be modified.
1063 BSD: the "geometry does not match label" warning is harmless in most
1064 cases but it points to problems in file system misalignment with
1065 disk geometry. The "c" partition is now implicit, covers the whole
1066 top-level drive and cannot be (mis)used by users.
1068 General: Kernel dumps are now not allowed to be written to devices
1069 whose partition types indicate they are meant to be used for file
1070 systems (or, in case of MSDOS partitions, as something else than
1073 Most of these changes date approximately from 200812.
1076 The uscanner(4) driver has been removed from the kernel. This follows
1077 Linux removing theirs in 2.6 and making libusb the default interface
1078 (supported by sane).
1081 The multicast forwarding code has been cleaned up. netstat(1)
1082 only relies on KVM now for printing bandwidth upcall meters.
1083 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1084 ip6_mroute_mod respectively. The config(5) options for statically
1085 compiling this code remain the same, i.e. 'options MROUTING'.
1088 Support for the IFF_NEEDSGIANT network interface flag has been
1089 removed, which means that non-MPSAFE network device drivers are no
1090 longer supported. In particular, if_ar, if_sr, and network device
1091 drivers from the old (legacy) USB stack can no longer be built or
1095 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1096 a bunch of new language catalog files have also been added.
1097 This means that some common libc messages are now localized and
1098 they depend on the LC_MESSAGES environmental variable.
1101 The k8temp(4) driver has been renamed to amdtemp(4) since
1102 support for Family 10 and Family 11 CPU families was added.
1105 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1106 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1108 For kernel developers, the most important changes are that the
1109 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1110 and this lock has been downgraded to a non-recursive mutex.
1112 Transport protocols (UDP, Raw IP) are now responsible for filtering
1113 inbound multicast traffic according to group membership and source
1114 filters. The imo_multicast_filter() KPI exists for this purpose.
1115 Transports which do not use multicast (SCTP, TCP) already reject
1116 multicast by default. Forwarding and receive performance may improve
1117 as a mutex acquisition is no longer needed in the ip_input()
1118 low-level input path. in_addmulti() and in_delmulti() are shimmed
1119 to new KPIs which exist to support SSM in-kernel.
1121 For application developers, it is recommended that loopback of
1122 multicast datagrams be disabled for best performance, as this
1123 will still cause the lock to be taken for each looped-back
1124 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1125 be tuned to 0 to disable loopback by default; it defaults to 1
1126 to preserve the existing behaviour.
1128 For systems administrators, to obtain best performance with
1129 multicast reception and multiple groups, it is always recommended
1130 that a card with a suitably precise hash filter is used. Hash
1131 collisions will still result in the lock being taken within the
1132 transport protocol input path to check group membership.
1134 If deploying FreeBSD in an environment with IGMP snooping switches,
1135 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1136 enabled; this forces 224.0.0.0/24 group membership to be announced
1139 The size of 'struct igmpstat' has changed; netstat needs to be
1140 recompiled to reflect this.
1141 Bump __FreeBSD_version to 800070.
1144 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1145 updated to use it. This requires a buildworld/installworld in order to
1146 update the library and dependencies (usbconfig, etc). Its advisable to
1147 rebuild all ports which uses libusb. More specific directions are given
1148 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1149 libusb are no longer required and can be removed.
1152 A workaround is committed to allow the creation of System V shared
1153 memory segment of size > 2 GB on the 64-bit architectures.
1154 Due to a limitation of the existing ABI, the shm_segsz member
1155 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1156 wrong for large segments. Note that limits must be explicitly
1157 raised to allow such segments to be created.
1160 The layout of struct ifnet has changed, requiring a rebuild of all
1161 network device driver modules.
1164 The /dev handling for the new USB stack has changed, a
1165 buildworld/installworld is required for libusb20.
1168 The new USB2 stack has now been permanently moved in and all kernel and
1169 module names reverted to their previous values (eg, usb, ehci, ohci,
1170 ums, ...). The old usb stack can be compiled in by prefixing the name
1171 with the letter 'o', the old usb modules have been removed.
1172 Updating entry 20090216 for xorg and 20090215 for libmap may still
1176 The rc.conf(5) option if_up_delay has been renamed to
1177 defaultroute_delay to better reflect its purpose. If you have
1178 customized this setting in /etc/rc.conf you need to update it to
1182 xorg 7.4 wants to configure its input devices via hald which does not
1183 yet work with USB2. If the keyboard/mouse does not work in xorg then
1185 Option "AllowEmptyInput" "off"
1186 to your ServerLayout section. This will cause X to use the configured
1187 kbd and mouse sections from your xorg.conf.
1190 The GENERIC kernels for all architectures now default to the new USB2
1191 stack. No kernel config options or code have been removed so if a
1192 problem arises please report it and optionally revert to the old USB
1193 stack. If you are loading USB kernel modules or have a custom kernel
1194 that includes GENERIC then ensure that usb names are also changed over,
1195 eg uftdi -> usb2_serial_ftdi.
1197 Older programs linked against the ports libusb 0.1 need to be
1198 redirected to the new stack's libusb20. /etc/libmap.conf can
1200 # Map old usb library to new one for usb2 stack
1201 libusb-0.1.so.8 libusb20.so.1
1204 All USB ethernet devices now attach as interfaces under the name ueN
1205 (eg. ue0). This is to provide a predictable name as vendors often
1206 change usb chipsets in a product without notice.
1209 The ichsmb(4) driver has been changed to require SMBus slave
1210 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1211 All of the other SMBus controller drivers require left-justified
1212 slave addresses, so this change makes all the drivers provide the
1216 INET6 statistics (struct ip6stat) was updated.
1217 netstat(1) needs to be recompiled.
1220 NTFS has been removed from GENERIC kernel on amd64 to match
1221 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1222 will load ntfs.ko module automatically when NTFS support is
1223 actually needed, unless ntfs.ko is not installed or security
1224 level prohibits loading kernel modules. If either is the case,
1225 "options NTFS" has to be added into kernel config.
1228 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1229 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1230 800061. User space tools that rely on the size of struct tcpcb in
1231 tcp_var.h (e.g. sockstat) need to be recompiled.
1234 ng_tty(4) module updated to match the new TTY subsystem.
1235 Due to API change, user-level applications must be updated.
1236 New API support added to mpd5 CVS and expected to be present
1237 in next mpd5.3 release.
1240 With __FreeBSD_version 800060 the makefs tool is part of
1241 the base system (it was a port).
1244 The afdata and ifnet locks have been changed from mutexes to
1245 rwlocks, network modules will need to be re-compiled.
1248 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1249 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1250 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1251 architecture and 40 bytes on 64-bit architecture. The userland
1252 applications "arp" and "ndp" have been updated accordingly.
1253 The output from "netstat -r" shows only routing entries and
1254 none of the L2 information.
1257 __FreeBSD_version 800057 marks the switchover from the
1258 binary ath hal to source code. Users must add the line:
1260 options AH_SUPPORT_AR5416
1262 to their kernel config files when specifying:
1266 The ath_hal module no longer exists; the code is now compiled
1267 together with the driver in the ath module. It is now
1268 possible to tailor chip support (i.e. reduce the set of chips
1269 and thereby the code size); consult ath_hal(4) for details.
1272 __FreeBSD_version 800054 adds memory barriers to
1273 <machine/atomic.h>, new interfaces to ifnet to facilitate
1274 multiple hardware transmit queues for cards that support
1275 them, and a lock-less ring-buffer implementation to
1276 enable drivers to more efficiently manage queueing of
1280 A new version of ZFS (version 13) has been merged to -HEAD.
1281 This version has zpool attribute "listsnapshots" off by
1282 default, which means "zfs list" does not show snapshots,
1283 and is the same as Solaris behavior.
1286 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1289 The uhci, ohci, ehci and slhci USB Host controller drivers have
1290 been put into separate modules. If you load the usb module
1291 separately through loader.conf you will need to load the
1292 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1293 controller add the following to loader.conf:
1299 The ABI used by the PMC toolset has changed. Please keep
1300 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1304 atapci kernel module now includes only generic PCI ATA
1305 driver. AHCI driver moved to ataahci kernel module.
1306 All vendor-specific code moved into separate kernel modules:
1307 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1308 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1309 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1310 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1313 The TTY subsystem of the kernel has been replaced by a new
1314 implementation, which provides better scalability and an
1315 improved driver model. Most common drivers have been migrated to
1316 the new TTY subsystem, while others have not. The following
1317 drivers have not yet been ported to the new TTY layer:
1320 cy, digi, rc, rp, sio
1326 ng_h4, ng_tty, ppp, sl, snp
1328 Adding these drivers to your kernel configuration file shall
1329 cause compilation to fail.
1332 ntpd has been upgraded to 4.2.4p5.
1335 OpenSSH has been upgraded to 5.1p1.
1337 For many years, FreeBSD's version of OpenSSH preferred DSA
1338 over RSA for host and user authentication keys. With this
1339 upgrade, we've switched to the vendor's default of RSA over
1340 DSA. This may cause upgraded clients to warn about unknown
1341 host keys even for previously known hosts. Users should
1342 follow the usual procedure for verifying host keys before
1343 accepting the RSA key.
1345 This can be circumvented by setting the "HostKeyAlgorithms"
1346 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1349 Please note that the sequence of keys offered for
1350 authentication has been changed as well. You may want to
1351 specify IdentityFile in a different order to revert this
1355 The sio(4) driver has been removed from the i386 and amd64
1356 kernel configuration files. This means uart(4) is now the
1357 default serial port driver on those platforms as well.
1359 To prevent collisions with the sio(4) driver, the uart(4) driver
1360 uses different names for its device nodes. This means the
1361 onboard serial port will now most likely be called "ttyu0"
1362 instead of "ttyd0". You may need to reconfigure applications to
1363 use the new device names.
1365 When using the serial port as a boot console, be sure to update
1366 /boot/device.hints and /etc/ttys before booting the new kernel.
1367 If you forget to do so, you can still manually specify the hints
1368 at the loader prompt:
1370 set hint.uart.0.at="isa"
1371 set hint.uart.0.port="0x3F8"
1372 set hint.uart.0.flags="0x10"
1373 set hint.uart.0.irq="4"
1377 The gpt(8) utility has been removed. Use gpart(8) to partition
1381 The version that Linuxulator emulates was changed from 2.4.2
1382 to 2.6.16. If you experience any problems with Linux binaries
1383 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1384 if it fixes the problem contact emulation mailing list.
1387 ISDN4BSD (I4B) was removed from the src tree. You may need to
1388 update a your kernel configuration and remove relevant entries.
1391 I have checked in code to support multiple routing tables.
1392 See the man pages setfib(1) and setfib(2).
1393 This is a hopefully backwards compatible version,
1394 but to make use of it you need to compile your kernel
1395 with options ROUTETABLES=2 (or more up to 16).
1398 The 802.11 wireless support was redone to enable multi-bss
1399 operation on devices that are capable. The underlying device
1400 is no longer used directly but instead wlanX devices are
1401 cloned with ifconfig. This requires changes to rc.conf files.
1402 For example, change:
1403 ifconfig_ath0="WPA DHCP"
1406 ifconfig_wlan0="WPA DHCP"
1407 see rc.conf(5) for more details. In addition, mergemaster of
1408 /etc/rc.d is highly recommended. Simultaneous update of userland
1409 and kernel wouldn't hurt either.
1411 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1412 modules were merged into the base wlan module. All references
1413 to these modules (e.g. in kernel config files) must be removed.
1416 psm(4) has gained write(2) support in native operation level.
1417 Arbitrary commands can be written to /dev/psm%d and status can
1418 be read back from it. Therefore, an application is responsible
1419 for status validation and error recovery. It is a no-op in
1420 other operation levels.
1423 Support for KSE threading has been removed from the kernel. To
1424 run legacy applications linked against KSE libmap.conf may
1425 be used. The following libmap.conf may be used to ensure
1426 compatibility with any prior release:
1428 libpthread.so.1 libthr.so.1
1429 libpthread.so.2 libthr.so.2
1430 libkse.so.3 libthr.so.3
1433 The layout of struct vmspace has changed. This affects libkvm
1434 and any executables that link against libkvm and use the
1435 kvm_getprocs() function. In particular, but not exclusively,
1436 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1437 The effects are minimal, but it's advisable to upgrade world
1441 The latest em driver no longer has support in it for the
1442 82575 adapter, this is now moved to the igb driver. The
1443 split was done to make new features that are incompatible
1444 with older hardware easier to do.
1447 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1448 likewise the kernel option is now GEOM_LINUX_LVM.
1451 The default NFS mount mode has changed from UDP to TCP for
1452 increased reliability. If you rely on (insecurely) NFS
1453 mounting across a firewall you may need to update your
1457 Belatedly note the addition of m_collapse for compacting
1461 The fts(3) structures have been changed to use adequate
1462 integer types for their members and so to be able to cope
1463 with huge file trees. The old fts(3) ABI is preserved
1464 through symbol versioning in libc, so third-party binaries
1465 using fts(3) should still work, although they will not take
1466 advantage of the extended types. At the same time, some
1467 third-party software might fail to build after this change
1468 due to unportable assumptions made in its source code about
1469 fts(3) structure members. Such software should be fixed
1470 by its vendor or, in the worst case, in the ports tree.
1471 FreeBSD_version 800015 marks this change for the unlikely
1472 case that a portable fix is impossible.
1475 To upgrade to -current after this date, you must be running
1476 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1477 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1480 The ADAPTIVE_GIANT kernel option has been retired because its
1481 functionality is the default now.
1484 The AT keyboard emulation of sunkbd(4) has been turned on
1485 by default. In order to make the special symbols of the Sun
1486 keyboards driven by sunkbd(4) work under X these now have
1487 to be configured the same way as Sun USB keyboards driven
1488 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1490 Option "XkbLayout" "us"
1491 Option "XkbRules" "xorg"
1492 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1495 It has been decided that it is desirable to provide ABI
1496 backwards compatibility to the FreeBSD 4/5/6 versions of the
1497 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1498 broken with the introduction of PCI domain support (see the
1499 20070930 entry). Unfortunately, this required the ABI of
1500 PCIOCGETCONF to be broken again in order to be able to
1501 provide backwards compatibility to the old version of that
1502 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1503 again. As for prominent ports this affects neither pciutils
1504 nor xorg-server this time, the hal port needs to be rebuilt
1508 The misnamed kthread_create() and friends have been renamed
1509 to kproc_create() etc. Many of the callers already
1510 used kproc_start()..
1511 I will return kthread_create() and friends in a while
1512 with implementations that actually create threads, not procs.
1513 Renaming corresponds with version 800002.
1522 Avoid using make -j when upgrading. While generally safe, there are
1523 sometimes problems using -j to upgrade. If your upgrade fails with
1524 -j, please try again without -j. From time to time in the past there
1525 have been problems using -j with buildworld and/or installworld. This
1526 is especially true when upgrading between "distant" versions (eg one
1527 that cross a major release boundary or several minor releases, or when
1528 several months have passed on the -current branch).
1530 Sometimes, obscure build problems are the result of environment
1531 poisoning. This can happen because the make utility reads its
1532 environment when searching for values for global variables. To run
1533 your build attempts in an "environmental clean room", prefix all make
1534 commands with 'env -i '. See the env(1) manual page for more details.
1536 When upgrading from one major version to another it is generally best
1537 to upgrade to the latest code in the currently installed branch first,
1538 then do an upgrade to the new branch. This is the best-tested upgrade
1539 path, and has the highest probability of being successful. Please try
1540 this approach before reporting problems with a major version upgrade.
1544 When upgrading the boot ZFS pool to a new version, always follow
1547 1.) recompile and reinstall the ZFS boot loader and boot block
1548 (this is part of "make buildworld" and "make installworld")
1550 2.) update the ZFS boot block on your boot drive
1552 The following example updates the ZFS boot block on the first
1553 partition (freebsd-boot) of a GPT partitioned drive ad0:
1554 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1556 Non-boot pools do not need these updates.
1560 If you are updating from a prior version of FreeBSD (even one just
1561 a few days old), you should follow this procedure. It is the most
1562 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1564 make kernel-toolchain
1565 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1566 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1568 To test a kernel once
1569 ---------------------
1570 If you just want to boot a kernel once (because you are not sure
1571 if it works, or if you want to boot a known bad kernel to provide
1572 debugging information) run
1573 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1574 nextboot -k testkernel
1576 To just build a kernel when you know that it won't mess you up
1577 --------------------------------------------------------------
1578 This assumes you are already running a CURRENT system. Replace
1579 ${arch} with the architecture of your machine (e.g. "i386",
1580 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1582 cd src/sys/${arch}/conf
1583 config KERNEL_NAME_HERE
1584 cd ../compile/KERNEL_NAME_HERE
1589 If this fails, go to the "To build a kernel" section.
1591 To rebuild everything and install it on the current system.
1592 -----------------------------------------------------------
1593 # Note: sometimes if you are running current you gotta do more than
1594 # is listed here if you are upgrading from a really old current.
1596 <make sure you have good level 0 dumps>
1598 make kernel KERNCONF=YOUR_KERNEL_HERE
1600 <reboot in single user> [3]
1608 To cross-install current onto a separate partition
1609 --------------------------------------------------
1610 # In this approach we use a separate partition to hold
1611 # current's root, 'usr', and 'var' directories. A partition
1612 # holding "/", "/usr" and "/var" should be about 2GB in
1615 <make sure you have good level 0 dumps>
1618 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1619 <maybe newfs current's root partition>
1620 <mount current's root partition on directory ${CURRENT_ROOT}>
1621 make installworld DESTDIR=${CURRENT_ROOT}
1622 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1623 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1624 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1625 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1626 <reboot into current>
1627 <do a "native" rebuild/install as described in the previous section>
1628 <maybe install compatibility libraries from ports/misc/compat*>
1632 To upgrade in-place from stable to current
1633 ----------------------------------------------
1634 <make sure you have good level 0 dumps>
1636 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1638 <reboot in single user> [3]
1645 Make sure that you've read the UPDATING file to understand the
1646 tweaks to various things you need. At this point in the life
1647 cycle of current, things change often and you are on your own
1648 to cope. The defaults can also change, so please read ALL of
1649 the UPDATING entries.
1651 Also, if you are tracking -current, you must be subscribed to
1652 freebsd-current@freebsd.org. Make sure that before you update
1653 your sources that you have read and understood all the recent
1654 messages there. If in doubt, please track -stable which has
1655 much fewer pitfalls.
1657 [1] If you have third party modules, such as vmware, you
1658 should disable them at this point so they don't crash your
1661 [3] From the bootblocks, boot -s, and then do
1666 adjkerntz -i # if CMOS is wall time
1667 Also, when doing a major release upgrade, it is required that
1668 you boot into single user mode to do the installworld.
1670 [4] Note: This step is non-optional. Failure to do this step
1671 can result in a significant reduction in the functionality of the
1672 system. Attempting to do it by hand is not recommended and those
1673 that pursue this avenue should read this file carefully, as well
1674 as the archives of freebsd-current and freebsd-hackers mailing lists
1675 for potential gotchas. The -U option is also useful to consider.
1676 See mergemaster(8) for more information.
1678 [5] Usually this step is a noop. However, from time to time
1679 you may need to do this if you get unknown user in the following
1680 step. It never hurts to do it all the time. You may need to
1681 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1682 install) after the buildworld before this step if you last updated
1683 from [78]-stable or 9-stable before 20130430.
1685 [6] This only deletes old files and directories. Old libraries
1686 can be deleted by "make delete-old-libs", but you have to make
1687 sure that no program is using those libraries anymore.
1689 [8] In order to have a kernel that can run the 4.x binaries needed to
1690 do an installworld, you must include the COMPAT_FREEBSD4 option in
1691 your kernel. Failure to do so may leave you with a system that is
1692 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1693 required to run the 5.x binaries on more recent kernels. And so on
1694 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1696 Make sure that you merge any new devices from GENERIC since the
1697 last time you updated your kernel config file.
1699 [9] When checking out sources, you must include the -P flag to have
1700 cvs prune empty directories.
1702 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1703 "?=" instead of the "=" assignment operator, so that buildworld can
1704 override the CPUTYPE if it needs to.
1706 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1707 not on the command line, or in /etc/make.conf. buildworld will
1708 warn if it is improperly defined.
1711 This file contains a list, in reverse chronological order, of major
1712 breakages in tracking -current. It is not guaranteed to be a complete
1713 list of such breakages, and only contains entries since October 10, 2007.
1714 If you need to see UPDATING entries from before that date, you will need
1715 to fetch an UPDATING file from an older FreeBSD release.
1717 Copyright information:
1719 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1721 Redistribution, publication, translation and use, with or without
1722 modification, in full or in part, in any form or format of this
1723 document are permitted without further permission from the author.
1725 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1726 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1727 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1728 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1729 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1730 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1731 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1732 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1733 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1734 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1735 POSSIBILITY OF SUCH DAMAGE.
1737 Contact Warner Losh if you have any questions about your use of