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 NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW:
13 FreeBSD 10.x has many debugging features turned on, in both the kernel
14 and userland. These features attempt to detect incorrect use of
15 system primitives, and encourage loud failure through extra sanity
16 checking and fail stop semantics. They also substantially impact
17 system performance. If you want to do performance measurement,
18 benchmarking, and optimization, you'll want to turn them off. This
19 includes various WITNESS- related kernel options, INVARIANTS, malloc
20 debugging flags in userland, and various verbose features in the
21 kernel. Many developers choose to disable these features on build
22 machines to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
26 The set_rcvar() function has been removed from /etc/rc.subr. All
27 base and ports rc.d scripts have been updated, so if you have a
28 port installed with a script in /usr/local/etc/rc.d you can either
29 hand-edit the rcvar= line, or reinstall the port.
31 An easy way to handle the mass-update of /etc/rc.d:
32 rm /etc/rc.d/* && mergemaster -i
35 panic(9) now stops other CPUs in the SMP systems, disables interrupts
36 on the current CPU and prevents other threads from running.
37 This behavior can be reverted using the kern.stop_scheduler_on_panic
39 The new behavior can be incompatible with kern.sync_on_panic.
42 The carp(4) facility has been changed significantly. Configuration
43 of the CARP protocol via ifconfig(8) has changed, as well as format
44 of CARP events submitted to devd(8) has changed. See manual pages
45 for more information. The arpbalance feature of carp(4) is currently
46 not supported anymore.
48 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
49 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
50 need to be recompiled.
53 The acpi_wmi(4) status device /dev/wmistat has been renamed to
57 The option VFS_ALLOW_NONMPSAFE option has been added in order to
58 explicitely support non-MPSAFE filesystems.
59 It is on by default for all supported platform at this present
63 The broken amd(4) driver has been replaced with esp(4) in the amd64,
64 i386 and pc98 GENERIC kernel configuration files.
67 sysinstall has been removed
70 The stable/9 branch created in subversion. This corresponds to the
71 RELENG_9 branch in CVS.
74 This commit modifies vfs_register() so that it uses a hash
75 calculation to set vfc_typenum, which is enabled by default.
76 The first time a system is booted after this change, the
77 vfc_typenum values will change for all file systems. The
78 main effect of this is a change to the NFS server file handles
79 for file systems that use vfc_typenum in their fsid, such as ZFS.
80 It will, however, prevent vfc_typenum from changing when file
81 systems are loaded in a different order for subsequent reboots.
82 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
83 until you are ready to remount all NFS clients after a reboot.
86 Bump the shared library version numbers for libraries that
87 do not use symbol versioning, have changed the ABI compared
88 to stable/8 and which shared library version was not bumped.
89 Done as part of 9.0-RELEASE cycle.
92 During the merge of Capsicum features, the fget(9) KPI was modified.
93 This may require the rebuilding of out-of-tree device drivers --
94 issues have been reported specifically with the nVidia device driver.
95 __FreeBSD_version is bumped to 900041.
97 Also, there is a period between 20110811 and 20110814 where the
98 special devices /dev/{stdin,stdout,stderr} did not work correctly.
99 Building world from a kernel during that window may not work.
102 The packet filter (pf) code has been updated to OpenBSD 4.5.
103 You need to update userland tools to be in sync with kernel.
104 This update breaks backward compatibility with earlier pfsync(4)
105 versions. Care must be taken when updating redundant firewall setups.
108 The following sysctls and tunables are retired on x86 platforms:
110 machdep.hlt_logical_cpus
111 The following sysctl is retired:
112 machdep.hyperthreading_allowed
113 The sysctls were supposed to provide a way to dynamically offline and
114 online selected CPUs on x86 platforms, but the implementation has not
115 been reliable especially with SCHED_ULE scheduler.
116 machdep.hyperthreading_allowed tunable is still available to ignore
117 hyperthreading CPUs at OS level.
118 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
119 where X is an APIC ID of a CPU. Be advised, though, that disabling
120 CPUs in non-uniform fashion will result in non-uniform topology and
121 may lead to sub-optimal system performance with SCHED_ULE, which is
125 cpumask_t type is retired and cpuset_t is used in order to describe
129 Changes to ifconfig(8) for dynamic address family detection mandate
130 that you are running a kernel of 20110525 or later. Make sure to
131 follow the update procedure to boot a new kernel before installing
135 Support for sun4v architecture is officially dropped
138 Several KPI breaking changes have been committed to the mii(4) layer,
139 the PHY drivers and consequently some Ethernet drivers using mii(4).
140 This means that miibus.ko and the modules of the affected Ethernet
141 drivers need to be recompiled.
143 Note to kernel developers: Given that the OUI bit reversion problem
144 was fixed as part of these changes all mii(4) commits related to OUIs,
145 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
146 handling, no longer can be merged verbatim to stable/8 and previous
150 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
151 into their kernel configurations along with 'device pci'.
154 The default NFS client is now the new NFS client, so fstype "newnfs"
155 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
156 Although mounts via fstype "nfs" will usually work without userland
157 changes, it is recommended that the mount(8) and mount_nfs(8)
158 commands be rebuilt from sources and that a link to mount_nfs called
159 mount_oldnfs be created. The new client is compiled into the
160 kernel with "options NFSCL" and this is needed for diskless root
161 file systems. The GENERIC kernel configs have been changed to use
162 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
163 To use the regular/old client, you can "mount -t oldnfs ...". For
164 a diskless root file system, you must also include a line like:
166 vfs.root.mountfrom="oldnfs:"
168 in the boot/loader.conf on the root fs on the NFS server to make
169 a diskless root fs use the old client.
172 The GENERIC kernels for all architectures now default to the new
173 CAM-based ATA stack. It means that all legacy ATA drivers were
174 removed and replaced by respective CAM drivers. If you are using
175 ATA device names in /etc/fstab or other places, make sure to update
176 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
177 where 'Y's are the sequential numbers starting from zero for each type
178 in order of detection, unless configured otherwise with tunables,
179 see cam(4)). There will be symbolic links created in /dev/ to map
180 old adX devices to the respective adaY. They should provide basic
181 compatibility for file systems mounting in most cases, but they do
182 not support old user-level APIs and do not have respective providers
183 in GEOM. Consider using updated management tools with new device names.
185 It is possible to load devices ahci, ata, siis and mvs as modules,
186 but option ATA_CAM should remain in kernel configuration to make ata
187 module work as CAM driver supporting legacy ATA controllers. Device ata
188 still can be used in modular fashion (atacore + ...). Modules atadisk
189 and atapi* are not used and won't affect operation in ATA_CAM mode.
190 Note that to use CAM-based ATA kernel should include CAM devices
191 scbus, pass, da (or explicitly ada), cd and optionally others. All of
192 them are parts of the cam module.
194 ataraid(4) functionality is now supported by the RAID GEOM class.
195 To use it you can load geom_raid kernel module and use graid(8) tool
196 for management. Instead of /dev/arX device names, use /dev/raid/rX.
198 No kernel config options or code have been removed, so if a problem
199 arises, please report it and optionally revert to the old ATA stack.
200 In order to do it you can remove from the kernel config:
205 , and instead add back:
206 device atadisk # ATA disk drives
207 device ataraid # ATA RAID drives
208 device atapicd # ATAPI CDROM drives
209 device atapifd # ATAPI floppy drives
210 device atapist # ATAPI tape drives
213 The default NFS server has been changed to the new server, which
214 was referred to as the experimental server. If you need to switch
215 back to the old NFS server, you must now put the "-o" option on
216 both the mountd and nfsd commands. This can be done using the
217 mountd_flags and nfs_server_flags rc.conf variables until an
218 update to the rc scripts is committed, which is coming soon.
221 The GNU Objective-C runtime library (libobjc), and other Objective-C
222 related components have been removed from the base system. If you
223 require an Objective-C library, please use one of the available ports.
226 ath(4) has been split into bus- and device- modules. if_ath contains
227 the HAL, the TX rate control and the network device code. if_ath_pci
228 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
229 contains the AHB glue. Users need to load both if_ath_pci and if_ath
230 in order to use ath on everything else.
232 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
233 need to load if_ath and if_ath_pci for ath(4) operation.
236 As part of the replacement of sysinstall, the process of building
237 release media has changed significantly. For details, please re-read
238 release(7), which has been updated to reflect the new build process.
241 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
242 is the last available version under GPLv2. It brings a number of new
243 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
244 4.1 and SSE 4.2), better support for powerpc64, a number of new
245 directives, and lots of other small improvements. See the ChangeLog
246 file in contrib/binutils for the full details.
249 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
250 compliant, and will now use half of hash for authentication.
251 This will break interoperability with all stacks (including all
252 actual FreeBSD versions) who implement
253 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
255 The only workaround with such peers is to use another HMAC
256 algorithm for IPsec ("phase 2") authentication.
259 Remove the uio_yield prototype and symbol. This function has
260 been misnamed since it was introduced and should not be
261 globally exposed with this name. The equivalent functionality
262 is now available using kern_yield(curthread->td_user_pri).
263 The function remains undocumented.
266 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
267 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
268 for scalar sysctls is defined but disabled. Code that needs
269 UQUAD to pass the type checking that must compile on older
270 systems where the define is not present can check against
271 __FreeBSD_version >= 900030.
273 The system dialog(1) has been replaced with a new version previously
274 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
275 with the previous version, but the libdialog associated with it has
276 a largely incompatible API. As such, the original version of libdialog
277 will be kept temporarily as libodialog, until its base system consumers
278 are replaced or updated. Bump __FreeBSD_version to 900030.
281 If you are trying to run make universe on a -stable system, and you get
282 the following warning:
283 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
284 unknown. config(8) likely too old."
285 or something similar to it, then you must upgrade your -stable system
286 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
287 stable/8) or build the config from the latest stable/8 branch and
288 install it on your system.
290 Prior to this date, building a current universe on 8-stable system from
291 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
292 error in the first kernel build phase. A new config on those old
293 systems will fix that problem for older versions of -current.
296 The TCP stack has been modified to allow Khelp modules to interact with
297 it via helper hook points and store per-connection data in the TCP
298 control block. Bump __FreeBSD_version to 900029. User space tools that
299 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
303 Generic IEEE 802.3 annex 31B full duplex flow control support has been
304 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
305 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
306 to take advantage of it instead of using custom implementations. This
307 means that these drivers now no longer unconditionally advertise
308 support for flow control but only do so if flow control is a selected
309 media option. This was implemented in the generic support that way in
310 order to allow flow control to be switched on and off via ifconfig(8)
311 with the PHY specific default to typically off in order to protect
312 from unwanted effects. Consequently, if you used flow control with
313 one of the above mentioned drivers you now need to explicitly enable
315 ifconfig bge0 media auto mediaopt flowcontrol
317 Along with the above mentioned changes generic support for setting
318 1000baseT master mode also has been added and brgphy(4), ciphy(4),
319 e1000phy(4) as well as ip1000phy(4) have been converted to take
320 advantage of it. This means that these drivers now no longer take the
321 link0 parameter for selecting master mode but the master media option
322 has to be used instead, for example like in the following:
323 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
325 Selection of master mode now is also available with all other PHY
326 drivers supporting 1000baseT.
329 The TCP stack has received a significant update to add support for
330 modularised congestion control and generally improve the clarity of
331 congestion control decisions. Bump __FreeBSD_version to 900025. User
332 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
333 sockstat) need to be recompiled.
336 The man(1) utility has been replaced by a new version that no longer
337 uses /etc/manpath.config. Please consult man.conf(5) for how to
338 migrate local entries to the new format.
341 The copyright strings printed by login(1) and sshd(8) at the time of a
342 new connection have been removed to follow other operating systems and
346 A workaround for a fixed ld bug has been removed in kernel code,
347 so make sure that your system ld is built from sources after
348 revision 210245 from 2010-07-19 (r211583 if building head kernel
349 on stable/8, r211584 for stable/7; both from 2010-08-21).
350 A symptom of incorrect ld version is different addresses for
351 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
354 The $ipv6_prefer variable in rc.conf(5) has been split into
355 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
357 The $ip6addrctl_policy is a variable to choose a pre-defined
358 address selection policy set by ip6addrctl(8). A value
359 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
362 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
363 flag (see an entry of 20090926) is set on an interface with no
364 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
365 security reason. If you want IPv6 link-local address on all
366 interfaces by default, set this to "YES".
368 The old ipv6_prefer="YES" is equivalent to
369 ipv6_activate_all_interfaces="YES" and
370 ip6addrctl_policy="ipv6_prefer".
373 DTrace has grown support for userland tracing. Due to this, DTrace is
374 now i386 and amd64 only.
375 dtruss(1) is now installed by default on those systems and a new
376 kernel module is needed for userland tracing: fasttrap.
377 No changes to your kernel config file are necessary to enable
378 userland tracing, but you might consider adding 'STRIP=' and
379 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
380 to have informative userland stack traces in DTrace (ustack).
383 The acpi_aiboost(4) driver has been removed in favor of the new
384 aibs(4) driver. You should update your kernel configuration file.
387 BSD grep has been imported to the base system and it is built by
388 default. It is completely BSD licensed, highly GNU-compatible, uses
389 less memory than its GNU counterpart and has a small codebase.
390 However, it is slower than its GNU counterpart, which is mostly
391 noticeable for larger searches, for smaller ones it is measurable
392 but not significant. The reason is complex, the most important factor
393 is that we lack a modern and efficient regex library and GNU
394 overcomes this by optimizing the searches internally. Future work
395 on improving the regex performance is planned, for the meantime,
396 users that need better performance, can build GNU grep instead by
397 setting the WITH_GNU_GREP knob.
400 Due to the import of powerpc64 support, all existing powerpc kernel
401 configuration files must be updated with a machine directive like this:
402 machine powerpc powerpc
404 In addition, an updated config(8) is required to build powerpc kernels
408 A new version of ZFS (version 15) has been merged to -HEAD.
409 This version uses a python library for the following subcommands:
410 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
411 For full functionality of these commands the following port must
412 be installed: sysutils/py-zfs
415 'vm_page's are now hashed by physical address to an array of mutexes.
416 Currently this is only used to serialize access to hold_count. Over
417 time the page queue mutex will be peeled away. This changes the size
418 of pmap on every architecture. And requires all callers of vm_page_hold
419 and vm_page_unhold to be updated.
422 WITH_CTF can now be specified in src.conf (not recommended, there
423 are some problems with static executables), make.conf (would also
424 affect ports which do not use GNU make and do not override the
425 compile targets) or in the kernel config (via "makeoptions
427 When WITH_CTF was specified there before this was silently ignored,
428 so make sure that WITH_CTF is not used in places which could lead
429 to unwanted behavior.
432 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
433 to allow 32-bit compatibility on non-x86 platforms. All kernel
434 configurations on amd64 and ia64 platforms using these options must
435 be modified accordingly.
438 The utmp user accounting database has been replaced with utmpx,
439 the user accounting interface standardized by POSIX.
440 Unfortunately the semantics of utmp and utmpx don't match,
441 making it practically impossible to support both interfaces.
442 The user accounting database is used by tools like finger(1),
443 last(1), talk(1), w(1) and ac(8).
445 All applications in the base system use utmpx. This means only
446 local binaries (e.g. from the ports tree) may still use these
447 utmp database files. These applications must be rebuilt to make
450 After the system has been upgraded, it is safe to remove the old
451 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
452 assuming their contents is of no importance anymore. Old wtmp
453 databases can only be used by last(1) and ac(8) after they have
454 been converted to the new format using wtmpcvt(1).
457 Introduce the kernel thread "deadlock resolver" (which can be enabled
458 via the DEADLKRES option, see NOTES for more details) and the
459 sleepq_type() function for sleepqueues.
462 The rc.firewall and rc.firewall6 were unified, and
463 rc.firewall6 and rc.d/ip6fw were removed.
464 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
465 variables are obsoleted. Instead, the following new rc
466 variables are added to rc.d/ipfw:
468 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
469 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
470 firewall_simple_onet_ipv6, firewall_trusted_ipv6
472 The meanings correspond to the relevant IPv4 variables.
478 The default terminal emulation for syscons(4) has been changed
479 from cons25 to xterm on all platforms except pc98. This means
480 that the /etc/ttys file needs to be updated to ensure correct
481 operation of applications on the console.
483 The terminal emulation style can be toggled per window by using
484 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
485 options can be used to change the compile-time default back to
488 To prevent graphical artifacts, make sure the TERM environment
489 variable is set to match the terminal emulation that is being
490 performed by syscons(4).
493 The layout of the structure ieee80211req_scan_result has changed.
494 Applications that require wireless scan results (e.g. ifconfig(8))
495 from net80211 need to be recompiled.
497 Applications such as wpa_supplicant(8) may require a full world
498 build without using NO_CLEAN in order to get synchronized with the
502 The iwn(4) driver has been updated to support the 5000 and 5150 series.
503 There's one kernel module for each firmware. Adding "device iwnfw"
504 to the kernel configuration file means including all three firmware
505 images inside the kernel. If you want to include just the one for
506 your wireless card, use the devices iwn4965fw, iwn5000fw or
510 The rc.d/network_ipv6, IPv6 configuration script has been integrated
511 into rc.d/netif. The changes are the following:
513 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
514 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
515 Note that both variables need the "inet6" keyword at the head.
517 Do not set $ipv6_network_interfaces manually if you do not
518 understand what you are doing. It is not needed in most cases.
520 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
523 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
524 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
526 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
527 all configured interfaces have "inet6 accept_rtadv" in the
528 $ifconfig_IF_ipv6. These are for backward compatibility.
530 3. A new variable $ipv6_prefer has been added. If NO, IPv6
531 functionality of interfaces with no corresponding
532 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
533 and the default address selection policy of ip6addrctl(8)
534 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
535 Note that if you want to configure IPv6 functionality on the
536 disabled interfaces after boot, first you need to clear the flag by
537 using ifconfig(8) like:
539 ifconfig em0 inet6 -ifdisabled
541 If YES, the default address selection policy is set as
544 The default value of $ipv6_prefer is NO.
546 4. If your system need to receive Router Advertisement messages,
547 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
548 scripts automatically invoke rtsol(8) when the interface becomes
549 UP. The Router Advertisement messages are used for SLAAC
550 (State-Less Address AutoConfiguration).
553 802.11s D3.03 support was committed. This is incompatible with the
554 previous code, which was based on D3.0.
557 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
558 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
559 control whether accepting Router Advertisement messages or not.
560 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
561 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
562 The ifconfig(8) utility now supports these flags.
565 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
566 mount(8) and -a option for df(1) to see them.
569 The old tunable hw.bus.devctl_disable has been superseded by
570 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
571 replaced by hw.bus.devctl_queue=0. The default for this new tunable
575 Remove the option STOP_NMI. The default action is now to use NMI only
576 for KDB via the newly introduced function stop_cpus_hard() and
577 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
580 The stable/8 branch created in subversion. This corresponds to the
581 RELENG_8 branch in CVS.
584 Bump the shared library version numbers for all libraries that do not
585 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
586 __FreeBSD_version to 800105.
589 Due to changes in the implementation of virtual network stack support,
590 all network-related kernel modules must be recompiled. As this change
591 breaks the ABI, bump __FreeBSD_version to 800104.
594 The TOE interface to the TCP syncache has been modified to remove
595 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
596 The cxgb driver is the only TOE consumer affected by this change, and
597 needs to be recompiled along with the kernel. As this change breaks
598 the ABI, bump __FreeBSD_version to 800103.
601 Padding has been added to struct tcpcb, sackhint and tcpstat in
602 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
603 maintaining the ABI. However, this change breaks the ABI, so bump
604 __FreeBSD_version to 800102. User space tools that rely on the size of
605 any of these structs (e.g. sockstat) need to be recompiled.
608 The NFS_LEGACYRPC option has been removed along with the old kernel
609 RPC implementation that this option selected. Kernel configurations
610 may need to be adjusted.
613 The network interface device nodes at /dev/net/<interface> have been
614 removed. All ioctl operations can be performed the normal way using
615 routing sockets. The kqueue functionality can generally be replaced
616 with routing sockets.
619 The documentation from the FreeBSD Documentation Project (Handbook,
620 FAQ, etc.) is now installed via packages by sysinstall(8) and under
621 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
624 The ABI of various structures related to the SYSV IPC API have been
625 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
626 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
630 Layout of struct vnet has changed as routing related variables were
631 moved to their own Vimage module. Modules need to be recompiled. Bump
632 __FreeBSD_version to 800099.
635 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
636 respectively. As long as no more than 16 groups per process are used,
637 no changes should be visible. When more than 16 groups are used, old
638 binaries may fail if they call getgroups() or getgrouplist() with
639 statically sized storage. Recompiling will work around this, but
640 applications should be modified to use dynamically allocated storage
641 for group arrays as POSIX.1-2008 does not cap an implementation's
642 number of supported groups at NGROUPS_MAX+1 as previous versions did.
644 NFS and portalfs mounts may also be affected as the list of groups is
645 truncated to 16. Users of NFS who use more than 16 groups, should
646 take care that negative group permissions are not used on the exported
647 file systems as they will not be reliable unless a GSSAPI based
648 authentication method is used.
651 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
652 option compiles in the support for adaptive spinning for lockmgrs
653 which want to enable it. The lockinit() function now accepts the flag
654 LK_ADAPTIVE in order to make the lock object subject to adaptive
655 spinning when both held in write and read mode.
658 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
659 changed. User applications that use this ioctl need to be rebuilt.
662 The layout of struct thread has changed. Kernel and modules need to
666 The layout of structs ifnet, domain, protosw and vnet_net has changed.
667 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
670 window(1) has been removed from the base system. It can now be
671 installed from ports. The port is called misc/window.
674 The way we are storing and accessing `routing table' entries has
675 changed. Programs reading the FIB, like netstat, need to be
679 A new netisr implementation has been added for FreeBSD 8. Network
680 file system modules, such as igmp, ipdivert, and others, should be
682 Bump __FreeBSD_version to 800096.
685 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
689 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
690 Bump __FreeBSD_version to 800094.
693 Add mnt_xflag field to 'struct mount'. File system modules need to be
695 Bump __FreeBSD_version to 800093.
698 The compiling option ADAPTIVE_SX has been retired while it has been
699 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
700 The KPI for sx_init_flags() changes as accepting flags:
701 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
702 been introduced in order to handle the reversed logic.
703 Bump __FreeBSD_version to 800092.
706 Add support for hierarchical jails. Remove global securelevel.
707 Bump __FreeBSD_version to 800091.
710 The layout of struct vnet_net has changed, therefore modules
712 Bump __FreeBSD_version to 800090.
715 The newly imported zic(8) produces a new format in the output. Please
716 run tzsetup(8) to install the newly created data to /etc/localtime.
719 The sysctl tree for the usb stack has renamed from hw.usb2.* to
720 hw.usb.* and is now consistent again with previous releases.
723 802.11 monitor mode support was revised and driver api's were changed.
724 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
725 of DLT_IEEE802_11. No user-visible data structures were changed but
726 applications that use DLT_IEEE802_11 may require changes.
727 Bump __FreeBSD_version to 800088.
730 The layout of the following structs has changed: sysctl_oid,
731 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
732 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
733 panics may be experienced. World rebuild is required for
734 correctly checking networking state from userland.
735 Bump __FreeBSD_version to 800085.
738 MLDv2 and Source-Specific Multicast (SSM) have been merged
739 to the IPv6 stack. VIMAGE hooks are in but not yet used.
740 The implementation of SSM within FreeBSD's IPv6 stack closely
741 follows the IPv4 implementation.
743 For kernel developers:
745 * The most important changes are that the ip6_output() and
746 ip6_input() paths no longer take the IN6_MULTI_LOCK,
747 and this lock has been downgraded to a non-recursive mutex.
749 * As with the changes to the IPv4 stack to support SSM, filtering
750 of inbound multicast traffic must now be performed by transport
751 protocols within the IPv6 stack. This does not apply to TCP and
752 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
754 * The KPIs used by IPv6 multicast are similar to those used by
755 the IPv4 stack, with the following differences:
756 * im6o_mc_filter() is analogous to imo_multicast_filter().
757 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
758 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
759 * IN6_LOOKUP_MULTI() has been deprecated and removed.
760 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
761 for MLDv1 have an additional 'timer' argument which is used to
762 jitter the initial membership report for the solicited-node
763 multicast membership on-link.
764 * This is not strictly needed for MLDv2, which already jitters
765 its report transmissions. However, the 'timer' argument is
766 preserved in case MLDv1 is active on the interface.
768 * The KAME linked-list based IPv6 membership implementation has
769 been refactored to use a vector similar to that used by the IPv4
771 Code which maintains a list of its own multicast memberships
772 internally, e.g. carp, has been updated to reflect the new
775 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
776 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
777 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
778 implementation constraint which needs to be addressed in HEAD.
780 For application developers:
782 * The changes are broadly similar to those made for the IPv4
785 * The use of IPv4 and IPv6 multicast socket options on the same
786 socket, using mapped addresses, HAS NOT been tested or supported.
788 * There are a number of issues with the implementation of various
789 IPv6 multicast APIs which need to be resolved in the API surface
790 before the implementation is fully compatible with KAME userland
791 use, and these are mostly to do with interface index treatment.
793 * The literature available discusses the use of either the delta / ASM
794 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
795 using setsourcefilter(3)/getsourcefilter(3). For more information
796 please refer to RFC 3768, 'Socket Interface Extensions for
797 Multicast Source Filters'.
799 * Applications which use the published RFC 3678 APIs should be fine.
801 For systems administrators:
803 * The mtest(8) utility has been refactored to support IPv6, in
804 addition to IPv4. Interface addresses are no longer accepted
805 as arguments, their names must be used instead. The utility
806 will map the interface name to its first IPv4 address as
807 returned by getifaddrs(3).
809 * The ifmcstat(8) utility has also been updated to print the MLDv2
810 endpoint state and source filter lists via sysctl(3).
812 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
813 loopback of IPv6 multicast datagrams by default; it defaults to 1
814 to preserve the existing behaviour. Disabling multicast loopback is
815 recommended for optimal system performance.
817 * The IPv6 MROUTING code has been changed to examine this sysctl
818 instead of attempting to perform a group lookup before looping
819 back forwarded datagrams.
821 Bump __FreeBSD_version to 800084.
824 Implement low-level Bluetooth HCI API.
825 Bump __FreeBSD_version to 800083.
828 The layout of struct malloc_type, used by modules to register new
829 memory allocation types, has changed. Most modules will need to
830 be rebuilt or panics may be experienced.
831 Bump __FreeBSD_version to 800081.
834 Anticipate overflowing inp_flags - add inp_flags2.
835 This changes most offsets in inpcb, so checking v4 connection
836 state will require a world rebuild.
837 Bump __FreeBSD_version to 800080.
840 Add an llentry to struct route and struct route_in6. Modules
841 embedding a struct route will need to be recompiled.
842 Bump __FreeBSD_version to 800079.
845 The size of rt_metrics_lite and by extension rtentry has changed.
846 Networking administration apps will need to be recompiled.
847 The route command now supports show as an alias for get, weighting
848 of routes, sticky and nostick flags to alter the behavior of stateful
850 Bump __FreeBSD_version to 800078.
853 Do not use Giant for kbdmux(4) locking. This is wrong and
854 apparently causing more problems than it solves. This will
855 re-open the issue where interrupt handlers may race with
856 kbdmux(4) in polling mode. Typical symptoms include (but
857 not limited to) duplicated and/or missing characters when
858 low level console functions (such as gets) are used while
859 interrupts are enabled (for example geli password prompt,
860 mountroot prompt etc.). Disabling kbdmux(4) may help.
863 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
864 kernel modules referencing any of the above need to be recompiled.
865 Bump __FreeBSD_version to 800075.
868 GEOM_PART has become the default partition slicer for storage devices,
869 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
870 introduces some changes:
872 MSDOS/EBR: the devices created from MSDOS extended partition entries
873 (EBR) can be named differently than with GEOM_MBR and are now symlinks
874 to devices with offset-based names. fstabs may need to be modified.
876 BSD: the "geometry does not match label" warning is harmless in most
877 cases but it points to problems in file system misalignment with
878 disk geometry. The "c" partition is now implicit, covers the whole
879 top-level drive and cannot be (mis)used by users.
881 General: Kernel dumps are now not allowed to be written to devices
882 whose partition types indicate they are meant to be used for file
883 systems (or, in case of MSDOS partitions, as something else than
886 Most of these changes date approximately from 200812.
889 The uscanner(4) driver has been removed from the kernel. This follows
890 Linux removing theirs in 2.6 and making libusb the default interface
894 The multicast forwarding code has been cleaned up. netstat(1)
895 only relies on KVM now for printing bandwidth upcall meters.
896 The IPv4 and IPv6 modules are split into ip_mroute_mod and
897 ip6_mroute_mod respectively. The config(5) options for statically
898 compiling this code remain the same, i.e. 'options MROUTING'.
901 Support for the IFF_NEEDSGIANT network interface flag has been
902 removed, which means that non-MPSAFE network device drivers are no
903 longer supported. In particular, if_ar, if_sr, and network device
904 drivers from the old (legacy) USB stack can no longer be built or
908 POSIX.1 Native Language Support (NLS) has been enabled in libc and
909 a bunch of new language catalog files have also been added.
910 This means that some common libc messages are now localized and
911 they depend on the LC_MESSAGES environmental variable.
914 The k8temp(4) driver has been renamed to amdtemp(4) since
915 support for Family 10 and Family 11 CPU families was added.
918 IGMPv3 and Source-Specific Multicast (SSM) have been merged
919 to the IPv4 stack. VIMAGE hooks are in but not yet used.
921 For kernel developers, the most important changes are that the
922 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
923 and this lock has been downgraded to a non-recursive mutex.
925 Transport protocols (UDP, Raw IP) are now responsible for filtering
926 inbound multicast traffic according to group membership and source
927 filters. The imo_multicast_filter() KPI exists for this purpose.
928 Transports which do not use multicast (SCTP, TCP) already reject
929 multicast by default. Forwarding and receive performance may improve
930 as a mutex acquisition is no longer needed in the ip_input()
931 low-level input path. in_addmulti() and in_delmulti() are shimmed
932 to new KPIs which exist to support SSM in-kernel.
934 For application developers, it is recommended that loopback of
935 multicast datagrams be disabled for best performance, as this
936 will still cause the lock to be taken for each looped-back
937 datagram transmission. The net.inet.ip.mcast.loop sysctl may
938 be tuned to 0 to disable loopback by default; it defaults to 1
939 to preserve the existing behaviour.
941 For systems administrators, to obtain best performance with
942 multicast reception and multiple groups, it is always recommended
943 that a card with a suitably precise hash filter is used. Hash
944 collisions will still result in the lock being taken within the
945 transport protocol input path to check group membership.
947 If deploying FreeBSD in an environment with IGMP snooping switches,
948 it is recommended that the net.inet.igmp.sendlocal sysctl remain
949 enabled; this forces 224.0.0.0/24 group membership to be announced
952 The size of 'struct igmpstat' has changed; netstat needs to be
953 recompiled to reflect this.
954 Bump __FreeBSD_version to 800070.
957 libusb20.so.1 is now installed as libusb.so.1 and the ports system
958 updated to use it. This requires a buildworld/installworld in order to
959 update the library and dependencies (usbconfig, etc). Its advisable to
960 rebuild all ports which uses libusb. More specific directions are given
961 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
962 libusb are no longer required and can be removed.
965 A workaround is committed to allow the creation of System V shared
966 memory segment of size > 2 GB on the 64-bit architectures.
967 Due to a limitation of the existing ABI, the shm_segsz member
968 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
969 wrong for large segments. Note that limits must be explicitly
970 raised to allow such segments to be created.
973 The layout of struct ifnet has changed, requiring a rebuild of all
974 network device driver modules.
977 The /dev handling for the new USB stack has changed, a
978 buildworld/installworld is required for libusb20.
981 The new USB2 stack has now been permanently moved in and all kernel and
982 module names reverted to their previous values (eg, usb, ehci, ohci,
983 ums, ...). The old usb stack can be compiled in by prefixing the name
984 with the letter 'o', the old usb modules have been removed.
985 Updating entry 20090216 for xorg and 20090215 for libmap may still
989 The rc.conf(5) option if_up_delay has been renamed to
990 defaultroute_delay to better reflect its purpose. If you have
991 customized this setting in /etc/rc.conf you need to update it to
995 xorg 7.4 wants to configure its input devices via hald which does not
996 yet work with USB2. If the keyboard/mouse does not work in xorg then
998 Option "AllowEmptyInput" "off"
999 to your ServerLayout section. This will cause X to use the configured
1000 kbd and mouse sections from your xorg.conf.
1003 The GENERIC kernels for all architectures now default to the new USB2
1004 stack. No kernel config options or code have been removed so if a
1005 problem arises please report it and optionally revert to the old USB
1006 stack. If you are loading USB kernel modules or have a custom kernel
1007 that includes GENERIC then ensure that usb names are also changed over,
1008 eg uftdi -> usb2_serial_ftdi.
1010 Older programs linked against the ports libusb 0.1 need to be
1011 redirected to the new stack's libusb20. /etc/libmap.conf can
1013 # Map old usb library to new one for usb2 stack
1014 libusb-0.1.so.8 libusb20.so.1
1017 All USB ethernet devices now attach as interfaces under the name ueN
1018 (eg. ue0). This is to provide a predictable name as vendors often
1019 change usb chipsets in a product without notice.
1022 The ichsmb(4) driver has been changed to require SMBus slave
1023 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1024 All of the other SMBus controller drivers require left-justified
1025 slave addresses, so this change makes all the drivers provide the
1029 INET6 statistics (struct ip6stat) was updated.
1030 netstat(1) needs to be recompiled.
1033 NTFS has been removed from GENERIC kernel on amd64 to match
1034 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1035 will load ntfs.ko module automatically when NTFS support is
1036 actually needed, unless ntfs.ko is not installed or security
1037 level prohibits loading kernel modules. If either is the case,
1038 "options NTFS" has to be added into kernel config.
1041 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1042 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1043 800061. User space tools that rely on the size of struct tcpcb in
1044 tcp_var.h (e.g. sockstat) need to be recompiled.
1047 ng_tty(4) module updated to match the new TTY subsystem.
1048 Due to API change, user-level applications must be updated.
1049 New API support added to mpd5 CVS and expected to be present
1050 in next mpd5.3 release.
1053 With __FreeBSD_version 800060 the makefs tool is part of
1054 the base system (it was a port).
1057 The afdata and ifnet locks have been changed from mutexes to
1058 rwlocks, network modules will need to be re-compiled.
1061 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1062 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1063 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1064 architecture and 40 bytes on 64-bit architecture. The userland
1065 applications "arp" and "ndp" have been updated accordingly.
1066 The output from "netstat -r" shows only routing entries and
1067 none of the L2 information.
1070 __FreeBSD_version 800057 marks the switchover from the
1071 binary ath hal to source code. Users must add the line:
1073 options AH_SUPPORT_AR5416
1075 to their kernel config files when specifying:
1079 The ath_hal module no longer exists; the code is now compiled
1080 together with the driver in the ath module. It is now
1081 possible to tailor chip support (i.e. reduce the set of chips
1082 and thereby the code size); consult ath_hal(4) for details.
1085 __FreeBSD_version 800054 adds memory barriers to
1086 <machine/atomic.h>, new interfaces to ifnet to facilitate
1087 multiple hardware transmit queues for cards that support
1088 them, and a lock-less ring-buffer implementation to
1089 enable drivers to more efficiently manage queueing of
1093 A new version of ZFS (version 13) has been merged to -HEAD.
1094 This version has zpool attribute "listsnapshots" off by
1095 default, which means "zfs list" does not show snapshots,
1096 and is the same as Solaris behavior.
1099 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1102 The uhci, ohci, ehci and slhci USB Host controller drivers have
1103 been put into separate modules. If you load the usb module
1104 separately through loader.conf you will need to load the
1105 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1106 controller add the following to loader.conf:
1112 The ABI used by the PMC toolset has changed. Please keep
1113 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1117 atapci kernel module now includes only generic PCI ATA
1118 driver. AHCI driver moved to ataahci kernel module.
1119 All vendor-specific code moved into separate kernel modules:
1120 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1121 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1122 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1123 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1126 The TTY subsystem of the kernel has been replaced by a new
1127 implementation, which provides better scalability and an
1128 improved driver model. Most common drivers have been migrated to
1129 the new TTY subsystem, while others have not. The following
1130 drivers have not yet been ported to the new TTY layer:
1133 cy, digi, rc, rp, sio
1139 ng_h4, ng_tty, ppp, sl, snp
1141 Adding these drivers to your kernel configuration file shall
1142 cause compilation to fail.
1145 ntpd has been upgraded to 4.2.4p5.
1148 OpenSSH has been upgraded to 5.1p1.
1150 For many years, FreeBSD's version of OpenSSH preferred DSA
1151 over RSA for host and user authentication keys. With this
1152 upgrade, we've switched to the vendor's default of RSA over
1153 DSA. This may cause upgraded clients to warn about unknown
1154 host keys even for previously known hosts. Users should
1155 follow the usual procedure for verifying host keys before
1156 accepting the RSA key.
1158 This can be circumvented by setting the "HostKeyAlgorithms"
1159 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1162 Please note that the sequence of keys offered for
1163 authentication has been changed as well. You may want to
1164 specify IdentityFile in a different order to revert this
1168 The sio(4) driver has been removed from the i386 and amd64
1169 kernel configuration files. This means uart(4) is now the
1170 default serial port driver on those platforms as well.
1172 To prevent collisions with the sio(4) driver, the uart(4) driver
1173 uses different names for its device nodes. This means the
1174 onboard serial port will now most likely be called "ttyu0"
1175 instead of "ttyd0". You may need to reconfigure applications to
1176 use the new device names.
1178 When using the serial port as a boot console, be sure to update
1179 /boot/device.hints and /etc/ttys before booting the new kernel.
1180 If you forget to do so, you can still manually specify the hints
1181 at the loader prompt:
1183 set hint.uart.0.at="isa"
1184 set hint.uart.0.port="0x3F8"
1185 set hint.uart.0.flags="0x10"
1186 set hint.uart.0.irq="4"
1190 The gpt(8) utility has been removed. Use gpart(8) to partition
1194 The version that Linuxulator emulates was changed from 2.4.2
1195 to 2.6.16. If you experience any problems with Linux binaries
1196 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1197 if it fixes the problem contact emulation mailing list.
1200 ISDN4BSD (I4B) was removed from the src tree. You may need to
1201 update a your kernel configuration and remove relevant entries.
1204 I have checked in code to support multiple routing tables.
1205 See the man pages setfib(1) and setfib(2).
1206 This is a hopefully backwards compatible version,
1207 but to make use of it you need to compile your kernel
1208 with options ROUTETABLES=2 (or more up to 16).
1211 The 802.11 wireless support was redone to enable multi-bss
1212 operation on devices that are capable. The underlying device
1213 is no longer used directly but instead wlanX devices are
1214 cloned with ifconfig. This requires changes to rc.conf files.
1215 For example, change:
1216 ifconfig_ath0="WPA DHCP"
1219 ifconfig_wlan0="WPA DHCP"
1220 see rc.conf(5) for more details. In addition, mergemaster of
1221 /etc/rc.d is highly recommended. Simultaneous update of userland
1222 and kernel wouldn't hurt either.
1224 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1225 modules were merged into the base wlan module. All references
1226 to these modules (e.g. in kernel config files) must be removed.
1229 psm(4) has gained write(2) support in native operation level.
1230 Arbitrary commands can be written to /dev/psm%d and status can
1231 be read back from it. Therefore, an application is responsible
1232 for status validation and error recovery. It is a no-op in
1233 other operation levels.
1236 Support for KSE threading has been removed from the kernel. To
1237 run legacy applications linked against KSE libmap.conf may
1238 be used. The following libmap.conf may be used to ensure
1239 compatibility with any prior release:
1241 libpthread.so.1 libthr.so.1
1242 libpthread.so.2 libthr.so.2
1243 libkse.so.3 libthr.so.3
1246 The layout of struct vmspace has changed. This affects libkvm
1247 and any executables that link against libkvm and use the
1248 kvm_getprocs() function. In particular, but not exclusively,
1249 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1250 The effects are minimal, but it's advisable to upgrade world
1254 The latest em driver no longer has support in it for the
1255 82575 adapter, this is now moved to the igb driver. The
1256 split was done to make new features that are incompatible
1257 with older hardware easier to do.
1260 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1261 likewise the kernel option is now GEOM_LINUX_LVM.
1264 The default NFS mount mode has changed from UDP to TCP for
1265 increased reliability. If you rely on (insecurely) NFS
1266 mounting across a firewall you may need to update your
1270 Belatedly note the addition of m_collapse for compacting
1274 The fts(3) structures have been changed to use adequate
1275 integer types for their members and so to be able to cope
1276 with huge file trees. The old fts(3) ABI is preserved
1277 through symbol versioning in libc, so third-party binaries
1278 using fts(3) should still work, although they will not take
1279 advantage of the extended types. At the same time, some
1280 third-party software might fail to build after this change
1281 due to unportable assumptions made in its source code about
1282 fts(3) structure members. Such software should be fixed
1283 by its vendor or, in the worst case, in the ports tree.
1284 FreeBSD_version 800015 marks this change for the unlikely
1285 case that a portable fix is impossible.
1288 To upgrade to -current after this date, you must be running
1289 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1290 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1293 The ADAPTIVE_GIANT kernel option has been retired because its
1294 functionality is the default now.
1297 The AT keyboard emulation of sunkbd(4) has been turned on
1298 by default. In order to make the special symbols of the Sun
1299 keyboards driven by sunkbd(4) work under X these now have
1300 to be configured the same way as Sun USB keyboards driven
1301 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1303 Option "XkbLayout" "us"
1304 Option "XkbRules" "xorg"
1305 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1308 It has been decided that it is desirable to provide ABI
1309 backwards compatibility to the FreeBSD 4/5/6 versions of the
1310 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1311 broken with the introduction of PCI domain support (see the
1312 20070930 entry). Unfortunately, this required the ABI of
1313 PCIOCGETCONF to be broken again in order to be able to
1314 provide backwards compatibility to the old version of that
1315 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1316 again. As for prominent ports this affects neither pciutils
1317 nor xorg-server this time, the hal port needs to be rebuilt
1321 The misnamed kthread_create() and friends have been renamed
1322 to kproc_create() etc. Many of the callers already
1323 used kproc_start()..
1324 I will return kthread_create() and friends in a while
1325 with implementations that actually create threads, not procs.
1326 Renaming corresponds with version 800002.
1335 Avoid using make -j when upgrading. While generally safe, there are
1336 sometimes problems using -j to upgrade. If your upgrade fails with
1337 -j, please try again without -j. From time to time in the past there
1338 have been problems using -j with buildworld and/or installworld. This
1339 is especially true when upgrading between "distant" versions (eg one
1340 that cross a major release boundary or several minor releases, or when
1341 several months have passed on the -current branch).
1343 Sometimes, obscure build problems are the result of environment
1344 poisoning. This can happen because the make utility reads its
1345 environment when searching for values for global variables. To run
1346 your build attempts in an "environmental clean room", prefix all make
1347 commands with 'env -i '. See the env(1) manual page for more details.
1349 When upgrading from one major version to another it is generally best
1350 to upgrade to the latest code in the currently installed branch first,
1351 then do an upgrade to the new branch. This is the best-tested upgrade
1352 path, and has the highest probability of being successful. Please try
1353 this approach before reporting problems with a major version upgrade.
1357 When upgrading the boot ZFS pool to a new version, always follow
1360 1.) recompile and reinstall the ZFS boot loader and boot block
1361 (this is part of "make buildworld" and "make installworld")
1363 2.) update the ZFS boot block on your boot drive
1365 The following example updates the ZFS boot block on the first
1366 partition (freebsd-boot) of a GPT partitioned drive ad0:
1367 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1369 Non-boot pools do not need these updates.
1373 If you are updating from a prior version of FreeBSD (even one just
1374 a few days old), you should follow this procedure. It is the most
1375 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1377 make kernel-toolchain
1378 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1379 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1381 To test a kernel once
1382 ---------------------
1383 If you just want to boot a kernel once (because you are not sure
1384 if it works, or if you want to boot a known bad kernel to provide
1385 debugging information) run
1386 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1387 nextboot -k testkernel
1389 To just build a kernel when you know that it won't mess you up
1390 --------------------------------------------------------------
1391 This assumes you are already running a CURRENT system. Replace
1392 ${arch} with the architecture of your machine (e.g. "i386",
1393 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1395 cd src/sys/${arch}/conf
1396 config KERNEL_NAME_HERE
1397 cd ../compile/KERNEL_NAME_HERE
1402 If this fails, go to the "To build a kernel" section.
1404 To rebuild everything and install it on the current system.
1405 -----------------------------------------------------------
1406 # Note: sometimes if you are running current you gotta do more than
1407 # is listed here if you are upgrading from a really old current.
1409 <make sure you have good level 0 dumps>
1411 make kernel KERNCONF=YOUR_KERNEL_HERE
1413 <reboot in single user> [3]
1421 To cross-install current onto a separate partition
1422 --------------------------------------------------
1423 # In this approach we use a separate partition to hold
1424 # current's root, 'usr', and 'var' directories. A partition
1425 # holding "/", "/usr" and "/var" should be about 2GB in
1428 <make sure you have good level 0 dumps>
1431 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1432 <maybe newfs current's root partition>
1433 <mount current's root partition on directory ${CURRENT_ROOT}>
1434 make installworld DESTDIR=${CURRENT_ROOT}
1435 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1436 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1437 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1438 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1439 <reboot into current>
1440 <do a "native" rebuild/install as described in the previous section>
1441 <maybe install compatibility libraries from ports/misc/compat*>
1445 To upgrade in-place from 8.x-stable to current
1446 ----------------------------------------------
1447 <make sure you have good level 0 dumps>
1449 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1451 <reboot in single user> [3]
1458 Make sure that you've read the UPDATING file to understand the
1459 tweaks to various things you need. At this point in the life
1460 cycle of current, things change often and you are on your own
1461 to cope. The defaults can also change, so please read ALL of
1462 the UPDATING entries.
1464 Also, if you are tracking -current, you must be subscribed to
1465 freebsd-current@freebsd.org. Make sure that before you update
1466 your sources that you have read and understood all the recent
1467 messages there. If in doubt, please track -stable which has
1468 much fewer pitfalls.
1470 [1] If you have third party modules, such as vmware, you
1471 should disable them at this point so they don't crash your
1474 [3] From the bootblocks, boot -s, and then do
1479 adjkerntz -i # if CMOS is wall time
1480 Also, when doing a major release upgrade, it is required that
1481 you boot into single user mode to do the installworld.
1483 [4] Note: This step is non-optional. Failure to do this step
1484 can result in a significant reduction in the functionality of the
1485 system. Attempting to do it by hand is not recommended and those
1486 that pursue this avenue should read this file carefully, as well
1487 as the archives of freebsd-current and freebsd-hackers mailing lists
1488 for potential gotchas. The -U option is also useful to consider.
1489 See mergemaster(8) for more information.
1491 [5] Usually this step is a noop. However, from time to time
1492 you may need to do this if you get unknown user in the following
1493 step. It never hurts to do it all the time. You may need to
1494 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1495 install) after the buildworld before this step if you last updated
1496 from current before 20020224 or from -stable before 20020408.
1498 [6] This only deletes old files and directories. Old libraries
1499 can be deleted by "make delete-old-libs", but you have to make
1500 sure that no program is using those libraries anymore.
1502 [8] In order to have a kernel that can run the 4.x binaries needed to
1503 do an installworld, you must include the COMPAT_FREEBSD4 option in
1504 your kernel. Failure to do so may leave you with a system that is
1505 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1506 required to run the 5.x binaries on more recent kernels. And so on
1507 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1509 Make sure that you merge any new devices from GENERIC since the
1510 last time you updated your kernel config file.
1512 [9] When checking out sources, you must include the -P flag to have
1513 cvs prune empty directories.
1515 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1516 "?=" instead of the "=" assignment operator, so that buildworld can
1517 override the CPUTYPE if it needs to.
1519 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1520 not on the command line, or in /etc/make.conf. buildworld will
1521 warn if it is improperly defined.
1524 This file contains a list, in reverse chronological order, of major
1525 breakages in tracking -current. It is not guaranteed to be a complete
1526 list of such breakages, and only contains entries since October 10, 2007.
1527 If you need to see UPDATING entries from before that date, you will need
1528 to fetch an UPDATING file from an older FreeBSD release.
1530 Copyright information:
1532 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1534 Redistribution, publication, translation and use, with or without
1535 modification, in full or in part, in any form or format of this
1536 document are permitted without further permission from the author.
1538 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1539 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1540 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1541 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1542 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1543 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1544 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1545 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1546 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1547 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1548 POSSIBILITY OF SUCH DAMAGE.
1550 Contact Warner Losh if you have any questions about your use of