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 20140909: p11 FreeBSD-SA-14:18.openssl
15 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
17 20140708: p10 FreeBSD-SA-14:17.kmem
18 Fix kernel memory disclosure in control messages and SCTP
19 notifications. [SA-14:17]
21 20140624: p9 FreeBSD-SA-14:16.file
22 FreeBSD-EN-14:08.heimdal
24 Fix multiple vulnerabilities in file(1) and libmagic(3).
27 Fix gss_pseudo_random interoperability issue. [EN-14:08]
29 20140605: p8 FreeBSD-SA-14:14.openssl
30 Fix OpenSSL multiple vulnerabilities. [SA-14:14]
32 20140603: p7 FreeBSD-SA-14:11.sendmail
33 FreeBSD-SA-14:12.ktrace
37 Fix sendmail improper close-on-exec flag handling. [SA-14:11]
39 Fix ktrace memory disclosure. [SA-14:12]
41 Fix incorrect error handling in PAM policy parser. [SA-14:13]
43 Fix triple-fault when executing from a threaded process.
46 20140513: p6 FreeBSD-EN-14:03.pkg
47 FreeBSD-EN-14:04.kldxref
50 Add pkg bootstrapping, configuration and public keys. [EN-14:03]
52 Improve build repeatability for kldxref(8). [EN-14:04]
54 Fix data corruption with ciss(4). [EN-14:05]
56 20140430: p5 FreeBSD-SA-14:08.tcp
58 Fix TCP reassembly vulnerability. [SA-14:08]
60 20140408: p4 FreeBSD-SA-14:05.nfsserver
61 FreeBSD-SA-14:06.openssl
62 Fix deadlock in the NFS server. [SA-14:05]
64 Fix for ECDSA Cache Side-channel Attack in OpenSSL. [SA-14:06]
66 20140114: p3 FreeBSD-SA-14:01.bsnmpd
69 FreeBSD-EN-14:01.random
71 Fix bsnmpd remote denial of service vulnerability. [SA-14:01]
73 Fix ntpd distributed reflection Denial of Service
74 vulnerability. [SA-14:02]
76 Fix BIND remote denial of service vulnerability. [SA-14:04]
78 Disable hardware RNGs by default. [EN-14:01]
80 Fix incorrect coalescing of stack entry with mmap. [EN-14:02]
82 20131128: p2 FreeBSD-EN-13:05.freebsd-update
83 Fix error in patch for FreeBSD-EN-13:04.freebsd-update.
85 20131026: p1 FreeBSD-EN-13:04.freebsd-update
86 Fix multiple freebsd-update bugs that break upgrading to
90 hastctl(8)'s `status' command output changed to terse one-liner format.
91 Scripts using this should switch to `list' command or be rewritten.
94 Fix a bug that allowed a tracing process (e.g. gdb) to write
95 to a memory-mapped file in the traced process's address space
96 even if neither the traced process nor the tracing process had
97 write access to that file.
100 Added ZFS TRIM support which is enabled by default. To disable
101 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
103 Creating new ZFS pools and adding new devices to existing pools
104 first performs a full device level TRIM which can take a significant
105 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
106 to disable this behaviour.
108 ZFS TRIM requires the underlying device support BIO_DELETE which
109 is currently provided by methods such as ATA TRIM and SCSI UNMAP
110 via CAM, which are typically supported by SSD's.
112 Stats for ZFS TRIM can be monitored by looking at the sysctl's
113 under kstat.zfs.misc.zio_trim.
116 `list' command has been added to hastctl(8). For now, it is full
117 equivalent of `status' command.
118 WARNING: in the near future the output of hastctl's status command
119 will change to more terse format. If you use `hastctl status'
120 for parsing in your scripts, switch to `hastctl list'.
123 The mergemaster command now uses the default MAKEOBJDIRPREFIX
124 rather than creating it's own in the temporary directory in
125 order allow access to bootstrapped versions of tools such as
126 install and mtree. When upgrading from version of FreeBSD where
127 the install command does not support -l, you will need to
128 install a new mergemaster command if mergemaster -p is required.
129 This can be accomplished with the command (cd src/usr.sbin/mergemaster
132 Due to the use of the new -l option to install(1) during build
133 and install, you must take care not to directly set the INSTALL
134 make variable in your /etc/make.conf, /etc/src.conf, or on the
135 command line. If you wish to use the -C flag for all installs
136 you may be able to add INSTALL+=-C to /etc/make.conf or
140 Fix a bug that allows NFS clients to issue READDIR on files.
143 The install(1) option -M has changed meaning and now takes an
144 argument that is a file or path to append logs to. In the
145 unlikely event that -M was the last option on the command line
146 and the command line contained at least two files and a target
147 directory the first file will have logs appended to it. The -M
148 option served little practical purpose in the last decade so it's
149 used expected to be extremely rare.
152 A new compression method (lz4) has been merged to. Please refer to
153 zpool-features(7) for more information.
155 Please refer to the "ZFS notes" section of this file for information
156 on upgrading boot ZFS pools.
159 The VFS KBI was changed with the merge of several nullfs
160 optimizations and fixes. All filesystem modules must be
164 With the addition of auditdistd(8), a new auditdistd user is now
165 depended on during installworld. "mergemaster -p" can be used to add
166 the user prior to installworld, as documented in the handbook.
172 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
173 Starting with this version the old system of ZFS pool versioning
174 is superseded by "feature flags". This concept enables forward
175 compatibility against certain future changes in functionality of ZFS
176 pools. The first two read-only compatible "feature flags" for ZFS
177 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
178 For more information read the new zpool-features(7) manual page.
179 Please refer to the "ZFS notes" section of this file for information
180 on upgrading boot ZFS pools.
183 The commit introducing bsd.compiler.mk breaks the traditional
184 building of kernels before this point. Add -m ${SRC}/share/mk
185 (for the right value of SRC) to your command lines to work
186 around; update your useland to a point after this; or use the
187 buildkernel/installkernel top-level targets. See also 20120829.
190 The IPFIREWALL_FORWARD kernel option has been removed. Its
191 functionality now turned on by default.
194 The random(4) support for the VIA hardware random number
195 generator (`PADLOCK') is no longer enabled unconditionally.
196 Add the PADLOCK_RNG option in the custom kernel config if
197 needed. The GENERIC kernels on i386 and amd64 do include the
198 option, so the change only affects the custom kernel
202 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
203 the traditional method, you must update your system with an installworld
204 before the kernel will build. The documented make buildkernel/installkernel
205 interfaces (coupled with fresh make kernel-toolchain) continue to work.
208 The sparc64 ZFS loader has been changed to no longer try to auto-
209 detect ZFS providers based on diskN aliases but now requires these
210 to be explicitly listed in the OFW boot-device environment variable.
213 Now unix domain sockets behave "as expected" on nullfs(5). Previously
214 nullfs(5) did not pass through all behaviours to the underlying layer,
215 as a result if we bound to a socket on the lower layer we could connect
216 only to the lower path; if we bound to the upper layer we could connect
217 only to the upper path. The new behavior is one can connect to both the
218 lower and the upper paths regardless what layer path one binds to.
221 The acpi_wmi(4) status device /dev/wmistat has been renamed to
225 A new VOP_ADVISE() was added to support posix_fadvise(2). All
226 filesystem modules must be recompiled.
229 The interface of the VOP_VPTOCNP(9) changed, now the returned
230 vnode shall be referenced, previously it was required to be
231 only held. All in-tree filesystems are converted.
237 The broken amd(4) driver has been replaced with esp(4) in the amd64,
238 i386 and pc98 GENERIC kernel configuration files.
241 This commit modifies vfs_register() so that it uses a hash
242 calculation to set vfc_typenum, which is enabled by default.
243 The first time a system is booted after this change, the
244 vfc_typenum values will change for all file systems. The
245 main effect of this is a change to the NFS server file handles
246 for file systems that use vfc_typenum in their fsid, such as ZFS.
247 It will, however, prevent vfc_typenum from changing when file
248 systems are loaded in a different order for subsequent reboots.
249 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
250 until you are ready to remount all NFS clients after a reboot.
253 Bump the shared library version numbers for libraries that
254 do not use symbol versioning, have changed the ABI compared
255 to stable/8 and which shared library version was not bumped.
256 Done as part of 9.0-RELEASE cycle.
259 During the merge of Capsicum features, the fget(9) KPI was modified.
260 This may require the rebuilding of out-of-tree device drivers --
261 issues have been reported specifically with the nVidia device driver.
262 __FreeBSD_version is bumped to 900041.
264 Also, there is a period between 20110811 and 20110814 where the
265 special devices /dev/{stdin,stdout,stderr} did not work correctly.
266 Building world from a kernel during that window may not work.
269 The packet filter (pf) code has been updated to OpenBSD 4.5.
270 You need to update userland tools to be in sync with kernel.
271 This update breaks backward compatibility with earlier pfsync(4)
272 versions. Care must be taken when updating redundant firewall setups.
275 The following sysctls and tunables are retired on x86 platforms:
277 machdep.hlt_logical_cpus
278 The following sysctl is retired:
279 machdep.hyperthreading_allowed
280 The sysctls were supposed to provide a way to dynamically offline and
281 online selected CPUs on x86 platforms, but the implementation has not
282 been reliable especially with SCHED_ULE scheduler.
283 machdep.hyperthreading_allowed tunable is still available to ignore
284 hyperthreading CPUs at OS level.
285 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
286 where X is an APIC ID of a CPU. Be advised, though, that disabling
287 CPUs in non-uniform fashion will result in non-uniform topology and
288 may lead to sub-optimal system performance with SCHED_ULE, which is
292 cpumask_t type is retired and cpuset_t is used in order to describe
296 Changes to ifconfig(8) for dynamic address family detection mandate
297 that you are running a kernel of 20110525 or later. Make sure to
298 follow the update procedure to boot a new kernel before installing
302 Support for sun4v architecture is officially dropped
305 Several KPI breaking changes have been committed to the mii(4) layer,
306 the PHY drivers and consequently some Ethernet drivers using mii(4).
307 This means that miibus.ko and the modules of the affected Ethernet
308 drivers need to be recompiled.
310 Note to kernel developers: Given that the OUI bit reversion problem
311 was fixed as part of these changes all mii(4) commits related to OUIs,
312 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
313 handling, no longer can be merged verbatim to stable/8 and previous
317 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
318 into their kernel configurations along with 'device pci'.
321 The default NFS client is now the new NFS client, so fstype "newnfs"
322 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
323 Although mounts via fstype "nfs" will usually work without userland
324 changes, it is recommended that the mount(8) and mount_nfs(8)
325 commands be rebuilt from sources and that a link to mount_nfs called
326 mount_oldnfs be created. The new client is compiled into the
327 kernel with "options NFSCL" and this is needed for diskless root
328 file systems. The GENERIC kernel configs have been changed to use
329 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
330 To use the regular/old client, you can "mount -t oldnfs ...". For
331 a diskless root file system, you must also include a line like:
333 vfs.root.mountfrom="oldnfs:"
335 in the boot/loader.conf on the root fs on the NFS server to make
336 a diskless root fs use the old client.
339 The GENERIC kernels for all architectures now default to the new
340 CAM-based ATA stack. It means that all legacy ATA drivers were
341 removed and replaced by respective CAM drivers. If you are using
342 ATA device names in /etc/fstab or other places, make sure to update
343 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
344 where 'Y's are the sequential numbers starting from zero for each type
345 in order of detection, unless configured otherwise with tunables,
346 see cam(4)). There will be symbolic links created in /dev/ to map
347 old adX devices to the respective adaY. They should provide basic
348 compatibility for file systems mounting in most cases, but they do
349 not support old user-level APIs and do not have respective providers
350 in GEOM. Consider using updated management tools with new device names.
352 It is possible to load devices ahci, ata, siis and mvs as modules,
353 but option ATA_CAM should remain in kernel configuration to make ata
354 module work as CAM driver supporting legacy ATA controllers. Device ata
355 still can be used in modular fashion (atacore + ...). Modules atadisk
356 and atapi* are not used and won't affect operation in ATA_CAM mode.
357 Note that to use CAM-based ATA kernel should include CAM devices
358 scbus, pass, da (or explicitly ada), cd and optionally others. All of
359 them are parts of the cam module.
361 ataraid(4) functionality is now supported by the RAID GEOM class.
362 To use it you can load geom_raid kernel module and use graid(8) tool
363 for management. Instead of /dev/arX device names, use /dev/raid/rX.
365 No kernel config options or code have been removed, so if a problem
366 arises, please report it and optionally revert to the old ATA stack.
367 In order to do it you can remove from the kernel config:
372 , and instead add back:
373 device atadisk # ATA disk drives
374 device ataraid # ATA RAID drives
375 device atapicd # ATAPI CDROM drives
376 device atapifd # ATAPI floppy drives
377 device atapist # ATAPI tape drives
380 The default NFS server has been changed to the new server, which
381 was referred to as the experimental server. If you need to switch
382 back to the old NFS server, you must now put the "-o" option on
383 both the mountd and nfsd commands. This can be done using the
384 mountd_flags and nfs_server_flags rc.conf variables until an
385 update to the rc scripts is committed, which is coming soon.
388 The GNU Objective-C runtime library (libobjc), and other Objective-C
389 related components have been removed from the base system. If you
390 require an Objective-C library, please use one of the available ports.
393 ath(4) has been split into bus- and device- modules. if_ath contains
394 the HAL, the TX rate control and the network device code. if_ath_pci
395 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
396 contains the AHB glue. Users need to load both if_ath_pci and if_ath
397 in order to use ath on everything else.
399 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
400 need to load if_ath and if_ath_pci for ath(4) operation.
403 As part of the replacement of sysinstall, the process of building
404 release media has changed significantly. For details, please re-read
405 release(7), which has been updated to reflect the new build process.
408 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
409 is the last available version under GPLv2. It brings a number of new
410 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
411 4.1 and SSE 4.2), better support for powerpc64, a number of new
412 directives, and lots of other small improvements. See the ChangeLog
413 file in contrib/binutils for the full details.
416 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
417 compliant, and will now use half of hash for authentication.
418 This will break interoperability with all stacks (including all
419 actual FreeBSD versions) who implement
420 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
422 The only workaround with such peers is to use another HMAC
423 algorithm for IPsec ("phase 2") authentication.
426 Remove the uio_yield prototype and symbol. This function has
427 been misnamed since it was introduced and should not be
428 globally exposed with this name. The equivalent functionality
429 is now available using kern_yield(curthread->td_user_pri).
430 The function remains undocumented.
433 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
434 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
435 for scalar sysctls is defined but disabled. Code that needs
436 UQUAD to pass the type checking that must compile on older
437 systems where the define is not present can check against
438 __FreeBSD_version >= 900030.
440 The system dialog(1) has been replaced with a new version previously
441 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
442 with the previous version, but the libdialog associated with it has
443 a largely incompatible API. As such, the original version of libdialog
444 will be kept temporarily as libodialog, until its base system consumers
445 are replaced or updated. Bump __FreeBSD_version to 900030.
448 If you are trying to run make universe on a -stable system, and you get
449 the following warning:
450 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
451 unknown. config(8) likely too old."
452 or something similar to it, then you must upgrade your -stable system
453 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
454 stable/8) or build the config from the latest stable/8 branch and
455 install it on your system.
457 Prior to this date, building a current universe on 8-stable system from
458 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
459 error in the first kernel build phase. A new config on those old
460 systems will fix that problem for older versions of -current.
463 The TCP stack has been modified to allow Khelp modules to interact with
464 it via helper hook points and store per-connection data in the TCP
465 control block. Bump __FreeBSD_version to 900029. User space tools that
466 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
470 Generic IEEE 802.3 annex 31B full duplex flow control support has been
471 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
472 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
473 to take advantage of it instead of using custom implementations. This
474 means that these drivers now no longer unconditionally advertise
475 support for flow control but only do so if flow control is a selected
476 media option. This was implemented in the generic support that way in
477 order to allow flow control to be switched on and off via ifconfig(8)
478 with the PHY specific default to typically off in order to protect
479 from unwanted effects. Consequently, if you used flow control with
480 one of the above mentioned drivers you now need to explicitly enable
482 ifconfig bge0 media auto mediaopt flowcontrol
484 Along with the above mentioned changes generic support for setting
485 1000baseT master mode also has been added and brgphy(4), ciphy(4),
486 e1000phy(4) as well as ip1000phy(4) have been converted to take
487 advantage of it. This means that these drivers now no longer take the
488 link0 parameter for selecting master mode but the master media option
489 has to be used instead, for example like in the following:
490 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
492 Selection of master mode now is also available with all other PHY
493 drivers supporting 1000baseT.
496 The TCP stack has received a significant update to add support for
497 modularised congestion control and generally improve the clarity of
498 congestion control decisions. Bump __FreeBSD_version to 900025. User
499 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
500 sockstat) need to be recompiled.
503 The man(1) utility has been replaced by a new version that no longer
504 uses /etc/manpath.config. Please consult man.conf(5) for how to
505 migrate local entries to the new format.
508 The copyright strings printed by login(1) and sshd(8) at the time of a
509 new connection have been removed to follow other operating systems and
513 A workaround for a fixed ld bug has been removed in kernel code,
514 so make sure that your system ld is built from sources after
515 revision 210245 from 2010-07-19 (r211583 if building head kernel
516 on stable/8, r211584 for stable/7; both from 2010-08-21).
517 A symptom of incorrect ld version is different addresses for
518 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
521 The $ipv6_prefer variable in rc.conf(5) has been split into
522 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
524 The $ip6addrctl_policy is a variable to choose a pre-defined
525 address selection policy set by ip6addrctl(8). A value
526 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
529 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
530 flag (see an entry of 20090926) is set on an interface with no
531 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
532 security reason. If you want IPv6 link-local address on all
533 interfaces by default, set this to "YES".
535 The old ipv6_prefer="YES" is equivalent to
536 ipv6_activate_all_interfaces="YES" and
537 ip6addrctl_policy="ipv6_prefer".
540 DTrace has grown support for userland tracing. Due to this, DTrace is
541 now i386 and amd64 only.
542 dtruss(1) is now installed by default on those systems and a new
543 kernel module is needed for userland tracing: fasttrap.
544 No changes to your kernel config file are necessary to enable
545 userland tracing, but you might consider adding 'STRIP=' and
546 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
547 to have informative userland stack traces in DTrace (ustack).
550 The acpi_aiboost(4) driver has been removed in favor of the new
551 aibs(4) driver. You should update your kernel configuration file.
554 BSD grep has been imported to the base system and it is built by
555 default. It is completely BSD licensed, highly GNU-compatible, uses
556 less memory than its GNU counterpart and has a small codebase.
557 However, it is slower than its GNU counterpart, which is mostly
558 noticeable for larger searches, for smaller ones it is measurable
559 but not significant. The reason is complex, the most important factor
560 is that we lack a modern and efficient regex library and GNU
561 overcomes this by optimizing the searches internally. Future work
562 on improving the regex performance is planned, for the meantime,
563 users that need better performance, can build GNU grep instead by
564 setting the WITH_GNU_GREP knob.
567 Due to the import of powerpc64 support, all existing powerpc kernel
568 configuration files must be updated with a machine directive like this:
569 machine powerpc powerpc
571 In addition, an updated config(8) is required to build powerpc kernels
575 A new version of ZFS (version 15) has been merged to -HEAD.
576 This version uses a python library for the following subcommands:
577 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
578 For full functionality of these commands the following port must
579 be installed: sysutils/py-zfs
582 'vm_page's are now hashed by physical address to an array of mutexes.
583 Currently this is only used to serialize access to hold_count. Over
584 time the page queue mutex will be peeled away. This changes the size
585 of pmap on every architecture. And requires all callers of vm_page_hold
586 and vm_page_unhold to be updated.
589 WITH_CTF can now be specified in src.conf (not recommended, there
590 are some problems with static executables), make.conf (would also
591 affect ports which do not use GNU make and do not override the
592 compile targets) or in the kernel config (via "makeoptions
594 When WITH_CTF was specified there before this was silently ignored,
595 so make sure that WITH_CTF is not used in places which could lead
596 to unwanted behavior.
599 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
600 to allow 32-bit compatibility on non-x86 platforms. All kernel
601 configurations on amd64 and ia64 platforms using these options must
602 be modified accordingly.
605 The utmp user accounting database has been replaced with utmpx,
606 the user accounting interface standardized by POSIX.
607 Unfortunately the semantics of utmp and utmpx don't match,
608 making it practically impossible to support both interfaces.
609 The user accounting database is used by tools like finger(1),
610 last(1), talk(1), w(1) and ac(8).
612 All applications in the base system use utmpx. This means only
613 local binaries (e.g. from the ports tree) may still use these
614 utmp database files. These applications must be rebuilt to make
617 After the system has been upgraded, it is safe to remove the old
618 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
619 assuming their contents is of no importance anymore. Old wtmp
620 databases can only be used by last(1) and ac(8) after they have
621 been converted to the new format using wtmpcvt(1).
624 Introduce the kernel thread "deadlock resolver" (which can be enabled
625 via the DEADLKRES option, see NOTES for more details) and the
626 sleepq_type() function for sleepqueues.
629 The rc.firewall and rc.firewall6 were unified, and
630 rc.firewall6 and rc.d/ip6fw were removed.
631 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
632 variables are obsoleted. Instead, the following new rc
633 variables are added to rc.d/ipfw:
635 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
636 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
637 firewall_simple_onet_ipv6, firewall_trusted_ipv6
639 The meanings correspond to the relevant IPv4 variables.
645 The default terminal emulation for syscons(4) has been changed
646 from cons25 to xterm on all platforms except pc98. This means
647 that the /etc/ttys file needs to be updated to ensure correct
648 operation of applications on the console.
650 The terminal emulation style can be toggled per window by using
651 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
652 options can be used to change the compile-time default back to
655 To prevent graphical artifacts, make sure the TERM environment
656 variable is set to match the terminal emulation that is being
657 performed by syscons(4).
660 The layout of the structure ieee80211req_scan_result has changed.
661 Applications that require wireless scan results (e.g. ifconfig(8))
662 from net80211 need to be recompiled.
664 Applications such as wpa_supplicant(8) may require a full world
665 build without using NO_CLEAN in order to get synchronized with the
669 The iwn(4) driver has been updated to support the 5000 and 5150 series.
670 There's one kernel module for each firmware. Adding "device iwnfw"
671 to the kernel configuration file means including all three firmware
672 images inside the kernel. If you want to include just the one for
673 your wireless card, use the devices iwn4965fw, iwn5000fw or
677 The rc.d/network_ipv6, IPv6 configuration script has been integrated
678 into rc.d/netif. The changes are the following:
680 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
681 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
682 Note that both variables need the "inet6" keyword at the head.
684 Do not set $ipv6_network_interfaces manually if you do not
685 understand what you are doing. It is not needed in most cases.
687 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
690 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
691 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
693 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
694 all configured interfaces have "inet6 accept_rtadv" in the
695 $ifconfig_IF_ipv6. These are for backward compatibility.
697 3. A new variable $ipv6_prefer has been added. If NO, IPv6
698 functionality of interfaces with no corresponding
699 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
700 and the default address selection policy of ip6addrctl(8)
701 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
702 Note that if you want to configure IPv6 functionality on the
703 disabled interfaces after boot, first you need to clear the flag by
704 using ifconfig(8) like:
706 ifconfig em0 inet6 -ifdisabled
708 If YES, the default address selection policy is set as
711 The default value of $ipv6_prefer is NO.
713 4. If your system need to receive Router Advertisement messages,
714 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
715 scripts automatically invoke rtsol(8) when the interface becomes
716 UP. The Router Advertisement messages are used for SLAAC
717 (State-Less Address AutoConfiguration).
720 802.11s D3.03 support was committed. This is incompatible with the
721 previous code, which was based on D3.0.
724 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
725 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
726 control whether accepting Router Advertisement messages or not.
727 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
728 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
729 The ifconfig(8) utility now supports these flags.
732 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
733 mount(8) and -a option for df(1) to see them.
736 The old tunable hw.bus.devctl_disable has been superseded by
737 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
738 replaced by hw.bus.devctl_queue=0. The default for this new tunable
742 Remove the option STOP_NMI. The default action is now to use NMI only
743 for KDB via the newly introduced function stop_cpus_hard() and
744 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
747 The stable/8 branch created in subversion. This corresponds to the
748 RELENG_8 branch in CVS.
751 Bump the shared library version numbers for all libraries that do not
752 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
753 __FreeBSD_version to 800105.
756 Due to changes in the implementation of virtual network stack support,
757 all network-related kernel modules must be recompiled. As this change
758 breaks the ABI, bump __FreeBSD_version to 800104.
761 The TOE interface to the TCP syncache has been modified to remove
762 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
763 The cxgb driver is the only TOE consumer affected by this change, and
764 needs to be recompiled along with the kernel. As this change breaks
765 the ABI, bump __FreeBSD_version to 800103.
768 Padding has been added to struct tcpcb, sackhint and tcpstat in
769 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
770 maintaining the ABI. However, this change breaks the ABI, so bump
771 __FreeBSD_version to 800102. User space tools that rely on the size of
772 any of these structs (e.g. sockstat) need to be recompiled.
775 The NFS_LEGACYRPC option has been removed along with the old kernel
776 RPC implementation that this option selected. Kernel configurations
777 may need to be adjusted.
780 The network interface device nodes at /dev/net/<interface> have been
781 removed. All ioctl operations can be performed the normal way using
782 routing sockets. The kqueue functionality can generally be replaced
783 with routing sockets.
786 The documentation from the FreeBSD Documentation Project (Handbook,
787 FAQ, etc.) is now installed via packages by sysinstall(8) and under
788 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
791 The ABI of various structures related to the SYSV IPC API have been
792 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
793 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
797 Layout of struct vnet has changed as routing related variables were
798 moved to their own Vimage module. Modules need to be recompiled. Bump
799 __FreeBSD_version to 800099.
802 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
803 respectively. As long as no more than 16 groups per process are used,
804 no changes should be visible. When more than 16 groups are used, old
805 binaries may fail if they call getgroups() or getgrouplist() with
806 statically sized storage. Recompiling will work around this, but
807 applications should be modified to use dynamically allocated storage
808 for group arrays as POSIX.1-2008 does not cap an implementation's
809 number of supported groups at NGROUPS_MAX+1 as previous versions did.
811 NFS and portalfs mounts may also be affected as the list of groups is
812 truncated to 16. Users of NFS who use more than 16 groups, should
813 take care that negative group permissions are not used on the exported
814 file systems as they will not be reliable unless a GSSAPI based
815 authentication method is used.
818 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
819 option compiles in the support for adaptive spinning for lockmgrs
820 which want to enable it. The lockinit() function now accepts the flag
821 LK_ADAPTIVE in order to make the lock object subject to adaptive
822 spinning when both held in write and read mode.
825 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
826 changed. User applications that use this ioctl need to be rebuilt.
829 The layout of struct thread has changed. Kernel and modules need to
833 The layout of structs ifnet, domain, protosw and vnet_net has changed.
834 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
837 window(1) has been removed from the base system. It can now be
838 installed from ports. The port is called misc/window.
841 The way we are storing and accessing `routing table' entries has
842 changed. Programs reading the FIB, like netstat, need to be
846 A new netisr implementation has been added for FreeBSD 8. Network
847 file system modules, such as igmp, ipdivert, and others, should be
849 Bump __FreeBSD_version to 800096.
852 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
856 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
857 Bump __FreeBSD_version to 800094.
860 Add mnt_xflag field to 'struct mount'. File system modules need to be
862 Bump __FreeBSD_version to 800093.
865 The compiling option ADAPTIVE_SX has been retired while it has been
866 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
867 The KPI for sx_init_flags() changes as accepting flags:
868 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
869 been introduced in order to handle the reversed logic.
870 Bump __FreeBSD_version to 800092.
873 Add support for hierarchical jails. Remove global securelevel.
874 Bump __FreeBSD_version to 800091.
877 The layout of struct vnet_net has changed, therefore modules
879 Bump __FreeBSD_version to 800090.
882 The newly imported zic(8) produces a new format in the output. Please
883 run tzsetup(8) to install the newly created data to /etc/localtime.
886 The sysctl tree for the usb stack has renamed from hw.usb2.* to
887 hw.usb.* and is now consistent again with previous releases.
890 802.11 monitor mode support was revised and driver api's were changed.
891 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
892 of DLT_IEEE802_11. No user-visible data structures were changed but
893 applications that use DLT_IEEE802_11 may require changes.
894 Bump __FreeBSD_version to 800088.
897 The layout of the following structs has changed: sysctl_oid,
898 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
899 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
900 panics may be experienced. World rebuild is required for
901 correctly checking networking state from userland.
902 Bump __FreeBSD_version to 800085.
905 MLDv2 and Source-Specific Multicast (SSM) have been merged
906 to the IPv6 stack. VIMAGE hooks are in but not yet used.
907 The implementation of SSM within FreeBSD's IPv6 stack closely
908 follows the IPv4 implementation.
910 For kernel developers:
912 * The most important changes are that the ip6_output() and
913 ip6_input() paths no longer take the IN6_MULTI_LOCK,
914 and this lock has been downgraded to a non-recursive mutex.
916 * As with the changes to the IPv4 stack to support SSM, filtering
917 of inbound multicast traffic must now be performed by transport
918 protocols within the IPv6 stack. This does not apply to TCP and
919 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
921 * The KPIs used by IPv6 multicast are similar to those used by
922 the IPv4 stack, with the following differences:
923 * im6o_mc_filter() is analogous to imo_multicast_filter().
924 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
925 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
926 * IN6_LOOKUP_MULTI() has been deprecated and removed.
927 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
928 for MLDv1 have an additional 'timer' argument which is used to
929 jitter the initial membership report for the solicited-node
930 multicast membership on-link.
931 * This is not strictly needed for MLDv2, which already jitters
932 its report transmissions. However, the 'timer' argument is
933 preserved in case MLDv1 is active on the interface.
935 * The KAME linked-list based IPv6 membership implementation has
936 been refactored to use a vector similar to that used by the IPv4
938 Code which maintains a list of its own multicast memberships
939 internally, e.g. carp, has been updated to reflect the new
942 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
943 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
944 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
945 implementation constraint which needs to be addressed in HEAD.
947 For application developers:
949 * The changes are broadly similar to those made for the IPv4
952 * The use of IPv4 and IPv6 multicast socket options on the same
953 socket, using mapped addresses, HAS NOT been tested or supported.
955 * There are a number of issues with the implementation of various
956 IPv6 multicast APIs which need to be resolved in the API surface
957 before the implementation is fully compatible with KAME userland
958 use, and these are mostly to do with interface index treatment.
960 * The literature available discusses the use of either the delta / ASM
961 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
962 using setsourcefilter(3)/getsourcefilter(3). For more information
963 please refer to RFC 3768, 'Socket Interface Extensions for
964 Multicast Source Filters'.
966 * Applications which use the published RFC 3678 APIs should be fine.
968 For systems administrators:
970 * The mtest(8) utility has been refactored to support IPv6, in
971 addition to IPv4. Interface addresses are no longer accepted
972 as arguments, their names must be used instead. The utility
973 will map the interface name to its first IPv4 address as
974 returned by getifaddrs(3).
976 * The ifmcstat(8) utility has also been updated to print the MLDv2
977 endpoint state and source filter lists via sysctl(3).
979 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
980 loopback of IPv6 multicast datagrams by default; it defaults to 1
981 to preserve the existing behaviour. Disabling multicast loopback is
982 recommended for optimal system performance.
984 * The IPv6 MROUTING code has been changed to examine this sysctl
985 instead of attempting to perform a group lookup before looping
986 back forwarded datagrams.
988 Bump __FreeBSD_version to 800084.
991 Implement low-level Bluetooth HCI API.
992 Bump __FreeBSD_version to 800083.
995 The layout of struct malloc_type, used by modules to register new
996 memory allocation types, has changed. Most modules will need to
997 be rebuilt or panics may be experienced.
998 Bump __FreeBSD_version to 800081.
1001 Anticipate overflowing inp_flags - add inp_flags2.
1002 This changes most offsets in inpcb, so checking v4 connection
1003 state will require a world rebuild.
1004 Bump __FreeBSD_version to 800080.
1007 Add an llentry to struct route and struct route_in6. Modules
1008 embedding a struct route will need to be recompiled.
1009 Bump __FreeBSD_version to 800079.
1012 The size of rt_metrics_lite and by extension rtentry has changed.
1013 Networking administration apps will need to be recompiled.
1014 The route command now supports show as an alias for get, weighting
1015 of routes, sticky and nostick flags to alter the behavior of stateful
1017 Bump __FreeBSD_version to 800078.
1020 Do not use Giant for kbdmux(4) locking. This is wrong and
1021 apparently causing more problems than it solves. This will
1022 re-open the issue where interrupt handlers may race with
1023 kbdmux(4) in polling mode. Typical symptoms include (but
1024 not limited to) duplicated and/or missing characters when
1025 low level console functions (such as gets) are used while
1026 interrupts are enabled (for example geli password prompt,
1027 mountroot prompt etc.). Disabling kbdmux(4) may help.
1030 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1031 kernel modules referencing any of the above need to be recompiled.
1032 Bump __FreeBSD_version to 800075.
1035 GEOM_PART has become the default partition slicer for storage devices,
1036 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1037 introduces some changes:
1039 MSDOS/EBR: the devices created from MSDOS extended partition entries
1040 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1041 to devices with offset-based names. fstabs may need to be modified.
1043 BSD: the "geometry does not match label" warning is harmless in most
1044 cases but it points to problems in file system misalignment with
1045 disk geometry. The "c" partition is now implicit, covers the whole
1046 top-level drive and cannot be (mis)used by users.
1048 General: Kernel dumps are now not allowed to be written to devices
1049 whose partition types indicate they are meant to be used for file
1050 systems (or, in case of MSDOS partitions, as something else than
1053 Most of these changes date approximately from 200812.
1056 The uscanner(4) driver has been removed from the kernel. This follows
1057 Linux removing theirs in 2.6 and making libusb the default interface
1058 (supported by sane).
1061 The multicast forwarding code has been cleaned up. netstat(1)
1062 only relies on KVM now for printing bandwidth upcall meters.
1063 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1064 ip6_mroute_mod respectively. The config(5) options for statically
1065 compiling this code remain the same, i.e. 'options MROUTING'.
1068 Support for the IFF_NEEDSGIANT network interface flag has been
1069 removed, which means that non-MPSAFE network device drivers are no
1070 longer supported. In particular, if_ar, if_sr, and network device
1071 drivers from the old (legacy) USB stack can no longer be built or
1075 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1076 a bunch of new language catalog files have also been added.
1077 This means that some common libc messages are now localized and
1078 they depend on the LC_MESSAGES environmental variable.
1081 The k8temp(4) driver has been renamed to amdtemp(4) since
1082 support for Family 10 and Family 11 CPU families was added.
1085 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1086 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1088 For kernel developers, the most important changes are that the
1089 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1090 and this lock has been downgraded to a non-recursive mutex.
1092 Transport protocols (UDP, Raw IP) are now responsible for filtering
1093 inbound multicast traffic according to group membership and source
1094 filters. The imo_multicast_filter() KPI exists for this purpose.
1095 Transports which do not use multicast (SCTP, TCP) already reject
1096 multicast by default. Forwarding and receive performance may improve
1097 as a mutex acquisition is no longer needed in the ip_input()
1098 low-level input path. in_addmulti() and in_delmulti() are shimmed
1099 to new KPIs which exist to support SSM in-kernel.
1101 For application developers, it is recommended that loopback of
1102 multicast datagrams be disabled for best performance, as this
1103 will still cause the lock to be taken for each looped-back
1104 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1105 be tuned to 0 to disable loopback by default; it defaults to 1
1106 to preserve the existing behaviour.
1108 For systems administrators, to obtain best performance with
1109 multicast reception and multiple groups, it is always recommended
1110 that a card with a suitably precise hash filter is used. Hash
1111 collisions will still result in the lock being taken within the
1112 transport protocol input path to check group membership.
1114 If deploying FreeBSD in an environment with IGMP snooping switches,
1115 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1116 enabled; this forces 224.0.0.0/24 group membership to be announced
1119 The size of 'struct igmpstat' has changed; netstat needs to be
1120 recompiled to reflect this.
1121 Bump __FreeBSD_version to 800070.
1124 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1125 updated to use it. This requires a buildworld/installworld in order to
1126 update the library and dependencies (usbconfig, etc). Its advisable to
1127 rebuild all ports which uses libusb. More specific directions are given
1128 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1129 libusb are no longer required and can be removed.
1132 A workaround is committed to allow the creation of System V shared
1133 memory segment of size > 2 GB on the 64-bit architectures.
1134 Due to a limitation of the existing ABI, the shm_segsz member
1135 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1136 wrong for large segments. Note that limits must be explicitly
1137 raised to allow such segments to be created.
1140 The layout of struct ifnet has changed, requiring a rebuild of all
1141 network device driver modules.
1144 The /dev handling for the new USB stack has changed, a
1145 buildworld/installworld is required for libusb20.
1148 The new USB2 stack has now been permanently moved in and all kernel and
1149 module names reverted to their previous values (eg, usb, ehci, ohci,
1150 ums, ...). The old usb stack can be compiled in by prefixing the name
1151 with the letter 'o', the old usb modules have been removed.
1152 Updating entry 20090216 for xorg and 20090215 for libmap may still
1156 The rc.conf(5) option if_up_delay has been renamed to
1157 defaultroute_delay to better reflect its purpose. If you have
1158 customized this setting in /etc/rc.conf you need to update it to
1162 xorg 7.4 wants to configure its input devices via hald which does not
1163 yet work with USB2. If the keyboard/mouse does not work in xorg then
1165 Option "AllowEmptyInput" "off"
1166 to your ServerLayout section. This will cause X to use the configured
1167 kbd and mouse sections from your xorg.conf.
1170 The GENERIC kernels for all architectures now default to the new USB2
1171 stack. No kernel config options or code have been removed so if a
1172 problem arises please report it and optionally revert to the old USB
1173 stack. If you are loading USB kernel modules or have a custom kernel
1174 that includes GENERIC then ensure that usb names are also changed over,
1175 eg uftdi -> usb2_serial_ftdi.
1177 Older programs linked against the ports libusb 0.1 need to be
1178 redirected to the new stack's libusb20. /etc/libmap.conf can
1180 # Map old usb library to new one for usb2 stack
1181 libusb-0.1.so.8 libusb20.so.1
1184 All USB ethernet devices now attach as interfaces under the name ueN
1185 (eg. ue0). This is to provide a predictable name as vendors often
1186 change usb chipsets in a product without notice.
1189 The ichsmb(4) driver has been changed to require SMBus slave
1190 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1191 All of the other SMBus controller drivers require left-justified
1192 slave addresses, so this change makes all the drivers provide the
1196 INET6 statistics (struct ip6stat) was updated.
1197 netstat(1) needs to be recompiled.
1200 NTFS has been removed from GENERIC kernel on amd64 to match
1201 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1202 will load ntfs.ko module automatically when NTFS support is
1203 actually needed, unless ntfs.ko is not installed or security
1204 level prohibits loading kernel modules. If either is the case,
1205 "options NTFS" has to be added into kernel config.
1208 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1209 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1210 800061. User space tools that rely on the size of struct tcpcb in
1211 tcp_var.h (e.g. sockstat) need to be recompiled.
1214 ng_tty(4) module updated to match the new TTY subsystem.
1215 Due to API change, user-level applications must be updated.
1216 New API support added to mpd5 CVS and expected to be present
1217 in next mpd5.3 release.
1220 With __FreeBSD_version 800060 the makefs tool is part of
1221 the base system (it was a port).
1224 The afdata and ifnet locks have been changed from mutexes to
1225 rwlocks, network modules will need to be re-compiled.
1228 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1229 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1230 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1231 architecture and 40 bytes on 64-bit architecture. The userland
1232 applications "arp" and "ndp" have been updated accordingly.
1233 The output from "netstat -r" shows only routing entries and
1234 none of the L2 information.
1237 __FreeBSD_version 800057 marks the switchover from the
1238 binary ath hal to source code. Users must add the line:
1240 options AH_SUPPORT_AR5416
1242 to their kernel config files when specifying:
1246 The ath_hal module no longer exists; the code is now compiled
1247 together with the driver in the ath module. It is now
1248 possible to tailor chip support (i.e. reduce the set of chips
1249 and thereby the code size); consult ath_hal(4) for details.
1252 __FreeBSD_version 800054 adds memory barriers to
1253 <machine/atomic.h>, new interfaces to ifnet to facilitate
1254 multiple hardware transmit queues for cards that support
1255 them, and a lock-less ring-buffer implementation to
1256 enable drivers to more efficiently manage queueing of
1260 A new version of ZFS (version 13) has been merged to -HEAD.
1261 This version has zpool attribute "listsnapshots" off by
1262 default, which means "zfs list" does not show snapshots,
1263 and is the same as Solaris behavior.
1266 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1269 The uhci, ohci, ehci and slhci USB Host controller drivers have
1270 been put into separate modules. If you load the usb module
1271 separately through loader.conf you will need to load the
1272 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1273 controller add the following to loader.conf:
1279 The ABI used by the PMC toolset has changed. Please keep
1280 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1284 atapci kernel module now includes only generic PCI ATA
1285 driver. AHCI driver moved to ataahci kernel module.
1286 All vendor-specific code moved into separate kernel modules:
1287 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1288 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1289 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1290 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1293 The TTY subsystem of the kernel has been replaced by a new
1294 implementation, which provides better scalability and an
1295 improved driver model. Most common drivers have been migrated to
1296 the new TTY subsystem, while others have not. The following
1297 drivers have not yet been ported to the new TTY layer:
1300 cy, digi, rc, rp, sio
1306 ng_h4, ng_tty, ppp, sl, snp
1308 Adding these drivers to your kernel configuration file shall
1309 cause compilation to fail.
1312 ntpd has been upgraded to 4.2.4p5.
1315 OpenSSH has been upgraded to 5.1p1.
1317 For many years, FreeBSD's version of OpenSSH preferred DSA
1318 over RSA for host and user authentication keys. With this
1319 upgrade, we've switched to the vendor's default of RSA over
1320 DSA. This may cause upgraded clients to warn about unknown
1321 host keys even for previously known hosts. Users should
1322 follow the usual procedure for verifying host keys before
1323 accepting the RSA key.
1325 This can be circumvented by setting the "HostKeyAlgorithms"
1326 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1329 Please note that the sequence of keys offered for
1330 authentication has been changed as well. You may want to
1331 specify IdentityFile in a different order to revert this
1335 The sio(4) driver has been removed from the i386 and amd64
1336 kernel configuration files. This means uart(4) is now the
1337 default serial port driver on those platforms as well.
1339 To prevent collisions with the sio(4) driver, the uart(4) driver
1340 uses different names for its device nodes. This means the
1341 onboard serial port will now most likely be called "ttyu0"
1342 instead of "ttyd0". You may need to reconfigure applications to
1343 use the new device names.
1345 When using the serial port as a boot console, be sure to update
1346 /boot/device.hints and /etc/ttys before booting the new kernel.
1347 If you forget to do so, you can still manually specify the hints
1348 at the loader prompt:
1350 set hint.uart.0.at="isa"
1351 set hint.uart.0.port="0x3F8"
1352 set hint.uart.0.flags="0x10"
1353 set hint.uart.0.irq="4"
1357 The gpt(8) utility has been removed. Use gpart(8) to partition
1361 The version that Linuxulator emulates was changed from 2.4.2
1362 to 2.6.16. If you experience any problems with Linux binaries
1363 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1364 if it fixes the problem contact emulation mailing list.
1367 ISDN4BSD (I4B) was removed from the src tree. You may need to
1368 update a your kernel configuration and remove relevant entries.
1371 I have checked in code to support multiple routing tables.
1372 See the man pages setfib(1) and setfib(2).
1373 This is a hopefully backwards compatible version,
1374 but to make use of it you need to compile your kernel
1375 with options ROUTETABLES=2 (or more up to 16).
1378 The 802.11 wireless support was redone to enable multi-bss
1379 operation on devices that are capable. The underlying device
1380 is no longer used directly but instead wlanX devices are
1381 cloned with ifconfig. This requires changes to rc.conf files.
1382 For example, change:
1383 ifconfig_ath0="WPA DHCP"
1386 ifconfig_wlan0="WPA DHCP"
1387 see rc.conf(5) for more details. In addition, mergemaster of
1388 /etc/rc.d is highly recommended. Simultaneous update of userland
1389 and kernel wouldn't hurt either.
1391 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1392 modules were merged into the base wlan module. All references
1393 to these modules (e.g. in kernel config files) must be removed.
1396 psm(4) has gained write(2) support in native operation level.
1397 Arbitrary commands can be written to /dev/psm%d and status can
1398 be read back from it. Therefore, an application is responsible
1399 for status validation and error recovery. It is a no-op in
1400 other operation levels.
1403 Support for KSE threading has been removed from the kernel. To
1404 run legacy applications linked against KSE libmap.conf may
1405 be used. The following libmap.conf may be used to ensure
1406 compatibility with any prior release:
1408 libpthread.so.1 libthr.so.1
1409 libpthread.so.2 libthr.so.2
1410 libkse.so.3 libthr.so.3
1413 The layout of struct vmspace has changed. This affects libkvm
1414 and any executables that link against libkvm and use the
1415 kvm_getprocs() function. In particular, but not exclusively,
1416 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1417 The effects are minimal, but it's advisable to upgrade world
1421 The latest em driver no longer has support in it for the
1422 82575 adapter, this is now moved to the igb driver. The
1423 split was done to make new features that are incompatible
1424 with older hardware easier to do.
1427 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1428 likewise the kernel option is now GEOM_LINUX_LVM.
1431 The default NFS mount mode has changed from UDP to TCP for
1432 increased reliability. If you rely on (insecurely) NFS
1433 mounting across a firewall you may need to update your
1437 Belatedly note the addition of m_collapse for compacting
1441 The fts(3) structures have been changed to use adequate
1442 integer types for their members and so to be able to cope
1443 with huge file trees. The old fts(3) ABI is preserved
1444 through symbol versioning in libc, so third-party binaries
1445 using fts(3) should still work, although they will not take
1446 advantage of the extended types. At the same time, some
1447 third-party software might fail to build after this change
1448 due to unportable assumptions made in its source code about
1449 fts(3) structure members. Such software should be fixed
1450 by its vendor or, in the worst case, in the ports tree.
1451 FreeBSD_version 800015 marks this change for the unlikely
1452 case that a portable fix is impossible.
1455 To upgrade to -current after this date, you must be running
1456 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1457 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1460 The ADAPTIVE_GIANT kernel option has been retired because its
1461 functionality is the default now.
1464 The AT keyboard emulation of sunkbd(4) has been turned on
1465 by default. In order to make the special symbols of the Sun
1466 keyboards driven by sunkbd(4) work under X these now have
1467 to be configured the same way as Sun USB keyboards driven
1468 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1470 Option "XkbLayout" "us"
1471 Option "XkbRules" "xorg"
1472 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1475 It has been decided that it is desirable to provide ABI
1476 backwards compatibility to the FreeBSD 4/5/6 versions of the
1477 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1478 broken with the introduction of PCI domain support (see the
1479 20070930 entry). Unfortunately, this required the ABI of
1480 PCIOCGETCONF to be broken again in order to be able to
1481 provide backwards compatibility to the old version of that
1482 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1483 again. As for prominent ports this affects neither pciutils
1484 nor xorg-server this time, the hal port needs to be rebuilt
1488 The misnamed kthread_create() and friends have been renamed
1489 to kproc_create() etc. Many of the callers already
1490 used kproc_start()..
1491 I will return kthread_create() and friends in a while
1492 with implementations that actually create threads, not procs.
1493 Renaming corresponds with version 800002.
1502 Avoid using make -j when upgrading. While generally safe, there are
1503 sometimes problems using -j to upgrade. If your upgrade fails with
1504 -j, please try again without -j. From time to time in the past there
1505 have been problems using -j with buildworld and/or installworld. This
1506 is especially true when upgrading between "distant" versions (eg one
1507 that cross a major release boundary or several minor releases, or when
1508 several months have passed on the -current branch).
1510 Sometimes, obscure build problems are the result of environment
1511 poisoning. This can happen because the make utility reads its
1512 environment when searching for values for global variables. To run
1513 your build attempts in an "environmental clean room", prefix all make
1514 commands with 'env -i '. See the env(1) manual page for more details.
1516 When upgrading from one major version to another it is generally best
1517 to upgrade to the latest code in the currently installed branch first,
1518 then do an upgrade to the new branch. This is the best-tested upgrade
1519 path, and has the highest probability of being successful. Please try
1520 this approach before reporting problems with a major version upgrade.
1524 When upgrading the boot ZFS pool to a new version, always follow
1527 1.) recompile and reinstall the ZFS boot loader and boot block
1528 (this is part of "make buildworld" and "make installworld")
1530 2.) update the ZFS boot block on your boot drive
1532 The following example updates the ZFS boot block on the first
1533 partition (freebsd-boot) of a GPT partitioned drive ad0:
1534 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1536 Non-boot pools do not need these updates.
1540 If you are updating from a prior version of FreeBSD (even one just
1541 a few days old), you should follow this procedure. It is the most
1542 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1544 make kernel-toolchain
1545 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1546 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1548 To test a kernel once
1549 ---------------------
1550 If you just want to boot a kernel once (because you are not sure
1551 if it works, or if you want to boot a known bad kernel to provide
1552 debugging information) run
1553 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1554 nextboot -k testkernel
1556 To just build a kernel when you know that it won't mess you up
1557 --------------------------------------------------------------
1558 This assumes you are already running a CURRENT system. Replace
1559 ${arch} with the architecture of your machine (e.g. "i386",
1560 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1562 cd src/sys/${arch}/conf
1563 config KERNEL_NAME_HERE
1564 cd ../compile/KERNEL_NAME_HERE
1569 If this fails, go to the "To build a kernel" section.
1571 To rebuild everything and install it on the current system.
1572 -----------------------------------------------------------
1573 # Note: sometimes if you are running current you gotta do more than
1574 # is listed here if you are upgrading from a really old current.
1576 <make sure you have good level 0 dumps>
1578 make kernel KERNCONF=YOUR_KERNEL_HERE
1580 <reboot in single user> [3]
1588 To cross-install current onto a separate partition
1589 --------------------------------------------------
1590 # In this approach we use a separate partition to hold
1591 # current's root, 'usr', and 'var' directories. A partition
1592 # holding "/", "/usr" and "/var" should be about 2GB in
1595 <make sure you have good level 0 dumps>
1598 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1599 <maybe newfs current's root partition>
1600 <mount current's root partition on directory ${CURRENT_ROOT}>
1601 make installworld DESTDIR=${CURRENT_ROOT}
1602 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1603 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1604 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1605 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1606 <reboot into current>
1607 <do a "native" rebuild/install as described in the previous section>
1608 <maybe install compatibility libraries from ports/misc/compat*>
1612 To upgrade in-place from stable to current
1613 ----------------------------------------------
1614 <make sure you have good level 0 dumps>
1616 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1618 <reboot in single user> [3]
1625 Make sure that you've read the UPDATING file to understand the
1626 tweaks to various things you need. At this point in the life
1627 cycle of current, things change often and you are on your own
1628 to cope. The defaults can also change, so please read ALL of
1629 the UPDATING entries.
1631 Also, if you are tracking -current, you must be subscribed to
1632 freebsd-current@freebsd.org. Make sure that before you update
1633 your sources that you have read and understood all the recent
1634 messages there. If in doubt, please track -stable which has
1635 much fewer pitfalls.
1637 [1] If you have third party modules, such as vmware, you
1638 should disable them at this point so they don't crash your
1641 [3] From the bootblocks, boot -s, and then do
1646 adjkerntz -i # if CMOS is wall time
1647 Also, when doing a major release upgrade, it is required that
1648 you boot into single user mode to do the installworld.
1650 [4] Note: This step is non-optional. Failure to do this step
1651 can result in a significant reduction in the functionality of the
1652 system. Attempting to do it by hand is not recommended and those
1653 that pursue this avenue should read this file carefully, as well
1654 as the archives of freebsd-current and freebsd-hackers mailing lists
1655 for potential gotchas. The -U option is also useful to consider.
1656 See mergemaster(8) for more information.
1658 [5] Usually this step is a noop. However, from time to time
1659 you may need to do this if you get unknown user in the following
1660 step. It never hurts to do it all the time. You may need to
1661 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1662 install) after the buildworld before this step if you last updated
1663 from [78]-stable or 9-stable before 20130430.
1665 [6] This only deletes old files and directories. Old libraries
1666 can be deleted by "make delete-old-libs", but you have to make
1667 sure that no program is using those libraries anymore.
1669 [8] In order to have a kernel that can run the 4.x binaries needed to
1670 do an installworld, you must include the COMPAT_FREEBSD4 option in
1671 your kernel. Failure to do so may leave you with a system that is
1672 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1673 required to run the 5.x binaries on more recent kernels. And so on
1674 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1676 Make sure that you merge any new devices from GENERIC since the
1677 last time you updated your kernel config file.
1679 [9] When checking out sources, you must include the -P flag to have
1680 cvs prune empty directories.
1682 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1683 "?=" instead of the "=" assignment operator, so that buildworld can
1684 override the CPUTYPE if it needs to.
1686 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1687 not on the command line, or in /etc/make.conf. buildworld will
1688 warn if it is improperly defined.
1691 This file contains a list, in reverse chronological order, of major
1692 breakages in tracking -current. It is not guaranteed to be a complete
1693 list of such breakages, and only contains entries since October 10, 2007.
1694 If you need to see UPDATING entries from before that date, you will need
1695 to fetch an UPDATING file from an older FreeBSD release.
1697 Copyright information:
1699 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1701 Redistribution, publication, translation and use, with or without
1702 modification, in full or in part, in any form or format of this
1703 document are permitted without further permission from the author.
1705 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1706 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1707 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1708 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1709 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1710 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1711 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1712 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1713 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1714 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1715 POSSIBILITY OF SUCH DAMAGE.
1717 Contact Warner Losh if you have any questions about your use of