xref: /freebsd/UPDATING (revision 456b5dd815b2a25e7b20ce087a62a59c3e7d06cd)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3456b5dd8SWarner LoshThis file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4456b5dd8SWarner LoshSee end of file for further details.  For commonly done items, please see the
5456b5dd8SWarner LoshCOMMON ITEMS: section later in the file.  These instructions assume that you
6456b5dd8SWarner Loshbasically know what you are doing.  If not, then please consult the FreeBSD
7456b5dd8SWarner Loshhandbook.
8e72fd46aSWarner Losh
92c724730SWarner LoshItems affecting the ports and packages system can be found in
10456b5dd8SWarner Losh/usr/ports/UPDATING.  Please read that file before running portupgrade.
112c724730SWarner Losh
12cf48cc9fSKen SmithNOTE TO PEOPLE WHO THINK THAT FreeBSD 9.x IS SLOW:
13456b5dd8SWarner Losh	FreeBSD 9.x has many debugging features turned on, in both the kernel
14456b5dd8SWarner Losh	and userland.  These features attempt to detect incorrect use of
15456b5dd8SWarner Losh	system primitives, and encourage loud failure through extra sanity
16456b5dd8SWarner Losh	checking and fail stop semantics.  They also substantially impact
17456b5dd8SWarner Losh	system performance.  If you want to do performance measurement,
18456b5dd8SWarner Losh	benchmarking, and optimization, you'll want to turn them off.  This
19456b5dd8SWarner Losh	includes various WITNESS- related kernel options, INVARIANTS, malloc
20456b5dd8SWarner Losh	debugging flags in userland, and various verbose features in the
21456b5dd8SWarner Losh	kernel.  Many developers choose to disable these features on build
22456b5dd8SWarner Losh	machines to maximize performance.  (To disable malloc debugging, run
236bea5c3cSTom Rhodes	ln -s aj /etc/malloc.conf.)
24efc06131SSam Leffler
25dc6fbf65SAttilio Rao20090813:
26456b5dd8SWarner Losh	Remove the option STOP_NMI.  The default action is now to use NMI only
27456b5dd8SWarner Losh	for KDB via the newly introduced function stop_cpus_hard() and
28456b5dd8SWarner Losh	maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
29456b5dd8SWarner Losh
30456b5dd8SWarner Losh20090803:
31456b5dd8SWarner Losh	RELENG_8 branched.
32dc6fbf65SAttilio Rao
333ca3047aSKen Smith20090719:
34456b5dd8SWarner Losh	Bump the shared library version numbers for all libraries that do not
35456b5dd8SWarner Losh	use symbol versioning as part of the 8.0-RELEASE cycle.  Bump
36456b5dd8SWarner Losh	__FreeBSD_version to 800105.
373ca3047aSKen Smith
38eddfbb76SRobert Watson20090714:
39456b5dd8SWarner Losh	Due to changes in the implementation of virtual network stack support,
40456b5dd8SWarner Losh	all network-related kernel modules must be recompiled.  As this change
41456b5dd8SWarner Losh	breaks the ABI, bump __FreeBSD_version to 800104.
42eddfbb76SRobert Watson
43237fbe0aSLawrence Stewart20090713:
44456b5dd8SWarner Losh	The TOE interface to the TCP syncache has been modified to remove
45456b5dd8SWarner Losh	struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
46456b5dd8SWarner Losh	The cxgb driver is the only TOE consumer affected by this change, and
47456b5dd8SWarner Losh	needs to be recompiled along with the kernel. As this change breaks
48456b5dd8SWarner Losh	the ABI, bump __FreeBSD_version to 800103.
49237fbe0aSLawrence Stewart
50962ebef8SLawrence Stewart20090712:
51962ebef8SLawrence Stewart	Padding has been added to struct tcpcb, sackhint and tcpstat in
52962ebef8SLawrence Stewart	<netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
53962ebef8SLawrence Stewart	maintainig the ABI. However, this change breaks the ABI, so bump
54962ebef8SLawrence Stewart	__FreeBSD_version to 800102. User space tools that rely on the size of
55962ebef8SLawrence Stewart	any of these structs (e.g. sockstat) need to be recompiled.
56962ebef8SLawrence Stewart
57bab42aadSDoug Rabson20090630:
58456b5dd8SWarner Losh	The NFS_LEGACYRPC option has been removed along with the old kernel
59456b5dd8SWarner Losh	RPC implementation that this option selected. Kernel configurations
60456b5dd8SWarner Losh	may need to be adjusted.
61bab42aadSDoug Rabson
626cb7f168SBrooks Davis20090629:
63456b5dd8SWarner Losh	The network interface device nodes at /dev/net/<interface> have been
64456b5dd8SWarner Losh	removed.  All ioctl operations can be performed the normal way using
65456b5dd8SWarner Losh	routing sockets.  The kqueue functionality can generally be replaced
66456b5dd8SWarner Losh	with routing sockets.
676cb7f168SBrooks Davis
68944bc81dSMarc Fonvieille20090628:
69456b5dd8SWarner Losh	The documentation from the FreeBSD Documentation Project (Handbook,
70456b5dd8SWarner Losh	FAQ, etc.) is now installed via packages by sysinstall(8) and under
71456b5dd8SWarner Losh	the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
72944bc81dSMarc Fonvieille
73f5e4c105SJohn Baldwin20090624:
74456b5dd8SWarner Losh	The ABI of various structures related to the SYSV IPC API have been
75456b5dd8SWarner Losh	changed.  As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
76456b5dd8SWarner Losh	options now all require COMPAT_FREEBSD7.  Bump __FreeBSD_version to
77456b5dd8SWarner Losh	800100.
78f5e4c105SJohn Baldwin
79b58ea5f3SBjoern A. Zeeb20090622:
80456b5dd8SWarner Losh	Layout of struct vnet has changed as routing related variables were
81456b5dd8SWarner Losh	moved to their own Vimage module. Modules need to be recompiled.  Bump
82456b5dd8SWarner Losh	__FreeBSD_version to 800099.
83b58ea5f3SBjoern A. Zeeb
84838d9858SBrooks Davis20090619:
85456b5dd8SWarner Losh	NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
86456b5dd8SWarner Losh	respectively.  As long as no more than 16 groups per process are used,
87456b5dd8SWarner Losh	no changes should be visible.  When more than 16 groups are used, old
88456b5dd8SWarner Losh	binaries may fail if they call getgroups() or getgrouplist() with
89456b5dd8SWarner Losh	statically sized storage.  Recompiling will work around this, but
90456b5dd8SWarner Losh	applications should be modified to use dynamically allocated storage
91456b5dd8SWarner Losh	for group arrays as POSIX.1-2008 does not cap an implementation's
92456b5dd8SWarner Losh	number of supported groups at NGROUPS_MAX+1 as previous versions did.
93838d9858SBrooks Davis
94456b5dd8SWarner Losh	NFS and portalfs mounts may also be affected as the list of groups is
95456b5dd8SWarner Losh	truncated to 16.  Users of NFS who use more than 16 groups, should
96456b5dd8SWarner Losh	take care that negative group permissions are not used on the exported
97456b5dd8SWarner Losh	file systems as they will not be reliable unless a GSSAPI based
98456b5dd8SWarner Losh	authentication method is used.
99838d9858SBrooks Davis
100651175c9SAttilio Rao20090616:
101456b5dd8SWarner Losh	The compiling option ADAPTIVE_LOCKMGRS has been introduced.  This
102456b5dd8SWarner Losh	option compiles in the support for adaptive spinning for lockmgrs
103456b5dd8SWarner Losh	which want to enable it.  The lockinit() function now accepts the flag
104456b5dd8SWarner Losh	LK_ADAPTIVE in order to make the lock object subject to adaptive
105456b5dd8SWarner Losh	spinning when both held in write and read mode.
106651175c9SAttilio Rao
1072c727cb9SSam Leffler20090613:
108456b5dd8SWarner Losh	The layout of the structure returned by IEEE80211_IOC_STA_INFO has
109456b5dd8SWarner Losh	changed.  User applications that use this ioctl need to be rebuilt.
1102c727cb9SSam Leffler
111f089869fSMarko Zec20090611:
112456b5dd8SWarner Losh	The layout of struct thread has changed.  Kernel and modules need to
113456b5dd8SWarner Losh	be rebuilt.
114f089869fSMarko Zec
115bc29160dSMarko Zec20090608:
116456b5dd8SWarner Losh	The layout of structs ifnet, domain, protosw and vnet_net has changed.
117456b5dd8SWarner Losh	Kernel modules need to be rebuilt.  Bump __FreeBSD_version to 800097.
118bc29160dSMarko Zec
11989f98d57SEd Schouten20090602:
12089f98d57SEd Schouten	window(1) has been removed from the base system. It can now be
12189f98d57SEd Schouten	installed from ports. The port is called misc/window.
12289f98d57SEd Schouten
123c2c2a7c1SBjoern A. Zeeb20090601:
124456b5dd8SWarner Losh	The way we are storing and accessing `routing table' entries has
125456b5dd8SWarner Losh	changed. Programs reading the FIB, like netstat, need to be
126456b5dd8SWarner Losh	re-compiled.
127c2c2a7c1SBjoern A. Zeeb
128529cb8e3SRobert Watson20090601:
129529cb8e3SRobert Watson	A new netisr implementation has been added for FreeBSD 8.  Network
130529cb8e3SRobert Watson	file system modules, such as igmp, ipdivert, and others, should be
131529cb8e3SRobert Watson	rebuilt.
132529cb8e3SRobert Watson	Bump __FreeBSD_version to 800096.
133529cb8e3SRobert Watson
1342a61ba47SEdward Tomasz Napierala20090530:
135456b5dd8SWarner Losh	Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
136456b5dd8SWarner Losh	more valid.
137faef64ccSAttilio Rao
138faef64ccSAttilio Rao20090530:
1392a61ba47SEdward Tomasz Napierala	Add VOP_ACCESSX(9).  File system modules need to be rebuilt.
1402a61ba47SEdward Tomasz Napierala	Bump __FreeBSD_version to 800094.
1412a61ba47SEdward Tomasz Napierala
142b89fed67SEdward Tomasz Napierala20090529:
143456b5dd8SWarner Losh	Add mnt_xflag field to 'struct mount'.  File system modules need to be
144456b5dd8SWarner Losh	rebuilt.
145b89fed67SEdward Tomasz Napierala	Bump __FreeBSD_version to 800093.
146b89fed67SEdward Tomasz Napierala
1471ae1c2a3SAttilio Rao20090528:
1481ae1c2a3SAttilio Rao	The compiling option ADAPTIVE_SX has been retired while it has been
1491ae1c2a3SAttilio Rao	introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1501ae1c2a3SAttilio Rao	The KPI for sx_init_flags() changes as accepting flags:
151456b5dd8SWarner Losh	SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
152456b5dd8SWarner Losh	been introduced in order to handle the reversed logic.
1531ae1c2a3SAttilio Rao	Bump __FreeBSD_version to 800092.
1541ae1c2a3SAttilio Rao
1550304c731SJamie Gritton20090527:
1560304c731SJamie Gritton	Add support for hierarchical jails.  Remove global securelevel.
1570304c731SJamie Gritton	Bump __FreeBSD_version to 800091.
1580304c731SJamie Gritton
159dfc79e89SEdwin Groothuis20090523:
16037f17770SMarko Zec	The layout of struct vnet_net has changed, therefore modules
16137f17770SMarko Zec	need to be rebuilt.
16237f17770SMarko Zec	Bump __FreeBSD_version to 800090.
16337f17770SMarko Zec
16437f17770SMarko Zec20090523:
165456b5dd8SWarner Losh	The newly imported zic(8) produces a new format in the output. Please
166456b5dd8SWarner Losh	run tzsetup(8) to install the newly created data to /etc/localtime.
167dfc79e89SEdwin Groothuis
16823790ac0SSam Leffler20090520:
1699360ae40SAndrew Thompson	The sysctl tree for the usb stack has renamed from hw.usb2.* to
1709360ae40SAndrew Thompson	hw.usb.* and is now consistent again with previous releases.
1719360ae40SAndrew Thompson
1729360ae40SAndrew Thompson20090520:
173456b5dd8SWarner Losh	802.11 monitor mode support was revised and driver api's were changed.
174456b5dd8SWarner Losh	Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
175456b5dd8SWarner Losh	of DLT_IEEE802_11.  No user-visible data structures were changed but
176456b5dd8SWarner Losh	applications that use DLT_IEEE802_11 may require changes.
17723790ac0SSam Leffler	Bump __FreeBSD_version to 800088.
17823790ac0SSam Leffler
179f6dfe47aSMarko Zec20090430:
180f6dfe47aSMarko Zec	The layout of the following structs has changed: sysctl_oid,
181f6dfe47aSMarko Zec	socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
182f6dfe47aSMarko Zec	vnet_inet6 and vnet_ipfw.  Most modules need to be rebuild or
183f6dfe47aSMarko Zec	panics may be experienced.  World rebuild is required for
184f6dfe47aSMarko Zec	correctly checking networking state from userland.
185f6dfe47aSMarko Zec	Bump __FreeBSD_version to 800085.
186f6dfe47aSMarko Zec
18733cde130SBruce M Simpson20090429:
18833cde130SBruce M Simpson	MLDv2 and Source-Specific Multicast (SSM) have been merged
18933cde130SBruce M Simpson	to the IPv6 stack. VIMAGE hooks are in but not yet used.
19033cde130SBruce M Simpson	The implementation of SSM within FreeBSD's IPv6 stack closely
19133cde130SBruce M Simpson	follows the IPv4 implementation.
19233cde130SBruce M Simpson
19333cde130SBruce M Simpson	For kernel developers:
19433cde130SBruce M Simpson
19533cde130SBruce M Simpson	* The most important changes are that the ip6_output() and
19633cde130SBruce M Simpson	  ip6_input() paths no longer take the IN6_MULTI_LOCK,
19733cde130SBruce M Simpson	  and this lock has been downgraded to a non-recursive mutex.
19833cde130SBruce M Simpson
19933cde130SBruce M Simpson	* As with the changes to the IPv4 stack to support SSM, filtering
20033cde130SBruce M Simpson	  of inbound multicast traffic must now be performed by transport
20133cde130SBruce M Simpson	  protocols within the IPv6 stack. This does not apply to TCP and
20233cde130SBruce M Simpson	  SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
20333cde130SBruce M Simpson
20433cde130SBruce M Simpson	* The KPIs used by IPv6 multicast are similar to those used by
20533cde130SBruce M Simpson	  the IPv4 stack, with the following differences:
20633cde130SBruce M Simpson	   * im6o_mc_filter() is analogous to imo_multicast_filter().
20733cde130SBruce M Simpson	   * The legacy KAME entry points in6_joingroup and in6_leavegroup()
20833cde130SBruce M Simpson	     are shimmed to in6_mc_join() and in6_mc_leave() respectively.
20933cde130SBruce M Simpson	   * IN6_LOOKUP_MULTI() has been deprecated and removed.
21033cde130SBruce M Simpson	   * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
21133cde130SBruce M Simpson	     for MLDv1 have an additional 'timer' argument which is used to
21233cde130SBruce M Simpson	     jitter the initial membership report for the solicited-node
21333cde130SBruce M Simpson	     multicast membership on-link.
21433cde130SBruce M Simpson	   * This is not strictly needed for MLDv2, which already jitters
21533cde130SBruce M Simpson	     its report transmissions.  However, the 'timer' argument is
21633cde130SBruce M Simpson	     preserved in case MLDv1 is active on the interface.
21733cde130SBruce M Simpson
21833cde130SBruce M Simpson	* The KAME linked-list based IPv6 membership implementation has
21933cde130SBruce M Simpson	  been refactored to use a vector similar to that used by the IPv4
22033cde130SBruce M Simpson	  stack.
22133cde130SBruce M Simpson	  Code which maintains a list of its own multicast memberships
22233cde130SBruce M Simpson	  internally, e.g. carp, has been updated to reflect the new
22333cde130SBruce M Simpson	  semantics.
22433cde130SBruce M Simpson
22533cde130SBruce M Simpson	* There is a known Lock Order Reversal (LOR) due to in6_setscope()
22633cde130SBruce M Simpson	  acquiring the IF_AFDATA_LOCK and being called within ip6_output().
22733cde130SBruce M Simpson	  Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
22833cde130SBruce M Simpson	  implementation constraint which needs to be addressed in HEAD.
22933cde130SBruce M Simpson
23033cde130SBruce M Simpson	For application developers:
23133cde130SBruce M Simpson
23233cde130SBruce M Simpson	* The changes are broadly similar to those made for the IPv4
23333cde130SBruce M Simpson	  stack.
23433cde130SBruce M Simpson
23533cde130SBruce M Simpson	* The use of IPv4 and IPv6 multicast socket options on the same
23633cde130SBruce M Simpson	  socket, using mapped addresses, HAS NOT been tested or supported.
23733cde130SBruce M Simpson
23833cde130SBruce M Simpson	* There are a number of issues with the implementation of various
23933cde130SBruce M Simpson	  IPv6 multicast APIs which need to be resolved in the API surface
24033cde130SBruce M Simpson	  before the implementation is fully compatible with KAME userland
24133cde130SBruce M Simpson	  use, and these are mostly to do with interface index treatment.
24233cde130SBruce M Simpson
24333cde130SBruce M Simpson	* The literature available discusses the use of either the delta / ASM
24433cde130SBruce M Simpson	  API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
24533cde130SBruce M Simpson	  using setsourcefilter(3)/getsourcefilter(3). For more information
24633cde130SBruce M Simpson	  please refer to RFC 3768, 'Socket Interface Extensions for
24733cde130SBruce M Simpson	  Multicast Source Filters'.
24833cde130SBruce M Simpson
24933cde130SBruce M Simpson	* Applications which use the published RFC 3678 APIs should be fine.
25033cde130SBruce M Simpson
25133cde130SBruce M Simpson	For systems administrators:
25233cde130SBruce M Simpson
25333cde130SBruce M Simpson	* The mtest(8) utility has been refactored to support IPv6, in
25433cde130SBruce M Simpson	  addition to IPv4. Interface addresses are no longer accepted
25533cde130SBruce M Simpson	  as arguments, their names must be used instead. The utility
25633cde130SBruce M Simpson	  will map the interface name to its first IPv4 address as
25733cde130SBruce M Simpson	  returned by getifaddrs(3).
25833cde130SBruce M Simpson
25933cde130SBruce M Simpson	* The ifmcstat(8) utility has also been updated to print the MLDv2
26033cde130SBruce M Simpson	  endpoint state and source filter lists via sysctl(3).
26133cde130SBruce M Simpson
26233cde130SBruce M Simpson	* The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
26333cde130SBruce M Simpson	  loopback of IPv6 multicast datagrams by default; it defaults to 1
26433cde130SBruce M Simpson	  to preserve the existing behaviour. Disabling multicast loopback is
26533cde130SBruce M Simpson	  recommended for optimal system performance.
26633cde130SBruce M Simpson
26733cde130SBruce M Simpson	* The IPv6 MROUTING code has been changed to examine this sysctl
26833cde130SBruce M Simpson	  instead of attempting to perform a group lookup before looping
26933cde130SBruce M Simpson	  back forwarded datagrams.
27033cde130SBruce M Simpson
27133cde130SBruce M Simpson	Bump __FreeBSD_version to 800084.
27233cde130SBruce M Simpson
2738b8bf775SRobert Watson20090422:
274131cdffbSMaksim Yevmenkin	Implement low-level Bluetooth HCI API.
275131cdffbSMaksim Yevmenkin	Bump __FreeBSD_version to 800083.
276131cdffbSMaksim Yevmenkin
2778b8bf775SRobert Watson20090419:
2788b8bf775SRobert Watson	The layout of struct malloc_type, used by modules to register new
2798b8bf775SRobert Watson	memory allocation types, has changed.  Most modules will need to
2808b8bf775SRobert Watson	be rebuilt or panics may be experienced.
2818b8bf775SRobert Watson	Bump __FreeBSD_version to 800081.
2828b8bf775SRobert Watson
283de4ab55eSKip Macy20090415:
284773b573aSKip Macy	Anticipate overflowing inp_flags - add inp_flags2.
285773b573aSKip Macy	This changes most offsets in inpcb, so checking v4 connection
286773b573aSKip Macy	state will require a world rebuild.
287773b573aSKip Macy	Bump __FreeBSD_version to 800080.
288f146c211SXin LI
289773b573aSKip Macy20090415:
290de4ab55eSKip Macy	Add an llentry to struct route and struct route_in6. Modules
291de4ab55eSKip Macy	embedding a struct route will need to be recompiled.
292de4ab55eSKip Macy	Bump __FreeBSD_version to 800079.
293de4ab55eSKip Macy
294427ac07fSKip Macy20090414:
295427ac07fSKip Macy	The size of rt_metrics_lite and by extension rtentry has changed.
296427ac07fSKip Macy	Networking administration apps will need to be recompiled.
297427ac07fSKip Macy	The route command now supports show as an alias for get, weighting
298427ac07fSKip Macy	of routes, sticky and nostick flags to alter the behavior of stateful
299427ac07fSKip Macy	load balancing.
300427ac07fSKip Macy	Bump __FreeBSD_version to 800078.
3018713ec3dSRenato Botelho
30287437955SMaksim Yevmenkin20090408:
30387437955SMaksim Yevmenkin	Do not use Giant for kbdmux(4) locking. This is wrong and
30487437955SMaksim Yevmenkin	apparently causing more problems than it solves. This will
30587437955SMaksim Yevmenkin	re-open the issue where interrupt handlers may race with
30687437955SMaksim Yevmenkin	kbdmux(4) in polling mode. Typical symptoms include (but
30787437955SMaksim Yevmenkin	not limited to) duplicated and/or missing characters when
30887437955SMaksim Yevmenkin	low level console functions (such as gets) are used while
30987437955SMaksim Yevmenkin	interrupts are enabled (for example geli password prompt,
31087437955SMaksim Yevmenkin	mountroot prompt etc.). Disabling kbdmux(4) may help.
31187437955SMaksim Yevmenkin
3122f6a1858SMarko Zec20090407:
3132f6a1858SMarko Zec	The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
3142f6a1858SMarko Zec	kernel modules referencing any of the above need to be recompiled.
3152f6a1858SMarko Zec	Bump __FreeBSD_version to 800075.
3162f6a1858SMarko Zec
317781d043cSIvan Voras20090320:
318781d043cSIvan Voras	GEOM_PART has become the default partition slicer for storage devices,
319781d043cSIvan Voras	replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
3209a07b548SIvan Voras	introduces some changes:
3219a07b548SIvan Voras
3229a07b548SIvan Voras	MSDOS/EBR: the devices created from MSDOS extended partition entries
3239a07b548SIvan Voras	(EBR) can be named differently than with GEOM_MBR and are now symlinks
3249a07b548SIvan Voras	to devices with offset-based names. fstabs may need to be modified.
3259a07b548SIvan Voras
3269a07b548SIvan Voras	BSD: the "geometry does not match label" warning is harmless in most
3279a07b548SIvan Voras	cases but it points to problems in file system misalignment with
3289a07b548SIvan Voras	disk geometry. The "c" partition is now implicit, covers the whole
3299a07b548SIvan Voras	top-level drive and cannot be (mis)used by users.
3309a07b548SIvan Voras
3319a07b548SIvan Voras	General: Kernel dumps are now not allowed to be written to devices
3329a07b548SIvan Voras	whose partition types indicate they are meant to be used for file
3339a07b548SIvan Voras	systems (or, in case of MSDOS partitions, as something else than
3349a07b548SIvan Voras	the "386BSD" type).
3359a07b548SIvan Voras
3369a07b548SIvan Voras	Most of these changes date approximately from 200812.
337781d043cSIvan Voras
338443fc317SBruce M Simpson20090319:
3392b78d306SAndrew Thompson	The uscanner(4) driver has been removed from the kernel. This follows
3402b78d306SAndrew Thompson	Linux removing theirs in 2.6 and making libusb the default interface
3412b78d306SAndrew Thompson	(supported by sane).
3422b78d306SAndrew Thompson
3432b78d306SAndrew Thompson20090319:
344443fc317SBruce M Simpson	The multicast forwarding code has been cleaned up. netstat(1)
345443fc317SBruce M Simpson	only relies on KVM now for printing bandwidth upcall meters.
346443fc317SBruce M Simpson	The IPv4 and IPv6 modules are split into ip_mroute_mod and
347443fc317SBruce M Simpson	ip6_mroute_mod respectively. The config(5) options for statically
348443fc317SBruce M Simpson	compiling this code remain the same, i.e. 'options MROUTING'.
349443fc317SBruce M Simpson
3501df14375SRobert Watson20090315:
3511df14375SRobert Watson	Support for the IFF_NEEDSGIANT network interface flag has been
3521df14375SRobert Watson	removed, which means that non-MPSAFE network device drivers are no
3531df14375SRobert Watson	longer supported.  In particular, if_ar, if_sr, and network device
3541df14375SRobert Watson	drivers from the old (legacy) USB stack can no longer be built or
3551df14375SRobert Watson	used.
3561df14375SRobert Watson
357e667034dSRui Paulo20090313:
3587e06afcaSGabor Kovesdan	POSIX.1 Native Language Support (NLS) has been enabled in libc and
3597e06afcaSGabor Kovesdan	a bunch of new language catalog files have also been added.
3607e06afcaSGabor Kovesdan	This means that some common libc messages are now localized and
3617e06afcaSGabor Kovesdan	they depend on the LC_MESSAGES environmental variable.
3627e06afcaSGabor Kovesdan
3637e06afcaSGabor Kovesdan20090313:
364e667034dSRui Paulo	The k8temp(4) driver has been renamed to amdtemp(4) since
365e667034dSRui Paulo	support for K10 and K11 CPU families was added.
366e667034dSRui Paulo
367a091d2a5SAndrew Thompson20090309:
368d10910e6SBruce M Simpson	IGMPv3 and Source-Specific Multicast (SSM) have been merged
369d10910e6SBruce M Simpson	to the IPv4 stack. VIMAGE hooks are in but not yet used.
370d10910e6SBruce M Simpson
371d10910e6SBruce M Simpson	For kernel developers, the most important changes are that the
372d10910e6SBruce M Simpson	ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
373d10910e6SBruce M Simpson	and this lock has been downgraded to a non-recursive mutex.
374d10910e6SBruce M Simpson
375d10910e6SBruce M Simpson	Transport protocols (UDP, Raw IP) are now responsible for filtering
376d10910e6SBruce M Simpson	inbound multicast traffic according to group membership and source
377d10910e6SBruce M Simpson	filters. The imo_multicast_filter() KPI exists for this purpose.
378d10910e6SBruce M Simpson	Transports which do not use multicast (SCTP, TCP) already reject
379d10910e6SBruce M Simpson	multicast by default. Forwarding and receive performance may improve
380d10910e6SBruce M Simpson	as a mutex acquisition is no longer needed in the ip_input()
381d10910e6SBruce M Simpson	low-level input path.  in_addmulti() and in_delmulti() are shimmed
382d10910e6SBruce M Simpson	to new KPIs which exist to support SSM in-kernel.
383d10910e6SBruce M Simpson
384d10910e6SBruce M Simpson	For application developers, it is recommended that loopback of
385d10910e6SBruce M Simpson	multicast datagrams be disabled for best performance, as this
386d10910e6SBruce M Simpson	will still cause the lock to be taken for each looped-back
387d10910e6SBruce M Simpson	datagram transmission. The net.inet.ip.mcast.loop sysctl may
388d10910e6SBruce M Simpson	be tuned to 0 to disable loopback by default; it defaults to 1
389d10910e6SBruce M Simpson	to preserve the existing behaviour.
390d10910e6SBruce M Simpson
391d10910e6SBruce M Simpson	For systems administrators, to obtain best performance with
392d10910e6SBruce M Simpson	multicast reception and multiple groups, it is always recommended
393d10910e6SBruce M Simpson	that a card with a suitably precise hash filter is used. Hash
394d10910e6SBruce M Simpson	collisions will still result in the lock being taken within the
395d10910e6SBruce M Simpson	transport protocol input path to check group membership.
396d10910e6SBruce M Simpson
397d10910e6SBruce M Simpson	If deploying FreeBSD in an environment with IGMP snooping switches,
398d10910e6SBruce M Simpson	it is recommended that the net.inet.igmp.sendlocal sysctl remain
399d10910e6SBruce M Simpson	enabled; this forces 224.0.0.0/24 group membership to be announced
400d10910e6SBruce M Simpson	via IGMP.
401d10910e6SBruce M Simpson
402d10910e6SBruce M Simpson	The size of 'struct igmpstat' has changed; netstat needs to be
403d10910e6SBruce M Simpson	recompiled to reflect this.
404d10910e6SBruce M Simpson	Bump __FreeBSD_version to 800070.
405d10910e6SBruce M Simpson
406d10910e6SBruce M Simpson20090309:
407a091d2a5SAndrew Thompson	libusb20.so.1 is now installed as libusb.so.1 and the ports system
408a091d2a5SAndrew Thompson	updated to use it. This requires a buildworld/installworld in order to
409a091d2a5SAndrew Thompson	update the library and dependencies (usbconfig, etc). Its advisable to
410cb2fe9b1SStanislav Sedov	rebuild all ports which uses libusb. More specific directions are given
4110ee5826eSAndrew Thompson	in the ports collection UPDATING file. Any /etc/libmap.conf entries for
4123296f80dSAndrew Thompson	libusb are no longer required and can be removed.
413a091d2a5SAndrew Thompson
41465067cc8SKonstantin Belousov20090302:
4159f960e98SKonstantin Belousov	A workaround is committed to allow the creation of System V shared
4169f960e98SKonstantin Belousov	memory segment of size > 2 GB on the 64-bit architectures.
4179f960e98SKonstantin Belousov	Due to a limitation of the existing ABI, the shm_segsz member
41865067cc8SKonstantin Belousov	of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
419813bb2c9SJoel Dahl	wrong for large segments. Note that limits must be explicitly
42065067cc8SKonstantin Belousov	raised to allow such segments to be created.
42165067cc8SKonstantin Belousov
422176273eaSRobert Watson20090301:
423176273eaSRobert Watson	The layout of struct ifnet has changed, requiring a rebuild of all
424176273eaSRobert Watson	network device driver modules.
425176273eaSRobert Watson
426a13a5664SAndrew Thompson20090227:
427a13a5664SAndrew Thompson	The /dev handling for the new USB stack has changed, a
428a13a5664SAndrew Thompson	buildworld/installworld is required for libusb20.
429a13a5664SAndrew Thompson
43071e9286cSAndrew Thompson20090223:
43171e9286cSAndrew Thompson	The new USB2 stack has now been permanently moved in and all kernel and
432200dcf9aSAndrew Thompson	module names reverted to their previous values (eg, usb, ehci, ohci,
4339c1e15b5SAndrew Thompson	ums, ...).  The old usb stack can be compiled in by prefixing the name
43471e9286cSAndrew Thompson	with the letter 'o', the old usb modules have been removed.
435a709c9a6SWarner Losh	Updating entry 20090216 for xorg and 20090215 for libmap may still
436a709c9a6SWarner Losh	apply.
43771e9286cSAndrew Thompson
438553bf6a4SMike Makonnen20090217:
439553bf6a4SMike Makonnen	The rc.conf(5) option if_up_delay has been renamed to
440553bf6a4SMike Makonnen	defaultroute_delay to better reflect its purpose. If you have
441553bf6a4SMike Makonnen	customized this setting in /etc/rc.conf you need to update it to
442553bf6a4SMike Makonnen	use the new name.
443553bf6a4SMike Makonnen
444bb71e4b6SAndrew Thompson20090216:
445bb71e4b6SAndrew Thompson	xorg 7.4 wants to configure its input devices via hald which does not
446bb71e4b6SAndrew Thompson	yet work with USB2. If the keyboard/mouse does not work in xorg then
447bb71e4b6SAndrew Thompson	add
448bb71e4b6SAndrew Thompson		Option "AllowEmptyInput" "off"
449bb71e4b6SAndrew Thompson	to your ServerLayout section.  This will cause X to use the configured
450cbb9c89eSMaxim Konovalov	kbd and mouse sections from your xorg.conf.
451bb71e4b6SAndrew Thompson
452e4edc14eSAndrew Thompson20090215:
453e4edc14eSAndrew Thompson	The GENERIC kernels for all architectures now default to the new USB2
454e4edc14eSAndrew Thompson	stack. No kernel config options or code have been removed so if a
455e4edc14eSAndrew Thompson	problem arises please report it and optionally revert to the old USB
456e4edc14eSAndrew Thompson	stack. If you are loading USB kernel modules or have a custom kernel
457e4edc14eSAndrew Thompson	that includes GENERIC then ensure that usb names are also changed over,
458cbb9c89eSMaxim Konovalov	eg uftdi -> usb2_serial_ftdi.
459e4edc14eSAndrew Thompson
460a709c9a6SWarner Losh	Older programs linked against the ports libusb 0.1 need to be
461a709c9a6SWarner Losh	redirected to the new stack's libusb20.  /etc/libmap.conf can
462a709c9a6SWarner Losh	be used for this:
463a709c9a6SWarner Losh		# Map old usb library to new one for usb2 stack
464a709c9a6SWarner Losh		libusb-0.1.so.8	libusb20.so.1
465a709c9a6SWarner Losh
46614943437SJohn Baldwin20090203:
46714943437SJohn Baldwin	The ichsmb(4) driver has been changed to require SMBus slave
46814943437SJohn Baldwin	addresses be left-justified (xxxxxxx0b) rather than right-justified.
46914943437SJohn Baldwin	All of the other SMBus controller drivers require left-justified
47014943437SJohn Baldwin	slave addresses, so this change makes all the drivers provide the
47114943437SJohn Baldwin	same interface.
47214943437SJohn Baldwin
47309f8c3ffSBjoern A. Zeeb20090201:
47409f8c3ffSBjoern A. Zeeb	INET6 statistics (struct ip6stat) was updated.
47509f8c3ffSBjoern A. Zeeb	netstat(1) needs to be recompiled.
47609f8c3ffSBjoern A. Zeeb
47774f91fb9SMaxim Sobolev20090119:
47874f91fb9SMaxim Sobolev	NTFS has been removed from GENERIC kernel on amd64 to match
47974f91fb9SMaxim Sobolev	GENERIC on i386. Should not cause any issues since mount_ntfs(8)
48074f91fb9SMaxim Sobolev	will load ntfs.ko module automatically when NTFS support is
48174f91fb9SMaxim Sobolev	actually needed, unless ntfs.ko is not installed or security
48274f91fb9SMaxim Sobolev	level prohibits loading kernel modules. If either is the case,
48374f91fb9SMaxim Sobolev	"options NTFS" has to be added into kernel config.
48474f91fb9SMaxim Sobolev
48524cb0f22SLawrence Stewart20090115:
48624cb0f22SLawrence Stewart	TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
48724cb0f22SLawrence Stewart	New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
48824cb0f22SLawrence Stewart	800061. User space tools that rely on the size of struct tcpcb in
48924cb0f22SLawrence Stewart	tcp_var.h (e.g. sockstat) need to be recompiled.
49024cb0f22SLawrence Stewart
4915d55747eSAlexander Motin20081225:
4925d55747eSAlexander Motin	ng_tty(4) module updated to match the new TTY subsystem.
4935d55747eSAlexander Motin	Due to API change, user-level applications must be updated.
4945d55747eSAlexander Motin	New API support added to mpd5 CVS and expected to be present
4955d55747eSAlexander Motin	in next mpd5.3 release.
4965d55747eSAlexander Motin
497efc06131SSam Leffler20081219:
498a1c64cafSSam Leffler	With __FreeBSD_version 800060 the makefs tool is part of
499a1c64cafSSam Leffler	the base system (it was a port).
500efc06131SSam Leffler
501991f8615SKip Macy20081216:
502991f8615SKip Macy	The afdata and ifnet locks have been changed from mutexes to
503991f8615SKip Macy	rwlocks, network modules will need to be re-compiled.
5041d7e99caSJohn Baldwin
5056e6b3f7cSQing Li20081214:
5066e6b3f7cSQing Li	__FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
5076e6b3f7cSQing Li	RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
5086e6b3f7cSQing Li	The new code reduced struct rtentry{} by 16 bytes on 32-bit
5096e6b3f7cSQing Li	architecture and 40 bytes on 64-bit architecture. The userland
5106e6b3f7cSQing Li	applications "arp" and "ndp" have been updated accordingly.
5116e6b3f7cSQing Li	The output from "netstat -r" shows only routing entries and
5126e6b3f7cSQing Li	none of the L2 information.
5136e6b3f7cSQing Li
51433644623SSam Leffler20081130:
51533644623SSam Leffler	__FreeBSD_version 800057 marks the switchover from the
51633644623SSam Leffler	binary ath hal to source code. Users must add the line:
51733644623SSam Leffler
518c60b227cSSam Leffler	options	AH_SUPPORT_AR5416
51933644623SSam Leffler
52033644623SSam Leffler	to their kernel config files when specifying:
52133644623SSam Leffler
52233644623SSam Leffler	device	ath_hal
52333644623SSam Leffler
52433644623SSam Leffler	The ath_hal module no longer exists; the code is now compiled
52533644623SSam Leffler	together with the driver in the ath module.  It is now
52633644623SSam Leffler	possible to tailor chip support (i.e. reduce the set of chips
52733644623SSam Leffler	and thereby the code size); consult ath_hal(4) for details.
52833644623SSam Leffler
529db7f0b97SKip Macy20081121:
530db7f0b97SKip Macy	__FreeBSD_version 800054 adds memory barriers to
531db7f0b97SKip Macy	<machine/atomic.h>, new interfaces to ifnet to facilitate
532db7f0b97SKip Macy	multiple hardware transmit queues for cards that support
533db7f0b97SKip Macy	them, and a lock-less ring-buffer implementation to
534db7f0b97SKip Macy	enable drivers to more efficiently manage queueing of
535db7f0b97SKip Macy	packets.
536db7f0b97SKip Macy
537de2e1b35SXin LI20081117:
538de2e1b35SXin LI	A new version of ZFS (version 13) has been merged to -HEAD.
539de3a91a0SXin LI	This version has zpool attribute "listsnapshots" off by
540de3a91a0SXin LI	default, which means "zfs list" does not show snapshots,
541de2e1b35SXin LI	and is the same as Solaris behavior.
542de2e1b35SXin LI
54302d09f79SOleg Bulyzhin20081028:
54402d09f79SOleg Bulyzhin	dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
54502d09f79SOleg Bulyzhin
546e91c7c81SJoseph Koshy20081009:
547d8135f4aSNick Hibma	The uhci, ohci, ehci and slhci USB Host controller drivers have
548d8135f4aSNick Hibma	been put into separate modules. If you load the usb module
549d8135f4aSNick Hibma	separately through loader.conf you will need to load the
550d8135f4aSNick Hibma	appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
551d8135f4aSNick Hibma	controller add the following to loader.conf:
552d8135f4aSNick Hibma
553d8135f4aSNick Hibma		uhci_load="YES"
554d8135f4aSNick Hibma		ehci_load="YES"
555d8135f4aSNick Hibma
556d8135f4aSNick Hibma20081009:
557e91c7c81SJoseph Koshy	The ABI used by the PMC toolset has changed.  Please keep
558e91c7c81SJoseph Koshy	userland (libpmc(3)) and the kernel module (hwpmc(4)) in
559e91c7c81SJoseph Koshy	sync.
560e91c7c81SJoseph Koshy
561bc093719SEd Schouten20080820:
562bc093719SEd Schouten	The TTY subsystem of the kernel has been replaced by a new
563bc093719SEd Schouten	implementation, which provides better scalability and an
564bc093719SEd Schouten	improved driver model. Most common drivers have been migrated to
565bc093719SEd Schouten	the new TTY subsystem, while others have not. The following
566bc093719SEd Schouten	drivers have not yet been ported to the new TTY layer:
567bc093719SEd Schouten
568bc093719SEd Schouten	PCI/ISA:
56966e7dc38SEd Schouten		cy, digi, rc, rp, sio
570bc093719SEd Schouten
571bc093719SEd Schouten	USB:
57266e7dc38SEd Schouten		ubser, ucycom
573bc093719SEd Schouten
574bc093719SEd Schouten	Line disciplines:
575bc093719SEd Schouten		ng_h4, ng_tty, ppp, sl, snp
576bc093719SEd Schouten
577bc093719SEd Schouten	Adding these drivers to your kernel configuration file shall
578bc093719SEd Schouten	cause compilation to fail.
579bc093719SEd Schouten
5809d965219SOllivier Robert20080818:
5819d965219SOllivier Robert	ntpd has been upgraded to 4.2.4p5.
5829d965219SOllivier Robert
583eaeb50d4SDag-Erling Smørgrav20080801:
584eaeb50d4SDag-Erling Smørgrav	OpenSSH has been upgraded to 5.1p1.
585eaeb50d4SDag-Erling Smørgrav
586eaeb50d4SDag-Erling Smørgrav	For many years, FreeBSD's version of OpenSSH preferred DSA
587eaeb50d4SDag-Erling Smørgrav	over RSA for host and user authentication keys.  With this
588eaeb50d4SDag-Erling Smørgrav	upgrade, we've switched to the vendor's default of RSA over
589eaeb50d4SDag-Erling Smørgrav	DSA.  This may cause upgraded clients to warn about unknown
590eaeb50d4SDag-Erling Smørgrav	host keys even for previously known hosts.  Users should
591eaeb50d4SDag-Erling Smørgrav	follow the usual procedure for verifying host keys before
592eaeb50d4SDag-Erling Smørgrav	accepting the RSA key.
593eaeb50d4SDag-Erling Smørgrav
594eaeb50d4SDag-Erling Smørgrav	This can be circumvented by setting the "HostKeyAlgorithms"
595eaeb50d4SDag-Erling Smørgrav	option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
596eaeb50d4SDag-Erling Smørgrav	command line.
597eaeb50d4SDag-Erling Smørgrav
598737d990aSXin LI	Please note that the sequence of keys offered for
599737d990aSXin LI	authentication has been changed as well.  You may want to
600737d990aSXin LI	specify IdentityFile in a different order to revert this
601737d990aSXin LI	behavior.
602737d990aSXin LI
603f4d811f0SEd Schouten20080713:
604f4d811f0SEd Schouten	The sio(4) driver has been removed from the i386 and amd64
605f4d811f0SEd Schouten	kernel configuration files. This means uart(4) is now the
606f4d811f0SEd Schouten	default serial port driver on those platforms as well.
607f4d811f0SEd Schouten
608f4d811f0SEd Schouten	To prevent collisions with the sio(4) driver, the uart(4) driver
609f4d811f0SEd Schouten	uses different names for its device nodes. This means the
610f4d811f0SEd Schouten	onboard serial port will now most likely be called "ttyu0"
611f4d811f0SEd Schouten	instead of "ttyd0". You may need to reconfigure applications to
612f4d811f0SEd Schouten	use the new device names.
613f4d811f0SEd Schouten
614db96ec0bSEd Schouten	When using the serial port as a boot console, be sure to update
615db96ec0bSEd Schouten	/boot/device.hints and /etc/ttys before booting the new kernel.
616db96ec0bSEd Schouten	If you forget to do so, you can still manually specify the hints
617db96ec0bSEd Schouten	at the loader prompt:
618db96ec0bSEd Schouten
619db96ec0bSEd Schouten		set hint.uart.0.at="isa"
620db96ec0bSEd Schouten		set hint.uart.0.port="0x3F8"
621db96ec0bSEd Schouten		set hint.uart.0.flags="0x10"
622db96ec0bSEd Schouten		set hint.uart.0.irq="4"
623db96ec0bSEd Schouten		boot -s
624db96ec0bSEd Schouten
625bdc03b37SMarcel Moolenaar20080609:
626bdc03b37SMarcel Moolenaar	The gpt(8) utility has been removed. Use gpart(8) to partition
627bdc03b37SMarcel Moolenaar	disks instead.
628bdc03b37SMarcel Moolenaar
62927f7c387SRoman Divacky20080603:
630a47444d5SRoman Divacky	The version that Linuxulator emulates was changed from 2.4.2
631a47444d5SRoman Divacky	to 2.6.16. If you experience any problems with Linux binaries
632a47444d5SRoman Divacky	please try to set sysctl compat.linux.osrelease to 2.4.2 and
633a47444d5SRoman Divacky	if it fixes the problem contact emulation mailing list.
634a47444d5SRoman Divacky
6352e598474SBjoern A. Zeeb20080525:
6362e598474SBjoern A. Zeeb	ISDN4BSD (I4B) was removed from the src tree. You may need to
6372e598474SBjoern A. Zeeb	update a your kernel configuration and remove relevant entries.
6382e598474SBjoern A. Zeeb
6394dcedde3SJulian Elischer20080509:
6404dcedde3SJulian Elischer	I have checked in code to support multiple routing tables.
641032e0bf8SMaxim Konovalov	See the man pages setfib(1) and setfib(2).
6424dcedde3SJulian Elischer	This is a hopefully backwards compatible version,
6434dcedde3SJulian Elischer	but to make use of it you need to compile your kernel
6444dcedde3SJulian Elischer	with options ROUTETABLES=2 (or more up to 16).
6454dcedde3SJulian Elischer
646de570baaSSam Leffler20080420:
647de570baaSSam Leffler	The 802.11 wireless support was redone to enable multi-bss
648de570baaSSam Leffler	operation on devices that are capable.  The underlying device
649de570baaSSam Leffler	is no longer used directly but instead wlanX devices are
650de570baaSSam Leffler	cloned with ifconfig.  This requires changes to rc.conf files.
6515318f840SWarner Losh	For example, change:
6525318f840SWarner Losh		ifconfig_ath0="WPA DHCP"
6535318f840SWarner Losh	to
6545318f840SWarner Losh		wlans_ath0=wlan0
6555318f840SWarner Losh		ifconfig_wlan0="WPA DHCP"
6560f95e625SWarner Losh	see rc.conf(5) for more details.  In addition, mergemaster of
6570f95e625SWarner Losh	/etc/rc.d is highly recommended.  Simultaneous update of userland
6580f95e625SWarner Losh	and kernel wouldn't hurt either.
659de570baaSSam Leffler
660de570baaSSam Leffler	As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
661de570baaSSam Leffler	modules were merged into the base wlan module.  All references
662de570baaSSam Leffler	to these modules (e.g. in kernel config files) must be removed.
663de570baaSSam Leffler
664ff0af72cSJung-uk Kim20080408:
665ff0af72cSJung-uk Kim	psm(4) has gained write(2) support in native operation level.
666ff0af72cSJung-uk Kim	Arbitrary commands can be written to /dev/psm%d and status can
667ff0af72cSJung-uk Kim	be read back from it.  Therefore, an application is responsible
668ff0af72cSJung-uk Kim	for status validation and error recovery.  It is a no-op in
669ff0af72cSJung-uk Kim	other operation levels.
670ff0af72cSJung-uk Kim
671e4c67b94SJeff Roberson20080312:
672e4c67b94SJeff Roberson	Support for KSE threading has been removed from the kernel.  To
673e4c67b94SJeff Roberson	run legacy applications linked against KSE libmap.conf may
674e4c67b94SJeff Roberson	be used.  The following libmap.conf may be used to ensure
675e4c67b94SJeff Roberson	compatibility with any prior release:
676e4c67b94SJeff Roberson
677e4c67b94SJeff Roberson	libpthread.so.1 libthr.so.1
678e4c67b94SJeff Roberson	libpthread.so.2 libthr.so.2
679e4c67b94SJeff Roberson	libkse.so.3 libthr.so.3
680e4c67b94SJeff Roberson
6818775db6fSMarcel Moolenaar20080301:
6828775db6fSMarcel Moolenaar	The layout of struct vmspace has changed. This affects libkvm
6838775db6fSMarcel Moolenaar	and any executables that link against libkvm and use the
6848775db6fSMarcel Moolenaar	kvm_getprocs() function. In particular, but not exclusively,
6858775db6fSMarcel Moolenaar	it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
6868775db6fSMarcel Moolenaar	The effects are minimal, but it's advisable to upgrade world
6878775db6fSMarcel Moolenaar	nonetheless.
6888775db6fSMarcel Moolenaar
689df09ebc0SJack F Vogel20080229:
690df09ebc0SJack F Vogel	The latest em driver no longer has support in it for the
691df09ebc0SJack F Vogel	82575 adapter, this is now moved to the igb driver. The
692df09ebc0SJack F Vogel	split was done to make new features that are incompatible
693df09ebc0SJack F Vogel	with older hardware easier to do.
694df09ebc0SJack F Vogel
6951669d8afSAndrew Thompson20080220:
6961669d8afSAndrew Thompson	The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
6971669d8afSAndrew Thompson	likewise the kernel option is now GEOM_LINUX_LVM.
6981669d8afSAndrew Thompson
6992427fa19SKris Kennaway20080211:
7002427fa19SKris Kennaway	The default NFS mount mode has changed from UDP to TCP for
7012427fa19SKris Kennaway	increased reliability.  If you rely on (insecurely) NFS
7022427fa19SKris Kennaway	mounting across a firewall you may need to update your
7032427fa19SKris Kennaway	firewall rules.
7042427fa19SKris Kennaway
7055e9f6b73SSam Leffler20080208:
7065e9f6b73SSam Leffler	Belatedly note the addition of m_collapse for compacting
7075e9f6b73SSam Leffler	mbuf chains.
7085e9f6b73SSam Leffler
70948aaad5fSYaroslav Tykhiy20080126:
71048aaad5fSYaroslav Tykhiy	The fts(3) structures have been changed to use adequate
71148aaad5fSYaroslav Tykhiy	integer types for their members and so to be able to cope
71248aaad5fSYaroslav Tykhiy	with huge file trees.  The old fts(3) ABI is preserved
71348aaad5fSYaroslav Tykhiy	through symbol versioning in libc, so third-party binaries
71448aaad5fSYaroslav Tykhiy	using fts(3) should still work, although they will not take
71548aaad5fSYaroslav Tykhiy	advantage of the extended types.  At the same time, some
71648aaad5fSYaroslav Tykhiy	third-party software might fail to build after this change
71748aaad5fSYaroslav Tykhiy	due to unportable assumptions made in its source code about
71848aaad5fSYaroslav Tykhiy	fts(3) structure members.  Such software should be fixed
71948aaad5fSYaroslav Tykhiy	by its vendor or, in the worst case, in the ports tree.
72048aaad5fSYaroslav Tykhiy	FreeBSD_version 800015 marks this change for the unlikely
72148aaad5fSYaroslav Tykhiy	case that a portable fix is impossible.
72248aaad5fSYaroslav Tykhiy
72351dc1e12SRuslan Ermilov20080123:
7248015f45cSWarner Losh	To upgrade to -current after this date, you must be running
72551dc1e12SRuslan Ermilov	FreeBSD not older than 6.0-RELEASE.  Upgrading to -current
7268015f45cSWarner Losh	from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
7278015f45cSWarner Losh
728ab4a2c41SMatteo Riondato20071128:
729ab4a2c41SMatteo Riondato	The ADAPTIVE_GIANT kernel option has been retired because its
730ab4a2c41SMatteo Riondato	functionality is the default now.
731ab4a2c41SMatteo Riondato
732e393af84SMarius Strobl20071118:
733e393af84SMarius Strobl	The AT keyboard emulation of sunkbd(4) has been turned on
734e393af84SMarius Strobl	by default. In order to make the special symbols of the Sun
735e393af84SMarius Strobl	keyboards driven by sunkbd(4) work under X these now have
736e393af84SMarius Strobl	to be configured the same way as Sun USB keyboards driven
737e393af84SMarius Strobl	by ukbd(4) (which also does AT keyboard emulation), f.e.:
738e393af84SMarius Strobl
739e393af84SMarius Strobl	Option	"XkbLayout" "us"
740e393af84SMarius Strobl	Option	"XkbRules" "xorg"
741e393af84SMarius Strobl	Option	"XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
742e393af84SMarius Strobl
74333d3fffaSMarius Strobl20071024:
74433d3fffaSMarius Strobl	It has been decided that it is desirable to provide ABI
74533d3fffaSMarius Strobl	backwards compatibility to the FreeBSD 4/5/6 versions of the
74633d3fffaSMarius Strobl	PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
74733d3fffaSMarius Strobl	broken with the introduction of PCI domain support (see the
74833d3fffaSMarius Strobl	20070930 entry). Unfortunately, this required the ABI of
74933d3fffaSMarius Strobl	PCIOCGETCONF to be broken again in order to be able to
75033d3fffaSMarius Strobl	provide backwards compatibility to the old version of that
75133d3fffaSMarius Strobl	IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
75233d3fffaSMarius Strobl	again. As for prominent ports this affects neither pciutils
75333d3fffaSMarius Strobl	nor xorg-server this time, the hal port needs to be rebuilt
75433d3fffaSMarius Strobl	however.
75533d3fffaSMarius Strobl
7563d461febSJulian Elischer20071020:
7573d461febSJulian Elischer	The misnamed kthread_create() and friends have been renamed
7583d461febSJulian Elischer	to kproc_create() etc. Many of the callers already
7593d461febSJulian Elischer	used kproc_start()..
7603d461febSJulian Elischer	I will return kthread_create() and friends in a while
7613d461febSJulian Elischer	with implementations that actually create threads, not procs.
7623d461febSJulian Elischer	Renaming corresponds with version 800002.
7633d461febSJulian Elischer
764c15e0967SKen Smith20071010:
765c15e0967SKen Smith	RELENG_7 branched.
766c15e0967SKen Smith
767dc0dbf5cSWarner LoshCOMMON ITEMS:
768dc0dbf5cSWarner Losh
769a24eff53SWarner Losh	General Notes
770a24eff53SWarner Losh	-------------
771456b5dd8SWarner Losh	Avoid using make -j when upgrading.  While generally safe, there are
772456b5dd8SWarner Losh	sometimes problems using -j to upgrade.  If your upgrade fails with
773456b5dd8SWarner Losh	-j, please try again wtihout -j.  From time to time in the past there
774456b5dd8SWarner Losh	have been problems using -j with buildworld and/or installworld.  This
775456b5dd8SWarner Losh	is especially true when upgrading between "distant" versions (eg one
776456b5dd8SWarner Losh	that cross a major release boundary or several minor releases, or when
777456b5dd8SWarner Losh	several months have passed on the -current branch).
778a24eff53SWarner Losh
7795780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
7805780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
781456b5dd8SWarner Losh	environment when searching for values for global variables.  To run
782456b5dd8SWarner Losh	your build attempts in an "environmental clean room", prefix all make
783456b5dd8SWarner Losh	commands with 'env -i '.  See the env(1) manual page for more details.
7845780f3baSWarner Losh
785456b5dd8SWarner Losh	When upgrading from one major version to another it is generally best
786456b5dd8SWarner Losh	to upgrade to the latest code in the currently installed branch first,
787456b5dd8SWarner Losh	then do an upgrade to the new branch. This is the best-tested upgrade
788456b5dd8SWarner Losh	path, and has the highest probability of being successful.  Please try
789456b5dd8SWarner Losh	this approach before reporting problems with a major version upgrade.
790081ff8acSDoug Barton
791dc0dbf5cSWarner Losh	To build a kernel
792dc0dbf5cSWarner Losh	-----------------
793ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
7941cf0ef11SDavid E. O'Brien	a few days old), you should follow this procedure.  It is the most
7951cf0ef11SDavid E. O'Brien	failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
7961cf0ef11SDavid E. O'Brien
7971cf0ef11SDavid E. O'Brien	make kernel-toolchain
798282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
799282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
800dc0dbf5cSWarner Losh
8012e937dd6SAlexander Leidinger	To test a kernel once
8022e937dd6SAlexander Leidinger	---------------------
8032e937dd6SAlexander Leidinger	If you just want to boot a kernel once (because you are not sure
8042e937dd6SAlexander Leidinger	if it works, or if you want to boot a known bad kernel to provide
8052e937dd6SAlexander Leidinger	debugging information) run
8062e937dd6SAlexander Leidinger	make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
8072e937dd6SAlexander Leidinger	nextboot -k testkernel
8082e937dd6SAlexander Leidinger
809ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
810ba01eb20SWarner Losh	--------------------------------------------------------------
811456b5dd8SWarner Losh	This assumes you are already running a CURRENT system.  Replace
8120fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
813456b5dd8SWarner Losh	"arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
8140fbd2da9SKen Smith
8150fbd2da9SKen Smith	cd src/sys/${arch}/conf
81647d0d01fSWarner Losh	config KERNEL_NAME_HERE
8170fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
818ba01eb20SWarner Losh	make depend
819ba01eb20SWarner Losh	make
820ba01eb20SWarner Losh	make install
821ba01eb20SWarner Losh
822ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
823ba01eb20SWarner Losh
824ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
825ba01eb20SWarner Losh	-----------------------------------------------------------
82663cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
82763cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
82863cb445eSWarner Losh
829f643de42SWarner Losh	<make sure you have good level 0 dumps>
83063cb445eSWarner Losh	make buildworld
8316586253aSWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE
83263cb445eSWarner Losh							[1]
83363cb445eSWarner Losh	<reboot in single user>				[3]
83463cb445eSWarner Losh	mergemaster -p					[5]
83563cb445eSWarner Losh	make installworld
836e2a36081SAlexander Leidinger	make delete-old
83763cb445eSWarner Losh	mergemaster					[4]
83863cb445eSWarner Losh	<reboot>
83963cb445eSWarner Losh
840759f0aefSWarner Losh
841f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
842f27b1fceSJoseph Koshy	--------------------------------------------------
843f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
844f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
845f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
846f27b1fceSJoseph Koshy	# size.
847f27b1fceSJoseph Koshy
848f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
849f27b1fceSJoseph Koshy	<boot into -stable>
850f27b1fceSJoseph Koshy	make buildworld
8513ecf3bddSRuslan Ermilov	make buildkernel KERNCONF=YOUR_KERNEL_HERE
852f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
853f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
854f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
8552d5cde04SRuslan Ermilov	make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
8563ecf3bddSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
857f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
858f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
859f27b1fceSJoseph Koshy	<reboot into current>
860f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
861737d990aSXin LI	<maybe install compatibility libraries from ports/misc/compat*>
862f27b1fceSJoseph Koshy	<reboot>
863f27b1fceSJoseph Koshy
864f27b1fceSJoseph Koshy
865456b5dd8SWarner Losh	To upgrade in-place from 8.x-stable to current
866f27b1fceSJoseph Koshy	----------------------------------------------
867f643de42SWarner Losh	<make sure you have good level 0 dumps>
86821c075eaSWarner Losh	make buildworld					[9]
869e5dc5f61SWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE		[8]
870fc8c157fSWarner Losh							[1]
871fc8c157fSWarner Losh	<reboot in single user>				[3]
872835284beSWarner Losh	mergemaster -p					[5]
873ba26da8eSWarner Losh	make installworld
874e2a36081SAlexander Leidinger	make delete-old
875802fc49dSBrian Feldman	mergemaster -i					[4]
876ba26da8eSWarner Losh	<reboot>
877ba26da8eSWarner Losh
878fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
879fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
880fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
881fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
882fdb9f54dSWarner Losh	the UPDATING entries.
883ba26da8eSWarner Losh
8841dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
8851dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
8861dece4a9SWarner Losh	your sources that you have read and understood all the recent
8871dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
8881dece4a9SWarner Losh	much fewer pitfalls.
8891dece4a9SWarner Losh
890134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
891134d2e86SWarner Losh	should disable them at this point so they don't crash your
892134d2e86SWarner Losh	system on reboot.
893134d2e86SWarner Losh
894ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
895ee6e1fc3SWarner Losh		fsck -p
896ee6e1fc3SWarner Losh		mount -u /
897ee6e1fc3SWarner Losh		mount -a
8986586253aSWarner Losh		cd src
89947d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
900f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
901f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
902ee6e1fc3SWarner Losh
903a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
904a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
905a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
906a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
907a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
908a6cd4f9dSWarner Losh	for potential gotchas.
909a6cd4f9dSWarner Losh
910835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
911835284beSWarner Losh	you may need to do this if you get unknown user in the following
912835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
913835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
914835284beSWarner Losh	install) after the buildworld before this step if you last updated
915835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
916835284beSWarner Losh
917456b5dd8SWarner Losh	[8] In order to have a kernel that can run the 4.x binaries needed to
918456b5dd8SWarner Losh	do an installworld, you must include the COMPAT_FREEBSD4 option in
919456b5dd8SWarner Losh	your kernel.  Failure to do so may leave you with a system that is
920456b5dd8SWarner Losh	hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
921456b5dd8SWarner Losh	required to run the 5.x binaries on more recent kernels.  And so on
922456b5dd8SWarner Losh	for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
923c74fe6afSWarner Losh
924e5dc5f61SWarner Losh	Make sure that you merge any new devices from GENERIC since the
925e5dc5f61SWarner Losh	last time you updated your kernel config file.
926e5dc5f61SWarner Losh
92721c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
928e5dc5f61SWarner Losh	cvs prune empty directories.
929e5dc5f61SWarner Losh
930e5dc5f61SWarner Losh	If CPUTYPE is defined in your /etc/make.conf, make sure to use the
931e5dc5f61SWarner Losh	"?=" instead of the "=" assignment operator, so that buildworld can
932e5dc5f61SWarner Losh	override the CPUTYPE if it needs to.
933e5dc5f61SWarner Losh
934e5dc5f61SWarner Losh	MAKEOBJDIRPREFIX must be defined in an environment variable, and
935e5dc5f61SWarner Losh	not on the command line, or in /etc/make.conf.  buildworld will
936e5dc5f61SWarner Losh	warn if it is improperly defined.
937dc0dbf5cSWarner LoshFORMAT:
938dc0dbf5cSWarner Losh
939f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
9401fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
9418ce4cbbfSWarner Loshand it only starts on October 16, 2004.  Updating files can found in
942f8ab1dd6SWarner Loshprevious releases if your system is older than this.
9431fc1a0dcSWarner Losh
944e72fd46aSWarner LoshCopyright information:
945e72fd46aSWarner Losh
946456b5dd8SWarner LoshCopyright 1998-2009 M. Warner Losh.  All Rights Reserved.
947e72fd46aSWarner Losh
948772730c7SWarner LoshRedistribution, publication, translation and use, with or without
949772730c7SWarner Loshmodification, in full or in part, in any form or format of this
9509698f2c0SWarner Loshdocument are permitted without further permission from the author.
951e72fd46aSWarner Losh
952e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
953e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
954e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
955e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
956e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
957e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
958e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
959e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
960e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
961e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
962e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
963e72fd46aSWarner Losh
96422306abcSWarner LoshContact Warner Losh if you have any questions about your use of
965772730c7SWarner Loshthis document.
966772730c7SWarner Losh
96797d92980SPeter Wemm$FreeBSD$
968