Lines Matching refs:a

5 by the kernel developers that the Linux kernel does not provide a stable
10 low-level userspace applications, with a new kernel release, the users
26   current kernel development. The goal of providing a stable interface
31   Parsing /proc/mounts is a waste of time. Other mount points are a
33   possibly support a SYSFS_PATH environment variable to overwrite the
40   just simply a "device". Class-, bus-, physical, ... types are just
44   The properties of a device are:
50         /sys, and always starting with a slash
51       - all elements of a devpath must be real directories. Symlinks
56       - using or exposing symlink values as elements in a devpath string
57         is a bug in the application
60       - a directory name, identical to the last element of the devpath
65       - simple string, never a path or a link
70       - a simple string, which may contain spaces, never a path or a
74       - devices which do not have "driver"-link just do not have a
75         driver; copying the driver value in a child device context is a
81       - accessing attributes reached by a symlink pointing to another device,
82         like the "device"-link, is a bug in the application
84   Everything else is just a kernel driver-core implementation detail
87 - Properties of parent devices never belong into a child device.
89   context properties. If the device 'eth0' or 'sda' does not have a
90   "driver"-link, then this device does not have a driver. Its value is empty.
91   Never copy any property of the parent-device into a child-device. Parent
95 - Hierarchy in a single device tree
112   The devices belonging to a subsystem will create a symlink in the
117   places, as the kernel is free to move a subsystem from one place to
122   /sys/block and /sys/class/block are not interchangeable is a bug in
128   at the same level, never in a hierarchy. Assuming the block subsystem to
130   a bug in the application.
133   Never depend on the "device"-link. The "device"-link is a workaround
135   /sys/devices/ like the bus devices. If the link-resolving of a
140   a device in /sys/devices/ is a bug in the application.
141   Accessing /sys/class/net/eth0/device is a bug in the application.
144   directory.  These links are also a workaround for the design mistake
145   that class devices are not created in /sys/devices. If a device
150   real child device directories in the /sys/devices tree is a bug in
157   Never depend on a specific parent device position in the devpath,
161   the device that matches the expected subsystem. Depending on a specific
162   position of a parent device or exposing relative paths using "../" to
163   access the chain of parents is a bug in the application.
178   Error codes will not be changed without good reason, and should a change
183   the attribute files to remain consistent in the absence of a version
184   attribute change in the context of a given attribute.