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 20170427 p19 FreeBSD-SA-17:04.ipfilter
21 Fix ipfilter(4) fragment handling panic. [SA-17:04]
23 20170412 p18 FreeBSD-SA-17:03.ntp
26 Fix multiple vulnerabilities of ntp. [SA-17:03]
28 Xen migration enhancements. [EN-17:05]
30 20170223 p17 FreeBSD-SA-17:02.openssl
32 Fix OpenSSL RC4_MD5 cipher vulnerability.
34 20170111 p16 FreeBSD-SA-17:01.openssh
36 Fix multiple vulnerabilities of OpenSSH.
38 20161222 p15 FreeBSD-SA-16:39.ntp
40 Fix multiple vulnerabilities of ntp.
42 20161208 p14 FreeBSD-SA-16:37.libc [revised]
44 Fix regressions introduced by SA-16:37.libc.
46 20161206 p13 FreeBSD-SA-16:36.telnetd
48 FreeBSD-SA-16:38.bhyve
49 FreeBSD-EN-16:19.tzcode
50 FreeBSD-EN-16:20.tzdata
52 Fix possible login(1) argument injection in telnetd(8). [SA-16:36]
53 Fix link_ntoa(3) buffer overflow in libc. [SA-16:37]
54 Fix possible escape from bhyve(8) virtual machine. [SA-16:38]
55 Fix warnings about valid time zone abbreviations. [EN-16:19]
56 Update timezone database information. [EN-16:20]
58 20161102 p12 FreeBSD-SA-16:33.openssh
59 FreeBSD-SA-16:35.openssl
61 Fix OpenSSH remote Denial of Service vulnerability. [SA-16:33]
63 Fix OpenSSL remote DoS vulnerability. [SA-16:35]
65 20161025 p11 FreeBSD-SA-16:15.sysarch [revised]
68 Fix incorrect argument validation in sysarch(2). [SA-16:15]
69 Fix virtual memory subsystem bugs. [EN-16:17]
71 20161010 p10 FreeBSD-SA-16:29.bspatch
72 FreeBSD-SA-16:30.portsnap
73 FreeBSD-SA-16:31.libarchive
75 Fix bspatch heap overflow vulnerability. [SA-16:29]
77 Fix multiple portsnap vulnerabilities. [SA-16:30]
79 Fix multiple libarchive vulnerabilities. [SA-16:31]
81 20160926 p9 FreeBSD-SA-16:26.openssl [revised]
83 Fix OpenSSL regression introduced in SA-16:26.
85 20160923 p8 FreeBSD-SA-16:26.openssl
87 Fix multiple OpenSSL vulnerabilitites.
89 20160811 p7 FreeBSD-EN-16:10.dhclient
90 FreeBSD-EN-16:11.vmbus
91 FreeBSD-EN-16:12.hv_storvsc
92 FreeBSD-EN-16:13.vmbus
93 FreeBSD-EN-16:14.hv_storvsc
94 FreeBSD-EN-16:15.vmbus
95 FreeBSD-EN-16:16.hv_storvsc
97 Fix handling of unknown options from a DHCP server. [EN-16:10]
98 Fix a panic in hv_vmbus(4). [EN-16:11]
99 Fix missing hotplugged disk in hv_storvsc(4). [EN-16:12]
100 Fix the timecounter emulation in hv_vmbus(4). [EN-16:13]
101 Fix callout(9) handling in hv_storvsc(4). [EN-16:14]
102 Fix memory allocation issues in hv_vmbus(4). [EN-16:15]
103 Fix SCSI command handling in hv_storvsc(4). [EN-16:16]
105 20160725 p6 FreeBSD-SA-16:25.bspatch
106 FreeBSD-EN-16:09.freebsd-update
108 Fix bspatch heap overflow vulnerability. [SA-16:25]
110 Fix freebsd-update(8) support of FreeBSD 11.0 release
111 distribution. [EN-16:09]
113 20160604 p5 FreeBSD-SA-16:24.ntp
115 Fix multiple vulnerabilities of ntp.
117 20160531 p4 FreeBSD-SA-16:20.linux
118 FreeBSD-SA-16:21.43bsd
119 FreeBSD-SA-16:22.libarchive
121 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
122 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
123 Fix directory traversal in cpio(1). [SA-16:22]
126 20160517 p3 FreeBSD-SA-16:18.atkbd
127 FreeBSD-SA-16:19.sendmsg
129 Fix buffer overflow in keyboard driver. [SA-16:18]
131 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
133 20160504 p2 FreeBSD-SA-16:17.openssl
134 FreeBSD-EN-16:06.libc
138 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
140 Fix performance regression in libc hash(3). [EN-16:06]
142 Fix excessive latency in x86 IPI delivery. [EN-16:07]
144 Fix memory leak in ZFS. [EN-16:08]
146 20160429 p1 FreeBSD-SA-16:16.ntp
148 Fix multiple vulnerabilities of ntp.
154 The NONE and HPN patches has been removed from OpenSSH. They are
155 still available in the security/openssh-portable port.
158 r292223 changed the internal interface between the nfsd.ko and
159 nfscommon.ko modules. As such, they must both be upgraded to-gether.
160 __FreeBSD_version has been bumped because of this.
163 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
164 Kernel modules isp_2400_multi and isp_2500_multi were removed and
165 should be replaced with isp_2400 and isp_2500 modules respectively.
168 The menu.rc and loader.rc files will now be replaced during
169 upgrades. Please migrate local changes to menu.rc.local and
170 loader.rc.local instead.
173 NTP has been upgraded to 4.2.8p4.
176 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
177 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
178 and devel/kyua to version 0.20+ and adjust any calling code to work
179 with Kyuafile and kyua.
182 The polarity of Pulse Per Second (PPS) capture events with the
183 uart(4) driver has been corrected. Prior to this change the PPS
184 "assert" event corresponded to the trailing edge of a positive PPS
185 pulse and the "clear" event was the leading edge of the next pulse.
187 As the width of a PPS pulse in a typical GPS receiver is on the
188 order of 1 millisecond, most users will not notice any significant
189 difference with this change.
191 Anyone who has compensated for the historical polarity reversal by
192 configuring a negative offset equal to the pulse width will need to
193 remove that workaround.
196 From legacy ata(4) driver was removed support for SATA controllers
197 supported by more functional drivers ahci(4), siis(4) and mvs(4).
198 Kernel modules ataahci and ataadaptec were removed completely,
199 replaced by ahci and mvs modules respectively.
205 As ZFS requires more kernel stack pages than is the default on some
206 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
207 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
209 Please consider using 'options KSTACK_PAGES=X' where X is greater
210 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
213 The default Unbound configuration now enables remote control
214 using a local socket. Users who have already enabled the
215 local_unbound service should regenerate their configuration
216 by running "service local_unbound setup" as root.
219 An additional fix for the issue described in the 20150614 sendmail
220 entry below has been been committed in revision 284786.
223 The fix for the issue described in the 20150614 sendmail entry
224 below has been been committed in revision 284485. The work
225 around described in that entry is no longer needed unless the
226 default setting is overridden by a confDH_PARAMETERS configuration
227 setting of '5' or pointing to a 512 bit DH parameter file.
230 The import of openssl to address the FreeBSD-SA-15:10.openssl
231 security advisory includes a change which rejects handshakes
232 with DH parameters below 768 bits. sendmail releases prior
233 to 8.15.2 (not yet released), defaulted to a 512 bit
234 DH parameter setting for client connections. To work around
235 this interoperability, sendmail can be configured to use a
236 2048 bit DH parameter by:
238 1. Edit /etc/mail/`hostname`.mc
239 2. If a setting for confDH_PARAMETERS does not exist or
240 exists and is set to a string beginning with '5',
242 3. If a setting for confDH_PARAMETERS exists and is set to
243 a file path, create a new file with:
244 openssl dhparam -out /path/to/file 2048
245 4. Rebuild the .cf file:
246 cd /etc/mail/; make; make install
248 cd /etc/mail/; make restart
250 A sendmail patch is coming, at which time this file will be
254 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
255 defined in symlink(7); previously symlinks were silently ignored.
258 The const qualifier has been removed from iconv(3) to comply with
259 POSIX. The ports tree is aware of this from r384038 onwards.
262 At svn r275807, The default linux compat kernel ABI has been adjusted
263 to 2.6.18 in support of the linux-c6 compat ports infrastructure
264 update. If you wish to continue using the linux-f10 compat ports,
265 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
266 encouraged to update their linux-compat packages to linux-c6 during
267 their next update cycle.
269 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
272 pjdfstest has been integrated into kyua as an opt-in test suite.
273 Please see share/doc/pjdfstest/README for a more details on how to
280 The ofwfb driver, used to provide a graphics console on PowerPC when
281 using vt(4), no longer allows mmap() of all of physical memory. This
282 will prevent Xorg on PowerPC with some ATI graphics cards from
283 initializing properly unless x11-servers/xorg-server is updated to
287 The libatf-c and libatf-c++ major versions were downgraded to 0 and
288 1 respectively to match the upstream numbers. They were out of
289 sync because, when they were originally added to FreeBSD, the
290 upstream versions were not respected. These libraries are private
291 and not yet built by default, so renumbering them should be a
292 non-issue. However, unclean source trees will yield broken test
293 programs once the operator executes "make delete-old-libs" after a
296 Additionally, the atf-sh binary was made private by moving it into
297 /usr/libexec/. Already-built shell test programs will keep the
298 path to the old binary so they will break after "make delete-old"
301 If you are using WITH_TESTS=yes (not the default), wipe the object
302 tree and rebuild from scratch to prevent spurious test failures.
303 This is only needed once: the misnumbered libraries and misplaced
304 binaries have been added to OptionalObsoleteFiles.inc so they will
305 be removed during a clean upgrade.
308 The ixgbe tunables now match their sysctl counterparts, for example:
309 hw.ixgbe.enable_aim => hw.ix.enable_aim
310 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
313 The NFSv4.1 server committed by r269398 changes the internal
314 function call interfaces used between the NFS and krpc modules.
315 As such, __FreeBSD_version was bumped.
318 The default unbound configuration has been modified to address
319 issues with reverse lookups on networks that use private
320 address ranges. If you use the local_unbound service, run
321 "service local_unbound setup" as root to regenerate your
322 configuration, then "service local_unbound reload" to load the
326 It is no longer necessary to include the dwarf version in your DEBUG
327 options in your kernel config file. The bug that required it to be
328 placed in the config file has bene fixed. DEBUG should now just
329 contain -g. The build system will automatically update things
330 to do the right thing.
333 Several ABI breaking changes were merged to CTL and new iSCSI code.
334 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
335 iscsictl need to be rebuilt to work with a new kernel.
338 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
339 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
340 which differs from the behaviour controlled by this knob.)
343 On i386 and amd64 systems, the onifconsole flag is now set by default
344 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
345 as a login TTY if it is set in the bootloader as an active kernel
346 console. No changes in behavior should result otherwise. To revert to
347 the previous behavior, set ttyu0 to "off" in /etc/ttys.
350 Clang and llvm have been upgraded to 3.4.1 release.
353 Clang and llvm have been upgraded to 3.4 release.
356 If a Makefile in a tests/ directory was auto-generating a Kyuafile
357 instead of providing an explicit one, this would prevent such
358 Makefile from providing its own Kyuafile in the future during
359 NO_CLEAN builds. This has been fixed in the Makefiles but manual
360 intervention is needed to clean an objdir if you use NO_CLEAN:
361 # find /usr/obj -name Kyuafile | xargs rm -f
364 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
365 capability mode support. Please note that enabling the feature in
366 kernel is still highly recommended.
369 OpenSSH is now built with sandbox support, and will use sandbox as
370 the default privilege separation method. This requires Capsicum
371 capability mode support in kernel.
374 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
375 been deprecated and will not be part of FreeBSD 11.0 and later
376 releases. If you use this driver, please consider switching to
377 the nfe(4) driver instead.
383 The behavior of gss_pseudo_random() for the krb5 mechanism
384 has changed, for applications requesting a longer random string
385 than produced by the underlying enctype's pseudo-random() function.
386 In particular, the random string produced from a session key of
387 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
388 be different at the 17th octet and later, after this change.
389 The counter used in the PRF+ construction is now encoded as a
390 big-endian integer in accordance with RFC 4402.
391 __FreeBSD_version is bumped to 1000701.
394 The WITHOUT_ATF build knob has been removed and its functionality
395 has been subsumed into the more generic WITHOUT_TESTS. If you were
396 using the former to disable the build of the ATF libraries, you
397 should change your settings to use the latter.
400 The default version of mtree is nmtree which is obtained from
401 NetBSD. The output is generally the same, but may vary
402 slightly. If you found you need identical output adding
403 "-F freebsd9" to the command line should do the trick. For the
404 time being, the old mtree is available as fmtree.
407 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
408 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
409 1.1.4_8 and verify bsdyml not linked in, before running "make
411 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
413 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
416 The rc.d/jail script has been updated to support jail(8)
417 configuration file. The "jail_<jname>_*" rc.conf(5) variables
418 for per-jail configuration are automatically converted to
419 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
420 This is transparently backward compatible. See below about some
421 incompatibilities and rc.conf(5) manual page for more details.
423 These variables are now deprecated in favor of jail(8) configuration
424 file. One can use "rc.d/jail config <jname>" command to generate
425 a jail(8) configuration file in /var/run/jail.<jname>.conf without
426 running the jail(8) utility. The default pathname of the
427 configuration file is /etc/jail.conf and can be specified by
428 using $jail_conf or $jail_<jname>_conf variables.
430 Please note that jail_devfs_ruleset accepts an integer at
431 this moment. Please consider to rewrite the ruleset name
435 BIND has been removed from the base system. If all you need
436 is a local resolver, simply enable and start the local_unbound
437 service instead. Otherwise, several versions of BIND are
438 available in the ports tree. The dns/bind99 port is one example.
440 With this change, nslookup(1) and dig(1) are no longer in the base
441 system. Users should instead use host(1) and drill(1) which are
442 in the base system. Alternatively, nslookup and dig can
443 be obtained by installing the dns/bind-tools port.
446 With the addition of unbound(8), a new unbound user is now
447 required during installworld. "mergemaster -p" can be used to
448 add the user prior to installworld, as documented in the handbook.
451 OpenSSH is now built with DNSSEC support, and will by default
452 silently trust signed SSHFP records. This can be controlled with
453 the VerifyHostKeyDNS client configuration setting. DNSSEC support
454 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
457 The GNU Compiler Collection and C++ standard library (libstdc++)
458 are no longer built by default on platforms where clang is the system
459 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
463 The PROCDESC kernel option is now part of the GENERIC kernel
464 configuration and is required for the rwhod(8) to work.
465 If you are using custom kernel configuration, you should include
469 The API and ABI related to the Capsicum framework was modified
470 in backward incompatible way. The userland libraries and programs
471 have to be recompiled to work with the new kernel. This includes the
472 following libraries and programs, but the whole buildworld is
473 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
474 kdump, procstat, rwho, rwhod, uniq.
477 AES-NI intrinsic support has been added to gcc. The AES-NI module
478 has been updated to use this support. A new gcc is required to build
479 the aesni module on both i386 and amd64.
482 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
483 Thus "device padlock_rng" and "device rdrand_rng" should be
484 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
487 WITH_ICONV has been split into two feature sets. WITH_ICONV now
488 enables just the iconv* functionality and is now on by default.
489 WITH_LIBICONV_COMPAT enables the libiconv api and link time
490 compatability. Set WITHOUT_ICONV to build the old way.
491 If you have been using WITH_ICONV before, you will very likely
492 need to turn on WITH_LIBICONV_COMPAT.
495 INVARIANTS option now enables DEBUG for code with OpenSolaris and
496 Illumos origin, including ZFS. If you have INVARIANTS in your
497 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
499 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
500 locks if WITNESS option was set. Because that generated a lot of
501 witness(9) reports and all of them were believed to be false
502 positives, this is no longer done. New option OPENSOLARIS_WITNESS
503 can be used to achieve the previous behavior.
506 Timer values in IPv6 data structures now use time_uptime instead
507 of time_second. Although this is not a user-visible functional
508 change, userland utilities which directly use them---ndp(8),
509 rtadvd(8), and rtsold(8) in the base system---need to be updated
513 find -delete can now delete the pathnames given as arguments,
514 instead of only files found below them or if the pathname did
515 not contain any slashes. Formerly, the following error message
518 find: -delete: <path>: relative path potentially not safe
520 Deleting the pathnames given as arguments can be prevented
521 without error messages using -mindepth 1 or by changing
522 directory and passing "." as argument to find. This works in the
523 old as well as the new version of find.
526 Behavior of devfs rules path matching has been changed.
527 Pattern is now always matched against fully qualified devfs
528 path and slash characters must be explicitly matched by
529 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
530 subdirectories must be reviewed.
533 The default ARM ABI has changed to the ARM EABI. The old ABI is
534 incompatible with the ARM EABI and all programs and modules will
535 need to be rebuilt to work with a new kernel.
537 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
539 NOTE: Support for the old ABI will be removed in the future and
540 users are advised to upgrade.
543 pkg_install has been disconnected from the build if you really need it
544 you should add WITH_PKGTOOLS in your src.conf(5).
547 Most of network statistics structures were changed to be able
548 keep 64-bits counters. Thus all tools, that work with networking
549 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
552 Fix a bug that allowed a tracing process (e.g. gdb) to write
553 to a memory-mapped file in the traced process's address space
554 even if neither the traced process nor the tracing process had
555 write access to that file.
558 CVS has been removed from the base system. An exact copy
559 of the code is available from the devel/cvs port.
562 Some people report the following error after the switch to bmake:
564 make: illegal option -- J
565 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
567 *** [buildworld] Error code 2
569 this likely due to an old instance of make in
570 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
571 which src/Makefile will use that blindly, if it exists, so if
572 you see the above error:
574 rm -rf `make -V MAKEPATH`
579 Use bmake by default.
580 Whereas before one could choose to build with bmake via
581 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
582 make. The goal is to remove these knobs for 10-RELEASE.
584 It is worth noting that bmake (like gmake) treats the command
585 line as the unit of failure, rather than statements within the
586 command line. Thus '(cd some/where && dosomething)' is safer
587 than 'cd some/where; dosomething'. The '()' allows consistent
588 behavior in parallel build.
591 Fix a bug that allows NFS clients to issue READDIR on files.
594 The WITHOUT_IDEA option has been removed because
595 the IDEA patent expired.
598 The sysctl which controls TRIM support under ZFS has been renamed
599 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
603 The mergemaster command now uses the default MAKEOBJDIRPREFIX
604 rather than creating it's own in the temporary directory in
605 order allow access to bootstrapped versions of tools such as
606 install and mtree. When upgrading from version of FreeBSD where
607 the install command does not support -l, you will need to
608 install a new mergemaster command if mergemaster -p is required.
609 This can be accomplished with the command (cd src/usr.sbin/mergemaster
613 Legacy ATA stack, disabled and replaced by new CAM-based one since
614 FreeBSD 9.0, completely removed from the sources. Kernel modules
615 atadisk and atapi*, user-level tools atacontrol and burncd are
616 removed. Kernel option `options ATA_CAM` is now permanently enabled
620 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
621 and socketpair(2). Software, in particular Kerberos, may
622 automatically detect and use these during building. The resulting
623 binaries will not work on older kernels.
626 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
627 information, see the respective 20130304 entry).
630 Recent commits to callout(9) changed the size of struct callout,
631 so the KBI is probably heavily disturbed. Also, some functions
632 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
633 by macros. Every kernel module using it won't load, so rebuild
636 The ctl device has been re-enabled in GENERIC for i386 and amd64,
637 but does not initialize by default (because of the new CTL_DISABLE
638 option) to save memory. To re-enable it, remove the CTL_DISABLE
639 option from the kernel config file or set kern.cam.ctl.disable=0
640 in /boot/loader.conf.
643 The ctl device has been disabled in GENERIC for i386 and amd64.
644 This was done due to the extra memory being allocated at system
645 initialisation time by the ctl driver which was only used if
646 a CAM target device was created. This makes a FreeBSD system
647 unusable on 128MB or less of RAM.
650 A new compression method (lz4) has been merged to -HEAD. Please
651 refer to zpool-features(7) for more information.
653 Please refer to the "ZFS notes" section of this file for information
654 on upgrading boot ZFS pools.
657 A BSD-licensed patch(1) variant has been added and is installed
658 as bsdpatch, being the GNU version the default patch.
659 To inverse the logic and use the BSD-licensed one as default,
660 while having the GNU version installed as gnupatch, rebuild
661 and install world with the WITH_BSD_PATCH knob set.
664 Due to the use of the new -l option to install(1) during build
665 and install, you must take care not to directly set the INSTALL
666 make variable in your /etc/make.conf, /etc/src.conf, or on the
667 command line. If you wish to use the -C flag for all installs
668 you may be able to add INSTALL+=-C to /etc/make.conf or
672 The install(1) option -M has changed meaning and now takes an
673 argument that is a file or path to append logs to. In the
674 unlikely event that -M was the last option on the command line
675 and the command line contained at least two files and a target
676 directory the first file will have logs appended to it. The -M
677 option served little practical purpose in the last decade so its
678 use is expected to be extremely rare.
681 After switching to Clang as the default compiler some users of ZFS
682 on i386 systems started to experience stack overflow kernel panics.
683 Please consider using 'options KSTACK_PAGES=4' in such configurations.
686 GEOM_LABEL now mangles label names read from file system metadata.
687 Mangling affect labels containing spaces, non-printable characters,
688 '%' or '"'. Device names in /etc/fstab and other places may need to
692 By default, only the 10 most recent kernel dumps will be saved. To
693 restore the previous behaviour (no limit on the number of kernel dumps
694 stored in the dump directory) add the following line to /etc/rc.conf:
699 With the addition of auditdistd(8), a new auditdistd user is now
700 required during installworld. "mergemaster -p" can be used to
701 add the user prior to installworld, as documented in the handbook.
704 The sin6_scope_id member variable in struct sockaddr_in6 is now
705 filled by the kernel before passing the structure to the userland via
706 sysctl or routing socket. This means the KAME-specific embedded scope
707 id in sin6_addr.s6_addr[2] is always cleared in userland application.
708 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
709 __FreeBSD_version is bumped to 1000025.
712 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
713 This means that the world and kernel will be compiled with clang
714 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
715 and /usr/bin/cpp. To disable this behavior and revert to building
716 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
717 of current may need to bootstrap WITHOUT_CLANG first if the clang
718 build fails (its compatibility window doesn't extend to the 9 stable
722 The IPFIREWALL_FORWARD kernel option has been removed. Its
723 functionality now turned on by default.
726 The ZERO_COPY_SOCKET kernel option has been removed and
727 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
728 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
729 mechanism which is not safe and may result in kernel crashes.
730 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
731 driver supports disposeable external page sized mbuf storage.
732 Proper replacements for both zero-copy mechanisms are under
733 consideration and will eventually lead to complete removal
734 of the two kernel options.
737 The IPv4 network stack has been converted to network byte
738 order. The following modules need to be recompiled together
739 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
740 pf(4), ipfw(4), ng_ipfw(4), stf(4).
743 Support for non-MPSAFE filesystems was removed from VFS. The
744 VFS_VERSION was bumped, all filesystem modules shall be
748 All the non-MPSAFE filesystems have been disconnected from
749 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
750 portalfs, smbfs, xfs.
753 The interface cloning API and ABI has changed. The following
754 modules need to be recompiled together with kernel:
755 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
756 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
757 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
760 The sdhci driver was split in two parts: sdhci (generic SD Host
761 Controller logic) and sdhci_pci (actual hardware driver).
762 No kernel config modifications are required, but if you
763 load sdhc as a module you must switch to sdhci_pci instead.
766 Import the FUSE kernel and userland support into base system.
769 The GNU sort(1) program has been removed since the BSD-licensed
770 sort(1) has been the default for quite some time and no serious
771 problems have been reported. The corresponding WITH_GNU_SORT
775 The pfil(9) API/ABI for AF_INET family has been changed. Packet
776 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
780 The net80211(4) ABI has been changed to allow for improved driver
781 PS-POLL and power-save support. All wireless drivers need to be
782 recompiled to work with the new kernel.
785 The random(4) support for the VIA hardware random number
786 generator (`PADLOCK') is no longer enabled unconditionally.
787 Add the padlock_rng device in the custom kernel config if
788 needed. The GENERIC kernels on i386 and amd64 do include the
789 device, so the change only affects the custom kernel
793 The pf(4) packet filter ABI has been changed. pfctl(8) and
794 snmp_pf module need to be recompiled to work with new kernel.
797 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
798 to -HEAD. Pools that have empty_bpobj in active state can not be
799 imported read-write with ZFS implementations that do not support
800 this feature. For more information read the zpool-features(5)
804 The sparc64 ZFS loader has been changed to no longer try to auto-
805 detect ZFS providers based on diskN aliases but now requires these
806 to be explicitly listed in the OFW boot-device environment variable.
809 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
810 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
811 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
814 The following sysctls and tunables have been renamed for consistency
815 with other variables:
816 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
817 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
820 The sort utility has been replaced with BSD sort. For now, GNU sort
821 is also available as "gnusort" or the default can be set back to
822 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
823 installed as "bsdsort".
826 A new version of ZFS (pool version 5000) has been merged to -HEAD.
827 Starting with this version the old system of ZFS pool versioning
828 is superseded by "feature flags". This concept enables forward
829 compatibility against certain future changes in functionality of ZFS
830 pools. The first read-only compatible "feature flag" for ZFS pools
831 is named "com.delphix:async_destroy". For more information
832 read the new zpool-features(5) manual page.
833 Please refer to the "ZFS notes" section of this file for information
834 on upgrading boot ZFS pools.
837 The malloc(3) implementation embedded in libc now uses sources imported
838 as contrib/jemalloc. The most disruptive API change is to
839 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
840 delete it prior to installworld, and optionally re-create it using the
841 new format after rebooting. See malloc.conf(5) for details
842 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
846 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
847 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
848 now spelled mips. This is to aid compatibility with third-party
849 software that expects this naming scheme in uname(3). Little-endian
850 settings are unchanged. If you are updating a big-endian mips64 machine
851 from before this change, you may need to set MACHINE_ARCH=mips64 in
852 your environment before the new build system will recognize your machine.
855 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
859 Now unix domain sockets behave "as expected" on nullfs(5). Previously
860 nullfs(5) did not pass through all behaviours to the underlying layer,
861 as a result if we bound to a socket on the lower layer we could connect
862 only to the lower path; if we bound to the upper layer we could connect
863 only to the upper path. The new behavior is one can connect to both the
864 lower and the upper paths regardless what layer path one binds to.
867 The getifaddrs upgrade path broken with 20111215 has been restored.
868 If you have upgraded in between 20111215 and 20120209 you need to
869 recompile libc again with your kernel. You still need to recompile
870 world to be able to configure CARP but this restriction already
874 The set_rcvar() function has been removed from /etc/rc.subr. All
875 base and ports rc.d scripts have been updated, so if you have a
876 port installed with a script in /usr/local/etc/rc.d you can either
877 hand-edit the rcvar= line, or reinstall the port.
879 An easy way to handle the mass-update of /etc/rc.d:
880 rm /etc/rc.d/* && mergemaster -i
883 panic(9) now stops other CPUs in the SMP systems, disables interrupts
884 on the current CPU and prevents other threads from running.
885 This behavior can be reverted using the kern.stop_scheduler_on_panic
887 The new behavior can be incompatible with kern.sync_on_panic.
890 The carp(4) facility has been changed significantly. Configuration
891 of the CARP protocol via ifconfig(8) has changed, as well as format
892 of CARP events submitted to devd(8) has changed. See manual pages
893 for more information. The arpbalance feature of carp(4) is currently
894 not supported anymore.
896 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
897 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
898 need to be recompiled.
901 The acpi_wmi(4) status device /dev/wmistat has been renamed to
905 The option VFS_ALLOW_NONMPSAFE option has been added in order to
906 explicitely support non-MPSAFE filesystems.
907 It is on by default for all supported platform at this present
911 The broken amd(4) driver has been replaced with esp(4) in the amd64,
912 i386 and pc98 GENERIC kernel configuration files.
915 sysinstall has been removed
918 The stable/9 branch created in subversion. This corresponds to the
919 RELENG_9 branch in CVS.
922 This commit modifies vfs_register() so that it uses a hash
923 calculation to set vfc_typenum, which is enabled by default.
924 The first time a system is booted after this change, the
925 vfc_typenum values will change for all file systems. The
926 main effect of this is a change to the NFS server file handles
927 for file systems that use vfc_typenum in their fsid, such as ZFS.
928 It will, however, prevent vfc_typenum from changing when file
929 systems are loaded in a different order for subsequent reboots.
930 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
931 until you are ready to remount all NFS clients after a reboot.
934 Bump the shared library version numbers for libraries that
935 do not use symbol versioning, have changed the ABI compared
936 to stable/8 and which shared library version was not bumped.
937 Done as part of 9.0-RELEASE cycle.
940 During the merge of Capsicum features, the fget(9) KPI was modified.
941 This may require the rebuilding of out-of-tree device drivers --
942 issues have been reported specifically with the nVidia device driver.
943 __FreeBSD_version is bumped to 900041.
945 Also, there is a period between 20110811 and 20110814 where the
946 special devices /dev/{stdin,stdout,stderr} did not work correctly.
947 Building world from a kernel during that window may not work.
950 The packet filter (pf) code has been updated to OpenBSD 4.5.
951 You need to update userland tools to be in sync with kernel.
952 This update breaks backward compatibility with earlier pfsync(4)
953 versions. Care must be taken when updating redundant firewall setups.
956 The following sysctls and tunables are retired on x86 platforms:
958 machdep.hlt_logical_cpus
959 The following sysctl is retired:
960 machdep.hyperthreading_allowed
961 The sysctls were supposed to provide a way to dynamically offline and
962 online selected CPUs on x86 platforms, but the implementation has not
963 been reliable especially with SCHED_ULE scheduler.
964 machdep.hyperthreading_allowed tunable is still available to ignore
965 hyperthreading CPUs at OS level.
966 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
967 where X is an APIC ID of a CPU. Be advised, though, that disabling
968 CPUs in non-uniform fashion will result in non-uniform topology and
969 may lead to sub-optimal system performance with SCHED_ULE, which is
973 cpumask_t type is retired and cpuset_t is used in order to describe
977 Changes to ifconfig(8) for dynamic address family detection mandate
978 that you are running a kernel of 20110525 or later. Make sure to
979 follow the update procedure to boot a new kernel before installing
983 Support for sun4v architecture is officially dropped
986 Several KPI breaking changes have been committed to the mii(4) layer,
987 the PHY drivers and consequently some Ethernet drivers using mii(4).
988 This means that miibus.ko and the modules of the affected Ethernet
989 drivers need to be recompiled.
991 Note to kernel developers: Given that the OUI bit reversion problem
992 was fixed as part of these changes all mii(4) commits related to OUIs,
993 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
994 handling, no longer can be merged verbatim to stable/8 and previous
998 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
999 into their kernel configurations along with 'device pci'.
1002 The default NFS client is now the new NFS client, so fstype "newnfs"
1003 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
1004 Although mounts via fstype "nfs" will usually work without userland
1005 changes, it is recommended that the mount(8) and mount_nfs(8)
1006 commands be rebuilt from sources and that a link to mount_nfs called
1007 mount_oldnfs be created. The new client is compiled into the
1008 kernel with "options NFSCL" and this is needed for diskless root
1009 file systems. The GENERIC kernel configs have been changed to use
1010 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
1011 To use the regular/old client, you can "mount -t oldnfs ...". For
1012 a diskless root file system, you must also include a line like:
1014 vfs.root.mountfrom="oldnfs:"
1016 in the boot/loader.conf on the root fs on the NFS server to make
1017 a diskless root fs use the old client.
1020 The GENERIC kernels for all architectures now default to the new
1021 CAM-based ATA stack. It means that all legacy ATA drivers were
1022 removed and replaced by respective CAM drivers. If you are using
1023 ATA device names in /etc/fstab or other places, make sure to update
1024 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
1025 where 'Y's are the sequential numbers starting from zero for each type
1026 in order of detection, unless configured otherwise with tunables,
1027 see cam(4)). There will be symbolic links created in /dev/ to map
1028 old adX devices to the respective adaY. They should provide basic
1029 compatibility for file systems mounting in most cases, but they do
1030 not support old user-level APIs and do not have respective providers
1031 in GEOM. Consider using updated management tools with new device names.
1033 It is possible to load devices ahci, ata, siis and mvs as modules,
1034 but option ATA_CAM should remain in kernel configuration to make ata
1035 module work as CAM driver supporting legacy ATA controllers. Device ata
1036 still can be used in modular fashion (atacore + ...). Modules atadisk
1037 and atapi* are not used and won't affect operation in ATA_CAM mode.
1038 Note that to use CAM-based ATA kernel should include CAM devices
1039 scbus, pass, da (or explicitly ada), cd and optionally others. All of
1040 them are parts of the cam module.
1042 ataraid(4) functionality is now supported by the RAID GEOM class.
1043 To use it you can load geom_raid kernel module and use graid(8) tool
1044 for management. Instead of /dev/arX device names, use /dev/raid/rX.
1046 No kernel config options or code have been removed, so if a problem
1047 arises, please report it and optionally revert to the old ATA stack.
1048 In order to do it you can remove from the kernel config:
1053 , and instead add back:
1054 device atadisk # ATA disk drives
1055 device ataraid # ATA RAID drives
1056 device atapicd # ATAPI CDROM drives
1057 device atapifd # ATAPI floppy drives
1058 device atapist # ATAPI tape drives
1061 The default NFS server has been changed to the new server, which
1062 was referred to as the experimental server. If you need to switch
1063 back to the old NFS server, you must now put the "-o" option on
1064 both the mountd and nfsd commands. This can be done using the
1065 mountd_flags and nfs_server_flags rc.conf variables until an
1066 update to the rc scripts is committed, which is coming soon.
1069 The GNU Objective-C runtime library (libobjc), and other Objective-C
1070 related components have been removed from the base system. If you
1071 require an Objective-C library, please use one of the available ports.
1074 ath(4) has been split into bus- and device- modules. if_ath contains
1075 the HAL, the TX rate control and the network device code. if_ath_pci
1076 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1077 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1078 in order to use ath on everything else.
1080 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1081 need to load if_ath and if_ath_pci for ath(4) operation.
1084 As part of the replacement of sysinstall, the process of building
1085 release media has changed significantly. For details, please re-read
1086 release(7), which has been updated to reflect the new build process.
1089 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1090 is the last available version under GPLv2. It brings a number of new
1091 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1092 4.1 and SSE 4.2), better support for powerpc64, a number of new
1093 directives, and lots of other small improvements. See the ChangeLog
1094 file in contrib/binutils for the full details.
1097 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1098 compliant, and will now use half of hash for authentication.
1099 This will break interoperability with all stacks (including all
1100 actual FreeBSD versions) who implement
1101 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1103 The only workaround with such peers is to use another HMAC
1104 algorithm for IPsec ("phase 2") authentication.
1107 Remove the uio_yield prototype and symbol. This function has
1108 been misnamed since it was introduced and should not be
1109 globally exposed with this name. The equivalent functionality
1110 is now available using kern_yield(curthread->td_user_pri).
1111 The function remains undocumented.
1114 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1115 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1116 for scalar sysctls is defined but disabled. Code that needs
1117 UQUAD to pass the type checking that must compile on older
1118 systems where the define is not present can check against
1119 __FreeBSD_version >= 900030.
1121 The system dialog(1) has been replaced with a new version previously
1122 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1123 with the previous version, but the libdialog associated with it has
1124 a largely incompatible API. As such, the original version of libdialog
1125 will be kept temporarily as libodialog, until its base system consumers
1126 are replaced or updated. Bump __FreeBSD_version to 900030.
1129 If you are trying to run make universe on a -stable system, and you get
1130 the following warning:
1131 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1132 unknown. config(8) likely too old."
1133 or something similar to it, then you must upgrade your -stable system
1134 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1135 stable/8) or build the config from the latest stable/8 branch and
1136 install it on your system.
1138 Prior to this date, building a current universe on 8-stable system from
1139 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1140 error in the first kernel build phase. A new config on those old
1141 systems will fix that problem for older versions of -current.
1144 The TCP stack has been modified to allow Khelp modules to interact with
1145 it via helper hook points and store per-connection data in the TCP
1146 control block. Bump __FreeBSD_version to 900029. User space tools that
1147 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1151 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1152 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1153 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1154 to take advantage of it instead of using custom implementations. This
1155 means that these drivers now no longer unconditionally advertise
1156 support for flow control but only do so if flow control is a selected
1157 media option. This was implemented in the generic support that way in
1158 order to allow flow control to be switched on and off via ifconfig(8)
1159 with the PHY specific default to typically off in order to protect
1160 from unwanted effects. Consequently, if you used flow control with
1161 one of the above mentioned drivers you now need to explicitly enable
1162 it, for example via:
1163 ifconfig bge0 media auto mediaopt flowcontrol
1165 Along with the above mentioned changes generic support for setting
1166 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1167 e1000phy(4) as well as ip1000phy(4) have been converted to take
1168 advantage of it. This means that these drivers now no longer take the
1169 link0 parameter for selecting master mode but the master media option
1170 has to be used instead, for example like in the following:
1171 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1173 Selection of master mode now is also available with all other PHY
1174 drivers supporting 1000baseT.
1177 The TCP stack has received a significant update to add support for
1178 modularised congestion control and generally improve the clarity of
1179 congestion control decisions. Bump __FreeBSD_version to 900025. User
1180 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1181 sockstat) need to be recompiled.
1184 The man(1) utility has been replaced by a new version that no longer
1185 uses /etc/manpath.config. Please consult man.conf(5) for how to
1186 migrate local entries to the new format.
1189 The copyright strings printed by login(1) and sshd(8) at the time of a
1190 new connection have been removed to follow other operating systems and
1194 A workaround for a fixed ld bug has been removed in kernel code,
1195 so make sure that your system ld is built from sources after
1196 revision 210245 from 2010-07-19 (r211583 if building head kernel
1197 on stable/8, r211584 for stable/7; both from 2010-08-21).
1198 A symptom of incorrect ld version is different addresses for
1199 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1202 The $ipv6_prefer variable in rc.conf(5) has been split into
1203 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1205 The $ip6addrctl_policy is a variable to choose a pre-defined
1206 address selection policy set by ip6addrctl(8). A value
1207 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1210 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1211 flag (see an entry of 20090926) is set on an interface with no
1212 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1213 security reason. If you want IPv6 link-local address on all
1214 interfaces by default, set this to "YES".
1216 The old ipv6_prefer="YES" is equivalent to
1217 ipv6_activate_all_interfaces="YES" and
1218 ip6addrctl_policy="ipv6_prefer".
1221 DTrace has grown support for userland tracing. Due to this, DTrace is
1222 now i386 and amd64 only.
1223 dtruss(1) is now installed by default on those systems and a new
1224 kernel module is needed for userland tracing: fasttrap.
1225 No changes to your kernel config file are necessary to enable
1226 userland tracing, but you might consider adding 'STRIP=' and
1227 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1228 to have informative userland stack traces in DTrace (ustack).
1231 The acpi_aiboost(4) driver has been removed in favor of the new
1232 aibs(4) driver. You should update your kernel configuration file.
1235 BSD grep has been imported to the base system and it is built by
1236 default. It is completely BSD licensed, highly GNU-compatible, uses
1237 less memory than its GNU counterpart and has a small codebase.
1238 However, it is slower than its GNU counterpart, which is mostly
1239 noticeable for larger searches, for smaller ones it is measurable
1240 but not significant. The reason is complex, the most important factor
1241 is that we lack a modern and efficient regex library and GNU
1242 overcomes this by optimizing the searches internally. Future work
1243 on improving the regex performance is planned, for the meantime,
1244 users that need better performance, can build GNU grep instead by
1245 setting the WITH_GNU_GREP knob.
1248 Due to the import of powerpc64 support, all existing powerpc kernel
1249 configuration files must be updated with a machine directive like this:
1250 machine powerpc powerpc
1252 In addition, an updated config(8) is required to build powerpc kernels
1256 A new version of ZFS (version 15) has been merged to -HEAD.
1257 This version uses a python library for the following subcommands:
1258 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1259 For full functionality of these commands the following port must
1260 be installed: sysutils/py-zfs
1263 'vm_page's are now hashed by physical address to an array of mutexes.
1264 Currently this is only used to serialize access to hold_count. Over
1265 time the page queue mutex will be peeled away. This changes the size
1266 of pmap on every architecture. And requires all callers of vm_page_hold
1267 and vm_page_unhold to be updated.
1270 WITH_CTF can now be specified in src.conf (not recommended, there
1271 are some problems with static executables), make.conf (would also
1272 affect ports which do not use GNU make and do not override the
1273 compile targets) or in the kernel config (via "makeoptions
1275 When WITH_CTF was specified there before this was silently ignored,
1276 so make sure that WITH_CTF is not used in places which could lead
1277 to unwanted behavior.
1280 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1281 to allow 32-bit compatibility on non-x86 platforms. All kernel
1282 configurations on amd64 and ia64 platforms using these options must
1283 be modified accordingly.
1286 The utmp user accounting database has been replaced with utmpx,
1287 the user accounting interface standardized by POSIX.
1288 Unfortunately the semantics of utmp and utmpx don't match,
1289 making it practically impossible to support both interfaces.
1290 The user accounting database is used by tools like finger(1),
1291 last(1), talk(1), w(1) and ac(8).
1293 All applications in the base system use utmpx. This means only
1294 local binaries (e.g. from the ports tree) may still use these
1295 utmp database files. These applications must be rebuilt to make
1298 After the system has been upgraded, it is safe to remove the old
1299 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1300 assuming their contents is of no importance anymore. Old wtmp
1301 databases can only be used by last(1) and ac(8) after they have
1302 been converted to the new format using wtmpcvt(1).
1305 Introduce the kernel thread "deadlock resolver" (which can be enabled
1306 via the DEADLKRES option, see NOTES for more details) and the
1307 sleepq_type() function for sleepqueues.
1310 The rc.firewall and rc.firewall6 were unified, and
1311 rc.firewall6 and rc.d/ip6fw were removed.
1312 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1313 variables are obsoleted. Instead, the following new rc
1314 variables are added to rc.d/ipfw:
1316 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1317 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1318 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1320 The meanings correspond to the relevant IPv4 variables.
1326 The default terminal emulation for syscons(4) has been changed
1327 from cons25 to xterm on all platforms except pc98. This means
1328 that the /etc/ttys file needs to be updated to ensure correct
1329 operation of applications on the console.
1331 The terminal emulation style can be toggled per window by using
1332 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1333 options can be used to change the compile-time default back to
1336 To prevent graphical artifacts, make sure the TERM environment
1337 variable is set to match the terminal emulation that is being
1338 performed by syscons(4).
1341 The layout of the structure ieee80211req_scan_result has changed.
1342 Applications that require wireless scan results (e.g. ifconfig(8))
1343 from net80211 need to be recompiled.
1345 Applications such as wpa_supplicant(8) may require a full world
1346 build without using NO_CLEAN in order to get synchronized with the
1350 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1351 There's one kernel module for each firmware. Adding "device iwnfw"
1352 to the kernel configuration file means including all three firmware
1353 images inside the kernel. If you want to include just the one for
1354 your wireless card, use the devices iwn4965fw, iwn5000fw or
1358 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1359 into rc.d/netif. The changes are the following:
1361 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1362 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1363 Note that both variables need the "inet6" keyword at the head.
1365 Do not set $ipv6_network_interfaces manually if you do not
1366 understand what you are doing. It is not needed in most cases.
1368 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1371 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1372 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1374 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1375 all configured interfaces have "inet6 accept_rtadv" in the
1376 $ifconfig_IF_ipv6. These are for backward compatibility.
1378 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1379 functionality of interfaces with no corresponding
1380 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1381 and the default address selection policy of ip6addrctl(8)
1382 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1383 Note that if you want to configure IPv6 functionality on the
1384 disabled interfaces after boot, first you need to clear the flag by
1385 using ifconfig(8) like:
1387 ifconfig em0 inet6 -ifdisabled
1389 If YES, the default address selection policy is set as
1392 The default value of $ipv6_prefer is NO.
1394 4. If your system need to receive Router Advertisement messages,
1395 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1396 scripts automatically invoke rtsol(8) when the interface becomes
1397 UP. The Router Advertisement messages are used for SLAAC
1398 (State-Less Address AutoConfiguration).
1401 802.11s D3.03 support was committed. This is incompatible with the
1402 previous code, which was based on D3.0.
1405 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1406 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1407 control whether accepting Router Advertisement messages or not.
1408 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1409 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1410 The ifconfig(8) utility now supports these flags.
1413 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1414 mount(8) and -a option for df(1) to see them.
1417 The old tunable hw.bus.devctl_disable has been superseded by
1418 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1419 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1423 Remove the option STOP_NMI. The default action is now to use NMI only
1424 for KDB via the newly introduced function stop_cpus_hard() and
1425 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1428 The stable/8 branch created in subversion. This corresponds to the
1429 RELENG_8 branch in CVS.
1432 Bump the shared library version numbers for all libraries that do not
1433 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1434 __FreeBSD_version to 800105.
1437 Due to changes in the implementation of virtual network stack support,
1438 all network-related kernel modules must be recompiled. As this change
1439 breaks the ABI, bump __FreeBSD_version to 800104.
1442 The TOE interface to the TCP syncache has been modified to remove
1443 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1444 The cxgb driver is the only TOE consumer affected by this change, and
1445 needs to be recompiled along with the kernel. As this change breaks
1446 the ABI, bump __FreeBSD_version to 800103.
1449 Padding has been added to struct tcpcb, sackhint and tcpstat in
1450 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1451 maintaining the ABI. However, this change breaks the ABI, so bump
1452 __FreeBSD_version to 800102. User space tools that rely on the size of
1453 any of these structs (e.g. sockstat) need to be recompiled.
1456 The NFS_LEGACYRPC option has been removed along with the old kernel
1457 RPC implementation that this option selected. Kernel configurations
1458 may need to be adjusted.
1461 The network interface device nodes at /dev/net/<interface> have been
1462 removed. All ioctl operations can be performed the normal way using
1463 routing sockets. The kqueue functionality can generally be replaced
1464 with routing sockets.
1467 The documentation from the FreeBSD Documentation Project (Handbook,
1468 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1469 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1472 The ABI of various structures related to the SYSV IPC API have been
1473 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1474 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1478 Layout of struct vnet has changed as routing related variables were
1479 moved to their own Vimage module. Modules need to be recompiled. Bump
1480 __FreeBSD_version to 800099.
1483 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1484 respectively. As long as no more than 16 groups per process are used,
1485 no changes should be visible. When more than 16 groups are used, old
1486 binaries may fail if they call getgroups() or getgrouplist() with
1487 statically sized storage. Recompiling will work around this, but
1488 applications should be modified to use dynamically allocated storage
1489 for group arrays as POSIX.1-2008 does not cap an implementation's
1490 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1492 NFS and portalfs mounts may also be affected as the list of groups is
1493 truncated to 16. Users of NFS who use more than 16 groups, should
1494 take care that negative group permissions are not used on the exported
1495 file systems as they will not be reliable unless a GSSAPI based
1496 authentication method is used.
1499 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1500 option compiles in the support for adaptive spinning for lockmgrs
1501 which want to enable it. The lockinit() function now accepts the flag
1502 LK_ADAPTIVE in order to make the lock object subject to adaptive
1503 spinning when both held in write and read mode.
1506 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1507 changed. User applications that use this ioctl need to be rebuilt.
1510 The layout of struct thread has changed. Kernel and modules need to
1514 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1515 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1518 window(1) has been removed from the base system. It can now be
1519 installed from ports. The port is called misc/window.
1522 The way we are storing and accessing `routing table' entries has
1523 changed. Programs reading the FIB, like netstat, need to be
1527 A new netisr implementation has been added for FreeBSD 8. Network
1528 file system modules, such as igmp, ipdivert, and others, should be
1530 Bump __FreeBSD_version to 800096.
1533 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1537 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1538 Bump __FreeBSD_version to 800094.
1541 Add mnt_xflag field to 'struct mount'. File system modules need to be
1543 Bump __FreeBSD_version to 800093.
1546 The compiling option ADAPTIVE_SX has been retired while it has been
1547 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1548 The KPI for sx_init_flags() changes as accepting flags:
1549 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1550 been introduced in order to handle the reversed logic.
1551 Bump __FreeBSD_version to 800092.
1554 Add support for hierarchical jails. Remove global securelevel.
1555 Bump __FreeBSD_version to 800091.
1558 The layout of struct vnet_net has changed, therefore modules
1560 Bump __FreeBSD_version to 800090.
1563 The newly imported zic(8) produces a new format in the output. Please
1564 run tzsetup(8) to install the newly created data to /etc/localtime.
1567 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1568 hw.usb.* and is now consistent again with previous releases.
1571 802.11 monitor mode support was revised and driver api's were changed.
1572 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1573 of DLT_IEEE802_11. No user-visible data structures were changed but
1574 applications that use DLT_IEEE802_11 may require changes.
1575 Bump __FreeBSD_version to 800088.
1578 The layout of the following structs has changed: sysctl_oid,
1579 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1580 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1581 panics may be experienced. World rebuild is required for
1582 correctly checking networking state from userland.
1583 Bump __FreeBSD_version to 800085.
1586 MLDv2 and Source-Specific Multicast (SSM) have been merged
1587 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1588 The implementation of SSM within FreeBSD's IPv6 stack closely
1589 follows the IPv4 implementation.
1591 For kernel developers:
1593 * The most important changes are that the ip6_output() and
1594 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1595 and this lock has been downgraded to a non-recursive mutex.
1597 * As with the changes to the IPv4 stack to support SSM, filtering
1598 of inbound multicast traffic must now be performed by transport
1599 protocols within the IPv6 stack. This does not apply to TCP and
1600 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1602 * The KPIs used by IPv6 multicast are similar to those used by
1603 the IPv4 stack, with the following differences:
1604 * im6o_mc_filter() is analogous to imo_multicast_filter().
1605 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1606 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1607 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1608 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1609 for MLDv1 have an additional 'timer' argument which is used to
1610 jitter the initial membership report for the solicited-node
1611 multicast membership on-link.
1612 * This is not strictly needed for MLDv2, which already jitters
1613 its report transmissions. However, the 'timer' argument is
1614 preserved in case MLDv1 is active on the interface.
1616 * The KAME linked-list based IPv6 membership implementation has
1617 been refactored to use a vector similar to that used by the IPv4
1619 Code which maintains a list of its own multicast memberships
1620 internally, e.g. carp, has been updated to reflect the new
1623 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1624 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1625 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1626 implementation constraint which needs to be addressed in HEAD.
1628 For application developers:
1630 * The changes are broadly similar to those made for the IPv4
1633 * The use of IPv4 and IPv6 multicast socket options on the same
1634 socket, using mapped addresses, HAS NOT been tested or supported.
1636 * There are a number of issues with the implementation of various
1637 IPv6 multicast APIs which need to be resolved in the API surface
1638 before the implementation is fully compatible with KAME userland
1639 use, and these are mostly to do with interface index treatment.
1641 * The literature available discusses the use of either the delta / ASM
1642 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1643 using setsourcefilter(3)/getsourcefilter(3). For more information
1644 please refer to RFC 3768, 'Socket Interface Extensions for
1645 Multicast Source Filters'.
1647 * Applications which use the published RFC 3678 APIs should be fine.
1649 For systems administrators:
1651 * The mtest(8) utility has been refactored to support IPv6, in
1652 addition to IPv4. Interface addresses are no longer accepted
1653 as arguments, their names must be used instead. The utility
1654 will map the interface name to its first IPv4 address as
1655 returned by getifaddrs(3).
1657 * The ifmcstat(8) utility has also been updated to print the MLDv2
1658 endpoint state and source filter lists via sysctl(3).
1660 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1661 loopback of IPv6 multicast datagrams by default; it defaults to 1
1662 to preserve the existing behaviour. Disabling multicast loopback is
1663 recommended for optimal system performance.
1665 * The IPv6 MROUTING code has been changed to examine this sysctl
1666 instead of attempting to perform a group lookup before looping
1667 back forwarded datagrams.
1669 Bump __FreeBSD_version to 800084.
1672 Implement low-level Bluetooth HCI API.
1673 Bump __FreeBSD_version to 800083.
1676 The layout of struct malloc_type, used by modules to register new
1677 memory allocation types, has changed. Most modules will need to
1678 be rebuilt or panics may be experienced.
1679 Bump __FreeBSD_version to 800081.
1682 Anticipate overflowing inp_flags - add inp_flags2.
1683 This changes most offsets in inpcb, so checking v4 connection
1684 state will require a world rebuild.
1685 Bump __FreeBSD_version to 800080.
1688 Add an llentry to struct route and struct route_in6. Modules
1689 embedding a struct route will need to be recompiled.
1690 Bump __FreeBSD_version to 800079.
1693 The size of rt_metrics_lite and by extension rtentry has changed.
1694 Networking administration apps will need to be recompiled.
1695 The route command now supports show as an alias for get, weighting
1696 of routes, sticky and nostick flags to alter the behavior of stateful
1698 Bump __FreeBSD_version to 800078.
1701 Do not use Giant for kbdmux(4) locking. This is wrong and
1702 apparently causing more problems than it solves. This will
1703 re-open the issue where interrupt handlers may race with
1704 kbdmux(4) in polling mode. Typical symptoms include (but
1705 not limited to) duplicated and/or missing characters when
1706 low level console functions (such as gets) are used while
1707 interrupts are enabled (for example geli password prompt,
1708 mountroot prompt etc.). Disabling kbdmux(4) may help.
1711 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1712 kernel modules referencing any of the above need to be recompiled.
1713 Bump __FreeBSD_version to 800075.
1716 GEOM_PART has become the default partition slicer for storage devices,
1717 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1718 introduces some changes:
1720 MSDOS/EBR: the devices created from MSDOS extended partition entries
1721 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1722 to devices with offset-based names. fstabs may need to be modified.
1724 BSD: the "geometry does not match label" warning is harmless in most
1725 cases but it points to problems in file system misalignment with
1726 disk geometry. The "c" partition is now implicit, covers the whole
1727 top-level drive and cannot be (mis)used by users.
1729 General: Kernel dumps are now not allowed to be written to devices
1730 whose partition types indicate they are meant to be used for file
1731 systems (or, in case of MSDOS partitions, as something else than
1734 Most of these changes date approximately from 200812.
1737 The uscanner(4) driver has been removed from the kernel. This follows
1738 Linux removing theirs in 2.6 and making libusb the default interface
1739 (supported by sane).
1742 The multicast forwarding code has been cleaned up. netstat(1)
1743 only relies on KVM now for printing bandwidth upcall meters.
1744 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1745 ip6_mroute_mod respectively. The config(5) options for statically
1746 compiling this code remain the same, i.e. 'options MROUTING'.
1749 Support for the IFF_NEEDSGIANT network interface flag has been
1750 removed, which means that non-MPSAFE network device drivers are no
1751 longer supported. In particular, if_ar, if_sr, and network device
1752 drivers from the old (legacy) USB stack can no longer be built or
1756 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1757 a bunch of new language catalog files have also been added.
1758 This means that some common libc messages are now localized and
1759 they depend on the LC_MESSAGES environmental variable.
1762 The k8temp(4) driver has been renamed to amdtemp(4) since
1763 support for Family 10 and Family 11 CPU families was added.
1766 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1767 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1769 For kernel developers, the most important changes are that the
1770 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1771 and this lock has been downgraded to a non-recursive mutex.
1773 Transport protocols (UDP, Raw IP) are now responsible for filtering
1774 inbound multicast traffic according to group membership and source
1775 filters. The imo_multicast_filter() KPI exists for this purpose.
1776 Transports which do not use multicast (SCTP, TCP) already reject
1777 multicast by default. Forwarding and receive performance may improve
1778 as a mutex acquisition is no longer needed in the ip_input()
1779 low-level input path. in_addmulti() and in_delmulti() are shimmed
1780 to new KPIs which exist to support SSM in-kernel.
1782 For application developers, it is recommended that loopback of
1783 multicast datagrams be disabled for best performance, as this
1784 will still cause the lock to be taken for each looped-back
1785 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1786 be tuned to 0 to disable loopback by default; it defaults to 1
1787 to preserve the existing behaviour.
1789 For systems administrators, to obtain best performance with
1790 multicast reception and multiple groups, it is always recommended
1791 that a card with a suitably precise hash filter is used. Hash
1792 collisions will still result in the lock being taken within the
1793 transport protocol input path to check group membership.
1795 If deploying FreeBSD in an environment with IGMP snooping switches,
1796 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1797 enabled; this forces 224.0.0.0/24 group membership to be announced
1800 The size of 'struct igmpstat' has changed; netstat needs to be
1801 recompiled to reflect this.
1802 Bump __FreeBSD_version to 800070.
1805 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1806 updated to use it. This requires a buildworld/installworld in order to
1807 update the library and dependencies (usbconfig, etc). Its advisable to
1808 rebuild all ports which uses libusb. More specific directions are given
1809 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1810 libusb are no longer required and can be removed.
1813 A workaround is committed to allow the creation of System V shared
1814 memory segment of size > 2 GB on the 64-bit architectures.
1815 Due to a limitation of the existing ABI, the shm_segsz member
1816 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1817 wrong for large segments. Note that limits must be explicitly
1818 raised to allow such segments to be created.
1821 The layout of struct ifnet has changed, requiring a rebuild of all
1822 network device driver modules.
1825 The /dev handling for the new USB stack has changed, a
1826 buildworld/installworld is required for libusb20.
1829 The new USB2 stack has now been permanently moved in and all kernel and
1830 module names reverted to their previous values (eg, usb, ehci, ohci,
1831 ums, ...). The old usb stack can be compiled in by prefixing the name
1832 with the letter 'o', the old usb modules have been removed.
1833 Updating entry 20090216 for xorg and 20090215 for libmap may still
1837 The rc.conf(5) option if_up_delay has been renamed to
1838 defaultroute_delay to better reflect its purpose. If you have
1839 customized this setting in /etc/rc.conf you need to update it to
1843 xorg 7.4 wants to configure its input devices via hald which does not
1844 yet work with USB2. If the keyboard/mouse does not work in xorg then
1846 Option "AllowEmptyInput" "off"
1847 to your ServerLayout section. This will cause X to use the configured
1848 kbd and mouse sections from your xorg.conf.
1851 The GENERIC kernels for all architectures now default to the new USB2
1852 stack. No kernel config options or code have been removed so if a
1853 problem arises please report it and optionally revert to the old USB
1854 stack. If you are loading USB kernel modules or have a custom kernel
1855 that includes GENERIC then ensure that usb names are also changed over,
1856 eg uftdi -> usb2_serial_ftdi.
1858 Older programs linked against the ports libusb 0.1 need to be
1859 redirected to the new stack's libusb20. /etc/libmap.conf can
1861 # Map old usb library to new one for usb2 stack
1862 libusb-0.1.so.8 libusb20.so.1
1865 All USB ethernet devices now attach as interfaces under the name ueN
1866 (eg. ue0). This is to provide a predictable name as vendors often
1867 change usb chipsets in a product without notice.
1870 The ichsmb(4) driver has been changed to require SMBus slave
1871 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1872 All of the other SMBus controller drivers require left-justified
1873 slave addresses, so this change makes all the drivers provide the
1877 INET6 statistics (struct ip6stat) was updated.
1878 netstat(1) needs to be recompiled.
1881 NTFS has been removed from GENERIC kernel on amd64 to match
1882 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1883 will load ntfs.ko module automatically when NTFS support is
1884 actually needed, unless ntfs.ko is not installed or security
1885 level prohibits loading kernel modules. If either is the case,
1886 "options NTFS" has to be added into kernel config.
1889 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1890 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1891 800061. User space tools that rely on the size of struct tcpcb in
1892 tcp_var.h (e.g. sockstat) need to be recompiled.
1895 ng_tty(4) module updated to match the new TTY subsystem.
1896 Due to API change, user-level applications must be updated.
1897 New API support added to mpd5 CVS and expected to be present
1898 in next mpd5.3 release.
1901 With __FreeBSD_version 800060 the makefs tool is part of
1902 the base system (it was a port).
1905 The afdata and ifnet locks have been changed from mutexes to
1906 rwlocks, network modules will need to be re-compiled.
1909 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1910 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1911 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1912 architecture and 40 bytes on 64-bit architecture. The userland
1913 applications "arp" and "ndp" have been updated accordingly.
1914 The output from "netstat -r" shows only routing entries and
1915 none of the L2 information.
1918 __FreeBSD_version 800057 marks the switchover from the
1919 binary ath hal to source code. Users must add the line:
1921 options AH_SUPPORT_AR5416
1923 to their kernel config files when specifying:
1927 The ath_hal module no longer exists; the code is now compiled
1928 together with the driver in the ath module. It is now
1929 possible to tailor chip support (i.e. reduce the set of chips
1930 and thereby the code size); consult ath_hal(4) for details.
1933 __FreeBSD_version 800054 adds memory barriers to
1934 <machine/atomic.h>, new interfaces to ifnet to facilitate
1935 multiple hardware transmit queues for cards that support
1936 them, and a lock-less ring-buffer implementation to
1937 enable drivers to more efficiently manage queueing of
1941 A new version of ZFS (version 13) has been merged to -HEAD.
1942 This version has zpool attribute "listsnapshots" off by
1943 default, which means "zfs list" does not show snapshots,
1944 and is the same as Solaris behavior.
1947 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1950 The uhci, ohci, ehci and slhci USB Host controller drivers have
1951 been put into separate modules. If you load the usb module
1952 separately through loader.conf you will need to load the
1953 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1954 controller add the following to loader.conf:
1960 The ABI used by the PMC toolset has changed. Please keep
1961 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1965 atapci kernel module now includes only generic PCI ATA
1966 driver. AHCI driver moved to ataahci kernel module.
1967 All vendor-specific code moved into separate kernel modules:
1968 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1969 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1970 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1971 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1974 The TTY subsystem of the kernel has been replaced by a new
1975 implementation, which provides better scalability and an
1976 improved driver model. Most common drivers have been migrated to
1977 the new TTY subsystem, while others have not. The following
1978 drivers have not yet been ported to the new TTY layer:
1981 cy, digi, rc, rp, sio
1987 ng_h4, ng_tty, ppp, sl, snp
1989 Adding these drivers to your kernel configuration file shall
1990 cause compilation to fail.
1993 ntpd has been upgraded to 4.2.4p5.
1996 OpenSSH has been upgraded to 5.1p1.
1998 For many years, FreeBSD's version of OpenSSH preferred DSA
1999 over RSA for host and user authentication keys. With this
2000 upgrade, we've switched to the vendor's default of RSA over
2001 DSA. This may cause upgraded clients to warn about unknown
2002 host keys even for previously known hosts. Users should
2003 follow the usual procedure for verifying host keys before
2004 accepting the RSA key.
2006 This can be circumvented by setting the "HostKeyAlgorithms"
2007 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
2010 Please note that the sequence of keys offered for
2011 authentication has been changed as well. You may want to
2012 specify IdentityFile in a different order to revert this
2016 The sio(4) driver has been removed from the i386 and amd64
2017 kernel configuration files. This means uart(4) is now the
2018 default serial port driver on those platforms as well.
2020 To prevent collisions with the sio(4) driver, the uart(4) driver
2021 uses different names for its device nodes. This means the
2022 onboard serial port will now most likely be called "ttyu0"
2023 instead of "ttyd0". You may need to reconfigure applications to
2024 use the new device names.
2026 When using the serial port as a boot console, be sure to update
2027 /boot/device.hints and /etc/ttys before booting the new kernel.
2028 If you forget to do so, you can still manually specify the hints
2029 at the loader prompt:
2031 set hint.uart.0.at="isa"
2032 set hint.uart.0.port="0x3F8"
2033 set hint.uart.0.flags="0x10"
2034 set hint.uart.0.irq="4"
2038 The gpt(8) utility has been removed. Use gpart(8) to partition
2042 The version that Linuxulator emulates was changed from 2.4.2
2043 to 2.6.16. If you experience any problems with Linux binaries
2044 please try to set sysctl compat.linux.osrelease to 2.4.2 and
2045 if it fixes the problem contact emulation mailing list.
2048 ISDN4BSD (I4B) was removed from the src tree. You may need to
2049 update a your kernel configuration and remove relevant entries.
2052 I have checked in code to support multiple routing tables.
2053 See the man pages setfib(1) and setfib(2).
2054 This is a hopefully backwards compatible version,
2055 but to make use of it you need to compile your kernel
2056 with options ROUTETABLES=2 (or more up to 16).
2059 The 802.11 wireless support was redone to enable multi-bss
2060 operation on devices that are capable. The underlying device
2061 is no longer used directly but instead wlanX devices are
2062 cloned with ifconfig. This requires changes to rc.conf files.
2063 For example, change:
2064 ifconfig_ath0="WPA DHCP"
2067 ifconfig_wlan0="WPA DHCP"
2068 see rc.conf(5) for more details. In addition, mergemaster of
2069 /etc/rc.d is highly recommended. Simultaneous update of userland
2070 and kernel wouldn't hurt either.
2072 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2073 modules were merged into the base wlan module. All references
2074 to these modules (e.g. in kernel config files) must be removed.
2077 psm(4) has gained write(2) support in native operation level.
2078 Arbitrary commands can be written to /dev/psm%d and status can
2079 be read back from it. Therefore, an application is responsible
2080 for status validation and error recovery. It is a no-op in
2081 other operation levels.
2084 Support for KSE threading has been removed from the kernel. To
2085 run legacy applications linked against KSE libmap.conf may
2086 be used. The following libmap.conf may be used to ensure
2087 compatibility with any prior release:
2089 libpthread.so.1 libthr.so.1
2090 libpthread.so.2 libthr.so.2
2091 libkse.so.3 libthr.so.3
2094 The layout of struct vmspace has changed. This affects libkvm
2095 and any executables that link against libkvm and use the
2096 kvm_getprocs() function. In particular, but not exclusively,
2097 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2098 The effects are minimal, but it's advisable to upgrade world
2102 The latest em driver no longer has support in it for the
2103 82575 adapter, this is now moved to the igb driver. The
2104 split was done to make new features that are incompatible
2105 with older hardware easier to do.
2108 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2109 likewise the kernel option is now GEOM_LINUX_LVM.
2112 The default NFS mount mode has changed from UDP to TCP for
2113 increased reliability. If you rely on (insecurely) NFS
2114 mounting across a firewall you may need to update your
2118 Belatedly note the addition of m_collapse for compacting
2122 The fts(3) structures have been changed to use adequate
2123 integer types for their members and so to be able to cope
2124 with huge file trees. The old fts(3) ABI is preserved
2125 through symbol versioning in libc, so third-party binaries
2126 using fts(3) should still work, although they will not take
2127 advantage of the extended types. At the same time, some
2128 third-party software might fail to build after this change
2129 due to unportable assumptions made in its source code about
2130 fts(3) structure members. Such software should be fixed
2131 by its vendor or, in the worst case, in the ports tree.
2132 FreeBSD_version 800015 marks this change for the unlikely
2133 case that a portable fix is impossible.
2136 To upgrade to -current after this date, you must be running
2137 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2138 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2141 The ADAPTIVE_GIANT kernel option has been retired because its
2142 functionality is the default now.
2145 The AT keyboard emulation of sunkbd(4) has been turned on
2146 by default. In order to make the special symbols of the Sun
2147 keyboards driven by sunkbd(4) work under X these now have
2148 to be configured the same way as Sun USB keyboards driven
2149 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2151 Option "XkbLayout" "us"
2152 Option "XkbRules" "xorg"
2153 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2156 It has been decided that it is desirable to provide ABI
2157 backwards compatibility to the FreeBSD 4/5/6 versions of the
2158 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2159 broken with the introduction of PCI domain support (see the
2160 20070930 entry). Unfortunately, this required the ABI of
2161 PCIOCGETCONF to be broken again in order to be able to
2162 provide backwards compatibility to the old version of that
2163 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2164 again. As for prominent ports this affects neither pciutils
2165 nor xorg-server this time, the hal port needs to be rebuilt
2169 The misnamed kthread_create() and friends have been renamed
2170 to kproc_create() etc. Many of the callers already
2171 used kproc_start()..
2172 I will return kthread_create() and friends in a while
2173 with implementations that actually create threads, not procs.
2174 Renaming corresponds with version 800002.
2183 Avoid using make -j when upgrading. While generally safe, there are
2184 sometimes problems using -j to upgrade. If your upgrade fails with
2185 -j, please try again without -j. From time to time in the past there
2186 have been problems using -j with buildworld and/or installworld. This
2187 is especially true when upgrading between "distant" versions (eg one
2188 that cross a major release boundary or several minor releases, or when
2189 several months have passed on the -current branch).
2191 Sometimes, obscure build problems are the result of environment
2192 poisoning. This can happen because the make utility reads its
2193 environment when searching for values for global variables. To run
2194 your build attempts in an "environmental clean room", prefix all make
2195 commands with 'env -i '. See the env(1) manual page for more details.
2197 When upgrading from one major version to another it is generally best
2198 to upgrade to the latest code in the currently installed branch first,
2199 then do an upgrade to the new branch. This is the best-tested upgrade
2200 path, and has the highest probability of being successful. Please try
2201 this approach before reporting problems with a major version upgrade.
2203 When upgrading a live system, having a root shell around before
2204 installing anything can help undo problems. Not having a root shell
2205 around can lead to problems if pam has changed too much from your
2206 starting point to allow continued authentication after the upgrade.
2210 When upgrading the boot ZFS pool to a new version, always follow
2213 1.) recompile and reinstall the ZFS boot loader and boot block
2214 (this is part of "make buildworld" and "make installworld")
2216 2.) update the ZFS boot block on your boot drive
2218 The following example updates the ZFS boot block on the first
2219 partition (freebsd-boot) of a GPT partitioned drive ad0:
2220 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2222 Non-boot pools do not need these updates.
2226 If you are updating from a prior version of FreeBSD (even one just
2227 a few days old), you should follow this procedure. It is the most
2228 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2230 make kernel-toolchain
2231 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2232 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2234 To test a kernel once
2235 ---------------------
2236 If you just want to boot a kernel once (because you are not sure
2237 if it works, or if you want to boot a known bad kernel to provide
2238 debugging information) run
2239 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2240 nextboot -k testkernel
2242 To just build a kernel when you know that it won't mess you up
2243 --------------------------------------------------------------
2244 This assumes you are already running a CURRENT system. Replace
2245 ${arch} with the architecture of your machine (e.g. "i386",
2246 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2248 cd src/sys/${arch}/conf
2249 config KERNEL_NAME_HERE
2250 cd ../compile/KERNEL_NAME_HERE
2255 If this fails, go to the "To build a kernel" section.
2257 To rebuild everything and install it on the current system.
2258 -----------------------------------------------------------
2259 # Note: sometimes if you are running current you gotta do more than
2260 # is listed here if you are upgrading from a really old current.
2262 <make sure you have good level 0 dumps>
2264 make kernel KERNCONF=YOUR_KERNEL_HERE
2266 <reboot in single user> [3]
2273 To cross-install current onto a separate partition
2274 --------------------------------------------------
2275 # In this approach we use a separate partition to hold
2276 # current's root, 'usr', and 'var' directories. A partition
2277 # holding "/", "/usr" and "/var" should be about 2GB in
2280 <make sure you have good level 0 dumps>
2283 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2284 <maybe newfs current's root partition>
2285 <mount current's root partition on directory ${CURRENT_ROOT}>
2286 make installworld DESTDIR=${CURRENT_ROOT}
2287 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2288 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2289 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2290 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2291 <reboot into current>
2292 <do a "native" rebuild/install as described in the previous section>
2293 <maybe install compatibility libraries from ports/misc/compat*>
2297 To upgrade in-place from stable to current
2298 ----------------------------------------------
2299 <make sure you have good level 0 dumps>
2301 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2303 <reboot in single user> [3]
2310 Make sure that you've read the UPDATING file to understand the
2311 tweaks to various things you need. At this point in the life
2312 cycle of current, things change often and you are on your own
2313 to cope. The defaults can also change, so please read ALL of
2314 the UPDATING entries.
2316 Also, if you are tracking -current, you must be subscribed to
2317 freebsd-current@freebsd.org. Make sure that before you update
2318 your sources that you have read and understood all the recent
2319 messages there. If in doubt, please track -stable which has
2320 much fewer pitfalls.
2322 [1] If you have third party modules, such as vmware, you
2323 should disable them at this point so they don't crash your
2326 [3] From the bootblocks, boot -s, and then do
2331 adjkerntz -i # if CMOS is wall time
2332 Also, when doing a major release upgrade, it is required that
2333 you boot into single user mode to do the installworld.
2335 [4] Note: This step is non-optional. Failure to do this step
2336 can result in a significant reduction in the functionality of the
2337 system. Attempting to do it by hand is not recommended and those
2338 that pursue this avenue should read this file carefully, as well
2339 as the archives of freebsd-current and freebsd-hackers mailing lists
2340 for potential gotchas. The -U option is also useful to consider.
2341 See mergemaster(8) for more information.
2343 [5] Usually this step is a noop. However, from time to time
2344 you may need to do this if you get unknown user in the following
2345 step. It never hurts to do it all the time. You may need to
2346 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2347 install) after the buildworld before this step if you last updated
2348 from current before 20130425 or from -stable before 20130430.
2350 [6] This only deletes old files and directories. Old libraries
2351 can be deleted by "make delete-old-libs", but you have to make
2352 sure that no program is using those libraries anymore.
2354 [8] In order to have a kernel that can run the 4.x binaries needed to
2355 do an installworld, you must include the COMPAT_FREEBSD4 option in
2356 your kernel. Failure to do so may leave you with a system that is
2357 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2358 required to run the 5.x binaries on more recent kernels. And so on
2359 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2361 Make sure that you merge any new devices from GENERIC since the
2362 last time you updated your kernel config file.
2364 [9] When checking out sources, you must include the -P flag to have
2365 cvs prune empty directories.
2367 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2368 "?=" instead of the "=" assignment operator, so that buildworld can
2369 override the CPUTYPE if it needs to.
2371 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2372 not on the command line, or in /etc/make.conf. buildworld will
2373 warn if it is improperly defined.
2376 This file contains a list, in reverse chronological order, of major
2377 breakages in tracking -current. It is not guaranteed to be a complete
2378 list of such breakages, and only contains entries since October 10, 2007.
2379 If you need to see UPDATING entries from before that date, you will need
2380 to fetch an UPDATING file from an older FreeBSD release.
2382 Copyright information:
2384 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2386 Redistribution, publication, translation and use, with or without
2387 modification, in full or in part, in any form or format of this
2388 document are permitted without further permission from the author.
2390 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2391 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2392 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2393 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2394 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2395 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2396 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2397 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2398 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2399 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2400 POSSIBILITY OF SUCH DAMAGE.
2402 Contact Warner Losh if you have any questions about your use of