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 broken amd(4) driver has been replaced with esp(4) in the amd64,
27 i386 and pc98 GENERIC kernel configuration files.
30 sysinstall has been removed
33 The stable/9 branch created in subversion. This corresponds to the
34 RELENG_9 branch in CVS.
37 This commit modifies vfs_register() so that it uses a hash
38 calculation to set vfc_typenum, which is enabled by default.
39 The first time a system is booted after this change, the
40 vfc_typenum values will change for all file systems. The
41 main effect of this is a change to the NFS server file handles
42 for file systems that use vfc_typenum in their fsid, such as ZFS.
43 It will, however, prevent vfc_typenum from changing when file
44 systems are loaded in a different order for subsequent reboots.
45 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
46 until you are ready to remount all NFS clients after a reboot.
49 Bump the shared library version numbers for libraries that
50 do not use symbol versioning, have changed the ABI compared
51 to stable/8 and which shared library version was not bumped.
52 Done as part of 9.0-RELEASE cycle.
55 During the merge of Capsicum features, the fget(9) KPI was modified.
56 This may require the rebuilding of out-of-tree device drivers --
57 issues have been reported specifically with the nVidia device driver.
58 __FreeBSD_version is bumped to 900041.
60 Also, there is a period between 20110811 and 20110814 where the
61 special devices /dev/{stdin,stdout,stderr} did not work correctly.
62 Building world from a kernel during that window may not work.
65 The packet filter (pf) code has been updated to OpenBSD 4.5.
66 You need to update userland tools to be in sync with kernel.
67 This update breaks backward compatibility with earlier pfsync(4)
68 versions. Care must be taken when updating redundant firewall setups.
71 The following sysctls and tunables are retired on x86 platforms:
73 machdep.hlt_logical_cpus
74 The following sysctl is retired:
75 machdep.hyperthreading_allowed
76 The sysctls were supposed to provide a way to dynamically offline and
77 online selected CPUs on x86 platforms, but the implementation has not
78 been reliable especially with SCHED_ULE scheduler.
79 machdep.hyperthreading_allowed tunable is still available to ignore
80 hyperthreading CPUs at OS level.
81 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
82 where X is an APIC ID of a CPU. Be advised, though, that disabling
83 CPUs in non-uniform fashion will result in non-uniform topology and
84 may lead to sub-optimal system performance with SCHED_ULE, which is
88 cpumask_t type is retired and cpuset_t is used in order to describe
92 Changes to ifconfig(8) for dynamic address family detection mandate
93 that you are running a kernel of 20110525 or later. Make sure to
94 follow the update procedure to boot a new kernel before installing
98 Support for sun4v architecture is officially dropped
101 Several KPI breaking changes have been committed to the mii(4) layer,
102 the PHY drivers and consequently some Ethernet drivers using mii(4).
103 This means that miibus.ko and the modules of the affected Ethernet
104 drivers need to be recompiled.
106 Note to kernel developers: Given that the OUI bit reversion problem
107 was fixed as part of these changes all mii(4) commits related to OUIs,
108 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
109 handling, no longer can be merged verbatim to stable/8 and previous
113 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
114 into their kernel configurations along with 'device pci'.
117 The default NFS client is now the new NFS client, so fstype "newnfs"
118 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
119 Although mounts via fstype "nfs" will usually work without userland
120 changes, it is recommended that the mount(8) and mount_nfs(8)
121 commands be rebuilt from sources and that a link to mount_nfs called
122 mount_oldnfs be created. The new client is compiled into the
123 kernel with "options NFSCL" and this is needed for diskless root
124 file systems. The GENERIC kernel configs have been changed to use
125 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
126 To use the regular/old client, you can "mount -t oldnfs ...". For
127 a diskless root file system, you must also include a line like:
129 vfs.root.mountfrom="oldnfs:"
131 in the boot/loader.conf on the root fs on the NFS server to make
132 a diskless root fs use the old client.
135 The GENERIC kernels for all architectures now default to the new
136 CAM-based ATA stack. It means that all legacy ATA drivers were
137 removed and replaced by respective CAM drivers. If you are using
138 ATA device names in /etc/fstab or other places, make sure to update
139 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
140 where 'Y's are the sequential numbers starting from zero for each type
141 in order of detection, unless configured otherwise with tunables,
142 see cam(4)). There will be symbolic links created in /dev/ to map
143 old adX devices to the respective adaY. They should provide basic
144 compatibility for file systems mounting in most cases, but they do
145 not support old user-level APIs and do not have respective providers
146 in GEOM. Consider using updated management tools with new device names.
148 It is possible to load devices ahci, ata, siis and mvs as modules,
149 but option ATA_CAM should remain in kernel configuration to make ata
150 module work as CAM driver supporting legacy ATA controllers. Device ata
151 still can be used in modular fashion (atacore + ...). Modules atadisk
152 and atapi* are not used and won't affect operation in ATA_CAM mode.
153 Note that to use CAM-based ATA kernel should include CAM devices
154 scbus, pass, da (or explicitly ada), cd and optionally others. All of
155 them are parts of the cam module.
157 ataraid(4) functionality is now supported by the RAID GEOM class.
158 To use it you can load geom_raid kernel module and use graid(8) tool
159 for management. Instead of /dev/arX device names, use /dev/raid/rX.
161 No kernel config options or code have been removed, so if a problem
162 arises, please report it and optionally revert to the old ATA stack.
163 In order to do it you can remove from the kernel config:
168 , and instead add back:
169 device atadisk # ATA disk drives
170 device ataraid # ATA RAID drives
171 device atapicd # ATAPI CDROM drives
172 device atapifd # ATAPI floppy drives
173 device atapist # ATAPI tape drives
176 The default NFS server has been changed to the new server, which
177 was referred to as the experimental server. If you need to switch
178 back to the old NFS server, you must now put the "-o" option on
179 both the mountd and nfsd commands. This can be done using the
180 mountd_flags and nfs_server_flags rc.conf variables until an
181 update to the rc scripts is committed, which is coming soon.
184 The GNU Objective-C runtime library (libobjc), and other Objective-C
185 related components have been removed from the base system. If you
186 require an Objective-C library, please use one of the available ports.
189 ath(4) has been split into bus- and device- modules. if_ath contains
190 the HAL, the TX rate control and the network device code. if_ath_pci
191 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
192 contains the AHB glue. Users need to load both if_ath_pci and if_ath
193 in order to use ath on everything else.
195 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
196 need to load if_ath and if_ath_pci for ath(4) operation.
199 As part of the replacement of sysinstall, the process of building
200 release media has changed significantly. For details, please re-read
201 release(7), which has been updated to reflect the new build process.
204 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
205 is the last available version under GPLv2. It brings a number of new
206 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
207 4.1 and SSE 4.2), better support for powerpc64, a number of new
208 directives, and lots of other small improvements. See the ChangeLog
209 file in contrib/binutils for the full details.
212 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
213 compliant, and will now use half of hash for authentication.
214 This will break interoperability with all stacks (including all
215 actual FreeBSD versions) who implement
216 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
218 The only workaround with such peers is to use another HMAC
219 algorithm for IPsec ("phase 2") authentication.
222 Remove the uio_yield prototype and symbol. This function has
223 been misnamed since it was introduced and should not be
224 globally exposed with this name. The equivalent functionality
225 is now available using kern_yield(curthread->td_user_pri).
226 The function remains undocumented.
229 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
230 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
231 for scalar sysctls is defined but disabled. Code that needs
232 UQUAD to pass the type checking that must compile on older
233 systems where the define is not present can check against
234 __FreeBSD_version >= 900030.
236 The system dialog(1) has been replaced with a new version previously
237 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
238 with the previous version, but the libdialog associated with it has
239 a largely incompatible API. As such, the original version of libdialog
240 will be kept temporarily as libodialog, until its base system consumers
241 are replaced or updated. Bump __FreeBSD_version to 900030.
244 If you are trying to run make universe on a -stable system, and you get
245 the following warning:
246 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
247 unknown. config(8) likely too old."
248 or something similar to it, then you must upgrade your -stable system
249 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
250 stable/8) or build the config from the latest stable/8 branch and
251 install it on your system.
253 Prior to this date, building a current universe on 8-stable system from
254 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
255 error in the first kernel build phase. A new config on those old
256 systems will fix that problem for older versions of -current.
259 The TCP stack has been modified to allow Khelp modules to interact with
260 it via helper hook points and store per-connection data in the TCP
261 control block. Bump __FreeBSD_version to 900029. User space tools that
262 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
266 Generic IEEE 802.3 annex 31B full duplex flow control support has been
267 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
268 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
269 to take advantage of it instead of using custom implementations. This
270 means that these drivers now no longer unconditionally advertise
271 support for flow control but only do so if flow control is a selected
272 media option. This was implemented in the generic support that way in
273 order to allow flow control to be switched on and off via ifconfig(8)
274 with the PHY specific default to typically off in order to protect
275 from unwanted effects. Consequently, if you used flow control with
276 one of the above mentioned drivers you now need to explicitly enable
278 ifconfig bge0 media auto mediaopt flowcontrol
280 Along with the above mentioned changes generic support for setting
281 1000baseT master mode also has been added and brgphy(4), ciphy(4),
282 e1000phy(4) as well as ip1000phy(4) have been converted to take
283 advantage of it. This means that these drivers now no longer take the
284 link0 parameter for selecting master mode but the master media option
285 has to be used instead, for example like in the following:
286 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
288 Selection of master mode now is also available with all other PHY
289 drivers supporting 1000baseT.
292 The TCP stack has received a significant update to add support for
293 modularised congestion control and generally improve the clarity of
294 congestion control decisions. Bump __FreeBSD_version to 900025. User
295 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
296 sockstat) need to be recompiled.
299 The man(1) utility has been replaced by a new version that no longer
300 uses /etc/manpath.config. Please consult man.conf(5) for how to
301 migrate local entries to the new format.
304 The copyright strings printed by login(1) and sshd(8) at the time of a
305 new connection have been removed to follow other operating systems and
309 A workaround for a fixed ld bug has been removed in kernel code,
310 so make sure that your system ld is built from sources after
311 revision 210245 from 2010-07-19 (r211583 if building head kernel
312 on stable/8, r211584 for stable/7; both from 2010-08-21).
313 A symptom of incorrect ld version is different addresses for
314 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
317 The $ipv6_prefer variable in rc.conf(5) has been split into
318 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
320 The $ip6addrctl_policy is a variable to choose a pre-defined
321 address selection policy set by ip6addrctl(8). A value
322 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
325 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
326 flag (see an entry of 20090926) is set on an interface with no
327 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
328 security reason. If you want IPv6 link-local address on all
329 interfaces by default, set this to "YES".
331 The old ipv6_prefer="YES" is equivalent to
332 ipv6_activate_all_interfaces="YES" and
333 ip6addrctl_policy="ipv6_prefer".
336 DTrace has grown support for userland tracing. Due to this, DTrace is
337 now i386 and amd64 only.
338 dtruss(1) is now installed by default on those systems and a new
339 kernel module is needed for userland tracing: fasttrap.
340 No changes to your kernel config file are necessary to enable
341 userland tracing, but you might consider adding 'STRIP=' and
342 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
343 to have informative userland stack traces in DTrace (ustack).
346 The acpi_aiboost(4) driver has been removed in favor of the new
347 aibs(4) driver. You should update your kernel configuration file.
350 BSD grep has been imported to the base system and it is built by
351 default. It is completely BSD licensed, highly GNU-compatible, uses
352 less memory than its GNU counterpart and has a small codebase.
353 However, it is slower than its GNU counterpart, which is mostly
354 noticeable for larger searches, for smaller ones it is measurable
355 but not significant. The reason is complex, the most important factor
356 is that we lack a modern and efficient regex library and GNU
357 overcomes this by optimizing the searches internally. Future work
358 on improving the regex performance is planned, for the meantime,
359 users that need better performance, can build GNU grep instead by
360 setting the WITH_GNU_GREP knob.
363 Due to the import of powerpc64 support, all existing powerpc kernel
364 configuration files must be updated with a machine directive like this:
365 machine powerpc powerpc
367 In addition, an updated config(8) is required to build powerpc kernels
371 A new version of ZFS (version 15) has been merged to -HEAD.
372 This version uses a python library for the following subcommands:
373 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
374 For full functionality of these commands the following port must
375 be installed: sysutils/py-zfs
378 'vm_page's are now hashed by physical address to an array of mutexes.
379 Currently this is only used to serialize access to hold_count. Over
380 time the page queue mutex will be peeled away. This changes the size
381 of pmap on every architecture. And requires all callers of vm_page_hold
382 and vm_page_unhold to be updated.
385 WITH_CTF can now be specified in src.conf (not recommended, there
386 are some problems with static executables), make.conf (would also
387 affect ports which do not use GNU make and do not override the
388 compile targets) or in the kernel config (via "makeoptions
390 When WITH_CTF was specified there before this was silently ignored,
391 so make sure that WITH_CTF is not used in places which could lead
392 to unwanted behavior.
395 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
396 to allow 32-bit compatibility on non-x86 platforms. All kernel
397 configurations on amd64 and ia64 platforms using these options must
398 be modified accordingly.
401 The utmp user accounting database has been replaced with utmpx,
402 the user accounting interface standardized by POSIX.
403 Unfortunately the semantics of utmp and utmpx don't match,
404 making it practically impossible to support both interfaces.
405 The user accounting database is used by tools like finger(1),
406 last(1), talk(1), w(1) and ac(8).
408 All applications in the base system use utmpx. This means only
409 local binaries (e.g. from the ports tree) may still use these
410 utmp database files. These applications must be rebuilt to make
413 After the system has been upgraded, it is safe to remove the old
414 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
415 assuming their contents is of no importance anymore. Old wtmp
416 databases can only be used by last(1) and ac(8) after they have
417 been converted to the new format using wtmpcvt(1).
420 Introduce the kernel thread "deadlock resolver" (which can be enabled
421 via the DEADLKRES option, see NOTES for more details) and the
422 sleepq_type() function for sleepqueues.
425 The rc.firewall and rc.firewall6 were unified, and
426 rc.firewall6 and rc.d/ip6fw were removed.
427 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
428 variables are obsoleted. Instead, the following new rc
429 variables are added to rc.d/ipfw:
431 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
432 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
433 firewall_simple_onet_ipv6, firewall_trusted_ipv6
435 The meanings correspond to the relevant IPv4 variables.
441 The default terminal emulation for syscons(4) has been changed
442 from cons25 to xterm on all platforms except pc98. This means
443 that the /etc/ttys file needs to be updated to ensure correct
444 operation of applications on the console.
446 The terminal emulation style can be toggled per window by using
447 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
448 options can be used to change the compile-time default back to
451 To prevent graphical artifacts, make sure the TERM environment
452 variable is set to match the terminal emulation that is being
453 performed by syscons(4).
456 The layout of the structure ieee80211req_scan_result has changed.
457 Applications that require wireless scan results (e.g. ifconfig(8))
458 from net80211 need to be recompiled.
460 Applications such as wpa_supplicant(8) may require a full world
461 build without using NO_CLEAN in order to get synchronized with the
465 The iwn(4) driver has been updated to support the 5000 and 5150 series.
466 There's one kernel module for each firmware. Adding "device iwnfw"
467 to the kernel configuration file means including all three firmware
468 images inside the kernel. If you want to include just the one for
469 your wireless card, use the devices iwn4965fw, iwn5000fw or
473 The rc.d/network_ipv6, IPv6 configuration script has been integrated
474 into rc.d/netif. The changes are the following:
476 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
477 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
478 Note that both variables need the "inet6" keyword at the head.
480 Do not set $ipv6_network_interfaces manually if you do not
481 understand what you are doing. It is not needed in most cases.
483 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
486 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
487 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
489 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
490 all configured interfaces have "inet6 accept_rtadv" in the
491 $ifconfig_IF_ipv6. These are for backward compatibility.
493 3. A new variable $ipv6_prefer has been added. If NO, IPv6
494 functionality of interfaces with no corresponding
495 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
496 and the default address selection policy of ip6addrctl(8)
497 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
498 Note that if you want to configure IPv6 functionality on the
499 disabled interfaces after boot, first you need to clear the flag by
500 using ifconfig(8) like:
502 ifconfig em0 inet6 -ifdisabled
504 If YES, the default address selection policy is set as
507 The default value of $ipv6_prefer is NO.
509 4. If your system need to receive Router Advertisement messages,
510 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
511 scripts automatically invoke rtsol(8) when the interface becomes
512 UP. The Router Advertisement messages are used for SLAAC
513 (State-Less Address AutoConfiguration).
516 802.11s D3.03 support was committed. This is incompatible with the
517 previous code, which was based on D3.0.
520 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
521 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
522 control whether accepting Router Advertisement messages or not.
523 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
524 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
525 The ifconfig(8) utility now supports these flags.
528 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
529 mount(8) and -a option for df(1) to see them.
532 The old tunable hw.bus.devctl_disable has been superseded by
533 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
534 replaced by hw.bus.devctl_queue=0. The default for this new tunable
538 Remove the option STOP_NMI. The default action is now to use NMI only
539 for KDB via the newly introduced function stop_cpus_hard() and
540 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
543 The stable/8 branch created in subversion. This corresponds to the
544 RELENG_8 branch in CVS.
547 Bump the shared library version numbers for all libraries that do not
548 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
549 __FreeBSD_version to 800105.
552 Due to changes in the implementation of virtual network stack support,
553 all network-related kernel modules must be recompiled. As this change
554 breaks the ABI, bump __FreeBSD_version to 800104.
557 The TOE interface to the TCP syncache has been modified to remove
558 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
559 The cxgb driver is the only TOE consumer affected by this change, and
560 needs to be recompiled along with the kernel. As this change breaks
561 the ABI, bump __FreeBSD_version to 800103.
564 Padding has been added to struct tcpcb, sackhint and tcpstat in
565 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
566 maintaining the ABI. However, this change breaks the ABI, so bump
567 __FreeBSD_version to 800102. User space tools that rely on the size of
568 any of these structs (e.g. sockstat) need to be recompiled.
571 The NFS_LEGACYRPC option has been removed along with the old kernel
572 RPC implementation that this option selected. Kernel configurations
573 may need to be adjusted.
576 The network interface device nodes at /dev/net/<interface> have been
577 removed. All ioctl operations can be performed the normal way using
578 routing sockets. The kqueue functionality can generally be replaced
579 with routing sockets.
582 The documentation from the FreeBSD Documentation Project (Handbook,
583 FAQ, etc.) is now installed via packages by sysinstall(8) and under
584 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
587 The ABI of various structures related to the SYSV IPC API have been
588 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
589 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
593 Layout of struct vnet has changed as routing related variables were
594 moved to their own Vimage module. Modules need to be recompiled. Bump
595 __FreeBSD_version to 800099.
598 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
599 respectively. As long as no more than 16 groups per process are used,
600 no changes should be visible. When more than 16 groups are used, old
601 binaries may fail if they call getgroups() or getgrouplist() with
602 statically sized storage. Recompiling will work around this, but
603 applications should be modified to use dynamically allocated storage
604 for group arrays as POSIX.1-2008 does not cap an implementation's
605 number of supported groups at NGROUPS_MAX+1 as previous versions did.
607 NFS and portalfs mounts may also be affected as the list of groups is
608 truncated to 16. Users of NFS who use more than 16 groups, should
609 take care that negative group permissions are not used on the exported
610 file systems as they will not be reliable unless a GSSAPI based
611 authentication method is used.
614 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
615 option compiles in the support for adaptive spinning for lockmgrs
616 which want to enable it. The lockinit() function now accepts the flag
617 LK_ADAPTIVE in order to make the lock object subject to adaptive
618 spinning when both held in write and read mode.
621 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
622 changed. User applications that use this ioctl need to be rebuilt.
625 The layout of struct thread has changed. Kernel and modules need to
629 The layout of structs ifnet, domain, protosw and vnet_net has changed.
630 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
633 window(1) has been removed from the base system. It can now be
634 installed from ports. The port is called misc/window.
637 The way we are storing and accessing `routing table' entries has
638 changed. Programs reading the FIB, like netstat, need to be
642 A new netisr implementation has been added for FreeBSD 8. Network
643 file system modules, such as igmp, ipdivert, and others, should be
645 Bump __FreeBSD_version to 800096.
648 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
652 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
653 Bump __FreeBSD_version to 800094.
656 Add mnt_xflag field to 'struct mount'. File system modules need to be
658 Bump __FreeBSD_version to 800093.
661 The compiling option ADAPTIVE_SX has been retired while it has been
662 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
663 The KPI for sx_init_flags() changes as accepting flags:
664 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
665 been introduced in order to handle the reversed logic.
666 Bump __FreeBSD_version to 800092.
669 Add support for hierarchical jails. Remove global securelevel.
670 Bump __FreeBSD_version to 800091.
673 The layout of struct vnet_net has changed, therefore modules
675 Bump __FreeBSD_version to 800090.
678 The newly imported zic(8) produces a new format in the output. Please
679 run tzsetup(8) to install the newly created data to /etc/localtime.
682 The sysctl tree for the usb stack has renamed from hw.usb2.* to
683 hw.usb.* and is now consistent again with previous releases.
686 802.11 monitor mode support was revised and driver api's were changed.
687 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
688 of DLT_IEEE802_11. No user-visible data structures were changed but
689 applications that use DLT_IEEE802_11 may require changes.
690 Bump __FreeBSD_version to 800088.
693 The layout of the following structs has changed: sysctl_oid,
694 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
695 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
696 panics may be experienced. World rebuild is required for
697 correctly checking networking state from userland.
698 Bump __FreeBSD_version to 800085.
701 MLDv2 and Source-Specific Multicast (SSM) have been merged
702 to the IPv6 stack. VIMAGE hooks are in but not yet used.
703 The implementation of SSM within FreeBSD's IPv6 stack closely
704 follows the IPv4 implementation.
706 For kernel developers:
708 * The most important changes are that the ip6_output() and
709 ip6_input() paths no longer take the IN6_MULTI_LOCK,
710 and this lock has been downgraded to a non-recursive mutex.
712 * As with the changes to the IPv4 stack to support SSM, filtering
713 of inbound multicast traffic must now be performed by transport
714 protocols within the IPv6 stack. This does not apply to TCP and
715 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
717 * The KPIs used by IPv6 multicast are similar to those used by
718 the IPv4 stack, with the following differences:
719 * im6o_mc_filter() is analogous to imo_multicast_filter().
720 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
721 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
722 * IN6_LOOKUP_MULTI() has been deprecated and removed.
723 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
724 for MLDv1 have an additional 'timer' argument which is used to
725 jitter the initial membership report for the solicited-node
726 multicast membership on-link.
727 * This is not strictly needed for MLDv2, which already jitters
728 its report transmissions. However, the 'timer' argument is
729 preserved in case MLDv1 is active on the interface.
731 * The KAME linked-list based IPv6 membership implementation has
732 been refactored to use a vector similar to that used by the IPv4
734 Code which maintains a list of its own multicast memberships
735 internally, e.g. carp, has been updated to reflect the new
738 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
739 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
740 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
741 implementation constraint which needs to be addressed in HEAD.
743 For application developers:
745 * The changes are broadly similar to those made for the IPv4
748 * The use of IPv4 and IPv6 multicast socket options on the same
749 socket, using mapped addresses, HAS NOT been tested or supported.
751 * There are a number of issues with the implementation of various
752 IPv6 multicast APIs which need to be resolved in the API surface
753 before the implementation is fully compatible with KAME userland
754 use, and these are mostly to do with interface index treatment.
756 * The literature available discusses the use of either the delta / ASM
757 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
758 using setsourcefilter(3)/getsourcefilter(3). For more information
759 please refer to RFC 3768, 'Socket Interface Extensions for
760 Multicast Source Filters'.
762 * Applications which use the published RFC 3678 APIs should be fine.
764 For systems administrators:
766 * The mtest(8) utility has been refactored to support IPv6, in
767 addition to IPv4. Interface addresses are no longer accepted
768 as arguments, their names must be used instead. The utility
769 will map the interface name to its first IPv4 address as
770 returned by getifaddrs(3).
772 * The ifmcstat(8) utility has also been updated to print the MLDv2
773 endpoint state and source filter lists via sysctl(3).
775 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
776 loopback of IPv6 multicast datagrams by default; it defaults to 1
777 to preserve the existing behaviour. Disabling multicast loopback is
778 recommended for optimal system performance.
780 * The IPv6 MROUTING code has been changed to examine this sysctl
781 instead of attempting to perform a group lookup before looping
782 back forwarded datagrams.
784 Bump __FreeBSD_version to 800084.
787 Implement low-level Bluetooth HCI API.
788 Bump __FreeBSD_version to 800083.
791 The layout of struct malloc_type, used by modules to register new
792 memory allocation types, has changed. Most modules will need to
793 be rebuilt or panics may be experienced.
794 Bump __FreeBSD_version to 800081.
797 Anticipate overflowing inp_flags - add inp_flags2.
798 This changes most offsets in inpcb, so checking v4 connection
799 state will require a world rebuild.
800 Bump __FreeBSD_version to 800080.
803 Add an llentry to struct route and struct route_in6. Modules
804 embedding a struct route will need to be recompiled.
805 Bump __FreeBSD_version to 800079.
808 The size of rt_metrics_lite and by extension rtentry has changed.
809 Networking administration apps will need to be recompiled.
810 The route command now supports show as an alias for get, weighting
811 of routes, sticky and nostick flags to alter the behavior of stateful
813 Bump __FreeBSD_version to 800078.
816 Do not use Giant for kbdmux(4) locking. This is wrong and
817 apparently causing more problems than it solves. This will
818 re-open the issue where interrupt handlers may race with
819 kbdmux(4) in polling mode. Typical symptoms include (but
820 not limited to) duplicated and/or missing characters when
821 low level console functions (such as gets) are used while
822 interrupts are enabled (for example geli password prompt,
823 mountroot prompt etc.). Disabling kbdmux(4) may help.
826 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
827 kernel modules referencing any of the above need to be recompiled.
828 Bump __FreeBSD_version to 800075.
831 GEOM_PART has become the default partition slicer for storage devices,
832 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
833 introduces some changes:
835 MSDOS/EBR: the devices created from MSDOS extended partition entries
836 (EBR) can be named differently than with GEOM_MBR and are now symlinks
837 to devices with offset-based names. fstabs may need to be modified.
839 BSD: the "geometry does not match label" warning is harmless in most
840 cases but it points to problems in file system misalignment with
841 disk geometry. The "c" partition is now implicit, covers the whole
842 top-level drive and cannot be (mis)used by users.
844 General: Kernel dumps are now not allowed to be written to devices
845 whose partition types indicate they are meant to be used for file
846 systems (or, in case of MSDOS partitions, as something else than
849 Most of these changes date approximately from 200812.
852 The uscanner(4) driver has been removed from the kernel. This follows
853 Linux removing theirs in 2.6 and making libusb the default interface
857 The multicast forwarding code has been cleaned up. netstat(1)
858 only relies on KVM now for printing bandwidth upcall meters.
859 The IPv4 and IPv6 modules are split into ip_mroute_mod and
860 ip6_mroute_mod respectively. The config(5) options for statically
861 compiling this code remain the same, i.e. 'options MROUTING'.
864 Support for the IFF_NEEDSGIANT network interface flag has been
865 removed, which means that non-MPSAFE network device drivers are no
866 longer supported. In particular, if_ar, if_sr, and network device
867 drivers from the old (legacy) USB stack can no longer be built or
871 POSIX.1 Native Language Support (NLS) has been enabled in libc and
872 a bunch of new language catalog files have also been added.
873 This means that some common libc messages are now localized and
874 they depend on the LC_MESSAGES environmental variable.
877 The k8temp(4) driver has been renamed to amdtemp(4) since
878 support for Family 10 and Family 11 CPU families was added.
881 IGMPv3 and Source-Specific Multicast (SSM) have been merged
882 to the IPv4 stack. VIMAGE hooks are in but not yet used.
884 For kernel developers, the most important changes are that the
885 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
886 and this lock has been downgraded to a non-recursive mutex.
888 Transport protocols (UDP, Raw IP) are now responsible for filtering
889 inbound multicast traffic according to group membership and source
890 filters. The imo_multicast_filter() KPI exists for this purpose.
891 Transports which do not use multicast (SCTP, TCP) already reject
892 multicast by default. Forwarding and receive performance may improve
893 as a mutex acquisition is no longer needed in the ip_input()
894 low-level input path. in_addmulti() and in_delmulti() are shimmed
895 to new KPIs which exist to support SSM in-kernel.
897 For application developers, it is recommended that loopback of
898 multicast datagrams be disabled for best performance, as this
899 will still cause the lock to be taken for each looped-back
900 datagram transmission. The net.inet.ip.mcast.loop sysctl may
901 be tuned to 0 to disable loopback by default; it defaults to 1
902 to preserve the existing behaviour.
904 For systems administrators, to obtain best performance with
905 multicast reception and multiple groups, it is always recommended
906 that a card with a suitably precise hash filter is used. Hash
907 collisions will still result in the lock being taken within the
908 transport protocol input path to check group membership.
910 If deploying FreeBSD in an environment with IGMP snooping switches,
911 it is recommended that the net.inet.igmp.sendlocal sysctl remain
912 enabled; this forces 224.0.0.0/24 group membership to be announced
915 The size of 'struct igmpstat' has changed; netstat needs to be
916 recompiled to reflect this.
917 Bump __FreeBSD_version to 800070.
920 libusb20.so.1 is now installed as libusb.so.1 and the ports system
921 updated to use it. This requires a buildworld/installworld in order to
922 update the library and dependencies (usbconfig, etc). Its advisable to
923 rebuild all ports which uses libusb. More specific directions are given
924 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
925 libusb are no longer required and can be removed.
928 A workaround is committed to allow the creation of System V shared
929 memory segment of size > 2 GB on the 64-bit architectures.
930 Due to a limitation of the existing ABI, the shm_segsz member
931 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
932 wrong for large segments. Note that limits must be explicitly
933 raised to allow such segments to be created.
936 The layout of struct ifnet has changed, requiring a rebuild of all
937 network device driver modules.
940 The /dev handling for the new USB stack has changed, a
941 buildworld/installworld is required for libusb20.
944 The new USB2 stack has now been permanently moved in and all kernel and
945 module names reverted to their previous values (eg, usb, ehci, ohci,
946 ums, ...). The old usb stack can be compiled in by prefixing the name
947 with the letter 'o', the old usb modules have been removed.
948 Updating entry 20090216 for xorg and 20090215 for libmap may still
952 The rc.conf(5) option if_up_delay has been renamed to
953 defaultroute_delay to better reflect its purpose. If you have
954 customized this setting in /etc/rc.conf you need to update it to
958 xorg 7.4 wants to configure its input devices via hald which does not
959 yet work with USB2. If the keyboard/mouse does not work in xorg then
961 Option "AllowEmptyInput" "off"
962 to your ServerLayout section. This will cause X to use the configured
963 kbd and mouse sections from your xorg.conf.
966 The GENERIC kernels for all architectures now default to the new USB2
967 stack. No kernel config options or code have been removed so if a
968 problem arises please report it and optionally revert to the old USB
969 stack. If you are loading USB kernel modules or have a custom kernel
970 that includes GENERIC then ensure that usb names are also changed over,
971 eg uftdi -> usb2_serial_ftdi.
973 Older programs linked against the ports libusb 0.1 need to be
974 redirected to the new stack's libusb20. /etc/libmap.conf can
976 # Map old usb library to new one for usb2 stack
977 libusb-0.1.so.8 libusb20.so.1
980 All USB ethernet devices now attach as interfaces under the name ueN
981 (eg. ue0). This is to provide a predictable name as vendors often
982 change usb chipsets in a product without notice.
985 The ichsmb(4) driver has been changed to require SMBus slave
986 addresses be left-justified (xxxxxxx0b) rather than right-justified.
987 All of the other SMBus controller drivers require left-justified
988 slave addresses, so this change makes all the drivers provide the
992 INET6 statistics (struct ip6stat) was updated.
993 netstat(1) needs to be recompiled.
996 NTFS has been removed from GENERIC kernel on amd64 to match
997 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
998 will load ntfs.ko module automatically when NTFS support is
999 actually needed, unless ntfs.ko is not installed or security
1000 level prohibits loading kernel modules. If either is the case,
1001 "options NTFS" has to be added into kernel config.
1004 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1005 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1006 800061. User space tools that rely on the size of struct tcpcb in
1007 tcp_var.h (e.g. sockstat) need to be recompiled.
1010 ng_tty(4) module updated to match the new TTY subsystem.
1011 Due to API change, user-level applications must be updated.
1012 New API support added to mpd5 CVS and expected to be present
1013 in next mpd5.3 release.
1016 With __FreeBSD_version 800060 the makefs tool is part of
1017 the base system (it was a port).
1020 The afdata and ifnet locks have been changed from mutexes to
1021 rwlocks, network modules will need to be re-compiled.
1024 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1025 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1026 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1027 architecture and 40 bytes on 64-bit architecture. The userland
1028 applications "arp" and "ndp" have been updated accordingly.
1029 The output from "netstat -r" shows only routing entries and
1030 none of the L2 information.
1033 __FreeBSD_version 800057 marks the switchover from the
1034 binary ath hal to source code. Users must add the line:
1036 options AH_SUPPORT_AR5416
1038 to their kernel config files when specifying:
1042 The ath_hal module no longer exists; the code is now compiled
1043 together with the driver in the ath module. It is now
1044 possible to tailor chip support (i.e. reduce the set of chips
1045 and thereby the code size); consult ath_hal(4) for details.
1048 __FreeBSD_version 800054 adds memory barriers to
1049 <machine/atomic.h>, new interfaces to ifnet to facilitate
1050 multiple hardware transmit queues for cards that support
1051 them, and a lock-less ring-buffer implementation to
1052 enable drivers to more efficiently manage queueing of
1056 A new version of ZFS (version 13) has been merged to -HEAD.
1057 This version has zpool attribute "listsnapshots" off by
1058 default, which means "zfs list" does not show snapshots,
1059 and is the same as Solaris behavior.
1062 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1065 The uhci, ohci, ehci and slhci USB Host controller drivers have
1066 been put into separate modules. If you load the usb module
1067 separately through loader.conf you will need to load the
1068 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1069 controller add the following to loader.conf:
1075 The ABI used by the PMC toolset has changed. Please keep
1076 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1080 atapci kernel module now includes only generic PCI ATA
1081 driver. AHCI driver moved to ataahci kernel module.
1082 All vendor-specific code moved into separate kernel modules:
1083 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1084 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1085 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1086 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1089 The TTY subsystem of the kernel has been replaced by a new
1090 implementation, which provides better scalability and an
1091 improved driver model. Most common drivers have been migrated to
1092 the new TTY subsystem, while others have not. The following
1093 drivers have not yet been ported to the new TTY layer:
1096 cy, digi, rc, rp, sio
1102 ng_h4, ng_tty, ppp, sl, snp
1104 Adding these drivers to your kernel configuration file shall
1105 cause compilation to fail.
1108 ntpd has been upgraded to 4.2.4p5.
1111 OpenSSH has been upgraded to 5.1p1.
1113 For many years, FreeBSD's version of OpenSSH preferred DSA
1114 over RSA for host and user authentication keys. With this
1115 upgrade, we've switched to the vendor's default of RSA over
1116 DSA. This may cause upgraded clients to warn about unknown
1117 host keys even for previously known hosts. Users should
1118 follow the usual procedure for verifying host keys before
1119 accepting the RSA key.
1121 This can be circumvented by setting the "HostKeyAlgorithms"
1122 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1125 Please note that the sequence of keys offered for
1126 authentication has been changed as well. You may want to
1127 specify IdentityFile in a different order to revert this
1131 The sio(4) driver has been removed from the i386 and amd64
1132 kernel configuration files. This means uart(4) is now the
1133 default serial port driver on those platforms as well.
1135 To prevent collisions with the sio(4) driver, the uart(4) driver
1136 uses different names for its device nodes. This means the
1137 onboard serial port will now most likely be called "ttyu0"
1138 instead of "ttyd0". You may need to reconfigure applications to
1139 use the new device names.
1141 When using the serial port as a boot console, be sure to update
1142 /boot/device.hints and /etc/ttys before booting the new kernel.
1143 If you forget to do so, you can still manually specify the hints
1144 at the loader prompt:
1146 set hint.uart.0.at="isa"
1147 set hint.uart.0.port="0x3F8"
1148 set hint.uart.0.flags="0x10"
1149 set hint.uart.0.irq="4"
1153 The gpt(8) utility has been removed. Use gpart(8) to partition
1157 The version that Linuxulator emulates was changed from 2.4.2
1158 to 2.6.16. If you experience any problems with Linux binaries
1159 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1160 if it fixes the problem contact emulation mailing list.
1163 ISDN4BSD (I4B) was removed from the src tree. You may need to
1164 update a your kernel configuration and remove relevant entries.
1167 I have checked in code to support multiple routing tables.
1168 See the man pages setfib(1) and setfib(2).
1169 This is a hopefully backwards compatible version,
1170 but to make use of it you need to compile your kernel
1171 with options ROUTETABLES=2 (or more up to 16).
1174 The 802.11 wireless support was redone to enable multi-bss
1175 operation on devices that are capable. The underlying device
1176 is no longer used directly but instead wlanX devices are
1177 cloned with ifconfig. This requires changes to rc.conf files.
1178 For example, change:
1179 ifconfig_ath0="WPA DHCP"
1182 ifconfig_wlan0="WPA DHCP"
1183 see rc.conf(5) for more details. In addition, mergemaster of
1184 /etc/rc.d is highly recommended. Simultaneous update of userland
1185 and kernel wouldn't hurt either.
1187 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1188 modules were merged into the base wlan module. All references
1189 to these modules (e.g. in kernel config files) must be removed.
1192 psm(4) has gained write(2) support in native operation level.
1193 Arbitrary commands can be written to /dev/psm%d and status can
1194 be read back from it. Therefore, an application is responsible
1195 for status validation and error recovery. It is a no-op in
1196 other operation levels.
1199 Support for KSE threading has been removed from the kernel. To
1200 run legacy applications linked against KSE libmap.conf may
1201 be used. The following libmap.conf may be used to ensure
1202 compatibility with any prior release:
1204 libpthread.so.1 libthr.so.1
1205 libpthread.so.2 libthr.so.2
1206 libkse.so.3 libthr.so.3
1209 The layout of struct vmspace has changed. This affects libkvm
1210 and any executables that link against libkvm and use the
1211 kvm_getprocs() function. In particular, but not exclusively,
1212 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1213 The effects are minimal, but it's advisable to upgrade world
1217 The latest em driver no longer has support in it for the
1218 82575 adapter, this is now moved to the igb driver. The
1219 split was done to make new features that are incompatible
1220 with older hardware easier to do.
1223 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1224 likewise the kernel option is now GEOM_LINUX_LVM.
1227 The default NFS mount mode has changed from UDP to TCP for
1228 increased reliability. If you rely on (insecurely) NFS
1229 mounting across a firewall you may need to update your
1233 Belatedly note the addition of m_collapse for compacting
1237 The fts(3) structures have been changed to use adequate
1238 integer types for their members and so to be able to cope
1239 with huge file trees. The old fts(3) ABI is preserved
1240 through symbol versioning in libc, so third-party binaries
1241 using fts(3) should still work, although they will not take
1242 advantage of the extended types. At the same time, some
1243 third-party software might fail to build after this change
1244 due to unportable assumptions made in its source code about
1245 fts(3) structure members. Such software should be fixed
1246 by its vendor or, in the worst case, in the ports tree.
1247 FreeBSD_version 800015 marks this change for the unlikely
1248 case that a portable fix is impossible.
1251 To upgrade to -current after this date, you must be running
1252 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1253 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1256 The ADAPTIVE_GIANT kernel option has been retired because its
1257 functionality is the default now.
1260 The AT keyboard emulation of sunkbd(4) has been turned on
1261 by default. In order to make the special symbols of the Sun
1262 keyboards driven by sunkbd(4) work under X these now have
1263 to be configured the same way as Sun USB keyboards driven
1264 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1266 Option "XkbLayout" "us"
1267 Option "XkbRules" "xorg"
1268 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1271 It has been decided that it is desirable to provide ABI
1272 backwards compatibility to the FreeBSD 4/5/6 versions of the
1273 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1274 broken with the introduction of PCI domain support (see the
1275 20070930 entry). Unfortunately, this required the ABI of
1276 PCIOCGETCONF to be broken again in order to be able to
1277 provide backwards compatibility to the old version of that
1278 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1279 again. As for prominent ports this affects neither pciutils
1280 nor xorg-server this time, the hal port needs to be rebuilt
1284 The misnamed kthread_create() and friends have been renamed
1285 to kproc_create() etc. Many of the callers already
1286 used kproc_start()..
1287 I will return kthread_create() and friends in a while
1288 with implementations that actually create threads, not procs.
1289 Renaming corresponds with version 800002.
1298 Avoid using make -j when upgrading. While generally safe, there are
1299 sometimes problems using -j to upgrade. If your upgrade fails with
1300 -j, please try again without -j. From time to time in the past there
1301 have been problems using -j with buildworld and/or installworld. This
1302 is especially true when upgrading between "distant" versions (eg one
1303 that cross a major release boundary or several minor releases, or when
1304 several months have passed on the -current branch).
1306 Sometimes, obscure build problems are the result of environment
1307 poisoning. This can happen because the make utility reads its
1308 environment when searching for values for global variables. To run
1309 your build attempts in an "environmental clean room", prefix all make
1310 commands with 'env -i '. See the env(1) manual page for more details.
1312 When upgrading from one major version to another it is generally best
1313 to upgrade to the latest code in the currently installed branch first,
1314 then do an upgrade to the new branch. This is the best-tested upgrade
1315 path, and has the highest probability of being successful. Please try
1316 this approach before reporting problems with a major version upgrade.
1320 When upgrading the boot ZFS pool to a new version, always follow
1323 1.) recompile and reinstall the ZFS boot loader and boot block
1324 (this is part of "make buildworld" and "make installworld")
1326 2.) update the ZFS boot block on your boot drive
1328 The following example updates the ZFS boot block on the first
1329 partition (freebsd-boot) of a GPT partitioned drive ad0:
1330 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1332 Non-boot pools do not need these updates.
1336 If you are updating from a prior version of FreeBSD (even one just
1337 a few days old), you should follow this procedure. It is the most
1338 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1340 make kernel-toolchain
1341 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1342 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1344 To test a kernel once
1345 ---------------------
1346 If you just want to boot a kernel once (because you are not sure
1347 if it works, or if you want to boot a known bad kernel to provide
1348 debugging information) run
1349 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1350 nextboot -k testkernel
1352 To just build a kernel when you know that it won't mess you up
1353 --------------------------------------------------------------
1354 This assumes you are already running a CURRENT system. Replace
1355 ${arch} with the architecture of your machine (e.g. "i386",
1356 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1358 cd src/sys/${arch}/conf
1359 config KERNEL_NAME_HERE
1360 cd ../compile/KERNEL_NAME_HERE
1365 If this fails, go to the "To build a kernel" section.
1367 To rebuild everything and install it on the current system.
1368 -----------------------------------------------------------
1369 # Note: sometimes if you are running current you gotta do more than
1370 # is listed here if you are upgrading from a really old current.
1372 <make sure you have good level 0 dumps>
1374 make kernel KERNCONF=YOUR_KERNEL_HERE
1376 <reboot in single user> [3]
1384 To cross-install current onto a separate partition
1385 --------------------------------------------------
1386 # In this approach we use a separate partition to hold
1387 # current's root, 'usr', and 'var' directories. A partition
1388 # holding "/", "/usr" and "/var" should be about 2GB in
1391 <make sure you have good level 0 dumps>
1394 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1395 <maybe newfs current's root partition>
1396 <mount current's root partition on directory ${CURRENT_ROOT}>
1397 make installworld DESTDIR=${CURRENT_ROOT}
1398 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1399 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1400 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1401 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1402 <reboot into current>
1403 <do a "native" rebuild/install as described in the previous section>
1404 <maybe install compatibility libraries from ports/misc/compat*>
1408 To upgrade in-place from 8.x-stable to current
1409 ----------------------------------------------
1410 <make sure you have good level 0 dumps>
1412 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1414 <reboot in single user> [3]
1421 Make sure that you've read the UPDATING file to understand the
1422 tweaks to various things you need. At this point in the life
1423 cycle of current, things change often and you are on your own
1424 to cope. The defaults can also change, so please read ALL of
1425 the UPDATING entries.
1427 Also, if you are tracking -current, you must be subscribed to
1428 freebsd-current@freebsd.org. Make sure that before you update
1429 your sources that you have read and understood all the recent
1430 messages there. If in doubt, please track -stable which has
1431 much fewer pitfalls.
1433 [1] If you have third party modules, such as vmware, you
1434 should disable them at this point so they don't crash your
1437 [3] From the bootblocks, boot -s, and then do
1442 adjkerntz -i # if CMOS is wall time
1443 Also, when doing a major release upgrade, it is required that
1444 you boot into single user mode to do the installworld.
1446 [4] Note: This step is non-optional. Failure to do this step
1447 can result in a significant reduction in the functionality of the
1448 system. Attempting to do it by hand is not recommended and those
1449 that pursue this avenue should read this file carefully, as well
1450 as the archives of freebsd-current and freebsd-hackers mailing lists
1451 for potential gotchas. The -U option is also useful to consider.
1452 See mergemaster(8) for more information.
1454 [5] Usually this step is a noop. However, from time to time
1455 you may need to do this if you get unknown user in the following
1456 step. It never hurts to do it all the time. You may need to
1457 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1458 install) after the buildworld before this step if you last updated
1459 from current before 20020224 or from -stable before 20020408.
1461 [6] This only deletes old files and directories. Old libraries
1462 can be deleted by "make delete-old-libs", but you have to make
1463 sure that no program is using those libraries anymore.
1465 [8] In order to have a kernel that can run the 4.x binaries needed to
1466 do an installworld, you must include the COMPAT_FREEBSD4 option in
1467 your kernel. Failure to do so may leave you with a system that is
1468 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1469 required to run the 5.x binaries on more recent kernels. And so on
1470 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1472 Make sure that you merge any new devices from GENERIC since the
1473 last time you updated your kernel config file.
1475 [9] When checking out sources, you must include the -P flag to have
1476 cvs prune empty directories.
1478 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1479 "?=" instead of the "=" assignment operator, so that buildworld can
1480 override the CPUTYPE if it needs to.
1482 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1483 not on the command line, or in /etc/make.conf. buildworld will
1484 warn if it is improperly defined.
1487 This file contains a list, in reverse chronological order, of major
1488 breakages in tracking -current. It is not guaranteed to be a complete
1489 list of such breakages, and only contains entries since October 10, 2007.
1490 If you need to see UPDATING entries from before that date, you will need
1491 to fetch an UPDATING file from an older FreeBSD release.
1493 Copyright information:
1495 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1497 Redistribution, publication, translation and use, with or without
1498 modification, in full or in part, in any form or format of this
1499 document are permitted without further permission from the author.
1501 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1502 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1503 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1504 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1505 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1506 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1507 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1508 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1509 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1510 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1511 POSSIBILITY OF SUCH DAMAGE.
1513 Contact Warner Losh if you have any questions about your use of