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