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