specifiy custom client on command line/specify custom client for unmount/disconnect event

Bug #660020 reported by Steffen Barszus
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

As started here allready:

The requirements are:
- to have a non standard client on mount
- to have a non standard client on unmount
- to provide the mountpoint to this clients
To specify these on command line of udisks-automounter

Standard array of apps should not be checked anymore if this options are specified.

proof of concept: http://pastebin.com/qRDgDi5P (will be reqorked)

Like that and started with ck-launch-session (to mount as different systemuser), the udisk-automounter can be used for HTPC environment like http://www.yavdr.org :)

I will rework what i have done (which did not had the intention to share it) and provide a patch here once done.

Revision history for this message
Steffen Barszus (steffenbpunkt) wrote :

Please check attached patch, if this is acceptable.

Revision history for this message
Steffen Barszus (steffenbpunkt) wrote :

I also tried to put an umount-all, for safe remove, together. This kind of works(it detects the right device) - but doesn't umount :/

Revision history for this message
Martin Pitt (pitti) wrote :


Sorry, I didn't see this patch in time. I do like the idea of being able to specify a custom --mount command, if the builtin list doesn't suffice. However, I don't buy the usefulness of --unmount. At the time when this is called, the entire device already went away, so there's little you can do about the device/mount still. What's your use case here?

However, this patch is quite hard to review and apply, as the patch makes a lot of unnecessary whitespace changes. Perhaps you can clean it up a little in that regard?

Perhaps you can re-do this to only add the --mount option, and I'll get that in separately?


Changed in udisks-automounter:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for udisks-automounter because there has been no activity for 60 days.]

Changed in udisks-automounter:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.