On 11/02/15 20:03, Lennart Poettering wrote:
>
> Well, no. It would add Wants= and After=, instead of Requires= and
> After=. But I figure what you wrote was just a typo?
yes what you say is what I meant.
> I think we should switch over to use WantsMountsFor for this
> unconditionally. After all we
On Thu, 05.02.15 10:08, John Lane (syst...@jelmail.com) wrote:
> On 02/02/15 20:54, Lennart Poettering wrote:
> > On Sat, 31.01.15 11:21, John Lane (syst...@jelmail.com) wrote:
> >
> >> Further to this, I tried manually creating a systemd-cryptsetup unit
> >> instead of putting an entry in /etc/cr
On 02/02/15 20:54, Lennart Poettering wrote:
> On Sat, 31.01.15 11:21, John Lane (syst...@jelmail.com) wrote:
>
>> Further to this, I tried manually creating a systemd-cryptsetup unit
>> instead of putting an entry in /etc/crypttab.
>> This allowed me to remove the "RequiresMountsFor" entry.
> Yeah
On 02/02/15 20:49, Lennart Poettering wrote:
> BTW, just to mention this. You can also just write:
>
> # systemctl start /home/myuser/data
That's good to know, thanks.
>
> This will automatically be translated to
> "home-myuser-data.mount". systemctl has some logic built in to
> translate strings t
On Sat, 31.01.15 11:21, John Lane (syst...@jelmail.com) wrote:
> Further to this, I tried manually creating a systemd-cryptsetup unit
> instead of putting an entry in /etc/crypttab.
> This allowed me to remove the "RequiresMountsFor" entry.
Yeah, I figure for your usecase a "WantsMountsFor=" sett
On Thu, 29.01.15 17:31, John Lane (syst...@jelmail.com) wrote:
> I am looking for some advice about configuring encrypted volumes with
> systemd that I want to open on demand (noauto).
>
> I can add entries into /etc/crypttab and /etc/fstab for the device, for
> example
>
> #
On 31/01/15 10:25, John Lane wrote:
> On 30/01/15 09:49, Jan Janssen wrote:
>>
>> But really: why not use automounting logic in fstab?:
>> /dev/mapper/data /home/myuser/data ext4 noauto,x-systemd.automount 0 0
>>
>> No need to manually trigger a mount. And you can even use "noauto" in
>> cryptt
On 30/01/15 09:49, Jan Janssen wrote:
>
> But really: why not use automounting logic in fstab?:
> /dev/mapper/data /home/myuser/data ext4 noauto,x-systemd.automount 0 0
>
> No need to manually trigger a mount. And you can even use "noauto" in
> crypttab so that the encrypted device is only open
John Lane jelmail.com> writes:
> $ mount /home/myuser/data
> mount: special device /dev/mapper/keyring does not exist
Your crypttab entry uses "noauto" as an option. This means that it won't get
activated and no plain text device is created. Hence your manual mount can
only fail.
> I'm guessi
On Thu, Jan 29, 2015 at 8:31 PM, John Lane wrote:
> I am looking for some advice about configuring encrypted volumes with
> systemd that I want to open on demand (noauto).
>
> I can add entries into /etc/crypttab and /etc/fstab for the device, for
> example
>
> #
10 matches
Mail list logo
