View Single Post
Old 07-26-2016, 02:37 PM   #703
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Well, my Kindle recently took to claiming to be an internal device, so it doesn't get automounted and udisks2 wanted sudo to mount it!
(But calibre still mounts it for me, so I don't care anyway.)

And despite the ridiculous move of media devices to weird obscure directories, I added the following udev rule:
Code:
[eschwartz@arch ~]$ cat /etc/udev/rules.d/99-udisks-fix-media.rules 
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"
Which I think is also automatically used on Ubuntu (intelligent policy choice). That should cover the common non-techie case. EDIT: Or they just stuck with old udisks1 for a really long time.
If not, well, I cannot make ALL the disclaimers, it would take too long.

Last edited by eschwartz; 07-26-2016 at 05:07 PM.
eschwartz is offline   Reply With Quote