1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
15 The mergemaster command now uses the default MAKEOBJDIRPREFIX
16 rather than creating it's own in the temporary directory in
17 order allow access to bootstrapped versions of tools such as
18 install and mtree. When upgrading from version of FreeBSD where
19 the install command does not support -l, you will need to
20 install a new mergemaster command if mergemaster -p is required.
21 This can be accomplished with the command (cd src/usr.sbin/mergemaster
24 Due to the use of the new -l option to install(1) during build
25 and install, you must take care not to directly set the INSTALL
26 make variable in your /etc/make.conf, /etc/src.conf, or on the
27 command line. If you wish to use the -C flag for all installs
28 you may be able to add INSTALL+=-C to /etc/make.conf or
32 Fix a bug that allows NFS clients to issue READDIR on files.
35 The install(1) option -M has changed meaning and now takes an
36 argument that is a file or path to append logs to. In the
37 unlikely event that -M was the last option on the command line
38 and the command line contained at least two files and a target
39 directory the first file will have logs appended to it. The -M
40 option served little practical purpose in the last decade so it's
41 used expected to be extremely rare.
44 A new compression method (lz4) has been merged to. Please refer to
45 zpool-features(7) for more information.
47 Please refer to the "ZFS notes" section of this file for information
48 on upgrading boot ZFS pools.
51 The VFS KBI was changed with the merge of several nullfs
52 optimizations and fixes. All filesystem modules must be
56 With the addition of auditdistd(8), a new auditdistd user is now
57 depended on during installworld. "mergemaster -p" can be used to add
58 the user prior to installworld, as documented in the handbook.
64 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
65 Starting with this version the old system of ZFS pool versioning
66 is superseded by "feature flags". This concept enables forward
67 compatibility against certain future changes in functionality of ZFS
68 pools. The first two read-only compatible "feature flags" for ZFS
69 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
70 For more information read the new zpool-features(7) manual page.
71 Please refer to the "ZFS notes" section of this file for information
72 on upgrading boot ZFS pools.
75 The commit introducing bsd.compiler.mk breaks the traditional
76 building of kernels before this point. Add -m ${SRC}/share/mk
77 (for the right value of SRC) to your command lines to work
78 around; update your useland to a point after this; or use the
79 buildkernel/installkernel top-level targets. See also 20120829.
82 The IPFIREWALL_FORWARD kernel option has been removed. Its
83 functionality now turned on by default.
86 The random(4) support for the VIA hardware random number
87 generator (`PADLOCK') is no longer enabled unconditionally.
88 Add the PADLOCK_RNG option in the custom kernel config if
89 needed. The GENERIC kernels on i386 and amd64 do include the
90 option, so the change only affects the custom kernel
94 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
95 the traditional method, you must update your system with an installworld
96 before the kernel will build. The documented make buildkernel/installkernel
97 interfaces (coupled with fresh make kernel-toolchain) continue to work.
100 The sparc64 ZFS loader has been changed to no longer try to auto-
101 detect ZFS providers based on diskN aliases but now requires these
102 to be explicitly listed in the OFW boot-device environment variable.
105 Now unix domain sockets behave "as expected" on nullfs(5). Previously
106 nullfs(5) did not pass through all behaviours to the underlying layer,
107 as a result if we bound to a socket on the lower layer we could connect
108 only to the lower path; if we bound to the upper layer we could connect
109 only to the upper path. The new behavior is one can connect to both the
110 lower and the upper paths regardless what layer path one binds to.
113 The acpi_wmi(4) status device /dev/wmistat has been renamed to
117 A new VOP_ADVISE() was added to support posix_fadvise(2). All
118 filesystem modules must be recompiled.
121 The interface of the VOP_VPTOCNP(9) changed, now the returned
122 vnode shall be referenced, previously it was required to be
123 only held. All in-tree filesystems are converted.
129 The broken amd(4) driver has been replaced with esp(4) in the amd64,
130 i386 and pc98 GENERIC kernel configuration files.
133 This commit modifies vfs_register() so that it uses a hash
134 calculation to set vfc_typenum, which is enabled by default.
135 The first time a system is booted after this change, the
136 vfc_typenum values will change for all file systems. The
137 main effect of this is a change to the NFS server file handles
138 for file systems that use vfc_typenum in their fsid, such as ZFS.
139 It will, however, prevent vfc_typenum from changing when file
140 systems are loaded in a different order for subsequent reboots.
141 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
142 until you are ready to remount all NFS clients after a reboot.
145 Bump the shared library version numbers for libraries that
146 do not use symbol versioning, have changed the ABI compared
147 to stable/8 and which shared library version was not bumped.
148 Done as part of 9.0-RELEASE cycle.
151 During the merge of Capsicum features, the fget(9) KPI was modified.
152 This may require the rebuilding of out-of-tree device drivers --
153 issues have been reported specifically with the nVidia device driver.
154 __FreeBSD_version is bumped to 900041.
156 Also, there is a period between 20110811 and 20110814 where the
157 special devices /dev/{stdin,stdout,stderr} did not work correctly.
158 Building world from a kernel during that window may not work.
161 The packet filter (pf) code has been updated to OpenBSD 4.5.
162 You need to update userland tools to be in sync with kernel.
163 This update breaks backward compatibility with earlier pfsync(4)
164 versions. Care must be taken when updating redundant firewall setups.
167 The following sysctls and tunables are retired on x86 platforms:
169 machdep.hlt_logical_cpus
170 The following sysctl is retired:
171 machdep.hyperthreading_allowed
172 The sysctls were supposed to provide a way to dynamically offline and
173 online selected CPUs on x86 platforms, but the implementation has not
174 been reliable especially with SCHED_ULE scheduler.
175 machdep.hyperthreading_allowed tunable is still available to ignore
176 hyperthreading CPUs at OS level.
177 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
178 where X is an APIC ID of a CPU. Be advised, though, that disabling
179 CPUs in non-uniform fashion will result in non-uniform topology and
180 may lead to sub-optimal system performance with SCHED_ULE, which is
184 cpumask_t type is retired and cpuset_t is used in order to describe
188 Changes to ifconfig(8) for dynamic address family detection mandate
189 that you are running a kernel of 20110525 or later. Make sure to
190 follow the update procedure to boot a new kernel before installing
194 Support for sun4v architecture is officially dropped
197 Several KPI breaking changes have been committed to the mii(4) layer,
198 the PHY drivers and consequently some Ethernet drivers using mii(4).
199 This means that miibus.ko and the modules of the affected Ethernet
200 drivers need to be recompiled.
202 Note to kernel developers: Given that the OUI bit reversion problem
203 was fixed as part of these changes all mii(4) commits related to OUIs,
204 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
205 handling, no longer can be merged verbatim to stable/8 and previous
209 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
210 into their kernel configurations along with 'device pci'.
213 The default NFS client is now the new NFS client, so fstype "newnfs"
214 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
215 Although mounts via fstype "nfs" will usually work without userland
216 changes, it is recommended that the mount(8) and mount_nfs(8)
217 commands be rebuilt from sources and that a link to mount_nfs called
218 mount_oldnfs be created. The new client is compiled into the
219 kernel with "options NFSCL" and this is needed for diskless root
220 file systems. The GENERIC kernel configs have been changed to use
221 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
222 To use the regular/old client, you can "mount -t oldnfs ...". For
223 a diskless root file system, you must also include a line like:
225 vfs.root.mountfrom="oldnfs:"
227 in the boot/loader.conf on the root fs on the NFS server to make
228 a diskless root fs use the old client.
231 The GENERIC kernels for all architectures now default to the new
232 CAM-based ATA stack. It means that all legacy ATA drivers were
233 removed and replaced by respective CAM drivers. If you are using
234 ATA device names in /etc/fstab or other places, make sure to update
235 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
236 where 'Y's are the sequential numbers starting from zero for each type
237 in order of detection, unless configured otherwise with tunables,
238 see cam(4)). There will be symbolic links created in /dev/ to map
239 old adX devices to the respective adaY. They should provide basic
240 compatibility for file systems mounting in most cases, but they do
241 not support old user-level APIs and do not have respective providers
242 in GEOM. Consider using updated management tools with new device names.
244 It is possible to load devices ahci, ata, siis and mvs as modules,
245 but option ATA_CAM should remain in kernel configuration to make ata
246 module work as CAM driver supporting legacy ATA controllers. Device ata
247 still can be used in modular fashion (atacore + ...). Modules atadisk
248 and atapi* are not used and won't affect operation in ATA_CAM mode.
249 Note that to use CAM-based ATA kernel should include CAM devices
250 scbus, pass, da (or explicitly ada), cd and optionally others. All of
251 them are parts of the cam module.
253 ataraid(4) functionality is now supported by the RAID GEOM class.
254 To use it you can load geom_raid kernel module and use graid(8) tool
255 for management. Instead of /dev/arX device names, use /dev/raid/rX.
257 No kernel config options or code have been removed, so if a problem
258 arises, please report it and optionally revert to the old ATA stack.
259 In order to do it you can remove from the kernel config:
264 , and instead add back:
265 device atadisk # ATA disk drives
266 device ataraid # ATA RAID drives
267 device atapicd # ATAPI CDROM drives
268 device atapifd # ATAPI floppy drives
269 device atapist # ATAPI tape drives
272 The default NFS server has been changed to the new server, which
273 was referred to as the experimental server. If you need to switch
274 back to the old NFS server, you must now put the "-o" option on
275 both the mountd and nfsd commands. This can be done using the
276 mountd_flags and nfs_server_flags rc.conf variables until an
277 update to the rc scripts is committed, which is coming soon.
280 The GNU Objective-C runtime library (libobjc), and other Objective-C
281 related components have been removed from the base system. If you
282 require an Objective-C library, please use one of the available ports.
285 ath(4) has been split into bus- and device- modules. if_ath contains
286 the HAL, the TX rate control and the network device code. if_ath_pci
287 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
288 contains the AHB glue. Users need to load both if_ath_pci and if_ath
289 in order to use ath on everything else.
291 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
292 need to load if_ath and if_ath_pci for ath(4) operation.
295 As part of the replacement of sysinstall, the process of building
296 release media has changed significantly. For details, please re-read
297 release(7), which has been updated to reflect the new build process.
300 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
301 is the last available version under GPLv2. It brings a number of new
302 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
303 4.1 and SSE 4.2), better support for powerpc64, a number of new
304 directives, and lots of other small improvements. See the ChangeLog
305 file in contrib/binutils for the full details.
308 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
309 compliant, and will now use half of hash for authentication.
310 This will break interoperability with all stacks (including all
311 actual FreeBSD versions) who implement
312 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
314 The only workaround with such peers is to use another HMAC
315 algorithm for IPsec ("phase 2") authentication.
318 Remove the uio_yield prototype and symbol. This function has
319 been misnamed since it was introduced and should not be
320 globally exposed with this name. The equivalent functionality
321 is now available using kern_yield(curthread->td_user_pri).
322 The function remains undocumented.
325 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
326 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
327 for scalar sysctls is defined but disabled. Code that needs
328 UQUAD to pass the type checking that must compile on older
329 systems where the define is not present can check against
330 __FreeBSD_version >= 900030.
332 The system dialog(1) has been replaced with a new version previously
333 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
334 with the previous version, but the libdialog associated with it has
335 a largely incompatible API. As such, the original version of libdialog
336 will be kept temporarily as libodialog, until its base system consumers
337 are replaced or updated. Bump __FreeBSD_version to 900030.
340 If you are trying to run make universe on a -stable system, and you get
341 the following warning:
342 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
343 unknown. config(8) likely too old."
344 or something similar to it, then you must upgrade your -stable system
345 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
346 stable/8) or build the config from the latest stable/8 branch and
347 install it on your system.
349 Prior to this date, building a current universe on 8-stable system from
350 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
351 error in the first kernel build phase. A new config on those old
352 systems will fix that problem for older versions of -current.
355 The TCP stack has been modified to allow Khelp modules to interact with
356 it via helper hook points and store per-connection data in the TCP
357 control block. Bump __FreeBSD_version to 900029. User space tools that
358 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
362 Generic IEEE 802.3 annex 31B full duplex flow control support has been
363 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
364 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
365 to take advantage of it instead of using custom implementations. This
366 means that these drivers now no longer unconditionally advertise
367 support for flow control but only do so if flow control is a selected
368 media option. This was implemented in the generic support that way in
369 order to allow flow control to be switched on and off via ifconfig(8)
370 with the PHY specific default to typically off in order to protect
371 from unwanted effects. Consequently, if you used flow control with
372 one of the above mentioned drivers you now need to explicitly enable
374 ifconfig bge0 media auto mediaopt flowcontrol
376 Along with the above mentioned changes generic support for setting
377 1000baseT master mode also has been added and brgphy(4), ciphy(4),
378 e1000phy(4) as well as ip1000phy(4) have been converted to take
379 advantage of it. This means that these drivers now no longer take the
380 link0 parameter for selecting master mode but the master media option
381 has to be used instead, for example like in the following:
382 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
384 Selection of master mode now is also available with all other PHY
385 drivers supporting 1000baseT.
388 The TCP stack has received a significant update to add support for
389 modularised congestion control and generally improve the clarity of
390 congestion control decisions. Bump __FreeBSD_version to 900025. User
391 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
392 sockstat) need to be recompiled.
395 The man(1) utility has been replaced by a new version that no longer
396 uses /etc/manpath.config. Please consult man.conf(5) for how to
397 migrate local entries to the new format.
400 The copyright strings printed by login(1) and sshd(8) at the time of a
401 new connection have been removed to follow other operating systems and
405 A workaround for a fixed ld bug has been removed in kernel code,
406 so make sure that your system ld is built from sources after
407 revision 210245 from 2010-07-19 (r211583 if building head kernel
408 on stable/8, r211584 for stable/7; both from 2010-08-21).
409 A symptom of incorrect ld version is different addresses for
410 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
413 The $ipv6_prefer variable in rc.conf(5) has been split into
414 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
416 The $ip6addrctl_policy is a variable to choose a pre-defined
417 address selection policy set by ip6addrctl(8). A value
418 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
421 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
422 flag (see an entry of 20090926) is set on an interface with no
423 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
424 security reason. If you want IPv6 link-local address on all
425 interfaces by default, set this to "YES".
427 The old ipv6_prefer="YES" is equivalent to
428 ipv6_activate_all_interfaces="YES" and
429 ip6addrctl_policy="ipv6_prefer".
432 DTrace has grown support for userland tracing. Due to this, DTrace is
433 now i386 and amd64 only.
434 dtruss(1) is now installed by default on those systems and a new
435 kernel module is needed for userland tracing: fasttrap.
436 No changes to your kernel config file are necessary to enable
437 userland tracing, but you might consider adding 'STRIP=' and
438 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
439 to have informative userland stack traces in DTrace (ustack).
442 The acpi_aiboost(4) driver has been removed in favor of the new
443 aibs(4) driver. You should update your kernel configuration file.
446 BSD grep has been imported to the base system and it is built by
447 default. It is completely BSD licensed, highly GNU-compatible, uses
448 less memory than its GNU counterpart and has a small codebase.
449 However, it is slower than its GNU counterpart, which is mostly
450 noticeable for larger searches, for smaller ones it is measurable
451 but not significant. The reason is complex, the most important factor
452 is that we lack a modern and efficient regex library and GNU
453 overcomes this by optimizing the searches internally. Future work
454 on improving the regex performance is planned, for the meantime,
455 users that need better performance, can build GNU grep instead by
456 setting the WITH_GNU_GREP knob.
459 Due to the import of powerpc64 support, all existing powerpc kernel
460 configuration files must be updated with a machine directive like this:
461 machine powerpc powerpc
463 In addition, an updated config(8) is required to build powerpc kernels
467 A new version of ZFS (version 15) has been merged to -HEAD.
468 This version uses a python library for the following subcommands:
469 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
470 For full functionality of these commands the following port must
471 be installed: sysutils/py-zfs
474 'vm_page's are now hashed by physical address to an array of mutexes.
475 Currently this is only used to serialize access to hold_count. Over
476 time the page queue mutex will be peeled away. This changes the size
477 of pmap on every architecture. And requires all callers of vm_page_hold
478 and vm_page_unhold to be updated.
481 WITH_CTF can now be specified in src.conf (not recommended, there
482 are some problems with static executables), make.conf (would also
483 affect ports which do not use GNU make and do not override the
484 compile targets) or in the kernel config (via "makeoptions
486 When WITH_CTF was specified there before this was silently ignored,
487 so make sure that WITH_CTF is not used in places which could lead
488 to unwanted behavior.
491 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
492 to allow 32-bit compatibility on non-x86 platforms. All kernel
493 configurations on amd64 and ia64 platforms using these options must
494 be modified accordingly.
497 The utmp user accounting database has been replaced with utmpx,
498 the user accounting interface standardized by POSIX.
499 Unfortunately the semantics of utmp and utmpx don't match,
500 making it practically impossible to support both interfaces.
501 The user accounting database is used by tools like finger(1),
502 last(1), talk(1), w(1) and ac(8).
504 All applications in the base system use utmpx. This means only
505 local binaries (e.g. from the ports tree) may still use these
506 utmp database files. These applications must be rebuilt to make
509 After the system has been upgraded, it is safe to remove the old
510 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
511 assuming their contents is of no importance anymore. Old wtmp
512 databases can only be used by last(1) and ac(8) after they have
513 been converted to the new format using wtmpcvt(1).
516 Introduce the kernel thread "deadlock resolver" (which can be enabled
517 via the DEADLKRES option, see NOTES for more details) and the
518 sleepq_type() function for sleepqueues.
521 The rc.firewall and rc.firewall6 were unified, and
522 rc.firewall6 and rc.d/ip6fw were removed.
523 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
524 variables are obsoleted. Instead, the following new rc
525 variables are added to rc.d/ipfw:
527 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
528 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
529 firewall_simple_onet_ipv6, firewall_trusted_ipv6
531 The meanings correspond to the relevant IPv4 variables.
537 The default terminal emulation for syscons(4) has been changed
538 from cons25 to xterm on all platforms except pc98. This means
539 that the /etc/ttys file needs to be updated to ensure correct
540 operation of applications on the console.
542 The terminal emulation style can be toggled per window by using
543 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
544 options can be used to change the compile-time default back to
547 To prevent graphical artifacts, make sure the TERM environment
548 variable is set to match the terminal emulation that is being
549 performed by syscons(4).
552 The layout of the structure ieee80211req_scan_result has changed.
553 Applications that require wireless scan results (e.g. ifconfig(8))
554 from net80211 need to be recompiled.
556 Applications such as wpa_supplicant(8) may require a full world
557 build without using NO_CLEAN in order to get synchronized with the
561 The iwn(4) driver has been updated to support the 5000 and 5150 series.
562 There's one kernel module for each firmware. Adding "device iwnfw"
563 to the kernel configuration file means including all three firmware
564 images inside the kernel. If you want to include just the one for
565 your wireless card, use the devices iwn4965fw, iwn5000fw or
569 The rc.d/network_ipv6, IPv6 configuration script has been integrated
570 into rc.d/netif. The changes are the following:
572 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
573 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
574 Note that both variables need the "inet6" keyword at the head.
576 Do not set $ipv6_network_interfaces manually if you do not
577 understand what you are doing. It is not needed in most cases.
579 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
582 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
583 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
585 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
586 all configured interfaces have "inet6 accept_rtadv" in the
587 $ifconfig_IF_ipv6. These are for backward compatibility.
589 3. A new variable $ipv6_prefer has been added. If NO, IPv6
590 functionality of interfaces with no corresponding
591 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
592 and the default address selection policy of ip6addrctl(8)
593 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
594 Note that if you want to configure IPv6 functionality on the
595 disabled interfaces after boot, first you need to clear the flag by
596 using ifconfig(8) like:
598 ifconfig em0 inet6 -ifdisabled
600 If YES, the default address selection policy is set as
603 The default value of $ipv6_prefer is NO.
605 4. If your system need to receive Router Advertisement messages,
606 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
607 scripts automatically invoke rtsol(8) when the interface becomes
608 UP. The Router Advertisement messages are used for SLAAC
609 (State-Less Address AutoConfiguration).
612 802.11s D3.03 support was committed. This is incompatible with the
613 previous code, which was based on D3.0.
616 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
617 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
618 control whether accepting Router Advertisement messages or not.
619 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
620 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
621 The ifconfig(8) utility now supports these flags.
624 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
625 mount(8) and -a option for df(1) to see them.
628 The old tunable hw.bus.devctl_disable has been superseded by
629 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
630 replaced by hw.bus.devctl_queue=0. The default for this new tunable
634 Remove the option STOP_NMI. The default action is now to use NMI only
635 for KDB via the newly introduced function stop_cpus_hard() and
636 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
639 The stable/8 branch created in subversion. This corresponds to the
640 RELENG_8 branch in CVS.
643 Bump the shared library version numbers for all libraries that do not
644 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
645 __FreeBSD_version to 800105.
648 Due to changes in the implementation of virtual network stack support,
649 all network-related kernel modules must be recompiled. As this change
650 breaks the ABI, bump __FreeBSD_version to 800104.
653 The TOE interface to the TCP syncache has been modified to remove
654 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
655 The cxgb driver is the only TOE consumer affected by this change, and
656 needs to be recompiled along with the kernel. As this change breaks
657 the ABI, bump __FreeBSD_version to 800103.
660 Padding has been added to struct tcpcb, sackhint and tcpstat in
661 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
662 maintaining the ABI. However, this change breaks the ABI, so bump
663 __FreeBSD_version to 800102. User space tools that rely on the size of
664 any of these structs (e.g. sockstat) need to be recompiled.
667 The NFS_LEGACYRPC option has been removed along with the old kernel
668 RPC implementation that this option selected. Kernel configurations
669 may need to be adjusted.
672 The network interface device nodes at /dev/net/<interface> have been
673 removed. All ioctl operations can be performed the normal way using
674 routing sockets. The kqueue functionality can generally be replaced
675 with routing sockets.
678 The documentation from the FreeBSD Documentation Project (Handbook,
679 FAQ, etc.) is now installed via packages by sysinstall(8) and under
680 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
683 The ABI of various structures related to the SYSV IPC API have been
684 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
685 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
689 Layout of struct vnet has changed as routing related variables were
690 moved to their own Vimage module. Modules need to be recompiled. Bump
691 __FreeBSD_version to 800099.
694 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
695 respectively. As long as no more than 16 groups per process are used,
696 no changes should be visible. When more than 16 groups are used, old
697 binaries may fail if they call getgroups() or getgrouplist() with
698 statically sized storage. Recompiling will work around this, but
699 applications should be modified to use dynamically allocated storage
700 for group arrays as POSIX.1-2008 does not cap an implementation's
701 number of supported groups at NGROUPS_MAX+1 as previous versions did.
703 NFS and portalfs mounts may also be affected as the list of groups is
704 truncated to 16. Users of NFS who use more than 16 groups, should
705 take care that negative group permissions are not used on the exported
706 file systems as they will not be reliable unless a GSSAPI based
707 authentication method is used.
710 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
711 option compiles in the support for adaptive spinning for lockmgrs
712 which want to enable it. The lockinit() function now accepts the flag
713 LK_ADAPTIVE in order to make the lock object subject to adaptive
714 spinning when both held in write and read mode.
717 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
718 changed. User applications that use this ioctl need to be rebuilt.
721 The layout of struct thread has changed. Kernel and modules need to
725 The layout of structs ifnet, domain, protosw and vnet_net has changed.
726 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
729 window(1) has been removed from the base system. It can now be
730 installed from ports. The port is called misc/window.
733 The way we are storing and accessing `routing table' entries has
734 changed. Programs reading the FIB, like netstat, need to be
738 A new netisr implementation has been added for FreeBSD 8. Network
739 file system modules, such as igmp, ipdivert, and others, should be
741 Bump __FreeBSD_version to 800096.
744 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
748 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
749 Bump __FreeBSD_version to 800094.
752 Add mnt_xflag field to 'struct mount'. File system modules need to be
754 Bump __FreeBSD_version to 800093.
757 The compiling option ADAPTIVE_SX has been retired while it has been
758 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
759 The KPI for sx_init_flags() changes as accepting flags:
760 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
761 been introduced in order to handle the reversed logic.
762 Bump __FreeBSD_version to 800092.
765 Add support for hierarchical jails. Remove global securelevel.
766 Bump __FreeBSD_version to 800091.
769 The layout of struct vnet_net has changed, therefore modules
771 Bump __FreeBSD_version to 800090.
774 The newly imported zic(8) produces a new format in the output. Please
775 run tzsetup(8) to install the newly created data to /etc/localtime.
778 The sysctl tree for the usb stack has renamed from hw.usb2.* to
779 hw.usb.* and is now consistent again with previous releases.
782 802.11 monitor mode support was revised and driver api's were changed.
783 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
784 of DLT_IEEE802_11. No user-visible data structures were changed but
785 applications that use DLT_IEEE802_11 may require changes.
786 Bump __FreeBSD_version to 800088.
789 The layout of the following structs has changed: sysctl_oid,
790 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
791 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
792 panics may be experienced. World rebuild is required for
793 correctly checking networking state from userland.
794 Bump __FreeBSD_version to 800085.
797 MLDv2 and Source-Specific Multicast (SSM) have been merged
798 to the IPv6 stack. VIMAGE hooks are in but not yet used.
799 The implementation of SSM within FreeBSD's IPv6 stack closely
800 follows the IPv4 implementation.
802 For kernel developers:
804 * The most important changes are that the ip6_output() and
805 ip6_input() paths no longer take the IN6_MULTI_LOCK,
806 and this lock has been downgraded to a non-recursive mutex.
808 * As with the changes to the IPv4 stack to support SSM, filtering
809 of inbound multicast traffic must now be performed by transport
810 protocols within the IPv6 stack. This does not apply to TCP and
811 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
813 * The KPIs used by IPv6 multicast are similar to those used by
814 the IPv4 stack, with the following differences:
815 * im6o_mc_filter() is analogous to imo_multicast_filter().
816 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
817 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
818 * IN6_LOOKUP_MULTI() has been deprecated and removed.
819 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
820 for MLDv1 have an additional 'timer' argument which is used to
821 jitter the initial membership report for the solicited-node
822 multicast membership on-link.
823 * This is not strictly needed for MLDv2, which already jitters
824 its report transmissions. However, the 'timer' argument is
825 preserved in case MLDv1 is active on the interface.
827 * The KAME linked-list based IPv6 membership implementation has
828 been refactored to use a vector similar to that used by the IPv4
830 Code which maintains a list of its own multicast memberships
831 internally, e.g. carp, has been updated to reflect the new
834 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
835 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
836 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
837 implementation constraint which needs to be addressed in HEAD.
839 For application developers:
841 * The changes are broadly similar to those made for the IPv4
844 * The use of IPv4 and IPv6 multicast socket options on the same
845 socket, using mapped addresses, HAS NOT been tested or supported.
847 * There are a number of issues with the implementation of various
848 IPv6 multicast APIs which need to be resolved in the API surface
849 before the implementation is fully compatible with KAME userland
850 use, and these are mostly to do with interface index treatment.
852 * The literature available discusses the use of either the delta / ASM
853 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
854 using setsourcefilter(3)/getsourcefilter(3). For more information
855 please refer to RFC 3768, 'Socket Interface Extensions for
856 Multicast Source Filters'.
858 * Applications which use the published RFC 3678 APIs should be fine.
860 For systems administrators:
862 * The mtest(8) utility has been refactored to support IPv6, in
863 addition to IPv4. Interface addresses are no longer accepted
864 as arguments, their names must be used instead. The utility
865 will map the interface name to its first IPv4 address as
866 returned by getifaddrs(3).
868 * The ifmcstat(8) utility has also been updated to print the MLDv2
869 endpoint state and source filter lists via sysctl(3).
871 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
872 loopback of IPv6 multicast datagrams by default; it defaults to 1
873 to preserve the existing behaviour. Disabling multicast loopback is
874 recommended for optimal system performance.
876 * The IPv6 MROUTING code has been changed to examine this sysctl
877 instead of attempting to perform a group lookup before looping
878 back forwarded datagrams.
880 Bump __FreeBSD_version to 800084.
883 Implement low-level Bluetooth HCI API.
884 Bump __FreeBSD_version to 800083.
887 The layout of struct malloc_type, used by modules to register new
888 memory allocation types, has changed. Most modules will need to
889 be rebuilt or panics may be experienced.
890 Bump __FreeBSD_version to 800081.
893 Anticipate overflowing inp_flags - add inp_flags2.
894 This changes most offsets in inpcb, so checking v4 connection
895 state will require a world rebuild.
896 Bump __FreeBSD_version to 800080.
899 Add an llentry to struct route and struct route_in6. Modules
900 embedding a struct route will need to be recompiled.
901 Bump __FreeBSD_version to 800079.
904 The size of rt_metrics_lite and by extension rtentry has changed.
905 Networking administration apps will need to be recompiled.
906 The route command now supports show as an alias for get, weighting
907 of routes, sticky and nostick flags to alter the behavior of stateful
909 Bump __FreeBSD_version to 800078.
912 Do not use Giant for kbdmux(4) locking. This is wrong and
913 apparently causing more problems than it solves. This will
914 re-open the issue where interrupt handlers may race with
915 kbdmux(4) in polling mode. Typical symptoms include (but
916 not limited to) duplicated and/or missing characters when
917 low level console functions (such as gets) are used while
918 interrupts are enabled (for example geli password prompt,
919 mountroot prompt etc.). Disabling kbdmux(4) may help.
922 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
923 kernel modules referencing any of the above need to be recompiled.
924 Bump __FreeBSD_version to 800075.
927 GEOM_PART has become the default partition slicer for storage devices,
928 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
929 introduces some changes:
931 MSDOS/EBR: the devices created from MSDOS extended partition entries
932 (EBR) can be named differently than with GEOM_MBR and are now symlinks
933 to devices with offset-based names. fstabs may need to be modified.
935 BSD: the "geometry does not match label" warning is harmless in most
936 cases but it points to problems in file system misalignment with
937 disk geometry. The "c" partition is now implicit, covers the whole
938 top-level drive and cannot be (mis)used by users.
940 General: Kernel dumps are now not allowed to be written to devices
941 whose partition types indicate they are meant to be used for file
942 systems (or, in case of MSDOS partitions, as something else than
945 Most of these changes date approximately from 200812.
948 The uscanner(4) driver has been removed from the kernel. This follows
949 Linux removing theirs in 2.6 and making libusb the default interface
953 The multicast forwarding code has been cleaned up. netstat(1)
954 only relies on KVM now for printing bandwidth upcall meters.
955 The IPv4 and IPv6 modules are split into ip_mroute_mod and
956 ip6_mroute_mod respectively. The config(5) options for statically
957 compiling this code remain the same, i.e. 'options MROUTING'.
960 Support for the IFF_NEEDSGIANT network interface flag has been
961 removed, which means that non-MPSAFE network device drivers are no
962 longer supported. In particular, if_ar, if_sr, and network device
963 drivers from the old (legacy) USB stack can no longer be built or
967 POSIX.1 Native Language Support (NLS) has been enabled in libc and
968 a bunch of new language catalog files have also been added.
969 This means that some common libc messages are now localized and
970 they depend on the LC_MESSAGES environmental variable.
973 The k8temp(4) driver has been renamed to amdtemp(4) since
974 support for Family 10 and Family 11 CPU families was added.
977 IGMPv3 and Source-Specific Multicast (SSM) have been merged
978 to the IPv4 stack. VIMAGE hooks are in but not yet used.
980 For kernel developers, the most important changes are that the
981 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
982 and this lock has been downgraded to a non-recursive mutex.
984 Transport protocols (UDP, Raw IP) are now responsible for filtering
985 inbound multicast traffic according to group membership and source
986 filters. The imo_multicast_filter() KPI exists for this purpose.
987 Transports which do not use multicast (SCTP, TCP) already reject
988 multicast by default. Forwarding and receive performance may improve
989 as a mutex acquisition is no longer needed in the ip_input()
990 low-level input path. in_addmulti() and in_delmulti() are shimmed
991 to new KPIs which exist to support SSM in-kernel.
993 For application developers, it is recommended that loopback of
994 multicast datagrams be disabled for best performance, as this
995 will still cause the lock to be taken for each looped-back
996 datagram transmission. The net.inet.ip.mcast.loop sysctl may
997 be tuned to 0 to disable loopback by default; it defaults to 1
998 to preserve the existing behaviour.
1000 For systems administrators, to obtain best performance with
1001 multicast reception and multiple groups, it is always recommended
1002 that a card with a suitably precise hash filter is used. Hash
1003 collisions will still result in the lock being taken within the
1004 transport protocol input path to check group membership.
1006 If deploying FreeBSD in an environment with IGMP snooping switches,
1007 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1008 enabled; this forces 224.0.0.0/24 group membership to be announced
1011 The size of 'struct igmpstat' has changed; netstat needs to be
1012 recompiled to reflect this.
1013 Bump __FreeBSD_version to 800070.
1016 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1017 updated to use it. This requires a buildworld/installworld in order to
1018 update the library and dependencies (usbconfig, etc). Its advisable to
1019 rebuild all ports which uses libusb. More specific directions are given
1020 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1021 libusb are no longer required and can be removed.
1024 A workaround is committed to allow the creation of System V shared
1025 memory segment of size > 2 GB on the 64-bit architectures.
1026 Due to a limitation of the existing ABI, the shm_segsz member
1027 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1028 wrong for large segments. Note that limits must be explicitly
1029 raised to allow such segments to be created.
1032 The layout of struct ifnet has changed, requiring a rebuild of all
1033 network device driver modules.
1036 The /dev handling for the new USB stack has changed, a
1037 buildworld/installworld is required for libusb20.
1040 The new USB2 stack has now been permanently moved in and all kernel and
1041 module names reverted to their previous values (eg, usb, ehci, ohci,
1042 ums, ...). The old usb stack can be compiled in by prefixing the name
1043 with the letter 'o', the old usb modules have been removed.
1044 Updating entry 20090216 for xorg and 20090215 for libmap may still
1048 The rc.conf(5) option if_up_delay has been renamed to
1049 defaultroute_delay to better reflect its purpose. If you have
1050 customized this setting in /etc/rc.conf you need to update it to
1054 xorg 7.4 wants to configure its input devices via hald which does not
1055 yet work with USB2. If the keyboard/mouse does not work in xorg then
1057 Option "AllowEmptyInput" "off"
1058 to your ServerLayout section. This will cause X to use the configured
1059 kbd and mouse sections from your xorg.conf.
1062 The GENERIC kernels for all architectures now default to the new USB2
1063 stack. No kernel config options or code have been removed so if a
1064 problem arises please report it and optionally revert to the old USB
1065 stack. If you are loading USB kernel modules or have a custom kernel
1066 that includes GENERIC then ensure that usb names are also changed over,
1067 eg uftdi -> usb2_serial_ftdi.
1069 Older programs linked against the ports libusb 0.1 need to be
1070 redirected to the new stack's libusb20. /etc/libmap.conf can
1072 # Map old usb library to new one for usb2 stack
1073 libusb-0.1.so.8 libusb20.so.1
1076 All USB ethernet devices now attach as interfaces under the name ueN
1077 (eg. ue0). This is to provide a predictable name as vendors often
1078 change usb chipsets in a product without notice.
1081 The ichsmb(4) driver has been changed to require SMBus slave
1082 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1083 All of the other SMBus controller drivers require left-justified
1084 slave addresses, so this change makes all the drivers provide the
1088 INET6 statistics (struct ip6stat) was updated.
1089 netstat(1) needs to be recompiled.
1092 NTFS has been removed from GENERIC kernel on amd64 to match
1093 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1094 will load ntfs.ko module automatically when NTFS support is
1095 actually needed, unless ntfs.ko is not installed or security
1096 level prohibits loading kernel modules. If either is the case,
1097 "options NTFS" has to be added into kernel config.
1100 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1101 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1102 800061. User space tools that rely on the size of struct tcpcb in
1103 tcp_var.h (e.g. sockstat) need to be recompiled.
1106 ng_tty(4) module updated to match the new TTY subsystem.
1107 Due to API change, user-level applications must be updated.
1108 New API support added to mpd5 CVS and expected to be present
1109 in next mpd5.3 release.
1112 With __FreeBSD_version 800060 the makefs tool is part of
1113 the base system (it was a port).
1116 The afdata and ifnet locks have been changed from mutexes to
1117 rwlocks, network modules will need to be re-compiled.
1120 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1121 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1122 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1123 architecture and 40 bytes on 64-bit architecture. The userland
1124 applications "arp" and "ndp" have been updated accordingly.
1125 The output from "netstat -r" shows only routing entries and
1126 none of the L2 information.
1129 __FreeBSD_version 800057 marks the switchover from the
1130 binary ath hal to source code. Users must add the line:
1132 options AH_SUPPORT_AR5416
1134 to their kernel config files when specifying:
1138 The ath_hal module no longer exists; the code is now compiled
1139 together with the driver in the ath module. It is now
1140 possible to tailor chip support (i.e. reduce the set of chips
1141 and thereby the code size); consult ath_hal(4) for details.
1144 __FreeBSD_version 800054 adds memory barriers to
1145 <machine/atomic.h>, new interfaces to ifnet to facilitate
1146 multiple hardware transmit queues for cards that support
1147 them, and a lock-less ring-buffer implementation to
1148 enable drivers to more efficiently manage queueing of
1152 A new version of ZFS (version 13) has been merged to -HEAD.
1153 This version has zpool attribute "listsnapshots" off by
1154 default, which means "zfs list" does not show snapshots,
1155 and is the same as Solaris behavior.
1158 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1161 The uhci, ohci, ehci and slhci USB Host controller drivers have
1162 been put into separate modules. If you load the usb module
1163 separately through loader.conf you will need to load the
1164 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1165 controller add the following to loader.conf:
1171 The ABI used by the PMC toolset has changed. Please keep
1172 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1176 atapci kernel module now includes only generic PCI ATA
1177 driver. AHCI driver moved to ataahci kernel module.
1178 All vendor-specific code moved into separate kernel modules:
1179 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1180 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1181 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1182 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1185 The TTY subsystem of the kernel has been replaced by a new
1186 implementation, which provides better scalability and an
1187 improved driver model. Most common drivers have been migrated to
1188 the new TTY subsystem, while others have not. The following
1189 drivers have not yet been ported to the new TTY layer:
1192 cy, digi, rc, rp, sio
1198 ng_h4, ng_tty, ppp, sl, snp
1200 Adding these drivers to your kernel configuration file shall
1201 cause compilation to fail.
1204 ntpd has been upgraded to 4.2.4p5.
1207 OpenSSH has been upgraded to 5.1p1.
1209 For many years, FreeBSD's version of OpenSSH preferred DSA
1210 over RSA for host and user authentication keys. With this
1211 upgrade, we've switched to the vendor's default of RSA over
1212 DSA. This may cause upgraded clients to warn about unknown
1213 host keys even for previously known hosts. Users should
1214 follow the usual procedure for verifying host keys before
1215 accepting the RSA key.
1217 This can be circumvented by setting the "HostKeyAlgorithms"
1218 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1221 Please note that the sequence of keys offered for
1222 authentication has been changed as well. You may want to
1223 specify IdentityFile in a different order to revert this
1227 The sio(4) driver has been removed from the i386 and amd64
1228 kernel configuration files. This means uart(4) is now the
1229 default serial port driver on those platforms as well.
1231 To prevent collisions with the sio(4) driver, the uart(4) driver
1232 uses different names for its device nodes. This means the
1233 onboard serial port will now most likely be called "ttyu0"
1234 instead of "ttyd0". You may need to reconfigure applications to
1235 use the new device names.
1237 When using the serial port as a boot console, be sure to update
1238 /boot/device.hints and /etc/ttys before booting the new kernel.
1239 If you forget to do so, you can still manually specify the hints
1240 at the loader prompt:
1242 set hint.uart.0.at="isa"
1243 set hint.uart.0.port="0x3F8"
1244 set hint.uart.0.flags="0x10"
1245 set hint.uart.0.irq="4"
1249 The gpt(8) utility has been removed. Use gpart(8) to partition
1253 The version that Linuxulator emulates was changed from 2.4.2
1254 to 2.6.16. If you experience any problems with Linux binaries
1255 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1256 if it fixes the problem contact emulation mailing list.
1259 ISDN4BSD (I4B) was removed from the src tree. You may need to
1260 update a your kernel configuration and remove relevant entries.
1263 I have checked in code to support multiple routing tables.
1264 See the man pages setfib(1) and setfib(2).
1265 This is a hopefully backwards compatible version,
1266 but to make use of it you need to compile your kernel
1267 with options ROUTETABLES=2 (or more up to 16).
1270 The 802.11 wireless support was redone to enable multi-bss
1271 operation on devices that are capable. The underlying device
1272 is no longer used directly but instead wlanX devices are
1273 cloned with ifconfig. This requires changes to rc.conf files.
1274 For example, change:
1275 ifconfig_ath0="WPA DHCP"
1278 ifconfig_wlan0="WPA DHCP"
1279 see rc.conf(5) for more details. In addition, mergemaster of
1280 /etc/rc.d is highly recommended. Simultaneous update of userland
1281 and kernel wouldn't hurt either.
1283 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1284 modules were merged into the base wlan module. All references
1285 to these modules (e.g. in kernel config files) must be removed.
1288 psm(4) has gained write(2) support in native operation level.
1289 Arbitrary commands can be written to /dev/psm%d and status can
1290 be read back from it. Therefore, an application is responsible
1291 for status validation and error recovery. It is a no-op in
1292 other operation levels.
1295 Support for KSE threading has been removed from the kernel. To
1296 run legacy applications linked against KSE libmap.conf may
1297 be used. The following libmap.conf may be used to ensure
1298 compatibility with any prior release:
1300 libpthread.so.1 libthr.so.1
1301 libpthread.so.2 libthr.so.2
1302 libkse.so.3 libthr.so.3
1305 The layout of struct vmspace has changed. This affects libkvm
1306 and any executables that link against libkvm and use the
1307 kvm_getprocs() function. In particular, but not exclusively,
1308 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1309 The effects are minimal, but it's advisable to upgrade world
1313 The latest em driver no longer has support in it for the
1314 82575 adapter, this is now moved to the igb driver. The
1315 split was done to make new features that are incompatible
1316 with older hardware easier to do.
1319 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1320 likewise the kernel option is now GEOM_LINUX_LVM.
1323 The default NFS mount mode has changed from UDP to TCP for
1324 increased reliability. If you rely on (insecurely) NFS
1325 mounting across a firewall you may need to update your
1329 Belatedly note the addition of m_collapse for compacting
1333 The fts(3) structures have been changed to use adequate
1334 integer types for their members and so to be able to cope
1335 with huge file trees. The old fts(3) ABI is preserved
1336 through symbol versioning in libc, so third-party binaries
1337 using fts(3) should still work, although they will not take
1338 advantage of the extended types. At the same time, some
1339 third-party software might fail to build after this change
1340 due to unportable assumptions made in its source code about
1341 fts(3) structure members. Such software should be fixed
1342 by its vendor or, in the worst case, in the ports tree.
1343 FreeBSD_version 800015 marks this change for the unlikely
1344 case that a portable fix is impossible.
1347 To upgrade to -current after this date, you must be running
1348 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1349 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1352 The ADAPTIVE_GIANT kernel option has been retired because its
1353 functionality is the default now.
1356 The AT keyboard emulation of sunkbd(4) has been turned on
1357 by default. In order to make the special symbols of the Sun
1358 keyboards driven by sunkbd(4) work under X these now have
1359 to be configured the same way as Sun USB keyboards driven
1360 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1362 Option "XkbLayout" "us"
1363 Option "XkbRules" "xorg"
1364 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1367 It has been decided that it is desirable to provide ABI
1368 backwards compatibility to the FreeBSD 4/5/6 versions of the
1369 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1370 broken with the introduction of PCI domain support (see the
1371 20070930 entry). Unfortunately, this required the ABI of
1372 PCIOCGETCONF to be broken again in order to be able to
1373 provide backwards compatibility to the old version of that
1374 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1375 again. As for prominent ports this affects neither pciutils
1376 nor xorg-server this time, the hal port needs to be rebuilt
1380 The misnamed kthread_create() and friends have been renamed
1381 to kproc_create() etc. Many of the callers already
1382 used kproc_start()..
1383 I will return kthread_create() and friends in a while
1384 with implementations that actually create threads, not procs.
1385 Renaming corresponds with version 800002.
1394 Avoid using make -j when upgrading. While generally safe, there are
1395 sometimes problems using -j to upgrade. If your upgrade fails with
1396 -j, please try again without -j. From time to time in the past there
1397 have been problems using -j with buildworld and/or installworld. This
1398 is especially true when upgrading between "distant" versions (eg one
1399 that cross a major release boundary or several minor releases, or when
1400 several months have passed on the -current branch).
1402 Sometimes, obscure build problems are the result of environment
1403 poisoning. This can happen because the make utility reads its
1404 environment when searching for values for global variables. To run
1405 your build attempts in an "environmental clean room", prefix all make
1406 commands with 'env -i '. See the env(1) manual page for more details.
1408 When upgrading from one major version to another it is generally best
1409 to upgrade to the latest code in the currently installed branch first,
1410 then do an upgrade to the new branch. This is the best-tested upgrade
1411 path, and has the highest probability of being successful. Please try
1412 this approach before reporting problems with a major version upgrade.
1416 When upgrading the boot ZFS pool to a new version, always follow
1419 1.) recompile and reinstall the ZFS boot loader and boot block
1420 (this is part of "make buildworld" and "make installworld")
1422 2.) update the ZFS boot block on your boot drive
1424 The following example updates the ZFS boot block on the first
1425 partition (freebsd-boot) of a GPT partitioned drive ad0:
1426 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1428 Non-boot pools do not need these updates.
1432 If you are updating from a prior version of FreeBSD (even one just
1433 a few days old), you should follow this procedure. It is the most
1434 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1436 make kernel-toolchain
1437 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1438 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1440 To test a kernel once
1441 ---------------------
1442 If you just want to boot a kernel once (because you are not sure
1443 if it works, or if you want to boot a known bad kernel to provide
1444 debugging information) run
1445 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1446 nextboot -k testkernel
1448 To just build a kernel when you know that it won't mess you up
1449 --------------------------------------------------------------
1450 This assumes you are already running a CURRENT system. Replace
1451 ${arch} with the architecture of your machine (e.g. "i386",
1452 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1454 cd src/sys/${arch}/conf
1455 config KERNEL_NAME_HERE
1456 cd ../compile/KERNEL_NAME_HERE
1461 If this fails, go to the "To build a kernel" section.
1463 To rebuild everything and install it on the current system.
1464 -----------------------------------------------------------
1465 # Note: sometimes if you are running current you gotta do more than
1466 # is listed here if you are upgrading from a really old current.
1468 <make sure you have good level 0 dumps>
1470 make kernel KERNCONF=YOUR_KERNEL_HERE
1472 <reboot in single user> [3]
1480 To cross-install current onto a separate partition
1481 --------------------------------------------------
1482 # In this approach we use a separate partition to hold
1483 # current's root, 'usr', and 'var' directories. A partition
1484 # holding "/", "/usr" and "/var" should be about 2GB in
1487 <make sure you have good level 0 dumps>
1490 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1491 <maybe newfs current's root partition>
1492 <mount current's root partition on directory ${CURRENT_ROOT}>
1493 make installworld DESTDIR=${CURRENT_ROOT}
1494 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1495 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1496 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1497 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1498 <reboot into current>
1499 <do a "native" rebuild/install as described in the previous section>
1500 <maybe install compatibility libraries from ports/misc/compat*>
1504 To upgrade in-place from stable to current
1505 ----------------------------------------------
1506 <make sure you have good level 0 dumps>
1508 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1510 <reboot in single user> [3]
1517 Make sure that you've read the UPDATING file to understand the
1518 tweaks to various things you need. At this point in the life
1519 cycle of current, things change often and you are on your own
1520 to cope. The defaults can also change, so please read ALL of
1521 the UPDATING entries.
1523 Also, if you are tracking -current, you must be subscribed to
1524 freebsd-current@freebsd.org. Make sure that before you update
1525 your sources that you have read and understood all the recent
1526 messages there. If in doubt, please track -stable which has
1527 much fewer pitfalls.
1529 [1] If you have third party modules, such as vmware, you
1530 should disable them at this point so they don't crash your
1533 [3] From the bootblocks, boot -s, and then do
1538 adjkerntz -i # if CMOS is wall time
1539 Also, when doing a major release upgrade, it is required that
1540 you boot into single user mode to do the installworld.
1542 [4] Note: This step is non-optional. Failure to do this step
1543 can result in a significant reduction in the functionality of the
1544 system. Attempting to do it by hand is not recommended and those
1545 that pursue this avenue should read this file carefully, as well
1546 as the archives of freebsd-current and freebsd-hackers mailing lists
1547 for potential gotchas. The -U option is also useful to consider.
1548 See mergemaster(8) for more information.
1550 [5] Usually this step is a noop. However, from time to time
1551 you may need to do this if you get unknown user in the following
1552 step. It never hurts to do it all the time. You may need to
1553 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1554 install) after the buildworld before this step if you last updated
1555 from [78]-stable or 9-stable before 20130430.
1557 [6] This only deletes old files and directories. Old libraries
1558 can be deleted by "make delete-old-libs", but you have to make
1559 sure that no program is using those libraries anymore.
1561 [8] In order to have a kernel that can run the 4.x binaries needed to
1562 do an installworld, you must include the COMPAT_FREEBSD4 option in
1563 your kernel. Failure to do so may leave you with a system that is
1564 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1565 required to run the 5.x binaries on more recent kernels. And so on
1566 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1568 Make sure that you merge any new devices from GENERIC since the
1569 last time you updated your kernel config file.
1571 [9] When checking out sources, you must include the -P flag to have
1572 cvs prune empty directories.
1574 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1575 "?=" instead of the "=" assignment operator, so that buildworld can
1576 override the CPUTYPE if it needs to.
1578 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1579 not on the command line, or in /etc/make.conf. buildworld will
1580 warn if it is improperly defined.
1583 This file contains a list, in reverse chronological order, of major
1584 breakages in tracking -current. It is not guaranteed to be a complete
1585 list of such breakages, and only contains entries since October 10, 2007.
1586 If you need to see UPDATING entries from before that date, you will need
1587 to fetch an UPDATING file from an older FreeBSD release.
1589 Copyright information:
1591 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1593 Redistribution, publication, translation and use, with or without
1594 modification, in full or in part, in any form or format of this
1595 document are permitted without further permission from the author.
1597 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1598 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1599 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1600 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1601 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1602 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1603 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1604 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1605 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1606 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1607 POSSIBILITY OF SUCH DAMAGE.
1609 Contact Warner Losh if you have any questions about your use of