7.8. Resources, ResourceId and EntityPath

It is important to understand the relationship between a Resource, it's ID and it's EntityPath.

In order be able to re-call the resource by it's ResourceId as well as have persistence in resource identification between sessions, openhpi persisted the SaHpiResourceIdT ResourceId field in the RptEntry structure using the resource's entitpath, being unique, by converting the resource's EntityPath to string, appending the root path defined in the config file to it then converting it to a unique number using uid utilities provided by openhpi.