<stikonas>fossy: so I've now got chroot mode working with significantly smaller rootfs.py script. But for some reason I'm hitting issues with qemu mode (out of space) ***Noisytoot_ is now known as Noisytoot
<fossy>stikonas[m]: thank you for that work it is looking good <fossy>i have just caught up on what is going on <fossy>a lot of chatter round here! <fossy>stikonas[m]: where does it hit out of space in qemu? what bit are you doing now to make rootfs.py smaller? <fossy>i have almost finished merging src/ directories into the one sources/ directory <fossy>mid-kid: quick rationale behind 4.9 kernel, GCC/binutils/make combo cannot build anything newer than that. You can hypothetically modify the build to use the current kernel, but I would strongly discourage you from doing so unless you need a newer feature <fossy>i can't really think of any mainstream newer features, apart from maybe architecture support? but that's pretty irrelevant right now (only x86 supported). 4.9 is still an LTS kernel but newer 4.9.xs don't work (i never found the exact version just settled on .10 because that worked and like .50 didn't and i didn't care to bisect) <stikonas[m]>I'll try to save some space by using bz2 instead of gzip for your packages <mid-kid>fossy: I have at least one laptop that won't boot with anything older than 5.0 <mid-kid>And I wouldn't have done it very differently <mid-kid>It's to bootstrap from a hypothetical minimal kernel into a proper linux kernel for a certain machine. <mid-kid>However, I was already using a newer kernel to get the initramfs to boot at all, so my pondering was mostly as to how to just keep running the same kernel instead of having to essentially downgrade to a kernel config of which idk if it'd even work. <dongcarl>oriansj: Wait what? People sent you death threats? <dongcarl>I'm sorry to hear that. My intention was only to bring attention to this important work. I hope you're alright. <stikonas>mid-kid: and what happens if you try to boot older kernel? <stikonas>but in any case we don't have many options, it's either backporting hw support to older kernel, switching to different hardware or try to upgrade early toolchain in live-bootstrap ***robin_ is now known as robin