1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 20141210: p6 FreeBSD-SA-14:28.file
17 Fix multiple vulnerabilities in file(1) and libmagic(3).
20 Fix BIND remote denial of service vulnerability. [SA-14:29]
22 20141104: p5 FreeBSD-SA-14:25.setlogin
26 Fix kernel stack disclosure in setlogin(2) / getlogin(2).
29 Fix remote command execution in ftp(1). [SA-14:26]
31 Fix NFSv4 and ZFS cache consistency issue. [EN-14:12]
33 20141022: p4 FreeBSD-EN-14:10.tzdata
34 FreeBSD-EN-14:11.crypt
36 Time zone data file update. [EN-14:10]
38 Change crypt(3) default hashing algorithm back to DES. [EN-14:11]
40 20141021: p3 FreeBSD-SA-14:20.rtsold
41 FreeBSD-SA-14:21.routed
42 FreeBSD-SA-14:22.namei
43 FreeBSD-SA-14:23.openssl
45 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
47 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
49 Fix memory leak in sandboxed namei lookup. [SA-14:22]
51 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
53 20140916: p2 FreeBSD-SA-14:19.tcp
54 Fix Denial of Service in TCP packet processing. [SA-14:19]
56 20140909: p1 FreeBSD-SA-14:18.openssl
57 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
63 On i386 and amd64 systems, the onifconsole flag is now set by default
64 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
65 as a login TTY if it is set in the bootloader as an active kernel
66 console. No changes in behavior should result otherwise. To revert to
67 the previous behavior, set ttyu0 to "off" in /etc/ttys.
70 Clang and llvm have been upgraded to 3.4.1 release.
73 Clang and llvm have been upgraded to 3.4 release.
76 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
77 been deprecated and will not be part of FreeBSD 11.0 and later
78 releases. If you use this driver, please consider switching to
79 the nfe(4) driver instead.
82 The behavior of gss_pseudo_random() for the krb5 mechanism
83 has changed, for applications requesting a longer random string
84 than produced by the underlying enctype's pseudo-random() function.
85 In particular, the random string produced from a session key of
86 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
87 be different at the 17th octet and later, after this change.
88 The counter used in the PRF+ construction is now encoded as a
89 big-endian integer in accordance with RFC 4402.
90 __FreeBSD_version is bumped to 902505.
96 Behavior of devfs rules path matching has been changed.
97 Pattern is now always matched against fully qualified devfs
98 path and slash characters must be explicitly matched by
99 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
100 subdirectories must be reviewed.
103 hastctl(8)'s `status' command output changed to terse one-liner format.
104 Scripts using this should switch to `list' command or be rewritten.
107 Fix a bug that allowed a tracing process (e.g. gdb) to write
108 to a memory-mapped file in the traced process's address space
109 even if neither the traced process nor the tracing process had
110 write access to that file.
113 Added ZFS TRIM support which is enabled by default. To disable
114 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
116 Creating new ZFS pools and adding new devices to existing pools
117 first performs a full device level TRIM which can take a significant
118 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
119 to disable this behaviour.
121 ZFS TRIM requires the underlying device support BIO_DELETE which
122 is currently provided by methods such as ATA TRIM and SCSI UNMAP
123 via CAM, which are typically supported by SSD's.
125 Stats for ZFS TRIM can be monitored by looking at the sysctl's
126 under kstat.zfs.misc.zio_trim.
129 `list' command has been added to hastctl(8). For now, it is full
130 equivalent of `status' command.
131 WARNING: in the near future the output of hastctl's status command
132 will change to more terse format. If you use `hastctl status'
133 for parsing in your scripts, switch to `hastctl list'.
136 The mergemaster command now uses the default MAKEOBJDIRPREFIX
137 rather than creating it's own in the temporary directory in
138 order allow access to bootstrapped versions of tools such as
139 install and mtree. When upgrading from version of FreeBSD where
140 the install command does not support -l, you will need to
141 install a new mergemaster command if mergemaster -p is required.
142 This can be accomplished with the command (cd src/usr.sbin/mergemaster
145 Due to the use of the new -l option to install(1) during build
146 and install, you must take care not to directly set the INSTALL
147 make variable in your /etc/make.conf, /etc/src.conf, or on the
148 command line. If you wish to use the -C flag for all installs
149 you may be able to add INSTALL+=-C to /etc/make.conf or
153 Fix a bug that allows NFS clients to issue READDIR on files.
156 The install(1) option -M has changed meaning and now takes an
157 argument that is a file or path to append logs to. In the
158 unlikely event that -M was the last option on the command line
159 and the command line contained at least two files and a target
160 directory the first file will have logs appended to it. The -M
161 option served little practical purpose in the last decade so it's
162 used expected to be extremely rare.
165 A new compression method (lz4) has been merged to. Please refer to
166 zpool-features(7) for more information.
168 Please refer to the "ZFS notes" section of this file for information
169 on upgrading boot ZFS pools.
172 The VFS KBI was changed with the merge of several nullfs
173 optimizations and fixes. All filesystem modules must be
177 With the addition of auditdistd(8), a new auditdistd user is now
178 depended on during installworld. "mergemaster -p" can be used to add
179 the user prior to installworld, as documented in the handbook.
185 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
186 Starting with this version the old system of ZFS pool versioning
187 is superseded by "feature flags". This concept enables forward
188 compatibility against certain future changes in functionality of ZFS
189 pools. The first two read-only compatible "feature flags" for ZFS
190 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
191 For more information read the new zpool-features(7) manual page.
192 Please refer to the "ZFS notes" section of this file for information
193 on upgrading boot ZFS pools.
196 The commit introducing bsd.compiler.mk breaks the traditional
197 building of kernels before this point. Add -m ${SRC}/share/mk
198 (for the right value of SRC) to your command lines to work
199 around; update your useland to a point after this; or use the
200 buildkernel/installkernel top-level targets. See also 20120829.
203 The IPFIREWALL_FORWARD kernel option has been removed. Its
204 functionality now turned on by default.
207 The random(4) support for the VIA hardware random number
208 generator (`PADLOCK') is no longer enabled unconditionally.
209 Add the PADLOCK_RNG option in the custom kernel config if
210 needed. The GENERIC kernels on i386 and amd64 do include the
211 option, so the change only affects the custom kernel
215 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
216 the traditional method, you must update your system with an installworld
217 before the kernel will build. The documented make buildkernel/installkernel
218 interfaces (coupled with fresh make kernel-toolchain) continue to work.
221 The sparc64 ZFS loader has been changed to no longer try to auto-
222 detect ZFS providers based on diskN aliases but now requires these
223 to be explicitly listed in the OFW boot-device environment variable.
226 Now unix domain sockets behave "as expected" on nullfs(5). Previously
227 nullfs(5) did not pass through all behaviours to the underlying layer,
228 as a result if we bound to a socket on the lower layer we could connect
229 only to the lower path; if we bound to the upper layer we could connect
230 only to the upper path. The new behavior is one can connect to both the
231 lower and the upper paths regardless what layer path one binds to.
234 The acpi_wmi(4) status device /dev/wmistat has been renamed to
238 A new VOP_ADVISE() was added to support posix_fadvise(2). All
239 filesystem modules must be recompiled.
242 The interface of the VOP_VPTOCNP(9) changed, now the returned
243 vnode shall be referenced, previously it was required to be
244 only held. All in-tree filesystems are converted.
250 The broken amd(4) driver has been replaced with esp(4) in the amd64,
251 i386 and pc98 GENERIC kernel configuration files.
254 This commit modifies vfs_register() so that it uses a hash
255 calculation to set vfc_typenum, which is enabled by default.
256 The first time a system is booted after this change, the
257 vfc_typenum values will change for all file systems. The
258 main effect of this is a change to the NFS server file handles
259 for file systems that use vfc_typenum in their fsid, such as ZFS.
260 It will, however, prevent vfc_typenum from changing when file
261 systems are loaded in a different order for subsequent reboots.
262 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
263 until you are ready to remount all NFS clients after a reboot.
266 Bump the shared library version numbers for libraries that
267 do not use symbol versioning, have changed the ABI compared
268 to stable/8 and which shared library version was not bumped.
269 Done as part of 9.0-RELEASE cycle.
272 During the merge of Capsicum features, the fget(9) KPI was modified.
273 This may require the rebuilding of out-of-tree device drivers --
274 issues have been reported specifically with the nVidia device driver.
275 __FreeBSD_version is bumped to 900041.
277 Also, there is a period between 20110811 and 20110814 where the
278 special devices /dev/{stdin,stdout,stderr} did not work correctly.
279 Building world from a kernel during that window may not work.
282 The packet filter (pf) code has been updated to OpenBSD 4.5.
283 You need to update userland tools to be in sync with kernel.
284 This update breaks backward compatibility with earlier pfsync(4)
285 versions. Care must be taken when updating redundant firewall setups.
288 The following sysctls and tunables are retired on x86 platforms:
290 machdep.hlt_logical_cpus
291 The following sysctl is retired:
292 machdep.hyperthreading_allowed
293 The sysctls were supposed to provide a way to dynamically offline and
294 online selected CPUs on x86 platforms, but the implementation has not
295 been reliable especially with SCHED_ULE scheduler.
296 machdep.hyperthreading_allowed tunable is still available to ignore
297 hyperthreading CPUs at OS level.
298 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
299 where X is an APIC ID of a CPU. Be advised, though, that disabling
300 CPUs in non-uniform fashion will result in non-uniform topology and
301 may lead to sub-optimal system performance with SCHED_ULE, which is
305 cpumask_t type is retired and cpuset_t is used in order to describe
309 Changes to ifconfig(8) for dynamic address family detection mandate
310 that you are running a kernel of 20110525 or later. Make sure to
311 follow the update procedure to boot a new kernel before installing
315 Support for sun4v architecture is officially dropped
318 Several KPI breaking changes have been committed to the mii(4) layer,
319 the PHY drivers and consequently some Ethernet drivers using mii(4).
320 This means that miibus.ko and the modules of the affected Ethernet
321 drivers need to be recompiled.
323 Note to kernel developers: Given that the OUI bit reversion problem
324 was fixed as part of these changes all mii(4) commits related to OUIs,
325 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
326 handling, no longer can be merged verbatim to stable/8 and previous
330 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
331 into their kernel configurations along with 'device pci'.
334 The default NFS client is now the new NFS client, so fstype "newnfs"
335 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
336 Although mounts via fstype "nfs" will usually work without userland
337 changes, it is recommended that the mount(8) and mount_nfs(8)
338 commands be rebuilt from sources and that a link to mount_nfs called
339 mount_oldnfs be created. The new client is compiled into the
340 kernel with "options NFSCL" and this is needed for diskless root
341 file systems. The GENERIC kernel configs have been changed to use
342 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
343 To use the regular/old client, you can "mount -t oldnfs ...". For
344 a diskless root file system, you must also include a line like:
346 vfs.root.mountfrom="oldnfs:"
348 in the boot/loader.conf on the root fs on the NFS server to make
349 a diskless root fs use the old client.
352 The GENERIC kernels for all architectures now default to the new
353 CAM-based ATA stack. It means that all legacy ATA drivers were
354 removed and replaced by respective CAM drivers. If you are using
355 ATA device names in /etc/fstab or other places, make sure to update
356 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
357 where 'Y's are the sequential numbers starting from zero for each type
358 in order of detection, unless configured otherwise with tunables,
359 see cam(4)). There will be symbolic links created in /dev/ to map
360 old adX devices to the respective adaY. They should provide basic
361 compatibility for file systems mounting in most cases, but they do
362 not support old user-level APIs and do not have respective providers
363 in GEOM. Consider using updated management tools with new device names.
365 It is possible to load devices ahci, ata, siis and mvs as modules,
366 but option ATA_CAM should remain in kernel configuration to make ata
367 module work as CAM driver supporting legacy ATA controllers. Device ata
368 still can be used in modular fashion (atacore + ...). Modules atadisk
369 and atapi* are not used and won't affect operation in ATA_CAM mode.
370 Note that to use CAM-based ATA kernel should include CAM devices
371 scbus, pass, da (or explicitly ada), cd and optionally others. All of
372 them are parts of the cam module.
374 ataraid(4) functionality is now supported by the RAID GEOM class.
375 To use it you can load geom_raid kernel module and use graid(8) tool
376 for management. Instead of /dev/arX device names, use /dev/raid/rX.
378 No kernel config options or code have been removed, so if a problem
379 arises, please report it and optionally revert to the old ATA stack.
380 In order to do it you can remove from the kernel config:
385 , and instead add back:
386 device atadisk # ATA disk drives
387 device ataraid # ATA RAID drives
388 device atapicd # ATAPI CDROM drives
389 device atapifd # ATAPI floppy drives
390 device atapist # ATAPI tape drives
393 The default NFS server has been changed to the new server, which
394 was referred to as the experimental server. If you need to switch
395 back to the old NFS server, you must now put the "-o" option on
396 both the mountd and nfsd commands. This can be done using the
397 mountd_flags and nfs_server_flags rc.conf variables until an
398 update to the rc scripts is committed, which is coming soon.
401 The GNU Objective-C runtime library (libobjc), and other Objective-C
402 related components have been removed from the base system. If you
403 require an Objective-C library, please use one of the available ports.
406 ath(4) has been split into bus- and device- modules. if_ath contains
407 the HAL, the TX rate control and the network device code. if_ath_pci
408 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
409 contains the AHB glue. Users need to load both if_ath_pci and if_ath
410 in order to use ath on everything else.
412 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
413 need to load if_ath and if_ath_pci for ath(4) operation.
416 As part of the replacement of sysinstall, the process of building
417 release media has changed significantly. For details, please re-read
418 release(7), which has been updated to reflect the new build process.
421 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
422 is the last available version under GPLv2. It brings a number of new
423 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
424 4.1 and SSE 4.2), better support for powerpc64, a number of new
425 directives, and lots of other small improvements. See the ChangeLog
426 file in contrib/binutils for the full details.
429 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
430 compliant, and will now use half of hash for authentication.
431 This will break interoperability with all stacks (including all
432 actual FreeBSD versions) who implement
433 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
435 The only workaround with such peers is to use another HMAC
436 algorithm for IPsec ("phase 2") authentication.
439 Remove the uio_yield prototype and symbol. This function has
440 been misnamed since it was introduced and should not be
441 globally exposed with this name. The equivalent functionality
442 is now available using kern_yield(curthread->td_user_pri).
443 The function remains undocumented.
446 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
447 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
448 for scalar sysctls is defined but disabled. Code that needs
449 UQUAD to pass the type checking that must compile on older
450 systems where the define is not present can check against
451 __FreeBSD_version >= 900030.
453 The system dialog(1) has been replaced with a new version previously
454 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
455 with the previous version, but the libdialog associated with it has
456 a largely incompatible API. As such, the original version of libdialog
457 will be kept temporarily as libodialog, until its base system consumers
458 are replaced or updated. Bump __FreeBSD_version to 900030.
461 If you are trying to run make universe on a -stable system, and you get
462 the following warning:
463 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
464 unknown. config(8) likely too old."
465 or something similar to it, then you must upgrade your -stable system
466 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
467 stable/8) or build the config from the latest stable/8 branch and
468 install it on your system.
470 Prior to this date, building a current universe on 8-stable system from
471 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
472 error in the first kernel build phase. A new config on those old
473 systems will fix that problem for older versions of -current.
476 The TCP stack has been modified to allow Khelp modules to interact with
477 it via helper hook points and store per-connection data in the TCP
478 control block. Bump __FreeBSD_version to 900029. User space tools that
479 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
483 Generic IEEE 802.3 annex 31B full duplex flow control support has been
484 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
485 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
486 to take advantage of it instead of using custom implementations. This
487 means that these drivers now no longer unconditionally advertise
488 support for flow control but only do so if flow control is a selected
489 media option. This was implemented in the generic support that way in
490 order to allow flow control to be switched on and off via ifconfig(8)
491 with the PHY specific default to typically off in order to protect
492 from unwanted effects. Consequently, if you used flow control with
493 one of the above mentioned drivers you now need to explicitly enable
495 ifconfig bge0 media auto mediaopt flowcontrol
497 Along with the above mentioned changes generic support for setting
498 1000baseT master mode also has been added and brgphy(4), ciphy(4),
499 e1000phy(4) as well as ip1000phy(4) have been converted to take
500 advantage of it. This means that these drivers now no longer take the
501 link0 parameter for selecting master mode but the master media option
502 has to be used instead, for example like in the following:
503 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
505 Selection of master mode now is also available with all other PHY
506 drivers supporting 1000baseT.
509 The TCP stack has received a significant update to add support for
510 modularised congestion control and generally improve the clarity of
511 congestion control decisions. Bump __FreeBSD_version to 900025. User
512 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
513 sockstat) need to be recompiled.
516 The man(1) utility has been replaced by a new version that no longer
517 uses /etc/manpath.config. Please consult man.conf(5) for how to
518 migrate local entries to the new format.
521 The copyright strings printed by login(1) and sshd(8) at the time of a
522 new connection have been removed to follow other operating systems and
526 A workaround for a fixed ld bug has been removed in kernel code,
527 so make sure that your system ld is built from sources after
528 revision 210245 from 2010-07-19 (r211583 if building head kernel
529 on stable/8, r211584 for stable/7; both from 2010-08-21).
530 A symptom of incorrect ld version is different addresses for
531 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
534 The $ipv6_prefer variable in rc.conf(5) has been split into
535 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
537 The $ip6addrctl_policy is a variable to choose a pre-defined
538 address selection policy set by ip6addrctl(8). A value
539 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
542 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
543 flag (see an entry of 20090926) is set on an interface with no
544 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
545 security reason. If you want IPv6 link-local address on all
546 interfaces by default, set this to "YES".
548 The old ipv6_prefer="YES" is equivalent to
549 ipv6_activate_all_interfaces="YES" and
550 ip6addrctl_policy="ipv6_prefer".
553 DTrace has grown support for userland tracing. Due to this, DTrace is
554 now i386 and amd64 only.
555 dtruss(1) is now installed by default on those systems and a new
556 kernel module is needed for userland tracing: fasttrap.
557 No changes to your kernel config file are necessary to enable
558 userland tracing, but you might consider adding 'STRIP=' and
559 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
560 to have informative userland stack traces in DTrace (ustack).
563 The acpi_aiboost(4) driver has been removed in favor of the new
564 aibs(4) driver. You should update your kernel configuration file.
567 BSD grep has been imported to the base system and it is built by
568 default. It is completely BSD licensed, highly GNU-compatible, uses
569 less memory than its GNU counterpart and has a small codebase.
570 However, it is slower than its GNU counterpart, which is mostly
571 noticeable for larger searches, for smaller ones it is measurable
572 but not significant. The reason is complex, the most important factor
573 is that we lack a modern and efficient regex library and GNU
574 overcomes this by optimizing the searches internally. Future work
575 on improving the regex performance is planned, for the meantime,
576 users that need better performance, can build GNU grep instead by
577 setting the WITH_GNU_GREP knob.
580 Due to the import of powerpc64 support, all existing powerpc kernel
581 configuration files must be updated with a machine directive like this:
582 machine powerpc powerpc
584 In addition, an updated config(8) is required to build powerpc kernels
588 A new version of ZFS (version 15) has been merged to -HEAD.
589 This version uses a python library for the following subcommands:
590 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
591 For full functionality of these commands the following port must
592 be installed: sysutils/py-zfs
595 'vm_page's are now hashed by physical address to an array of mutexes.
596 Currently this is only used to serialize access to hold_count. Over
597 time the page queue mutex will be peeled away. This changes the size
598 of pmap on every architecture. And requires all callers of vm_page_hold
599 and vm_page_unhold to be updated.
602 WITH_CTF can now be specified in src.conf (not recommended, there
603 are some problems with static executables), make.conf (would also
604 affect ports which do not use GNU make and do not override the
605 compile targets) or in the kernel config (via "makeoptions
607 When WITH_CTF was specified there before this was silently ignored,
608 so make sure that WITH_CTF is not used in places which could lead
609 to unwanted behavior.
612 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
613 to allow 32-bit compatibility on non-x86 platforms. All kernel
614 configurations on amd64 and ia64 platforms using these options must
615 be modified accordingly.
618 The utmp user accounting database has been replaced with utmpx,
619 the user accounting interface standardized by POSIX.
620 Unfortunately the semantics of utmp and utmpx don't match,
621 making it practically impossible to support both interfaces.
622 The user accounting database is used by tools like finger(1),
623 last(1), talk(1), w(1) and ac(8).
625 All applications in the base system use utmpx. This means only
626 local binaries (e.g. from the ports tree) may still use these
627 utmp database files. These applications must be rebuilt to make
630 After the system has been upgraded, it is safe to remove the old
631 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
632 assuming their contents is of no importance anymore. Old wtmp
633 databases can only be used by last(1) and ac(8) after they have
634 been converted to the new format using wtmpcvt(1).
637 Introduce the kernel thread "deadlock resolver" (which can be enabled
638 via the DEADLKRES option, see NOTES for more details) and the
639 sleepq_type() function for sleepqueues.
642 The rc.firewall and rc.firewall6 were unified, and
643 rc.firewall6 and rc.d/ip6fw were removed.
644 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
645 variables are obsoleted. Instead, the following new rc
646 variables are added to rc.d/ipfw:
648 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
649 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
650 firewall_simple_onet_ipv6, firewall_trusted_ipv6
652 The meanings correspond to the relevant IPv4 variables.
658 The default terminal emulation for syscons(4) has been changed
659 from cons25 to xterm on all platforms except pc98. This means
660 that the /etc/ttys file needs to be updated to ensure correct
661 operation of applications on the console.
663 The terminal emulation style can be toggled per window by using
664 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
665 options can be used to change the compile-time default back to
668 To prevent graphical artifacts, make sure the TERM environment
669 variable is set to match the terminal emulation that is being
670 performed by syscons(4).
673 The layout of the structure ieee80211req_scan_result has changed.
674 Applications that require wireless scan results (e.g. ifconfig(8))
675 from net80211 need to be recompiled.
677 Applications such as wpa_supplicant(8) may require a full world
678 build without using NO_CLEAN in order to get synchronized with the
682 The iwn(4) driver has been updated to support the 5000 and 5150 series.
683 There's one kernel module for each firmware. Adding "device iwnfw"
684 to the kernel configuration file means including all three firmware
685 images inside the kernel. If you want to include just the one for
686 your wireless card, use the devices iwn4965fw, iwn5000fw or
690 The rc.d/network_ipv6, IPv6 configuration script has been integrated
691 into rc.d/netif. The changes are the following:
693 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
694 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
695 Note that both variables need the "inet6" keyword at the head.
697 Do not set $ipv6_network_interfaces manually if you do not
698 understand what you are doing. It is not needed in most cases.
700 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
703 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
704 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
706 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
707 all configured interfaces have "inet6 accept_rtadv" in the
708 $ifconfig_IF_ipv6. These are for backward compatibility.
710 3. A new variable $ipv6_prefer has been added. If NO, IPv6
711 functionality of interfaces with no corresponding
712 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
713 and the default address selection policy of ip6addrctl(8)
714 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
715 Note that if you want to configure IPv6 functionality on the
716 disabled interfaces after boot, first you need to clear the flag by
717 using ifconfig(8) like:
719 ifconfig em0 inet6 -ifdisabled
721 If YES, the default address selection policy is set as
724 The default value of $ipv6_prefer is NO.
726 4. If your system need to receive Router Advertisement messages,
727 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
728 scripts automatically invoke rtsol(8) when the interface becomes
729 UP. The Router Advertisement messages are used for SLAAC
730 (State-Less Address AutoConfiguration).
733 802.11s D3.03 support was committed. This is incompatible with the
734 previous code, which was based on D3.0.
737 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
738 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
739 control whether accepting Router Advertisement messages or not.
740 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
741 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
742 The ifconfig(8) utility now supports these flags.
745 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
746 mount(8) and -a option for df(1) to see them.
749 The old tunable hw.bus.devctl_disable has been superseded by
750 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
751 replaced by hw.bus.devctl_queue=0. The default for this new tunable
755 Remove the option STOP_NMI. The default action is now to use NMI only
756 for KDB via the newly introduced function stop_cpus_hard() and
757 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
760 The stable/8 branch created in subversion. This corresponds to the
761 RELENG_8 branch in CVS.
764 Bump the shared library version numbers for all libraries that do not
765 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
766 __FreeBSD_version to 800105.
769 Due to changes in the implementation of virtual network stack support,
770 all network-related kernel modules must be recompiled. As this change
771 breaks the ABI, bump __FreeBSD_version to 800104.
774 The TOE interface to the TCP syncache has been modified to remove
775 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
776 The cxgb driver is the only TOE consumer affected by this change, and
777 needs to be recompiled along with the kernel. As this change breaks
778 the ABI, bump __FreeBSD_version to 800103.
781 Padding has been added to struct tcpcb, sackhint and tcpstat in
782 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
783 maintaining the ABI. However, this change breaks the ABI, so bump
784 __FreeBSD_version to 800102. User space tools that rely on the size of
785 any of these structs (e.g. sockstat) need to be recompiled.
788 The NFS_LEGACYRPC option has been removed along with the old kernel
789 RPC implementation that this option selected. Kernel configurations
790 may need to be adjusted.
793 The network interface device nodes at /dev/net/<interface> have been
794 removed. All ioctl operations can be performed the normal way using
795 routing sockets. The kqueue functionality can generally be replaced
796 with routing sockets.
799 The documentation from the FreeBSD Documentation Project (Handbook,
800 FAQ, etc.) is now installed via packages by sysinstall(8) and under
801 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
804 The ABI of various structures related to the SYSV IPC API have been
805 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
806 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
810 Layout of struct vnet has changed as routing related variables were
811 moved to their own Vimage module. Modules need to be recompiled. Bump
812 __FreeBSD_version to 800099.
815 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
816 respectively. As long as no more than 16 groups per process are used,
817 no changes should be visible. When more than 16 groups are used, old
818 binaries may fail if they call getgroups() or getgrouplist() with
819 statically sized storage. Recompiling will work around this, but
820 applications should be modified to use dynamically allocated storage
821 for group arrays as POSIX.1-2008 does not cap an implementation's
822 number of supported groups at NGROUPS_MAX+1 as previous versions did.
824 NFS and portalfs mounts may also be affected as the list of groups is
825 truncated to 16. Users of NFS who use more than 16 groups, should
826 take care that negative group permissions are not used on the exported
827 file systems as they will not be reliable unless a GSSAPI based
828 authentication method is used.
831 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
832 option compiles in the support for adaptive spinning for lockmgrs
833 which want to enable it. The lockinit() function now accepts the flag
834 LK_ADAPTIVE in order to make the lock object subject to adaptive
835 spinning when both held in write and read mode.
838 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
839 changed. User applications that use this ioctl need to be rebuilt.
842 The layout of struct thread has changed. Kernel and modules need to
846 The layout of structs ifnet, domain, protosw and vnet_net has changed.
847 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
850 window(1) has been removed from the base system. It can now be
851 installed from ports. The port is called misc/window.
854 The way we are storing and accessing `routing table' entries has
855 changed. Programs reading the FIB, like netstat, need to be
859 A new netisr implementation has been added for FreeBSD 8. Network
860 file system modules, such as igmp, ipdivert, and others, should be
862 Bump __FreeBSD_version to 800096.
865 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
869 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
870 Bump __FreeBSD_version to 800094.
873 Add mnt_xflag field to 'struct mount'. File system modules need to be
875 Bump __FreeBSD_version to 800093.
878 The compiling option ADAPTIVE_SX has been retired while it has been
879 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
880 The KPI for sx_init_flags() changes as accepting flags:
881 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
882 been introduced in order to handle the reversed logic.
883 Bump __FreeBSD_version to 800092.
886 Add support for hierarchical jails. Remove global securelevel.
887 Bump __FreeBSD_version to 800091.
890 The layout of struct vnet_net has changed, therefore modules
892 Bump __FreeBSD_version to 800090.
895 The newly imported zic(8) produces a new format in the output. Please
896 run tzsetup(8) to install the newly created data to /etc/localtime.
899 The sysctl tree for the usb stack has renamed from hw.usb2.* to
900 hw.usb.* and is now consistent again with previous releases.
903 802.11 monitor mode support was revised and driver api's were changed.
904 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
905 of DLT_IEEE802_11. No user-visible data structures were changed but
906 applications that use DLT_IEEE802_11 may require changes.
907 Bump __FreeBSD_version to 800088.
910 The layout of the following structs has changed: sysctl_oid,
911 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
912 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
913 panics may be experienced. World rebuild is required for
914 correctly checking networking state from userland.
915 Bump __FreeBSD_version to 800085.
918 MLDv2 and Source-Specific Multicast (SSM) have been merged
919 to the IPv6 stack. VIMAGE hooks are in but not yet used.
920 The implementation of SSM within FreeBSD's IPv6 stack closely
921 follows the IPv4 implementation.
923 For kernel developers:
925 * The most important changes are that the ip6_output() and
926 ip6_input() paths no longer take the IN6_MULTI_LOCK,
927 and this lock has been downgraded to a non-recursive mutex.
929 * As with the changes to the IPv4 stack to support SSM, filtering
930 of inbound multicast traffic must now be performed by transport
931 protocols within the IPv6 stack. This does not apply to TCP and
932 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
934 * The KPIs used by IPv6 multicast are similar to those used by
935 the IPv4 stack, with the following differences:
936 * im6o_mc_filter() is analogous to imo_multicast_filter().
937 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
938 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
939 * IN6_LOOKUP_MULTI() has been deprecated and removed.
940 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
941 for MLDv1 have an additional 'timer' argument which is used to
942 jitter the initial membership report for the solicited-node
943 multicast membership on-link.
944 * This is not strictly needed for MLDv2, which already jitters
945 its report transmissions. However, the 'timer' argument is
946 preserved in case MLDv1 is active on the interface.
948 * The KAME linked-list based IPv6 membership implementation has
949 been refactored to use a vector similar to that used by the IPv4
951 Code which maintains a list of its own multicast memberships
952 internally, e.g. carp, has been updated to reflect the new
955 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
956 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
957 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
958 implementation constraint which needs to be addressed in HEAD.
960 For application developers:
962 * The changes are broadly similar to those made for the IPv4
965 * The use of IPv4 and IPv6 multicast socket options on the same
966 socket, using mapped addresses, HAS NOT been tested or supported.
968 * There are a number of issues with the implementation of various
969 IPv6 multicast APIs which need to be resolved in the API surface
970 before the implementation is fully compatible with KAME userland
971 use, and these are mostly to do with interface index treatment.
973 * The literature available discusses the use of either the delta / ASM
974 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
975 using setsourcefilter(3)/getsourcefilter(3). For more information
976 please refer to RFC 3768, 'Socket Interface Extensions for
977 Multicast Source Filters'.
979 * Applications which use the published RFC 3678 APIs should be fine.
981 For systems administrators:
983 * The mtest(8) utility has been refactored to support IPv6, in
984 addition to IPv4. Interface addresses are no longer accepted
985 as arguments, their names must be used instead. The utility
986 will map the interface name to its first IPv4 address as
987 returned by getifaddrs(3).
989 * The ifmcstat(8) utility has also been updated to print the MLDv2
990 endpoint state and source filter lists via sysctl(3).
992 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
993 loopback of IPv6 multicast datagrams by default; it defaults to 1
994 to preserve the existing behaviour. Disabling multicast loopback is
995 recommended for optimal system performance.
997 * The IPv6 MROUTING code has been changed to examine this sysctl
998 instead of attempting to perform a group lookup before looping
999 back forwarded datagrams.
1001 Bump __FreeBSD_version to 800084.
1004 Implement low-level Bluetooth HCI API.
1005 Bump __FreeBSD_version to 800083.
1008 The layout of struct malloc_type, used by modules to register new
1009 memory allocation types, has changed. Most modules will need to
1010 be rebuilt or panics may be experienced.
1011 Bump __FreeBSD_version to 800081.
1014 Anticipate overflowing inp_flags - add inp_flags2.
1015 This changes most offsets in inpcb, so checking v4 connection
1016 state will require a world rebuild.
1017 Bump __FreeBSD_version to 800080.
1020 Add an llentry to struct route and struct route_in6. Modules
1021 embedding a struct route will need to be recompiled.
1022 Bump __FreeBSD_version to 800079.
1025 The size of rt_metrics_lite and by extension rtentry has changed.
1026 Networking administration apps will need to be recompiled.
1027 The route command now supports show as an alias for get, weighting
1028 of routes, sticky and nostick flags to alter the behavior of stateful
1030 Bump __FreeBSD_version to 800078.
1033 Do not use Giant for kbdmux(4) locking. This is wrong and
1034 apparently causing more problems than it solves. This will
1035 re-open the issue where interrupt handlers may race with
1036 kbdmux(4) in polling mode. Typical symptoms include (but
1037 not limited to) duplicated and/or missing characters when
1038 low level console functions (such as gets) are used while
1039 interrupts are enabled (for example geli password prompt,
1040 mountroot prompt etc.). Disabling kbdmux(4) may help.
1043 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1044 kernel modules referencing any of the above need to be recompiled.
1045 Bump __FreeBSD_version to 800075.
1048 GEOM_PART has become the default partition slicer for storage devices,
1049 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1050 introduces some changes:
1052 MSDOS/EBR: the devices created from MSDOS extended partition entries
1053 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1054 to devices with offset-based names. fstabs may need to be modified.
1056 BSD: the "geometry does not match label" warning is harmless in most
1057 cases but it points to problems in file system misalignment with
1058 disk geometry. The "c" partition is now implicit, covers the whole
1059 top-level drive and cannot be (mis)used by users.
1061 General: Kernel dumps are now not allowed to be written to devices
1062 whose partition types indicate they are meant to be used for file
1063 systems (or, in case of MSDOS partitions, as something else than
1066 Most of these changes date approximately from 200812.
1069 The uscanner(4) driver has been removed from the kernel. This follows
1070 Linux removing theirs in 2.6 and making libusb the default interface
1071 (supported by sane).
1074 The multicast forwarding code has been cleaned up. netstat(1)
1075 only relies on KVM now for printing bandwidth upcall meters.
1076 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1077 ip6_mroute_mod respectively. The config(5) options for statically
1078 compiling this code remain the same, i.e. 'options MROUTING'.
1081 Support for the IFF_NEEDSGIANT network interface flag has been
1082 removed, which means that non-MPSAFE network device drivers are no
1083 longer supported. In particular, if_ar, if_sr, and network device
1084 drivers from the old (legacy) USB stack can no longer be built or
1088 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1089 a bunch of new language catalog files have also been added.
1090 This means that some common libc messages are now localized and
1091 they depend on the LC_MESSAGES environmental variable.
1094 The k8temp(4) driver has been renamed to amdtemp(4) since
1095 support for Family 10 and Family 11 CPU families was added.
1098 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1099 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1101 For kernel developers, the most important changes are that the
1102 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1103 and this lock has been downgraded to a non-recursive mutex.
1105 Transport protocols (UDP, Raw IP) are now responsible for filtering
1106 inbound multicast traffic according to group membership and source
1107 filters. The imo_multicast_filter() KPI exists for this purpose.
1108 Transports which do not use multicast (SCTP, TCP) already reject
1109 multicast by default. Forwarding and receive performance may improve
1110 as a mutex acquisition is no longer needed in the ip_input()
1111 low-level input path. in_addmulti() and in_delmulti() are shimmed
1112 to new KPIs which exist to support SSM in-kernel.
1114 For application developers, it is recommended that loopback of
1115 multicast datagrams be disabled for best performance, as this
1116 will still cause the lock to be taken for each looped-back
1117 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1118 be tuned to 0 to disable loopback by default; it defaults to 1
1119 to preserve the existing behaviour.
1121 For systems administrators, to obtain best performance with
1122 multicast reception and multiple groups, it is always recommended
1123 that a card with a suitably precise hash filter is used. Hash
1124 collisions will still result in the lock being taken within the
1125 transport protocol input path to check group membership.
1127 If deploying FreeBSD in an environment with IGMP snooping switches,
1128 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1129 enabled; this forces 224.0.0.0/24 group membership to be announced
1132 The size of 'struct igmpstat' has changed; netstat needs to be
1133 recompiled to reflect this.
1134 Bump __FreeBSD_version to 800070.
1137 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1138 updated to use it. This requires a buildworld/installworld in order to
1139 update the library and dependencies (usbconfig, etc). Its advisable to
1140 rebuild all ports which uses libusb. More specific directions are given
1141 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1142 libusb are no longer required and can be removed.
1145 A workaround is committed to allow the creation of System V shared
1146 memory segment of size > 2 GB on the 64-bit architectures.
1147 Due to a limitation of the existing ABI, the shm_segsz member
1148 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1149 wrong for large segments. Note that limits must be explicitly
1150 raised to allow such segments to be created.
1153 The layout of struct ifnet has changed, requiring a rebuild of all
1154 network device driver modules.
1157 The /dev handling for the new USB stack has changed, a
1158 buildworld/installworld is required for libusb20.
1161 The new USB2 stack has now been permanently moved in and all kernel and
1162 module names reverted to their previous values (eg, usb, ehci, ohci,
1163 ums, ...). The old usb stack can be compiled in by prefixing the name
1164 with the letter 'o', the old usb modules have been removed.
1165 Updating entry 20090216 for xorg and 20090215 for libmap may still
1169 The rc.conf(5) option if_up_delay has been renamed to
1170 defaultroute_delay to better reflect its purpose. If you have
1171 customized this setting in /etc/rc.conf you need to update it to
1175 xorg 7.4 wants to configure its input devices via hald which does not
1176 yet work with USB2. If the keyboard/mouse does not work in xorg then
1178 Option "AllowEmptyInput" "off"
1179 to your ServerLayout section. This will cause X to use the configured
1180 kbd and mouse sections from your xorg.conf.
1183 The GENERIC kernels for all architectures now default to the new USB2
1184 stack. No kernel config options or code have been removed so if a
1185 problem arises please report it and optionally revert to the old USB
1186 stack. If you are loading USB kernel modules or have a custom kernel
1187 that includes GENERIC then ensure that usb names are also changed over,
1188 eg uftdi -> usb2_serial_ftdi.
1190 Older programs linked against the ports libusb 0.1 need to be
1191 redirected to the new stack's libusb20. /etc/libmap.conf can
1193 # Map old usb library to new one for usb2 stack
1194 libusb-0.1.so.8 libusb20.so.1
1197 All USB ethernet devices now attach as interfaces under the name ueN
1198 (eg. ue0). This is to provide a predictable name as vendors often
1199 change usb chipsets in a product without notice.
1202 The ichsmb(4) driver has been changed to require SMBus slave
1203 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1204 All of the other SMBus controller drivers require left-justified
1205 slave addresses, so this change makes all the drivers provide the
1209 INET6 statistics (struct ip6stat) was updated.
1210 netstat(1) needs to be recompiled.
1213 NTFS has been removed from GENERIC kernel on amd64 to match
1214 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1215 will load ntfs.ko module automatically when NTFS support is
1216 actually needed, unless ntfs.ko is not installed or security
1217 level prohibits loading kernel modules. If either is the case,
1218 "options NTFS" has to be added into kernel config.
1221 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1222 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1223 800061. User space tools that rely on the size of struct tcpcb in
1224 tcp_var.h (e.g. sockstat) need to be recompiled.
1227 ng_tty(4) module updated to match the new TTY subsystem.
1228 Due to API change, user-level applications must be updated.
1229 New API support added to mpd5 CVS and expected to be present
1230 in next mpd5.3 release.
1233 With __FreeBSD_version 800060 the makefs tool is part of
1234 the base system (it was a port).
1237 The afdata and ifnet locks have been changed from mutexes to
1238 rwlocks, network modules will need to be re-compiled.
1241 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1242 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1243 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1244 architecture and 40 bytes on 64-bit architecture. The userland
1245 applications "arp" and "ndp" have been updated accordingly.
1246 The output from "netstat -r" shows only routing entries and
1247 none of the L2 information.
1250 __FreeBSD_version 800057 marks the switchover from the
1251 binary ath hal to source code. Users must add the line:
1253 options AH_SUPPORT_AR5416
1255 to their kernel config files when specifying:
1259 The ath_hal module no longer exists; the code is now compiled
1260 together with the driver in the ath module. It is now
1261 possible to tailor chip support (i.e. reduce the set of chips
1262 and thereby the code size); consult ath_hal(4) for details.
1265 __FreeBSD_version 800054 adds memory barriers to
1266 <machine/atomic.h>, new interfaces to ifnet to facilitate
1267 multiple hardware transmit queues for cards that support
1268 them, and a lock-less ring-buffer implementation to
1269 enable drivers to more efficiently manage queueing of
1273 A new version of ZFS (version 13) has been merged to -HEAD.
1274 This version has zpool attribute "listsnapshots" off by
1275 default, which means "zfs list" does not show snapshots,
1276 and is the same as Solaris behavior.
1279 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1282 The uhci, ohci, ehci and slhci USB Host controller drivers have
1283 been put into separate modules. If you load the usb module
1284 separately through loader.conf you will need to load the
1285 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1286 controller add the following to loader.conf:
1292 The ABI used by the PMC toolset has changed. Please keep
1293 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1297 atapci kernel module now includes only generic PCI ATA
1298 driver. AHCI driver moved to ataahci kernel module.
1299 All vendor-specific code moved into separate kernel modules:
1300 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1301 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1302 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1303 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1306 The TTY subsystem of the kernel has been replaced by a new
1307 implementation, which provides better scalability and an
1308 improved driver model. Most common drivers have been migrated to
1309 the new TTY subsystem, while others have not. The following
1310 drivers have not yet been ported to the new TTY layer:
1313 cy, digi, rc, rp, sio
1319 ng_h4, ng_tty, ppp, sl, snp
1321 Adding these drivers to your kernel configuration file shall
1322 cause compilation to fail.
1325 ntpd has been upgraded to 4.2.4p5.
1328 OpenSSH has been upgraded to 5.1p1.
1330 For many years, FreeBSD's version of OpenSSH preferred DSA
1331 over RSA for host and user authentication keys. With this
1332 upgrade, we've switched to the vendor's default of RSA over
1333 DSA. This may cause upgraded clients to warn about unknown
1334 host keys even for previously known hosts. Users should
1335 follow the usual procedure for verifying host keys before
1336 accepting the RSA key.
1338 This can be circumvented by setting the "HostKeyAlgorithms"
1339 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1342 Please note that the sequence of keys offered for
1343 authentication has been changed as well. You may want to
1344 specify IdentityFile in a different order to revert this
1348 The sio(4) driver has been removed from the i386 and amd64
1349 kernel configuration files. This means uart(4) is now the
1350 default serial port driver on those platforms as well.
1352 To prevent collisions with the sio(4) driver, the uart(4) driver
1353 uses different names for its device nodes. This means the
1354 onboard serial port will now most likely be called "ttyu0"
1355 instead of "ttyd0". You may need to reconfigure applications to
1356 use the new device names.
1358 When using the serial port as a boot console, be sure to update
1359 /boot/device.hints and /etc/ttys before booting the new kernel.
1360 If you forget to do so, you can still manually specify the hints
1361 at the loader prompt:
1363 set hint.uart.0.at="isa"
1364 set hint.uart.0.port="0x3F8"
1365 set hint.uart.0.flags="0x10"
1366 set hint.uart.0.irq="4"
1370 The gpt(8) utility has been removed. Use gpart(8) to partition
1374 The version that Linuxulator emulates was changed from 2.4.2
1375 to 2.6.16. If you experience any problems with Linux binaries
1376 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1377 if it fixes the problem contact emulation mailing list.
1380 ISDN4BSD (I4B) was removed from the src tree. You may need to
1381 update a your kernel configuration and remove relevant entries.
1384 I have checked in code to support multiple routing tables.
1385 See the man pages setfib(1) and setfib(2).
1386 This is a hopefully backwards compatible version,
1387 but to make use of it you need to compile your kernel
1388 with options ROUTETABLES=2 (or more up to 16).
1391 The 802.11 wireless support was redone to enable multi-bss
1392 operation on devices that are capable. The underlying device
1393 is no longer used directly but instead wlanX devices are
1394 cloned with ifconfig. This requires changes to rc.conf files.
1395 For example, change:
1396 ifconfig_ath0="WPA DHCP"
1399 ifconfig_wlan0="WPA DHCP"
1400 see rc.conf(5) for more details. In addition, mergemaster of
1401 /etc/rc.d is highly recommended. Simultaneous update of userland
1402 and kernel wouldn't hurt either.
1404 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1405 modules were merged into the base wlan module. All references
1406 to these modules (e.g. in kernel config files) must be removed.
1409 psm(4) has gained write(2) support in native operation level.
1410 Arbitrary commands can be written to /dev/psm%d and status can
1411 be read back from it. Therefore, an application is responsible
1412 for status validation and error recovery. It is a no-op in
1413 other operation levels.
1416 Support for KSE threading has been removed from the kernel. To
1417 run legacy applications linked against KSE libmap.conf may
1418 be used. The following libmap.conf may be used to ensure
1419 compatibility with any prior release:
1421 libpthread.so.1 libthr.so.1
1422 libpthread.so.2 libthr.so.2
1423 libkse.so.3 libthr.so.3
1426 The layout of struct vmspace has changed. This affects libkvm
1427 and any executables that link against libkvm and use the
1428 kvm_getprocs() function. In particular, but not exclusively,
1429 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1430 The effects are minimal, but it's advisable to upgrade world
1434 The latest em driver no longer has support in it for the
1435 82575 adapter, this is now moved to the igb driver. The
1436 split was done to make new features that are incompatible
1437 with older hardware easier to do.
1440 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1441 likewise the kernel option is now GEOM_LINUX_LVM.
1444 The default NFS mount mode has changed from UDP to TCP for
1445 increased reliability. If you rely on (insecurely) NFS
1446 mounting across a firewall you may need to update your
1450 Belatedly note the addition of m_collapse for compacting
1454 The fts(3) structures have been changed to use adequate
1455 integer types for their members and so to be able to cope
1456 with huge file trees. The old fts(3) ABI is preserved
1457 through symbol versioning in libc, so third-party binaries
1458 using fts(3) should still work, although they will not take
1459 advantage of the extended types. At the same time, some
1460 third-party software might fail to build after this change
1461 due to unportable assumptions made in its source code about
1462 fts(3) structure members. Such software should be fixed
1463 by its vendor or, in the worst case, in the ports tree.
1464 FreeBSD_version 800015 marks this change for the unlikely
1465 case that a portable fix is impossible.
1468 To upgrade to -current after this date, you must be running
1469 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1470 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1473 The ADAPTIVE_GIANT kernel option has been retired because its
1474 functionality is the default now.
1477 The AT keyboard emulation of sunkbd(4) has been turned on
1478 by default. In order to make the special symbols of the Sun
1479 keyboards driven by sunkbd(4) work under X these now have
1480 to be configured the same way as Sun USB keyboards driven
1481 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1483 Option "XkbLayout" "us"
1484 Option "XkbRules" "xorg"
1485 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1488 It has been decided that it is desirable to provide ABI
1489 backwards compatibility to the FreeBSD 4/5/6 versions of the
1490 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1491 broken with the introduction of PCI domain support (see the
1492 20070930 entry). Unfortunately, this required the ABI of
1493 PCIOCGETCONF to be broken again in order to be able to
1494 provide backwards compatibility to the old version of that
1495 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1496 again. As for prominent ports this affects neither pciutils
1497 nor xorg-server this time, the hal port needs to be rebuilt
1501 The misnamed kthread_create() and friends have been renamed
1502 to kproc_create() etc. Many of the callers already
1503 used kproc_start()..
1504 I will return kthread_create() and friends in a while
1505 with implementations that actually create threads, not procs.
1506 Renaming corresponds with version 800002.
1515 Avoid using make -j when upgrading. While generally safe, there are
1516 sometimes problems using -j to upgrade. If your upgrade fails with
1517 -j, please try again without -j. From time to time in the past there
1518 have been problems using -j with buildworld and/or installworld. This
1519 is especially true when upgrading between "distant" versions (eg one
1520 that cross a major release boundary or several minor releases, or when
1521 several months have passed on the -current branch).
1523 Sometimes, obscure build problems are the result of environment
1524 poisoning. This can happen because the make utility reads its
1525 environment when searching for values for global variables. To run
1526 your build attempts in an "environmental clean room", prefix all make
1527 commands with 'env -i '. See the env(1) manual page for more details.
1529 When upgrading from one major version to another it is generally best
1530 to upgrade to the latest code in the currently installed branch first,
1531 then do an upgrade to the new branch. This is the best-tested upgrade
1532 path, and has the highest probability of being successful. Please try
1533 this approach before reporting problems with a major version upgrade.
1537 When upgrading the boot ZFS pool to a new version, always follow
1540 1.) recompile and reinstall the ZFS boot loader and boot block
1541 (this is part of "make buildworld" and "make installworld")
1543 2.) update the ZFS boot block on your boot drive
1545 The following example updates the ZFS boot block on the first
1546 partition (freebsd-boot) of a GPT partitioned drive ad0:
1547 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1549 Non-boot pools do not need these updates.
1553 If you are updating from a prior version of FreeBSD (even one just
1554 a few days old), you should follow this procedure. It is the most
1555 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1557 make kernel-toolchain
1558 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1559 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1561 To test a kernel once
1562 ---------------------
1563 If you just want to boot a kernel once (because you are not sure
1564 if it works, or if you want to boot a known bad kernel to provide
1565 debugging information) run
1566 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1567 nextboot -k testkernel
1569 To just build a kernel when you know that it won't mess you up
1570 --------------------------------------------------------------
1571 This assumes you are already running a CURRENT system. Replace
1572 ${arch} with the architecture of your machine (e.g. "i386",
1573 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1575 cd src/sys/${arch}/conf
1576 config KERNEL_NAME_HERE
1577 cd ../compile/KERNEL_NAME_HERE
1582 If this fails, go to the "To build a kernel" section.
1584 To rebuild everything and install it on the current system.
1585 -----------------------------------------------------------
1586 # Note: sometimes if you are running current you gotta do more than
1587 # is listed here if you are upgrading from a really old current.
1589 <make sure you have good level 0 dumps>
1591 make kernel KERNCONF=YOUR_KERNEL_HERE
1593 <reboot in single user> [3]
1601 To cross-install current onto a separate partition
1602 --------------------------------------------------
1603 # In this approach we use a separate partition to hold
1604 # current's root, 'usr', and 'var' directories. A partition
1605 # holding "/", "/usr" and "/var" should be about 2GB in
1608 <make sure you have good level 0 dumps>
1611 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1612 <maybe newfs current's root partition>
1613 <mount current's root partition on directory ${CURRENT_ROOT}>
1614 make installworld DESTDIR=${CURRENT_ROOT}
1615 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1616 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1617 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1618 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1619 <reboot into current>
1620 <do a "native" rebuild/install as described in the previous section>
1621 <maybe install compatibility libraries from ports/misc/compat*>
1625 To upgrade in-place from stable to current
1626 ----------------------------------------------
1627 <make sure you have good level 0 dumps>
1629 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1631 <reboot in single user> [3]
1638 Make sure that you've read the UPDATING file to understand the
1639 tweaks to various things you need. At this point in the life
1640 cycle of current, things change often and you are on your own
1641 to cope. The defaults can also change, so please read ALL of
1642 the UPDATING entries.
1644 Also, if you are tracking -current, you must be subscribed to
1645 freebsd-current@freebsd.org. Make sure that before you update
1646 your sources that you have read and understood all the recent
1647 messages there. If in doubt, please track -stable which has
1648 much fewer pitfalls.
1650 [1] If you have third party modules, such as vmware, you
1651 should disable them at this point so they don't crash your
1654 [3] From the bootblocks, boot -s, and then do
1659 adjkerntz -i # if CMOS is wall time
1660 Also, when doing a major release upgrade, it is required that
1661 you boot into single user mode to do the installworld.
1663 [4] Note: This step is non-optional. Failure to do this step
1664 can result in a significant reduction in the functionality of the
1665 system. Attempting to do it by hand is not recommended and those
1666 that pursue this avenue should read this file carefully, as well
1667 as the archives of freebsd-current and freebsd-hackers mailing lists
1668 for potential gotchas. The -U option is also useful to consider.
1669 See mergemaster(8) for more information.
1671 [5] Usually this step is a noop. However, from time to time
1672 you may need to do this if you get unknown user in the following
1673 step. It never hurts to do it all the time. You may need to
1674 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1675 install) after the buildworld before this step if you last updated
1676 from [78]-stable or 9-stable before 20130430.
1678 [6] This only deletes old files and directories. Old libraries
1679 can be deleted by "make delete-old-libs", but you have to make
1680 sure that no program is using those libraries anymore.
1682 [8] In order to have a kernel that can run the 4.x binaries needed to
1683 do an installworld, you must include the COMPAT_FREEBSD4 option in
1684 your kernel. Failure to do so may leave you with a system that is
1685 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1686 required to run the 5.x binaries on more recent kernels. And so on
1687 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1689 Make sure that you merge any new devices from GENERIC since the
1690 last time you updated your kernel config file.
1692 [9] When checking out sources, you must include the -P flag to have
1693 cvs prune empty directories.
1695 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1696 "?=" instead of the "=" assignment operator, so that buildworld can
1697 override the CPUTYPE if it needs to.
1699 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1700 not on the command line, or in /etc/make.conf. buildworld will
1701 warn if it is improperly defined.
1704 This file contains a list, in reverse chronological order, of major
1705 breakages in tracking -current. It is not guaranteed to be a complete
1706 list of such breakages, and only contains entries since October 10, 2007.
1707 If you need to see UPDATING entries from before that date, you will need
1708 to fetch an UPDATING file from an older FreeBSD release.
1710 Copyright information:
1712 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1714 Redistribution, publication, translation and use, with or without
1715 modification, in full or in part, in any form or format of this
1716 document are permitted without further permission from the author.
1718 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1719 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1720 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1721 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1722 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1723 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1724 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1725 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1726 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1727 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1728 POSSIBILITY OF SUCH DAMAGE.
1730 Contact Warner Losh if you have any questions about your use of