trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: August 2013

Re: [trinity-devel] about pmount and R14 new backends

From: "Timothy Pearson" <kb9vqf@...>
Date: Wed, 7 Aug 2013 15:42:44 -0500
>> You're right, I think that 99% of the time, the connected user can eject
>> them with eject command ...
>>   What about the mount feature ? Can't udisks(2) be used for that
>> purpose,
>> instead of pmount ? We do not have a "-DWITH_PMOUNT" option yet, but
>> distributions are more likely to provide udisks than pmount ...
>>
>  I've told about this in the first answer on the thread. For now it won't
> be introduced before 14.1 because it will require API changes.

Why would it require an API change?  The entire point of the TDE HW
library is to abstract low level calls; simple calls to the udisks/udisks2
mount/unmount commands can be easily added (with fallback to pmount if
they do not succeed).  See the eject routine for an example of how to do
this properly with CMake conditionals and fallback support.

Tim