Lennart Poettering
Lennart Poettering
I prepped a fix for the issues @YHNdnzj raised now in #37981. Kinda still hoping that @Werkov would address the documentation issue, he kinda volunteered, no? ;-)
yeah, we should have explicit support for something like that. But I'd assume we'd want dm-verity-of-dm-crypt rather than the opposite. (simply because we store sigs of verity stuff in separate...
huu? what? that means any process can reset any cgroups accounting? that sounds very wrong?
@hnaz heya, what's the thing here? is memory.peak safe to be opened up world-writable? can you explain what's going on here?
254 is too old to be tracked here. Please contact your downstream distro for help. and this is not a useful bug report, as you didn't include logs of the...
*[Canned reply follows]* This is the upstream bug and feature request tracker of systemd. Please use this only for issues in the two most current upstream systemd versions. See this...
> Actually we still do stable release updates for v254 hmm, can we *please* dial down the noise on this? this bug tracker becomes useless if it starts tracking issues...
hmm, huh. good question. I guess it would be best if we'd refuse booting if we can't acquire a trusted initrd either from the UKI or from an add-on. Otherwise...
so two strategies we could implement 1. in sd-stub: refuse booting of no embedded initrd is found and none in an add-on either 2. in sd-stub: uninstall the initrd LoadFile2...
yeah, i think option 1 is nicer. we should just detect that and politely refuse