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 20130822: p6 FreeBSD-SA-13:09.ip_multicast
15 Fix an integer overflow in computing the size of a temporary buffer
16 can result in a buffer which is too small for the requested
19 Fix a bug that could lead to kernel memory disclosure with
20 SCTP state cookie. [13:10]
22 Fix a data corruption problem with mfi(4) operating on > 2TB
23 disks in a JBOD. [EN-13:03]
25 20130726: p5 FreeBSD-SA-13:07.bind FreeBSD-SA-13:08.nfsserver
26 Fix Denial of Service vulnerability in named(8). [13:07]
28 Fix a bug that allows remote client bypass the normal
29 access checks when when -network or -host restrictions are
30 used at the same time with -mapall. [13:08]
32 20130618: p4 FreeBSD-SA-13:06.mmap
33 Fix a bug that allowed a tracing process (e.g. gdb) to write
34 to a memory-mapped file in the traced process's address space
35 even if neither the traced process nor the tracing process had
36 write access to that file.
38 20130429: p3 FreeBSD-SA-13:05.nfsserver
39 Fix a bug that allows NFS clients to issue READDIR on files.
41 20130402: p2 FreeBSD-SA-13:03.openssl FreeBSD-SA-13:04.bind
42 Fix multiple vulnerabilities in OpenSSL.
44 Fix Denial of Service vulnerability in named(8).
46 20130218: p1 FreeBSD-SA-13:01.bind FreeBSD-SA-13:02.libc
47 Fix Denial of Service vulnerability in named(8) with DNS64.
49 Fix Denial of Service vulnerability in libc's glob(3) functionality.
55 The sparc64 ZFS loader has been changed to no longer try to auto-
56 detect ZFS providers based on diskN aliases but now requires these
57 to be explicitly listed in the OFW boot-device environment variable.
60 Now unix domain sockets behave "as expected" on nullfs(5). Previously
61 nullfs(5) did not pass through all behaviours to the underlying layer,
62 as a result if we bound to a socket on the lower layer we could connect
63 only to the lower path; if we bound to the upper layer we could connect
64 only to the upper path. The new behavior is one can connect to both the
65 lower and the upper paths regardless what layer path one binds to.
68 The acpi_wmi(4) status device /dev/wmistat has been renamed to
72 A new VOP_ADVISE() was added to support posix_fadvise(2). All
73 filesystem modules must be recompiled.
76 The interface of the VOP_VPTOCNP(9) changed, now the returned
77 vnode shall be referenced, previously it was required to be
78 only held. All in-tree filesystems are converted.
84 The broken amd(4) driver has been replaced with esp(4) in the amd64,
85 i386 and pc98 GENERIC kernel configuration files.
88 This commit modifies vfs_register() so that it uses a hash
89 calculation to set vfc_typenum, which is enabled by default.
90 The first time a system is booted after this change, the
91 vfc_typenum values will change for all file systems. The
92 main effect of this is a change to the NFS server file handles
93 for file systems that use vfc_typenum in their fsid, such as ZFS.
94 It will, however, prevent vfc_typenum from changing when file
95 systems are loaded in a different order for subsequent reboots.
96 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
97 until you are ready to remount all NFS clients after a reboot.
100 Bump the shared library version numbers for libraries that
101 do not use symbol versioning, have changed the ABI compared
102 to stable/8 and which shared library version was not bumped.
103 Done as part of 9.0-RELEASE cycle.
106 During the merge of Capsicum features, the fget(9) KPI was modified.
107 This may require the rebuilding of out-of-tree device drivers --
108 issues have been reported specifically with the nVidia device driver.
109 __FreeBSD_version is bumped to 900041.
111 Also, there is a period between 20110811 and 20110814 where the
112 special devices /dev/{stdin,stdout,stderr} did not work correctly.
113 Building world from a kernel during that window may not work.
116 The packet filter (pf) code has been updated to OpenBSD 4.5.
117 You need to update userland tools to be in sync with kernel.
118 This update breaks backward compatibility with earlier pfsync(4)
119 versions. Care must be taken when updating redundant firewall setups.
122 The following sysctls and tunables are retired on x86 platforms:
124 machdep.hlt_logical_cpus
125 The following sysctl is retired:
126 machdep.hyperthreading_allowed
127 The sysctls were supposed to provide a way to dynamically offline and
128 online selected CPUs on x86 platforms, but the implementation has not
129 been reliable especially with SCHED_ULE scheduler.
130 machdep.hyperthreading_allowed tunable is still available to ignore
131 hyperthreading CPUs at OS level.
132 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
133 where X is an APIC ID of a CPU. Be advised, though, that disabling
134 CPUs in non-uniform fashion will result in non-uniform topology and
135 may lead to sub-optimal system performance with SCHED_ULE, which is
139 cpumask_t type is retired and cpuset_t is used in order to describe
143 Changes to ifconfig(8) for dynamic address family detection mandate
144 that you are running a kernel of 20110525 or later. Make sure to
145 follow the update procedure to boot a new kernel before installing
149 Support for sun4v architecture is officially dropped
152 Several KPI breaking changes have been committed to the mii(4) layer,
153 the PHY drivers and consequently some Ethernet drivers using mii(4).
154 This means that miibus.ko and the modules of the affected Ethernet
155 drivers need to be recompiled.
157 Note to kernel developers: Given that the OUI bit reversion problem
158 was fixed as part of these changes all mii(4) commits related to OUIs,
159 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
160 handling, no longer can be merged verbatim to stable/8 and previous
164 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
165 into their kernel configurations along with 'device pci'.
168 The default NFS client is now the new NFS client, so fstype "newnfs"
169 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
170 Although mounts via fstype "nfs" will usually work without userland
171 changes, it is recommended that the mount(8) and mount_nfs(8)
172 commands be rebuilt from sources and that a link to mount_nfs called
173 mount_oldnfs be created. The new client is compiled into the
174 kernel with "options NFSCL" and this is needed for diskless root
175 file systems. The GENERIC kernel configs have been changed to use
176 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
177 To use the regular/old client, you can "mount -t oldnfs ...". For
178 a diskless root file system, you must also include a line like:
180 vfs.root.mountfrom="oldnfs:"
182 in the boot/loader.conf on the root fs on the NFS server to make
183 a diskless root fs use the old client.
186 The GENERIC kernels for all architectures now default to the new
187 CAM-based ATA stack. It means that all legacy ATA drivers were
188 removed and replaced by respective CAM drivers. If you are using
189 ATA device names in /etc/fstab or other places, make sure to update
190 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
191 where 'Y's are the sequential numbers starting from zero for each type
192 in order of detection, unless configured otherwise with tunables,
193 see cam(4)). There will be symbolic links created in /dev/ to map
194 old adX devices to the respective adaY. They should provide basic
195 compatibility for file systems mounting in most cases, but they do
196 not support old user-level APIs and do not have respective providers
197 in GEOM. Consider using updated management tools with new device names.
199 It is possible to load devices ahci, ata, siis and mvs as modules,
200 but option ATA_CAM should remain in kernel configuration to make ata
201 module work as CAM driver supporting legacy ATA controllers. Device ata
202 still can be used in modular fashion (atacore + ...). Modules atadisk
203 and atapi* are not used and won't affect operation in ATA_CAM mode.
204 Note that to use CAM-based ATA kernel should include CAM devices
205 scbus, pass, da (or explicitly ada), cd and optionally others. All of
206 them are parts of the cam module.
208 ataraid(4) functionality is now supported by the RAID GEOM class.
209 To use it you can load geom_raid kernel module and use graid(8) tool
210 for management. Instead of /dev/arX device names, use /dev/raid/rX.
212 No kernel config options or code have been removed, so if a problem
213 arises, please report it and optionally revert to the old ATA stack.
214 In order to do it you can remove from the kernel config:
219 , and instead add back:
220 device atadisk # ATA disk drives
221 device ataraid # ATA RAID drives
222 device atapicd # ATAPI CDROM drives
223 device atapifd # ATAPI floppy drives
224 device atapist # ATAPI tape drives
227 The default NFS server has been changed to the new server, which
228 was referred to as the experimental server. If you need to switch
229 back to the old NFS server, you must now put the "-o" option on
230 both the mountd and nfsd commands. This can be done using the
231 mountd_flags and nfs_server_flags rc.conf variables until an
232 update to the rc scripts is committed, which is coming soon.
235 The GNU Objective-C runtime library (libobjc), and other Objective-C
236 related components have been removed from the base system. If you
237 require an Objective-C library, please use one of the available ports.
240 ath(4) has been split into bus- and device- modules. if_ath contains
241 the HAL, the TX rate control and the network device code. if_ath_pci
242 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
243 contains the AHB glue. Users need to load both if_ath_pci and if_ath
244 in order to use ath on everything else.
246 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
247 need to load if_ath and if_ath_pci for ath(4) operation.
250 As part of the replacement of sysinstall, the process of building
251 release media has changed significantly. For details, please re-read
252 release(7), which has been updated to reflect the new build process.
255 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
256 is the last available version under GPLv2. It brings a number of new
257 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
258 4.1 and SSE 4.2), better support for powerpc64, a number of new
259 directives, and lots of other small improvements. See the ChangeLog
260 file in contrib/binutils for the full details.
263 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
264 compliant, and will now use half of hash for authentication.
265 This will break interoperability with all stacks (including all
266 actual FreeBSD versions) who implement
267 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
269 The only workaround with such peers is to use another HMAC
270 algorithm for IPsec ("phase 2") authentication.
273 Remove the uio_yield prototype and symbol. This function has
274 been misnamed since it was introduced and should not be
275 globally exposed with this name. The equivalent functionality
276 is now available using kern_yield(curthread->td_user_pri).
277 The function remains undocumented.
280 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
281 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
282 for scalar sysctls is defined but disabled. Code that needs
283 UQUAD to pass the type checking that must compile on older
284 systems where the define is not present can check against
285 __FreeBSD_version >= 900030.
287 The system dialog(1) has been replaced with a new version previously
288 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
289 with the previous version, but the libdialog associated with it has
290 a largely incompatible API. As such, the original version of libdialog
291 will be kept temporarily as libodialog, until its base system consumers
292 are replaced or updated. Bump __FreeBSD_version to 900030.
295 If you are trying to run make universe on a -stable system, and you get
296 the following warning:
297 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
298 unknown. config(8) likely too old."
299 or something similar to it, then you must upgrade your -stable system
300 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
301 stable/8) or build the config from the latest stable/8 branch and
302 install it on your system.
304 Prior to this date, building a current universe on 8-stable system from
305 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
306 error in the first kernel build phase. A new config on those old
307 systems will fix that problem for older versions of -current.
310 The TCP stack has been modified to allow Khelp modules to interact with
311 it via helper hook points and store per-connection data in the TCP
312 control block. Bump __FreeBSD_version to 900029. User space tools that
313 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
317 Generic IEEE 802.3 annex 31B full duplex flow control support has been
318 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
319 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
320 to take advantage of it instead of using custom implementations. This
321 means that these drivers now no longer unconditionally advertise
322 support for flow control but only do so if flow control is a selected
323 media option. This was implemented in the generic support that way in
324 order to allow flow control to be switched on and off via ifconfig(8)
325 with the PHY specific default to typically off in order to protect
326 from unwanted effects. Consequently, if you used flow control with
327 one of the above mentioned drivers you now need to explicitly enable
329 ifconfig bge0 media auto mediaopt flowcontrol
331 Along with the above mentioned changes generic support for setting
332 1000baseT master mode also has been added and brgphy(4), ciphy(4),
333 e1000phy(4) as well as ip1000phy(4) have been converted to take
334 advantage of it. This means that these drivers now no longer take the
335 link0 parameter for selecting master mode but the master media option
336 has to be used instead, for example like in the following:
337 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
339 Selection of master mode now is also available with all other PHY
340 drivers supporting 1000baseT.
343 The TCP stack has received a significant update to add support for
344 modularised congestion control and generally improve the clarity of
345 congestion control decisions. Bump __FreeBSD_version to 900025. User
346 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
347 sockstat) need to be recompiled.
350 The man(1) utility has been replaced by a new version that no longer
351 uses /etc/manpath.config. Please consult man.conf(5) for how to
352 migrate local entries to the new format.
355 The copyright strings printed by login(1) and sshd(8) at the time of a
356 new connection have been removed to follow other operating systems and
360 A workaround for a fixed ld bug has been removed in kernel code,
361 so make sure that your system ld is built from sources after
362 revision 210245 from 2010-07-19 (r211583 if building head kernel
363 on stable/8, r211584 for stable/7; both from 2010-08-21).
364 A symptom of incorrect ld version is different addresses for
365 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
368 The $ipv6_prefer variable in rc.conf(5) has been split into
369 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
371 The $ip6addrctl_policy is a variable to choose a pre-defined
372 address selection policy set by ip6addrctl(8). A value
373 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
376 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
377 flag (see an entry of 20090926) is set on an interface with no
378 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
379 security reason. If you want IPv6 link-local address on all
380 interfaces by default, set this to "YES".
382 The old ipv6_prefer="YES" is equivalent to
383 ipv6_activate_all_interfaces="YES" and
384 ip6addrctl_policy="ipv6_prefer".
387 DTrace has grown support for userland tracing. Due to this, DTrace is
388 now i386 and amd64 only.
389 dtruss(1) is now installed by default on those systems and a new
390 kernel module is needed for userland tracing: fasttrap.
391 No changes to your kernel config file are necessary to enable
392 userland tracing, but you might consider adding 'STRIP=' and
393 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
394 to have informative userland stack traces in DTrace (ustack).
397 The acpi_aiboost(4) driver has been removed in favor of the new
398 aibs(4) driver. You should update your kernel configuration file.
401 BSD grep has been imported to the base system and it is built by
402 default. It is completely BSD licensed, highly GNU-compatible, uses
403 less memory than its GNU counterpart and has a small codebase.
404 However, it is slower than its GNU counterpart, which is mostly
405 noticeable for larger searches, for smaller ones it is measurable
406 but not significant. The reason is complex, the most important factor
407 is that we lack a modern and efficient regex library and GNU
408 overcomes this by optimizing the searches internally. Future work
409 on improving the regex performance is planned, for the meantime,
410 users that need better performance, can build GNU grep instead by
411 setting the WITH_GNU_GREP knob.
414 Due to the import of powerpc64 support, all existing powerpc kernel
415 configuration files must be updated with a machine directive like this:
416 machine powerpc powerpc
418 In addition, an updated config(8) is required to build powerpc kernels
422 A new version of ZFS (version 15) has been merged to -HEAD.
423 This version uses a python library for the following subcommands:
424 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
425 For full functionality of these commands the following port must
426 be installed: sysutils/py-zfs
429 'vm_page's are now hashed by physical address to an array of mutexes.
430 Currently this is only used to serialize access to hold_count. Over
431 time the page queue mutex will be peeled away. This changes the size
432 of pmap on every architecture. And requires all callers of vm_page_hold
433 and vm_page_unhold to be updated.
436 WITH_CTF can now be specified in src.conf (not recommended, there
437 are some problems with static executables), make.conf (would also
438 affect ports which do not use GNU make and do not override the
439 compile targets) or in the kernel config (via "makeoptions
441 When WITH_CTF was specified there before this was silently ignored,
442 so make sure that WITH_CTF is not used in places which could lead
443 to unwanted behavior.
446 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
447 to allow 32-bit compatibility on non-x86 platforms. All kernel
448 configurations on amd64 and ia64 platforms using these options must
449 be modified accordingly.
452 The utmp user accounting database has been replaced with utmpx,
453 the user accounting interface standardized by POSIX.
454 Unfortunately the semantics of utmp and utmpx don't match,
455 making it practically impossible to support both interfaces.
456 The user accounting database is used by tools like finger(1),
457 last(1), talk(1), w(1) and ac(8).
459 All applications in the base system use utmpx. This means only
460 local binaries (e.g. from the ports tree) may still use these
461 utmp database files. These applications must be rebuilt to make
464 After the system has been upgraded, it is safe to remove the old
465 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
466 assuming their contents is of no importance anymore. Old wtmp
467 databases can only be used by last(1) and ac(8) after they have
468 been converted to the new format using wtmpcvt(1).
471 Introduce the kernel thread "deadlock resolver" (which can be enabled
472 via the DEADLKRES option, see NOTES for more details) and the
473 sleepq_type() function for sleepqueues.
476 The rc.firewall and rc.firewall6 were unified, and
477 rc.firewall6 and rc.d/ip6fw were removed.
478 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
479 variables are obsoleted. Instead, the following new rc
480 variables are added to rc.d/ipfw:
482 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
483 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
484 firewall_simple_onet_ipv6, firewall_trusted_ipv6
486 The meanings correspond to the relevant IPv4 variables.
492 The default terminal emulation for syscons(4) has been changed
493 from cons25 to xterm on all platforms except pc98. This means
494 that the /etc/ttys file needs to be updated to ensure correct
495 operation of applications on the console.
497 The terminal emulation style can be toggled per window by using
498 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
499 options can be used to change the compile-time default back to
502 To prevent graphical artifacts, make sure the TERM environment
503 variable is set to match the terminal emulation that is being
504 performed by syscons(4).
507 The layout of the structure ieee80211req_scan_result has changed.
508 Applications that require wireless scan results (e.g. ifconfig(8))
509 from net80211 need to be recompiled.
511 Applications such as wpa_supplicant(8) may require a full world
512 build without using NO_CLEAN in order to get synchronized with the
516 The iwn(4) driver has been updated to support the 5000 and 5150 series.
517 There's one kernel module for each firmware. Adding "device iwnfw"
518 to the kernel configuration file means including all three firmware
519 images inside the kernel. If you want to include just the one for
520 your wireless card, use the devices iwn4965fw, iwn5000fw or
524 The rc.d/network_ipv6, IPv6 configuration script has been integrated
525 into rc.d/netif. The changes are the following:
527 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
528 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
529 Note that both variables need the "inet6" keyword at the head.
531 Do not set $ipv6_network_interfaces manually if you do not
532 understand what you are doing. It is not needed in most cases.
534 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
537 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
538 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
540 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
541 all configured interfaces have "inet6 accept_rtadv" in the
542 $ifconfig_IF_ipv6. These are for backward compatibility.
544 3. A new variable $ipv6_prefer has been added. If NO, IPv6
545 functionality of interfaces with no corresponding
546 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
547 and the default address selection policy of ip6addrctl(8)
548 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
549 Note that if you want to configure IPv6 functionality on the
550 disabled interfaces after boot, first you need to clear the flag by
551 using ifconfig(8) like:
553 ifconfig em0 inet6 -ifdisabled
555 If YES, the default address selection policy is set as
558 The default value of $ipv6_prefer is NO.
560 4. If your system need to receive Router Advertisement messages,
561 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
562 scripts automatically invoke rtsol(8) when the interface becomes
563 UP. The Router Advertisement messages are used for SLAAC
564 (State-Less Address AutoConfiguration).
567 802.11s D3.03 support was committed. This is incompatible with the
568 previous code, which was based on D3.0.
571 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
572 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
573 control whether accepting Router Advertisement messages or not.
574 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
575 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
576 The ifconfig(8) utility now supports these flags.
579 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
580 mount(8) and -a option for df(1) to see them.
583 The old tunable hw.bus.devctl_disable has been superseded by
584 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
585 replaced by hw.bus.devctl_queue=0. The default for this new tunable
589 Remove the option STOP_NMI. The default action is now to use NMI only
590 for KDB via the newly introduced function stop_cpus_hard() and
591 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
594 The stable/8 branch created in subversion. This corresponds to the
595 RELENG_8 branch in CVS.
598 Bump the shared library version numbers for all libraries that do not
599 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
600 __FreeBSD_version to 800105.
603 Due to changes in the implementation of virtual network stack support,
604 all network-related kernel modules must be recompiled. As this change
605 breaks the ABI, bump __FreeBSD_version to 800104.
608 The TOE interface to the TCP syncache has been modified to remove
609 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
610 The cxgb driver is the only TOE consumer affected by this change, and
611 needs to be recompiled along with the kernel. As this change breaks
612 the ABI, bump __FreeBSD_version to 800103.
615 Padding has been added to struct tcpcb, sackhint and tcpstat in
616 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
617 maintaining the ABI. However, this change breaks the ABI, so bump
618 __FreeBSD_version to 800102. User space tools that rely on the size of
619 any of these structs (e.g. sockstat) need to be recompiled.
622 The NFS_LEGACYRPC option has been removed along with the old kernel
623 RPC implementation that this option selected. Kernel configurations
624 may need to be adjusted.
627 The network interface device nodes at /dev/net/<interface> have been
628 removed. All ioctl operations can be performed the normal way using
629 routing sockets. The kqueue functionality can generally be replaced
630 with routing sockets.
633 The documentation from the FreeBSD Documentation Project (Handbook,
634 FAQ, etc.) is now installed via packages by sysinstall(8) and under
635 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
638 The ABI of various structures related to the SYSV IPC API have been
639 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
640 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
644 Layout of struct vnet has changed as routing related variables were
645 moved to their own Vimage module. Modules need to be recompiled. Bump
646 __FreeBSD_version to 800099.
649 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
650 respectively. As long as no more than 16 groups per process are used,
651 no changes should be visible. When more than 16 groups are used, old
652 binaries may fail if they call getgroups() or getgrouplist() with
653 statically sized storage. Recompiling will work around this, but
654 applications should be modified to use dynamically allocated storage
655 for group arrays as POSIX.1-2008 does not cap an implementation's
656 number of supported groups at NGROUPS_MAX+1 as previous versions did.
658 NFS and portalfs mounts may also be affected as the list of groups is
659 truncated to 16. Users of NFS who use more than 16 groups, should
660 take care that negative group permissions are not used on the exported
661 file systems as they will not be reliable unless a GSSAPI based
662 authentication method is used.
665 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
666 option compiles in the support for adaptive spinning for lockmgrs
667 which want to enable it. The lockinit() function now accepts the flag
668 LK_ADAPTIVE in order to make the lock object subject to adaptive
669 spinning when both held in write and read mode.
672 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
673 changed. User applications that use this ioctl need to be rebuilt.
676 The layout of struct thread has changed. Kernel and modules need to
680 The layout of structs ifnet, domain, protosw and vnet_net has changed.
681 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
684 window(1) has been removed from the base system. It can now be
685 installed from ports. The port is called misc/window.
688 The way we are storing and accessing `routing table' entries has
689 changed. Programs reading the FIB, like netstat, need to be
693 A new netisr implementation has been added for FreeBSD 8. Network
694 file system modules, such as igmp, ipdivert, and others, should be
696 Bump __FreeBSD_version to 800096.
699 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
703 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
704 Bump __FreeBSD_version to 800094.
707 Add mnt_xflag field to 'struct mount'. File system modules need to be
709 Bump __FreeBSD_version to 800093.
712 The compiling option ADAPTIVE_SX has been retired while it has been
713 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
714 The KPI for sx_init_flags() changes as accepting flags:
715 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
716 been introduced in order to handle the reversed logic.
717 Bump __FreeBSD_version to 800092.
720 Add support for hierarchical jails. Remove global securelevel.
721 Bump __FreeBSD_version to 800091.
724 The layout of struct vnet_net has changed, therefore modules
726 Bump __FreeBSD_version to 800090.
729 The newly imported zic(8) produces a new format in the output. Please
730 run tzsetup(8) to install the newly created data to /etc/localtime.
733 The sysctl tree for the usb stack has renamed from hw.usb2.* to
734 hw.usb.* and is now consistent again with previous releases.
737 802.11 monitor mode support was revised and driver api's were changed.
738 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
739 of DLT_IEEE802_11. No user-visible data structures were changed but
740 applications that use DLT_IEEE802_11 may require changes.
741 Bump __FreeBSD_version to 800088.
744 The layout of the following structs has changed: sysctl_oid,
745 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
746 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
747 panics may be experienced. World rebuild is required for
748 correctly checking networking state from userland.
749 Bump __FreeBSD_version to 800085.
752 MLDv2 and Source-Specific Multicast (SSM) have been merged
753 to the IPv6 stack. VIMAGE hooks are in but not yet used.
754 The implementation of SSM within FreeBSD's IPv6 stack closely
755 follows the IPv4 implementation.
757 For kernel developers:
759 * The most important changes are that the ip6_output() and
760 ip6_input() paths no longer take the IN6_MULTI_LOCK,
761 and this lock has been downgraded to a non-recursive mutex.
763 * As with the changes to the IPv4 stack to support SSM, filtering
764 of inbound multicast traffic must now be performed by transport
765 protocols within the IPv6 stack. This does not apply to TCP and
766 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
768 * The KPIs used by IPv6 multicast are similar to those used by
769 the IPv4 stack, with the following differences:
770 * im6o_mc_filter() is analogous to imo_multicast_filter().
771 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
772 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
773 * IN6_LOOKUP_MULTI() has been deprecated and removed.
774 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
775 for MLDv1 have an additional 'timer' argument which is used to
776 jitter the initial membership report for the solicited-node
777 multicast membership on-link.
778 * This is not strictly needed for MLDv2, which already jitters
779 its report transmissions. However, the 'timer' argument is
780 preserved in case MLDv1 is active on the interface.
782 * The KAME linked-list based IPv6 membership implementation has
783 been refactored to use a vector similar to that used by the IPv4
785 Code which maintains a list of its own multicast memberships
786 internally, e.g. carp, has been updated to reflect the new
789 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
790 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
791 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
792 implementation constraint which needs to be addressed in HEAD.
794 For application developers:
796 * The changes are broadly similar to those made for the IPv4
799 * The use of IPv4 and IPv6 multicast socket options on the same
800 socket, using mapped addresses, HAS NOT been tested or supported.
802 * There are a number of issues with the implementation of various
803 IPv6 multicast APIs which need to be resolved in the API surface
804 before the implementation is fully compatible with KAME userland
805 use, and these are mostly to do with interface index treatment.
807 * The literature available discusses the use of either the delta / ASM
808 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
809 using setsourcefilter(3)/getsourcefilter(3). For more information
810 please refer to RFC 3768, 'Socket Interface Extensions for
811 Multicast Source Filters'.
813 * Applications which use the published RFC 3678 APIs should be fine.
815 For systems administrators:
817 * The mtest(8) utility has been refactored to support IPv6, in
818 addition to IPv4. Interface addresses are no longer accepted
819 as arguments, their names must be used instead. The utility
820 will map the interface name to its first IPv4 address as
821 returned by getifaddrs(3).
823 * The ifmcstat(8) utility has also been updated to print the MLDv2
824 endpoint state and source filter lists via sysctl(3).
826 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
827 loopback of IPv6 multicast datagrams by default; it defaults to 1
828 to preserve the existing behaviour. Disabling multicast loopback is
829 recommended for optimal system performance.
831 * The IPv6 MROUTING code has been changed to examine this sysctl
832 instead of attempting to perform a group lookup before looping
833 back forwarded datagrams.
835 Bump __FreeBSD_version to 800084.
838 Implement low-level Bluetooth HCI API.
839 Bump __FreeBSD_version to 800083.
842 The layout of struct malloc_type, used by modules to register new
843 memory allocation types, has changed. Most modules will need to
844 be rebuilt or panics may be experienced.
845 Bump __FreeBSD_version to 800081.
848 Anticipate overflowing inp_flags - add inp_flags2.
849 This changes most offsets in inpcb, so checking v4 connection
850 state will require a world rebuild.
851 Bump __FreeBSD_version to 800080.
854 Add an llentry to struct route and struct route_in6. Modules
855 embedding a struct route will need to be recompiled.
856 Bump __FreeBSD_version to 800079.
859 The size of rt_metrics_lite and by extension rtentry has changed.
860 Networking administration apps will need to be recompiled.
861 The route command now supports show as an alias for get, weighting
862 of routes, sticky and nostick flags to alter the behavior of stateful
864 Bump __FreeBSD_version to 800078.
867 Do not use Giant for kbdmux(4) locking. This is wrong and
868 apparently causing more problems than it solves. This will
869 re-open the issue where interrupt handlers may race with
870 kbdmux(4) in polling mode. Typical symptoms include (but
871 not limited to) duplicated and/or missing characters when
872 low level console functions (such as gets) are used while
873 interrupts are enabled (for example geli password prompt,
874 mountroot prompt etc.). Disabling kbdmux(4) may help.
877 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
878 kernel modules referencing any of the above need to be recompiled.
879 Bump __FreeBSD_version to 800075.
882 GEOM_PART has become the default partition slicer for storage devices,
883 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
884 introduces some changes:
886 MSDOS/EBR: the devices created from MSDOS extended partition entries
887 (EBR) can be named differently than with GEOM_MBR and are now symlinks
888 to devices with offset-based names. fstabs may need to be modified.
890 BSD: the "geometry does not match label" warning is harmless in most
891 cases but it points to problems in file system misalignment with
892 disk geometry. The "c" partition is now implicit, covers the whole
893 top-level drive and cannot be (mis)used by users.
895 General: Kernel dumps are now not allowed to be written to devices
896 whose partition types indicate they are meant to be used for file
897 systems (or, in case of MSDOS partitions, as something else than
900 Most of these changes date approximately from 200812.
903 The uscanner(4) driver has been removed from the kernel. This follows
904 Linux removing theirs in 2.6 and making libusb the default interface
908 The multicast forwarding code has been cleaned up. netstat(1)
909 only relies on KVM now for printing bandwidth upcall meters.
910 The IPv4 and IPv6 modules are split into ip_mroute_mod and
911 ip6_mroute_mod respectively. The config(5) options for statically
912 compiling this code remain the same, i.e. 'options MROUTING'.
915 Support for the IFF_NEEDSGIANT network interface flag has been
916 removed, which means that non-MPSAFE network device drivers are no
917 longer supported. In particular, if_ar, if_sr, and network device
918 drivers from the old (legacy) USB stack can no longer be built or
922 POSIX.1 Native Language Support (NLS) has been enabled in libc and
923 a bunch of new language catalog files have also been added.
924 This means that some common libc messages are now localized and
925 they depend on the LC_MESSAGES environmental variable.
928 The k8temp(4) driver has been renamed to amdtemp(4) since
929 support for Family 10 and Family 11 CPU families was added.
932 IGMPv3 and Source-Specific Multicast (SSM) have been merged
933 to the IPv4 stack. VIMAGE hooks are in but not yet used.
935 For kernel developers, the most important changes are that the
936 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
937 and this lock has been downgraded to a non-recursive mutex.
939 Transport protocols (UDP, Raw IP) are now responsible for filtering
940 inbound multicast traffic according to group membership and source
941 filters. The imo_multicast_filter() KPI exists for this purpose.
942 Transports which do not use multicast (SCTP, TCP) already reject
943 multicast by default. Forwarding and receive performance may improve
944 as a mutex acquisition is no longer needed in the ip_input()
945 low-level input path. in_addmulti() and in_delmulti() are shimmed
946 to new KPIs which exist to support SSM in-kernel.
948 For application developers, it is recommended that loopback of
949 multicast datagrams be disabled for best performance, as this
950 will still cause the lock to be taken for each looped-back
951 datagram transmission. The net.inet.ip.mcast.loop sysctl may
952 be tuned to 0 to disable loopback by default; it defaults to 1
953 to preserve the existing behaviour.
955 For systems administrators, to obtain best performance with
956 multicast reception and multiple groups, it is always recommended
957 that a card with a suitably precise hash filter is used. Hash
958 collisions will still result in the lock being taken within the
959 transport protocol input path to check group membership.
961 If deploying FreeBSD in an environment with IGMP snooping switches,
962 it is recommended that the net.inet.igmp.sendlocal sysctl remain
963 enabled; this forces 224.0.0.0/24 group membership to be announced
966 The size of 'struct igmpstat' has changed; netstat needs to be
967 recompiled to reflect this.
968 Bump __FreeBSD_version to 800070.
971 libusb20.so.1 is now installed as libusb.so.1 and the ports system
972 updated to use it. This requires a buildworld/installworld in order to
973 update the library and dependencies (usbconfig, etc). Its advisable to
974 rebuild all ports which uses libusb. More specific directions are given
975 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
976 libusb are no longer required and can be removed.
979 A workaround is committed to allow the creation of System V shared
980 memory segment of size > 2 GB on the 64-bit architectures.
981 Due to a limitation of the existing ABI, the shm_segsz member
982 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
983 wrong for large segments. Note that limits must be explicitly
984 raised to allow such segments to be created.
987 The layout of struct ifnet has changed, requiring a rebuild of all
988 network device driver modules.
991 The /dev handling for the new USB stack has changed, a
992 buildworld/installworld is required for libusb20.
995 The new USB2 stack has now been permanently moved in and all kernel and
996 module names reverted to their previous values (eg, usb, ehci, ohci,
997 ums, ...). The old usb stack can be compiled in by prefixing the name
998 with the letter 'o', the old usb modules have been removed.
999 Updating entry 20090216 for xorg and 20090215 for libmap may still
1003 The rc.conf(5) option if_up_delay has been renamed to
1004 defaultroute_delay to better reflect its purpose. If you have
1005 customized this setting in /etc/rc.conf you need to update it to
1009 xorg 7.4 wants to configure its input devices via hald which does not
1010 yet work with USB2. If the keyboard/mouse does not work in xorg then
1012 Option "AllowEmptyInput" "off"
1013 to your ServerLayout section. This will cause X to use the configured
1014 kbd and mouse sections from your xorg.conf.
1017 The GENERIC kernels for all architectures now default to the new USB2
1018 stack. No kernel config options or code have been removed so if a
1019 problem arises please report it and optionally revert to the old USB
1020 stack. If you are loading USB kernel modules or have a custom kernel
1021 that includes GENERIC then ensure that usb names are also changed over,
1022 eg uftdi -> usb2_serial_ftdi.
1024 Older programs linked against the ports libusb 0.1 need to be
1025 redirected to the new stack's libusb20. /etc/libmap.conf can
1027 # Map old usb library to new one for usb2 stack
1028 libusb-0.1.so.8 libusb20.so.1
1031 All USB ethernet devices now attach as interfaces under the name ueN
1032 (eg. ue0). This is to provide a predictable name as vendors often
1033 change usb chipsets in a product without notice.
1036 The ichsmb(4) driver has been changed to require SMBus slave
1037 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1038 All of the other SMBus controller drivers require left-justified
1039 slave addresses, so this change makes all the drivers provide the
1043 INET6 statistics (struct ip6stat) was updated.
1044 netstat(1) needs to be recompiled.
1047 NTFS has been removed from GENERIC kernel on amd64 to match
1048 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1049 will load ntfs.ko module automatically when NTFS support is
1050 actually needed, unless ntfs.ko is not installed or security
1051 level prohibits loading kernel modules. If either is the case,
1052 "options NTFS" has to be added into kernel config.
1055 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1056 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1057 800061. User space tools that rely on the size of struct tcpcb in
1058 tcp_var.h (e.g. sockstat) need to be recompiled.
1061 ng_tty(4) module updated to match the new TTY subsystem.
1062 Due to API change, user-level applications must be updated.
1063 New API support added to mpd5 CVS and expected to be present
1064 in next mpd5.3 release.
1067 With __FreeBSD_version 800060 the makefs tool is part of
1068 the base system (it was a port).
1071 The afdata and ifnet locks have been changed from mutexes to
1072 rwlocks, network modules will need to be re-compiled.
1075 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1076 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1077 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1078 architecture and 40 bytes on 64-bit architecture. The userland
1079 applications "arp" and "ndp" have been updated accordingly.
1080 The output from "netstat -r" shows only routing entries and
1081 none of the L2 information.
1084 __FreeBSD_version 800057 marks the switchover from the
1085 binary ath hal to source code. Users must add the line:
1087 options AH_SUPPORT_AR5416
1089 to their kernel config files when specifying:
1093 The ath_hal module no longer exists; the code is now compiled
1094 together with the driver in the ath module. It is now
1095 possible to tailor chip support (i.e. reduce the set of chips
1096 and thereby the code size); consult ath_hal(4) for details.
1099 __FreeBSD_version 800054 adds memory barriers to
1100 <machine/atomic.h>, new interfaces to ifnet to facilitate
1101 multiple hardware transmit queues for cards that support
1102 them, and a lock-less ring-buffer implementation to
1103 enable drivers to more efficiently manage queueing of
1107 A new version of ZFS (version 13) has been merged to -HEAD.
1108 This version has zpool attribute "listsnapshots" off by
1109 default, which means "zfs list" does not show snapshots,
1110 and is the same as Solaris behavior.
1113 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1116 The uhci, ohci, ehci and slhci USB Host controller drivers have
1117 been put into separate modules. If you load the usb module
1118 separately through loader.conf you will need to load the
1119 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1120 controller add the following to loader.conf:
1126 The ABI used by the PMC toolset has changed. Please keep
1127 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1131 atapci kernel module now includes only generic PCI ATA
1132 driver. AHCI driver moved to ataahci kernel module.
1133 All vendor-specific code moved into separate kernel modules:
1134 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1135 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1136 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1137 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1140 The TTY subsystem of the kernel has been replaced by a new
1141 implementation, which provides better scalability and an
1142 improved driver model. Most common drivers have been migrated to
1143 the new TTY subsystem, while others have not. The following
1144 drivers have not yet been ported to the new TTY layer:
1147 cy, digi, rc, rp, sio
1153 ng_h4, ng_tty, ppp, sl, snp
1155 Adding these drivers to your kernel configuration file shall
1156 cause compilation to fail.
1159 ntpd has been upgraded to 4.2.4p5.
1162 OpenSSH has been upgraded to 5.1p1.
1164 For many years, FreeBSD's version of OpenSSH preferred DSA
1165 over RSA for host and user authentication keys. With this
1166 upgrade, we've switched to the vendor's default of RSA over
1167 DSA. This may cause upgraded clients to warn about unknown
1168 host keys even for previously known hosts. Users should
1169 follow the usual procedure for verifying host keys before
1170 accepting the RSA key.
1172 This can be circumvented by setting the "HostKeyAlgorithms"
1173 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1176 Please note that the sequence of keys offered for
1177 authentication has been changed as well. You may want to
1178 specify IdentityFile in a different order to revert this
1182 The sio(4) driver has been removed from the i386 and amd64
1183 kernel configuration files. This means uart(4) is now the
1184 default serial port driver on those platforms as well.
1186 To prevent collisions with the sio(4) driver, the uart(4) driver
1187 uses different names for its device nodes. This means the
1188 onboard serial port will now most likely be called "ttyu0"
1189 instead of "ttyd0". You may need to reconfigure applications to
1190 use the new device names.
1192 When using the serial port as a boot console, be sure to update
1193 /boot/device.hints and /etc/ttys before booting the new kernel.
1194 If you forget to do so, you can still manually specify the hints
1195 at the loader prompt:
1197 set hint.uart.0.at="isa"
1198 set hint.uart.0.port="0x3F8"
1199 set hint.uart.0.flags="0x10"
1200 set hint.uart.0.irq="4"
1204 The gpt(8) utility has been removed. Use gpart(8) to partition
1208 The version that Linuxulator emulates was changed from 2.4.2
1209 to 2.6.16. If you experience any problems with Linux binaries
1210 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1211 if it fixes the problem contact emulation mailing list.
1214 ISDN4BSD (I4B) was removed from the src tree. You may need to
1215 update a your kernel configuration and remove relevant entries.
1218 I have checked in code to support multiple routing tables.
1219 See the man pages setfib(1) and setfib(2).
1220 This is a hopefully backwards compatible version,
1221 but to make use of it you need to compile your kernel
1222 with options ROUTETABLES=2 (or more up to 16).
1225 The 802.11 wireless support was redone to enable multi-bss
1226 operation on devices that are capable. The underlying device
1227 is no longer used directly but instead wlanX devices are
1228 cloned with ifconfig. This requires changes to rc.conf files.
1229 For example, change:
1230 ifconfig_ath0="WPA DHCP"
1233 ifconfig_wlan0="WPA DHCP"
1234 see rc.conf(5) for more details. In addition, mergemaster of
1235 /etc/rc.d is highly recommended. Simultaneous update of userland
1236 and kernel wouldn't hurt either.
1238 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1239 modules were merged into the base wlan module. All references
1240 to these modules (e.g. in kernel config files) must be removed.
1243 psm(4) has gained write(2) support in native operation level.
1244 Arbitrary commands can be written to /dev/psm%d and status can
1245 be read back from it. Therefore, an application is responsible
1246 for status validation and error recovery. It is a no-op in
1247 other operation levels.
1250 Support for KSE threading has been removed from the kernel. To
1251 run legacy applications linked against KSE libmap.conf may
1252 be used. The following libmap.conf may be used to ensure
1253 compatibility with any prior release:
1255 libpthread.so.1 libthr.so.1
1256 libpthread.so.2 libthr.so.2
1257 libkse.so.3 libthr.so.3
1260 The layout of struct vmspace has changed. This affects libkvm
1261 and any executables that link against libkvm and use the
1262 kvm_getprocs() function. In particular, but not exclusively,
1263 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1264 The effects are minimal, but it's advisable to upgrade world
1268 The latest em driver no longer has support in it for the
1269 82575 adapter, this is now moved to the igb driver. The
1270 split was done to make new features that are incompatible
1271 with older hardware easier to do.
1274 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1275 likewise the kernel option is now GEOM_LINUX_LVM.
1278 The default NFS mount mode has changed from UDP to TCP for
1279 increased reliability. If you rely on (insecurely) NFS
1280 mounting across a firewall you may need to update your
1284 Belatedly note the addition of m_collapse for compacting
1288 The fts(3) structures have been changed to use adequate
1289 integer types for their members and so to be able to cope
1290 with huge file trees. The old fts(3) ABI is preserved
1291 through symbol versioning in libc, so third-party binaries
1292 using fts(3) should still work, although they will not take
1293 advantage of the extended types. At the same time, some
1294 third-party software might fail to build after this change
1295 due to unportable assumptions made in its source code about
1296 fts(3) structure members. Such software should be fixed
1297 by its vendor or, in the worst case, in the ports tree.
1298 FreeBSD_version 800015 marks this change for the unlikely
1299 case that a portable fix is impossible.
1302 To upgrade to -current after this date, you must be running
1303 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1304 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1307 The ADAPTIVE_GIANT kernel option has been retired because its
1308 functionality is the default now.
1311 The AT keyboard emulation of sunkbd(4) has been turned on
1312 by default. In order to make the special symbols of the Sun
1313 keyboards driven by sunkbd(4) work under X these now have
1314 to be configured the same way as Sun USB keyboards driven
1315 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1317 Option "XkbLayout" "us"
1318 Option "XkbRules" "xorg"
1319 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1322 It has been decided that it is desirable to provide ABI
1323 backwards compatibility to the FreeBSD 4/5/6 versions of the
1324 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1325 broken with the introduction of PCI domain support (see the
1326 20070930 entry). Unfortunately, this required the ABI of
1327 PCIOCGETCONF to be broken again in order to be able to
1328 provide backwards compatibility to the old version of that
1329 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1330 again. As for prominent ports this affects neither pciutils
1331 nor xorg-server this time, the hal port needs to be rebuilt
1335 The misnamed kthread_create() and friends have been renamed
1336 to kproc_create() etc. Many of the callers already
1337 used kproc_start()..
1338 I will return kthread_create() and friends in a while
1339 with implementations that actually create threads, not procs.
1340 Renaming corresponds with version 800002.
1349 Avoid using make -j when upgrading. While generally safe, there are
1350 sometimes problems using -j to upgrade. If your upgrade fails with
1351 -j, please try again without -j. From time to time in the past there
1352 have been problems using -j with buildworld and/or installworld. This
1353 is especially true when upgrading between "distant" versions (eg one
1354 that cross a major release boundary or several minor releases, or when
1355 several months have passed on the -current branch).
1357 Sometimes, obscure build problems are the result of environment
1358 poisoning. This can happen because the make utility reads its
1359 environment when searching for values for global variables. To run
1360 your build attempts in an "environmental clean room", prefix all make
1361 commands with 'env -i '. See the env(1) manual page for more details.
1363 When upgrading from one major version to another it is generally best
1364 to upgrade to the latest code in the currently installed branch first,
1365 then do an upgrade to the new branch. This is the best-tested upgrade
1366 path, and has the highest probability of being successful. Please try
1367 this approach before reporting problems with a major version upgrade.
1371 When upgrading the boot ZFS pool to a new version, always follow
1374 1.) recompile and reinstall the ZFS boot loader and boot block
1375 (this is part of "make buildworld" and "make installworld")
1377 2.) update the ZFS boot block on your boot drive
1379 The following example updates the ZFS boot block on the first
1380 partition (freebsd-boot) of a GPT partitioned drive ad0:
1381 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1383 Non-boot pools do not need these updates.
1387 If you are updating from a prior version of FreeBSD (even one just
1388 a few days old), you should follow this procedure. It is the most
1389 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1391 make kernel-toolchain
1392 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1393 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1395 To test a kernel once
1396 ---------------------
1397 If you just want to boot a kernel once (because you are not sure
1398 if it works, or if you want to boot a known bad kernel to provide
1399 debugging information) run
1400 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1401 nextboot -k testkernel
1403 To just build a kernel when you know that it won't mess you up
1404 --------------------------------------------------------------
1405 This assumes you are already running a CURRENT system. Replace
1406 ${arch} with the architecture of your machine (e.g. "i386",
1407 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1409 cd src/sys/${arch}/conf
1410 config KERNEL_NAME_HERE
1411 cd ../compile/KERNEL_NAME_HERE
1416 If this fails, go to the "To build a kernel" section.
1418 To rebuild everything and install it on the current system.
1419 -----------------------------------------------------------
1420 # Note: sometimes if you are running current you gotta do more than
1421 # is listed here if you are upgrading from a really old current.
1423 <make sure you have good level 0 dumps>
1425 make kernel KERNCONF=YOUR_KERNEL_HERE
1427 <reboot in single user> [3]
1435 To cross-install current onto a separate partition
1436 --------------------------------------------------
1437 # In this approach we use a separate partition to hold
1438 # current's root, 'usr', and 'var' directories. A partition
1439 # holding "/", "/usr" and "/var" should be about 2GB in
1442 <make sure you have good level 0 dumps>
1445 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1446 <maybe newfs current's root partition>
1447 <mount current's root partition on directory ${CURRENT_ROOT}>
1448 make installworld DESTDIR=${CURRENT_ROOT}
1449 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1450 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1451 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1452 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1453 <reboot into current>
1454 <do a "native" rebuild/install as described in the previous section>
1455 <maybe install compatibility libraries from ports/misc/compat*>
1459 To upgrade in-place from 8.x-stable to current
1460 ----------------------------------------------
1461 <make sure you have good level 0 dumps>
1463 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1465 <reboot in single user> [3]
1472 Make sure that you've read the UPDATING file to understand the
1473 tweaks to various things you need. At this point in the life
1474 cycle of current, things change often and you are on your own
1475 to cope. The defaults can also change, so please read ALL of
1476 the UPDATING entries.
1478 Also, if you are tracking -current, you must be subscribed to
1479 freebsd-current@freebsd.org. Make sure that before you update
1480 your sources that you have read and understood all the recent
1481 messages there. If in doubt, please track -stable which has
1482 much fewer pitfalls.
1484 [1] If you have third party modules, such as vmware, you
1485 should disable them at this point so they don't crash your
1488 [3] From the bootblocks, boot -s, and then do
1493 adjkerntz -i # if CMOS is wall time
1494 Also, when doing a major release upgrade, it is required that
1495 you boot into single user mode to do the installworld.
1497 [4] Note: This step is non-optional. Failure to do this step
1498 can result in a significant reduction in the functionality of the
1499 system. Attempting to do it by hand is not recommended and those
1500 that pursue this avenue should read this file carefully, as well
1501 as the archives of freebsd-current and freebsd-hackers mailing lists
1502 for potential gotchas. The -U option is also useful to consider.
1503 See mergemaster(8) for more information.
1505 [5] Usually this step is a noop. However, from time to time
1506 you may need to do this if you get unknown user in the following
1507 step. It never hurts to do it all the time. You may need to
1508 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1509 install) after the buildworld before this step if you last updated
1510 from current before 20020224 or from -stable before 20020408.
1512 [6] This only deletes old files and directories. Old libraries
1513 can be deleted by "make delete-old-libs", but you have to make
1514 sure that no program is using those libraries anymore.
1516 [8] In order to have a kernel that can run the 4.x binaries needed to
1517 do an installworld, you must include the COMPAT_FREEBSD4 option in
1518 your kernel. Failure to do so may leave you with a system that is
1519 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1520 required to run the 5.x binaries on more recent kernels. And so on
1521 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1523 Make sure that you merge any new devices from GENERIC since the
1524 last time you updated your kernel config file.
1526 [9] When checking out sources, you must include the -P flag to have
1527 cvs prune empty directories.
1529 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1530 "?=" instead of the "=" assignment operator, so that buildworld can
1531 override the CPUTYPE if it needs to.
1533 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1534 not on the command line, or in /etc/make.conf. buildworld will
1535 warn if it is improperly defined.
1538 This file contains a list, in reverse chronological order, of major
1539 breakages in tracking -current. It is not guaranteed to be a complete
1540 list of such breakages, and only contains entries since October 10, 2007.
1541 If you need to see UPDATING entries from before that date, you will need
1542 to fetch an UPDATING file from an older FreeBSD release.
1544 Copyright information:
1546 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1548 Redistribution, publication, translation and use, with or without
1549 modification, in full or in part, in any form or format of this
1550 document are permitted without further permission from the author.
1552 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1553 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1554 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1555 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1556 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1557 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1558 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1559 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1560 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1561 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1562 POSSIBILITY OF SUCH DAMAGE.
1564 Contact Warner Losh if you have any questions about your use of