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 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
21 Kernel modules isp_2400_multi and isp_2500_multi were removed and
22 should be replaced with isp_2400 and isp_2500 modules respectively.
25 NTP has been upgraded to 4.2.8p4.
28 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
29 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
30 and devel/kyua to version 0.20+ and adjust any calling code to work
31 with Kyuafile and kyua.
34 The polarity of Pulse Per Second (PPS) capture events with the
35 uart(4) driver has been corrected. Prior to this change the PPS
36 "assert" event corresponded to the trailing edge of a positive PPS
37 pulse and the "clear" event was the leading edge of the next pulse.
39 As the width of a PPS pulse in a typical GPS receiver is on the
40 order of 1 millisecond, most users will not notice any significant
41 difference with this change.
43 Anyone who has compensated for the historical polarity reversal by
44 configuring a negative offset equal to the pulse width will need to
45 remove that workaround.
48 From legacy ata(4) driver was removed support for SATA controllers
49 supported by more functional drivers ahci(4), siis(4) and mvs(4).
50 Kernel modules ataahci and ataadaptec were removed completely,
51 replaced by ahci and mvs modules respectively.
57 As ZFS requires more kernel stack pages than is the default on some
58 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
59 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
61 Please consider using 'options KSTACK_PAGES=X' where X is greater
62 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
65 The default Unbound configuration now enables remote control
66 using a local socket. Users who have already enabled the
67 local_unbound service should regenerate their configuration
68 by running "service local_unbound setup" as root.
71 An additional fix for the issue described in the 20150614 sendmail
72 entry below has been been committed in revision 284786.
75 The fix for the issue described in the 20150614 sendmail entry
76 below has been been committed in revision 284485. The work
77 around described in that entry is no longer needed unless the
78 default setting is overridden by a confDH_PARAMETERS configuration
79 setting of '5' or pointing to a 512 bit DH parameter file.
82 The import of openssl to address the FreeBSD-SA-15:10.openssl
83 security advisory includes a change which rejects handshakes
84 with DH parameters below 768 bits. sendmail releases prior
85 to 8.15.2 (not yet released), defaulted to a 512 bit
86 DH parameter setting for client connections. To work around
87 this interoperability, sendmail can be configured to use a
88 2048 bit DH parameter by:
90 1. Edit /etc/mail/`hostname`.mc
91 2. If a setting for confDH_PARAMETERS does not exist or
92 exists and is set to a string beginning with '5',
94 3. If a setting for confDH_PARAMETERS exists and is set to
95 a file path, create a new file with:
96 openssl dhparam -out /path/to/file 2048
97 4. Rebuild the .cf file:
98 cd /etc/mail/; make; make install
100 cd /etc/mail/; make restart
102 A sendmail patch is coming, at which time this file will be
106 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
107 defined in symlink(7); previously symlinks were silently ignored.
110 The const qualifier has been removed from iconv(3) to comply with
111 POSIX. The ports tree is aware of this from r384038 onwards.
114 At svn r275807, The default linux compat kernel ABI has been adjusted
115 to 2.6.18 in support of the linux-c6 compat ports infrastructure
116 update. If you wish to continue using the linux-f10 compat ports,
117 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
118 encouraged to update their linux-compat packages to linux-c6 during
119 their next update cycle.
121 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
124 pjdfstest has been integrated into kyua as an opt-in test suite.
125 Please see share/doc/pjdfstest/README for a more details on how to
132 The ofwfb driver, used to provide a graphics console on PowerPC when
133 using vt(4), no longer allows mmap() of all of physical memory. This
134 will prevent Xorg on PowerPC with some ATI graphics cards from
135 initializing properly unless x11-servers/xorg-server is updated to
139 The libatf-c and libatf-c++ major versions were downgraded to 0 and
140 1 respectively to match the upstream numbers. They were out of
141 sync because, when they were originally added to FreeBSD, the
142 upstream versions were not respected. These libraries are private
143 and not yet built by default, so renumbering them should be a
144 non-issue. However, unclean source trees will yield broken test
145 programs once the operator executes "make delete-old-libs" after a
148 Additionally, the atf-sh binary was made private by moving it into
149 /usr/libexec/. Already-built shell test programs will keep the
150 path to the old binary so they will break after "make delete-old"
153 If you are using WITH_TESTS=yes (not the default), wipe the object
154 tree and rebuild from scratch to prevent spurious test failures.
155 This is only needed once: the misnumbered libraries and misplaced
156 binaries have been added to OptionalObsoleteFiles.inc so they will
157 be removed during a clean upgrade.
160 The ixgbe tunables now match their sysctl counterparts, for example:
161 hw.ixgbe.enable_aim => hw.ix.enable_aim
162 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
165 The NFSv4.1 server committed by r269398 changes the internal
166 function call interfaces used between the NFS and krpc modules.
167 As such, __FreeBSD_version was bumped.
170 The default unbound configuration has been modified to address
171 issues with reverse lookups on networks that use private
172 address ranges. If you use the local_unbound service, run
173 "service local_unbound setup" as root to regenerate your
174 configuration, then "service local_unbound reload" to load the
178 It is no longer necessary to include the dwarf version in your DEBUG
179 options in your kernel config file. The bug that required it to be
180 placed in the config file has bene fixed. DEBUG should now just
181 contain -g. The build system will automatically update things
182 to do the right thing.
185 Several ABI breaking changes were merged to CTL and new iSCSI code.
186 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
187 iscsictl need to be rebuilt to work with a new kernel.
190 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
191 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
192 which differs from the behaviour controlled by this knob.)
195 On i386 and amd64 systems, the onifconsole flag is now set by default
196 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
197 as a login TTY if it is set in the bootloader as an active kernel
198 console. No changes in behavior should result otherwise. To revert to
199 the previous behavior, set ttyu0 to "off" in /etc/ttys.
202 Clang and llvm have been upgraded to 3.4.1 release.
205 Clang and llvm have been upgraded to 3.4 release.
208 If a Makefile in a tests/ directory was auto-generating a Kyuafile
209 instead of providing an explicit one, this would prevent such
210 Makefile from providing its own Kyuafile in the future during
211 NO_CLEAN builds. This has been fixed in the Makefiles but manual
212 intervention is needed to clean an objdir if you use NO_CLEAN:
213 # find /usr/obj -name Kyuafile | xargs rm -f
216 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
217 capability mode support. Please note that enabling the feature in
218 kernel is still highly recommended.
221 OpenSSH is now built with sandbox support, and will use sandbox as
222 the default privilege separation method. This requires Capsicum
223 capability mode support in kernel.
226 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
227 been deprecated and will not be part of FreeBSD 11.0 and later
228 releases. If you use this driver, please consider switching to
229 the nfe(4) driver instead.
235 The behavior of gss_pseudo_random() for the krb5 mechanism
236 has changed, for applications requesting a longer random string
237 than produced by the underlying enctype's pseudo-random() function.
238 In particular, the random string produced from a session key of
239 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
240 be different at the 17th octet and later, after this change.
241 The counter used in the PRF+ construction is now encoded as a
242 big-endian integer in accordance with RFC 4402.
243 __FreeBSD_version is bumped to 1000701.
246 The WITHOUT_ATF build knob has been removed and its functionality
247 has been subsumed into the more generic WITHOUT_TESTS. If you were
248 using the former to disable the build of the ATF libraries, you
249 should change your settings to use the latter.
252 The default version of mtree is nmtree which is obtained from
253 NetBSD. The output is generally the same, but may vary
254 slightly. If you found you need identical output adding
255 "-F freebsd9" to the command line should do the trick. For the
256 time being, the old mtree is available as fmtree.
259 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
260 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
261 1.1.4_8 and verify bsdyml not linked in, before running "make
263 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
265 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
268 The rc.d/jail script has been updated to support jail(8)
269 configuration file. The "jail_<jname>_*" rc.conf(5) variables
270 for per-jail configuration are automatically converted to
271 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
272 This is transparently backward compatible. See below about some
273 incompatibilities and rc.conf(5) manual page for more details.
275 These variables are now deprecated in favor of jail(8) configuration
276 file. One can use "rc.d/jail config <jname>" command to generate
277 a jail(8) configuration file in /var/run/jail.<jname>.conf without
278 running the jail(8) utility. The default pathname of the
279 configuration file is /etc/jail.conf and can be specified by
280 using $jail_conf or $jail_<jname>_conf variables.
282 Please note that jail_devfs_ruleset accepts an integer at
283 this moment. Please consider to rewrite the ruleset name
287 BIND has been removed from the base system. If all you need
288 is a local resolver, simply enable and start the local_unbound
289 service instead. Otherwise, several versions of BIND are
290 available in the ports tree. The dns/bind99 port is one example.
292 With this change, nslookup(1) and dig(1) are no longer in the base
293 system. Users should instead use host(1) and drill(1) which are
294 in the base system. Alternatively, nslookup and dig can
295 be obtained by installing the dns/bind-tools port.
298 With the addition of unbound(8), a new unbound user is now
299 required during installworld. "mergemaster -p" can be used to
300 add the user prior to installworld, as documented in the handbook.
303 OpenSSH is now built with DNSSEC support, and will by default
304 silently trust signed SSHFP records. This can be controlled with
305 the VerifyHostKeyDNS client configuration setting. DNSSEC support
306 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
309 The GNU Compiler Collection and C++ standard library (libstdc++)
310 are no longer built by default on platforms where clang is the system
311 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
315 The PROCDESC kernel option is now part of the GENERIC kernel
316 configuration and is required for the rwhod(8) to work.
317 If you are using custom kernel configuration, you should include
321 The API and ABI related to the Capsicum framework was modified
322 in backward incompatible way. The userland libraries and programs
323 have to be recompiled to work with the new kernel. This includes the
324 following libraries and programs, but the whole buildworld is
325 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
326 kdump, procstat, rwho, rwhod, uniq.
329 AES-NI intrinsic support has been added to gcc. The AES-NI module
330 has been updated to use this support. A new gcc is required to build
331 the aesni module on both i386 and amd64.
334 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
335 Thus "device padlock_rng" and "device rdrand_rng" should be
336 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
339 WITH_ICONV has been split into two feature sets. WITH_ICONV now
340 enables just the iconv* functionality and is now on by default.
341 WITH_LIBICONV_COMPAT enables the libiconv api and link time
342 compatability. Set WITHOUT_ICONV to build the old way.
343 If you have been using WITH_ICONV before, you will very likely
344 need to turn on WITH_LIBICONV_COMPAT.
347 INVARIANTS option now enables DEBUG for code with OpenSolaris and
348 Illumos origin, including ZFS. If you have INVARIANTS in your
349 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
351 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
352 locks if WITNESS option was set. Because that generated a lot of
353 witness(9) reports and all of them were believed to be false
354 positives, this is no longer done. New option OPENSOLARIS_WITNESS
355 can be used to achieve the previous behavior.
358 Timer values in IPv6 data structures now use time_uptime instead
359 of time_second. Although this is not a user-visible functional
360 change, userland utilities which directly use them---ndp(8),
361 rtadvd(8), and rtsold(8) in the base system---need to be updated
365 find -delete can now delete the pathnames given as arguments,
366 instead of only files found below them or if the pathname did
367 not contain any slashes. Formerly, the following error message
370 find: -delete: <path>: relative path potentially not safe
372 Deleting the pathnames given as arguments can be prevented
373 without error messages using -mindepth 1 or by changing
374 directory and passing "." as argument to find. This works in the
375 old as well as the new version of find.
378 Behavior of devfs rules path matching has been changed.
379 Pattern is now always matched against fully qualified devfs
380 path and slash characters must be explicitly matched by
381 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
382 subdirectories must be reviewed.
385 The default ARM ABI has changed to the ARM EABI. The old ABI is
386 incompatible with the ARM EABI and all programs and modules will
387 need to be rebuilt to work with a new kernel.
389 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
391 NOTE: Support for the old ABI will be removed in the future and
392 users are advised to upgrade.
395 pkg_install has been disconnected from the build if you really need it
396 you should add WITH_PKGTOOLS in your src.conf(5).
399 Most of network statistics structures were changed to be able
400 keep 64-bits counters. Thus all tools, that work with networking
401 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
404 Fix targets that run multiple make's to use && rather than ;
405 so that subsequent steps depend on success of previous.
407 NOTE: if building 'universe' with -j* on stable/8 or stable/9
408 it would be better to start the build using bmake, to avoid
409 overloading the machine.
412 Fix a bug that allowed a tracing process (e.g. gdb) to write
413 to a memory-mapped file in the traced process's address space
414 even if neither the traced process nor the tracing process had
415 write access to that file.
418 CVS has been removed from the base system. An exact copy
419 of the code is available from the devel/cvs port.
422 Some people report the following error after the switch to bmake:
424 make: illegal option -- J
425 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
427 *** [buildworld] Error code 2
429 this likely due to an old instance of make in
430 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
431 which src/Makefile will use that blindly, if it exists, so if
432 you see the above error:
434 rm -rf `make -V MAKEPATH`
439 Use bmake by default.
440 Whereas before one could choose to build with bmake via
441 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
442 make. The goal is to remove these knobs for 10-RELEASE.
444 It is worth noting that bmake (like gmake) treats the command
445 line as the unit of failure, rather than statements within the
446 command line. Thus '(cd some/where && dosomething)' is safer
447 than 'cd some/where; dosomething'. The '()' allows consistent
448 behavior in parallel build.
451 Fix a bug that allows NFS clients to issue READDIR on files.
454 The WITHOUT_IDEA option has been removed because
455 the IDEA patent expired.
458 The sysctl which controls TRIM support under ZFS has been renamed
459 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
463 The mergemaster command now uses the default MAKEOBJDIRPREFIX
464 rather than creating it's own in the temporary directory in
465 order allow access to bootstrapped versions of tools such as
466 install and mtree. When upgrading from version of FreeBSD where
467 the install command does not support -l, you will need to
468 install a new mergemaster command if mergemaster -p is required.
469 This can be accomplished with the command (cd src/usr.sbin/mergemaster
473 Legacy ATA stack, disabled and replaced by new CAM-based one since
474 FreeBSD 9.0, completely removed from the sources. Kernel modules
475 atadisk and atapi*, user-level tools atacontrol and burncd are
476 removed. Kernel option `options ATA_CAM` is now permanently enabled
480 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
481 and socketpair(2). Software, in particular Kerberos, may
482 automatically detect and use these during building. The resulting
483 binaries will not work on older kernels.
486 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
487 information, see the respective 20130304 entry).
490 Recent commits to callout(9) changed the size of struct callout,
491 so the KBI is probably heavily disturbed. Also, some functions
492 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
493 by macros. Every kernel module using it won't load, so rebuild
496 The ctl device has been re-enabled in GENERIC for i386 and amd64,
497 but does not initialize by default (because of the new CTL_DISABLE
498 option) to save memory. To re-enable it, remove the CTL_DISABLE
499 option from the kernel config file or set kern.cam.ctl.disable=0
500 in /boot/loader.conf.
503 The ctl device has been disabled in GENERIC for i386 and amd64.
504 This was done due to the extra memory being allocated at system
505 initialisation time by the ctl driver which was only used if
506 a CAM target device was created. This makes a FreeBSD system
507 unusable on 128MB or less of RAM.
510 A new compression method (lz4) has been merged to -HEAD. Please
511 refer to zpool-features(7) for more information.
513 Please refer to the "ZFS notes" section of this file for information
514 on upgrading boot ZFS pools.
517 A BSD-licensed patch(1) variant has been added and is installed
518 as bsdpatch, being the GNU version the default patch.
519 To inverse the logic and use the BSD-licensed one as default,
520 while having the GNU version installed as gnupatch, rebuild
521 and install world with the WITH_BSD_PATCH knob set.
524 Due to the use of the new -l option to install(1) during build
525 and install, you must take care not to directly set the INSTALL
526 make variable in your /etc/make.conf, /etc/src.conf, or on the
527 command line. If you wish to use the -C flag for all installs
528 you may be able to add INSTALL+=-C to /etc/make.conf or
532 The install(1) option -M has changed meaning and now takes an
533 argument that is a file or path to append logs to. In the
534 unlikely event that -M was the last option on the command line
535 and the command line contained at least two files and a target
536 directory the first file will have logs appended to it. The -M
537 option served little practical purpose in the last decade so its
538 use is expected to be extremely rare.
541 After switching to Clang as the default compiler some users of ZFS
542 on i386 systems started to experience stack overflow kernel panics.
543 Please consider using 'options KSTACK_PAGES=4' in such configurations.
546 GEOM_LABEL now mangles label names read from file system metadata.
547 Mangling affect labels containing spaces, non-printable characters,
548 '%' or '"'. Device names in /etc/fstab and other places may need to
552 By default, only the 10 most recent kernel dumps will be saved. To
553 restore the previous behaviour (no limit on the number of kernel dumps
554 stored in the dump directory) add the following line to /etc/rc.conf:
559 With the addition of auditdistd(8), a new auditdistd user is now
560 required during installworld. "mergemaster -p" can be used to
561 add the user prior to installworld, as documented in the handbook.
564 The sin6_scope_id member variable in struct sockaddr_in6 is now
565 filled by the kernel before passing the structure to the userland via
566 sysctl or routing socket. This means the KAME-specific embedded scope
567 id in sin6_addr.s6_addr[2] is always cleared in userland application.
568 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
569 __FreeBSD_version is bumped to 1000025.
572 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
573 This means that the world and kernel will be compiled with clang
574 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
575 and /usr/bin/cpp. To disable this behavior and revert to building
576 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
577 of current may need to bootstrap WITHOUT_CLANG first if the clang
578 build fails (its compatibility window doesn't extend to the 9 stable
582 The IPFIREWALL_FORWARD kernel option has been removed. Its
583 functionality now turned on by default.
586 The ZERO_COPY_SOCKET kernel option has been removed and
587 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
588 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
589 mechanism which is not safe and may result in kernel crashes.
590 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
591 driver supports disposeable external page sized mbuf storage.
592 Proper replacements for both zero-copy mechanisms are under
593 consideration and will eventually lead to complete removal
594 of the two kernel options.
597 The IPv4 network stack has been converted to network byte
598 order. The following modules need to be recompiled together
599 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
600 pf(4), ipfw(4), ng_ipfw(4), stf(4).
603 Support for non-MPSAFE filesystems was removed from VFS. The
604 VFS_VERSION was bumped, all filesystem modules shall be
608 All the non-MPSAFE filesystems have been disconnected from
609 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
610 portalfs, smbfs, xfs.
613 The interface cloning API and ABI has changed. The following
614 modules need to be recompiled together with kernel:
615 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
616 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
617 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
620 The sdhci driver was split in two parts: sdhci (generic SD Host
621 Controller logic) and sdhci_pci (actual hardware driver).
622 No kernel config modifications are required, but if you
623 load sdhc as a module you must switch to sdhci_pci instead.
626 Import the FUSE kernel and userland support into base system.
629 The GNU sort(1) program has been removed since the BSD-licensed
630 sort(1) has been the default for quite some time and no serious
631 problems have been reported. The corresponding WITH_GNU_SORT
635 The pfil(9) API/ABI for AF_INET family has been changed. Packet
636 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
640 The net80211(4) ABI has been changed to allow for improved driver
641 PS-POLL and power-save support. All wireless drivers need to be
642 recompiled to work with the new kernel.
645 The random(4) support for the VIA hardware random number
646 generator (`PADLOCK') is no longer enabled unconditionally.
647 Add the padlock_rng device in the custom kernel config if
648 needed. The GENERIC kernels on i386 and amd64 do include the
649 device, so the change only affects the custom kernel
653 The pf(4) packet filter ABI has been changed. pfctl(8) and
654 snmp_pf module need to be recompiled to work with new kernel.
657 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
658 to -HEAD. Pools that have empty_bpobj in active state can not be
659 imported read-write with ZFS implementations that do not support
660 this feature. For more information read the zpool-features(5)
664 The sparc64 ZFS loader has been changed to no longer try to auto-
665 detect ZFS providers based on diskN aliases but now requires these
666 to be explicitly listed in the OFW boot-device environment variable.
669 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
670 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
671 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
674 The following sysctls and tunables have been renamed for consistency
675 with other variables:
676 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
677 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
680 The sort utility has been replaced with BSD sort. For now, GNU sort
681 is also available as "gnusort" or the default can be set back to
682 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
683 installed as "bsdsort".
686 A new version of ZFS (pool version 5000) has been merged to -HEAD.
687 Starting with this version the old system of ZFS pool versioning
688 is superseded by "feature flags". This concept enables forward
689 compatibility against certain future changes in functionality of ZFS
690 pools. The first read-only compatible "feature flag" for ZFS pools
691 is named "com.delphix:async_destroy". For more information
692 read the new zpool-features(5) manual page.
693 Please refer to the "ZFS notes" section of this file for information
694 on upgrading boot ZFS pools.
697 The malloc(3) implementation embedded in libc now uses sources imported
698 as contrib/jemalloc. The most disruptive API change is to
699 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
700 delete it prior to installworld, and optionally re-create it using the
701 new format after rebooting. See malloc.conf(5) for details
702 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
706 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
707 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
708 now spelled mips. This is to aid compatibility with third-party
709 software that expects this naming scheme in uname(3). Little-endian
710 settings are unchanged. If you are updating a big-endian mips64 machine
711 from before this change, you may need to set MACHINE_ARCH=mips64 in
712 your environment before the new build system will recognize your machine.
715 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
719 Now unix domain sockets behave "as expected" on nullfs(5). Previously
720 nullfs(5) did not pass through all behaviours to the underlying layer,
721 as a result if we bound to a socket on the lower layer we could connect
722 only to the lower path; if we bound to the upper layer we could connect
723 only to the upper path. The new behavior is one can connect to both the
724 lower and the upper paths regardless what layer path one binds to.
727 The getifaddrs upgrade path broken with 20111215 has been restored.
728 If you have upgraded in between 20111215 and 20120209 you need to
729 recompile libc again with your kernel. You still need to recompile
730 world to be able to configure CARP but this restriction already
734 The set_rcvar() function has been removed from /etc/rc.subr. All
735 base and ports rc.d scripts have been updated, so if you have a
736 port installed with a script in /usr/local/etc/rc.d you can either
737 hand-edit the rcvar= line, or reinstall the port.
739 An easy way to handle the mass-update of /etc/rc.d:
740 rm /etc/rc.d/* && mergemaster -i
743 panic(9) now stops other CPUs in the SMP systems, disables interrupts
744 on the current CPU and prevents other threads from running.
745 This behavior can be reverted using the kern.stop_scheduler_on_panic
747 The new behavior can be incompatible with kern.sync_on_panic.
750 The carp(4) facility has been changed significantly. Configuration
751 of the CARP protocol via ifconfig(8) has changed, as well as format
752 of CARP events submitted to devd(8) has changed. See manual pages
753 for more information. The arpbalance feature of carp(4) is currently
754 not supported anymore.
756 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
757 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
758 need to be recompiled.
761 The acpi_wmi(4) status device /dev/wmistat has been renamed to
765 The option VFS_ALLOW_NONMPSAFE option has been added in order to
766 explicitely support non-MPSAFE filesystems.
767 It is on by default for all supported platform at this present
771 The broken amd(4) driver has been replaced with esp(4) in the amd64,
772 i386 and pc98 GENERIC kernel configuration files.
775 sysinstall has been removed
778 The stable/9 branch created in subversion. This corresponds to the
779 RELENG_9 branch in CVS.
782 This commit modifies vfs_register() so that it uses a hash
783 calculation to set vfc_typenum, which is enabled by default.
784 The first time a system is booted after this change, the
785 vfc_typenum values will change for all file systems. The
786 main effect of this is a change to the NFS server file handles
787 for file systems that use vfc_typenum in their fsid, such as ZFS.
788 It will, however, prevent vfc_typenum from changing when file
789 systems are loaded in a different order for subsequent reboots.
790 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
791 until you are ready to remount all NFS clients after a reboot.
794 Bump the shared library version numbers for libraries that
795 do not use symbol versioning, have changed the ABI compared
796 to stable/8 and which shared library version was not bumped.
797 Done as part of 9.0-RELEASE cycle.
800 During the merge of Capsicum features, the fget(9) KPI was modified.
801 This may require the rebuilding of out-of-tree device drivers --
802 issues have been reported specifically with the nVidia device driver.
803 __FreeBSD_version is bumped to 900041.
805 Also, there is a period between 20110811 and 20110814 where the
806 special devices /dev/{stdin,stdout,stderr} did not work correctly.
807 Building world from a kernel during that window may not work.
810 The packet filter (pf) code has been updated to OpenBSD 4.5.
811 You need to update userland tools to be in sync with kernel.
812 This update breaks backward compatibility with earlier pfsync(4)
813 versions. Care must be taken when updating redundant firewall setups.
816 The following sysctls and tunables are retired on x86 platforms:
818 machdep.hlt_logical_cpus
819 The following sysctl is retired:
820 machdep.hyperthreading_allowed
821 The sysctls were supposed to provide a way to dynamically offline and
822 online selected CPUs on x86 platforms, but the implementation has not
823 been reliable especially with SCHED_ULE scheduler.
824 machdep.hyperthreading_allowed tunable is still available to ignore
825 hyperthreading CPUs at OS level.
826 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
827 where X is an APIC ID of a CPU. Be advised, though, that disabling
828 CPUs in non-uniform fashion will result in non-uniform topology and
829 may lead to sub-optimal system performance with SCHED_ULE, which is
833 cpumask_t type is retired and cpuset_t is used in order to describe
837 Changes to ifconfig(8) for dynamic address family detection mandate
838 that you are running a kernel of 20110525 or later. Make sure to
839 follow the update procedure to boot a new kernel before installing
843 Support for sun4v architecture is officially dropped
846 Several KPI breaking changes have been committed to the mii(4) layer,
847 the PHY drivers and consequently some Ethernet drivers using mii(4).
848 This means that miibus.ko and the modules of the affected Ethernet
849 drivers need to be recompiled.
851 Note to kernel developers: Given that the OUI bit reversion problem
852 was fixed as part of these changes all mii(4) commits related to OUIs,
853 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
854 handling, no longer can be merged verbatim to stable/8 and previous
858 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
859 into their kernel configurations along with 'device pci'.
862 The default NFS client is now the new NFS client, so fstype "newnfs"
863 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
864 Although mounts via fstype "nfs" will usually work without userland
865 changes, it is recommended that the mount(8) and mount_nfs(8)
866 commands be rebuilt from sources and that a link to mount_nfs called
867 mount_oldnfs be created. The new client is compiled into the
868 kernel with "options NFSCL" and this is needed for diskless root
869 file systems. The GENERIC kernel configs have been changed to use
870 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
871 To use the regular/old client, you can "mount -t oldnfs ...". For
872 a diskless root file system, you must also include a line like:
874 vfs.root.mountfrom="oldnfs:"
876 in the boot/loader.conf on the root fs on the NFS server to make
877 a diskless root fs use the old client.
880 The GENERIC kernels for all architectures now default to the new
881 CAM-based ATA stack. It means that all legacy ATA drivers were
882 removed and replaced by respective CAM drivers. If you are using
883 ATA device names in /etc/fstab or other places, make sure to update
884 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
885 where 'Y's are the sequential numbers starting from zero for each type
886 in order of detection, unless configured otherwise with tunables,
887 see cam(4)). There will be symbolic links created in /dev/ to map
888 old adX devices to the respective adaY. They should provide basic
889 compatibility for file systems mounting in most cases, but they do
890 not support old user-level APIs and do not have respective providers
891 in GEOM. Consider using updated management tools with new device names.
893 It is possible to load devices ahci, ata, siis and mvs as modules,
894 but option ATA_CAM should remain in kernel configuration to make ata
895 module work as CAM driver supporting legacy ATA controllers. Device ata
896 still can be used in modular fashion (atacore + ...). Modules atadisk
897 and atapi* are not used and won't affect operation in ATA_CAM mode.
898 Note that to use CAM-based ATA kernel should include CAM devices
899 scbus, pass, da (or explicitly ada), cd and optionally others. All of
900 them are parts of the cam module.
902 ataraid(4) functionality is now supported by the RAID GEOM class.
903 To use it you can load geom_raid kernel module and use graid(8) tool
904 for management. Instead of /dev/arX device names, use /dev/raid/rX.
906 No kernel config options or code have been removed, so if a problem
907 arises, please report it and optionally revert to the old ATA stack.
908 In order to do it you can remove from the kernel config:
913 , and instead add back:
914 device atadisk # ATA disk drives
915 device ataraid # ATA RAID drives
916 device atapicd # ATAPI CDROM drives
917 device atapifd # ATAPI floppy drives
918 device atapist # ATAPI tape drives
921 The default NFS server has been changed to the new server, which
922 was referred to as the experimental server. If you need to switch
923 back to the old NFS server, you must now put the "-o" option on
924 both the mountd and nfsd commands. This can be done using the
925 mountd_flags and nfs_server_flags rc.conf variables until an
926 update to the rc scripts is committed, which is coming soon.
929 The GNU Objective-C runtime library (libobjc), and other Objective-C
930 related components have been removed from the base system. If you
931 require an Objective-C library, please use one of the available ports.
934 ath(4) has been split into bus- and device- modules. if_ath contains
935 the HAL, the TX rate control and the network device code. if_ath_pci
936 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
937 contains the AHB glue. Users need to load both if_ath_pci and if_ath
938 in order to use ath on everything else.
940 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
941 need to load if_ath and if_ath_pci for ath(4) operation.
944 As part of the replacement of sysinstall, the process of building
945 release media has changed significantly. For details, please re-read
946 release(7), which has been updated to reflect the new build process.
949 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
950 is the last available version under GPLv2. It brings a number of new
951 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
952 4.1 and SSE 4.2), better support for powerpc64, a number of new
953 directives, and lots of other small improvements. See the ChangeLog
954 file in contrib/binutils for the full details.
957 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
958 compliant, and will now use half of hash for authentication.
959 This will break interoperability with all stacks (including all
960 actual FreeBSD versions) who implement
961 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
963 The only workaround with such peers is to use another HMAC
964 algorithm for IPsec ("phase 2") authentication.
967 Remove the uio_yield prototype and symbol. This function has
968 been misnamed since it was introduced and should not be
969 globally exposed with this name. The equivalent functionality
970 is now available using kern_yield(curthread->td_user_pri).
971 The function remains undocumented.
974 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
975 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
976 for scalar sysctls is defined but disabled. Code that needs
977 UQUAD to pass the type checking that must compile on older
978 systems where the define is not present can check against
979 __FreeBSD_version >= 900030.
981 The system dialog(1) has been replaced with a new version previously
982 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
983 with the previous version, but the libdialog associated with it has
984 a largely incompatible API. As such, the original version of libdialog
985 will be kept temporarily as libodialog, until its base system consumers
986 are replaced or updated. Bump __FreeBSD_version to 900030.
989 If you are trying to run make universe on a -stable system, and you get
990 the following warning:
991 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
992 unknown. config(8) likely too old."
993 or something similar to it, then you must upgrade your -stable system
994 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
995 stable/8) or build the config from the latest stable/8 branch and
996 install it on your system.
998 Prior to this date, building a current universe on 8-stable system from
999 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1000 error in the first kernel build phase. A new config on those old
1001 systems will fix that problem for older versions of -current.
1004 The TCP stack has been modified to allow Khelp modules to interact with
1005 it via helper hook points and store per-connection data in the TCP
1006 control block. Bump __FreeBSD_version to 900029. User space tools that
1007 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1011 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1012 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1013 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1014 to take advantage of it instead of using custom implementations. This
1015 means that these drivers now no longer unconditionally advertise
1016 support for flow control but only do so if flow control is a selected
1017 media option. This was implemented in the generic support that way in
1018 order to allow flow control to be switched on and off via ifconfig(8)
1019 with the PHY specific default to typically off in order to protect
1020 from unwanted effects. Consequently, if you used flow control with
1021 one of the above mentioned drivers you now need to explicitly enable
1022 it, for example via:
1023 ifconfig bge0 media auto mediaopt flowcontrol
1025 Along with the above mentioned changes generic support for setting
1026 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1027 e1000phy(4) as well as ip1000phy(4) have been converted to take
1028 advantage of it. This means that these drivers now no longer take the
1029 link0 parameter for selecting master mode but the master media option
1030 has to be used instead, for example like in the following:
1031 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1033 Selection of master mode now is also available with all other PHY
1034 drivers supporting 1000baseT.
1037 The TCP stack has received a significant update to add support for
1038 modularised congestion control and generally improve the clarity of
1039 congestion control decisions. Bump __FreeBSD_version to 900025. User
1040 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1041 sockstat) need to be recompiled.
1044 The man(1) utility has been replaced by a new version that no longer
1045 uses /etc/manpath.config. Please consult man.conf(5) for how to
1046 migrate local entries to the new format.
1049 The copyright strings printed by login(1) and sshd(8) at the time of a
1050 new connection have been removed to follow other operating systems and
1054 A workaround for a fixed ld bug has been removed in kernel code,
1055 so make sure that your system ld is built from sources after
1056 revision 210245 from 2010-07-19 (r211583 if building head kernel
1057 on stable/8, r211584 for stable/7; both from 2010-08-21).
1058 A symptom of incorrect ld version is different addresses for
1059 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1062 The $ipv6_prefer variable in rc.conf(5) has been split into
1063 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1065 The $ip6addrctl_policy is a variable to choose a pre-defined
1066 address selection policy set by ip6addrctl(8). A value
1067 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1070 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1071 flag (see an entry of 20090926) is set on an interface with no
1072 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1073 security reason. If you want IPv6 link-local address on all
1074 interfaces by default, set this to "YES".
1076 The old ipv6_prefer="YES" is equivalent to
1077 ipv6_activate_all_interfaces="YES" and
1078 ip6addrctl_policy="ipv6_prefer".
1081 DTrace has grown support for userland tracing. Due to this, DTrace is
1082 now i386 and amd64 only.
1083 dtruss(1) is now installed by default on those systems and a new
1084 kernel module is needed for userland tracing: fasttrap.
1085 No changes to your kernel config file are necessary to enable
1086 userland tracing, but you might consider adding 'STRIP=' and
1087 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1088 to have informative userland stack traces in DTrace (ustack).
1091 The acpi_aiboost(4) driver has been removed in favor of the new
1092 aibs(4) driver. You should update your kernel configuration file.
1095 BSD grep has been imported to the base system and it is built by
1096 default. It is completely BSD licensed, highly GNU-compatible, uses
1097 less memory than its GNU counterpart and has a small codebase.
1098 However, it is slower than its GNU counterpart, which is mostly
1099 noticeable for larger searches, for smaller ones it is measurable
1100 but not significant. The reason is complex, the most important factor
1101 is that we lack a modern and efficient regex library and GNU
1102 overcomes this by optimizing the searches internally. Future work
1103 on improving the regex performance is planned, for the meantime,
1104 users that need better performance, can build GNU grep instead by
1105 setting the WITH_GNU_GREP knob.
1108 Due to the import of powerpc64 support, all existing powerpc kernel
1109 configuration files must be updated with a machine directive like this:
1110 machine powerpc powerpc
1112 In addition, an updated config(8) is required to build powerpc kernels
1116 A new version of ZFS (version 15) has been merged to -HEAD.
1117 This version uses a python library for the following subcommands:
1118 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1119 For full functionality of these commands the following port must
1120 be installed: sysutils/py-zfs
1123 'vm_page's are now hashed by physical address to an array of mutexes.
1124 Currently this is only used to serialize access to hold_count. Over
1125 time the page queue mutex will be peeled away. This changes the size
1126 of pmap on every architecture. And requires all callers of vm_page_hold
1127 and vm_page_unhold to be updated.
1130 WITH_CTF can now be specified in src.conf (not recommended, there
1131 are some problems with static executables), make.conf (would also
1132 affect ports which do not use GNU make and do not override the
1133 compile targets) or in the kernel config (via "makeoptions
1135 When WITH_CTF was specified there before this was silently ignored,
1136 so make sure that WITH_CTF is not used in places which could lead
1137 to unwanted behavior.
1140 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1141 to allow 32-bit compatibility on non-x86 platforms. All kernel
1142 configurations on amd64 and ia64 platforms using these options must
1143 be modified accordingly.
1146 The utmp user accounting database has been replaced with utmpx,
1147 the user accounting interface standardized by POSIX.
1148 Unfortunately the semantics of utmp and utmpx don't match,
1149 making it practically impossible to support both interfaces.
1150 The user accounting database is used by tools like finger(1),
1151 last(1), talk(1), w(1) and ac(8).
1153 All applications in the base system use utmpx. This means only
1154 local binaries (e.g. from the ports tree) may still use these
1155 utmp database files. These applications must be rebuilt to make
1158 After the system has been upgraded, it is safe to remove the old
1159 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1160 assuming their contents is of no importance anymore. Old wtmp
1161 databases can only be used by last(1) and ac(8) after they have
1162 been converted to the new format using wtmpcvt(1).
1165 Introduce the kernel thread "deadlock resolver" (which can be enabled
1166 via the DEADLKRES option, see NOTES for more details) and the
1167 sleepq_type() function for sleepqueues.
1170 The rc.firewall and rc.firewall6 were unified, and
1171 rc.firewall6 and rc.d/ip6fw were removed.
1172 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1173 variables are obsoleted. Instead, the following new rc
1174 variables are added to rc.d/ipfw:
1176 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1177 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1178 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1180 The meanings correspond to the relevant IPv4 variables.
1186 The default terminal emulation for syscons(4) has been changed
1187 from cons25 to xterm on all platforms except pc98. This means
1188 that the /etc/ttys file needs to be updated to ensure correct
1189 operation of applications on the console.
1191 The terminal emulation style can be toggled per window by using
1192 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1193 options can be used to change the compile-time default back to
1196 To prevent graphical artifacts, make sure the TERM environment
1197 variable is set to match the terminal emulation that is being
1198 performed by syscons(4).
1201 The layout of the structure ieee80211req_scan_result has changed.
1202 Applications that require wireless scan results (e.g. ifconfig(8))
1203 from net80211 need to be recompiled.
1205 Applications such as wpa_supplicant(8) may require a full world
1206 build without using NO_CLEAN in order to get synchronized with the
1210 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1211 There's one kernel module for each firmware. Adding "device iwnfw"
1212 to the kernel configuration file means including all three firmware
1213 images inside the kernel. If you want to include just the one for
1214 your wireless card, use the devices iwn4965fw, iwn5000fw or
1218 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1219 into rc.d/netif. The changes are the following:
1221 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1222 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1223 Note that both variables need the "inet6" keyword at the head.
1225 Do not set $ipv6_network_interfaces manually if you do not
1226 understand what you are doing. It is not needed in most cases.
1228 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1231 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1232 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1234 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1235 all configured interfaces have "inet6 accept_rtadv" in the
1236 $ifconfig_IF_ipv6. These are for backward compatibility.
1238 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1239 functionality of interfaces with no corresponding
1240 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1241 and the default address selection policy of ip6addrctl(8)
1242 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1243 Note that if you want to configure IPv6 functionality on the
1244 disabled interfaces after boot, first you need to clear the flag by
1245 using ifconfig(8) like:
1247 ifconfig em0 inet6 -ifdisabled
1249 If YES, the default address selection policy is set as
1252 The default value of $ipv6_prefer is NO.
1254 4. If your system need to receive Router Advertisement messages,
1255 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1256 scripts automatically invoke rtsol(8) when the interface becomes
1257 UP. The Router Advertisement messages are used for SLAAC
1258 (State-Less Address AutoConfiguration).
1261 802.11s D3.03 support was committed. This is incompatible with the
1262 previous code, which was based on D3.0.
1265 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1266 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1267 control whether accepting Router Advertisement messages or not.
1268 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1269 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1270 The ifconfig(8) utility now supports these flags.
1273 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1274 mount(8) and -a option for df(1) to see them.
1277 The old tunable hw.bus.devctl_disable has been superseded by
1278 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1279 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1283 Remove the option STOP_NMI. The default action is now to use NMI only
1284 for KDB via the newly introduced function stop_cpus_hard() and
1285 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1288 The stable/8 branch created in subversion. This corresponds to the
1289 RELENG_8 branch in CVS.
1292 Bump the shared library version numbers for all libraries that do not
1293 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1294 __FreeBSD_version to 800105.
1297 Due to changes in the implementation of virtual network stack support,
1298 all network-related kernel modules must be recompiled. As this change
1299 breaks the ABI, bump __FreeBSD_version to 800104.
1302 The TOE interface to the TCP syncache has been modified to remove
1303 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1304 The cxgb driver is the only TOE consumer affected by this change, and
1305 needs to be recompiled along with the kernel. As this change breaks
1306 the ABI, bump __FreeBSD_version to 800103.
1309 Padding has been added to struct tcpcb, sackhint and tcpstat in
1310 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1311 maintaining the ABI. However, this change breaks the ABI, so bump
1312 __FreeBSD_version to 800102. User space tools that rely on the size of
1313 any of these structs (e.g. sockstat) need to be recompiled.
1316 The NFS_LEGACYRPC option has been removed along with the old kernel
1317 RPC implementation that this option selected. Kernel configurations
1318 may need to be adjusted.
1321 The network interface device nodes at /dev/net/<interface> have been
1322 removed. All ioctl operations can be performed the normal way using
1323 routing sockets. The kqueue functionality can generally be replaced
1324 with routing sockets.
1327 The documentation from the FreeBSD Documentation Project (Handbook,
1328 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1329 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1332 The ABI of various structures related to the SYSV IPC API have been
1333 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1334 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1338 Layout of struct vnet has changed as routing related variables were
1339 moved to their own Vimage module. Modules need to be recompiled. Bump
1340 __FreeBSD_version to 800099.
1343 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1344 respectively. As long as no more than 16 groups per process are used,
1345 no changes should be visible. When more than 16 groups are used, old
1346 binaries may fail if they call getgroups() or getgrouplist() with
1347 statically sized storage. Recompiling will work around this, but
1348 applications should be modified to use dynamically allocated storage
1349 for group arrays as POSIX.1-2008 does not cap an implementation's
1350 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1352 NFS and portalfs mounts may also be affected as the list of groups is
1353 truncated to 16. Users of NFS who use more than 16 groups, should
1354 take care that negative group permissions are not used on the exported
1355 file systems as they will not be reliable unless a GSSAPI based
1356 authentication method is used.
1359 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1360 option compiles in the support for adaptive spinning for lockmgrs
1361 which want to enable it. The lockinit() function now accepts the flag
1362 LK_ADAPTIVE in order to make the lock object subject to adaptive
1363 spinning when both held in write and read mode.
1366 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1367 changed. User applications that use this ioctl need to be rebuilt.
1370 The layout of struct thread has changed. Kernel and modules need to
1374 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1375 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1378 window(1) has been removed from the base system. It can now be
1379 installed from ports. The port is called misc/window.
1382 The way we are storing and accessing `routing table' entries has
1383 changed. Programs reading the FIB, like netstat, need to be
1387 A new netisr implementation has been added for FreeBSD 8. Network
1388 file system modules, such as igmp, ipdivert, and others, should be
1390 Bump __FreeBSD_version to 800096.
1393 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1397 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1398 Bump __FreeBSD_version to 800094.
1401 Add mnt_xflag field to 'struct mount'. File system modules need to be
1403 Bump __FreeBSD_version to 800093.
1406 The compiling option ADAPTIVE_SX has been retired while it has been
1407 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1408 The KPI for sx_init_flags() changes as accepting flags:
1409 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1410 been introduced in order to handle the reversed logic.
1411 Bump __FreeBSD_version to 800092.
1414 Add support for hierarchical jails. Remove global securelevel.
1415 Bump __FreeBSD_version to 800091.
1418 The layout of struct vnet_net has changed, therefore modules
1420 Bump __FreeBSD_version to 800090.
1423 The newly imported zic(8) produces a new format in the output. Please
1424 run tzsetup(8) to install the newly created data to /etc/localtime.
1427 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1428 hw.usb.* and is now consistent again with previous releases.
1431 802.11 monitor mode support was revised and driver api's were changed.
1432 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1433 of DLT_IEEE802_11. No user-visible data structures were changed but
1434 applications that use DLT_IEEE802_11 may require changes.
1435 Bump __FreeBSD_version to 800088.
1438 The layout of the following structs has changed: sysctl_oid,
1439 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1440 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1441 panics may be experienced. World rebuild is required for
1442 correctly checking networking state from userland.
1443 Bump __FreeBSD_version to 800085.
1446 MLDv2 and Source-Specific Multicast (SSM) have been merged
1447 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1448 The implementation of SSM within FreeBSD's IPv6 stack closely
1449 follows the IPv4 implementation.
1451 For kernel developers:
1453 * The most important changes are that the ip6_output() and
1454 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1455 and this lock has been downgraded to a non-recursive mutex.
1457 * As with the changes to the IPv4 stack to support SSM, filtering
1458 of inbound multicast traffic must now be performed by transport
1459 protocols within the IPv6 stack. This does not apply to TCP and
1460 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1462 * The KPIs used by IPv6 multicast are similar to those used by
1463 the IPv4 stack, with the following differences:
1464 * im6o_mc_filter() is analogous to imo_multicast_filter().
1465 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1466 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1467 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1468 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1469 for MLDv1 have an additional 'timer' argument which is used to
1470 jitter the initial membership report for the solicited-node
1471 multicast membership on-link.
1472 * This is not strictly needed for MLDv2, which already jitters
1473 its report transmissions. However, the 'timer' argument is
1474 preserved in case MLDv1 is active on the interface.
1476 * The KAME linked-list based IPv6 membership implementation has
1477 been refactored to use a vector similar to that used by the IPv4
1479 Code which maintains a list of its own multicast memberships
1480 internally, e.g. carp, has been updated to reflect the new
1483 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1484 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1485 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1486 implementation constraint which needs to be addressed in HEAD.
1488 For application developers:
1490 * The changes are broadly similar to those made for the IPv4
1493 * The use of IPv4 and IPv6 multicast socket options on the same
1494 socket, using mapped addresses, HAS NOT been tested or supported.
1496 * There are a number of issues with the implementation of various
1497 IPv6 multicast APIs which need to be resolved in the API surface
1498 before the implementation is fully compatible with KAME userland
1499 use, and these are mostly to do with interface index treatment.
1501 * The literature available discusses the use of either the delta / ASM
1502 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1503 using setsourcefilter(3)/getsourcefilter(3). For more information
1504 please refer to RFC 3768, 'Socket Interface Extensions for
1505 Multicast Source Filters'.
1507 * Applications which use the published RFC 3678 APIs should be fine.
1509 For systems administrators:
1511 * The mtest(8) utility has been refactored to support IPv6, in
1512 addition to IPv4. Interface addresses are no longer accepted
1513 as arguments, their names must be used instead. The utility
1514 will map the interface name to its first IPv4 address as
1515 returned by getifaddrs(3).
1517 * The ifmcstat(8) utility has also been updated to print the MLDv2
1518 endpoint state and source filter lists via sysctl(3).
1520 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1521 loopback of IPv6 multicast datagrams by default; it defaults to 1
1522 to preserve the existing behaviour. Disabling multicast loopback is
1523 recommended for optimal system performance.
1525 * The IPv6 MROUTING code has been changed to examine this sysctl
1526 instead of attempting to perform a group lookup before looping
1527 back forwarded datagrams.
1529 Bump __FreeBSD_version to 800084.
1532 Implement low-level Bluetooth HCI API.
1533 Bump __FreeBSD_version to 800083.
1536 The layout of struct malloc_type, used by modules to register new
1537 memory allocation types, has changed. Most modules will need to
1538 be rebuilt or panics may be experienced.
1539 Bump __FreeBSD_version to 800081.
1542 Anticipate overflowing inp_flags - add inp_flags2.
1543 This changes most offsets in inpcb, so checking v4 connection
1544 state will require a world rebuild.
1545 Bump __FreeBSD_version to 800080.
1548 Add an llentry to struct route and struct route_in6. Modules
1549 embedding a struct route will need to be recompiled.
1550 Bump __FreeBSD_version to 800079.
1553 The size of rt_metrics_lite and by extension rtentry has changed.
1554 Networking administration apps will need to be recompiled.
1555 The route command now supports show as an alias for get, weighting
1556 of routes, sticky and nostick flags to alter the behavior of stateful
1558 Bump __FreeBSD_version to 800078.
1561 Do not use Giant for kbdmux(4) locking. This is wrong and
1562 apparently causing more problems than it solves. This will
1563 re-open the issue where interrupt handlers may race with
1564 kbdmux(4) in polling mode. Typical symptoms include (but
1565 not limited to) duplicated and/or missing characters when
1566 low level console functions (such as gets) are used while
1567 interrupts are enabled (for example geli password prompt,
1568 mountroot prompt etc.). Disabling kbdmux(4) may help.
1571 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1572 kernel modules referencing any of the above need to be recompiled.
1573 Bump __FreeBSD_version to 800075.
1576 GEOM_PART has become the default partition slicer for storage devices,
1577 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1578 introduces some changes:
1580 MSDOS/EBR: the devices created from MSDOS extended partition entries
1581 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1582 to devices with offset-based names. fstabs may need to be modified.
1584 BSD: the "geometry does not match label" warning is harmless in most
1585 cases but it points to problems in file system misalignment with
1586 disk geometry. The "c" partition is now implicit, covers the whole
1587 top-level drive and cannot be (mis)used by users.
1589 General: Kernel dumps are now not allowed to be written to devices
1590 whose partition types indicate they are meant to be used for file
1591 systems (or, in case of MSDOS partitions, as something else than
1594 Most of these changes date approximately from 200812.
1597 The uscanner(4) driver has been removed from the kernel. This follows
1598 Linux removing theirs in 2.6 and making libusb the default interface
1599 (supported by sane).
1602 The multicast forwarding code has been cleaned up. netstat(1)
1603 only relies on KVM now for printing bandwidth upcall meters.
1604 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1605 ip6_mroute_mod respectively. The config(5) options for statically
1606 compiling this code remain the same, i.e. 'options MROUTING'.
1609 Support for the IFF_NEEDSGIANT network interface flag has been
1610 removed, which means that non-MPSAFE network device drivers are no
1611 longer supported. In particular, if_ar, if_sr, and network device
1612 drivers from the old (legacy) USB stack can no longer be built or
1616 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1617 a bunch of new language catalog files have also been added.
1618 This means that some common libc messages are now localized and
1619 they depend on the LC_MESSAGES environmental variable.
1622 The k8temp(4) driver has been renamed to amdtemp(4) since
1623 support for Family 10 and Family 11 CPU families was added.
1626 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1627 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1629 For kernel developers, the most important changes are that the
1630 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1631 and this lock has been downgraded to a non-recursive mutex.
1633 Transport protocols (UDP, Raw IP) are now responsible for filtering
1634 inbound multicast traffic according to group membership and source
1635 filters. The imo_multicast_filter() KPI exists for this purpose.
1636 Transports which do not use multicast (SCTP, TCP) already reject
1637 multicast by default. Forwarding and receive performance may improve
1638 as a mutex acquisition is no longer needed in the ip_input()
1639 low-level input path. in_addmulti() and in_delmulti() are shimmed
1640 to new KPIs which exist to support SSM in-kernel.
1642 For application developers, it is recommended that loopback of
1643 multicast datagrams be disabled for best performance, as this
1644 will still cause the lock to be taken for each looped-back
1645 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1646 be tuned to 0 to disable loopback by default; it defaults to 1
1647 to preserve the existing behaviour.
1649 For systems administrators, to obtain best performance with
1650 multicast reception and multiple groups, it is always recommended
1651 that a card with a suitably precise hash filter is used. Hash
1652 collisions will still result in the lock being taken within the
1653 transport protocol input path to check group membership.
1655 If deploying FreeBSD in an environment with IGMP snooping switches,
1656 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1657 enabled; this forces 224.0.0.0/24 group membership to be announced
1660 The size of 'struct igmpstat' has changed; netstat needs to be
1661 recompiled to reflect this.
1662 Bump __FreeBSD_version to 800070.
1665 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1666 updated to use it. This requires a buildworld/installworld in order to
1667 update the library and dependencies (usbconfig, etc). Its advisable to
1668 rebuild all ports which uses libusb. More specific directions are given
1669 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1670 libusb are no longer required and can be removed.
1673 A workaround is committed to allow the creation of System V shared
1674 memory segment of size > 2 GB on the 64-bit architectures.
1675 Due to a limitation of the existing ABI, the shm_segsz member
1676 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1677 wrong for large segments. Note that limits must be explicitly
1678 raised to allow such segments to be created.
1681 The layout of struct ifnet has changed, requiring a rebuild of all
1682 network device driver modules.
1685 The /dev handling for the new USB stack has changed, a
1686 buildworld/installworld is required for libusb20.
1689 The new USB2 stack has now been permanently moved in and all kernel and
1690 module names reverted to their previous values (eg, usb, ehci, ohci,
1691 ums, ...). The old usb stack can be compiled in by prefixing the name
1692 with the letter 'o', the old usb modules have been removed.
1693 Updating entry 20090216 for xorg and 20090215 for libmap may still
1697 The rc.conf(5) option if_up_delay has been renamed to
1698 defaultroute_delay to better reflect its purpose. If you have
1699 customized this setting in /etc/rc.conf you need to update it to
1703 xorg 7.4 wants to configure its input devices via hald which does not
1704 yet work with USB2. If the keyboard/mouse does not work in xorg then
1706 Option "AllowEmptyInput" "off"
1707 to your ServerLayout section. This will cause X to use the configured
1708 kbd and mouse sections from your xorg.conf.
1711 The GENERIC kernels for all architectures now default to the new USB2
1712 stack. No kernel config options or code have been removed so if a
1713 problem arises please report it and optionally revert to the old USB
1714 stack. If you are loading USB kernel modules or have a custom kernel
1715 that includes GENERIC then ensure that usb names are also changed over,
1716 eg uftdi -> usb2_serial_ftdi.
1718 Older programs linked against the ports libusb 0.1 need to be
1719 redirected to the new stack's libusb20. /etc/libmap.conf can
1721 # Map old usb library to new one for usb2 stack
1722 libusb-0.1.so.8 libusb20.so.1
1725 All USB ethernet devices now attach as interfaces under the name ueN
1726 (eg. ue0). This is to provide a predictable name as vendors often
1727 change usb chipsets in a product without notice.
1730 The ichsmb(4) driver has been changed to require SMBus slave
1731 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1732 All of the other SMBus controller drivers require left-justified
1733 slave addresses, so this change makes all the drivers provide the
1737 INET6 statistics (struct ip6stat) was updated.
1738 netstat(1) needs to be recompiled.
1741 NTFS has been removed from GENERIC kernel on amd64 to match
1742 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1743 will load ntfs.ko module automatically when NTFS support is
1744 actually needed, unless ntfs.ko is not installed or security
1745 level prohibits loading kernel modules. If either is the case,
1746 "options NTFS" has to be added into kernel config.
1749 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1750 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1751 800061. User space tools that rely on the size of struct tcpcb in
1752 tcp_var.h (e.g. sockstat) need to be recompiled.
1755 ng_tty(4) module updated to match the new TTY subsystem.
1756 Due to API change, user-level applications must be updated.
1757 New API support added to mpd5 CVS and expected to be present
1758 in next mpd5.3 release.
1761 With __FreeBSD_version 800060 the makefs tool is part of
1762 the base system (it was a port).
1765 The afdata and ifnet locks have been changed from mutexes to
1766 rwlocks, network modules will need to be re-compiled.
1769 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1770 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1771 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1772 architecture and 40 bytes on 64-bit architecture. The userland
1773 applications "arp" and "ndp" have been updated accordingly.
1774 The output from "netstat -r" shows only routing entries and
1775 none of the L2 information.
1778 __FreeBSD_version 800057 marks the switchover from the
1779 binary ath hal to source code. Users must add the line:
1781 options AH_SUPPORT_AR5416
1783 to their kernel config files when specifying:
1787 The ath_hal module no longer exists; the code is now compiled
1788 together with the driver in the ath module. It is now
1789 possible to tailor chip support (i.e. reduce the set of chips
1790 and thereby the code size); consult ath_hal(4) for details.
1793 __FreeBSD_version 800054 adds memory barriers to
1794 <machine/atomic.h>, new interfaces to ifnet to facilitate
1795 multiple hardware transmit queues for cards that support
1796 them, and a lock-less ring-buffer implementation to
1797 enable drivers to more efficiently manage queueing of
1801 A new version of ZFS (version 13) has been merged to -HEAD.
1802 This version has zpool attribute "listsnapshots" off by
1803 default, which means "zfs list" does not show snapshots,
1804 and is the same as Solaris behavior.
1807 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1810 The uhci, ohci, ehci and slhci USB Host controller drivers have
1811 been put into separate modules. If you load the usb module
1812 separately through loader.conf you will need to load the
1813 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1814 controller add the following to loader.conf:
1820 The ABI used by the PMC toolset has changed. Please keep
1821 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1825 atapci kernel module now includes only generic PCI ATA
1826 driver. AHCI driver moved to ataahci kernel module.
1827 All vendor-specific code moved into separate kernel modules:
1828 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1829 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1830 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1831 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1834 The TTY subsystem of the kernel has been replaced by a new
1835 implementation, which provides better scalability and an
1836 improved driver model. Most common drivers have been migrated to
1837 the new TTY subsystem, while others have not. The following
1838 drivers have not yet been ported to the new TTY layer:
1841 cy, digi, rc, rp, sio
1847 ng_h4, ng_tty, ppp, sl, snp
1849 Adding these drivers to your kernel configuration file shall
1850 cause compilation to fail.
1853 ntpd has been upgraded to 4.2.4p5.
1856 OpenSSH has been upgraded to 5.1p1.
1858 For many years, FreeBSD's version of OpenSSH preferred DSA
1859 over RSA for host and user authentication keys. With this
1860 upgrade, we've switched to the vendor's default of RSA over
1861 DSA. This may cause upgraded clients to warn about unknown
1862 host keys even for previously known hosts. Users should
1863 follow the usual procedure for verifying host keys before
1864 accepting the RSA key.
1866 This can be circumvented by setting the "HostKeyAlgorithms"
1867 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1870 Please note that the sequence of keys offered for
1871 authentication has been changed as well. You may want to
1872 specify IdentityFile in a different order to revert this
1876 The sio(4) driver has been removed from the i386 and amd64
1877 kernel configuration files. This means uart(4) is now the
1878 default serial port driver on those platforms as well.
1880 To prevent collisions with the sio(4) driver, the uart(4) driver
1881 uses different names for its device nodes. This means the
1882 onboard serial port will now most likely be called "ttyu0"
1883 instead of "ttyd0". You may need to reconfigure applications to
1884 use the new device names.
1886 When using the serial port as a boot console, be sure to update
1887 /boot/device.hints and /etc/ttys before booting the new kernel.
1888 If you forget to do so, you can still manually specify the hints
1889 at the loader prompt:
1891 set hint.uart.0.at="isa"
1892 set hint.uart.0.port="0x3F8"
1893 set hint.uart.0.flags="0x10"
1894 set hint.uart.0.irq="4"
1898 The gpt(8) utility has been removed. Use gpart(8) to partition
1902 The version that Linuxulator emulates was changed from 2.4.2
1903 to 2.6.16. If you experience any problems with Linux binaries
1904 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1905 if it fixes the problem contact emulation mailing list.
1908 ISDN4BSD (I4B) was removed from the src tree. You may need to
1909 update a your kernel configuration and remove relevant entries.
1912 I have checked in code to support multiple routing tables.
1913 See the man pages setfib(1) and setfib(2).
1914 This is a hopefully backwards compatible version,
1915 but to make use of it you need to compile your kernel
1916 with options ROUTETABLES=2 (or more up to 16).
1919 The 802.11 wireless support was redone to enable multi-bss
1920 operation on devices that are capable. The underlying device
1921 is no longer used directly but instead wlanX devices are
1922 cloned with ifconfig. This requires changes to rc.conf files.
1923 For example, change:
1924 ifconfig_ath0="WPA DHCP"
1927 ifconfig_wlan0="WPA DHCP"
1928 see rc.conf(5) for more details. In addition, mergemaster of
1929 /etc/rc.d is highly recommended. Simultaneous update of userland
1930 and kernel wouldn't hurt either.
1932 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1933 modules were merged into the base wlan module. All references
1934 to these modules (e.g. in kernel config files) must be removed.
1937 psm(4) has gained write(2) support in native operation level.
1938 Arbitrary commands can be written to /dev/psm%d and status can
1939 be read back from it. Therefore, an application is responsible
1940 for status validation and error recovery. It is a no-op in
1941 other operation levels.
1944 Support for KSE threading has been removed from the kernel. To
1945 run legacy applications linked against KSE libmap.conf may
1946 be used. The following libmap.conf may be used to ensure
1947 compatibility with any prior release:
1949 libpthread.so.1 libthr.so.1
1950 libpthread.so.2 libthr.so.2
1951 libkse.so.3 libthr.so.3
1954 The layout of struct vmspace has changed. This affects libkvm
1955 and any executables that link against libkvm and use the
1956 kvm_getprocs() function. In particular, but not exclusively,
1957 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1958 The effects are minimal, but it's advisable to upgrade world
1962 The latest em driver no longer has support in it for the
1963 82575 adapter, this is now moved to the igb driver. The
1964 split was done to make new features that are incompatible
1965 with older hardware easier to do.
1968 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1969 likewise the kernel option is now GEOM_LINUX_LVM.
1972 The default NFS mount mode has changed from UDP to TCP for
1973 increased reliability. If you rely on (insecurely) NFS
1974 mounting across a firewall you may need to update your
1978 Belatedly note the addition of m_collapse for compacting
1982 The fts(3) structures have been changed to use adequate
1983 integer types for their members and so to be able to cope
1984 with huge file trees. The old fts(3) ABI is preserved
1985 through symbol versioning in libc, so third-party binaries
1986 using fts(3) should still work, although they will not take
1987 advantage of the extended types. At the same time, some
1988 third-party software might fail to build after this change
1989 due to unportable assumptions made in its source code about
1990 fts(3) structure members. Such software should be fixed
1991 by its vendor or, in the worst case, in the ports tree.
1992 FreeBSD_version 800015 marks this change for the unlikely
1993 case that a portable fix is impossible.
1996 To upgrade to -current after this date, you must be running
1997 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1998 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2001 The ADAPTIVE_GIANT kernel option has been retired because its
2002 functionality is the default now.
2005 The AT keyboard emulation of sunkbd(4) has been turned on
2006 by default. In order to make the special symbols of the Sun
2007 keyboards driven by sunkbd(4) work under X these now have
2008 to be configured the same way as Sun USB keyboards driven
2009 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2011 Option "XkbLayout" "us"
2012 Option "XkbRules" "xorg"
2013 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2016 It has been decided that it is desirable to provide ABI
2017 backwards compatibility to the FreeBSD 4/5/6 versions of the
2018 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2019 broken with the introduction of PCI domain support (see the
2020 20070930 entry). Unfortunately, this required the ABI of
2021 PCIOCGETCONF to be broken again in order to be able to
2022 provide backwards compatibility to the old version of that
2023 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2024 again. As for prominent ports this affects neither pciutils
2025 nor xorg-server this time, the hal port needs to be rebuilt
2029 The misnamed kthread_create() and friends have been renamed
2030 to kproc_create() etc. Many of the callers already
2031 used kproc_start()..
2032 I will return kthread_create() and friends in a while
2033 with implementations that actually create threads, not procs.
2034 Renaming corresponds with version 800002.
2043 Avoid using make -j when upgrading. While generally safe, there are
2044 sometimes problems using -j to upgrade. If your upgrade fails with
2045 -j, please try again without -j. From time to time in the past there
2046 have been problems using -j with buildworld and/or installworld. This
2047 is especially true when upgrading between "distant" versions (eg one
2048 that cross a major release boundary or several minor releases, or when
2049 several months have passed on the -current branch).
2051 Sometimes, obscure build problems are the result of environment
2052 poisoning. This can happen because the make utility reads its
2053 environment when searching for values for global variables. To run
2054 your build attempts in an "environmental clean room", prefix all make
2055 commands with 'env -i '. See the env(1) manual page for more details.
2057 When upgrading from one major version to another it is generally best
2058 to upgrade to the latest code in the currently installed branch first,
2059 then do an upgrade to the new branch. This is the best-tested upgrade
2060 path, and has the highest probability of being successful. Please try
2061 this approach before reporting problems with a major version upgrade.
2063 When upgrading a live system, having a root shell around before
2064 installing anything can help undo problems. Not having a root shell
2065 around can lead to problems if pam has changed too much from your
2066 starting point to allow continued authentication after the upgrade.
2070 When upgrading the boot ZFS pool to a new version, always follow
2073 1.) recompile and reinstall the ZFS boot loader and boot block
2074 (this is part of "make buildworld" and "make installworld")
2076 2.) update the ZFS boot block on your boot drive
2078 The following example updates the ZFS boot block on the first
2079 partition (freebsd-boot) of a GPT partitioned drive ad0:
2080 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2082 Non-boot pools do not need these updates.
2086 If you are updating from a prior version of FreeBSD (even one just
2087 a few days old), you should follow this procedure. It is the most
2088 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2090 make kernel-toolchain
2091 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2092 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2094 To test a kernel once
2095 ---------------------
2096 If you just want to boot a kernel once (because you are not sure
2097 if it works, or if you want to boot a known bad kernel to provide
2098 debugging information) run
2099 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2100 nextboot -k testkernel
2102 To just build a kernel when you know that it won't mess you up
2103 --------------------------------------------------------------
2104 This assumes you are already running a CURRENT system. Replace
2105 ${arch} with the architecture of your machine (e.g. "i386",
2106 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2108 cd src/sys/${arch}/conf
2109 config KERNEL_NAME_HERE
2110 cd ../compile/KERNEL_NAME_HERE
2115 If this fails, go to the "To build a kernel" section.
2117 To rebuild everything and install it on the current system.
2118 -----------------------------------------------------------
2119 # Note: sometimes if you are running current you gotta do more than
2120 # is listed here if you are upgrading from a really old current.
2122 <make sure you have good level 0 dumps>
2124 make kernel KERNCONF=YOUR_KERNEL_HERE
2126 <reboot in single user> [3]
2133 To cross-install current onto a separate partition
2134 --------------------------------------------------
2135 # In this approach we use a separate partition to hold
2136 # current's root, 'usr', and 'var' directories. A partition
2137 # holding "/", "/usr" and "/var" should be about 2GB in
2140 <make sure you have good level 0 dumps>
2143 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2144 <maybe newfs current's root partition>
2145 <mount current's root partition on directory ${CURRENT_ROOT}>
2146 make installworld DESTDIR=${CURRENT_ROOT}
2147 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2148 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2149 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2150 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2151 <reboot into current>
2152 <do a "native" rebuild/install as described in the previous section>
2153 <maybe install compatibility libraries from ports/misc/compat*>
2157 To upgrade in-place from stable to current
2158 ----------------------------------------------
2159 <make sure you have good level 0 dumps>
2161 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2163 <reboot in single user> [3]
2170 Make sure that you've read the UPDATING file to understand the
2171 tweaks to various things you need. At this point in the life
2172 cycle of current, things change often and you are on your own
2173 to cope. The defaults can also change, so please read ALL of
2174 the UPDATING entries.
2176 Also, if you are tracking -current, you must be subscribed to
2177 freebsd-current@freebsd.org. Make sure that before you update
2178 your sources that you have read and understood all the recent
2179 messages there. If in doubt, please track -stable which has
2180 much fewer pitfalls.
2182 [1] If you have third party modules, such as vmware, you
2183 should disable them at this point so they don't crash your
2186 [3] From the bootblocks, boot -s, and then do
2191 adjkerntz -i # if CMOS is wall time
2192 Also, when doing a major release upgrade, it is required that
2193 you boot into single user mode to do the installworld.
2195 [4] Note: This step is non-optional. Failure to do this step
2196 can result in a significant reduction in the functionality of the
2197 system. Attempting to do it by hand is not recommended and those
2198 that pursue this avenue should read this file carefully, as well
2199 as the archives of freebsd-current and freebsd-hackers mailing lists
2200 for potential gotchas. The -U option is also useful to consider.
2201 See mergemaster(8) for more information.
2203 [5] Usually this step is a noop. However, from time to time
2204 you may need to do this if you get unknown user in the following
2205 step. It never hurts to do it all the time. You may need to
2206 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2207 install) after the buildworld before this step if you last updated
2208 from current before 20130425 or from -stable before 20130430.
2210 [6] This only deletes old files and directories. Old libraries
2211 can be deleted by "make delete-old-libs", but you have to make
2212 sure that no program is using those libraries anymore.
2214 [8] In order to have a kernel that can run the 4.x binaries needed to
2215 do an installworld, you must include the COMPAT_FREEBSD4 option in
2216 your kernel. Failure to do so may leave you with a system that is
2217 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2218 required to run the 5.x binaries on more recent kernels. And so on
2219 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2221 Make sure that you merge any new devices from GENERIC since the
2222 last time you updated your kernel config file.
2224 [9] When checking out sources, you must include the -P flag to have
2225 cvs prune empty directories.
2227 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2228 "?=" instead of the "=" assignment operator, so that buildworld can
2229 override the CPUTYPE if it needs to.
2231 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2232 not on the command line, or in /etc/make.conf. buildworld will
2233 warn if it is improperly defined.
2236 This file contains a list, in reverse chronological order, of major
2237 breakages in tracking -current. It is not guaranteed to be a complete
2238 list of such breakages, and only contains entries since October 10, 2007.
2239 If you need to see UPDATING entries from before that date, you will need
2240 to fetch an UPDATING file from an older FreeBSD release.
2242 Copyright information:
2244 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2246 Redistribution, publication, translation and use, with or without
2247 modification, in full or in part, in any form or format of this
2248 document are permitted without further permission from the author.
2250 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2251 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2252 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2253 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2254 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2255 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2256 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2257 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2258 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2259 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2260 POSSIBILITY OF SUCH DAMAGE.
2262 Contact Warner Losh if you have any questions about your use of