- do this when breaking the D-Bus interface for other reasons
- When the GDBus stuff lands in GLib we should probably start using it
+ - probably do this when breaking the D-Bus interface for other reasons
- We probably have too many polkit actions - probably just two are enough
- reads should require org.fd.udisks.read
- - this should be yes
+ - this should be 'yes'
- write/modification should require org.fd.udisks.write
- - this should be auth_admin_keep
+ - this should be 'auth_admin_keep'
+
+ - Jobs should be separate D-Bus objects instead of Job* properties
+ on the Device objects. We should probably also synthesize Job objects
+ for jobs being tracked/managed by separate kernel- and/or user-subsystems.
+ For example, if the user does
+
+ # echo check > /sys/block/md0/md/sync_action
+
+ from the command-line, we should create a Job object. Things like that
+
+ - We should have a notion of events and a history of events. This
+ would include SMART data, IO errors and such things. Each event
+ would have generic metadata (type, collection date, source,
+ relationship to 0 or more devices, human readable string,
+ type-specific blobs) and UI like Palimpsest would allow searching,
+ viewing, organizing and purging any type of event.
+
+ We probably want some way of rate-limiting / collapsing multiple events
+ into one etc. Think tons of IO errors.
+
+ The type-specific blob could contain e.g. SMART data and this could be
+ used to realize SMART graphs.
- It would be nice to be able to have different back-ends
- Partition/Filesystem resizing
- Maybe just enhance PartitionModify
+
+ - SES2 Enclosure Management
+ - In particular, we should do something with the LEDs