>>> Michael Cassaniti schrieb am 26.08.2022 um 06:46
>>> in
Nachricht
<01000182d8797b39-375650cc-485b-43ec-84e0-9be3a66f22f4-000...@email.amazonses.co
>:
> On 25/8/22 22:22, Lennart Poettering wrote:
>> On Do, 25.08.22 10:50, Michael Cassaniti (mich...@cassaniti.id.au) wrote:
>>
>>> It seems to
On 25/8/22 22:22, Lennart Poettering wrote:
On Do, 25.08.22 10:50, Michael Cassaniti (mich...@cassaniti.id.au) wrote:
It seems to be somewhat more complicated than that, and perhaps it has more
to do with my setup. Here's my /etc/crypttab which just might explain a bit:
# Mount root and s
On Do, 25.08.22 10:50, Michael Cassaniti (mich...@cassaniti.id.au) wrote:
> It seems to be somewhat more complicated than that, and perhaps it has more
> to do with my setup. Here's my /etc/crypttab which just might explain a bit:
>
> # Mount root and swap
> # These will initially have an
On 25/8/22 20:43, Lennart Poettering wrote:
On Mi, 17.08.22 13:23, Michael Cassaniti (mich...@cassaniti.id.au) wrote:
Hi,
I'm trying to order my units and targets during early boot so that:
1. A symlink to the specific FIDO2 token I'm using gets created. I already
have a udev rule in place for
On Mi, 17.08.22 13:23, Michael Cassaniti (mich...@cassaniti.id.au) wrote:
> Hi,
>
> I'm trying to order my units and targets during early boot so that:
> 1. A symlink to the specific FIDO2 token I'm using gets created. I already
> have a udev rule in place for this and it successfully creates the
On 17.08.2022 16:23, Michael Cassaniti wrote:
> Hi,
>
> I'm trying to order my units and targets during early boot so that:
> 1. A symlink to the specific FIDO2 token I'm using gets created. I
> already have a udev rule in place for this and it successfully creates
> the symlink under /dev. Beca
