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 20160130 p12 FreeBSD-SA-16:11.openssl
21 Fix OpenSSL SSLv2 ciphersuite downgrade vulnerability. [SA-16:11]
23 20160127 p11 FreeBSD-SA-16:09.ntp
24 FreeBSD-SA-16:10.linux
26 Fix multiple vulnerabilities of ntp. [SA-16:09]
28 Fix Linux compatibility layer issetugid(2) system call
29 vulnerability. [SA-16:10]
31 20160114 p10 FreeBSD-SA-16:07.openssh
33 Fix OpenSSH client information leak. [SA-16:07]
35 20160114 p9 FreeBSD-EN-16:01.filemon
37 FreeBSD-EN-16:03.yplib
40 FreeBSD-SA-16:03.linux
41 FreeBSD-SA-16:04.linux
43 FreeBSD-SA-16:06.bsnmpd
45 Fix multiple stability and locking problems in filemon(4). [EN-16:01]
46 Fix pf(4) generating bad TCP checksums. [EN-16:02]
47 Fix infinite loop in YP/NIS client library. [EN-16:03]
48 Fix remote denial of service in SCTP. [SA-16:01]
49 Update NTP to 4.2.8p5. [SA-16:02]
50 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
51 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
52 Fix crash in TCP MD5 signatures. [SA-16:05]
53 Fix insecure default permissions for snmpd.config. [SA-16:06]
55 20151205 p8 FreeBSD-SA-15:26.openssl
57 Fix multiple OpenSSL vulnerabilities. [SA-15:26]
59 20151104 p7 FreeBSD-SA-15:25.ntp [revised]
60 FreeBSD-EN-15:19.kqueue
63 Fix regression in ntpd(8) lacking support for RAWDCF reference
64 clock in 10.2-RELEASE-p6. [SA-15:25]
66 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
68 Fix applications exiting due to segmentation violation on a correct
69 memory address. [EN-15:20.vm]
71 20151026: p6 FreeBSD-SA-15:25.ntp
73 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
75 20151002: p5 FreeBSD-SA-15:24.rpcbind [revised]
76 Revised patch to address a regression that prevents NIS from working.
78 20150929: p4 FreeBSD-SA-15:24.rpcbind
80 Fix rpcbind(8) remote denial of service. [SA-15:24]
82 20150916: p3 FreeBSD-EN-15:16.pw
86 Fix regression in pw(8) when creating numeric users or groups.
89 Fix libc handling of signals for multi-threaded processes.
92 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
94 20150825: p2 FreeBSD-SA-15:22.openssh
96 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
98 Fix insufficient check of unsupported pkg(7) signature methods.
101 20150818: p1 FreeBSD-SA-15:20.expat
102 FreeBSD-EN-15:11.toolchain
103 FreeBSD-EN-15:12.netstat
104 FreeBSD-EN-15:13.vidcontrol
106 Fix multiple integer overflows in expat (libbsdxml) XML parser.
109 Fix make(1) syntax errors when upgrading from 9.x and earlier.
112 Fix incorrect netstat(1) data handling on 32-bit systems.
115 Allow size argument to vidcontrol(1) for syscons(4). [EN-15:13]
121 The default Unbound configuration now enables remote control
122 using a local socket. Users who have already enabled the
123 local_unbound service should regenerate their configuration
124 by running "service local_unbound setup" as root.
127 An additional fix for the issue described in the 20150614 sendmail
128 entry below has been been committed in revision 284786.
131 The fix for the issue described in the 20150614 sendmail entry
132 below has been been committed in revision 284485. The work
133 around described in that entry is no longer needed unless the
134 default setting is overridden by a confDH_PARAMETERS configuration
135 setting of '5' or pointing to a 512 bit DH parameter file.
138 The import of openssl to address the FreeBSD-SA-15:10.openssl
139 security advisory includes a change which rejects handshakes
140 with DH parameters below 768 bits. sendmail releases prior
141 to 8.15.2 (not yet released), defaulted to a 512 bit
142 DH parameter setting for client connections. To work around
143 this interoperability, sendmail can be configured to use a
144 2048 bit DH parameter by:
146 1. Edit /etc/mail/`hostname`.mc
147 2. If a setting for confDH_PARAMETERS does not exist or
148 exists and is set to a string beginning with '5',
150 3. If a setting for confDH_PARAMETERS exists and is set to
151 a file path, create a new file with:
152 openssl dhparam -out /path/to/file 2048
153 4. Rebuild the .cf file:
154 cd /etc/mail/; make; make install
156 cd /etc/mail/; make restart
158 A sendmail patch is coming, at which time this file will be
162 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
163 defined in symlink(7); previously symlinks were silently ignored.
166 The const qualifier has been removed from iconv(3) to comply with
167 POSIX. The ports tree is aware of this from r384038 onwards.
170 At svn r275807, The default linux compat kernel ABI has been adjusted
171 to 2.6.18 in support of the linux-c6 compat ports infrastructure
172 update. If you wish to continue using the linux-f10 compat ports,
173 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
174 encouraged to update their linux-compat packages to linux-c6 during
175 their next update cycle.
177 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
180 pjdfstest has been integrated into kyua as an opt-in test suite.
181 Please see share/doc/pjdfstest/README for a more details on how to
188 The ofwfb driver, used to provide a graphics console on PowerPC when
189 using vt(4), no longer allows mmap() of all of physical memory. This
190 will prevent Xorg on PowerPC with some ATI graphics cards from
191 initializing properly unless x11-servers/xorg-server is updated to
195 The libatf-c and libatf-c++ major versions were downgraded to 0 and
196 1 respectively to match the upstream numbers. They were out of
197 sync because, when they were originally added to FreeBSD, the
198 upstream versions were not respected. These libraries are private
199 and not yet built by default, so renumbering them should be a
200 non-issue. However, unclean source trees will yield broken test
201 programs once the operator executes "make delete-old-libs" after a
204 Additionally, the atf-sh binary was made private by moving it into
205 /usr/libexec/. Already-built shell test programs will keep the
206 path to the old binary so they will break after "make delete-old"
209 If you are using WITH_TESTS=yes (not the default), wipe the object
210 tree and rebuild from scratch to prevent spurious test failures.
211 This is only needed once: the misnumbered libraries and misplaced
212 binaries have been added to OptionalObsoleteFiles.inc so they will
213 be removed during a clean upgrade.
216 The ixgbe tunables now match their sysctl counterparts, for example:
217 hw.ixgbe.enable_aim => hw.ix.enable_aim
218 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
221 The NFSv4.1 server committed by r269398 changes the internal
222 function call interfaces used between the NFS and krpc modules.
223 As such, __FreeBSD_version was bumped.
226 The default unbound configuration has been modified to address
227 issues with reverse lookups on networks that use private
228 address ranges. If you use the local_unbound service, run
229 "service local_unbound setup" as root to regenerate your
230 configuration, then "service local_unbound reload" to load the
234 It is no longer necessary to include the dwarf version in your DEBUG
235 options in your kernel config file. The bug that required it to be
236 placed in the config file has bene fixed. DEBUG should now just
237 contain -g. The build system will automatically update things
238 to do the right thing.
241 Several ABI breaking changes were merged to CTL and new iSCSI code.
242 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
243 iscsictl need to be rebuilt to work with a new kernel.
246 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
247 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
248 which differs from the behaviour controlled by this knob.)
251 On i386 and amd64 systems, the onifconsole flag is now set by default
252 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
253 as a login TTY if it is set in the bootloader as an active kernel
254 console. No changes in behavior should result otherwise. To revert to
255 the previous behavior, set ttyu0 to "off" in /etc/ttys.
258 Clang and llvm have been upgraded to 3.4.1 release.
261 Clang and llvm have been upgraded to 3.4 release.
264 If a Makefile in a tests/ directory was auto-generating a Kyuafile
265 instead of providing an explicit one, this would prevent such
266 Makefile from providing its own Kyuafile in the future during
267 NO_CLEAN builds. This has been fixed in the Makefiles but manual
268 intervention is needed to clean an objdir if you use NO_CLEAN:
269 # find /usr/obj -name Kyuafile | xargs rm -f
272 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
273 capability mode support. Please note that enabling the feature in
274 kernel is still highly recommended.
277 OpenSSH is now built with sandbox support, and will use sandbox as
278 the default privilege separation method. This requires Capsicum
279 capability mode support in kernel.
282 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
283 been deprecated and will not be part of FreeBSD 11.0 and later
284 releases. If you use this driver, please consider switching to
285 the nfe(4) driver instead.
291 The behavior of gss_pseudo_random() for the krb5 mechanism
292 has changed, for applications requesting a longer random string
293 than produced by the underlying enctype's pseudo-random() function.
294 In particular, the random string produced from a session key of
295 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
296 be different at the 17th octet and later, after this change.
297 The counter used in the PRF+ construction is now encoded as a
298 big-endian integer in accordance with RFC 4402.
299 __FreeBSD_version is bumped to 1000701.
302 The WITHOUT_ATF build knob has been removed and its functionality
303 has been subsumed into the more generic WITHOUT_TESTS. If you were
304 using the former to disable the build of the ATF libraries, you
305 should change your settings to use the latter.
308 The default version of mtree is nmtree which is obtained from
309 NetBSD. The output is generally the same, but may vary
310 slightly. If you found you need identical output adding
311 "-F freebsd9" to the command line should do the trick. For the
312 time being, the old mtree is available as fmtree.
315 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
316 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
317 1.1.4_8 and verify bsdyml not linked in, before running "make
319 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
321 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
324 The rc.d/jail script has been updated to support jail(8)
325 configuration file. The "jail_<jname>_*" rc.conf(5) variables
326 for per-jail configuration are automatically converted to
327 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
328 This is transparently backward compatible. See below about some
329 incompatibilities and rc.conf(5) manual page for more details.
331 These variables are now deprecated in favor of jail(8) configuration
332 file. One can use "rc.d/jail config <jname>" command to generate
333 a jail(8) configuration file in /var/run/jail.<jname>.conf without
334 running the jail(8) utility. The default pathname of the
335 configuration file is /etc/jail.conf and can be specified by
336 using $jail_conf or $jail_<jname>_conf variables.
338 Please note that jail_devfs_ruleset accepts an integer at
339 this moment. Please consider to rewrite the ruleset name
343 BIND has been removed from the base system. If all you need
344 is a local resolver, simply enable and start the local_unbound
345 service instead. Otherwise, several versions of BIND are
346 available in the ports tree. The dns/bind99 port is one example.
348 With this change, nslookup(1) and dig(1) are no longer in the base
349 system. Users should instead use host(1) and drill(1) which are
350 in the base system. Alternatively, nslookup and dig can
351 be obtained by installing the dns/bind-tools port.
354 With the addition of unbound(8), a new unbound user is now
355 required during installworld. "mergemaster -p" can be used to
356 add the user prior to installworld, as documented in the handbook.
359 OpenSSH is now built with DNSSEC support, and will by default
360 silently trust signed SSHFP records. This can be controlled with
361 the VerifyHostKeyDNS client configuration setting. DNSSEC support
362 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
365 The GNU Compiler Collection and C++ standard library (libstdc++)
366 are no longer built by default on platforms where clang is the system
367 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
371 The PROCDESC kernel option is now part of the GENERIC kernel
372 configuration and is required for the rwhod(8) to work.
373 If you are using custom kernel configuration, you should include
377 The API and ABI related to the Capsicum framework was modified
378 in backward incompatible way. The userland libraries and programs
379 have to be recompiled to work with the new kernel. This includes the
380 following libraries and programs, but the whole buildworld is
381 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
382 kdump, procstat, rwho, rwhod, uniq.
385 AES-NI intrinsic support has been added to gcc. The AES-NI module
386 has been updated to use this support. A new gcc is required to build
387 the aesni module on both i386 and amd64.
390 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
391 Thus "device padlock_rng" and "device rdrand_rng" should be
392 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
395 WITH_ICONV has been split into two feature sets. WITH_ICONV now
396 enables just the iconv* functionality and is now on by default.
397 WITH_LIBICONV_COMPAT enables the libiconv api and link time
398 compatability. Set WITHOUT_ICONV to build the old way.
399 If you have been using WITH_ICONV before, you will very likely
400 need to turn on WITH_LIBICONV_COMPAT.
403 INVARIANTS option now enables DEBUG for code with OpenSolaris and
404 Illumos origin, including ZFS. If you have INVARIANTS in your
405 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
407 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
408 locks if WITNESS option was set. Because that generated a lot of
409 witness(9) reports and all of them were believed to be false
410 positives, this is no longer done. New option OPENSOLARIS_WITNESS
411 can be used to achieve the previous behavior.
414 Timer values in IPv6 data structures now use time_uptime instead
415 of time_second. Although this is not a user-visible functional
416 change, userland utilities which directly use them---ndp(8),
417 rtadvd(8), and rtsold(8) in the base system---need to be updated
421 find -delete can now delete the pathnames given as arguments,
422 instead of only files found below them or if the pathname did
423 not contain any slashes. Formerly, the following error message
426 find: -delete: <path>: relative path potentially not safe
428 Deleting the pathnames given as arguments can be prevented
429 without error messages using -mindepth 1 or by changing
430 directory and passing "." as argument to find. This works in the
431 old as well as the new version of find.
434 Behavior of devfs rules path matching has been changed.
435 Pattern is now always matched against fully qualified devfs
436 path and slash characters must be explicitly matched by
437 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
438 subdirectories must be reviewed.
441 The default ARM ABI has changed to the ARM EABI. The old ABI is
442 incompatible with the ARM EABI and all programs and modules will
443 need to be rebuilt to work with a new kernel.
445 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
447 NOTE: Support for the old ABI will be removed in the future and
448 users are advised to upgrade.
451 pkg_install has been disconnected from the build if you really need it
452 you should add WITH_PKGTOOLS in your src.conf(5).
455 Most of network statistics structures were changed to be able
456 keep 64-bits counters. Thus all tools, that work with networking
457 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
460 Fix targets that run multiple make's to use && rather than ;
461 so that subsequent steps depend on success of previous.
463 NOTE: if building 'universe' with -j* on stable/8 or stable/9
464 it would be better to start the build using bmake, to avoid
465 overloading the machine.
468 Fix a bug that allowed a tracing process (e.g. gdb) to write
469 to a memory-mapped file in the traced process's address space
470 even if neither the traced process nor the tracing process had
471 write access to that file.
474 CVS has been removed from the base system. An exact copy
475 of the code is available from the devel/cvs port.
478 Some people report the following error after the switch to bmake:
480 make: illegal option -- J
481 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
483 *** [buildworld] Error code 2
485 this likely due to an old instance of make in
486 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
487 which src/Makefile will use that blindly, if it exists, so if
488 you see the above error:
490 rm -rf `make -V MAKEPATH`
495 Use bmake by default.
496 Whereas before one could choose to build with bmake via
497 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
498 make. The goal is to remove these knobs for 10-RELEASE.
500 It is worth noting that bmake (like gmake) treats the command
501 line as the unit of failure, rather than statements within the
502 command line. Thus '(cd some/where && dosomething)' is safer
503 than 'cd some/where; dosomething'. The '()' allows consistent
504 behavior in parallel build.
507 Fix a bug that allows NFS clients to issue READDIR on files.
510 The WITHOUT_IDEA option has been removed because
511 the IDEA patent expired.
514 The sysctl which controls TRIM support under ZFS has been renamed
515 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
519 The mergemaster command now uses the default MAKEOBJDIRPREFIX
520 rather than creating it's own in the temporary directory in
521 order allow access to bootstrapped versions of tools such as
522 install and mtree. When upgrading from version of FreeBSD where
523 the install command does not support -l, you will need to
524 install a new mergemaster command if mergemaster -p is required.
525 This can be accomplished with the command (cd src/usr.sbin/mergemaster
529 Legacy ATA stack, disabled and replaced by new CAM-based one since
530 FreeBSD 9.0, completely removed from the sources. Kernel modules
531 atadisk and atapi*, user-level tools atacontrol and burncd are
532 removed. Kernel option `options ATA_CAM` is now permanently enabled
536 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
537 and socketpair(2). Software, in particular Kerberos, may
538 automatically detect and use these during building. The resulting
539 binaries will not work on older kernels.
542 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
543 information, see the respective 20130304 entry).
546 Recent commits to callout(9) changed the size of struct callout,
547 so the KBI is probably heavily disturbed. Also, some functions
548 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
549 by macros. Every kernel module using it won't load, so rebuild
552 The ctl device has been re-enabled in GENERIC for i386 and amd64,
553 but does not initialize by default (because of the new CTL_DISABLE
554 option) to save memory. To re-enable it, remove the CTL_DISABLE
555 option from the kernel config file or set kern.cam.ctl.disable=0
556 in /boot/loader.conf.
559 The ctl device has been disabled in GENERIC for i386 and amd64.
560 This was done due to the extra memory being allocated at system
561 initialisation time by the ctl driver which was only used if
562 a CAM target device was created. This makes a FreeBSD system
563 unusable on 128MB or less of RAM.
566 A new compression method (lz4) has been merged to -HEAD. Please
567 refer to zpool-features(7) for more information.
569 Please refer to the "ZFS notes" section of this file for information
570 on upgrading boot ZFS pools.
573 A BSD-licensed patch(1) variant has been added and is installed
574 as bsdpatch, being the GNU version the default patch.
575 To inverse the logic and use the BSD-licensed one as default,
576 while having the GNU version installed as gnupatch, rebuild
577 and install world with the WITH_BSD_PATCH knob set.
580 Due to the use of the new -l option to install(1) during build
581 and install, you must take care not to directly set the INSTALL
582 make variable in your /etc/make.conf, /etc/src.conf, or on the
583 command line. If you wish to use the -C flag for all installs
584 you may be able to add INSTALL+=-C to /etc/make.conf or
588 The install(1) option -M has changed meaning and now takes an
589 argument that is a file or path to append logs to. In the
590 unlikely event that -M was the last option on the command line
591 and the command line contained at least two files and a target
592 directory the first file will have logs appended to it. The -M
593 option served little practical purpose in the last decade so its
594 use is expected to be extremely rare.
597 After switching to Clang as the default compiler some users of ZFS
598 on i386 systems started to experience stack overflow kernel panics.
599 Please consider using 'options KSTACK_PAGES=4' in such configurations.
602 GEOM_LABEL now mangles label names read from file system metadata.
603 Mangling affect labels containing spaces, non-printable characters,
604 '%' or '"'. Device names in /etc/fstab and other places may need to
608 By default, only the 10 most recent kernel dumps will be saved. To
609 restore the previous behaviour (no limit on the number of kernel dumps
610 stored in the dump directory) add the following line to /etc/rc.conf:
615 With the addition of auditdistd(8), a new auditdistd user is now
616 required during installworld. "mergemaster -p" can be used to
617 add the user prior to installworld, as documented in the handbook.
620 The sin6_scope_id member variable in struct sockaddr_in6 is now
621 filled by the kernel before passing the structure to the userland via
622 sysctl or routing socket. This means the KAME-specific embedded scope
623 id in sin6_addr.s6_addr[2] is always cleared in userland application.
624 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
625 __FreeBSD_version is bumped to 1000025.
628 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
629 This means that the world and kernel will be compiled with clang
630 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
631 and /usr/bin/cpp. To disable this behavior and revert to building
632 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
633 of current may need to bootstrap WITHOUT_CLANG first if the clang
634 build fails (its compatibility window doesn't extend to the 9 stable
638 The IPFIREWALL_FORWARD kernel option has been removed. Its
639 functionality now turned on by default.
642 The ZERO_COPY_SOCKET kernel option has been removed and
643 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
644 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
645 mechanism which is not safe and may result in kernel crashes.
646 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
647 driver supports disposeable external page sized mbuf storage.
648 Proper replacements for both zero-copy mechanisms are under
649 consideration and will eventually lead to complete removal
650 of the two kernel options.
653 The IPv4 network stack has been converted to network byte
654 order. The following modules need to be recompiled together
655 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
656 pf(4), ipfw(4), ng_ipfw(4), stf(4).
659 Support for non-MPSAFE filesystems was removed from VFS. The
660 VFS_VERSION was bumped, all filesystem modules shall be
664 All the non-MPSAFE filesystems have been disconnected from
665 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
666 portalfs, smbfs, xfs.
669 The interface cloning API and ABI has changed. The following
670 modules need to be recompiled together with kernel:
671 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
672 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
673 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
676 The sdhci driver was split in two parts: sdhci (generic SD Host
677 Controller logic) and sdhci_pci (actual hardware driver).
678 No kernel config modifications are required, but if you
679 load sdhc as a module you must switch to sdhci_pci instead.
682 Import the FUSE kernel and userland support into base system.
685 The GNU sort(1) program has been removed since the BSD-licensed
686 sort(1) has been the default for quite some time and no serious
687 problems have been reported. The corresponding WITH_GNU_SORT
691 The pfil(9) API/ABI for AF_INET family has been changed. Packet
692 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
696 The net80211(4) ABI has been changed to allow for improved driver
697 PS-POLL and power-save support. All wireless drivers need to be
698 recompiled to work with the new kernel.
701 The random(4) support for the VIA hardware random number
702 generator (`PADLOCK') is no longer enabled unconditionally.
703 Add the padlock_rng device in the custom kernel config if
704 needed. The GENERIC kernels on i386 and amd64 do include the
705 device, so the change only affects the custom kernel
709 The pf(4) packet filter ABI has been changed. pfctl(8) and
710 snmp_pf module need to be recompiled to work with new kernel.
713 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
714 to -HEAD. Pools that have empty_bpobj in active state can not be
715 imported read-write with ZFS implementations that do not support
716 this feature. For more information read the zpool-features(5)
720 The sparc64 ZFS loader has been changed to no longer try to auto-
721 detect ZFS providers based on diskN aliases but now requires these
722 to be explicitly listed in the OFW boot-device environment variable.
725 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
726 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
727 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
730 The following sysctls and tunables have been renamed for consistency
731 with other variables:
732 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
733 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
736 The sort utility has been replaced with BSD sort. For now, GNU sort
737 is also available as "gnusort" or the default can be set back to
738 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
739 installed as "bsdsort".
742 A new version of ZFS (pool version 5000) has been merged to -HEAD.
743 Starting with this version the old system of ZFS pool versioning
744 is superseded by "feature flags". This concept enables forward
745 compatibility against certain future changes in functionality of ZFS
746 pools. The first read-only compatible "feature flag" for ZFS pools
747 is named "com.delphix:async_destroy". For more information
748 read the new zpool-features(5) manual page.
749 Please refer to the "ZFS notes" section of this file for information
750 on upgrading boot ZFS pools.
753 The malloc(3) implementation embedded in libc now uses sources imported
754 as contrib/jemalloc. The most disruptive API change is to
755 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
756 delete it prior to installworld, and optionally re-create it using the
757 new format after rebooting. See malloc.conf(5) for details
758 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
762 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
763 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
764 now spelled mips. This is to aid compatibility with third-party
765 software that expects this naming scheme in uname(3). Little-endian
766 settings are unchanged. If you are updating a big-endian mips64 machine
767 from before this change, you may need to set MACHINE_ARCH=mips64 in
768 your environment before the new build system will recognize your machine.
771 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
775 Now unix domain sockets behave "as expected" on nullfs(5). Previously
776 nullfs(5) did not pass through all behaviours to the underlying layer,
777 as a result if we bound to a socket on the lower layer we could connect
778 only to the lower path; if we bound to the upper layer we could connect
779 only to the upper path. The new behavior is one can connect to both the
780 lower and the upper paths regardless what layer path one binds to.
783 The getifaddrs upgrade path broken with 20111215 has been restored.
784 If you have upgraded in between 20111215 and 20120209 you need to
785 recompile libc again with your kernel. You still need to recompile
786 world to be able to configure CARP but this restriction already
790 The set_rcvar() function has been removed from /etc/rc.subr. All
791 base and ports rc.d scripts have been updated, so if you have a
792 port installed with a script in /usr/local/etc/rc.d you can either
793 hand-edit the rcvar= line, or reinstall the port.
795 An easy way to handle the mass-update of /etc/rc.d:
796 rm /etc/rc.d/* && mergemaster -i
799 panic(9) now stops other CPUs in the SMP systems, disables interrupts
800 on the current CPU and prevents other threads from running.
801 This behavior can be reverted using the kern.stop_scheduler_on_panic
803 The new behavior can be incompatible with kern.sync_on_panic.
806 The carp(4) facility has been changed significantly. Configuration
807 of the CARP protocol via ifconfig(8) has changed, as well as format
808 of CARP events submitted to devd(8) has changed. See manual pages
809 for more information. The arpbalance feature of carp(4) is currently
810 not supported anymore.
812 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
813 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
814 need to be recompiled.
817 The acpi_wmi(4) status device /dev/wmistat has been renamed to
821 The option VFS_ALLOW_NONMPSAFE option has been added in order to
822 explicitely support non-MPSAFE filesystems.
823 It is on by default for all supported platform at this present
827 The broken amd(4) driver has been replaced with esp(4) in the amd64,
828 i386 and pc98 GENERIC kernel configuration files.
831 sysinstall has been removed
834 The stable/9 branch created in subversion. This corresponds to the
835 RELENG_9 branch in CVS.
838 This commit modifies vfs_register() so that it uses a hash
839 calculation to set vfc_typenum, which is enabled by default.
840 The first time a system is booted after this change, the
841 vfc_typenum values will change for all file systems. The
842 main effect of this is a change to the NFS server file handles
843 for file systems that use vfc_typenum in their fsid, such as ZFS.
844 It will, however, prevent vfc_typenum from changing when file
845 systems are loaded in a different order for subsequent reboots.
846 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
847 until you are ready to remount all NFS clients after a reboot.
850 Bump the shared library version numbers for libraries that
851 do not use symbol versioning, have changed the ABI compared
852 to stable/8 and which shared library version was not bumped.
853 Done as part of 9.0-RELEASE cycle.
856 During the merge of Capsicum features, the fget(9) KPI was modified.
857 This may require the rebuilding of out-of-tree device drivers --
858 issues have been reported specifically with the nVidia device driver.
859 __FreeBSD_version is bumped to 900041.
861 Also, there is a period between 20110811 and 20110814 where the
862 special devices /dev/{stdin,stdout,stderr} did not work correctly.
863 Building world from a kernel during that window may not work.
866 The packet filter (pf) code has been updated to OpenBSD 4.5.
867 You need to update userland tools to be in sync with kernel.
868 This update breaks backward compatibility with earlier pfsync(4)
869 versions. Care must be taken when updating redundant firewall setups.
872 The following sysctls and tunables are retired on x86 platforms:
874 machdep.hlt_logical_cpus
875 The following sysctl is retired:
876 machdep.hyperthreading_allowed
877 The sysctls were supposed to provide a way to dynamically offline and
878 online selected CPUs on x86 platforms, but the implementation has not
879 been reliable especially with SCHED_ULE scheduler.
880 machdep.hyperthreading_allowed tunable is still available to ignore
881 hyperthreading CPUs at OS level.
882 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
883 where X is an APIC ID of a CPU. Be advised, though, that disabling
884 CPUs in non-uniform fashion will result in non-uniform topology and
885 may lead to sub-optimal system performance with SCHED_ULE, which is
889 cpumask_t type is retired and cpuset_t is used in order to describe
893 Changes to ifconfig(8) for dynamic address family detection mandate
894 that you are running a kernel of 20110525 or later. Make sure to
895 follow the update procedure to boot a new kernel before installing
899 Support for sun4v architecture is officially dropped
902 Several KPI breaking changes have been committed to the mii(4) layer,
903 the PHY drivers and consequently some Ethernet drivers using mii(4).
904 This means that miibus.ko and the modules of the affected Ethernet
905 drivers need to be recompiled.
907 Note to kernel developers: Given that the OUI bit reversion problem
908 was fixed as part of these changes all mii(4) commits related to OUIs,
909 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
910 handling, no longer can be merged verbatim to stable/8 and previous
914 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
915 into their kernel configurations along with 'device pci'.
918 The default NFS client is now the new NFS client, so fstype "newnfs"
919 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
920 Although mounts via fstype "nfs" will usually work without userland
921 changes, it is recommended that the mount(8) and mount_nfs(8)
922 commands be rebuilt from sources and that a link to mount_nfs called
923 mount_oldnfs be created. The new client is compiled into the
924 kernel with "options NFSCL" and this is needed for diskless root
925 file systems. The GENERIC kernel configs have been changed to use
926 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
927 To use the regular/old client, you can "mount -t oldnfs ...". For
928 a diskless root file system, you must also include a line like:
930 vfs.root.mountfrom="oldnfs:"
932 in the boot/loader.conf on the root fs on the NFS server to make
933 a diskless root fs use the old client.
936 The GENERIC kernels for all architectures now default to the new
937 CAM-based ATA stack. It means that all legacy ATA drivers were
938 removed and replaced by respective CAM drivers. If you are using
939 ATA device names in /etc/fstab or other places, make sure to update
940 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
941 where 'Y's are the sequential numbers starting from zero for each type
942 in order of detection, unless configured otherwise with tunables,
943 see cam(4)). There will be symbolic links created in /dev/ to map
944 old adX devices to the respective adaY. They should provide basic
945 compatibility for file systems mounting in most cases, but they do
946 not support old user-level APIs and do not have respective providers
947 in GEOM. Consider using updated management tools with new device names.
949 It is possible to load devices ahci, ata, siis and mvs as modules,
950 but option ATA_CAM should remain in kernel configuration to make ata
951 module work as CAM driver supporting legacy ATA controllers. Device ata
952 still can be used in modular fashion (atacore + ...). Modules atadisk
953 and atapi* are not used and won't affect operation in ATA_CAM mode.
954 Note that to use CAM-based ATA kernel should include CAM devices
955 scbus, pass, da (or explicitly ada), cd and optionally others. All of
956 them are parts of the cam module.
958 ataraid(4) functionality is now supported by the RAID GEOM class.
959 To use it you can load geom_raid kernel module and use graid(8) tool
960 for management. Instead of /dev/arX device names, use /dev/raid/rX.
962 No kernel config options or code have been removed, so if a problem
963 arises, please report it and optionally revert to the old ATA stack.
964 In order to do it you can remove from the kernel config:
969 , and instead add back:
970 device atadisk # ATA disk drives
971 device ataraid # ATA RAID drives
972 device atapicd # ATAPI CDROM drives
973 device atapifd # ATAPI floppy drives
974 device atapist # ATAPI tape drives
977 The default NFS server has been changed to the new server, which
978 was referred to as the experimental server. If you need to switch
979 back to the old NFS server, you must now put the "-o" option on
980 both the mountd and nfsd commands. This can be done using the
981 mountd_flags and nfs_server_flags rc.conf variables until an
982 update to the rc scripts is committed, which is coming soon.
985 The GNU Objective-C runtime library (libobjc), and other Objective-C
986 related components have been removed from the base system. If you
987 require an Objective-C library, please use one of the available ports.
990 ath(4) has been split into bus- and device- modules. if_ath contains
991 the HAL, the TX rate control and the network device code. if_ath_pci
992 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
993 contains the AHB glue. Users need to load both if_ath_pci and if_ath
994 in order to use ath on everything else.
996 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
997 need to load if_ath and if_ath_pci for ath(4) operation.
1000 As part of the replacement of sysinstall, the process of building
1001 release media has changed significantly. For details, please re-read
1002 release(7), which has been updated to reflect the new build process.
1005 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1006 is the last available version under GPLv2. It brings a number of new
1007 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1008 4.1 and SSE 4.2), better support for powerpc64, a number of new
1009 directives, and lots of other small improvements. See the ChangeLog
1010 file in contrib/binutils for the full details.
1013 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1014 compliant, and will now use half of hash for authentication.
1015 This will break interoperability with all stacks (including all
1016 actual FreeBSD versions) who implement
1017 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1019 The only workaround with such peers is to use another HMAC
1020 algorithm for IPsec ("phase 2") authentication.
1023 Remove the uio_yield prototype and symbol. This function has
1024 been misnamed since it was introduced and should not be
1025 globally exposed with this name. The equivalent functionality
1026 is now available using kern_yield(curthread->td_user_pri).
1027 The function remains undocumented.
1030 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1031 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1032 for scalar sysctls is defined but disabled. Code that needs
1033 UQUAD to pass the type checking that must compile on older
1034 systems where the define is not present can check against
1035 __FreeBSD_version >= 900030.
1037 The system dialog(1) has been replaced with a new version previously
1038 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1039 with the previous version, but the libdialog associated with it has
1040 a largely incompatible API. As such, the original version of libdialog
1041 will be kept temporarily as libodialog, until its base system consumers
1042 are replaced or updated. Bump __FreeBSD_version to 900030.
1045 If you are trying to run make universe on a -stable system, and you get
1046 the following warning:
1047 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1048 unknown. config(8) likely too old."
1049 or something similar to it, then you must upgrade your -stable system
1050 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1051 stable/8) or build the config from the latest stable/8 branch and
1052 install it on your system.
1054 Prior to this date, building a current universe on 8-stable system from
1055 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1056 error in the first kernel build phase. A new config on those old
1057 systems will fix that problem for older versions of -current.
1060 The TCP stack has been modified to allow Khelp modules to interact with
1061 it via helper hook points and store per-connection data in the TCP
1062 control block. Bump __FreeBSD_version to 900029. User space tools that
1063 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1067 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1068 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1069 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1070 to take advantage of it instead of using custom implementations. This
1071 means that these drivers now no longer unconditionally advertise
1072 support for flow control but only do so if flow control is a selected
1073 media option. This was implemented in the generic support that way in
1074 order to allow flow control to be switched on and off via ifconfig(8)
1075 with the PHY specific default to typically off in order to protect
1076 from unwanted effects. Consequently, if you used flow control with
1077 one of the above mentioned drivers you now need to explicitly enable
1078 it, for example via:
1079 ifconfig bge0 media auto mediaopt flowcontrol
1081 Along with the above mentioned changes generic support for setting
1082 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1083 e1000phy(4) as well as ip1000phy(4) have been converted to take
1084 advantage of it. This means that these drivers now no longer take the
1085 link0 parameter for selecting master mode but the master media option
1086 has to be used instead, for example like in the following:
1087 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1089 Selection of master mode now is also available with all other PHY
1090 drivers supporting 1000baseT.
1093 The TCP stack has received a significant update to add support for
1094 modularised congestion control and generally improve the clarity of
1095 congestion control decisions. Bump __FreeBSD_version to 900025. User
1096 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1097 sockstat) need to be recompiled.
1100 The man(1) utility has been replaced by a new version that no longer
1101 uses /etc/manpath.config. Please consult man.conf(5) for how to
1102 migrate local entries to the new format.
1105 The copyright strings printed by login(1) and sshd(8) at the time of a
1106 new connection have been removed to follow other operating systems and
1110 A workaround for a fixed ld bug has been removed in kernel code,
1111 so make sure that your system ld is built from sources after
1112 revision 210245 from 2010-07-19 (r211583 if building head kernel
1113 on stable/8, r211584 for stable/7; both from 2010-08-21).
1114 A symptom of incorrect ld version is different addresses for
1115 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1118 The $ipv6_prefer variable in rc.conf(5) has been split into
1119 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1121 The $ip6addrctl_policy is a variable to choose a pre-defined
1122 address selection policy set by ip6addrctl(8). A value
1123 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1126 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1127 flag (see an entry of 20090926) is set on an interface with no
1128 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1129 security reason. If you want IPv6 link-local address on all
1130 interfaces by default, set this to "YES".
1132 The old ipv6_prefer="YES" is equivalent to
1133 ipv6_activate_all_interfaces="YES" and
1134 ip6addrctl_policy="ipv6_prefer".
1137 DTrace has grown support for userland tracing. Due to this, DTrace is
1138 now i386 and amd64 only.
1139 dtruss(1) is now installed by default on those systems and a new
1140 kernel module is needed for userland tracing: fasttrap.
1141 No changes to your kernel config file are necessary to enable
1142 userland tracing, but you might consider adding 'STRIP=' and
1143 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1144 to have informative userland stack traces in DTrace (ustack).
1147 The acpi_aiboost(4) driver has been removed in favor of the new
1148 aibs(4) driver. You should update your kernel configuration file.
1151 BSD grep has been imported to the base system and it is built by
1152 default. It is completely BSD licensed, highly GNU-compatible, uses
1153 less memory than its GNU counterpart and has a small codebase.
1154 However, it is slower than its GNU counterpart, which is mostly
1155 noticeable for larger searches, for smaller ones it is measurable
1156 but not significant. The reason is complex, the most important factor
1157 is that we lack a modern and efficient regex library and GNU
1158 overcomes this by optimizing the searches internally. Future work
1159 on improving the regex performance is planned, for the meantime,
1160 users that need better performance, can build GNU grep instead by
1161 setting the WITH_GNU_GREP knob.
1164 Due to the import of powerpc64 support, all existing powerpc kernel
1165 configuration files must be updated with a machine directive like this:
1166 machine powerpc powerpc
1168 In addition, an updated config(8) is required to build powerpc kernels
1172 A new version of ZFS (version 15) has been merged to -HEAD.
1173 This version uses a python library for the following subcommands:
1174 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1175 For full functionality of these commands the following port must
1176 be installed: sysutils/py-zfs
1179 'vm_page's are now hashed by physical address to an array of mutexes.
1180 Currently this is only used to serialize access to hold_count. Over
1181 time the page queue mutex will be peeled away. This changes the size
1182 of pmap on every architecture. And requires all callers of vm_page_hold
1183 and vm_page_unhold to be updated.
1186 WITH_CTF can now be specified in src.conf (not recommended, there
1187 are some problems with static executables), make.conf (would also
1188 affect ports which do not use GNU make and do not override the
1189 compile targets) or in the kernel config (via "makeoptions
1191 When WITH_CTF was specified there before this was silently ignored,
1192 so make sure that WITH_CTF is not used in places which could lead
1193 to unwanted behavior.
1196 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1197 to allow 32-bit compatibility on non-x86 platforms. All kernel
1198 configurations on amd64 and ia64 platforms using these options must
1199 be modified accordingly.
1202 The utmp user accounting database has been replaced with utmpx,
1203 the user accounting interface standardized by POSIX.
1204 Unfortunately the semantics of utmp and utmpx don't match,
1205 making it practically impossible to support both interfaces.
1206 The user accounting database is used by tools like finger(1),
1207 last(1), talk(1), w(1) and ac(8).
1209 All applications in the base system use utmpx. This means only
1210 local binaries (e.g. from the ports tree) may still use these
1211 utmp database files. These applications must be rebuilt to make
1214 After the system has been upgraded, it is safe to remove the old
1215 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1216 assuming their contents is of no importance anymore. Old wtmp
1217 databases can only be used by last(1) and ac(8) after they have
1218 been converted to the new format using wtmpcvt(1).
1221 Introduce the kernel thread "deadlock resolver" (which can be enabled
1222 via the DEADLKRES option, see NOTES for more details) and the
1223 sleepq_type() function for sleepqueues.
1226 The rc.firewall and rc.firewall6 were unified, and
1227 rc.firewall6 and rc.d/ip6fw were removed.
1228 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1229 variables are obsoleted. Instead, the following new rc
1230 variables are added to rc.d/ipfw:
1232 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1233 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1234 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1236 The meanings correspond to the relevant IPv4 variables.
1242 The default terminal emulation for syscons(4) has been changed
1243 from cons25 to xterm on all platforms except pc98. This means
1244 that the /etc/ttys file needs to be updated to ensure correct
1245 operation of applications on the console.
1247 The terminal emulation style can be toggled per window by using
1248 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1249 options can be used to change the compile-time default back to
1252 To prevent graphical artifacts, make sure the TERM environment
1253 variable is set to match the terminal emulation that is being
1254 performed by syscons(4).
1257 The layout of the structure ieee80211req_scan_result has changed.
1258 Applications that require wireless scan results (e.g. ifconfig(8))
1259 from net80211 need to be recompiled.
1261 Applications such as wpa_supplicant(8) may require a full world
1262 build without using NO_CLEAN in order to get synchronized with the
1266 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1267 There's one kernel module for each firmware. Adding "device iwnfw"
1268 to the kernel configuration file means including all three firmware
1269 images inside the kernel. If you want to include just the one for
1270 your wireless card, use the devices iwn4965fw, iwn5000fw or
1274 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1275 into rc.d/netif. The changes are the following:
1277 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1278 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1279 Note that both variables need the "inet6" keyword at the head.
1281 Do not set $ipv6_network_interfaces manually if you do not
1282 understand what you are doing. It is not needed in most cases.
1284 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1287 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1288 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1290 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1291 all configured interfaces have "inet6 accept_rtadv" in the
1292 $ifconfig_IF_ipv6. These are for backward compatibility.
1294 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1295 functionality of interfaces with no corresponding
1296 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1297 and the default address selection policy of ip6addrctl(8)
1298 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1299 Note that if you want to configure IPv6 functionality on the
1300 disabled interfaces after boot, first you need to clear the flag by
1301 using ifconfig(8) like:
1303 ifconfig em0 inet6 -ifdisabled
1305 If YES, the default address selection policy is set as
1308 The default value of $ipv6_prefer is NO.
1310 4. If your system need to receive Router Advertisement messages,
1311 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1312 scripts automatically invoke rtsol(8) when the interface becomes
1313 UP. The Router Advertisement messages are used for SLAAC
1314 (State-Less Address AutoConfiguration).
1317 802.11s D3.03 support was committed. This is incompatible with the
1318 previous code, which was based on D3.0.
1321 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1322 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1323 control whether accepting Router Advertisement messages or not.
1324 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1325 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1326 The ifconfig(8) utility now supports these flags.
1329 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1330 mount(8) and -a option for df(1) to see them.
1333 The old tunable hw.bus.devctl_disable has been superseded by
1334 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1335 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1339 Remove the option STOP_NMI. The default action is now to use NMI only
1340 for KDB via the newly introduced function stop_cpus_hard() and
1341 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1344 The stable/8 branch created in subversion. This corresponds to the
1345 RELENG_8 branch in CVS.
1348 Bump the shared library version numbers for all libraries that do not
1349 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1350 __FreeBSD_version to 800105.
1353 Due to changes in the implementation of virtual network stack support,
1354 all network-related kernel modules must be recompiled. As this change
1355 breaks the ABI, bump __FreeBSD_version to 800104.
1358 The TOE interface to the TCP syncache has been modified to remove
1359 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1360 The cxgb driver is the only TOE consumer affected by this change, and
1361 needs to be recompiled along with the kernel. As this change breaks
1362 the ABI, bump __FreeBSD_version to 800103.
1365 Padding has been added to struct tcpcb, sackhint and tcpstat in
1366 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1367 maintaining the ABI. However, this change breaks the ABI, so bump
1368 __FreeBSD_version to 800102. User space tools that rely on the size of
1369 any of these structs (e.g. sockstat) need to be recompiled.
1372 The NFS_LEGACYRPC option has been removed along with the old kernel
1373 RPC implementation that this option selected. Kernel configurations
1374 may need to be adjusted.
1377 The network interface device nodes at /dev/net/<interface> have been
1378 removed. All ioctl operations can be performed the normal way using
1379 routing sockets. The kqueue functionality can generally be replaced
1380 with routing sockets.
1383 The documentation from the FreeBSD Documentation Project (Handbook,
1384 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1385 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1388 The ABI of various structures related to the SYSV IPC API have been
1389 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1390 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1394 Layout of struct vnet has changed as routing related variables were
1395 moved to their own Vimage module. Modules need to be recompiled. Bump
1396 __FreeBSD_version to 800099.
1399 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1400 respectively. As long as no more than 16 groups per process are used,
1401 no changes should be visible. When more than 16 groups are used, old
1402 binaries may fail if they call getgroups() or getgrouplist() with
1403 statically sized storage. Recompiling will work around this, but
1404 applications should be modified to use dynamically allocated storage
1405 for group arrays as POSIX.1-2008 does not cap an implementation's
1406 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1408 NFS and portalfs mounts may also be affected as the list of groups is
1409 truncated to 16. Users of NFS who use more than 16 groups, should
1410 take care that negative group permissions are not used on the exported
1411 file systems as they will not be reliable unless a GSSAPI based
1412 authentication method is used.
1415 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1416 option compiles in the support for adaptive spinning for lockmgrs
1417 which want to enable it. The lockinit() function now accepts the flag
1418 LK_ADAPTIVE in order to make the lock object subject to adaptive
1419 spinning when both held in write and read mode.
1422 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1423 changed. User applications that use this ioctl need to be rebuilt.
1426 The layout of struct thread has changed. Kernel and modules need to
1430 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1431 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1434 window(1) has been removed from the base system. It can now be
1435 installed from ports. The port is called misc/window.
1438 The way we are storing and accessing `routing table' entries has
1439 changed. Programs reading the FIB, like netstat, need to be
1443 A new netisr implementation has been added for FreeBSD 8. Network
1444 file system modules, such as igmp, ipdivert, and others, should be
1446 Bump __FreeBSD_version to 800096.
1449 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1453 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1454 Bump __FreeBSD_version to 800094.
1457 Add mnt_xflag field to 'struct mount'. File system modules need to be
1459 Bump __FreeBSD_version to 800093.
1462 The compiling option ADAPTIVE_SX has been retired while it has been
1463 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1464 The KPI for sx_init_flags() changes as accepting flags:
1465 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1466 been introduced in order to handle the reversed logic.
1467 Bump __FreeBSD_version to 800092.
1470 Add support for hierarchical jails. Remove global securelevel.
1471 Bump __FreeBSD_version to 800091.
1474 The layout of struct vnet_net has changed, therefore modules
1476 Bump __FreeBSD_version to 800090.
1479 The newly imported zic(8) produces a new format in the output. Please
1480 run tzsetup(8) to install the newly created data to /etc/localtime.
1483 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1484 hw.usb.* and is now consistent again with previous releases.
1487 802.11 monitor mode support was revised and driver api's were changed.
1488 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1489 of DLT_IEEE802_11. No user-visible data structures were changed but
1490 applications that use DLT_IEEE802_11 may require changes.
1491 Bump __FreeBSD_version to 800088.
1494 The layout of the following structs has changed: sysctl_oid,
1495 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1496 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1497 panics may be experienced. World rebuild is required for
1498 correctly checking networking state from userland.
1499 Bump __FreeBSD_version to 800085.
1502 MLDv2 and Source-Specific Multicast (SSM) have been merged
1503 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1504 The implementation of SSM within FreeBSD's IPv6 stack closely
1505 follows the IPv4 implementation.
1507 For kernel developers:
1509 * The most important changes are that the ip6_output() and
1510 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1511 and this lock has been downgraded to a non-recursive mutex.
1513 * As with the changes to the IPv4 stack to support SSM, filtering
1514 of inbound multicast traffic must now be performed by transport
1515 protocols within the IPv6 stack. This does not apply to TCP and
1516 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1518 * The KPIs used by IPv6 multicast are similar to those used by
1519 the IPv4 stack, with the following differences:
1520 * im6o_mc_filter() is analogous to imo_multicast_filter().
1521 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1522 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1523 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1524 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1525 for MLDv1 have an additional 'timer' argument which is used to
1526 jitter the initial membership report for the solicited-node
1527 multicast membership on-link.
1528 * This is not strictly needed for MLDv2, which already jitters
1529 its report transmissions. However, the 'timer' argument is
1530 preserved in case MLDv1 is active on the interface.
1532 * The KAME linked-list based IPv6 membership implementation has
1533 been refactored to use a vector similar to that used by the IPv4
1535 Code which maintains a list of its own multicast memberships
1536 internally, e.g. carp, has been updated to reflect the new
1539 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1540 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1541 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1542 implementation constraint which needs to be addressed in HEAD.
1544 For application developers:
1546 * The changes are broadly similar to those made for the IPv4
1549 * The use of IPv4 and IPv6 multicast socket options on the same
1550 socket, using mapped addresses, HAS NOT been tested or supported.
1552 * There are a number of issues with the implementation of various
1553 IPv6 multicast APIs which need to be resolved in the API surface
1554 before the implementation is fully compatible with KAME userland
1555 use, and these are mostly to do with interface index treatment.
1557 * The literature available discusses the use of either the delta / ASM
1558 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1559 using setsourcefilter(3)/getsourcefilter(3). For more information
1560 please refer to RFC 3768, 'Socket Interface Extensions for
1561 Multicast Source Filters'.
1563 * Applications which use the published RFC 3678 APIs should be fine.
1565 For systems administrators:
1567 * The mtest(8) utility has been refactored to support IPv6, in
1568 addition to IPv4. Interface addresses are no longer accepted
1569 as arguments, their names must be used instead. The utility
1570 will map the interface name to its first IPv4 address as
1571 returned by getifaddrs(3).
1573 * The ifmcstat(8) utility has also been updated to print the MLDv2
1574 endpoint state and source filter lists via sysctl(3).
1576 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1577 loopback of IPv6 multicast datagrams by default; it defaults to 1
1578 to preserve the existing behaviour. Disabling multicast loopback is
1579 recommended for optimal system performance.
1581 * The IPv6 MROUTING code has been changed to examine this sysctl
1582 instead of attempting to perform a group lookup before looping
1583 back forwarded datagrams.
1585 Bump __FreeBSD_version to 800084.
1588 Implement low-level Bluetooth HCI API.
1589 Bump __FreeBSD_version to 800083.
1592 The layout of struct malloc_type, used by modules to register new
1593 memory allocation types, has changed. Most modules will need to
1594 be rebuilt or panics may be experienced.
1595 Bump __FreeBSD_version to 800081.
1598 Anticipate overflowing inp_flags - add inp_flags2.
1599 This changes most offsets in inpcb, so checking v4 connection
1600 state will require a world rebuild.
1601 Bump __FreeBSD_version to 800080.
1604 Add an llentry to struct route and struct route_in6. Modules
1605 embedding a struct route will need to be recompiled.
1606 Bump __FreeBSD_version to 800079.
1609 The size of rt_metrics_lite and by extension rtentry has changed.
1610 Networking administration apps will need to be recompiled.
1611 The route command now supports show as an alias for get, weighting
1612 of routes, sticky and nostick flags to alter the behavior of stateful
1614 Bump __FreeBSD_version to 800078.
1617 Do not use Giant for kbdmux(4) locking. This is wrong and
1618 apparently causing more problems than it solves. This will
1619 re-open the issue where interrupt handlers may race with
1620 kbdmux(4) in polling mode. Typical symptoms include (but
1621 not limited to) duplicated and/or missing characters when
1622 low level console functions (such as gets) are used while
1623 interrupts are enabled (for example geli password prompt,
1624 mountroot prompt etc.). Disabling kbdmux(4) may help.
1627 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1628 kernel modules referencing any of the above need to be recompiled.
1629 Bump __FreeBSD_version to 800075.
1632 GEOM_PART has become the default partition slicer for storage devices,
1633 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1634 introduces some changes:
1636 MSDOS/EBR: the devices created from MSDOS extended partition entries
1637 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1638 to devices with offset-based names. fstabs may need to be modified.
1640 BSD: the "geometry does not match label" warning is harmless in most
1641 cases but it points to problems in file system misalignment with
1642 disk geometry. The "c" partition is now implicit, covers the whole
1643 top-level drive and cannot be (mis)used by users.
1645 General: Kernel dumps are now not allowed to be written to devices
1646 whose partition types indicate they are meant to be used for file
1647 systems (or, in case of MSDOS partitions, as something else than
1650 Most of these changes date approximately from 200812.
1653 The uscanner(4) driver has been removed from the kernel. This follows
1654 Linux removing theirs in 2.6 and making libusb the default interface
1655 (supported by sane).
1658 The multicast forwarding code has been cleaned up. netstat(1)
1659 only relies on KVM now for printing bandwidth upcall meters.
1660 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1661 ip6_mroute_mod respectively. The config(5) options for statically
1662 compiling this code remain the same, i.e. 'options MROUTING'.
1665 Support for the IFF_NEEDSGIANT network interface flag has been
1666 removed, which means that non-MPSAFE network device drivers are no
1667 longer supported. In particular, if_ar, if_sr, and network device
1668 drivers from the old (legacy) USB stack can no longer be built or
1672 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1673 a bunch of new language catalog files have also been added.
1674 This means that some common libc messages are now localized and
1675 they depend on the LC_MESSAGES environmental variable.
1678 The k8temp(4) driver has been renamed to amdtemp(4) since
1679 support for Family 10 and Family 11 CPU families was added.
1682 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1683 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1685 For kernel developers, the most important changes are that the
1686 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1687 and this lock has been downgraded to a non-recursive mutex.
1689 Transport protocols (UDP, Raw IP) are now responsible for filtering
1690 inbound multicast traffic according to group membership and source
1691 filters. The imo_multicast_filter() KPI exists for this purpose.
1692 Transports which do not use multicast (SCTP, TCP) already reject
1693 multicast by default. Forwarding and receive performance may improve
1694 as a mutex acquisition is no longer needed in the ip_input()
1695 low-level input path. in_addmulti() and in_delmulti() are shimmed
1696 to new KPIs which exist to support SSM in-kernel.
1698 For application developers, it is recommended that loopback of
1699 multicast datagrams be disabled for best performance, as this
1700 will still cause the lock to be taken for each looped-back
1701 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1702 be tuned to 0 to disable loopback by default; it defaults to 1
1703 to preserve the existing behaviour.
1705 For systems administrators, to obtain best performance with
1706 multicast reception and multiple groups, it is always recommended
1707 that a card with a suitably precise hash filter is used. Hash
1708 collisions will still result in the lock being taken within the
1709 transport protocol input path to check group membership.
1711 If deploying FreeBSD in an environment with IGMP snooping switches,
1712 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1713 enabled; this forces 224.0.0.0/24 group membership to be announced
1716 The size of 'struct igmpstat' has changed; netstat needs to be
1717 recompiled to reflect this.
1718 Bump __FreeBSD_version to 800070.
1721 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1722 updated to use it. This requires a buildworld/installworld in order to
1723 update the library and dependencies (usbconfig, etc). Its advisable to
1724 rebuild all ports which uses libusb. More specific directions are given
1725 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1726 libusb are no longer required and can be removed.
1729 A workaround is committed to allow the creation of System V shared
1730 memory segment of size > 2 GB on the 64-bit architectures.
1731 Due to a limitation of the existing ABI, the shm_segsz member
1732 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1733 wrong for large segments. Note that limits must be explicitly
1734 raised to allow such segments to be created.
1737 The layout of struct ifnet has changed, requiring a rebuild of all
1738 network device driver modules.
1741 The /dev handling for the new USB stack has changed, a
1742 buildworld/installworld is required for libusb20.
1745 The new USB2 stack has now been permanently moved in and all kernel and
1746 module names reverted to their previous values (eg, usb, ehci, ohci,
1747 ums, ...). The old usb stack can be compiled in by prefixing the name
1748 with the letter 'o', the old usb modules have been removed.
1749 Updating entry 20090216 for xorg and 20090215 for libmap may still
1753 The rc.conf(5) option if_up_delay has been renamed to
1754 defaultroute_delay to better reflect its purpose. If you have
1755 customized this setting in /etc/rc.conf you need to update it to
1759 xorg 7.4 wants to configure its input devices via hald which does not
1760 yet work with USB2. If the keyboard/mouse does not work in xorg then
1762 Option "AllowEmptyInput" "off"
1763 to your ServerLayout section. This will cause X to use the configured
1764 kbd and mouse sections from your xorg.conf.
1767 The GENERIC kernels for all architectures now default to the new USB2
1768 stack. No kernel config options or code have been removed so if a
1769 problem arises please report it and optionally revert to the old USB
1770 stack. If you are loading USB kernel modules or have a custom kernel
1771 that includes GENERIC then ensure that usb names are also changed over,
1772 eg uftdi -> usb2_serial_ftdi.
1774 Older programs linked against the ports libusb 0.1 need to be
1775 redirected to the new stack's libusb20. /etc/libmap.conf can
1777 # Map old usb library to new one for usb2 stack
1778 libusb-0.1.so.8 libusb20.so.1
1781 All USB ethernet devices now attach as interfaces under the name ueN
1782 (eg. ue0). This is to provide a predictable name as vendors often
1783 change usb chipsets in a product without notice.
1786 The ichsmb(4) driver has been changed to require SMBus slave
1787 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1788 All of the other SMBus controller drivers require left-justified
1789 slave addresses, so this change makes all the drivers provide the
1793 INET6 statistics (struct ip6stat) was updated.
1794 netstat(1) needs to be recompiled.
1797 NTFS has been removed from GENERIC kernel on amd64 to match
1798 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1799 will load ntfs.ko module automatically when NTFS support is
1800 actually needed, unless ntfs.ko is not installed or security
1801 level prohibits loading kernel modules. If either is the case,
1802 "options NTFS" has to be added into kernel config.
1805 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1806 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1807 800061. User space tools that rely on the size of struct tcpcb in
1808 tcp_var.h (e.g. sockstat) need to be recompiled.
1811 ng_tty(4) module updated to match the new TTY subsystem.
1812 Due to API change, user-level applications must be updated.
1813 New API support added to mpd5 CVS and expected to be present
1814 in next mpd5.3 release.
1817 With __FreeBSD_version 800060 the makefs tool is part of
1818 the base system (it was a port).
1821 The afdata and ifnet locks have been changed from mutexes to
1822 rwlocks, network modules will need to be re-compiled.
1825 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1826 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1827 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1828 architecture and 40 bytes on 64-bit architecture. The userland
1829 applications "arp" and "ndp" have been updated accordingly.
1830 The output from "netstat -r" shows only routing entries and
1831 none of the L2 information.
1834 __FreeBSD_version 800057 marks the switchover from the
1835 binary ath hal to source code. Users must add the line:
1837 options AH_SUPPORT_AR5416
1839 to their kernel config files when specifying:
1843 The ath_hal module no longer exists; the code is now compiled
1844 together with the driver in the ath module. It is now
1845 possible to tailor chip support (i.e. reduce the set of chips
1846 and thereby the code size); consult ath_hal(4) for details.
1849 __FreeBSD_version 800054 adds memory barriers to
1850 <machine/atomic.h>, new interfaces to ifnet to facilitate
1851 multiple hardware transmit queues for cards that support
1852 them, and a lock-less ring-buffer implementation to
1853 enable drivers to more efficiently manage queueing of
1857 A new version of ZFS (version 13) has been merged to -HEAD.
1858 This version has zpool attribute "listsnapshots" off by
1859 default, which means "zfs list" does not show snapshots,
1860 and is the same as Solaris behavior.
1863 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1866 The uhci, ohci, ehci and slhci USB Host controller drivers have
1867 been put into separate modules. If you load the usb module
1868 separately through loader.conf you will need to load the
1869 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1870 controller add the following to loader.conf:
1876 The ABI used by the PMC toolset has changed. Please keep
1877 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1881 atapci kernel module now includes only generic PCI ATA
1882 driver. AHCI driver moved to ataahci kernel module.
1883 All vendor-specific code moved into separate kernel modules:
1884 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1885 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1886 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1887 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1890 The TTY subsystem of the kernel has been replaced by a new
1891 implementation, which provides better scalability and an
1892 improved driver model. Most common drivers have been migrated to
1893 the new TTY subsystem, while others have not. The following
1894 drivers have not yet been ported to the new TTY layer:
1897 cy, digi, rc, rp, sio
1903 ng_h4, ng_tty, ppp, sl, snp
1905 Adding these drivers to your kernel configuration file shall
1906 cause compilation to fail.
1909 ntpd has been upgraded to 4.2.4p5.
1912 OpenSSH has been upgraded to 5.1p1.
1914 For many years, FreeBSD's version of OpenSSH preferred DSA
1915 over RSA for host and user authentication keys. With this
1916 upgrade, we've switched to the vendor's default of RSA over
1917 DSA. This may cause upgraded clients to warn about unknown
1918 host keys even for previously known hosts. Users should
1919 follow the usual procedure for verifying host keys before
1920 accepting the RSA key.
1922 This can be circumvented by setting the "HostKeyAlgorithms"
1923 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1926 Please note that the sequence of keys offered for
1927 authentication has been changed as well. You may want to
1928 specify IdentityFile in a different order to revert this
1932 The sio(4) driver has been removed from the i386 and amd64
1933 kernel configuration files. This means uart(4) is now the
1934 default serial port driver on those platforms as well.
1936 To prevent collisions with the sio(4) driver, the uart(4) driver
1937 uses different names for its device nodes. This means the
1938 onboard serial port will now most likely be called "ttyu0"
1939 instead of "ttyd0". You may need to reconfigure applications to
1940 use the new device names.
1942 When using the serial port as a boot console, be sure to update
1943 /boot/device.hints and /etc/ttys before booting the new kernel.
1944 If you forget to do so, you can still manually specify the hints
1945 at the loader prompt:
1947 set hint.uart.0.at="isa"
1948 set hint.uart.0.port="0x3F8"
1949 set hint.uart.0.flags="0x10"
1950 set hint.uart.0.irq="4"
1954 The gpt(8) utility has been removed. Use gpart(8) to partition
1958 The version that Linuxulator emulates was changed from 2.4.2
1959 to 2.6.16. If you experience any problems with Linux binaries
1960 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1961 if it fixes the problem contact emulation mailing list.
1964 ISDN4BSD (I4B) was removed from the src tree. You may need to
1965 update a your kernel configuration and remove relevant entries.
1968 I have checked in code to support multiple routing tables.
1969 See the man pages setfib(1) and setfib(2).
1970 This is a hopefully backwards compatible version,
1971 but to make use of it you need to compile your kernel
1972 with options ROUTETABLES=2 (or more up to 16).
1975 The 802.11 wireless support was redone to enable multi-bss
1976 operation on devices that are capable. The underlying device
1977 is no longer used directly but instead wlanX devices are
1978 cloned with ifconfig. This requires changes to rc.conf files.
1979 For example, change:
1980 ifconfig_ath0="WPA DHCP"
1983 ifconfig_wlan0="WPA DHCP"
1984 see rc.conf(5) for more details. In addition, mergemaster of
1985 /etc/rc.d is highly recommended. Simultaneous update of userland
1986 and kernel wouldn't hurt either.
1988 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1989 modules were merged into the base wlan module. All references
1990 to these modules (e.g. in kernel config files) must be removed.
1993 psm(4) has gained write(2) support in native operation level.
1994 Arbitrary commands can be written to /dev/psm%d and status can
1995 be read back from it. Therefore, an application is responsible
1996 for status validation and error recovery. It is a no-op in
1997 other operation levels.
2000 Support for KSE threading has been removed from the kernel. To
2001 run legacy applications linked against KSE libmap.conf may
2002 be used. The following libmap.conf may be used to ensure
2003 compatibility with any prior release:
2005 libpthread.so.1 libthr.so.1
2006 libpthread.so.2 libthr.so.2
2007 libkse.so.3 libthr.so.3
2010 The layout of struct vmspace has changed. This affects libkvm
2011 and any executables that link against libkvm and use the
2012 kvm_getprocs() function. In particular, but not exclusively,
2013 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2014 The effects are minimal, but it's advisable to upgrade world
2018 The latest em driver no longer has support in it for the
2019 82575 adapter, this is now moved to the igb driver. The
2020 split was done to make new features that are incompatible
2021 with older hardware easier to do.
2024 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2025 likewise the kernel option is now GEOM_LINUX_LVM.
2028 The default NFS mount mode has changed from UDP to TCP for
2029 increased reliability. If you rely on (insecurely) NFS
2030 mounting across a firewall you may need to update your
2034 Belatedly note the addition of m_collapse for compacting
2038 The fts(3) structures have been changed to use adequate
2039 integer types for their members and so to be able to cope
2040 with huge file trees. The old fts(3) ABI is preserved
2041 through symbol versioning in libc, so third-party binaries
2042 using fts(3) should still work, although they will not take
2043 advantage of the extended types. At the same time, some
2044 third-party software might fail to build after this change
2045 due to unportable assumptions made in its source code about
2046 fts(3) structure members. Such software should be fixed
2047 by its vendor or, in the worst case, in the ports tree.
2048 FreeBSD_version 800015 marks this change for the unlikely
2049 case that a portable fix is impossible.
2052 To upgrade to -current after this date, you must be running
2053 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2054 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2057 The ADAPTIVE_GIANT kernel option has been retired because its
2058 functionality is the default now.
2061 The AT keyboard emulation of sunkbd(4) has been turned on
2062 by default. In order to make the special symbols of the Sun
2063 keyboards driven by sunkbd(4) work under X these now have
2064 to be configured the same way as Sun USB keyboards driven
2065 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2067 Option "XkbLayout" "us"
2068 Option "XkbRules" "xorg"
2069 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2072 It has been decided that it is desirable to provide ABI
2073 backwards compatibility to the FreeBSD 4/5/6 versions of the
2074 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2075 broken with the introduction of PCI domain support (see the
2076 20070930 entry). Unfortunately, this required the ABI of
2077 PCIOCGETCONF to be broken again in order to be able to
2078 provide backwards compatibility to the old version of that
2079 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2080 again. As for prominent ports this affects neither pciutils
2081 nor xorg-server this time, the hal port needs to be rebuilt
2085 The misnamed kthread_create() and friends have been renamed
2086 to kproc_create() etc. Many of the callers already
2087 used kproc_start()..
2088 I will return kthread_create() and friends in a while
2089 with implementations that actually create threads, not procs.
2090 Renaming corresponds with version 800002.
2099 Avoid using make -j when upgrading. While generally safe, there are
2100 sometimes problems using -j to upgrade. If your upgrade fails with
2101 -j, please try again without -j. From time to time in the past there
2102 have been problems using -j with buildworld and/or installworld. This
2103 is especially true when upgrading between "distant" versions (eg one
2104 that cross a major release boundary or several minor releases, or when
2105 several months have passed on the -current branch).
2107 Sometimes, obscure build problems are the result of environment
2108 poisoning. This can happen because the make utility reads its
2109 environment when searching for values for global variables. To run
2110 your build attempts in an "environmental clean room", prefix all make
2111 commands with 'env -i '. See the env(1) manual page for more details.
2113 When upgrading from one major version to another it is generally best
2114 to upgrade to the latest code in the currently installed branch first,
2115 then do an upgrade to the new branch. This is the best-tested upgrade
2116 path, and has the highest probability of being successful. Please try
2117 this approach before reporting problems with a major version upgrade.
2119 When upgrading a live system, having a root shell around before
2120 installing anything can help undo problems. Not having a root shell
2121 around can lead to problems if pam has changed too much from your
2122 starting point to allow continued authentication after the upgrade.
2126 When upgrading the boot ZFS pool to a new version, always follow
2129 1.) recompile and reinstall the ZFS boot loader and boot block
2130 (this is part of "make buildworld" and "make installworld")
2132 2.) update the ZFS boot block on your boot drive
2134 The following example updates the ZFS boot block on the first
2135 partition (freebsd-boot) of a GPT partitioned drive ad0:
2136 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2138 Non-boot pools do not need these updates.
2142 If you are updating from a prior version of FreeBSD (even one just
2143 a few days old), you should follow this procedure. It is the most
2144 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2146 make kernel-toolchain
2147 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2148 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2150 To test a kernel once
2151 ---------------------
2152 If you just want to boot a kernel once (because you are not sure
2153 if it works, or if you want to boot a known bad kernel to provide
2154 debugging information) run
2155 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2156 nextboot -k testkernel
2158 To just build a kernel when you know that it won't mess you up
2159 --------------------------------------------------------------
2160 This assumes you are already running a CURRENT system. Replace
2161 ${arch} with the architecture of your machine (e.g. "i386",
2162 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2164 cd src/sys/${arch}/conf
2165 config KERNEL_NAME_HERE
2166 cd ../compile/KERNEL_NAME_HERE
2171 If this fails, go to the "To build a kernel" section.
2173 To rebuild everything and install it on the current system.
2174 -----------------------------------------------------------
2175 # Note: sometimes if you are running current you gotta do more than
2176 # is listed here if you are upgrading from a really old current.
2178 <make sure you have good level 0 dumps>
2180 make kernel KERNCONF=YOUR_KERNEL_HERE
2182 <reboot in single user> [3]
2189 To cross-install current onto a separate partition
2190 --------------------------------------------------
2191 # In this approach we use a separate partition to hold
2192 # current's root, 'usr', and 'var' directories. A partition
2193 # holding "/", "/usr" and "/var" should be about 2GB in
2196 <make sure you have good level 0 dumps>
2199 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2200 <maybe newfs current's root partition>
2201 <mount current's root partition on directory ${CURRENT_ROOT}>
2202 make installworld DESTDIR=${CURRENT_ROOT}
2203 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2204 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2205 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2206 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2207 <reboot into current>
2208 <do a "native" rebuild/install as described in the previous section>
2209 <maybe install compatibility libraries from ports/misc/compat*>
2213 To upgrade in-place from stable to current
2214 ----------------------------------------------
2215 <make sure you have good level 0 dumps>
2217 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2219 <reboot in single user> [3]
2226 Make sure that you've read the UPDATING file to understand the
2227 tweaks to various things you need. At this point in the life
2228 cycle of current, things change often and you are on your own
2229 to cope. The defaults can also change, so please read ALL of
2230 the UPDATING entries.
2232 Also, if you are tracking -current, you must be subscribed to
2233 freebsd-current@freebsd.org. Make sure that before you update
2234 your sources that you have read and understood all the recent
2235 messages there. If in doubt, please track -stable which has
2236 much fewer pitfalls.
2238 [1] If you have third party modules, such as vmware, you
2239 should disable them at this point so they don't crash your
2242 [3] From the bootblocks, boot -s, and then do
2247 adjkerntz -i # if CMOS is wall time
2248 Also, when doing a major release upgrade, it is required that
2249 you boot into single user mode to do the installworld.
2251 [4] Note: This step is non-optional. Failure to do this step
2252 can result in a significant reduction in the functionality of the
2253 system. Attempting to do it by hand is not recommended and those
2254 that pursue this avenue should read this file carefully, as well
2255 as the archives of freebsd-current and freebsd-hackers mailing lists
2256 for potential gotchas. The -U option is also useful to consider.
2257 See mergemaster(8) for more information.
2259 [5] Usually this step is a noop. However, from time to time
2260 you may need to do this if you get unknown user in the following
2261 step. It never hurts to do it all the time. You may need to
2262 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2263 install) after the buildworld before this step if you last updated
2264 from current before 20130425 or from -stable before 20130430.
2266 [6] This only deletes old files and directories. Old libraries
2267 can be deleted by "make delete-old-libs", but you have to make
2268 sure that no program is using those libraries anymore.
2270 [8] In order to have a kernel that can run the 4.x binaries needed to
2271 do an installworld, you must include the COMPAT_FREEBSD4 option in
2272 your kernel. Failure to do so may leave you with a system that is
2273 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2274 required to run the 5.x binaries on more recent kernels. And so on
2275 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2277 Make sure that you merge any new devices from GENERIC since the
2278 last time you updated your kernel config file.
2280 [9] When checking out sources, you must include the -P flag to have
2281 cvs prune empty directories.
2283 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2284 "?=" instead of the "=" assignment operator, so that buildworld can
2285 override the CPUTYPE if it needs to.
2287 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2288 not on the command line, or in /etc/make.conf. buildworld will
2289 warn if it is improperly defined.
2292 This file contains a list, in reverse chronological order, of major
2293 breakages in tracking -current. It is not guaranteed to be a complete
2294 list of such breakages, and only contains entries since October 10, 2007.
2295 If you need to see UPDATING entries from before that date, you will need
2296 to fetch an UPDATING file from an older FreeBSD release.
2298 Copyright information:
2300 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2302 Redistribution, publication, translation and use, with or without
2303 modification, in full or in part, in any form or format of this
2304 document are permitted without further permission from the author.
2306 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2307 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2308 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2309 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2310 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2311 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2312 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2313 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2314 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2315 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2316 POSSIBILITY OF SUCH DAMAGE.
2318 Contact Warner Losh if you have any questions about your use of