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.
23 The default Unbound configuration now enables remote control
24 using a local socket. Users who have already enabled the
25 local_unbound service should regenerate their configuration
26 by running "service local_unbound setup" as root.
29 An additional fix for the issue described in the 20150614 sendmail
30 entry below has been been committed in revision 284786.
33 The fix for the issue described in the 20150614 sendmail entry
34 below has been been committed in revision 284485. The work
35 around described in that entry is no longer needed unless the
36 default setting is overridden by a confDH_PARAMETERS configuration
37 setting of '5' or pointing to a 512 bit DH parameter file.
40 The import of openssl to address the FreeBSD-SA-15:10.openssl
41 security advisory includes a change which rejects handshakes
42 with DH parameters below 768 bits. sendmail releases prior
43 to 8.15.2 (not yet released), defaulted to a 512 bit
44 DH parameter setting for client connections. To work around
45 this interoperability, sendmail can be configured to use a
46 2048 bit DH parameter by:
48 1. Edit /etc/mail/`hostname`.mc
49 2. If a setting for confDH_PARAMETERS does not exist or
50 exists and is set to a string beginning with '5',
52 3. If a setting for confDH_PARAMETERS exists and is set to
53 a file path, create a new file with:
54 openssl dhparam -out /path/to/file 2048
55 4. Rebuild the .cf file:
56 cd /etc/mail/; make; make install
58 cd /etc/mail/; make restart
60 A sendmail patch is coming, at which time this file will be
64 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
65 defined in symlink(7); previously symlinks were silently ignored.
68 The const qualifier has been removed from iconv(3) to comply with
69 POSIX. The ports tree is aware of this from r384038 onwards.
72 At svn r275807, The default linux compat kernel ABI has been adjusted
73 to 2.6.18 in support of the linux-c6 compat ports infrastructure
74 update. If you wish to continue using the linux-f10 compat ports,
75 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
76 encouraged to update their linux-compat packages to linux-c6 during
77 their next update cycle.
79 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
82 pjdfstest has been integrated into kyua as an opt-in test suite.
83 Please see share/doc/pjdfstest/README for a more details on how to
90 The ofwfb driver, used to provide a graphics console on PowerPC when
91 using vt(4), no longer allows mmap() of all of physical memory. This
92 will prevent Xorg on PowerPC with some ATI graphics cards from
93 initializing properly unless x11-servers/xorg-server is updated to
97 The libatf-c and libatf-c++ major versions were downgraded to 0 and
98 1 respectively to match the upstream numbers. They were out of
99 sync because, when they were originally added to FreeBSD, the
100 upstream versions were not respected. These libraries are private
101 and not yet built by default, so renumbering them should be a
102 non-issue. However, unclean source trees will yield broken test
103 programs once the operator executes "make delete-old-libs" after a
106 Additionally, the atf-sh binary was made private by moving it into
107 /usr/libexec/. Already-built shell test programs will keep the
108 path to the old binary so they will break after "make delete-old"
111 If you are using WITH_TESTS=yes (not the default), wipe the object
112 tree and rebuild from scratch to prevent spurious test failures.
113 This is only needed once: the misnumbered libraries and misplaced
114 binaries have been added to OptionalObsoleteFiles.inc so they will
115 be removed during a clean upgrade.
118 The ixgbe tunables now match their sysctl counterparts, for example:
119 hw.ixgbe.enable_aim => hw.ix.enable_aim
120 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
123 The NFSv4.1 server committed by r269398 changes the internal
124 function call interfaces used between the NFS and krpc modules.
125 As such, __FreeBSD_version was bumped.
128 The default unbound configuration has been modified to address
129 issues with reverse lookups on networks that use private
130 address ranges. If you use the local_unbound service, run
131 "service local_unbound setup" as root to regenerate your
132 configuration, then "service local_unbound reload" to load the
136 It is no longer necessary to include the dwarf version in your DEBUG
137 options in your kernel config file. The bug that required it to be
138 placed in the config file has bene fixed. DEBUG should now just
139 contain -g. The build system will automatically update things
140 to do the right thing.
143 Several ABI breaking changes were merged to CTL and new iSCSI code.
144 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
145 iscsictl need to be rebuilt to work with a new kernel.
148 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
149 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
150 which differs from the behaviour controlled by this knob.)
153 On i386 and amd64 systems, the onifconsole flag is now set by default
154 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
155 as a login TTY if it is set in the bootloader as an active kernel
156 console. No changes in behavior should result otherwise. To revert to
157 the previous behavior, set ttyu0 to "off" in /etc/ttys.
160 Clang and llvm have been upgraded to 3.4.1 release.
163 Clang and llvm have been upgraded to 3.4 release.
166 If a Makefile in a tests/ directory was auto-generating a Kyuafile
167 instead of providing an explicit one, this would prevent such
168 Makefile from providing its own Kyuafile in the future during
169 NO_CLEAN builds. This has been fixed in the Makefiles but manual
170 intervention is needed to clean an objdir if you use NO_CLEAN:
171 # find /usr/obj -name Kyuafile | xargs rm -f
174 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
175 capability mode support. Please note that enabling the feature in
176 kernel is still highly recommended.
179 OpenSSH is now built with sandbox support, and will use sandbox as
180 the default privilege separation method. This requires Capsicum
181 capability mode support in kernel.
184 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
185 been deprecated and will not be part of FreeBSD 11.0 and later
186 releases. If you use this driver, please consider switching to
187 the nfe(4) driver instead.
193 The behavior of gss_pseudo_random() for the krb5 mechanism
194 has changed, for applications requesting a longer random string
195 than produced by the underlying enctype's pseudo-random() function.
196 In particular, the random string produced from a session key of
197 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
198 be different at the 17th octet and later, after this change.
199 The counter used in the PRF+ construction is now encoded as a
200 big-endian integer in accordance with RFC 4402.
201 __FreeBSD_version is bumped to 1000701.
204 The WITHOUT_ATF build knob has been removed and its functionality
205 has been subsumed into the more generic WITHOUT_TESTS. If you were
206 using the former to disable the build of the ATF libraries, you
207 should change your settings to use the latter.
210 The default version of mtree is nmtree which is obtained from
211 NetBSD. The output is generally the same, but may vary
212 slightly. If you found you need identical output adding
213 "-F freebsd9" to the command line should do the trick. For the
214 time being, the old mtree is available as fmtree.
217 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
218 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
219 1.1.4_8 and verify bsdyml not linked in, before running "make
221 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
223 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
226 The rc.d/jail script has been updated to support jail(8)
227 configuration file. The "jail_<jname>_*" rc.conf(5) variables
228 for per-jail configuration are automatically converted to
229 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
230 This is transparently backward compatible. See below about some
231 incompatibilities and rc.conf(5) manual page for more details.
233 These variables are now deprecated in favor of jail(8) configuration
234 file. One can use "rc.d/jail config <jname>" command to generate
235 a jail(8) configuration file in /var/run/jail.<jname>.conf without
236 running the jail(8) utility. The default pathname of the
237 configuration file is /etc/jail.conf and can be specified by
238 using $jail_conf or $jail_<jname>_conf variables.
240 Please note that jail_devfs_ruleset accepts an integer at
241 this moment. Please consider to rewrite the ruleset name
245 BIND has been removed from the base system. If all you need
246 is a local resolver, simply enable and start the local_unbound
247 service instead. Otherwise, several versions of BIND are
248 available in the ports tree. The dns/bind99 port is one example.
250 With this change, nslookup(1) and dig(1) are no longer in the base
251 system. Users should instead use host(1) and drill(1) which are
252 in the base system. Alternatively, nslookup and dig can
253 be obtained by installing the dns/bind-tools port.
256 With the addition of unbound(8), a new unbound user is now
257 required during installworld. "mergemaster -p" can be used to
258 add the user prior to installworld, as documented in the handbook.
261 OpenSSH is now built with DNSSEC support, and will by default
262 silently trust signed SSHFP records. This can be controlled with
263 the VerifyHostKeyDNS client configuration setting. DNSSEC support
264 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
267 The GNU Compiler Collection and C++ standard library (libstdc++)
268 are no longer built by default on platforms where clang is the system
269 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
273 The PROCDESC kernel option is now part of the GENERIC kernel
274 configuration and is required for the rwhod(8) to work.
275 If you are using custom kernel configuration, you should include
279 The API and ABI related to the Capsicum framework was modified
280 in backward incompatible way. The userland libraries and programs
281 have to be recompiled to work with the new kernel. This includes the
282 following libraries and programs, but the whole buildworld is
283 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
284 kdump, procstat, rwho, rwhod, uniq.
287 AES-NI intrinsic support has been added to gcc. The AES-NI module
288 has been updated to use this support. A new gcc is required to build
289 the aesni module on both i386 and amd64.
292 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
293 Thus "device padlock_rng" and "device rdrand_rng" should be
294 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
297 WITH_ICONV has been split into two feature sets. WITH_ICONV now
298 enables just the iconv* functionality and is now on by default.
299 WITH_LIBICONV_COMPAT enables the libiconv api and link time
300 compatability. Set WITHOUT_ICONV to build the old way.
301 If you have been using WITH_ICONV before, you will very likely
302 need to turn on WITH_LIBICONV_COMPAT.
305 INVARIANTS option now enables DEBUG for code with OpenSolaris and
306 Illumos origin, including ZFS. If you have INVARIANTS in your
307 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
309 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
310 locks if WITNESS option was set. Because that generated a lot of
311 witness(9) reports and all of them were believed to be false
312 positives, this is no longer done. New option OPENSOLARIS_WITNESS
313 can be used to achieve the previous behavior.
316 Timer values in IPv6 data structures now use time_uptime instead
317 of time_second. Although this is not a user-visible functional
318 change, userland utilities which directly use them---ndp(8),
319 rtadvd(8), and rtsold(8) in the base system---need to be updated
323 find -delete can now delete the pathnames given as arguments,
324 instead of only files found below them or if the pathname did
325 not contain any slashes. Formerly, the following error message
328 find: -delete: <path>: relative path potentially not safe
330 Deleting the pathnames given as arguments can be prevented
331 without error messages using -mindepth 1 or by changing
332 directory and passing "." as argument to find. This works in the
333 old as well as the new version of find.
336 Behavior of devfs rules path matching has been changed.
337 Pattern is now always matched against fully qualified devfs
338 path and slash characters must be explicitly matched by
339 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
340 subdirectories must be reviewed.
343 The default ARM ABI has changed to the ARM EABI. The old ABI is
344 incompatible with the ARM EABI and all programs and modules will
345 need to be rebuilt to work with a new kernel.
347 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
349 NOTE: Support for the old ABI will be removed in the future and
350 users are advised to upgrade.
353 pkg_install has been disconnected from the build if you really need it
354 you should add WITH_PKGTOOLS in your src.conf(5).
357 Most of network statistics structures were changed to be able
358 keep 64-bits counters. Thus all tools, that work with networking
359 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
362 Fix targets that run multiple make's to use && rather than ;
363 so that subsequent steps depend on success of previous.
365 NOTE: if building 'universe' with -j* on stable/8 or stable/9
366 it would be better to start the build using bmake, to avoid
367 overloading the machine.
370 Fix a bug that allowed a tracing process (e.g. gdb) to write
371 to a memory-mapped file in the traced process's address space
372 even if neither the traced process nor the tracing process had
373 write access to that file.
376 CVS has been removed from the base system. An exact copy
377 of the code is available from the devel/cvs port.
380 Some people report the following error after the switch to bmake:
382 make: illegal option -- J
383 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
385 *** [buildworld] Error code 2
387 this likely due to an old instance of make in
388 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
389 which src/Makefile will use that blindly, if it exists, so if
390 you see the above error:
392 rm -rf `make -V MAKEPATH`
397 Use bmake by default.
398 Whereas before one could choose to build with bmake via
399 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
400 make. The goal is to remove these knobs for 10-RELEASE.
402 It is worth noting that bmake (like gmake) treats the command
403 line as the unit of failure, rather than statements within the
404 command line. Thus '(cd some/where && dosomething)' is safer
405 than 'cd some/where; dosomething'. The '()' allows consistent
406 behavior in parallel build.
409 Fix a bug that allows NFS clients to issue READDIR on files.
412 The WITHOUT_IDEA option has been removed because
413 the IDEA patent expired.
416 The sysctl which controls TRIM support under ZFS has been renamed
417 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
421 The mergemaster command now uses the default MAKEOBJDIRPREFIX
422 rather than creating it's own in the temporary directory in
423 order allow access to bootstrapped versions of tools such as
424 install and mtree. When upgrading from version of FreeBSD where
425 the install command does not support -l, you will need to
426 install a new mergemaster command if mergemaster -p is required.
427 This can be accomplished with the command (cd src/usr.sbin/mergemaster
431 Legacy ATA stack, disabled and replaced by new CAM-based one since
432 FreeBSD 9.0, completely removed from the sources. Kernel modules
433 atadisk and atapi*, user-level tools atacontrol and burncd are
434 removed. Kernel option `options ATA_CAM` is now permanently enabled
438 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
439 and socketpair(2). Software, in particular Kerberos, may
440 automatically detect and use these during building. The resulting
441 binaries will not work on older kernels.
444 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
445 information, see the respective 20130304 entry).
448 Recent commits to callout(9) changed the size of struct callout,
449 so the KBI is probably heavily disturbed. Also, some functions
450 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
451 by macros. Every kernel module using it won't load, so rebuild
454 The ctl device has been re-enabled in GENERIC for i386 and amd64,
455 but does not initialize by default (because of the new CTL_DISABLE
456 option) to save memory. To re-enable it, remove the CTL_DISABLE
457 option from the kernel config file or set kern.cam.ctl.disable=0
458 in /boot/loader.conf.
461 The ctl device has been disabled in GENERIC for i386 and amd64.
462 This was done due to the extra memory being allocated at system
463 initialisation time by the ctl driver which was only used if
464 a CAM target device was created. This makes a FreeBSD system
465 unusable on 128MB or less of RAM.
468 A new compression method (lz4) has been merged to -HEAD. Please
469 refer to zpool-features(7) for more information.
471 Please refer to the "ZFS notes" section of this file for information
472 on upgrading boot ZFS pools.
475 A BSD-licensed patch(1) variant has been added and is installed
476 as bsdpatch, being the GNU version the default patch.
477 To inverse the logic and use the BSD-licensed one as default,
478 while having the GNU version installed as gnupatch, rebuild
479 and install world with the WITH_BSD_PATCH knob set.
482 Due to the use of the new -l option to install(1) during build
483 and install, you must take care not to directly set the INSTALL
484 make variable in your /etc/make.conf, /etc/src.conf, or on the
485 command line. If you wish to use the -C flag for all installs
486 you may be able to add INSTALL+=-C to /etc/make.conf or
490 The install(1) option -M has changed meaning and now takes an
491 argument that is a file or path to append logs to. In the
492 unlikely event that -M was the last option on the command line
493 and the command line contained at least two files and a target
494 directory the first file will have logs appended to it. The -M
495 option served little practical purpose in the last decade so its
496 use is expected to be extremely rare.
499 After switching to Clang as the default compiler some users of ZFS
500 on i386 systems started to experience stack overflow kernel panics.
501 Please consider using 'options KSTACK_PAGES=4' in such configurations.
504 GEOM_LABEL now mangles label names read from file system metadata.
505 Mangling affect labels containing spaces, non-printable characters,
506 '%' or '"'. Device names in /etc/fstab and other places may need to
510 By default, only the 10 most recent kernel dumps will be saved. To
511 restore the previous behaviour (no limit on the number of kernel dumps
512 stored in the dump directory) add the following line to /etc/rc.conf:
517 With the addition of auditdistd(8), a new auditdistd user is now
518 required during installworld. "mergemaster -p" can be used to
519 add the user prior to installworld, as documented in the handbook.
522 The sin6_scope_id member variable in struct sockaddr_in6 is now
523 filled by the kernel before passing the structure to the userland via
524 sysctl or routing socket. This means the KAME-specific embedded scope
525 id in sin6_addr.s6_addr[2] is always cleared in userland application.
526 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
527 __FreeBSD_version is bumped to 1000025.
530 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
531 This means that the world and kernel will be compiled with clang
532 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
533 and /usr/bin/cpp. To disable this behavior and revert to building
534 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
535 of current may need to bootstrap WITHOUT_CLANG first if the clang
536 build fails (its compatibility window doesn't extend to the 9 stable
540 The IPFIREWALL_FORWARD kernel option has been removed. Its
541 functionality now turned on by default.
544 The ZERO_COPY_SOCKET kernel option has been removed and
545 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
546 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
547 mechanism which is not safe and may result in kernel crashes.
548 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
549 driver supports disposeable external page sized mbuf storage.
550 Proper replacements for both zero-copy mechanisms are under
551 consideration and will eventually lead to complete removal
552 of the two kernel options.
555 The IPv4 network stack has been converted to network byte
556 order. The following modules need to be recompiled together
557 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
558 pf(4), ipfw(4), ng_ipfw(4), stf(4).
561 Support for non-MPSAFE filesystems was removed from VFS. The
562 VFS_VERSION was bumped, all filesystem modules shall be
566 All the non-MPSAFE filesystems have been disconnected from
567 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
568 portalfs, smbfs, xfs.
571 The interface cloning API and ABI has changed. The following
572 modules need to be recompiled together with kernel:
573 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
574 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
575 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
578 The sdhci driver was split in two parts: sdhci (generic SD Host
579 Controller logic) and sdhci_pci (actual hardware driver).
580 No kernel config modifications are required, but if you
581 load sdhc as a module you must switch to sdhci_pci instead.
584 Import the FUSE kernel and userland support into base system.
587 The GNU sort(1) program has been removed since the BSD-licensed
588 sort(1) has been the default for quite some time and no serious
589 problems have been reported. The corresponding WITH_GNU_SORT
593 The pfil(9) API/ABI for AF_INET family has been changed. Packet
594 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
598 The net80211(4) ABI has been changed to allow for improved driver
599 PS-POLL and power-save support. All wireless drivers need to be
600 recompiled to work with the new kernel.
603 The random(4) support for the VIA hardware random number
604 generator (`PADLOCK') is no longer enabled unconditionally.
605 Add the padlock_rng device in the custom kernel config if
606 needed. The GENERIC kernels on i386 and amd64 do include the
607 device, so the change only affects the custom kernel
611 The pf(4) packet filter ABI has been changed. pfctl(8) and
612 snmp_pf module need to be recompiled to work with new kernel.
615 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
616 to -HEAD. Pools that have empty_bpobj in active state can not be
617 imported read-write with ZFS implementations that do not support
618 this feature. For more information read the zpool-features(5)
622 The sparc64 ZFS loader has been changed to no longer try to auto-
623 detect ZFS providers based on diskN aliases but now requires these
624 to be explicitly listed in the OFW boot-device environment variable.
627 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
628 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
629 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
632 The following sysctls and tunables have been renamed for consistency
633 with other variables:
634 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
635 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
638 The sort utility has been replaced with BSD sort. For now, GNU sort
639 is also available as "gnusort" or the default can be set back to
640 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
641 installed as "bsdsort".
644 A new version of ZFS (pool version 5000) has been merged to -HEAD.
645 Starting with this version the old system of ZFS pool versioning
646 is superseded by "feature flags". This concept enables forward
647 compatibility against certain future changes in functionality of ZFS
648 pools. The first read-only compatible "feature flag" for ZFS pools
649 is named "com.delphix:async_destroy". For more information
650 read the new zpool-features(5) manual page.
651 Please refer to the "ZFS notes" section of this file for information
652 on upgrading boot ZFS pools.
655 The malloc(3) implementation embedded in libc now uses sources imported
656 as contrib/jemalloc. The most disruptive API change is to
657 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
658 delete it prior to installworld, and optionally re-create it using the
659 new format after rebooting. See malloc.conf(5) for details
660 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
664 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
665 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
666 now spelled mips. This is to aid compatibility with third-party
667 software that expects this naming scheme in uname(3). Little-endian
668 settings are unchanged. If you are updating a big-endian mips64 machine
669 from before this change, you may need to set MACHINE_ARCH=mips64 in
670 your environment before the new build system will recognize your machine.
673 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
677 Now unix domain sockets behave "as expected" on nullfs(5). Previously
678 nullfs(5) did not pass through all behaviours to the underlying layer,
679 as a result if we bound to a socket on the lower layer we could connect
680 only to the lower path; if we bound to the upper layer we could connect
681 only to the upper path. The new behavior is one can connect to both the
682 lower and the upper paths regardless what layer path one binds to.
685 The getifaddrs upgrade path broken with 20111215 has been restored.
686 If you have upgraded in between 20111215 and 20120209 you need to
687 recompile libc again with your kernel. You still need to recompile
688 world to be able to configure CARP but this restriction already
692 The set_rcvar() function has been removed from /etc/rc.subr. All
693 base and ports rc.d scripts have been updated, so if you have a
694 port installed with a script in /usr/local/etc/rc.d you can either
695 hand-edit the rcvar= line, or reinstall the port.
697 An easy way to handle the mass-update of /etc/rc.d:
698 rm /etc/rc.d/* && mergemaster -i
701 panic(9) now stops other CPUs in the SMP systems, disables interrupts
702 on the current CPU and prevents other threads from running.
703 This behavior can be reverted using the kern.stop_scheduler_on_panic
705 The new behavior can be incompatible with kern.sync_on_panic.
708 The carp(4) facility has been changed significantly. Configuration
709 of the CARP protocol via ifconfig(8) has changed, as well as format
710 of CARP events submitted to devd(8) has changed. See manual pages
711 for more information. The arpbalance feature of carp(4) is currently
712 not supported anymore.
714 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
715 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
716 need to be recompiled.
719 The acpi_wmi(4) status device /dev/wmistat has been renamed to
723 The option VFS_ALLOW_NONMPSAFE option has been added in order to
724 explicitely support non-MPSAFE filesystems.
725 It is on by default for all supported platform at this present
729 The broken amd(4) driver has been replaced with esp(4) in the amd64,
730 i386 and pc98 GENERIC kernel configuration files.
733 sysinstall has been removed
736 The stable/9 branch created in subversion. This corresponds to the
737 RELENG_9 branch in CVS.
740 This commit modifies vfs_register() so that it uses a hash
741 calculation to set vfc_typenum, which is enabled by default.
742 The first time a system is booted after this change, the
743 vfc_typenum values will change for all file systems. The
744 main effect of this is a change to the NFS server file handles
745 for file systems that use vfc_typenum in their fsid, such as ZFS.
746 It will, however, prevent vfc_typenum from changing when file
747 systems are loaded in a different order for subsequent reboots.
748 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
749 until you are ready to remount all NFS clients after a reboot.
752 Bump the shared library version numbers for libraries that
753 do not use symbol versioning, have changed the ABI compared
754 to stable/8 and which shared library version was not bumped.
755 Done as part of 9.0-RELEASE cycle.
758 During the merge of Capsicum features, the fget(9) KPI was modified.
759 This may require the rebuilding of out-of-tree device drivers --
760 issues have been reported specifically with the nVidia device driver.
761 __FreeBSD_version is bumped to 900041.
763 Also, there is a period between 20110811 and 20110814 where the
764 special devices /dev/{stdin,stdout,stderr} did not work correctly.
765 Building world from a kernel during that window may not work.
768 The packet filter (pf) code has been updated to OpenBSD 4.5.
769 You need to update userland tools to be in sync with kernel.
770 This update breaks backward compatibility with earlier pfsync(4)
771 versions. Care must be taken when updating redundant firewall setups.
774 The following sysctls and tunables are retired on x86 platforms:
776 machdep.hlt_logical_cpus
777 The following sysctl is retired:
778 machdep.hyperthreading_allowed
779 The sysctls were supposed to provide a way to dynamically offline and
780 online selected CPUs on x86 platforms, but the implementation has not
781 been reliable especially with SCHED_ULE scheduler.
782 machdep.hyperthreading_allowed tunable is still available to ignore
783 hyperthreading CPUs at OS level.
784 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
785 where X is an APIC ID of a CPU. Be advised, though, that disabling
786 CPUs in non-uniform fashion will result in non-uniform topology and
787 may lead to sub-optimal system performance with SCHED_ULE, which is
791 cpumask_t type is retired and cpuset_t is used in order to describe
795 Changes to ifconfig(8) for dynamic address family detection mandate
796 that you are running a kernel of 20110525 or later. Make sure to
797 follow the update procedure to boot a new kernel before installing
801 Support for sun4v architecture is officially dropped
804 Several KPI breaking changes have been committed to the mii(4) layer,
805 the PHY drivers and consequently some Ethernet drivers using mii(4).
806 This means that miibus.ko and the modules of the affected Ethernet
807 drivers need to be recompiled.
809 Note to kernel developers: Given that the OUI bit reversion problem
810 was fixed as part of these changes all mii(4) commits related to OUIs,
811 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
812 handling, no longer can be merged verbatim to stable/8 and previous
816 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
817 into their kernel configurations along with 'device pci'.
820 The default NFS client is now the new NFS client, so fstype "newnfs"
821 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
822 Although mounts via fstype "nfs" will usually work without userland
823 changes, it is recommended that the mount(8) and mount_nfs(8)
824 commands be rebuilt from sources and that a link to mount_nfs called
825 mount_oldnfs be created. The new client is compiled into the
826 kernel with "options NFSCL" and this is needed for diskless root
827 file systems. The GENERIC kernel configs have been changed to use
828 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
829 To use the regular/old client, you can "mount -t oldnfs ...". For
830 a diskless root file system, you must also include a line like:
832 vfs.root.mountfrom="oldnfs:"
834 in the boot/loader.conf on the root fs on the NFS server to make
835 a diskless root fs use the old client.
838 The GENERIC kernels for all architectures now default to the new
839 CAM-based ATA stack. It means that all legacy ATA drivers were
840 removed and replaced by respective CAM drivers. If you are using
841 ATA device names in /etc/fstab or other places, make sure to update
842 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
843 where 'Y's are the sequential numbers starting from zero for each type
844 in order of detection, unless configured otherwise with tunables,
845 see cam(4)). There will be symbolic links created in /dev/ to map
846 old adX devices to the respective adaY. They should provide basic
847 compatibility for file systems mounting in most cases, but they do
848 not support old user-level APIs and do not have respective providers
849 in GEOM. Consider using updated management tools with new device names.
851 It is possible to load devices ahci, ata, siis and mvs as modules,
852 but option ATA_CAM should remain in kernel configuration to make ata
853 module work as CAM driver supporting legacy ATA controllers. Device ata
854 still can be used in modular fashion (atacore + ...). Modules atadisk
855 and atapi* are not used and won't affect operation in ATA_CAM mode.
856 Note that to use CAM-based ATA kernel should include CAM devices
857 scbus, pass, da (or explicitly ada), cd and optionally others. All of
858 them are parts of the cam module.
860 ataraid(4) functionality is now supported by the RAID GEOM class.
861 To use it you can load geom_raid kernel module and use graid(8) tool
862 for management. Instead of /dev/arX device names, use /dev/raid/rX.
864 No kernel config options or code have been removed, so if a problem
865 arises, please report it and optionally revert to the old ATA stack.
866 In order to do it you can remove from the kernel config:
871 , and instead add back:
872 device atadisk # ATA disk drives
873 device ataraid # ATA RAID drives
874 device atapicd # ATAPI CDROM drives
875 device atapifd # ATAPI floppy drives
876 device atapist # ATAPI tape drives
879 The default NFS server has been changed to the new server, which
880 was referred to as the experimental server. If you need to switch
881 back to the old NFS server, you must now put the "-o" option on
882 both the mountd and nfsd commands. This can be done using the
883 mountd_flags and nfs_server_flags rc.conf variables until an
884 update to the rc scripts is committed, which is coming soon.
887 The GNU Objective-C runtime library (libobjc), and other Objective-C
888 related components have been removed from the base system. If you
889 require an Objective-C library, please use one of the available ports.
892 ath(4) has been split into bus- and device- modules. if_ath contains
893 the HAL, the TX rate control and the network device code. if_ath_pci
894 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
895 contains the AHB glue. Users need to load both if_ath_pci and if_ath
896 in order to use ath on everything else.
898 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
899 need to load if_ath and if_ath_pci for ath(4) operation.
902 As part of the replacement of sysinstall, the process of building
903 release media has changed significantly. For details, please re-read
904 release(7), which has been updated to reflect the new build process.
907 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
908 is the last available version under GPLv2. It brings a number of new
909 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
910 4.1 and SSE 4.2), better support for powerpc64, a number of new
911 directives, and lots of other small improvements. See the ChangeLog
912 file in contrib/binutils for the full details.
915 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
916 compliant, and will now use half of hash for authentication.
917 This will break interoperability with all stacks (including all
918 actual FreeBSD versions) who implement
919 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
921 The only workaround with such peers is to use another HMAC
922 algorithm for IPsec ("phase 2") authentication.
925 Remove the uio_yield prototype and symbol. This function has
926 been misnamed since it was introduced and should not be
927 globally exposed with this name. The equivalent functionality
928 is now available using kern_yield(curthread->td_user_pri).
929 The function remains undocumented.
932 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
933 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
934 for scalar sysctls is defined but disabled. Code that needs
935 UQUAD to pass the type checking that must compile on older
936 systems where the define is not present can check against
937 __FreeBSD_version >= 900030.
939 The system dialog(1) has been replaced with a new version previously
940 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
941 with the previous version, but the libdialog associated with it has
942 a largely incompatible API. As such, the original version of libdialog
943 will be kept temporarily as libodialog, until its base system consumers
944 are replaced or updated. Bump __FreeBSD_version to 900030.
947 If you are trying to run make universe on a -stable system, and you get
948 the following warning:
949 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
950 unknown. config(8) likely too old."
951 or something similar to it, then you must upgrade your -stable system
952 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
953 stable/8) or build the config from the latest stable/8 branch and
954 install it on your system.
956 Prior to this date, building a current universe on 8-stable system from
957 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
958 error in the first kernel build phase. A new config on those old
959 systems will fix that problem for older versions of -current.
962 The TCP stack has been modified to allow Khelp modules to interact with
963 it via helper hook points and store per-connection data in the TCP
964 control block. Bump __FreeBSD_version to 900029. User space tools that
965 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
969 Generic IEEE 802.3 annex 31B full duplex flow control support has been
970 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
971 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
972 to take advantage of it instead of using custom implementations. This
973 means that these drivers now no longer unconditionally advertise
974 support for flow control but only do so if flow control is a selected
975 media option. This was implemented in the generic support that way in
976 order to allow flow control to be switched on and off via ifconfig(8)
977 with the PHY specific default to typically off in order to protect
978 from unwanted effects. Consequently, if you used flow control with
979 one of the above mentioned drivers you now need to explicitly enable
981 ifconfig bge0 media auto mediaopt flowcontrol
983 Along with the above mentioned changes generic support for setting
984 1000baseT master mode also has been added and brgphy(4), ciphy(4),
985 e1000phy(4) as well as ip1000phy(4) have been converted to take
986 advantage of it. This means that these drivers now no longer take the
987 link0 parameter for selecting master mode but the master media option
988 has to be used instead, for example like in the following:
989 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
991 Selection of master mode now is also available with all other PHY
992 drivers supporting 1000baseT.
995 The TCP stack has received a significant update to add support for
996 modularised congestion control and generally improve the clarity of
997 congestion control decisions. Bump __FreeBSD_version to 900025. User
998 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
999 sockstat) need to be recompiled.
1002 The man(1) utility has been replaced by a new version that no longer
1003 uses /etc/manpath.config. Please consult man.conf(5) for how to
1004 migrate local entries to the new format.
1007 The copyright strings printed by login(1) and sshd(8) at the time of a
1008 new connection have been removed to follow other operating systems and
1012 A workaround for a fixed ld bug has been removed in kernel code,
1013 so make sure that your system ld is built from sources after
1014 revision 210245 from 2010-07-19 (r211583 if building head kernel
1015 on stable/8, r211584 for stable/7; both from 2010-08-21).
1016 A symptom of incorrect ld version is different addresses for
1017 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1020 The $ipv6_prefer variable in rc.conf(5) has been split into
1021 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1023 The $ip6addrctl_policy is a variable to choose a pre-defined
1024 address selection policy set by ip6addrctl(8). A value
1025 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1028 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1029 flag (see an entry of 20090926) is set on an interface with no
1030 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1031 security reason. If you want IPv6 link-local address on all
1032 interfaces by default, set this to "YES".
1034 The old ipv6_prefer="YES" is equivalent to
1035 ipv6_activate_all_interfaces="YES" and
1036 ip6addrctl_policy="ipv6_prefer".
1039 DTrace has grown support for userland tracing. Due to this, DTrace is
1040 now i386 and amd64 only.
1041 dtruss(1) is now installed by default on those systems and a new
1042 kernel module is needed for userland tracing: fasttrap.
1043 No changes to your kernel config file are necessary to enable
1044 userland tracing, but you might consider adding 'STRIP=' and
1045 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1046 to have informative userland stack traces in DTrace (ustack).
1049 The acpi_aiboost(4) driver has been removed in favor of the new
1050 aibs(4) driver. You should update your kernel configuration file.
1053 BSD grep has been imported to the base system and it is built by
1054 default. It is completely BSD licensed, highly GNU-compatible, uses
1055 less memory than its GNU counterpart and has a small codebase.
1056 However, it is slower than its GNU counterpart, which is mostly
1057 noticeable for larger searches, for smaller ones it is measurable
1058 but not significant. The reason is complex, the most important factor
1059 is that we lack a modern and efficient regex library and GNU
1060 overcomes this by optimizing the searches internally. Future work
1061 on improving the regex performance is planned, for the meantime,
1062 users that need better performance, can build GNU grep instead by
1063 setting the WITH_GNU_GREP knob.
1066 Due to the import of powerpc64 support, all existing powerpc kernel
1067 configuration files must be updated with a machine directive like this:
1068 machine powerpc powerpc
1070 In addition, an updated config(8) is required to build powerpc kernels
1074 A new version of ZFS (version 15) has been merged to -HEAD.
1075 This version uses a python library for the following subcommands:
1076 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1077 For full functionality of these commands the following port must
1078 be installed: sysutils/py-zfs
1081 'vm_page's are now hashed by physical address to an array of mutexes.
1082 Currently this is only used to serialize access to hold_count. Over
1083 time the page queue mutex will be peeled away. This changes the size
1084 of pmap on every architecture. And requires all callers of vm_page_hold
1085 and vm_page_unhold to be updated.
1088 WITH_CTF can now be specified in src.conf (not recommended, there
1089 are some problems with static executables), make.conf (would also
1090 affect ports which do not use GNU make and do not override the
1091 compile targets) or in the kernel config (via "makeoptions
1093 When WITH_CTF was specified there before this was silently ignored,
1094 so make sure that WITH_CTF is not used in places which could lead
1095 to unwanted behavior.
1098 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1099 to allow 32-bit compatibility on non-x86 platforms. All kernel
1100 configurations on amd64 and ia64 platforms using these options must
1101 be modified accordingly.
1104 The utmp user accounting database has been replaced with utmpx,
1105 the user accounting interface standardized by POSIX.
1106 Unfortunately the semantics of utmp and utmpx don't match,
1107 making it practically impossible to support both interfaces.
1108 The user accounting database is used by tools like finger(1),
1109 last(1), talk(1), w(1) and ac(8).
1111 All applications in the base system use utmpx. This means only
1112 local binaries (e.g. from the ports tree) may still use these
1113 utmp database files. These applications must be rebuilt to make
1116 After the system has been upgraded, it is safe to remove the old
1117 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1118 assuming their contents is of no importance anymore. Old wtmp
1119 databases can only be used by last(1) and ac(8) after they have
1120 been converted to the new format using wtmpcvt(1).
1123 Introduce the kernel thread "deadlock resolver" (which can be enabled
1124 via the DEADLKRES option, see NOTES for more details) and the
1125 sleepq_type() function for sleepqueues.
1128 The rc.firewall and rc.firewall6 were unified, and
1129 rc.firewall6 and rc.d/ip6fw were removed.
1130 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1131 variables are obsoleted. Instead, the following new rc
1132 variables are added to rc.d/ipfw:
1134 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1135 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1136 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1138 The meanings correspond to the relevant IPv4 variables.
1144 The default terminal emulation for syscons(4) has been changed
1145 from cons25 to xterm on all platforms except pc98. This means
1146 that the /etc/ttys file needs to be updated to ensure correct
1147 operation of applications on the console.
1149 The terminal emulation style can be toggled per window by using
1150 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1151 options can be used to change the compile-time default back to
1154 To prevent graphical artifacts, make sure the TERM environment
1155 variable is set to match the terminal emulation that is being
1156 performed by syscons(4).
1159 The layout of the structure ieee80211req_scan_result has changed.
1160 Applications that require wireless scan results (e.g. ifconfig(8))
1161 from net80211 need to be recompiled.
1163 Applications such as wpa_supplicant(8) may require a full world
1164 build without using NO_CLEAN in order to get synchronized with the
1168 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1169 There's one kernel module for each firmware. Adding "device iwnfw"
1170 to the kernel configuration file means including all three firmware
1171 images inside the kernel. If you want to include just the one for
1172 your wireless card, use the devices iwn4965fw, iwn5000fw or
1176 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1177 into rc.d/netif. The changes are the following:
1179 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1180 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1181 Note that both variables need the "inet6" keyword at the head.
1183 Do not set $ipv6_network_interfaces manually if you do not
1184 understand what you are doing. It is not needed in most cases.
1186 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1189 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1190 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1192 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1193 all configured interfaces have "inet6 accept_rtadv" in the
1194 $ifconfig_IF_ipv6. These are for backward compatibility.
1196 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1197 functionality of interfaces with no corresponding
1198 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1199 and the default address selection policy of ip6addrctl(8)
1200 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1201 Note that if you want to configure IPv6 functionality on the
1202 disabled interfaces after boot, first you need to clear the flag by
1203 using ifconfig(8) like:
1205 ifconfig em0 inet6 -ifdisabled
1207 If YES, the default address selection policy is set as
1210 The default value of $ipv6_prefer is NO.
1212 4. If your system need to receive Router Advertisement messages,
1213 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1214 scripts automatically invoke rtsol(8) when the interface becomes
1215 UP. The Router Advertisement messages are used for SLAAC
1216 (State-Less Address AutoConfiguration).
1219 802.11s D3.03 support was committed. This is incompatible with the
1220 previous code, which was based on D3.0.
1223 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1224 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1225 control whether accepting Router Advertisement messages or not.
1226 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1227 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1228 The ifconfig(8) utility now supports these flags.
1231 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1232 mount(8) and -a option for df(1) to see them.
1235 The old tunable hw.bus.devctl_disable has been superseded by
1236 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1237 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1241 Remove the option STOP_NMI. The default action is now to use NMI only
1242 for KDB via the newly introduced function stop_cpus_hard() and
1243 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1246 The stable/8 branch created in subversion. This corresponds to the
1247 RELENG_8 branch in CVS.
1250 Bump the shared library version numbers for all libraries that do not
1251 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1252 __FreeBSD_version to 800105.
1255 Due to changes in the implementation of virtual network stack support,
1256 all network-related kernel modules must be recompiled. As this change
1257 breaks the ABI, bump __FreeBSD_version to 800104.
1260 The TOE interface to the TCP syncache has been modified to remove
1261 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1262 The cxgb driver is the only TOE consumer affected by this change, and
1263 needs to be recompiled along with the kernel. As this change breaks
1264 the ABI, bump __FreeBSD_version to 800103.
1267 Padding has been added to struct tcpcb, sackhint and tcpstat in
1268 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1269 maintaining the ABI. However, this change breaks the ABI, so bump
1270 __FreeBSD_version to 800102. User space tools that rely on the size of
1271 any of these structs (e.g. sockstat) need to be recompiled.
1274 The NFS_LEGACYRPC option has been removed along with the old kernel
1275 RPC implementation that this option selected. Kernel configurations
1276 may need to be adjusted.
1279 The network interface device nodes at /dev/net/<interface> have been
1280 removed. All ioctl operations can be performed the normal way using
1281 routing sockets. The kqueue functionality can generally be replaced
1282 with routing sockets.
1285 The documentation from the FreeBSD Documentation Project (Handbook,
1286 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1287 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1290 The ABI of various structures related to the SYSV IPC API have been
1291 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1292 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1296 Layout of struct vnet has changed as routing related variables were
1297 moved to their own Vimage module. Modules need to be recompiled. Bump
1298 __FreeBSD_version to 800099.
1301 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1302 respectively. As long as no more than 16 groups per process are used,
1303 no changes should be visible. When more than 16 groups are used, old
1304 binaries may fail if they call getgroups() or getgrouplist() with
1305 statically sized storage. Recompiling will work around this, but
1306 applications should be modified to use dynamically allocated storage
1307 for group arrays as POSIX.1-2008 does not cap an implementation's
1308 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1310 NFS and portalfs mounts may also be affected as the list of groups is
1311 truncated to 16. Users of NFS who use more than 16 groups, should
1312 take care that negative group permissions are not used on the exported
1313 file systems as they will not be reliable unless a GSSAPI based
1314 authentication method is used.
1317 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1318 option compiles in the support for adaptive spinning for lockmgrs
1319 which want to enable it. The lockinit() function now accepts the flag
1320 LK_ADAPTIVE in order to make the lock object subject to adaptive
1321 spinning when both held in write and read mode.
1324 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1325 changed. User applications that use this ioctl need to be rebuilt.
1328 The layout of struct thread has changed. Kernel and modules need to
1332 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1333 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1336 window(1) has been removed from the base system. It can now be
1337 installed from ports. The port is called misc/window.
1340 The way we are storing and accessing `routing table' entries has
1341 changed. Programs reading the FIB, like netstat, need to be
1345 A new netisr implementation has been added for FreeBSD 8. Network
1346 file system modules, such as igmp, ipdivert, and others, should be
1348 Bump __FreeBSD_version to 800096.
1351 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1355 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1356 Bump __FreeBSD_version to 800094.
1359 Add mnt_xflag field to 'struct mount'. File system modules need to be
1361 Bump __FreeBSD_version to 800093.
1364 The compiling option ADAPTIVE_SX has been retired while it has been
1365 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1366 The KPI for sx_init_flags() changes as accepting flags:
1367 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1368 been introduced in order to handle the reversed logic.
1369 Bump __FreeBSD_version to 800092.
1372 Add support for hierarchical jails. Remove global securelevel.
1373 Bump __FreeBSD_version to 800091.
1376 The layout of struct vnet_net has changed, therefore modules
1378 Bump __FreeBSD_version to 800090.
1381 The newly imported zic(8) produces a new format in the output. Please
1382 run tzsetup(8) to install the newly created data to /etc/localtime.
1385 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1386 hw.usb.* and is now consistent again with previous releases.
1389 802.11 monitor mode support was revised and driver api's were changed.
1390 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1391 of DLT_IEEE802_11. No user-visible data structures were changed but
1392 applications that use DLT_IEEE802_11 may require changes.
1393 Bump __FreeBSD_version to 800088.
1396 The layout of the following structs has changed: sysctl_oid,
1397 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1398 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1399 panics may be experienced. World rebuild is required for
1400 correctly checking networking state from userland.
1401 Bump __FreeBSD_version to 800085.
1404 MLDv2 and Source-Specific Multicast (SSM) have been merged
1405 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1406 The implementation of SSM within FreeBSD's IPv6 stack closely
1407 follows the IPv4 implementation.
1409 For kernel developers:
1411 * The most important changes are that the ip6_output() and
1412 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1413 and this lock has been downgraded to a non-recursive mutex.
1415 * As with the changes to the IPv4 stack to support SSM, filtering
1416 of inbound multicast traffic must now be performed by transport
1417 protocols within the IPv6 stack. This does not apply to TCP and
1418 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1420 * The KPIs used by IPv6 multicast are similar to those used by
1421 the IPv4 stack, with the following differences:
1422 * im6o_mc_filter() is analogous to imo_multicast_filter().
1423 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1424 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1425 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1426 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1427 for MLDv1 have an additional 'timer' argument which is used to
1428 jitter the initial membership report for the solicited-node
1429 multicast membership on-link.
1430 * This is not strictly needed for MLDv2, which already jitters
1431 its report transmissions. However, the 'timer' argument is
1432 preserved in case MLDv1 is active on the interface.
1434 * The KAME linked-list based IPv6 membership implementation has
1435 been refactored to use a vector similar to that used by the IPv4
1437 Code which maintains a list of its own multicast memberships
1438 internally, e.g. carp, has been updated to reflect the new
1441 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1442 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1443 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1444 implementation constraint which needs to be addressed in HEAD.
1446 For application developers:
1448 * The changes are broadly similar to those made for the IPv4
1451 * The use of IPv4 and IPv6 multicast socket options on the same
1452 socket, using mapped addresses, HAS NOT been tested or supported.
1454 * There are a number of issues with the implementation of various
1455 IPv6 multicast APIs which need to be resolved in the API surface
1456 before the implementation is fully compatible with KAME userland
1457 use, and these are mostly to do with interface index treatment.
1459 * The literature available discusses the use of either the delta / ASM
1460 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1461 using setsourcefilter(3)/getsourcefilter(3). For more information
1462 please refer to RFC 3768, 'Socket Interface Extensions for
1463 Multicast Source Filters'.
1465 * Applications which use the published RFC 3678 APIs should be fine.
1467 For systems administrators:
1469 * The mtest(8) utility has been refactored to support IPv6, in
1470 addition to IPv4. Interface addresses are no longer accepted
1471 as arguments, their names must be used instead. The utility
1472 will map the interface name to its first IPv4 address as
1473 returned by getifaddrs(3).
1475 * The ifmcstat(8) utility has also been updated to print the MLDv2
1476 endpoint state and source filter lists via sysctl(3).
1478 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1479 loopback of IPv6 multicast datagrams by default; it defaults to 1
1480 to preserve the existing behaviour. Disabling multicast loopback is
1481 recommended for optimal system performance.
1483 * The IPv6 MROUTING code has been changed to examine this sysctl
1484 instead of attempting to perform a group lookup before looping
1485 back forwarded datagrams.
1487 Bump __FreeBSD_version to 800084.
1490 Implement low-level Bluetooth HCI API.
1491 Bump __FreeBSD_version to 800083.
1494 The layout of struct malloc_type, used by modules to register new
1495 memory allocation types, has changed. Most modules will need to
1496 be rebuilt or panics may be experienced.
1497 Bump __FreeBSD_version to 800081.
1500 Anticipate overflowing inp_flags - add inp_flags2.
1501 This changes most offsets in inpcb, so checking v4 connection
1502 state will require a world rebuild.
1503 Bump __FreeBSD_version to 800080.
1506 Add an llentry to struct route and struct route_in6. Modules
1507 embedding a struct route will need to be recompiled.
1508 Bump __FreeBSD_version to 800079.
1511 The size of rt_metrics_lite and by extension rtentry has changed.
1512 Networking administration apps will need to be recompiled.
1513 The route command now supports show as an alias for get, weighting
1514 of routes, sticky and nostick flags to alter the behavior of stateful
1516 Bump __FreeBSD_version to 800078.
1519 Do not use Giant for kbdmux(4) locking. This is wrong and
1520 apparently causing more problems than it solves. This will
1521 re-open the issue where interrupt handlers may race with
1522 kbdmux(4) in polling mode. Typical symptoms include (but
1523 not limited to) duplicated and/or missing characters when
1524 low level console functions (such as gets) are used while
1525 interrupts are enabled (for example geli password prompt,
1526 mountroot prompt etc.). Disabling kbdmux(4) may help.
1529 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1530 kernel modules referencing any of the above need to be recompiled.
1531 Bump __FreeBSD_version to 800075.
1534 GEOM_PART has become the default partition slicer for storage devices,
1535 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1536 introduces some changes:
1538 MSDOS/EBR: the devices created from MSDOS extended partition entries
1539 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1540 to devices with offset-based names. fstabs may need to be modified.
1542 BSD: the "geometry does not match label" warning is harmless in most
1543 cases but it points to problems in file system misalignment with
1544 disk geometry. The "c" partition is now implicit, covers the whole
1545 top-level drive and cannot be (mis)used by users.
1547 General: Kernel dumps are now not allowed to be written to devices
1548 whose partition types indicate they are meant to be used for file
1549 systems (or, in case of MSDOS partitions, as something else than
1552 Most of these changes date approximately from 200812.
1555 The uscanner(4) driver has been removed from the kernel. This follows
1556 Linux removing theirs in 2.6 and making libusb the default interface
1557 (supported by sane).
1560 The multicast forwarding code has been cleaned up. netstat(1)
1561 only relies on KVM now for printing bandwidth upcall meters.
1562 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1563 ip6_mroute_mod respectively. The config(5) options for statically
1564 compiling this code remain the same, i.e. 'options MROUTING'.
1567 Support for the IFF_NEEDSGIANT network interface flag has been
1568 removed, which means that non-MPSAFE network device drivers are no
1569 longer supported. In particular, if_ar, if_sr, and network device
1570 drivers from the old (legacy) USB stack can no longer be built or
1574 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1575 a bunch of new language catalog files have also been added.
1576 This means that some common libc messages are now localized and
1577 they depend on the LC_MESSAGES environmental variable.
1580 The k8temp(4) driver has been renamed to amdtemp(4) since
1581 support for Family 10 and Family 11 CPU families was added.
1584 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1585 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1587 For kernel developers, the most important changes are that the
1588 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1589 and this lock has been downgraded to a non-recursive mutex.
1591 Transport protocols (UDP, Raw IP) are now responsible for filtering
1592 inbound multicast traffic according to group membership and source
1593 filters. The imo_multicast_filter() KPI exists for this purpose.
1594 Transports which do not use multicast (SCTP, TCP) already reject
1595 multicast by default. Forwarding and receive performance may improve
1596 as a mutex acquisition is no longer needed in the ip_input()
1597 low-level input path. in_addmulti() and in_delmulti() are shimmed
1598 to new KPIs which exist to support SSM in-kernel.
1600 For application developers, it is recommended that loopback of
1601 multicast datagrams be disabled for best performance, as this
1602 will still cause the lock to be taken for each looped-back
1603 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1604 be tuned to 0 to disable loopback by default; it defaults to 1
1605 to preserve the existing behaviour.
1607 For systems administrators, to obtain best performance with
1608 multicast reception and multiple groups, it is always recommended
1609 that a card with a suitably precise hash filter is used. Hash
1610 collisions will still result in the lock being taken within the
1611 transport protocol input path to check group membership.
1613 If deploying FreeBSD in an environment with IGMP snooping switches,
1614 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1615 enabled; this forces 224.0.0.0/24 group membership to be announced
1618 The size of 'struct igmpstat' has changed; netstat needs to be
1619 recompiled to reflect this.
1620 Bump __FreeBSD_version to 800070.
1623 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1624 updated to use it. This requires a buildworld/installworld in order to
1625 update the library and dependencies (usbconfig, etc). Its advisable to
1626 rebuild all ports which uses libusb. More specific directions are given
1627 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1628 libusb are no longer required and can be removed.
1631 A workaround is committed to allow the creation of System V shared
1632 memory segment of size > 2 GB on the 64-bit architectures.
1633 Due to a limitation of the existing ABI, the shm_segsz member
1634 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1635 wrong for large segments. Note that limits must be explicitly
1636 raised to allow such segments to be created.
1639 The layout of struct ifnet has changed, requiring a rebuild of all
1640 network device driver modules.
1643 The /dev handling for the new USB stack has changed, a
1644 buildworld/installworld is required for libusb20.
1647 The new USB2 stack has now been permanently moved in and all kernel and
1648 module names reverted to their previous values (eg, usb, ehci, ohci,
1649 ums, ...). The old usb stack can be compiled in by prefixing the name
1650 with the letter 'o', the old usb modules have been removed.
1651 Updating entry 20090216 for xorg and 20090215 for libmap may still
1655 The rc.conf(5) option if_up_delay has been renamed to
1656 defaultroute_delay to better reflect its purpose. If you have
1657 customized this setting in /etc/rc.conf you need to update it to
1661 xorg 7.4 wants to configure its input devices via hald which does not
1662 yet work with USB2. If the keyboard/mouse does not work in xorg then
1664 Option "AllowEmptyInput" "off"
1665 to your ServerLayout section. This will cause X to use the configured
1666 kbd and mouse sections from your xorg.conf.
1669 The GENERIC kernels for all architectures now default to the new USB2
1670 stack. No kernel config options or code have been removed so if a
1671 problem arises please report it and optionally revert to the old USB
1672 stack. If you are loading USB kernel modules or have a custom kernel
1673 that includes GENERIC then ensure that usb names are also changed over,
1674 eg uftdi -> usb2_serial_ftdi.
1676 Older programs linked against the ports libusb 0.1 need to be
1677 redirected to the new stack's libusb20. /etc/libmap.conf can
1679 # Map old usb library to new one for usb2 stack
1680 libusb-0.1.so.8 libusb20.so.1
1683 All USB ethernet devices now attach as interfaces under the name ueN
1684 (eg. ue0). This is to provide a predictable name as vendors often
1685 change usb chipsets in a product without notice.
1688 The ichsmb(4) driver has been changed to require SMBus slave
1689 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1690 All of the other SMBus controller drivers require left-justified
1691 slave addresses, so this change makes all the drivers provide the
1695 INET6 statistics (struct ip6stat) was updated.
1696 netstat(1) needs to be recompiled.
1699 NTFS has been removed from GENERIC kernel on amd64 to match
1700 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1701 will load ntfs.ko module automatically when NTFS support is
1702 actually needed, unless ntfs.ko is not installed or security
1703 level prohibits loading kernel modules. If either is the case,
1704 "options NTFS" has to be added into kernel config.
1707 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1708 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1709 800061. User space tools that rely on the size of struct tcpcb in
1710 tcp_var.h (e.g. sockstat) need to be recompiled.
1713 ng_tty(4) module updated to match the new TTY subsystem.
1714 Due to API change, user-level applications must be updated.
1715 New API support added to mpd5 CVS and expected to be present
1716 in next mpd5.3 release.
1719 With __FreeBSD_version 800060 the makefs tool is part of
1720 the base system (it was a port).
1723 The afdata and ifnet locks have been changed from mutexes to
1724 rwlocks, network modules will need to be re-compiled.
1727 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1728 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1729 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1730 architecture and 40 bytes on 64-bit architecture. The userland
1731 applications "arp" and "ndp" have been updated accordingly.
1732 The output from "netstat -r" shows only routing entries and
1733 none of the L2 information.
1736 __FreeBSD_version 800057 marks the switchover from the
1737 binary ath hal to source code. Users must add the line:
1739 options AH_SUPPORT_AR5416
1741 to their kernel config files when specifying:
1745 The ath_hal module no longer exists; the code is now compiled
1746 together with the driver in the ath module. It is now
1747 possible to tailor chip support (i.e. reduce the set of chips
1748 and thereby the code size); consult ath_hal(4) for details.
1751 __FreeBSD_version 800054 adds memory barriers to
1752 <machine/atomic.h>, new interfaces to ifnet to facilitate
1753 multiple hardware transmit queues for cards that support
1754 them, and a lock-less ring-buffer implementation to
1755 enable drivers to more efficiently manage queueing of
1759 A new version of ZFS (version 13) has been merged to -HEAD.
1760 This version has zpool attribute "listsnapshots" off by
1761 default, which means "zfs list" does not show snapshots,
1762 and is the same as Solaris behavior.
1765 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1768 The uhci, ohci, ehci and slhci USB Host controller drivers have
1769 been put into separate modules. If you load the usb module
1770 separately through loader.conf you will need to load the
1771 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1772 controller add the following to loader.conf:
1778 The ABI used by the PMC toolset has changed. Please keep
1779 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1783 atapci kernel module now includes only generic PCI ATA
1784 driver. AHCI driver moved to ataahci kernel module.
1785 All vendor-specific code moved into separate kernel modules:
1786 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1787 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1788 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1789 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1792 The TTY subsystem of the kernel has been replaced by a new
1793 implementation, which provides better scalability and an
1794 improved driver model. Most common drivers have been migrated to
1795 the new TTY subsystem, while others have not. The following
1796 drivers have not yet been ported to the new TTY layer:
1799 cy, digi, rc, rp, sio
1805 ng_h4, ng_tty, ppp, sl, snp
1807 Adding these drivers to your kernel configuration file shall
1808 cause compilation to fail.
1811 ntpd has been upgraded to 4.2.4p5.
1814 OpenSSH has been upgraded to 5.1p1.
1816 For many years, FreeBSD's version of OpenSSH preferred DSA
1817 over RSA for host and user authentication keys. With this
1818 upgrade, we've switched to the vendor's default of RSA over
1819 DSA. This may cause upgraded clients to warn about unknown
1820 host keys even for previously known hosts. Users should
1821 follow the usual procedure for verifying host keys before
1822 accepting the RSA key.
1824 This can be circumvented by setting the "HostKeyAlgorithms"
1825 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1828 Please note that the sequence of keys offered for
1829 authentication has been changed as well. You may want to
1830 specify IdentityFile in a different order to revert this
1834 The sio(4) driver has been removed from the i386 and amd64
1835 kernel configuration files. This means uart(4) is now the
1836 default serial port driver on those platforms as well.
1838 To prevent collisions with the sio(4) driver, the uart(4) driver
1839 uses different names for its device nodes. This means the
1840 onboard serial port will now most likely be called "ttyu0"
1841 instead of "ttyd0". You may need to reconfigure applications to
1842 use the new device names.
1844 When using the serial port as a boot console, be sure to update
1845 /boot/device.hints and /etc/ttys before booting the new kernel.
1846 If you forget to do so, you can still manually specify the hints
1847 at the loader prompt:
1849 set hint.uart.0.at="isa"
1850 set hint.uart.0.port="0x3F8"
1851 set hint.uart.0.flags="0x10"
1852 set hint.uart.0.irq="4"
1856 The gpt(8) utility has been removed. Use gpart(8) to partition
1860 The version that Linuxulator emulates was changed from 2.4.2
1861 to 2.6.16. If you experience any problems with Linux binaries
1862 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1863 if it fixes the problem contact emulation mailing list.
1866 ISDN4BSD (I4B) was removed from the src tree. You may need to
1867 update a your kernel configuration and remove relevant entries.
1870 I have checked in code to support multiple routing tables.
1871 See the man pages setfib(1) and setfib(2).
1872 This is a hopefully backwards compatible version,
1873 but to make use of it you need to compile your kernel
1874 with options ROUTETABLES=2 (or more up to 16).
1877 The 802.11 wireless support was redone to enable multi-bss
1878 operation on devices that are capable. The underlying device
1879 is no longer used directly but instead wlanX devices are
1880 cloned with ifconfig. This requires changes to rc.conf files.
1881 For example, change:
1882 ifconfig_ath0="WPA DHCP"
1885 ifconfig_wlan0="WPA DHCP"
1886 see rc.conf(5) for more details. In addition, mergemaster of
1887 /etc/rc.d is highly recommended. Simultaneous update of userland
1888 and kernel wouldn't hurt either.
1890 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1891 modules were merged into the base wlan module. All references
1892 to these modules (e.g. in kernel config files) must be removed.
1895 psm(4) has gained write(2) support in native operation level.
1896 Arbitrary commands can be written to /dev/psm%d and status can
1897 be read back from it. Therefore, an application is responsible
1898 for status validation and error recovery. It is a no-op in
1899 other operation levels.
1902 Support for KSE threading has been removed from the kernel. To
1903 run legacy applications linked against KSE libmap.conf may
1904 be used. The following libmap.conf may be used to ensure
1905 compatibility with any prior release:
1907 libpthread.so.1 libthr.so.1
1908 libpthread.so.2 libthr.so.2
1909 libkse.so.3 libthr.so.3
1912 The layout of struct vmspace has changed. This affects libkvm
1913 and any executables that link against libkvm and use the
1914 kvm_getprocs() function. In particular, but not exclusively,
1915 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1916 The effects are minimal, but it's advisable to upgrade world
1920 The latest em driver no longer has support in it for the
1921 82575 adapter, this is now moved to the igb driver. The
1922 split was done to make new features that are incompatible
1923 with older hardware easier to do.
1926 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1927 likewise the kernel option is now GEOM_LINUX_LVM.
1930 The default NFS mount mode has changed from UDP to TCP for
1931 increased reliability. If you rely on (insecurely) NFS
1932 mounting across a firewall you may need to update your
1936 Belatedly note the addition of m_collapse for compacting
1940 The fts(3) structures have been changed to use adequate
1941 integer types for their members and so to be able to cope
1942 with huge file trees. The old fts(3) ABI is preserved
1943 through symbol versioning in libc, so third-party binaries
1944 using fts(3) should still work, although they will not take
1945 advantage of the extended types. At the same time, some
1946 third-party software might fail to build after this change
1947 due to unportable assumptions made in its source code about
1948 fts(3) structure members. Such software should be fixed
1949 by its vendor or, in the worst case, in the ports tree.
1950 FreeBSD_version 800015 marks this change for the unlikely
1951 case that a portable fix is impossible.
1954 To upgrade to -current after this date, you must be running
1955 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1956 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1959 The ADAPTIVE_GIANT kernel option has been retired because its
1960 functionality is the default now.
1963 The AT keyboard emulation of sunkbd(4) has been turned on
1964 by default. In order to make the special symbols of the Sun
1965 keyboards driven by sunkbd(4) work under X these now have
1966 to be configured the same way as Sun USB keyboards driven
1967 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1969 Option "XkbLayout" "us"
1970 Option "XkbRules" "xorg"
1971 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1974 It has been decided that it is desirable to provide ABI
1975 backwards compatibility to the FreeBSD 4/5/6 versions of the
1976 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1977 broken with the introduction of PCI domain support (see the
1978 20070930 entry). Unfortunately, this required the ABI of
1979 PCIOCGETCONF to be broken again in order to be able to
1980 provide backwards compatibility to the old version of that
1981 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1982 again. As for prominent ports this affects neither pciutils
1983 nor xorg-server this time, the hal port needs to be rebuilt
1987 The misnamed kthread_create() and friends have been renamed
1988 to kproc_create() etc. Many of the callers already
1989 used kproc_start()..
1990 I will return kthread_create() and friends in a while
1991 with implementations that actually create threads, not procs.
1992 Renaming corresponds with version 800002.
2001 Avoid using make -j when upgrading. While generally safe, there are
2002 sometimes problems using -j to upgrade. If your upgrade fails with
2003 -j, please try again without -j. From time to time in the past there
2004 have been problems using -j with buildworld and/or installworld. This
2005 is especially true when upgrading between "distant" versions (eg one
2006 that cross a major release boundary or several minor releases, or when
2007 several months have passed on the -current branch).
2009 Sometimes, obscure build problems are the result of environment
2010 poisoning. This can happen because the make utility reads its
2011 environment when searching for values for global variables. To run
2012 your build attempts in an "environmental clean room", prefix all make
2013 commands with 'env -i '. See the env(1) manual page for more details.
2015 When upgrading from one major version to another it is generally best
2016 to upgrade to the latest code in the currently installed branch first,
2017 then do an upgrade to the new branch. This is the best-tested upgrade
2018 path, and has the highest probability of being successful. Please try
2019 this approach before reporting problems with a major version upgrade.
2021 When upgrading a live system, having a root shell around before
2022 installing anything can help undo problems. Not having a root shell
2023 around can lead to problems if pam has changed too much from your
2024 starting point to allow continued authentication after the upgrade.
2028 When upgrading the boot ZFS pool to a new version, always follow
2031 1.) recompile and reinstall the ZFS boot loader and boot block
2032 (this is part of "make buildworld" and "make installworld")
2034 2.) update the ZFS boot block on your boot drive
2036 The following example updates the ZFS boot block on the first
2037 partition (freebsd-boot) of a GPT partitioned drive ad0:
2038 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2040 Non-boot pools do not need these updates.
2044 If you are updating from a prior version of FreeBSD (even one just
2045 a few days old), you should follow this procedure. It is the most
2046 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2048 make kernel-toolchain
2049 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2050 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2052 To test a kernel once
2053 ---------------------
2054 If you just want to boot a kernel once (because you are not sure
2055 if it works, or if you want to boot a known bad kernel to provide
2056 debugging information) run
2057 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2058 nextboot -k testkernel
2060 To just build a kernel when you know that it won't mess you up
2061 --------------------------------------------------------------
2062 This assumes you are already running a CURRENT system. Replace
2063 ${arch} with the architecture of your machine (e.g. "i386",
2064 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2066 cd src/sys/${arch}/conf
2067 config KERNEL_NAME_HERE
2068 cd ../compile/KERNEL_NAME_HERE
2073 If this fails, go to the "To build a kernel" section.
2075 To rebuild everything and install it on the current system.
2076 -----------------------------------------------------------
2077 # Note: sometimes if you are running current you gotta do more than
2078 # is listed here if you are upgrading from a really old current.
2080 <make sure you have good level 0 dumps>
2082 make kernel KERNCONF=YOUR_KERNEL_HERE
2084 <reboot in single user> [3]
2091 To cross-install current onto a separate partition
2092 --------------------------------------------------
2093 # In this approach we use a separate partition to hold
2094 # current's root, 'usr', and 'var' directories. A partition
2095 # holding "/", "/usr" and "/var" should be about 2GB in
2098 <make sure you have good level 0 dumps>
2101 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2102 <maybe newfs current's root partition>
2103 <mount current's root partition on directory ${CURRENT_ROOT}>
2104 make installworld DESTDIR=${CURRENT_ROOT}
2105 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2106 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2107 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2108 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2109 <reboot into current>
2110 <do a "native" rebuild/install as described in the previous section>
2111 <maybe install compatibility libraries from ports/misc/compat*>
2115 To upgrade in-place from stable to current
2116 ----------------------------------------------
2117 <make sure you have good level 0 dumps>
2119 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2121 <reboot in single user> [3]
2128 Make sure that you've read the UPDATING file to understand the
2129 tweaks to various things you need. At this point in the life
2130 cycle of current, things change often and you are on your own
2131 to cope. The defaults can also change, so please read ALL of
2132 the UPDATING entries.
2134 Also, if you are tracking -current, you must be subscribed to
2135 freebsd-current@freebsd.org. Make sure that before you update
2136 your sources that you have read and understood all the recent
2137 messages there. If in doubt, please track -stable which has
2138 much fewer pitfalls.
2140 [1] If you have third party modules, such as vmware, you
2141 should disable them at this point so they don't crash your
2144 [3] From the bootblocks, boot -s, and then do
2149 adjkerntz -i # if CMOS is wall time
2150 Also, when doing a major release upgrade, it is required that
2151 you boot into single user mode to do the installworld.
2153 [4] Note: This step is non-optional. Failure to do this step
2154 can result in a significant reduction in the functionality of the
2155 system. Attempting to do it by hand is not recommended and those
2156 that pursue this avenue should read this file carefully, as well
2157 as the archives of freebsd-current and freebsd-hackers mailing lists
2158 for potential gotchas. The -U option is also useful to consider.
2159 See mergemaster(8) for more information.
2161 [5] Usually this step is a noop. However, from time to time
2162 you may need to do this if you get unknown user in the following
2163 step. It never hurts to do it all the time. You may need to
2164 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2165 install) after the buildworld before this step if you last updated
2166 from current before 20130425 or from -stable before 20130430.
2168 [6] This only deletes old files and directories. Old libraries
2169 can be deleted by "make delete-old-libs", but you have to make
2170 sure that no program is using those libraries anymore.
2172 [8] In order to have a kernel that can run the 4.x binaries needed to
2173 do an installworld, you must include the COMPAT_FREEBSD4 option in
2174 your kernel. Failure to do so may leave you with a system that is
2175 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2176 required to run the 5.x binaries on more recent kernels. And so on
2177 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2179 Make sure that you merge any new devices from GENERIC since the
2180 last time you updated your kernel config file.
2182 [9] When checking out sources, you must include the -P flag to have
2183 cvs prune empty directories.
2185 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2186 "?=" instead of the "=" assignment operator, so that buildworld can
2187 override the CPUTYPE if it needs to.
2189 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2190 not on the command line, or in /etc/make.conf. buildworld will
2191 warn if it is improperly defined.
2194 This file contains a list, in reverse chronological order, of major
2195 breakages in tracking -current. It is not guaranteed to be a complete
2196 list of such breakages, and only contains entries since October 10, 2007.
2197 If you need to see UPDATING entries from before that date, you will need
2198 to fetch an UPDATING file from an older FreeBSD release.
2200 Copyright information:
2202 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2204 Redistribution, publication, translation and use, with or without
2205 modification, in full or in part, in any form or format of this
2206 document are permitted without further permission from the author.
2208 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2209 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2210 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2211 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2212 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2213 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2214 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2215 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2216 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2217 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2218 POSSIBILITY OF SUCH DAMAGE.
2220 Contact Warner Losh if you have any questions about your use of