IRC channel logs
2023-12-24.log
back to list of logs
<stikonas>and now I need to fix uefi stack alignment in M2libc ... <stikonas>with these M2libc I can go all the way to final checksums... <stikonas>hmm, /steps//1.sh: line 34: /dev/null: error 13 shouldn't be there... <stikonas>maybe you missed somethign rootfs does... <oriansj>well I didn't need the distinct 16bit unsigned values when doing cc_* and once we had that, mescc-tools didn't need it to be bootstrapped <oriansj>so yeah, M0 is missing a few things and a good bit slower than it needs to be <fossy>wth, that asset url thing is a bit stupid... <oriansj>fossy: you know all of the forks share the same back end as the original right? <oriansj>which means hash collision attacks can be done without needing any access to the master repo <fossy>oriansj: yeah i know that, github's url security is fairly poor :\ <stikonas>so right now I'm using @ which works with M0 <stikonas>but of course that file would know fail with M1 (@ fill fail range check) <stikonas>so our options are 1) keep it as it is now, just M0 compatible. 2) extend M0.efi <stikonas>argh, again forgot that M2-Planet makes 32-bit constants negative...