<Mic92>
I can also see a lot of XXXX in the binary
<flokli>
Yes
<flokli>
And the /nix/ is cut off as well
<flokli>
Can't we just use patchelf there?
<Mic92>
flokli: you can removeReferencesTo here
<Mic92>
But I am not sure what the bug is about.
<flokli>
the bug is about initrd assembly failing since the meson bump
<Mic92>
flokli: the length of rpath is not calculated correctly I thin
<Mic92>
flokli: so the hostfix could be even sed
<Mic92>
flokli: Is there actually a reason why lvm/dmsetup are included in initrd by default?
<Mic92>
I don't think I use any of them
<ajs124>
Mic92: hasn't it always been like that? Iirc our initrd is kind of suboptimal when it comes to that kind of stuff anyways, because it's hard to include arbitraty "phases" optionally, right?
<Mic92>
ajs124: is it tough? I see that some programs are included optionally
<ajs124>
I got that impression from reading e.g. #46541, but it's been a while, so I might be misremembering.
<flokli>
look at ac8a2ae57700e65e11396027993aab17b7187b51
<Mic92>
ajs124: It's funny that it was 2018-me asking the same question
<flokli>
That PR is somewhat related - I wonder if we should only provide lvm and mdadm in initrd if it's enabled in the nixos configuration (which should happen via nixos-generate-config)
<flokli>
and provide some release notes of course
<ajs124>
lol. Yeah, the impression I'm always getting is that the initrd does too much for some people and too little for others. Maybe even the same people, just for different environments.