No such device error for Linux should be considered as missing file
svartalf opened this issue · 0 comments
svartalf commented
Originally reported at svartalf/rust-battop#7
It seems that some drivers are creating the files at sysfs, but attempt to read them fails with the ENODEV error.
Same issue can be observed here with a current_now file.
I suppose it would be okay to consider the ENODEV errors as a "missing file" result.