----- Original Message -----
> 2) that has its place in a storage API.
Why is an API providing some additional functionality you are not going
to use in your specific usecase a problem ?
I'm sure glibc and kernel provide many API calls not directly used by
the default apps on the workstation and we are still using them...
If I ever saw an example of logical fallacy, that is one.
Why do I care? Because if I didn't whine on this very list some time ago,
storaged wouldn't be API-compatible with udisks2, and I have to wonder about
the architecture of something we would have to support when it makes
decisions like supporting features for which you don't have a clear use-case.