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