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 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 20140430: p5 FreeBSD-SA-14:08.tcp
16 Fix TCP reassembly vulnerability. [SA-14:08]
18 20140408: p4 FreeBSD-SA-14:05.nfsserver
19 FreeBSD-SA-14:06.openssl
20 Fix deadlock in the NFS server. [SA-14:05]
22 Fix for ECDSA Cache Side-channel Attack in OpenSSL. [SA-14:06]
24 20140114: p3 FreeBSD-SA-14:01.bsnmpd
27 FreeBSD-EN-14:01.random
29 Fix bsnmpd remote denial of service vulnerability. [SA-14:01]
31 Fix ntpd distributed reflection Denial of Service
32 vulnerability. [SA-14:02]
34 Fix BIND remote denial of service vulnerability. [SA-14:04]
36 Disable hardware RNGs by default. [EN-14:01]
38 Fix incorrect coalescing of stack entry with mmap. [EN-14:02]
40 20131128: p2 FreeBSD-EN-13:05.freebsd-update
41 Fix error in patch for FreeBSD-EN-13:04.freebsd-update.
43 20131026: p1 FreeBSD-EN-13:04.freebsd-update
44 Fix multiple freebsd-update bugs that break upgrading to
48 hastctl(8)'s `status' command output changed to terse one-liner format.
49 Scripts using this should switch to `list' command or be rewritten.
52 Fix a bug that allowed a tracing process (e.g. gdb) to write
53 to a memory-mapped file in the traced process's address space
54 even if neither the traced process nor the tracing process had
55 write access to that file.
58 Added ZFS TRIM support which is enabled by default. To disable
59 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
61 Creating new ZFS pools and adding new devices to existing pools
62 first performs a full device level TRIM which can take a significant
63 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
64 to disable this behaviour.
66 ZFS TRIM requires the underlying device support BIO_DELETE which
67 is currently provided by methods such as ATA TRIM and SCSI UNMAP
68 via CAM, which are typically supported by SSD's.
70 Stats for ZFS TRIM can be monitored by looking at the sysctl's
71 under kstat.zfs.misc.zio_trim.
74 `list' command has been added to hastctl(8). For now, it is full
75 equivalent of `status' command.
76 WARNING: in the near future the output of hastctl's status command
77 will change to more terse format. If you use `hastctl status'
78 for parsing in your scripts, switch to `hastctl list'.
81 The mergemaster command now uses the default MAKEOBJDIRPREFIX
82 rather than creating it's own in the temporary directory in
83 order allow access to bootstrapped versions of tools such as
84 install and mtree. When upgrading from version of FreeBSD where
85 the install command does not support -l, you will need to
86 install a new mergemaster command if mergemaster -p is required.
87 This can be accomplished with the command (cd src/usr.sbin/mergemaster
90 Due to the use of the new -l option to install(1) during build
91 and install, you must take care not to directly set the INSTALL
92 make variable in your /etc/make.conf, /etc/src.conf, or on the
93 command line. If you wish to use the -C flag for all installs
94 you may be able to add INSTALL+=-C to /etc/make.conf or
98 Fix a bug that allows NFS clients to issue READDIR on files.
101 The install(1) option -M has changed meaning and now takes an
102 argument that is a file or path to append logs to. In the
103 unlikely event that -M was the last option on the command line
104 and the command line contained at least two files and a target
105 directory the first file will have logs appended to it. The -M
106 option served little practical purpose in the last decade so it's
107 used expected to be extremely rare.
110 A new compression method (lz4) has been merged to. Please refer to
111 zpool-features(7) for more information.
113 Please refer to the "ZFS notes" section of this file for information
114 on upgrading boot ZFS pools.
117 The VFS KBI was changed with the merge of several nullfs
118 optimizations and fixes. All filesystem modules must be
122 With the addition of auditdistd(8), a new auditdistd user is now
123 depended on during installworld. "mergemaster -p" can be used to add
124 the user prior to installworld, as documented in the handbook.
130 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
131 Starting with this version the old system of ZFS pool versioning
132 is superseded by "feature flags". This concept enables forward
133 compatibility against certain future changes in functionality of ZFS
134 pools. The first two read-only compatible "feature flags" for ZFS
135 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
136 For more information read the new zpool-features(7) manual page.
137 Please refer to the "ZFS notes" section of this file for information
138 on upgrading boot ZFS pools.
141 The commit introducing bsd.compiler.mk breaks the traditional
142 building of kernels before this point. Add -m ${SRC}/share/mk
143 (for the right value of SRC) to your command lines to work
144 around; update your useland to a point after this; or use the
145 buildkernel/installkernel top-level targets. See also 20120829.
148 The IPFIREWALL_FORWARD kernel option has been removed. Its
149 functionality now turned on by default.
152 The random(4) support for the VIA hardware random number
153 generator (`PADLOCK') is no longer enabled unconditionally.
154 Add the PADLOCK_RNG option in the custom kernel config if
155 needed. The GENERIC kernels on i386 and amd64 do include the
156 option, so the change only affects the custom kernel
160 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
161 the traditional method, you must update your system with an installworld
162 before the kernel will build. The documented make buildkernel/installkernel
163 interfaces (coupled with fresh make kernel-toolchain) continue to work.
166 The sparc64 ZFS loader has been changed to no longer try to auto-
167 detect ZFS providers based on diskN aliases but now requires these
168 to be explicitly listed in the OFW boot-device environment variable.
171 Now unix domain sockets behave "as expected" on nullfs(5). Previously
172 nullfs(5) did not pass through all behaviours to the underlying layer,
173 as a result if we bound to a socket on the lower layer we could connect
174 only to the lower path; if we bound to the upper layer we could connect
175 only to the upper path. The new behavior is one can connect to both the
176 lower and the upper paths regardless what layer path one binds to.
179 The acpi_wmi(4) status device /dev/wmistat has been renamed to
183 A new VOP_ADVISE() was added to support posix_fadvise(2). All
184 filesystem modules must be recompiled.
187 The interface of the VOP_VPTOCNP(9) changed, now the returned
188 vnode shall be referenced, previously it was required to be
189 only held. All in-tree filesystems are converted.
195 The broken amd(4) driver has been replaced with esp(4) in the amd64,
196 i386 and pc98 GENERIC kernel configuration files.
199 This commit modifies vfs_register() so that it uses a hash
200 calculation to set vfc_typenum, which is enabled by default.
201 The first time a system is booted after this change, the
202 vfc_typenum values will change for all file systems. The
203 main effect of this is a change to the NFS server file handles
204 for file systems that use vfc_typenum in their fsid, such as ZFS.
205 It will, however, prevent vfc_typenum from changing when file
206 systems are loaded in a different order for subsequent reboots.
207 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
208 until you are ready to remount all NFS clients after a reboot.
211 Bump the shared library version numbers for libraries that
212 do not use symbol versioning, have changed the ABI compared
213 to stable/8 and which shared library version was not bumped.
214 Done as part of 9.0-RELEASE cycle.
217 During the merge of Capsicum features, the fget(9) KPI was modified.
218 This may require the rebuilding of out-of-tree device drivers --
219 issues have been reported specifically with the nVidia device driver.
220 __FreeBSD_version is bumped to 900041.
222 Also, there is a period between 20110811 and 20110814 where the
223 special devices /dev/{stdin,stdout,stderr} did not work correctly.
224 Building world from a kernel during that window may not work.
227 The packet filter (pf) code has been updated to OpenBSD 4.5.
228 You need to update userland tools to be in sync with kernel.
229 This update breaks backward compatibility with earlier pfsync(4)
230 versions. Care must be taken when updating redundant firewall setups.
233 The following sysctls and tunables are retired on x86 platforms:
235 machdep.hlt_logical_cpus
236 The following sysctl is retired:
237 machdep.hyperthreading_allowed
238 The sysctls were supposed to provide a way to dynamically offline and
239 online selected CPUs on x86 platforms, but the implementation has not
240 been reliable especially with SCHED_ULE scheduler.
241 machdep.hyperthreading_allowed tunable is still available to ignore
242 hyperthreading CPUs at OS level.
243 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
244 where X is an APIC ID of a CPU. Be advised, though, that disabling
245 CPUs in non-uniform fashion will result in non-uniform topology and
246 may lead to sub-optimal system performance with SCHED_ULE, which is
250 cpumask_t type is retired and cpuset_t is used in order to describe
254 Changes to ifconfig(8) for dynamic address family detection mandate
255 that you are running a kernel of 20110525 or later. Make sure to
256 follow the update procedure to boot a new kernel before installing
260 Support for sun4v architecture is officially dropped
263 Several KPI breaking changes have been committed to the mii(4) layer,
264 the PHY drivers and consequently some Ethernet drivers using mii(4).
265 This means that miibus.ko and the modules of the affected Ethernet
266 drivers need to be recompiled.
268 Note to kernel developers: Given that the OUI bit reversion problem
269 was fixed as part of these changes all mii(4) commits related to OUIs,
270 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
271 handling, no longer can be merged verbatim to stable/8 and previous
275 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
276 into their kernel configurations along with 'device pci'.
279 The default NFS client is now the new NFS client, so fstype "newnfs"
280 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
281 Although mounts via fstype "nfs" will usually work without userland
282 changes, it is recommended that the mount(8) and mount_nfs(8)
283 commands be rebuilt from sources and that a link to mount_nfs called
284 mount_oldnfs be created. The new client is compiled into the
285 kernel with "options NFSCL" and this is needed for diskless root
286 file systems. The GENERIC kernel configs have been changed to use
287 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
288 To use the regular/old client, you can "mount -t oldnfs ...". For
289 a diskless root file system, you must also include a line like:
291 vfs.root.mountfrom="oldnfs:"
293 in the boot/loader.conf on the root fs on the NFS server to make
294 a diskless root fs use the old client.
297 The GENERIC kernels for all architectures now default to the new
298 CAM-based ATA stack. It means that all legacy ATA drivers were
299 removed and replaced by respective CAM drivers. If you are using
300 ATA device names in /etc/fstab or other places, make sure to update
301 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
302 where 'Y's are the sequential numbers starting from zero for each type
303 in order of detection, unless configured otherwise with tunables,
304 see cam(4)). There will be symbolic links created in /dev/ to map
305 old adX devices to the respective adaY. They should provide basic
306 compatibility for file systems mounting in most cases, but they do
307 not support old user-level APIs and do not have respective providers
308 in GEOM. Consider using updated management tools with new device names.
310 It is possible to load devices ahci, ata, siis and mvs as modules,
311 but option ATA_CAM should remain in kernel configuration to make ata
312 module work as CAM driver supporting legacy ATA controllers. Device ata
313 still can be used in modular fashion (atacore + ...). Modules atadisk
314 and atapi* are not used and won't affect operation in ATA_CAM mode.
315 Note that to use CAM-based ATA kernel should include CAM devices
316 scbus, pass, da (or explicitly ada), cd and optionally others. All of
317 them are parts of the cam module.
319 ataraid(4) functionality is now supported by the RAID GEOM class.
320 To use it you can load geom_raid kernel module and use graid(8) tool
321 for management. Instead of /dev/arX device names, use /dev/raid/rX.
323 No kernel config options or code have been removed, so if a problem
324 arises, please report it and optionally revert to the old ATA stack.
325 In order to do it you can remove from the kernel config:
330 , and instead add back:
331 device atadisk # ATA disk drives
332 device ataraid # ATA RAID drives
333 device atapicd # ATAPI CDROM drives
334 device atapifd # ATAPI floppy drives
335 device atapist # ATAPI tape drives
338 The default NFS server has been changed to the new server, which
339 was referred to as the experimental server. If you need to switch
340 back to the old NFS server, you must now put the "-o" option on
341 both the mountd and nfsd commands. This can be done using the
342 mountd_flags and nfs_server_flags rc.conf variables until an
343 update to the rc scripts is committed, which is coming soon.
346 The GNU Objective-C runtime library (libobjc), and other Objective-C
347 related components have been removed from the base system. If you
348 require an Objective-C library, please use one of the available ports.
351 ath(4) has been split into bus- and device- modules. if_ath contains
352 the HAL, the TX rate control and the network device code. if_ath_pci
353 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
354 contains the AHB glue. Users need to load both if_ath_pci and if_ath
355 in order to use ath on everything else.
357 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
358 need to load if_ath and if_ath_pci for ath(4) operation.
361 As part of the replacement of sysinstall, the process of building
362 release media has changed significantly. For details, please re-read
363 release(7), which has been updated to reflect the new build process.
366 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
367 is the last available version under GPLv2. It brings a number of new
368 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
369 4.1 and SSE 4.2), better support for powerpc64, a number of new
370 directives, and lots of other small improvements. See the ChangeLog
371 file in contrib/binutils for the full details.
374 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
375 compliant, and will now use half of hash for authentication.
376 This will break interoperability with all stacks (including all
377 actual FreeBSD versions) who implement
378 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
380 The only workaround with such peers is to use another HMAC
381 algorithm for IPsec ("phase 2") authentication.
384 Remove the uio_yield prototype and symbol. This function has
385 been misnamed since it was introduced and should not be
386 globally exposed with this name. The equivalent functionality
387 is now available using kern_yield(curthread->td_user_pri).
388 The function remains undocumented.
391 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
392 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
393 for scalar sysctls is defined but disabled. Code that needs
394 UQUAD to pass the type checking that must compile on older
395 systems where the define is not present can check against
396 __FreeBSD_version >= 900030.
398 The system dialog(1) has been replaced with a new version previously
399 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
400 with the previous version, but the libdialog associated with it has
401 a largely incompatible API. As such, the original version of libdialog
402 will be kept temporarily as libodialog, until its base system consumers
403 are replaced or updated. Bump __FreeBSD_version to 900030.
406 If you are trying to run make universe on a -stable system, and you get
407 the following warning:
408 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
409 unknown. config(8) likely too old."
410 or something similar to it, then you must upgrade your -stable system
411 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
412 stable/8) or build the config from the latest stable/8 branch and
413 install it on your system.
415 Prior to this date, building a current universe on 8-stable system from
416 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
417 error in the first kernel build phase. A new config on those old
418 systems will fix that problem for older versions of -current.
421 The TCP stack has been modified to allow Khelp modules to interact with
422 it via helper hook points and store per-connection data in the TCP
423 control block. Bump __FreeBSD_version to 900029. User space tools that
424 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
428 Generic IEEE 802.3 annex 31B full duplex flow control support has been
429 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
430 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
431 to take advantage of it instead of using custom implementations. This
432 means that these drivers now no longer unconditionally advertise
433 support for flow control but only do so if flow control is a selected
434 media option. This was implemented in the generic support that way in
435 order to allow flow control to be switched on and off via ifconfig(8)
436 with the PHY specific default to typically off in order to protect
437 from unwanted effects. Consequently, if you used flow control with
438 one of the above mentioned drivers you now need to explicitly enable
440 ifconfig bge0 media auto mediaopt flowcontrol
442 Along with the above mentioned changes generic support for setting
443 1000baseT master mode also has been added and brgphy(4), ciphy(4),
444 e1000phy(4) as well as ip1000phy(4) have been converted to take
445 advantage of it. This means that these drivers now no longer take the
446 link0 parameter for selecting master mode but the master media option
447 has to be used instead, for example like in the following:
448 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
450 Selection of master mode now is also available with all other PHY
451 drivers supporting 1000baseT.
454 The TCP stack has received a significant update to add support for
455 modularised congestion control and generally improve the clarity of
456 congestion control decisions. Bump __FreeBSD_version to 900025. User
457 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
458 sockstat) need to be recompiled.
461 The man(1) utility has been replaced by a new version that no longer
462 uses /etc/manpath.config. Please consult man.conf(5) for how to
463 migrate local entries to the new format.
466 The copyright strings printed by login(1) and sshd(8) at the time of a
467 new connection have been removed to follow other operating systems and
471 A workaround for a fixed ld bug has been removed in kernel code,
472 so make sure that your system ld is built from sources after
473 revision 210245 from 2010-07-19 (r211583 if building head kernel
474 on stable/8, r211584 for stable/7; both from 2010-08-21).
475 A symptom of incorrect ld version is different addresses for
476 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
479 The $ipv6_prefer variable in rc.conf(5) has been split into
480 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
482 The $ip6addrctl_policy is a variable to choose a pre-defined
483 address selection policy set by ip6addrctl(8). A value
484 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
487 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
488 flag (see an entry of 20090926) is set on an interface with no
489 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
490 security reason. If you want IPv6 link-local address on all
491 interfaces by default, set this to "YES".
493 The old ipv6_prefer="YES" is equivalent to
494 ipv6_activate_all_interfaces="YES" and
495 ip6addrctl_policy="ipv6_prefer".
498 DTrace has grown support for userland tracing. Due to this, DTrace is
499 now i386 and amd64 only.
500 dtruss(1) is now installed by default on those systems and a new
501 kernel module is needed for userland tracing: fasttrap.
502 No changes to your kernel config file are necessary to enable
503 userland tracing, but you might consider adding 'STRIP=' and
504 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
505 to have informative userland stack traces in DTrace (ustack).
508 The acpi_aiboost(4) driver has been removed in favor of the new
509 aibs(4) driver. You should update your kernel configuration file.
512 BSD grep has been imported to the base system and it is built by
513 default. It is completely BSD licensed, highly GNU-compatible, uses
514 less memory than its GNU counterpart and has a small codebase.
515 However, it is slower than its GNU counterpart, which is mostly
516 noticeable for larger searches, for smaller ones it is measurable
517 but not significant. The reason is complex, the most important factor
518 is that we lack a modern and efficient regex library and GNU
519 overcomes this by optimizing the searches internally. Future work
520 on improving the regex performance is planned, for the meantime,
521 users that need better performance, can build GNU grep instead by
522 setting the WITH_GNU_GREP knob.
525 Due to the import of powerpc64 support, all existing powerpc kernel
526 configuration files must be updated with a machine directive like this:
527 machine powerpc powerpc
529 In addition, an updated config(8) is required to build powerpc kernels
533 A new version of ZFS (version 15) has been merged to -HEAD.
534 This version uses a python library for the following subcommands:
535 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
536 For full functionality of these commands the following port must
537 be installed: sysutils/py-zfs
540 'vm_page's are now hashed by physical address to an array of mutexes.
541 Currently this is only used to serialize access to hold_count. Over
542 time the page queue mutex will be peeled away. This changes the size
543 of pmap on every architecture. And requires all callers of vm_page_hold
544 and vm_page_unhold to be updated.
547 WITH_CTF can now be specified in src.conf (not recommended, there
548 are some problems with static executables), make.conf (would also
549 affect ports which do not use GNU make and do not override the
550 compile targets) or in the kernel config (via "makeoptions
552 When WITH_CTF was specified there before this was silently ignored,
553 so make sure that WITH_CTF is not used in places which could lead
554 to unwanted behavior.
557 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
558 to allow 32-bit compatibility on non-x86 platforms. All kernel
559 configurations on amd64 and ia64 platforms using these options must
560 be modified accordingly.
563 The utmp user accounting database has been replaced with utmpx,
564 the user accounting interface standardized by POSIX.
565 Unfortunately the semantics of utmp and utmpx don't match,
566 making it practically impossible to support both interfaces.
567 The user accounting database is used by tools like finger(1),
568 last(1), talk(1), w(1) and ac(8).
570 All applications in the base system use utmpx. This means only
571 local binaries (e.g. from the ports tree) may still use these
572 utmp database files. These applications must be rebuilt to make
575 After the system has been upgraded, it is safe to remove the old
576 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
577 assuming their contents is of no importance anymore. Old wtmp
578 databases can only be used by last(1) and ac(8) after they have
579 been converted to the new format using wtmpcvt(1).
582 Introduce the kernel thread "deadlock resolver" (which can be enabled
583 via the DEADLKRES option, see NOTES for more details) and the
584 sleepq_type() function for sleepqueues.
587 The rc.firewall and rc.firewall6 were unified, and
588 rc.firewall6 and rc.d/ip6fw were removed.
589 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
590 variables are obsoleted. Instead, the following new rc
591 variables are added to rc.d/ipfw:
593 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
594 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
595 firewall_simple_onet_ipv6, firewall_trusted_ipv6
597 The meanings correspond to the relevant IPv4 variables.
603 The default terminal emulation for syscons(4) has been changed
604 from cons25 to xterm on all platforms except pc98. This means
605 that the /etc/ttys file needs to be updated to ensure correct
606 operation of applications on the console.
608 The terminal emulation style can be toggled per window by using
609 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
610 options can be used to change the compile-time default back to
613 To prevent graphical artifacts, make sure the TERM environment
614 variable is set to match the terminal emulation that is being
615 performed by syscons(4).
618 The layout of the structure ieee80211req_scan_result has changed.
619 Applications that require wireless scan results (e.g. ifconfig(8))
620 from net80211 need to be recompiled.
622 Applications such as wpa_supplicant(8) may require a full world
623 build without using NO_CLEAN in order to get synchronized with the
627 The iwn(4) driver has been updated to support the 5000 and 5150 series.
628 There's one kernel module for each firmware. Adding "device iwnfw"
629 to the kernel configuration file means including all three firmware
630 images inside the kernel. If you want to include just the one for
631 your wireless card, use the devices iwn4965fw, iwn5000fw or
635 The rc.d/network_ipv6, IPv6 configuration script has been integrated
636 into rc.d/netif. The changes are the following:
638 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
639 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
640 Note that both variables need the "inet6" keyword at the head.
642 Do not set $ipv6_network_interfaces manually if you do not
643 understand what you are doing. It is not needed in most cases.
645 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
648 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
649 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
651 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
652 all configured interfaces have "inet6 accept_rtadv" in the
653 $ifconfig_IF_ipv6. These are for backward compatibility.
655 3. A new variable $ipv6_prefer has been added. If NO, IPv6
656 functionality of interfaces with no corresponding
657 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
658 and the default address selection policy of ip6addrctl(8)
659 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
660 Note that if you want to configure IPv6 functionality on the
661 disabled interfaces after boot, first you need to clear the flag by
662 using ifconfig(8) like:
664 ifconfig em0 inet6 -ifdisabled
666 If YES, the default address selection policy is set as
669 The default value of $ipv6_prefer is NO.
671 4. If your system need to receive Router Advertisement messages,
672 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
673 scripts automatically invoke rtsol(8) when the interface becomes
674 UP. The Router Advertisement messages are used for SLAAC
675 (State-Less Address AutoConfiguration).
678 802.11s D3.03 support was committed. This is incompatible with the
679 previous code, which was based on D3.0.
682 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
683 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
684 control whether accepting Router Advertisement messages or not.
685 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
686 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
687 The ifconfig(8) utility now supports these flags.
690 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
691 mount(8) and -a option for df(1) to see them.
694 The old tunable hw.bus.devctl_disable has been superseded by
695 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
696 replaced by hw.bus.devctl_queue=0. The default for this new tunable
700 Remove the option STOP_NMI. The default action is now to use NMI only
701 for KDB via the newly introduced function stop_cpus_hard() and
702 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
705 The stable/8 branch created in subversion. This corresponds to the
706 RELENG_8 branch in CVS.
709 Bump the shared library version numbers for all libraries that do not
710 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
711 __FreeBSD_version to 800105.
714 Due to changes in the implementation of virtual network stack support,
715 all network-related kernel modules must be recompiled. As this change
716 breaks the ABI, bump __FreeBSD_version to 800104.
719 The TOE interface to the TCP syncache has been modified to remove
720 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
721 The cxgb driver is the only TOE consumer affected by this change, and
722 needs to be recompiled along with the kernel. As this change breaks
723 the ABI, bump __FreeBSD_version to 800103.
726 Padding has been added to struct tcpcb, sackhint and tcpstat in
727 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
728 maintaining the ABI. However, this change breaks the ABI, so bump
729 __FreeBSD_version to 800102. User space tools that rely on the size of
730 any of these structs (e.g. sockstat) need to be recompiled.
733 The NFS_LEGACYRPC option has been removed along with the old kernel
734 RPC implementation that this option selected. Kernel configurations
735 may need to be adjusted.
738 The network interface device nodes at /dev/net/<interface> have been
739 removed. All ioctl operations can be performed the normal way using
740 routing sockets. The kqueue functionality can generally be replaced
741 with routing sockets.
744 The documentation from the FreeBSD Documentation Project (Handbook,
745 FAQ, etc.) is now installed via packages by sysinstall(8) and under
746 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
749 The ABI of various structures related to the SYSV IPC API have been
750 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
751 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
755 Layout of struct vnet has changed as routing related variables were
756 moved to their own Vimage module. Modules need to be recompiled. Bump
757 __FreeBSD_version to 800099.
760 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
761 respectively. As long as no more than 16 groups per process are used,
762 no changes should be visible. When more than 16 groups are used, old
763 binaries may fail if they call getgroups() or getgrouplist() with
764 statically sized storage. Recompiling will work around this, but
765 applications should be modified to use dynamically allocated storage
766 for group arrays as POSIX.1-2008 does not cap an implementation's
767 number of supported groups at NGROUPS_MAX+1 as previous versions did.
769 NFS and portalfs mounts may also be affected as the list of groups is
770 truncated to 16. Users of NFS who use more than 16 groups, should
771 take care that negative group permissions are not used on the exported
772 file systems as they will not be reliable unless a GSSAPI based
773 authentication method is used.
776 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
777 option compiles in the support for adaptive spinning for lockmgrs
778 which want to enable it. The lockinit() function now accepts the flag
779 LK_ADAPTIVE in order to make the lock object subject to adaptive
780 spinning when both held in write and read mode.
783 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
784 changed. User applications that use this ioctl need to be rebuilt.
787 The layout of struct thread has changed. Kernel and modules need to
791 The layout of structs ifnet, domain, protosw and vnet_net has changed.
792 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
795 window(1) has been removed from the base system. It can now be
796 installed from ports. The port is called misc/window.
799 The way we are storing and accessing `routing table' entries has
800 changed. Programs reading the FIB, like netstat, need to be
804 A new netisr implementation has been added for FreeBSD 8. Network
805 file system modules, such as igmp, ipdivert, and others, should be
807 Bump __FreeBSD_version to 800096.
810 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
814 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
815 Bump __FreeBSD_version to 800094.
818 Add mnt_xflag field to 'struct mount'. File system modules need to be
820 Bump __FreeBSD_version to 800093.
823 The compiling option ADAPTIVE_SX has been retired while it has been
824 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
825 The KPI for sx_init_flags() changes as accepting flags:
826 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
827 been introduced in order to handle the reversed logic.
828 Bump __FreeBSD_version to 800092.
831 Add support for hierarchical jails. Remove global securelevel.
832 Bump __FreeBSD_version to 800091.
835 The layout of struct vnet_net has changed, therefore modules
837 Bump __FreeBSD_version to 800090.
840 The newly imported zic(8) produces a new format in the output. Please
841 run tzsetup(8) to install the newly created data to /etc/localtime.
844 The sysctl tree for the usb stack has renamed from hw.usb2.* to
845 hw.usb.* and is now consistent again with previous releases.
848 802.11 monitor mode support was revised and driver api's were changed.
849 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
850 of DLT_IEEE802_11. No user-visible data structures were changed but
851 applications that use DLT_IEEE802_11 may require changes.
852 Bump __FreeBSD_version to 800088.
855 The layout of the following structs has changed: sysctl_oid,
856 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
857 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
858 panics may be experienced. World rebuild is required for
859 correctly checking networking state from userland.
860 Bump __FreeBSD_version to 800085.
863 MLDv2 and Source-Specific Multicast (SSM) have been merged
864 to the IPv6 stack. VIMAGE hooks are in but not yet used.
865 The implementation of SSM within FreeBSD's IPv6 stack closely
866 follows the IPv4 implementation.
868 For kernel developers:
870 * The most important changes are that the ip6_output() and
871 ip6_input() paths no longer take the IN6_MULTI_LOCK,
872 and this lock has been downgraded to a non-recursive mutex.
874 * As with the changes to the IPv4 stack to support SSM, filtering
875 of inbound multicast traffic must now be performed by transport
876 protocols within the IPv6 stack. This does not apply to TCP and
877 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
879 * The KPIs used by IPv6 multicast are similar to those used by
880 the IPv4 stack, with the following differences:
881 * im6o_mc_filter() is analogous to imo_multicast_filter().
882 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
883 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
884 * IN6_LOOKUP_MULTI() has been deprecated and removed.
885 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
886 for MLDv1 have an additional 'timer' argument which is used to
887 jitter the initial membership report for the solicited-node
888 multicast membership on-link.
889 * This is not strictly needed for MLDv2, which already jitters
890 its report transmissions. However, the 'timer' argument is
891 preserved in case MLDv1 is active on the interface.
893 * The KAME linked-list based IPv6 membership implementation has
894 been refactored to use a vector similar to that used by the IPv4
896 Code which maintains a list of its own multicast memberships
897 internally, e.g. carp, has been updated to reflect the new
900 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
901 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
902 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
903 implementation constraint which needs to be addressed in HEAD.
905 For application developers:
907 * The changes are broadly similar to those made for the IPv4
910 * The use of IPv4 and IPv6 multicast socket options on the same
911 socket, using mapped addresses, HAS NOT been tested or supported.
913 * There are a number of issues with the implementation of various
914 IPv6 multicast APIs which need to be resolved in the API surface
915 before the implementation is fully compatible with KAME userland
916 use, and these are mostly to do with interface index treatment.
918 * The literature available discusses the use of either the delta / ASM
919 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
920 using setsourcefilter(3)/getsourcefilter(3). For more information
921 please refer to RFC 3768, 'Socket Interface Extensions for
922 Multicast Source Filters'.
924 * Applications which use the published RFC 3678 APIs should be fine.
926 For systems administrators:
928 * The mtest(8) utility has been refactored to support IPv6, in
929 addition to IPv4. Interface addresses are no longer accepted
930 as arguments, their names must be used instead. The utility
931 will map the interface name to its first IPv4 address as
932 returned by getifaddrs(3).
934 * The ifmcstat(8) utility has also been updated to print the MLDv2
935 endpoint state and source filter lists via sysctl(3).
937 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
938 loopback of IPv6 multicast datagrams by default; it defaults to 1
939 to preserve the existing behaviour. Disabling multicast loopback is
940 recommended for optimal system performance.
942 * The IPv6 MROUTING code has been changed to examine this sysctl
943 instead of attempting to perform a group lookup before looping
944 back forwarded datagrams.
946 Bump __FreeBSD_version to 800084.
949 Implement low-level Bluetooth HCI API.
950 Bump __FreeBSD_version to 800083.
953 The layout of struct malloc_type, used by modules to register new
954 memory allocation types, has changed. Most modules will need to
955 be rebuilt or panics may be experienced.
956 Bump __FreeBSD_version to 800081.
959 Anticipate overflowing inp_flags - add inp_flags2.
960 This changes most offsets in inpcb, so checking v4 connection
961 state will require a world rebuild.
962 Bump __FreeBSD_version to 800080.
965 Add an llentry to struct route and struct route_in6. Modules
966 embedding a struct route will need to be recompiled.
967 Bump __FreeBSD_version to 800079.
970 The size of rt_metrics_lite and by extension rtentry has changed.
971 Networking administration apps will need to be recompiled.
972 The route command now supports show as an alias for get, weighting
973 of routes, sticky and nostick flags to alter the behavior of stateful
975 Bump __FreeBSD_version to 800078.
978 Do not use Giant for kbdmux(4) locking. This is wrong and
979 apparently causing more problems than it solves. This will
980 re-open the issue where interrupt handlers may race with
981 kbdmux(4) in polling mode. Typical symptoms include (but
982 not limited to) duplicated and/or missing characters when
983 low level console functions (such as gets) are used while
984 interrupts are enabled (for example geli password prompt,
985 mountroot prompt etc.). Disabling kbdmux(4) may help.
988 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
989 kernel modules referencing any of the above need to be recompiled.
990 Bump __FreeBSD_version to 800075.
993 GEOM_PART has become the default partition slicer for storage devices,
994 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
995 introduces some changes:
997 MSDOS/EBR: the devices created from MSDOS extended partition entries
998 (EBR) can be named differently than with GEOM_MBR and are now symlinks
999 to devices with offset-based names. fstabs may need to be modified.
1001 BSD: the "geometry does not match label" warning is harmless in most
1002 cases but it points to problems in file system misalignment with
1003 disk geometry. The "c" partition is now implicit, covers the whole
1004 top-level drive and cannot be (mis)used by users.
1006 General: Kernel dumps are now not allowed to be written to devices
1007 whose partition types indicate they are meant to be used for file
1008 systems (or, in case of MSDOS partitions, as something else than
1011 Most of these changes date approximately from 200812.
1014 The uscanner(4) driver has been removed from the kernel. This follows
1015 Linux removing theirs in 2.6 and making libusb the default interface
1016 (supported by sane).
1019 The multicast forwarding code has been cleaned up. netstat(1)
1020 only relies on KVM now for printing bandwidth upcall meters.
1021 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1022 ip6_mroute_mod respectively. The config(5) options for statically
1023 compiling this code remain the same, i.e. 'options MROUTING'.
1026 Support for the IFF_NEEDSGIANT network interface flag has been
1027 removed, which means that non-MPSAFE network device drivers are no
1028 longer supported. In particular, if_ar, if_sr, and network device
1029 drivers from the old (legacy) USB stack can no longer be built or
1033 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1034 a bunch of new language catalog files have also been added.
1035 This means that some common libc messages are now localized and
1036 they depend on the LC_MESSAGES environmental variable.
1039 The k8temp(4) driver has been renamed to amdtemp(4) since
1040 support for Family 10 and Family 11 CPU families was added.
1043 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1044 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1046 For kernel developers, the most important changes are that the
1047 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1048 and this lock has been downgraded to a non-recursive mutex.
1050 Transport protocols (UDP, Raw IP) are now responsible for filtering
1051 inbound multicast traffic according to group membership and source
1052 filters. The imo_multicast_filter() KPI exists for this purpose.
1053 Transports which do not use multicast (SCTP, TCP) already reject
1054 multicast by default. Forwarding and receive performance may improve
1055 as a mutex acquisition is no longer needed in the ip_input()
1056 low-level input path. in_addmulti() and in_delmulti() are shimmed
1057 to new KPIs which exist to support SSM in-kernel.
1059 For application developers, it is recommended that loopback of
1060 multicast datagrams be disabled for best performance, as this
1061 will still cause the lock to be taken for each looped-back
1062 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1063 be tuned to 0 to disable loopback by default; it defaults to 1
1064 to preserve the existing behaviour.
1066 For systems administrators, to obtain best performance with
1067 multicast reception and multiple groups, it is always recommended
1068 that a card with a suitably precise hash filter is used. Hash
1069 collisions will still result in the lock being taken within the
1070 transport protocol input path to check group membership.
1072 If deploying FreeBSD in an environment with IGMP snooping switches,
1073 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1074 enabled; this forces 224.0.0.0/24 group membership to be announced
1077 The size of 'struct igmpstat' has changed; netstat needs to be
1078 recompiled to reflect this.
1079 Bump __FreeBSD_version to 800070.
1082 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1083 updated to use it. This requires a buildworld/installworld in order to
1084 update the library and dependencies (usbconfig, etc). Its advisable to
1085 rebuild all ports which uses libusb. More specific directions are given
1086 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1087 libusb are no longer required and can be removed.
1090 A workaround is committed to allow the creation of System V shared
1091 memory segment of size > 2 GB on the 64-bit architectures.
1092 Due to a limitation of the existing ABI, the shm_segsz member
1093 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1094 wrong for large segments. Note that limits must be explicitly
1095 raised to allow such segments to be created.
1098 The layout of struct ifnet has changed, requiring a rebuild of all
1099 network device driver modules.
1102 The /dev handling for the new USB stack has changed, a
1103 buildworld/installworld is required for libusb20.
1106 The new USB2 stack has now been permanently moved in and all kernel and
1107 module names reverted to their previous values (eg, usb, ehci, ohci,
1108 ums, ...). The old usb stack can be compiled in by prefixing the name
1109 with the letter 'o', the old usb modules have been removed.
1110 Updating entry 20090216 for xorg and 20090215 for libmap may still
1114 The rc.conf(5) option if_up_delay has been renamed to
1115 defaultroute_delay to better reflect its purpose. If you have
1116 customized this setting in /etc/rc.conf you need to update it to
1120 xorg 7.4 wants to configure its input devices via hald which does not
1121 yet work with USB2. If the keyboard/mouse does not work in xorg then
1123 Option "AllowEmptyInput" "off"
1124 to your ServerLayout section. This will cause X to use the configured
1125 kbd and mouse sections from your xorg.conf.
1128 The GENERIC kernels for all architectures now default to the new USB2
1129 stack. No kernel config options or code have been removed so if a
1130 problem arises please report it and optionally revert to the old USB
1131 stack. If you are loading USB kernel modules or have a custom kernel
1132 that includes GENERIC then ensure that usb names are also changed over,
1133 eg uftdi -> usb2_serial_ftdi.
1135 Older programs linked against the ports libusb 0.1 need to be
1136 redirected to the new stack's libusb20. /etc/libmap.conf can
1138 # Map old usb library to new one for usb2 stack
1139 libusb-0.1.so.8 libusb20.so.1
1142 All USB ethernet devices now attach as interfaces under the name ueN
1143 (eg. ue0). This is to provide a predictable name as vendors often
1144 change usb chipsets in a product without notice.
1147 The ichsmb(4) driver has been changed to require SMBus slave
1148 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1149 All of the other SMBus controller drivers require left-justified
1150 slave addresses, so this change makes all the drivers provide the
1154 INET6 statistics (struct ip6stat) was updated.
1155 netstat(1) needs to be recompiled.
1158 NTFS has been removed from GENERIC kernel on amd64 to match
1159 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1160 will load ntfs.ko module automatically when NTFS support is
1161 actually needed, unless ntfs.ko is not installed or security
1162 level prohibits loading kernel modules. If either is the case,
1163 "options NTFS" has to be added into kernel config.
1166 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1167 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1168 800061. User space tools that rely on the size of struct tcpcb in
1169 tcp_var.h (e.g. sockstat) need to be recompiled.
1172 ng_tty(4) module updated to match the new TTY subsystem.
1173 Due to API change, user-level applications must be updated.
1174 New API support added to mpd5 CVS and expected to be present
1175 in next mpd5.3 release.
1178 With __FreeBSD_version 800060 the makefs tool is part of
1179 the base system (it was a port).
1182 The afdata and ifnet locks have been changed from mutexes to
1183 rwlocks, network modules will need to be re-compiled.
1186 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1187 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1188 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1189 architecture and 40 bytes on 64-bit architecture. The userland
1190 applications "arp" and "ndp" have been updated accordingly.
1191 The output from "netstat -r" shows only routing entries and
1192 none of the L2 information.
1195 __FreeBSD_version 800057 marks the switchover from the
1196 binary ath hal to source code. Users must add the line:
1198 options AH_SUPPORT_AR5416
1200 to their kernel config files when specifying:
1204 The ath_hal module no longer exists; the code is now compiled
1205 together with the driver in the ath module. It is now
1206 possible to tailor chip support (i.e. reduce the set of chips
1207 and thereby the code size); consult ath_hal(4) for details.
1210 __FreeBSD_version 800054 adds memory barriers to
1211 <machine/atomic.h>, new interfaces to ifnet to facilitate
1212 multiple hardware transmit queues for cards that support
1213 them, and a lock-less ring-buffer implementation to
1214 enable drivers to more efficiently manage queueing of
1218 A new version of ZFS (version 13) has been merged to -HEAD.
1219 This version has zpool attribute "listsnapshots" off by
1220 default, which means "zfs list" does not show snapshots,
1221 and is the same as Solaris behavior.
1224 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1227 The uhci, ohci, ehci and slhci USB Host controller drivers have
1228 been put into separate modules. If you load the usb module
1229 separately through loader.conf you will need to load the
1230 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1231 controller add the following to loader.conf:
1237 The ABI used by the PMC toolset has changed. Please keep
1238 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1242 atapci kernel module now includes only generic PCI ATA
1243 driver. AHCI driver moved to ataahci kernel module.
1244 All vendor-specific code moved into separate kernel modules:
1245 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1246 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1247 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1248 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1251 The TTY subsystem of the kernel has been replaced by a new
1252 implementation, which provides better scalability and an
1253 improved driver model. Most common drivers have been migrated to
1254 the new TTY subsystem, while others have not. The following
1255 drivers have not yet been ported to the new TTY layer:
1258 cy, digi, rc, rp, sio
1264 ng_h4, ng_tty, ppp, sl, snp
1266 Adding these drivers to your kernel configuration file shall
1267 cause compilation to fail.
1270 ntpd has been upgraded to 4.2.4p5.
1273 OpenSSH has been upgraded to 5.1p1.
1275 For many years, FreeBSD's version of OpenSSH preferred DSA
1276 over RSA for host and user authentication keys. With this
1277 upgrade, we've switched to the vendor's default of RSA over
1278 DSA. This may cause upgraded clients to warn about unknown
1279 host keys even for previously known hosts. Users should
1280 follow the usual procedure for verifying host keys before
1281 accepting the RSA key.
1283 This can be circumvented by setting the "HostKeyAlgorithms"
1284 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1287 Please note that the sequence of keys offered for
1288 authentication has been changed as well. You may want to
1289 specify IdentityFile in a different order to revert this
1293 The sio(4) driver has been removed from the i386 and amd64
1294 kernel configuration files. This means uart(4) is now the
1295 default serial port driver on those platforms as well.
1297 To prevent collisions with the sio(4) driver, the uart(4) driver
1298 uses different names for its device nodes. This means the
1299 onboard serial port will now most likely be called "ttyu0"
1300 instead of "ttyd0". You may need to reconfigure applications to
1301 use the new device names.
1303 When using the serial port as a boot console, be sure to update
1304 /boot/device.hints and /etc/ttys before booting the new kernel.
1305 If you forget to do so, you can still manually specify the hints
1306 at the loader prompt:
1308 set hint.uart.0.at="isa"
1309 set hint.uart.0.port="0x3F8"
1310 set hint.uart.0.flags="0x10"
1311 set hint.uart.0.irq="4"
1315 The gpt(8) utility has been removed. Use gpart(8) to partition
1319 The version that Linuxulator emulates was changed from 2.4.2
1320 to 2.6.16. If you experience any problems with Linux binaries
1321 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1322 if it fixes the problem contact emulation mailing list.
1325 ISDN4BSD (I4B) was removed from the src tree. You may need to
1326 update a your kernel configuration and remove relevant entries.
1329 I have checked in code to support multiple routing tables.
1330 See the man pages setfib(1) and setfib(2).
1331 This is a hopefully backwards compatible version,
1332 but to make use of it you need to compile your kernel
1333 with options ROUTETABLES=2 (or more up to 16).
1336 The 802.11 wireless support was redone to enable multi-bss
1337 operation on devices that are capable. The underlying device
1338 is no longer used directly but instead wlanX devices are
1339 cloned with ifconfig. This requires changes to rc.conf files.
1340 For example, change:
1341 ifconfig_ath0="WPA DHCP"
1344 ifconfig_wlan0="WPA DHCP"
1345 see rc.conf(5) for more details. In addition, mergemaster of
1346 /etc/rc.d is highly recommended. Simultaneous update of userland
1347 and kernel wouldn't hurt either.
1349 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1350 modules were merged into the base wlan module. All references
1351 to these modules (e.g. in kernel config files) must be removed.
1354 psm(4) has gained write(2) support in native operation level.
1355 Arbitrary commands can be written to /dev/psm%d and status can
1356 be read back from it. Therefore, an application is responsible
1357 for status validation and error recovery. It is a no-op in
1358 other operation levels.
1361 Support for KSE threading has been removed from the kernel. To
1362 run legacy applications linked against KSE libmap.conf may
1363 be used. The following libmap.conf may be used to ensure
1364 compatibility with any prior release:
1366 libpthread.so.1 libthr.so.1
1367 libpthread.so.2 libthr.so.2
1368 libkse.so.3 libthr.so.3
1371 The layout of struct vmspace has changed. This affects libkvm
1372 and any executables that link against libkvm and use the
1373 kvm_getprocs() function. In particular, but not exclusively,
1374 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1375 The effects are minimal, but it's advisable to upgrade world
1379 The latest em driver no longer has support in it for the
1380 82575 adapter, this is now moved to the igb driver. The
1381 split was done to make new features that are incompatible
1382 with older hardware easier to do.
1385 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1386 likewise the kernel option is now GEOM_LINUX_LVM.
1389 The default NFS mount mode has changed from UDP to TCP for
1390 increased reliability. If you rely on (insecurely) NFS
1391 mounting across a firewall you may need to update your
1395 Belatedly note the addition of m_collapse for compacting
1399 The fts(3) structures have been changed to use adequate
1400 integer types for their members and so to be able to cope
1401 with huge file trees. The old fts(3) ABI is preserved
1402 through symbol versioning in libc, so third-party binaries
1403 using fts(3) should still work, although they will not take
1404 advantage of the extended types. At the same time, some
1405 third-party software might fail to build after this change
1406 due to unportable assumptions made in its source code about
1407 fts(3) structure members. Such software should be fixed
1408 by its vendor or, in the worst case, in the ports tree.
1409 FreeBSD_version 800015 marks this change for the unlikely
1410 case that a portable fix is impossible.
1413 To upgrade to -current after this date, you must be running
1414 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1415 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1418 The ADAPTIVE_GIANT kernel option has been retired because its
1419 functionality is the default now.
1422 The AT keyboard emulation of sunkbd(4) has been turned on
1423 by default. In order to make the special symbols of the Sun
1424 keyboards driven by sunkbd(4) work under X these now have
1425 to be configured the same way as Sun USB keyboards driven
1426 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1428 Option "XkbLayout" "us"
1429 Option "XkbRules" "xorg"
1430 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1433 It has been decided that it is desirable to provide ABI
1434 backwards compatibility to the FreeBSD 4/5/6 versions of the
1435 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1436 broken with the introduction of PCI domain support (see the
1437 20070930 entry). Unfortunately, this required the ABI of
1438 PCIOCGETCONF to be broken again in order to be able to
1439 provide backwards compatibility to the old version of that
1440 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1441 again. As for prominent ports this affects neither pciutils
1442 nor xorg-server this time, the hal port needs to be rebuilt
1446 The misnamed kthread_create() and friends have been renamed
1447 to kproc_create() etc. Many of the callers already
1448 used kproc_start()..
1449 I will return kthread_create() and friends in a while
1450 with implementations that actually create threads, not procs.
1451 Renaming corresponds with version 800002.
1460 Avoid using make -j when upgrading. While generally safe, there are
1461 sometimes problems using -j to upgrade. If your upgrade fails with
1462 -j, please try again without -j. From time to time in the past there
1463 have been problems using -j with buildworld and/or installworld. This
1464 is especially true when upgrading between "distant" versions (eg one
1465 that cross a major release boundary or several minor releases, or when
1466 several months have passed on the -current branch).
1468 Sometimes, obscure build problems are the result of environment
1469 poisoning. This can happen because the make utility reads its
1470 environment when searching for values for global variables. To run
1471 your build attempts in an "environmental clean room", prefix all make
1472 commands with 'env -i '. See the env(1) manual page for more details.
1474 When upgrading from one major version to another it is generally best
1475 to upgrade to the latest code in the currently installed branch first,
1476 then do an upgrade to the new branch. This is the best-tested upgrade
1477 path, and has the highest probability of being successful. Please try
1478 this approach before reporting problems with a major version upgrade.
1482 When upgrading the boot ZFS pool to a new version, always follow
1485 1.) recompile and reinstall the ZFS boot loader and boot block
1486 (this is part of "make buildworld" and "make installworld")
1488 2.) update the ZFS boot block on your boot drive
1490 The following example updates the ZFS boot block on the first
1491 partition (freebsd-boot) of a GPT partitioned drive ad0:
1492 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1494 Non-boot pools do not need these updates.
1498 If you are updating from a prior version of FreeBSD (even one just
1499 a few days old), you should follow this procedure. It is the most
1500 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1502 make kernel-toolchain
1503 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1504 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1506 To test a kernel once
1507 ---------------------
1508 If you just want to boot a kernel once (because you are not sure
1509 if it works, or if you want to boot a known bad kernel to provide
1510 debugging information) run
1511 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1512 nextboot -k testkernel
1514 To just build a kernel when you know that it won't mess you up
1515 --------------------------------------------------------------
1516 This assumes you are already running a CURRENT system. Replace
1517 ${arch} with the architecture of your machine (e.g. "i386",
1518 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1520 cd src/sys/${arch}/conf
1521 config KERNEL_NAME_HERE
1522 cd ../compile/KERNEL_NAME_HERE
1527 If this fails, go to the "To build a kernel" section.
1529 To rebuild everything and install it on the current system.
1530 -----------------------------------------------------------
1531 # Note: sometimes if you are running current you gotta do more than
1532 # is listed here if you are upgrading from a really old current.
1534 <make sure you have good level 0 dumps>
1536 make kernel KERNCONF=YOUR_KERNEL_HERE
1538 <reboot in single user> [3]
1546 To cross-install current onto a separate partition
1547 --------------------------------------------------
1548 # In this approach we use a separate partition to hold
1549 # current's root, 'usr', and 'var' directories. A partition
1550 # holding "/", "/usr" and "/var" should be about 2GB in
1553 <make sure you have good level 0 dumps>
1556 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1557 <maybe newfs current's root partition>
1558 <mount current's root partition on directory ${CURRENT_ROOT}>
1559 make installworld DESTDIR=${CURRENT_ROOT}
1560 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1561 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1562 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1563 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1564 <reboot into current>
1565 <do a "native" rebuild/install as described in the previous section>
1566 <maybe install compatibility libraries from ports/misc/compat*>
1570 To upgrade in-place from stable to current
1571 ----------------------------------------------
1572 <make sure you have good level 0 dumps>
1574 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1576 <reboot in single user> [3]
1583 Make sure that you've read the UPDATING file to understand the
1584 tweaks to various things you need. At this point in the life
1585 cycle of current, things change often and you are on your own
1586 to cope. The defaults can also change, so please read ALL of
1587 the UPDATING entries.
1589 Also, if you are tracking -current, you must be subscribed to
1590 freebsd-current@freebsd.org. Make sure that before you update
1591 your sources that you have read and understood all the recent
1592 messages there. If in doubt, please track -stable which has
1593 much fewer pitfalls.
1595 [1] If you have third party modules, such as vmware, you
1596 should disable them at this point so they don't crash your
1599 [3] From the bootblocks, boot -s, and then do
1604 adjkerntz -i # if CMOS is wall time
1605 Also, when doing a major release upgrade, it is required that
1606 you boot into single user mode to do the installworld.
1608 [4] Note: This step is non-optional. Failure to do this step
1609 can result in a significant reduction in the functionality of the
1610 system. Attempting to do it by hand is not recommended and those
1611 that pursue this avenue should read this file carefully, as well
1612 as the archives of freebsd-current and freebsd-hackers mailing lists
1613 for potential gotchas. The -U option is also useful to consider.
1614 See mergemaster(8) for more information.
1616 [5] Usually this step is a noop. However, from time to time
1617 you may need to do this if you get unknown user in the following
1618 step. It never hurts to do it all the time. You may need to
1619 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1620 install) after the buildworld before this step if you last updated
1621 from [78]-stable or 9-stable before 20130430.
1623 [6] This only deletes old files and directories. Old libraries
1624 can be deleted by "make delete-old-libs", but you have to make
1625 sure that no program is using those libraries anymore.
1627 [8] In order to have a kernel that can run the 4.x binaries needed to
1628 do an installworld, you must include the COMPAT_FREEBSD4 option in
1629 your kernel. Failure to do so may leave you with a system that is
1630 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1631 required to run the 5.x binaries on more recent kernels. And so on
1632 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1634 Make sure that you merge any new devices from GENERIC since the
1635 last time you updated your kernel config file.
1637 [9] When checking out sources, you must include the -P flag to have
1638 cvs prune empty directories.
1640 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1641 "?=" instead of the "=" assignment operator, so that buildworld can
1642 override the CPUTYPE if it needs to.
1644 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1645 not on the command line, or in /etc/make.conf. buildworld will
1646 warn if it is improperly defined.
1649 This file contains a list, in reverse chronological order, of major
1650 breakages in tracking -current. It is not guaranteed to be a complete
1651 list of such breakages, and only contains entries since October 10, 2007.
1652 If you need to see UPDATING entries from before that date, you will need
1653 to fetch an UPDATING file from an older FreeBSD release.
1655 Copyright information:
1657 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1659 Redistribution, publication, translation and use, with or without
1660 modification, in full or in part, in any form or format of this
1661 document are permitted without further permission from the author.
1663 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1664 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1665 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1666 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1667 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1668 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1669 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1670 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1671 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1672 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1673 POSSIBILITY OF SUCH DAMAGE.
1675 Contact Warner Losh if you have any questions about your use of