Michael wrote:
> On Wednesday, 10 June 2020 07:59:19 BST Dale wrote:
>> Howdy,
>>
>> Same topic just new question.  I use KDE and am wanting to have it so
>> the Device Notifier will allow me to mount the drive when I turn it on. 
> I probably missed in earlier threads, but is this is an externally powered USB 
> device?
>

Not USB but eSATA. 

>> So far, I got it set up and when I turn the drive on and click for it to
>> mount it, it asks me for a password.
> Where do you "click for it"?

The Device Notifier in the KDE panel thingy.  I use it to access my
cameras, SD cards put in my card reader and even my cell phone. 


>
>
>> I type in the password but it mounts it to the wrong place.  
> Please define "wrong place".
>

It mounts under /run.  I want it mounted under /home. 


>> If I do it on the command line, it works  as expected.  
> What is expected?
>

I was expecting it to mount from the Device Notifier just like it does
from the command line.

>> I have it set up in dmcrypt and fstab.  So, command line
>> works, KDE's Device Notifier doesn't.
> For the avoidance of doubt:
>
> "command line" = /bin/mount
>
> "KDE's Device Notifier" = /usr/bin/udisksctl
>
> There is a difference between the two:
>
> $ ls -la /bin/mount
> -rws--x--x 1 root root 56360 May 11 00:25 /bin/mount
>
> $ ls -la /usr/bin/udisksctl 
> -rwxr-xr-x 1 root root 60496 Nov 23  2019 /usr/bin/udisksctl
>
>
> You run mount as root with temporarily elevated privileges and operate on 
> devices directly via the kernel, but can only mount such block devices if they 
> have a corresponding /etc/fstab entry - unless you are root.
>
> You run udisksctl as plain user - it is a userspace command which operates on 
> the udisks daemon to manipulate mountable devices via D-Bus.  The default 
> mountpoint by udisksctl is under /run/media/<user_name>/LABEL
>

True but since I'm wanting to mount it under the same /home directory as
the user doing the mounting, it shouldn't require any additional
privileges. 


>> It tells me I don't have
>> permission to access but it also mounts it in the wrong place.  I
>> suspect it mounting it in the wrong place leads to the permissions
>> error.  It mounts under /run.  I want it mounted under /home.
> You may be able to achieve this via udev rules for the specific UUID of the 
> disk, or perhaps via a symlink from /home to the /run mountpoint.  I haven't 
> tested this, but you could give it a spin and see what you get.
>
> PS. You can ignore my earlier questions, no need to answer them.  The 
> structure of your message was perhaps back to front to assist my 
> understanding.  :-)


No problem.  Sometimes when anyone is writing, it's assumed that
everyone else knows the steps that are taken.  Usually that is not the
case.  It's why we always ask for error messages, commands used etc etc
etc.  ;-)

Based on everything I've found with google, I think the Device Notifier
is badly limited.  It can get to a certain point but it can't go any
further.  It seems we need a better tool or the current tool needs a
little extra programming.  I was wanting to avoid the command line part
in case something happened to me and someone needed to access a
encrypted device.  Victor seems to confirm that with his reply. 

Thanks.

Dale

:-)  :-)