<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Hmm. As far as the installer goes, having the debian-installer mark
the device with <span class="term"><code class="option">x-initrd.attach</code></span>
which appears to have similar functionality (systemd fomat) but not <span
class="term"><code class="option">initramfs</code></span> seems
like an oversight or a bug in itself. The installer should leave the
computer in a bootable state. I suppose the installer should either
also add the <span class="term"><code class="option">initramfs</code></span> option,
or else the <span class="term"><code class="option">x-initrd.attach </code></span>flag
it already adds should produce similar behaviour for the purposes of
determining drives required at initramfs time.
<p><br>
</p>
<p>On Tue, 16 Jun 2026 18:14:04 +0200 Guilhem Moulin
<a class="moz-txt-link-rfc2396E" href="mailto:guilhem@debian.org"><guilhem@debian.org></a> wrote:</p>
> On Tue, 16 Jun 2026 at 10:38:29 -0500, Alez wrote:<br>
> > The installer should leave the computer in a bootable
state.<br>
> <br>
> The computer is bootable isn't it? AFAIK remote unlocking isn't
done by<br>
> the installer itself.<br>
> <br>
> -- <br>
> Guilhem.<br>
> <br>
> <br>
<br>
</body>
</html>