On Fri, Dec 30, 2016 at 06:01:02AM -0700, Trammell Hudson wrote: > On Thu, Dec 29, 2016 at 09:20:41PM +0000, Rusty Bird wrote: > > If I understand it right, [rd.]luks.key= isn't working as it should? > > I've played around with that a tiny bit and systemd-cryptsetup-generator > > was indeed behaving weirdly, some "out of memory" nonsense. > > I don't think that I get that error; it seems to just be ignored and > Qube's initrd prompts for a disk password.
When I actually read the text on the screen during the boot, I see the same "out of memory" error. This does seem to indicate that it is the systemd bug that you had identified: > > Which might be fixed by > > https://github.com/systemd/systemd/commit/c802a7306bdc3e82378a87acd9402bbabe9f6b28 Have you been able to test this change? Figuring out how to deploy one particular patch into the qubes initrd seems complicated; one big advantage of shell scripts for these things is that they can be edited on the fly, rather than requiring recompiling all of systemd. -- Trammell -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20170105133852.GD30182%40chishio.swcp.com. For more options, visit https://groups.google.com/d/optout.
