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 20160130 p36 FreeBSD-SA-16:11.openssl
16 Fix OpenSSL SSLv2 ciphersuite downgrade vulnerability. [SA-16:11]
18 20160127 p35 FreeBSD-SA-16:08.bind
20 FreeBSD-SA-16:10.linux
22 Fix BIND remote denial of service vulnerability. [SA-16:08]
24 Fix multiple vulnerabilities of ntp. [SA-16:09]
26 Fix Linux compatibility layer issetugid(2) system call
27 vulnerability. [SA-16:10]
29 20160114 p34 FreeBSD-SA-16:07.openssh
31 Fix OpenSSH client information leak. [SA-16:07]
33 20160114 p33 FreeBSD-EN-16:02.pf
34 FreeBSD-EN-16:03.yplib
37 FreeBSD-SA-16:03.linux
38 FreeBSD-SA-16:04.linux
40 FreeBSD-SA-16:06.bsnmpd
42 Fix pf(4) generating bad TCP checksums. [EN-16:02]
43 Fix infinite loop in YP/NIS client library. [EN-16:03]
44 Fix remote denial of service in SCTP. [SA-16:01]
45 Update NTP to 4.2.8p5. [SA-16:02]
46 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
47 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
48 Fix crash in TCP MD5 signatures. [SA-16:05]
49 Fix insecure default permissions for snmpd.config. [SA-16:06]
51 20151216 p32 FreeBSD-SA-15:27.bind
52 Fix BIND remote denial of service vulnerability. [SA-15:27]
54 20151205 p31 FreeBSD-SA-15:26.openssl
56 Fix OpenSSL X509_ATTRIBUTE memory leak. [SA-15:26]
58 20151104 p30 FreeBSD-SA-15:25.ntp [revised]
59 FreeBSD-EN-15:19.kqueue
62 Fix regression of ntpq(8) utility exiting due to trap 6 in
63 9.3-RELEASE-p29. [SA-15:25]
65 Fix regression in ntpd(8) lacking support for RAWDCF reference
66 clock in 9.3-RELEASE-p29. [SA-15:25]
68 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
70 Fix applications exiting due to segmentation violation on a correct
71 memory address. [EN-15:20]
73 20151026: p29 FreeBSD-SA-15:25.ntp
75 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
77 The configuration file syntax has been changed, thus mergemaster
78 run is recommended. Now the "kod" parameter requires "limited"
79 parameter. If the ntp.conf is not updated, the ntpd will run
80 successfully, but with KoD disabled.
82 20151002: p28 FreeBSD-SA-15:24.rpcbind [revised]
83 Revised patch to address a regression that prevents NIS from working.
85 20150929: p27 FreeBSD-SA-15:24.rpcbind
87 Fix rpcbind(8) remote denial of service. [SA-15:24]
89 20150916: p26 FreeBSD-EN-15:18.pkg
91 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
93 20150902: p25 FreeBSD-SA-15:23.bind
95 Fix BIND remote denial of service vulnerability. [SA-15:23]
97 20150825: p24 FreeBSD-SA-15:21.amd64
98 FreeBSD-SA-15:22.openssh
101 Fix local privilege escalation in IRET handler. [SA-15:21]
103 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
105 Fix insufficient check of unsupported pkg(7) signature methods.
108 20150818: p23 FreeBSD-SA-15:20.expat
110 Fix multiple integer overflows in expat (libbsdxml) XML parser.
113 20150805: p22 FreeBSD-SA-15:19.routed
115 Fix routed remote denial of service vulnerability.
117 20150728: p21 FreeBSD-SA-15:15.tcp
118 FreeBSD-SA-15:16.openssh
119 FreeBSD-SA-15:17.bind
121 Fix resource exhaustion in TCP reassembly. [SA-15:15]
123 Fix OpenSSH multiple vulnerabilities. [SA-15:16]
125 Fix BIND remote denial of service vulnerability. [SA-15:17]
127 20150721: p20 FreeBSD-SA-15:13.tcp
129 Fix resource exhaustion due to sessions stuck in LAST_ACK state.
132 20150707: p19 FreeBSD-SA-15:11.bind
133 Fix BIND resolver remote denial of service when validating.
135 20150630: p18 FreeBSD-EN-15:08.sendmail [revised]
136 FreeBSD-EN-15:09.xlocale
138 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
140 Fix inconsistency between locale and rune locale states.
143 20150618: p17 FreeBSD-EN-15:08.sendmail
144 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
146 20150612: p16 FreeBSD-SA-15:10.openssl
147 Fix multiple vulnerabilities in OpenSSL. [SA-15:10]
149 20150609: p15 FreeBSD-EN-15:06.file
151 Updated base system file(1) to 5.22 to address multiple denial
154 20150513: p14 FreeBSD-EN-15:04.freebsd-update
156 Fix bug with freebsd-update(8) that does not ensure the previous
157 upgrade was completed. [EN-15:04]
159 20150407: p13 FreeBSD-SA-15:04.igmp [revised]
161 FreeBSD-SA-15:09.ipv6
163 Improved patch for SA-15:04.igmp.
165 Fix multiple vulnerabilities of ntp. [SA-15:07]
167 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
170 Fix patch for SA-15:06.openssl.
172 20150319: p11 FreeBSD-SA-15:06.openssl
173 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
175 20150225: p10 FreeBSD-SA-15:04.igmp
176 FreeBSD-SA-15:05.bind
178 FreeBSD-EN-15:02.openssl
179 FreeBSD-EN-15:03.freebsd-update
181 Fix integer overflow in IGMP protocol. [SA-15:04]
183 Fix BIND remote denial of service vulnerability. [SA-15:05]
185 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
187 Updated base system OpenSSL to 0.9.8zd. [EN-15:02]
189 Fix freebsd-update libraries update ordering issue. [EN-15:03]
191 20150127: p9 FreeBSD-SA-15:02.kmem
192 FreeBSD-SA-15:03.sctp
194 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
195 vulnerability. [SA-15:02]
197 Fix SCTP stream reset vulnerability. [SA-15:03]
199 20150114: p8 FreeBSD-SA-15:01.openssl
200 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
202 20141223: p7 FreeBSD-SA-14:31.ntp
203 FreeBSD-EN-14:13.freebsd-update
205 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
206 Fix directory deletion issue in freebsd-update. [EN-14:13]
208 20141210: p6 FreeBSD-SA-14:28.file
209 FreeBSD-SA-14:29.bind
211 Fix multiple vulnerabilities in file(1) and libmagic(3).
214 Fix BIND remote denial of service vulnerability. [SA-14:29]
216 20141104: p5 FreeBSD-SA-14:25.setlogin
220 Fix kernel stack disclosure in setlogin(2) / getlogin(2).
223 Fix remote command execution in ftp(1). [SA-14:26]
225 Fix NFSv4 and ZFS cache consistency issue. [EN-14:12]
227 20141022: p4 FreeBSD-EN-14:10.tzdata
228 FreeBSD-EN-14:11.crypt
230 Time zone data file update. [EN-14:10]
232 Change crypt(3) default hashing algorithm back to DES. [EN-14:11]
234 20141021: p3 FreeBSD-SA-14:20.rtsold
235 FreeBSD-SA-14:21.routed
236 FreeBSD-SA-14:22.namei
237 FreeBSD-SA-14:23.openssl
239 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
241 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
243 Fix memory leak in sandboxed namei lookup. [SA-14:22]
245 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
247 20140916: p2 FreeBSD-SA-14:19.tcp
248 Fix Denial of Service in TCP packet processing. [SA-14:19]
250 20140909: p1 FreeBSD-SA-14:18.openssl
251 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
257 On i386 and amd64 systems, the onifconsole flag is now set by default
258 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
259 as a login TTY if it is set in the bootloader as an active kernel
260 console. No changes in behavior should result otherwise. To revert to
261 the previous behavior, set ttyu0 to "off" in /etc/ttys.
264 Clang and llvm have been upgraded to 3.4.1 release.
267 Clang and llvm have been upgraded to 3.4 release.
270 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
271 been deprecated and will not be part of FreeBSD 11.0 and later
272 releases. If you use this driver, please consider switching to
273 the nfe(4) driver instead.
276 The behavior of gss_pseudo_random() for the krb5 mechanism
277 has changed, for applications requesting a longer random string
278 than produced by the underlying enctype's pseudo-random() function.
279 In particular, the random string produced from a session key of
280 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
281 be different at the 17th octet and later, after this change.
282 The counter used in the PRF+ construction is now encoded as a
283 big-endian integer in accordance with RFC 4402.
284 __FreeBSD_version is bumped to 902505.
290 Behavior of devfs rules path matching has been changed.
291 Pattern is now always matched against fully qualified devfs
292 path and slash characters must be explicitly matched by
293 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
294 subdirectories must be reviewed.
297 hastctl(8)'s `status' command output changed to terse one-liner format.
298 Scripts using this should switch to `list' command or be rewritten.
301 Fix a bug that allowed a tracing process (e.g. gdb) to write
302 to a memory-mapped file in the traced process's address space
303 even if neither the traced process nor the tracing process had
304 write access to that file.
307 Added ZFS TRIM support which is enabled by default. To disable
308 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
310 Creating new ZFS pools and adding new devices to existing pools
311 first performs a full device level TRIM which can take a significant
312 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
313 to disable this behaviour.
315 ZFS TRIM requires the underlying device support BIO_DELETE which
316 is currently provided by methods such as ATA TRIM and SCSI UNMAP
317 via CAM, which are typically supported by SSD's.
319 Stats for ZFS TRIM can be monitored by looking at the sysctl's
320 under kstat.zfs.misc.zio_trim.
323 `list' command has been added to hastctl(8). For now, it is full
324 equivalent of `status' command.
325 WARNING: in the near future the output of hastctl's status command
326 will change to more terse format. If you use `hastctl status'
327 for parsing in your scripts, switch to `hastctl list'.
330 The mergemaster command now uses the default MAKEOBJDIRPREFIX
331 rather than creating it's own in the temporary directory in
332 order allow access to bootstrapped versions of tools such as
333 install and mtree. When upgrading from version of FreeBSD where
334 the install command does not support -l, you will need to
335 install a new mergemaster command if mergemaster -p is required.
336 This can be accomplished with the command (cd src/usr.sbin/mergemaster
339 Due to the use of the new -l option to install(1) during build
340 and install, you must take care not to directly set the INSTALL
341 make variable in your /etc/make.conf, /etc/src.conf, or on the
342 command line. If you wish to use the -C flag for all installs
343 you may be able to add INSTALL+=-C to /etc/make.conf or
347 Fix a bug that allows NFS clients to issue READDIR on files.
350 The install(1) option -M has changed meaning and now takes an
351 argument that is a file or path to append logs to. In the
352 unlikely event that -M was the last option on the command line
353 and the command line contained at least two files and a target
354 directory the first file will have logs appended to it. The -M
355 option served little practical purpose in the last decade so it's
356 used expected to be extremely rare.
359 A new compression method (lz4) has been merged to. Please refer to
360 zpool-features(7) for more information.
362 Please refer to the "ZFS notes" section of this file for information
363 on upgrading boot ZFS pools.
366 The VFS KBI was changed with the merge of several nullfs
367 optimizations and fixes. All filesystem modules must be
371 With the addition of auditdistd(8), a new auditdistd user is now
372 depended on during installworld. "mergemaster -p" can be used to add
373 the user prior to installworld, as documented in the handbook.
379 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
380 Starting with this version the old system of ZFS pool versioning
381 is superseded by "feature flags". This concept enables forward
382 compatibility against certain future changes in functionality of ZFS
383 pools. The first two read-only compatible "feature flags" for ZFS
384 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
385 For more information read the new zpool-features(7) manual page.
386 Please refer to the "ZFS notes" section of this file for information
387 on upgrading boot ZFS pools.
390 The commit introducing bsd.compiler.mk breaks the traditional
391 building of kernels before this point. Add -m ${SRC}/share/mk
392 (for the right value of SRC) to your command lines to work
393 around; update your useland to a point after this; or use the
394 buildkernel/installkernel top-level targets. See also 20120829.
397 The IPFIREWALL_FORWARD kernel option has been removed. Its
398 functionality now turned on by default.
401 The random(4) support for the VIA hardware random number
402 generator (`PADLOCK') is no longer enabled unconditionally.
403 Add the PADLOCK_RNG option in the custom kernel config if
404 needed. The GENERIC kernels on i386 and amd64 do include the
405 option, so the change only affects the custom kernel
409 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
410 the traditional method, you must update your system with an installworld
411 before the kernel will build. The documented make buildkernel/installkernel
412 interfaces (coupled with fresh make kernel-toolchain) continue to work.
415 The sparc64 ZFS loader has been changed to no longer try to auto-
416 detect ZFS providers based on diskN aliases but now requires these
417 to be explicitly listed in the OFW boot-device environment variable.
420 Now unix domain sockets behave "as expected" on nullfs(5). Previously
421 nullfs(5) did not pass through all behaviours to the underlying layer,
422 as a result if we bound to a socket on the lower layer we could connect
423 only to the lower path; if we bound to the upper layer we could connect
424 only to the upper path. The new behavior is one can connect to both the
425 lower and the upper paths regardless what layer path one binds to.
428 The acpi_wmi(4) status device /dev/wmistat has been renamed to
432 A new VOP_ADVISE() was added to support posix_fadvise(2). All
433 filesystem modules must be recompiled.
436 The interface of the VOP_VPTOCNP(9) changed, now the returned
437 vnode shall be referenced, previously it was required to be
438 only held. All in-tree filesystems are converted.
444 The broken amd(4) driver has been replaced with esp(4) in the amd64,
445 i386 and pc98 GENERIC kernel configuration files.
448 This commit modifies vfs_register() so that it uses a hash
449 calculation to set vfc_typenum, which is enabled by default.
450 The first time a system is booted after this change, the
451 vfc_typenum values will change for all file systems. The
452 main effect of this is a change to the NFS server file handles
453 for file systems that use vfc_typenum in their fsid, such as ZFS.
454 It will, however, prevent vfc_typenum from changing when file
455 systems are loaded in a different order for subsequent reboots.
456 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
457 until you are ready to remount all NFS clients after a reboot.
460 Bump the shared library version numbers for libraries that
461 do not use symbol versioning, have changed the ABI compared
462 to stable/8 and which shared library version was not bumped.
463 Done as part of 9.0-RELEASE cycle.
466 During the merge of Capsicum features, the fget(9) KPI was modified.
467 This may require the rebuilding of out-of-tree device drivers --
468 issues have been reported specifically with the nVidia device driver.
469 __FreeBSD_version is bumped to 900041.
471 Also, there is a period between 20110811 and 20110814 where the
472 special devices /dev/{stdin,stdout,stderr} did not work correctly.
473 Building world from a kernel during that window may not work.
476 The packet filter (pf) code has been updated to OpenBSD 4.5.
477 You need to update userland tools to be in sync with kernel.
478 This update breaks backward compatibility with earlier pfsync(4)
479 versions. Care must be taken when updating redundant firewall setups.
482 The following sysctls and tunables are retired on x86 platforms:
484 machdep.hlt_logical_cpus
485 The following sysctl is retired:
486 machdep.hyperthreading_allowed
487 The sysctls were supposed to provide a way to dynamically offline and
488 online selected CPUs on x86 platforms, but the implementation has not
489 been reliable especially with SCHED_ULE scheduler.
490 machdep.hyperthreading_allowed tunable is still available to ignore
491 hyperthreading CPUs at OS level.
492 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
493 where X is an APIC ID of a CPU. Be advised, though, that disabling
494 CPUs in non-uniform fashion will result in non-uniform topology and
495 may lead to sub-optimal system performance with SCHED_ULE, which is
499 cpumask_t type is retired and cpuset_t is used in order to describe
503 Changes to ifconfig(8) for dynamic address family detection mandate
504 that you are running a kernel of 20110525 or later. Make sure to
505 follow the update procedure to boot a new kernel before installing
509 Support for sun4v architecture is officially dropped
512 Several KPI breaking changes have been committed to the mii(4) layer,
513 the PHY drivers and consequently some Ethernet drivers using mii(4).
514 This means that miibus.ko and the modules of the affected Ethernet
515 drivers need to be recompiled.
517 Note to kernel developers: Given that the OUI bit reversion problem
518 was fixed as part of these changes all mii(4) commits related to OUIs,
519 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
520 handling, no longer can be merged verbatim to stable/8 and previous
524 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
525 into their kernel configurations along with 'device pci'.
528 The default NFS client is now the new NFS client, so fstype "newnfs"
529 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
530 Although mounts via fstype "nfs" will usually work without userland
531 changes, it is recommended that the mount(8) and mount_nfs(8)
532 commands be rebuilt from sources and that a link to mount_nfs called
533 mount_oldnfs be created. The new client is compiled into the
534 kernel with "options NFSCL" and this is needed for diskless root
535 file systems. The GENERIC kernel configs have been changed to use
536 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
537 To use the regular/old client, you can "mount -t oldnfs ...". For
538 a diskless root file system, you must also include a line like:
540 vfs.root.mountfrom="oldnfs:"
542 in the boot/loader.conf on the root fs on the NFS server to make
543 a diskless root fs use the old client.
546 The GENERIC kernels for all architectures now default to the new
547 CAM-based ATA stack. It means that all legacy ATA drivers were
548 removed and replaced by respective CAM drivers. If you are using
549 ATA device names in /etc/fstab or other places, make sure to update
550 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
551 where 'Y's are the sequential numbers starting from zero for each type
552 in order of detection, unless configured otherwise with tunables,
553 see cam(4)). There will be symbolic links created in /dev/ to map
554 old adX devices to the respective adaY. They should provide basic
555 compatibility for file systems mounting in most cases, but they do
556 not support old user-level APIs and do not have respective providers
557 in GEOM. Consider using updated management tools with new device names.
559 It is possible to load devices ahci, ata, siis and mvs as modules,
560 but option ATA_CAM should remain in kernel configuration to make ata
561 module work as CAM driver supporting legacy ATA controllers. Device ata
562 still can be used in modular fashion (atacore + ...). Modules atadisk
563 and atapi* are not used and won't affect operation in ATA_CAM mode.
564 Note that to use CAM-based ATA kernel should include CAM devices
565 scbus, pass, da (or explicitly ada), cd and optionally others. All of
566 them are parts of the cam module.
568 ataraid(4) functionality is now supported by the RAID GEOM class.
569 To use it you can load geom_raid kernel module and use graid(8) tool
570 for management. Instead of /dev/arX device names, use /dev/raid/rX.
572 No kernel config options or code have been removed, so if a problem
573 arises, please report it and optionally revert to the old ATA stack.
574 In order to do it you can remove from the kernel config:
579 , and instead add back:
580 device atadisk # ATA disk drives
581 device ataraid # ATA RAID drives
582 device atapicd # ATAPI CDROM drives
583 device atapifd # ATAPI floppy drives
584 device atapist # ATAPI tape drives
587 The default NFS server has been changed to the new server, which
588 was referred to as the experimental server. If you need to switch
589 back to the old NFS server, you must now put the "-o" option on
590 both the mountd and nfsd commands. This can be done using the
591 mountd_flags and nfs_server_flags rc.conf variables until an
592 update to the rc scripts is committed, which is coming soon.
595 The GNU Objective-C runtime library (libobjc), and other Objective-C
596 related components have been removed from the base system. If you
597 require an Objective-C library, please use one of the available ports.
600 ath(4) has been split into bus- and device- modules. if_ath contains
601 the HAL, the TX rate control and the network device code. if_ath_pci
602 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
603 contains the AHB glue. Users need to load both if_ath_pci and if_ath
604 in order to use ath on everything else.
606 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
607 need to load if_ath and if_ath_pci for ath(4) operation.
610 As part of the replacement of sysinstall, the process of building
611 release media has changed significantly. For details, please re-read
612 release(7), which has been updated to reflect the new build process.
615 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
616 is the last available version under GPLv2. It brings a number of new
617 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
618 4.1 and SSE 4.2), better support for powerpc64, a number of new
619 directives, and lots of other small improvements. See the ChangeLog
620 file in contrib/binutils for the full details.
623 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
624 compliant, and will now use half of hash for authentication.
625 This will break interoperability with all stacks (including all
626 actual FreeBSD versions) who implement
627 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
629 The only workaround with such peers is to use another HMAC
630 algorithm for IPsec ("phase 2") authentication.
633 Remove the uio_yield prototype and symbol. This function has
634 been misnamed since it was introduced and should not be
635 globally exposed with this name. The equivalent functionality
636 is now available using kern_yield(curthread->td_user_pri).
637 The function remains undocumented.
640 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
641 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
642 for scalar sysctls is defined but disabled. Code that needs
643 UQUAD to pass the type checking that must compile on older
644 systems where the define is not present can check against
645 __FreeBSD_version >= 900030.
647 The system dialog(1) has been replaced with a new version previously
648 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
649 with the previous version, but the libdialog associated with it has
650 a largely incompatible API. As such, the original version of libdialog
651 will be kept temporarily as libodialog, until its base system consumers
652 are replaced or updated. Bump __FreeBSD_version to 900030.
655 If you are trying to run make universe on a -stable system, and you get
656 the following warning:
657 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
658 unknown. config(8) likely too old."
659 or something similar to it, then you must upgrade your -stable system
660 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
661 stable/8) or build the config from the latest stable/8 branch and
662 install it on your system.
664 Prior to this date, building a current universe on 8-stable system from
665 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
666 error in the first kernel build phase. A new config on those old
667 systems will fix that problem for older versions of -current.
670 The TCP stack has been modified to allow Khelp modules to interact with
671 it via helper hook points and store per-connection data in the TCP
672 control block. Bump __FreeBSD_version to 900029. User space tools that
673 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
677 Generic IEEE 802.3 annex 31B full duplex flow control support has been
678 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
679 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
680 to take advantage of it instead of using custom implementations. This
681 means that these drivers now no longer unconditionally advertise
682 support for flow control but only do so if flow control is a selected
683 media option. This was implemented in the generic support that way in
684 order to allow flow control to be switched on and off via ifconfig(8)
685 with the PHY specific default to typically off in order to protect
686 from unwanted effects. Consequently, if you used flow control with
687 one of the above mentioned drivers you now need to explicitly enable
689 ifconfig bge0 media auto mediaopt flowcontrol
691 Along with the above mentioned changes generic support for setting
692 1000baseT master mode also has been added and brgphy(4), ciphy(4),
693 e1000phy(4) as well as ip1000phy(4) have been converted to take
694 advantage of it. This means that these drivers now no longer take the
695 link0 parameter for selecting master mode but the master media option
696 has to be used instead, for example like in the following:
697 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
699 Selection of master mode now is also available with all other PHY
700 drivers supporting 1000baseT.
703 The TCP stack has received a significant update to add support for
704 modularised congestion control and generally improve the clarity of
705 congestion control decisions. Bump __FreeBSD_version to 900025. User
706 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
707 sockstat) need to be recompiled.
710 The man(1) utility has been replaced by a new version that no longer
711 uses /etc/manpath.config. Please consult man.conf(5) for how to
712 migrate local entries to the new format.
715 The copyright strings printed by login(1) and sshd(8) at the time of a
716 new connection have been removed to follow other operating systems and
720 A workaround for a fixed ld bug has been removed in kernel code,
721 so make sure that your system ld is built from sources after
722 revision 210245 from 2010-07-19 (r211583 if building head kernel
723 on stable/8, r211584 for stable/7; both from 2010-08-21).
724 A symptom of incorrect ld version is different addresses for
725 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
728 The $ipv6_prefer variable in rc.conf(5) has been split into
729 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
731 The $ip6addrctl_policy is a variable to choose a pre-defined
732 address selection policy set by ip6addrctl(8). A value
733 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
736 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
737 flag (see an entry of 20090926) is set on an interface with no
738 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
739 security reason. If you want IPv6 link-local address on all
740 interfaces by default, set this to "YES".
742 The old ipv6_prefer="YES" is equivalent to
743 ipv6_activate_all_interfaces="YES" and
744 ip6addrctl_policy="ipv6_prefer".
747 DTrace has grown support for userland tracing. Due to this, DTrace is
748 now i386 and amd64 only.
749 dtruss(1) is now installed by default on those systems and a new
750 kernel module is needed for userland tracing: fasttrap.
751 No changes to your kernel config file are necessary to enable
752 userland tracing, but you might consider adding 'STRIP=' and
753 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
754 to have informative userland stack traces in DTrace (ustack).
757 The acpi_aiboost(4) driver has been removed in favor of the new
758 aibs(4) driver. You should update your kernel configuration file.
761 BSD grep has been imported to the base system and it is built by
762 default. It is completely BSD licensed, highly GNU-compatible, uses
763 less memory than its GNU counterpart and has a small codebase.
764 However, it is slower than its GNU counterpart, which is mostly
765 noticeable for larger searches, for smaller ones it is measurable
766 but not significant. The reason is complex, the most important factor
767 is that we lack a modern and efficient regex library and GNU
768 overcomes this by optimizing the searches internally. Future work
769 on improving the regex performance is planned, for the meantime,
770 users that need better performance, can build GNU grep instead by
771 setting the WITH_GNU_GREP knob.
774 Due to the import of powerpc64 support, all existing powerpc kernel
775 configuration files must be updated with a machine directive like this:
776 machine powerpc powerpc
778 In addition, an updated config(8) is required to build powerpc kernels
782 A new version of ZFS (version 15) has been merged to -HEAD.
783 This version uses a python library for the following subcommands:
784 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
785 For full functionality of these commands the following port must
786 be installed: sysutils/py-zfs
789 'vm_page's are now hashed by physical address to an array of mutexes.
790 Currently this is only used to serialize access to hold_count. Over
791 time the page queue mutex will be peeled away. This changes the size
792 of pmap on every architecture. And requires all callers of vm_page_hold
793 and vm_page_unhold to be updated.
796 WITH_CTF can now be specified in src.conf (not recommended, there
797 are some problems with static executables), make.conf (would also
798 affect ports which do not use GNU make and do not override the
799 compile targets) or in the kernel config (via "makeoptions
801 When WITH_CTF was specified there before this was silently ignored,
802 so make sure that WITH_CTF is not used in places which could lead
803 to unwanted behavior.
806 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
807 to allow 32-bit compatibility on non-x86 platforms. All kernel
808 configurations on amd64 and ia64 platforms using these options must
809 be modified accordingly.
812 The utmp user accounting database has been replaced with utmpx,
813 the user accounting interface standardized by POSIX.
814 Unfortunately the semantics of utmp and utmpx don't match,
815 making it practically impossible to support both interfaces.
816 The user accounting database is used by tools like finger(1),
817 last(1), talk(1), w(1) and ac(8).
819 All applications in the base system use utmpx. This means only
820 local binaries (e.g. from the ports tree) may still use these
821 utmp database files. These applications must be rebuilt to make
824 After the system has been upgraded, it is safe to remove the old
825 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
826 assuming their contents is of no importance anymore. Old wtmp
827 databases can only be used by last(1) and ac(8) after they have
828 been converted to the new format using wtmpcvt(1).
831 Introduce the kernel thread "deadlock resolver" (which can be enabled
832 via the DEADLKRES option, see NOTES for more details) and the
833 sleepq_type() function for sleepqueues.
836 The rc.firewall and rc.firewall6 were unified, and
837 rc.firewall6 and rc.d/ip6fw were removed.
838 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
839 variables are obsoleted. Instead, the following new rc
840 variables are added to rc.d/ipfw:
842 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
843 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
844 firewall_simple_onet_ipv6, firewall_trusted_ipv6
846 The meanings correspond to the relevant IPv4 variables.
852 The default terminal emulation for syscons(4) has been changed
853 from cons25 to xterm on all platforms except pc98. This means
854 that the /etc/ttys file needs to be updated to ensure correct
855 operation of applications on the console.
857 The terminal emulation style can be toggled per window by using
858 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
859 options can be used to change the compile-time default back to
862 To prevent graphical artifacts, make sure the TERM environment
863 variable is set to match the terminal emulation that is being
864 performed by syscons(4).
867 The layout of the structure ieee80211req_scan_result has changed.
868 Applications that require wireless scan results (e.g. ifconfig(8))
869 from net80211 need to be recompiled.
871 Applications such as wpa_supplicant(8) may require a full world
872 build without using NO_CLEAN in order to get synchronized with the
876 The iwn(4) driver has been updated to support the 5000 and 5150 series.
877 There's one kernel module for each firmware. Adding "device iwnfw"
878 to the kernel configuration file means including all three firmware
879 images inside the kernel. If you want to include just the one for
880 your wireless card, use the devices iwn4965fw, iwn5000fw or
884 The rc.d/network_ipv6, IPv6 configuration script has been integrated
885 into rc.d/netif. The changes are the following:
887 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
888 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
889 Note that both variables need the "inet6" keyword at the head.
891 Do not set $ipv6_network_interfaces manually if you do not
892 understand what you are doing. It is not needed in most cases.
894 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
897 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
898 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
900 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
901 all configured interfaces have "inet6 accept_rtadv" in the
902 $ifconfig_IF_ipv6. These are for backward compatibility.
904 3. A new variable $ipv6_prefer has been added. If NO, IPv6
905 functionality of interfaces with no corresponding
906 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
907 and the default address selection policy of ip6addrctl(8)
908 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
909 Note that if you want to configure IPv6 functionality on the
910 disabled interfaces after boot, first you need to clear the flag by
911 using ifconfig(8) like:
913 ifconfig em0 inet6 -ifdisabled
915 If YES, the default address selection policy is set as
918 The default value of $ipv6_prefer is NO.
920 4. If your system need to receive Router Advertisement messages,
921 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
922 scripts automatically invoke rtsol(8) when the interface becomes
923 UP. The Router Advertisement messages are used for SLAAC
924 (State-Less Address AutoConfiguration).
927 802.11s D3.03 support was committed. This is incompatible with the
928 previous code, which was based on D3.0.
931 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
932 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
933 control whether accepting Router Advertisement messages or not.
934 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
935 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
936 The ifconfig(8) utility now supports these flags.
939 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
940 mount(8) and -a option for df(1) to see them.
943 The old tunable hw.bus.devctl_disable has been superseded by
944 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
945 replaced by hw.bus.devctl_queue=0. The default for this new tunable
949 Remove the option STOP_NMI. The default action is now to use NMI only
950 for KDB via the newly introduced function stop_cpus_hard() and
951 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
954 The stable/8 branch created in subversion. This corresponds to the
955 RELENG_8 branch in CVS.
958 Bump the shared library version numbers for all libraries that do not
959 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
960 __FreeBSD_version to 800105.
963 Due to changes in the implementation of virtual network stack support,
964 all network-related kernel modules must be recompiled. As this change
965 breaks the ABI, bump __FreeBSD_version to 800104.
968 The TOE interface to the TCP syncache has been modified to remove
969 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
970 The cxgb driver is the only TOE consumer affected by this change, and
971 needs to be recompiled along with the kernel. As this change breaks
972 the ABI, bump __FreeBSD_version to 800103.
975 Padding has been added to struct tcpcb, sackhint and tcpstat in
976 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
977 maintaining the ABI. However, this change breaks the ABI, so bump
978 __FreeBSD_version to 800102. User space tools that rely on the size of
979 any of these structs (e.g. sockstat) need to be recompiled.
982 The NFS_LEGACYRPC option has been removed along with the old kernel
983 RPC implementation that this option selected. Kernel configurations
984 may need to be adjusted.
987 The network interface device nodes at /dev/net/<interface> have been
988 removed. All ioctl operations can be performed the normal way using
989 routing sockets. The kqueue functionality can generally be replaced
990 with routing sockets.
993 The documentation from the FreeBSD Documentation Project (Handbook,
994 FAQ, etc.) is now installed via packages by sysinstall(8) and under
995 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
998 The ABI of various structures related to the SYSV IPC API have been
999 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1000 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1004 Layout of struct vnet has changed as routing related variables were
1005 moved to their own Vimage module. Modules need to be recompiled. Bump
1006 __FreeBSD_version to 800099.
1009 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1010 respectively. As long as no more than 16 groups per process are used,
1011 no changes should be visible. When more than 16 groups are used, old
1012 binaries may fail if they call getgroups() or getgrouplist() with
1013 statically sized storage. Recompiling will work around this, but
1014 applications should be modified to use dynamically allocated storage
1015 for group arrays as POSIX.1-2008 does not cap an implementation's
1016 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1018 NFS and portalfs mounts may also be affected as the list of groups is
1019 truncated to 16. Users of NFS who use more than 16 groups, should
1020 take care that negative group permissions are not used on the exported
1021 file systems as they will not be reliable unless a GSSAPI based
1022 authentication method is used.
1025 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1026 option compiles in the support for adaptive spinning for lockmgrs
1027 which want to enable it. The lockinit() function now accepts the flag
1028 LK_ADAPTIVE in order to make the lock object subject to adaptive
1029 spinning when both held in write and read mode.
1032 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1033 changed. User applications that use this ioctl need to be rebuilt.
1036 The layout of struct thread has changed. Kernel and modules need to
1040 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1041 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1044 window(1) has been removed from the base system. It can now be
1045 installed from ports. The port is called misc/window.
1048 The way we are storing and accessing `routing table' entries has
1049 changed. Programs reading the FIB, like netstat, need to be
1053 A new netisr implementation has been added for FreeBSD 8. Network
1054 file system modules, such as igmp, ipdivert, and others, should be
1056 Bump __FreeBSD_version to 800096.
1059 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1063 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1064 Bump __FreeBSD_version to 800094.
1067 Add mnt_xflag field to 'struct mount'. File system modules need to be
1069 Bump __FreeBSD_version to 800093.
1072 The compiling option ADAPTIVE_SX has been retired while it has been
1073 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1074 The KPI for sx_init_flags() changes as accepting flags:
1075 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1076 been introduced in order to handle the reversed logic.
1077 Bump __FreeBSD_version to 800092.
1080 Add support for hierarchical jails. Remove global securelevel.
1081 Bump __FreeBSD_version to 800091.
1084 The layout of struct vnet_net has changed, therefore modules
1086 Bump __FreeBSD_version to 800090.
1089 The newly imported zic(8) produces a new format in the output. Please
1090 run tzsetup(8) to install the newly created data to /etc/localtime.
1093 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1094 hw.usb.* and is now consistent again with previous releases.
1097 802.11 monitor mode support was revised and driver api's were changed.
1098 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1099 of DLT_IEEE802_11. No user-visible data structures were changed but
1100 applications that use DLT_IEEE802_11 may require changes.
1101 Bump __FreeBSD_version to 800088.
1104 The layout of the following structs has changed: sysctl_oid,
1105 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1106 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1107 panics may be experienced. World rebuild is required for
1108 correctly checking networking state from userland.
1109 Bump __FreeBSD_version to 800085.
1112 MLDv2 and Source-Specific Multicast (SSM) have been merged
1113 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1114 The implementation of SSM within FreeBSD's IPv6 stack closely
1115 follows the IPv4 implementation.
1117 For kernel developers:
1119 * The most important changes are that the ip6_output() and
1120 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1121 and this lock has been downgraded to a non-recursive mutex.
1123 * As with the changes to the IPv4 stack to support SSM, filtering
1124 of inbound multicast traffic must now be performed by transport
1125 protocols within the IPv6 stack. This does not apply to TCP and
1126 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1128 * The KPIs used by IPv6 multicast are similar to those used by
1129 the IPv4 stack, with the following differences:
1130 * im6o_mc_filter() is analogous to imo_multicast_filter().
1131 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1132 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1133 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1134 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1135 for MLDv1 have an additional 'timer' argument which is used to
1136 jitter the initial membership report for the solicited-node
1137 multicast membership on-link.
1138 * This is not strictly needed for MLDv2, which already jitters
1139 its report transmissions. However, the 'timer' argument is
1140 preserved in case MLDv1 is active on the interface.
1142 * The KAME linked-list based IPv6 membership implementation has
1143 been refactored to use a vector similar to that used by the IPv4
1145 Code which maintains a list of its own multicast memberships
1146 internally, e.g. carp, has been updated to reflect the new
1149 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1150 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1151 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1152 implementation constraint which needs to be addressed in HEAD.
1154 For application developers:
1156 * The changes are broadly similar to those made for the IPv4
1159 * The use of IPv4 and IPv6 multicast socket options on the same
1160 socket, using mapped addresses, HAS NOT been tested or supported.
1162 * There are a number of issues with the implementation of various
1163 IPv6 multicast APIs which need to be resolved in the API surface
1164 before the implementation is fully compatible with KAME userland
1165 use, and these are mostly to do with interface index treatment.
1167 * The literature available discusses the use of either the delta / ASM
1168 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1169 using setsourcefilter(3)/getsourcefilter(3). For more information
1170 please refer to RFC 3768, 'Socket Interface Extensions for
1171 Multicast Source Filters'.
1173 * Applications which use the published RFC 3678 APIs should be fine.
1175 For systems administrators:
1177 * The mtest(8) utility has been refactored to support IPv6, in
1178 addition to IPv4. Interface addresses are no longer accepted
1179 as arguments, their names must be used instead. The utility
1180 will map the interface name to its first IPv4 address as
1181 returned by getifaddrs(3).
1183 * The ifmcstat(8) utility has also been updated to print the MLDv2
1184 endpoint state and source filter lists via sysctl(3).
1186 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1187 loopback of IPv6 multicast datagrams by default; it defaults to 1
1188 to preserve the existing behaviour. Disabling multicast loopback is
1189 recommended for optimal system performance.
1191 * The IPv6 MROUTING code has been changed to examine this sysctl
1192 instead of attempting to perform a group lookup before looping
1193 back forwarded datagrams.
1195 Bump __FreeBSD_version to 800084.
1198 Implement low-level Bluetooth HCI API.
1199 Bump __FreeBSD_version to 800083.
1202 The layout of struct malloc_type, used by modules to register new
1203 memory allocation types, has changed. Most modules will need to
1204 be rebuilt or panics may be experienced.
1205 Bump __FreeBSD_version to 800081.
1208 Anticipate overflowing inp_flags - add inp_flags2.
1209 This changes most offsets in inpcb, so checking v4 connection
1210 state will require a world rebuild.
1211 Bump __FreeBSD_version to 800080.
1214 Add an llentry to struct route and struct route_in6. Modules
1215 embedding a struct route will need to be recompiled.
1216 Bump __FreeBSD_version to 800079.
1219 The size of rt_metrics_lite and by extension rtentry has changed.
1220 Networking administration apps will need to be recompiled.
1221 The route command now supports show as an alias for get, weighting
1222 of routes, sticky and nostick flags to alter the behavior of stateful
1224 Bump __FreeBSD_version to 800078.
1227 Do not use Giant for kbdmux(4) locking. This is wrong and
1228 apparently causing more problems than it solves. This will
1229 re-open the issue where interrupt handlers may race with
1230 kbdmux(4) in polling mode. Typical symptoms include (but
1231 not limited to) duplicated and/or missing characters when
1232 low level console functions (such as gets) are used while
1233 interrupts are enabled (for example geli password prompt,
1234 mountroot prompt etc.). Disabling kbdmux(4) may help.
1237 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1238 kernel modules referencing any of the above need to be recompiled.
1239 Bump __FreeBSD_version to 800075.
1242 GEOM_PART has become the default partition slicer for storage devices,
1243 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1244 introduces some changes:
1246 MSDOS/EBR: the devices created from MSDOS extended partition entries
1247 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1248 to devices with offset-based names. fstabs may need to be modified.
1250 BSD: the "geometry does not match label" warning is harmless in most
1251 cases but it points to problems in file system misalignment with
1252 disk geometry. The "c" partition is now implicit, covers the whole
1253 top-level drive and cannot be (mis)used by users.
1255 General: Kernel dumps are now not allowed to be written to devices
1256 whose partition types indicate they are meant to be used for file
1257 systems (or, in case of MSDOS partitions, as something else than
1260 Most of these changes date approximately from 200812.
1263 The uscanner(4) driver has been removed from the kernel. This follows
1264 Linux removing theirs in 2.6 and making libusb the default interface
1265 (supported by sane).
1268 The multicast forwarding code has been cleaned up. netstat(1)
1269 only relies on KVM now for printing bandwidth upcall meters.
1270 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1271 ip6_mroute_mod respectively. The config(5) options for statically
1272 compiling this code remain the same, i.e. 'options MROUTING'.
1275 Support for the IFF_NEEDSGIANT network interface flag has been
1276 removed, which means that non-MPSAFE network device drivers are no
1277 longer supported. In particular, if_ar, if_sr, and network device
1278 drivers from the old (legacy) USB stack can no longer be built or
1282 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1283 a bunch of new language catalog files have also been added.
1284 This means that some common libc messages are now localized and
1285 they depend on the LC_MESSAGES environmental variable.
1288 The k8temp(4) driver has been renamed to amdtemp(4) since
1289 support for Family 10 and Family 11 CPU families was added.
1292 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1293 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1295 For kernel developers, the most important changes are that the
1296 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1297 and this lock has been downgraded to a non-recursive mutex.
1299 Transport protocols (UDP, Raw IP) are now responsible for filtering
1300 inbound multicast traffic according to group membership and source
1301 filters. The imo_multicast_filter() KPI exists for this purpose.
1302 Transports which do not use multicast (SCTP, TCP) already reject
1303 multicast by default. Forwarding and receive performance may improve
1304 as a mutex acquisition is no longer needed in the ip_input()
1305 low-level input path. in_addmulti() and in_delmulti() are shimmed
1306 to new KPIs which exist to support SSM in-kernel.
1308 For application developers, it is recommended that loopback of
1309 multicast datagrams be disabled for best performance, as this
1310 will still cause the lock to be taken for each looped-back
1311 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1312 be tuned to 0 to disable loopback by default; it defaults to 1
1313 to preserve the existing behaviour.
1315 For systems administrators, to obtain best performance with
1316 multicast reception and multiple groups, it is always recommended
1317 that a card with a suitably precise hash filter is used. Hash
1318 collisions will still result in the lock being taken within the
1319 transport protocol input path to check group membership.
1321 If deploying FreeBSD in an environment with IGMP snooping switches,
1322 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1323 enabled; this forces 224.0.0.0/24 group membership to be announced
1326 The size of 'struct igmpstat' has changed; netstat needs to be
1327 recompiled to reflect this.
1328 Bump __FreeBSD_version to 800070.
1331 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1332 updated to use it. This requires a buildworld/installworld in order to
1333 update the library and dependencies (usbconfig, etc). Its advisable to
1334 rebuild all ports which uses libusb. More specific directions are given
1335 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1336 libusb are no longer required and can be removed.
1339 A workaround is committed to allow the creation of System V shared
1340 memory segment of size > 2 GB on the 64-bit architectures.
1341 Due to a limitation of the existing ABI, the shm_segsz member
1342 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1343 wrong for large segments. Note that limits must be explicitly
1344 raised to allow such segments to be created.
1347 The layout of struct ifnet has changed, requiring a rebuild of all
1348 network device driver modules.
1351 The /dev handling for the new USB stack has changed, a
1352 buildworld/installworld is required for libusb20.
1355 The new USB2 stack has now been permanently moved in and all kernel and
1356 module names reverted to their previous values (eg, usb, ehci, ohci,
1357 ums, ...). The old usb stack can be compiled in by prefixing the name
1358 with the letter 'o', the old usb modules have been removed.
1359 Updating entry 20090216 for xorg and 20090215 for libmap may still
1363 The rc.conf(5) option if_up_delay has been renamed to
1364 defaultroute_delay to better reflect its purpose. If you have
1365 customized this setting in /etc/rc.conf you need to update it to
1369 xorg 7.4 wants to configure its input devices via hald which does not
1370 yet work with USB2. If the keyboard/mouse does not work in xorg then
1372 Option "AllowEmptyInput" "off"
1373 to your ServerLayout section. This will cause X to use the configured
1374 kbd and mouse sections from your xorg.conf.
1377 The GENERIC kernels for all architectures now default to the new USB2
1378 stack. No kernel config options or code have been removed so if a
1379 problem arises please report it and optionally revert to the old USB
1380 stack. If you are loading USB kernel modules or have a custom kernel
1381 that includes GENERIC then ensure that usb names are also changed over,
1382 eg uftdi -> usb2_serial_ftdi.
1384 Older programs linked against the ports libusb 0.1 need to be
1385 redirected to the new stack's libusb20. /etc/libmap.conf can
1387 # Map old usb library to new one for usb2 stack
1388 libusb-0.1.so.8 libusb20.so.1
1391 All USB ethernet devices now attach as interfaces under the name ueN
1392 (eg. ue0). This is to provide a predictable name as vendors often
1393 change usb chipsets in a product without notice.
1396 The ichsmb(4) driver has been changed to require SMBus slave
1397 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1398 All of the other SMBus controller drivers require left-justified
1399 slave addresses, so this change makes all the drivers provide the
1403 INET6 statistics (struct ip6stat) was updated.
1404 netstat(1) needs to be recompiled.
1407 NTFS has been removed from GENERIC kernel on amd64 to match
1408 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1409 will load ntfs.ko module automatically when NTFS support is
1410 actually needed, unless ntfs.ko is not installed or security
1411 level prohibits loading kernel modules. If either is the case,
1412 "options NTFS" has to be added into kernel config.
1415 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1416 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1417 800061. User space tools that rely on the size of struct tcpcb in
1418 tcp_var.h (e.g. sockstat) need to be recompiled.
1421 ng_tty(4) module updated to match the new TTY subsystem.
1422 Due to API change, user-level applications must be updated.
1423 New API support added to mpd5 CVS and expected to be present
1424 in next mpd5.3 release.
1427 With __FreeBSD_version 800060 the makefs tool is part of
1428 the base system (it was a port).
1431 The afdata and ifnet locks have been changed from mutexes to
1432 rwlocks, network modules will need to be re-compiled.
1435 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1436 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1437 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1438 architecture and 40 bytes on 64-bit architecture. The userland
1439 applications "arp" and "ndp" have been updated accordingly.
1440 The output from "netstat -r" shows only routing entries and
1441 none of the L2 information.
1444 __FreeBSD_version 800057 marks the switchover from the
1445 binary ath hal to source code. Users must add the line:
1447 options AH_SUPPORT_AR5416
1449 to their kernel config files when specifying:
1453 The ath_hal module no longer exists; the code is now compiled
1454 together with the driver in the ath module. It is now
1455 possible to tailor chip support (i.e. reduce the set of chips
1456 and thereby the code size); consult ath_hal(4) for details.
1459 __FreeBSD_version 800054 adds memory barriers to
1460 <machine/atomic.h>, new interfaces to ifnet to facilitate
1461 multiple hardware transmit queues for cards that support
1462 them, and a lock-less ring-buffer implementation to
1463 enable drivers to more efficiently manage queueing of
1467 A new version of ZFS (version 13) has been merged to -HEAD.
1468 This version has zpool attribute "listsnapshots" off by
1469 default, which means "zfs list" does not show snapshots,
1470 and is the same as Solaris behavior.
1473 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1476 The uhci, ohci, ehci and slhci USB Host controller drivers have
1477 been put into separate modules. If you load the usb module
1478 separately through loader.conf you will need to load the
1479 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1480 controller add the following to loader.conf:
1486 The ABI used by the PMC toolset has changed. Please keep
1487 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1491 atapci kernel module now includes only generic PCI ATA
1492 driver. AHCI driver moved to ataahci kernel module.
1493 All vendor-specific code moved into separate kernel modules:
1494 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1495 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1496 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1497 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1500 The TTY subsystem of the kernel has been replaced by a new
1501 implementation, which provides better scalability and an
1502 improved driver model. Most common drivers have been migrated to
1503 the new TTY subsystem, while others have not. The following
1504 drivers have not yet been ported to the new TTY layer:
1507 cy, digi, rc, rp, sio
1513 ng_h4, ng_tty, ppp, sl, snp
1515 Adding these drivers to your kernel configuration file shall
1516 cause compilation to fail.
1519 ntpd has been upgraded to 4.2.4p5.
1522 OpenSSH has been upgraded to 5.1p1.
1524 For many years, FreeBSD's version of OpenSSH preferred DSA
1525 over RSA for host and user authentication keys. With this
1526 upgrade, we've switched to the vendor's default of RSA over
1527 DSA. This may cause upgraded clients to warn about unknown
1528 host keys even for previously known hosts. Users should
1529 follow the usual procedure for verifying host keys before
1530 accepting the RSA key.
1532 This can be circumvented by setting the "HostKeyAlgorithms"
1533 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1536 Please note that the sequence of keys offered for
1537 authentication has been changed as well. You may want to
1538 specify IdentityFile in a different order to revert this
1542 The sio(4) driver has been removed from the i386 and amd64
1543 kernel configuration files. This means uart(4) is now the
1544 default serial port driver on those platforms as well.
1546 To prevent collisions with the sio(4) driver, the uart(4) driver
1547 uses different names for its device nodes. This means the
1548 onboard serial port will now most likely be called "ttyu0"
1549 instead of "ttyd0". You may need to reconfigure applications to
1550 use the new device names.
1552 When using the serial port as a boot console, be sure to update
1553 /boot/device.hints and /etc/ttys before booting the new kernel.
1554 If you forget to do so, you can still manually specify the hints
1555 at the loader prompt:
1557 set hint.uart.0.at="isa"
1558 set hint.uart.0.port="0x3F8"
1559 set hint.uart.0.flags="0x10"
1560 set hint.uart.0.irq="4"
1564 The gpt(8) utility has been removed. Use gpart(8) to partition
1568 The version that Linuxulator emulates was changed from 2.4.2
1569 to 2.6.16. If you experience any problems with Linux binaries
1570 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1571 if it fixes the problem contact emulation mailing list.
1574 ISDN4BSD (I4B) was removed from the src tree. You may need to
1575 update a your kernel configuration and remove relevant entries.
1578 I have checked in code to support multiple routing tables.
1579 See the man pages setfib(1) and setfib(2).
1580 This is a hopefully backwards compatible version,
1581 but to make use of it you need to compile your kernel
1582 with options ROUTETABLES=2 (or more up to 16).
1585 The 802.11 wireless support was redone to enable multi-bss
1586 operation on devices that are capable. The underlying device
1587 is no longer used directly but instead wlanX devices are
1588 cloned with ifconfig. This requires changes to rc.conf files.
1589 For example, change:
1590 ifconfig_ath0="WPA DHCP"
1593 ifconfig_wlan0="WPA DHCP"
1594 see rc.conf(5) for more details. In addition, mergemaster of
1595 /etc/rc.d is highly recommended. Simultaneous update of userland
1596 and kernel wouldn't hurt either.
1598 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1599 modules were merged into the base wlan module. All references
1600 to these modules (e.g. in kernel config files) must be removed.
1603 psm(4) has gained write(2) support in native operation level.
1604 Arbitrary commands can be written to /dev/psm%d and status can
1605 be read back from it. Therefore, an application is responsible
1606 for status validation and error recovery. It is a no-op in
1607 other operation levels.
1610 Support for KSE threading has been removed from the kernel. To
1611 run legacy applications linked against KSE libmap.conf may
1612 be used. The following libmap.conf may be used to ensure
1613 compatibility with any prior release:
1615 libpthread.so.1 libthr.so.1
1616 libpthread.so.2 libthr.so.2
1617 libkse.so.3 libthr.so.3
1620 The layout of struct vmspace has changed. This affects libkvm
1621 and any executables that link against libkvm and use the
1622 kvm_getprocs() function. In particular, but not exclusively,
1623 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1624 The effects are minimal, but it's advisable to upgrade world
1628 The latest em driver no longer has support in it for the
1629 82575 adapter, this is now moved to the igb driver. The
1630 split was done to make new features that are incompatible
1631 with older hardware easier to do.
1634 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1635 likewise the kernel option is now GEOM_LINUX_LVM.
1638 The default NFS mount mode has changed from UDP to TCP for
1639 increased reliability. If you rely on (insecurely) NFS
1640 mounting across a firewall you may need to update your
1644 Belatedly note the addition of m_collapse for compacting
1648 The fts(3) structures have been changed to use adequate
1649 integer types for their members and so to be able to cope
1650 with huge file trees. The old fts(3) ABI is preserved
1651 through symbol versioning in libc, so third-party binaries
1652 using fts(3) should still work, although they will not take
1653 advantage of the extended types. At the same time, some
1654 third-party software might fail to build after this change
1655 due to unportable assumptions made in its source code about
1656 fts(3) structure members. Such software should be fixed
1657 by its vendor or, in the worst case, in the ports tree.
1658 FreeBSD_version 800015 marks this change for the unlikely
1659 case that a portable fix is impossible.
1662 To upgrade to -current after this date, you must be running
1663 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1664 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1667 The ADAPTIVE_GIANT kernel option has been retired because its
1668 functionality is the default now.
1671 The AT keyboard emulation of sunkbd(4) has been turned on
1672 by default. In order to make the special symbols of the Sun
1673 keyboards driven by sunkbd(4) work under X these now have
1674 to be configured the same way as Sun USB keyboards driven
1675 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1677 Option "XkbLayout" "us"
1678 Option "XkbRules" "xorg"
1679 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1682 It has been decided that it is desirable to provide ABI
1683 backwards compatibility to the FreeBSD 4/5/6 versions of the
1684 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1685 broken with the introduction of PCI domain support (see the
1686 20070930 entry). Unfortunately, this required the ABI of
1687 PCIOCGETCONF to be broken again in order to be able to
1688 provide backwards compatibility to the old version of that
1689 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1690 again. As for prominent ports this affects neither pciutils
1691 nor xorg-server this time, the hal port needs to be rebuilt
1695 The misnamed kthread_create() and friends have been renamed
1696 to kproc_create() etc. Many of the callers already
1697 used kproc_start()..
1698 I will return kthread_create() and friends in a while
1699 with implementations that actually create threads, not procs.
1700 Renaming corresponds with version 800002.
1709 Avoid using make -j when upgrading. While generally safe, there are
1710 sometimes problems using -j to upgrade. If your upgrade fails with
1711 -j, please try again without -j. From time to time in the past there
1712 have been problems using -j with buildworld and/or installworld. This
1713 is especially true when upgrading between "distant" versions (eg one
1714 that cross a major release boundary or several minor releases, or when
1715 several months have passed on the -current branch).
1717 Sometimes, obscure build problems are the result of environment
1718 poisoning. This can happen because the make utility reads its
1719 environment when searching for values for global variables. To run
1720 your build attempts in an "environmental clean room", prefix all make
1721 commands with 'env -i '. See the env(1) manual page for more details.
1723 When upgrading from one major version to another it is generally best
1724 to upgrade to the latest code in the currently installed branch first,
1725 then do an upgrade to the new branch. This is the best-tested upgrade
1726 path, and has the highest probability of being successful. Please try
1727 this approach before reporting problems with a major version upgrade.
1731 When upgrading the boot ZFS pool to a new version, always follow
1734 1.) recompile and reinstall the ZFS boot loader and boot block
1735 (this is part of "make buildworld" and "make installworld")
1737 2.) update the ZFS boot block on your boot drive
1739 The following example updates the ZFS boot block on the first
1740 partition (freebsd-boot) of a GPT partitioned drive ad0:
1741 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1743 Non-boot pools do not need these updates.
1747 If you are updating from a prior version of FreeBSD (even one just
1748 a few days old), you should follow this procedure. It is the most
1749 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1751 make kernel-toolchain
1752 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1753 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1755 To test a kernel once
1756 ---------------------
1757 If you just want to boot a kernel once (because you are not sure
1758 if it works, or if you want to boot a known bad kernel to provide
1759 debugging information) run
1760 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1761 nextboot -k testkernel
1763 To just build a kernel when you know that it won't mess you up
1764 --------------------------------------------------------------
1765 This assumes you are already running a CURRENT system. Replace
1766 ${arch} with the architecture of your machine (e.g. "i386",
1767 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1769 cd src/sys/${arch}/conf
1770 config KERNEL_NAME_HERE
1771 cd ../compile/KERNEL_NAME_HERE
1776 If this fails, go to the "To build a kernel" section.
1778 To rebuild everything and install it on the current system.
1779 -----------------------------------------------------------
1780 # Note: sometimes if you are running current you gotta do more than
1781 # is listed here if you are upgrading from a really old current.
1783 <make sure you have good level 0 dumps>
1785 make kernel KERNCONF=YOUR_KERNEL_HERE
1787 <reboot in single user> [3]
1795 To cross-install current onto a separate partition
1796 --------------------------------------------------
1797 # In this approach we use a separate partition to hold
1798 # current's root, 'usr', and 'var' directories. A partition
1799 # holding "/", "/usr" and "/var" should be about 2GB in
1802 <make sure you have good level 0 dumps>
1805 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1806 <maybe newfs current's root partition>
1807 <mount current's root partition on directory ${CURRENT_ROOT}>
1808 make installworld DESTDIR=${CURRENT_ROOT}
1809 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1810 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1811 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1812 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1813 <reboot into current>
1814 <do a "native" rebuild/install as described in the previous section>
1815 <maybe install compatibility libraries from ports/misc/compat*>
1819 To upgrade in-place from stable to current
1820 ----------------------------------------------
1821 <make sure you have good level 0 dumps>
1823 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1825 <reboot in single user> [3]
1832 Make sure that you've read the UPDATING file to understand the
1833 tweaks to various things you need. At this point in the life
1834 cycle of current, things change often and you are on your own
1835 to cope. The defaults can also change, so please read ALL of
1836 the UPDATING entries.
1838 Also, if you are tracking -current, you must be subscribed to
1839 freebsd-current@freebsd.org. Make sure that before you update
1840 your sources that you have read and understood all the recent
1841 messages there. If in doubt, please track -stable which has
1842 much fewer pitfalls.
1844 [1] If you have third party modules, such as vmware, you
1845 should disable them at this point so they don't crash your
1848 [3] From the bootblocks, boot -s, and then do
1853 adjkerntz -i # if CMOS is wall time
1854 Also, when doing a major release upgrade, it is required that
1855 you boot into single user mode to do the installworld.
1857 [4] Note: This step is non-optional. Failure to do this step
1858 can result in a significant reduction in the functionality of the
1859 system. Attempting to do it by hand is not recommended and those
1860 that pursue this avenue should read this file carefully, as well
1861 as the archives of freebsd-current and freebsd-hackers mailing lists
1862 for potential gotchas. The -U option is also useful to consider.
1863 See mergemaster(8) for more information.
1865 [5] Usually this step is a noop. However, from time to time
1866 you may need to do this if you get unknown user in the following
1867 step. It never hurts to do it all the time. You may need to
1868 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1869 install) after the buildworld before this step if you last updated
1870 from [78]-stable or 9-stable before 20130430.
1872 [6] This only deletes old files and directories. Old libraries
1873 can be deleted by "make delete-old-libs", but you have to make
1874 sure that no program is using those libraries anymore.
1876 [8] In order to have a kernel that can run the 4.x binaries needed to
1877 do an installworld, you must include the COMPAT_FREEBSD4 option in
1878 your kernel. Failure to do so may leave you with a system that is
1879 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1880 required to run the 5.x binaries on more recent kernels. And so on
1881 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1883 Make sure that you merge any new devices from GENERIC since the
1884 last time you updated your kernel config file.
1886 [9] When checking out sources, you must include the -P flag to have
1887 cvs prune empty directories.
1889 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1890 "?=" instead of the "=" assignment operator, so that buildworld can
1891 override the CPUTYPE if it needs to.
1893 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1894 not on the command line, or in /etc/make.conf. buildworld will
1895 warn if it is improperly defined.
1898 This file contains a list, in reverse chronological order, of major
1899 breakages in tracking -current. It is not guaranteed to be a complete
1900 list of such breakages, and only contains entries since October 10, 2007.
1901 If you need to see UPDATING entries from before that date, you will need
1902 to fetch an UPDATING file from an older FreeBSD release.
1904 Copyright information:
1906 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1908 Redistribution, publication, translation and use, with or without
1909 modification, in full or in part, in any form or format of this
1910 document are permitted without further permission from the author.
1912 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1913 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1914 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1915 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1916 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1917 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1918 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1919 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1920 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1921 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1922 POSSIBILITY OF SUCH DAMAGE.
1924 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / releng / 9.3.git / blob