For fun and profit: after spotting the words #lilo and #loadlin in a #Linux #kernel build config help text I had to check how often the #LinuxKernel sources still refer to themโฆ
[edit] Updated screenshot fixing a bug (missing a "-i" in the global search; sorry!) [/edit]
@kernellogger LILO - all I remember after some mistake in my lilo.conf is a bootscreen full of 010101010101010... that required a live-system to recover from, since there was no interactive LILO shell.
@eliasp @kernellogger probably LILILILI...
@ptesarik @kernellogger # CONFIG_MMU is not set
cc @ljs @vbabka
@ljs @kernellogger @lkundrak @vbabka And I was hoping to port Linux to MOS 6502 on day when I retire. Now, all hope is gone.
@ljs @kernellogger @lkundrak @vbabka I'd rather set CONFIG_SELF_IMMOLATE_AND_DISAPPEAR on myself in that case.
@gregkh @kernellogger @pinganini @jarkko yeah, if you're running a custom kernel build and don't need to manage any trust anchor for anything else, you can definitely just do this. Though it'd be nicer if you didn't have to build the initramfs /before/ the kernel.
@jarkko @kernellogger @pinganini @jarkko Yeah, nobody needs to know when their data is silently corrupted anyway. Better left a mystery. Or I guess use dm-integrity.