1c18f6365SGreg Kroah-HartmanWhat:		/sys/devices
2c18f6365SGreg Kroah-HartmanDate:		February 2006
3bc5bca53SGreg Kroah-HartmanContact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4c18f6365SGreg Kroah-HartmanDescription:
5c18f6365SGreg Kroah-Hartman		The /sys/devices tree contains a snapshot of the
6c18f6365SGreg Kroah-Hartman		internal state of the kernel device tree.  Devices will
7c18f6365SGreg Kroah-Hartman		be added and removed dynamically as the machine runs,
8c18f6365SGreg Kroah-Hartman		and between different kernel versions, the layout of the
9c18f6365SGreg Kroah-Hartman		devices within this tree will change.
10c18f6365SGreg Kroah-Hartman
11c18f6365SGreg Kroah-Hartman		Please do not rely on the format of this tree because of
12c18f6365SGreg Kroah-Hartman		this.  If a program wishes to find different things in
13c18f6365SGreg Kroah-Hartman		the tree, please use the /sys/class structure and rely
14c18f6365SGreg Kroah-Hartman		on the symlinks there to point to the proper location
15c18f6365SGreg Kroah-Hartman		within the /sys/devices tree of the individual devices.
16c18f6365SGreg Kroah-Hartman		Or rely on the uevent messages to notify programs of
17c18f6365SGreg Kroah-Hartman		devices being added and removed from this tree to find
18c18f6365SGreg Kroah-Hartman		the location of those devices.
19c18f6365SGreg Kroah-Hartman
20c18f6365SGreg Kroah-Hartman		Note that sometimes not all devices along the directory
21c18f6365SGreg Kroah-Hartman		chain will have emitted uevent messages, so userspace
22c18f6365SGreg Kroah-Hartman		programs must be able to handle such occurrences.
23c18f6365SGreg Kroah-Hartman
24c18f6365SGreg Kroah-HartmanUsers:
25c18f6365SGreg Kroah-Hartman	udev <linux-hotplug-devel@lists.sourceforge.net>
26