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 20140430: p2 FreeBSD-SA-14:07.devfs
21 FreeBSD-SA-14:09.openssl
23 Fix devfs rules not applied by default for jails. [SA-14:07]
25 Fix TCP reassembly vulnerability. [SA-14:08]
27 Fix OpenSSL use-after-free vulnerability. [SA-14:09]
29 20140408: p1 FreeBSD-SA-14:05.nfsserver
30 FreeBSD-SA-14:06.openssl
31 Fix deadlock in the NFS server. [SA-14:05]
33 Fix multiple vulnerabilities in OpenSSL. [SA-14:06]
36 The behavior of gss_pseudo_random() for the krb5 mechanism
37 has changed, for applications requesting a longer random string
38 than produced by the underlying enctype's pseudo-random() function.
39 In particular, the random string produced from a session key of
40 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
41 be different at the 17th octet and later, after this change.
42 The counter used in the PRF+ construction is now encoded as a
43 big-endian integer in accordance with RFC 4402.
46 The default version of mtree is nmtree which is obtained from
47 NetBSD. The output is generally the same, but may vary
48 slightly. If you found you need identical output adding
49 "-F freebsd9" to the command line should do the trick. For the
50 time being, the old mtree is available as fmtree.
53 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
54 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
55 1.1.4_8 and verify bsdyml not linked in, before running "make
57 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
59 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
62 The rc.d/jail script has been updated to support jail(8)
63 configuration file. The "jail_<jname>_*" rc.conf(5) variables
64 for per-jail configuration are automatically converted to
65 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
66 This is transparently backward compatible. See below about some
67 incompatibilities and rc.conf(5) manual page for more details.
69 These variables are now deprecated in favor of jail(8) configuration
70 file. One can use "rc.d/jail config <jname>" command to generate
71 a jail(8) configuration file in /var/run/jail.<jname>.conf without
72 running the jail(8) utility. The default pathname of the
73 configuration file is /etc/jail.conf and can be specified by
74 using $jail_conf or $jail_<jname>_conf variables.
76 Please note that jail_devfs_ruleset accepts an integer at
77 this moment. Please consider to rewrite the ruleset name
81 BIND has been removed from the base system. If all you need
82 is a local resolver, simply enable and start the local_unbound
83 service instead. Otherwise, several versions of BIND are
84 available in the ports tree. The dns/bind99 port is one example.
86 With this change, nslookup(1) and dig(1) are no longer in the base
87 system. Users should instead use host(1) and drill(1) which are
88 in the base system. Alternatively, nslookup and dig can
89 be obtained by installing the dns/bind-tools port.
92 With the addition of unbound(8), a new unbound user is now
93 required during installworld. "mergemaster -p" can be used to
94 add the user prior to installworld, as documented in the handbook.
97 OpenSSH is now built with DNSSEC support, and will by default
98 silently trust signed SSHFP records. This can be controlled with
99 the VerifyHostKeyDNS client configuration setting. DNSSEC support
100 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
103 The GNU Compiler Collection and C++ standard library (libstdc++)
104 are no longer built by default on platforms where clang is the system
105 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
109 The PROCDESC kernel option is now part of the GENERIC kernel
110 configuration and is required for the rwhod(8) to work.
111 If you are using custom kernel configuration, you should include
115 The API and ABI related to the Capsicum framework was modified
116 in backward incompatible way. The userland libraries and programs
117 have to be recompiled to work with the new kernel. This includes the
118 following libraries and programs, but the whole buildworld is
119 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
120 kdump, procstat, rwho, rwhod, uniq.
123 AES-NI intrinsic support has been added to gcc. The AES-NI module
124 has been updated to use this support. A new gcc is required to build
125 the aesni module on both i386 and amd64.
128 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
129 Thus "device padlock_rng" and "device rdrand_rng" should be
130 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
133 WITH_ICONV has been split into two feature sets. WITH_ICONV now
134 enables just the iconv* functionality and is now on by default.
135 WITH_LIBICONV_COMPAT enables the libiconv api and link time
136 compatability. Set WITHOUT_ICONV to build the old way.
137 If you have been using WITH_ICONV before, you will very likely
138 need to turn on WITH_LIBICONV_COMPAT.
141 INVARIANTS option now enables DEBUG for code with OpenSolaris and
142 Illumos origin, including ZFS. If you have INVARIANTS in your
143 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
145 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
146 locks if WITNESS option was set. Because that generated a lot of
147 witness(9) reports and all of them were believed to be false
148 positives, this is no longer done. New option OPENSOLARIS_WITNESS
149 can be used to achieve the previous behavior.
152 Timer values in IPv6 data structures now use time_uptime instead
153 of time_second. Although this is not a user-visible functional
154 change, userland utilities which directly use them---ndp(8),
155 rtadvd(8), and rtsold(8) in the base system---need to be updated
159 find -delete can now delete the pathnames given as arguments,
160 instead of only files found below them or if the pathname did
161 not contain any slashes. Formerly, the following error message
164 find: -delete: <path>: relative path potentially not safe
166 Deleting the pathnames given as arguments can be prevented
167 without error messages using -mindepth 1 or by changing
168 directory and passing "." as argument to find. This works in the
169 old as well as the new version of find.
172 Behavior of devfs rules path matching has been changed.
173 Pattern is now always matched against fully qualified devfs
174 path and slash characters must be explicitly matched by
175 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
176 subdirectories must be reviewed.
179 The default ARM ABI has changed to the ARM EABI. The old ABI is
180 incompatible with the ARM EABI and all programs and modules will
181 need to be rebuilt to work with a new kernel.
183 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
185 NOTE: Support for the old ABI will be removed in the future and
186 users are advised to upgrade.
189 pkg_install has been disconnected from the build if you really need it
190 you should add WITH_PKGTOOLS in your src.conf(5).
193 Most of network statistics structures were changed to be able
194 keep 64-bits counters. Thus all tools, that work with networking
195 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
198 Fix targets that run multiple make's to use && rather than ;
199 so that subsequent steps depend on success of previous.
201 NOTE: if building 'universe' with -j* on stable/8 or stable/9
202 it would be better to start the build using bmake, to avoid
203 overloading the machine.
206 Fix a bug that allowed a tracing process (e.g. gdb) to write
207 to a memory-mapped file in the traced process's address space
208 even if neither the traced process nor the tracing process had
209 write access to that file.
212 CVS has been removed from the base system. An exact copy
213 of the code is available from the devel/cvs port.
216 Some people report the following error after the switch to bmake:
218 make: illegal option -- J
219 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
221 *** [buildworld] Error code 2
223 this likely due to an old instance of make in
224 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
225 which src/Makefile will use that blindly, if it exists, so if
226 you see the above error:
228 rm -rf `make -V MAKEPATH`
233 Use bmake by default.
234 Whereas before one could choose to build with bmake via
235 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
236 make. The goal is to remove these knobs for 10-RELEASE.
238 It is worth noting that bmake (like gmake) treats the command
239 line as the unit of failure, rather than statements within the
240 command line. Thus '(cd some/where && dosomething)' is safer
241 than 'cd some/where; dosomething'. The '()' allows consistent
242 behavior in parallel build.
245 Fix a bug that allows NFS clients to issue READDIR on files.
248 The WITHOUT_IDEA option has been removed because
249 the IDEA patent expired.
252 The sysctl which controls TRIM support under ZFS has been renamed
253 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
257 The mergemaster command now uses the default MAKEOBJDIRPREFIX
258 rather than creating it's own in the temporary directory in
259 order allow access to bootstrapped versions of tools such as
260 install and mtree. When upgrading from version of FreeBSD where
261 the install command does not support -l, you will need to
262 install a new mergemaster command if mergemaster -p is required.
263 This can be accomplished with the command (cd src/usr.sbin/mergemaster
267 Legacy ATA stack, disabled and replaced by new CAM-based one since
268 FreeBSD 9.0, completely removed from the sources. Kernel modules
269 atadisk and atapi*, user-level tools atacontrol and burncd are
270 removed. Kernel option `options ATA_CAM` is now permanently enabled
274 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
275 and socketpair(2). Software, in particular Kerberos, may
276 automatically detect and use these during building. The resulting
277 binaries will not work on older kernels.
280 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
281 information, see the respective 20130304 entry).
284 Recent commits to callout(9) changed the size of struct callout,
285 so the KBI is probably heavily disturbed. Also, some functions
286 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
287 by macros. Every kernel module using it won't load, so rebuild
290 The ctl device has been re-enabled in GENERIC for i386 and amd64,
291 but does not initialize by default (because of the new CTL_DISABLE
292 option) to save memory. To re-enable it, remove the CTL_DISABLE
293 option from the kernel config file or set kern.cam.ctl.disable=0
294 in /boot/loader.conf.
297 The ctl device has been disabled in GENERIC for i386 and amd64.
298 This was done due to the extra memory being allocated at system
299 initialisation time by the ctl driver which was only used if
300 a CAM target device was created. This makes a FreeBSD system
301 unusable on 128MB or less of RAM.
304 A new compression method (lz4) has been merged to -HEAD. Please
305 refer to zpool-features(7) for more information.
307 Please refer to the "ZFS notes" section of this file for information
308 on upgrading boot ZFS pools.
311 A BSD-licensed patch(1) variant has been added and is installed
312 as bsdpatch, being the GNU version the default patch.
313 To inverse the logic and use the BSD-licensed one as default,
314 while having the GNU version installed as gnupatch, rebuild
315 and install world with the WITH_BSD_PATCH knob set.
318 Due to the use of the new -l option to install(1) during build
319 and install, you must take care not to directly set the INSTALL
320 make variable in your /etc/make.conf, /etc/src.conf, or on the
321 command line. If you wish to use the -C flag for all installs
322 you may be able to add INSTALL+=-C to /etc/make.conf or
326 The install(1) option -M has changed meaning and now takes an
327 argument that is a file or path to append logs to. In the
328 unlikely event that -M was the last option on the command line
329 and the command line contained at least two files and a target
330 directory the first file will have logs appended to it. The -M
331 option served little practical purpose in the last decade so its
332 use is expected to be extremely rare.
335 After switching to Clang as the default compiler some users of ZFS
336 on i386 systems started to experience stack overflow kernel panics.
337 Please consider using 'options KSTACK_PAGES=4' in such configurations.
340 GEOM_LABEL now mangles label names read from file system metadata.
341 Mangling affect labels containing spaces, non-printable characters,
342 '%' or '"'. Device names in /etc/fstab and other places may need to
346 By default, only the 10 most recent kernel dumps will be saved. To
347 restore the previous behaviour (no limit on the number of kernel dumps
348 stored in the dump directory) add the following line to /etc/rc.conf:
353 With the addition of auditdistd(8), a new auditdistd user is now
354 required during installworld. "mergemaster -p" can be used to
355 add the user prior to installworld, as documented in the handbook.
358 The sin6_scope_id member variable in struct sockaddr_in6 is now
359 filled by the kernel before passing the structure to the userland via
360 sysctl or routing socket. This means the KAME-specific embedded scope
361 id in sin6_addr.s6_addr[2] is always cleared in userland application.
362 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
363 __FreeBSD_version is bumped to 1000025.
366 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
367 This means that the world and kernel will be compiled with clang
368 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
369 and /usr/bin/cpp. To disable this behavior and revert to building
370 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
371 of current may need to bootstrap WITHOUT_CLANG first if the clang
372 build fails (its compatibility window doesn't extend to the 9 stable
376 The IPFIREWALL_FORWARD kernel option has been removed. Its
377 functionality now turned on by default.
380 The ZERO_COPY_SOCKET kernel option has been removed and
381 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
382 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
383 mechanism which is not safe and may result in kernel crashes.
384 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
385 driver supports disposeable external page sized mbuf storage.
386 Proper replacements for both zero-copy mechanisms are under
387 consideration and will eventually lead to complete removal
388 of the two kernel options.
391 The IPv4 network stack has been converted to network byte
392 order. The following modules need to be recompiled together
393 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
394 pf(4), ipfw(4), ng_ipfw(4), stf(4).
397 Support for non-MPSAFE filesystems was removed from VFS. The
398 VFS_VERSION was bumped, all filesystem modules shall be
402 All the non-MPSAFE filesystems have been disconnected from
403 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
404 portalfs, smbfs, xfs.
407 The interface cloning API and ABI has changed. The following
408 modules need to be recompiled together with kernel:
409 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
410 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
411 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
414 The sdhci driver was split in two parts: sdhci (generic SD Host
415 Controller logic) and sdhci_pci (actual hardware driver).
416 No kernel config modifications are required, but if you
417 load sdhc as a module you must switch to sdhci_pci instead.
420 Import the FUSE kernel and userland support into base system.
423 The GNU sort(1) program has been removed since the BSD-licensed
424 sort(1) has been the default for quite some time and no serious
425 problems have been reported. The corresponding WITH_GNU_SORT
429 The pfil(9) API/ABI for AF_INET family has been changed. Packet
430 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
434 The net80211(4) ABI has been changed to allow for improved driver
435 PS-POLL and power-save support. All wireless drivers need to be
436 recompiled to work with the new kernel.
439 The random(4) support for the VIA hardware random number
440 generator (`PADLOCK') is no longer enabled unconditionally.
441 Add the padlock_rng device in the custom kernel config if
442 needed. The GENERIC kernels on i386 and amd64 do include the
443 device, so the change only affects the custom kernel
447 The pf(4) packet filter ABI has been changed. pfctl(8) and
448 snmp_pf module need to be recompiled to work with new kernel.
451 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
452 to -HEAD. Pools that have empty_bpobj in active state can not be
453 imported read-write with ZFS implementations that do not support
454 this feature. For more information read the zpool-features(5)
458 The sparc64 ZFS loader has been changed to no longer try to auto-
459 detect ZFS providers based on diskN aliases but now requires these
460 to be explicitly listed in the OFW boot-device environment variable.
463 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
464 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
465 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
468 The following sysctls and tunables have been renamed for consistency
469 with other variables:
470 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
471 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
474 The sort utility has been replaced with BSD sort. For now, GNU sort
475 is also available as "gnusort" or the default can be set back to
476 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
477 installed as "bsdsort".
480 A new version of ZFS (pool version 5000) has been merged to -HEAD.
481 Starting with this version the old system of ZFS pool versioning
482 is superseded by "feature flags". This concept enables forward
483 compatibility against certain future changes in functionality of ZFS
484 pools. The first read-only compatible "feature flag" for ZFS pools
485 is named "com.delphix:async_destroy". For more information
486 read the new zpool-features(5) manual page.
487 Please refer to the "ZFS notes" section of this file for information
488 on upgrading boot ZFS pools.
491 The malloc(3) implementation embedded in libc now uses sources imported
492 as contrib/jemalloc. The most disruptive API change is to
493 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
494 delete it prior to installworld, and optionally re-create it using the
495 new format after rebooting. See malloc.conf(5) for details
496 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
500 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
501 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
502 now spelled mips. This is to aid compatibility with third-party
503 software that expects this naming scheme in uname(3). Little-endian
504 settings are unchanged. If you are updating a big-endian mips64 machine
505 from before this change, you may need to set MACHINE_ARCH=mips64 in
506 your environment before the new build system will recognize your machine.
509 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
513 Now unix domain sockets behave "as expected" on nullfs(5). Previously
514 nullfs(5) did not pass through all behaviours to the underlying layer,
515 as a result if we bound to a socket on the lower layer we could connect
516 only to the lower path; if we bound to the upper layer we could connect
517 only to the upper path. The new behavior is one can connect to both the
518 lower and the upper paths regardless what layer path one binds to.
521 The getifaddrs upgrade path broken with 20111215 has been restored.
522 If you have upgraded in between 20111215 and 20120209 you need to
523 recompile libc again with your kernel. You still need to recompile
524 world to be able to configure CARP but this restriction already
528 The set_rcvar() function has been removed from /etc/rc.subr. All
529 base and ports rc.d scripts have been updated, so if you have a
530 port installed with a script in /usr/local/etc/rc.d you can either
531 hand-edit the rcvar= line, or reinstall the port.
533 An easy way to handle the mass-update of /etc/rc.d:
534 rm /etc/rc.d/* && mergemaster -i
537 panic(9) now stops other CPUs in the SMP systems, disables interrupts
538 on the current CPU and prevents other threads from running.
539 This behavior can be reverted using the kern.stop_scheduler_on_panic
541 The new behavior can be incompatible with kern.sync_on_panic.
544 The carp(4) facility has been changed significantly. Configuration
545 of the CARP protocol via ifconfig(8) has changed, as well as format
546 of CARP events submitted to devd(8) has changed. See manual pages
547 for more information. The arpbalance feature of carp(4) is currently
548 not supported anymore.
550 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
551 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
552 need to be recompiled.
555 The acpi_wmi(4) status device /dev/wmistat has been renamed to
559 The option VFS_ALLOW_NONMPSAFE option has been added in order to
560 explicitely support non-MPSAFE filesystems.
561 It is on by default for all supported platform at this present
565 The broken amd(4) driver has been replaced with esp(4) in the amd64,
566 i386 and pc98 GENERIC kernel configuration files.
569 sysinstall has been removed
572 The stable/9 branch created in subversion. This corresponds to the
573 RELENG_9 branch in CVS.
576 This commit modifies vfs_register() so that it uses a hash
577 calculation to set vfc_typenum, which is enabled by default.
578 The first time a system is booted after this change, the
579 vfc_typenum values will change for all file systems. The
580 main effect of this is a change to the NFS server file handles
581 for file systems that use vfc_typenum in their fsid, such as ZFS.
582 It will, however, prevent vfc_typenum from changing when file
583 systems are loaded in a different order for subsequent reboots.
584 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
585 until you are ready to remount all NFS clients after a reboot.
588 Bump the shared library version numbers for libraries that
589 do not use symbol versioning, have changed the ABI compared
590 to stable/8 and which shared library version was not bumped.
591 Done as part of 9.0-RELEASE cycle.
594 During the merge of Capsicum features, the fget(9) KPI was modified.
595 This may require the rebuilding of out-of-tree device drivers --
596 issues have been reported specifically with the nVidia device driver.
597 __FreeBSD_version is bumped to 900041.
599 Also, there is a period between 20110811 and 20110814 where the
600 special devices /dev/{stdin,stdout,stderr} did not work correctly.
601 Building world from a kernel during that window may not work.
604 The packet filter (pf) code has been updated to OpenBSD 4.5.
605 You need to update userland tools to be in sync with kernel.
606 This update breaks backward compatibility with earlier pfsync(4)
607 versions. Care must be taken when updating redundant firewall setups.
610 The following sysctls and tunables are retired on x86 platforms:
612 machdep.hlt_logical_cpus
613 The following sysctl is retired:
614 machdep.hyperthreading_allowed
615 The sysctls were supposed to provide a way to dynamically offline and
616 online selected CPUs on x86 platforms, but the implementation has not
617 been reliable especially with SCHED_ULE scheduler.
618 machdep.hyperthreading_allowed tunable is still available to ignore
619 hyperthreading CPUs at OS level.
620 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
621 where X is an APIC ID of a CPU. Be advised, though, that disabling
622 CPUs in non-uniform fashion will result in non-uniform topology and
623 may lead to sub-optimal system performance with SCHED_ULE, which is
627 cpumask_t type is retired and cpuset_t is used in order to describe
631 Changes to ifconfig(8) for dynamic address family detection mandate
632 that you are running a kernel of 20110525 or later. Make sure to
633 follow the update procedure to boot a new kernel before installing
637 Support for sun4v architecture is officially dropped
640 Several KPI breaking changes have been committed to the mii(4) layer,
641 the PHY drivers and consequently some Ethernet drivers using mii(4).
642 This means that miibus.ko and the modules of the affected Ethernet
643 drivers need to be recompiled.
645 Note to kernel developers: Given that the OUI bit reversion problem
646 was fixed as part of these changes all mii(4) commits related to OUIs,
647 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
648 handling, no longer can be merged verbatim to stable/8 and previous
652 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
653 into their kernel configurations along with 'device pci'.
656 The default NFS client is now the new NFS client, so fstype "newnfs"
657 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
658 Although mounts via fstype "nfs" will usually work without userland
659 changes, it is recommended that the mount(8) and mount_nfs(8)
660 commands be rebuilt from sources and that a link to mount_nfs called
661 mount_oldnfs be created. The new client is compiled into the
662 kernel with "options NFSCL" and this is needed for diskless root
663 file systems. The GENERIC kernel configs have been changed to use
664 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
665 To use the regular/old client, you can "mount -t oldnfs ...". For
666 a diskless root file system, you must also include a line like:
668 vfs.root.mountfrom="oldnfs:"
670 in the boot/loader.conf on the root fs on the NFS server to make
671 a diskless root fs use the old client.
674 The GENERIC kernels for all architectures now default to the new
675 CAM-based ATA stack. It means that all legacy ATA drivers were
676 removed and replaced by respective CAM drivers. If you are using
677 ATA device names in /etc/fstab or other places, make sure to update
678 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
679 where 'Y's are the sequential numbers starting from zero for each type
680 in order of detection, unless configured otherwise with tunables,
681 see cam(4)). There will be symbolic links created in /dev/ to map
682 old adX devices to the respective adaY. They should provide basic
683 compatibility for file systems mounting in most cases, but they do
684 not support old user-level APIs and do not have respective providers
685 in GEOM. Consider using updated management tools with new device names.
687 It is possible to load devices ahci, ata, siis and mvs as modules,
688 but option ATA_CAM should remain in kernel configuration to make ata
689 module work as CAM driver supporting legacy ATA controllers. Device ata
690 still can be used in modular fashion (atacore + ...). Modules atadisk
691 and atapi* are not used and won't affect operation in ATA_CAM mode.
692 Note that to use CAM-based ATA kernel should include CAM devices
693 scbus, pass, da (or explicitly ada), cd and optionally others. All of
694 them are parts of the cam module.
696 ataraid(4) functionality is now supported by the RAID GEOM class.
697 To use it you can load geom_raid kernel module and use graid(8) tool
698 for management. Instead of /dev/arX device names, use /dev/raid/rX.
700 No kernel config options or code have been removed, so if a problem
701 arises, please report it and optionally revert to the old ATA stack.
702 In order to do it you can remove from the kernel config:
707 , and instead add back:
708 device atadisk # ATA disk drives
709 device ataraid # ATA RAID drives
710 device atapicd # ATAPI CDROM drives
711 device atapifd # ATAPI floppy drives
712 device atapist # ATAPI tape drives
715 The default NFS server has been changed to the new server, which
716 was referred to as the experimental server. If you need to switch
717 back to the old NFS server, you must now put the "-o" option on
718 both the mountd and nfsd commands. This can be done using the
719 mountd_flags and nfs_server_flags rc.conf variables until an
720 update to the rc scripts is committed, which is coming soon.
723 The GNU Objective-C runtime library (libobjc), and other Objective-C
724 related components have been removed from the base system. If you
725 require an Objective-C library, please use one of the available ports.
728 ath(4) has been split into bus- and device- modules. if_ath contains
729 the HAL, the TX rate control and the network device code. if_ath_pci
730 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
731 contains the AHB glue. Users need to load both if_ath_pci and if_ath
732 in order to use ath on everything else.
734 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
735 need to load if_ath and if_ath_pci for ath(4) operation.
738 As part of the replacement of sysinstall, the process of building
739 release media has changed significantly. For details, please re-read
740 release(7), which has been updated to reflect the new build process.
743 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
744 is the last available version under GPLv2. It brings a number of new
745 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
746 4.1 and SSE 4.2), better support for powerpc64, a number of new
747 directives, and lots of other small improvements. See the ChangeLog
748 file in contrib/binutils for the full details.
751 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
752 compliant, and will now use half of hash for authentication.
753 This will break interoperability with all stacks (including all
754 actual FreeBSD versions) who implement
755 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
757 The only workaround with such peers is to use another HMAC
758 algorithm for IPsec ("phase 2") authentication.
761 Remove the uio_yield prototype and symbol. This function has
762 been misnamed since it was introduced and should not be
763 globally exposed with this name. The equivalent functionality
764 is now available using kern_yield(curthread->td_user_pri).
765 The function remains undocumented.
768 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
769 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
770 for scalar sysctls is defined but disabled. Code that needs
771 UQUAD to pass the type checking that must compile on older
772 systems where the define is not present can check against
773 __FreeBSD_version >= 900030.
775 The system dialog(1) has been replaced with a new version previously
776 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
777 with the previous version, but the libdialog associated with it has
778 a largely incompatible API. As such, the original version of libdialog
779 will be kept temporarily as libodialog, until its base system consumers
780 are replaced or updated. Bump __FreeBSD_version to 900030.
783 If you are trying to run make universe on a -stable system, and you get
784 the following warning:
785 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
786 unknown. config(8) likely too old."
787 or something similar to it, then you must upgrade your -stable system
788 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
789 stable/8) or build the config from the latest stable/8 branch and
790 install it on your system.
792 Prior to this date, building a current universe on 8-stable system from
793 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
794 error in the first kernel build phase. A new config on those old
795 systems will fix that problem for older versions of -current.
798 The TCP stack has been modified to allow Khelp modules to interact with
799 it via helper hook points and store per-connection data in the TCP
800 control block. Bump __FreeBSD_version to 900029. User space tools that
801 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
805 Generic IEEE 802.3 annex 31B full duplex flow control support has been
806 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
807 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
808 to take advantage of it instead of using custom implementations. This
809 means that these drivers now no longer unconditionally advertise
810 support for flow control but only do so if flow control is a selected
811 media option. This was implemented in the generic support that way in
812 order to allow flow control to be switched on and off via ifconfig(8)
813 with the PHY specific default to typically off in order to protect
814 from unwanted effects. Consequently, if you used flow control with
815 one of the above mentioned drivers you now need to explicitly enable
817 ifconfig bge0 media auto mediaopt flowcontrol
819 Along with the above mentioned changes generic support for setting
820 1000baseT master mode also has been added and brgphy(4), ciphy(4),
821 e1000phy(4) as well as ip1000phy(4) have been converted to take
822 advantage of it. This means that these drivers now no longer take the
823 link0 parameter for selecting master mode but the master media option
824 has to be used instead, for example like in the following:
825 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
827 Selection of master mode now is also available with all other PHY
828 drivers supporting 1000baseT.
831 The TCP stack has received a significant update to add support for
832 modularised congestion control and generally improve the clarity of
833 congestion control decisions. Bump __FreeBSD_version to 900025. User
834 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
835 sockstat) need to be recompiled.
838 The man(1) utility has been replaced by a new version that no longer
839 uses /etc/manpath.config. Please consult man.conf(5) for how to
840 migrate local entries to the new format.
843 The copyright strings printed by login(1) and sshd(8) at the time of a
844 new connection have been removed to follow other operating systems and
848 A workaround for a fixed ld bug has been removed in kernel code,
849 so make sure that your system ld is built from sources after
850 revision 210245 from 2010-07-19 (r211583 if building head kernel
851 on stable/8, r211584 for stable/7; both from 2010-08-21).
852 A symptom of incorrect ld version is different addresses for
853 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
856 The $ipv6_prefer variable in rc.conf(5) has been split into
857 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
859 The $ip6addrctl_policy is a variable to choose a pre-defined
860 address selection policy set by ip6addrctl(8). A value
861 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
864 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
865 flag (see an entry of 20090926) is set on an interface with no
866 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
867 security reason. If you want IPv6 link-local address on all
868 interfaces by default, set this to "YES".
870 The old ipv6_prefer="YES" is equivalent to
871 ipv6_activate_all_interfaces="YES" and
872 ip6addrctl_policy="ipv6_prefer".
875 DTrace has grown support for userland tracing. Due to this, DTrace is
876 now i386 and amd64 only.
877 dtruss(1) is now installed by default on those systems and a new
878 kernel module is needed for userland tracing: fasttrap.
879 No changes to your kernel config file are necessary to enable
880 userland tracing, but you might consider adding 'STRIP=' and
881 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
882 to have informative userland stack traces in DTrace (ustack).
885 The acpi_aiboost(4) driver has been removed in favor of the new
886 aibs(4) driver. You should update your kernel configuration file.
889 BSD grep has been imported to the base system and it is built by
890 default. It is completely BSD licensed, highly GNU-compatible, uses
891 less memory than its GNU counterpart and has a small codebase.
892 However, it is slower than its GNU counterpart, which is mostly
893 noticeable for larger searches, for smaller ones it is measurable
894 but not significant. The reason is complex, the most important factor
895 is that we lack a modern and efficient regex library and GNU
896 overcomes this by optimizing the searches internally. Future work
897 on improving the regex performance is planned, for the meantime,
898 users that need better performance, can build GNU grep instead by
899 setting the WITH_GNU_GREP knob.
902 Due to the import of powerpc64 support, all existing powerpc kernel
903 configuration files must be updated with a machine directive like this:
904 machine powerpc powerpc
906 In addition, an updated config(8) is required to build powerpc kernels
910 A new version of ZFS (version 15) has been merged to -HEAD.
911 This version uses a python library for the following subcommands:
912 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
913 For full functionality of these commands the following port must
914 be installed: sysutils/py-zfs
917 'vm_page's are now hashed by physical address to an array of mutexes.
918 Currently this is only used to serialize access to hold_count. Over
919 time the page queue mutex will be peeled away. This changes the size
920 of pmap on every architecture. And requires all callers of vm_page_hold
921 and vm_page_unhold to be updated.
924 WITH_CTF can now be specified in src.conf (not recommended, there
925 are some problems with static executables), make.conf (would also
926 affect ports which do not use GNU make and do not override the
927 compile targets) or in the kernel config (via "makeoptions
929 When WITH_CTF was specified there before this was silently ignored,
930 so make sure that WITH_CTF is not used in places which could lead
931 to unwanted behavior.
934 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
935 to allow 32-bit compatibility on non-x86 platforms. All kernel
936 configurations on amd64 and ia64 platforms using these options must
937 be modified accordingly.
940 The utmp user accounting database has been replaced with utmpx,
941 the user accounting interface standardized by POSIX.
942 Unfortunately the semantics of utmp and utmpx don't match,
943 making it practically impossible to support both interfaces.
944 The user accounting database is used by tools like finger(1),
945 last(1), talk(1), w(1) and ac(8).
947 All applications in the base system use utmpx. This means only
948 local binaries (e.g. from the ports tree) may still use these
949 utmp database files. These applications must be rebuilt to make
952 After the system has been upgraded, it is safe to remove the old
953 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
954 assuming their contents is of no importance anymore. Old wtmp
955 databases can only be used by last(1) and ac(8) after they have
956 been converted to the new format using wtmpcvt(1).
959 Introduce the kernel thread "deadlock resolver" (which can be enabled
960 via the DEADLKRES option, see NOTES for more details) and the
961 sleepq_type() function for sleepqueues.
964 The rc.firewall and rc.firewall6 were unified, and
965 rc.firewall6 and rc.d/ip6fw were removed.
966 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
967 variables are obsoleted. Instead, the following new rc
968 variables are added to rc.d/ipfw:
970 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
971 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
972 firewall_simple_onet_ipv6, firewall_trusted_ipv6
974 The meanings correspond to the relevant IPv4 variables.
980 The default terminal emulation for syscons(4) has been changed
981 from cons25 to xterm on all platforms except pc98. This means
982 that the /etc/ttys file needs to be updated to ensure correct
983 operation of applications on the console.
985 The terminal emulation style can be toggled per window by using
986 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
987 options can be used to change the compile-time default back to
990 To prevent graphical artifacts, make sure the TERM environment
991 variable is set to match the terminal emulation that is being
992 performed by syscons(4).
995 The layout of the structure ieee80211req_scan_result has changed.
996 Applications that require wireless scan results (e.g. ifconfig(8))
997 from net80211 need to be recompiled.
999 Applications such as wpa_supplicant(8) may require a full world
1000 build without using NO_CLEAN in order to get synchronized with the
1004 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1005 There's one kernel module for each firmware. Adding "device iwnfw"
1006 to the kernel configuration file means including all three firmware
1007 images inside the kernel. If you want to include just the one for
1008 your wireless card, use the devices iwn4965fw, iwn5000fw or
1012 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1013 into rc.d/netif. The changes are the following:
1015 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1016 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1017 Note that both variables need the "inet6" keyword at the head.
1019 Do not set $ipv6_network_interfaces manually if you do not
1020 understand what you are doing. It is not needed in most cases.
1022 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1025 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1026 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1028 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1029 all configured interfaces have "inet6 accept_rtadv" in the
1030 $ifconfig_IF_ipv6. These are for backward compatibility.
1032 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1033 functionality of interfaces with no corresponding
1034 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1035 and the default address selection policy of ip6addrctl(8)
1036 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1037 Note that if you want to configure IPv6 functionality on the
1038 disabled interfaces after boot, first you need to clear the flag by
1039 using ifconfig(8) like:
1041 ifconfig em0 inet6 -ifdisabled
1043 If YES, the default address selection policy is set as
1046 The default value of $ipv6_prefer is NO.
1048 4. If your system need to receive Router Advertisement messages,
1049 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1050 scripts automatically invoke rtsol(8) when the interface becomes
1051 UP. The Router Advertisement messages are used for SLAAC
1052 (State-Less Address AutoConfiguration).
1055 802.11s D3.03 support was committed. This is incompatible with the
1056 previous code, which was based on D3.0.
1059 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1060 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1061 control whether accepting Router Advertisement messages or not.
1062 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1063 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1064 The ifconfig(8) utility now supports these flags.
1067 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1068 mount(8) and -a option for df(1) to see them.
1071 The old tunable hw.bus.devctl_disable has been superseded by
1072 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1073 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1077 Remove the option STOP_NMI. The default action is now to use NMI only
1078 for KDB via the newly introduced function stop_cpus_hard() and
1079 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1082 The stable/8 branch created in subversion. This corresponds to the
1083 RELENG_8 branch in CVS.
1086 Bump the shared library version numbers for all libraries that do not
1087 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1088 __FreeBSD_version to 800105.
1091 Due to changes in the implementation of virtual network stack support,
1092 all network-related kernel modules must be recompiled. As this change
1093 breaks the ABI, bump __FreeBSD_version to 800104.
1096 The TOE interface to the TCP syncache has been modified to remove
1097 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1098 The cxgb driver is the only TOE consumer affected by this change, and
1099 needs to be recompiled along with the kernel. As this change breaks
1100 the ABI, bump __FreeBSD_version to 800103.
1103 Padding has been added to struct tcpcb, sackhint and tcpstat in
1104 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1105 maintaining the ABI. However, this change breaks the ABI, so bump
1106 __FreeBSD_version to 800102. User space tools that rely on the size of
1107 any of these structs (e.g. sockstat) need to be recompiled.
1110 The NFS_LEGACYRPC option has been removed along with the old kernel
1111 RPC implementation that this option selected. Kernel configurations
1112 may need to be adjusted.
1115 The network interface device nodes at /dev/net/<interface> have been
1116 removed. All ioctl operations can be performed the normal way using
1117 routing sockets. The kqueue functionality can generally be replaced
1118 with routing sockets.
1121 The documentation from the FreeBSD Documentation Project (Handbook,
1122 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1123 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1126 The ABI of various structures related to the SYSV IPC API have been
1127 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1128 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1132 Layout of struct vnet has changed as routing related variables were
1133 moved to their own Vimage module. Modules need to be recompiled. Bump
1134 __FreeBSD_version to 800099.
1137 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1138 respectively. As long as no more than 16 groups per process are used,
1139 no changes should be visible. When more than 16 groups are used, old
1140 binaries may fail if they call getgroups() or getgrouplist() with
1141 statically sized storage. Recompiling will work around this, but
1142 applications should be modified to use dynamically allocated storage
1143 for group arrays as POSIX.1-2008 does not cap an implementation's
1144 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1146 NFS and portalfs mounts may also be affected as the list of groups is
1147 truncated to 16. Users of NFS who use more than 16 groups, should
1148 take care that negative group permissions are not used on the exported
1149 file systems as they will not be reliable unless a GSSAPI based
1150 authentication method is used.
1153 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1154 option compiles in the support for adaptive spinning for lockmgrs
1155 which want to enable it. The lockinit() function now accepts the flag
1156 LK_ADAPTIVE in order to make the lock object subject to adaptive
1157 spinning when both held in write and read mode.
1160 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1161 changed. User applications that use this ioctl need to be rebuilt.
1164 The layout of struct thread has changed. Kernel and modules need to
1168 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1169 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1172 window(1) has been removed from the base system. It can now be
1173 installed from ports. The port is called misc/window.
1176 The way we are storing and accessing `routing table' entries has
1177 changed. Programs reading the FIB, like netstat, need to be
1181 A new netisr implementation has been added for FreeBSD 8. Network
1182 file system modules, such as igmp, ipdivert, and others, should be
1184 Bump __FreeBSD_version to 800096.
1187 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1191 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1192 Bump __FreeBSD_version to 800094.
1195 Add mnt_xflag field to 'struct mount'. File system modules need to be
1197 Bump __FreeBSD_version to 800093.
1200 The compiling option ADAPTIVE_SX has been retired while it has been
1201 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1202 The KPI for sx_init_flags() changes as accepting flags:
1203 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1204 been introduced in order to handle the reversed logic.
1205 Bump __FreeBSD_version to 800092.
1208 Add support for hierarchical jails. Remove global securelevel.
1209 Bump __FreeBSD_version to 800091.
1212 The layout of struct vnet_net has changed, therefore modules
1214 Bump __FreeBSD_version to 800090.
1217 The newly imported zic(8) produces a new format in the output. Please
1218 run tzsetup(8) to install the newly created data to /etc/localtime.
1221 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1222 hw.usb.* and is now consistent again with previous releases.
1225 802.11 monitor mode support was revised and driver api's were changed.
1226 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1227 of DLT_IEEE802_11. No user-visible data structures were changed but
1228 applications that use DLT_IEEE802_11 may require changes.
1229 Bump __FreeBSD_version to 800088.
1232 The layout of the following structs has changed: sysctl_oid,
1233 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1234 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1235 panics may be experienced. World rebuild is required for
1236 correctly checking networking state from userland.
1237 Bump __FreeBSD_version to 800085.
1240 MLDv2 and Source-Specific Multicast (SSM) have been merged
1241 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1242 The implementation of SSM within FreeBSD's IPv6 stack closely
1243 follows the IPv4 implementation.
1245 For kernel developers:
1247 * The most important changes are that the ip6_output() and
1248 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1249 and this lock has been downgraded to a non-recursive mutex.
1251 * As with the changes to the IPv4 stack to support SSM, filtering
1252 of inbound multicast traffic must now be performed by transport
1253 protocols within the IPv6 stack. This does not apply to TCP and
1254 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1256 * The KPIs used by IPv6 multicast are similar to those used by
1257 the IPv4 stack, with the following differences:
1258 * im6o_mc_filter() is analogous to imo_multicast_filter().
1259 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1260 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1261 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1262 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1263 for MLDv1 have an additional 'timer' argument which is used to
1264 jitter the initial membership report for the solicited-node
1265 multicast membership on-link.
1266 * This is not strictly needed for MLDv2, which already jitters
1267 its report transmissions. However, the 'timer' argument is
1268 preserved in case MLDv1 is active on the interface.
1270 * The KAME linked-list based IPv6 membership implementation has
1271 been refactored to use a vector similar to that used by the IPv4
1273 Code which maintains a list of its own multicast memberships
1274 internally, e.g. carp, has been updated to reflect the new
1277 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1278 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1279 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1280 implementation constraint which needs to be addressed in HEAD.
1282 For application developers:
1284 * The changes are broadly similar to those made for the IPv4
1287 * The use of IPv4 and IPv6 multicast socket options on the same
1288 socket, using mapped addresses, HAS NOT been tested or supported.
1290 * There are a number of issues with the implementation of various
1291 IPv6 multicast APIs which need to be resolved in the API surface
1292 before the implementation is fully compatible with KAME userland
1293 use, and these are mostly to do with interface index treatment.
1295 * The literature available discusses the use of either the delta / ASM
1296 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1297 using setsourcefilter(3)/getsourcefilter(3). For more information
1298 please refer to RFC 3768, 'Socket Interface Extensions for
1299 Multicast Source Filters'.
1301 * Applications which use the published RFC 3678 APIs should be fine.
1303 For systems administrators:
1305 * The mtest(8) utility has been refactored to support IPv6, in
1306 addition to IPv4. Interface addresses are no longer accepted
1307 as arguments, their names must be used instead. The utility
1308 will map the interface name to its first IPv4 address as
1309 returned by getifaddrs(3).
1311 * The ifmcstat(8) utility has also been updated to print the MLDv2
1312 endpoint state and source filter lists via sysctl(3).
1314 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1315 loopback of IPv6 multicast datagrams by default; it defaults to 1
1316 to preserve the existing behaviour. Disabling multicast loopback is
1317 recommended for optimal system performance.
1319 * The IPv6 MROUTING code has been changed to examine this sysctl
1320 instead of attempting to perform a group lookup before looping
1321 back forwarded datagrams.
1323 Bump __FreeBSD_version to 800084.
1326 Implement low-level Bluetooth HCI API.
1327 Bump __FreeBSD_version to 800083.
1330 The layout of struct malloc_type, used by modules to register new
1331 memory allocation types, has changed. Most modules will need to
1332 be rebuilt or panics may be experienced.
1333 Bump __FreeBSD_version to 800081.
1336 Anticipate overflowing inp_flags - add inp_flags2.
1337 This changes most offsets in inpcb, so checking v4 connection
1338 state will require a world rebuild.
1339 Bump __FreeBSD_version to 800080.
1342 Add an llentry to struct route and struct route_in6. Modules
1343 embedding a struct route will need to be recompiled.
1344 Bump __FreeBSD_version to 800079.
1347 The size of rt_metrics_lite and by extension rtentry has changed.
1348 Networking administration apps will need to be recompiled.
1349 The route command now supports show as an alias for get, weighting
1350 of routes, sticky and nostick flags to alter the behavior of stateful
1352 Bump __FreeBSD_version to 800078.
1355 Do not use Giant for kbdmux(4) locking. This is wrong and
1356 apparently causing more problems than it solves. This will
1357 re-open the issue where interrupt handlers may race with
1358 kbdmux(4) in polling mode. Typical symptoms include (but
1359 not limited to) duplicated and/or missing characters when
1360 low level console functions (such as gets) are used while
1361 interrupts are enabled (for example geli password prompt,
1362 mountroot prompt etc.). Disabling kbdmux(4) may help.
1365 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1366 kernel modules referencing any of the above need to be recompiled.
1367 Bump __FreeBSD_version to 800075.
1370 GEOM_PART has become the default partition slicer for storage devices,
1371 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1372 introduces some changes:
1374 MSDOS/EBR: the devices created from MSDOS extended partition entries
1375 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1376 to devices with offset-based names. fstabs may need to be modified.
1378 BSD: the "geometry does not match label" warning is harmless in most
1379 cases but it points to problems in file system misalignment with
1380 disk geometry. The "c" partition is now implicit, covers the whole
1381 top-level drive and cannot be (mis)used by users.
1383 General: Kernel dumps are now not allowed to be written to devices
1384 whose partition types indicate they are meant to be used for file
1385 systems (or, in case of MSDOS partitions, as something else than
1388 Most of these changes date approximately from 200812.
1391 The uscanner(4) driver has been removed from the kernel. This follows
1392 Linux removing theirs in 2.6 and making libusb the default interface
1393 (supported by sane).
1396 The multicast forwarding code has been cleaned up. netstat(1)
1397 only relies on KVM now for printing bandwidth upcall meters.
1398 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1399 ip6_mroute_mod respectively. The config(5) options for statically
1400 compiling this code remain the same, i.e. 'options MROUTING'.
1403 Support for the IFF_NEEDSGIANT network interface flag has been
1404 removed, which means that non-MPSAFE network device drivers are no
1405 longer supported. In particular, if_ar, if_sr, and network device
1406 drivers from the old (legacy) USB stack can no longer be built or
1410 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1411 a bunch of new language catalog files have also been added.
1412 This means that some common libc messages are now localized and
1413 they depend on the LC_MESSAGES environmental variable.
1416 The k8temp(4) driver has been renamed to amdtemp(4) since
1417 support for Family 10 and Family 11 CPU families was added.
1420 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1421 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1423 For kernel developers, the most important changes are that the
1424 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1425 and this lock has been downgraded to a non-recursive mutex.
1427 Transport protocols (UDP, Raw IP) are now responsible for filtering
1428 inbound multicast traffic according to group membership and source
1429 filters. The imo_multicast_filter() KPI exists for this purpose.
1430 Transports which do not use multicast (SCTP, TCP) already reject
1431 multicast by default. Forwarding and receive performance may improve
1432 as a mutex acquisition is no longer needed in the ip_input()
1433 low-level input path. in_addmulti() and in_delmulti() are shimmed
1434 to new KPIs which exist to support SSM in-kernel.
1436 For application developers, it is recommended that loopback of
1437 multicast datagrams be disabled for best performance, as this
1438 will still cause the lock to be taken for each looped-back
1439 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1440 be tuned to 0 to disable loopback by default; it defaults to 1
1441 to preserve the existing behaviour.
1443 For systems administrators, to obtain best performance with
1444 multicast reception and multiple groups, it is always recommended
1445 that a card with a suitably precise hash filter is used. Hash
1446 collisions will still result in the lock being taken within the
1447 transport protocol input path to check group membership.
1449 If deploying FreeBSD in an environment with IGMP snooping switches,
1450 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1451 enabled; this forces 224.0.0.0/24 group membership to be announced
1454 The size of 'struct igmpstat' has changed; netstat needs to be
1455 recompiled to reflect this.
1456 Bump __FreeBSD_version to 800070.
1459 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1460 updated to use it. This requires a buildworld/installworld in order to
1461 update the library and dependencies (usbconfig, etc). Its advisable to
1462 rebuild all ports which uses libusb. More specific directions are given
1463 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1464 libusb are no longer required and can be removed.
1467 A workaround is committed to allow the creation of System V shared
1468 memory segment of size > 2 GB on the 64-bit architectures.
1469 Due to a limitation of the existing ABI, the shm_segsz member
1470 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1471 wrong for large segments. Note that limits must be explicitly
1472 raised to allow such segments to be created.
1475 The layout of struct ifnet has changed, requiring a rebuild of all
1476 network device driver modules.
1479 The /dev handling for the new USB stack has changed, a
1480 buildworld/installworld is required for libusb20.
1483 The new USB2 stack has now been permanently moved in and all kernel and
1484 module names reverted to their previous values (eg, usb, ehci, ohci,
1485 ums, ...). The old usb stack can be compiled in by prefixing the name
1486 with the letter 'o', the old usb modules have been removed.
1487 Updating entry 20090216 for xorg and 20090215 for libmap may still
1491 The rc.conf(5) option if_up_delay has been renamed to
1492 defaultroute_delay to better reflect its purpose. If you have
1493 customized this setting in /etc/rc.conf you need to update it to
1497 xorg 7.4 wants to configure its input devices via hald which does not
1498 yet work with USB2. If the keyboard/mouse does not work in xorg then
1500 Option "AllowEmptyInput" "off"
1501 to your ServerLayout section. This will cause X to use the configured
1502 kbd and mouse sections from your xorg.conf.
1505 The GENERIC kernels for all architectures now default to the new USB2
1506 stack. No kernel config options or code have been removed so if a
1507 problem arises please report it and optionally revert to the old USB
1508 stack. If you are loading USB kernel modules or have a custom kernel
1509 that includes GENERIC then ensure that usb names are also changed over,
1510 eg uftdi -> usb2_serial_ftdi.
1512 Older programs linked against the ports libusb 0.1 need to be
1513 redirected to the new stack's libusb20. /etc/libmap.conf can
1515 # Map old usb library to new one for usb2 stack
1516 libusb-0.1.so.8 libusb20.so.1
1519 All USB ethernet devices now attach as interfaces under the name ueN
1520 (eg. ue0). This is to provide a predictable name as vendors often
1521 change usb chipsets in a product without notice.
1524 The ichsmb(4) driver has been changed to require SMBus slave
1525 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1526 All of the other SMBus controller drivers require left-justified
1527 slave addresses, so this change makes all the drivers provide the
1531 INET6 statistics (struct ip6stat) was updated.
1532 netstat(1) needs to be recompiled.
1535 NTFS has been removed from GENERIC kernel on amd64 to match
1536 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1537 will load ntfs.ko module automatically when NTFS support is
1538 actually needed, unless ntfs.ko is not installed or security
1539 level prohibits loading kernel modules. If either is the case,
1540 "options NTFS" has to be added into kernel config.
1543 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1544 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1545 800061. User space tools that rely on the size of struct tcpcb in
1546 tcp_var.h (e.g. sockstat) need to be recompiled.
1549 ng_tty(4) module updated to match the new TTY subsystem.
1550 Due to API change, user-level applications must be updated.
1551 New API support added to mpd5 CVS and expected to be present
1552 in next mpd5.3 release.
1555 With __FreeBSD_version 800060 the makefs tool is part of
1556 the base system (it was a port).
1559 The afdata and ifnet locks have been changed from mutexes to
1560 rwlocks, network modules will need to be re-compiled.
1563 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1564 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1565 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1566 architecture and 40 bytes on 64-bit architecture. The userland
1567 applications "arp" and "ndp" have been updated accordingly.
1568 The output from "netstat -r" shows only routing entries and
1569 none of the L2 information.
1572 __FreeBSD_version 800057 marks the switchover from the
1573 binary ath hal to source code. Users must add the line:
1575 options AH_SUPPORT_AR5416
1577 to their kernel config files when specifying:
1581 The ath_hal module no longer exists; the code is now compiled
1582 together with the driver in the ath module. It is now
1583 possible to tailor chip support (i.e. reduce the set of chips
1584 and thereby the code size); consult ath_hal(4) for details.
1587 __FreeBSD_version 800054 adds memory barriers to
1588 <machine/atomic.h>, new interfaces to ifnet to facilitate
1589 multiple hardware transmit queues for cards that support
1590 them, and a lock-less ring-buffer implementation to
1591 enable drivers to more efficiently manage queueing of
1595 A new version of ZFS (version 13) has been merged to -HEAD.
1596 This version has zpool attribute "listsnapshots" off by
1597 default, which means "zfs list" does not show snapshots,
1598 and is the same as Solaris behavior.
1601 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1604 The uhci, ohci, ehci and slhci USB Host controller drivers have
1605 been put into separate modules. If you load the usb module
1606 separately through loader.conf you will need to load the
1607 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1608 controller add the following to loader.conf:
1614 The ABI used by the PMC toolset has changed. Please keep
1615 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1619 atapci kernel module now includes only generic PCI ATA
1620 driver. AHCI driver moved to ataahci kernel module.
1621 All vendor-specific code moved into separate kernel modules:
1622 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1623 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1624 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1625 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1628 The TTY subsystem of the kernel has been replaced by a new
1629 implementation, which provides better scalability and an
1630 improved driver model. Most common drivers have been migrated to
1631 the new TTY subsystem, while others have not. The following
1632 drivers have not yet been ported to the new TTY layer:
1635 cy, digi, rc, rp, sio
1641 ng_h4, ng_tty, ppp, sl, snp
1643 Adding these drivers to your kernel configuration file shall
1644 cause compilation to fail.
1647 ntpd has been upgraded to 4.2.4p5.
1650 OpenSSH has been upgraded to 5.1p1.
1652 For many years, FreeBSD's version of OpenSSH preferred DSA
1653 over RSA for host and user authentication keys. With this
1654 upgrade, we've switched to the vendor's default of RSA over
1655 DSA. This may cause upgraded clients to warn about unknown
1656 host keys even for previously known hosts. Users should
1657 follow the usual procedure for verifying host keys before
1658 accepting the RSA key.
1660 This can be circumvented by setting the "HostKeyAlgorithms"
1661 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1664 Please note that the sequence of keys offered for
1665 authentication has been changed as well. You may want to
1666 specify IdentityFile in a different order to revert this
1670 The sio(4) driver has been removed from the i386 and amd64
1671 kernel configuration files. This means uart(4) is now the
1672 default serial port driver on those platforms as well.
1674 To prevent collisions with the sio(4) driver, the uart(4) driver
1675 uses different names for its device nodes. This means the
1676 onboard serial port will now most likely be called "ttyu0"
1677 instead of "ttyd0". You may need to reconfigure applications to
1678 use the new device names.
1680 When using the serial port as a boot console, be sure to update
1681 /boot/device.hints and /etc/ttys before booting the new kernel.
1682 If you forget to do so, you can still manually specify the hints
1683 at the loader prompt:
1685 set hint.uart.0.at="isa"
1686 set hint.uart.0.port="0x3F8"
1687 set hint.uart.0.flags="0x10"
1688 set hint.uart.0.irq="4"
1692 The gpt(8) utility has been removed. Use gpart(8) to partition
1696 The version that Linuxulator emulates was changed from 2.4.2
1697 to 2.6.16. If you experience any problems with Linux binaries
1698 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1699 if it fixes the problem contact emulation mailing list.
1702 ISDN4BSD (I4B) was removed from the src tree. You may need to
1703 update a your kernel configuration and remove relevant entries.
1706 I have checked in code to support multiple routing tables.
1707 See the man pages setfib(1) and setfib(2).
1708 This is a hopefully backwards compatible version,
1709 but to make use of it you need to compile your kernel
1710 with options ROUTETABLES=2 (or more up to 16).
1713 The 802.11 wireless support was redone to enable multi-bss
1714 operation on devices that are capable. The underlying device
1715 is no longer used directly but instead wlanX devices are
1716 cloned with ifconfig. This requires changes to rc.conf files.
1717 For example, change:
1718 ifconfig_ath0="WPA DHCP"
1721 ifconfig_wlan0="WPA DHCP"
1722 see rc.conf(5) for more details. In addition, mergemaster of
1723 /etc/rc.d is highly recommended. Simultaneous update of userland
1724 and kernel wouldn't hurt either.
1726 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1727 modules were merged into the base wlan module. All references
1728 to these modules (e.g. in kernel config files) must be removed.
1731 psm(4) has gained write(2) support in native operation level.
1732 Arbitrary commands can be written to /dev/psm%d and status can
1733 be read back from it. Therefore, an application is responsible
1734 for status validation and error recovery. It is a no-op in
1735 other operation levels.
1738 Support for KSE threading has been removed from the kernel. To
1739 run legacy applications linked against KSE libmap.conf may
1740 be used. The following libmap.conf may be used to ensure
1741 compatibility with any prior release:
1743 libpthread.so.1 libthr.so.1
1744 libpthread.so.2 libthr.so.2
1745 libkse.so.3 libthr.so.3
1748 The layout of struct vmspace has changed. This affects libkvm
1749 and any executables that link against libkvm and use the
1750 kvm_getprocs() function. In particular, but not exclusively,
1751 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1752 The effects are minimal, but it's advisable to upgrade world
1756 The latest em driver no longer has support in it for the
1757 82575 adapter, this is now moved to the igb driver. The
1758 split was done to make new features that are incompatible
1759 with older hardware easier to do.
1762 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1763 likewise the kernel option is now GEOM_LINUX_LVM.
1766 The default NFS mount mode has changed from UDP to TCP for
1767 increased reliability. If you rely on (insecurely) NFS
1768 mounting across a firewall you may need to update your
1772 Belatedly note the addition of m_collapse for compacting
1776 The fts(3) structures have been changed to use adequate
1777 integer types for their members and so to be able to cope
1778 with huge file trees. The old fts(3) ABI is preserved
1779 through symbol versioning in libc, so third-party binaries
1780 using fts(3) should still work, although they will not take
1781 advantage of the extended types. At the same time, some
1782 third-party software might fail to build after this change
1783 due to unportable assumptions made in its source code about
1784 fts(3) structure members. Such software should be fixed
1785 by its vendor or, in the worst case, in the ports tree.
1786 FreeBSD_version 800015 marks this change for the unlikely
1787 case that a portable fix is impossible.
1790 To upgrade to -current after this date, you must be running
1791 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1792 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1795 The ADAPTIVE_GIANT kernel option has been retired because its
1796 functionality is the default now.
1799 The AT keyboard emulation of sunkbd(4) has been turned on
1800 by default. In order to make the special symbols of the Sun
1801 keyboards driven by sunkbd(4) work under X these now have
1802 to be configured the same way as Sun USB keyboards driven
1803 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1805 Option "XkbLayout" "us"
1806 Option "XkbRules" "xorg"
1807 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1810 It has been decided that it is desirable to provide ABI
1811 backwards compatibility to the FreeBSD 4/5/6 versions of the
1812 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1813 broken with the introduction of PCI domain support (see the
1814 20070930 entry). Unfortunately, this required the ABI of
1815 PCIOCGETCONF to be broken again in order to be able to
1816 provide backwards compatibility to the old version of that
1817 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1818 again. As for prominent ports this affects neither pciutils
1819 nor xorg-server this time, the hal port needs to be rebuilt
1823 The misnamed kthread_create() and friends have been renamed
1824 to kproc_create() etc. Many of the callers already
1825 used kproc_start()..
1826 I will return kthread_create() and friends in a while
1827 with implementations that actually create threads, not procs.
1828 Renaming corresponds with version 800002.
1837 Avoid using make -j when upgrading. While generally safe, there are
1838 sometimes problems using -j to upgrade. If your upgrade fails with
1839 -j, please try again without -j. From time to time in the past there
1840 have been problems using -j with buildworld and/or installworld. This
1841 is especially true when upgrading between "distant" versions (eg one
1842 that cross a major release boundary or several minor releases, or when
1843 several months have passed on the -current branch).
1845 Sometimes, obscure build problems are the result of environment
1846 poisoning. This can happen because the make utility reads its
1847 environment when searching for values for global variables. To run
1848 your build attempts in an "environmental clean room", prefix all make
1849 commands with 'env -i '. See the env(1) manual page for more details.
1851 When upgrading from one major version to another it is generally best
1852 to upgrade to the latest code in the currently installed branch first,
1853 then do an upgrade to the new branch. This is the best-tested upgrade
1854 path, and has the highest probability of being successful. Please try
1855 this approach before reporting problems with a major version upgrade.
1857 When upgrading a live system, having a root shell around before
1858 installing anything can help undo problems. Not having a root shell
1859 around can lead to problems if pam has changed too much from your
1860 starting point to allow continued authentication after the upgrade.
1864 When upgrading the boot ZFS pool to a new version, always follow
1867 1.) recompile and reinstall the ZFS boot loader and boot block
1868 (this is part of "make buildworld" and "make installworld")
1870 2.) update the ZFS boot block on your boot drive
1872 The following example updates the ZFS boot block on the first
1873 partition (freebsd-boot) of a GPT partitioned drive ad0:
1874 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1876 Non-boot pools do not need these updates.
1880 If you are updating from a prior version of FreeBSD (even one just
1881 a few days old), you should follow this procedure. It is the most
1882 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1884 make kernel-toolchain
1885 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1886 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1888 To test a kernel once
1889 ---------------------
1890 If you just want to boot a kernel once (because you are not sure
1891 if it works, or if you want to boot a known bad kernel to provide
1892 debugging information) run
1893 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1894 nextboot -k testkernel
1896 To just build a kernel when you know that it won't mess you up
1897 --------------------------------------------------------------
1898 This assumes you are already running a CURRENT system. Replace
1899 ${arch} with the architecture of your machine (e.g. "i386",
1900 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1902 cd src/sys/${arch}/conf
1903 config KERNEL_NAME_HERE
1904 cd ../compile/KERNEL_NAME_HERE
1909 If this fails, go to the "To build a kernel" section.
1911 To rebuild everything and install it on the current system.
1912 -----------------------------------------------------------
1913 # Note: sometimes if you are running current you gotta do more than
1914 # is listed here if you are upgrading from a really old current.
1916 <make sure you have good level 0 dumps>
1918 make kernel KERNCONF=YOUR_KERNEL_HERE
1920 <reboot in single user> [3]
1927 To cross-install current onto a separate partition
1928 --------------------------------------------------
1929 # In this approach we use a separate partition to hold
1930 # current's root, 'usr', and 'var' directories. A partition
1931 # holding "/", "/usr" and "/var" should be about 2GB in
1934 <make sure you have good level 0 dumps>
1937 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1938 <maybe newfs current's root partition>
1939 <mount current's root partition on directory ${CURRENT_ROOT}>
1940 make installworld DESTDIR=${CURRENT_ROOT}
1941 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1942 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1943 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1944 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1945 <reboot into current>
1946 <do a "native" rebuild/install as described in the previous section>
1947 <maybe install compatibility libraries from ports/misc/compat*>
1951 To upgrade in-place from stable to current
1952 ----------------------------------------------
1953 <make sure you have good level 0 dumps>
1955 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1957 <reboot in single user> [3]
1964 Make sure that you've read the UPDATING file to understand the
1965 tweaks to various things you need. At this point in the life
1966 cycle of current, things change often and you are on your own
1967 to cope. The defaults can also change, so please read ALL of
1968 the UPDATING entries.
1970 Also, if you are tracking -current, you must be subscribed to
1971 freebsd-current@freebsd.org. Make sure that before you update
1972 your sources that you have read and understood all the recent
1973 messages there. If in doubt, please track -stable which has
1974 much fewer pitfalls.
1976 [1] If you have third party modules, such as vmware, you
1977 should disable them at this point so they don't crash your
1980 [3] From the bootblocks, boot -s, and then do
1985 adjkerntz -i # if CMOS is wall time
1986 Also, when doing a major release upgrade, it is required that
1987 you boot into single user mode to do the installworld.
1989 [4] Note: This step is non-optional. Failure to do this step
1990 can result in a significant reduction in the functionality of the
1991 system. Attempting to do it by hand is not recommended and those
1992 that pursue this avenue should read this file carefully, as well
1993 as the archives of freebsd-current and freebsd-hackers mailing lists
1994 for potential gotchas. The -U option is also useful to consider.
1995 See mergemaster(8) for more information.
1997 [5] Usually this step is a noop. However, from time to time
1998 you may need to do this if you get unknown user in the following
1999 step. It never hurts to do it all the time. You may need to
2000 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2001 install) after the buildworld before this step if you last updated
2002 from current before 20130425 or from -stable before 20130430.
2004 [6] This only deletes old files and directories. Old libraries
2005 can be deleted by "make delete-old-libs", but you have to make
2006 sure that no program is using those libraries anymore.
2008 [8] In order to have a kernel that can run the 4.x binaries needed to
2009 do an installworld, you must include the COMPAT_FREEBSD4 option in
2010 your kernel. Failure to do so may leave you with a system that is
2011 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2012 required to run the 5.x binaries on more recent kernels. And so on
2013 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2015 Make sure that you merge any new devices from GENERIC since the
2016 last time you updated your kernel config file.
2018 [9] When checking out sources, you must include the -P flag to have
2019 cvs prune empty directories.
2021 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2022 "?=" instead of the "=" assignment operator, so that buildworld can
2023 override the CPUTYPE if it needs to.
2025 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2026 not on the command line, or in /etc/make.conf. buildworld will
2027 warn if it is improperly defined.
2030 This file contains a list, in reverse chronological order, of major
2031 breakages in tracking -current. It is not guaranteed to be a complete
2032 list of such breakages, and only contains entries since October 10, 2007.
2033 If you need to see UPDATING entries from before that date, you will need
2034 to fetch an UPDATING file from an older FreeBSD release.
2036 Copyright information:
2038 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2040 Redistribution, publication, translation and use, with or without
2041 modification, in full or in part, in any form or format of this
2042 document are permitted without further permission from the author.
2044 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2045 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2046 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2047 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2048 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2049 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2050 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2051 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2052 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2053 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2054 POSSIBILITY OF SUCH DAMAGE.
2056 Contact Warner Losh if you have any questions about your use of