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