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