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 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
20 The polarity of Pulse Per Second (PPS) capture events with the
21 uart(4) driver has been corrected. Prior to this change the PPS
22 "assert" event corresponded to the trailing edge of a positive PPS
23 pulse and the "clear" event was the leading edge of the next pulse.
25 As the width of a PPS pulse in a typical GPS receiver is on the
26 order of 1 millisecond, most users will not notice any significant
27 difference with this change.
29 Anyone who has compensated for the historical polarity reversal by
30 configuring a negative offset equal to the pulse width will need to
31 remove that workaround.
34 From legacy ata(4) driver was removed support for SATA controllers
35 supported by more functional drivers ahci(4), siis(4) and mvs(4).
36 Kernel modules ataahci and ataadaptec were removed completely,
37 replaced by ahci and mvs modules respectively.
43 As ZFS requires more kernel stack pages than is the default on some
44 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
45 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
47 Please consider using 'options KSTACK_PAGES=X' where X is greater
48 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
51 The default Unbound configuration now enables remote control
52 using a local socket. Users who have already enabled the
53 local_unbound service should regenerate their configuration
54 by running "service local_unbound setup" as root.
57 An additional fix for the issue described in the 20150614 sendmail
58 entry below has been been committed in revision 284786.
61 The fix for the issue described in the 20150614 sendmail entry
62 below has been been committed in revision 284485. The work
63 around described in that entry is no longer needed unless the
64 default setting is overridden by a confDH_PARAMETERS configuration
65 setting of '5' or pointing to a 512 bit DH parameter file.
68 The import of openssl to address the FreeBSD-SA-15:10.openssl
69 security advisory includes a change which rejects handshakes
70 with DH parameters below 768 bits. sendmail releases prior
71 to 8.15.2 (not yet released), defaulted to a 512 bit
72 DH parameter setting for client connections. To work around
73 this interoperability, sendmail can be configured to use a
74 2048 bit DH parameter by:
76 1. Edit /etc/mail/`hostname`.mc
77 2. If a setting for confDH_PARAMETERS does not exist or
78 exists and is set to a string beginning with '5',
80 3. If a setting for confDH_PARAMETERS exists and is set to
81 a file path, create a new file with:
82 openssl dhparam -out /path/to/file 2048
83 4. Rebuild the .cf file:
84 cd /etc/mail/; make; make install
86 cd /etc/mail/; make restart
88 A sendmail patch is coming, at which time this file will be
92 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
93 defined in symlink(7); previously symlinks were silently ignored.
96 The const qualifier has been removed from iconv(3) to comply with
97 POSIX. The ports tree is aware of this from r384038 onwards.
100 At svn r275807, The default linux compat kernel ABI has been adjusted
101 to 2.6.18 in support of the linux-c6 compat ports infrastructure
102 update. If you wish to continue using the linux-f10 compat ports,
103 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
104 encouraged to update their linux-compat packages to linux-c6 during
105 their next update cycle.
107 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
110 pjdfstest has been integrated into kyua as an opt-in test suite.
111 Please see share/doc/pjdfstest/README for a more details on how to
118 The ofwfb driver, used to provide a graphics console on PowerPC when
119 using vt(4), no longer allows mmap() of all of physical memory. This
120 will prevent Xorg on PowerPC with some ATI graphics cards from
121 initializing properly unless x11-servers/xorg-server is updated to
125 The libatf-c and libatf-c++ major versions were downgraded to 0 and
126 1 respectively to match the upstream numbers. They were out of
127 sync because, when they were originally added to FreeBSD, the
128 upstream versions were not respected. These libraries are private
129 and not yet built by default, so renumbering them should be a
130 non-issue. However, unclean source trees will yield broken test
131 programs once the operator executes "make delete-old-libs" after a
134 Additionally, the atf-sh binary was made private by moving it into
135 /usr/libexec/. Already-built shell test programs will keep the
136 path to the old binary so they will break after "make delete-old"
139 If you are using WITH_TESTS=yes (not the default), wipe the object
140 tree and rebuild from scratch to prevent spurious test failures.
141 This is only needed once: the misnumbered libraries and misplaced
142 binaries have been added to OptionalObsoleteFiles.inc so they will
143 be removed during a clean upgrade.
146 The ixgbe tunables now match their sysctl counterparts, for example:
147 hw.ixgbe.enable_aim => hw.ix.enable_aim
148 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
151 The NFSv4.1 server committed by r269398 changes the internal
152 function call interfaces used between the NFS and krpc modules.
153 As such, __FreeBSD_version was bumped.
156 The default unbound configuration has been modified to address
157 issues with reverse lookups on networks that use private
158 address ranges. If you use the local_unbound service, run
159 "service local_unbound setup" as root to regenerate your
160 configuration, then "service local_unbound reload" to load the
164 It is no longer necessary to include the dwarf version in your DEBUG
165 options in your kernel config file. The bug that required it to be
166 placed in the config file has bene fixed. DEBUG should now just
167 contain -g. The build system will automatically update things
168 to do the right thing.
171 Several ABI breaking changes were merged to CTL and new iSCSI code.
172 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
173 iscsictl need to be rebuilt to work with a new kernel.
176 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
177 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
178 which differs from the behaviour controlled by this knob.)
181 On i386 and amd64 systems, the onifconsole flag is now set by default
182 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
183 as a login TTY if it is set in the bootloader as an active kernel
184 console. No changes in behavior should result otherwise. To revert to
185 the previous behavior, set ttyu0 to "off" in /etc/ttys.
188 Clang and llvm have been upgraded to 3.4.1 release.
191 Clang and llvm have been upgraded to 3.4 release.
194 If a Makefile in a tests/ directory was auto-generating a Kyuafile
195 instead of providing an explicit one, this would prevent such
196 Makefile from providing its own Kyuafile in the future during
197 NO_CLEAN builds. This has been fixed in the Makefiles but manual
198 intervention is needed to clean an objdir if you use NO_CLEAN:
199 # find /usr/obj -name Kyuafile | xargs rm -f
202 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
203 capability mode support. Please note that enabling the feature in
204 kernel is still highly recommended.
207 OpenSSH is now built with sandbox support, and will use sandbox as
208 the default privilege separation method. This requires Capsicum
209 capability mode support in kernel.
212 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
213 been deprecated and will not be part of FreeBSD 11.0 and later
214 releases. If you use this driver, please consider switching to
215 the nfe(4) driver instead.
221 The behavior of gss_pseudo_random() for the krb5 mechanism
222 has changed, for applications requesting a longer random string
223 than produced by the underlying enctype's pseudo-random() function.
224 In particular, the random string produced from a session key of
225 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
226 be different at the 17th octet and later, after this change.
227 The counter used in the PRF+ construction is now encoded as a
228 big-endian integer in accordance with RFC 4402.
229 __FreeBSD_version is bumped to 1000701.
232 The WITHOUT_ATF build knob has been removed and its functionality
233 has been subsumed into the more generic WITHOUT_TESTS. If you were
234 using the former to disable the build of the ATF libraries, you
235 should change your settings to use the latter.
238 The default version of mtree is nmtree which is obtained from
239 NetBSD. The output is generally the same, but may vary
240 slightly. If you found you need identical output adding
241 "-F freebsd9" to the command line should do the trick. For the
242 time being, the old mtree is available as fmtree.
245 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
246 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
247 1.1.4_8 and verify bsdyml not linked in, before running "make
249 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
251 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
254 The rc.d/jail script has been updated to support jail(8)
255 configuration file. The "jail_<jname>_*" rc.conf(5) variables
256 for per-jail configuration are automatically converted to
257 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
258 This is transparently backward compatible. See below about some
259 incompatibilities and rc.conf(5) manual page for more details.
261 These variables are now deprecated in favor of jail(8) configuration
262 file. One can use "rc.d/jail config <jname>" command to generate
263 a jail(8) configuration file in /var/run/jail.<jname>.conf without
264 running the jail(8) utility. The default pathname of the
265 configuration file is /etc/jail.conf and can be specified by
266 using $jail_conf or $jail_<jname>_conf variables.
268 Please note that jail_devfs_ruleset accepts an integer at
269 this moment. Please consider to rewrite the ruleset name
273 BIND has been removed from the base system. If all you need
274 is a local resolver, simply enable and start the local_unbound
275 service instead. Otherwise, several versions of BIND are
276 available in the ports tree. The dns/bind99 port is one example.
278 With this change, nslookup(1) and dig(1) are no longer in the base
279 system. Users should instead use host(1) and drill(1) which are
280 in the base system. Alternatively, nslookup and dig can
281 be obtained by installing the dns/bind-tools port.
284 With the addition of unbound(8), a new unbound user is now
285 required during installworld. "mergemaster -p" can be used to
286 add the user prior to installworld, as documented in the handbook.
289 OpenSSH is now built with DNSSEC support, and will by default
290 silently trust signed SSHFP records. This can be controlled with
291 the VerifyHostKeyDNS client configuration setting. DNSSEC support
292 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
295 The GNU Compiler Collection and C++ standard library (libstdc++)
296 are no longer built by default on platforms where clang is the system
297 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
301 The PROCDESC kernel option is now part of the GENERIC kernel
302 configuration and is required for the rwhod(8) to work.
303 If you are using custom kernel configuration, you should include
307 The API and ABI related to the Capsicum framework was modified
308 in backward incompatible way. The userland libraries and programs
309 have to be recompiled to work with the new kernel. This includes the
310 following libraries and programs, but the whole buildworld is
311 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
312 kdump, procstat, rwho, rwhod, uniq.
315 AES-NI intrinsic support has been added to gcc. The AES-NI module
316 has been updated to use this support. A new gcc is required to build
317 the aesni module on both i386 and amd64.
320 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
321 Thus "device padlock_rng" and "device rdrand_rng" should be
322 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
325 WITH_ICONV has been split into two feature sets. WITH_ICONV now
326 enables just the iconv* functionality and is now on by default.
327 WITH_LIBICONV_COMPAT enables the libiconv api and link time
328 compatability. Set WITHOUT_ICONV to build the old way.
329 If you have been using WITH_ICONV before, you will very likely
330 need to turn on WITH_LIBICONV_COMPAT.
333 INVARIANTS option now enables DEBUG for code with OpenSolaris and
334 Illumos origin, including ZFS. If you have INVARIANTS in your
335 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
337 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
338 locks if WITNESS option was set. Because that generated a lot of
339 witness(9) reports and all of them were believed to be false
340 positives, this is no longer done. New option OPENSOLARIS_WITNESS
341 can be used to achieve the previous behavior.
344 Timer values in IPv6 data structures now use time_uptime instead
345 of time_second. Although this is not a user-visible functional
346 change, userland utilities which directly use them---ndp(8),
347 rtadvd(8), and rtsold(8) in the base system---need to be updated
351 find -delete can now delete the pathnames given as arguments,
352 instead of only files found below them or if the pathname did
353 not contain any slashes. Formerly, the following error message
356 find: -delete: <path>: relative path potentially not safe
358 Deleting the pathnames given as arguments can be prevented
359 without error messages using -mindepth 1 or by changing
360 directory and passing "." as argument to find. This works in the
361 old as well as the new version of find.
364 Behavior of devfs rules path matching has been changed.
365 Pattern is now always matched against fully qualified devfs
366 path and slash characters must be explicitly matched by
367 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
368 subdirectories must be reviewed.
371 The default ARM ABI has changed to the ARM EABI. The old ABI is
372 incompatible with the ARM EABI and all programs and modules will
373 need to be rebuilt to work with a new kernel.
375 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
377 NOTE: Support for the old ABI will be removed in the future and
378 users are advised to upgrade.
381 pkg_install has been disconnected from the build if you really need it
382 you should add WITH_PKGTOOLS in your src.conf(5).
385 Most of network statistics structures were changed to be able
386 keep 64-bits counters. Thus all tools, that work with networking
387 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
390 Fix targets that run multiple make's to use && rather than ;
391 so that subsequent steps depend on success of previous.
393 NOTE: if building 'universe' with -j* on stable/8 or stable/9
394 it would be better to start the build using bmake, to avoid
395 overloading the machine.
398 Fix a bug that allowed a tracing process (e.g. gdb) to write
399 to a memory-mapped file in the traced process's address space
400 even if neither the traced process nor the tracing process had
401 write access to that file.
404 CVS has been removed from the base system. An exact copy
405 of the code is available from the devel/cvs port.
408 Some people report the following error after the switch to bmake:
410 make: illegal option -- J
411 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
413 *** [buildworld] Error code 2
415 this likely due to an old instance of make in
416 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
417 which src/Makefile will use that blindly, if it exists, so if
418 you see the above error:
420 rm -rf `make -V MAKEPATH`
425 Use bmake by default.
426 Whereas before one could choose to build with bmake via
427 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
428 make. The goal is to remove these knobs for 10-RELEASE.
430 It is worth noting that bmake (like gmake) treats the command
431 line as the unit of failure, rather than statements within the
432 command line. Thus '(cd some/where && dosomething)' is safer
433 than 'cd some/where; dosomething'. The '()' allows consistent
434 behavior in parallel build.
437 Fix a bug that allows NFS clients to issue READDIR on files.
440 The WITHOUT_IDEA option has been removed because
441 the IDEA patent expired.
444 The sysctl which controls TRIM support under ZFS has been renamed
445 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
449 The mergemaster command now uses the default MAKEOBJDIRPREFIX
450 rather than creating it's own in the temporary directory in
451 order allow access to bootstrapped versions of tools such as
452 install and mtree. When upgrading from version of FreeBSD where
453 the install command does not support -l, you will need to
454 install a new mergemaster command if mergemaster -p is required.
455 This can be accomplished with the command (cd src/usr.sbin/mergemaster
459 Legacy ATA stack, disabled and replaced by new CAM-based one since
460 FreeBSD 9.0, completely removed from the sources. Kernel modules
461 atadisk and atapi*, user-level tools atacontrol and burncd are
462 removed. Kernel option `options ATA_CAM` is now permanently enabled
466 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
467 and socketpair(2). Software, in particular Kerberos, may
468 automatically detect and use these during building. The resulting
469 binaries will not work on older kernels.
472 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
473 information, see the respective 20130304 entry).
476 Recent commits to callout(9) changed the size of struct callout,
477 so the KBI is probably heavily disturbed. Also, some functions
478 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
479 by macros. Every kernel module using it won't load, so rebuild
482 The ctl device has been re-enabled in GENERIC for i386 and amd64,
483 but does not initialize by default (because of the new CTL_DISABLE
484 option) to save memory. To re-enable it, remove the CTL_DISABLE
485 option from the kernel config file or set kern.cam.ctl.disable=0
486 in /boot/loader.conf.
489 The ctl device has been disabled in GENERIC for i386 and amd64.
490 This was done due to the extra memory being allocated at system
491 initialisation time by the ctl driver which was only used if
492 a CAM target device was created. This makes a FreeBSD system
493 unusable on 128MB or less of RAM.
496 A new compression method (lz4) has been merged to -HEAD. Please
497 refer to zpool-features(7) for more information.
499 Please refer to the "ZFS notes" section of this file for information
500 on upgrading boot ZFS pools.
503 A BSD-licensed patch(1) variant has been added and is installed
504 as bsdpatch, being the GNU version the default patch.
505 To inverse the logic and use the BSD-licensed one as default,
506 while having the GNU version installed as gnupatch, rebuild
507 and install world with the WITH_BSD_PATCH knob set.
510 Due to the use of the new -l option to install(1) during build
511 and install, you must take care not to directly set the INSTALL
512 make variable in your /etc/make.conf, /etc/src.conf, or on the
513 command line. If you wish to use the -C flag for all installs
514 you may be able to add INSTALL+=-C to /etc/make.conf or
518 The install(1) option -M has changed meaning and now takes an
519 argument that is a file or path to append logs to. In the
520 unlikely event that -M was the last option on the command line
521 and the command line contained at least two files and a target
522 directory the first file will have logs appended to it. The -M
523 option served little practical purpose in the last decade so its
524 use is expected to be extremely rare.
527 After switching to Clang as the default compiler some users of ZFS
528 on i386 systems started to experience stack overflow kernel panics.
529 Please consider using 'options KSTACK_PAGES=4' in such configurations.
532 GEOM_LABEL now mangles label names read from file system metadata.
533 Mangling affect labels containing spaces, non-printable characters,
534 '%' or '"'. Device names in /etc/fstab and other places may need to
538 By default, only the 10 most recent kernel dumps will be saved. To
539 restore the previous behaviour (no limit on the number of kernel dumps
540 stored in the dump directory) add the following line to /etc/rc.conf:
545 With the addition of auditdistd(8), a new auditdistd user is now
546 required during installworld. "mergemaster -p" can be used to
547 add the user prior to installworld, as documented in the handbook.
550 The sin6_scope_id member variable in struct sockaddr_in6 is now
551 filled by the kernel before passing the structure to the userland via
552 sysctl or routing socket. This means the KAME-specific embedded scope
553 id in sin6_addr.s6_addr[2] is always cleared in userland application.
554 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
555 __FreeBSD_version is bumped to 1000025.
558 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
559 This means that the world and kernel will be compiled with clang
560 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
561 and /usr/bin/cpp. To disable this behavior and revert to building
562 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
563 of current may need to bootstrap WITHOUT_CLANG first if the clang
564 build fails (its compatibility window doesn't extend to the 9 stable
568 The IPFIREWALL_FORWARD kernel option has been removed. Its
569 functionality now turned on by default.
572 The ZERO_COPY_SOCKET kernel option has been removed and
573 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
574 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
575 mechanism which is not safe and may result in kernel crashes.
576 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
577 driver supports disposeable external page sized mbuf storage.
578 Proper replacements for both zero-copy mechanisms are under
579 consideration and will eventually lead to complete removal
580 of the two kernel options.
583 The IPv4 network stack has been converted to network byte
584 order. The following modules need to be recompiled together
585 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
586 pf(4), ipfw(4), ng_ipfw(4), stf(4).
589 Support for non-MPSAFE filesystems was removed from VFS. The
590 VFS_VERSION was bumped, all filesystem modules shall be
594 All the non-MPSAFE filesystems have been disconnected from
595 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
596 portalfs, smbfs, xfs.
599 The interface cloning API and ABI has changed. The following
600 modules need to be recompiled together with kernel:
601 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
602 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
603 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
606 The sdhci driver was split in two parts: sdhci (generic SD Host
607 Controller logic) and sdhci_pci (actual hardware driver).
608 No kernel config modifications are required, but if you
609 load sdhc as a module you must switch to sdhci_pci instead.
612 Import the FUSE kernel and userland support into base system.
615 The GNU sort(1) program has been removed since the BSD-licensed
616 sort(1) has been the default for quite some time and no serious
617 problems have been reported. The corresponding WITH_GNU_SORT
621 The pfil(9) API/ABI for AF_INET family has been changed. Packet
622 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
626 The net80211(4) ABI has been changed to allow for improved driver
627 PS-POLL and power-save support. All wireless drivers need to be
628 recompiled to work with the new kernel.
631 The random(4) support for the VIA hardware random number
632 generator (`PADLOCK') is no longer enabled unconditionally.
633 Add the padlock_rng device in the custom kernel config if
634 needed. The GENERIC kernels on i386 and amd64 do include the
635 device, so the change only affects the custom kernel
639 The pf(4) packet filter ABI has been changed. pfctl(8) and
640 snmp_pf module need to be recompiled to work with new kernel.
643 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
644 to -HEAD. Pools that have empty_bpobj in active state can not be
645 imported read-write with ZFS implementations that do not support
646 this feature. For more information read the zpool-features(5)
650 The sparc64 ZFS loader has been changed to no longer try to auto-
651 detect ZFS providers based on diskN aliases but now requires these
652 to be explicitly listed in the OFW boot-device environment variable.
655 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
656 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
657 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
660 The following sysctls and tunables have been renamed for consistency
661 with other variables:
662 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
663 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
666 The sort utility has been replaced with BSD sort. For now, GNU sort
667 is also available as "gnusort" or the default can be set back to
668 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
669 installed as "bsdsort".
672 A new version of ZFS (pool version 5000) has been merged to -HEAD.
673 Starting with this version the old system of ZFS pool versioning
674 is superseded by "feature flags". This concept enables forward
675 compatibility against certain future changes in functionality of ZFS
676 pools. The first read-only compatible "feature flag" for ZFS pools
677 is named "com.delphix:async_destroy". For more information
678 read the new zpool-features(5) manual page.
679 Please refer to the "ZFS notes" section of this file for information
680 on upgrading boot ZFS pools.
683 The malloc(3) implementation embedded in libc now uses sources imported
684 as contrib/jemalloc. The most disruptive API change is to
685 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
686 delete it prior to installworld, and optionally re-create it using the
687 new format after rebooting. See malloc.conf(5) for details
688 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
692 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
693 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
694 now spelled mips. This is to aid compatibility with third-party
695 software that expects this naming scheme in uname(3). Little-endian
696 settings are unchanged. If you are updating a big-endian mips64 machine
697 from before this change, you may need to set MACHINE_ARCH=mips64 in
698 your environment before the new build system will recognize your machine.
701 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
705 Now unix domain sockets behave "as expected" on nullfs(5). Previously
706 nullfs(5) did not pass through all behaviours to the underlying layer,
707 as a result if we bound to a socket on the lower layer we could connect
708 only to the lower path; if we bound to the upper layer we could connect
709 only to the upper path. The new behavior is one can connect to both the
710 lower and the upper paths regardless what layer path one binds to.
713 The getifaddrs upgrade path broken with 20111215 has been restored.
714 If you have upgraded in between 20111215 and 20120209 you need to
715 recompile libc again with your kernel. You still need to recompile
716 world to be able to configure CARP but this restriction already
720 The set_rcvar() function has been removed from /etc/rc.subr. All
721 base and ports rc.d scripts have been updated, so if you have a
722 port installed with a script in /usr/local/etc/rc.d you can either
723 hand-edit the rcvar= line, or reinstall the port.
725 An easy way to handle the mass-update of /etc/rc.d:
726 rm /etc/rc.d/* && mergemaster -i
729 panic(9) now stops other CPUs in the SMP systems, disables interrupts
730 on the current CPU and prevents other threads from running.
731 This behavior can be reverted using the kern.stop_scheduler_on_panic
733 The new behavior can be incompatible with kern.sync_on_panic.
736 The carp(4) facility has been changed significantly. Configuration
737 of the CARP protocol via ifconfig(8) has changed, as well as format
738 of CARP events submitted to devd(8) has changed. See manual pages
739 for more information. The arpbalance feature of carp(4) is currently
740 not supported anymore.
742 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
743 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
744 need to be recompiled.
747 The acpi_wmi(4) status device /dev/wmistat has been renamed to
751 The option VFS_ALLOW_NONMPSAFE option has been added in order to
752 explicitely support non-MPSAFE filesystems.
753 It is on by default for all supported platform at this present
757 The broken amd(4) driver has been replaced with esp(4) in the amd64,
758 i386 and pc98 GENERIC kernel configuration files.
761 sysinstall has been removed
764 The stable/9 branch created in subversion. This corresponds to the
765 RELENG_9 branch in CVS.
768 This commit modifies vfs_register() so that it uses a hash
769 calculation to set vfc_typenum, which is enabled by default.
770 The first time a system is booted after this change, the
771 vfc_typenum values will change for all file systems. The
772 main effect of this is a change to the NFS server file handles
773 for file systems that use vfc_typenum in their fsid, such as ZFS.
774 It will, however, prevent vfc_typenum from changing when file
775 systems are loaded in a different order for subsequent reboots.
776 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
777 until you are ready to remount all NFS clients after a reboot.
780 Bump the shared library version numbers for libraries that
781 do not use symbol versioning, have changed the ABI compared
782 to stable/8 and which shared library version was not bumped.
783 Done as part of 9.0-RELEASE cycle.
786 During the merge of Capsicum features, the fget(9) KPI was modified.
787 This may require the rebuilding of out-of-tree device drivers --
788 issues have been reported specifically with the nVidia device driver.
789 __FreeBSD_version is bumped to 900041.
791 Also, there is a period between 20110811 and 20110814 where the
792 special devices /dev/{stdin,stdout,stderr} did not work correctly.
793 Building world from a kernel during that window may not work.
796 The packet filter (pf) code has been updated to OpenBSD 4.5.
797 You need to update userland tools to be in sync with kernel.
798 This update breaks backward compatibility with earlier pfsync(4)
799 versions. Care must be taken when updating redundant firewall setups.
802 The following sysctls and tunables are retired on x86 platforms:
804 machdep.hlt_logical_cpus
805 The following sysctl is retired:
806 machdep.hyperthreading_allowed
807 The sysctls were supposed to provide a way to dynamically offline and
808 online selected CPUs on x86 platforms, but the implementation has not
809 been reliable especially with SCHED_ULE scheduler.
810 machdep.hyperthreading_allowed tunable is still available to ignore
811 hyperthreading CPUs at OS level.
812 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
813 where X is an APIC ID of a CPU. Be advised, though, that disabling
814 CPUs in non-uniform fashion will result in non-uniform topology and
815 may lead to sub-optimal system performance with SCHED_ULE, which is
819 cpumask_t type is retired and cpuset_t is used in order to describe
823 Changes to ifconfig(8) for dynamic address family detection mandate
824 that you are running a kernel of 20110525 or later. Make sure to
825 follow the update procedure to boot a new kernel before installing
829 Support for sun4v architecture is officially dropped
832 Several KPI breaking changes have been committed to the mii(4) layer,
833 the PHY drivers and consequently some Ethernet drivers using mii(4).
834 This means that miibus.ko and the modules of the affected Ethernet
835 drivers need to be recompiled.
837 Note to kernel developers: Given that the OUI bit reversion problem
838 was fixed as part of these changes all mii(4) commits related to OUIs,
839 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
840 handling, no longer can be merged verbatim to stable/8 and previous
844 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
845 into their kernel configurations along with 'device pci'.
848 The default NFS client is now the new NFS client, so fstype "newnfs"
849 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
850 Although mounts via fstype "nfs" will usually work without userland
851 changes, it is recommended that the mount(8) and mount_nfs(8)
852 commands be rebuilt from sources and that a link to mount_nfs called
853 mount_oldnfs be created. The new client is compiled into the
854 kernel with "options NFSCL" and this is needed for diskless root
855 file systems. The GENERIC kernel configs have been changed to use
856 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
857 To use the regular/old client, you can "mount -t oldnfs ...". For
858 a diskless root file system, you must also include a line like:
860 vfs.root.mountfrom="oldnfs:"
862 in the boot/loader.conf on the root fs on the NFS server to make
863 a diskless root fs use the old client.
866 The GENERIC kernels for all architectures now default to the new
867 CAM-based ATA stack. It means that all legacy ATA drivers were
868 removed and replaced by respective CAM drivers. If you are using
869 ATA device names in /etc/fstab or other places, make sure to update
870 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
871 where 'Y's are the sequential numbers starting from zero for each type
872 in order of detection, unless configured otherwise with tunables,
873 see cam(4)). There will be symbolic links created in /dev/ to map
874 old adX devices to the respective adaY. They should provide basic
875 compatibility for file systems mounting in most cases, but they do
876 not support old user-level APIs and do not have respective providers
877 in GEOM. Consider using updated management tools with new device names.
879 It is possible to load devices ahci, ata, siis and mvs as modules,
880 but option ATA_CAM should remain in kernel configuration to make ata
881 module work as CAM driver supporting legacy ATA controllers. Device ata
882 still can be used in modular fashion (atacore + ...). Modules atadisk
883 and atapi* are not used and won't affect operation in ATA_CAM mode.
884 Note that to use CAM-based ATA kernel should include CAM devices
885 scbus, pass, da (or explicitly ada), cd and optionally others. All of
886 them are parts of the cam module.
888 ataraid(4) functionality is now supported by the RAID GEOM class.
889 To use it you can load geom_raid kernel module and use graid(8) tool
890 for management. Instead of /dev/arX device names, use /dev/raid/rX.
892 No kernel config options or code have been removed, so if a problem
893 arises, please report it and optionally revert to the old ATA stack.
894 In order to do it you can remove from the kernel config:
899 , and instead add back:
900 device atadisk # ATA disk drives
901 device ataraid # ATA RAID drives
902 device atapicd # ATAPI CDROM drives
903 device atapifd # ATAPI floppy drives
904 device atapist # ATAPI tape drives
907 The default NFS server has been changed to the new server, which
908 was referred to as the experimental server. If you need to switch
909 back to the old NFS server, you must now put the "-o" option on
910 both the mountd and nfsd commands. This can be done using the
911 mountd_flags and nfs_server_flags rc.conf variables until an
912 update to the rc scripts is committed, which is coming soon.
915 The GNU Objective-C runtime library (libobjc), and other Objective-C
916 related components have been removed from the base system. If you
917 require an Objective-C library, please use one of the available ports.
920 ath(4) has been split into bus- and device- modules. if_ath contains
921 the HAL, the TX rate control and the network device code. if_ath_pci
922 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
923 contains the AHB glue. Users need to load both if_ath_pci and if_ath
924 in order to use ath on everything else.
926 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
927 need to load if_ath and if_ath_pci for ath(4) operation.
930 As part of the replacement of sysinstall, the process of building
931 release media has changed significantly. For details, please re-read
932 release(7), which has been updated to reflect the new build process.
935 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
936 is the last available version under GPLv2. It brings a number of new
937 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
938 4.1 and SSE 4.2), better support for powerpc64, a number of new
939 directives, and lots of other small improvements. See the ChangeLog
940 file in contrib/binutils for the full details.
943 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
944 compliant, and will now use half of hash for authentication.
945 This will break interoperability with all stacks (including all
946 actual FreeBSD versions) who implement
947 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
949 The only workaround with such peers is to use another HMAC
950 algorithm for IPsec ("phase 2") authentication.
953 Remove the uio_yield prototype and symbol. This function has
954 been misnamed since it was introduced and should not be
955 globally exposed with this name. The equivalent functionality
956 is now available using kern_yield(curthread->td_user_pri).
957 The function remains undocumented.
960 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
961 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
962 for scalar sysctls is defined but disabled. Code that needs
963 UQUAD to pass the type checking that must compile on older
964 systems where the define is not present can check against
965 __FreeBSD_version >= 900030.
967 The system dialog(1) has been replaced with a new version previously
968 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
969 with the previous version, but the libdialog associated with it has
970 a largely incompatible API. As such, the original version of libdialog
971 will be kept temporarily as libodialog, until its base system consumers
972 are replaced or updated. Bump __FreeBSD_version to 900030.
975 If you are trying to run make universe on a -stable system, and you get
976 the following warning:
977 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
978 unknown. config(8) likely too old."
979 or something similar to it, then you must upgrade your -stable system
980 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
981 stable/8) or build the config from the latest stable/8 branch and
982 install it on your system.
984 Prior to this date, building a current universe on 8-stable system from
985 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
986 error in the first kernel build phase. A new config on those old
987 systems will fix that problem for older versions of -current.
990 The TCP stack has been modified to allow Khelp modules to interact with
991 it via helper hook points and store per-connection data in the TCP
992 control block. Bump __FreeBSD_version to 900029. User space tools that
993 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
997 Generic IEEE 802.3 annex 31B full duplex flow control support has been
998 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
999 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1000 to take advantage of it instead of using custom implementations. This
1001 means that these drivers now no longer unconditionally advertise
1002 support for flow control but only do so if flow control is a selected
1003 media option. This was implemented in the generic support that way in
1004 order to allow flow control to be switched on and off via ifconfig(8)
1005 with the PHY specific default to typically off in order to protect
1006 from unwanted effects. Consequently, if you used flow control with
1007 one of the above mentioned drivers you now need to explicitly enable
1008 it, for example via:
1009 ifconfig bge0 media auto mediaopt flowcontrol
1011 Along with the above mentioned changes generic support for setting
1012 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1013 e1000phy(4) as well as ip1000phy(4) have been converted to take
1014 advantage of it. This means that these drivers now no longer take the
1015 link0 parameter for selecting master mode but the master media option
1016 has to be used instead, for example like in the following:
1017 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1019 Selection of master mode now is also available with all other PHY
1020 drivers supporting 1000baseT.
1023 The TCP stack has received a significant update to add support for
1024 modularised congestion control and generally improve the clarity of
1025 congestion control decisions. Bump __FreeBSD_version to 900025. User
1026 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1027 sockstat) need to be recompiled.
1030 The man(1) utility has been replaced by a new version that no longer
1031 uses /etc/manpath.config. Please consult man.conf(5) for how to
1032 migrate local entries to the new format.
1035 The copyright strings printed by login(1) and sshd(8) at the time of a
1036 new connection have been removed to follow other operating systems and
1040 A workaround for a fixed ld bug has been removed in kernel code,
1041 so make sure that your system ld is built from sources after
1042 revision 210245 from 2010-07-19 (r211583 if building head kernel
1043 on stable/8, r211584 for stable/7; both from 2010-08-21).
1044 A symptom of incorrect ld version is different addresses for
1045 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1048 The $ipv6_prefer variable in rc.conf(5) has been split into
1049 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1051 The $ip6addrctl_policy is a variable to choose a pre-defined
1052 address selection policy set by ip6addrctl(8). A value
1053 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1056 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1057 flag (see an entry of 20090926) is set on an interface with no
1058 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1059 security reason. If you want IPv6 link-local address on all
1060 interfaces by default, set this to "YES".
1062 The old ipv6_prefer="YES" is equivalent to
1063 ipv6_activate_all_interfaces="YES" and
1064 ip6addrctl_policy="ipv6_prefer".
1067 DTrace has grown support for userland tracing. Due to this, DTrace is
1068 now i386 and amd64 only.
1069 dtruss(1) is now installed by default on those systems and a new
1070 kernel module is needed for userland tracing: fasttrap.
1071 No changes to your kernel config file are necessary to enable
1072 userland tracing, but you might consider adding 'STRIP=' and
1073 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1074 to have informative userland stack traces in DTrace (ustack).
1077 The acpi_aiboost(4) driver has been removed in favor of the new
1078 aibs(4) driver. You should update your kernel configuration file.
1081 BSD grep has been imported to the base system and it is built by
1082 default. It is completely BSD licensed, highly GNU-compatible, uses
1083 less memory than its GNU counterpart and has a small codebase.
1084 However, it is slower than its GNU counterpart, which is mostly
1085 noticeable for larger searches, for smaller ones it is measurable
1086 but not significant. The reason is complex, the most important factor
1087 is that we lack a modern and efficient regex library and GNU
1088 overcomes this by optimizing the searches internally. Future work
1089 on improving the regex performance is planned, for the meantime,
1090 users that need better performance, can build GNU grep instead by
1091 setting the WITH_GNU_GREP knob.
1094 Due to the import of powerpc64 support, all existing powerpc kernel
1095 configuration files must be updated with a machine directive like this:
1096 machine powerpc powerpc
1098 In addition, an updated config(8) is required to build powerpc kernels
1102 A new version of ZFS (version 15) has been merged to -HEAD.
1103 This version uses a python library for the following subcommands:
1104 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1105 For full functionality of these commands the following port must
1106 be installed: sysutils/py-zfs
1109 'vm_page's are now hashed by physical address to an array of mutexes.
1110 Currently this is only used to serialize access to hold_count. Over
1111 time the page queue mutex will be peeled away. This changes the size
1112 of pmap on every architecture. And requires all callers of vm_page_hold
1113 and vm_page_unhold to be updated.
1116 WITH_CTF can now be specified in src.conf (not recommended, there
1117 are some problems with static executables), make.conf (would also
1118 affect ports which do not use GNU make and do not override the
1119 compile targets) or in the kernel config (via "makeoptions
1121 When WITH_CTF was specified there before this was silently ignored,
1122 so make sure that WITH_CTF is not used in places which could lead
1123 to unwanted behavior.
1126 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1127 to allow 32-bit compatibility on non-x86 platforms. All kernel
1128 configurations on amd64 and ia64 platforms using these options must
1129 be modified accordingly.
1132 The utmp user accounting database has been replaced with utmpx,
1133 the user accounting interface standardized by POSIX.
1134 Unfortunately the semantics of utmp and utmpx don't match,
1135 making it practically impossible to support both interfaces.
1136 The user accounting database is used by tools like finger(1),
1137 last(1), talk(1), w(1) and ac(8).
1139 All applications in the base system use utmpx. This means only
1140 local binaries (e.g. from the ports tree) may still use these
1141 utmp database files. These applications must be rebuilt to make
1144 After the system has been upgraded, it is safe to remove the old
1145 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1146 assuming their contents is of no importance anymore. Old wtmp
1147 databases can only be used by last(1) and ac(8) after they have
1148 been converted to the new format using wtmpcvt(1).
1151 Introduce the kernel thread "deadlock resolver" (which can be enabled
1152 via the DEADLKRES option, see NOTES for more details) and the
1153 sleepq_type() function for sleepqueues.
1156 The rc.firewall and rc.firewall6 were unified, and
1157 rc.firewall6 and rc.d/ip6fw were removed.
1158 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1159 variables are obsoleted. Instead, the following new rc
1160 variables are added to rc.d/ipfw:
1162 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1163 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1164 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1166 The meanings correspond to the relevant IPv4 variables.
1172 The default terminal emulation for syscons(4) has been changed
1173 from cons25 to xterm on all platforms except pc98. This means
1174 that the /etc/ttys file needs to be updated to ensure correct
1175 operation of applications on the console.
1177 The terminal emulation style can be toggled per window by using
1178 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1179 options can be used to change the compile-time default back to
1182 To prevent graphical artifacts, make sure the TERM environment
1183 variable is set to match the terminal emulation that is being
1184 performed by syscons(4).
1187 The layout of the structure ieee80211req_scan_result has changed.
1188 Applications that require wireless scan results (e.g. ifconfig(8))
1189 from net80211 need to be recompiled.
1191 Applications such as wpa_supplicant(8) may require a full world
1192 build without using NO_CLEAN in order to get synchronized with the
1196 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1197 There's one kernel module for each firmware. Adding "device iwnfw"
1198 to the kernel configuration file means including all three firmware
1199 images inside the kernel. If you want to include just the one for
1200 your wireless card, use the devices iwn4965fw, iwn5000fw or
1204 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1205 into rc.d/netif. The changes are the following:
1207 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1208 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1209 Note that both variables need the "inet6" keyword at the head.
1211 Do not set $ipv6_network_interfaces manually if you do not
1212 understand what you are doing. It is not needed in most cases.
1214 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1217 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1218 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1220 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1221 all configured interfaces have "inet6 accept_rtadv" in the
1222 $ifconfig_IF_ipv6. These are for backward compatibility.
1224 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1225 functionality of interfaces with no corresponding
1226 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1227 and the default address selection policy of ip6addrctl(8)
1228 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1229 Note that if you want to configure IPv6 functionality on the
1230 disabled interfaces after boot, first you need to clear the flag by
1231 using ifconfig(8) like:
1233 ifconfig em0 inet6 -ifdisabled
1235 If YES, the default address selection policy is set as
1238 The default value of $ipv6_prefer is NO.
1240 4. If your system need to receive Router Advertisement messages,
1241 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1242 scripts automatically invoke rtsol(8) when the interface becomes
1243 UP. The Router Advertisement messages are used for SLAAC
1244 (State-Less Address AutoConfiguration).
1247 802.11s D3.03 support was committed. This is incompatible with the
1248 previous code, which was based on D3.0.
1251 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1252 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1253 control whether accepting Router Advertisement messages or not.
1254 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1255 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1256 The ifconfig(8) utility now supports these flags.
1259 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1260 mount(8) and -a option for df(1) to see them.
1263 The old tunable hw.bus.devctl_disable has been superseded by
1264 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1265 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1269 Remove the option STOP_NMI. The default action is now to use NMI only
1270 for KDB via the newly introduced function stop_cpus_hard() and
1271 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1274 The stable/8 branch created in subversion. This corresponds to the
1275 RELENG_8 branch in CVS.
1278 Bump the shared library version numbers for all libraries that do not
1279 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1280 __FreeBSD_version to 800105.
1283 Due to changes in the implementation of virtual network stack support,
1284 all network-related kernel modules must be recompiled. As this change
1285 breaks the ABI, bump __FreeBSD_version to 800104.
1288 The TOE interface to the TCP syncache has been modified to remove
1289 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1290 The cxgb driver is the only TOE consumer affected by this change, and
1291 needs to be recompiled along with the kernel. As this change breaks
1292 the ABI, bump __FreeBSD_version to 800103.
1295 Padding has been added to struct tcpcb, sackhint and tcpstat in
1296 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1297 maintaining the ABI. However, this change breaks the ABI, so bump
1298 __FreeBSD_version to 800102. User space tools that rely on the size of
1299 any of these structs (e.g. sockstat) need to be recompiled.
1302 The NFS_LEGACYRPC option has been removed along with the old kernel
1303 RPC implementation that this option selected. Kernel configurations
1304 may need to be adjusted.
1307 The network interface device nodes at /dev/net/<interface> have been
1308 removed. All ioctl operations can be performed the normal way using
1309 routing sockets. The kqueue functionality can generally be replaced
1310 with routing sockets.
1313 The documentation from the FreeBSD Documentation Project (Handbook,
1314 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1315 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1318 The ABI of various structures related to the SYSV IPC API have been
1319 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1320 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1324 Layout of struct vnet has changed as routing related variables were
1325 moved to their own Vimage module. Modules need to be recompiled. Bump
1326 __FreeBSD_version to 800099.
1329 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1330 respectively. As long as no more than 16 groups per process are used,
1331 no changes should be visible. When more than 16 groups are used, old
1332 binaries may fail if they call getgroups() or getgrouplist() with
1333 statically sized storage. Recompiling will work around this, but
1334 applications should be modified to use dynamically allocated storage
1335 for group arrays as POSIX.1-2008 does not cap an implementation's
1336 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1338 NFS and portalfs mounts may also be affected as the list of groups is
1339 truncated to 16. Users of NFS who use more than 16 groups, should
1340 take care that negative group permissions are not used on the exported
1341 file systems as they will not be reliable unless a GSSAPI based
1342 authentication method is used.
1345 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1346 option compiles in the support for adaptive spinning for lockmgrs
1347 which want to enable it. The lockinit() function now accepts the flag
1348 LK_ADAPTIVE in order to make the lock object subject to adaptive
1349 spinning when both held in write and read mode.
1352 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1353 changed. User applications that use this ioctl need to be rebuilt.
1356 The layout of struct thread has changed. Kernel and modules need to
1360 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1361 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1364 window(1) has been removed from the base system. It can now be
1365 installed from ports. The port is called misc/window.
1368 The way we are storing and accessing `routing table' entries has
1369 changed. Programs reading the FIB, like netstat, need to be
1373 A new netisr implementation has been added for FreeBSD 8. Network
1374 file system modules, such as igmp, ipdivert, and others, should be
1376 Bump __FreeBSD_version to 800096.
1379 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1383 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1384 Bump __FreeBSD_version to 800094.
1387 Add mnt_xflag field to 'struct mount'. File system modules need to be
1389 Bump __FreeBSD_version to 800093.
1392 The compiling option ADAPTIVE_SX has been retired while it has been
1393 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1394 The KPI for sx_init_flags() changes as accepting flags:
1395 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1396 been introduced in order to handle the reversed logic.
1397 Bump __FreeBSD_version to 800092.
1400 Add support for hierarchical jails. Remove global securelevel.
1401 Bump __FreeBSD_version to 800091.
1404 The layout of struct vnet_net has changed, therefore modules
1406 Bump __FreeBSD_version to 800090.
1409 The newly imported zic(8) produces a new format in the output. Please
1410 run tzsetup(8) to install the newly created data to /etc/localtime.
1413 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1414 hw.usb.* and is now consistent again with previous releases.
1417 802.11 monitor mode support was revised and driver api's were changed.
1418 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1419 of DLT_IEEE802_11. No user-visible data structures were changed but
1420 applications that use DLT_IEEE802_11 may require changes.
1421 Bump __FreeBSD_version to 800088.
1424 The layout of the following structs has changed: sysctl_oid,
1425 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1426 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1427 panics may be experienced. World rebuild is required for
1428 correctly checking networking state from userland.
1429 Bump __FreeBSD_version to 800085.
1432 MLDv2 and Source-Specific Multicast (SSM) have been merged
1433 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1434 The implementation of SSM within FreeBSD's IPv6 stack closely
1435 follows the IPv4 implementation.
1437 For kernel developers:
1439 * The most important changes are that the ip6_output() and
1440 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1441 and this lock has been downgraded to a non-recursive mutex.
1443 * As with the changes to the IPv4 stack to support SSM, filtering
1444 of inbound multicast traffic must now be performed by transport
1445 protocols within the IPv6 stack. This does not apply to TCP and
1446 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1448 * The KPIs used by IPv6 multicast are similar to those used by
1449 the IPv4 stack, with the following differences:
1450 * im6o_mc_filter() is analogous to imo_multicast_filter().
1451 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1452 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1453 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1454 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1455 for MLDv1 have an additional 'timer' argument which is used to
1456 jitter the initial membership report for the solicited-node
1457 multicast membership on-link.
1458 * This is not strictly needed for MLDv2, which already jitters
1459 its report transmissions. However, the 'timer' argument is
1460 preserved in case MLDv1 is active on the interface.
1462 * The KAME linked-list based IPv6 membership implementation has
1463 been refactored to use a vector similar to that used by the IPv4
1465 Code which maintains a list of its own multicast memberships
1466 internally, e.g. carp, has been updated to reflect the new
1469 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1470 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1471 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1472 implementation constraint which needs to be addressed in HEAD.
1474 For application developers:
1476 * The changes are broadly similar to those made for the IPv4
1479 * The use of IPv4 and IPv6 multicast socket options on the same
1480 socket, using mapped addresses, HAS NOT been tested or supported.
1482 * There are a number of issues with the implementation of various
1483 IPv6 multicast APIs which need to be resolved in the API surface
1484 before the implementation is fully compatible with KAME userland
1485 use, and these are mostly to do with interface index treatment.
1487 * The literature available discusses the use of either the delta / ASM
1488 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1489 using setsourcefilter(3)/getsourcefilter(3). For more information
1490 please refer to RFC 3768, 'Socket Interface Extensions for
1491 Multicast Source Filters'.
1493 * Applications which use the published RFC 3678 APIs should be fine.
1495 For systems administrators:
1497 * The mtest(8) utility has been refactored to support IPv6, in
1498 addition to IPv4. Interface addresses are no longer accepted
1499 as arguments, their names must be used instead. The utility
1500 will map the interface name to its first IPv4 address as
1501 returned by getifaddrs(3).
1503 * The ifmcstat(8) utility has also been updated to print the MLDv2
1504 endpoint state and source filter lists via sysctl(3).
1506 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1507 loopback of IPv6 multicast datagrams by default; it defaults to 1
1508 to preserve the existing behaviour. Disabling multicast loopback is
1509 recommended for optimal system performance.
1511 * The IPv6 MROUTING code has been changed to examine this sysctl
1512 instead of attempting to perform a group lookup before looping
1513 back forwarded datagrams.
1515 Bump __FreeBSD_version to 800084.
1518 Implement low-level Bluetooth HCI API.
1519 Bump __FreeBSD_version to 800083.
1522 The layout of struct malloc_type, used by modules to register new
1523 memory allocation types, has changed. Most modules will need to
1524 be rebuilt or panics may be experienced.
1525 Bump __FreeBSD_version to 800081.
1528 Anticipate overflowing inp_flags - add inp_flags2.
1529 This changes most offsets in inpcb, so checking v4 connection
1530 state will require a world rebuild.
1531 Bump __FreeBSD_version to 800080.
1534 Add an llentry to struct route and struct route_in6. Modules
1535 embedding a struct route will need to be recompiled.
1536 Bump __FreeBSD_version to 800079.
1539 The size of rt_metrics_lite and by extension rtentry has changed.
1540 Networking administration apps will need to be recompiled.
1541 The route command now supports show as an alias for get, weighting
1542 of routes, sticky and nostick flags to alter the behavior of stateful
1544 Bump __FreeBSD_version to 800078.
1547 Do not use Giant for kbdmux(4) locking. This is wrong and
1548 apparently causing more problems than it solves. This will
1549 re-open the issue where interrupt handlers may race with
1550 kbdmux(4) in polling mode. Typical symptoms include (but
1551 not limited to) duplicated and/or missing characters when
1552 low level console functions (such as gets) are used while
1553 interrupts are enabled (for example geli password prompt,
1554 mountroot prompt etc.). Disabling kbdmux(4) may help.
1557 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1558 kernel modules referencing any of the above need to be recompiled.
1559 Bump __FreeBSD_version to 800075.
1562 GEOM_PART has become the default partition slicer for storage devices,
1563 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1564 introduces some changes:
1566 MSDOS/EBR: the devices created from MSDOS extended partition entries
1567 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1568 to devices with offset-based names. fstabs may need to be modified.
1570 BSD: the "geometry does not match label" warning is harmless in most
1571 cases but it points to problems in file system misalignment with
1572 disk geometry. The "c" partition is now implicit, covers the whole
1573 top-level drive and cannot be (mis)used by users.
1575 General: Kernel dumps are now not allowed to be written to devices
1576 whose partition types indicate they are meant to be used for file
1577 systems (or, in case of MSDOS partitions, as something else than
1580 Most of these changes date approximately from 200812.
1583 The uscanner(4) driver has been removed from the kernel. This follows
1584 Linux removing theirs in 2.6 and making libusb the default interface
1585 (supported by sane).
1588 The multicast forwarding code has been cleaned up. netstat(1)
1589 only relies on KVM now for printing bandwidth upcall meters.
1590 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1591 ip6_mroute_mod respectively. The config(5) options for statically
1592 compiling this code remain the same, i.e. 'options MROUTING'.
1595 Support for the IFF_NEEDSGIANT network interface flag has been
1596 removed, which means that non-MPSAFE network device drivers are no
1597 longer supported. In particular, if_ar, if_sr, and network device
1598 drivers from the old (legacy) USB stack can no longer be built or
1602 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1603 a bunch of new language catalog files have also been added.
1604 This means that some common libc messages are now localized and
1605 they depend on the LC_MESSAGES environmental variable.
1608 The k8temp(4) driver has been renamed to amdtemp(4) since
1609 support for Family 10 and Family 11 CPU families was added.
1612 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1613 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1615 For kernel developers, the most important changes are that the
1616 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1617 and this lock has been downgraded to a non-recursive mutex.
1619 Transport protocols (UDP, Raw IP) are now responsible for filtering
1620 inbound multicast traffic according to group membership and source
1621 filters. The imo_multicast_filter() KPI exists for this purpose.
1622 Transports which do not use multicast (SCTP, TCP) already reject
1623 multicast by default. Forwarding and receive performance may improve
1624 as a mutex acquisition is no longer needed in the ip_input()
1625 low-level input path. in_addmulti() and in_delmulti() are shimmed
1626 to new KPIs which exist to support SSM in-kernel.
1628 For application developers, it is recommended that loopback of
1629 multicast datagrams be disabled for best performance, as this
1630 will still cause the lock to be taken for each looped-back
1631 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1632 be tuned to 0 to disable loopback by default; it defaults to 1
1633 to preserve the existing behaviour.
1635 For systems administrators, to obtain best performance with
1636 multicast reception and multiple groups, it is always recommended
1637 that a card with a suitably precise hash filter is used. Hash
1638 collisions will still result in the lock being taken within the
1639 transport protocol input path to check group membership.
1641 If deploying FreeBSD in an environment with IGMP snooping switches,
1642 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1643 enabled; this forces 224.0.0.0/24 group membership to be announced
1646 The size of 'struct igmpstat' has changed; netstat needs to be
1647 recompiled to reflect this.
1648 Bump __FreeBSD_version to 800070.
1651 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1652 updated to use it. This requires a buildworld/installworld in order to
1653 update the library and dependencies (usbconfig, etc). Its advisable to
1654 rebuild all ports which uses libusb. More specific directions are given
1655 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1656 libusb are no longer required and can be removed.
1659 A workaround is committed to allow the creation of System V shared
1660 memory segment of size > 2 GB on the 64-bit architectures.
1661 Due to a limitation of the existing ABI, the shm_segsz member
1662 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1663 wrong for large segments. Note that limits must be explicitly
1664 raised to allow such segments to be created.
1667 The layout of struct ifnet has changed, requiring a rebuild of all
1668 network device driver modules.
1671 The /dev handling for the new USB stack has changed, a
1672 buildworld/installworld is required for libusb20.
1675 The new USB2 stack has now been permanently moved in and all kernel and
1676 module names reverted to their previous values (eg, usb, ehci, ohci,
1677 ums, ...). The old usb stack can be compiled in by prefixing the name
1678 with the letter 'o', the old usb modules have been removed.
1679 Updating entry 20090216 for xorg and 20090215 for libmap may still
1683 The rc.conf(5) option if_up_delay has been renamed to
1684 defaultroute_delay to better reflect its purpose. If you have
1685 customized this setting in /etc/rc.conf you need to update it to
1689 xorg 7.4 wants to configure its input devices via hald which does not
1690 yet work with USB2. If the keyboard/mouse does not work in xorg then
1692 Option "AllowEmptyInput" "off"
1693 to your ServerLayout section. This will cause X to use the configured
1694 kbd and mouse sections from your xorg.conf.
1697 The GENERIC kernels for all architectures now default to the new USB2
1698 stack. No kernel config options or code have been removed so if a
1699 problem arises please report it and optionally revert to the old USB
1700 stack. If you are loading USB kernel modules or have a custom kernel
1701 that includes GENERIC then ensure that usb names are also changed over,
1702 eg uftdi -> usb2_serial_ftdi.
1704 Older programs linked against the ports libusb 0.1 need to be
1705 redirected to the new stack's libusb20. /etc/libmap.conf can
1707 # Map old usb library to new one for usb2 stack
1708 libusb-0.1.so.8 libusb20.so.1
1711 All USB ethernet devices now attach as interfaces under the name ueN
1712 (eg. ue0). This is to provide a predictable name as vendors often
1713 change usb chipsets in a product without notice.
1716 The ichsmb(4) driver has been changed to require SMBus slave
1717 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1718 All of the other SMBus controller drivers require left-justified
1719 slave addresses, so this change makes all the drivers provide the
1723 INET6 statistics (struct ip6stat) was updated.
1724 netstat(1) needs to be recompiled.
1727 NTFS has been removed from GENERIC kernel on amd64 to match
1728 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1729 will load ntfs.ko module automatically when NTFS support is
1730 actually needed, unless ntfs.ko is not installed or security
1731 level prohibits loading kernel modules. If either is the case,
1732 "options NTFS" has to be added into kernel config.
1735 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1736 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1737 800061. User space tools that rely on the size of struct tcpcb in
1738 tcp_var.h (e.g. sockstat) need to be recompiled.
1741 ng_tty(4) module updated to match the new TTY subsystem.
1742 Due to API change, user-level applications must be updated.
1743 New API support added to mpd5 CVS and expected to be present
1744 in next mpd5.3 release.
1747 With __FreeBSD_version 800060 the makefs tool is part of
1748 the base system (it was a port).
1751 The afdata and ifnet locks have been changed from mutexes to
1752 rwlocks, network modules will need to be re-compiled.
1755 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1756 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1757 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1758 architecture and 40 bytes on 64-bit architecture. The userland
1759 applications "arp" and "ndp" have been updated accordingly.
1760 The output from "netstat -r" shows only routing entries and
1761 none of the L2 information.
1764 __FreeBSD_version 800057 marks the switchover from the
1765 binary ath hal to source code. Users must add the line:
1767 options AH_SUPPORT_AR5416
1769 to their kernel config files when specifying:
1773 The ath_hal module no longer exists; the code is now compiled
1774 together with the driver in the ath module. It is now
1775 possible to tailor chip support (i.e. reduce the set of chips
1776 and thereby the code size); consult ath_hal(4) for details.
1779 __FreeBSD_version 800054 adds memory barriers to
1780 <machine/atomic.h>, new interfaces to ifnet to facilitate
1781 multiple hardware transmit queues for cards that support
1782 them, and a lock-less ring-buffer implementation to
1783 enable drivers to more efficiently manage queueing of
1787 A new version of ZFS (version 13) has been merged to -HEAD.
1788 This version has zpool attribute "listsnapshots" off by
1789 default, which means "zfs list" does not show snapshots,
1790 and is the same as Solaris behavior.
1793 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1796 The uhci, ohci, ehci and slhci USB Host controller drivers have
1797 been put into separate modules. If you load the usb module
1798 separately through loader.conf you will need to load the
1799 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1800 controller add the following to loader.conf:
1806 The ABI used by the PMC toolset has changed. Please keep
1807 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1811 atapci kernel module now includes only generic PCI ATA
1812 driver. AHCI driver moved to ataahci kernel module.
1813 All vendor-specific code moved into separate kernel modules:
1814 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1815 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1816 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1817 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1820 The TTY subsystem of the kernel has been replaced by a new
1821 implementation, which provides better scalability and an
1822 improved driver model. Most common drivers have been migrated to
1823 the new TTY subsystem, while others have not. The following
1824 drivers have not yet been ported to the new TTY layer:
1827 cy, digi, rc, rp, sio
1833 ng_h4, ng_tty, ppp, sl, snp
1835 Adding these drivers to your kernel configuration file shall
1836 cause compilation to fail.
1839 ntpd has been upgraded to 4.2.4p5.
1842 OpenSSH has been upgraded to 5.1p1.
1844 For many years, FreeBSD's version of OpenSSH preferred DSA
1845 over RSA for host and user authentication keys. With this
1846 upgrade, we've switched to the vendor's default of RSA over
1847 DSA. This may cause upgraded clients to warn about unknown
1848 host keys even for previously known hosts. Users should
1849 follow the usual procedure for verifying host keys before
1850 accepting the RSA key.
1852 This can be circumvented by setting the "HostKeyAlgorithms"
1853 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1856 Please note that the sequence of keys offered for
1857 authentication has been changed as well. You may want to
1858 specify IdentityFile in a different order to revert this
1862 The sio(4) driver has been removed from the i386 and amd64
1863 kernel configuration files. This means uart(4) is now the
1864 default serial port driver on those platforms as well.
1866 To prevent collisions with the sio(4) driver, the uart(4) driver
1867 uses different names for its device nodes. This means the
1868 onboard serial port will now most likely be called "ttyu0"
1869 instead of "ttyd0". You may need to reconfigure applications to
1870 use the new device names.
1872 When using the serial port as a boot console, be sure to update
1873 /boot/device.hints and /etc/ttys before booting the new kernel.
1874 If you forget to do so, you can still manually specify the hints
1875 at the loader prompt:
1877 set hint.uart.0.at="isa"
1878 set hint.uart.0.port="0x3F8"
1879 set hint.uart.0.flags="0x10"
1880 set hint.uart.0.irq="4"
1884 The gpt(8) utility has been removed. Use gpart(8) to partition
1888 The version that Linuxulator emulates was changed from 2.4.2
1889 to 2.6.16. If you experience any problems with Linux binaries
1890 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1891 if it fixes the problem contact emulation mailing list.
1894 ISDN4BSD (I4B) was removed from the src tree. You may need to
1895 update a your kernel configuration and remove relevant entries.
1898 I have checked in code to support multiple routing tables.
1899 See the man pages setfib(1) and setfib(2).
1900 This is a hopefully backwards compatible version,
1901 but to make use of it you need to compile your kernel
1902 with options ROUTETABLES=2 (or more up to 16).
1905 The 802.11 wireless support was redone to enable multi-bss
1906 operation on devices that are capable. The underlying device
1907 is no longer used directly but instead wlanX devices are
1908 cloned with ifconfig. This requires changes to rc.conf files.
1909 For example, change:
1910 ifconfig_ath0="WPA DHCP"
1913 ifconfig_wlan0="WPA DHCP"
1914 see rc.conf(5) for more details. In addition, mergemaster of
1915 /etc/rc.d is highly recommended. Simultaneous update of userland
1916 and kernel wouldn't hurt either.
1918 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1919 modules were merged into the base wlan module. All references
1920 to these modules (e.g. in kernel config files) must be removed.
1923 psm(4) has gained write(2) support in native operation level.
1924 Arbitrary commands can be written to /dev/psm%d and status can
1925 be read back from it. Therefore, an application is responsible
1926 for status validation and error recovery. It is a no-op in
1927 other operation levels.
1930 Support for KSE threading has been removed from the kernel. To
1931 run legacy applications linked against KSE libmap.conf may
1932 be used. The following libmap.conf may be used to ensure
1933 compatibility with any prior release:
1935 libpthread.so.1 libthr.so.1
1936 libpthread.so.2 libthr.so.2
1937 libkse.so.3 libthr.so.3
1940 The layout of struct vmspace has changed. This affects libkvm
1941 and any executables that link against libkvm and use the
1942 kvm_getprocs() function. In particular, but not exclusively,
1943 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1944 The effects are minimal, but it's advisable to upgrade world
1948 The latest em driver no longer has support in it for the
1949 82575 adapter, this is now moved to the igb driver. The
1950 split was done to make new features that are incompatible
1951 with older hardware easier to do.
1954 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1955 likewise the kernel option is now GEOM_LINUX_LVM.
1958 The default NFS mount mode has changed from UDP to TCP for
1959 increased reliability. If you rely on (insecurely) NFS
1960 mounting across a firewall you may need to update your
1964 Belatedly note the addition of m_collapse for compacting
1968 The fts(3) structures have been changed to use adequate
1969 integer types for their members and so to be able to cope
1970 with huge file trees. The old fts(3) ABI is preserved
1971 through symbol versioning in libc, so third-party binaries
1972 using fts(3) should still work, although they will not take
1973 advantage of the extended types. At the same time, some
1974 third-party software might fail to build after this change
1975 due to unportable assumptions made in its source code about
1976 fts(3) structure members. Such software should be fixed
1977 by its vendor or, in the worst case, in the ports tree.
1978 FreeBSD_version 800015 marks this change for the unlikely
1979 case that a portable fix is impossible.
1982 To upgrade to -current after this date, you must be running
1983 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1984 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1987 The ADAPTIVE_GIANT kernel option has been retired because its
1988 functionality is the default now.
1991 The AT keyboard emulation of sunkbd(4) has been turned on
1992 by default. In order to make the special symbols of the Sun
1993 keyboards driven by sunkbd(4) work under X these now have
1994 to be configured the same way as Sun USB keyboards driven
1995 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1997 Option "XkbLayout" "us"
1998 Option "XkbRules" "xorg"
1999 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2002 It has been decided that it is desirable to provide ABI
2003 backwards compatibility to the FreeBSD 4/5/6 versions of the
2004 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2005 broken with the introduction of PCI domain support (see the
2006 20070930 entry). Unfortunately, this required the ABI of
2007 PCIOCGETCONF to be broken again in order to be able to
2008 provide backwards compatibility to the old version of that
2009 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2010 again. As for prominent ports this affects neither pciutils
2011 nor xorg-server this time, the hal port needs to be rebuilt
2015 The misnamed kthread_create() and friends have been renamed
2016 to kproc_create() etc. Many of the callers already
2017 used kproc_start()..
2018 I will return kthread_create() and friends in a while
2019 with implementations that actually create threads, not procs.
2020 Renaming corresponds with version 800002.
2029 Avoid using make -j when upgrading. While generally safe, there are
2030 sometimes problems using -j to upgrade. If your upgrade fails with
2031 -j, please try again without -j. From time to time in the past there
2032 have been problems using -j with buildworld and/or installworld. This
2033 is especially true when upgrading between "distant" versions (eg one
2034 that cross a major release boundary or several minor releases, or when
2035 several months have passed on the -current branch).
2037 Sometimes, obscure build problems are the result of environment
2038 poisoning. This can happen because the make utility reads its
2039 environment when searching for values for global variables. To run
2040 your build attempts in an "environmental clean room", prefix all make
2041 commands with 'env -i '. See the env(1) manual page for more details.
2043 When upgrading from one major version to another it is generally best
2044 to upgrade to the latest code in the currently installed branch first,
2045 then do an upgrade to the new branch. This is the best-tested upgrade
2046 path, and has the highest probability of being successful. Please try
2047 this approach before reporting problems with a major version upgrade.
2049 When upgrading a live system, having a root shell around before
2050 installing anything can help undo problems. Not having a root shell
2051 around can lead to problems if pam has changed too much from your
2052 starting point to allow continued authentication after the upgrade.
2056 When upgrading the boot ZFS pool to a new version, always follow
2059 1.) recompile and reinstall the ZFS boot loader and boot block
2060 (this is part of "make buildworld" and "make installworld")
2062 2.) update the ZFS boot block on your boot drive
2064 The following example updates the ZFS boot block on the first
2065 partition (freebsd-boot) of a GPT partitioned drive ad0:
2066 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2068 Non-boot pools do not need these updates.
2072 If you are updating from a prior version of FreeBSD (even one just
2073 a few days old), you should follow this procedure. It is the most
2074 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2076 make kernel-toolchain
2077 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2078 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2080 To test a kernel once
2081 ---------------------
2082 If you just want to boot a kernel once (because you are not sure
2083 if it works, or if you want to boot a known bad kernel to provide
2084 debugging information) run
2085 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2086 nextboot -k testkernel
2088 To just build a kernel when you know that it won't mess you up
2089 --------------------------------------------------------------
2090 This assumes you are already running a CURRENT system. Replace
2091 ${arch} with the architecture of your machine (e.g. "i386",
2092 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2094 cd src/sys/${arch}/conf
2095 config KERNEL_NAME_HERE
2096 cd ../compile/KERNEL_NAME_HERE
2101 If this fails, go to the "To build a kernel" section.
2103 To rebuild everything and install it on the current system.
2104 -----------------------------------------------------------
2105 # Note: sometimes if you are running current you gotta do more than
2106 # is listed here if you are upgrading from a really old current.
2108 <make sure you have good level 0 dumps>
2110 make kernel KERNCONF=YOUR_KERNEL_HERE
2112 <reboot in single user> [3]
2119 To cross-install current onto a separate partition
2120 --------------------------------------------------
2121 # In this approach we use a separate partition to hold
2122 # current's root, 'usr', and 'var' directories. A partition
2123 # holding "/", "/usr" and "/var" should be about 2GB in
2126 <make sure you have good level 0 dumps>
2129 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2130 <maybe newfs current's root partition>
2131 <mount current's root partition on directory ${CURRENT_ROOT}>
2132 make installworld DESTDIR=${CURRENT_ROOT}
2133 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2134 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2135 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2136 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2137 <reboot into current>
2138 <do a "native" rebuild/install as described in the previous section>
2139 <maybe install compatibility libraries from ports/misc/compat*>
2143 To upgrade in-place from stable to current
2144 ----------------------------------------------
2145 <make sure you have good level 0 dumps>
2147 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2149 <reboot in single user> [3]
2156 Make sure that you've read the UPDATING file to understand the
2157 tweaks to various things you need. At this point in the life
2158 cycle of current, things change often and you are on your own
2159 to cope. The defaults can also change, so please read ALL of
2160 the UPDATING entries.
2162 Also, if you are tracking -current, you must be subscribed to
2163 freebsd-current@freebsd.org. Make sure that before you update
2164 your sources that you have read and understood all the recent
2165 messages there. If in doubt, please track -stable which has
2166 much fewer pitfalls.
2168 [1] If you have third party modules, such as vmware, you
2169 should disable them at this point so they don't crash your
2172 [3] From the bootblocks, boot -s, and then do
2177 adjkerntz -i # if CMOS is wall time
2178 Also, when doing a major release upgrade, it is required that
2179 you boot into single user mode to do the installworld.
2181 [4] Note: This step is non-optional. Failure to do this step
2182 can result in a significant reduction in the functionality of the
2183 system. Attempting to do it by hand is not recommended and those
2184 that pursue this avenue should read this file carefully, as well
2185 as the archives of freebsd-current and freebsd-hackers mailing lists
2186 for potential gotchas. The -U option is also useful to consider.
2187 See mergemaster(8) for more information.
2189 [5] Usually this step is a noop. However, from time to time
2190 you may need to do this if you get unknown user in the following
2191 step. It never hurts to do it all the time. You may need to
2192 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2193 install) after the buildworld before this step if you last updated
2194 from current before 20130425 or from -stable before 20130430.
2196 [6] This only deletes old files and directories. Old libraries
2197 can be deleted by "make delete-old-libs", but you have to make
2198 sure that no program is using those libraries anymore.
2200 [8] In order to have a kernel that can run the 4.x binaries needed to
2201 do an installworld, you must include the COMPAT_FREEBSD4 option in
2202 your kernel. Failure to do so may leave you with a system that is
2203 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2204 required to run the 5.x binaries on more recent kernels. And so on
2205 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2207 Make sure that you merge any new devices from GENERIC since the
2208 last time you updated your kernel config file.
2210 [9] When checking out sources, you must include the -P flag to have
2211 cvs prune empty directories.
2213 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2214 "?=" instead of the "=" assignment operator, so that buildworld can
2215 override the CPUTYPE if it needs to.
2217 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2218 not on the command line, or in /etc/make.conf. buildworld will
2219 warn if it is improperly defined.
2222 This file contains a list, in reverse chronological order, of major
2223 breakages in tracking -current. It is not guaranteed to be a complete
2224 list of such breakages, and only contains entries since October 10, 2007.
2225 If you need to see UPDATING entries from before that date, you will need
2226 to fetch an UPDATING file from an older FreeBSD release.
2228 Copyright information:
2230 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2232 Redistribution, publication, translation and use, with or without
2233 modification, in full or in part, in any form or format of this
2234 document are permitted without further permission from the author.
2236 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2237 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2238 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2239 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2240 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2241 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2242 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2243 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2244 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2245 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2246 POSSIBILITY OF SUCH DAMAGE.
2248 Contact Warner Losh if you have any questions about your use of