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