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 From legacy ata(4) driver was removed support for SATA controllers
21 supported by more functional drivers ahci(4), siis(4) and mvs(4).
22 Kernel modules ataahci and ataadaptec were removed completely,
23 replaced by ahci and mvs modules respectively.
29 As ZFS requires more kernel stack pages than is the default on some
30 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
31 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
33 Please consider using 'options KSTACK_PAGES=X' where X is greater
34 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
37 The default Unbound configuration now enables remote control
38 using a local socket. Users who have already enabled the
39 local_unbound service should regenerate their configuration
40 by running "service local_unbound setup" as root.
43 An additional fix for the issue described in the 20150614 sendmail
44 entry below has been been committed in revision 284786.
47 The fix for the issue described in the 20150614 sendmail entry
48 below has been been committed in revision 284485. The work
49 around described in that entry is no longer needed unless the
50 default setting is overridden by a confDH_PARAMETERS configuration
51 setting of '5' or pointing to a 512 bit DH parameter file.
54 The import of openssl to address the FreeBSD-SA-15:10.openssl
55 security advisory includes a change which rejects handshakes
56 with DH parameters below 768 bits. sendmail releases prior
57 to 8.15.2 (not yet released), defaulted to a 512 bit
58 DH parameter setting for client connections. To work around
59 this interoperability, sendmail can be configured to use a
60 2048 bit DH parameter by:
62 1. Edit /etc/mail/`hostname`.mc
63 2. If a setting for confDH_PARAMETERS does not exist or
64 exists and is set to a string beginning with '5',
66 3. If a setting for confDH_PARAMETERS exists and is set to
67 a file path, create a new file with:
68 openssl dhparam -out /path/to/file 2048
69 4. Rebuild the .cf file:
70 cd /etc/mail/; make; make install
72 cd /etc/mail/; make restart
74 A sendmail patch is coming, at which time this file will be
78 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
79 defined in symlink(7); previously symlinks were silently ignored.
82 The const qualifier has been removed from iconv(3) to comply with
83 POSIX. The ports tree is aware of this from r384038 onwards.
86 At svn r275807, The default linux compat kernel ABI has been adjusted
87 to 2.6.18 in support of the linux-c6 compat ports infrastructure
88 update. If you wish to continue using the linux-f10 compat ports,
89 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
90 encouraged to update their linux-compat packages to linux-c6 during
91 their next update cycle.
93 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
96 pjdfstest has been integrated into kyua as an opt-in test suite.
97 Please see share/doc/pjdfstest/README for a more details on how to
104 The ofwfb driver, used to provide a graphics console on PowerPC when
105 using vt(4), no longer allows mmap() of all of physical memory. This
106 will prevent Xorg on PowerPC with some ATI graphics cards from
107 initializing properly unless x11-servers/xorg-server is updated to
111 The libatf-c and libatf-c++ major versions were downgraded to 0 and
112 1 respectively to match the upstream numbers. They were out of
113 sync because, when they were originally added to FreeBSD, the
114 upstream versions were not respected. These libraries are private
115 and not yet built by default, so renumbering them should be a
116 non-issue. However, unclean source trees will yield broken test
117 programs once the operator executes "make delete-old-libs" after a
120 Additionally, the atf-sh binary was made private by moving it into
121 /usr/libexec/. Already-built shell test programs will keep the
122 path to the old binary so they will break after "make delete-old"
125 If you are using WITH_TESTS=yes (not the default), wipe the object
126 tree and rebuild from scratch to prevent spurious test failures.
127 This is only needed once: the misnumbered libraries and misplaced
128 binaries have been added to OptionalObsoleteFiles.inc so they will
129 be removed during a clean upgrade.
132 The ixgbe tunables now match their sysctl counterparts, for example:
133 hw.ixgbe.enable_aim => hw.ix.enable_aim
134 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
137 The NFSv4.1 server committed by r269398 changes the internal
138 function call interfaces used between the NFS and krpc modules.
139 As such, __FreeBSD_version was bumped.
142 The default unbound configuration has been modified to address
143 issues with reverse lookups on networks that use private
144 address ranges. If you use the local_unbound service, run
145 "service local_unbound setup" as root to regenerate your
146 configuration, then "service local_unbound reload" to load the
150 It is no longer necessary to include the dwarf version in your DEBUG
151 options in your kernel config file. The bug that required it to be
152 placed in the config file has bene fixed. DEBUG should now just
153 contain -g. The build system will automatically update things
154 to do the right thing.
157 Several ABI breaking changes were merged to CTL and new iSCSI code.
158 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
159 iscsictl need to be rebuilt to work with a new kernel.
162 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
163 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
164 which differs from the behaviour controlled by this knob.)
167 On i386 and amd64 systems, the onifconsole flag is now set by default
168 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
169 as a login TTY if it is set in the bootloader as an active kernel
170 console. No changes in behavior should result otherwise. To revert to
171 the previous behavior, set ttyu0 to "off" in /etc/ttys.
174 Clang and llvm have been upgraded to 3.4.1 release.
177 Clang and llvm have been upgraded to 3.4 release.
180 If a Makefile in a tests/ directory was auto-generating a Kyuafile
181 instead of providing an explicit one, this would prevent such
182 Makefile from providing its own Kyuafile in the future during
183 NO_CLEAN builds. This has been fixed in the Makefiles but manual
184 intervention is needed to clean an objdir if you use NO_CLEAN:
185 # find /usr/obj -name Kyuafile | xargs rm -f
188 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
189 capability mode support. Please note that enabling the feature in
190 kernel is still highly recommended.
193 OpenSSH is now built with sandbox support, and will use sandbox as
194 the default privilege separation method. This requires Capsicum
195 capability mode support in kernel.
198 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
199 been deprecated and will not be part of FreeBSD 11.0 and later
200 releases. If you use this driver, please consider switching to
201 the nfe(4) driver instead.
207 The behavior of gss_pseudo_random() for the krb5 mechanism
208 has changed, for applications requesting a longer random string
209 than produced by the underlying enctype's pseudo-random() function.
210 In particular, the random string produced from a session key of
211 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
212 be different at the 17th octet and later, after this change.
213 The counter used in the PRF+ construction is now encoded as a
214 big-endian integer in accordance with RFC 4402.
215 __FreeBSD_version is bumped to 1000701.
218 The WITHOUT_ATF build knob has been removed and its functionality
219 has been subsumed into the more generic WITHOUT_TESTS. If you were
220 using the former to disable the build of the ATF libraries, you
221 should change your settings to use the latter.
224 The default version of mtree is nmtree which is obtained from
225 NetBSD. The output is generally the same, but may vary
226 slightly. If you found you need identical output adding
227 "-F freebsd9" to the command line should do the trick. For the
228 time being, the old mtree is available as fmtree.
231 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
232 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
233 1.1.4_8 and verify bsdyml not linked in, before running "make
235 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
237 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
240 The rc.d/jail script has been updated to support jail(8)
241 configuration file. The "jail_<jname>_*" rc.conf(5) variables
242 for per-jail configuration are automatically converted to
243 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
244 This is transparently backward compatible. See below about some
245 incompatibilities and rc.conf(5) manual page for more details.
247 These variables are now deprecated in favor of jail(8) configuration
248 file. One can use "rc.d/jail config <jname>" command to generate
249 a jail(8) configuration file in /var/run/jail.<jname>.conf without
250 running the jail(8) utility. The default pathname of the
251 configuration file is /etc/jail.conf and can be specified by
252 using $jail_conf or $jail_<jname>_conf variables.
254 Please note that jail_devfs_ruleset accepts an integer at
255 this moment. Please consider to rewrite the ruleset name
259 BIND has been removed from the base system. If all you need
260 is a local resolver, simply enable and start the local_unbound
261 service instead. Otherwise, several versions of BIND are
262 available in the ports tree. The dns/bind99 port is one example.
264 With this change, nslookup(1) and dig(1) are no longer in the base
265 system. Users should instead use host(1) and drill(1) which are
266 in the base system. Alternatively, nslookup and dig can
267 be obtained by installing the dns/bind-tools port.
270 With the addition of unbound(8), a new unbound user is now
271 required during installworld. "mergemaster -p" can be used to
272 add the user prior to installworld, as documented in the handbook.
275 OpenSSH is now built with DNSSEC support, and will by default
276 silently trust signed SSHFP records. This can be controlled with
277 the VerifyHostKeyDNS client configuration setting. DNSSEC support
278 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
281 The GNU Compiler Collection and C++ standard library (libstdc++)
282 are no longer built by default on platforms where clang is the system
283 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
287 The PROCDESC kernel option is now part of the GENERIC kernel
288 configuration and is required for the rwhod(8) to work.
289 If you are using custom kernel configuration, you should include
293 The API and ABI related to the Capsicum framework was modified
294 in backward incompatible way. The userland libraries and programs
295 have to be recompiled to work with the new kernel. This includes the
296 following libraries and programs, but the whole buildworld is
297 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
298 kdump, procstat, rwho, rwhod, uniq.
301 AES-NI intrinsic support has been added to gcc. The AES-NI module
302 has been updated to use this support. A new gcc is required to build
303 the aesni module on both i386 and amd64.
306 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
307 Thus "device padlock_rng" and "device rdrand_rng" should be
308 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
311 WITH_ICONV has been split into two feature sets. WITH_ICONV now
312 enables just the iconv* functionality and is now on by default.
313 WITH_LIBICONV_COMPAT enables the libiconv api and link time
314 compatability. Set WITHOUT_ICONV to build the old way.
315 If you have been using WITH_ICONV before, you will very likely
316 need to turn on WITH_LIBICONV_COMPAT.
319 INVARIANTS option now enables DEBUG for code with OpenSolaris and
320 Illumos origin, including ZFS. If you have INVARIANTS in your
321 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
323 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
324 locks if WITNESS option was set. Because that generated a lot of
325 witness(9) reports and all of them were believed to be false
326 positives, this is no longer done. New option OPENSOLARIS_WITNESS
327 can be used to achieve the previous behavior.
330 Timer values in IPv6 data structures now use time_uptime instead
331 of time_second. Although this is not a user-visible functional
332 change, userland utilities which directly use them---ndp(8),
333 rtadvd(8), and rtsold(8) in the base system---need to be updated
337 find -delete can now delete the pathnames given as arguments,
338 instead of only files found below them or if the pathname did
339 not contain any slashes. Formerly, the following error message
342 find: -delete: <path>: relative path potentially not safe
344 Deleting the pathnames given as arguments can be prevented
345 without error messages using -mindepth 1 or by changing
346 directory and passing "." as argument to find. This works in the
347 old as well as the new version of find.
350 Behavior of devfs rules path matching has been changed.
351 Pattern is now always matched against fully qualified devfs
352 path and slash characters must be explicitly matched by
353 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
354 subdirectories must be reviewed.
357 The default ARM ABI has changed to the ARM EABI. The old ABI is
358 incompatible with the ARM EABI and all programs and modules will
359 need to be rebuilt to work with a new kernel.
361 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
363 NOTE: Support for the old ABI will be removed in the future and
364 users are advised to upgrade.
367 pkg_install has been disconnected from the build if you really need it
368 you should add WITH_PKGTOOLS in your src.conf(5).
371 Most of network statistics structures were changed to be able
372 keep 64-bits counters. Thus all tools, that work with networking
373 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
376 Fix targets that run multiple make's to use && rather than ;
377 so that subsequent steps depend on success of previous.
379 NOTE: if building 'universe' with -j* on stable/8 or stable/9
380 it would be better to start the build using bmake, to avoid
381 overloading the machine.
384 Fix a bug that allowed a tracing process (e.g. gdb) to write
385 to a memory-mapped file in the traced process's address space
386 even if neither the traced process nor the tracing process had
387 write access to that file.
390 CVS has been removed from the base system. An exact copy
391 of the code is available from the devel/cvs port.
394 Some people report the following error after the switch to bmake:
396 make: illegal option -- J
397 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
399 *** [buildworld] Error code 2
401 this likely due to an old instance of make in
402 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
403 which src/Makefile will use that blindly, if it exists, so if
404 you see the above error:
406 rm -rf `make -V MAKEPATH`
411 Use bmake by default.
412 Whereas before one could choose to build with bmake via
413 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
414 make. The goal is to remove these knobs for 10-RELEASE.
416 It is worth noting that bmake (like gmake) treats the command
417 line as the unit of failure, rather than statements within the
418 command line. Thus '(cd some/where && dosomething)' is safer
419 than 'cd some/where; dosomething'. The '()' allows consistent
420 behavior in parallel build.
423 Fix a bug that allows NFS clients to issue READDIR on files.
426 The WITHOUT_IDEA option has been removed because
427 the IDEA patent expired.
430 The sysctl which controls TRIM support under ZFS has been renamed
431 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
435 The mergemaster command now uses the default MAKEOBJDIRPREFIX
436 rather than creating it's own in the temporary directory in
437 order allow access to bootstrapped versions of tools such as
438 install and mtree. When upgrading from version of FreeBSD where
439 the install command does not support -l, you will need to
440 install a new mergemaster command if mergemaster -p is required.
441 This can be accomplished with the command (cd src/usr.sbin/mergemaster
445 Legacy ATA stack, disabled and replaced by new CAM-based one since
446 FreeBSD 9.0, completely removed from the sources. Kernel modules
447 atadisk and atapi*, user-level tools atacontrol and burncd are
448 removed. Kernel option `options ATA_CAM` is now permanently enabled
452 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
453 and socketpair(2). Software, in particular Kerberos, may
454 automatically detect and use these during building. The resulting
455 binaries will not work on older kernels.
458 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
459 information, see the respective 20130304 entry).
462 Recent commits to callout(9) changed the size of struct callout,
463 so the KBI is probably heavily disturbed. Also, some functions
464 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
465 by macros. Every kernel module using it won't load, so rebuild
468 The ctl device has been re-enabled in GENERIC for i386 and amd64,
469 but does not initialize by default (because of the new CTL_DISABLE
470 option) to save memory. To re-enable it, remove the CTL_DISABLE
471 option from the kernel config file or set kern.cam.ctl.disable=0
472 in /boot/loader.conf.
475 The ctl device has been disabled in GENERIC for i386 and amd64.
476 This was done due to the extra memory being allocated at system
477 initialisation time by the ctl driver which was only used if
478 a CAM target device was created. This makes a FreeBSD system
479 unusable on 128MB or less of RAM.
482 A new compression method (lz4) has been merged to -HEAD. Please
483 refer to zpool-features(7) for more information.
485 Please refer to the "ZFS notes" section of this file for information
486 on upgrading boot ZFS pools.
489 A BSD-licensed patch(1) variant has been added and is installed
490 as bsdpatch, being the GNU version the default patch.
491 To inverse the logic and use the BSD-licensed one as default,
492 while having the GNU version installed as gnupatch, rebuild
493 and install world with the WITH_BSD_PATCH knob set.
496 Due to the use of the new -l option to install(1) during build
497 and install, you must take care not to directly set the INSTALL
498 make variable in your /etc/make.conf, /etc/src.conf, or on the
499 command line. If you wish to use the -C flag for all installs
500 you may be able to add INSTALL+=-C to /etc/make.conf or
504 The install(1) option -M has changed meaning and now takes an
505 argument that is a file or path to append logs to. In the
506 unlikely event that -M was the last option on the command line
507 and the command line contained at least two files and a target
508 directory the first file will have logs appended to it. The -M
509 option served little practical purpose in the last decade so its
510 use is expected to be extremely rare.
513 After switching to Clang as the default compiler some users of ZFS
514 on i386 systems started to experience stack overflow kernel panics.
515 Please consider using 'options KSTACK_PAGES=4' in such configurations.
518 GEOM_LABEL now mangles label names read from file system metadata.
519 Mangling affect labels containing spaces, non-printable characters,
520 '%' or '"'. Device names in /etc/fstab and other places may need to
524 By default, only the 10 most recent kernel dumps will be saved. To
525 restore the previous behaviour (no limit on the number of kernel dumps
526 stored in the dump directory) add the following line to /etc/rc.conf:
531 With the addition of auditdistd(8), a new auditdistd user is now
532 required during installworld. "mergemaster -p" can be used to
533 add the user prior to installworld, as documented in the handbook.
536 The sin6_scope_id member variable in struct sockaddr_in6 is now
537 filled by the kernel before passing the structure to the userland via
538 sysctl or routing socket. This means the KAME-specific embedded scope
539 id in sin6_addr.s6_addr[2] is always cleared in userland application.
540 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
541 __FreeBSD_version is bumped to 1000025.
544 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
545 This means that the world and kernel will be compiled with clang
546 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
547 and /usr/bin/cpp. To disable this behavior and revert to building
548 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
549 of current may need to bootstrap WITHOUT_CLANG first if the clang
550 build fails (its compatibility window doesn't extend to the 9 stable
554 The IPFIREWALL_FORWARD kernel option has been removed. Its
555 functionality now turned on by default.
558 The ZERO_COPY_SOCKET kernel option has been removed and
559 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
560 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
561 mechanism which is not safe and may result in kernel crashes.
562 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
563 driver supports disposeable external page sized mbuf storage.
564 Proper replacements for both zero-copy mechanisms are under
565 consideration and will eventually lead to complete removal
566 of the two kernel options.
569 The IPv4 network stack has been converted to network byte
570 order. The following modules need to be recompiled together
571 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
572 pf(4), ipfw(4), ng_ipfw(4), stf(4).
575 Support for non-MPSAFE filesystems was removed from VFS. The
576 VFS_VERSION was bumped, all filesystem modules shall be
580 All the non-MPSAFE filesystems have been disconnected from
581 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
582 portalfs, smbfs, xfs.
585 The interface cloning API and ABI has changed. The following
586 modules need to be recompiled together with kernel:
587 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
588 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
589 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
592 The sdhci driver was split in two parts: sdhci (generic SD Host
593 Controller logic) and sdhci_pci (actual hardware driver).
594 No kernel config modifications are required, but if you
595 load sdhc as a module you must switch to sdhci_pci instead.
598 Import the FUSE kernel and userland support into base system.
601 The GNU sort(1) program has been removed since the BSD-licensed
602 sort(1) has been the default for quite some time and no serious
603 problems have been reported. The corresponding WITH_GNU_SORT
607 The pfil(9) API/ABI for AF_INET family has been changed. Packet
608 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
612 The net80211(4) ABI has been changed to allow for improved driver
613 PS-POLL and power-save support. All wireless drivers need to be
614 recompiled to work with the new kernel.
617 The random(4) support for the VIA hardware random number
618 generator (`PADLOCK') is no longer enabled unconditionally.
619 Add the padlock_rng device in the custom kernel config if
620 needed. The GENERIC kernels on i386 and amd64 do include the
621 device, so the change only affects the custom kernel
625 The pf(4) packet filter ABI has been changed. pfctl(8) and
626 snmp_pf module need to be recompiled to work with new kernel.
629 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
630 to -HEAD. Pools that have empty_bpobj in active state can not be
631 imported read-write with ZFS implementations that do not support
632 this feature. For more information read the zpool-features(5)
636 The sparc64 ZFS loader has been changed to no longer try to auto-
637 detect ZFS providers based on diskN aliases but now requires these
638 to be explicitly listed in the OFW boot-device environment variable.
641 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
642 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
643 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
646 The following sysctls and tunables have been renamed for consistency
647 with other variables:
648 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
649 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
652 The sort utility has been replaced with BSD sort. For now, GNU sort
653 is also available as "gnusort" or the default can be set back to
654 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
655 installed as "bsdsort".
658 A new version of ZFS (pool version 5000) has been merged to -HEAD.
659 Starting with this version the old system of ZFS pool versioning
660 is superseded by "feature flags". This concept enables forward
661 compatibility against certain future changes in functionality of ZFS
662 pools. The first read-only compatible "feature flag" for ZFS pools
663 is named "com.delphix:async_destroy". For more information
664 read the new zpool-features(5) manual page.
665 Please refer to the "ZFS notes" section of this file for information
666 on upgrading boot ZFS pools.
669 The malloc(3) implementation embedded in libc now uses sources imported
670 as contrib/jemalloc. The most disruptive API change is to
671 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
672 delete it prior to installworld, and optionally re-create it using the
673 new format after rebooting. See malloc.conf(5) for details
674 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
678 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
679 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
680 now spelled mips. This is to aid compatibility with third-party
681 software that expects this naming scheme in uname(3). Little-endian
682 settings are unchanged. If you are updating a big-endian mips64 machine
683 from before this change, you may need to set MACHINE_ARCH=mips64 in
684 your environment before the new build system will recognize your machine.
687 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
691 Now unix domain sockets behave "as expected" on nullfs(5). Previously
692 nullfs(5) did not pass through all behaviours to the underlying layer,
693 as a result if we bound to a socket on the lower layer we could connect
694 only to the lower path; if we bound to the upper layer we could connect
695 only to the upper path. The new behavior is one can connect to both the
696 lower and the upper paths regardless what layer path one binds to.
699 The getifaddrs upgrade path broken with 20111215 has been restored.
700 If you have upgraded in between 20111215 and 20120209 you need to
701 recompile libc again with your kernel. You still need to recompile
702 world to be able to configure CARP but this restriction already
706 The set_rcvar() function has been removed from /etc/rc.subr. All
707 base and ports rc.d scripts have been updated, so if you have a
708 port installed with a script in /usr/local/etc/rc.d you can either
709 hand-edit the rcvar= line, or reinstall the port.
711 An easy way to handle the mass-update of /etc/rc.d:
712 rm /etc/rc.d/* && mergemaster -i
715 panic(9) now stops other CPUs in the SMP systems, disables interrupts
716 on the current CPU and prevents other threads from running.
717 This behavior can be reverted using the kern.stop_scheduler_on_panic
719 The new behavior can be incompatible with kern.sync_on_panic.
722 The carp(4) facility has been changed significantly. Configuration
723 of the CARP protocol via ifconfig(8) has changed, as well as format
724 of CARP events submitted to devd(8) has changed. See manual pages
725 for more information. The arpbalance feature of carp(4) is currently
726 not supported anymore.
728 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
729 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
730 need to be recompiled.
733 The acpi_wmi(4) status device /dev/wmistat has been renamed to
737 The option VFS_ALLOW_NONMPSAFE option has been added in order to
738 explicitely support non-MPSAFE filesystems.
739 It is on by default for all supported platform at this present
743 The broken amd(4) driver has been replaced with esp(4) in the amd64,
744 i386 and pc98 GENERIC kernel configuration files.
747 sysinstall has been removed
750 The stable/9 branch created in subversion. This corresponds to the
751 RELENG_9 branch in CVS.
754 This commit modifies vfs_register() so that it uses a hash
755 calculation to set vfc_typenum, which is enabled by default.
756 The first time a system is booted after this change, the
757 vfc_typenum values will change for all file systems. The
758 main effect of this is a change to the NFS server file handles
759 for file systems that use vfc_typenum in their fsid, such as ZFS.
760 It will, however, prevent vfc_typenum from changing when file
761 systems are loaded in a different order for subsequent reboots.
762 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
763 until you are ready to remount all NFS clients after a reboot.
766 Bump the shared library version numbers for libraries that
767 do not use symbol versioning, have changed the ABI compared
768 to stable/8 and which shared library version was not bumped.
769 Done as part of 9.0-RELEASE cycle.
772 During the merge of Capsicum features, the fget(9) KPI was modified.
773 This may require the rebuilding of out-of-tree device drivers --
774 issues have been reported specifically with the nVidia device driver.
775 __FreeBSD_version is bumped to 900041.
777 Also, there is a period between 20110811 and 20110814 where the
778 special devices /dev/{stdin,stdout,stderr} did not work correctly.
779 Building world from a kernel during that window may not work.
782 The packet filter (pf) code has been updated to OpenBSD 4.5.
783 You need to update userland tools to be in sync with kernel.
784 This update breaks backward compatibility with earlier pfsync(4)
785 versions. Care must be taken when updating redundant firewall setups.
788 The following sysctls and tunables are retired on x86 platforms:
790 machdep.hlt_logical_cpus
791 The following sysctl is retired:
792 machdep.hyperthreading_allowed
793 The sysctls were supposed to provide a way to dynamically offline and
794 online selected CPUs on x86 platforms, but the implementation has not
795 been reliable especially with SCHED_ULE scheduler.
796 machdep.hyperthreading_allowed tunable is still available to ignore
797 hyperthreading CPUs at OS level.
798 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
799 where X is an APIC ID of a CPU. Be advised, though, that disabling
800 CPUs in non-uniform fashion will result in non-uniform topology and
801 may lead to sub-optimal system performance with SCHED_ULE, which is
805 cpumask_t type is retired and cpuset_t is used in order to describe
809 Changes to ifconfig(8) for dynamic address family detection mandate
810 that you are running a kernel of 20110525 or later. Make sure to
811 follow the update procedure to boot a new kernel before installing
815 Support for sun4v architecture is officially dropped
818 Several KPI breaking changes have been committed to the mii(4) layer,
819 the PHY drivers and consequently some Ethernet drivers using mii(4).
820 This means that miibus.ko and the modules of the affected Ethernet
821 drivers need to be recompiled.
823 Note to kernel developers: Given that the OUI bit reversion problem
824 was fixed as part of these changes all mii(4) commits related to OUIs,
825 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
826 handling, no longer can be merged verbatim to stable/8 and previous
830 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
831 into their kernel configurations along with 'device pci'.
834 The default NFS client is now the new NFS client, so fstype "newnfs"
835 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
836 Although mounts via fstype "nfs" will usually work without userland
837 changes, it is recommended that the mount(8) and mount_nfs(8)
838 commands be rebuilt from sources and that a link to mount_nfs called
839 mount_oldnfs be created. The new client is compiled into the
840 kernel with "options NFSCL" and this is needed for diskless root
841 file systems. The GENERIC kernel configs have been changed to use
842 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
843 To use the regular/old client, you can "mount -t oldnfs ...". For
844 a diskless root file system, you must also include a line like:
846 vfs.root.mountfrom="oldnfs:"
848 in the boot/loader.conf on the root fs on the NFS server to make
849 a diskless root fs use the old client.
852 The GENERIC kernels for all architectures now default to the new
853 CAM-based ATA stack. It means that all legacy ATA drivers were
854 removed and replaced by respective CAM drivers. If you are using
855 ATA device names in /etc/fstab or other places, make sure to update
856 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
857 where 'Y's are the sequential numbers starting from zero for each type
858 in order of detection, unless configured otherwise with tunables,
859 see cam(4)). There will be symbolic links created in /dev/ to map
860 old adX devices to the respective adaY. They should provide basic
861 compatibility for file systems mounting in most cases, but they do
862 not support old user-level APIs and do not have respective providers
863 in GEOM. Consider using updated management tools with new device names.
865 It is possible to load devices ahci, ata, siis and mvs as modules,
866 but option ATA_CAM should remain in kernel configuration to make ata
867 module work as CAM driver supporting legacy ATA controllers. Device ata
868 still can be used in modular fashion (atacore + ...). Modules atadisk
869 and atapi* are not used and won't affect operation in ATA_CAM mode.
870 Note that to use CAM-based ATA kernel should include CAM devices
871 scbus, pass, da (or explicitly ada), cd and optionally others. All of
872 them are parts of the cam module.
874 ataraid(4) functionality is now supported by the RAID GEOM class.
875 To use it you can load geom_raid kernel module and use graid(8) tool
876 for management. Instead of /dev/arX device names, use /dev/raid/rX.
878 No kernel config options or code have been removed, so if a problem
879 arises, please report it and optionally revert to the old ATA stack.
880 In order to do it you can remove from the kernel config:
885 , and instead add back:
886 device atadisk # ATA disk drives
887 device ataraid # ATA RAID drives
888 device atapicd # ATAPI CDROM drives
889 device atapifd # ATAPI floppy drives
890 device atapist # ATAPI tape drives
893 The default NFS server has been changed to the new server, which
894 was referred to as the experimental server. If you need to switch
895 back to the old NFS server, you must now put the "-o" option on
896 both the mountd and nfsd commands. This can be done using the
897 mountd_flags and nfs_server_flags rc.conf variables until an
898 update to the rc scripts is committed, which is coming soon.
901 The GNU Objective-C runtime library (libobjc), and other Objective-C
902 related components have been removed from the base system. If you
903 require an Objective-C library, please use one of the available ports.
906 ath(4) has been split into bus- and device- modules. if_ath contains
907 the HAL, the TX rate control and the network device code. if_ath_pci
908 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
909 contains the AHB glue. Users need to load both if_ath_pci and if_ath
910 in order to use ath on everything else.
912 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
913 need to load if_ath and if_ath_pci for ath(4) operation.
916 As part of the replacement of sysinstall, the process of building
917 release media has changed significantly. For details, please re-read
918 release(7), which has been updated to reflect the new build process.
921 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
922 is the last available version under GPLv2. It brings a number of new
923 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
924 4.1 and SSE 4.2), better support for powerpc64, a number of new
925 directives, and lots of other small improvements. See the ChangeLog
926 file in contrib/binutils for the full details.
929 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
930 compliant, and will now use half of hash for authentication.
931 This will break interoperability with all stacks (including all
932 actual FreeBSD versions) who implement
933 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
935 The only workaround with such peers is to use another HMAC
936 algorithm for IPsec ("phase 2") authentication.
939 Remove the uio_yield prototype and symbol. This function has
940 been misnamed since it was introduced and should not be
941 globally exposed with this name. The equivalent functionality
942 is now available using kern_yield(curthread->td_user_pri).
943 The function remains undocumented.
946 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
947 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
948 for scalar sysctls is defined but disabled. Code that needs
949 UQUAD to pass the type checking that must compile on older
950 systems where the define is not present can check against
951 __FreeBSD_version >= 900030.
953 The system dialog(1) has been replaced with a new version previously
954 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
955 with the previous version, but the libdialog associated with it has
956 a largely incompatible API. As such, the original version of libdialog
957 will be kept temporarily as libodialog, until its base system consumers
958 are replaced or updated. Bump __FreeBSD_version to 900030.
961 If you are trying to run make universe on a -stable system, and you get
962 the following warning:
963 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
964 unknown. config(8) likely too old."
965 or something similar to it, then you must upgrade your -stable system
966 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
967 stable/8) or build the config from the latest stable/8 branch and
968 install it on your system.
970 Prior to this date, building a current universe on 8-stable system from
971 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
972 error in the first kernel build phase. A new config on those old
973 systems will fix that problem for older versions of -current.
976 The TCP stack has been modified to allow Khelp modules to interact with
977 it via helper hook points and store per-connection data in the TCP
978 control block. Bump __FreeBSD_version to 900029. User space tools that
979 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
983 Generic IEEE 802.3 annex 31B full duplex flow control support has been
984 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
985 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
986 to take advantage of it instead of using custom implementations. This
987 means that these drivers now no longer unconditionally advertise
988 support for flow control but only do so if flow control is a selected
989 media option. This was implemented in the generic support that way in
990 order to allow flow control to be switched on and off via ifconfig(8)
991 with the PHY specific default to typically off in order to protect
992 from unwanted effects. Consequently, if you used flow control with
993 one of the above mentioned drivers you now need to explicitly enable
995 ifconfig bge0 media auto mediaopt flowcontrol
997 Along with the above mentioned changes generic support for setting
998 1000baseT master mode also has been added and brgphy(4), ciphy(4),
999 e1000phy(4) as well as ip1000phy(4) have been converted to take
1000 advantage of it. This means that these drivers now no longer take the
1001 link0 parameter for selecting master mode but the master media option
1002 has to be used instead, for example like in the following:
1003 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1005 Selection of master mode now is also available with all other PHY
1006 drivers supporting 1000baseT.
1009 The TCP stack has received a significant update to add support for
1010 modularised congestion control and generally improve the clarity of
1011 congestion control decisions. Bump __FreeBSD_version to 900025. User
1012 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1013 sockstat) need to be recompiled.
1016 The man(1) utility has been replaced by a new version that no longer
1017 uses /etc/manpath.config. Please consult man.conf(5) for how to
1018 migrate local entries to the new format.
1021 The copyright strings printed by login(1) and sshd(8) at the time of a
1022 new connection have been removed to follow other operating systems and
1026 A workaround for a fixed ld bug has been removed in kernel code,
1027 so make sure that your system ld is built from sources after
1028 revision 210245 from 2010-07-19 (r211583 if building head kernel
1029 on stable/8, r211584 for stable/7; both from 2010-08-21).
1030 A symptom of incorrect ld version is different addresses for
1031 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1034 The $ipv6_prefer variable in rc.conf(5) has been split into
1035 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1037 The $ip6addrctl_policy is a variable to choose a pre-defined
1038 address selection policy set by ip6addrctl(8). A value
1039 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1042 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1043 flag (see an entry of 20090926) is set on an interface with no
1044 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1045 security reason. If you want IPv6 link-local address on all
1046 interfaces by default, set this to "YES".
1048 The old ipv6_prefer="YES" is equivalent to
1049 ipv6_activate_all_interfaces="YES" and
1050 ip6addrctl_policy="ipv6_prefer".
1053 DTrace has grown support for userland tracing. Due to this, DTrace is
1054 now i386 and amd64 only.
1055 dtruss(1) is now installed by default on those systems and a new
1056 kernel module is needed for userland tracing: fasttrap.
1057 No changes to your kernel config file are necessary to enable
1058 userland tracing, but you might consider adding 'STRIP=' and
1059 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1060 to have informative userland stack traces in DTrace (ustack).
1063 The acpi_aiboost(4) driver has been removed in favor of the new
1064 aibs(4) driver. You should update your kernel configuration file.
1067 BSD grep has been imported to the base system and it is built by
1068 default. It is completely BSD licensed, highly GNU-compatible, uses
1069 less memory than its GNU counterpart and has a small codebase.
1070 However, it is slower than its GNU counterpart, which is mostly
1071 noticeable for larger searches, for smaller ones it is measurable
1072 but not significant. The reason is complex, the most important factor
1073 is that we lack a modern and efficient regex library and GNU
1074 overcomes this by optimizing the searches internally. Future work
1075 on improving the regex performance is planned, for the meantime,
1076 users that need better performance, can build GNU grep instead by
1077 setting the WITH_GNU_GREP knob.
1080 Due to the import of powerpc64 support, all existing powerpc kernel
1081 configuration files must be updated with a machine directive like this:
1082 machine powerpc powerpc
1084 In addition, an updated config(8) is required to build powerpc kernels
1088 A new version of ZFS (version 15) has been merged to -HEAD.
1089 This version uses a python library for the following subcommands:
1090 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1091 For full functionality of these commands the following port must
1092 be installed: sysutils/py-zfs
1095 'vm_page's are now hashed by physical address to an array of mutexes.
1096 Currently this is only used to serialize access to hold_count. Over
1097 time the page queue mutex will be peeled away. This changes the size
1098 of pmap on every architecture. And requires all callers of vm_page_hold
1099 and vm_page_unhold to be updated.
1102 WITH_CTF can now be specified in src.conf (not recommended, there
1103 are some problems with static executables), make.conf (would also
1104 affect ports which do not use GNU make and do not override the
1105 compile targets) or in the kernel config (via "makeoptions
1107 When WITH_CTF was specified there before this was silently ignored,
1108 so make sure that WITH_CTF is not used in places which could lead
1109 to unwanted behavior.
1112 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1113 to allow 32-bit compatibility on non-x86 platforms. All kernel
1114 configurations on amd64 and ia64 platforms using these options must
1115 be modified accordingly.
1118 The utmp user accounting database has been replaced with utmpx,
1119 the user accounting interface standardized by POSIX.
1120 Unfortunately the semantics of utmp and utmpx don't match,
1121 making it practically impossible to support both interfaces.
1122 The user accounting database is used by tools like finger(1),
1123 last(1), talk(1), w(1) and ac(8).
1125 All applications in the base system use utmpx. This means only
1126 local binaries (e.g. from the ports tree) may still use these
1127 utmp database files. These applications must be rebuilt to make
1130 After the system has been upgraded, it is safe to remove the old
1131 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1132 assuming their contents is of no importance anymore. Old wtmp
1133 databases can only be used by last(1) and ac(8) after they have
1134 been converted to the new format using wtmpcvt(1).
1137 Introduce the kernel thread "deadlock resolver" (which can be enabled
1138 via the DEADLKRES option, see NOTES for more details) and the
1139 sleepq_type() function for sleepqueues.
1142 The rc.firewall and rc.firewall6 were unified, and
1143 rc.firewall6 and rc.d/ip6fw were removed.
1144 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1145 variables are obsoleted. Instead, the following new rc
1146 variables are added to rc.d/ipfw:
1148 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1149 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1150 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1152 The meanings correspond to the relevant IPv4 variables.
1158 The default terminal emulation for syscons(4) has been changed
1159 from cons25 to xterm on all platforms except pc98. This means
1160 that the /etc/ttys file needs to be updated to ensure correct
1161 operation of applications on the console.
1163 The terminal emulation style can be toggled per window by using
1164 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1165 options can be used to change the compile-time default back to
1168 To prevent graphical artifacts, make sure the TERM environment
1169 variable is set to match the terminal emulation that is being
1170 performed by syscons(4).
1173 The layout of the structure ieee80211req_scan_result has changed.
1174 Applications that require wireless scan results (e.g. ifconfig(8))
1175 from net80211 need to be recompiled.
1177 Applications such as wpa_supplicant(8) may require a full world
1178 build without using NO_CLEAN in order to get synchronized with the
1182 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1183 There's one kernel module for each firmware. Adding "device iwnfw"
1184 to the kernel configuration file means including all three firmware
1185 images inside the kernel. If you want to include just the one for
1186 your wireless card, use the devices iwn4965fw, iwn5000fw or
1190 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1191 into rc.d/netif. The changes are the following:
1193 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1194 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1195 Note that both variables need the "inet6" keyword at the head.
1197 Do not set $ipv6_network_interfaces manually if you do not
1198 understand what you are doing. It is not needed in most cases.
1200 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1203 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1204 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1206 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1207 all configured interfaces have "inet6 accept_rtadv" in the
1208 $ifconfig_IF_ipv6. These are for backward compatibility.
1210 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1211 functionality of interfaces with no corresponding
1212 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1213 and the default address selection policy of ip6addrctl(8)
1214 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1215 Note that if you want to configure IPv6 functionality on the
1216 disabled interfaces after boot, first you need to clear the flag by
1217 using ifconfig(8) like:
1219 ifconfig em0 inet6 -ifdisabled
1221 If YES, the default address selection policy is set as
1224 The default value of $ipv6_prefer is NO.
1226 4. If your system need to receive Router Advertisement messages,
1227 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1228 scripts automatically invoke rtsol(8) when the interface becomes
1229 UP. The Router Advertisement messages are used for SLAAC
1230 (State-Less Address AutoConfiguration).
1233 802.11s D3.03 support was committed. This is incompatible with the
1234 previous code, which was based on D3.0.
1237 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1238 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1239 control whether accepting Router Advertisement messages or not.
1240 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1241 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1242 The ifconfig(8) utility now supports these flags.
1245 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1246 mount(8) and -a option for df(1) to see them.
1249 The old tunable hw.bus.devctl_disable has been superseded by
1250 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1251 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1255 Remove the option STOP_NMI. The default action is now to use NMI only
1256 for KDB via the newly introduced function stop_cpus_hard() and
1257 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1260 The stable/8 branch created in subversion. This corresponds to the
1261 RELENG_8 branch in CVS.
1264 Bump the shared library version numbers for all libraries that do not
1265 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1266 __FreeBSD_version to 800105.
1269 Due to changes in the implementation of virtual network stack support,
1270 all network-related kernel modules must be recompiled. As this change
1271 breaks the ABI, bump __FreeBSD_version to 800104.
1274 The TOE interface to the TCP syncache has been modified to remove
1275 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1276 The cxgb driver is the only TOE consumer affected by this change, and
1277 needs to be recompiled along with the kernel. As this change breaks
1278 the ABI, bump __FreeBSD_version to 800103.
1281 Padding has been added to struct tcpcb, sackhint and tcpstat in
1282 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1283 maintaining the ABI. However, this change breaks the ABI, so bump
1284 __FreeBSD_version to 800102. User space tools that rely on the size of
1285 any of these structs (e.g. sockstat) need to be recompiled.
1288 The NFS_LEGACYRPC option has been removed along with the old kernel
1289 RPC implementation that this option selected. Kernel configurations
1290 may need to be adjusted.
1293 The network interface device nodes at /dev/net/<interface> have been
1294 removed. All ioctl operations can be performed the normal way using
1295 routing sockets. The kqueue functionality can generally be replaced
1296 with routing sockets.
1299 The documentation from the FreeBSD Documentation Project (Handbook,
1300 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1301 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1304 The ABI of various structures related to the SYSV IPC API have been
1305 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1306 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1310 Layout of struct vnet has changed as routing related variables were
1311 moved to their own Vimage module. Modules need to be recompiled. Bump
1312 __FreeBSD_version to 800099.
1315 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1316 respectively. As long as no more than 16 groups per process are used,
1317 no changes should be visible. When more than 16 groups are used, old
1318 binaries may fail if they call getgroups() or getgrouplist() with
1319 statically sized storage. Recompiling will work around this, but
1320 applications should be modified to use dynamically allocated storage
1321 for group arrays as POSIX.1-2008 does not cap an implementation's
1322 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1324 NFS and portalfs mounts may also be affected as the list of groups is
1325 truncated to 16. Users of NFS who use more than 16 groups, should
1326 take care that negative group permissions are not used on the exported
1327 file systems as they will not be reliable unless a GSSAPI based
1328 authentication method is used.
1331 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1332 option compiles in the support for adaptive spinning for lockmgrs
1333 which want to enable it. The lockinit() function now accepts the flag
1334 LK_ADAPTIVE in order to make the lock object subject to adaptive
1335 spinning when both held in write and read mode.
1338 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1339 changed. User applications that use this ioctl need to be rebuilt.
1342 The layout of struct thread has changed. Kernel and modules need to
1346 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1347 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1350 window(1) has been removed from the base system. It can now be
1351 installed from ports. The port is called misc/window.
1354 The way we are storing and accessing `routing table' entries has
1355 changed. Programs reading the FIB, like netstat, need to be
1359 A new netisr implementation has been added for FreeBSD 8. Network
1360 file system modules, such as igmp, ipdivert, and others, should be
1362 Bump __FreeBSD_version to 800096.
1365 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1369 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1370 Bump __FreeBSD_version to 800094.
1373 Add mnt_xflag field to 'struct mount'. File system modules need to be
1375 Bump __FreeBSD_version to 800093.
1378 The compiling option ADAPTIVE_SX has been retired while it has been
1379 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1380 The KPI for sx_init_flags() changes as accepting flags:
1381 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1382 been introduced in order to handle the reversed logic.
1383 Bump __FreeBSD_version to 800092.
1386 Add support for hierarchical jails. Remove global securelevel.
1387 Bump __FreeBSD_version to 800091.
1390 The layout of struct vnet_net has changed, therefore modules
1392 Bump __FreeBSD_version to 800090.
1395 The newly imported zic(8) produces a new format in the output. Please
1396 run tzsetup(8) to install the newly created data to /etc/localtime.
1399 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1400 hw.usb.* and is now consistent again with previous releases.
1403 802.11 monitor mode support was revised and driver api's were changed.
1404 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1405 of DLT_IEEE802_11. No user-visible data structures were changed but
1406 applications that use DLT_IEEE802_11 may require changes.
1407 Bump __FreeBSD_version to 800088.
1410 The layout of the following structs has changed: sysctl_oid,
1411 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1412 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1413 panics may be experienced. World rebuild is required for
1414 correctly checking networking state from userland.
1415 Bump __FreeBSD_version to 800085.
1418 MLDv2 and Source-Specific Multicast (SSM) have been merged
1419 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1420 The implementation of SSM within FreeBSD's IPv6 stack closely
1421 follows the IPv4 implementation.
1423 For kernel developers:
1425 * The most important changes are that the ip6_output() and
1426 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1427 and this lock has been downgraded to a non-recursive mutex.
1429 * As with the changes to the IPv4 stack to support SSM, filtering
1430 of inbound multicast traffic must now be performed by transport
1431 protocols within the IPv6 stack. This does not apply to TCP and
1432 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1434 * The KPIs used by IPv6 multicast are similar to those used by
1435 the IPv4 stack, with the following differences:
1436 * im6o_mc_filter() is analogous to imo_multicast_filter().
1437 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1438 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1439 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1440 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1441 for MLDv1 have an additional 'timer' argument which is used to
1442 jitter the initial membership report for the solicited-node
1443 multicast membership on-link.
1444 * This is not strictly needed for MLDv2, which already jitters
1445 its report transmissions. However, the 'timer' argument is
1446 preserved in case MLDv1 is active on the interface.
1448 * The KAME linked-list based IPv6 membership implementation has
1449 been refactored to use a vector similar to that used by the IPv4
1451 Code which maintains a list of its own multicast memberships
1452 internally, e.g. carp, has been updated to reflect the new
1455 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1456 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1457 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1458 implementation constraint which needs to be addressed in HEAD.
1460 For application developers:
1462 * The changes are broadly similar to those made for the IPv4
1465 * The use of IPv4 and IPv6 multicast socket options on the same
1466 socket, using mapped addresses, HAS NOT been tested or supported.
1468 * There are a number of issues with the implementation of various
1469 IPv6 multicast APIs which need to be resolved in the API surface
1470 before the implementation is fully compatible with KAME userland
1471 use, and these are mostly to do with interface index treatment.
1473 * The literature available discusses the use of either the delta / ASM
1474 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1475 using setsourcefilter(3)/getsourcefilter(3). For more information
1476 please refer to RFC 3768, 'Socket Interface Extensions for
1477 Multicast Source Filters'.
1479 * Applications which use the published RFC 3678 APIs should be fine.
1481 For systems administrators:
1483 * The mtest(8) utility has been refactored to support IPv6, in
1484 addition to IPv4. Interface addresses are no longer accepted
1485 as arguments, their names must be used instead. The utility
1486 will map the interface name to its first IPv4 address as
1487 returned by getifaddrs(3).
1489 * The ifmcstat(8) utility has also been updated to print the MLDv2
1490 endpoint state and source filter lists via sysctl(3).
1492 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1493 loopback of IPv6 multicast datagrams by default; it defaults to 1
1494 to preserve the existing behaviour. Disabling multicast loopback is
1495 recommended for optimal system performance.
1497 * The IPv6 MROUTING code has been changed to examine this sysctl
1498 instead of attempting to perform a group lookup before looping
1499 back forwarded datagrams.
1501 Bump __FreeBSD_version to 800084.
1504 Implement low-level Bluetooth HCI API.
1505 Bump __FreeBSD_version to 800083.
1508 The layout of struct malloc_type, used by modules to register new
1509 memory allocation types, has changed. Most modules will need to
1510 be rebuilt or panics may be experienced.
1511 Bump __FreeBSD_version to 800081.
1514 Anticipate overflowing inp_flags - add inp_flags2.
1515 This changes most offsets in inpcb, so checking v4 connection
1516 state will require a world rebuild.
1517 Bump __FreeBSD_version to 800080.
1520 Add an llentry to struct route and struct route_in6. Modules
1521 embedding a struct route will need to be recompiled.
1522 Bump __FreeBSD_version to 800079.
1525 The size of rt_metrics_lite and by extension rtentry has changed.
1526 Networking administration apps will need to be recompiled.
1527 The route command now supports show as an alias for get, weighting
1528 of routes, sticky and nostick flags to alter the behavior of stateful
1530 Bump __FreeBSD_version to 800078.
1533 Do not use Giant for kbdmux(4) locking. This is wrong and
1534 apparently causing more problems than it solves. This will
1535 re-open the issue where interrupt handlers may race with
1536 kbdmux(4) in polling mode. Typical symptoms include (but
1537 not limited to) duplicated and/or missing characters when
1538 low level console functions (such as gets) are used while
1539 interrupts are enabled (for example geli password prompt,
1540 mountroot prompt etc.). Disabling kbdmux(4) may help.
1543 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1544 kernel modules referencing any of the above need to be recompiled.
1545 Bump __FreeBSD_version to 800075.
1548 GEOM_PART has become the default partition slicer for storage devices,
1549 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1550 introduces some changes:
1552 MSDOS/EBR: the devices created from MSDOS extended partition entries
1553 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1554 to devices with offset-based names. fstabs may need to be modified.
1556 BSD: the "geometry does not match label" warning is harmless in most
1557 cases but it points to problems in file system misalignment with
1558 disk geometry. The "c" partition is now implicit, covers the whole
1559 top-level drive and cannot be (mis)used by users.
1561 General: Kernel dumps are now not allowed to be written to devices
1562 whose partition types indicate they are meant to be used for file
1563 systems (or, in case of MSDOS partitions, as something else than
1566 Most of these changes date approximately from 200812.
1569 The uscanner(4) driver has been removed from the kernel. This follows
1570 Linux removing theirs in 2.6 and making libusb the default interface
1571 (supported by sane).
1574 The multicast forwarding code has been cleaned up. netstat(1)
1575 only relies on KVM now for printing bandwidth upcall meters.
1576 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1577 ip6_mroute_mod respectively. The config(5) options for statically
1578 compiling this code remain the same, i.e. 'options MROUTING'.
1581 Support for the IFF_NEEDSGIANT network interface flag has been
1582 removed, which means that non-MPSAFE network device drivers are no
1583 longer supported. In particular, if_ar, if_sr, and network device
1584 drivers from the old (legacy) USB stack can no longer be built or
1588 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1589 a bunch of new language catalog files have also been added.
1590 This means that some common libc messages are now localized and
1591 they depend on the LC_MESSAGES environmental variable.
1594 The k8temp(4) driver has been renamed to amdtemp(4) since
1595 support for Family 10 and Family 11 CPU families was added.
1598 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1599 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1601 For kernel developers, the most important changes are that the
1602 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1603 and this lock has been downgraded to a non-recursive mutex.
1605 Transport protocols (UDP, Raw IP) are now responsible for filtering
1606 inbound multicast traffic according to group membership and source
1607 filters. The imo_multicast_filter() KPI exists for this purpose.
1608 Transports which do not use multicast (SCTP, TCP) already reject
1609 multicast by default. Forwarding and receive performance may improve
1610 as a mutex acquisition is no longer needed in the ip_input()
1611 low-level input path. in_addmulti() and in_delmulti() are shimmed
1612 to new KPIs which exist to support SSM in-kernel.
1614 For application developers, it is recommended that loopback of
1615 multicast datagrams be disabled for best performance, as this
1616 will still cause the lock to be taken for each looped-back
1617 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1618 be tuned to 0 to disable loopback by default; it defaults to 1
1619 to preserve the existing behaviour.
1621 For systems administrators, to obtain best performance with
1622 multicast reception and multiple groups, it is always recommended
1623 that a card with a suitably precise hash filter is used. Hash
1624 collisions will still result in the lock being taken within the
1625 transport protocol input path to check group membership.
1627 If deploying FreeBSD in an environment with IGMP snooping switches,
1628 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1629 enabled; this forces 224.0.0.0/24 group membership to be announced
1632 The size of 'struct igmpstat' has changed; netstat needs to be
1633 recompiled to reflect this.
1634 Bump __FreeBSD_version to 800070.
1637 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1638 updated to use it. This requires a buildworld/installworld in order to
1639 update the library and dependencies (usbconfig, etc). Its advisable to
1640 rebuild all ports which uses libusb. More specific directions are given
1641 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1642 libusb are no longer required and can be removed.
1645 A workaround is committed to allow the creation of System V shared
1646 memory segment of size > 2 GB on the 64-bit architectures.
1647 Due to a limitation of the existing ABI, the shm_segsz member
1648 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1649 wrong for large segments. Note that limits must be explicitly
1650 raised to allow such segments to be created.
1653 The layout of struct ifnet has changed, requiring a rebuild of all
1654 network device driver modules.
1657 The /dev handling for the new USB stack has changed, a
1658 buildworld/installworld is required for libusb20.
1661 The new USB2 stack has now been permanently moved in and all kernel and
1662 module names reverted to their previous values (eg, usb, ehci, ohci,
1663 ums, ...). The old usb stack can be compiled in by prefixing the name
1664 with the letter 'o', the old usb modules have been removed.
1665 Updating entry 20090216 for xorg and 20090215 for libmap may still
1669 The rc.conf(5) option if_up_delay has been renamed to
1670 defaultroute_delay to better reflect its purpose. If you have
1671 customized this setting in /etc/rc.conf you need to update it to
1675 xorg 7.4 wants to configure its input devices via hald which does not
1676 yet work with USB2. If the keyboard/mouse does not work in xorg then
1678 Option "AllowEmptyInput" "off"
1679 to your ServerLayout section. This will cause X to use the configured
1680 kbd and mouse sections from your xorg.conf.
1683 The GENERIC kernels for all architectures now default to the new USB2
1684 stack. No kernel config options or code have been removed so if a
1685 problem arises please report it and optionally revert to the old USB
1686 stack. If you are loading USB kernel modules or have a custom kernel
1687 that includes GENERIC then ensure that usb names are also changed over,
1688 eg uftdi -> usb2_serial_ftdi.
1690 Older programs linked against the ports libusb 0.1 need to be
1691 redirected to the new stack's libusb20. /etc/libmap.conf can
1693 # Map old usb library to new one for usb2 stack
1694 libusb-0.1.so.8 libusb20.so.1
1697 All USB ethernet devices now attach as interfaces under the name ueN
1698 (eg. ue0). This is to provide a predictable name as vendors often
1699 change usb chipsets in a product without notice.
1702 The ichsmb(4) driver has been changed to require SMBus slave
1703 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1704 All of the other SMBus controller drivers require left-justified
1705 slave addresses, so this change makes all the drivers provide the
1709 INET6 statistics (struct ip6stat) was updated.
1710 netstat(1) needs to be recompiled.
1713 NTFS has been removed from GENERIC kernel on amd64 to match
1714 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1715 will load ntfs.ko module automatically when NTFS support is
1716 actually needed, unless ntfs.ko is not installed or security
1717 level prohibits loading kernel modules. If either is the case,
1718 "options NTFS" has to be added into kernel config.
1721 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1722 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1723 800061. User space tools that rely on the size of struct tcpcb in
1724 tcp_var.h (e.g. sockstat) need to be recompiled.
1727 ng_tty(4) module updated to match the new TTY subsystem.
1728 Due to API change, user-level applications must be updated.
1729 New API support added to mpd5 CVS and expected to be present
1730 in next mpd5.3 release.
1733 With __FreeBSD_version 800060 the makefs tool is part of
1734 the base system (it was a port).
1737 The afdata and ifnet locks have been changed from mutexes to
1738 rwlocks, network modules will need to be re-compiled.
1741 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1742 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1743 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1744 architecture and 40 bytes on 64-bit architecture. The userland
1745 applications "arp" and "ndp" have been updated accordingly.
1746 The output from "netstat -r" shows only routing entries and
1747 none of the L2 information.
1750 __FreeBSD_version 800057 marks the switchover from the
1751 binary ath hal to source code. Users must add the line:
1753 options AH_SUPPORT_AR5416
1755 to their kernel config files when specifying:
1759 The ath_hal module no longer exists; the code is now compiled
1760 together with the driver in the ath module. It is now
1761 possible to tailor chip support (i.e. reduce the set of chips
1762 and thereby the code size); consult ath_hal(4) for details.
1765 __FreeBSD_version 800054 adds memory barriers to
1766 <machine/atomic.h>, new interfaces to ifnet to facilitate
1767 multiple hardware transmit queues for cards that support
1768 them, and a lock-less ring-buffer implementation to
1769 enable drivers to more efficiently manage queueing of
1773 A new version of ZFS (version 13) has been merged to -HEAD.
1774 This version has zpool attribute "listsnapshots" off by
1775 default, which means "zfs list" does not show snapshots,
1776 and is the same as Solaris behavior.
1779 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1782 The uhci, ohci, ehci and slhci USB Host controller drivers have
1783 been put into separate modules. If you load the usb module
1784 separately through loader.conf you will need to load the
1785 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1786 controller add the following to loader.conf:
1792 The ABI used by the PMC toolset has changed. Please keep
1793 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1797 atapci kernel module now includes only generic PCI ATA
1798 driver. AHCI driver moved to ataahci kernel module.
1799 All vendor-specific code moved into separate kernel modules:
1800 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1801 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1802 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1803 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1806 The TTY subsystem of the kernel has been replaced by a new
1807 implementation, which provides better scalability and an
1808 improved driver model. Most common drivers have been migrated to
1809 the new TTY subsystem, while others have not. The following
1810 drivers have not yet been ported to the new TTY layer:
1813 cy, digi, rc, rp, sio
1819 ng_h4, ng_tty, ppp, sl, snp
1821 Adding these drivers to your kernel configuration file shall
1822 cause compilation to fail.
1825 ntpd has been upgraded to 4.2.4p5.
1828 OpenSSH has been upgraded to 5.1p1.
1830 For many years, FreeBSD's version of OpenSSH preferred DSA
1831 over RSA for host and user authentication keys. With this
1832 upgrade, we've switched to the vendor's default of RSA over
1833 DSA. This may cause upgraded clients to warn about unknown
1834 host keys even for previously known hosts. Users should
1835 follow the usual procedure for verifying host keys before
1836 accepting the RSA key.
1838 This can be circumvented by setting the "HostKeyAlgorithms"
1839 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1842 Please note that the sequence of keys offered for
1843 authentication has been changed as well. You may want to
1844 specify IdentityFile in a different order to revert this
1848 The sio(4) driver has been removed from the i386 and amd64
1849 kernel configuration files. This means uart(4) is now the
1850 default serial port driver on those platforms as well.
1852 To prevent collisions with the sio(4) driver, the uart(4) driver
1853 uses different names for its device nodes. This means the
1854 onboard serial port will now most likely be called "ttyu0"
1855 instead of "ttyd0". You may need to reconfigure applications to
1856 use the new device names.
1858 When using the serial port as a boot console, be sure to update
1859 /boot/device.hints and /etc/ttys before booting the new kernel.
1860 If you forget to do so, you can still manually specify the hints
1861 at the loader prompt:
1863 set hint.uart.0.at="isa"
1864 set hint.uart.0.port="0x3F8"
1865 set hint.uart.0.flags="0x10"
1866 set hint.uart.0.irq="4"
1870 The gpt(8) utility has been removed. Use gpart(8) to partition
1874 The version that Linuxulator emulates was changed from 2.4.2
1875 to 2.6.16. If you experience any problems with Linux binaries
1876 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1877 if it fixes the problem contact emulation mailing list.
1880 ISDN4BSD (I4B) was removed from the src tree. You may need to
1881 update a your kernel configuration and remove relevant entries.
1884 I have checked in code to support multiple routing tables.
1885 See the man pages setfib(1) and setfib(2).
1886 This is a hopefully backwards compatible version,
1887 but to make use of it you need to compile your kernel
1888 with options ROUTETABLES=2 (or more up to 16).
1891 The 802.11 wireless support was redone to enable multi-bss
1892 operation on devices that are capable. The underlying device
1893 is no longer used directly but instead wlanX devices are
1894 cloned with ifconfig. This requires changes to rc.conf files.
1895 For example, change:
1896 ifconfig_ath0="WPA DHCP"
1899 ifconfig_wlan0="WPA DHCP"
1900 see rc.conf(5) for more details. In addition, mergemaster of
1901 /etc/rc.d is highly recommended. Simultaneous update of userland
1902 and kernel wouldn't hurt either.
1904 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1905 modules were merged into the base wlan module. All references
1906 to these modules (e.g. in kernel config files) must be removed.
1909 psm(4) has gained write(2) support in native operation level.
1910 Arbitrary commands can be written to /dev/psm%d and status can
1911 be read back from it. Therefore, an application is responsible
1912 for status validation and error recovery. It is a no-op in
1913 other operation levels.
1916 Support for KSE threading has been removed from the kernel. To
1917 run legacy applications linked against KSE libmap.conf may
1918 be used. The following libmap.conf may be used to ensure
1919 compatibility with any prior release:
1921 libpthread.so.1 libthr.so.1
1922 libpthread.so.2 libthr.so.2
1923 libkse.so.3 libthr.so.3
1926 The layout of struct vmspace has changed. This affects libkvm
1927 and any executables that link against libkvm and use the
1928 kvm_getprocs() function. In particular, but not exclusively,
1929 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1930 The effects are minimal, but it's advisable to upgrade world
1934 The latest em driver no longer has support in it for the
1935 82575 adapter, this is now moved to the igb driver. The
1936 split was done to make new features that are incompatible
1937 with older hardware easier to do.
1940 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1941 likewise the kernel option is now GEOM_LINUX_LVM.
1944 The default NFS mount mode has changed from UDP to TCP for
1945 increased reliability. If you rely on (insecurely) NFS
1946 mounting across a firewall you may need to update your
1950 Belatedly note the addition of m_collapse for compacting
1954 The fts(3) structures have been changed to use adequate
1955 integer types for their members and so to be able to cope
1956 with huge file trees. The old fts(3) ABI is preserved
1957 through symbol versioning in libc, so third-party binaries
1958 using fts(3) should still work, although they will not take
1959 advantage of the extended types. At the same time, some
1960 third-party software might fail to build after this change
1961 due to unportable assumptions made in its source code about
1962 fts(3) structure members. Such software should be fixed
1963 by its vendor or, in the worst case, in the ports tree.
1964 FreeBSD_version 800015 marks this change for the unlikely
1965 case that a portable fix is impossible.
1968 To upgrade to -current after this date, you must be running
1969 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1970 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1973 The ADAPTIVE_GIANT kernel option has been retired because its
1974 functionality is the default now.
1977 The AT keyboard emulation of sunkbd(4) has been turned on
1978 by default. In order to make the special symbols of the Sun
1979 keyboards driven by sunkbd(4) work under X these now have
1980 to be configured the same way as Sun USB keyboards driven
1981 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1983 Option "XkbLayout" "us"
1984 Option "XkbRules" "xorg"
1985 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1988 It has been decided that it is desirable to provide ABI
1989 backwards compatibility to the FreeBSD 4/5/6 versions of the
1990 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1991 broken with the introduction of PCI domain support (see the
1992 20070930 entry). Unfortunately, this required the ABI of
1993 PCIOCGETCONF to be broken again in order to be able to
1994 provide backwards compatibility to the old version of that
1995 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1996 again. As for prominent ports this affects neither pciutils
1997 nor xorg-server this time, the hal port needs to be rebuilt
2001 The misnamed kthread_create() and friends have been renamed
2002 to kproc_create() etc. Many of the callers already
2003 used kproc_start()..
2004 I will return kthread_create() and friends in a while
2005 with implementations that actually create threads, not procs.
2006 Renaming corresponds with version 800002.
2015 Avoid using make -j when upgrading. While generally safe, there are
2016 sometimes problems using -j to upgrade. If your upgrade fails with
2017 -j, please try again without -j. From time to time in the past there
2018 have been problems using -j with buildworld and/or installworld. This
2019 is especially true when upgrading between "distant" versions (eg one
2020 that cross a major release boundary or several minor releases, or when
2021 several months have passed on the -current branch).
2023 Sometimes, obscure build problems are the result of environment
2024 poisoning. This can happen because the make utility reads its
2025 environment when searching for values for global variables. To run
2026 your build attempts in an "environmental clean room", prefix all make
2027 commands with 'env -i '. See the env(1) manual page for more details.
2029 When upgrading from one major version to another it is generally best
2030 to upgrade to the latest code in the currently installed branch first,
2031 then do an upgrade to the new branch. This is the best-tested upgrade
2032 path, and has the highest probability of being successful. Please try
2033 this approach before reporting problems with a major version upgrade.
2035 When upgrading a live system, having a root shell around before
2036 installing anything can help undo problems. Not having a root shell
2037 around can lead to problems if pam has changed too much from your
2038 starting point to allow continued authentication after the upgrade.
2042 When upgrading the boot ZFS pool to a new version, always follow
2045 1.) recompile and reinstall the ZFS boot loader and boot block
2046 (this is part of "make buildworld" and "make installworld")
2048 2.) update the ZFS boot block on your boot drive
2050 The following example updates the ZFS boot block on the first
2051 partition (freebsd-boot) of a GPT partitioned drive ad0:
2052 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2054 Non-boot pools do not need these updates.
2058 If you are updating from a prior version of FreeBSD (even one just
2059 a few days old), you should follow this procedure. It is the most
2060 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2062 make kernel-toolchain
2063 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2064 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2066 To test a kernel once
2067 ---------------------
2068 If you just want to boot a kernel once (because you are not sure
2069 if it works, or if you want to boot a known bad kernel to provide
2070 debugging information) run
2071 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2072 nextboot -k testkernel
2074 To just build a kernel when you know that it won't mess you up
2075 --------------------------------------------------------------
2076 This assumes you are already running a CURRENT system. Replace
2077 ${arch} with the architecture of your machine (e.g. "i386",
2078 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2080 cd src/sys/${arch}/conf
2081 config KERNEL_NAME_HERE
2082 cd ../compile/KERNEL_NAME_HERE
2087 If this fails, go to the "To build a kernel" section.
2089 To rebuild everything and install it on the current system.
2090 -----------------------------------------------------------
2091 # Note: sometimes if you are running current you gotta do more than
2092 # is listed here if you are upgrading from a really old current.
2094 <make sure you have good level 0 dumps>
2096 make kernel KERNCONF=YOUR_KERNEL_HERE
2098 <reboot in single user> [3]
2105 To cross-install current onto a separate partition
2106 --------------------------------------------------
2107 # In this approach we use a separate partition to hold
2108 # current's root, 'usr', and 'var' directories. A partition
2109 # holding "/", "/usr" and "/var" should be about 2GB in
2112 <make sure you have good level 0 dumps>
2115 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2116 <maybe newfs current's root partition>
2117 <mount current's root partition on directory ${CURRENT_ROOT}>
2118 make installworld DESTDIR=${CURRENT_ROOT}
2119 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2120 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2121 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2122 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2123 <reboot into current>
2124 <do a "native" rebuild/install as described in the previous section>
2125 <maybe install compatibility libraries from ports/misc/compat*>
2129 To upgrade in-place from stable to current
2130 ----------------------------------------------
2131 <make sure you have good level 0 dumps>
2133 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2135 <reboot in single user> [3]
2142 Make sure that you've read the UPDATING file to understand the
2143 tweaks to various things you need. At this point in the life
2144 cycle of current, things change often and you are on your own
2145 to cope. The defaults can also change, so please read ALL of
2146 the UPDATING entries.
2148 Also, if you are tracking -current, you must be subscribed to
2149 freebsd-current@freebsd.org. Make sure that before you update
2150 your sources that you have read and understood all the recent
2151 messages there. If in doubt, please track -stable which has
2152 much fewer pitfalls.
2154 [1] If you have third party modules, such as vmware, you
2155 should disable them at this point so they don't crash your
2158 [3] From the bootblocks, boot -s, and then do
2163 adjkerntz -i # if CMOS is wall time
2164 Also, when doing a major release upgrade, it is required that
2165 you boot into single user mode to do the installworld.
2167 [4] Note: This step is non-optional. Failure to do this step
2168 can result in a significant reduction in the functionality of the
2169 system. Attempting to do it by hand is not recommended and those
2170 that pursue this avenue should read this file carefully, as well
2171 as the archives of freebsd-current and freebsd-hackers mailing lists
2172 for potential gotchas. The -U option is also useful to consider.
2173 See mergemaster(8) for more information.
2175 [5] Usually this step is a noop. However, from time to time
2176 you may need to do this if you get unknown user in the following
2177 step. It never hurts to do it all the time. You may need to
2178 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2179 install) after the buildworld before this step if you last updated
2180 from current before 20130425 or from -stable before 20130430.
2182 [6] This only deletes old files and directories. Old libraries
2183 can be deleted by "make delete-old-libs", but you have to make
2184 sure that no program is using those libraries anymore.
2186 [8] In order to have a kernel that can run the 4.x binaries needed to
2187 do an installworld, you must include the COMPAT_FREEBSD4 option in
2188 your kernel. Failure to do so may leave you with a system that is
2189 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2190 required to run the 5.x binaries on more recent kernels. And so on
2191 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2193 Make sure that you merge any new devices from GENERIC since the
2194 last time you updated your kernel config file.
2196 [9] When checking out sources, you must include the -P flag to have
2197 cvs prune empty directories.
2199 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2200 "?=" instead of the "=" assignment operator, so that buildworld can
2201 override the CPUTYPE if it needs to.
2203 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2204 not on the command line, or in /etc/make.conf. buildworld will
2205 warn if it is improperly defined.
2208 This file contains a list, in reverse chronological order, of major
2209 breakages in tracking -current. It is not guaranteed to be a complete
2210 list of such breakages, and only contains entries since October 10, 2007.
2211 If you need to see UPDATING entries from before that date, you will need
2212 to fetch an UPDATING file from an older FreeBSD release.
2214 Copyright information:
2216 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2218 Redistribution, publication, translation and use, with or without
2219 modification, in full or in part, in any form or format of this
2220 document are permitted without further permission from the author.
2222 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2223 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2224 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2225 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2226 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2227 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2228 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2229 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2230 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2231 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2232 POSSIBILITY OF SUCH DAMAGE.
2234 Contact Warner Losh if you have any questions about your use of