sysobj-device - storing device objects in the system objects database
The system objects database, sysobj enables the following tasks:
Storing objects describing a part of the system, such as devices
Looking objects up in a flexible way
Associating persistent data in the form of properties with the objects
Cross-referencing namespaces in which the objects appear
The following sections provide an overview of how device objects are stored in the system objects database, sysobj.
Oracle Solaris uses the following class names to describe devices:
Devices
Device minor nodes
An object appears in one or more namespaces for each of its classes. The following namespaces are currently defined for the classes of device objects:
The driver@instance namespace
devids in string form
The device path under /devices
The device path under /devices
Persistent data stored with a system object is called a property. A property can be of any type that the libnvpair(3LIB) library supports. Properties are divided into property classes. The following list specifies the property classes for the device object classes:
The current state and structure
Software properties such as driver, and instance
libdevid(3LIB), libnvpair(3LIB), libsysobj(3LIB), sysobj_add_alias(3SYSOBJ), sysobj_add_property(3SYSOBJ), sysobj_create(3SYSOBJ), sysobj_event_register(3SYSOBJ), devfs(4FS), sysobjadm(8), sysobjd(8)