1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
20 Clang and llvm have been upgraded to 3.4 release.
23 If a Makefile in a tests/ directory was auto-generating a Kyuafile
24 instead of providing an explicit one, this would prevent such
25 Makefile from providing its own Kyuafile in the future during
26 NO_CLEAN builds. This has been fixed in the Makefiles but manual
27 intervention is needed to clean an objdir if you use NO_CLEAN:
28 # find /usr/obj -name Kyuafile | xargs rm -f
31 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
32 capability mode support. Please note that enabling the feature in
33 kernel is still highly recommended.
36 OpenSSH is now built with sandbox support, and will use sandbox as
37 the default privilege separation method. This requires Capsicum
38 capability mode support in kernel.
41 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
42 been deprecated and will not be part of FreeBSD 11.0 and later
43 releases. If you use this driver, please consider switching to
44 the nfe(4) driver instead.
50 The behavior of gss_pseudo_random() for the krb5 mechanism
51 has changed, for applications requesting a longer random string
52 than produced by the underlying enctype's pseudo-random() function.
53 In particular, the random string produced from a session key of
54 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
55 be different at the 17th octet and later, after this change.
56 The counter used in the PRF+ construction is now encoded as a
57 big-endian integer in accordance with RFC 4402.
58 __FreeBSD_version is bumped to 1000701.
61 The WITHOUT_ATF build knob has been removed and its functionality
62 has been subsumed into the more generic WITHOUT_TESTS. If you were
63 using the former to disable the build of the ATF libraries, you
64 should change your settings to use the latter.
67 The default version of mtree is nmtree which is obtained from
68 NetBSD. The output is generally the same, but may vary
69 slightly. If you found you need identical output adding
70 "-F freebsd9" to the command line should do the trick. For the
71 time being, the old mtree is available as fmtree.
74 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
75 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
76 1.1.4_8 and verify bsdyml not linked in, before running "make
78 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
80 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
83 The rc.d/jail script has been updated to support jail(8)
84 configuration file. The "jail_<jname>_*" rc.conf(5) variables
85 for per-jail configuration are automatically converted to
86 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
87 This is transparently backward compatible. See below about some
88 incompatibilities and rc.conf(5) manual page for more details.
90 These variables are now deprecated in favor of jail(8) configuration
91 file. One can use "rc.d/jail config <jname>" command to generate
92 a jail(8) configuration file in /var/run/jail.<jname>.conf without
93 running the jail(8) utility. The default pathname of the
94 configuration file is /etc/jail.conf and can be specified by
95 using $jail_conf or $jail_<jname>_conf variables.
97 Please note that jail_devfs_ruleset accepts an integer at
98 this moment. Please consider to rewrite the ruleset name
102 BIND has been removed from the base system. If all you need
103 is a local resolver, simply enable and start the local_unbound
104 service instead. Otherwise, several versions of BIND are
105 available in the ports tree. The dns/bind99 port is one example.
107 With this change, nslookup(1) and dig(1) are no longer in the base
108 system. Users should instead use host(1) and drill(1) which are
109 in the base system. Alternatively, nslookup and dig can
110 be obtained by installing the dns/bind-tools port.
113 With the addition of unbound(8), a new unbound user is now
114 required during installworld. "mergemaster -p" can be used to
115 add the user prior to installworld, as documented in the handbook.
118 OpenSSH is now built with DNSSEC support, and will by default
119 silently trust signed SSHFP records. This can be controlled with
120 the VerifyHostKeyDNS client configuration setting. DNSSEC support
121 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
124 The GNU Compiler Collection and C++ standard library (libstdc++)
125 are no longer built by default on platforms where clang is the system
126 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
130 The PROCDESC kernel option is now part of the GENERIC kernel
131 configuration and is required for the rwhod(8) to work.
132 If you are using custom kernel configuration, you should include
136 The API and ABI related to the Capsicum framework was modified
137 in backward incompatible way. The userland libraries and programs
138 have to be recompiled to work with the new kernel. This includes the
139 following libraries and programs, but the whole buildworld is
140 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
141 kdump, procstat, rwho, rwhod, uniq.
144 AES-NI intrinsic support has been added to gcc. The AES-NI module
145 has been updated to use this support. A new gcc is required to build
146 the aesni module on both i386 and amd64.
149 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
150 Thus "device padlock_rng" and "device rdrand_rng" should be
151 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
154 WITH_ICONV has been split into two feature sets. WITH_ICONV now
155 enables just the iconv* functionality and is now on by default.
156 WITH_LIBICONV_COMPAT enables the libiconv api and link time
157 compatability. Set WITHOUT_ICONV to build the old way.
158 If you have been using WITH_ICONV before, you will very likely
159 need to turn on WITH_LIBICONV_COMPAT.
162 INVARIANTS option now enables DEBUG for code with OpenSolaris and
163 Illumos origin, including ZFS. If you have INVARIANTS in your
164 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
166 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
167 locks if WITNESS option was set. Because that generated a lot of
168 witness(9) reports and all of them were believed to be false
169 positives, this is no longer done. New option OPENSOLARIS_WITNESS
170 can be used to achieve the previous behavior.
173 Timer values in IPv6 data structures now use time_uptime instead
174 of time_second. Although this is not a user-visible functional
175 change, userland utilities which directly use them---ndp(8),
176 rtadvd(8), and rtsold(8) in the base system---need to be updated
180 find -delete can now delete the pathnames given as arguments,
181 instead of only files found below them or if the pathname did
182 not contain any slashes. Formerly, the following error message
185 find: -delete: <path>: relative path potentially not safe
187 Deleting the pathnames given as arguments can be prevented
188 without error messages using -mindepth 1 or by changing
189 directory and passing "." as argument to find. This works in the
190 old as well as the new version of find.
193 Behavior of devfs rules path matching has been changed.
194 Pattern is now always matched against fully qualified devfs
195 path and slash characters must be explicitly matched by
196 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
197 subdirectories must be reviewed.
200 The default ARM ABI has changed to the ARM EABI. The old ABI is
201 incompatible with the ARM EABI and all programs and modules will
202 need to be rebuilt to work with a new kernel.
204 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
206 NOTE: Support for the old ABI will be removed in the future and
207 users are advised to upgrade.
210 pkg_install has been disconnected from the build if you really need it
211 you should add WITH_PKGTOOLS in your src.conf(5).
214 Most of network statistics structures were changed to be able
215 keep 64-bits counters. Thus all tools, that work with networking
216 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
219 Fix targets that run multiple make's to use && rather than ;
220 so that subsequent steps depend on success of previous.
222 NOTE: if building 'universe' with -j* on stable/8 or stable/9
223 it would be better to start the build using bmake, to avoid
224 overloading the machine.
227 Fix a bug that allowed a tracing process (e.g. gdb) to write
228 to a memory-mapped file in the traced process's address space
229 even if neither the traced process nor the tracing process had
230 write access to that file.
233 CVS has been removed from the base system. An exact copy
234 of the code is available from the devel/cvs port.
237 Some people report the following error after the switch to bmake:
239 make: illegal option -- J
240 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
242 *** [buildworld] Error code 2
244 this likely due to an old instance of make in
245 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
246 which src/Makefile will use that blindly, if it exists, so if
247 you see the above error:
249 rm -rf `make -V MAKEPATH`
254 Use bmake by default.
255 Whereas before one could choose to build with bmake via
256 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
257 make. The goal is to remove these knobs for 10-RELEASE.
259 It is worth noting that bmake (like gmake) treats the command
260 line as the unit of failure, rather than statements within the
261 command line. Thus '(cd some/where && dosomething)' is safer
262 than 'cd some/where; dosomething'. The '()' allows consistent
263 behavior in parallel build.
266 Fix a bug that allows NFS clients to issue READDIR on files.
269 The WITHOUT_IDEA option has been removed because
270 the IDEA patent expired.
273 The sysctl which controls TRIM support under ZFS has been renamed
274 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
278 The mergemaster command now uses the default MAKEOBJDIRPREFIX
279 rather than creating it's own in the temporary directory in
280 order allow access to bootstrapped versions of tools such as
281 install and mtree. When upgrading from version of FreeBSD where
282 the install command does not support -l, you will need to
283 install a new mergemaster command if mergemaster -p is required.
284 This can be accomplished with the command (cd src/usr.sbin/mergemaster
288 Legacy ATA stack, disabled and replaced by new CAM-based one since
289 FreeBSD 9.0, completely removed from the sources. Kernel modules
290 atadisk and atapi*, user-level tools atacontrol and burncd are
291 removed. Kernel option `options ATA_CAM` is now permanently enabled
295 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
296 and socketpair(2). Software, in particular Kerberos, may
297 automatically detect and use these during building. The resulting
298 binaries will not work on older kernels.
301 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
302 information, see the respective 20130304 entry).
305 Recent commits to callout(9) changed the size of struct callout,
306 so the KBI is probably heavily disturbed. Also, some functions
307 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
308 by macros. Every kernel module using it won't load, so rebuild
311 The ctl device has been re-enabled in GENERIC for i386 and amd64,
312 but does not initialize by default (because of the new CTL_DISABLE
313 option) to save memory. To re-enable it, remove the CTL_DISABLE
314 option from the kernel config file or set kern.cam.ctl.disable=0
315 in /boot/loader.conf.
318 The ctl device has been disabled in GENERIC for i386 and amd64.
319 This was done due to the extra memory being allocated at system
320 initialisation time by the ctl driver which was only used if
321 a CAM target device was created. This makes a FreeBSD system
322 unusable on 128MB or less of RAM.
325 A new compression method (lz4) has been merged to -HEAD. Please
326 refer to zpool-features(7) for more information.
328 Please refer to the "ZFS notes" section of this file for information
329 on upgrading boot ZFS pools.
332 A BSD-licensed patch(1) variant has been added and is installed
333 as bsdpatch, being the GNU version the default patch.
334 To inverse the logic and use the BSD-licensed one as default,
335 while having the GNU version installed as gnupatch, rebuild
336 and install world with the WITH_BSD_PATCH knob set.
339 Due to the use of the new -l option to install(1) during build
340 and install, you must take care not to directly set the INSTALL
341 make variable in your /etc/make.conf, /etc/src.conf, or on the
342 command line. If you wish to use the -C flag for all installs
343 you may be able to add INSTALL+=-C to /etc/make.conf or
347 The install(1) option -M has changed meaning and now takes an
348 argument that is a file or path to append logs to. In the
349 unlikely event that -M was the last option on the command line
350 and the command line contained at least two files and a target
351 directory the first file will have logs appended to it. The -M
352 option served little practical purpose in the last decade so its
353 use is expected to be extremely rare.
356 After switching to Clang as the default compiler some users of ZFS
357 on i386 systems started to experience stack overflow kernel panics.
358 Please consider using 'options KSTACK_PAGES=4' in such configurations.
361 GEOM_LABEL now mangles label names read from file system metadata.
362 Mangling affect labels containing spaces, non-printable characters,
363 '%' or '"'. Device names in /etc/fstab and other places may need to
367 By default, only the 10 most recent kernel dumps will be saved. To
368 restore the previous behaviour (no limit on the number of kernel dumps
369 stored in the dump directory) add the following line to /etc/rc.conf:
374 With the addition of auditdistd(8), a new auditdistd user is now
375 required during installworld. "mergemaster -p" can be used to
376 add the user prior to installworld, as documented in the handbook.
379 The sin6_scope_id member variable in struct sockaddr_in6 is now
380 filled by the kernel before passing the structure to the userland via
381 sysctl or routing socket. This means the KAME-specific embedded scope
382 id in sin6_addr.s6_addr[2] is always cleared in userland application.
383 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
384 __FreeBSD_version is bumped to 1000025.
387 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
388 This means that the world and kernel will be compiled with clang
389 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
390 and /usr/bin/cpp. To disable this behavior and revert to building
391 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
392 of current may need to bootstrap WITHOUT_CLANG first if the clang
393 build fails (its compatibility window doesn't extend to the 9 stable
397 The IPFIREWALL_FORWARD kernel option has been removed. Its
398 functionality now turned on by default.
401 The ZERO_COPY_SOCKET kernel option has been removed and
402 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
403 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
404 mechanism which is not safe and may result in kernel crashes.
405 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
406 driver supports disposeable external page sized mbuf storage.
407 Proper replacements for both zero-copy mechanisms are under
408 consideration and will eventually lead to complete removal
409 of the two kernel options.
412 The IPv4 network stack has been converted to network byte
413 order. The following modules need to be recompiled together
414 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
415 pf(4), ipfw(4), ng_ipfw(4), stf(4).
418 Support for non-MPSAFE filesystems was removed from VFS. The
419 VFS_VERSION was bumped, all filesystem modules shall be
423 All the non-MPSAFE filesystems have been disconnected from
424 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
425 portalfs, smbfs, xfs.
428 The interface cloning API and ABI has changed. The following
429 modules need to be recompiled together with kernel:
430 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
431 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
432 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
435 The sdhci driver was split in two parts: sdhci (generic SD Host
436 Controller logic) and sdhci_pci (actual hardware driver).
437 No kernel config modifications are required, but if you
438 load sdhc as a module you must switch to sdhci_pci instead.
441 Import the FUSE kernel and userland support into base system.
444 The GNU sort(1) program has been removed since the BSD-licensed
445 sort(1) has been the default for quite some time and no serious
446 problems have been reported. The corresponding WITH_GNU_SORT
450 The pfil(9) API/ABI for AF_INET family has been changed. Packet
451 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
455 The net80211(4) ABI has been changed to allow for improved driver
456 PS-POLL and power-save support. All wireless drivers need to be
457 recompiled to work with the new kernel.
460 The random(4) support for the VIA hardware random number
461 generator (`PADLOCK') is no longer enabled unconditionally.
462 Add the padlock_rng device in the custom kernel config if
463 needed. The GENERIC kernels on i386 and amd64 do include the
464 device, so the change only affects the custom kernel
468 The pf(4) packet filter ABI has been changed. pfctl(8) and
469 snmp_pf module need to be recompiled to work with new kernel.
472 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
473 to -HEAD. Pools that have empty_bpobj in active state can not be
474 imported read-write with ZFS implementations that do not support
475 this feature. For more information read the zpool-features(5)
479 The sparc64 ZFS loader has been changed to no longer try to auto-
480 detect ZFS providers based on diskN aliases but now requires these
481 to be explicitly listed in the OFW boot-device environment variable.
484 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
485 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
486 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
489 The following sysctls and tunables have been renamed for consistency
490 with other variables:
491 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
492 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
495 The sort utility has been replaced with BSD sort. For now, GNU sort
496 is also available as "gnusort" or the default can be set back to
497 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
498 installed as "bsdsort".
501 A new version of ZFS (pool version 5000) has been merged to -HEAD.
502 Starting with this version the old system of ZFS pool versioning
503 is superseded by "feature flags". This concept enables forward
504 compatibility against certain future changes in functionality of ZFS
505 pools. The first read-only compatible "feature flag" for ZFS pools
506 is named "com.delphix:async_destroy". For more information
507 read the new zpool-features(5) manual page.
508 Please refer to the "ZFS notes" section of this file for information
509 on upgrading boot ZFS pools.
512 The malloc(3) implementation embedded in libc now uses sources imported
513 as contrib/jemalloc. The most disruptive API change is to
514 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
515 delete it prior to installworld, and optionally re-create it using the
516 new format after rebooting. See malloc.conf(5) for details
517 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
521 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
522 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
523 now spelled mips. This is to aid compatibility with third-party
524 software that expects this naming scheme in uname(3). Little-endian
525 settings are unchanged. If you are updating a big-endian mips64 machine
526 from before this change, you may need to set MACHINE_ARCH=mips64 in
527 your environment before the new build system will recognize your machine.
530 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
534 Now unix domain sockets behave "as expected" on nullfs(5). Previously
535 nullfs(5) did not pass through all behaviours to the underlying layer,
536 as a result if we bound to a socket on the lower layer we could connect
537 only to the lower path; if we bound to the upper layer we could connect
538 only to the upper path. The new behavior is one can connect to both the
539 lower and the upper paths regardless what layer path one binds to.
542 The getifaddrs upgrade path broken with 20111215 has been restored.
543 If you have upgraded in between 20111215 and 20120209 you need to
544 recompile libc again with your kernel. You still need to recompile
545 world to be able to configure CARP but this restriction already
549 The set_rcvar() function has been removed from /etc/rc.subr. All
550 base and ports rc.d scripts have been updated, so if you have a
551 port installed with a script in /usr/local/etc/rc.d you can either
552 hand-edit the rcvar= line, or reinstall the port.
554 An easy way to handle the mass-update of /etc/rc.d:
555 rm /etc/rc.d/* && mergemaster -i
558 panic(9) now stops other CPUs in the SMP systems, disables interrupts
559 on the current CPU and prevents other threads from running.
560 This behavior can be reverted using the kern.stop_scheduler_on_panic
562 The new behavior can be incompatible with kern.sync_on_panic.
565 The carp(4) facility has been changed significantly. Configuration
566 of the CARP protocol via ifconfig(8) has changed, as well as format
567 of CARP events submitted to devd(8) has changed. See manual pages
568 for more information. The arpbalance feature of carp(4) is currently
569 not supported anymore.
571 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
572 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
573 need to be recompiled.
576 The acpi_wmi(4) status device /dev/wmistat has been renamed to
580 The option VFS_ALLOW_NONMPSAFE option has been added in order to
581 explicitely support non-MPSAFE filesystems.
582 It is on by default for all supported platform at this present
586 The broken amd(4) driver has been replaced with esp(4) in the amd64,
587 i386 and pc98 GENERIC kernel configuration files.
590 sysinstall has been removed
593 The stable/9 branch created in subversion. This corresponds to the
594 RELENG_9 branch in CVS.
597 This commit modifies vfs_register() so that it uses a hash
598 calculation to set vfc_typenum, which is enabled by default.
599 The first time a system is booted after this change, the
600 vfc_typenum values will change for all file systems. The
601 main effect of this is a change to the NFS server file handles
602 for file systems that use vfc_typenum in their fsid, such as ZFS.
603 It will, however, prevent vfc_typenum from changing when file
604 systems are loaded in a different order for subsequent reboots.
605 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
606 until you are ready to remount all NFS clients after a reboot.
609 Bump the shared library version numbers for libraries that
610 do not use symbol versioning, have changed the ABI compared
611 to stable/8 and which shared library version was not bumped.
612 Done as part of 9.0-RELEASE cycle.
615 During the merge of Capsicum features, the fget(9) KPI was modified.
616 This may require the rebuilding of out-of-tree device drivers --
617 issues have been reported specifically with the nVidia device driver.
618 __FreeBSD_version is bumped to 900041.
620 Also, there is a period between 20110811 and 20110814 where the
621 special devices /dev/{stdin,stdout,stderr} did not work correctly.
622 Building world from a kernel during that window may not work.
625 The packet filter (pf) code has been updated to OpenBSD 4.5.
626 You need to update userland tools to be in sync with kernel.
627 This update breaks backward compatibility with earlier pfsync(4)
628 versions. Care must be taken when updating redundant firewall setups.
631 The following sysctls and tunables are retired on x86 platforms:
633 machdep.hlt_logical_cpus
634 The following sysctl is retired:
635 machdep.hyperthreading_allowed
636 The sysctls were supposed to provide a way to dynamically offline and
637 online selected CPUs on x86 platforms, but the implementation has not
638 been reliable especially with SCHED_ULE scheduler.
639 machdep.hyperthreading_allowed tunable is still available to ignore
640 hyperthreading CPUs at OS level.
641 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
642 where X is an APIC ID of a CPU. Be advised, though, that disabling
643 CPUs in non-uniform fashion will result in non-uniform topology and
644 may lead to sub-optimal system performance with SCHED_ULE, which is
648 cpumask_t type is retired and cpuset_t is used in order to describe
652 Changes to ifconfig(8) for dynamic address family detection mandate
653 that you are running a kernel of 20110525 or later. Make sure to
654 follow the update procedure to boot a new kernel before installing
658 Support for sun4v architecture is officially dropped
661 Several KPI breaking changes have been committed to the mii(4) layer,
662 the PHY drivers and consequently some Ethernet drivers using mii(4).
663 This means that miibus.ko and the modules of the affected Ethernet
664 drivers need to be recompiled.
666 Note to kernel developers: Given that the OUI bit reversion problem
667 was fixed as part of these changes all mii(4) commits related to OUIs,
668 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
669 handling, no longer can be merged verbatim to stable/8 and previous
673 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
674 into their kernel configurations along with 'device pci'.
677 The default NFS client is now the new NFS client, so fstype "newnfs"
678 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
679 Although mounts via fstype "nfs" will usually work without userland
680 changes, it is recommended that the mount(8) and mount_nfs(8)
681 commands be rebuilt from sources and that a link to mount_nfs called
682 mount_oldnfs be created. The new client is compiled into the
683 kernel with "options NFSCL" and this is needed for diskless root
684 file systems. The GENERIC kernel configs have been changed to use
685 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
686 To use the regular/old client, you can "mount -t oldnfs ...". For
687 a diskless root file system, you must also include a line like:
689 vfs.root.mountfrom="oldnfs:"
691 in the boot/loader.conf on the root fs on the NFS server to make
692 a diskless root fs use the old client.
695 The GENERIC kernels for all architectures now default to the new
696 CAM-based ATA stack. It means that all legacy ATA drivers were
697 removed and replaced by respective CAM drivers. If you are using
698 ATA device names in /etc/fstab or other places, make sure to update
699 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
700 where 'Y's are the sequential numbers starting from zero for each type
701 in order of detection, unless configured otherwise with tunables,
702 see cam(4)). There will be symbolic links created in /dev/ to map
703 old adX devices to the respective adaY. They should provide basic
704 compatibility for file systems mounting in most cases, but they do
705 not support old user-level APIs and do not have respective providers
706 in GEOM. Consider using updated management tools with new device names.
708 It is possible to load devices ahci, ata, siis and mvs as modules,
709 but option ATA_CAM should remain in kernel configuration to make ata
710 module work as CAM driver supporting legacy ATA controllers. Device ata
711 still can be used in modular fashion (atacore + ...). Modules atadisk
712 and atapi* are not used and won't affect operation in ATA_CAM mode.
713 Note that to use CAM-based ATA kernel should include CAM devices
714 scbus, pass, da (or explicitly ada), cd and optionally others. All of
715 them are parts of the cam module.
717 ataraid(4) functionality is now supported by the RAID GEOM class.
718 To use it you can load geom_raid kernel module and use graid(8) tool
719 for management. Instead of /dev/arX device names, use /dev/raid/rX.
721 No kernel config options or code have been removed, so if a problem
722 arises, please report it and optionally revert to the old ATA stack.
723 In order to do it you can remove from the kernel config:
728 , and instead add back:
729 device atadisk # ATA disk drives
730 device ataraid # ATA RAID drives
731 device atapicd # ATAPI CDROM drives
732 device atapifd # ATAPI floppy drives
733 device atapist # ATAPI tape drives
736 The default NFS server has been changed to the new server, which
737 was referred to as the experimental server. If you need to switch
738 back to the old NFS server, you must now put the "-o" option on
739 both the mountd and nfsd commands. This can be done using the
740 mountd_flags and nfs_server_flags rc.conf variables until an
741 update to the rc scripts is committed, which is coming soon.
744 The GNU Objective-C runtime library (libobjc), and other Objective-C
745 related components have been removed from the base system. If you
746 require an Objective-C library, please use one of the available ports.
749 ath(4) has been split into bus- and device- modules. if_ath contains
750 the HAL, the TX rate control and the network device code. if_ath_pci
751 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
752 contains the AHB glue. Users need to load both if_ath_pci and if_ath
753 in order to use ath on everything else.
755 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
756 need to load if_ath and if_ath_pci for ath(4) operation.
759 As part of the replacement of sysinstall, the process of building
760 release media has changed significantly. For details, please re-read
761 release(7), which has been updated to reflect the new build process.
764 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
765 is the last available version under GPLv2. It brings a number of new
766 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
767 4.1 and SSE 4.2), better support for powerpc64, a number of new
768 directives, and lots of other small improvements. See the ChangeLog
769 file in contrib/binutils for the full details.
772 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
773 compliant, and will now use half of hash for authentication.
774 This will break interoperability with all stacks (including all
775 actual FreeBSD versions) who implement
776 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
778 The only workaround with such peers is to use another HMAC
779 algorithm for IPsec ("phase 2") authentication.
782 Remove the uio_yield prototype and symbol. This function has
783 been misnamed since it was introduced and should not be
784 globally exposed with this name. The equivalent functionality
785 is now available using kern_yield(curthread->td_user_pri).
786 The function remains undocumented.
789 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
790 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
791 for scalar sysctls is defined but disabled. Code that needs
792 UQUAD to pass the type checking that must compile on older
793 systems where the define is not present can check against
794 __FreeBSD_version >= 900030.
796 The system dialog(1) has been replaced with a new version previously
797 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
798 with the previous version, but the libdialog associated with it has
799 a largely incompatible API. As such, the original version of libdialog
800 will be kept temporarily as libodialog, until its base system consumers
801 are replaced or updated. Bump __FreeBSD_version to 900030.
804 If you are trying to run make universe on a -stable system, and you get
805 the following warning:
806 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
807 unknown. config(8) likely too old."
808 or something similar to it, then you must upgrade your -stable system
809 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
810 stable/8) or build the config from the latest stable/8 branch and
811 install it on your system.
813 Prior to this date, building a current universe on 8-stable system from
814 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
815 error in the first kernel build phase. A new config on those old
816 systems will fix that problem for older versions of -current.
819 The TCP stack has been modified to allow Khelp modules to interact with
820 it via helper hook points and store per-connection data in the TCP
821 control block. Bump __FreeBSD_version to 900029. User space tools that
822 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
826 Generic IEEE 802.3 annex 31B full duplex flow control support has been
827 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
828 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
829 to take advantage of it instead of using custom implementations. This
830 means that these drivers now no longer unconditionally advertise
831 support for flow control but only do so if flow control is a selected
832 media option. This was implemented in the generic support that way in
833 order to allow flow control to be switched on and off via ifconfig(8)
834 with the PHY specific default to typically off in order to protect
835 from unwanted effects. Consequently, if you used flow control with
836 one of the above mentioned drivers you now need to explicitly enable
838 ifconfig bge0 media auto mediaopt flowcontrol
840 Along with the above mentioned changes generic support for setting
841 1000baseT master mode also has been added and brgphy(4), ciphy(4),
842 e1000phy(4) as well as ip1000phy(4) have been converted to take
843 advantage of it. This means that these drivers now no longer take the
844 link0 parameter for selecting master mode but the master media option
845 has to be used instead, for example like in the following:
846 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
848 Selection of master mode now is also available with all other PHY
849 drivers supporting 1000baseT.
852 The TCP stack has received a significant update to add support for
853 modularised congestion control and generally improve the clarity of
854 congestion control decisions. Bump __FreeBSD_version to 900025. User
855 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
856 sockstat) need to be recompiled.
859 The man(1) utility has been replaced by a new version that no longer
860 uses /etc/manpath.config. Please consult man.conf(5) for how to
861 migrate local entries to the new format.
864 The copyright strings printed by login(1) and sshd(8) at the time of a
865 new connection have been removed to follow other operating systems and
869 A workaround for a fixed ld bug has been removed in kernel code,
870 so make sure that your system ld is built from sources after
871 revision 210245 from 2010-07-19 (r211583 if building head kernel
872 on stable/8, r211584 for stable/7; both from 2010-08-21).
873 A symptom of incorrect ld version is different addresses for
874 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
877 The $ipv6_prefer variable in rc.conf(5) has been split into
878 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
880 The $ip6addrctl_policy is a variable to choose a pre-defined
881 address selection policy set by ip6addrctl(8). A value
882 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
885 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
886 flag (see an entry of 20090926) is set on an interface with no
887 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
888 security reason. If you want IPv6 link-local address on all
889 interfaces by default, set this to "YES".
891 The old ipv6_prefer="YES" is equivalent to
892 ipv6_activate_all_interfaces="YES" and
893 ip6addrctl_policy="ipv6_prefer".
896 DTrace has grown support for userland tracing. Due to this, DTrace is
897 now i386 and amd64 only.
898 dtruss(1) is now installed by default on those systems and a new
899 kernel module is needed for userland tracing: fasttrap.
900 No changes to your kernel config file are necessary to enable
901 userland tracing, but you might consider adding 'STRIP=' and
902 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
903 to have informative userland stack traces in DTrace (ustack).
906 The acpi_aiboost(4) driver has been removed in favor of the new
907 aibs(4) driver. You should update your kernel configuration file.
910 BSD grep has been imported to the base system and it is built by
911 default. It is completely BSD licensed, highly GNU-compatible, uses
912 less memory than its GNU counterpart and has a small codebase.
913 However, it is slower than its GNU counterpart, which is mostly
914 noticeable for larger searches, for smaller ones it is measurable
915 but not significant. The reason is complex, the most important factor
916 is that we lack a modern and efficient regex library and GNU
917 overcomes this by optimizing the searches internally. Future work
918 on improving the regex performance is planned, for the meantime,
919 users that need better performance, can build GNU grep instead by
920 setting the WITH_GNU_GREP knob.
923 Due to the import of powerpc64 support, all existing powerpc kernel
924 configuration files must be updated with a machine directive like this:
925 machine powerpc powerpc
927 In addition, an updated config(8) is required to build powerpc kernels
931 A new version of ZFS (version 15) has been merged to -HEAD.
932 This version uses a python library for the following subcommands:
933 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
934 For full functionality of these commands the following port must
935 be installed: sysutils/py-zfs
938 'vm_page's are now hashed by physical address to an array of mutexes.
939 Currently this is only used to serialize access to hold_count. Over
940 time the page queue mutex will be peeled away. This changes the size
941 of pmap on every architecture. And requires all callers of vm_page_hold
942 and vm_page_unhold to be updated.
945 WITH_CTF can now be specified in src.conf (not recommended, there
946 are some problems with static executables), make.conf (would also
947 affect ports which do not use GNU make and do not override the
948 compile targets) or in the kernel config (via "makeoptions
950 When WITH_CTF was specified there before this was silently ignored,
951 so make sure that WITH_CTF is not used in places which could lead
952 to unwanted behavior.
955 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
956 to allow 32-bit compatibility on non-x86 platforms. All kernel
957 configurations on amd64 and ia64 platforms using these options must
958 be modified accordingly.
961 The utmp user accounting database has been replaced with utmpx,
962 the user accounting interface standardized by POSIX.
963 Unfortunately the semantics of utmp and utmpx don't match,
964 making it practically impossible to support both interfaces.
965 The user accounting database is used by tools like finger(1),
966 last(1), talk(1), w(1) and ac(8).
968 All applications in the base system use utmpx. This means only
969 local binaries (e.g. from the ports tree) may still use these
970 utmp database files. These applications must be rebuilt to make
973 After the system has been upgraded, it is safe to remove the old
974 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
975 assuming their contents is of no importance anymore. Old wtmp
976 databases can only be used by last(1) and ac(8) after they have
977 been converted to the new format using wtmpcvt(1).
980 Introduce the kernel thread "deadlock resolver" (which can be enabled
981 via the DEADLKRES option, see NOTES for more details) and the
982 sleepq_type() function for sleepqueues.
985 The rc.firewall and rc.firewall6 were unified, and
986 rc.firewall6 and rc.d/ip6fw were removed.
987 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
988 variables are obsoleted. Instead, the following new rc
989 variables are added to rc.d/ipfw:
991 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
992 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
993 firewall_simple_onet_ipv6, firewall_trusted_ipv6
995 The meanings correspond to the relevant IPv4 variables.
1001 The default terminal emulation for syscons(4) has been changed
1002 from cons25 to xterm on all platforms except pc98. This means
1003 that the /etc/ttys file needs to be updated to ensure correct
1004 operation of applications on the console.
1006 The terminal emulation style can be toggled per window by using
1007 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1008 options can be used to change the compile-time default back to
1011 To prevent graphical artifacts, make sure the TERM environment
1012 variable is set to match the terminal emulation that is being
1013 performed by syscons(4).
1016 The layout of the structure ieee80211req_scan_result has changed.
1017 Applications that require wireless scan results (e.g. ifconfig(8))
1018 from net80211 need to be recompiled.
1020 Applications such as wpa_supplicant(8) may require a full world
1021 build without using NO_CLEAN in order to get synchronized with the
1025 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1026 There's one kernel module for each firmware. Adding "device iwnfw"
1027 to the kernel configuration file means including all three firmware
1028 images inside the kernel. If you want to include just the one for
1029 your wireless card, use the devices iwn4965fw, iwn5000fw or
1033 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1034 into rc.d/netif. The changes are the following:
1036 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1037 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1038 Note that both variables need the "inet6" keyword at the head.
1040 Do not set $ipv6_network_interfaces manually if you do not
1041 understand what you are doing. It is not needed in most cases.
1043 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1046 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1047 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1049 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1050 all configured interfaces have "inet6 accept_rtadv" in the
1051 $ifconfig_IF_ipv6. These are for backward compatibility.
1053 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1054 functionality of interfaces with no corresponding
1055 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1056 and the default address selection policy of ip6addrctl(8)
1057 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1058 Note that if you want to configure IPv6 functionality on the
1059 disabled interfaces after boot, first you need to clear the flag by
1060 using ifconfig(8) like:
1062 ifconfig em0 inet6 -ifdisabled
1064 If YES, the default address selection policy is set as
1067 The default value of $ipv6_prefer is NO.
1069 4. If your system need to receive Router Advertisement messages,
1070 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1071 scripts automatically invoke rtsol(8) when the interface becomes
1072 UP. The Router Advertisement messages are used for SLAAC
1073 (State-Less Address AutoConfiguration).
1076 802.11s D3.03 support was committed. This is incompatible with the
1077 previous code, which was based on D3.0.
1080 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1081 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1082 control whether accepting Router Advertisement messages or not.
1083 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1084 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1085 The ifconfig(8) utility now supports these flags.
1088 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1089 mount(8) and -a option for df(1) to see them.
1092 The old tunable hw.bus.devctl_disable has been superseded by
1093 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1094 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1098 Remove the option STOP_NMI. The default action is now to use NMI only
1099 for KDB via the newly introduced function stop_cpus_hard() and
1100 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1103 The stable/8 branch created in subversion. This corresponds to the
1104 RELENG_8 branch in CVS.
1107 Bump the shared library version numbers for all libraries that do not
1108 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1109 __FreeBSD_version to 800105.
1112 Due to changes in the implementation of virtual network stack support,
1113 all network-related kernel modules must be recompiled. As this change
1114 breaks the ABI, bump __FreeBSD_version to 800104.
1117 The TOE interface to the TCP syncache has been modified to remove
1118 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1119 The cxgb driver is the only TOE consumer affected by this change, and
1120 needs to be recompiled along with the kernel. As this change breaks
1121 the ABI, bump __FreeBSD_version to 800103.
1124 Padding has been added to struct tcpcb, sackhint and tcpstat in
1125 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1126 maintaining the ABI. However, this change breaks the ABI, so bump
1127 __FreeBSD_version to 800102. User space tools that rely on the size of
1128 any of these structs (e.g. sockstat) need to be recompiled.
1131 The NFS_LEGACYRPC option has been removed along with the old kernel
1132 RPC implementation that this option selected. Kernel configurations
1133 may need to be adjusted.
1136 The network interface device nodes at /dev/net/<interface> have been
1137 removed. All ioctl operations can be performed the normal way using
1138 routing sockets. The kqueue functionality can generally be replaced
1139 with routing sockets.
1142 The documentation from the FreeBSD Documentation Project (Handbook,
1143 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1144 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1147 The ABI of various structures related to the SYSV IPC API have been
1148 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1149 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1153 Layout of struct vnet has changed as routing related variables were
1154 moved to their own Vimage module. Modules need to be recompiled. Bump
1155 __FreeBSD_version to 800099.
1158 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1159 respectively. As long as no more than 16 groups per process are used,
1160 no changes should be visible. When more than 16 groups are used, old
1161 binaries may fail if they call getgroups() or getgrouplist() with
1162 statically sized storage. Recompiling will work around this, but
1163 applications should be modified to use dynamically allocated storage
1164 for group arrays as POSIX.1-2008 does not cap an implementation's
1165 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1167 NFS and portalfs mounts may also be affected as the list of groups is
1168 truncated to 16. Users of NFS who use more than 16 groups, should
1169 take care that negative group permissions are not used on the exported
1170 file systems as they will not be reliable unless a GSSAPI based
1171 authentication method is used.
1174 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1175 option compiles in the support for adaptive spinning for lockmgrs
1176 which want to enable it. The lockinit() function now accepts the flag
1177 LK_ADAPTIVE in order to make the lock object subject to adaptive
1178 spinning when both held in write and read mode.
1181 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1182 changed. User applications that use this ioctl need to be rebuilt.
1185 The layout of struct thread has changed. Kernel and modules need to
1189 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1190 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1193 window(1) has been removed from the base system. It can now be
1194 installed from ports. The port is called misc/window.
1197 The way we are storing and accessing `routing table' entries has
1198 changed. Programs reading the FIB, like netstat, need to be
1202 A new netisr implementation has been added for FreeBSD 8. Network
1203 file system modules, such as igmp, ipdivert, and others, should be
1205 Bump __FreeBSD_version to 800096.
1208 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1212 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1213 Bump __FreeBSD_version to 800094.
1216 Add mnt_xflag field to 'struct mount'. File system modules need to be
1218 Bump __FreeBSD_version to 800093.
1221 The compiling option ADAPTIVE_SX has been retired while it has been
1222 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1223 The KPI for sx_init_flags() changes as accepting flags:
1224 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1225 been introduced in order to handle the reversed logic.
1226 Bump __FreeBSD_version to 800092.
1229 Add support for hierarchical jails. Remove global securelevel.
1230 Bump __FreeBSD_version to 800091.
1233 The layout of struct vnet_net has changed, therefore modules
1235 Bump __FreeBSD_version to 800090.
1238 The newly imported zic(8) produces a new format in the output. Please
1239 run tzsetup(8) to install the newly created data to /etc/localtime.
1242 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1243 hw.usb.* and is now consistent again with previous releases.
1246 802.11 monitor mode support was revised and driver api's were changed.
1247 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1248 of DLT_IEEE802_11. No user-visible data structures were changed but
1249 applications that use DLT_IEEE802_11 may require changes.
1250 Bump __FreeBSD_version to 800088.
1253 The layout of the following structs has changed: sysctl_oid,
1254 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1255 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1256 panics may be experienced. World rebuild is required for
1257 correctly checking networking state from userland.
1258 Bump __FreeBSD_version to 800085.
1261 MLDv2 and Source-Specific Multicast (SSM) have been merged
1262 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1263 The implementation of SSM within FreeBSD's IPv6 stack closely
1264 follows the IPv4 implementation.
1266 For kernel developers:
1268 * The most important changes are that the ip6_output() and
1269 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1270 and this lock has been downgraded to a non-recursive mutex.
1272 * As with the changes to the IPv4 stack to support SSM, filtering
1273 of inbound multicast traffic must now be performed by transport
1274 protocols within the IPv6 stack. This does not apply to TCP and
1275 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1277 * The KPIs used by IPv6 multicast are similar to those used by
1278 the IPv4 stack, with the following differences:
1279 * im6o_mc_filter() is analogous to imo_multicast_filter().
1280 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1281 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1282 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1283 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1284 for MLDv1 have an additional 'timer' argument which is used to
1285 jitter the initial membership report for the solicited-node
1286 multicast membership on-link.
1287 * This is not strictly needed for MLDv2, which already jitters
1288 its report transmissions. However, the 'timer' argument is
1289 preserved in case MLDv1 is active on the interface.
1291 * The KAME linked-list based IPv6 membership implementation has
1292 been refactored to use a vector similar to that used by the IPv4
1294 Code which maintains a list of its own multicast memberships
1295 internally, e.g. carp, has been updated to reflect the new
1298 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1299 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1300 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1301 implementation constraint which needs to be addressed in HEAD.
1303 For application developers:
1305 * The changes are broadly similar to those made for the IPv4
1308 * The use of IPv4 and IPv6 multicast socket options on the same
1309 socket, using mapped addresses, HAS NOT been tested or supported.
1311 * There are a number of issues with the implementation of various
1312 IPv6 multicast APIs which need to be resolved in the API surface
1313 before the implementation is fully compatible with KAME userland
1314 use, and these are mostly to do with interface index treatment.
1316 * The literature available discusses the use of either the delta / ASM
1317 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1318 using setsourcefilter(3)/getsourcefilter(3). For more information
1319 please refer to RFC 3768, 'Socket Interface Extensions for
1320 Multicast Source Filters'.
1322 * Applications which use the published RFC 3678 APIs should be fine.
1324 For systems administrators:
1326 * The mtest(8) utility has been refactored to support IPv6, in
1327 addition to IPv4. Interface addresses are no longer accepted
1328 as arguments, their names must be used instead. The utility
1329 will map the interface name to its first IPv4 address as
1330 returned by getifaddrs(3).
1332 * The ifmcstat(8) utility has also been updated to print the MLDv2
1333 endpoint state and source filter lists via sysctl(3).
1335 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1336 loopback of IPv6 multicast datagrams by default; it defaults to 1
1337 to preserve the existing behaviour. Disabling multicast loopback is
1338 recommended for optimal system performance.
1340 * The IPv6 MROUTING code has been changed to examine this sysctl
1341 instead of attempting to perform a group lookup before looping
1342 back forwarded datagrams.
1344 Bump __FreeBSD_version to 800084.
1347 Implement low-level Bluetooth HCI API.
1348 Bump __FreeBSD_version to 800083.
1351 The layout of struct malloc_type, used by modules to register new
1352 memory allocation types, has changed. Most modules will need to
1353 be rebuilt or panics may be experienced.
1354 Bump __FreeBSD_version to 800081.
1357 Anticipate overflowing inp_flags - add inp_flags2.
1358 This changes most offsets in inpcb, so checking v4 connection
1359 state will require a world rebuild.
1360 Bump __FreeBSD_version to 800080.
1363 Add an llentry to struct route and struct route_in6. Modules
1364 embedding a struct route will need to be recompiled.
1365 Bump __FreeBSD_version to 800079.
1368 The size of rt_metrics_lite and by extension rtentry has changed.
1369 Networking administration apps will need to be recompiled.
1370 The route command now supports show as an alias for get, weighting
1371 of routes, sticky and nostick flags to alter the behavior of stateful
1373 Bump __FreeBSD_version to 800078.
1376 Do not use Giant for kbdmux(4) locking. This is wrong and
1377 apparently causing more problems than it solves. This will
1378 re-open the issue where interrupt handlers may race with
1379 kbdmux(4) in polling mode. Typical symptoms include (but
1380 not limited to) duplicated and/or missing characters when
1381 low level console functions (such as gets) are used while
1382 interrupts are enabled (for example geli password prompt,
1383 mountroot prompt etc.). Disabling kbdmux(4) may help.
1386 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1387 kernel modules referencing any of the above need to be recompiled.
1388 Bump __FreeBSD_version to 800075.
1391 GEOM_PART has become the default partition slicer for storage devices,
1392 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1393 introduces some changes:
1395 MSDOS/EBR: the devices created from MSDOS extended partition entries
1396 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1397 to devices with offset-based names. fstabs may need to be modified.
1399 BSD: the "geometry does not match label" warning is harmless in most
1400 cases but it points to problems in file system misalignment with
1401 disk geometry. The "c" partition is now implicit, covers the whole
1402 top-level drive and cannot be (mis)used by users.
1404 General: Kernel dumps are now not allowed to be written to devices
1405 whose partition types indicate they are meant to be used for file
1406 systems (or, in case of MSDOS partitions, as something else than
1409 Most of these changes date approximately from 200812.
1412 The uscanner(4) driver has been removed from the kernel. This follows
1413 Linux removing theirs in 2.6 and making libusb the default interface
1414 (supported by sane).
1417 The multicast forwarding code has been cleaned up. netstat(1)
1418 only relies on KVM now for printing bandwidth upcall meters.
1419 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1420 ip6_mroute_mod respectively. The config(5) options for statically
1421 compiling this code remain the same, i.e. 'options MROUTING'.
1424 Support for the IFF_NEEDSGIANT network interface flag has been
1425 removed, which means that non-MPSAFE network device drivers are no
1426 longer supported. In particular, if_ar, if_sr, and network device
1427 drivers from the old (legacy) USB stack can no longer be built or
1431 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1432 a bunch of new language catalog files have also been added.
1433 This means that some common libc messages are now localized and
1434 they depend on the LC_MESSAGES environmental variable.
1437 The k8temp(4) driver has been renamed to amdtemp(4) since
1438 support for Family 10 and Family 11 CPU families was added.
1441 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1442 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1444 For kernel developers, the most important changes are that the
1445 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1446 and this lock has been downgraded to a non-recursive mutex.
1448 Transport protocols (UDP, Raw IP) are now responsible for filtering
1449 inbound multicast traffic according to group membership and source
1450 filters. The imo_multicast_filter() KPI exists for this purpose.
1451 Transports which do not use multicast (SCTP, TCP) already reject
1452 multicast by default. Forwarding and receive performance may improve
1453 as a mutex acquisition is no longer needed in the ip_input()
1454 low-level input path. in_addmulti() and in_delmulti() are shimmed
1455 to new KPIs which exist to support SSM in-kernel.
1457 For application developers, it is recommended that loopback of
1458 multicast datagrams be disabled for best performance, as this
1459 will still cause the lock to be taken for each looped-back
1460 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1461 be tuned to 0 to disable loopback by default; it defaults to 1
1462 to preserve the existing behaviour.
1464 For systems administrators, to obtain best performance with
1465 multicast reception and multiple groups, it is always recommended
1466 that a card with a suitably precise hash filter is used. Hash
1467 collisions will still result in the lock being taken within the
1468 transport protocol input path to check group membership.
1470 If deploying FreeBSD in an environment with IGMP snooping switches,
1471 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1472 enabled; this forces 224.0.0.0/24 group membership to be announced
1475 The size of 'struct igmpstat' has changed; netstat needs to be
1476 recompiled to reflect this.
1477 Bump __FreeBSD_version to 800070.
1480 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1481 updated to use it. This requires a buildworld/installworld in order to
1482 update the library and dependencies (usbconfig, etc). Its advisable to
1483 rebuild all ports which uses libusb. More specific directions are given
1484 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1485 libusb are no longer required and can be removed.
1488 A workaround is committed to allow the creation of System V shared
1489 memory segment of size > 2 GB on the 64-bit architectures.
1490 Due to a limitation of the existing ABI, the shm_segsz member
1491 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1492 wrong for large segments. Note that limits must be explicitly
1493 raised to allow such segments to be created.
1496 The layout of struct ifnet has changed, requiring a rebuild of all
1497 network device driver modules.
1500 The /dev handling for the new USB stack has changed, a
1501 buildworld/installworld is required for libusb20.
1504 The new USB2 stack has now been permanently moved in and all kernel and
1505 module names reverted to their previous values (eg, usb, ehci, ohci,
1506 ums, ...). The old usb stack can be compiled in by prefixing the name
1507 with the letter 'o', the old usb modules have been removed.
1508 Updating entry 20090216 for xorg and 20090215 for libmap may still
1512 The rc.conf(5) option if_up_delay has been renamed to
1513 defaultroute_delay to better reflect its purpose. If you have
1514 customized this setting in /etc/rc.conf you need to update it to
1518 xorg 7.4 wants to configure its input devices via hald which does not
1519 yet work with USB2. If the keyboard/mouse does not work in xorg then
1521 Option "AllowEmptyInput" "off"
1522 to your ServerLayout section. This will cause X to use the configured
1523 kbd and mouse sections from your xorg.conf.
1526 The GENERIC kernels for all architectures now default to the new USB2
1527 stack. No kernel config options or code have been removed so if a
1528 problem arises please report it and optionally revert to the old USB
1529 stack. If you are loading USB kernel modules or have a custom kernel
1530 that includes GENERIC then ensure that usb names are also changed over,
1531 eg uftdi -> usb2_serial_ftdi.
1533 Older programs linked against the ports libusb 0.1 need to be
1534 redirected to the new stack's libusb20. /etc/libmap.conf can
1536 # Map old usb library to new one for usb2 stack
1537 libusb-0.1.so.8 libusb20.so.1
1540 All USB ethernet devices now attach as interfaces under the name ueN
1541 (eg. ue0). This is to provide a predictable name as vendors often
1542 change usb chipsets in a product without notice.
1545 The ichsmb(4) driver has been changed to require SMBus slave
1546 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1547 All of the other SMBus controller drivers require left-justified
1548 slave addresses, so this change makes all the drivers provide the
1552 INET6 statistics (struct ip6stat) was updated.
1553 netstat(1) needs to be recompiled.
1556 NTFS has been removed from GENERIC kernel on amd64 to match
1557 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1558 will load ntfs.ko module automatically when NTFS support is
1559 actually needed, unless ntfs.ko is not installed or security
1560 level prohibits loading kernel modules. If either is the case,
1561 "options NTFS" has to be added into kernel config.
1564 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1565 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1566 800061. User space tools that rely on the size of struct tcpcb in
1567 tcp_var.h (e.g. sockstat) need to be recompiled.
1570 ng_tty(4) module updated to match the new TTY subsystem.
1571 Due to API change, user-level applications must be updated.
1572 New API support added to mpd5 CVS and expected to be present
1573 in next mpd5.3 release.
1576 With __FreeBSD_version 800060 the makefs tool is part of
1577 the base system (it was a port).
1580 The afdata and ifnet locks have been changed from mutexes to
1581 rwlocks, network modules will need to be re-compiled.
1584 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1585 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1586 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1587 architecture and 40 bytes on 64-bit architecture. The userland
1588 applications "arp" and "ndp" have been updated accordingly.
1589 The output from "netstat -r" shows only routing entries and
1590 none of the L2 information.
1593 __FreeBSD_version 800057 marks the switchover from the
1594 binary ath hal to source code. Users must add the line:
1596 options AH_SUPPORT_AR5416
1598 to their kernel config files when specifying:
1602 The ath_hal module no longer exists; the code is now compiled
1603 together with the driver in the ath module. It is now
1604 possible to tailor chip support (i.e. reduce the set of chips
1605 and thereby the code size); consult ath_hal(4) for details.
1608 __FreeBSD_version 800054 adds memory barriers to
1609 <machine/atomic.h>, new interfaces to ifnet to facilitate
1610 multiple hardware transmit queues for cards that support
1611 them, and a lock-less ring-buffer implementation to
1612 enable drivers to more efficiently manage queueing of
1616 A new version of ZFS (version 13) has been merged to -HEAD.
1617 This version has zpool attribute "listsnapshots" off by
1618 default, which means "zfs list" does not show snapshots,
1619 and is the same as Solaris behavior.
1622 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1625 The uhci, ohci, ehci and slhci USB Host controller drivers have
1626 been put into separate modules. If you load the usb module
1627 separately through loader.conf you will need to load the
1628 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1629 controller add the following to loader.conf:
1635 The ABI used by the PMC toolset has changed. Please keep
1636 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1640 atapci kernel module now includes only generic PCI ATA
1641 driver. AHCI driver moved to ataahci kernel module.
1642 All vendor-specific code moved into separate kernel modules:
1643 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1644 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1645 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1646 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1649 The TTY subsystem of the kernel has been replaced by a new
1650 implementation, which provides better scalability and an
1651 improved driver model. Most common drivers have been migrated to
1652 the new TTY subsystem, while others have not. The following
1653 drivers have not yet been ported to the new TTY layer:
1656 cy, digi, rc, rp, sio
1662 ng_h4, ng_tty, ppp, sl, snp
1664 Adding these drivers to your kernel configuration file shall
1665 cause compilation to fail.
1668 ntpd has been upgraded to 4.2.4p5.
1671 OpenSSH has been upgraded to 5.1p1.
1673 For many years, FreeBSD's version of OpenSSH preferred DSA
1674 over RSA for host and user authentication keys. With this
1675 upgrade, we've switched to the vendor's default of RSA over
1676 DSA. This may cause upgraded clients to warn about unknown
1677 host keys even for previously known hosts. Users should
1678 follow the usual procedure for verifying host keys before
1679 accepting the RSA key.
1681 This can be circumvented by setting the "HostKeyAlgorithms"
1682 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1685 Please note that the sequence of keys offered for
1686 authentication has been changed as well. You may want to
1687 specify IdentityFile in a different order to revert this
1691 The sio(4) driver has been removed from the i386 and amd64
1692 kernel configuration files. This means uart(4) is now the
1693 default serial port driver on those platforms as well.
1695 To prevent collisions with the sio(4) driver, the uart(4) driver
1696 uses different names for its device nodes. This means the
1697 onboard serial port will now most likely be called "ttyu0"
1698 instead of "ttyd0". You may need to reconfigure applications to
1699 use the new device names.
1701 When using the serial port as a boot console, be sure to update
1702 /boot/device.hints and /etc/ttys before booting the new kernel.
1703 If you forget to do so, you can still manually specify the hints
1704 at the loader prompt:
1706 set hint.uart.0.at="isa"
1707 set hint.uart.0.port="0x3F8"
1708 set hint.uart.0.flags="0x10"
1709 set hint.uart.0.irq="4"
1713 The gpt(8) utility has been removed. Use gpart(8) to partition
1717 The version that Linuxulator emulates was changed from 2.4.2
1718 to 2.6.16. If you experience any problems with Linux binaries
1719 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1720 if it fixes the problem contact emulation mailing list.
1723 ISDN4BSD (I4B) was removed from the src tree. You may need to
1724 update a your kernel configuration and remove relevant entries.
1727 I have checked in code to support multiple routing tables.
1728 See the man pages setfib(1) and setfib(2).
1729 This is a hopefully backwards compatible version,
1730 but to make use of it you need to compile your kernel
1731 with options ROUTETABLES=2 (or more up to 16).
1734 The 802.11 wireless support was redone to enable multi-bss
1735 operation on devices that are capable. The underlying device
1736 is no longer used directly but instead wlanX devices are
1737 cloned with ifconfig. This requires changes to rc.conf files.
1738 For example, change:
1739 ifconfig_ath0="WPA DHCP"
1742 ifconfig_wlan0="WPA DHCP"
1743 see rc.conf(5) for more details. In addition, mergemaster of
1744 /etc/rc.d is highly recommended. Simultaneous update of userland
1745 and kernel wouldn't hurt either.
1747 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1748 modules were merged into the base wlan module. All references
1749 to these modules (e.g. in kernel config files) must be removed.
1752 psm(4) has gained write(2) support in native operation level.
1753 Arbitrary commands can be written to /dev/psm%d and status can
1754 be read back from it. Therefore, an application is responsible
1755 for status validation and error recovery. It is a no-op in
1756 other operation levels.
1759 Support for KSE threading has been removed from the kernel. To
1760 run legacy applications linked against KSE libmap.conf may
1761 be used. The following libmap.conf may be used to ensure
1762 compatibility with any prior release:
1764 libpthread.so.1 libthr.so.1
1765 libpthread.so.2 libthr.so.2
1766 libkse.so.3 libthr.so.3
1769 The layout of struct vmspace has changed. This affects libkvm
1770 and any executables that link against libkvm and use the
1771 kvm_getprocs() function. In particular, but not exclusively,
1772 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1773 The effects are minimal, but it's advisable to upgrade world
1777 The latest em driver no longer has support in it for the
1778 82575 adapter, this is now moved to the igb driver. The
1779 split was done to make new features that are incompatible
1780 with older hardware easier to do.
1783 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1784 likewise the kernel option is now GEOM_LINUX_LVM.
1787 The default NFS mount mode has changed from UDP to TCP for
1788 increased reliability. If you rely on (insecurely) NFS
1789 mounting across a firewall you may need to update your
1793 Belatedly note the addition of m_collapse for compacting
1797 The fts(3) structures have been changed to use adequate
1798 integer types for their members and so to be able to cope
1799 with huge file trees. The old fts(3) ABI is preserved
1800 through symbol versioning in libc, so third-party binaries
1801 using fts(3) should still work, although they will not take
1802 advantage of the extended types. At the same time, some
1803 third-party software might fail to build after this change
1804 due to unportable assumptions made in its source code about
1805 fts(3) structure members. Such software should be fixed
1806 by its vendor or, in the worst case, in the ports tree.
1807 FreeBSD_version 800015 marks this change for the unlikely
1808 case that a portable fix is impossible.
1811 To upgrade to -current after this date, you must be running
1812 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1813 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1816 The ADAPTIVE_GIANT kernel option has been retired because its
1817 functionality is the default now.
1820 The AT keyboard emulation of sunkbd(4) has been turned on
1821 by default. In order to make the special symbols of the Sun
1822 keyboards driven by sunkbd(4) work under X these now have
1823 to be configured the same way as Sun USB keyboards driven
1824 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1826 Option "XkbLayout" "us"
1827 Option "XkbRules" "xorg"
1828 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1831 It has been decided that it is desirable to provide ABI
1832 backwards compatibility to the FreeBSD 4/5/6 versions of the
1833 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1834 broken with the introduction of PCI domain support (see the
1835 20070930 entry). Unfortunately, this required the ABI of
1836 PCIOCGETCONF to be broken again in order to be able to
1837 provide backwards compatibility to the old version of that
1838 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1839 again. As for prominent ports this affects neither pciutils
1840 nor xorg-server this time, the hal port needs to be rebuilt
1844 The misnamed kthread_create() and friends have been renamed
1845 to kproc_create() etc. Many of the callers already
1846 used kproc_start()..
1847 I will return kthread_create() and friends in a while
1848 with implementations that actually create threads, not procs.
1849 Renaming corresponds with version 800002.
1858 Avoid using make -j when upgrading. While generally safe, there are
1859 sometimes problems using -j to upgrade. If your upgrade fails with
1860 -j, please try again without -j. From time to time in the past there
1861 have been problems using -j with buildworld and/or installworld. This
1862 is especially true when upgrading between "distant" versions (eg one
1863 that cross a major release boundary or several minor releases, or when
1864 several months have passed on the -current branch).
1866 Sometimes, obscure build problems are the result of environment
1867 poisoning. This can happen because the make utility reads its
1868 environment when searching for values for global variables. To run
1869 your build attempts in an "environmental clean room", prefix all make
1870 commands with 'env -i '. See the env(1) manual page for more details.
1872 When upgrading from one major version to another it is generally best
1873 to upgrade to the latest code in the currently installed branch first,
1874 then do an upgrade to the new branch. This is the best-tested upgrade
1875 path, and has the highest probability of being successful. Please try
1876 this approach before reporting problems with a major version upgrade.
1878 When upgrading a live system, having a root shell around before
1879 installing anything can help undo problems. Not having a root shell
1880 around can lead to problems if pam has changed too much from your
1881 starting point to allow continued authentication after the upgrade.
1885 When upgrading the boot ZFS pool to a new version, always follow
1888 1.) recompile and reinstall the ZFS boot loader and boot block
1889 (this is part of "make buildworld" and "make installworld")
1891 2.) update the ZFS boot block on your boot drive
1893 The following example updates the ZFS boot block on the first
1894 partition (freebsd-boot) of a GPT partitioned drive ad0:
1895 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1897 Non-boot pools do not need these updates.
1901 If you are updating from a prior version of FreeBSD (even one just
1902 a few days old), you should follow this procedure. It is the most
1903 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1905 make kernel-toolchain
1906 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1907 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1909 To test a kernel once
1910 ---------------------
1911 If you just want to boot a kernel once (because you are not sure
1912 if it works, or if you want to boot a known bad kernel to provide
1913 debugging information) run
1914 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1915 nextboot -k testkernel
1917 To just build a kernel when you know that it won't mess you up
1918 --------------------------------------------------------------
1919 This assumes you are already running a CURRENT system. Replace
1920 ${arch} with the architecture of your machine (e.g. "i386",
1921 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1923 cd src/sys/${arch}/conf
1924 config KERNEL_NAME_HERE
1925 cd ../compile/KERNEL_NAME_HERE
1930 If this fails, go to the "To build a kernel" section.
1932 To rebuild everything and install it on the current system.
1933 -----------------------------------------------------------
1934 # Note: sometimes if you are running current you gotta do more than
1935 # is listed here if you are upgrading from a really old current.
1937 <make sure you have good level 0 dumps>
1939 make kernel KERNCONF=YOUR_KERNEL_HERE
1941 <reboot in single user> [3]
1948 To cross-install current onto a separate partition
1949 --------------------------------------------------
1950 # In this approach we use a separate partition to hold
1951 # current's root, 'usr', and 'var' directories. A partition
1952 # holding "/", "/usr" and "/var" should be about 2GB in
1955 <make sure you have good level 0 dumps>
1958 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1959 <maybe newfs current's root partition>
1960 <mount current's root partition on directory ${CURRENT_ROOT}>
1961 make installworld DESTDIR=${CURRENT_ROOT}
1962 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1963 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1964 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1965 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1966 <reboot into current>
1967 <do a "native" rebuild/install as described in the previous section>
1968 <maybe install compatibility libraries from ports/misc/compat*>
1972 To upgrade in-place from stable to current
1973 ----------------------------------------------
1974 <make sure you have good level 0 dumps>
1976 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1978 <reboot in single user> [3]
1985 Make sure that you've read the UPDATING file to understand the
1986 tweaks to various things you need. At this point in the life
1987 cycle of current, things change often and you are on your own
1988 to cope. The defaults can also change, so please read ALL of
1989 the UPDATING entries.
1991 Also, if you are tracking -current, you must be subscribed to
1992 freebsd-current@freebsd.org. Make sure that before you update
1993 your sources that you have read and understood all the recent
1994 messages there. If in doubt, please track -stable which has
1995 much fewer pitfalls.
1997 [1] If you have third party modules, such as vmware, you
1998 should disable them at this point so they don't crash your
2001 [3] From the bootblocks, boot -s, and then do
2006 adjkerntz -i # if CMOS is wall time
2007 Also, when doing a major release upgrade, it is required that
2008 you boot into single user mode to do the installworld.
2010 [4] Note: This step is non-optional. Failure to do this step
2011 can result in a significant reduction in the functionality of the
2012 system. Attempting to do it by hand is not recommended and those
2013 that pursue this avenue should read this file carefully, as well
2014 as the archives of freebsd-current and freebsd-hackers mailing lists
2015 for potential gotchas. The -U option is also useful to consider.
2016 See mergemaster(8) for more information.
2018 [5] Usually this step is a noop. However, from time to time
2019 you may need to do this if you get unknown user in the following
2020 step. It never hurts to do it all the time. You may need to
2021 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2022 install) after the buildworld before this step if you last updated
2023 from current before 20130425 or from -stable before 20130430.
2025 [6] This only deletes old files and directories. Old libraries
2026 can be deleted by "make delete-old-libs", but you have to make
2027 sure that no program is using those libraries anymore.
2029 [8] In order to have a kernel that can run the 4.x binaries needed to
2030 do an installworld, you must include the COMPAT_FREEBSD4 option in
2031 your kernel. Failure to do so may leave you with a system that is
2032 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2033 required to run the 5.x binaries on more recent kernels. And so on
2034 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2036 Make sure that you merge any new devices from GENERIC since the
2037 last time you updated your kernel config file.
2039 [9] When checking out sources, you must include the -P flag to have
2040 cvs prune empty directories.
2042 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2043 "?=" instead of the "=" assignment operator, so that buildworld can
2044 override the CPUTYPE if it needs to.
2046 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2047 not on the command line, or in /etc/make.conf. buildworld will
2048 warn if it is improperly defined.
2051 This file contains a list, in reverse chronological order, of major
2052 breakages in tracking -current. It is not guaranteed to be a complete
2053 list of such breakages, and only contains entries since October 10, 2007.
2054 If you need to see UPDATING entries from before that date, you will need
2055 to fetch an UPDATING file from an older FreeBSD release.
2057 Copyright information:
2059 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2061 Redistribution, publication, translation and use, with or without
2062 modification, in full or in part, in any form or format of this
2063 document are permitted without further permission from the author.
2065 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2066 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2067 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2068 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2069 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2070 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2071 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2072 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2073 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2074 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2075 POSSIBILITY OF SUCH DAMAGE.
2077 Contact Warner Losh if you have any questions about your use of