Re: Coercing sane file permissions -- site specific

[rhkramer@gmail.com]

I'll answer with something a little bit like Joe's answer.  On my daily 
working machine, which uses Wheezy, I use Dophin as a file manager.

After I plug in a USB stick, after a few seconds (maybe up to 20??), a new 
entry appears on the left hand list of partitions in Dolphin.  If I click on 
that, the files are displayed in the (current working) pane of Dolphin, and I 
can use the mouse to drag and drop them, open them, or similar.

The top of that dophin pane shows where the device is mounted, for example, 
/media/84BE-2329/.

If I then go to a CLI and refer to that mountpoint, I can access the files.

To anticipate an answer to your potential next question, there is no 
pmount.allow file on this computer.

I may try the same thing on my future daily working machine, using Jessie 
(and, iiuc, systemd or whatever it is called).  If I try that, I'll let you 
know.



On Sunday, November 20, 2016 08:58:04 AM Joe wrote:
> There *is* a generic answer, which requires no fstab entry, but I have
> to admit that I haven't a clue what it is.
> 
> I'm running sid with systemd, with absolutely nothing in /etc/fstab
> which refers to USB sticks, but nonetheless any USB stick inserted is
> recognised and automounted under /media/joe (maybe immediately and maybe
> on access, I'm not sure, but it shows instantly in file managers) with
> everything in a FAT partition having ownership of joe:me and
> permissions of 644. Ext partitions have their own permissions, as
> expected.
> 
> This all Just Works, and I have no idea what configuration it depends
> on. "I didn't build this," sid basically builds and rebuilds itself, so
> I tend to keep my fingers out of the works. I do know that USB sticks
> were a real pain with usbmount, which *sometimes* mounted the entire
> device instead of the partitions, and at some point, things just
> started working better.
> 
> There is nothing in /etc/polkit-1, /etc/udev or /etc/udisks2 referring
> to USB sticks, which are the most likely suspects as far as I can see.
> Presumably the culprit is systemd, as usual, so possibly someone more
> knowledgable about this beast can finish my part-answer.