On 2024-07-14 13:17:45 +0200, Lists wrote:
> On 2024-07-14 11:00, Nicolas George wrote:
> > Hi.
> >
> > In case you are running unstable or testing and it recently started
> > blocking at boot waiting for encrypted swap or something to do with
> > encrypted disks:
> >
> > Check if systemd-cryptse
Lists (12024-07-16):
> In that case you were correct. I had found posts online where people were
> pointing in the direction of systemd and due to the problem with
> systemd-cryptsetup you warned us about I was inclined to take those posts at
> face value. It seems that was not "fair".
That happen
On 2024-07-16 12:51, Nicolas George wrote:
Lists (12024-07-16):
That referred to a warning I got after booting up after d-i finished
installing the system. The exact message shown was this:
cryptsetup: WARNING nvme1n1p3_crypt: ignoring unknown option
'x-initrd.attach'
This message comes from
Lists (12024-07-16):
> That referred to a warning I got after booting up after d-i finished
> installing the system. The exact message shown was this:
>
> cryptsetup: WARNING nvme1n1p3_crypt: ignoring unknown option
> 'x-initrd.attach'
This message comes from /usr/lib/cryptsetup/functions, a fil
On 2024-07-16 11:52, Nicolas George wrote:
I do not know what you are referring to when you talk about
x-initrd.attach, you were too terse. But I notice that you talked about
it in the same paragraph that you reported the inaccurate information
that systemd has its own implementation of cryptset
Lists (12024-07-15):
> For the most part I understand your point of view. As a matter of fact I am
> not even opposed to systemd as such [1], but over the years I have had my
> share of problems that in the end proved to be caused by some transition to
> systemd. This has made me a bit wary of it.
Hi Nicolas,
Thanks for the explanation.
For the most part I understand your point of view. As a matter of fact I
am not even opposed to systemd as such [1], but over the years I have
had my share of problems that in the end proved to be caused by some
transition to systemd. This has made me a
Lists (12024-07-14):
> When I researched the problem I encountered some posts stating that systemd
> had its own implementation for cryptsetup
This is not true. systemd-cryptsetup uses libcryptsetup, it is mostly
only glue.
>
> Why the *&^%#@! it is necessary to have this borg-like behaviour of
On 2024-07-14, Erwan David wrote:
> I have a "full" disk encryption as made by the installer, thus mounted in the
> initramfs, so it may be a little different
If "full disk" include /boot you should be ask for password by grub. Else
it is initramfs and you should be ask by cryptsetup
(package cry
On 2024-07-14 11:00, Nicolas George wrote:
Hi.
In case you are running unstable or testing and it recently started
blocking at boot waiting for encrypted swap or something to do with
encrypted disks:
Check if systemd-cryptsetup is installed.
HtH
Thanks for the confirmation!
I downloaded deb
Le 14/07/2024 à 11:44, Nicolas George a écrit :
Erwan David (12024-07-14):
You are a bit cryptic here : should it be installed or should it be removed
Sorry. For me it was not installed and installing it fixed the problem.
? I am running testing without problem and systemd-cryptsetup is not
i
Erwan David (12024-07-14):
> You are a bit cryptic here : should it be installed or should it be removed
Sorry. For me it was not installed and installing it fixed the problem.
> ? I am running testing without problem and systemd-cryptsetup is not
> installed. If I should install it I'd prefer to
Le 14/07/2024 à 11:00, Nicolas George a écrit :
Hi.
In case you are running unstable or testing and it recently started
blocking at boot waiting for encrypted swap or something to do with
encrypted disks:
Check if systemd-cryptsetup is installed.
HtH
You are a bit cryptic here : should it be
13 matches
Mail list logo
