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