public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Encrypting a hard drive's data. Best method.
Date: Wed, 10 Jun 2020 01:59:19 -0500	[thread overview]
Message-ID: <3082a322-c6f8-31e7-fbc4-823963307b87@gmail.com> (raw)
In-Reply-To: <ddcf7e41-ef39-eae8-ba36-82efc057a1ee@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

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. 
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.  I type in the password but it
mounts it to the wrong place.  If I do it on the command line, it works
as expected.  I have it set up in dmcrypt and fstab.  So, command line
works, KDE's Device Notifier doesn't.  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.

How do I tell the Device Notifier that I want it mounted somewhere
else?  I've never done this part before since I let everything else
mount under /run.  My cameras, cell phone, card reader and such mounts
under it.  That's fine for those.  This I want to mount under /home tho. 

Is this doable?  Is there another tool KDE needs to do this? 

Thanks.

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 1405 bytes --]

  parent reply	other threads:[~2020-06-10  6:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-06  4:37 [gentoo-user] Encrypting a hard drive's data. Best method Dale
2020-06-06  7:14 ` J. Roeleveld
2020-06-06  7:16 ` J. Roeleveld
2020-06-06  7:49   ` Dale
2020-06-06 10:32     ` Michael
2020-06-06 14:14       ` antlists
2020-06-06 11:05     ` Rich Freeman
2020-06-06 13:31       ` Victor Ivanov
2020-06-06 13:57     ` antlists
2020-06-06 14:10       ` Rich Freeman
2020-06-06 15:05         ` Jack
2020-06-06 14:18       ` antlists
2020-06-06 15:07       ` Dale
2020-06-06 19:02         ` J. Roeleveld
2020-06-06 14:07 ` Victor Ivanov
2020-06-06 18:51   ` Rich Freeman
2020-06-06 19:38     ` Victor Ivanov
2020-06-06 20:12       ` Rich Freeman
2020-06-07  0:47         ` Victor Ivanov
2020-06-07  1:04           ` Rich Freeman
2020-06-07  1:50             ` Dale
2020-06-07  8:08               ` Dale
2020-06-07  9:07                 ` antlists
2020-06-07 18:23                   ` antlists
2020-06-09 20:24                     ` Dale
2020-06-09 21:30                       ` [gentoo-user] Encrypting a hard drive's data. Best method. PICS attached Dale
2020-06-07 10:33                 ` [gentoo-user] Encrypting a hard drive's data. Best method Rich Freeman
2020-06-07 11:52                 ` Victor Ivanov
2020-06-07 12:43                   ` Victor Ivanov
2020-06-07  7:37         ` antlists
2020-06-06 15:07 ` Frank Steinmetzger
2020-06-06 20:21 ` Sebastiaan L. Zoutendijk
2020-06-07  1:54   ` Dale
2020-06-10  6:59 ` Dale [this message]
2020-06-10  9:52   ` Michael
2020-06-10 21:02     ` Dale
2020-06-10 13:37   ` Victor Ivanov
2020-06-10 20:52     ` Dale
2020-06-11 21:51       ` Victor Ivanov
2020-06-11 22:17         ` Dale
2020-06-11 23:08           ` Victor Ivanov
2020-06-12  2:00             ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3082a322-c6f8-31e7-fbc4-823963307b87@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox