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.
15 At svn r296219, the default linux compat kernel ABI has been adjusted
16 to 2.6.18 in support of the linux-c6 compat ports infrastructure
17 update. If you wish to continue using the linux-f10 compat ports,
18 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
19 encouraged to update their linux-compat packages to linux-c6 during
20 their next update cycle.
23 NTP has been upgraded to 4.2.8p4.
24 The configuration file syntax has been changed, thus mergemaster
25 run is recommended. Now the "kod" parameter requires "limited"
26 parameter. If the ntp.conf is not updated, the ntpd will run
27 successfully, but with KoD disabled.
30 An additional fix for the issue described in the 20150615 sendmail
31 entry below has been been committed in revision 284788.
34 The latest version of openssl rejects TLS handshakes with DH
35 parameters below 768 bits. sendmail releases prior to 8.15.2
36 (not yet released), defaulted to a 512 bit DH parameter setting
37 for client connections. To improve interoperability, the
38 sendmail default for client connections has been raised to
42 It is no longer necessary to include the dwarf version in your DEBUG
43 options in your kernel config file. The bug that required it to be
44 placed in the config file has bene fixed. DEBUG should now just
45 contain -g. The build system will automatically update things
46 to do the right thing.
52 On i386 and amd64 systems, the onifconsole flag is now set by default
53 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
54 as a login TTY if it is set in the bootloader as an active kernel
55 console. No changes in behavior should result otherwise. To revert to
56 the previous behavior, set ttyu0 to "off" in /etc/ttys.
59 Clang and llvm have been upgraded to 3.4.1 release.
62 Clang and llvm have been upgraded to 3.4 release.
65 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
66 been deprecated and will not be part of FreeBSD 11.0 and later
67 releases. If you use this driver, please consider switching to
68 the nfe(4) driver instead.
71 The behavior of gss_pseudo_random() for the krb5 mechanism
72 has changed, for applications requesting a longer random string
73 than produced by the underlying enctype's pseudo-random() function.
74 In particular, the random string produced from a session key of
75 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
76 be different at the 17th octet and later, after this change.
77 The counter used in the PRF+ construction is now encoded as a
78 big-endian integer in accordance with RFC 4402.
79 __FreeBSD_version is bumped to 902505.
85 Behavior of devfs rules path matching has been changed.
86 Pattern is now always matched against fully qualified devfs
87 path and slash characters must be explicitly matched by
88 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
89 subdirectories must be reviewed.
92 hastctl(8)'s `status' command output changed to terse one-liner format.
93 Scripts using this should switch to `list' command or be rewritten.
96 Fix a bug that allowed a tracing process (e.g. gdb) to write
97 to a memory-mapped file in the traced process's address space
98 even if neither the traced process nor the tracing process had
99 write access to that file.
102 Added ZFS TRIM support which is enabled by default. To disable
103 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
105 Creating new ZFS pools and adding new devices to existing pools
106 first performs a full device level TRIM which can take a significant
107 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
108 to disable this behaviour.
110 ZFS TRIM requires the underlying device support BIO_DELETE which
111 is currently provided by methods such as ATA TRIM and SCSI UNMAP
112 via CAM, which are typically supported by SSD's.
114 Stats for ZFS TRIM can be monitored by looking at the sysctl's
115 under kstat.zfs.misc.zio_trim.
118 `list' command has been added to hastctl(8). For now, it is full
119 equivalent of `status' command.
120 WARNING: in the near future the output of hastctl's status command
121 will change to more terse format. If you use `hastctl status'
122 for parsing in your scripts, switch to `hastctl list'.
125 The mergemaster command now uses the default MAKEOBJDIRPREFIX
126 rather than creating it's own in the temporary directory in
127 order allow access to bootstrapped versions of tools such as
128 install and mtree. When upgrading from version of FreeBSD where
129 the install command does not support -l, you will need to
130 install a new mergemaster command if mergemaster -p is required.
131 This can be accomplished with the command (cd src/usr.sbin/mergemaster
134 Due to the use of the new -l option to install(1) during build
135 and install, you must take care not to directly set the INSTALL
136 make variable in your /etc/make.conf, /etc/src.conf, or on the
137 command line. If you wish to use the -C flag for all installs
138 you may be able to add INSTALL+=-C to /etc/make.conf or
142 Fix a bug that allows NFS clients to issue READDIR on files.
145 The install(1) option -M has changed meaning and now takes an
146 argument that is a file or path to append logs to. In the
147 unlikely event that -M was the last option on the command line
148 and the command line contained at least two files and a target
149 directory the first file will have logs appended to it. The -M
150 option served little practical purpose in the last decade so it's
151 used expected to be extremely rare.
154 A new compression method (lz4) has been merged to. Please refer to
155 zpool-features(7) for more information.
157 Please refer to the "ZFS notes" section of this file for information
158 on upgrading boot ZFS pools.
161 The VFS KBI was changed with the merge of several nullfs
162 optimizations and fixes. All filesystem modules must be
166 With the addition of auditdistd(8), a new auditdistd user is now
167 depended on during installworld. "mergemaster -p" can be used to add
168 the user prior to installworld, as documented in the handbook.
174 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
175 Starting with this version the old system of ZFS pool versioning
176 is superseded by "feature flags". This concept enables forward
177 compatibility against certain future changes in functionality of ZFS
178 pools. The first two read-only compatible "feature flags" for ZFS
179 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
180 For more information read the new zpool-features(7) manual page.
181 Please refer to the "ZFS notes" section of this file for information
182 on upgrading boot ZFS pools.
185 The commit introducing bsd.compiler.mk breaks the traditional
186 building of kernels before this point. Add -m ${SRC}/share/mk
187 (for the right value of SRC) to your command lines to work
188 around; update your useland to a point after this; or use the
189 buildkernel/installkernel top-level targets. See also 20120829.
192 The IPFIREWALL_FORWARD kernel option has been removed. Its
193 functionality now turned on by default.
196 The random(4) support for the VIA hardware random number
197 generator (`PADLOCK') is no longer enabled unconditionally.
198 Add the PADLOCK_RNG option in the custom kernel config if
199 needed. The GENERIC kernels on i386 and amd64 do include the
200 option, so the change only affects the custom kernel
204 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
205 the traditional method, you must update your system with an installworld
206 before the kernel will build. The documented make buildkernel/installkernel
207 interfaces (coupled with fresh make kernel-toolchain) continue to work.
210 The sparc64 ZFS loader has been changed to no longer try to auto-
211 detect ZFS providers based on diskN aliases but now requires these
212 to be explicitly listed in the OFW boot-device environment variable.
215 Now unix domain sockets behave "as expected" on nullfs(5). Previously
216 nullfs(5) did not pass through all behaviours to the underlying layer,
217 as a result if we bound to a socket on the lower layer we could connect
218 only to the lower path; if we bound to the upper layer we could connect
219 only to the upper path. The new behavior is one can connect to both the
220 lower and the upper paths regardless what layer path one binds to.
223 The acpi_wmi(4) status device /dev/wmistat has been renamed to
227 A new VOP_ADVISE() was added to support posix_fadvise(2). All
228 filesystem modules must be recompiled.
231 The interface of the VOP_VPTOCNP(9) changed, now the returned
232 vnode shall be referenced, previously it was required to be
233 only held. All in-tree filesystems are converted.
239 The broken amd(4) driver has been replaced with esp(4) in the amd64,
240 i386 and pc98 GENERIC kernel configuration files.
243 This commit modifies vfs_register() so that it uses a hash
244 calculation to set vfc_typenum, which is enabled by default.
245 The first time a system is booted after this change, the
246 vfc_typenum values will change for all file systems. The
247 main effect of this is a change to the NFS server file handles
248 for file systems that use vfc_typenum in their fsid, such as ZFS.
249 It will, however, prevent vfc_typenum from changing when file
250 systems are loaded in a different order for subsequent reboots.
251 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
252 until you are ready to remount all NFS clients after a reboot.
255 Bump the shared library version numbers for libraries that
256 do not use symbol versioning, have changed the ABI compared
257 to stable/8 and which shared library version was not bumped.
258 Done as part of 9.0-RELEASE cycle.
261 During the merge of Capsicum features, the fget(9) KPI was modified.
262 This may require the rebuilding of out-of-tree device drivers --
263 issues have been reported specifically with the nVidia device driver.
264 __FreeBSD_version is bumped to 900041.
266 Also, there is a period between 20110811 and 20110814 where the
267 special devices /dev/{stdin,stdout,stderr} did not work correctly.
268 Building world from a kernel during that window may not work.
271 The packet filter (pf) code has been updated to OpenBSD 4.5.
272 You need to update userland tools to be in sync with kernel.
273 This update breaks backward compatibility with earlier pfsync(4)
274 versions. Care must be taken when updating redundant firewall setups.
277 The following sysctls and tunables are retired on x86 platforms:
279 machdep.hlt_logical_cpus
280 The following sysctl is retired:
281 machdep.hyperthreading_allowed
282 The sysctls were supposed to provide a way to dynamically offline and
283 online selected CPUs on x86 platforms, but the implementation has not
284 been reliable especially with SCHED_ULE scheduler.
285 machdep.hyperthreading_allowed tunable is still available to ignore
286 hyperthreading CPUs at OS level.
287 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
288 where X is an APIC ID of a CPU. Be advised, though, that disabling
289 CPUs in non-uniform fashion will result in non-uniform topology and
290 may lead to sub-optimal system performance with SCHED_ULE, which is
294 cpumask_t type is retired and cpuset_t is used in order to describe
298 Changes to ifconfig(8) for dynamic address family detection mandate
299 that you are running a kernel of 20110525 or later. Make sure to
300 follow the update procedure to boot a new kernel before installing
304 Support for sun4v architecture is officially dropped
307 Several KPI breaking changes have been committed to the mii(4) layer,
308 the PHY drivers and consequently some Ethernet drivers using mii(4).
309 This means that miibus.ko and the modules of the affected Ethernet
310 drivers need to be recompiled.
312 Note to kernel developers: Given that the OUI bit reversion problem
313 was fixed as part of these changes all mii(4) commits related to OUIs,
314 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
315 handling, no longer can be merged verbatim to stable/8 and previous
319 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
320 into their kernel configurations along with 'device pci'.
323 The default NFS client is now the new NFS client, so fstype "newnfs"
324 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
325 Although mounts via fstype "nfs" will usually work without userland
326 changes, it is recommended that the mount(8) and mount_nfs(8)
327 commands be rebuilt from sources and that a link to mount_nfs called
328 mount_oldnfs be created. The new client is compiled into the
329 kernel with "options NFSCL" and this is needed for diskless root
330 file systems. The GENERIC kernel configs have been changed to use
331 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
332 To use the regular/old client, you can "mount -t oldnfs ...". For
333 a diskless root file system, you must also include a line like:
335 vfs.root.mountfrom="oldnfs:"
337 in the boot/loader.conf on the root fs on the NFS server to make
338 a diskless root fs use the old client.
341 The GENERIC kernels for all architectures now default to the new
342 CAM-based ATA stack. It means that all legacy ATA drivers were
343 removed and replaced by respective CAM drivers. If you are using
344 ATA device names in /etc/fstab or other places, make sure to update
345 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
346 where 'Y's are the sequential numbers starting from zero for each type
347 in order of detection, unless configured otherwise with tunables,
348 see cam(4)). There will be symbolic links created in /dev/ to map
349 old adX devices to the respective adaY. They should provide basic
350 compatibility for file systems mounting in most cases, but they do
351 not support old user-level APIs and do not have respective providers
352 in GEOM. Consider using updated management tools with new device names.
354 It is possible to load devices ahci, ata, siis and mvs as modules,
355 but option ATA_CAM should remain in kernel configuration to make ata
356 module work as CAM driver supporting legacy ATA controllers. Device ata
357 still can be used in modular fashion (atacore + ...). Modules atadisk
358 and atapi* are not used and won't affect operation in ATA_CAM mode.
359 Note that to use CAM-based ATA kernel should include CAM devices
360 scbus, pass, da (or explicitly ada), cd and optionally others. All of
361 them are parts of the cam module.
363 ataraid(4) functionality is now supported by the RAID GEOM class.
364 To use it you can load geom_raid kernel module and use graid(8) tool
365 for management. Instead of /dev/arX device names, use /dev/raid/rX.
367 No kernel config options or code have been removed, so if a problem
368 arises, please report it and optionally revert to the old ATA stack.
369 In order to do it you can remove from the kernel config:
374 , and instead add back:
375 device atadisk # ATA disk drives
376 device ataraid # ATA RAID drives
377 device atapicd # ATAPI CDROM drives
378 device atapifd # ATAPI floppy drives
379 device atapist # ATAPI tape drives
382 The default NFS server has been changed to the new server, which
383 was referred to as the experimental server. If you need to switch
384 back to the old NFS server, you must now put the "-o" option on
385 both the mountd and nfsd commands. This can be done using the
386 mountd_flags and nfs_server_flags rc.conf variables until an
387 update to the rc scripts is committed, which is coming soon.
390 The GNU Objective-C runtime library (libobjc), and other Objective-C
391 related components have been removed from the base system. If you
392 require an Objective-C library, please use one of the available ports.
395 ath(4) has been split into bus- and device- modules. if_ath contains
396 the HAL, the TX rate control and the network device code. if_ath_pci
397 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
398 contains the AHB glue. Users need to load both if_ath_pci and if_ath
399 in order to use ath on everything else.
401 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
402 need to load if_ath and if_ath_pci for ath(4) operation.
405 As part of the replacement of sysinstall, the process of building
406 release media has changed significantly. For details, please re-read
407 release(7), which has been updated to reflect the new build process.
410 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
411 is the last available version under GPLv2. It brings a number of new
412 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
413 4.1 and SSE 4.2), better support for powerpc64, a number of new
414 directives, and lots of other small improvements. See the ChangeLog
415 file in contrib/binutils for the full details.
418 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
419 compliant, and will now use half of hash for authentication.
420 This will break interoperability with all stacks (including all
421 actual FreeBSD versions) who implement
422 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
424 The only workaround with such peers is to use another HMAC
425 algorithm for IPsec ("phase 2") authentication.
428 Remove the uio_yield prototype and symbol. This function has
429 been misnamed since it was introduced and should not be
430 globally exposed with this name. The equivalent functionality
431 is now available using kern_yield(curthread->td_user_pri).
432 The function remains undocumented.
435 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
436 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
437 for scalar sysctls is defined but disabled. Code that needs
438 UQUAD to pass the type checking that must compile on older
439 systems where the define is not present can check against
440 __FreeBSD_version >= 900030.
442 The system dialog(1) has been replaced with a new version previously
443 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
444 with the previous version, but the libdialog associated with it has
445 a largely incompatible API. As such, the original version of libdialog
446 will be kept temporarily as libodialog, until its base system consumers
447 are replaced or updated. Bump __FreeBSD_version to 900030.
450 If you are trying to run make universe on a -stable system, and you get
451 the following warning:
452 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
453 unknown. config(8) likely too old."
454 or something similar to it, then you must upgrade your -stable system
455 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
456 stable/8) or build the config from the latest stable/8 branch and
457 install it on your system.
459 Prior to this date, building a current universe on 8-stable system from
460 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
461 error in the first kernel build phase. A new config on those old
462 systems will fix that problem for older versions of -current.
465 The TCP stack has been modified to allow Khelp modules to interact with
466 it via helper hook points and store per-connection data in the TCP
467 control block. Bump __FreeBSD_version to 900029. User space tools that
468 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
472 Generic IEEE 802.3 annex 31B full duplex flow control support has been
473 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
474 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
475 to take advantage of it instead of using custom implementations. This
476 means that these drivers now no longer unconditionally advertise
477 support for flow control but only do so if flow control is a selected
478 media option. This was implemented in the generic support that way in
479 order to allow flow control to be switched on and off via ifconfig(8)
480 with the PHY specific default to typically off in order to protect
481 from unwanted effects. Consequently, if you used flow control with
482 one of the above mentioned drivers you now need to explicitly enable
484 ifconfig bge0 media auto mediaopt flowcontrol
486 Along with the above mentioned changes generic support for setting
487 1000baseT master mode also has been added and brgphy(4), ciphy(4),
488 e1000phy(4) as well as ip1000phy(4) have been converted to take
489 advantage of it. This means that these drivers now no longer take the
490 link0 parameter for selecting master mode but the master media option
491 has to be used instead, for example like in the following:
492 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
494 Selection of master mode now is also available with all other PHY
495 drivers supporting 1000baseT.
498 The TCP stack has received a significant update to add support for
499 modularised congestion control and generally improve the clarity of
500 congestion control decisions. Bump __FreeBSD_version to 900025. User
501 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
502 sockstat) need to be recompiled.
505 The man(1) utility has been replaced by a new version that no longer
506 uses /etc/manpath.config. Please consult man.conf(5) for how to
507 migrate local entries to the new format.
510 The copyright strings printed by login(1) and sshd(8) at the time of a
511 new connection have been removed to follow other operating systems and
515 A workaround for a fixed ld bug has been removed in kernel code,
516 so make sure that your system ld is built from sources after
517 revision 210245 from 2010-07-19 (r211583 if building head kernel
518 on stable/8, r211584 for stable/7; both from 2010-08-21).
519 A symptom of incorrect ld version is different addresses for
520 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
523 The $ipv6_prefer variable in rc.conf(5) has been split into
524 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
526 The $ip6addrctl_policy is a variable to choose a pre-defined
527 address selection policy set by ip6addrctl(8). A value
528 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
531 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
532 flag (see an entry of 20090926) is set on an interface with no
533 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
534 security reason. If you want IPv6 link-local address on all
535 interfaces by default, set this to "YES".
537 The old ipv6_prefer="YES" is equivalent to
538 ipv6_activate_all_interfaces="YES" and
539 ip6addrctl_policy="ipv6_prefer".
542 DTrace has grown support for userland tracing. Due to this, DTrace is
543 now i386 and amd64 only.
544 dtruss(1) is now installed by default on those systems and a new
545 kernel module is needed for userland tracing: fasttrap.
546 No changes to your kernel config file are necessary to enable
547 userland tracing, but you might consider adding 'STRIP=' and
548 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
549 to have informative userland stack traces in DTrace (ustack).
552 The acpi_aiboost(4) driver has been removed in favor of the new
553 aibs(4) driver. You should update your kernel configuration file.
556 BSD grep has been imported to the base system and it is built by
557 default. It is completely BSD licensed, highly GNU-compatible, uses
558 less memory than its GNU counterpart and has a small codebase.
559 However, it is slower than its GNU counterpart, which is mostly
560 noticeable for larger searches, for smaller ones it is measurable
561 but not significant. The reason is complex, the most important factor
562 is that we lack a modern and efficient regex library and GNU
563 overcomes this by optimizing the searches internally. Future work
564 on improving the regex performance is planned, for the meantime,
565 users that need better performance, can build GNU grep instead by
566 setting the WITH_GNU_GREP knob.
569 Due to the import of powerpc64 support, all existing powerpc kernel
570 configuration files must be updated with a machine directive like this:
571 machine powerpc powerpc
573 In addition, an updated config(8) is required to build powerpc kernels
577 A new version of ZFS (version 15) has been merged to -HEAD.
578 This version uses a python library for the following subcommands:
579 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
580 For full functionality of these commands the following port must
581 be installed: sysutils/py-zfs
584 'vm_page's are now hashed by physical address to an array of mutexes.
585 Currently this is only used to serialize access to hold_count. Over
586 time the page queue mutex will be peeled away. This changes the size
587 of pmap on every architecture. And requires all callers of vm_page_hold
588 and vm_page_unhold to be updated.
591 WITH_CTF can now be specified in src.conf (not recommended, there
592 are some problems with static executables), make.conf (would also
593 affect ports which do not use GNU make and do not override the
594 compile targets) or in the kernel config (via "makeoptions
596 When WITH_CTF was specified there before this was silently ignored,
597 so make sure that WITH_CTF is not used in places which could lead
598 to unwanted behavior.
601 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
602 to allow 32-bit compatibility on non-x86 platforms. All kernel
603 configurations on amd64 and ia64 platforms using these options must
604 be modified accordingly.
607 The utmp user accounting database has been replaced with utmpx,
608 the user accounting interface standardized by POSIX.
609 Unfortunately the semantics of utmp and utmpx don't match,
610 making it practically impossible to support both interfaces.
611 The user accounting database is used by tools like finger(1),
612 last(1), talk(1), w(1) and ac(8).
614 All applications in the base system use utmpx. This means only
615 local binaries (e.g. from the ports tree) may still use these
616 utmp database files. These applications must be rebuilt to make
619 After the system has been upgraded, it is safe to remove the old
620 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
621 assuming their contents is of no importance anymore. Old wtmp
622 databases can only be used by last(1) and ac(8) after they have
623 been converted to the new format using wtmpcvt(1).
626 Introduce the kernel thread "deadlock resolver" (which can be enabled
627 via the DEADLKRES option, see NOTES for more details) and the
628 sleepq_type() function for sleepqueues.
631 The rc.firewall and rc.firewall6 were unified, and
632 rc.firewall6 and rc.d/ip6fw were removed.
633 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
634 variables are obsoleted. Instead, the following new rc
635 variables are added to rc.d/ipfw:
637 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
638 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
639 firewall_simple_onet_ipv6, firewall_trusted_ipv6
641 The meanings correspond to the relevant IPv4 variables.
647 The default terminal emulation for syscons(4) has been changed
648 from cons25 to xterm on all platforms except pc98. This means
649 that the /etc/ttys file needs to be updated to ensure correct
650 operation of applications on the console.
652 The terminal emulation style can be toggled per window by using
653 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
654 options can be used to change the compile-time default back to
657 To prevent graphical artifacts, make sure the TERM environment
658 variable is set to match the terminal emulation that is being
659 performed by syscons(4).
662 The layout of the structure ieee80211req_scan_result has changed.
663 Applications that require wireless scan results (e.g. ifconfig(8))
664 from net80211 need to be recompiled.
666 Applications such as wpa_supplicant(8) may require a full world
667 build without using NO_CLEAN in order to get synchronized with the
671 The iwn(4) driver has been updated to support the 5000 and 5150 series.
672 There's one kernel module for each firmware. Adding "device iwnfw"
673 to the kernel configuration file means including all three firmware
674 images inside the kernel. If you want to include just the one for
675 your wireless card, use the devices iwn4965fw, iwn5000fw or
679 The rc.d/network_ipv6, IPv6 configuration script has been integrated
680 into rc.d/netif. The changes are the following:
682 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
683 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
684 Note that both variables need the "inet6" keyword at the head.
686 Do not set $ipv6_network_interfaces manually if you do not
687 understand what you are doing. It is not needed in most cases.
689 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
692 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
693 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
695 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
696 all configured interfaces have "inet6 accept_rtadv" in the
697 $ifconfig_IF_ipv6. These are for backward compatibility.
699 3. A new variable $ipv6_prefer has been added. If NO, IPv6
700 functionality of interfaces with no corresponding
701 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
702 and the default address selection policy of ip6addrctl(8)
703 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
704 Note that if you want to configure IPv6 functionality on the
705 disabled interfaces after boot, first you need to clear the flag by
706 using ifconfig(8) like:
708 ifconfig em0 inet6 -ifdisabled
710 If YES, the default address selection policy is set as
713 The default value of $ipv6_prefer is NO.
715 4. If your system need to receive Router Advertisement messages,
716 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
717 scripts automatically invoke rtsol(8) when the interface becomes
718 UP. The Router Advertisement messages are used for SLAAC
719 (State-Less Address AutoConfiguration).
722 802.11s D3.03 support was committed. This is incompatible with the
723 previous code, which was based on D3.0.
726 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
727 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
728 control whether accepting Router Advertisement messages or not.
729 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
730 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
731 The ifconfig(8) utility now supports these flags.
734 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
735 mount(8) and -a option for df(1) to see them.
738 The old tunable hw.bus.devctl_disable has been superseded by
739 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
740 replaced by hw.bus.devctl_queue=0. The default for this new tunable
744 Remove the option STOP_NMI. The default action is now to use NMI only
745 for KDB via the newly introduced function stop_cpus_hard() and
746 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
749 The stable/8 branch created in subversion. This corresponds to the
750 RELENG_8 branch in CVS.
753 Bump the shared library version numbers for all libraries that do not
754 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
755 __FreeBSD_version to 800105.
758 Due to changes in the implementation of virtual network stack support,
759 all network-related kernel modules must be recompiled. As this change
760 breaks the ABI, bump __FreeBSD_version to 800104.
763 The TOE interface to the TCP syncache has been modified to remove
764 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
765 The cxgb driver is the only TOE consumer affected by this change, and
766 needs to be recompiled along with the kernel. As this change breaks
767 the ABI, bump __FreeBSD_version to 800103.
770 Padding has been added to struct tcpcb, sackhint and tcpstat in
771 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
772 maintaining the ABI. However, this change breaks the ABI, so bump
773 __FreeBSD_version to 800102. User space tools that rely on the size of
774 any of these structs (e.g. sockstat) need to be recompiled.
777 The NFS_LEGACYRPC option has been removed along with the old kernel
778 RPC implementation that this option selected. Kernel configurations
779 may need to be adjusted.
782 The network interface device nodes at /dev/net/<interface> have been
783 removed. All ioctl operations can be performed the normal way using
784 routing sockets. The kqueue functionality can generally be replaced
785 with routing sockets.
788 The documentation from the FreeBSD Documentation Project (Handbook,
789 FAQ, etc.) is now installed via packages by sysinstall(8) and under
790 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
793 The ABI of various structures related to the SYSV IPC API have been
794 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
795 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
799 Layout of struct vnet has changed as routing related variables were
800 moved to their own Vimage module. Modules need to be recompiled. Bump
801 __FreeBSD_version to 800099.
804 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
805 respectively. As long as no more than 16 groups per process are used,
806 no changes should be visible. When more than 16 groups are used, old
807 binaries may fail if they call getgroups() or getgrouplist() with
808 statically sized storage. Recompiling will work around this, but
809 applications should be modified to use dynamically allocated storage
810 for group arrays as POSIX.1-2008 does not cap an implementation's
811 number of supported groups at NGROUPS_MAX+1 as previous versions did.
813 NFS and portalfs mounts may also be affected as the list of groups is
814 truncated to 16. Users of NFS who use more than 16 groups, should
815 take care that negative group permissions are not used on the exported
816 file systems as they will not be reliable unless a GSSAPI based
817 authentication method is used.
820 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
821 option compiles in the support for adaptive spinning for lockmgrs
822 which want to enable it. The lockinit() function now accepts the flag
823 LK_ADAPTIVE in order to make the lock object subject to adaptive
824 spinning when both held in write and read mode.
827 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
828 changed. User applications that use this ioctl need to be rebuilt.
831 The layout of struct thread has changed. Kernel and modules need to
835 The layout of structs ifnet, domain, protosw and vnet_net has changed.
836 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
839 window(1) has been removed from the base system. It can now be
840 installed from ports. The port is called misc/window.
843 The way we are storing and accessing `routing table' entries has
844 changed. Programs reading the FIB, like netstat, need to be
848 A new netisr implementation has been added for FreeBSD 8. Network
849 file system modules, such as igmp, ipdivert, and others, should be
851 Bump __FreeBSD_version to 800096.
854 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
858 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
859 Bump __FreeBSD_version to 800094.
862 Add mnt_xflag field to 'struct mount'. File system modules need to be
864 Bump __FreeBSD_version to 800093.
867 The compiling option ADAPTIVE_SX has been retired while it has been
868 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
869 The KPI for sx_init_flags() changes as accepting flags:
870 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
871 been introduced in order to handle the reversed logic.
872 Bump __FreeBSD_version to 800092.
875 Add support for hierarchical jails. Remove global securelevel.
876 Bump __FreeBSD_version to 800091.
879 The layout of struct vnet_net has changed, therefore modules
881 Bump __FreeBSD_version to 800090.
884 The newly imported zic(8) produces a new format in the output. Please
885 run tzsetup(8) to install the newly created data to /etc/localtime.
888 The sysctl tree for the usb stack has renamed from hw.usb2.* to
889 hw.usb.* and is now consistent again with previous releases.
892 802.11 monitor mode support was revised and driver api's were changed.
893 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
894 of DLT_IEEE802_11. No user-visible data structures were changed but
895 applications that use DLT_IEEE802_11 may require changes.
896 Bump __FreeBSD_version to 800088.
899 The layout of the following structs has changed: sysctl_oid,
900 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
901 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
902 panics may be experienced. World rebuild is required for
903 correctly checking networking state from userland.
904 Bump __FreeBSD_version to 800085.
907 MLDv2 and Source-Specific Multicast (SSM) have been merged
908 to the IPv6 stack. VIMAGE hooks are in but not yet used.
909 The implementation of SSM within FreeBSD's IPv6 stack closely
910 follows the IPv4 implementation.
912 For kernel developers:
914 * The most important changes are that the ip6_output() and
915 ip6_input() paths no longer take the IN6_MULTI_LOCK,
916 and this lock has been downgraded to a non-recursive mutex.
918 * As with the changes to the IPv4 stack to support SSM, filtering
919 of inbound multicast traffic must now be performed by transport
920 protocols within the IPv6 stack. This does not apply to TCP and
921 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
923 * The KPIs used by IPv6 multicast are similar to those used by
924 the IPv4 stack, with the following differences:
925 * im6o_mc_filter() is analogous to imo_multicast_filter().
926 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
927 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
928 * IN6_LOOKUP_MULTI() has been deprecated and removed.
929 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
930 for MLDv1 have an additional 'timer' argument which is used to
931 jitter the initial membership report for the solicited-node
932 multicast membership on-link.
933 * This is not strictly needed for MLDv2, which already jitters
934 its report transmissions. However, the 'timer' argument is
935 preserved in case MLDv1 is active on the interface.
937 * The KAME linked-list based IPv6 membership implementation has
938 been refactored to use a vector similar to that used by the IPv4
940 Code which maintains a list of its own multicast memberships
941 internally, e.g. carp, has been updated to reflect the new
944 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
945 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
946 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
947 implementation constraint which needs to be addressed in HEAD.
949 For application developers:
951 * The changes are broadly similar to those made for the IPv4
954 * The use of IPv4 and IPv6 multicast socket options on the same
955 socket, using mapped addresses, HAS NOT been tested or supported.
957 * There are a number of issues with the implementation of various
958 IPv6 multicast APIs which need to be resolved in the API surface
959 before the implementation is fully compatible with KAME userland
960 use, and these are mostly to do with interface index treatment.
962 * The literature available discusses the use of either the delta / ASM
963 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
964 using setsourcefilter(3)/getsourcefilter(3). For more information
965 please refer to RFC 3768, 'Socket Interface Extensions for
966 Multicast Source Filters'.
968 * Applications which use the published RFC 3678 APIs should be fine.
970 For systems administrators:
972 * The mtest(8) utility has been refactored to support IPv6, in
973 addition to IPv4. Interface addresses are no longer accepted
974 as arguments, their names must be used instead. The utility
975 will map the interface name to its first IPv4 address as
976 returned by getifaddrs(3).
978 * The ifmcstat(8) utility has also been updated to print the MLDv2
979 endpoint state and source filter lists via sysctl(3).
981 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
982 loopback of IPv6 multicast datagrams by default; it defaults to 1
983 to preserve the existing behaviour. Disabling multicast loopback is
984 recommended for optimal system performance.
986 * The IPv6 MROUTING code has been changed to examine this sysctl
987 instead of attempting to perform a group lookup before looping
988 back forwarded datagrams.
990 Bump __FreeBSD_version to 800084.
993 Implement low-level Bluetooth HCI API.
994 Bump __FreeBSD_version to 800083.
997 The layout of struct malloc_type, used by modules to register new
998 memory allocation types, has changed. Most modules will need to
999 be rebuilt or panics may be experienced.
1000 Bump __FreeBSD_version to 800081.
1003 Anticipate overflowing inp_flags - add inp_flags2.
1004 This changes most offsets in inpcb, so checking v4 connection
1005 state will require a world rebuild.
1006 Bump __FreeBSD_version to 800080.
1009 Add an llentry to struct route and struct route_in6. Modules
1010 embedding a struct route will need to be recompiled.
1011 Bump __FreeBSD_version to 800079.
1014 The size of rt_metrics_lite and by extension rtentry has changed.
1015 Networking administration apps will need to be recompiled.
1016 The route command now supports show as an alias for get, weighting
1017 of routes, sticky and nostick flags to alter the behavior of stateful
1019 Bump __FreeBSD_version to 800078.
1022 Do not use Giant for kbdmux(4) locking. This is wrong and
1023 apparently causing more problems than it solves. This will
1024 re-open the issue where interrupt handlers may race with
1025 kbdmux(4) in polling mode. Typical symptoms include (but
1026 not limited to) duplicated and/or missing characters when
1027 low level console functions (such as gets) are used while
1028 interrupts are enabled (for example geli password prompt,
1029 mountroot prompt etc.). Disabling kbdmux(4) may help.
1032 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1033 kernel modules referencing any of the above need to be recompiled.
1034 Bump __FreeBSD_version to 800075.
1037 GEOM_PART has become the default partition slicer for storage devices,
1038 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1039 introduces some changes:
1041 MSDOS/EBR: the devices created from MSDOS extended partition entries
1042 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1043 to devices with offset-based names. fstabs may need to be modified.
1045 BSD: the "geometry does not match label" warning is harmless in most
1046 cases but it points to problems in file system misalignment with
1047 disk geometry. The "c" partition is now implicit, covers the whole
1048 top-level drive and cannot be (mis)used by users.
1050 General: Kernel dumps are now not allowed to be written to devices
1051 whose partition types indicate they are meant to be used for file
1052 systems (or, in case of MSDOS partitions, as something else than
1055 Most of these changes date approximately from 200812.
1058 The uscanner(4) driver has been removed from the kernel. This follows
1059 Linux removing theirs in 2.6 and making libusb the default interface
1060 (supported by sane).
1063 The multicast forwarding code has been cleaned up. netstat(1)
1064 only relies on KVM now for printing bandwidth upcall meters.
1065 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1066 ip6_mroute_mod respectively. The config(5) options for statically
1067 compiling this code remain the same, i.e. 'options MROUTING'.
1070 Support for the IFF_NEEDSGIANT network interface flag has been
1071 removed, which means that non-MPSAFE network device drivers are no
1072 longer supported. In particular, if_ar, if_sr, and network device
1073 drivers from the old (legacy) USB stack can no longer be built or
1077 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1078 a bunch of new language catalog files have also been added.
1079 This means that some common libc messages are now localized and
1080 they depend on the LC_MESSAGES environmental variable.
1083 The k8temp(4) driver has been renamed to amdtemp(4) since
1084 support for Family 10 and Family 11 CPU families was added.
1087 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1088 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1090 For kernel developers, the most important changes are that the
1091 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1092 and this lock has been downgraded to a non-recursive mutex.
1094 Transport protocols (UDP, Raw IP) are now responsible for filtering
1095 inbound multicast traffic according to group membership and source
1096 filters. The imo_multicast_filter() KPI exists for this purpose.
1097 Transports which do not use multicast (SCTP, TCP) already reject
1098 multicast by default. Forwarding and receive performance may improve
1099 as a mutex acquisition is no longer needed in the ip_input()
1100 low-level input path. in_addmulti() and in_delmulti() are shimmed
1101 to new KPIs which exist to support SSM in-kernel.
1103 For application developers, it is recommended that loopback of
1104 multicast datagrams be disabled for best performance, as this
1105 will still cause the lock to be taken for each looped-back
1106 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1107 be tuned to 0 to disable loopback by default; it defaults to 1
1108 to preserve the existing behaviour.
1110 For systems administrators, to obtain best performance with
1111 multicast reception and multiple groups, it is always recommended
1112 that a card with a suitably precise hash filter is used. Hash
1113 collisions will still result in the lock being taken within the
1114 transport protocol input path to check group membership.
1116 If deploying FreeBSD in an environment with IGMP snooping switches,
1117 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1118 enabled; this forces 224.0.0.0/24 group membership to be announced
1121 The size of 'struct igmpstat' has changed; netstat needs to be
1122 recompiled to reflect this.
1123 Bump __FreeBSD_version to 800070.
1126 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1127 updated to use it. This requires a buildworld/installworld in order to
1128 update the library and dependencies (usbconfig, etc). Its advisable to
1129 rebuild all ports which uses libusb. More specific directions are given
1130 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1131 libusb are no longer required and can be removed.
1134 A workaround is committed to allow the creation of System V shared
1135 memory segment of size > 2 GB on the 64-bit architectures.
1136 Due to a limitation of the existing ABI, the shm_segsz member
1137 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1138 wrong for large segments. Note that limits must be explicitly
1139 raised to allow such segments to be created.
1142 The layout of struct ifnet has changed, requiring a rebuild of all
1143 network device driver modules.
1146 The /dev handling for the new USB stack has changed, a
1147 buildworld/installworld is required for libusb20.
1150 The new USB2 stack has now been permanently moved in and all kernel and
1151 module names reverted to their previous values (eg, usb, ehci, ohci,
1152 ums, ...). The old usb stack can be compiled in by prefixing the name
1153 with the letter 'o', the old usb modules have been removed.
1154 Updating entry 20090216 for xorg and 20090215 for libmap may still
1158 The rc.conf(5) option if_up_delay has been renamed to
1159 defaultroute_delay to better reflect its purpose. If you have
1160 customized this setting in /etc/rc.conf you need to update it to
1164 xorg 7.4 wants to configure its input devices via hald which does not
1165 yet work with USB2. If the keyboard/mouse does not work in xorg then
1167 Option "AllowEmptyInput" "off"
1168 to your ServerLayout section. This will cause X to use the configured
1169 kbd and mouse sections from your xorg.conf.
1172 The GENERIC kernels for all architectures now default to the new USB2
1173 stack. No kernel config options or code have been removed so if a
1174 problem arises please report it and optionally revert to the old USB
1175 stack. If you are loading USB kernel modules or have a custom kernel
1176 that includes GENERIC then ensure that usb names are also changed over,
1177 eg uftdi -> usb2_serial_ftdi.
1179 Older programs linked against the ports libusb 0.1 need to be
1180 redirected to the new stack's libusb20. /etc/libmap.conf can
1182 # Map old usb library to new one for usb2 stack
1183 libusb-0.1.so.8 libusb20.so.1
1186 All USB ethernet devices now attach as interfaces under the name ueN
1187 (eg. ue0). This is to provide a predictable name as vendors often
1188 change usb chipsets in a product without notice.
1191 The ichsmb(4) driver has been changed to require SMBus slave
1192 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1193 All of the other SMBus controller drivers require left-justified
1194 slave addresses, so this change makes all the drivers provide the
1198 INET6 statistics (struct ip6stat) was updated.
1199 netstat(1) needs to be recompiled.
1202 NTFS has been removed from GENERIC kernel on amd64 to match
1203 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1204 will load ntfs.ko module automatically when NTFS support is
1205 actually needed, unless ntfs.ko is not installed or security
1206 level prohibits loading kernel modules. If either is the case,
1207 "options NTFS" has to be added into kernel config.
1210 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1211 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1212 800061. User space tools that rely on the size of struct tcpcb in
1213 tcp_var.h (e.g. sockstat) need to be recompiled.
1216 ng_tty(4) module updated to match the new TTY subsystem.
1217 Due to API change, user-level applications must be updated.
1218 New API support added to mpd5 CVS and expected to be present
1219 in next mpd5.3 release.
1222 With __FreeBSD_version 800060 the makefs tool is part of
1223 the base system (it was a port).
1226 The afdata and ifnet locks have been changed from mutexes to
1227 rwlocks, network modules will need to be re-compiled.
1230 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1231 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1232 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1233 architecture and 40 bytes on 64-bit architecture. The userland
1234 applications "arp" and "ndp" have been updated accordingly.
1235 The output from "netstat -r" shows only routing entries and
1236 none of the L2 information.
1239 __FreeBSD_version 800057 marks the switchover from the
1240 binary ath hal to source code. Users must add the line:
1242 options AH_SUPPORT_AR5416
1244 to their kernel config files when specifying:
1248 The ath_hal module no longer exists; the code is now compiled
1249 together with the driver in the ath module. It is now
1250 possible to tailor chip support (i.e. reduce the set of chips
1251 and thereby the code size); consult ath_hal(4) for details.
1254 __FreeBSD_version 800054 adds memory barriers to
1255 <machine/atomic.h>, new interfaces to ifnet to facilitate
1256 multiple hardware transmit queues for cards that support
1257 them, and a lock-less ring-buffer implementation to
1258 enable drivers to more efficiently manage queueing of
1262 A new version of ZFS (version 13) has been merged to -HEAD.
1263 This version has zpool attribute "listsnapshots" off by
1264 default, which means "zfs list" does not show snapshots,
1265 and is the same as Solaris behavior.
1268 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1271 The uhci, ohci, ehci and slhci USB Host controller drivers have
1272 been put into separate modules. If you load the usb module
1273 separately through loader.conf you will need to load the
1274 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1275 controller add the following to loader.conf:
1281 The ABI used by the PMC toolset has changed. Please keep
1282 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1286 atapci kernel module now includes only generic PCI ATA
1287 driver. AHCI driver moved to ataahci kernel module.
1288 All vendor-specific code moved into separate kernel modules:
1289 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1290 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1291 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1292 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1295 The TTY subsystem of the kernel has been replaced by a new
1296 implementation, which provides better scalability and an
1297 improved driver model. Most common drivers have been migrated to
1298 the new TTY subsystem, while others have not. The following
1299 drivers have not yet been ported to the new TTY layer:
1302 cy, digi, rc, rp, sio
1308 ng_h4, ng_tty, ppp, sl, snp
1310 Adding these drivers to your kernel configuration file shall
1311 cause compilation to fail.
1314 ntpd has been upgraded to 4.2.4p5.
1317 OpenSSH has been upgraded to 5.1p1.
1319 For many years, FreeBSD's version of OpenSSH preferred DSA
1320 over RSA for host and user authentication keys. With this
1321 upgrade, we've switched to the vendor's default of RSA over
1322 DSA. This may cause upgraded clients to warn about unknown
1323 host keys even for previously known hosts. Users should
1324 follow the usual procedure for verifying host keys before
1325 accepting the RSA key.
1327 This can be circumvented by setting the "HostKeyAlgorithms"
1328 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1331 Please note that the sequence of keys offered for
1332 authentication has been changed as well. You may want to
1333 specify IdentityFile in a different order to revert this
1337 The sio(4) driver has been removed from the i386 and amd64
1338 kernel configuration files. This means uart(4) is now the
1339 default serial port driver on those platforms as well.
1341 To prevent collisions with the sio(4) driver, the uart(4) driver
1342 uses different names for its device nodes. This means the
1343 onboard serial port will now most likely be called "ttyu0"
1344 instead of "ttyd0". You may need to reconfigure applications to
1345 use the new device names.
1347 When using the serial port as a boot console, be sure to update
1348 /boot/device.hints and /etc/ttys before booting the new kernel.
1349 If you forget to do so, you can still manually specify the hints
1350 at the loader prompt:
1352 set hint.uart.0.at="isa"
1353 set hint.uart.0.port="0x3F8"
1354 set hint.uart.0.flags="0x10"
1355 set hint.uart.0.irq="4"
1359 The gpt(8) utility has been removed. Use gpart(8) to partition
1363 The version that Linuxulator emulates was changed from 2.4.2
1364 to 2.6.16. If you experience any problems with Linux binaries
1365 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1366 if it fixes the problem contact emulation mailing list.
1369 ISDN4BSD (I4B) was removed from the src tree. You may need to
1370 update a your kernel configuration and remove relevant entries.
1373 I have checked in code to support multiple routing tables.
1374 See the man pages setfib(1) and setfib(2).
1375 This is a hopefully backwards compatible version,
1376 but to make use of it you need to compile your kernel
1377 with options ROUTETABLES=2 (or more up to 16).
1380 The 802.11 wireless support was redone to enable multi-bss
1381 operation on devices that are capable. The underlying device
1382 is no longer used directly but instead wlanX devices are
1383 cloned with ifconfig. This requires changes to rc.conf files.
1384 For example, change:
1385 ifconfig_ath0="WPA DHCP"
1388 ifconfig_wlan0="WPA DHCP"
1389 see rc.conf(5) for more details. In addition, mergemaster of
1390 /etc/rc.d is highly recommended. Simultaneous update of userland
1391 and kernel wouldn't hurt either.
1393 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1394 modules were merged into the base wlan module. All references
1395 to these modules (e.g. in kernel config files) must be removed.
1398 psm(4) has gained write(2) support in native operation level.
1399 Arbitrary commands can be written to /dev/psm%d and status can
1400 be read back from it. Therefore, an application is responsible
1401 for status validation and error recovery. It is a no-op in
1402 other operation levels.
1405 Support for KSE threading has been removed from the kernel. To
1406 run legacy applications linked against KSE libmap.conf may
1407 be used. The following libmap.conf may be used to ensure
1408 compatibility with any prior release:
1410 libpthread.so.1 libthr.so.1
1411 libpthread.so.2 libthr.so.2
1412 libkse.so.3 libthr.so.3
1415 The layout of struct vmspace has changed. This affects libkvm
1416 and any executables that link against libkvm and use the
1417 kvm_getprocs() function. In particular, but not exclusively,
1418 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1419 The effects are minimal, but it's advisable to upgrade world
1423 The latest em driver no longer has support in it for the
1424 82575 adapter, this is now moved to the igb driver. The
1425 split was done to make new features that are incompatible
1426 with older hardware easier to do.
1429 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1430 likewise the kernel option is now GEOM_LINUX_LVM.
1433 The default NFS mount mode has changed from UDP to TCP for
1434 increased reliability. If you rely on (insecurely) NFS
1435 mounting across a firewall you may need to update your
1439 Belatedly note the addition of m_collapse for compacting
1443 The fts(3) structures have been changed to use adequate
1444 integer types for their members and so to be able to cope
1445 with huge file trees. The old fts(3) ABI is preserved
1446 through symbol versioning in libc, so third-party binaries
1447 using fts(3) should still work, although they will not take
1448 advantage of the extended types. At the same time, some
1449 third-party software might fail to build after this change
1450 due to unportable assumptions made in its source code about
1451 fts(3) structure members. Such software should be fixed
1452 by its vendor or, in the worst case, in the ports tree.
1453 FreeBSD_version 800015 marks this change for the unlikely
1454 case that a portable fix is impossible.
1457 To upgrade to -current after this date, you must be running
1458 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1459 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1462 The ADAPTIVE_GIANT kernel option has been retired because its
1463 functionality is the default now.
1466 The AT keyboard emulation of sunkbd(4) has been turned on
1467 by default. In order to make the special symbols of the Sun
1468 keyboards driven by sunkbd(4) work under X these now have
1469 to be configured the same way as Sun USB keyboards driven
1470 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1472 Option "XkbLayout" "us"
1473 Option "XkbRules" "xorg"
1474 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1477 It has been decided that it is desirable to provide ABI
1478 backwards compatibility to the FreeBSD 4/5/6 versions of the
1479 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1480 broken with the introduction of PCI domain support (see the
1481 20070930 entry). Unfortunately, this required the ABI of
1482 PCIOCGETCONF to be broken again in order to be able to
1483 provide backwards compatibility to the old version of that
1484 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1485 again. As for prominent ports this affects neither pciutils
1486 nor xorg-server this time, the hal port needs to be rebuilt
1490 The misnamed kthread_create() and friends have been renamed
1491 to kproc_create() etc. Many of the callers already
1492 used kproc_start()..
1493 I will return kthread_create() and friends in a while
1494 with implementations that actually create threads, not procs.
1495 Renaming corresponds with version 800002.
1504 Avoid using make -j when upgrading. While generally safe, there are
1505 sometimes problems using -j to upgrade. If your upgrade fails with
1506 -j, please try again without -j. From time to time in the past there
1507 have been problems using -j with buildworld and/or installworld. This
1508 is especially true when upgrading between "distant" versions (eg one
1509 that cross a major release boundary or several minor releases, or when
1510 several months have passed on the -current branch).
1512 Sometimes, obscure build problems are the result of environment
1513 poisoning. This can happen because the make utility reads its
1514 environment when searching for values for global variables. To run
1515 your build attempts in an "environmental clean room", prefix all make
1516 commands with 'env -i '. See the env(1) manual page for more details.
1518 When upgrading from one major version to another it is generally best
1519 to upgrade to the latest code in the currently installed branch first,
1520 then do an upgrade to the new branch. This is the best-tested upgrade
1521 path, and has the highest probability of being successful. Please try
1522 this approach before reporting problems with a major version upgrade.
1526 When upgrading the boot ZFS pool to a new version, always follow
1529 1.) recompile and reinstall the ZFS boot loader and boot block
1530 (this is part of "make buildworld" and "make installworld")
1532 2.) update the ZFS boot block on your boot drive
1534 The following example updates the ZFS boot block on the first
1535 partition (freebsd-boot) of a GPT partitioned drive ad0:
1536 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1538 Non-boot pools do not need these updates.
1542 If you are updating from a prior version of FreeBSD (even one just
1543 a few days old), you should follow this procedure. It is the most
1544 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1546 make kernel-toolchain
1547 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1548 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1550 To test a kernel once
1551 ---------------------
1552 If you just want to boot a kernel once (because you are not sure
1553 if it works, or if you want to boot a known bad kernel to provide
1554 debugging information) run
1555 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1556 nextboot -k testkernel
1558 To just build a kernel when you know that it won't mess you up
1559 --------------------------------------------------------------
1560 This assumes you are already running a CURRENT system. Replace
1561 ${arch} with the architecture of your machine (e.g. "i386",
1562 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1564 cd src/sys/${arch}/conf
1565 config KERNEL_NAME_HERE
1566 cd ../compile/KERNEL_NAME_HERE
1571 If this fails, go to the "To build a kernel" section.
1573 To rebuild everything and install it on the current system.
1574 -----------------------------------------------------------
1575 # Note: sometimes if you are running current you gotta do more than
1576 # is listed here if you are upgrading from a really old current.
1578 <make sure you have good level 0 dumps>
1580 make kernel KERNCONF=YOUR_KERNEL_HERE
1582 <reboot in single user> [3]
1590 To cross-install current onto a separate partition
1591 --------------------------------------------------
1592 # In this approach we use a separate partition to hold
1593 # current's root, 'usr', and 'var' directories. A partition
1594 # holding "/", "/usr" and "/var" should be about 2GB in
1597 <make sure you have good level 0 dumps>
1600 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1601 <maybe newfs current's root partition>
1602 <mount current's root partition on directory ${CURRENT_ROOT}>
1603 make installworld DESTDIR=${CURRENT_ROOT}
1604 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1605 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1606 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1607 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1608 <reboot into current>
1609 <do a "native" rebuild/install as described in the previous section>
1610 <maybe install compatibility libraries from ports/misc/compat*>
1614 To upgrade in-place from stable to current
1615 ----------------------------------------------
1616 <make sure you have good level 0 dumps>
1618 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1620 <reboot in single user> [3]
1627 Make sure that you've read the UPDATING file to understand the
1628 tweaks to various things you need. At this point in the life
1629 cycle of current, things change often and you are on your own
1630 to cope. The defaults can also change, so please read ALL of
1631 the UPDATING entries.
1633 Also, if you are tracking -current, you must be subscribed to
1634 freebsd-current@freebsd.org. Make sure that before you update
1635 your sources that you have read and understood all the recent
1636 messages there. If in doubt, please track -stable which has
1637 much fewer pitfalls.
1639 [1] If you have third party modules, such as vmware, you
1640 should disable them at this point so they don't crash your
1643 [3] From the bootblocks, boot -s, and then do
1648 adjkerntz -i # if CMOS is wall time
1649 Also, when doing a major release upgrade, it is required that
1650 you boot into single user mode to do the installworld.
1652 [4] Note: This step is non-optional. Failure to do this step
1653 can result in a significant reduction in the functionality of the
1654 system. Attempting to do it by hand is not recommended and those
1655 that pursue this avenue should read this file carefully, as well
1656 as the archives of freebsd-current and freebsd-hackers mailing lists
1657 for potential gotchas. The -U option is also useful to consider.
1658 See mergemaster(8) for more information.
1660 [5] Usually this step is a noop. However, from time to time
1661 you may need to do this if you get unknown user in the following
1662 step. It never hurts to do it all the time. You may need to
1663 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1664 install) after the buildworld before this step if you last updated
1665 from [78]-stable or 9-stable before 20130430.
1667 [6] This only deletes old files and directories. Old libraries
1668 can be deleted by "make delete-old-libs", but you have to make
1669 sure that no program is using those libraries anymore.
1671 [8] In order to have a kernel that can run the 4.x binaries needed to
1672 do an installworld, you must include the COMPAT_FREEBSD4 option in
1673 your kernel. Failure to do so may leave you with a system that is
1674 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1675 required to run the 5.x binaries on more recent kernels. And so on
1676 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1678 Make sure that you merge any new devices from GENERIC since the
1679 last time you updated your kernel config file.
1681 [9] When checking out sources, you must include the -P flag to have
1682 cvs prune empty directories.
1684 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1685 "?=" instead of the "=" assignment operator, so that buildworld can
1686 override the CPUTYPE if it needs to.
1688 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1689 not on the command line, or in /etc/make.conf. buildworld will
1690 warn if it is improperly defined.
1693 This file contains a list, in reverse chronological order, of major
1694 breakages in tracking -current. It is not guaranteed to be a complete
1695 list of such breakages, and only contains entries since October 10, 2007.
1696 If you need to see UPDATING entries from before that date, you will need
1697 to fetch an UPDATING file from an older FreeBSD release.
1699 Copyright information:
1701 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1703 Redistribution, publication, translation and use, with or without
1704 modification, in full or in part, in any form or format of this
1705 document are permitted without further permission from the author.
1707 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1708 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1709 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1710 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1711 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1712 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1713 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1714 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1715 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1716 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1717 POSSIBILITY OF SUCH DAMAGE.
1719 Contact Warner Losh if you have any questions about your use of