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 20150513: p14 FreeBSD-EN-15:04.freebsd-update
16 Fix bug with freebsd-update(8) that does not ensure the previous
17 upgrade was completed. [EN-15:04]
19 20150407: p13 FreeBSD-SA-15:04.igmp [revised]
23 Improved patch for SA-15:04.igmp.
25 Fix multiple vulnerabilities of ntp. [SA-15:07]
27 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
30 Fix patch for SA-15:06.openssl.
32 20150319: p11 FreeBSD-SA-15:06.openssl
33 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
35 20150225: p10 FreeBSD-SA-15:04.igmp
38 FreeBSD-EN-15:02.openssl
39 FreeBSD-EN-15:03.freebsd-update
41 Fix integer overflow in IGMP protocol. [SA-15:04]
43 Fix BIND remote denial of service vulnerability. [SA-15:05]
45 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
47 Updated base system OpenSSL to 0.9.8zd. [EN-15:02]
49 Fix freebsd-update libraries update ordering issue. [EN-15:03]
51 20150127: p9 FreeBSD-SA-15:02.kmem
54 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
55 vulnerability. [SA-15:02]
57 Fix SCTP stream reset vulnerability. [SA-15:03]
59 20150114: p8 FreeBSD-SA-15:01.openssl
60 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
62 20141223: p7 FreeBSD-SA-14:31.ntp
63 FreeBSD-EN-14:13.freebsd-update
65 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
66 Fix directory deletion issue in freebsd-update. [EN-14:13]
68 20141210: p6 FreeBSD-SA-14:28.file
71 Fix multiple vulnerabilities in file(1) and libmagic(3).
74 Fix BIND remote denial of service vulnerability. [SA-14:29]
76 20141104: p5 FreeBSD-SA-14:25.setlogin
80 Fix kernel stack disclosure in setlogin(2) / getlogin(2).
83 Fix remote command execution in ftp(1). [SA-14:26]
85 Fix NFSv4 and ZFS cache consistency issue. [EN-14:12]
87 20141022: p4 FreeBSD-EN-14:10.tzdata
88 FreeBSD-EN-14:11.crypt
90 Time zone data file update. [EN-14:10]
92 Change crypt(3) default hashing algorithm back to DES. [EN-14:11]
94 20141021: p3 FreeBSD-SA-14:20.rtsold
95 FreeBSD-SA-14:21.routed
96 FreeBSD-SA-14:22.namei
97 FreeBSD-SA-14:23.openssl
99 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20]
101 Fix routed(8) remote denial of service vulnerability. [SA-14:21]
103 Fix memory leak in sandboxed namei lookup. [SA-14:22]
105 Fix OpenSSL multiple vulnerabilities. [SA-14:23]
107 20140916: p2 FreeBSD-SA-14:19.tcp
108 Fix Denial of Service in TCP packet processing. [SA-14:19]
110 20140909: p1 FreeBSD-SA-14:18.openssl
111 Fix OpenSSL multiple vulnerabilities. [SA-14:18]
117 On i386 and amd64 systems, the onifconsole flag is now set by default
118 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
119 as a login TTY if it is set in the bootloader as an active kernel
120 console. No changes in behavior should result otherwise. To revert to
121 the previous behavior, set ttyu0 to "off" in /etc/ttys.
124 Clang and llvm have been upgraded to 3.4.1 release.
127 Clang and llvm have been upgraded to 3.4 release.
130 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
131 been deprecated and will not be part of FreeBSD 11.0 and later
132 releases. If you use this driver, please consider switching to
133 the nfe(4) driver instead.
136 The behavior of gss_pseudo_random() for the krb5 mechanism
137 has changed, for applications requesting a longer random string
138 than produced by the underlying enctype's pseudo-random() function.
139 In particular, the random string produced from a session key of
140 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
141 be different at the 17th octet and later, after this change.
142 The counter used in the PRF+ construction is now encoded as a
143 big-endian integer in accordance with RFC 4402.
144 __FreeBSD_version is bumped to 902505.
150 Behavior of devfs rules path matching has been changed.
151 Pattern is now always matched against fully qualified devfs
152 path and slash characters must be explicitly matched by
153 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
154 subdirectories must be reviewed.
157 hastctl(8)'s `status' command output changed to terse one-liner format.
158 Scripts using this should switch to `list' command or be rewritten.
161 Fix a bug that allowed a tracing process (e.g. gdb) to write
162 to a memory-mapped file in the traced process's address space
163 even if neither the traced process nor the tracing process had
164 write access to that file.
167 Added ZFS TRIM support which is enabled by default. To disable
168 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf.
170 Creating new ZFS pools and adding new devices to existing pools
171 first performs a full device level TRIM which can take a significant
172 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0
173 to disable this behaviour.
175 ZFS TRIM requires the underlying device support BIO_DELETE which
176 is currently provided by methods such as ATA TRIM and SCSI UNMAP
177 via CAM, which are typically supported by SSD's.
179 Stats for ZFS TRIM can be monitored by looking at the sysctl's
180 under kstat.zfs.misc.zio_trim.
183 `list' command has been added to hastctl(8). For now, it is full
184 equivalent of `status' command.
185 WARNING: in the near future the output of hastctl's status command
186 will change to more terse format. If you use `hastctl status'
187 for parsing in your scripts, switch to `hastctl list'.
190 The mergemaster command now uses the default MAKEOBJDIRPREFIX
191 rather than creating it's own in the temporary directory in
192 order allow access to bootstrapped versions of tools such as
193 install and mtree. When upgrading from version of FreeBSD where
194 the install command does not support -l, you will need to
195 install a new mergemaster command if mergemaster -p is required.
196 This can be accomplished with the command (cd src/usr.sbin/mergemaster
199 Due to the use of the new -l option to install(1) during build
200 and install, you must take care not to directly set the INSTALL
201 make variable in your /etc/make.conf, /etc/src.conf, or on the
202 command line. If you wish to use the -C flag for all installs
203 you may be able to add INSTALL+=-C to /etc/make.conf or
207 Fix a bug that allows NFS clients to issue READDIR on files.
210 The install(1) option -M has changed meaning and now takes an
211 argument that is a file or path to append logs to. In the
212 unlikely event that -M was the last option on the command line
213 and the command line contained at least two files and a target
214 directory the first file will have logs appended to it. The -M
215 option served little practical purpose in the last decade so it's
216 used expected to be extremely rare.
219 A new compression method (lz4) has been merged to. Please refer to
220 zpool-features(7) for more information.
222 Please refer to the "ZFS notes" section of this file for information
223 on upgrading boot ZFS pools.
226 The VFS KBI was changed with the merge of several nullfs
227 optimizations and fixes. All filesystem modules must be
231 With the addition of auditdistd(8), a new auditdistd user is now
232 depended on during installworld. "mergemaster -p" can be used to add
233 the user prior to installworld, as documented in the handbook.
239 A new version of ZFS (pool version 5000) has been merged to 9-STABLE.
240 Starting with this version the old system of ZFS pool versioning
241 is superseded by "feature flags". This concept enables forward
242 compatibility against certain future changes in functionality of ZFS
243 pools. The first two read-only compatible "feature flags" for ZFS
244 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj".
245 For more information read the new zpool-features(7) manual page.
246 Please refer to the "ZFS notes" section of this file for information
247 on upgrading boot ZFS pools.
250 The commit introducing bsd.compiler.mk breaks the traditional
251 building of kernels before this point. Add -m ${SRC}/share/mk
252 (for the right value of SRC) to your command lines to work
253 around; update your useland to a point after this; or use the
254 buildkernel/installkernel top-level targets. See also 20120829.
257 The IPFIREWALL_FORWARD kernel option has been removed. Its
258 functionality now turned on by default.
261 The random(4) support for the VIA hardware random number
262 generator (`PADLOCK') is no longer enabled unconditionally.
263 Add the PADLOCK_RNG option in the custom kernel config if
264 needed. The GENERIC kernels on i386 and amd64 do include the
265 option, so the change only affects the custom kernel
269 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
270 the traditional method, you must update your system with an installworld
271 before the kernel will build. The documented make buildkernel/installkernel
272 interfaces (coupled with fresh make kernel-toolchain) continue to work.
275 The sparc64 ZFS loader has been changed to no longer try to auto-
276 detect ZFS providers based on diskN aliases but now requires these
277 to be explicitly listed in the OFW boot-device environment variable.
280 Now unix domain sockets behave "as expected" on nullfs(5). Previously
281 nullfs(5) did not pass through all behaviours to the underlying layer,
282 as a result if we bound to a socket on the lower layer we could connect
283 only to the lower path; if we bound to the upper layer we could connect
284 only to the upper path. The new behavior is one can connect to both the
285 lower and the upper paths regardless what layer path one binds to.
288 The acpi_wmi(4) status device /dev/wmistat has been renamed to
292 A new VOP_ADVISE() was added to support posix_fadvise(2). All
293 filesystem modules must be recompiled.
296 The interface of the VOP_VPTOCNP(9) changed, now the returned
297 vnode shall be referenced, previously it was required to be
298 only held. All in-tree filesystems are converted.
304 The broken amd(4) driver has been replaced with esp(4) in the amd64,
305 i386 and pc98 GENERIC kernel configuration files.
308 This commit modifies vfs_register() so that it uses a hash
309 calculation to set vfc_typenum, which is enabled by default.
310 The first time a system is booted after this change, the
311 vfc_typenum values will change for all file systems. The
312 main effect of this is a change to the NFS server file handles
313 for file systems that use vfc_typenum in their fsid, such as ZFS.
314 It will, however, prevent vfc_typenum from changing when file
315 systems are loaded in a different order for subsequent reboots.
316 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
317 until you are ready to remount all NFS clients after a reboot.
320 Bump the shared library version numbers for libraries that
321 do not use symbol versioning, have changed the ABI compared
322 to stable/8 and which shared library version was not bumped.
323 Done as part of 9.0-RELEASE cycle.
326 During the merge of Capsicum features, the fget(9) KPI was modified.
327 This may require the rebuilding of out-of-tree device drivers --
328 issues have been reported specifically with the nVidia device driver.
329 __FreeBSD_version is bumped to 900041.
331 Also, there is a period between 20110811 and 20110814 where the
332 special devices /dev/{stdin,stdout,stderr} did not work correctly.
333 Building world from a kernel during that window may not work.
336 The packet filter (pf) code has been updated to OpenBSD 4.5.
337 You need to update userland tools to be in sync with kernel.
338 This update breaks backward compatibility with earlier pfsync(4)
339 versions. Care must be taken when updating redundant firewall setups.
342 The following sysctls and tunables are retired on x86 platforms:
344 machdep.hlt_logical_cpus
345 The following sysctl is retired:
346 machdep.hyperthreading_allowed
347 The sysctls were supposed to provide a way to dynamically offline and
348 online selected CPUs on x86 platforms, but the implementation has not
349 been reliable especially with SCHED_ULE scheduler.
350 machdep.hyperthreading_allowed tunable is still available to ignore
351 hyperthreading CPUs at OS level.
352 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
353 where X is an APIC ID of a CPU. Be advised, though, that disabling
354 CPUs in non-uniform fashion will result in non-uniform topology and
355 may lead to sub-optimal system performance with SCHED_ULE, which is
359 cpumask_t type is retired and cpuset_t is used in order to describe
363 Changes to ifconfig(8) for dynamic address family detection mandate
364 that you are running a kernel of 20110525 or later. Make sure to
365 follow the update procedure to boot a new kernel before installing
369 Support for sun4v architecture is officially dropped
372 Several KPI breaking changes have been committed to the mii(4) layer,
373 the PHY drivers and consequently some Ethernet drivers using mii(4).
374 This means that miibus.ko and the modules of the affected Ethernet
375 drivers need to be recompiled.
377 Note to kernel developers: Given that the OUI bit reversion problem
378 was fixed as part of these changes all mii(4) commits related to OUIs,
379 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
380 handling, no longer can be merged verbatim to stable/8 and previous
384 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
385 into their kernel configurations along with 'device pci'.
388 The default NFS client is now the new NFS client, so fstype "newnfs"
389 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
390 Although mounts via fstype "nfs" will usually work without userland
391 changes, it is recommended that the mount(8) and mount_nfs(8)
392 commands be rebuilt from sources and that a link to mount_nfs called
393 mount_oldnfs be created. The new client is compiled into the
394 kernel with "options NFSCL" and this is needed for diskless root
395 file systems. The GENERIC kernel configs have been changed to use
396 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
397 To use the regular/old client, you can "mount -t oldnfs ...". For
398 a diskless root file system, you must also include a line like:
400 vfs.root.mountfrom="oldnfs:"
402 in the boot/loader.conf on the root fs on the NFS server to make
403 a diskless root fs use the old client.
406 The GENERIC kernels for all architectures now default to the new
407 CAM-based ATA stack. It means that all legacy ATA drivers were
408 removed and replaced by respective CAM drivers. If you are using
409 ATA device names in /etc/fstab or other places, make sure to update
410 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
411 where 'Y's are the sequential numbers starting from zero for each type
412 in order of detection, unless configured otherwise with tunables,
413 see cam(4)). There will be symbolic links created in /dev/ to map
414 old adX devices to the respective adaY. They should provide basic
415 compatibility for file systems mounting in most cases, but they do
416 not support old user-level APIs and do not have respective providers
417 in GEOM. Consider using updated management tools with new device names.
419 It is possible to load devices ahci, ata, siis and mvs as modules,
420 but option ATA_CAM should remain in kernel configuration to make ata
421 module work as CAM driver supporting legacy ATA controllers. Device ata
422 still can be used in modular fashion (atacore + ...). Modules atadisk
423 and atapi* are not used and won't affect operation in ATA_CAM mode.
424 Note that to use CAM-based ATA kernel should include CAM devices
425 scbus, pass, da (or explicitly ada), cd and optionally others. All of
426 them are parts of the cam module.
428 ataraid(4) functionality is now supported by the RAID GEOM class.
429 To use it you can load geom_raid kernel module and use graid(8) tool
430 for management. Instead of /dev/arX device names, use /dev/raid/rX.
432 No kernel config options or code have been removed, so if a problem
433 arises, please report it and optionally revert to the old ATA stack.
434 In order to do it you can remove from the kernel config:
439 , and instead add back:
440 device atadisk # ATA disk drives
441 device ataraid # ATA RAID drives
442 device atapicd # ATAPI CDROM drives
443 device atapifd # ATAPI floppy drives
444 device atapist # ATAPI tape drives
447 The default NFS server has been changed to the new server, which
448 was referred to as the experimental server. If you need to switch
449 back to the old NFS server, you must now put the "-o" option on
450 both the mountd and nfsd commands. This can be done using the
451 mountd_flags and nfs_server_flags rc.conf variables until an
452 update to the rc scripts is committed, which is coming soon.
455 The GNU Objective-C runtime library (libobjc), and other Objective-C
456 related components have been removed from the base system. If you
457 require an Objective-C library, please use one of the available ports.
460 ath(4) has been split into bus- and device- modules. if_ath contains
461 the HAL, the TX rate control and the network device code. if_ath_pci
462 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
463 contains the AHB glue. Users need to load both if_ath_pci and if_ath
464 in order to use ath on everything else.
466 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
467 need to load if_ath and if_ath_pci for ath(4) operation.
470 As part of the replacement of sysinstall, the process of building
471 release media has changed significantly. For details, please re-read
472 release(7), which has been updated to reflect the new build process.
475 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
476 is the last available version under GPLv2. It brings a number of new
477 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
478 4.1 and SSE 4.2), better support for powerpc64, a number of new
479 directives, and lots of other small improvements. See the ChangeLog
480 file in contrib/binutils for the full details.
483 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
484 compliant, and will now use half of hash for authentication.
485 This will break interoperability with all stacks (including all
486 actual FreeBSD versions) who implement
487 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
489 The only workaround with such peers is to use another HMAC
490 algorithm for IPsec ("phase 2") authentication.
493 Remove the uio_yield prototype and symbol. This function has
494 been misnamed since it was introduced and should not be
495 globally exposed with this name. The equivalent functionality
496 is now available using kern_yield(curthread->td_user_pri).
497 The function remains undocumented.
500 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
501 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
502 for scalar sysctls is defined but disabled. Code that needs
503 UQUAD to pass the type checking that must compile on older
504 systems where the define is not present can check against
505 __FreeBSD_version >= 900030.
507 The system dialog(1) has been replaced with a new version previously
508 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
509 with the previous version, but the libdialog associated with it has
510 a largely incompatible API. As such, the original version of libdialog
511 will be kept temporarily as libodialog, until its base system consumers
512 are replaced or updated. Bump __FreeBSD_version to 900030.
515 If you are trying to run make universe on a -stable system, and you get
516 the following warning:
517 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
518 unknown. config(8) likely too old."
519 or something similar to it, then you must upgrade your -stable system
520 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
521 stable/8) or build the config from the latest stable/8 branch and
522 install it on your system.
524 Prior to this date, building a current universe on 8-stable system from
525 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
526 error in the first kernel build phase. A new config on those old
527 systems will fix that problem for older versions of -current.
530 The TCP stack has been modified to allow Khelp modules to interact with
531 it via helper hook points and store per-connection data in the TCP
532 control block. Bump __FreeBSD_version to 900029. User space tools that
533 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
537 Generic IEEE 802.3 annex 31B full duplex flow control support has been
538 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
539 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
540 to take advantage of it instead of using custom implementations. This
541 means that these drivers now no longer unconditionally advertise
542 support for flow control but only do so if flow control is a selected
543 media option. This was implemented in the generic support that way in
544 order to allow flow control to be switched on and off via ifconfig(8)
545 with the PHY specific default to typically off in order to protect
546 from unwanted effects. Consequently, if you used flow control with
547 one of the above mentioned drivers you now need to explicitly enable
549 ifconfig bge0 media auto mediaopt flowcontrol
551 Along with the above mentioned changes generic support for setting
552 1000baseT master mode also has been added and brgphy(4), ciphy(4),
553 e1000phy(4) as well as ip1000phy(4) have been converted to take
554 advantage of it. This means that these drivers now no longer take the
555 link0 parameter for selecting master mode but the master media option
556 has to be used instead, for example like in the following:
557 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
559 Selection of master mode now is also available with all other PHY
560 drivers supporting 1000baseT.
563 The TCP stack has received a significant update to add support for
564 modularised congestion control and generally improve the clarity of
565 congestion control decisions. Bump __FreeBSD_version to 900025. User
566 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
567 sockstat) need to be recompiled.
570 The man(1) utility has been replaced by a new version that no longer
571 uses /etc/manpath.config. Please consult man.conf(5) for how to
572 migrate local entries to the new format.
575 The copyright strings printed by login(1) and sshd(8) at the time of a
576 new connection have been removed to follow other operating systems and
580 A workaround for a fixed ld bug has been removed in kernel code,
581 so make sure that your system ld is built from sources after
582 revision 210245 from 2010-07-19 (r211583 if building head kernel
583 on stable/8, r211584 for stable/7; both from 2010-08-21).
584 A symptom of incorrect ld version is different addresses for
585 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
588 The $ipv6_prefer variable in rc.conf(5) has been split into
589 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
591 The $ip6addrctl_policy is a variable to choose a pre-defined
592 address selection policy set by ip6addrctl(8). A value
593 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
596 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
597 flag (see an entry of 20090926) is set on an interface with no
598 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
599 security reason. If you want IPv6 link-local address on all
600 interfaces by default, set this to "YES".
602 The old ipv6_prefer="YES" is equivalent to
603 ipv6_activate_all_interfaces="YES" and
604 ip6addrctl_policy="ipv6_prefer".
607 DTrace has grown support for userland tracing. Due to this, DTrace is
608 now i386 and amd64 only.
609 dtruss(1) is now installed by default on those systems and a new
610 kernel module is needed for userland tracing: fasttrap.
611 No changes to your kernel config file are necessary to enable
612 userland tracing, but you might consider adding 'STRIP=' and
613 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
614 to have informative userland stack traces in DTrace (ustack).
617 The acpi_aiboost(4) driver has been removed in favor of the new
618 aibs(4) driver. You should update your kernel configuration file.
621 BSD grep has been imported to the base system and it is built by
622 default. It is completely BSD licensed, highly GNU-compatible, uses
623 less memory than its GNU counterpart and has a small codebase.
624 However, it is slower than its GNU counterpart, which is mostly
625 noticeable for larger searches, for smaller ones it is measurable
626 but not significant. The reason is complex, the most important factor
627 is that we lack a modern and efficient regex library and GNU
628 overcomes this by optimizing the searches internally. Future work
629 on improving the regex performance is planned, for the meantime,
630 users that need better performance, can build GNU grep instead by
631 setting the WITH_GNU_GREP knob.
634 Due to the import of powerpc64 support, all existing powerpc kernel
635 configuration files must be updated with a machine directive like this:
636 machine powerpc powerpc
638 In addition, an updated config(8) is required to build powerpc kernels
642 A new version of ZFS (version 15) has been merged to -HEAD.
643 This version uses a python library for the following subcommands:
644 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
645 For full functionality of these commands the following port must
646 be installed: sysutils/py-zfs
649 'vm_page's are now hashed by physical address to an array of mutexes.
650 Currently this is only used to serialize access to hold_count. Over
651 time the page queue mutex will be peeled away. This changes the size
652 of pmap on every architecture. And requires all callers of vm_page_hold
653 and vm_page_unhold to be updated.
656 WITH_CTF can now be specified in src.conf (not recommended, there
657 are some problems with static executables), make.conf (would also
658 affect ports which do not use GNU make and do not override the
659 compile targets) or in the kernel config (via "makeoptions
661 When WITH_CTF was specified there before this was silently ignored,
662 so make sure that WITH_CTF is not used in places which could lead
663 to unwanted behavior.
666 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
667 to allow 32-bit compatibility on non-x86 platforms. All kernel
668 configurations on amd64 and ia64 platforms using these options must
669 be modified accordingly.
672 The utmp user accounting database has been replaced with utmpx,
673 the user accounting interface standardized by POSIX.
674 Unfortunately the semantics of utmp and utmpx don't match,
675 making it practically impossible to support both interfaces.
676 The user accounting database is used by tools like finger(1),
677 last(1), talk(1), w(1) and ac(8).
679 All applications in the base system use utmpx. This means only
680 local binaries (e.g. from the ports tree) may still use these
681 utmp database files. These applications must be rebuilt to make
684 After the system has been upgraded, it is safe to remove the old
685 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
686 assuming their contents is of no importance anymore. Old wtmp
687 databases can only be used by last(1) and ac(8) after they have
688 been converted to the new format using wtmpcvt(1).
691 Introduce the kernel thread "deadlock resolver" (which can be enabled
692 via the DEADLKRES option, see NOTES for more details) and the
693 sleepq_type() function for sleepqueues.
696 The rc.firewall and rc.firewall6 were unified, and
697 rc.firewall6 and rc.d/ip6fw were removed.
698 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
699 variables are obsoleted. Instead, the following new rc
700 variables are added to rc.d/ipfw:
702 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
703 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
704 firewall_simple_onet_ipv6, firewall_trusted_ipv6
706 The meanings correspond to the relevant IPv4 variables.
712 The default terminal emulation for syscons(4) has been changed
713 from cons25 to xterm on all platforms except pc98. This means
714 that the /etc/ttys file needs to be updated to ensure correct
715 operation of applications on the console.
717 The terminal emulation style can be toggled per window by using
718 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
719 options can be used to change the compile-time default back to
722 To prevent graphical artifacts, make sure the TERM environment
723 variable is set to match the terminal emulation that is being
724 performed by syscons(4).
727 The layout of the structure ieee80211req_scan_result has changed.
728 Applications that require wireless scan results (e.g. ifconfig(8))
729 from net80211 need to be recompiled.
731 Applications such as wpa_supplicant(8) may require a full world
732 build without using NO_CLEAN in order to get synchronized with the
736 The iwn(4) driver has been updated to support the 5000 and 5150 series.
737 There's one kernel module for each firmware. Adding "device iwnfw"
738 to the kernel configuration file means including all three firmware
739 images inside the kernel. If you want to include just the one for
740 your wireless card, use the devices iwn4965fw, iwn5000fw or
744 The rc.d/network_ipv6, IPv6 configuration script has been integrated
745 into rc.d/netif. The changes are the following:
747 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
748 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
749 Note that both variables need the "inet6" keyword at the head.
751 Do not set $ipv6_network_interfaces manually if you do not
752 understand what you are doing. It is not needed in most cases.
754 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
757 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
758 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
760 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
761 all configured interfaces have "inet6 accept_rtadv" in the
762 $ifconfig_IF_ipv6. These are for backward compatibility.
764 3. A new variable $ipv6_prefer has been added. If NO, IPv6
765 functionality of interfaces with no corresponding
766 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
767 and the default address selection policy of ip6addrctl(8)
768 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
769 Note that if you want to configure IPv6 functionality on the
770 disabled interfaces after boot, first you need to clear the flag by
771 using ifconfig(8) like:
773 ifconfig em0 inet6 -ifdisabled
775 If YES, the default address selection policy is set as
778 The default value of $ipv6_prefer is NO.
780 4. If your system need to receive Router Advertisement messages,
781 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
782 scripts automatically invoke rtsol(8) when the interface becomes
783 UP. The Router Advertisement messages are used for SLAAC
784 (State-Less Address AutoConfiguration).
787 802.11s D3.03 support was committed. This is incompatible with the
788 previous code, which was based on D3.0.
791 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
792 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
793 control whether accepting Router Advertisement messages or not.
794 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
795 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
796 The ifconfig(8) utility now supports these flags.
799 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
800 mount(8) and -a option for df(1) to see them.
803 The old tunable hw.bus.devctl_disable has been superseded by
804 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
805 replaced by hw.bus.devctl_queue=0. The default for this new tunable
809 Remove the option STOP_NMI. The default action is now to use NMI only
810 for KDB via the newly introduced function stop_cpus_hard() and
811 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
814 The stable/8 branch created in subversion. This corresponds to the
815 RELENG_8 branch in CVS.
818 Bump the shared library version numbers for all libraries that do not
819 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
820 __FreeBSD_version to 800105.
823 Due to changes in the implementation of virtual network stack support,
824 all network-related kernel modules must be recompiled. As this change
825 breaks the ABI, bump __FreeBSD_version to 800104.
828 The TOE interface to the TCP syncache has been modified to remove
829 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
830 The cxgb driver is the only TOE consumer affected by this change, and
831 needs to be recompiled along with the kernel. As this change breaks
832 the ABI, bump __FreeBSD_version to 800103.
835 Padding has been added to struct tcpcb, sackhint and tcpstat in
836 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
837 maintaining the ABI. However, this change breaks the ABI, so bump
838 __FreeBSD_version to 800102. User space tools that rely on the size of
839 any of these structs (e.g. sockstat) need to be recompiled.
842 The NFS_LEGACYRPC option has been removed along with the old kernel
843 RPC implementation that this option selected. Kernel configurations
844 may need to be adjusted.
847 The network interface device nodes at /dev/net/<interface> have been
848 removed. All ioctl operations can be performed the normal way using
849 routing sockets. The kqueue functionality can generally be replaced
850 with routing sockets.
853 The documentation from the FreeBSD Documentation Project (Handbook,
854 FAQ, etc.) is now installed via packages by sysinstall(8) and under
855 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
858 The ABI of various structures related to the SYSV IPC API have been
859 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
860 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
864 Layout of struct vnet has changed as routing related variables were
865 moved to their own Vimage module. Modules need to be recompiled. Bump
866 __FreeBSD_version to 800099.
869 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
870 respectively. As long as no more than 16 groups per process are used,
871 no changes should be visible. When more than 16 groups are used, old
872 binaries may fail if they call getgroups() or getgrouplist() with
873 statically sized storage. Recompiling will work around this, but
874 applications should be modified to use dynamically allocated storage
875 for group arrays as POSIX.1-2008 does not cap an implementation's
876 number of supported groups at NGROUPS_MAX+1 as previous versions did.
878 NFS and portalfs mounts may also be affected as the list of groups is
879 truncated to 16. Users of NFS who use more than 16 groups, should
880 take care that negative group permissions are not used on the exported
881 file systems as they will not be reliable unless a GSSAPI based
882 authentication method is used.
885 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
886 option compiles in the support for adaptive spinning for lockmgrs
887 which want to enable it. The lockinit() function now accepts the flag
888 LK_ADAPTIVE in order to make the lock object subject to adaptive
889 spinning when both held in write and read mode.
892 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
893 changed. User applications that use this ioctl need to be rebuilt.
896 The layout of struct thread has changed. Kernel and modules need to
900 The layout of structs ifnet, domain, protosw and vnet_net has changed.
901 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
904 window(1) has been removed from the base system. It can now be
905 installed from ports. The port is called misc/window.
908 The way we are storing and accessing `routing table' entries has
909 changed. Programs reading the FIB, like netstat, need to be
913 A new netisr implementation has been added for FreeBSD 8. Network
914 file system modules, such as igmp, ipdivert, and others, should be
916 Bump __FreeBSD_version to 800096.
919 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
923 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
924 Bump __FreeBSD_version to 800094.
927 Add mnt_xflag field to 'struct mount'. File system modules need to be
929 Bump __FreeBSD_version to 800093.
932 The compiling option ADAPTIVE_SX has been retired while it has been
933 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
934 The KPI for sx_init_flags() changes as accepting flags:
935 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
936 been introduced in order to handle the reversed logic.
937 Bump __FreeBSD_version to 800092.
940 Add support for hierarchical jails. Remove global securelevel.
941 Bump __FreeBSD_version to 800091.
944 The layout of struct vnet_net has changed, therefore modules
946 Bump __FreeBSD_version to 800090.
949 The newly imported zic(8) produces a new format in the output. Please
950 run tzsetup(8) to install the newly created data to /etc/localtime.
953 The sysctl tree for the usb stack has renamed from hw.usb2.* to
954 hw.usb.* and is now consistent again with previous releases.
957 802.11 monitor mode support was revised and driver api's were changed.
958 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
959 of DLT_IEEE802_11. No user-visible data structures were changed but
960 applications that use DLT_IEEE802_11 may require changes.
961 Bump __FreeBSD_version to 800088.
964 The layout of the following structs has changed: sysctl_oid,
965 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
966 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
967 panics may be experienced. World rebuild is required for
968 correctly checking networking state from userland.
969 Bump __FreeBSD_version to 800085.
972 MLDv2 and Source-Specific Multicast (SSM) have been merged
973 to the IPv6 stack. VIMAGE hooks are in but not yet used.
974 The implementation of SSM within FreeBSD's IPv6 stack closely
975 follows the IPv4 implementation.
977 For kernel developers:
979 * The most important changes are that the ip6_output() and
980 ip6_input() paths no longer take the IN6_MULTI_LOCK,
981 and this lock has been downgraded to a non-recursive mutex.
983 * As with the changes to the IPv4 stack to support SSM, filtering
984 of inbound multicast traffic must now be performed by transport
985 protocols within the IPv6 stack. This does not apply to TCP and
986 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
988 * The KPIs used by IPv6 multicast are similar to those used by
989 the IPv4 stack, with the following differences:
990 * im6o_mc_filter() is analogous to imo_multicast_filter().
991 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
992 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
993 * IN6_LOOKUP_MULTI() has been deprecated and removed.
994 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
995 for MLDv1 have an additional 'timer' argument which is used to
996 jitter the initial membership report for the solicited-node
997 multicast membership on-link.
998 * This is not strictly needed for MLDv2, which already jitters
999 its report transmissions. However, the 'timer' argument is
1000 preserved in case MLDv1 is active on the interface.
1002 * The KAME linked-list based IPv6 membership implementation has
1003 been refactored to use a vector similar to that used by the IPv4
1005 Code which maintains a list of its own multicast memberships
1006 internally, e.g. carp, has been updated to reflect the new
1009 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1010 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1011 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1012 implementation constraint which needs to be addressed in HEAD.
1014 For application developers:
1016 * The changes are broadly similar to those made for the IPv4
1019 * The use of IPv4 and IPv6 multicast socket options on the same
1020 socket, using mapped addresses, HAS NOT been tested or supported.
1022 * There are a number of issues with the implementation of various
1023 IPv6 multicast APIs which need to be resolved in the API surface
1024 before the implementation is fully compatible with KAME userland
1025 use, and these are mostly to do with interface index treatment.
1027 * The literature available discusses the use of either the delta / ASM
1028 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1029 using setsourcefilter(3)/getsourcefilter(3). For more information
1030 please refer to RFC 3768, 'Socket Interface Extensions for
1031 Multicast Source Filters'.
1033 * Applications which use the published RFC 3678 APIs should be fine.
1035 For systems administrators:
1037 * The mtest(8) utility has been refactored to support IPv6, in
1038 addition to IPv4. Interface addresses are no longer accepted
1039 as arguments, their names must be used instead. The utility
1040 will map the interface name to its first IPv4 address as
1041 returned by getifaddrs(3).
1043 * The ifmcstat(8) utility has also been updated to print the MLDv2
1044 endpoint state and source filter lists via sysctl(3).
1046 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1047 loopback of IPv6 multicast datagrams by default; it defaults to 1
1048 to preserve the existing behaviour. Disabling multicast loopback is
1049 recommended for optimal system performance.
1051 * The IPv6 MROUTING code has been changed to examine this sysctl
1052 instead of attempting to perform a group lookup before looping
1053 back forwarded datagrams.
1055 Bump __FreeBSD_version to 800084.
1058 Implement low-level Bluetooth HCI API.
1059 Bump __FreeBSD_version to 800083.
1062 The layout of struct malloc_type, used by modules to register new
1063 memory allocation types, has changed. Most modules will need to
1064 be rebuilt or panics may be experienced.
1065 Bump __FreeBSD_version to 800081.
1068 Anticipate overflowing inp_flags - add inp_flags2.
1069 This changes most offsets in inpcb, so checking v4 connection
1070 state will require a world rebuild.
1071 Bump __FreeBSD_version to 800080.
1074 Add an llentry to struct route and struct route_in6. Modules
1075 embedding a struct route will need to be recompiled.
1076 Bump __FreeBSD_version to 800079.
1079 The size of rt_metrics_lite and by extension rtentry has changed.
1080 Networking administration apps will need to be recompiled.
1081 The route command now supports show as an alias for get, weighting
1082 of routes, sticky and nostick flags to alter the behavior of stateful
1084 Bump __FreeBSD_version to 800078.
1087 Do not use Giant for kbdmux(4) locking. This is wrong and
1088 apparently causing more problems than it solves. This will
1089 re-open the issue where interrupt handlers may race with
1090 kbdmux(4) in polling mode. Typical symptoms include (but
1091 not limited to) duplicated and/or missing characters when
1092 low level console functions (such as gets) are used while
1093 interrupts are enabled (for example geli password prompt,
1094 mountroot prompt etc.). Disabling kbdmux(4) may help.
1097 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1098 kernel modules referencing any of the above need to be recompiled.
1099 Bump __FreeBSD_version to 800075.
1102 GEOM_PART has become the default partition slicer for storage devices,
1103 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1104 introduces some changes:
1106 MSDOS/EBR: the devices created from MSDOS extended partition entries
1107 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1108 to devices with offset-based names. fstabs may need to be modified.
1110 BSD: the "geometry does not match label" warning is harmless in most
1111 cases but it points to problems in file system misalignment with
1112 disk geometry. The "c" partition is now implicit, covers the whole
1113 top-level drive and cannot be (mis)used by users.
1115 General: Kernel dumps are now not allowed to be written to devices
1116 whose partition types indicate they are meant to be used for file
1117 systems (or, in case of MSDOS partitions, as something else than
1120 Most of these changes date approximately from 200812.
1123 The uscanner(4) driver has been removed from the kernel. This follows
1124 Linux removing theirs in 2.6 and making libusb the default interface
1125 (supported by sane).
1128 The multicast forwarding code has been cleaned up. netstat(1)
1129 only relies on KVM now for printing bandwidth upcall meters.
1130 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1131 ip6_mroute_mod respectively. The config(5) options for statically
1132 compiling this code remain the same, i.e. 'options MROUTING'.
1135 Support for the IFF_NEEDSGIANT network interface flag has been
1136 removed, which means that non-MPSAFE network device drivers are no
1137 longer supported. In particular, if_ar, if_sr, and network device
1138 drivers from the old (legacy) USB stack can no longer be built or
1142 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1143 a bunch of new language catalog files have also been added.
1144 This means that some common libc messages are now localized and
1145 they depend on the LC_MESSAGES environmental variable.
1148 The k8temp(4) driver has been renamed to amdtemp(4) since
1149 support for Family 10 and Family 11 CPU families was added.
1152 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1153 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1155 For kernel developers, the most important changes are that the
1156 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1157 and this lock has been downgraded to a non-recursive mutex.
1159 Transport protocols (UDP, Raw IP) are now responsible for filtering
1160 inbound multicast traffic according to group membership and source
1161 filters. The imo_multicast_filter() KPI exists for this purpose.
1162 Transports which do not use multicast (SCTP, TCP) already reject
1163 multicast by default. Forwarding and receive performance may improve
1164 as a mutex acquisition is no longer needed in the ip_input()
1165 low-level input path. in_addmulti() and in_delmulti() are shimmed
1166 to new KPIs which exist to support SSM in-kernel.
1168 For application developers, it is recommended that loopback of
1169 multicast datagrams be disabled for best performance, as this
1170 will still cause the lock to be taken for each looped-back
1171 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1172 be tuned to 0 to disable loopback by default; it defaults to 1
1173 to preserve the existing behaviour.
1175 For systems administrators, to obtain best performance with
1176 multicast reception and multiple groups, it is always recommended
1177 that a card with a suitably precise hash filter is used. Hash
1178 collisions will still result in the lock being taken within the
1179 transport protocol input path to check group membership.
1181 If deploying FreeBSD in an environment with IGMP snooping switches,
1182 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1183 enabled; this forces 224.0.0.0/24 group membership to be announced
1186 The size of 'struct igmpstat' has changed; netstat needs to be
1187 recompiled to reflect this.
1188 Bump __FreeBSD_version to 800070.
1191 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1192 updated to use it. This requires a buildworld/installworld in order to
1193 update the library and dependencies (usbconfig, etc). Its advisable to
1194 rebuild all ports which uses libusb. More specific directions are given
1195 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1196 libusb are no longer required and can be removed.
1199 A workaround is committed to allow the creation of System V shared
1200 memory segment of size > 2 GB on the 64-bit architectures.
1201 Due to a limitation of the existing ABI, the shm_segsz member
1202 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1203 wrong for large segments. Note that limits must be explicitly
1204 raised to allow such segments to be created.
1207 The layout of struct ifnet has changed, requiring a rebuild of all
1208 network device driver modules.
1211 The /dev handling for the new USB stack has changed, a
1212 buildworld/installworld is required for libusb20.
1215 The new USB2 stack has now been permanently moved in and all kernel and
1216 module names reverted to their previous values (eg, usb, ehci, ohci,
1217 ums, ...). The old usb stack can be compiled in by prefixing the name
1218 with the letter 'o', the old usb modules have been removed.
1219 Updating entry 20090216 for xorg and 20090215 for libmap may still
1223 The rc.conf(5) option if_up_delay has been renamed to
1224 defaultroute_delay to better reflect its purpose. If you have
1225 customized this setting in /etc/rc.conf you need to update it to
1229 xorg 7.4 wants to configure its input devices via hald which does not
1230 yet work with USB2. If the keyboard/mouse does not work in xorg then
1232 Option "AllowEmptyInput" "off"
1233 to your ServerLayout section. This will cause X to use the configured
1234 kbd and mouse sections from your xorg.conf.
1237 The GENERIC kernels for all architectures now default to the new USB2
1238 stack. No kernel config options or code have been removed so if a
1239 problem arises please report it and optionally revert to the old USB
1240 stack. If you are loading USB kernel modules or have a custom kernel
1241 that includes GENERIC then ensure that usb names are also changed over,
1242 eg uftdi -> usb2_serial_ftdi.
1244 Older programs linked against the ports libusb 0.1 need to be
1245 redirected to the new stack's libusb20. /etc/libmap.conf can
1247 # Map old usb library to new one for usb2 stack
1248 libusb-0.1.so.8 libusb20.so.1
1251 All USB ethernet devices now attach as interfaces under the name ueN
1252 (eg. ue0). This is to provide a predictable name as vendors often
1253 change usb chipsets in a product without notice.
1256 The ichsmb(4) driver has been changed to require SMBus slave
1257 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1258 All of the other SMBus controller drivers require left-justified
1259 slave addresses, so this change makes all the drivers provide the
1263 INET6 statistics (struct ip6stat) was updated.
1264 netstat(1) needs to be recompiled.
1267 NTFS has been removed from GENERIC kernel on amd64 to match
1268 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1269 will load ntfs.ko module automatically when NTFS support is
1270 actually needed, unless ntfs.ko is not installed or security
1271 level prohibits loading kernel modules. If either is the case,
1272 "options NTFS" has to be added into kernel config.
1275 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1276 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1277 800061. User space tools that rely on the size of struct tcpcb in
1278 tcp_var.h (e.g. sockstat) need to be recompiled.
1281 ng_tty(4) module updated to match the new TTY subsystem.
1282 Due to API change, user-level applications must be updated.
1283 New API support added to mpd5 CVS and expected to be present
1284 in next mpd5.3 release.
1287 With __FreeBSD_version 800060 the makefs tool is part of
1288 the base system (it was a port).
1291 The afdata and ifnet locks have been changed from mutexes to
1292 rwlocks, network modules will need to be re-compiled.
1295 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1296 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1297 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1298 architecture and 40 bytes on 64-bit architecture. The userland
1299 applications "arp" and "ndp" have been updated accordingly.
1300 The output from "netstat -r" shows only routing entries and
1301 none of the L2 information.
1304 __FreeBSD_version 800057 marks the switchover from the
1305 binary ath hal to source code. Users must add the line:
1307 options AH_SUPPORT_AR5416
1309 to their kernel config files when specifying:
1313 The ath_hal module no longer exists; the code is now compiled
1314 together with the driver in the ath module. It is now
1315 possible to tailor chip support (i.e. reduce the set of chips
1316 and thereby the code size); consult ath_hal(4) for details.
1319 __FreeBSD_version 800054 adds memory barriers to
1320 <machine/atomic.h>, new interfaces to ifnet to facilitate
1321 multiple hardware transmit queues for cards that support
1322 them, and a lock-less ring-buffer implementation to
1323 enable drivers to more efficiently manage queueing of
1327 A new version of ZFS (version 13) has been merged to -HEAD.
1328 This version has zpool attribute "listsnapshots" off by
1329 default, which means "zfs list" does not show snapshots,
1330 and is the same as Solaris behavior.
1333 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1336 The uhci, ohci, ehci and slhci USB Host controller drivers have
1337 been put into separate modules. If you load the usb module
1338 separately through loader.conf you will need to load the
1339 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1340 controller add the following to loader.conf:
1346 The ABI used by the PMC toolset has changed. Please keep
1347 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1351 atapci kernel module now includes only generic PCI ATA
1352 driver. AHCI driver moved to ataahci kernel module.
1353 All vendor-specific code moved into separate kernel modules:
1354 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1355 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1356 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1357 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1360 The TTY subsystem of the kernel has been replaced by a new
1361 implementation, which provides better scalability and an
1362 improved driver model. Most common drivers have been migrated to
1363 the new TTY subsystem, while others have not. The following
1364 drivers have not yet been ported to the new TTY layer:
1367 cy, digi, rc, rp, sio
1373 ng_h4, ng_tty, ppp, sl, snp
1375 Adding these drivers to your kernel configuration file shall
1376 cause compilation to fail.
1379 ntpd has been upgraded to 4.2.4p5.
1382 OpenSSH has been upgraded to 5.1p1.
1384 For many years, FreeBSD's version of OpenSSH preferred DSA
1385 over RSA for host and user authentication keys. With this
1386 upgrade, we've switched to the vendor's default of RSA over
1387 DSA. This may cause upgraded clients to warn about unknown
1388 host keys even for previously known hosts. Users should
1389 follow the usual procedure for verifying host keys before
1390 accepting the RSA key.
1392 This can be circumvented by setting the "HostKeyAlgorithms"
1393 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1396 Please note that the sequence of keys offered for
1397 authentication has been changed as well. You may want to
1398 specify IdentityFile in a different order to revert this
1402 The sio(4) driver has been removed from the i386 and amd64
1403 kernel configuration files. This means uart(4) is now the
1404 default serial port driver on those platforms as well.
1406 To prevent collisions with the sio(4) driver, the uart(4) driver
1407 uses different names for its device nodes. This means the
1408 onboard serial port will now most likely be called "ttyu0"
1409 instead of "ttyd0". You may need to reconfigure applications to
1410 use the new device names.
1412 When using the serial port as a boot console, be sure to update
1413 /boot/device.hints and /etc/ttys before booting the new kernel.
1414 If you forget to do so, you can still manually specify the hints
1415 at the loader prompt:
1417 set hint.uart.0.at="isa"
1418 set hint.uart.0.port="0x3F8"
1419 set hint.uart.0.flags="0x10"
1420 set hint.uart.0.irq="4"
1424 The gpt(8) utility has been removed. Use gpart(8) to partition
1428 The version that Linuxulator emulates was changed from 2.4.2
1429 to 2.6.16. If you experience any problems with Linux binaries
1430 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1431 if it fixes the problem contact emulation mailing list.
1434 ISDN4BSD (I4B) was removed from the src tree. You may need to
1435 update a your kernel configuration and remove relevant entries.
1438 I have checked in code to support multiple routing tables.
1439 See the man pages setfib(1) and setfib(2).
1440 This is a hopefully backwards compatible version,
1441 but to make use of it you need to compile your kernel
1442 with options ROUTETABLES=2 (or more up to 16).
1445 The 802.11 wireless support was redone to enable multi-bss
1446 operation on devices that are capable. The underlying device
1447 is no longer used directly but instead wlanX devices are
1448 cloned with ifconfig. This requires changes to rc.conf files.
1449 For example, change:
1450 ifconfig_ath0="WPA DHCP"
1453 ifconfig_wlan0="WPA DHCP"
1454 see rc.conf(5) for more details. In addition, mergemaster of
1455 /etc/rc.d is highly recommended. Simultaneous update of userland
1456 and kernel wouldn't hurt either.
1458 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1459 modules were merged into the base wlan module. All references
1460 to these modules (e.g. in kernel config files) must be removed.
1463 psm(4) has gained write(2) support in native operation level.
1464 Arbitrary commands can be written to /dev/psm%d and status can
1465 be read back from it. Therefore, an application is responsible
1466 for status validation and error recovery. It is a no-op in
1467 other operation levels.
1470 Support for KSE threading has been removed from the kernel. To
1471 run legacy applications linked against KSE libmap.conf may
1472 be used. The following libmap.conf may be used to ensure
1473 compatibility with any prior release:
1475 libpthread.so.1 libthr.so.1
1476 libpthread.so.2 libthr.so.2
1477 libkse.so.3 libthr.so.3
1480 The layout of struct vmspace has changed. This affects libkvm
1481 and any executables that link against libkvm and use the
1482 kvm_getprocs() function. In particular, but not exclusively,
1483 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1484 The effects are minimal, but it's advisable to upgrade world
1488 The latest em driver no longer has support in it for the
1489 82575 adapter, this is now moved to the igb driver. The
1490 split was done to make new features that are incompatible
1491 with older hardware easier to do.
1494 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1495 likewise the kernel option is now GEOM_LINUX_LVM.
1498 The default NFS mount mode has changed from UDP to TCP for
1499 increased reliability. If you rely on (insecurely) NFS
1500 mounting across a firewall you may need to update your
1504 Belatedly note the addition of m_collapse for compacting
1508 The fts(3) structures have been changed to use adequate
1509 integer types for their members and so to be able to cope
1510 with huge file trees. The old fts(3) ABI is preserved
1511 through symbol versioning in libc, so third-party binaries
1512 using fts(3) should still work, although they will not take
1513 advantage of the extended types. At the same time, some
1514 third-party software might fail to build after this change
1515 due to unportable assumptions made in its source code about
1516 fts(3) structure members. Such software should be fixed
1517 by its vendor or, in the worst case, in the ports tree.
1518 FreeBSD_version 800015 marks this change for the unlikely
1519 case that a portable fix is impossible.
1522 To upgrade to -current after this date, you must be running
1523 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1524 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1527 The ADAPTIVE_GIANT kernel option has been retired because its
1528 functionality is the default now.
1531 The AT keyboard emulation of sunkbd(4) has been turned on
1532 by default. In order to make the special symbols of the Sun
1533 keyboards driven by sunkbd(4) work under X these now have
1534 to be configured the same way as Sun USB keyboards driven
1535 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1537 Option "XkbLayout" "us"
1538 Option "XkbRules" "xorg"
1539 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1542 It has been decided that it is desirable to provide ABI
1543 backwards compatibility to the FreeBSD 4/5/6 versions of the
1544 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1545 broken with the introduction of PCI domain support (see the
1546 20070930 entry). Unfortunately, this required the ABI of
1547 PCIOCGETCONF to be broken again in order to be able to
1548 provide backwards compatibility to the old version of that
1549 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1550 again. As for prominent ports this affects neither pciutils
1551 nor xorg-server this time, the hal port needs to be rebuilt
1555 The misnamed kthread_create() and friends have been renamed
1556 to kproc_create() etc. Many of the callers already
1557 used kproc_start()..
1558 I will return kthread_create() and friends in a while
1559 with implementations that actually create threads, not procs.
1560 Renaming corresponds with version 800002.
1569 Avoid using make -j when upgrading. While generally safe, there are
1570 sometimes problems using -j to upgrade. If your upgrade fails with
1571 -j, please try again without -j. From time to time in the past there
1572 have been problems using -j with buildworld and/or installworld. This
1573 is especially true when upgrading between "distant" versions (eg one
1574 that cross a major release boundary or several minor releases, or when
1575 several months have passed on the -current branch).
1577 Sometimes, obscure build problems are the result of environment
1578 poisoning. This can happen because the make utility reads its
1579 environment when searching for values for global variables. To run
1580 your build attempts in an "environmental clean room", prefix all make
1581 commands with 'env -i '. See the env(1) manual page for more details.
1583 When upgrading from one major version to another it is generally best
1584 to upgrade to the latest code in the currently installed branch first,
1585 then do an upgrade to the new branch. This is the best-tested upgrade
1586 path, and has the highest probability of being successful. Please try
1587 this approach before reporting problems with a major version upgrade.
1591 When upgrading the boot ZFS pool to a new version, always follow
1594 1.) recompile and reinstall the ZFS boot loader and boot block
1595 (this is part of "make buildworld" and "make installworld")
1597 2.) update the ZFS boot block on your boot drive
1599 The following example updates the ZFS boot block on the first
1600 partition (freebsd-boot) of a GPT partitioned drive ad0:
1601 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1603 Non-boot pools do not need these updates.
1607 If you are updating from a prior version of FreeBSD (even one just
1608 a few days old), you should follow this procedure. It is the most
1609 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1611 make kernel-toolchain
1612 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1613 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1615 To test a kernel once
1616 ---------------------
1617 If you just want to boot a kernel once (because you are not sure
1618 if it works, or if you want to boot a known bad kernel to provide
1619 debugging information) run
1620 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1621 nextboot -k testkernel
1623 To just build a kernel when you know that it won't mess you up
1624 --------------------------------------------------------------
1625 This assumes you are already running a CURRENT system. Replace
1626 ${arch} with the architecture of your machine (e.g. "i386",
1627 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1629 cd src/sys/${arch}/conf
1630 config KERNEL_NAME_HERE
1631 cd ../compile/KERNEL_NAME_HERE
1636 If this fails, go to the "To build a kernel" section.
1638 To rebuild everything and install it on the current system.
1639 -----------------------------------------------------------
1640 # Note: sometimes if you are running current you gotta do more than
1641 # is listed here if you are upgrading from a really old current.
1643 <make sure you have good level 0 dumps>
1645 make kernel KERNCONF=YOUR_KERNEL_HERE
1647 <reboot in single user> [3]
1655 To cross-install current onto a separate partition
1656 --------------------------------------------------
1657 # In this approach we use a separate partition to hold
1658 # current's root, 'usr', and 'var' directories. A partition
1659 # holding "/", "/usr" and "/var" should be about 2GB in
1662 <make sure you have good level 0 dumps>
1665 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1666 <maybe newfs current's root partition>
1667 <mount current's root partition on directory ${CURRENT_ROOT}>
1668 make installworld DESTDIR=${CURRENT_ROOT}
1669 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1670 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1671 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1672 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1673 <reboot into current>
1674 <do a "native" rebuild/install as described in the previous section>
1675 <maybe install compatibility libraries from ports/misc/compat*>
1679 To upgrade in-place from stable to current
1680 ----------------------------------------------
1681 <make sure you have good level 0 dumps>
1683 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1685 <reboot in single user> [3]
1692 Make sure that you've read the UPDATING file to understand the
1693 tweaks to various things you need. At this point in the life
1694 cycle of current, things change often and you are on your own
1695 to cope. The defaults can also change, so please read ALL of
1696 the UPDATING entries.
1698 Also, if you are tracking -current, you must be subscribed to
1699 freebsd-current@freebsd.org. Make sure that before you update
1700 your sources that you have read and understood all the recent
1701 messages there. If in doubt, please track -stable which has
1702 much fewer pitfalls.
1704 [1] If you have third party modules, such as vmware, you
1705 should disable them at this point so they don't crash your
1708 [3] From the bootblocks, boot -s, and then do
1713 adjkerntz -i # if CMOS is wall time
1714 Also, when doing a major release upgrade, it is required that
1715 you boot into single user mode to do the installworld.
1717 [4] Note: This step is non-optional. Failure to do this step
1718 can result in a significant reduction in the functionality of the
1719 system. Attempting to do it by hand is not recommended and those
1720 that pursue this avenue should read this file carefully, as well
1721 as the archives of freebsd-current and freebsd-hackers mailing lists
1722 for potential gotchas. The -U option is also useful to consider.
1723 See mergemaster(8) for more information.
1725 [5] Usually this step is a noop. However, from time to time
1726 you may need to do this if you get unknown user in the following
1727 step. It never hurts to do it all the time. You may need to
1728 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1729 install) after the buildworld before this step if you last updated
1730 from [78]-stable or 9-stable before 20130430.
1732 [6] This only deletes old files and directories. Old libraries
1733 can be deleted by "make delete-old-libs", but you have to make
1734 sure that no program is using those libraries anymore.
1736 [8] In order to have a kernel that can run the 4.x binaries needed to
1737 do an installworld, you must include the COMPAT_FREEBSD4 option in
1738 your kernel. Failure to do so may leave you with a system that is
1739 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1740 required to run the 5.x binaries on more recent kernels. And so on
1741 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1743 Make sure that you merge any new devices from GENERIC since the
1744 last time you updated your kernel config file.
1746 [9] When checking out sources, you must include the -P flag to have
1747 cvs prune empty directories.
1749 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1750 "?=" instead of the "=" assignment operator, so that buildworld can
1751 override the CPUTYPE if it needs to.
1753 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1754 not on the command line, or in /etc/make.conf. buildworld will
1755 warn if it is improperly defined.
1758 This file contains a list, in reverse chronological order, of major
1759 breakages in tracking -current. It is not guaranteed to be a complete
1760 list of such breakages, and only contains entries since October 10, 2007.
1761 If you need to see UPDATING entries from before that date, you will need
1762 to fetch an UPDATING file from an older FreeBSD release.
1764 Copyright information:
1766 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1768 Redistribution, publication, translation and use, with or without
1769 modification, in full or in part, in any form or format of this
1770 document are permitted without further permission from the author.
1772 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1773 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1774 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1775 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1776 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1777 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1778 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1779 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1780 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1781 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1782 POSSIBILITY OF SUCH DAMAGE.
1784 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / releng / 9.3.git / blob