Opaque object representing one kernel sys device.

Device number.

Create new udev device, and fill in information from the sys device and the udev database entry. The syspath is the absolute path to the device, including the sys mount point.

Create new udev device, and fill in information from the sys device and the udev database entry. The device is looked-up by its major/minor number and type. Character and block device numbers are not unique across the two types.

The device is looked up by the subsystem and name string of the device, like "mem" / "zero", or "block" / "sda".

The device is looked-up by a special string:

• b8:2 - block device major:minor
• c128:1 - char device major:minor
• n3 - network device ifindex
• +sound:card29 - kernel driver core subsystem:device name

Create new udev device, and fill in information from the current process environment. This only works reliable if the process is called from a udev rule. It is usually used for tools executed from IMPORT= rules.

Find the next parent device, and fill in information from the sys device and the udev database entry.

Find the next parent device, with a matching subsystem and devtype value, and fill in information from the sys device and the udev database entry.

Retrieve the kernel devpath value of the udev device. The path does not contain the sys mount point, and starts with a '/'.

Retrieve the subsystem string of the udev device. The string does not contain any "/".

Retrieve the devtype string of the udev device.

Retrieve the sys path of the udev device. The path is an absolute path and starts with the sys mount point.

Get the kernel device name in /sys.

Get the instance number of the device.

Retrieve the device node file name belonging to the udev device. The path is an absolute path, and starts with the device directory.

Check if udev has already handled the device and has set up device node permissions and context, or has renamed a network device.

This is only implemented for devices with a device node or network interfaces. All other devices return 1 here.

Retrieve the list of device links pointing to the device file of the udev device. The next list entry can be retrieved with getNext, which returns Nothing if no more entries exist. The devlink path can be retrieved from the list entry by getName. The path is an absolute path, and starts with the device directory.

Retrieve the list of key/value device properties of the udev device. The next list entry can be retrieved with getNext, which returns Nothing if no more entries exist. The property name can be retrieved from the list entry by getName, the property value by getValue.

Retrieve the list of tags attached to the udev device. The next list entry can be retrieved with getNext, which returns Nothing if no more entries exist. The tag string can be retrieved from the list entry by getName.

Get the value of a given property.

Get the kernel driver name.

Get the device major/minor number.

This is only valid if the device was received through a monitor. Devices read from sys do not have an action string.

The retrieved value is cached in the device. Repeated calls will return the same value and not open the attribute again.

Update the contents of the sys attribute and the cached value of the device.

Retrieve the list of available sysattrs, with value being empty; This just return all available sysfs attributes for a particular device without reading their values.

This is only valid if the device was received through a monitor. Devices read from sys do not have a sequence number.

Return the number of microseconds passed since udev set up the device for the first time.

This is only implemented for devices with need to store properties in the udev database. All other devices return Nothing here.

Check if a given device has a certain tag associated.