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 r292223 changed the internal interface between the nfsd.ko and
21 nfscommon.ko modules. As such, they must both be upgraded to-gether.
22 __FreeBSD_version has been bumped because of this.
25 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
26 Kernel modules isp_2400_multi and isp_2500_multi were removed and
27 should be replaced with isp_2400 and isp_2500 modules respectively.
30 NTP has been upgraded to 4.2.8p4.
33 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
34 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
35 and devel/kyua to version 0.20+ and adjust any calling code to work
36 with Kyuafile and kyua.
39 The polarity of Pulse Per Second (PPS) capture events with the
40 uart(4) driver has been corrected. Prior to this change the PPS
41 "assert" event corresponded to the trailing edge of a positive PPS
42 pulse and the "clear" event was the leading edge of the next pulse.
44 As the width of a PPS pulse in a typical GPS receiver is on the
45 order of 1 millisecond, most users will not notice any significant
46 difference with this change.
48 Anyone who has compensated for the historical polarity reversal by
49 configuring a negative offset equal to the pulse width will need to
50 remove that workaround.
53 From legacy ata(4) driver was removed support for SATA controllers
54 supported by more functional drivers ahci(4), siis(4) and mvs(4).
55 Kernel modules ataahci and ataadaptec were removed completely,
56 replaced by ahci and mvs modules respectively.
62 As ZFS requires more kernel stack pages than is the default on some
63 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
64 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
66 Please consider using 'options KSTACK_PAGES=X' where X is greater
67 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
70 The default Unbound configuration now enables remote control
71 using a local socket. Users who have already enabled the
72 local_unbound service should regenerate their configuration
73 by running "service local_unbound setup" as root.
76 An additional fix for the issue described in the 20150614 sendmail
77 entry below has been been committed in revision 284786.
80 The fix for the issue described in the 20150614 sendmail entry
81 below has been been committed in revision 284485. The work
82 around described in that entry is no longer needed unless the
83 default setting is overridden by a confDH_PARAMETERS configuration
84 setting of '5' or pointing to a 512 bit DH parameter file.
87 The import of openssl to address the FreeBSD-SA-15:10.openssl
88 security advisory includes a change which rejects handshakes
89 with DH parameters below 768 bits. sendmail releases prior
90 to 8.15.2 (not yet released), defaulted to a 512 bit
91 DH parameter setting for client connections. To work around
92 this interoperability, sendmail can be configured to use a
93 2048 bit DH parameter by:
95 1. Edit /etc/mail/`hostname`.mc
96 2. If a setting for confDH_PARAMETERS does not exist or
97 exists and is set to a string beginning with '5',
99 3. If a setting for confDH_PARAMETERS exists and is set to
100 a file path, create a new file with:
101 openssl dhparam -out /path/to/file 2048
102 4. Rebuild the .cf file:
103 cd /etc/mail/; make; make install
105 cd /etc/mail/; make restart
107 A sendmail patch is coming, at which time this file will be
111 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
112 defined in symlink(7); previously symlinks were silently ignored.
115 The const qualifier has been removed from iconv(3) to comply with
116 POSIX. The ports tree is aware of this from r384038 onwards.
119 At svn r275807, The default linux compat kernel ABI has been adjusted
120 to 2.6.18 in support of the linux-c6 compat ports infrastructure
121 update. If you wish to continue using the linux-f10 compat ports,
122 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
123 encouraged to update their linux-compat packages to linux-c6 during
124 their next update cycle.
126 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
129 pjdfstest has been integrated into kyua as an opt-in test suite.
130 Please see share/doc/pjdfstest/README for a more details on how to
137 The ofwfb driver, used to provide a graphics console on PowerPC when
138 using vt(4), no longer allows mmap() of all of physical memory. This
139 will prevent Xorg on PowerPC with some ATI graphics cards from
140 initializing properly unless x11-servers/xorg-server is updated to
144 The libatf-c and libatf-c++ major versions were downgraded to 0 and
145 1 respectively to match the upstream numbers. They were out of
146 sync because, when they were originally added to FreeBSD, the
147 upstream versions were not respected. These libraries are private
148 and not yet built by default, so renumbering them should be a
149 non-issue. However, unclean source trees will yield broken test
150 programs once the operator executes "make delete-old-libs" after a
153 Additionally, the atf-sh binary was made private by moving it into
154 /usr/libexec/. Already-built shell test programs will keep the
155 path to the old binary so they will break after "make delete-old"
158 If you are using WITH_TESTS=yes (not the default), wipe the object
159 tree and rebuild from scratch to prevent spurious test failures.
160 This is only needed once: the misnumbered libraries and misplaced
161 binaries have been added to OptionalObsoleteFiles.inc so they will
162 be removed during a clean upgrade.
165 The ixgbe tunables now match their sysctl counterparts, for example:
166 hw.ixgbe.enable_aim => hw.ix.enable_aim
167 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
170 The NFSv4.1 server committed by r269398 changes the internal
171 function call interfaces used between the NFS and krpc modules.
172 As such, __FreeBSD_version was bumped.
175 The default unbound configuration has been modified to address
176 issues with reverse lookups on networks that use private
177 address ranges. If you use the local_unbound service, run
178 "service local_unbound setup" as root to regenerate your
179 configuration, then "service local_unbound reload" to load the
183 It is no longer necessary to include the dwarf version in your DEBUG
184 options in your kernel config file. The bug that required it to be
185 placed in the config file has bene fixed. DEBUG should now just
186 contain -g. The build system will automatically update things
187 to do the right thing.
190 Several ABI breaking changes were merged to CTL and new iSCSI code.
191 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
192 iscsictl need to be rebuilt to work with a new kernel.
195 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
196 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
197 which differs from the behaviour controlled by this knob.)
200 On i386 and amd64 systems, the onifconsole flag is now set by default
201 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
202 as a login TTY if it is set in the bootloader as an active kernel
203 console. No changes in behavior should result otherwise. To revert to
204 the previous behavior, set ttyu0 to "off" in /etc/ttys.
207 Clang and llvm have been upgraded to 3.4.1 release.
210 Clang and llvm have been upgraded to 3.4 release.
213 If a Makefile in a tests/ directory was auto-generating a Kyuafile
214 instead of providing an explicit one, this would prevent such
215 Makefile from providing its own Kyuafile in the future during
216 NO_CLEAN builds. This has been fixed in the Makefiles but manual
217 intervention is needed to clean an objdir if you use NO_CLEAN:
218 # find /usr/obj -name Kyuafile | xargs rm -f
221 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
222 capability mode support. Please note that enabling the feature in
223 kernel is still highly recommended.
226 OpenSSH is now built with sandbox support, and will use sandbox as
227 the default privilege separation method. This requires Capsicum
228 capability mode support in kernel.
231 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
232 been deprecated and will not be part of FreeBSD 11.0 and later
233 releases. If you use this driver, please consider switching to
234 the nfe(4) driver instead.
240 The behavior of gss_pseudo_random() for the krb5 mechanism
241 has changed, for applications requesting a longer random string
242 than produced by the underlying enctype's pseudo-random() function.
243 In particular, the random string produced from a session key of
244 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
245 be different at the 17th octet and later, after this change.
246 The counter used in the PRF+ construction is now encoded as a
247 big-endian integer in accordance with RFC 4402.
248 __FreeBSD_version is bumped to 1000701.
251 The WITHOUT_ATF build knob has been removed and its functionality
252 has been subsumed into the more generic WITHOUT_TESTS. If you were
253 using the former to disable the build of the ATF libraries, you
254 should change your settings to use the latter.
257 The default version of mtree is nmtree which is obtained from
258 NetBSD. The output is generally the same, but may vary
259 slightly. If you found you need identical output adding
260 "-F freebsd9" to the command line should do the trick. For the
261 time being, the old mtree is available as fmtree.
264 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
265 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
266 1.1.4_8 and verify bsdyml not linked in, before running "make
268 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
270 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
273 The rc.d/jail script has been updated to support jail(8)
274 configuration file. The "jail_<jname>_*" rc.conf(5) variables
275 for per-jail configuration are automatically converted to
276 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
277 This is transparently backward compatible. See below about some
278 incompatibilities and rc.conf(5) manual page for more details.
280 These variables are now deprecated in favor of jail(8) configuration
281 file. One can use "rc.d/jail config <jname>" command to generate
282 a jail(8) configuration file in /var/run/jail.<jname>.conf without
283 running the jail(8) utility. The default pathname of the
284 configuration file is /etc/jail.conf and can be specified by
285 using $jail_conf or $jail_<jname>_conf variables.
287 Please note that jail_devfs_ruleset accepts an integer at
288 this moment. Please consider to rewrite the ruleset name
292 BIND has been removed from the base system. If all you need
293 is a local resolver, simply enable and start the local_unbound
294 service instead. Otherwise, several versions of BIND are
295 available in the ports tree. The dns/bind99 port is one example.
297 With this change, nslookup(1) and dig(1) are no longer in the base
298 system. Users should instead use host(1) and drill(1) which are
299 in the base system. Alternatively, nslookup and dig can
300 be obtained by installing the dns/bind-tools port.
303 With the addition of unbound(8), a new unbound user is now
304 required during installworld. "mergemaster -p" can be used to
305 add the user prior to installworld, as documented in the handbook.
308 OpenSSH is now built with DNSSEC support, and will by default
309 silently trust signed SSHFP records. This can be controlled with
310 the VerifyHostKeyDNS client configuration setting. DNSSEC support
311 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
314 The GNU Compiler Collection and C++ standard library (libstdc++)
315 are no longer built by default on platforms where clang is the system
316 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
320 The PROCDESC kernel option is now part of the GENERIC kernel
321 configuration and is required for the rwhod(8) to work.
322 If you are using custom kernel configuration, you should include
326 The API and ABI related to the Capsicum framework was modified
327 in backward incompatible way. The userland libraries and programs
328 have to be recompiled to work with the new kernel. This includes the
329 following libraries and programs, but the whole buildworld is
330 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
331 kdump, procstat, rwho, rwhod, uniq.
334 AES-NI intrinsic support has been added to gcc. The AES-NI module
335 has been updated to use this support. A new gcc is required to build
336 the aesni module on both i386 and amd64.
339 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
340 Thus "device padlock_rng" and "device rdrand_rng" should be
341 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
344 WITH_ICONV has been split into two feature sets. WITH_ICONV now
345 enables just the iconv* functionality and is now on by default.
346 WITH_LIBICONV_COMPAT enables the libiconv api and link time
347 compatability. Set WITHOUT_ICONV to build the old way.
348 If you have been using WITH_ICONV before, you will very likely
349 need to turn on WITH_LIBICONV_COMPAT.
352 INVARIANTS option now enables DEBUG for code with OpenSolaris and
353 Illumos origin, including ZFS. If you have INVARIANTS in your
354 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
356 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
357 locks if WITNESS option was set. Because that generated a lot of
358 witness(9) reports and all of them were believed to be false
359 positives, this is no longer done. New option OPENSOLARIS_WITNESS
360 can be used to achieve the previous behavior.
363 Timer values in IPv6 data structures now use time_uptime instead
364 of time_second. Although this is not a user-visible functional
365 change, userland utilities which directly use them---ndp(8),
366 rtadvd(8), and rtsold(8) in the base system---need to be updated
370 find -delete can now delete the pathnames given as arguments,
371 instead of only files found below them or if the pathname did
372 not contain any slashes. Formerly, the following error message
375 find: -delete: <path>: relative path potentially not safe
377 Deleting the pathnames given as arguments can be prevented
378 without error messages using -mindepth 1 or by changing
379 directory and passing "." as argument to find. This works in the
380 old as well as the new version of find.
383 Behavior of devfs rules path matching has been changed.
384 Pattern is now always matched against fully qualified devfs
385 path and slash characters must be explicitly matched by
386 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
387 subdirectories must be reviewed.
390 The default ARM ABI has changed to the ARM EABI. The old ABI is
391 incompatible with the ARM EABI and all programs and modules will
392 need to be rebuilt to work with a new kernel.
394 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
396 NOTE: Support for the old ABI will be removed in the future and
397 users are advised to upgrade.
400 pkg_install has been disconnected from the build if you really need it
401 you should add WITH_PKGTOOLS in your src.conf(5).
404 Most of network statistics structures were changed to be able
405 keep 64-bits counters. Thus all tools, that work with networking
406 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
409 Fix a bug that allowed a tracing process (e.g. gdb) to write
410 to a memory-mapped file in the traced process's address space
411 even if neither the traced process nor the tracing process had
412 write access to that file.
415 CVS has been removed from the base system. An exact copy
416 of the code is available from the devel/cvs port.
419 Some people report the following error after the switch to bmake:
421 make: illegal option -- J
422 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
424 *** [buildworld] Error code 2
426 this likely due to an old instance of make in
427 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
428 which src/Makefile will use that blindly, if it exists, so if
429 you see the above error:
431 rm -rf `make -V MAKEPATH`
436 Use bmake by default.
437 Whereas before one could choose to build with bmake via
438 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
439 make. The goal is to remove these knobs for 10-RELEASE.
441 It is worth noting that bmake (like gmake) treats the command
442 line as the unit of failure, rather than statements within the
443 command line. Thus '(cd some/where && dosomething)' is safer
444 than 'cd some/where; dosomething'. The '()' allows consistent
445 behavior in parallel build.
448 Fix a bug that allows NFS clients to issue READDIR on files.
451 The WITHOUT_IDEA option has been removed because
452 the IDEA patent expired.
455 The sysctl which controls TRIM support under ZFS has been renamed
456 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
460 The mergemaster command now uses the default MAKEOBJDIRPREFIX
461 rather than creating it's own in the temporary directory in
462 order allow access to bootstrapped versions of tools such as
463 install and mtree. When upgrading from version of FreeBSD where
464 the install command does not support -l, you will need to
465 install a new mergemaster command if mergemaster -p is required.
466 This can be accomplished with the command (cd src/usr.sbin/mergemaster
470 Legacy ATA stack, disabled and replaced by new CAM-based one since
471 FreeBSD 9.0, completely removed from the sources. Kernel modules
472 atadisk and atapi*, user-level tools atacontrol and burncd are
473 removed. Kernel option `options ATA_CAM` is now permanently enabled
477 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
478 and socketpair(2). Software, in particular Kerberos, may
479 automatically detect and use these during building. The resulting
480 binaries will not work on older kernels.
483 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
484 information, see the respective 20130304 entry).
487 Recent commits to callout(9) changed the size of struct callout,
488 so the KBI is probably heavily disturbed. Also, some functions
489 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
490 by macros. Every kernel module using it won't load, so rebuild
493 The ctl device has been re-enabled in GENERIC for i386 and amd64,
494 but does not initialize by default (because of the new CTL_DISABLE
495 option) to save memory. To re-enable it, remove the CTL_DISABLE
496 option from the kernel config file or set kern.cam.ctl.disable=0
497 in /boot/loader.conf.
500 The ctl device has been disabled in GENERIC for i386 and amd64.
501 This was done due to the extra memory being allocated at system
502 initialisation time by the ctl driver which was only used if
503 a CAM target device was created. This makes a FreeBSD system
504 unusable on 128MB or less of RAM.
507 A new compression method (lz4) has been merged to -HEAD. Please
508 refer to zpool-features(7) for more information.
510 Please refer to the "ZFS notes" section of this file for information
511 on upgrading boot ZFS pools.
514 A BSD-licensed patch(1) variant has been added and is installed
515 as bsdpatch, being the GNU version the default patch.
516 To inverse the logic and use the BSD-licensed one as default,
517 while having the GNU version installed as gnupatch, rebuild
518 and install world with the WITH_BSD_PATCH knob set.
521 Due to the use of the new -l option to install(1) during build
522 and install, you must take care not to directly set the INSTALL
523 make variable in your /etc/make.conf, /etc/src.conf, or on the
524 command line. If you wish to use the -C flag for all installs
525 you may be able to add INSTALL+=-C to /etc/make.conf or
529 The install(1) option -M has changed meaning and now takes an
530 argument that is a file or path to append logs to. In the
531 unlikely event that -M was the last option on the command line
532 and the command line contained at least two files and a target
533 directory the first file will have logs appended to it. The -M
534 option served little practical purpose in the last decade so its
535 use is expected to be extremely rare.
538 After switching to Clang as the default compiler some users of ZFS
539 on i386 systems started to experience stack overflow kernel panics.
540 Please consider using 'options KSTACK_PAGES=4' in such configurations.
543 GEOM_LABEL now mangles label names read from file system metadata.
544 Mangling affect labels containing spaces, non-printable characters,
545 '%' or '"'. Device names in /etc/fstab and other places may need to
549 By default, only the 10 most recent kernel dumps will be saved. To
550 restore the previous behaviour (no limit on the number of kernel dumps
551 stored in the dump directory) add the following line to /etc/rc.conf:
556 With the addition of auditdistd(8), a new auditdistd user is now
557 required during installworld. "mergemaster -p" can be used to
558 add the user prior to installworld, as documented in the handbook.
561 The sin6_scope_id member variable in struct sockaddr_in6 is now
562 filled by the kernel before passing the structure to the userland via
563 sysctl or routing socket. This means the KAME-specific embedded scope
564 id in sin6_addr.s6_addr[2] is always cleared in userland application.
565 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
566 __FreeBSD_version is bumped to 1000025.
569 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
570 This means that the world and kernel will be compiled with clang
571 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
572 and /usr/bin/cpp. To disable this behavior and revert to building
573 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
574 of current may need to bootstrap WITHOUT_CLANG first if the clang
575 build fails (its compatibility window doesn't extend to the 9 stable
579 The IPFIREWALL_FORWARD kernel option has been removed. Its
580 functionality now turned on by default.
583 The ZERO_COPY_SOCKET kernel option has been removed and
584 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
585 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
586 mechanism which is not safe and may result in kernel crashes.
587 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
588 driver supports disposeable external page sized mbuf storage.
589 Proper replacements for both zero-copy mechanisms are under
590 consideration and will eventually lead to complete removal
591 of the two kernel options.
594 The IPv4 network stack has been converted to network byte
595 order. The following modules need to be recompiled together
596 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
597 pf(4), ipfw(4), ng_ipfw(4), stf(4).
600 Support for non-MPSAFE filesystems was removed from VFS. The
601 VFS_VERSION was bumped, all filesystem modules shall be
605 All the non-MPSAFE filesystems have been disconnected from
606 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
607 portalfs, smbfs, xfs.
610 The interface cloning API and ABI has changed. The following
611 modules need to be recompiled together with kernel:
612 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
613 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
614 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
617 The sdhci driver was split in two parts: sdhci (generic SD Host
618 Controller logic) and sdhci_pci (actual hardware driver).
619 No kernel config modifications are required, but if you
620 load sdhc as a module you must switch to sdhci_pci instead.
623 Import the FUSE kernel and userland support into base system.
626 The GNU sort(1) program has been removed since the BSD-licensed
627 sort(1) has been the default for quite some time and no serious
628 problems have been reported. The corresponding WITH_GNU_SORT
632 The pfil(9) API/ABI for AF_INET family has been changed. Packet
633 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
637 The net80211(4) ABI has been changed to allow for improved driver
638 PS-POLL and power-save support. All wireless drivers need to be
639 recompiled to work with the new kernel.
642 The random(4) support for the VIA hardware random number
643 generator (`PADLOCK') is no longer enabled unconditionally.
644 Add the padlock_rng device in the custom kernel config if
645 needed. The GENERIC kernels on i386 and amd64 do include the
646 device, so the change only affects the custom kernel
650 The pf(4) packet filter ABI has been changed. pfctl(8) and
651 snmp_pf module need to be recompiled to work with new kernel.
654 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
655 to -HEAD. Pools that have empty_bpobj in active state can not be
656 imported read-write with ZFS implementations that do not support
657 this feature. For more information read the zpool-features(5)
661 The sparc64 ZFS loader has been changed to no longer try to auto-
662 detect ZFS providers based on diskN aliases but now requires these
663 to be explicitly listed in the OFW boot-device environment variable.
666 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
667 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
668 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
671 The following sysctls and tunables have been renamed for consistency
672 with other variables:
673 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
674 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
677 The sort utility has been replaced with BSD sort. For now, GNU sort
678 is also available as "gnusort" or the default can be set back to
679 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
680 installed as "bsdsort".
683 A new version of ZFS (pool version 5000) has been merged to -HEAD.
684 Starting with this version the old system of ZFS pool versioning
685 is superseded by "feature flags". This concept enables forward
686 compatibility against certain future changes in functionality of ZFS
687 pools. The first read-only compatible "feature flag" for ZFS pools
688 is named "com.delphix:async_destroy". For more information
689 read the new zpool-features(5) manual page.
690 Please refer to the "ZFS notes" section of this file for information
691 on upgrading boot ZFS pools.
694 The malloc(3) implementation embedded in libc now uses sources imported
695 as contrib/jemalloc. The most disruptive API change is to
696 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
697 delete it prior to installworld, and optionally re-create it using the
698 new format after rebooting. See malloc.conf(5) for details
699 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
703 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
704 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
705 now spelled mips. This is to aid compatibility with third-party
706 software that expects this naming scheme in uname(3). Little-endian
707 settings are unchanged. If you are updating a big-endian mips64 machine
708 from before this change, you may need to set MACHINE_ARCH=mips64 in
709 your environment before the new build system will recognize your machine.
712 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
716 Now unix domain sockets behave "as expected" on nullfs(5). Previously
717 nullfs(5) did not pass through all behaviours to the underlying layer,
718 as a result if we bound to a socket on the lower layer we could connect
719 only to the lower path; if we bound to the upper layer we could connect
720 only to the upper path. The new behavior is one can connect to both the
721 lower and the upper paths regardless what layer path one binds to.
724 The getifaddrs upgrade path broken with 20111215 has been restored.
725 If you have upgraded in between 20111215 and 20120209 you need to
726 recompile libc again with your kernel. You still need to recompile
727 world to be able to configure CARP but this restriction already
731 The set_rcvar() function has been removed from /etc/rc.subr. All
732 base and ports rc.d scripts have been updated, so if you have a
733 port installed with a script in /usr/local/etc/rc.d you can either
734 hand-edit the rcvar= line, or reinstall the port.
736 An easy way to handle the mass-update of /etc/rc.d:
737 rm /etc/rc.d/* && mergemaster -i
740 panic(9) now stops other CPUs in the SMP systems, disables interrupts
741 on the current CPU and prevents other threads from running.
742 This behavior can be reverted using the kern.stop_scheduler_on_panic
744 The new behavior can be incompatible with kern.sync_on_panic.
747 The carp(4) facility has been changed significantly. Configuration
748 of the CARP protocol via ifconfig(8) has changed, as well as format
749 of CARP events submitted to devd(8) has changed. See manual pages
750 for more information. The arpbalance feature of carp(4) is currently
751 not supported anymore.
753 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
754 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
755 need to be recompiled.
758 The acpi_wmi(4) status device /dev/wmistat has been renamed to
762 The option VFS_ALLOW_NONMPSAFE option has been added in order to
763 explicitely support non-MPSAFE filesystems.
764 It is on by default for all supported platform at this present
768 The broken amd(4) driver has been replaced with esp(4) in the amd64,
769 i386 and pc98 GENERIC kernel configuration files.
772 sysinstall has been removed
775 The stable/9 branch created in subversion. This corresponds to the
776 RELENG_9 branch in CVS.
779 This commit modifies vfs_register() so that it uses a hash
780 calculation to set vfc_typenum, which is enabled by default.
781 The first time a system is booted after this change, the
782 vfc_typenum values will change for all file systems. The
783 main effect of this is a change to the NFS server file handles
784 for file systems that use vfc_typenum in their fsid, such as ZFS.
785 It will, however, prevent vfc_typenum from changing when file
786 systems are loaded in a different order for subsequent reboots.
787 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
788 until you are ready to remount all NFS clients after a reboot.
791 Bump the shared library version numbers for libraries that
792 do not use symbol versioning, have changed the ABI compared
793 to stable/8 and which shared library version was not bumped.
794 Done as part of 9.0-RELEASE cycle.
797 During the merge of Capsicum features, the fget(9) KPI was modified.
798 This may require the rebuilding of out-of-tree device drivers --
799 issues have been reported specifically with the nVidia device driver.
800 __FreeBSD_version is bumped to 900041.
802 Also, there is a period between 20110811 and 20110814 where the
803 special devices /dev/{stdin,stdout,stderr} did not work correctly.
804 Building world from a kernel during that window may not work.
807 The packet filter (pf) code has been updated to OpenBSD 4.5.
808 You need to update userland tools to be in sync with kernel.
809 This update breaks backward compatibility with earlier pfsync(4)
810 versions. Care must be taken when updating redundant firewall setups.
813 The following sysctls and tunables are retired on x86 platforms:
815 machdep.hlt_logical_cpus
816 The following sysctl is retired:
817 machdep.hyperthreading_allowed
818 The sysctls were supposed to provide a way to dynamically offline and
819 online selected CPUs on x86 platforms, but the implementation has not
820 been reliable especially with SCHED_ULE scheduler.
821 machdep.hyperthreading_allowed tunable is still available to ignore
822 hyperthreading CPUs at OS level.
823 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
824 where X is an APIC ID of a CPU. Be advised, though, that disabling
825 CPUs in non-uniform fashion will result in non-uniform topology and
826 may lead to sub-optimal system performance with SCHED_ULE, which is
830 cpumask_t type is retired and cpuset_t is used in order to describe
834 Changes to ifconfig(8) for dynamic address family detection mandate
835 that you are running a kernel of 20110525 or later. Make sure to
836 follow the update procedure to boot a new kernel before installing
840 Support for sun4v architecture is officially dropped
843 Several KPI breaking changes have been committed to the mii(4) layer,
844 the PHY drivers and consequently some Ethernet drivers using mii(4).
845 This means that miibus.ko and the modules of the affected Ethernet
846 drivers need to be recompiled.
848 Note to kernel developers: Given that the OUI bit reversion problem
849 was fixed as part of these changes all mii(4) commits related to OUIs,
850 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
851 handling, no longer can be merged verbatim to stable/8 and previous
855 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
856 into their kernel configurations along with 'device pci'.
859 The default NFS client is now the new NFS client, so fstype "newnfs"
860 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
861 Although mounts via fstype "nfs" will usually work without userland
862 changes, it is recommended that the mount(8) and mount_nfs(8)
863 commands be rebuilt from sources and that a link to mount_nfs called
864 mount_oldnfs be created. The new client is compiled into the
865 kernel with "options NFSCL" and this is needed for diskless root
866 file systems. The GENERIC kernel configs have been changed to use
867 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
868 To use the regular/old client, you can "mount -t oldnfs ...". For
869 a diskless root file system, you must also include a line like:
871 vfs.root.mountfrom="oldnfs:"
873 in the boot/loader.conf on the root fs on the NFS server to make
874 a diskless root fs use the old client.
877 The GENERIC kernels for all architectures now default to the new
878 CAM-based ATA stack. It means that all legacy ATA drivers were
879 removed and replaced by respective CAM drivers. If you are using
880 ATA device names in /etc/fstab or other places, make sure to update
881 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
882 where 'Y's are the sequential numbers starting from zero for each type
883 in order of detection, unless configured otherwise with tunables,
884 see cam(4)). There will be symbolic links created in /dev/ to map
885 old adX devices to the respective adaY. They should provide basic
886 compatibility for file systems mounting in most cases, but they do
887 not support old user-level APIs and do not have respective providers
888 in GEOM. Consider using updated management tools with new device names.
890 It is possible to load devices ahci, ata, siis and mvs as modules,
891 but option ATA_CAM should remain in kernel configuration to make ata
892 module work as CAM driver supporting legacy ATA controllers. Device ata
893 still can be used in modular fashion (atacore + ...). Modules atadisk
894 and atapi* are not used and won't affect operation in ATA_CAM mode.
895 Note that to use CAM-based ATA kernel should include CAM devices
896 scbus, pass, da (or explicitly ada), cd and optionally others. All of
897 them are parts of the cam module.
899 ataraid(4) functionality is now supported by the RAID GEOM class.
900 To use it you can load geom_raid kernel module and use graid(8) tool
901 for management. Instead of /dev/arX device names, use /dev/raid/rX.
903 No kernel config options or code have been removed, so if a problem
904 arises, please report it and optionally revert to the old ATA stack.
905 In order to do it you can remove from the kernel config:
910 , and instead add back:
911 device atadisk # ATA disk drives
912 device ataraid # ATA RAID drives
913 device atapicd # ATAPI CDROM drives
914 device atapifd # ATAPI floppy drives
915 device atapist # ATAPI tape drives
918 The default NFS server has been changed to the new server, which
919 was referred to as the experimental server. If you need to switch
920 back to the old NFS server, you must now put the "-o" option on
921 both the mountd and nfsd commands. This can be done using the
922 mountd_flags and nfs_server_flags rc.conf variables until an
923 update to the rc scripts is committed, which is coming soon.
926 The GNU Objective-C runtime library (libobjc), and other Objective-C
927 related components have been removed from the base system. If you
928 require an Objective-C library, please use one of the available ports.
931 ath(4) has been split into bus- and device- modules. if_ath contains
932 the HAL, the TX rate control and the network device code. if_ath_pci
933 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
934 contains the AHB glue. Users need to load both if_ath_pci and if_ath
935 in order to use ath on everything else.
937 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
938 need to load if_ath and if_ath_pci for ath(4) operation.
941 As part of the replacement of sysinstall, the process of building
942 release media has changed significantly. For details, please re-read
943 release(7), which has been updated to reflect the new build process.
946 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
947 is the last available version under GPLv2. It brings a number of new
948 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
949 4.1 and SSE 4.2), better support for powerpc64, a number of new
950 directives, and lots of other small improvements. See the ChangeLog
951 file in contrib/binutils for the full details.
954 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
955 compliant, and will now use half of hash for authentication.
956 This will break interoperability with all stacks (including all
957 actual FreeBSD versions) who implement
958 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
960 The only workaround with such peers is to use another HMAC
961 algorithm for IPsec ("phase 2") authentication.
964 Remove the uio_yield prototype and symbol. This function has
965 been misnamed since it was introduced and should not be
966 globally exposed with this name. The equivalent functionality
967 is now available using kern_yield(curthread->td_user_pri).
968 The function remains undocumented.
971 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
972 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
973 for scalar sysctls is defined but disabled. Code that needs
974 UQUAD to pass the type checking that must compile on older
975 systems where the define is not present can check against
976 __FreeBSD_version >= 900030.
978 The system dialog(1) has been replaced with a new version previously
979 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
980 with the previous version, but the libdialog associated with it has
981 a largely incompatible API. As such, the original version of libdialog
982 will be kept temporarily as libodialog, until its base system consumers
983 are replaced or updated. Bump __FreeBSD_version to 900030.
986 If you are trying to run make universe on a -stable system, and you get
987 the following warning:
988 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
989 unknown. config(8) likely too old."
990 or something similar to it, then you must upgrade your -stable system
991 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
992 stable/8) or build the config from the latest stable/8 branch and
993 install it on your system.
995 Prior to this date, building a current universe on 8-stable system from
996 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
997 error in the first kernel build phase. A new config on those old
998 systems will fix that problem for older versions of -current.
1001 The TCP stack has been modified to allow Khelp modules to interact with
1002 it via helper hook points and store per-connection data in the TCP
1003 control block. Bump __FreeBSD_version to 900029. User space tools that
1004 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1008 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1009 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1010 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1011 to take advantage of it instead of using custom implementations. This
1012 means that these drivers now no longer unconditionally advertise
1013 support for flow control but only do so if flow control is a selected
1014 media option. This was implemented in the generic support that way in
1015 order to allow flow control to be switched on and off via ifconfig(8)
1016 with the PHY specific default to typically off in order to protect
1017 from unwanted effects. Consequently, if you used flow control with
1018 one of the above mentioned drivers you now need to explicitly enable
1019 it, for example via:
1020 ifconfig bge0 media auto mediaopt flowcontrol
1022 Along with the above mentioned changes generic support for setting
1023 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1024 e1000phy(4) as well as ip1000phy(4) have been converted to take
1025 advantage of it. This means that these drivers now no longer take the
1026 link0 parameter for selecting master mode but the master media option
1027 has to be used instead, for example like in the following:
1028 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1030 Selection of master mode now is also available with all other PHY
1031 drivers supporting 1000baseT.
1034 The TCP stack has received a significant update to add support for
1035 modularised congestion control and generally improve the clarity of
1036 congestion control decisions. Bump __FreeBSD_version to 900025. User
1037 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1038 sockstat) need to be recompiled.
1041 The man(1) utility has been replaced by a new version that no longer
1042 uses /etc/manpath.config. Please consult man.conf(5) for how to
1043 migrate local entries to the new format.
1046 The copyright strings printed by login(1) and sshd(8) at the time of a
1047 new connection have been removed to follow other operating systems and
1051 A workaround for a fixed ld bug has been removed in kernel code,
1052 so make sure that your system ld is built from sources after
1053 revision 210245 from 2010-07-19 (r211583 if building head kernel
1054 on stable/8, r211584 for stable/7; both from 2010-08-21).
1055 A symptom of incorrect ld version is different addresses for
1056 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1059 The $ipv6_prefer variable in rc.conf(5) has been split into
1060 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1062 The $ip6addrctl_policy is a variable to choose a pre-defined
1063 address selection policy set by ip6addrctl(8). A value
1064 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1067 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1068 flag (see an entry of 20090926) is set on an interface with no
1069 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1070 security reason. If you want IPv6 link-local address on all
1071 interfaces by default, set this to "YES".
1073 The old ipv6_prefer="YES" is equivalent to
1074 ipv6_activate_all_interfaces="YES" and
1075 ip6addrctl_policy="ipv6_prefer".
1078 DTrace has grown support for userland tracing. Due to this, DTrace is
1079 now i386 and amd64 only.
1080 dtruss(1) is now installed by default on those systems and a new
1081 kernel module is needed for userland tracing: fasttrap.
1082 No changes to your kernel config file are necessary to enable
1083 userland tracing, but you might consider adding 'STRIP=' and
1084 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1085 to have informative userland stack traces in DTrace (ustack).
1088 The acpi_aiboost(4) driver has been removed in favor of the new
1089 aibs(4) driver. You should update your kernel configuration file.
1092 BSD grep has been imported to the base system and it is built by
1093 default. It is completely BSD licensed, highly GNU-compatible, uses
1094 less memory than its GNU counterpart and has a small codebase.
1095 However, it is slower than its GNU counterpart, which is mostly
1096 noticeable for larger searches, for smaller ones it is measurable
1097 but not significant. The reason is complex, the most important factor
1098 is that we lack a modern and efficient regex library and GNU
1099 overcomes this by optimizing the searches internally. Future work
1100 on improving the regex performance is planned, for the meantime,
1101 users that need better performance, can build GNU grep instead by
1102 setting the WITH_GNU_GREP knob.
1105 Due to the import of powerpc64 support, all existing powerpc kernel
1106 configuration files must be updated with a machine directive like this:
1107 machine powerpc powerpc
1109 In addition, an updated config(8) is required to build powerpc kernels
1113 A new version of ZFS (version 15) has been merged to -HEAD.
1114 This version uses a python library for the following subcommands:
1115 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1116 For full functionality of these commands the following port must
1117 be installed: sysutils/py-zfs
1120 'vm_page's are now hashed by physical address to an array of mutexes.
1121 Currently this is only used to serialize access to hold_count. Over
1122 time the page queue mutex will be peeled away. This changes the size
1123 of pmap on every architecture. And requires all callers of vm_page_hold
1124 and vm_page_unhold to be updated.
1127 WITH_CTF can now be specified in src.conf (not recommended, there
1128 are some problems with static executables), make.conf (would also
1129 affect ports which do not use GNU make and do not override the
1130 compile targets) or in the kernel config (via "makeoptions
1132 When WITH_CTF was specified there before this was silently ignored,
1133 so make sure that WITH_CTF is not used in places which could lead
1134 to unwanted behavior.
1137 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1138 to allow 32-bit compatibility on non-x86 platforms. All kernel
1139 configurations on amd64 and ia64 platforms using these options must
1140 be modified accordingly.
1143 The utmp user accounting database has been replaced with utmpx,
1144 the user accounting interface standardized by POSIX.
1145 Unfortunately the semantics of utmp and utmpx don't match,
1146 making it practically impossible to support both interfaces.
1147 The user accounting database is used by tools like finger(1),
1148 last(1), talk(1), w(1) and ac(8).
1150 All applications in the base system use utmpx. This means only
1151 local binaries (e.g. from the ports tree) may still use these
1152 utmp database files. These applications must be rebuilt to make
1155 After the system has been upgraded, it is safe to remove the old
1156 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1157 assuming their contents is of no importance anymore. Old wtmp
1158 databases can only be used by last(1) and ac(8) after they have
1159 been converted to the new format using wtmpcvt(1).
1162 Introduce the kernel thread "deadlock resolver" (which can be enabled
1163 via the DEADLKRES option, see NOTES for more details) and the
1164 sleepq_type() function for sleepqueues.
1167 The rc.firewall and rc.firewall6 were unified, and
1168 rc.firewall6 and rc.d/ip6fw were removed.
1169 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1170 variables are obsoleted. Instead, the following new rc
1171 variables are added to rc.d/ipfw:
1173 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1174 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1175 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1177 The meanings correspond to the relevant IPv4 variables.
1183 The default terminal emulation for syscons(4) has been changed
1184 from cons25 to xterm on all platforms except pc98. This means
1185 that the /etc/ttys file needs to be updated to ensure correct
1186 operation of applications on the console.
1188 The terminal emulation style can be toggled per window by using
1189 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1190 options can be used to change the compile-time default back to
1193 To prevent graphical artifacts, make sure the TERM environment
1194 variable is set to match the terminal emulation that is being
1195 performed by syscons(4).
1198 The layout of the structure ieee80211req_scan_result has changed.
1199 Applications that require wireless scan results (e.g. ifconfig(8))
1200 from net80211 need to be recompiled.
1202 Applications such as wpa_supplicant(8) may require a full world
1203 build without using NO_CLEAN in order to get synchronized with the
1207 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1208 There's one kernel module for each firmware. Adding "device iwnfw"
1209 to the kernel configuration file means including all three firmware
1210 images inside the kernel. If you want to include just the one for
1211 your wireless card, use the devices iwn4965fw, iwn5000fw or
1215 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1216 into rc.d/netif. The changes are the following:
1218 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1219 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1220 Note that both variables need the "inet6" keyword at the head.
1222 Do not set $ipv6_network_interfaces manually if you do not
1223 understand what you are doing. It is not needed in most cases.
1225 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1228 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1229 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1231 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1232 all configured interfaces have "inet6 accept_rtadv" in the
1233 $ifconfig_IF_ipv6. These are for backward compatibility.
1235 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1236 functionality of interfaces with no corresponding
1237 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1238 and the default address selection policy of ip6addrctl(8)
1239 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1240 Note that if you want to configure IPv6 functionality on the
1241 disabled interfaces after boot, first you need to clear the flag by
1242 using ifconfig(8) like:
1244 ifconfig em0 inet6 -ifdisabled
1246 If YES, the default address selection policy is set as
1249 The default value of $ipv6_prefer is NO.
1251 4. If your system need to receive Router Advertisement messages,
1252 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1253 scripts automatically invoke rtsol(8) when the interface becomes
1254 UP. The Router Advertisement messages are used for SLAAC
1255 (State-Less Address AutoConfiguration).
1258 802.11s D3.03 support was committed. This is incompatible with the
1259 previous code, which was based on D3.0.
1262 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1263 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1264 control whether accepting Router Advertisement messages or not.
1265 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1266 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1267 The ifconfig(8) utility now supports these flags.
1270 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1271 mount(8) and -a option for df(1) to see them.
1274 The old tunable hw.bus.devctl_disable has been superseded by
1275 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1276 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1280 Remove the option STOP_NMI. The default action is now to use NMI only
1281 for KDB via the newly introduced function stop_cpus_hard() and
1282 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1285 The stable/8 branch created in subversion. This corresponds to the
1286 RELENG_8 branch in CVS.
1289 Bump the shared library version numbers for all libraries that do not
1290 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1291 __FreeBSD_version to 800105.
1294 Due to changes in the implementation of virtual network stack support,
1295 all network-related kernel modules must be recompiled. As this change
1296 breaks the ABI, bump __FreeBSD_version to 800104.
1299 The TOE interface to the TCP syncache has been modified to remove
1300 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1301 The cxgb driver is the only TOE consumer affected by this change, and
1302 needs to be recompiled along with the kernel. As this change breaks
1303 the ABI, bump __FreeBSD_version to 800103.
1306 Padding has been added to struct tcpcb, sackhint and tcpstat in
1307 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1308 maintaining the ABI. However, this change breaks the ABI, so bump
1309 __FreeBSD_version to 800102. User space tools that rely on the size of
1310 any of these structs (e.g. sockstat) need to be recompiled.
1313 The NFS_LEGACYRPC option has been removed along with the old kernel
1314 RPC implementation that this option selected. Kernel configurations
1315 may need to be adjusted.
1318 The network interface device nodes at /dev/net/<interface> have been
1319 removed. All ioctl operations can be performed the normal way using
1320 routing sockets. The kqueue functionality can generally be replaced
1321 with routing sockets.
1324 The documentation from the FreeBSD Documentation Project (Handbook,
1325 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1326 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1329 The ABI of various structures related to the SYSV IPC API have been
1330 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1331 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1335 Layout of struct vnet has changed as routing related variables were
1336 moved to their own Vimage module. Modules need to be recompiled. Bump
1337 __FreeBSD_version to 800099.
1340 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1341 respectively. As long as no more than 16 groups per process are used,
1342 no changes should be visible. When more than 16 groups are used, old
1343 binaries may fail if they call getgroups() or getgrouplist() with
1344 statically sized storage. Recompiling will work around this, but
1345 applications should be modified to use dynamically allocated storage
1346 for group arrays as POSIX.1-2008 does not cap an implementation's
1347 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1349 NFS and portalfs mounts may also be affected as the list of groups is
1350 truncated to 16. Users of NFS who use more than 16 groups, should
1351 take care that negative group permissions are not used on the exported
1352 file systems as they will not be reliable unless a GSSAPI based
1353 authentication method is used.
1356 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1357 option compiles in the support for adaptive spinning for lockmgrs
1358 which want to enable it. The lockinit() function now accepts the flag
1359 LK_ADAPTIVE in order to make the lock object subject to adaptive
1360 spinning when both held in write and read mode.
1363 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1364 changed. User applications that use this ioctl need to be rebuilt.
1367 The layout of struct thread has changed. Kernel and modules need to
1371 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1372 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1375 window(1) has been removed from the base system. It can now be
1376 installed from ports. The port is called misc/window.
1379 The way we are storing and accessing `routing table' entries has
1380 changed. Programs reading the FIB, like netstat, need to be
1384 A new netisr implementation has been added for FreeBSD 8. Network
1385 file system modules, such as igmp, ipdivert, and others, should be
1387 Bump __FreeBSD_version to 800096.
1390 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1394 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1395 Bump __FreeBSD_version to 800094.
1398 Add mnt_xflag field to 'struct mount'. File system modules need to be
1400 Bump __FreeBSD_version to 800093.
1403 The compiling option ADAPTIVE_SX has been retired while it has been
1404 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1405 The KPI for sx_init_flags() changes as accepting flags:
1406 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1407 been introduced in order to handle the reversed logic.
1408 Bump __FreeBSD_version to 800092.
1411 Add support for hierarchical jails. Remove global securelevel.
1412 Bump __FreeBSD_version to 800091.
1415 The layout of struct vnet_net has changed, therefore modules
1417 Bump __FreeBSD_version to 800090.
1420 The newly imported zic(8) produces a new format in the output. Please
1421 run tzsetup(8) to install the newly created data to /etc/localtime.
1424 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1425 hw.usb.* and is now consistent again with previous releases.
1428 802.11 monitor mode support was revised and driver api's were changed.
1429 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1430 of DLT_IEEE802_11. No user-visible data structures were changed but
1431 applications that use DLT_IEEE802_11 may require changes.
1432 Bump __FreeBSD_version to 800088.
1435 The layout of the following structs has changed: sysctl_oid,
1436 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1437 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1438 panics may be experienced. World rebuild is required for
1439 correctly checking networking state from userland.
1440 Bump __FreeBSD_version to 800085.
1443 MLDv2 and Source-Specific Multicast (SSM) have been merged
1444 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1445 The implementation of SSM within FreeBSD's IPv6 stack closely
1446 follows the IPv4 implementation.
1448 For kernel developers:
1450 * The most important changes are that the ip6_output() and
1451 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1452 and this lock has been downgraded to a non-recursive mutex.
1454 * As with the changes to the IPv4 stack to support SSM, filtering
1455 of inbound multicast traffic must now be performed by transport
1456 protocols within the IPv6 stack. This does not apply to TCP and
1457 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1459 * The KPIs used by IPv6 multicast are similar to those used by
1460 the IPv4 stack, with the following differences:
1461 * im6o_mc_filter() is analogous to imo_multicast_filter().
1462 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1463 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1464 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1465 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1466 for MLDv1 have an additional 'timer' argument which is used to
1467 jitter the initial membership report for the solicited-node
1468 multicast membership on-link.
1469 * This is not strictly needed for MLDv2, which already jitters
1470 its report transmissions. However, the 'timer' argument is
1471 preserved in case MLDv1 is active on the interface.
1473 * The KAME linked-list based IPv6 membership implementation has
1474 been refactored to use a vector similar to that used by the IPv4
1476 Code which maintains a list of its own multicast memberships
1477 internally, e.g. carp, has been updated to reflect the new
1480 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1481 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1482 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1483 implementation constraint which needs to be addressed in HEAD.
1485 For application developers:
1487 * The changes are broadly similar to those made for the IPv4
1490 * The use of IPv4 and IPv6 multicast socket options on the same
1491 socket, using mapped addresses, HAS NOT been tested or supported.
1493 * There are a number of issues with the implementation of various
1494 IPv6 multicast APIs which need to be resolved in the API surface
1495 before the implementation is fully compatible with KAME userland
1496 use, and these are mostly to do with interface index treatment.
1498 * The literature available discusses the use of either the delta / ASM
1499 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1500 using setsourcefilter(3)/getsourcefilter(3). For more information
1501 please refer to RFC 3768, 'Socket Interface Extensions for
1502 Multicast Source Filters'.
1504 * Applications which use the published RFC 3678 APIs should be fine.
1506 For systems administrators:
1508 * The mtest(8) utility has been refactored to support IPv6, in
1509 addition to IPv4. Interface addresses are no longer accepted
1510 as arguments, their names must be used instead. The utility
1511 will map the interface name to its first IPv4 address as
1512 returned by getifaddrs(3).
1514 * The ifmcstat(8) utility has also been updated to print the MLDv2
1515 endpoint state and source filter lists via sysctl(3).
1517 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1518 loopback of IPv6 multicast datagrams by default; it defaults to 1
1519 to preserve the existing behaviour. Disabling multicast loopback is
1520 recommended for optimal system performance.
1522 * The IPv6 MROUTING code has been changed to examine this sysctl
1523 instead of attempting to perform a group lookup before looping
1524 back forwarded datagrams.
1526 Bump __FreeBSD_version to 800084.
1529 Implement low-level Bluetooth HCI API.
1530 Bump __FreeBSD_version to 800083.
1533 The layout of struct malloc_type, used by modules to register new
1534 memory allocation types, has changed. Most modules will need to
1535 be rebuilt or panics may be experienced.
1536 Bump __FreeBSD_version to 800081.
1539 Anticipate overflowing inp_flags - add inp_flags2.
1540 This changes most offsets in inpcb, so checking v4 connection
1541 state will require a world rebuild.
1542 Bump __FreeBSD_version to 800080.
1545 Add an llentry to struct route and struct route_in6. Modules
1546 embedding a struct route will need to be recompiled.
1547 Bump __FreeBSD_version to 800079.
1550 The size of rt_metrics_lite and by extension rtentry has changed.
1551 Networking administration apps will need to be recompiled.
1552 The route command now supports show as an alias for get, weighting
1553 of routes, sticky and nostick flags to alter the behavior of stateful
1555 Bump __FreeBSD_version to 800078.
1558 Do not use Giant for kbdmux(4) locking. This is wrong and
1559 apparently causing more problems than it solves. This will
1560 re-open the issue where interrupt handlers may race with
1561 kbdmux(4) in polling mode. Typical symptoms include (but
1562 not limited to) duplicated and/or missing characters when
1563 low level console functions (such as gets) are used while
1564 interrupts are enabled (for example geli password prompt,
1565 mountroot prompt etc.). Disabling kbdmux(4) may help.
1568 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1569 kernel modules referencing any of the above need to be recompiled.
1570 Bump __FreeBSD_version to 800075.
1573 GEOM_PART has become the default partition slicer for storage devices,
1574 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1575 introduces some changes:
1577 MSDOS/EBR: the devices created from MSDOS extended partition entries
1578 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1579 to devices with offset-based names. fstabs may need to be modified.
1581 BSD: the "geometry does not match label" warning is harmless in most
1582 cases but it points to problems in file system misalignment with
1583 disk geometry. The "c" partition is now implicit, covers the whole
1584 top-level drive and cannot be (mis)used by users.
1586 General: Kernel dumps are now not allowed to be written to devices
1587 whose partition types indicate they are meant to be used for file
1588 systems (or, in case of MSDOS partitions, as something else than
1591 Most of these changes date approximately from 200812.
1594 The uscanner(4) driver has been removed from the kernel. This follows
1595 Linux removing theirs in 2.6 and making libusb the default interface
1596 (supported by sane).
1599 The multicast forwarding code has been cleaned up. netstat(1)
1600 only relies on KVM now for printing bandwidth upcall meters.
1601 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1602 ip6_mroute_mod respectively. The config(5) options for statically
1603 compiling this code remain the same, i.e. 'options MROUTING'.
1606 Support for the IFF_NEEDSGIANT network interface flag has been
1607 removed, which means that non-MPSAFE network device drivers are no
1608 longer supported. In particular, if_ar, if_sr, and network device
1609 drivers from the old (legacy) USB stack can no longer be built or
1613 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1614 a bunch of new language catalog files have also been added.
1615 This means that some common libc messages are now localized and
1616 they depend on the LC_MESSAGES environmental variable.
1619 The k8temp(4) driver has been renamed to amdtemp(4) since
1620 support for Family 10 and Family 11 CPU families was added.
1623 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1624 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1626 For kernel developers, the most important changes are that the
1627 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1628 and this lock has been downgraded to a non-recursive mutex.
1630 Transport protocols (UDP, Raw IP) are now responsible for filtering
1631 inbound multicast traffic according to group membership and source
1632 filters. The imo_multicast_filter() KPI exists for this purpose.
1633 Transports which do not use multicast (SCTP, TCP) already reject
1634 multicast by default. Forwarding and receive performance may improve
1635 as a mutex acquisition is no longer needed in the ip_input()
1636 low-level input path. in_addmulti() and in_delmulti() are shimmed
1637 to new KPIs which exist to support SSM in-kernel.
1639 For application developers, it is recommended that loopback of
1640 multicast datagrams be disabled for best performance, as this
1641 will still cause the lock to be taken for each looped-back
1642 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1643 be tuned to 0 to disable loopback by default; it defaults to 1
1644 to preserve the existing behaviour.
1646 For systems administrators, to obtain best performance with
1647 multicast reception and multiple groups, it is always recommended
1648 that a card with a suitably precise hash filter is used. Hash
1649 collisions will still result in the lock being taken within the
1650 transport protocol input path to check group membership.
1652 If deploying FreeBSD in an environment with IGMP snooping switches,
1653 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1654 enabled; this forces 224.0.0.0/24 group membership to be announced
1657 The size of 'struct igmpstat' has changed; netstat needs to be
1658 recompiled to reflect this.
1659 Bump __FreeBSD_version to 800070.
1662 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1663 updated to use it. This requires a buildworld/installworld in order to
1664 update the library and dependencies (usbconfig, etc). Its advisable to
1665 rebuild all ports which uses libusb. More specific directions are given
1666 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1667 libusb are no longer required and can be removed.
1670 A workaround is committed to allow the creation of System V shared
1671 memory segment of size > 2 GB on the 64-bit architectures.
1672 Due to a limitation of the existing ABI, the shm_segsz member
1673 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1674 wrong for large segments. Note that limits must be explicitly
1675 raised to allow such segments to be created.
1678 The layout of struct ifnet has changed, requiring a rebuild of all
1679 network device driver modules.
1682 The /dev handling for the new USB stack has changed, a
1683 buildworld/installworld is required for libusb20.
1686 The new USB2 stack has now been permanently moved in and all kernel and
1687 module names reverted to their previous values (eg, usb, ehci, ohci,
1688 ums, ...). The old usb stack can be compiled in by prefixing the name
1689 with the letter 'o', the old usb modules have been removed.
1690 Updating entry 20090216 for xorg and 20090215 for libmap may still
1694 The rc.conf(5) option if_up_delay has been renamed to
1695 defaultroute_delay to better reflect its purpose. If you have
1696 customized this setting in /etc/rc.conf you need to update it to
1700 xorg 7.4 wants to configure its input devices via hald which does not
1701 yet work with USB2. If the keyboard/mouse does not work in xorg then
1703 Option "AllowEmptyInput" "off"
1704 to your ServerLayout section. This will cause X to use the configured
1705 kbd and mouse sections from your xorg.conf.
1708 The GENERIC kernels for all architectures now default to the new USB2
1709 stack. No kernel config options or code have been removed so if a
1710 problem arises please report it and optionally revert to the old USB
1711 stack. If you are loading USB kernel modules or have a custom kernel
1712 that includes GENERIC then ensure that usb names are also changed over,
1713 eg uftdi -> usb2_serial_ftdi.
1715 Older programs linked against the ports libusb 0.1 need to be
1716 redirected to the new stack's libusb20. /etc/libmap.conf can
1718 # Map old usb library to new one for usb2 stack
1719 libusb-0.1.so.8 libusb20.so.1
1722 All USB ethernet devices now attach as interfaces under the name ueN
1723 (eg. ue0). This is to provide a predictable name as vendors often
1724 change usb chipsets in a product without notice.
1727 The ichsmb(4) driver has been changed to require SMBus slave
1728 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1729 All of the other SMBus controller drivers require left-justified
1730 slave addresses, so this change makes all the drivers provide the
1734 INET6 statistics (struct ip6stat) was updated.
1735 netstat(1) needs to be recompiled.
1738 NTFS has been removed from GENERIC kernel on amd64 to match
1739 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1740 will load ntfs.ko module automatically when NTFS support is
1741 actually needed, unless ntfs.ko is not installed or security
1742 level prohibits loading kernel modules. If either is the case,
1743 "options NTFS" has to be added into kernel config.
1746 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1747 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1748 800061. User space tools that rely on the size of struct tcpcb in
1749 tcp_var.h (e.g. sockstat) need to be recompiled.
1752 ng_tty(4) module updated to match the new TTY subsystem.
1753 Due to API change, user-level applications must be updated.
1754 New API support added to mpd5 CVS and expected to be present
1755 in next mpd5.3 release.
1758 With __FreeBSD_version 800060 the makefs tool is part of
1759 the base system (it was a port).
1762 The afdata and ifnet locks have been changed from mutexes to
1763 rwlocks, network modules will need to be re-compiled.
1766 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1767 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1768 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1769 architecture and 40 bytes on 64-bit architecture. The userland
1770 applications "arp" and "ndp" have been updated accordingly.
1771 The output from "netstat -r" shows only routing entries and
1772 none of the L2 information.
1775 __FreeBSD_version 800057 marks the switchover from the
1776 binary ath hal to source code. Users must add the line:
1778 options AH_SUPPORT_AR5416
1780 to their kernel config files when specifying:
1784 The ath_hal module no longer exists; the code is now compiled
1785 together with the driver in the ath module. It is now
1786 possible to tailor chip support (i.e. reduce the set of chips
1787 and thereby the code size); consult ath_hal(4) for details.
1790 __FreeBSD_version 800054 adds memory barriers to
1791 <machine/atomic.h>, new interfaces to ifnet to facilitate
1792 multiple hardware transmit queues for cards that support
1793 them, and a lock-less ring-buffer implementation to
1794 enable drivers to more efficiently manage queueing of
1798 A new version of ZFS (version 13) has been merged to -HEAD.
1799 This version has zpool attribute "listsnapshots" off by
1800 default, which means "zfs list" does not show snapshots,
1801 and is the same as Solaris behavior.
1804 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1807 The uhci, ohci, ehci and slhci USB Host controller drivers have
1808 been put into separate modules. If you load the usb module
1809 separately through loader.conf you will need to load the
1810 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1811 controller add the following to loader.conf:
1817 The ABI used by the PMC toolset has changed. Please keep
1818 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1822 atapci kernel module now includes only generic PCI ATA
1823 driver. AHCI driver moved to ataahci kernel module.
1824 All vendor-specific code moved into separate kernel modules:
1825 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1826 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1827 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1828 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1831 The TTY subsystem of the kernel has been replaced by a new
1832 implementation, which provides better scalability and an
1833 improved driver model. Most common drivers have been migrated to
1834 the new TTY subsystem, while others have not. The following
1835 drivers have not yet been ported to the new TTY layer:
1838 cy, digi, rc, rp, sio
1844 ng_h4, ng_tty, ppp, sl, snp
1846 Adding these drivers to your kernel configuration file shall
1847 cause compilation to fail.
1850 ntpd has been upgraded to 4.2.4p5.
1853 OpenSSH has been upgraded to 5.1p1.
1855 For many years, FreeBSD's version of OpenSSH preferred DSA
1856 over RSA for host and user authentication keys. With this
1857 upgrade, we've switched to the vendor's default of RSA over
1858 DSA. This may cause upgraded clients to warn about unknown
1859 host keys even for previously known hosts. Users should
1860 follow the usual procedure for verifying host keys before
1861 accepting the RSA key.
1863 This can be circumvented by setting the "HostKeyAlgorithms"
1864 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1867 Please note that the sequence of keys offered for
1868 authentication has been changed as well. You may want to
1869 specify IdentityFile in a different order to revert this
1873 The sio(4) driver has been removed from the i386 and amd64
1874 kernel configuration files. This means uart(4) is now the
1875 default serial port driver on those platforms as well.
1877 To prevent collisions with the sio(4) driver, the uart(4) driver
1878 uses different names for its device nodes. This means the
1879 onboard serial port will now most likely be called "ttyu0"
1880 instead of "ttyd0". You may need to reconfigure applications to
1881 use the new device names.
1883 When using the serial port as a boot console, be sure to update
1884 /boot/device.hints and /etc/ttys before booting the new kernel.
1885 If you forget to do so, you can still manually specify the hints
1886 at the loader prompt:
1888 set hint.uart.0.at="isa"
1889 set hint.uart.0.port="0x3F8"
1890 set hint.uart.0.flags="0x10"
1891 set hint.uart.0.irq="4"
1895 The gpt(8) utility has been removed. Use gpart(8) to partition
1899 The version that Linuxulator emulates was changed from 2.4.2
1900 to 2.6.16. If you experience any problems with Linux binaries
1901 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1902 if it fixes the problem contact emulation mailing list.
1905 ISDN4BSD (I4B) was removed from the src tree. You may need to
1906 update a your kernel configuration and remove relevant entries.
1909 I have checked in code to support multiple routing tables.
1910 See the man pages setfib(1) and setfib(2).
1911 This is a hopefully backwards compatible version,
1912 but to make use of it you need to compile your kernel
1913 with options ROUTETABLES=2 (or more up to 16).
1916 The 802.11 wireless support was redone to enable multi-bss
1917 operation on devices that are capable. The underlying device
1918 is no longer used directly but instead wlanX devices are
1919 cloned with ifconfig. This requires changes to rc.conf files.
1920 For example, change:
1921 ifconfig_ath0="WPA DHCP"
1924 ifconfig_wlan0="WPA DHCP"
1925 see rc.conf(5) for more details. In addition, mergemaster of
1926 /etc/rc.d is highly recommended. Simultaneous update of userland
1927 and kernel wouldn't hurt either.
1929 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1930 modules were merged into the base wlan module. All references
1931 to these modules (e.g. in kernel config files) must be removed.
1934 psm(4) has gained write(2) support in native operation level.
1935 Arbitrary commands can be written to /dev/psm%d and status can
1936 be read back from it. Therefore, an application is responsible
1937 for status validation and error recovery. It is a no-op in
1938 other operation levels.
1941 Support for KSE threading has been removed from the kernel. To
1942 run legacy applications linked against KSE libmap.conf may
1943 be used. The following libmap.conf may be used to ensure
1944 compatibility with any prior release:
1946 libpthread.so.1 libthr.so.1
1947 libpthread.so.2 libthr.so.2
1948 libkse.so.3 libthr.so.3
1951 The layout of struct vmspace has changed. This affects libkvm
1952 and any executables that link against libkvm and use the
1953 kvm_getprocs() function. In particular, but not exclusively,
1954 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1955 The effects are minimal, but it's advisable to upgrade world
1959 The latest em driver no longer has support in it for the
1960 82575 adapter, this is now moved to the igb driver. The
1961 split was done to make new features that are incompatible
1962 with older hardware easier to do.
1965 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1966 likewise the kernel option is now GEOM_LINUX_LVM.
1969 The default NFS mount mode has changed from UDP to TCP for
1970 increased reliability. If you rely on (insecurely) NFS
1971 mounting across a firewall you may need to update your
1975 Belatedly note the addition of m_collapse for compacting
1979 The fts(3) structures have been changed to use adequate
1980 integer types for their members and so to be able to cope
1981 with huge file trees. The old fts(3) ABI is preserved
1982 through symbol versioning in libc, so third-party binaries
1983 using fts(3) should still work, although they will not take
1984 advantage of the extended types. At the same time, some
1985 third-party software might fail to build after this change
1986 due to unportable assumptions made in its source code about
1987 fts(3) structure members. Such software should be fixed
1988 by its vendor or, in the worst case, in the ports tree.
1989 FreeBSD_version 800015 marks this change for the unlikely
1990 case that a portable fix is impossible.
1993 To upgrade to -current after this date, you must be running
1994 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1995 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1998 The ADAPTIVE_GIANT kernel option has been retired because its
1999 functionality is the default now.
2002 The AT keyboard emulation of sunkbd(4) has been turned on
2003 by default. In order to make the special symbols of the Sun
2004 keyboards driven by sunkbd(4) work under X these now have
2005 to be configured the same way as Sun USB keyboards driven
2006 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2008 Option "XkbLayout" "us"
2009 Option "XkbRules" "xorg"
2010 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2013 It has been decided that it is desirable to provide ABI
2014 backwards compatibility to the FreeBSD 4/5/6 versions of the
2015 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2016 broken with the introduction of PCI domain support (see the
2017 20070930 entry). Unfortunately, this required the ABI of
2018 PCIOCGETCONF to be broken again in order to be able to
2019 provide backwards compatibility to the old version of that
2020 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2021 again. As for prominent ports this affects neither pciutils
2022 nor xorg-server this time, the hal port needs to be rebuilt
2026 The misnamed kthread_create() and friends have been renamed
2027 to kproc_create() etc. Many of the callers already
2028 used kproc_start()..
2029 I will return kthread_create() and friends in a while
2030 with implementations that actually create threads, not procs.
2031 Renaming corresponds with version 800002.
2040 Avoid using make -j when upgrading. While generally safe, there are
2041 sometimes problems using -j to upgrade. If your upgrade fails with
2042 -j, please try again without -j. From time to time in the past there
2043 have been problems using -j with buildworld and/or installworld. This
2044 is especially true when upgrading between "distant" versions (eg one
2045 that cross a major release boundary or several minor releases, or when
2046 several months have passed on the -current branch).
2048 Sometimes, obscure build problems are the result of environment
2049 poisoning. This can happen because the make utility reads its
2050 environment when searching for values for global variables. To run
2051 your build attempts in an "environmental clean room", prefix all make
2052 commands with 'env -i '. See the env(1) manual page for more details.
2054 When upgrading from one major version to another it is generally best
2055 to upgrade to the latest code in the currently installed branch first,
2056 then do an upgrade to the new branch. This is the best-tested upgrade
2057 path, and has the highest probability of being successful. Please try
2058 this approach before reporting problems with a major version upgrade.
2060 When upgrading a live system, having a root shell around before
2061 installing anything can help undo problems. Not having a root shell
2062 around can lead to problems if pam has changed too much from your
2063 starting point to allow continued authentication after the upgrade.
2067 When upgrading the boot ZFS pool to a new version, always follow
2070 1.) recompile and reinstall the ZFS boot loader and boot block
2071 (this is part of "make buildworld" and "make installworld")
2073 2.) update the ZFS boot block on your boot drive
2075 The following example updates the ZFS boot block on the first
2076 partition (freebsd-boot) of a GPT partitioned drive ad0:
2077 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2079 Non-boot pools do not need these updates.
2083 If you are updating from a prior version of FreeBSD (even one just
2084 a few days old), you should follow this procedure. It is the most
2085 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2087 make kernel-toolchain
2088 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2089 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2091 To test a kernel once
2092 ---------------------
2093 If you just want to boot a kernel once (because you are not sure
2094 if it works, or if you want to boot a known bad kernel to provide
2095 debugging information) run
2096 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2097 nextboot -k testkernel
2099 To just build a kernel when you know that it won't mess you up
2100 --------------------------------------------------------------
2101 This assumes you are already running a CURRENT system. Replace
2102 ${arch} with the architecture of your machine (e.g. "i386",
2103 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2105 cd src/sys/${arch}/conf
2106 config KERNEL_NAME_HERE
2107 cd ../compile/KERNEL_NAME_HERE
2112 If this fails, go to the "To build a kernel" section.
2114 To rebuild everything and install it on the current system.
2115 -----------------------------------------------------------
2116 # Note: sometimes if you are running current you gotta do more than
2117 # is listed here if you are upgrading from a really old current.
2119 <make sure you have good level 0 dumps>
2121 make kernel KERNCONF=YOUR_KERNEL_HERE
2123 <reboot in single user> [3]
2130 To cross-install current onto a separate partition
2131 --------------------------------------------------
2132 # In this approach we use a separate partition to hold
2133 # current's root, 'usr', and 'var' directories. A partition
2134 # holding "/", "/usr" and "/var" should be about 2GB in
2137 <make sure you have good level 0 dumps>
2140 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2141 <maybe newfs current's root partition>
2142 <mount current's root partition on directory ${CURRENT_ROOT}>
2143 make installworld DESTDIR=${CURRENT_ROOT}
2144 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2145 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2146 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2147 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2148 <reboot into current>
2149 <do a "native" rebuild/install as described in the previous section>
2150 <maybe install compatibility libraries from ports/misc/compat*>
2154 To upgrade in-place from stable to current
2155 ----------------------------------------------
2156 <make sure you have good level 0 dumps>
2158 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2160 <reboot in single user> [3]
2167 Make sure that you've read the UPDATING file to understand the
2168 tweaks to various things you need. At this point in the life
2169 cycle of current, things change often and you are on your own
2170 to cope. The defaults can also change, so please read ALL of
2171 the UPDATING entries.
2173 Also, if you are tracking -current, you must be subscribed to
2174 freebsd-current@freebsd.org. Make sure that before you update
2175 your sources that you have read and understood all the recent
2176 messages there. If in doubt, please track -stable which has
2177 much fewer pitfalls.
2179 [1] If you have third party modules, such as vmware, you
2180 should disable them at this point so they don't crash your
2183 [3] From the bootblocks, boot -s, and then do
2188 adjkerntz -i # if CMOS is wall time
2189 Also, when doing a major release upgrade, it is required that
2190 you boot into single user mode to do the installworld.
2192 [4] Note: This step is non-optional. Failure to do this step
2193 can result in a significant reduction in the functionality of the
2194 system. Attempting to do it by hand is not recommended and those
2195 that pursue this avenue should read this file carefully, as well
2196 as the archives of freebsd-current and freebsd-hackers mailing lists
2197 for potential gotchas. The -U option is also useful to consider.
2198 See mergemaster(8) for more information.
2200 [5] Usually this step is a noop. However, from time to time
2201 you may need to do this if you get unknown user in the following
2202 step. It never hurts to do it all the time. You may need to
2203 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2204 install) after the buildworld before this step if you last updated
2205 from current before 20130425 or from -stable before 20130430.
2207 [6] This only deletes old files and directories. Old libraries
2208 can be deleted by "make delete-old-libs", but you have to make
2209 sure that no program is using those libraries anymore.
2211 [8] In order to have a kernel that can run the 4.x binaries needed to
2212 do an installworld, you must include the COMPAT_FREEBSD4 option in
2213 your kernel. Failure to do so may leave you with a system that is
2214 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2215 required to run the 5.x binaries on more recent kernels. And so on
2216 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2218 Make sure that you merge any new devices from GENERIC since the
2219 last time you updated your kernel config file.
2221 [9] When checking out sources, you must include the -P flag to have
2222 cvs prune empty directories.
2224 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2225 "?=" instead of the "=" assignment operator, so that buildworld can
2226 override the CPUTYPE if it needs to.
2228 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2229 not on the command line, or in /etc/make.conf. buildworld will
2230 warn if it is improperly defined.
2233 This file contains a list, in reverse chronological order, of major
2234 breakages in tracking -current. It is not guaranteed to be a complete
2235 list of such breakages, and only contains entries since October 10, 2007.
2236 If you need to see UPDATING entries from before that date, you will need
2237 to fetch an UPDATING file from an older FreeBSD release.
2239 Copyright information:
2241 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2243 Redistribution, publication, translation and use, with or without
2244 modification, in full or in part, in any form or format of this
2245 document are permitted without further permission from the author.
2247 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2248 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2249 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2250 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2251 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2252 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2253 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2254 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2255 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2256 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2257 POSSIBILITY OF SUCH DAMAGE.
2259 Contact Warner Losh if you have any questions about your use of