[Kde-hardware-devel] GSoC Proposal : S.M.A.R.T HDD health and ISO file / optical disk management

Anant Kamath kamathanant at gmail.com
Tue Mar 20 12:29:26 UTC 2012


On 19 March 2012 14:59, Alex Fiestas <afiestas at kde.org> wrote:

> This kind of Disk operationsa are not material for SystemSettings, be aware
> that System Settings IS NOT like the "Windows control panel", the main
> difference is that ours is ONLY for preferences while Windows CP is for
> system
> management as well.
>
> Said that, I don't think these Disk operations should be done in system
> preference but instead in a separate application.
>

I get it.



> Do we have any guarantee that libatasmart API won't change? I don't care on
>
using udisk/udisk2 but I want we to abstract it in a way that we only have
> to
> care about creating a new backend in case that udisk2 changes its api (I'm
> sure we will see udisk3 someday).
>
>
> So the best way to go about it would be to modify our existing udisks
backend (and the upcoming udisks2 backend) so that they expose SMART
atrributes and other relevant udisks dbus methods to the frontend classes
,and then create the application using this new solid API, right?
Of course, I think we still need to investigate if the set of SMART
properties/methods available through udisks are sufficient for our
purposes.( I'm not sure it provides all properties/functions provided by
libatasmart)

As for the need to run SMART tests, I'm finding info on how SMART
attributes are updated (besides testing, there's only offline data
collection which updates these attributes AFAIK)..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-hardware-devel/attachments/20120320/f0b56a9c/attachment.html>


More information about the Kde-hardware-devel mailing list