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