Tetstack
what is happening with the code.
it was not suppose to go this far on the mutation.
❤1❤🔥1💘1
okay so / represents 63 which translates too 0xFF so what ever was being fed to the base64 decoder is the random offset 0xFF and not the real kernel sooo why is bzImage all 0xFF and also data-seabios.
Tetstack
okay so / represents 63 which translates too 0xFF so what ever was being fed to the base64 decoder is the random offset 0xFF and not the real kernel sooo why is bzImage all 0xFF and also data-seabios.
It was because the curl download, i used raw github and it redirected me to the html 404 and it downloaded the 404 and said it worked instead of the real kernel
Tetstack
Okay not an image problem, it's how the kernel is being embedded and parsed.
Oh yeah sorry I didn't explain this, so I am implementing a real working Linux inside my portfolio. Spolier: it's all inside a 22.8Mb html file .