On 12/10/2021 16:54, Lennart Poettering wrote:
On Di, 12.10.21 16:17, lejeczek (pelj...@yahoo.co.uk) wrote:
I have 'clevis' set to get luks pin from 'tang' but unlock does not happen
at/during boot time and I wonder if someone can share thoughts on how to
investigate that?
I cannot see
On Di, 12.10.21 16:17, lejeczek (pelj...@yahoo.co.uk) wrote:
> > > I have 'clevis' set to get luks pin from 'tang' but unlock does not happen
> > > at/during boot time and I wonder if someone can share thoughts on how to
> > > investigate that?
> > > I cannot see anything obvious fail during
On 28/09/2021 12:33, Lennart Poettering wrote:
On Di, 28.09.21 12:26, lejeczek (pelj...@yahoo.co.uk) wrote:
Hi guys.
I have 'clevis' set to get luks pin from 'tang' but unlock does not happen
at/during boot time and I wonder if someone can share thoughts on how to
investigate that?
I
>>> Lennart Poettering schrieb am 12.10.2021 um 12:56
in
Nachricht :
> On Di, 12.10.21 12:09, Frank Steiner (fsteiner‑ma...@bio.ifi.lmu.de) wrote:
>
>> Hi,
>>
>> after upgrading from SLES 15 SP2 (systemd 2.34) to SP3 (systemd 2.46)
>> the boot messages are not only colored (which I like for
On Di, 12.10.21 12:09, Frank Steiner (fsteiner-ma...@bio.ifi.lmu.de) wrote:
> Hi,
>
> after upgrading from SLES 15 SP2 (systemd 2.34) to SP3 (systemd 2.46)
> the boot messages are not only colored (which I like for seeing failures
> in red) but partially printed in bold face. This makes messages
Hi,
after upgrading from SLES 15 SP2 (systemd 2.34) to SP3 (systemd 2.46)
the boot messages are not only colored (which I like for seeing failures
in red) but partially printed in bold face. This makes messages indeed
harder to read on serial console (with amt or ipmi), so I wonder if
there is a
