[I posted it once already, but it ended up buried in another discussion
thread due to a botched InReplyTo]
Is libatasmart a going concern? The functionality overlaps with
smartmontools, and the development seems to have stalled [1]. I
originally started using libatasmart few years ago because it had better
support for USB bridges, i.e. it allowed reading SMART data from USB
external enclosures, which smartctl couldn't do at the time.
Recently, however, I ran into issues in skdump reading the SSD SMART
attributes. I opened a bugzilla case [2], but there has been no traffic
there.
Is there a reason for two SMART utilities? I believe that the current
smartctl functionality is a superset of libatasmart's. Are there
capabilities in libatasmart that justify its separate existence?
[1] last commit on http://git.0pointer.de/?p=libatasmart.git is from 2
years ago
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1103179
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
