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.
19 20151026: p6 FreeBSD-SA-15:25.ntp
21 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
23 20151002: p5 FreeBSD-SA-15:24.rpcbind [revised]
24 Revised patch to address a regression that prevents NIS from working.
26 20150929: p4 FreeBSD-SA-15:24.rpcbind
28 Fix rpcbind(8) remote denial of service. [SA-15:24]
30 20150916: p3 FreeBSD-EN-15:16.pw
34 Fix regression in pw(8) when creating numeric users or groups.
37 Fix libc handling of signals for multi-threaded processes.
40 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
42 20150825: p2 FreeBSD-SA-15:22.openssh
44 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
46 Fix insufficient check of unsupported pkg(7) signature methods.
49 20150818: p1 FreeBSD-SA-15:20.expat
50 FreeBSD-EN-15:11.toolchain
51 FreeBSD-EN-15:12.netstat
52 FreeBSD-EN-15:13.vidcontrol
54 Fix multiple integer overflows in expat (libbsdxml) XML parser.
57 Fix make(1) syntax errors when upgrading from 9.x and earlier.
60 Fix incorrect netstat(1) data handling on 32-bit systems.
63 Allow size argument to vidcontrol(1) for syscons(4). [EN-15:13]
69 The default Unbound configuration now enables remote control
70 using a local socket. Users who have already enabled the
71 local_unbound service should regenerate their configuration
72 by running "service local_unbound setup" as root.
75 An additional fix for the issue described in the 20150614 sendmail
76 entry below has been been committed in revision 284786.
79 The fix for the issue described in the 20150614 sendmail entry
80 below has been been committed in revision 284485. The work
81 around described in that entry is no longer needed unless the
82 default setting is overridden by a confDH_PARAMETERS configuration
83 setting of '5' or pointing to a 512 bit DH parameter file.
86 The import of openssl to address the FreeBSD-SA-15:10.openssl
87 security advisory includes a change which rejects handshakes
88 with DH parameters below 768 bits. sendmail releases prior
89 to 8.15.2 (not yet released), defaulted to a 512 bit
90 DH parameter setting for client connections. To work around
91 this interoperability, sendmail can be configured to use a
92 2048 bit DH parameter by:
94 1. Edit /etc/mail/`hostname`.mc
95 2. If a setting for confDH_PARAMETERS does not exist or
96 exists and is set to a string beginning with '5',
98 3. If a setting for confDH_PARAMETERS exists and is set to
99 a file path, create a new file with:
100 openssl dhparam -out /path/to/file 2048
101 4. Rebuild the .cf file:
102 cd /etc/mail/; make; make install
104 cd /etc/mail/; make restart
106 A sendmail patch is coming, at which time this file will be
110 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
111 defined in symlink(7); previously symlinks were silently ignored.
114 The const qualifier has been removed from iconv(3) to comply with
115 POSIX. The ports tree is aware of this from r384038 onwards.
118 At svn r275807, The default linux compat kernel ABI has been adjusted
119 to 2.6.18 in support of the linux-c6 compat ports infrastructure
120 update. If you wish to continue using the linux-f10 compat ports,
121 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
122 encouraged to update their linux-compat packages to linux-c6 during
123 their next update cycle.
125 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
128 pjdfstest has been integrated into kyua as an opt-in test suite.
129 Please see share/doc/pjdfstest/README for a more details on how to
136 The ofwfb driver, used to provide a graphics console on PowerPC when
137 using vt(4), no longer allows mmap() of all of physical memory. This
138 will prevent Xorg on PowerPC with some ATI graphics cards from
139 initializing properly unless x11-servers/xorg-server is updated to
143 The libatf-c and libatf-c++ major versions were downgraded to 0 and
144 1 respectively to match the upstream numbers. They were out of
145 sync because, when they were originally added to FreeBSD, the
146 upstream versions were not respected. These libraries are private
147 and not yet built by default, so renumbering them should be a
148 non-issue. However, unclean source trees will yield broken test
149 programs once the operator executes "make delete-old-libs" after a
152 Additionally, the atf-sh binary was made private by moving it into
153 /usr/libexec/. Already-built shell test programs will keep the
154 path to the old binary so they will break after "make delete-old"
157 If you are using WITH_TESTS=yes (not the default), wipe the object
158 tree and rebuild from scratch to prevent spurious test failures.
159 This is only needed once: the misnumbered libraries and misplaced
160 binaries have been added to OptionalObsoleteFiles.inc so they will
161 be removed during a clean upgrade.
164 The ixgbe tunables now match their sysctl counterparts, for example:
165 hw.ixgbe.enable_aim => hw.ix.enable_aim
166 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
169 The NFSv4.1 server committed by r269398 changes the internal
170 function call interfaces used between the NFS and krpc modules.
171 As such, __FreeBSD_version was bumped.
174 The default unbound configuration has been modified to address
175 issues with reverse lookups on networks that use private
176 address ranges. If you use the local_unbound service, run
177 "service local_unbound setup" as root to regenerate your
178 configuration, then "service local_unbound reload" to load the
182 It is no longer necessary to include the dwarf version in your DEBUG
183 options in your kernel config file. The bug that required it to be
184 placed in the config file has bene fixed. DEBUG should now just
185 contain -g. The build system will automatically update things
186 to do the right thing.
189 Several ABI breaking changes were merged to CTL and new iSCSI code.
190 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
191 iscsictl need to be rebuilt to work with a new kernel.
194 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
195 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
196 which differs from the behaviour controlled by this knob.)
199 On i386 and amd64 systems, the onifconsole flag is now set by default
200 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
201 as a login TTY if it is set in the bootloader as an active kernel
202 console. No changes in behavior should result otherwise. To revert to
203 the previous behavior, set ttyu0 to "off" in /etc/ttys.
206 Clang and llvm have been upgraded to 3.4.1 release.
209 Clang and llvm have been upgraded to 3.4 release.
212 If a Makefile in a tests/ directory was auto-generating a Kyuafile
213 instead of providing an explicit one, this would prevent such
214 Makefile from providing its own Kyuafile in the future during
215 NO_CLEAN builds. This has been fixed in the Makefiles but manual
216 intervention is needed to clean an objdir if you use NO_CLEAN:
217 # find /usr/obj -name Kyuafile | xargs rm -f
220 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
221 capability mode support. Please note that enabling the feature in
222 kernel is still highly recommended.
225 OpenSSH is now built with sandbox support, and will use sandbox as
226 the default privilege separation method. This requires Capsicum
227 capability mode support in kernel.
230 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
231 been deprecated and will not be part of FreeBSD 11.0 and later
232 releases. If you use this driver, please consider switching to
233 the nfe(4) driver instead.
239 The behavior of gss_pseudo_random() for the krb5 mechanism
240 has changed, for applications requesting a longer random string
241 than produced by the underlying enctype's pseudo-random() function.
242 In particular, the random string produced from a session key of
243 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
244 be different at the 17th octet and later, after this change.
245 The counter used in the PRF+ construction is now encoded as a
246 big-endian integer in accordance with RFC 4402.
247 __FreeBSD_version is bumped to 1000701.
250 The WITHOUT_ATF build knob has been removed and its functionality
251 has been subsumed into the more generic WITHOUT_TESTS. If you were
252 using the former to disable the build of the ATF libraries, you
253 should change your settings to use the latter.
256 The default version of mtree is nmtree which is obtained from
257 NetBSD. The output is generally the same, but may vary
258 slightly. If you found you need identical output adding
259 "-F freebsd9" to the command line should do the trick. For the
260 time being, the old mtree is available as fmtree.
263 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
264 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
265 1.1.4_8 and verify bsdyml not linked in, before running "make
267 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
269 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
272 The rc.d/jail script has been updated to support jail(8)
273 configuration file. The "jail_<jname>_*" rc.conf(5) variables
274 for per-jail configuration are automatically converted to
275 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
276 This is transparently backward compatible. See below about some
277 incompatibilities and rc.conf(5) manual page for more details.
279 These variables are now deprecated in favor of jail(8) configuration
280 file. One can use "rc.d/jail config <jname>" command to generate
281 a jail(8) configuration file in /var/run/jail.<jname>.conf without
282 running the jail(8) utility. The default pathname of the
283 configuration file is /etc/jail.conf and can be specified by
284 using $jail_conf or $jail_<jname>_conf variables.
286 Please note that jail_devfs_ruleset accepts an integer at
287 this moment. Please consider to rewrite the ruleset name
291 BIND has been removed from the base system. If all you need
292 is a local resolver, simply enable and start the local_unbound
293 service instead. Otherwise, several versions of BIND are
294 available in the ports tree. The dns/bind99 port is one example.
296 With this change, nslookup(1) and dig(1) are no longer in the base
297 system. Users should instead use host(1) and drill(1) which are
298 in the base system. Alternatively, nslookup and dig can
299 be obtained by installing the dns/bind-tools port.
302 With the addition of unbound(8), a new unbound user is now
303 required during installworld. "mergemaster -p" can be used to
304 add the user prior to installworld, as documented in the handbook.
307 OpenSSH is now built with DNSSEC support, and will by default
308 silently trust signed SSHFP records. This can be controlled with
309 the VerifyHostKeyDNS client configuration setting. DNSSEC support
310 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
313 The GNU Compiler Collection and C++ standard library (libstdc++)
314 are no longer built by default on platforms where clang is the system
315 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
319 The PROCDESC kernel option is now part of the GENERIC kernel
320 configuration and is required for the rwhod(8) to work.
321 If you are using custom kernel configuration, you should include
325 The API and ABI related to the Capsicum framework was modified
326 in backward incompatible way. The userland libraries and programs
327 have to be recompiled to work with the new kernel. This includes the
328 following libraries and programs, but the whole buildworld is
329 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
330 kdump, procstat, rwho, rwhod, uniq.
333 AES-NI intrinsic support has been added to gcc. The AES-NI module
334 has been updated to use this support. A new gcc is required to build
335 the aesni module on both i386 and amd64.
338 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
339 Thus "device padlock_rng" and "device rdrand_rng" should be
340 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
343 WITH_ICONV has been split into two feature sets. WITH_ICONV now
344 enables just the iconv* functionality and is now on by default.
345 WITH_LIBICONV_COMPAT enables the libiconv api and link time
346 compatability. Set WITHOUT_ICONV to build the old way.
347 If you have been using WITH_ICONV before, you will very likely
348 need to turn on WITH_LIBICONV_COMPAT.
351 INVARIANTS option now enables DEBUG for code with OpenSolaris and
352 Illumos origin, including ZFS. If you have INVARIANTS in your
353 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
355 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
356 locks if WITNESS option was set. Because that generated a lot of
357 witness(9) reports and all of them were believed to be false
358 positives, this is no longer done. New option OPENSOLARIS_WITNESS
359 can be used to achieve the previous behavior.
362 Timer values in IPv6 data structures now use time_uptime instead
363 of time_second. Although this is not a user-visible functional
364 change, userland utilities which directly use them---ndp(8),
365 rtadvd(8), and rtsold(8) in the base system---need to be updated
369 find -delete can now delete the pathnames given as arguments,
370 instead of only files found below them or if the pathname did
371 not contain any slashes. Formerly, the following error message
374 find: -delete: <path>: relative path potentially not safe
376 Deleting the pathnames given as arguments can be prevented
377 without error messages using -mindepth 1 or by changing
378 directory and passing "." as argument to find. This works in the
379 old as well as the new version of find.
382 Behavior of devfs rules path matching has been changed.
383 Pattern is now always matched against fully qualified devfs
384 path and slash characters must be explicitly matched by
385 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
386 subdirectories must be reviewed.
389 The default ARM ABI has changed to the ARM EABI. The old ABI is
390 incompatible with the ARM EABI and all programs and modules will
391 need to be rebuilt to work with a new kernel.
393 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
395 NOTE: Support for the old ABI will be removed in the future and
396 users are advised to upgrade.
399 pkg_install has been disconnected from the build if you really need it
400 you should add WITH_PKGTOOLS in your src.conf(5).
403 Most of network statistics structures were changed to be able
404 keep 64-bits counters. Thus all tools, that work with networking
405 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
408 Fix targets that run multiple make's to use && rather than ;
409 so that subsequent steps depend on success of previous.
411 NOTE: if building 'universe' with -j* on stable/8 or stable/9
412 it would be better to start the build using bmake, to avoid
413 overloading the machine.
416 Fix a bug that allowed a tracing process (e.g. gdb) to write
417 to a memory-mapped file in the traced process's address space
418 even if neither the traced process nor the tracing process had
419 write access to that file.
422 CVS has been removed from the base system. An exact copy
423 of the code is available from the devel/cvs port.
426 Some people report the following error after the switch to bmake:
428 make: illegal option -- J
429 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
431 *** [buildworld] Error code 2
433 this likely due to an old instance of make in
434 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
435 which src/Makefile will use that blindly, if it exists, so if
436 you see the above error:
438 rm -rf `make -V MAKEPATH`
443 Use bmake by default.
444 Whereas before one could choose to build with bmake via
445 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
446 make. The goal is to remove these knobs for 10-RELEASE.
448 It is worth noting that bmake (like gmake) treats the command
449 line as the unit of failure, rather than statements within the
450 command line. Thus '(cd some/where && dosomething)' is safer
451 than 'cd some/where; dosomething'. The '()' allows consistent
452 behavior in parallel build.
455 Fix a bug that allows NFS clients to issue READDIR on files.
458 The WITHOUT_IDEA option has been removed because
459 the IDEA patent expired.
462 The sysctl which controls TRIM support under ZFS has been renamed
463 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
467 The mergemaster command now uses the default MAKEOBJDIRPREFIX
468 rather than creating it's own in the temporary directory in
469 order allow access to bootstrapped versions of tools such as
470 install and mtree. When upgrading from version of FreeBSD where
471 the install command does not support -l, you will need to
472 install a new mergemaster command if mergemaster -p is required.
473 This can be accomplished with the command (cd src/usr.sbin/mergemaster
477 Legacy ATA stack, disabled and replaced by new CAM-based one since
478 FreeBSD 9.0, completely removed from the sources. Kernel modules
479 atadisk and atapi*, user-level tools atacontrol and burncd are
480 removed. Kernel option `options ATA_CAM` is now permanently enabled
484 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
485 and socketpair(2). Software, in particular Kerberos, may
486 automatically detect and use these during building. The resulting
487 binaries will not work on older kernels.
490 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
491 information, see the respective 20130304 entry).
494 Recent commits to callout(9) changed the size of struct callout,
495 so the KBI is probably heavily disturbed. Also, some functions
496 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
497 by macros. Every kernel module using it won't load, so rebuild
500 The ctl device has been re-enabled in GENERIC for i386 and amd64,
501 but does not initialize by default (because of the new CTL_DISABLE
502 option) to save memory. To re-enable it, remove the CTL_DISABLE
503 option from the kernel config file or set kern.cam.ctl.disable=0
504 in /boot/loader.conf.
507 The ctl device has been disabled in GENERIC for i386 and amd64.
508 This was done due to the extra memory being allocated at system
509 initialisation time by the ctl driver which was only used if
510 a CAM target device was created. This makes a FreeBSD system
511 unusable on 128MB or less of RAM.
514 A new compression method (lz4) has been merged to -HEAD. Please
515 refer to zpool-features(7) for more information.
517 Please refer to the "ZFS notes" section of this file for information
518 on upgrading boot ZFS pools.
521 A BSD-licensed patch(1) variant has been added and is installed
522 as bsdpatch, being the GNU version the default patch.
523 To inverse the logic and use the BSD-licensed one as default,
524 while having the GNU version installed as gnupatch, rebuild
525 and install world with the WITH_BSD_PATCH knob set.
528 Due to the use of the new -l option to install(1) during build
529 and install, you must take care not to directly set the INSTALL
530 make variable in your /etc/make.conf, /etc/src.conf, or on the
531 command line. If you wish to use the -C flag for all installs
532 you may be able to add INSTALL+=-C to /etc/make.conf or
536 The install(1) option -M has changed meaning and now takes an
537 argument that is a file or path to append logs to. In the
538 unlikely event that -M was the last option on the command line
539 and the command line contained at least two files and a target
540 directory the first file will have logs appended to it. The -M
541 option served little practical purpose in the last decade so its
542 use is expected to be extremely rare.
545 After switching to Clang as the default compiler some users of ZFS
546 on i386 systems started to experience stack overflow kernel panics.
547 Please consider using 'options KSTACK_PAGES=4' in such configurations.
550 GEOM_LABEL now mangles label names read from file system metadata.
551 Mangling affect labels containing spaces, non-printable characters,
552 '%' or '"'. Device names in /etc/fstab and other places may need to
556 By default, only the 10 most recent kernel dumps will be saved. To
557 restore the previous behaviour (no limit on the number of kernel dumps
558 stored in the dump directory) add the following line to /etc/rc.conf:
563 With the addition of auditdistd(8), a new auditdistd user is now
564 required during installworld. "mergemaster -p" can be used to
565 add the user prior to installworld, as documented in the handbook.
568 The sin6_scope_id member variable in struct sockaddr_in6 is now
569 filled by the kernel before passing the structure to the userland via
570 sysctl or routing socket. This means the KAME-specific embedded scope
571 id in sin6_addr.s6_addr[2] is always cleared in userland application.
572 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
573 __FreeBSD_version is bumped to 1000025.
576 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
577 This means that the world and kernel will be compiled with clang
578 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
579 and /usr/bin/cpp. To disable this behavior and revert to building
580 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
581 of current may need to bootstrap WITHOUT_CLANG first if the clang
582 build fails (its compatibility window doesn't extend to the 9 stable
586 The IPFIREWALL_FORWARD kernel option has been removed. Its
587 functionality now turned on by default.
590 The ZERO_COPY_SOCKET kernel option has been removed and
591 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
592 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
593 mechanism which is not safe and may result in kernel crashes.
594 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
595 driver supports disposeable external page sized mbuf storage.
596 Proper replacements for both zero-copy mechanisms are under
597 consideration and will eventually lead to complete removal
598 of the two kernel options.
601 The IPv4 network stack has been converted to network byte
602 order. The following modules need to be recompiled together
603 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
604 pf(4), ipfw(4), ng_ipfw(4), stf(4).
607 Support for non-MPSAFE filesystems was removed from VFS. The
608 VFS_VERSION was bumped, all filesystem modules shall be
612 All the non-MPSAFE filesystems have been disconnected from
613 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
614 portalfs, smbfs, xfs.
617 The interface cloning API and ABI has changed. The following
618 modules need to be recompiled together with kernel:
619 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
620 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
621 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
624 The sdhci driver was split in two parts: sdhci (generic SD Host
625 Controller logic) and sdhci_pci (actual hardware driver).
626 No kernel config modifications are required, but if you
627 load sdhc as a module you must switch to sdhci_pci instead.
630 Import the FUSE kernel and userland support into base system.
633 The GNU sort(1) program has been removed since the BSD-licensed
634 sort(1) has been the default for quite some time and no serious
635 problems have been reported. The corresponding WITH_GNU_SORT
639 The pfil(9) API/ABI for AF_INET family has been changed. Packet
640 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
644 The net80211(4) ABI has been changed to allow for improved driver
645 PS-POLL and power-save support. All wireless drivers need to be
646 recompiled to work with the new kernel.
649 The random(4) support for the VIA hardware random number
650 generator (`PADLOCK') is no longer enabled unconditionally.
651 Add the padlock_rng device in the custom kernel config if
652 needed. The GENERIC kernels on i386 and amd64 do include the
653 device, so the change only affects the custom kernel
657 The pf(4) packet filter ABI has been changed. pfctl(8) and
658 snmp_pf module need to be recompiled to work with new kernel.
661 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
662 to -HEAD. Pools that have empty_bpobj in active state can not be
663 imported read-write with ZFS implementations that do not support
664 this feature. For more information read the zpool-features(5)
668 The sparc64 ZFS loader has been changed to no longer try to auto-
669 detect ZFS providers based on diskN aliases but now requires these
670 to be explicitly listed in the OFW boot-device environment variable.
673 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
674 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
675 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
678 The following sysctls and tunables have been renamed for consistency
679 with other variables:
680 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
681 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
684 The sort utility has been replaced with BSD sort. For now, GNU sort
685 is also available as "gnusort" or the default can be set back to
686 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
687 installed as "bsdsort".
690 A new version of ZFS (pool version 5000) has been merged to -HEAD.
691 Starting with this version the old system of ZFS pool versioning
692 is superseded by "feature flags". This concept enables forward
693 compatibility against certain future changes in functionality of ZFS
694 pools. The first read-only compatible "feature flag" for ZFS pools
695 is named "com.delphix:async_destroy". For more information
696 read the new zpool-features(5) manual page.
697 Please refer to the "ZFS notes" section of this file for information
698 on upgrading boot ZFS pools.
701 The malloc(3) implementation embedded in libc now uses sources imported
702 as contrib/jemalloc. The most disruptive API change is to
703 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
704 delete it prior to installworld, and optionally re-create it using the
705 new format after rebooting. See malloc.conf(5) for details
706 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
710 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
711 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
712 now spelled mips. This is to aid compatibility with third-party
713 software that expects this naming scheme in uname(3). Little-endian
714 settings are unchanged. If you are updating a big-endian mips64 machine
715 from before this change, you may need to set MACHINE_ARCH=mips64 in
716 your environment before the new build system will recognize your machine.
719 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
723 Now unix domain sockets behave "as expected" on nullfs(5). Previously
724 nullfs(5) did not pass through all behaviours to the underlying layer,
725 as a result if we bound to a socket on the lower layer we could connect
726 only to the lower path; if we bound to the upper layer we could connect
727 only to the upper path. The new behavior is one can connect to both the
728 lower and the upper paths regardless what layer path one binds to.
731 The getifaddrs upgrade path broken with 20111215 has been restored.
732 If you have upgraded in between 20111215 and 20120209 you need to
733 recompile libc again with your kernel. You still need to recompile
734 world to be able to configure CARP but this restriction already
738 The set_rcvar() function has been removed from /etc/rc.subr. All
739 base and ports rc.d scripts have been updated, so if you have a
740 port installed with a script in /usr/local/etc/rc.d you can either
741 hand-edit the rcvar= line, or reinstall the port.
743 An easy way to handle the mass-update of /etc/rc.d:
744 rm /etc/rc.d/* && mergemaster -i
747 panic(9) now stops other CPUs in the SMP systems, disables interrupts
748 on the current CPU and prevents other threads from running.
749 This behavior can be reverted using the kern.stop_scheduler_on_panic
751 The new behavior can be incompatible with kern.sync_on_panic.
754 The carp(4) facility has been changed significantly. Configuration
755 of the CARP protocol via ifconfig(8) has changed, as well as format
756 of CARP events submitted to devd(8) has changed. See manual pages
757 for more information. The arpbalance feature of carp(4) is currently
758 not supported anymore.
760 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
761 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
762 need to be recompiled.
765 The acpi_wmi(4) status device /dev/wmistat has been renamed to
769 The option VFS_ALLOW_NONMPSAFE option has been added in order to
770 explicitely support non-MPSAFE filesystems.
771 It is on by default for all supported platform at this present
775 The broken amd(4) driver has been replaced with esp(4) in the amd64,
776 i386 and pc98 GENERIC kernel configuration files.
779 sysinstall has been removed
782 The stable/9 branch created in subversion. This corresponds to the
783 RELENG_9 branch in CVS.
786 This commit modifies vfs_register() so that it uses a hash
787 calculation to set vfc_typenum, which is enabled by default.
788 The first time a system is booted after this change, the
789 vfc_typenum values will change for all file systems. The
790 main effect of this is a change to the NFS server file handles
791 for file systems that use vfc_typenum in their fsid, such as ZFS.
792 It will, however, prevent vfc_typenum from changing when file
793 systems are loaded in a different order for subsequent reboots.
794 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
795 until you are ready to remount all NFS clients after a reboot.
798 Bump the shared library version numbers for libraries that
799 do not use symbol versioning, have changed the ABI compared
800 to stable/8 and which shared library version was not bumped.
801 Done as part of 9.0-RELEASE cycle.
804 During the merge of Capsicum features, the fget(9) KPI was modified.
805 This may require the rebuilding of out-of-tree device drivers --
806 issues have been reported specifically with the nVidia device driver.
807 __FreeBSD_version is bumped to 900041.
809 Also, there is a period between 20110811 and 20110814 where the
810 special devices /dev/{stdin,stdout,stderr} did not work correctly.
811 Building world from a kernel during that window may not work.
814 The packet filter (pf) code has been updated to OpenBSD 4.5.
815 You need to update userland tools to be in sync with kernel.
816 This update breaks backward compatibility with earlier pfsync(4)
817 versions. Care must be taken when updating redundant firewall setups.
820 The following sysctls and tunables are retired on x86 platforms:
822 machdep.hlt_logical_cpus
823 The following sysctl is retired:
824 machdep.hyperthreading_allowed
825 The sysctls were supposed to provide a way to dynamically offline and
826 online selected CPUs on x86 platforms, but the implementation has not
827 been reliable especially with SCHED_ULE scheduler.
828 machdep.hyperthreading_allowed tunable is still available to ignore
829 hyperthreading CPUs at OS level.
830 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
831 where X is an APIC ID of a CPU. Be advised, though, that disabling
832 CPUs in non-uniform fashion will result in non-uniform topology and
833 may lead to sub-optimal system performance with SCHED_ULE, which is
837 cpumask_t type is retired and cpuset_t is used in order to describe
841 Changes to ifconfig(8) for dynamic address family detection mandate
842 that you are running a kernel of 20110525 or later. Make sure to
843 follow the update procedure to boot a new kernel before installing
847 Support for sun4v architecture is officially dropped
850 Several KPI breaking changes have been committed to the mii(4) layer,
851 the PHY drivers and consequently some Ethernet drivers using mii(4).
852 This means that miibus.ko and the modules of the affected Ethernet
853 drivers need to be recompiled.
855 Note to kernel developers: Given that the OUI bit reversion problem
856 was fixed as part of these changes all mii(4) commits related to OUIs,
857 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
858 handling, no longer can be merged verbatim to stable/8 and previous
862 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
863 into their kernel configurations along with 'device pci'.
866 The default NFS client is now the new NFS client, so fstype "newnfs"
867 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
868 Although mounts via fstype "nfs" will usually work without userland
869 changes, it is recommended that the mount(8) and mount_nfs(8)
870 commands be rebuilt from sources and that a link to mount_nfs called
871 mount_oldnfs be created. The new client is compiled into the
872 kernel with "options NFSCL" and this is needed for diskless root
873 file systems. The GENERIC kernel configs have been changed to use
874 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
875 To use the regular/old client, you can "mount -t oldnfs ...". For
876 a diskless root file system, you must also include a line like:
878 vfs.root.mountfrom="oldnfs:"
880 in the boot/loader.conf on the root fs on the NFS server to make
881 a diskless root fs use the old client.
884 The GENERIC kernels for all architectures now default to the new
885 CAM-based ATA stack. It means that all legacy ATA drivers were
886 removed and replaced by respective CAM drivers. If you are using
887 ATA device names in /etc/fstab or other places, make sure to update
888 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
889 where 'Y's are the sequential numbers starting from zero for each type
890 in order of detection, unless configured otherwise with tunables,
891 see cam(4)). There will be symbolic links created in /dev/ to map
892 old adX devices to the respective adaY. They should provide basic
893 compatibility for file systems mounting in most cases, but they do
894 not support old user-level APIs and do not have respective providers
895 in GEOM. Consider using updated management tools with new device names.
897 It is possible to load devices ahci, ata, siis and mvs as modules,
898 but option ATA_CAM should remain in kernel configuration to make ata
899 module work as CAM driver supporting legacy ATA controllers. Device ata
900 still can be used in modular fashion (atacore + ...). Modules atadisk
901 and atapi* are not used and won't affect operation in ATA_CAM mode.
902 Note that to use CAM-based ATA kernel should include CAM devices
903 scbus, pass, da (or explicitly ada), cd and optionally others. All of
904 them are parts of the cam module.
906 ataraid(4) functionality is now supported by the RAID GEOM class.
907 To use it you can load geom_raid kernel module and use graid(8) tool
908 for management. Instead of /dev/arX device names, use /dev/raid/rX.
910 No kernel config options or code have been removed, so if a problem
911 arises, please report it and optionally revert to the old ATA stack.
912 In order to do it you can remove from the kernel config:
917 , and instead add back:
918 device atadisk # ATA disk drives
919 device ataraid # ATA RAID drives
920 device atapicd # ATAPI CDROM drives
921 device atapifd # ATAPI floppy drives
922 device atapist # ATAPI tape drives
925 The default NFS server has been changed to the new server, which
926 was referred to as the experimental server. If you need to switch
927 back to the old NFS server, you must now put the "-o" option on
928 both the mountd and nfsd commands. This can be done using the
929 mountd_flags and nfs_server_flags rc.conf variables until an
930 update to the rc scripts is committed, which is coming soon.
933 The GNU Objective-C runtime library (libobjc), and other Objective-C
934 related components have been removed from the base system. If you
935 require an Objective-C library, please use one of the available ports.
938 ath(4) has been split into bus- and device- modules. if_ath contains
939 the HAL, the TX rate control and the network device code. if_ath_pci
940 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
941 contains the AHB glue. Users need to load both if_ath_pci and if_ath
942 in order to use ath on everything else.
944 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
945 need to load if_ath and if_ath_pci for ath(4) operation.
948 As part of the replacement of sysinstall, the process of building
949 release media has changed significantly. For details, please re-read
950 release(7), which has been updated to reflect the new build process.
953 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
954 is the last available version under GPLv2. It brings a number of new
955 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
956 4.1 and SSE 4.2), better support for powerpc64, a number of new
957 directives, and lots of other small improvements. See the ChangeLog
958 file in contrib/binutils for the full details.
961 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
962 compliant, and will now use half of hash for authentication.
963 This will break interoperability with all stacks (including all
964 actual FreeBSD versions) who implement
965 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
967 The only workaround with such peers is to use another HMAC
968 algorithm for IPsec ("phase 2") authentication.
971 Remove the uio_yield prototype and symbol. This function has
972 been misnamed since it was introduced and should not be
973 globally exposed with this name. The equivalent functionality
974 is now available using kern_yield(curthread->td_user_pri).
975 The function remains undocumented.
978 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
979 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
980 for scalar sysctls is defined but disabled. Code that needs
981 UQUAD to pass the type checking that must compile on older
982 systems where the define is not present can check against
983 __FreeBSD_version >= 900030.
985 The system dialog(1) has been replaced with a new version previously
986 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
987 with the previous version, but the libdialog associated with it has
988 a largely incompatible API. As such, the original version of libdialog
989 will be kept temporarily as libodialog, until its base system consumers
990 are replaced or updated. Bump __FreeBSD_version to 900030.
993 If you are trying to run make universe on a -stable system, and you get
994 the following warning:
995 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
996 unknown. config(8) likely too old."
997 or something similar to it, then you must upgrade your -stable system
998 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
999 stable/8) or build the config from the latest stable/8 branch and
1000 install it on your system.
1002 Prior to this date, building a current universe on 8-stable system from
1003 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1004 error in the first kernel build phase. A new config on those old
1005 systems will fix that problem for older versions of -current.
1008 The TCP stack has been modified to allow Khelp modules to interact with
1009 it via helper hook points and store per-connection data in the TCP
1010 control block. Bump __FreeBSD_version to 900029. User space tools that
1011 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1015 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1016 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1017 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1018 to take advantage of it instead of using custom implementations. This
1019 means that these drivers now no longer unconditionally advertise
1020 support for flow control but only do so if flow control is a selected
1021 media option. This was implemented in the generic support that way in
1022 order to allow flow control to be switched on and off via ifconfig(8)
1023 with the PHY specific default to typically off in order to protect
1024 from unwanted effects. Consequently, if you used flow control with
1025 one of the above mentioned drivers you now need to explicitly enable
1026 it, for example via:
1027 ifconfig bge0 media auto mediaopt flowcontrol
1029 Along with the above mentioned changes generic support for setting
1030 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1031 e1000phy(4) as well as ip1000phy(4) have been converted to take
1032 advantage of it. This means that these drivers now no longer take the
1033 link0 parameter for selecting master mode but the master media option
1034 has to be used instead, for example like in the following:
1035 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1037 Selection of master mode now is also available with all other PHY
1038 drivers supporting 1000baseT.
1041 The TCP stack has received a significant update to add support for
1042 modularised congestion control and generally improve the clarity of
1043 congestion control decisions. Bump __FreeBSD_version to 900025. User
1044 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1045 sockstat) need to be recompiled.
1048 The man(1) utility has been replaced by a new version that no longer
1049 uses /etc/manpath.config. Please consult man.conf(5) for how to
1050 migrate local entries to the new format.
1053 The copyright strings printed by login(1) and sshd(8) at the time of a
1054 new connection have been removed to follow other operating systems and
1058 A workaround for a fixed ld bug has been removed in kernel code,
1059 so make sure that your system ld is built from sources after
1060 revision 210245 from 2010-07-19 (r211583 if building head kernel
1061 on stable/8, r211584 for stable/7; both from 2010-08-21).
1062 A symptom of incorrect ld version is different addresses for
1063 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1066 The $ipv6_prefer variable in rc.conf(5) has been split into
1067 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1069 The $ip6addrctl_policy is a variable to choose a pre-defined
1070 address selection policy set by ip6addrctl(8). A value
1071 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1074 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1075 flag (see an entry of 20090926) is set on an interface with no
1076 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1077 security reason. If you want IPv6 link-local address on all
1078 interfaces by default, set this to "YES".
1080 The old ipv6_prefer="YES" is equivalent to
1081 ipv6_activate_all_interfaces="YES" and
1082 ip6addrctl_policy="ipv6_prefer".
1085 DTrace has grown support for userland tracing. Due to this, DTrace is
1086 now i386 and amd64 only.
1087 dtruss(1) is now installed by default on those systems and a new
1088 kernel module is needed for userland tracing: fasttrap.
1089 No changes to your kernel config file are necessary to enable
1090 userland tracing, but you might consider adding 'STRIP=' and
1091 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1092 to have informative userland stack traces in DTrace (ustack).
1095 The acpi_aiboost(4) driver has been removed in favor of the new
1096 aibs(4) driver. You should update your kernel configuration file.
1099 BSD grep has been imported to the base system and it is built by
1100 default. It is completely BSD licensed, highly GNU-compatible, uses
1101 less memory than its GNU counterpart and has a small codebase.
1102 However, it is slower than its GNU counterpart, which is mostly
1103 noticeable for larger searches, for smaller ones it is measurable
1104 but not significant. The reason is complex, the most important factor
1105 is that we lack a modern and efficient regex library and GNU
1106 overcomes this by optimizing the searches internally. Future work
1107 on improving the regex performance is planned, for the meantime,
1108 users that need better performance, can build GNU grep instead by
1109 setting the WITH_GNU_GREP knob.
1112 Due to the import of powerpc64 support, all existing powerpc kernel
1113 configuration files must be updated with a machine directive like this:
1114 machine powerpc powerpc
1116 In addition, an updated config(8) is required to build powerpc kernels
1120 A new version of ZFS (version 15) has been merged to -HEAD.
1121 This version uses a python library for the following subcommands:
1122 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1123 For full functionality of these commands the following port must
1124 be installed: sysutils/py-zfs
1127 'vm_page's are now hashed by physical address to an array of mutexes.
1128 Currently this is only used to serialize access to hold_count. Over
1129 time the page queue mutex will be peeled away. This changes the size
1130 of pmap on every architecture. And requires all callers of vm_page_hold
1131 and vm_page_unhold to be updated.
1134 WITH_CTF can now be specified in src.conf (not recommended, there
1135 are some problems with static executables), make.conf (would also
1136 affect ports which do not use GNU make and do not override the
1137 compile targets) or in the kernel config (via "makeoptions
1139 When WITH_CTF was specified there before this was silently ignored,
1140 so make sure that WITH_CTF is not used in places which could lead
1141 to unwanted behavior.
1144 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1145 to allow 32-bit compatibility on non-x86 platforms. All kernel
1146 configurations on amd64 and ia64 platforms using these options must
1147 be modified accordingly.
1150 The utmp user accounting database has been replaced with utmpx,
1151 the user accounting interface standardized by POSIX.
1152 Unfortunately the semantics of utmp and utmpx don't match,
1153 making it practically impossible to support both interfaces.
1154 The user accounting database is used by tools like finger(1),
1155 last(1), talk(1), w(1) and ac(8).
1157 All applications in the base system use utmpx. This means only
1158 local binaries (e.g. from the ports tree) may still use these
1159 utmp database files. These applications must be rebuilt to make
1162 After the system has been upgraded, it is safe to remove the old
1163 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1164 assuming their contents is of no importance anymore. Old wtmp
1165 databases can only be used by last(1) and ac(8) after they have
1166 been converted to the new format using wtmpcvt(1).
1169 Introduce the kernel thread "deadlock resolver" (which can be enabled
1170 via the DEADLKRES option, see NOTES for more details) and the
1171 sleepq_type() function for sleepqueues.
1174 The rc.firewall and rc.firewall6 were unified, and
1175 rc.firewall6 and rc.d/ip6fw were removed.
1176 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1177 variables are obsoleted. Instead, the following new rc
1178 variables are added to rc.d/ipfw:
1180 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1181 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1182 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1184 The meanings correspond to the relevant IPv4 variables.
1190 The default terminal emulation for syscons(4) has been changed
1191 from cons25 to xterm on all platforms except pc98. This means
1192 that the /etc/ttys file needs to be updated to ensure correct
1193 operation of applications on the console.
1195 The terminal emulation style can be toggled per window by using
1196 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1197 options can be used to change the compile-time default back to
1200 To prevent graphical artifacts, make sure the TERM environment
1201 variable is set to match the terminal emulation that is being
1202 performed by syscons(4).
1205 The layout of the structure ieee80211req_scan_result has changed.
1206 Applications that require wireless scan results (e.g. ifconfig(8))
1207 from net80211 need to be recompiled.
1209 Applications such as wpa_supplicant(8) may require a full world
1210 build without using NO_CLEAN in order to get synchronized with the
1214 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1215 There's one kernel module for each firmware. Adding "device iwnfw"
1216 to the kernel configuration file means including all three firmware
1217 images inside the kernel. If you want to include just the one for
1218 your wireless card, use the devices iwn4965fw, iwn5000fw or
1222 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1223 into rc.d/netif. The changes are the following:
1225 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1226 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1227 Note that both variables need the "inet6" keyword at the head.
1229 Do not set $ipv6_network_interfaces manually if you do not
1230 understand what you are doing. It is not needed in most cases.
1232 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1235 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1236 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1238 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1239 all configured interfaces have "inet6 accept_rtadv" in the
1240 $ifconfig_IF_ipv6. These are for backward compatibility.
1242 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1243 functionality of interfaces with no corresponding
1244 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1245 and the default address selection policy of ip6addrctl(8)
1246 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1247 Note that if you want to configure IPv6 functionality on the
1248 disabled interfaces after boot, first you need to clear the flag by
1249 using ifconfig(8) like:
1251 ifconfig em0 inet6 -ifdisabled
1253 If YES, the default address selection policy is set as
1256 The default value of $ipv6_prefer is NO.
1258 4. If your system need to receive Router Advertisement messages,
1259 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1260 scripts automatically invoke rtsol(8) when the interface becomes
1261 UP. The Router Advertisement messages are used for SLAAC
1262 (State-Less Address AutoConfiguration).
1265 802.11s D3.03 support was committed. This is incompatible with the
1266 previous code, which was based on D3.0.
1269 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1270 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1271 control whether accepting Router Advertisement messages or not.
1272 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1273 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1274 The ifconfig(8) utility now supports these flags.
1277 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1278 mount(8) and -a option for df(1) to see them.
1281 The old tunable hw.bus.devctl_disable has been superseded by
1282 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1283 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1287 Remove the option STOP_NMI. The default action is now to use NMI only
1288 for KDB via the newly introduced function stop_cpus_hard() and
1289 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1292 The stable/8 branch created in subversion. This corresponds to the
1293 RELENG_8 branch in CVS.
1296 Bump the shared library version numbers for all libraries that do not
1297 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1298 __FreeBSD_version to 800105.
1301 Due to changes in the implementation of virtual network stack support,
1302 all network-related kernel modules must be recompiled. As this change
1303 breaks the ABI, bump __FreeBSD_version to 800104.
1306 The TOE interface to the TCP syncache has been modified to remove
1307 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1308 The cxgb driver is the only TOE consumer affected by this change, and
1309 needs to be recompiled along with the kernel. As this change breaks
1310 the ABI, bump __FreeBSD_version to 800103.
1313 Padding has been added to struct tcpcb, sackhint and tcpstat in
1314 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1315 maintaining the ABI. However, this change breaks the ABI, so bump
1316 __FreeBSD_version to 800102. User space tools that rely on the size of
1317 any of these structs (e.g. sockstat) need to be recompiled.
1320 The NFS_LEGACYRPC option has been removed along with the old kernel
1321 RPC implementation that this option selected. Kernel configurations
1322 may need to be adjusted.
1325 The network interface device nodes at /dev/net/<interface> have been
1326 removed. All ioctl operations can be performed the normal way using
1327 routing sockets. The kqueue functionality can generally be replaced
1328 with routing sockets.
1331 The documentation from the FreeBSD Documentation Project (Handbook,
1332 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1333 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1336 The ABI of various structures related to the SYSV IPC API have been
1337 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1338 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1342 Layout of struct vnet has changed as routing related variables were
1343 moved to their own Vimage module. Modules need to be recompiled. Bump
1344 __FreeBSD_version to 800099.
1347 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1348 respectively. As long as no more than 16 groups per process are used,
1349 no changes should be visible. When more than 16 groups are used, old
1350 binaries may fail if they call getgroups() or getgrouplist() with
1351 statically sized storage. Recompiling will work around this, but
1352 applications should be modified to use dynamically allocated storage
1353 for group arrays as POSIX.1-2008 does not cap an implementation's
1354 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1356 NFS and portalfs mounts may also be affected as the list of groups is
1357 truncated to 16. Users of NFS who use more than 16 groups, should
1358 take care that negative group permissions are not used on the exported
1359 file systems as they will not be reliable unless a GSSAPI based
1360 authentication method is used.
1363 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1364 option compiles in the support for adaptive spinning for lockmgrs
1365 which want to enable it. The lockinit() function now accepts the flag
1366 LK_ADAPTIVE in order to make the lock object subject to adaptive
1367 spinning when both held in write and read mode.
1370 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1371 changed. User applications that use this ioctl need to be rebuilt.
1374 The layout of struct thread has changed. Kernel and modules need to
1378 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1379 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1382 window(1) has been removed from the base system. It can now be
1383 installed from ports. The port is called misc/window.
1386 The way we are storing and accessing `routing table' entries has
1387 changed. Programs reading the FIB, like netstat, need to be
1391 A new netisr implementation has been added for FreeBSD 8. Network
1392 file system modules, such as igmp, ipdivert, and others, should be
1394 Bump __FreeBSD_version to 800096.
1397 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1401 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1402 Bump __FreeBSD_version to 800094.
1405 Add mnt_xflag field to 'struct mount'. File system modules need to be
1407 Bump __FreeBSD_version to 800093.
1410 The compiling option ADAPTIVE_SX has been retired while it has been
1411 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1412 The KPI for sx_init_flags() changes as accepting flags:
1413 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1414 been introduced in order to handle the reversed logic.
1415 Bump __FreeBSD_version to 800092.
1418 Add support for hierarchical jails. Remove global securelevel.
1419 Bump __FreeBSD_version to 800091.
1422 The layout of struct vnet_net has changed, therefore modules
1424 Bump __FreeBSD_version to 800090.
1427 The newly imported zic(8) produces a new format in the output. Please
1428 run tzsetup(8) to install the newly created data to /etc/localtime.
1431 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1432 hw.usb.* and is now consistent again with previous releases.
1435 802.11 monitor mode support was revised and driver api's were changed.
1436 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1437 of DLT_IEEE802_11. No user-visible data structures were changed but
1438 applications that use DLT_IEEE802_11 may require changes.
1439 Bump __FreeBSD_version to 800088.
1442 The layout of the following structs has changed: sysctl_oid,
1443 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1444 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1445 panics may be experienced. World rebuild is required for
1446 correctly checking networking state from userland.
1447 Bump __FreeBSD_version to 800085.
1450 MLDv2 and Source-Specific Multicast (SSM) have been merged
1451 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1452 The implementation of SSM within FreeBSD's IPv6 stack closely
1453 follows the IPv4 implementation.
1455 For kernel developers:
1457 * The most important changes are that the ip6_output() and
1458 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1459 and this lock has been downgraded to a non-recursive mutex.
1461 * As with the changes to the IPv4 stack to support SSM, filtering
1462 of inbound multicast traffic must now be performed by transport
1463 protocols within the IPv6 stack. This does not apply to TCP and
1464 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1466 * The KPIs used by IPv6 multicast are similar to those used by
1467 the IPv4 stack, with the following differences:
1468 * im6o_mc_filter() is analogous to imo_multicast_filter().
1469 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1470 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1471 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1472 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1473 for MLDv1 have an additional 'timer' argument which is used to
1474 jitter the initial membership report for the solicited-node
1475 multicast membership on-link.
1476 * This is not strictly needed for MLDv2, which already jitters
1477 its report transmissions. However, the 'timer' argument is
1478 preserved in case MLDv1 is active on the interface.
1480 * The KAME linked-list based IPv6 membership implementation has
1481 been refactored to use a vector similar to that used by the IPv4
1483 Code which maintains a list of its own multicast memberships
1484 internally, e.g. carp, has been updated to reflect the new
1487 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1488 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1489 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1490 implementation constraint which needs to be addressed in HEAD.
1492 For application developers:
1494 * The changes are broadly similar to those made for the IPv4
1497 * The use of IPv4 and IPv6 multicast socket options on the same
1498 socket, using mapped addresses, HAS NOT been tested or supported.
1500 * There are a number of issues with the implementation of various
1501 IPv6 multicast APIs which need to be resolved in the API surface
1502 before the implementation is fully compatible with KAME userland
1503 use, and these are mostly to do with interface index treatment.
1505 * The literature available discusses the use of either the delta / ASM
1506 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1507 using setsourcefilter(3)/getsourcefilter(3). For more information
1508 please refer to RFC 3768, 'Socket Interface Extensions for
1509 Multicast Source Filters'.
1511 * Applications which use the published RFC 3678 APIs should be fine.
1513 For systems administrators:
1515 * The mtest(8) utility has been refactored to support IPv6, in
1516 addition to IPv4. Interface addresses are no longer accepted
1517 as arguments, their names must be used instead. The utility
1518 will map the interface name to its first IPv4 address as
1519 returned by getifaddrs(3).
1521 * The ifmcstat(8) utility has also been updated to print the MLDv2
1522 endpoint state and source filter lists via sysctl(3).
1524 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1525 loopback of IPv6 multicast datagrams by default; it defaults to 1
1526 to preserve the existing behaviour. Disabling multicast loopback is
1527 recommended for optimal system performance.
1529 * The IPv6 MROUTING code has been changed to examine this sysctl
1530 instead of attempting to perform a group lookup before looping
1531 back forwarded datagrams.
1533 Bump __FreeBSD_version to 800084.
1536 Implement low-level Bluetooth HCI API.
1537 Bump __FreeBSD_version to 800083.
1540 The layout of struct malloc_type, used by modules to register new
1541 memory allocation types, has changed. Most modules will need to
1542 be rebuilt or panics may be experienced.
1543 Bump __FreeBSD_version to 800081.
1546 Anticipate overflowing inp_flags - add inp_flags2.
1547 This changes most offsets in inpcb, so checking v4 connection
1548 state will require a world rebuild.
1549 Bump __FreeBSD_version to 800080.
1552 Add an llentry to struct route and struct route_in6. Modules
1553 embedding a struct route will need to be recompiled.
1554 Bump __FreeBSD_version to 800079.
1557 The size of rt_metrics_lite and by extension rtentry has changed.
1558 Networking administration apps will need to be recompiled.
1559 The route command now supports show as an alias for get, weighting
1560 of routes, sticky and nostick flags to alter the behavior of stateful
1562 Bump __FreeBSD_version to 800078.
1565 Do not use Giant for kbdmux(4) locking. This is wrong and
1566 apparently causing more problems than it solves. This will
1567 re-open the issue where interrupt handlers may race with
1568 kbdmux(4) in polling mode. Typical symptoms include (but
1569 not limited to) duplicated and/or missing characters when
1570 low level console functions (such as gets) are used while
1571 interrupts are enabled (for example geli password prompt,
1572 mountroot prompt etc.). Disabling kbdmux(4) may help.
1575 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1576 kernel modules referencing any of the above need to be recompiled.
1577 Bump __FreeBSD_version to 800075.
1580 GEOM_PART has become the default partition slicer for storage devices,
1581 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1582 introduces some changes:
1584 MSDOS/EBR: the devices created from MSDOS extended partition entries
1585 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1586 to devices with offset-based names. fstabs may need to be modified.
1588 BSD: the "geometry does not match label" warning is harmless in most
1589 cases but it points to problems in file system misalignment with
1590 disk geometry. The "c" partition is now implicit, covers the whole
1591 top-level drive and cannot be (mis)used by users.
1593 General: Kernel dumps are now not allowed to be written to devices
1594 whose partition types indicate they are meant to be used for file
1595 systems (or, in case of MSDOS partitions, as something else than
1598 Most of these changes date approximately from 200812.
1601 The uscanner(4) driver has been removed from the kernel. This follows
1602 Linux removing theirs in 2.6 and making libusb the default interface
1603 (supported by sane).
1606 The multicast forwarding code has been cleaned up. netstat(1)
1607 only relies on KVM now for printing bandwidth upcall meters.
1608 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1609 ip6_mroute_mod respectively. The config(5) options for statically
1610 compiling this code remain the same, i.e. 'options MROUTING'.
1613 Support for the IFF_NEEDSGIANT network interface flag has been
1614 removed, which means that non-MPSAFE network device drivers are no
1615 longer supported. In particular, if_ar, if_sr, and network device
1616 drivers from the old (legacy) USB stack can no longer be built or
1620 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1621 a bunch of new language catalog files have also been added.
1622 This means that some common libc messages are now localized and
1623 they depend on the LC_MESSAGES environmental variable.
1626 The k8temp(4) driver has been renamed to amdtemp(4) since
1627 support for Family 10 and Family 11 CPU families was added.
1630 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1631 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1633 For kernel developers, the most important changes are that the
1634 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1635 and this lock has been downgraded to a non-recursive mutex.
1637 Transport protocols (UDP, Raw IP) are now responsible for filtering
1638 inbound multicast traffic according to group membership and source
1639 filters. The imo_multicast_filter() KPI exists for this purpose.
1640 Transports which do not use multicast (SCTP, TCP) already reject
1641 multicast by default. Forwarding and receive performance may improve
1642 as a mutex acquisition is no longer needed in the ip_input()
1643 low-level input path. in_addmulti() and in_delmulti() are shimmed
1644 to new KPIs which exist to support SSM in-kernel.
1646 For application developers, it is recommended that loopback of
1647 multicast datagrams be disabled for best performance, as this
1648 will still cause the lock to be taken for each looped-back
1649 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1650 be tuned to 0 to disable loopback by default; it defaults to 1
1651 to preserve the existing behaviour.
1653 For systems administrators, to obtain best performance with
1654 multicast reception and multiple groups, it is always recommended
1655 that a card with a suitably precise hash filter is used. Hash
1656 collisions will still result in the lock being taken within the
1657 transport protocol input path to check group membership.
1659 If deploying FreeBSD in an environment with IGMP snooping switches,
1660 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1661 enabled; this forces 224.0.0.0/24 group membership to be announced
1664 The size of 'struct igmpstat' has changed; netstat needs to be
1665 recompiled to reflect this.
1666 Bump __FreeBSD_version to 800070.
1669 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1670 updated to use it. This requires a buildworld/installworld in order to
1671 update the library and dependencies (usbconfig, etc). Its advisable to
1672 rebuild all ports which uses libusb. More specific directions are given
1673 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1674 libusb are no longer required and can be removed.
1677 A workaround is committed to allow the creation of System V shared
1678 memory segment of size > 2 GB on the 64-bit architectures.
1679 Due to a limitation of the existing ABI, the shm_segsz member
1680 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1681 wrong for large segments. Note that limits must be explicitly
1682 raised to allow such segments to be created.
1685 The layout of struct ifnet has changed, requiring a rebuild of all
1686 network device driver modules.
1689 The /dev handling for the new USB stack has changed, a
1690 buildworld/installworld is required for libusb20.
1693 The new USB2 stack has now been permanently moved in and all kernel and
1694 module names reverted to their previous values (eg, usb, ehci, ohci,
1695 ums, ...). The old usb stack can be compiled in by prefixing the name
1696 with the letter 'o', the old usb modules have been removed.
1697 Updating entry 20090216 for xorg and 20090215 for libmap may still
1701 The rc.conf(5) option if_up_delay has been renamed to
1702 defaultroute_delay to better reflect its purpose. If you have
1703 customized this setting in /etc/rc.conf you need to update it to
1707 xorg 7.4 wants to configure its input devices via hald which does not
1708 yet work with USB2. If the keyboard/mouse does not work in xorg then
1710 Option "AllowEmptyInput" "off"
1711 to your ServerLayout section. This will cause X to use the configured
1712 kbd and mouse sections from your xorg.conf.
1715 The GENERIC kernels for all architectures now default to the new USB2
1716 stack. No kernel config options or code have been removed so if a
1717 problem arises please report it and optionally revert to the old USB
1718 stack. If you are loading USB kernel modules or have a custom kernel
1719 that includes GENERIC then ensure that usb names are also changed over,
1720 eg uftdi -> usb2_serial_ftdi.
1722 Older programs linked against the ports libusb 0.1 need to be
1723 redirected to the new stack's libusb20. /etc/libmap.conf can
1725 # Map old usb library to new one for usb2 stack
1726 libusb-0.1.so.8 libusb20.so.1
1729 All USB ethernet devices now attach as interfaces under the name ueN
1730 (eg. ue0). This is to provide a predictable name as vendors often
1731 change usb chipsets in a product without notice.
1734 The ichsmb(4) driver has been changed to require SMBus slave
1735 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1736 All of the other SMBus controller drivers require left-justified
1737 slave addresses, so this change makes all the drivers provide the
1741 INET6 statistics (struct ip6stat) was updated.
1742 netstat(1) needs to be recompiled.
1745 NTFS has been removed from GENERIC kernel on amd64 to match
1746 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1747 will load ntfs.ko module automatically when NTFS support is
1748 actually needed, unless ntfs.ko is not installed or security
1749 level prohibits loading kernel modules. If either is the case,
1750 "options NTFS" has to be added into kernel config.
1753 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1754 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1755 800061. User space tools that rely on the size of struct tcpcb in
1756 tcp_var.h (e.g. sockstat) need to be recompiled.
1759 ng_tty(4) module updated to match the new TTY subsystem.
1760 Due to API change, user-level applications must be updated.
1761 New API support added to mpd5 CVS and expected to be present
1762 in next mpd5.3 release.
1765 With __FreeBSD_version 800060 the makefs tool is part of
1766 the base system (it was a port).
1769 The afdata and ifnet locks have been changed from mutexes to
1770 rwlocks, network modules will need to be re-compiled.
1773 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1774 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1775 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1776 architecture and 40 bytes on 64-bit architecture. The userland
1777 applications "arp" and "ndp" have been updated accordingly.
1778 The output from "netstat -r" shows only routing entries and
1779 none of the L2 information.
1782 __FreeBSD_version 800057 marks the switchover from the
1783 binary ath hal to source code. Users must add the line:
1785 options AH_SUPPORT_AR5416
1787 to their kernel config files when specifying:
1791 The ath_hal module no longer exists; the code is now compiled
1792 together with the driver in the ath module. It is now
1793 possible to tailor chip support (i.e. reduce the set of chips
1794 and thereby the code size); consult ath_hal(4) for details.
1797 __FreeBSD_version 800054 adds memory barriers to
1798 <machine/atomic.h>, new interfaces to ifnet to facilitate
1799 multiple hardware transmit queues for cards that support
1800 them, and a lock-less ring-buffer implementation to
1801 enable drivers to more efficiently manage queueing of
1805 A new version of ZFS (version 13) has been merged to -HEAD.
1806 This version has zpool attribute "listsnapshots" off by
1807 default, which means "zfs list" does not show snapshots,
1808 and is the same as Solaris behavior.
1811 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1814 The uhci, ohci, ehci and slhci USB Host controller drivers have
1815 been put into separate modules. If you load the usb module
1816 separately through loader.conf you will need to load the
1817 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1818 controller add the following to loader.conf:
1824 The ABI used by the PMC toolset has changed. Please keep
1825 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1829 atapci kernel module now includes only generic PCI ATA
1830 driver. AHCI driver moved to ataahci kernel module.
1831 All vendor-specific code moved into separate kernel modules:
1832 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1833 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1834 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1835 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1838 The TTY subsystem of the kernel has been replaced by a new
1839 implementation, which provides better scalability and an
1840 improved driver model. Most common drivers have been migrated to
1841 the new TTY subsystem, while others have not. The following
1842 drivers have not yet been ported to the new TTY layer:
1845 cy, digi, rc, rp, sio
1851 ng_h4, ng_tty, ppp, sl, snp
1853 Adding these drivers to your kernel configuration file shall
1854 cause compilation to fail.
1857 ntpd has been upgraded to 4.2.4p5.
1860 OpenSSH has been upgraded to 5.1p1.
1862 For many years, FreeBSD's version of OpenSSH preferred DSA
1863 over RSA for host and user authentication keys. With this
1864 upgrade, we've switched to the vendor's default of RSA over
1865 DSA. This may cause upgraded clients to warn about unknown
1866 host keys even for previously known hosts. Users should
1867 follow the usual procedure for verifying host keys before
1868 accepting the RSA key.
1870 This can be circumvented by setting the "HostKeyAlgorithms"
1871 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1874 Please note that the sequence of keys offered for
1875 authentication has been changed as well. You may want to
1876 specify IdentityFile in a different order to revert this
1880 The sio(4) driver has been removed from the i386 and amd64
1881 kernel configuration files. This means uart(4) is now the
1882 default serial port driver on those platforms as well.
1884 To prevent collisions with the sio(4) driver, the uart(4) driver
1885 uses different names for its device nodes. This means the
1886 onboard serial port will now most likely be called "ttyu0"
1887 instead of "ttyd0". You may need to reconfigure applications to
1888 use the new device names.
1890 When using the serial port as a boot console, be sure to update
1891 /boot/device.hints and /etc/ttys before booting the new kernel.
1892 If you forget to do so, you can still manually specify the hints
1893 at the loader prompt:
1895 set hint.uart.0.at="isa"
1896 set hint.uart.0.port="0x3F8"
1897 set hint.uart.0.flags="0x10"
1898 set hint.uart.0.irq="4"
1902 The gpt(8) utility has been removed. Use gpart(8) to partition
1906 The version that Linuxulator emulates was changed from 2.4.2
1907 to 2.6.16. If you experience any problems with Linux binaries
1908 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1909 if it fixes the problem contact emulation mailing list.
1912 ISDN4BSD (I4B) was removed from the src tree. You may need to
1913 update a your kernel configuration and remove relevant entries.
1916 I have checked in code to support multiple routing tables.
1917 See the man pages setfib(1) and setfib(2).
1918 This is a hopefully backwards compatible version,
1919 but to make use of it you need to compile your kernel
1920 with options ROUTETABLES=2 (or more up to 16).
1923 The 802.11 wireless support was redone to enable multi-bss
1924 operation on devices that are capable. The underlying device
1925 is no longer used directly but instead wlanX devices are
1926 cloned with ifconfig. This requires changes to rc.conf files.
1927 For example, change:
1928 ifconfig_ath0="WPA DHCP"
1931 ifconfig_wlan0="WPA DHCP"
1932 see rc.conf(5) for more details. In addition, mergemaster of
1933 /etc/rc.d is highly recommended. Simultaneous update of userland
1934 and kernel wouldn't hurt either.
1936 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1937 modules were merged into the base wlan module. All references
1938 to these modules (e.g. in kernel config files) must be removed.
1941 psm(4) has gained write(2) support in native operation level.
1942 Arbitrary commands can be written to /dev/psm%d and status can
1943 be read back from it. Therefore, an application is responsible
1944 for status validation and error recovery. It is a no-op in
1945 other operation levels.
1948 Support for KSE threading has been removed from the kernel. To
1949 run legacy applications linked against KSE libmap.conf may
1950 be used. The following libmap.conf may be used to ensure
1951 compatibility with any prior release:
1953 libpthread.so.1 libthr.so.1
1954 libpthread.so.2 libthr.so.2
1955 libkse.so.3 libthr.so.3
1958 The layout of struct vmspace has changed. This affects libkvm
1959 and any executables that link against libkvm and use the
1960 kvm_getprocs() function. In particular, but not exclusively,
1961 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1962 The effects are minimal, but it's advisable to upgrade world
1966 The latest em driver no longer has support in it for the
1967 82575 adapter, this is now moved to the igb driver. The
1968 split was done to make new features that are incompatible
1969 with older hardware easier to do.
1972 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1973 likewise the kernel option is now GEOM_LINUX_LVM.
1976 The default NFS mount mode has changed from UDP to TCP for
1977 increased reliability. If you rely on (insecurely) NFS
1978 mounting across a firewall you may need to update your
1982 Belatedly note the addition of m_collapse for compacting
1986 The fts(3) structures have been changed to use adequate
1987 integer types for their members and so to be able to cope
1988 with huge file trees. The old fts(3) ABI is preserved
1989 through symbol versioning in libc, so third-party binaries
1990 using fts(3) should still work, although they will not take
1991 advantage of the extended types. At the same time, some
1992 third-party software might fail to build after this change
1993 due to unportable assumptions made in its source code about
1994 fts(3) structure members. Such software should be fixed
1995 by its vendor or, in the worst case, in the ports tree.
1996 FreeBSD_version 800015 marks this change for the unlikely
1997 case that a portable fix is impossible.
2000 To upgrade to -current after this date, you must be running
2001 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2002 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2005 The ADAPTIVE_GIANT kernel option has been retired because its
2006 functionality is the default now.
2009 The AT keyboard emulation of sunkbd(4) has been turned on
2010 by default. In order to make the special symbols of the Sun
2011 keyboards driven by sunkbd(4) work under X these now have
2012 to be configured the same way as Sun USB keyboards driven
2013 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2015 Option "XkbLayout" "us"
2016 Option "XkbRules" "xorg"
2017 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2020 It has been decided that it is desirable to provide ABI
2021 backwards compatibility to the FreeBSD 4/5/6 versions of the
2022 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2023 broken with the introduction of PCI domain support (see the
2024 20070930 entry). Unfortunately, this required the ABI of
2025 PCIOCGETCONF to be broken again in order to be able to
2026 provide backwards compatibility to the old version of that
2027 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2028 again. As for prominent ports this affects neither pciutils
2029 nor xorg-server this time, the hal port needs to be rebuilt
2033 The misnamed kthread_create() and friends have been renamed
2034 to kproc_create() etc. Many of the callers already
2035 used kproc_start()..
2036 I will return kthread_create() and friends in a while
2037 with implementations that actually create threads, not procs.
2038 Renaming corresponds with version 800002.
2047 Avoid using make -j when upgrading. While generally safe, there are
2048 sometimes problems using -j to upgrade. If your upgrade fails with
2049 -j, please try again without -j. From time to time in the past there
2050 have been problems using -j with buildworld and/or installworld. This
2051 is especially true when upgrading between "distant" versions (eg one
2052 that cross a major release boundary or several minor releases, or when
2053 several months have passed on the -current branch).
2055 Sometimes, obscure build problems are the result of environment
2056 poisoning. This can happen because the make utility reads its
2057 environment when searching for values for global variables. To run
2058 your build attempts in an "environmental clean room", prefix all make
2059 commands with 'env -i '. See the env(1) manual page for more details.
2061 When upgrading from one major version to another it is generally best
2062 to upgrade to the latest code in the currently installed branch first,
2063 then do an upgrade to the new branch. This is the best-tested upgrade
2064 path, and has the highest probability of being successful. Please try
2065 this approach before reporting problems with a major version upgrade.
2067 When upgrading a live system, having a root shell around before
2068 installing anything can help undo problems. Not having a root shell
2069 around can lead to problems if pam has changed too much from your
2070 starting point to allow continued authentication after the upgrade.
2074 When upgrading the boot ZFS pool to a new version, always follow
2077 1.) recompile and reinstall the ZFS boot loader and boot block
2078 (this is part of "make buildworld" and "make installworld")
2080 2.) update the ZFS boot block on your boot drive
2082 The following example updates the ZFS boot block on the first
2083 partition (freebsd-boot) of a GPT partitioned drive ad0:
2084 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2086 Non-boot pools do not need these updates.
2090 If you are updating from a prior version of FreeBSD (even one just
2091 a few days old), you should follow this procedure. It is the most
2092 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2094 make kernel-toolchain
2095 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2096 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2098 To test a kernel once
2099 ---------------------
2100 If you just want to boot a kernel once (because you are not sure
2101 if it works, or if you want to boot a known bad kernel to provide
2102 debugging information) run
2103 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2104 nextboot -k testkernel
2106 To just build a kernel when you know that it won't mess you up
2107 --------------------------------------------------------------
2108 This assumes you are already running a CURRENT system. Replace
2109 ${arch} with the architecture of your machine (e.g. "i386",
2110 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2112 cd src/sys/${arch}/conf
2113 config KERNEL_NAME_HERE
2114 cd ../compile/KERNEL_NAME_HERE
2119 If this fails, go to the "To build a kernel" section.
2121 To rebuild everything and install it on the current system.
2122 -----------------------------------------------------------
2123 # Note: sometimes if you are running current you gotta do more than
2124 # is listed here if you are upgrading from a really old current.
2126 <make sure you have good level 0 dumps>
2128 make kernel KERNCONF=YOUR_KERNEL_HERE
2130 <reboot in single user> [3]
2137 To cross-install current onto a separate partition
2138 --------------------------------------------------
2139 # In this approach we use a separate partition to hold
2140 # current's root, 'usr', and 'var' directories. A partition
2141 # holding "/", "/usr" and "/var" should be about 2GB in
2144 <make sure you have good level 0 dumps>
2147 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2148 <maybe newfs current's root partition>
2149 <mount current's root partition on directory ${CURRENT_ROOT}>
2150 make installworld DESTDIR=${CURRENT_ROOT}
2151 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2152 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2153 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2154 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2155 <reboot into current>
2156 <do a "native" rebuild/install as described in the previous section>
2157 <maybe install compatibility libraries from ports/misc/compat*>
2161 To upgrade in-place from stable to current
2162 ----------------------------------------------
2163 <make sure you have good level 0 dumps>
2165 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2167 <reboot in single user> [3]
2174 Make sure that you've read the UPDATING file to understand the
2175 tweaks to various things you need. At this point in the life
2176 cycle of current, things change often and you are on your own
2177 to cope. The defaults can also change, so please read ALL of
2178 the UPDATING entries.
2180 Also, if you are tracking -current, you must be subscribed to
2181 freebsd-current@freebsd.org. Make sure that before you update
2182 your sources that you have read and understood all the recent
2183 messages there. If in doubt, please track -stable which has
2184 much fewer pitfalls.
2186 [1] If you have third party modules, such as vmware, you
2187 should disable them at this point so they don't crash your
2190 [3] From the bootblocks, boot -s, and then do
2195 adjkerntz -i # if CMOS is wall time
2196 Also, when doing a major release upgrade, it is required that
2197 you boot into single user mode to do the installworld.
2199 [4] Note: This step is non-optional. Failure to do this step
2200 can result in a significant reduction in the functionality of the
2201 system. Attempting to do it by hand is not recommended and those
2202 that pursue this avenue should read this file carefully, as well
2203 as the archives of freebsd-current and freebsd-hackers mailing lists
2204 for potential gotchas. The -U option is also useful to consider.
2205 See mergemaster(8) for more information.
2207 [5] Usually this step is a noop. However, from time to time
2208 you may need to do this if you get unknown user in the following
2209 step. It never hurts to do it all the time. You may need to
2210 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2211 install) after the buildworld before this step if you last updated
2212 from current before 20130425 or from -stable before 20130430.
2214 [6] This only deletes old files and directories. Old libraries
2215 can be deleted by "make delete-old-libs", but you have to make
2216 sure that no program is using those libraries anymore.
2218 [8] In order to have a kernel that can run the 4.x binaries needed to
2219 do an installworld, you must include the COMPAT_FREEBSD4 option in
2220 your kernel. Failure to do so may leave you with a system that is
2221 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2222 required to run the 5.x binaries on more recent kernels. And so on
2223 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2225 Make sure that you merge any new devices from GENERIC since the
2226 last time you updated your kernel config file.
2228 [9] When checking out sources, you must include the -P flag to have
2229 cvs prune empty directories.
2231 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2232 "?=" instead of the "=" assignment operator, so that buildworld can
2233 override the CPUTYPE if it needs to.
2235 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2236 not on the command line, or in /etc/make.conf. buildworld will
2237 warn if it is improperly defined.
2240 This file contains a list, in reverse chronological order, of major
2241 breakages in tracking -current. It is not guaranteed to be a complete
2242 list of such breakages, and only contains entries since October 10, 2007.
2243 If you need to see UPDATING entries from before that date, you will need
2244 to fetch an UPDATING file from an older FreeBSD release.
2246 Copyright information:
2248 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2250 Redistribution, publication, translation and use, with or without
2251 modification, in full or in part, in any form or format of this
2252 document are permitted without further permission from the author.
2254 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2255 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2256 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2257 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2258 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2259 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2260 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2261 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2262 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2263 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2264 POSSIBILITY OF SUCH DAMAGE.
2266 Contact Warner Losh if you have any questions about your use of