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 20160114 p33 FreeBSD-EN-16:02.pf
15 FreeBSD-EN-16:03.yplib
18 FreeBSD-SA-16:03.linux
19 FreeBSD-SA-16:04.linux
21 FreeBSD-SA-16:06.bsnmpd
23 Fix pf(4) generating bad TCP checksums. [EN-16:02]
24 Fix infinite loop in YP/NIS client library. [EN-16:03]
25 Fix remote denial of service in SCTP. [SA-16:01]
26 Update NTP to 4.2.8p5. [SA-16:02]
27 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
28 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
29 Fix crash in TCP MD5 signatures. [SA-16:05]
30 Fix insecure default permissions for snmpd.config. [SA-16:06]
32 20151216 p32 FreeBSD-SA-15:27.bind
33 Fix BIND remote denial of service vulnerability. [SA-15:27]
35 20151205 p31 FreeBSD-SA-15:26.openssl
37 Fix OpenSSL X509_ATTRIBUTE memory leak. [SA-15:26]
39 20151104 p30 FreeBSD-SA-15:25.ntp [revised]
40 FreeBSD-EN-15:19.kqueue
43 Fix regression of ntpq(8) utility exiting due to trap 6 in
44 9.3-RELEASE-p29. [SA-15:25]
46 Fix regression in ntpd(8) lacking support for RAWDCF reference
47 clock in 9.3-RELEASE-p29. [SA-15:25]
49 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
51 Fix applications exiting due to segmentation violation on a correct
52 memory address. [EN-15:20]
54 20151026: p29 FreeBSD-SA-15:25.ntp
56 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
58 The configuration file syntax has been changed, thus mergemaster
59 run is recommended. Now the "kod" parameter requires "limited"
60 parameter. If the ntp.conf is not updated, the ntpd will run
61 successfully, but with KoD disabled.
63 20151002: p28 FreeBSD-SA-15:24.rpcbind [revised]
64 Revised patch to address a regression that prevents NIS from working.
66 20150929: p27 FreeBSD-SA-15:24.rpcbind
68 Fix rpcbind(8) remote denial of service. [SA-15:24]
70 20150916: p26 FreeBSD-EN-15:18.pkg
72 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
74 20150902: p25 FreeBSD-SA-15:23.bind
76 Fix BIND remote denial of service vulnerability. [SA-15:23]
78 20150825: p24 FreeBSD-SA-15:21.amd64
79 FreeBSD-SA-15:22.openssh
82 Fix local privilege escalation in IRET handler. [SA-15:21]
84 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
86 Fix insufficient check of unsupported pkg(7) signature methods.
89 20150818: p23 FreeBSD-SA-15:20.expat
91 Fix multiple integer overflows in expat (libbsdxml) XML parser.
94 20150805: p22 FreeBSD-SA-15:19.routed
96 Fix routed remote denial of service vulnerability.
98 20150728: p21 FreeBSD-SA-15:15.tcp
99 FreeBSD-SA-15:16.openssh
100 FreeBSD-SA-15:17.bind
102 Fix resource exhaustion in TCP reassembly. [SA-15:15]
104 Fix OpenSSH multiple vulnerabilities. [SA-15:16]
106 Fix BIND remote denial of service vulnerability. [SA-15:17]
108 20150721: p20 FreeBSD-SA-15:13.tcp
110 Fix resource exhaustion due to sessions stuck in LAST_ACK state.
113 20150707: p19 FreeBSD-SA-15:11.bind
114 Fix BIND resolver remote denial of service when validating.
116 20150630: p18 FreeBSD-EN-15:08.sendmail [revised]
117 FreeBSD-EN-15:09.xlocale
119 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
121 Fix inconsistency between locale and rune locale states.
124 20150618: p17 FreeBSD-EN-15:08.sendmail
125 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
127 20150612: p16 FreeBSD-SA-15:10.openssl
128 Fix multiple vulnerabilities in OpenSSL. [SA-15:10]
130 20150609: p15 FreeBSD-EN-15:06.file
132 Updated base system file(1) to 5.22 to address multiple denial
135 20150513: p14 FreeBSD-EN-15:04.freebsd-update
137 Fix bug with freebsd-update(8) that does not ensure the previous
138 upgrade was completed. [EN-15:04]
140 20150407: p13 FreeBSD-SA-15:04.igmp [revised]
142 FreeBSD-SA-15:09.ipv6
144 Improved patch for SA-15:04.igmp.
146 Fix multiple vulnerabilities of ntp. [SA-15:07]
148 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
151 Fix patch for SA-15:06.openssl.
153 20150319: p11 FreeBSD-SA-15:06.openssl
154 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
156 20150225: p10 FreeBSD-SA-15:04.igmp
157 FreeBSD-SA-15:05.bind
159 FreeBSD-EN-15:02.openssl
160 FreeBSD-EN-15:03.freebsd-update
162 Fix integer overflow in IGMP protocol. [SA-15:04]
164 Fix BIND remote denial of service vulnerability. [SA-15:05]
166 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
168 Updated base system OpenSSL to 0.9.8zd. [EN-15:02]
170 Fix freebsd-update libraries update ordering issue. [EN-15:03]
172 20150127: p9 FreeBSD-SA-15:02.kmem
173 FreeBSD-SA-15:03.sctp
175 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
176 vulnerability. [SA-15:02]
178 Fix SCTP stream reset vulnerability. [SA-15:03]
180 20150114: p8 FreeBSD-SA-15:01.openssl
181 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
183 20141223: p7 FreeBSD-SA-14:31.ntp
184 FreeBSD-EN-14:13.freebsd-update
186 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
187 Fix directory deletion issue in freebsd-update. [EN-14:13]
189 20141210: p6 FreeBSD-SA-14:28.file
190 FreeBSD-SA-14:29.bind
192 Fix multiple vulnerabilities in file(1) and libmagic(3).
195 Fix BIND remote denial of service vulnerability. [SA-14:29]
197 20141104: p5 FreeBSD-SA-14:25.setlogin
201 Fix kernel stack disclosure in setlogin(2) / getlogin(2).
204 Fix remote command execution in ftp(1). [SA-14:26]
206 Fix NFSv4 and ZFS cache consistency issue. [EN-14:12]
208 20141022: p4 FreeBSD-EN-14:10.tzdata
209 FreeBSD-EN-14:11.crypt
211 Time zone data file update. [EN-14:10]
213 Change crypt(3) default hashing algorithm back to DES. [EN-14:11]
215 20141021: p3 FreeBSD-SA-14:20.rtsold
216 FreeBSD-SA-14:21.routed
217 FreeBSD-SA-14:22.namei
218 FreeBSD-SA-14:23.openssl
220 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
222 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
224 Fix memory leak in sandboxed namei lookup. [SA-14:22]
226 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
228 20140916: p2 FreeBSD-SA-14:19.tcp
229 Fix Denial of Service in TCP packet processing. [SA-14:19]
231 20140909: p1 FreeBSD-SA-14:18.openssl
232 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
238 On i386 and amd64 systems, the onifconsole flag is now set by default
239 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
240 as a login TTY if it is set in the bootloader as an active kernel
241 console. No changes in behavior should result otherwise. To revert to
242 the previous behavior, set ttyu0 to "off" in /etc/ttys.
245 Clang and llvm have been upgraded to 3.4.1 release.
248 Clang and llvm have been upgraded to 3.4 release.
251 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
252 been deprecated and will not be part of FreeBSD 11.0 and later
253 releases. If you use this driver, please consider switching to
254 the nfe(4) driver instead.
257 The behavior of gss_pseudo_random() for the krb5 mechanism
258 has changed, for applications requesting a longer random string
259 than produced by the underlying enctype's pseudo-random() function.
260 In particular, the random string produced from a session key of
261 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
262 be different at the 17th octet and later, after this change.
263 The counter used in the PRF+ construction is now encoded as a
264 big-endian integer in accordance with RFC 4402.
265 __FreeBSD_version is bumped to 902505.
271 Behavior of devfs rules path matching has been changed.
272 Pattern is now always matched against fully qualified devfs
273 path and slash characters must be explicitly matched by
274 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
275 subdirectories must be reviewed.
278 hastctl(8)'s `status' command output changed to terse one-liner format.
279 Scripts using this should switch to `list' command or be rewritten.
282 Fix a bug that allowed a tracing process (e.g. gdb) to write
283 to a memory-mapped file in the traced process's address space
284 even if neither the traced process nor the tracing process had
285 write access to that file.
288 Added ZFS TRIM support which is enabled by default. To disable
289 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
291 Creating new ZFS pools and adding new devices to existing pools
292 first performs a full device level TRIM which can take a significant
293 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
294 to disable this behaviour.
296 ZFS TRIM requires the underlying device support BIO_DELETE which
297 is currently provided by methods such as ATA TRIM and SCSI UNMAP
298 via CAM, which are typically supported by SSD's.
300 Stats for ZFS TRIM can be monitored by looking at the sysctl's
301 under kstat.zfs.misc.zio_trim.
304 `list' command has been added to hastctl(8). For now, it is full
305 equivalent of `status' command.
306 WARNING: in the near future the output of hastctl's status command
307 will change to more terse format. If you use `hastctl status'
308 for parsing in your scripts, switch to `hastctl list'.
311 The mergemaster command now uses the default MAKEOBJDIRPREFIX
312 rather than creating it's own in the temporary directory in
313 order allow access to bootstrapped versions of tools such as
314 install and mtree. When upgrading from version of FreeBSD where
315 the install command does not support -l, you will need to
316 install a new mergemaster command if mergemaster -p is required.
317 This can be accomplished with the command (cd src/usr.sbin/mergemaster
320 Due to the use of the new -l option to install(1) during build
321 and install, you must take care not to directly set the INSTALL
322 make variable in your /etc/make.conf, /etc/src.conf, or on the
323 command line. If you wish to use the -C flag for all installs
324 you may be able to add INSTALL+=-C to /etc/make.conf or
328 Fix a bug that allows NFS clients to issue READDIR on files.
331 The install(1) option -M has changed meaning and now takes an
332 argument that is a file or path to append logs to. In the
333 unlikely event that -M was the last option on the command line
334 and the command line contained at least two files and a target
335 directory the first file will have logs appended to it. The -M
336 option served little practical purpose in the last decade so it's
337 used expected to be extremely rare.
340 A new compression method (lz4) has been merged to. Please refer to
341 zpool-features(7) for more information.
343 Please refer to the "ZFS notes" section of this file for information
344 on upgrading boot ZFS pools.
347 The VFS KBI was changed with the merge of several nullfs
348 optimizations and fixes. All filesystem modules must be
352 With the addition of auditdistd(8), a new auditdistd user is now
353 depended on during installworld. "mergemaster -p" can be used to add
354 the user prior to installworld, as documented in the handbook.
360 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
361 Starting with this version the old system of ZFS pool versioning
362 is superseded by "feature flags". This concept enables forward
363 compatibility against certain future changes in functionality of ZFS
364 pools. The first two read-only compatible "feature flags" for ZFS
365 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
366 For more information read the new zpool-features(7) manual page.
367 Please refer to the "ZFS notes" section of this file for information
368 on upgrading boot ZFS pools.
371 The commit introducing bsd.compiler.mk breaks the traditional
372 building of kernels before this point. Add -m ${SRC}/share/mk
373 (for the right value of SRC) to your command lines to work
374 around; update your useland to a point after this; or use the
375 buildkernel/installkernel top-level targets. See also 20120829.
378 The IPFIREWALL_FORWARD kernel option has been removed. Its
379 functionality now turned on by default.
382 The random(4) support for the VIA hardware random number
383 generator (`PADLOCK') is no longer enabled unconditionally.
384 Add the PADLOCK_RNG option in the custom kernel config if
385 needed. The GENERIC kernels on i386 and amd64 do include the
386 option, so the change only affects the custom kernel
390 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
391 the traditional method, you must update your system with an installworld
392 before the kernel will build. The documented make buildkernel/installkernel
393 interfaces (coupled with fresh make kernel-toolchain) continue to work.
396 The sparc64 ZFS loader has been changed to no longer try to auto-
397 detect ZFS providers based on diskN aliases but now requires these
398 to be explicitly listed in the OFW boot-device environment variable.
401 Now unix domain sockets behave "as expected" on nullfs(5). Previously
402 nullfs(5) did not pass through all behaviours to the underlying layer,
403 as a result if we bound to a socket on the lower layer we could connect
404 only to the lower path; if we bound to the upper layer we could connect
405 only to the upper path. The new behavior is one can connect to both the
406 lower and the upper paths regardless what layer path one binds to.
409 The acpi_wmi(4) status device /dev/wmistat has been renamed to
413 A new VOP_ADVISE() was added to support posix_fadvise(2). All
414 filesystem modules must be recompiled.
417 The interface of the VOP_VPTOCNP(9) changed, now the returned
418 vnode shall be referenced, previously it was required to be
419 only held. All in-tree filesystems are converted.
425 The broken amd(4) driver has been replaced with esp(4) in the amd64,
426 i386 and pc98 GENERIC kernel configuration files.
429 This commit modifies vfs_register() so that it uses a hash
430 calculation to set vfc_typenum, which is enabled by default.
431 The first time a system is booted after this change, the
432 vfc_typenum values will change for all file systems. The
433 main effect of this is a change to the NFS server file handles
434 for file systems that use vfc_typenum in their fsid, such as ZFS.
435 It will, however, prevent vfc_typenum from changing when file
436 systems are loaded in a different order for subsequent reboots.
437 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
438 until you are ready to remount all NFS clients after a reboot.
441 Bump the shared library version numbers for libraries that
442 do not use symbol versioning, have changed the ABI compared
443 to stable/8 and which shared library version was not bumped.
444 Done as part of 9.0-RELEASE cycle.
447 During the merge of Capsicum features, the fget(9) KPI was modified.
448 This may require the rebuilding of out-of-tree device drivers --
449 issues have been reported specifically with the nVidia device driver.
450 __FreeBSD_version is bumped to 900041.
452 Also, there is a period between 20110811 and 20110814 where the
453 special devices /dev/{stdin,stdout,stderr} did not work correctly.
454 Building world from a kernel during that window may not work.
457 The packet filter (pf) code has been updated to OpenBSD 4.5.
458 You need to update userland tools to be in sync with kernel.
459 This update breaks backward compatibility with earlier pfsync(4)
460 versions. Care must be taken when updating redundant firewall setups.
463 The following sysctls and tunables are retired on x86 platforms:
465 machdep.hlt_logical_cpus
466 The following sysctl is retired:
467 machdep.hyperthreading_allowed
468 The sysctls were supposed to provide a way to dynamically offline and
469 online selected CPUs on x86 platforms, but the implementation has not
470 been reliable especially with SCHED_ULE scheduler.
471 machdep.hyperthreading_allowed tunable is still available to ignore
472 hyperthreading CPUs at OS level.
473 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
474 where X is an APIC ID of a CPU. Be advised, though, that disabling
475 CPUs in non-uniform fashion will result in non-uniform topology and
476 may lead to sub-optimal system performance with SCHED_ULE, which is
480 cpumask_t type is retired and cpuset_t is used in order to describe
484 Changes to ifconfig(8) for dynamic address family detection mandate
485 that you are running a kernel of 20110525 or later. Make sure to
486 follow the update procedure to boot a new kernel before installing
490 Support for sun4v architecture is officially dropped
493 Several KPI breaking changes have been committed to the mii(4) layer,
494 the PHY drivers and consequently some Ethernet drivers using mii(4).
495 This means that miibus.ko and the modules of the affected Ethernet
496 drivers need to be recompiled.
498 Note to kernel developers: Given that the OUI bit reversion problem
499 was fixed as part of these changes all mii(4) commits related to OUIs,
500 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
501 handling, no longer can be merged verbatim to stable/8 and previous
505 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
506 into their kernel configurations along with 'device pci'.
509 The default NFS client is now the new NFS client, so fstype "newnfs"
510 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
511 Although mounts via fstype "nfs" will usually work without userland
512 changes, it is recommended that the mount(8) and mount_nfs(8)
513 commands be rebuilt from sources and that a link to mount_nfs called
514 mount_oldnfs be created. The new client is compiled into the
515 kernel with "options NFSCL" and this is needed for diskless root
516 file systems. The GENERIC kernel configs have been changed to use
517 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
518 To use the regular/old client, you can "mount -t oldnfs ...". For
519 a diskless root file system, you must also include a line like:
521 vfs.root.mountfrom="oldnfs:"
523 in the boot/loader.conf on the root fs on the NFS server to make
524 a diskless root fs use the old client.
527 The GENERIC kernels for all architectures now default to the new
528 CAM-based ATA stack. It means that all legacy ATA drivers were
529 removed and replaced by respective CAM drivers. If you are using
530 ATA device names in /etc/fstab or other places, make sure to update
531 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
532 where 'Y's are the sequential numbers starting from zero for each type
533 in order of detection, unless configured otherwise with tunables,
534 see cam(4)). There will be symbolic links created in /dev/ to map
535 old adX devices to the respective adaY. They should provide basic
536 compatibility for file systems mounting in most cases, but they do
537 not support old user-level APIs and do not have respective providers
538 in GEOM. Consider using updated management tools with new device names.
540 It is possible to load devices ahci, ata, siis and mvs as modules,
541 but option ATA_CAM should remain in kernel configuration to make ata
542 module work as CAM driver supporting legacy ATA controllers. Device ata
543 still can be used in modular fashion (atacore + ...). Modules atadisk
544 and atapi* are not used and won't affect operation in ATA_CAM mode.
545 Note that to use CAM-based ATA kernel should include CAM devices
546 scbus, pass, da (or explicitly ada), cd and optionally others. All of
547 them are parts of the cam module.
549 ataraid(4) functionality is now supported by the RAID GEOM class.
550 To use it you can load geom_raid kernel module and use graid(8) tool
551 for management. Instead of /dev/arX device names, use /dev/raid/rX.
553 No kernel config options or code have been removed, so if a problem
554 arises, please report it and optionally revert to the old ATA stack.
555 In order to do it you can remove from the kernel config:
560 , and instead add back:
561 device atadisk # ATA disk drives
562 device ataraid # ATA RAID drives
563 device atapicd # ATAPI CDROM drives
564 device atapifd # ATAPI floppy drives
565 device atapist # ATAPI tape drives
568 The default NFS server has been changed to the new server, which
569 was referred to as the experimental server. If you need to switch
570 back to the old NFS server, you must now put the "-o" option on
571 both the mountd and nfsd commands. This can be done using the
572 mountd_flags and nfs_server_flags rc.conf variables until an
573 update to the rc scripts is committed, which is coming soon.
576 The GNU Objective-C runtime library (libobjc), and other Objective-C
577 related components have been removed from the base system. If you
578 require an Objective-C library, please use one of the available ports.
581 ath(4) has been split into bus- and device- modules. if_ath contains
582 the HAL, the TX rate control and the network device code. if_ath_pci
583 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
584 contains the AHB glue. Users need to load both if_ath_pci and if_ath
585 in order to use ath on everything else.
587 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
588 need to load if_ath and if_ath_pci for ath(4) operation.
591 As part of the replacement of sysinstall, the process of building
592 release media has changed significantly. For details, please re-read
593 release(7), which has been updated to reflect the new build process.
596 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
597 is the last available version under GPLv2. It brings a number of new
598 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
599 4.1 and SSE 4.2), better support for powerpc64, a number of new
600 directives, and lots of other small improvements. See the ChangeLog
601 file in contrib/binutils for the full details.
604 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
605 compliant, and will now use half of hash for authentication.
606 This will break interoperability with all stacks (including all
607 actual FreeBSD versions) who implement
608 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
610 The only workaround with such peers is to use another HMAC
611 algorithm for IPsec ("phase 2") authentication.
614 Remove the uio_yield prototype and symbol. This function has
615 been misnamed since it was introduced and should not be
616 globally exposed with this name. The equivalent functionality
617 is now available using kern_yield(curthread->td_user_pri).
618 The function remains undocumented.
621 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
622 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
623 for scalar sysctls is defined but disabled. Code that needs
624 UQUAD to pass the type checking that must compile on older
625 systems where the define is not present can check against
626 __FreeBSD_version >= 900030.
628 The system dialog(1) has been replaced with a new version previously
629 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
630 with the previous version, but the libdialog associated with it has
631 a largely incompatible API. As such, the original version of libdialog
632 will be kept temporarily as libodialog, until its base system consumers
633 are replaced or updated. Bump __FreeBSD_version to 900030.
636 If you are trying to run make universe on a -stable system, and you get
637 the following warning:
638 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
639 unknown. config(8) likely too old."
640 or something similar to it, then you must upgrade your -stable system
641 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
642 stable/8) or build the config from the latest stable/8 branch and
643 install it on your system.
645 Prior to this date, building a current universe on 8-stable system from
646 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
647 error in the first kernel build phase. A new config on those old
648 systems will fix that problem for older versions of -current.
651 The TCP stack has been modified to allow Khelp modules to interact with
652 it via helper hook points and store per-connection data in the TCP
653 control block. Bump __FreeBSD_version to 900029. User space tools that
654 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
658 Generic IEEE 802.3 annex 31B full duplex flow control support has been
659 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
660 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
661 to take advantage of it instead of using custom implementations. This
662 means that these drivers now no longer unconditionally advertise
663 support for flow control but only do so if flow control is a selected
664 media option. This was implemented in the generic support that way in
665 order to allow flow control to be switched on and off via ifconfig(8)
666 with the PHY specific default to typically off in order to protect
667 from unwanted effects. Consequently, if you used flow control with
668 one of the above mentioned drivers you now need to explicitly enable
670 ifconfig bge0 media auto mediaopt flowcontrol
672 Along with the above mentioned changes generic support for setting
673 1000baseT master mode also has been added and brgphy(4), ciphy(4),
674 e1000phy(4) as well as ip1000phy(4) have been converted to take
675 advantage of it. This means that these drivers now no longer take the
676 link0 parameter for selecting master mode but the master media option
677 has to be used instead, for example like in the following:
678 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
680 Selection of master mode now is also available with all other PHY
681 drivers supporting 1000baseT.
684 The TCP stack has received a significant update to add support for
685 modularised congestion control and generally improve the clarity of
686 congestion control decisions. Bump __FreeBSD_version to 900025. User
687 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
688 sockstat) need to be recompiled.
691 The man(1) utility has been replaced by a new version that no longer
692 uses /etc/manpath.config. Please consult man.conf(5) for how to
693 migrate local entries to the new format.
696 The copyright strings printed by login(1) and sshd(8) at the time of a
697 new connection have been removed to follow other operating systems and
701 A workaround for a fixed ld bug has been removed in kernel code,
702 so make sure that your system ld is built from sources after
703 revision 210245 from 2010-07-19 (r211583 if building head kernel
704 on stable/8, r211584 for stable/7; both from 2010-08-21).
705 A symptom of incorrect ld version is different addresses for
706 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
709 The $ipv6_prefer variable in rc.conf(5) has been split into
710 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
712 The $ip6addrctl_policy is a variable to choose a pre-defined
713 address selection policy set by ip6addrctl(8). A value
714 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
717 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
718 flag (see an entry of 20090926) is set on an interface with no
719 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
720 security reason. If you want IPv6 link-local address on all
721 interfaces by default, set this to "YES".
723 The old ipv6_prefer="YES" is equivalent to
724 ipv6_activate_all_interfaces="YES" and
725 ip6addrctl_policy="ipv6_prefer".
728 DTrace has grown support for userland tracing. Due to this, DTrace is
729 now i386 and amd64 only.
730 dtruss(1) is now installed by default on those systems and a new
731 kernel module is needed for userland tracing: fasttrap.
732 No changes to your kernel config file are necessary to enable
733 userland tracing, but you might consider adding 'STRIP=' and
734 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
735 to have informative userland stack traces in DTrace (ustack).
738 The acpi_aiboost(4) driver has been removed in favor of the new
739 aibs(4) driver. You should update your kernel configuration file.
742 BSD grep has been imported to the base system and it is built by
743 default. It is completely BSD licensed, highly GNU-compatible, uses
744 less memory than its GNU counterpart and has a small codebase.
745 However, it is slower than its GNU counterpart, which is mostly
746 noticeable for larger searches, for smaller ones it is measurable
747 but not significant. The reason is complex, the most important factor
748 is that we lack a modern and efficient regex library and GNU
749 overcomes this by optimizing the searches internally. Future work
750 on improving the regex performance is planned, for the meantime,
751 users that need better performance, can build GNU grep instead by
752 setting the WITH_GNU_GREP knob.
755 Due to the import of powerpc64 support, all existing powerpc kernel
756 configuration files must be updated with a machine directive like this:
757 machine powerpc powerpc
759 In addition, an updated config(8) is required to build powerpc kernels
763 A new version of ZFS (version 15) has been merged to -HEAD.
764 This version uses a python library for the following subcommands:
765 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
766 For full functionality of these commands the following port must
767 be installed: sysutils/py-zfs
770 'vm_page's are now hashed by physical address to an array of mutexes.
771 Currently this is only used to serialize access to hold_count. Over
772 time the page queue mutex will be peeled away. This changes the size
773 of pmap on every architecture. And requires all callers of vm_page_hold
774 and vm_page_unhold to be updated.
777 WITH_CTF can now be specified in src.conf (not recommended, there
778 are some problems with static executables), make.conf (would also
779 affect ports which do not use GNU make and do not override the
780 compile targets) or in the kernel config (via "makeoptions
782 When WITH_CTF was specified there before this was silently ignored,
783 so make sure that WITH_CTF is not used in places which could lead
784 to unwanted behavior.
787 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
788 to allow 32-bit compatibility on non-x86 platforms. All kernel
789 configurations on amd64 and ia64 platforms using these options must
790 be modified accordingly.
793 The utmp user accounting database has been replaced with utmpx,
794 the user accounting interface standardized by POSIX.
795 Unfortunately the semantics of utmp and utmpx don't match,
796 making it practically impossible to support both interfaces.
797 The user accounting database is used by tools like finger(1),
798 last(1), talk(1), w(1) and ac(8).
800 All applications in the base system use utmpx. This means only
801 local binaries (e.g. from the ports tree) may still use these
802 utmp database files. These applications must be rebuilt to make
805 After the system has been upgraded, it is safe to remove the old
806 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
807 assuming their contents is of no importance anymore. Old wtmp
808 databases can only be used by last(1) and ac(8) after they have
809 been converted to the new format using wtmpcvt(1).
812 Introduce the kernel thread "deadlock resolver" (which can be enabled
813 via the DEADLKRES option, see NOTES for more details) and the
814 sleepq_type() function for sleepqueues.
817 The rc.firewall and rc.firewall6 were unified, and
818 rc.firewall6 and rc.d/ip6fw were removed.
819 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
820 variables are obsoleted. Instead, the following new rc
821 variables are added to rc.d/ipfw:
823 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
824 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
825 firewall_simple_onet_ipv6, firewall_trusted_ipv6
827 The meanings correspond to the relevant IPv4 variables.
833 The default terminal emulation for syscons(4) has been changed
834 from cons25 to xterm on all platforms except pc98. This means
835 that the /etc/ttys file needs to be updated to ensure correct
836 operation of applications on the console.
838 The terminal emulation style can be toggled per window by using
839 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
840 options can be used to change the compile-time default back to
843 To prevent graphical artifacts, make sure the TERM environment
844 variable is set to match the terminal emulation that is being
845 performed by syscons(4).
848 The layout of the structure ieee80211req_scan_result has changed.
849 Applications that require wireless scan results (e.g. ifconfig(8))
850 from net80211 need to be recompiled.
852 Applications such as wpa_supplicant(8) may require a full world
853 build without using NO_CLEAN in order to get synchronized with the
857 The iwn(4) driver has been updated to support the 5000 and 5150 series.
858 There's one kernel module for each firmware. Adding "device iwnfw"
859 to the kernel configuration file means including all three firmware
860 images inside the kernel. If you want to include just the one for
861 your wireless card, use the devices iwn4965fw, iwn5000fw or
865 The rc.d/network_ipv6, IPv6 configuration script has been integrated
866 into rc.d/netif. The changes are the following:
868 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
869 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
870 Note that both variables need the "inet6" keyword at the head.
872 Do not set $ipv6_network_interfaces manually if you do not
873 understand what you are doing. It is not needed in most cases.
875 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
878 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
879 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
881 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
882 all configured interfaces have "inet6 accept_rtadv" in the
883 $ifconfig_IF_ipv6. These are for backward compatibility.
885 3. A new variable $ipv6_prefer has been added. If NO, IPv6
886 functionality of interfaces with no corresponding
887 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
888 and the default address selection policy of ip6addrctl(8)
889 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
890 Note that if you want to configure IPv6 functionality on the
891 disabled interfaces after boot, first you need to clear the flag by
892 using ifconfig(8) like:
894 ifconfig em0 inet6 -ifdisabled
896 If YES, the default address selection policy is set as
899 The default value of $ipv6_prefer is NO.
901 4. If your system need to receive Router Advertisement messages,
902 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
903 scripts automatically invoke rtsol(8) when the interface becomes
904 UP. The Router Advertisement messages are used for SLAAC
905 (State-Less Address AutoConfiguration).
908 802.11s D3.03 support was committed. This is incompatible with the
909 previous code, which was based on D3.0.
912 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
913 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
914 control whether accepting Router Advertisement messages or not.
915 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
916 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
917 The ifconfig(8) utility now supports these flags.
920 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
921 mount(8) and -a option for df(1) to see them.
924 The old tunable hw.bus.devctl_disable has been superseded by
925 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
926 replaced by hw.bus.devctl_queue=0. The default for this new tunable
930 Remove the option STOP_NMI. The default action is now to use NMI only
931 for KDB via the newly introduced function stop_cpus_hard() and
932 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
935 The stable/8 branch created in subversion. This corresponds to the
936 RELENG_8 branch in CVS.
939 Bump the shared library version numbers for all libraries that do not
940 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
941 __FreeBSD_version to 800105.
944 Due to changes in the implementation of virtual network stack support,
945 all network-related kernel modules must be recompiled. As this change
946 breaks the ABI, bump __FreeBSD_version to 800104.
949 The TOE interface to the TCP syncache has been modified to remove
950 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
951 The cxgb driver is the only TOE consumer affected by this change, and
952 needs to be recompiled along with the kernel. As this change breaks
953 the ABI, bump __FreeBSD_version to 800103.
956 Padding has been added to struct tcpcb, sackhint and tcpstat in
957 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
958 maintaining the ABI. However, this change breaks the ABI, so bump
959 __FreeBSD_version to 800102. User space tools that rely on the size of
960 any of these structs (e.g. sockstat) need to be recompiled.
963 The NFS_LEGACYRPC option has been removed along with the old kernel
964 RPC implementation that this option selected. Kernel configurations
965 may need to be adjusted.
968 The network interface device nodes at /dev/net/<interface> have been
969 removed. All ioctl operations can be performed the normal way using
970 routing sockets. The kqueue functionality can generally be replaced
971 with routing sockets.
974 The documentation from the FreeBSD Documentation Project (Handbook,
975 FAQ, etc.) is now installed via packages by sysinstall(8) and under
976 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
979 The ABI of various structures related to the SYSV IPC API have been
980 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
981 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
985 Layout of struct vnet has changed as routing related variables were
986 moved to their own Vimage module. Modules need to be recompiled. Bump
987 __FreeBSD_version to 800099.
990 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
991 respectively. As long as no more than 16 groups per process are used,
992 no changes should be visible. When more than 16 groups are used, old
993 binaries may fail if they call getgroups() or getgrouplist() with
994 statically sized storage. Recompiling will work around this, but
995 applications should be modified to use dynamically allocated storage
996 for group arrays as POSIX.1-2008 does not cap an implementation's
997 number of supported groups at NGROUPS_MAX+1 as previous versions did.
999 NFS and portalfs mounts may also be affected as the list of groups is
1000 truncated to 16. Users of NFS who use more than 16 groups, should
1001 take care that negative group permissions are not used on the exported
1002 file systems as they will not be reliable unless a GSSAPI based
1003 authentication method is used.
1006 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1007 option compiles in the support for adaptive spinning for lockmgrs
1008 which want to enable it. The lockinit() function now accepts the flag
1009 LK_ADAPTIVE in order to make the lock object subject to adaptive
1010 spinning when both held in write and read mode.
1013 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1014 changed. User applications that use this ioctl need to be rebuilt.
1017 The layout of struct thread has changed. Kernel and modules need to
1021 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1022 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1025 window(1) has been removed from the base system. It can now be
1026 installed from ports. The port is called misc/window.
1029 The way we are storing and accessing `routing table' entries has
1030 changed. Programs reading the FIB, like netstat, need to be
1034 A new netisr implementation has been added for FreeBSD 8. Network
1035 file system modules, such as igmp, ipdivert, and others, should be
1037 Bump __FreeBSD_version to 800096.
1040 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1044 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1045 Bump __FreeBSD_version to 800094.
1048 Add mnt_xflag field to 'struct mount'. File system modules need to be
1050 Bump __FreeBSD_version to 800093.
1053 The compiling option ADAPTIVE_SX has been retired while it has been
1054 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1055 The KPI for sx_init_flags() changes as accepting flags:
1056 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1057 been introduced in order to handle the reversed logic.
1058 Bump __FreeBSD_version to 800092.
1061 Add support for hierarchical jails. Remove global securelevel.
1062 Bump __FreeBSD_version to 800091.
1065 The layout of struct vnet_net has changed, therefore modules
1067 Bump __FreeBSD_version to 800090.
1070 The newly imported zic(8) produces a new format in the output. Please
1071 run tzsetup(8) to install the newly created data to /etc/localtime.
1074 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1075 hw.usb.* and is now consistent again with previous releases.
1078 802.11 monitor mode support was revised and driver api's were changed.
1079 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1080 of DLT_IEEE802_11. No user-visible data structures were changed but
1081 applications that use DLT_IEEE802_11 may require changes.
1082 Bump __FreeBSD_version to 800088.
1085 The layout of the following structs has changed: sysctl_oid,
1086 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1087 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1088 panics may be experienced. World rebuild is required for
1089 correctly checking networking state from userland.
1090 Bump __FreeBSD_version to 800085.
1093 MLDv2 and Source-Specific Multicast (SSM) have been merged
1094 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1095 The implementation of SSM within FreeBSD's IPv6 stack closely
1096 follows the IPv4 implementation.
1098 For kernel developers:
1100 * The most important changes are that the ip6_output() and
1101 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1102 and this lock has been downgraded to a non-recursive mutex.
1104 * As with the changes to the IPv4 stack to support SSM, filtering
1105 of inbound multicast traffic must now be performed by transport
1106 protocols within the IPv6 stack. This does not apply to TCP and
1107 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1109 * The KPIs used by IPv6 multicast are similar to those used by
1110 the IPv4 stack, with the following differences:
1111 * im6o_mc_filter() is analogous to imo_multicast_filter().
1112 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1113 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1114 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1115 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1116 for MLDv1 have an additional 'timer' argument which is used to
1117 jitter the initial membership report for the solicited-node
1118 multicast membership on-link.
1119 * This is not strictly needed for MLDv2, which already jitters
1120 its report transmissions. However, the 'timer' argument is
1121 preserved in case MLDv1 is active on the interface.
1123 * The KAME linked-list based IPv6 membership implementation has
1124 been refactored to use a vector similar to that used by the IPv4
1126 Code which maintains a list of its own multicast memberships
1127 internally, e.g. carp, has been updated to reflect the new
1130 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1131 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1132 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1133 implementation constraint which needs to be addressed in HEAD.
1135 For application developers:
1137 * The changes are broadly similar to those made for the IPv4
1140 * The use of IPv4 and IPv6 multicast socket options on the same
1141 socket, using mapped addresses, HAS NOT been tested or supported.
1143 * There are a number of issues with the implementation of various
1144 IPv6 multicast APIs which need to be resolved in the API surface
1145 before the implementation is fully compatible with KAME userland
1146 use, and these are mostly to do with interface index treatment.
1148 * The literature available discusses the use of either the delta / ASM
1149 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1150 using setsourcefilter(3)/getsourcefilter(3). For more information
1151 please refer to RFC 3768, 'Socket Interface Extensions for
1152 Multicast Source Filters'.
1154 * Applications which use the published RFC 3678 APIs should be fine.
1156 For systems administrators:
1158 * The mtest(8) utility has been refactored to support IPv6, in
1159 addition to IPv4. Interface addresses are no longer accepted
1160 as arguments, their names must be used instead. The utility
1161 will map the interface name to its first IPv4 address as
1162 returned by getifaddrs(3).
1164 * The ifmcstat(8) utility has also been updated to print the MLDv2
1165 endpoint state and source filter lists via sysctl(3).
1167 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1168 loopback of IPv6 multicast datagrams by default; it defaults to 1
1169 to preserve the existing behaviour. Disabling multicast loopback is
1170 recommended for optimal system performance.
1172 * The IPv6 MROUTING code has been changed to examine this sysctl
1173 instead of attempting to perform a group lookup before looping
1174 back forwarded datagrams.
1176 Bump __FreeBSD_version to 800084.
1179 Implement low-level Bluetooth HCI API.
1180 Bump __FreeBSD_version to 800083.
1183 The layout of struct malloc_type, used by modules to register new
1184 memory allocation types, has changed. Most modules will need to
1185 be rebuilt or panics may be experienced.
1186 Bump __FreeBSD_version to 800081.
1189 Anticipate overflowing inp_flags - add inp_flags2.
1190 This changes most offsets in inpcb, so checking v4 connection
1191 state will require a world rebuild.
1192 Bump __FreeBSD_version to 800080.
1195 Add an llentry to struct route and struct route_in6. Modules
1196 embedding a struct route will need to be recompiled.
1197 Bump __FreeBSD_version to 800079.
1200 The size of rt_metrics_lite and by extension rtentry has changed.
1201 Networking administration apps will need to be recompiled.
1202 The route command now supports show as an alias for get, weighting
1203 of routes, sticky and nostick flags to alter the behavior of stateful
1205 Bump __FreeBSD_version to 800078.
1208 Do not use Giant for kbdmux(4) locking. This is wrong and
1209 apparently causing more problems than it solves. This will
1210 re-open the issue where interrupt handlers may race with
1211 kbdmux(4) in polling mode. Typical symptoms include (but
1212 not limited to) duplicated and/or missing characters when
1213 low level console functions (such as gets) are used while
1214 interrupts are enabled (for example geli password prompt,
1215 mountroot prompt etc.). Disabling kbdmux(4) may help.
1218 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1219 kernel modules referencing any of the above need to be recompiled.
1220 Bump __FreeBSD_version to 800075.
1223 GEOM_PART has become the default partition slicer for storage devices,
1224 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1225 introduces some changes:
1227 MSDOS/EBR: the devices created from MSDOS extended partition entries
1228 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1229 to devices with offset-based names. fstabs may need to be modified.
1231 BSD: the "geometry does not match label" warning is harmless in most
1232 cases but it points to problems in file system misalignment with
1233 disk geometry. The "c" partition is now implicit, covers the whole
1234 top-level drive and cannot be (mis)used by users.
1236 General: Kernel dumps are now not allowed to be written to devices
1237 whose partition types indicate they are meant to be used for file
1238 systems (or, in case of MSDOS partitions, as something else than
1241 Most of these changes date approximately from 200812.
1244 The uscanner(4) driver has been removed from the kernel. This follows
1245 Linux removing theirs in 2.6 and making libusb the default interface
1246 (supported by sane).
1249 The multicast forwarding code has been cleaned up. netstat(1)
1250 only relies on KVM now for printing bandwidth upcall meters.
1251 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1252 ip6_mroute_mod respectively. The config(5) options for statically
1253 compiling this code remain the same, i.e. 'options MROUTING'.
1256 Support for the IFF_NEEDSGIANT network interface flag has been
1257 removed, which means that non-MPSAFE network device drivers are no
1258 longer supported. In particular, if_ar, if_sr, and network device
1259 drivers from the old (legacy) USB stack can no longer be built or
1263 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1264 a bunch of new language catalog files have also been added.
1265 This means that some common libc messages are now localized and
1266 they depend on the LC_MESSAGES environmental variable.
1269 The k8temp(4) driver has been renamed to amdtemp(4) since
1270 support for Family 10 and Family 11 CPU families was added.
1273 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1274 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1276 For kernel developers, the most important changes are that the
1277 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1278 and this lock has been downgraded to a non-recursive mutex.
1280 Transport protocols (UDP, Raw IP) are now responsible for filtering
1281 inbound multicast traffic according to group membership and source
1282 filters. The imo_multicast_filter() KPI exists for this purpose.
1283 Transports which do not use multicast (SCTP, TCP) already reject
1284 multicast by default. Forwarding and receive performance may improve
1285 as a mutex acquisition is no longer needed in the ip_input()
1286 low-level input path. in_addmulti() and in_delmulti() are shimmed
1287 to new KPIs which exist to support SSM in-kernel.
1289 For application developers, it is recommended that loopback of
1290 multicast datagrams be disabled for best performance, as this
1291 will still cause the lock to be taken for each looped-back
1292 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1293 be tuned to 0 to disable loopback by default; it defaults to 1
1294 to preserve the existing behaviour.
1296 For systems administrators, to obtain best performance with
1297 multicast reception and multiple groups, it is always recommended
1298 that a card with a suitably precise hash filter is used. Hash
1299 collisions will still result in the lock being taken within the
1300 transport protocol input path to check group membership.
1302 If deploying FreeBSD in an environment with IGMP snooping switches,
1303 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1304 enabled; this forces 224.0.0.0/24 group membership to be announced
1307 The size of 'struct igmpstat' has changed; netstat needs to be
1308 recompiled to reflect this.
1309 Bump __FreeBSD_version to 800070.
1312 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1313 updated to use it. This requires a buildworld/installworld in order to
1314 update the library and dependencies (usbconfig, etc). Its advisable to
1315 rebuild all ports which uses libusb. More specific directions are given
1316 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1317 libusb are no longer required and can be removed.
1320 A workaround is committed to allow the creation of System V shared
1321 memory segment of size > 2 GB on the 64-bit architectures.
1322 Due to a limitation of the existing ABI, the shm_segsz member
1323 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1324 wrong for large segments. Note that limits must be explicitly
1325 raised to allow such segments to be created.
1328 The layout of struct ifnet has changed, requiring a rebuild of all
1329 network device driver modules.
1332 The /dev handling for the new USB stack has changed, a
1333 buildworld/installworld is required for libusb20.
1336 The new USB2 stack has now been permanently moved in and all kernel and
1337 module names reverted to their previous values (eg, usb, ehci, ohci,
1338 ums, ...). The old usb stack can be compiled in by prefixing the name
1339 with the letter 'o', the old usb modules have been removed.
1340 Updating entry 20090216 for xorg and 20090215 for libmap may still
1344 The rc.conf(5) option if_up_delay has been renamed to
1345 defaultroute_delay to better reflect its purpose. If you have
1346 customized this setting in /etc/rc.conf you need to update it to
1350 xorg 7.4 wants to configure its input devices via hald which does not
1351 yet work with USB2. If the keyboard/mouse does not work in xorg then
1353 Option "AllowEmptyInput" "off"
1354 to your ServerLayout section. This will cause X to use the configured
1355 kbd and mouse sections from your xorg.conf.
1358 The GENERIC kernels for all architectures now default to the new USB2
1359 stack. No kernel config options or code have been removed so if a
1360 problem arises please report it and optionally revert to the old USB
1361 stack. If you are loading USB kernel modules or have a custom kernel
1362 that includes GENERIC then ensure that usb names are also changed over,
1363 eg uftdi -> usb2_serial_ftdi.
1365 Older programs linked against the ports libusb 0.1 need to be
1366 redirected to the new stack's libusb20. /etc/libmap.conf can
1368 # Map old usb library to new one for usb2 stack
1369 libusb-0.1.so.8 libusb20.so.1
1372 All USB ethernet devices now attach as interfaces under the name ueN
1373 (eg. ue0). This is to provide a predictable name as vendors often
1374 change usb chipsets in a product without notice.
1377 The ichsmb(4) driver has been changed to require SMBus slave
1378 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1379 All of the other SMBus controller drivers require left-justified
1380 slave addresses, so this change makes all the drivers provide the
1384 INET6 statistics (struct ip6stat) was updated.
1385 netstat(1) needs to be recompiled.
1388 NTFS has been removed from GENERIC kernel on amd64 to match
1389 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1390 will load ntfs.ko module automatically when NTFS support is
1391 actually needed, unless ntfs.ko is not installed or security
1392 level prohibits loading kernel modules. If either is the case,
1393 "options NTFS" has to be added into kernel config.
1396 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1397 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1398 800061. User space tools that rely on the size of struct tcpcb in
1399 tcp_var.h (e.g. sockstat) need to be recompiled.
1402 ng_tty(4) module updated to match the new TTY subsystem.
1403 Due to API change, user-level applications must be updated.
1404 New API support added to mpd5 CVS and expected to be present
1405 in next mpd5.3 release.
1408 With __FreeBSD_version 800060 the makefs tool is part of
1409 the base system (it was a port).
1412 The afdata and ifnet locks have been changed from mutexes to
1413 rwlocks, network modules will need to be re-compiled.
1416 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1417 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1418 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1419 architecture and 40 bytes on 64-bit architecture. The userland
1420 applications "arp" and "ndp" have been updated accordingly.
1421 The output from "netstat -r" shows only routing entries and
1422 none of the L2 information.
1425 __FreeBSD_version 800057 marks the switchover from the
1426 binary ath hal to source code. Users must add the line:
1428 options AH_SUPPORT_AR5416
1430 to their kernel config files when specifying:
1434 The ath_hal module no longer exists; the code is now compiled
1435 together with the driver in the ath module. It is now
1436 possible to tailor chip support (i.e. reduce the set of chips
1437 and thereby the code size); consult ath_hal(4) for details.
1440 __FreeBSD_version 800054 adds memory barriers to
1441 <machine/atomic.h>, new interfaces to ifnet to facilitate
1442 multiple hardware transmit queues for cards that support
1443 them, and a lock-less ring-buffer implementation to
1444 enable drivers to more efficiently manage queueing of
1448 A new version of ZFS (version 13) has been merged to -HEAD.
1449 This version has zpool attribute "listsnapshots" off by
1450 default, which means "zfs list" does not show snapshots,
1451 and is the same as Solaris behavior.
1454 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1457 The uhci, ohci, ehci and slhci USB Host controller drivers have
1458 been put into separate modules. If you load the usb module
1459 separately through loader.conf you will need to load the
1460 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1461 controller add the following to loader.conf:
1467 The ABI used by the PMC toolset has changed. Please keep
1468 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1472 atapci kernel module now includes only generic PCI ATA
1473 driver. AHCI driver moved to ataahci kernel module.
1474 All vendor-specific code moved into separate kernel modules:
1475 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1476 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1477 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1478 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1481 The TTY subsystem of the kernel has been replaced by a new
1482 implementation, which provides better scalability and an
1483 improved driver model. Most common drivers have been migrated to
1484 the new TTY subsystem, while others have not. The following
1485 drivers have not yet been ported to the new TTY layer:
1488 cy, digi, rc, rp, sio
1494 ng_h4, ng_tty, ppp, sl, snp
1496 Adding these drivers to your kernel configuration file shall
1497 cause compilation to fail.
1500 ntpd has been upgraded to 4.2.4p5.
1503 OpenSSH has been upgraded to 5.1p1.
1505 For many years, FreeBSD's version of OpenSSH preferred DSA
1506 over RSA for host and user authentication keys. With this
1507 upgrade, we've switched to the vendor's default of RSA over
1508 DSA. This may cause upgraded clients to warn about unknown
1509 host keys even for previously known hosts. Users should
1510 follow the usual procedure for verifying host keys before
1511 accepting the RSA key.
1513 This can be circumvented by setting the "HostKeyAlgorithms"
1514 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1517 Please note that the sequence of keys offered for
1518 authentication has been changed as well. You may want to
1519 specify IdentityFile in a different order to revert this
1523 The sio(4) driver has been removed from the i386 and amd64
1524 kernel configuration files. This means uart(4) is now the
1525 default serial port driver on those platforms as well.
1527 To prevent collisions with the sio(4) driver, the uart(4) driver
1528 uses different names for its device nodes. This means the
1529 onboard serial port will now most likely be called "ttyu0"
1530 instead of "ttyd0". You may need to reconfigure applications to
1531 use the new device names.
1533 When using the serial port as a boot console, be sure to update
1534 /boot/device.hints and /etc/ttys before booting the new kernel.
1535 If you forget to do so, you can still manually specify the hints
1536 at the loader prompt:
1538 set hint.uart.0.at="isa"
1539 set hint.uart.0.port="0x3F8"
1540 set hint.uart.0.flags="0x10"
1541 set hint.uart.0.irq="4"
1545 The gpt(8) utility has been removed. Use gpart(8) to partition
1549 The version that Linuxulator emulates was changed from 2.4.2
1550 to 2.6.16. If you experience any problems with Linux binaries
1551 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1552 if it fixes the problem contact emulation mailing list.
1555 ISDN4BSD (I4B) was removed from the src tree. You may need to
1556 update a your kernel configuration and remove relevant entries.
1559 I have checked in code to support multiple routing tables.
1560 See the man pages setfib(1) and setfib(2).
1561 This is a hopefully backwards compatible version,
1562 but to make use of it you need to compile your kernel
1563 with options ROUTETABLES=2 (or more up to 16).
1566 The 802.11 wireless support was redone to enable multi-bss
1567 operation on devices that are capable. The underlying device
1568 is no longer used directly but instead wlanX devices are
1569 cloned with ifconfig. This requires changes to rc.conf files.
1570 For example, change:
1571 ifconfig_ath0="WPA DHCP"
1574 ifconfig_wlan0="WPA DHCP"
1575 see rc.conf(5) for more details. In addition, mergemaster of
1576 /etc/rc.d is highly recommended. Simultaneous update of userland
1577 and kernel wouldn't hurt either.
1579 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1580 modules were merged into the base wlan module. All references
1581 to these modules (e.g. in kernel config files) must be removed.
1584 psm(4) has gained write(2) support in native operation level.
1585 Arbitrary commands can be written to /dev/psm%d and status can
1586 be read back from it. Therefore, an application is responsible
1587 for status validation and error recovery. It is a no-op in
1588 other operation levels.
1591 Support for KSE threading has been removed from the kernel. To
1592 run legacy applications linked against KSE libmap.conf may
1593 be used. The following libmap.conf may be used to ensure
1594 compatibility with any prior release:
1596 libpthread.so.1 libthr.so.1
1597 libpthread.so.2 libthr.so.2
1598 libkse.so.3 libthr.so.3
1601 The layout of struct vmspace has changed. This affects libkvm
1602 and any executables that link against libkvm and use the
1603 kvm_getprocs() function. In particular, but not exclusively,
1604 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1605 The effects are minimal, but it's advisable to upgrade world
1609 The latest em driver no longer has support in it for the
1610 82575 adapter, this is now moved to the igb driver. The
1611 split was done to make new features that are incompatible
1612 with older hardware easier to do.
1615 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1616 likewise the kernel option is now GEOM_LINUX_LVM.
1619 The default NFS mount mode has changed from UDP to TCP for
1620 increased reliability. If you rely on (insecurely) NFS
1621 mounting across a firewall you may need to update your
1625 Belatedly note the addition of m_collapse for compacting
1629 The fts(3) structures have been changed to use adequate
1630 integer types for their members and so to be able to cope
1631 with huge file trees. The old fts(3) ABI is preserved
1632 through symbol versioning in libc, so third-party binaries
1633 using fts(3) should still work, although they will not take
1634 advantage of the extended types. At the same time, some
1635 third-party software might fail to build after this change
1636 due to unportable assumptions made in its source code about
1637 fts(3) structure members. Such software should be fixed
1638 by its vendor or, in the worst case, in the ports tree.
1639 FreeBSD_version 800015 marks this change for the unlikely
1640 case that a portable fix is impossible.
1643 To upgrade to -current after this date, you must be running
1644 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1645 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1648 The ADAPTIVE_GIANT kernel option has been retired because its
1649 functionality is the default now.
1652 The AT keyboard emulation of sunkbd(4) has been turned on
1653 by default. In order to make the special symbols of the Sun
1654 keyboards driven by sunkbd(4) work under X these now have
1655 to be configured the same way as Sun USB keyboards driven
1656 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1658 Option "XkbLayout" "us"
1659 Option "XkbRules" "xorg"
1660 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1663 It has been decided that it is desirable to provide ABI
1664 backwards compatibility to the FreeBSD 4/5/6 versions of the
1665 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1666 broken with the introduction of PCI domain support (see the
1667 20070930 entry). Unfortunately, this required the ABI of
1668 PCIOCGETCONF to be broken again in order to be able to
1669 provide backwards compatibility to the old version of that
1670 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1671 again. As for prominent ports this affects neither pciutils
1672 nor xorg-server this time, the hal port needs to be rebuilt
1676 The misnamed kthread_create() and friends have been renamed
1677 to kproc_create() etc. Many of the callers already
1678 used kproc_start()..
1679 I will return kthread_create() and friends in a while
1680 with implementations that actually create threads, not procs.
1681 Renaming corresponds with version 800002.
1690 Avoid using make -j when upgrading. While generally safe, there are
1691 sometimes problems using -j to upgrade. If your upgrade fails with
1692 -j, please try again without -j. From time to time in the past there
1693 have been problems using -j with buildworld and/or installworld. This
1694 is especially true when upgrading between "distant" versions (eg one
1695 that cross a major release boundary or several minor releases, or when
1696 several months have passed on the -current branch).
1698 Sometimes, obscure build problems are the result of environment
1699 poisoning. This can happen because the make utility reads its
1700 environment when searching for values for global variables. To run
1701 your build attempts in an "environmental clean room", prefix all make
1702 commands with 'env -i '. See the env(1) manual page for more details.
1704 When upgrading from one major version to another it is generally best
1705 to upgrade to the latest code in the currently installed branch first,
1706 then do an upgrade to the new branch. This is the best-tested upgrade
1707 path, and has the highest probability of being successful. Please try
1708 this approach before reporting problems with a major version upgrade.
1712 When upgrading the boot ZFS pool to a new version, always follow
1715 1.) recompile and reinstall the ZFS boot loader and boot block
1716 (this is part of "make buildworld" and "make installworld")
1718 2.) update the ZFS boot block on your boot drive
1720 The following example updates the ZFS boot block on the first
1721 partition (freebsd-boot) of a GPT partitioned drive ad0:
1722 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1724 Non-boot pools do not need these updates.
1728 If you are updating from a prior version of FreeBSD (even one just
1729 a few days old), you should follow this procedure. It is the most
1730 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1732 make kernel-toolchain
1733 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1734 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1736 To test a kernel once
1737 ---------------------
1738 If you just want to boot a kernel once (because you are not sure
1739 if it works, or if you want to boot a known bad kernel to provide
1740 debugging information) run
1741 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1742 nextboot -k testkernel
1744 To just build a kernel when you know that it won't mess you up
1745 --------------------------------------------------------------
1746 This assumes you are already running a CURRENT system. Replace
1747 ${arch} with the architecture of your machine (e.g. "i386",
1748 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1750 cd src/sys/${arch}/conf
1751 config KERNEL_NAME_HERE
1752 cd ../compile/KERNEL_NAME_HERE
1757 If this fails, go to the "To build a kernel" section.
1759 To rebuild everything and install it on the current system.
1760 -----------------------------------------------------------
1761 # Note: sometimes if you are running current you gotta do more than
1762 # is listed here if you are upgrading from a really old current.
1764 <make sure you have good level 0 dumps>
1766 make kernel KERNCONF=YOUR_KERNEL_HERE
1768 <reboot in single user> [3]
1776 To cross-install current onto a separate partition
1777 --------------------------------------------------
1778 # In this approach we use a separate partition to hold
1779 # current's root, 'usr', and 'var' directories. A partition
1780 # holding "/", "/usr" and "/var" should be about 2GB in
1783 <make sure you have good level 0 dumps>
1786 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1787 <maybe newfs current's root partition>
1788 <mount current's root partition on directory ${CURRENT_ROOT}>
1789 make installworld DESTDIR=${CURRENT_ROOT}
1790 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1791 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1792 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1793 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1794 <reboot into current>
1795 <do a "native" rebuild/install as described in the previous section>
1796 <maybe install compatibility libraries from ports/misc/compat*>
1800 To upgrade in-place from stable to current
1801 ----------------------------------------------
1802 <make sure you have good level 0 dumps>
1804 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1806 <reboot in single user> [3]
1813 Make sure that you've read the UPDATING file to understand the
1814 tweaks to various things you need. At this point in the life
1815 cycle of current, things change often and you are on your own
1816 to cope. The defaults can also change, so please read ALL of
1817 the UPDATING entries.
1819 Also, if you are tracking -current, you must be subscribed to
1820 freebsd-current@freebsd.org. Make sure that before you update
1821 your sources that you have read and understood all the recent
1822 messages there. If in doubt, please track -stable which has
1823 much fewer pitfalls.
1825 [1] If you have third party modules, such as vmware, you
1826 should disable them at this point so they don't crash your
1829 [3] From the bootblocks, boot -s, and then do
1834 adjkerntz -i # if CMOS is wall time
1835 Also, when doing a major release upgrade, it is required that
1836 you boot into single user mode to do the installworld.
1838 [4] Note: This step is non-optional. Failure to do this step
1839 can result in a significant reduction in the functionality of the
1840 system. Attempting to do it by hand is not recommended and those
1841 that pursue this avenue should read this file carefully, as well
1842 as the archives of freebsd-current and freebsd-hackers mailing lists
1843 for potential gotchas. The -U option is also useful to consider.
1844 See mergemaster(8) for more information.
1846 [5] Usually this step is a noop. However, from time to time
1847 you may need to do this if you get unknown user in the following
1848 step. It never hurts to do it all the time. You may need to
1849 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1850 install) after the buildworld before this step if you last updated
1851 from [78]-stable or 9-stable before 20130430.
1853 [6] This only deletes old files and directories. Old libraries
1854 can be deleted by "make delete-old-libs", but you have to make
1855 sure that no program is using those libraries anymore.
1857 [8] In order to have a kernel that can run the 4.x binaries needed to
1858 do an installworld, you must include the COMPAT_FREEBSD4 option in
1859 your kernel. Failure to do so may leave you with a system that is
1860 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1861 required to run the 5.x binaries on more recent kernels. And so on
1862 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1864 Make sure that you merge any new devices from GENERIC since the
1865 last time you updated your kernel config file.
1867 [9] When checking out sources, you must include the -P flag to have
1868 cvs prune empty directories.
1870 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1871 "?=" instead of the "=" assignment operator, so that buildworld can
1872 override the CPUTYPE if it needs to.
1874 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1875 not on the command line, or in /etc/make.conf. buildworld will
1876 warn if it is improperly defined.
1879 This file contains a list, in reverse chronological order, of major
1880 breakages in tracking -current. It is not guaranteed to be a complete
1881 list of such breakages, and only contains entries since October 10, 2007.
1882 If you need to see UPDATING entries from before that date, you will need
1883 to fetch an UPDATING file from an older FreeBSD release.
1885 Copyright information:
1887 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1889 Redistribution, publication, translation and use, with or without
1890 modification, in full or in part, in any form or format of this
1891 document are permitted without further permission from the author.
1893 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1894 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1895 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1896 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1897 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1898 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1899 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1900 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1901 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1902 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1903 POSSIBILITY OF SUCH DAMAGE.
1905 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / releng / 9.3.git / blob