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