sysfs-dev (e5451c8f8330e03ad3cfa16048b4daf961af434f) | sysfs-dev (54a19b4d3fe0fa0a31b46cd60951e8177cac25fa) |
---|---|
1What: /sys/dev 2Date: April 2008 3KernelVersion: 2.6.26 4Contact: Dan Williams <dan.j.williams@intel.com> 5Description: The /sys/dev tree provides a method to look up the sysfs 6 path for a device using the information returned from 7 stat(2). There are two directories, 'block' and 'char', 8 beneath /sys/dev containing symbolic links with names of 9 the form "<major>:<minor>". These links point to the 10 corresponding sysfs path for the given device. 11 | 1What: /sys/dev 2Date: April 2008 3KernelVersion: 2.6.26 4Contact: Dan Williams <dan.j.williams@intel.com> 5Description: The /sys/dev tree provides a method to look up the sysfs 6 path for a device using the information returned from 7 stat(2). There are two directories, 'block' and 'char', 8 beneath /sys/dev containing symbolic links with names of 9 the form "<major>:<minor>". These links point to the 10 corresponding sysfs path for the given device. 11 |
12 Example: 13 $ readlink /sys/dev/block/8:32 14 ../../block/sdc | 12 Example:: |
15 | 13 |
14 $ readlink /sys/dev/block/8:32 15 ../../block/sdc 16 |
|
16 Entries in /sys/dev/char and /sys/dev/block will be 17 dynamically created and destroyed as devices enter and 18 leave the system. 19 20Users: mdadm <linux-raid@vger.kernel.org> | 17 Entries in /sys/dev/char and /sys/dev/block will be 18 dynamically created and destroyed as devices enter and 19 leave the system. 20 21Users: mdadm <linux-raid@vger.kernel.org> |