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 Items affecting the ports and packages system can be found in
10 /usr/ports/UPDATING. Please read that file before running portupgrade.
12 20141021: p20 FreeBSD-SA-14:20.rtsold
13 FreeBSD-SA-14:21.routed
14 FreeBSD-SA-14:22.namei
15 FreeBSD-SA-14:23.openssl
17 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
19 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
21 Fix memory leak in sandboxed namei lookup. [SA-14:22]
23 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
25 20140916: p19 FreeBSD-SA-14:19.tcp
26 Fix Denial of Service in TCP packet processing. [SA-14:19]
28 20140909: p18 FreeBSD-SA-14:18.openssl
29 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
31 20140708: p17 FreeBSD-SA-14:17.kmem
32 Fix kernel memory disclosure in control messages and SCTP
33 notifications. [SA-14:17]
35 20140624: p16 FreeBSD-SA-14:16.file
36 FreeBSD-EN-14:08.heimdal
38 Fix multiple vulnerabilities in file(1) and libmagic(3).
41 Fix gss_pseudo_random interoperability issue. [EN-14:08]
43 20140605: p15 FreeBSD-SA-14:14.openssl
44 Fix OpenSSL multiple vulnerabilities. [SA-14:14]
46 20140603: p14 FreeBSD-SA-14:11.sendmail
47 FreeBSD-SA-14:12.ktrace
51 Fix sendmail improper close-on-exec flag handling. [SA-14:11]
53 Fix ktrace memory disclosure. [SA-14:12]
55 Fix incorrect error handling in PAM policy parser. [SA-14:13]
57 Fix triple-fault when executing from a threaded process.
60 20140513: p13 FreeBSD-EN-14:03.pkg
61 FreeBSD-EN-14:04.kldxref
64 Add pkg bootstrapping, configuration and public keys. [EN-14:03]
66 Improve build repeatability for kldxref(8). [EN-14:04]
68 Fix data corruption with ciss(4). [EN-14:05]
70 20140430: p12 FreeBSD-SA-14:08.tcp
72 Fix TCP reassembly vulnerability. [SA-14:08]
74 20140408: p11 FreeBSD-SA-14:05.nfsserver
75 FreeBSD-SA-14:06.openssl
76 Fix deadlock in the NFS server. [SA-14:05]
78 Fix for ECDSA Cache Side-channel Attack in OpenSSL. [SA-14:06]
80 20140114: p10 FreeBSD-SA-14:01.bsnmpd
83 FreeBSD-EN-14:01.random
85 Fix bsnmpd remote denial of service vulnerability. [SA-14:01]
87 Fix ntpd distributed reflection Denial of Service
88 vulnerability. [SA-14:02]
90 Fix BIND remote denial of service vulnerability. [SA-14:04]
92 Disable hardware RNGs by default. [EN-14:01]
94 Fix incorrect coalescing of stack entry with mmap. [EN-14:02]
96 20131128: p9 FreeBSD-EN-13:05.freebsd-update
97 Fix error in patch for FreeBSD-EN-13:04.freebsd-update.
99 20131026: p8 FreeBSD-EN-13:04.freebsd-update
100 Fix multiple freebsd-update bugs that break upgrading to
103 20130910: p7 FreeBSD-SA-13:12.ifioctl
104 FreeBSD-SA-13:13.nullfs
106 In IPv6 and NetATM, stop SIOCSIFADDR, SIOCSIFBRDADDR,
107 SIOCSIFDSTADDR and SIOCSIFNETMASK at the socket layer rather
108 than pass them on to the link layer without validation or
109 credential checks. [SA-13:12]
111 Prevent cross-mount hardlinks between different nullfs mounts
112 of the same underlying filesystem. [SA-13:13]
114 20130822: p6 FreeBSD-SA-13:09.ip_multicast
115 FreeBSD-SA-13:10.sctp
117 Fix an integer overflow in computing the size of a temporary buffer
118 can result in a buffer which is too small for the requested
121 Fix a bug that could lead to kernel memory disclosure with
122 SCTP state cookie. [13:10]
124 Fix a data corruption problem with mfi(4) operating on > 2TB
125 disks in a JBOD. [EN-13:03]
127 20130726: p5 FreeBSD-SA-13:07.bind FreeBSD-SA-13:08.nfsserver
128 Fix Denial of Service vulnerability in named(8). [13:07]
130 Fix a bug that allows remote client bypass the normal
131 access checks when when -network or -host restrictions are
132 used at the same time with -mapall. [13:08]
134 20130618: p4 FreeBSD-SA-13:06.mmap
135 Fix a bug that allowed a tracing process (e.g. gdb) to write
136 to a memory-mapped file in the traced process's address space
137 even if neither the traced process nor the tracing process had
138 write access to that file.
140 20130429: p3 FreeBSD-SA-13:05.nfsserver
141 Fix a bug that allows NFS clients to issue READDIR on files.
143 20130402: p2 FreeBSD-SA-13:03.openssl FreeBSD-SA-13:04.bind
144 Fix multiple vulnerabilities in OpenSSL.
146 Fix Denial of Service vulnerability in named(8).
148 20130218: p1 FreeBSD-SA-13:01.bind FreeBSD-SA-13:02.libc
149 Fix Denial of Service vulnerability in named(8) with DNS64.
151 Fix Denial of Service vulnerability in libc's glob(3) functionality.
157 The sparc64 ZFS loader has been changed to no longer try to auto-
158 detect ZFS providers based on diskN aliases but now requires these
159 to be explicitly listed in the OFW boot-device environment variable.
162 Now unix domain sockets behave "as expected" on nullfs(5). Previously
163 nullfs(5) did not pass through all behaviours to the underlying layer,
164 as a result if we bound to a socket on the lower layer we could connect
165 only to the lower path; if we bound to the upper layer we could connect
166 only to the upper path. The new behavior is one can connect to both the
167 lower and the upper paths regardless what layer path one binds to.
170 The acpi_wmi(4) status device /dev/wmistat has been renamed to
174 A new VOP_ADVISE() was added to support posix_fadvise(2). All
175 filesystem modules must be recompiled.
178 The interface of the VOP_VPTOCNP(9) changed, now the returned
179 vnode shall be referenced, previously it was required to be
180 only held. All in-tree filesystems are converted.
186 The broken amd(4) driver has been replaced with esp(4) in the amd64,
187 i386 and pc98 GENERIC kernel configuration files.
190 This commit modifies vfs_register() so that it uses a hash
191 calculation to set vfc_typenum, which is enabled by default.
192 The first time a system is booted after this change, the
193 vfc_typenum values will change for all file systems. The
194 main effect of this is a change to the NFS server file handles
195 for file systems that use vfc_typenum in their fsid, such as ZFS.
196 It will, however, prevent vfc_typenum from changing when file
197 systems are loaded in a different order for subsequent reboots.
198 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
199 until you are ready to remount all NFS clients after a reboot.
202 Bump the shared library version numbers for libraries that
203 do not use symbol versioning, have changed the ABI compared
204 to stable/8 and which shared library version was not bumped.
205 Done as part of 9.0-RELEASE cycle.
208 During the merge of Capsicum features, the fget(9) KPI was modified.
209 This may require the rebuilding of out-of-tree device drivers --
210 issues have been reported specifically with the nVidia device driver.
211 __FreeBSD_version is bumped to 900041.
213 Also, there is a period between 20110811 and 20110814 where the
214 special devices /dev/{stdin,stdout,stderr} did not work correctly.
215 Building world from a kernel during that window may not work.
218 The packet filter (pf) code has been updated to OpenBSD 4.5.
219 You need to update userland tools to be in sync with kernel.
220 This update breaks backward compatibility with earlier pfsync(4)
221 versions. Care must be taken when updating redundant firewall setups.
224 The following sysctls and tunables are retired on x86 platforms:
226 machdep.hlt_logical_cpus
227 The following sysctl is retired:
228 machdep.hyperthreading_allowed
229 The sysctls were supposed to provide a way to dynamically offline and
230 online selected CPUs on x86 platforms, but the implementation has not
231 been reliable especially with SCHED_ULE scheduler.
232 machdep.hyperthreading_allowed tunable is still available to ignore
233 hyperthreading CPUs at OS level.
234 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
235 where X is an APIC ID of a CPU. Be advised, though, that disabling
236 CPUs in non-uniform fashion will result in non-uniform topology and
237 may lead to sub-optimal system performance with SCHED_ULE, which is
241 cpumask_t type is retired and cpuset_t is used in order to describe
245 Changes to ifconfig(8) for dynamic address family detection mandate
246 that you are running a kernel of 20110525 or later. Make sure to
247 follow the update procedure to boot a new kernel before installing
251 Support for sun4v architecture is officially dropped
254 Several KPI breaking changes have been committed to the mii(4) layer,
255 the PHY drivers and consequently some Ethernet drivers using mii(4).
256 This means that miibus.ko and the modules of the affected Ethernet
257 drivers need to be recompiled.
259 Note to kernel developers: Given that the OUI bit reversion problem
260 was fixed as part of these changes all mii(4) commits related to OUIs,
261 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
262 handling, no longer can be merged verbatim to stable/8 and previous
266 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
267 into their kernel configurations along with 'device pci'.
270 The default NFS client is now the new NFS client, so fstype "newnfs"
271 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
272 Although mounts via fstype "nfs" will usually work without userland
273 changes, it is recommended that the mount(8) and mount_nfs(8)
274 commands be rebuilt from sources and that a link to mount_nfs called
275 mount_oldnfs be created. The new client is compiled into the
276 kernel with "options NFSCL" and this is needed for diskless root
277 file systems. The GENERIC kernel configs have been changed to use
278 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
279 To use the regular/old client, you can "mount -t oldnfs ...". For
280 a diskless root file system, you must also include a line like:
282 vfs.root.mountfrom="oldnfs:"
284 in the boot/loader.conf on the root fs on the NFS server to make
285 a diskless root fs use the old client.
288 The GENERIC kernels for all architectures now default to the new
289 CAM-based ATA stack. It means that all legacy ATA drivers were
290 removed and replaced by respective CAM drivers. If you are using
291 ATA device names in /etc/fstab or other places, make sure to update
292 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
293 where 'Y's are the sequential numbers starting from zero for each type
294 in order of detection, unless configured otherwise with tunables,
295 see cam(4)). There will be symbolic links created in /dev/ to map
296 old adX devices to the respective adaY. They should provide basic
297 compatibility for file systems mounting in most cases, but they do
298 not support old user-level APIs and do not have respective providers
299 in GEOM. Consider using updated management tools with new device names.
301 It is possible to load devices ahci, ata, siis and mvs as modules,
302 but option ATA_CAM should remain in kernel configuration to make ata
303 module work as CAM driver supporting legacy ATA controllers. Device ata
304 still can be used in modular fashion (atacore + ...). Modules atadisk
305 and atapi* are not used and won't affect operation in ATA_CAM mode.
306 Note that to use CAM-based ATA kernel should include CAM devices
307 scbus, pass, da (or explicitly ada), cd and optionally others. All of
308 them are parts of the cam module.
310 ataraid(4) functionality is now supported by the RAID GEOM class.
311 To use it you can load geom_raid kernel module and use graid(8) tool
312 for management. Instead of /dev/arX device names, use /dev/raid/rX.
314 No kernel config options or code have been removed, so if a problem
315 arises, please report it and optionally revert to the old ATA stack.
316 In order to do it you can remove from the kernel config:
321 , and instead add back:
322 device atadisk # ATA disk drives
323 device ataraid # ATA RAID drives
324 device atapicd # ATAPI CDROM drives
325 device atapifd # ATAPI floppy drives
326 device atapist # ATAPI tape drives
329 The default NFS server has been changed to the new server, which
330 was referred to as the experimental server. If you need to switch
331 back to the old NFS server, you must now put the "-o" option on
332 both the mountd and nfsd commands. This can be done using the
333 mountd_flags and nfs_server_flags rc.conf variables until an
334 update to the rc scripts is committed, which is coming soon.
337 The GNU Objective-C runtime library (libobjc), and other Objective-C
338 related components have been removed from the base system. If you
339 require an Objective-C library, please use one of the available ports.
342 ath(4) has been split into bus- and device- modules. if_ath contains
343 the HAL, the TX rate control and the network device code. if_ath_pci
344 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
345 contains the AHB glue. Users need to load both if_ath_pci and if_ath
346 in order to use ath on everything else.
348 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
349 need to load if_ath and if_ath_pci for ath(4) operation.
352 As part of the replacement of sysinstall, the process of building
353 release media has changed significantly. For details, please re-read
354 release(7), which has been updated to reflect the new build process.
357 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
358 is the last available version under GPLv2. It brings a number of new
359 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
360 4.1 and SSE 4.2), better support for powerpc64, a number of new
361 directives, and lots of other small improvements. See the ChangeLog
362 file in contrib/binutils for the full details.
365 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
366 compliant, and will now use half of hash for authentication.
367 This will break interoperability with all stacks (including all
368 actual FreeBSD versions) who implement
369 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
371 The only workaround with such peers is to use another HMAC
372 algorithm for IPsec ("phase 2") authentication.
375 Remove the uio_yield prototype and symbol. This function has
376 been misnamed since it was introduced and should not be
377 globally exposed with this name. The equivalent functionality
378 is now available using kern_yield(curthread->td_user_pri).
379 The function remains undocumented.
382 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
383 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
384 for scalar sysctls is defined but disabled. Code that needs
385 UQUAD to pass the type checking that must compile on older
386 systems where the define is not present can check against
387 __FreeBSD_version >= 900030.
389 The system dialog(1) has been replaced with a new version previously
390 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
391 with the previous version, but the libdialog associated with it has
392 a largely incompatible API. As such, the original version of libdialog
393 will be kept temporarily as libodialog, until its base system consumers
394 are replaced or updated. Bump __FreeBSD_version to 900030.
397 If you are trying to run make universe on a -stable system, and you get
398 the following warning:
399 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
400 unknown. config(8) likely too old."
401 or something similar to it, then you must upgrade your -stable system
402 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
403 stable/8) or build the config from the latest stable/8 branch and
404 install it on your system.
406 Prior to this date, building a current universe on 8-stable system from
407 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
408 error in the first kernel build phase. A new config on those old
409 systems will fix that problem for older versions of -current.
412 The TCP stack has been modified to allow Khelp modules to interact with
413 it via helper hook points and store per-connection data in the TCP
414 control block. Bump __FreeBSD_version to 900029. User space tools that
415 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
419 Generic IEEE 802.3 annex 31B full duplex flow control support has been
420 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
421 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
422 to take advantage of it instead of using custom implementations. This
423 means that these drivers now no longer unconditionally advertise
424 support for flow control but only do so if flow control is a selected
425 media option. This was implemented in the generic support that way in
426 order to allow flow control to be switched on and off via ifconfig(8)
427 with the PHY specific default to typically off in order to protect
428 from unwanted effects. Consequently, if you used flow control with
429 one of the above mentioned drivers you now need to explicitly enable
431 ifconfig bge0 media auto mediaopt flowcontrol
433 Along with the above mentioned changes generic support for setting
434 1000baseT master mode also has been added and brgphy(4), ciphy(4),
435 e1000phy(4) as well as ip1000phy(4) have been converted to take
436 advantage of it. This means that these drivers now no longer take the
437 link0 parameter for selecting master mode but the master media option
438 has to be used instead, for example like in the following:
439 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
441 Selection of master mode now is also available with all other PHY
442 drivers supporting 1000baseT.
445 The TCP stack has received a significant update to add support for
446 modularised congestion control and generally improve the clarity of
447 congestion control decisions. Bump __FreeBSD_version to 900025. User
448 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
449 sockstat) need to be recompiled.
452 The man(1) utility has been replaced by a new version that no longer
453 uses /etc/manpath.config. Please consult man.conf(5) for how to
454 migrate local entries to the new format.
457 The copyright strings printed by login(1) and sshd(8) at the time of a
458 new connection have been removed to follow other operating systems and
462 A workaround for a fixed ld bug has been removed in kernel code,
463 so make sure that your system ld is built from sources after
464 revision 210245 from 2010-07-19 (r211583 if building head kernel
465 on stable/8, r211584 for stable/7; both from 2010-08-21).
466 A symptom of incorrect ld version is different addresses for
467 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
470 The $ipv6_prefer variable in rc.conf(5) has been split into
471 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
473 The $ip6addrctl_policy is a variable to choose a pre-defined
474 address selection policy set by ip6addrctl(8). A value
475 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
478 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
479 flag (see an entry of 20090926) is set on an interface with no
480 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
481 security reason. If you want IPv6 link-local address on all
482 interfaces by default, set this to "YES".
484 The old ipv6_prefer="YES" is equivalent to
485 ipv6_activate_all_interfaces="YES" and
486 ip6addrctl_policy="ipv6_prefer".
489 DTrace has grown support for userland tracing. Due to this, DTrace is
490 now i386 and amd64 only.
491 dtruss(1) is now installed by default on those systems and a new
492 kernel module is needed for userland tracing: fasttrap.
493 No changes to your kernel config file are necessary to enable
494 userland tracing, but you might consider adding 'STRIP=' and
495 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
496 to have informative userland stack traces in DTrace (ustack).
499 The acpi_aiboost(4) driver has been removed in favor of the new
500 aibs(4) driver. You should update your kernel configuration file.
503 BSD grep has been imported to the base system and it is built by
504 default. It is completely BSD licensed, highly GNU-compatible, uses
505 less memory than its GNU counterpart and has a small codebase.
506 However, it is slower than its GNU counterpart, which is mostly
507 noticeable for larger searches, for smaller ones it is measurable
508 but not significant. The reason is complex, the most important factor
509 is that we lack a modern and efficient regex library and GNU
510 overcomes this by optimizing the searches internally. Future work
511 on improving the regex performance is planned, for the meantime,
512 users that need better performance, can build GNU grep instead by
513 setting the WITH_GNU_GREP knob.
516 Due to the import of powerpc64 support, all existing powerpc kernel
517 configuration files must be updated with a machine directive like this:
518 machine powerpc powerpc
520 In addition, an updated config(8) is required to build powerpc kernels
524 A new version of ZFS (version 15) has been merged to -HEAD.
525 This version uses a python library for the following subcommands:
526 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
527 For full functionality of these commands the following port must
528 be installed: sysutils/py-zfs
531 'vm_page's are now hashed by physical address to an array of mutexes.
532 Currently this is only used to serialize access to hold_count. Over
533 time the page queue mutex will be peeled away. This changes the size
534 of pmap on every architecture. And requires all callers of vm_page_hold
535 and vm_page_unhold to be updated.
538 WITH_CTF can now be specified in src.conf (not recommended, there
539 are some problems with static executables), make.conf (would also
540 affect ports which do not use GNU make and do not override the
541 compile targets) or in the kernel config (via "makeoptions
543 When WITH_CTF was specified there before this was silently ignored,
544 so make sure that WITH_CTF is not used in places which could lead
545 to unwanted behavior.
548 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
549 to allow 32-bit compatibility on non-x86 platforms. All kernel
550 configurations on amd64 and ia64 platforms using these options must
551 be modified accordingly.
554 The utmp user accounting database has been replaced with utmpx,
555 the user accounting interface standardized by POSIX.
556 Unfortunately the semantics of utmp and utmpx don't match,
557 making it practically impossible to support both interfaces.
558 The user accounting database is used by tools like finger(1),
559 last(1), talk(1), w(1) and ac(8).
561 All applications in the base system use utmpx. This means only
562 local binaries (e.g. from the ports tree) may still use these
563 utmp database files. These applications must be rebuilt to make
566 After the system has been upgraded, it is safe to remove the old
567 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
568 assuming their contents is of no importance anymore. Old wtmp
569 databases can only be used by last(1) and ac(8) after they have
570 been converted to the new format using wtmpcvt(1).
573 Introduce the kernel thread "deadlock resolver" (which can be enabled
574 via the DEADLKRES option, see NOTES for more details) and the
575 sleepq_type() function for sleepqueues.
578 The rc.firewall and rc.firewall6 were unified, and
579 rc.firewall6 and rc.d/ip6fw were removed.
580 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
581 variables are obsoleted. Instead, the following new rc
582 variables are added to rc.d/ipfw:
584 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
585 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
586 firewall_simple_onet_ipv6, firewall_trusted_ipv6
588 The meanings correspond to the relevant IPv4 variables.
594 The default terminal emulation for syscons(4) has been changed
595 from cons25 to xterm on all platforms except pc98. This means
596 that the /etc/ttys file needs to be updated to ensure correct
597 operation of applications on the console.
599 The terminal emulation style can be toggled per window by using
600 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
601 options can be used to change the compile-time default back to
604 To prevent graphical artifacts, make sure the TERM environment
605 variable is set to match the terminal emulation that is being
606 performed by syscons(4).
609 The layout of the structure ieee80211req_scan_result has changed.
610 Applications that require wireless scan results (e.g. ifconfig(8))
611 from net80211 need to be recompiled.
613 Applications such as wpa_supplicant(8) may require a full world
614 build without using NO_CLEAN in order to get synchronized with the
618 The iwn(4) driver has been updated to support the 5000 and 5150 series.
619 There's one kernel module for each firmware. Adding "device iwnfw"
620 to the kernel configuration file means including all three firmware
621 images inside the kernel. If you want to include just the one for
622 your wireless card, use the devices iwn4965fw, iwn5000fw or
626 The rc.d/network_ipv6, IPv6 configuration script has been integrated
627 into rc.d/netif. The changes are the following:
629 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
630 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
631 Note that both variables need the "inet6" keyword at the head.
633 Do not set $ipv6_network_interfaces manually if you do not
634 understand what you are doing. It is not needed in most cases.
636 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
639 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
640 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
642 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
643 all configured interfaces have "inet6 accept_rtadv" in the
644 $ifconfig_IF_ipv6. These are for backward compatibility.
646 3. A new variable $ipv6_prefer has been added. If NO, IPv6
647 functionality of interfaces with no corresponding
648 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
649 and the default address selection policy of ip6addrctl(8)
650 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
651 Note that if you want to configure IPv6 functionality on the
652 disabled interfaces after boot, first you need to clear the flag by
653 using ifconfig(8) like:
655 ifconfig em0 inet6 -ifdisabled
657 If YES, the default address selection policy is set as
660 The default value of $ipv6_prefer is NO.
662 4. If your system need to receive Router Advertisement messages,
663 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
664 scripts automatically invoke rtsol(8) when the interface becomes
665 UP. The Router Advertisement messages are used for SLAAC
666 (State-Less Address AutoConfiguration).
669 802.11s D3.03 support was committed. This is incompatible with the
670 previous code, which was based on D3.0.
673 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
674 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
675 control whether accepting Router Advertisement messages or not.
676 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
677 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
678 The ifconfig(8) utility now supports these flags.
681 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
682 mount(8) and -a option for df(1) to see them.
685 The old tunable hw.bus.devctl_disable has been superseded by
686 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
687 replaced by hw.bus.devctl_queue=0. The default for this new tunable
691 Remove the option STOP_NMI. The default action is now to use NMI only
692 for KDB via the newly introduced function stop_cpus_hard() and
693 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
696 The stable/8 branch created in subversion. This corresponds to the
697 RELENG_8 branch in CVS.
700 Bump the shared library version numbers for all libraries that do not
701 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
702 __FreeBSD_version to 800105.
705 Due to changes in the implementation of virtual network stack support,
706 all network-related kernel modules must be recompiled. As this change
707 breaks the ABI, bump __FreeBSD_version to 800104.
710 The TOE interface to the TCP syncache has been modified to remove
711 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
712 The cxgb driver is the only TOE consumer affected by this change, and
713 needs to be recompiled along with the kernel. As this change breaks
714 the ABI, bump __FreeBSD_version to 800103.
717 Padding has been added to struct tcpcb, sackhint and tcpstat in
718 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
719 maintaining the ABI. However, this change breaks the ABI, so bump
720 __FreeBSD_version to 800102. User space tools that rely on the size of
721 any of these structs (e.g. sockstat) need to be recompiled.
724 The NFS_LEGACYRPC option has been removed along with the old kernel
725 RPC implementation that this option selected. Kernel configurations
726 may need to be adjusted.
729 The network interface device nodes at /dev/net/<interface> have been
730 removed. All ioctl operations can be performed the normal way using
731 routing sockets. The kqueue functionality can generally be replaced
732 with routing sockets.
735 The documentation from the FreeBSD Documentation Project (Handbook,
736 FAQ, etc.) is now installed via packages by sysinstall(8) and under
737 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
740 The ABI of various structures related to the SYSV IPC API have been
741 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
742 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
746 Layout of struct vnet has changed as routing related variables were
747 moved to their own Vimage module. Modules need to be recompiled. Bump
748 __FreeBSD_version to 800099.
751 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
752 respectively. As long as no more than 16 groups per process are used,
753 no changes should be visible. When more than 16 groups are used, old
754 binaries may fail if they call getgroups() or getgrouplist() with
755 statically sized storage. Recompiling will work around this, but
756 applications should be modified to use dynamically allocated storage
757 for group arrays as POSIX.1-2008 does not cap an implementation's
758 number of supported groups at NGROUPS_MAX+1 as previous versions did.
760 NFS and portalfs mounts may also be affected as the list of groups is
761 truncated to 16. Users of NFS who use more than 16 groups, should
762 take care that negative group permissions are not used on the exported
763 file systems as they will not be reliable unless a GSSAPI based
764 authentication method is used.
767 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
768 option compiles in the support for adaptive spinning for lockmgrs
769 which want to enable it. The lockinit() function now accepts the flag
770 LK_ADAPTIVE in order to make the lock object subject to adaptive
771 spinning when both held in write and read mode.
774 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
775 changed. User applications that use this ioctl need to be rebuilt.
778 The layout of struct thread has changed. Kernel and modules need to
782 The layout of structs ifnet, domain, protosw and vnet_net has changed.
783 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
786 window(1) has been removed from the base system. It can now be
787 installed from ports. The port is called misc/window.
790 The way we are storing and accessing `routing table' entries has
791 changed. Programs reading the FIB, like netstat, need to be
795 A new netisr implementation has been added for FreeBSD 8. Network
796 file system modules, such as igmp, ipdivert, and others, should be
798 Bump __FreeBSD_version to 800096.
801 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
805 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
806 Bump __FreeBSD_version to 800094.
809 Add mnt_xflag field to 'struct mount'. File system modules need to be
811 Bump __FreeBSD_version to 800093.
814 The compiling option ADAPTIVE_SX has been retired while it has been
815 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
816 The KPI for sx_init_flags() changes as accepting flags:
817 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
818 been introduced in order to handle the reversed logic.
819 Bump __FreeBSD_version to 800092.
822 Add support for hierarchical jails. Remove global securelevel.
823 Bump __FreeBSD_version to 800091.
826 The layout of struct vnet_net has changed, therefore modules
828 Bump __FreeBSD_version to 800090.
831 The newly imported zic(8) produces a new format in the output. Please
832 run tzsetup(8) to install the newly created data to /etc/localtime.
835 The sysctl tree for the usb stack has renamed from hw.usb2.* to
836 hw.usb.* and is now consistent again with previous releases.
839 802.11 monitor mode support was revised and driver api's were changed.
840 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
841 of DLT_IEEE802_11. No user-visible data structures were changed but
842 applications that use DLT_IEEE802_11 may require changes.
843 Bump __FreeBSD_version to 800088.
846 The layout of the following structs has changed: sysctl_oid,
847 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
848 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
849 panics may be experienced. World rebuild is required for
850 correctly checking networking state from userland.
851 Bump __FreeBSD_version to 800085.
854 MLDv2 and Source-Specific Multicast (SSM) have been merged
855 to the IPv6 stack. VIMAGE hooks are in but not yet used.
856 The implementation of SSM within FreeBSD's IPv6 stack closely
857 follows the IPv4 implementation.
859 For kernel developers:
861 * The most important changes are that the ip6_output() and
862 ip6_input() paths no longer take the IN6_MULTI_LOCK,
863 and this lock has been downgraded to a non-recursive mutex.
865 * As with the changes to the IPv4 stack to support SSM, filtering
866 of inbound multicast traffic must now be performed by transport
867 protocols within the IPv6 stack. This does not apply to TCP and
868 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
870 * The KPIs used by IPv6 multicast are similar to those used by
871 the IPv4 stack, with the following differences:
872 * im6o_mc_filter() is analogous to imo_multicast_filter().
873 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
874 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
875 * IN6_LOOKUP_MULTI() has been deprecated and removed.
876 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
877 for MLDv1 have an additional 'timer' argument which is used to
878 jitter the initial membership report for the solicited-node
879 multicast membership on-link.
880 * This is not strictly needed for MLDv2, which already jitters
881 its report transmissions. However, the 'timer' argument is
882 preserved in case MLDv1 is active on the interface.
884 * The KAME linked-list based IPv6 membership implementation has
885 been refactored to use a vector similar to that used by the IPv4
887 Code which maintains a list of its own multicast memberships
888 internally, e.g. carp, has been updated to reflect the new
891 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
892 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
893 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
894 implementation constraint which needs to be addressed in HEAD.
896 For application developers:
898 * The changes are broadly similar to those made for the IPv4
901 * The use of IPv4 and IPv6 multicast socket options on the same
902 socket, using mapped addresses, HAS NOT been tested or supported.
904 * There are a number of issues with the implementation of various
905 IPv6 multicast APIs which need to be resolved in the API surface
906 before the implementation is fully compatible with KAME userland
907 use, and these are mostly to do with interface index treatment.
909 * The literature available discusses the use of either the delta / ASM
910 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
911 using setsourcefilter(3)/getsourcefilter(3). For more information
912 please refer to RFC 3768, 'Socket Interface Extensions for
913 Multicast Source Filters'.
915 * Applications which use the published RFC 3678 APIs should be fine.
917 For systems administrators:
919 * The mtest(8) utility has been refactored to support IPv6, in
920 addition to IPv4. Interface addresses are no longer accepted
921 as arguments, their names must be used instead. The utility
922 will map the interface name to its first IPv4 address as
923 returned by getifaddrs(3).
925 * The ifmcstat(8) utility has also been updated to print the MLDv2
926 endpoint state and source filter lists via sysctl(3).
928 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
929 loopback of IPv6 multicast datagrams by default; it defaults to 1
930 to preserve the existing behaviour. Disabling multicast loopback is
931 recommended for optimal system performance.
933 * The IPv6 MROUTING code has been changed to examine this sysctl
934 instead of attempting to perform a group lookup before looping
935 back forwarded datagrams.
937 Bump __FreeBSD_version to 800084.
940 Implement low-level Bluetooth HCI API.
941 Bump __FreeBSD_version to 800083.
944 The layout of struct malloc_type, used by modules to register new
945 memory allocation types, has changed. Most modules will need to
946 be rebuilt or panics may be experienced.
947 Bump __FreeBSD_version to 800081.
950 Anticipate overflowing inp_flags - add inp_flags2.
951 This changes most offsets in inpcb, so checking v4 connection
952 state will require a world rebuild.
953 Bump __FreeBSD_version to 800080.
956 Add an llentry to struct route and struct route_in6. Modules
957 embedding a struct route will need to be recompiled.
958 Bump __FreeBSD_version to 800079.
961 The size of rt_metrics_lite and by extension rtentry has changed.
962 Networking administration apps will need to be recompiled.
963 The route command now supports show as an alias for get, weighting
964 of routes, sticky and nostick flags to alter the behavior of stateful
966 Bump __FreeBSD_version to 800078.
969 Do not use Giant for kbdmux(4) locking. This is wrong and
970 apparently causing more problems than it solves. This will
971 re-open the issue where interrupt handlers may race with
972 kbdmux(4) in polling mode. Typical symptoms include (but
973 not limited to) duplicated and/or missing characters when
974 low level console functions (such as gets) are used while
975 interrupts are enabled (for example geli password prompt,
976 mountroot prompt etc.). Disabling kbdmux(4) may help.
979 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
980 kernel modules referencing any of the above need to be recompiled.
981 Bump __FreeBSD_version to 800075.
984 GEOM_PART has become the default partition slicer for storage devices,
985 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
986 introduces some changes:
988 MSDOS/EBR: the devices created from MSDOS extended partition entries
989 (EBR) can be named differently than with GEOM_MBR and are now symlinks
990 to devices with offset-based names. fstabs may need to be modified.
992 BSD: the "geometry does not match label" warning is harmless in most
993 cases but it points to problems in file system misalignment with
994 disk geometry. The "c" partition is now implicit, covers the whole
995 top-level drive and cannot be (mis)used by users.
997 General: Kernel dumps are now not allowed to be written to devices
998 whose partition types indicate they are meant to be used for file
999 systems (or, in case of MSDOS partitions, as something else than
1002 Most of these changes date approximately from 200812.
1005 The uscanner(4) driver has been removed from the kernel. This follows
1006 Linux removing theirs in 2.6 and making libusb the default interface
1007 (supported by sane).
1010 The multicast forwarding code has been cleaned up. netstat(1)
1011 only relies on KVM now for printing bandwidth upcall meters.
1012 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1013 ip6_mroute_mod respectively. The config(5) options for statically
1014 compiling this code remain the same, i.e. 'options MROUTING'.
1017 Support for the IFF_NEEDSGIANT network interface flag has been
1018 removed, which means that non-MPSAFE network device drivers are no
1019 longer supported. In particular, if_ar, if_sr, and network device
1020 drivers from the old (legacy) USB stack can no longer be built or
1024 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1025 a bunch of new language catalog files have also been added.
1026 This means that some common libc messages are now localized and
1027 they depend on the LC_MESSAGES environmental variable.
1030 The k8temp(4) driver has been renamed to amdtemp(4) since
1031 support for Family 10 and Family 11 CPU families was added.
1034 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1035 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1037 For kernel developers, the most important changes are that the
1038 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1039 and this lock has been downgraded to a non-recursive mutex.
1041 Transport protocols (UDP, Raw IP) are now responsible for filtering
1042 inbound multicast traffic according to group membership and source
1043 filters. The imo_multicast_filter() KPI exists for this purpose.
1044 Transports which do not use multicast (SCTP, TCP) already reject
1045 multicast by default. Forwarding and receive performance may improve
1046 as a mutex acquisition is no longer needed in the ip_input()
1047 low-level input path. in_addmulti() and in_delmulti() are shimmed
1048 to new KPIs which exist to support SSM in-kernel.
1050 For application developers, it is recommended that loopback of
1051 multicast datagrams be disabled for best performance, as this
1052 will still cause the lock to be taken for each looped-back
1053 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1054 be tuned to 0 to disable loopback by default; it defaults to 1
1055 to preserve the existing behaviour.
1057 For systems administrators, to obtain best performance with
1058 multicast reception and multiple groups, it is always recommended
1059 that a card with a suitably precise hash filter is used. Hash
1060 collisions will still result in the lock being taken within the
1061 transport protocol input path to check group membership.
1063 If deploying FreeBSD in an environment with IGMP snooping switches,
1064 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1065 enabled; this forces 224.0.0.0/24 group membership to be announced
1068 The size of 'struct igmpstat' has changed; netstat needs to be
1069 recompiled to reflect this.
1070 Bump __FreeBSD_version to 800070.
1073 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1074 updated to use it. This requires a buildworld/installworld in order to
1075 update the library and dependencies (usbconfig, etc). Its advisable to
1076 rebuild all ports which uses libusb. More specific directions are given
1077 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1078 libusb are no longer required and can be removed.
1081 A workaround is committed to allow the creation of System V shared
1082 memory segment of size > 2 GB on the 64-bit architectures.
1083 Due to a limitation of the existing ABI, the shm_segsz member
1084 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1085 wrong for large segments. Note that limits must be explicitly
1086 raised to allow such segments to be created.
1089 The layout of struct ifnet has changed, requiring a rebuild of all
1090 network device driver modules.
1093 The /dev handling for the new USB stack has changed, a
1094 buildworld/installworld is required for libusb20.
1097 The new USB2 stack has now been permanently moved in and all kernel and
1098 module names reverted to their previous values (eg, usb, ehci, ohci,
1099 ums, ...). The old usb stack can be compiled in by prefixing the name
1100 with the letter 'o', the old usb modules have been removed.
1101 Updating entry 20090216 for xorg and 20090215 for libmap may still
1105 The rc.conf(5) option if_up_delay has been renamed to
1106 defaultroute_delay to better reflect its purpose. If you have
1107 customized this setting in /etc/rc.conf you need to update it to
1111 xorg 7.4 wants to configure its input devices via hald which does not
1112 yet work with USB2. If the keyboard/mouse does not work in xorg then
1114 Option "AllowEmptyInput" "off"
1115 to your ServerLayout section. This will cause X to use the configured
1116 kbd and mouse sections from your xorg.conf.
1119 The GENERIC kernels for all architectures now default to the new USB2
1120 stack. No kernel config options or code have been removed so if a
1121 problem arises please report it and optionally revert to the old USB
1122 stack. If you are loading USB kernel modules or have a custom kernel
1123 that includes GENERIC then ensure that usb names are also changed over,
1124 eg uftdi -> usb2_serial_ftdi.
1126 Older programs linked against the ports libusb 0.1 need to be
1127 redirected to the new stack's libusb20. /etc/libmap.conf can
1129 # Map old usb library to new one for usb2 stack
1130 libusb-0.1.so.8 libusb20.so.1
1133 All USB ethernet devices now attach as interfaces under the name ueN
1134 (eg. ue0). This is to provide a predictable name as vendors often
1135 change usb chipsets in a product without notice.
1138 The ichsmb(4) driver has been changed to require SMBus slave
1139 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1140 All of the other SMBus controller drivers require left-justified
1141 slave addresses, so this change makes all the drivers provide the
1145 INET6 statistics (struct ip6stat) was updated.
1146 netstat(1) needs to be recompiled.
1149 NTFS has been removed from GENERIC kernel on amd64 to match
1150 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1151 will load ntfs.ko module automatically when NTFS support is
1152 actually needed, unless ntfs.ko is not installed or security
1153 level prohibits loading kernel modules. If either is the case,
1154 "options NTFS" has to be added into kernel config.
1157 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1158 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1159 800061. User space tools that rely on the size of struct tcpcb in
1160 tcp_var.h (e.g. sockstat) need to be recompiled.
1163 ng_tty(4) module updated to match the new TTY subsystem.
1164 Due to API change, user-level applications must be updated.
1165 New API support added to mpd5 CVS and expected to be present
1166 in next mpd5.3 release.
1169 With __FreeBSD_version 800060 the makefs tool is part of
1170 the base system (it was a port).
1173 The afdata and ifnet locks have been changed from mutexes to
1174 rwlocks, network modules will need to be re-compiled.
1177 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1178 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1179 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1180 architecture and 40 bytes on 64-bit architecture. The userland
1181 applications "arp" and "ndp" have been updated accordingly.
1182 The output from "netstat -r" shows only routing entries and
1183 none of the L2 information.
1186 __FreeBSD_version 800057 marks the switchover from the
1187 binary ath hal to source code. Users must add the line:
1189 options AH_SUPPORT_AR5416
1191 to their kernel config files when specifying:
1195 The ath_hal module no longer exists; the code is now compiled
1196 together with the driver in the ath module. It is now
1197 possible to tailor chip support (i.e. reduce the set of chips
1198 and thereby the code size); consult ath_hal(4) for details.
1201 __FreeBSD_version 800054 adds memory barriers to
1202 <machine/atomic.h>, new interfaces to ifnet to facilitate
1203 multiple hardware transmit queues for cards that support
1204 them, and a lock-less ring-buffer implementation to
1205 enable drivers to more efficiently manage queueing of
1209 A new version of ZFS (version 13) has been merged to -HEAD.
1210 This version has zpool attribute "listsnapshots" off by
1211 default, which means "zfs list" does not show snapshots,
1212 and is the same as Solaris behavior.
1215 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1218 The uhci, ohci, ehci and slhci USB Host controller drivers have
1219 been put into separate modules. If you load the usb module
1220 separately through loader.conf you will need to load the
1221 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1222 controller add the following to loader.conf:
1228 The ABI used by the PMC toolset has changed. Please keep
1229 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1233 atapci kernel module now includes only generic PCI ATA
1234 driver. AHCI driver moved to ataahci kernel module.
1235 All vendor-specific code moved into separate kernel modules:
1236 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1237 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1238 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1239 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1242 The TTY subsystem of the kernel has been replaced by a new
1243 implementation, which provides better scalability and an
1244 improved driver model. Most common drivers have been migrated to
1245 the new TTY subsystem, while others have not. The following
1246 drivers have not yet been ported to the new TTY layer:
1249 cy, digi, rc, rp, sio
1255 ng_h4, ng_tty, ppp, sl, snp
1257 Adding these drivers to your kernel configuration file shall
1258 cause compilation to fail.
1261 ntpd has been upgraded to 4.2.4p5.
1264 OpenSSH has been upgraded to 5.1p1.
1266 For many years, FreeBSD's version of OpenSSH preferred DSA
1267 over RSA for host and user authentication keys. With this
1268 upgrade, we've switched to the vendor's default of RSA over
1269 DSA. This may cause upgraded clients to warn about unknown
1270 host keys even for previously known hosts. Users should
1271 follow the usual procedure for verifying host keys before
1272 accepting the RSA key.
1274 This can be circumvented by setting the "HostKeyAlgorithms"
1275 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1278 Please note that the sequence of keys offered for
1279 authentication has been changed as well. You may want to
1280 specify IdentityFile in a different order to revert this
1284 The sio(4) driver has been removed from the i386 and amd64
1285 kernel configuration files. This means uart(4) is now the
1286 default serial port driver on those platforms as well.
1288 To prevent collisions with the sio(4) driver, the uart(4) driver
1289 uses different names for its device nodes. This means the
1290 onboard serial port will now most likely be called "ttyu0"
1291 instead of "ttyd0". You may need to reconfigure applications to
1292 use the new device names.
1294 When using the serial port as a boot console, be sure to update
1295 /boot/device.hints and /etc/ttys before booting the new kernel.
1296 If you forget to do so, you can still manually specify the hints
1297 at the loader prompt:
1299 set hint.uart.0.at="isa"
1300 set hint.uart.0.port="0x3F8"
1301 set hint.uart.0.flags="0x10"
1302 set hint.uart.0.irq="4"
1306 The gpt(8) utility has been removed. Use gpart(8) to partition
1310 The version that Linuxulator emulates was changed from 2.4.2
1311 to 2.6.16. If you experience any problems with Linux binaries
1312 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1313 if it fixes the problem contact emulation mailing list.
1316 ISDN4BSD (I4B) was removed from the src tree. You may need to
1317 update a your kernel configuration and remove relevant entries.
1320 I have checked in code to support multiple routing tables.
1321 See the man pages setfib(1) and setfib(2).
1322 This is a hopefully backwards compatible version,
1323 but to make use of it you need to compile your kernel
1324 with options ROUTETABLES=2 (or more up to 16).
1327 The 802.11 wireless support was redone to enable multi-bss
1328 operation on devices that are capable. The underlying device
1329 is no longer used directly but instead wlanX devices are
1330 cloned with ifconfig. This requires changes to rc.conf files.
1331 For example, change:
1332 ifconfig_ath0="WPA DHCP"
1335 ifconfig_wlan0="WPA DHCP"
1336 see rc.conf(5) for more details. In addition, mergemaster of
1337 /etc/rc.d is highly recommended. Simultaneous update of userland
1338 and kernel wouldn't hurt either.
1340 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1341 modules were merged into the base wlan module. All references
1342 to these modules (e.g. in kernel config files) must be removed.
1345 psm(4) has gained write(2) support in native operation level.
1346 Arbitrary commands can be written to /dev/psm%d and status can
1347 be read back from it. Therefore, an application is responsible
1348 for status validation and error recovery. It is a no-op in
1349 other operation levels.
1352 Support for KSE threading has been removed from the kernel. To
1353 run legacy applications linked against KSE libmap.conf may
1354 be used. The following libmap.conf may be used to ensure
1355 compatibility with any prior release:
1357 libpthread.so.1 libthr.so.1
1358 libpthread.so.2 libthr.so.2
1359 libkse.so.3 libthr.so.3
1362 The layout of struct vmspace has changed. This affects libkvm
1363 and any executables that link against libkvm and use the
1364 kvm_getprocs() function. In particular, but not exclusively,
1365 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1366 The effects are minimal, but it's advisable to upgrade world
1370 The latest em driver no longer has support in it for the
1371 82575 adapter, this is now moved to the igb driver. The
1372 split was done to make new features that are incompatible
1373 with older hardware easier to do.
1376 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1377 likewise the kernel option is now GEOM_LINUX_LVM.
1380 The default NFS mount mode has changed from UDP to TCP for
1381 increased reliability. If you rely on (insecurely) NFS
1382 mounting across a firewall you may need to update your
1386 Belatedly note the addition of m_collapse for compacting
1390 The fts(3) structures have been changed to use adequate
1391 integer types for their members and so to be able to cope
1392 with huge file trees. The old fts(3) ABI is preserved
1393 through symbol versioning in libc, so third-party binaries
1394 using fts(3) should still work, although they will not take
1395 advantage of the extended types. At the same time, some
1396 third-party software might fail to build after this change
1397 due to unportable assumptions made in its source code about
1398 fts(3) structure members. Such software should be fixed
1399 by its vendor or, in the worst case, in the ports tree.
1400 FreeBSD_version 800015 marks this change for the unlikely
1401 case that a portable fix is impossible.
1404 To upgrade to -current after this date, you must be running
1405 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1406 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1409 The ADAPTIVE_GIANT kernel option has been retired because its
1410 functionality is the default now.
1413 The AT keyboard emulation of sunkbd(4) has been turned on
1414 by default. In order to make the special symbols of the Sun
1415 keyboards driven by sunkbd(4) work under X these now have
1416 to be configured the same way as Sun USB keyboards driven
1417 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1419 Option "XkbLayout" "us"
1420 Option "XkbRules" "xorg"
1421 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1424 It has been decided that it is desirable to provide ABI
1425 backwards compatibility to the FreeBSD 4/5/6 versions of the
1426 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1427 broken with the introduction of PCI domain support (see the
1428 20070930 entry). Unfortunately, this required the ABI of
1429 PCIOCGETCONF to be broken again in order to be able to
1430 provide backwards compatibility to the old version of that
1431 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1432 again. As for prominent ports this affects neither pciutils
1433 nor xorg-server this time, the hal port needs to be rebuilt
1437 The misnamed kthread_create() and friends have been renamed
1438 to kproc_create() etc. Many of the callers already
1439 used kproc_start()..
1440 I will return kthread_create() and friends in a while
1441 with implementations that actually create threads, not procs.
1442 Renaming corresponds with version 800002.
1451 Avoid using make -j when upgrading. While generally safe, there are
1452 sometimes problems using -j to upgrade. If your upgrade fails with
1453 -j, please try again without -j. From time to time in the past there
1454 have been problems using -j with buildworld and/or installworld. This
1455 is especially true when upgrading between "distant" versions (eg one
1456 that cross a major release boundary or several minor releases, or when
1457 several months have passed on the -current branch).
1459 Sometimes, obscure build problems are the result of environment
1460 poisoning. This can happen because the make utility reads its
1461 environment when searching for values for global variables. To run
1462 your build attempts in an "environmental clean room", prefix all make
1463 commands with 'env -i '. See the env(1) manual page for more details.
1465 When upgrading from one major version to another it is generally best
1466 to upgrade to the latest code in the currently installed branch first,
1467 then do an upgrade to the new branch. This is the best-tested upgrade
1468 path, and has the highest probability of being successful. Please try
1469 this approach before reporting problems with a major version upgrade.
1473 When upgrading the boot ZFS pool to a new version, always follow
1476 1.) recompile and reinstall the ZFS boot loader and boot block
1477 (this is part of "make buildworld" and "make installworld")
1479 2.) update the ZFS boot block on your boot drive
1481 The following example updates the ZFS boot block on the first
1482 partition (freebsd-boot) of a GPT partitioned drive ad0:
1483 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1485 Non-boot pools do not need these updates.
1489 If you are updating from a prior version of FreeBSD (even one just
1490 a few days old), you should follow this procedure. It is the most
1491 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1493 make kernel-toolchain
1494 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1495 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1497 To test a kernel once
1498 ---------------------
1499 If you just want to boot a kernel once (because you are not sure
1500 if it works, or if you want to boot a known bad kernel to provide
1501 debugging information) run
1502 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1503 nextboot -k testkernel
1505 To just build a kernel when you know that it won't mess you up
1506 --------------------------------------------------------------
1507 This assumes you are already running a CURRENT system. Replace
1508 ${arch} with the architecture of your machine (e.g. "i386",
1509 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1511 cd src/sys/${arch}/conf
1512 config KERNEL_NAME_HERE
1513 cd ../compile/KERNEL_NAME_HERE
1518 If this fails, go to the "To build a kernel" section.
1520 To rebuild everything and install it on the current system.
1521 -----------------------------------------------------------
1522 # Note: sometimes if you are running current you gotta do more than
1523 # is listed here if you are upgrading from a really old current.
1525 <make sure you have good level 0 dumps>
1527 make kernel KERNCONF=YOUR_KERNEL_HERE
1529 <reboot in single user> [3]
1537 To cross-install current onto a separate partition
1538 --------------------------------------------------
1539 # In this approach we use a separate partition to hold
1540 # current's root, 'usr', and 'var' directories. A partition
1541 # holding "/", "/usr" and "/var" should be about 2GB in
1544 <make sure you have good level 0 dumps>
1547 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1548 <maybe newfs current's root partition>
1549 <mount current's root partition on directory ${CURRENT_ROOT}>
1550 make installworld DESTDIR=${CURRENT_ROOT}
1551 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1552 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1553 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1554 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1555 <reboot into current>
1556 <do a "native" rebuild/install as described in the previous section>
1557 <maybe install compatibility libraries from ports/misc/compat*>
1561 To upgrade in-place from 8.x-stable to current
1562 ----------------------------------------------
1563 <make sure you have good level 0 dumps>
1565 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1567 <reboot in single user> [3]
1574 Make sure that you've read the UPDATING file to understand the
1575 tweaks to various things you need. At this point in the life
1576 cycle of current, things change often and you are on your own
1577 to cope. The defaults can also change, so please read ALL of
1578 the UPDATING entries.
1580 Also, if you are tracking -current, you must be subscribed to
1581 freebsd-current@freebsd.org. Make sure that before you update
1582 your sources that you have read and understood all the recent
1583 messages there. If in doubt, please track -stable which has
1584 much fewer pitfalls.
1586 [1] If you have third party modules, such as vmware, you
1587 should disable them at this point so they don't crash your
1590 [3] From the bootblocks, boot -s, and then do
1595 adjkerntz -i # if CMOS is wall time
1596 Also, when doing a major release upgrade, it is required that
1597 you boot into single user mode to do the installworld.
1599 [4] Note: This step is non-optional. Failure to do this step
1600 can result in a significant reduction in the functionality of the
1601 system. Attempting to do it by hand is not recommended and those
1602 that pursue this avenue should read this file carefully, as well
1603 as the archives of freebsd-current and freebsd-hackers mailing lists
1604 for potential gotchas. The -U option is also useful to consider.
1605 See mergemaster(8) for more information.
1607 [5] Usually this step is a noop. However, from time to time
1608 you may need to do this if you get unknown user in the following
1609 step. It never hurts to do it all the time. You may need to
1610 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1611 install) after the buildworld before this step if you last updated
1612 from current before 20020224 or from -stable before 20020408.
1614 [6] This only deletes old files and directories. Old libraries
1615 can be deleted by "make delete-old-libs", but you have to make
1616 sure that no program is using those libraries anymore.
1618 [8] In order to have a kernel that can run the 4.x binaries needed to
1619 do an installworld, you must include the COMPAT_FREEBSD4 option in
1620 your kernel. Failure to do so may leave you with a system that is
1621 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1622 required to run the 5.x binaries on more recent kernels. And so on
1623 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1625 Make sure that you merge any new devices from GENERIC since the
1626 last time you updated your kernel config file.
1628 [9] When checking out sources, you must include the -P flag to have
1629 cvs prune empty directories.
1631 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1632 "?=" instead of the "=" assignment operator, so that buildworld can
1633 override the CPUTYPE if it needs to.
1635 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1636 not on the command line, or in /etc/make.conf. buildworld will
1637 warn if it is improperly defined.
1640 This file contains a list, in reverse chronological order, of major
1641 breakages in tracking -current. It is not guaranteed to be a complete
1642 list of such breakages, and only contains entries since October 10, 2007.
1643 If you need to see UPDATING entries from before that date, you will need
1644 to fetch an UPDATING file from an older FreeBSD release.
1646 Copyright information:
1648 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1650 Redistribution, publication, translation and use, with or without
1651 modification, in full or in part, in any form or format of this
1652 document are permitted without further permission from the author.
1654 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1655 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1656 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1657 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1658 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1659 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1660 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1661 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1662 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1663 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1664 POSSIBILITY OF SUCH DAMAGE.
1666 Contact Warner Losh if you have any questions about your use of