Back

@pikesley @Salty @mavica_again @esm

"Borp: our incredible journey". Coming soon to Poob.

@w8emv @pikesley @Salty @mavica_again @esm

I wouldn't be seen dead paying for borp. All you do, right, literally all you do, it's really simple, right? You start by installing Arch. Then you patch libmavis.so.1 to patch around the call to zebble — not the first call, obviously, that checks for grob, but the second call that checks for binjun. You patch around that using a seven-byte NOP — or a five-byte NOP on x86 or an eight-byte NOP on ARM, but you knew that already — you can find the address by tracing through it at assembly level in gdb, it's trivial, a child could do it. Obviously, since you haven't initted binjun, cerise bevel won't load, so you'll need to write a short awk script to mock that up and handle bevel --awooga and then stick that in your path, obviously, before nigel. Owing to a race condition, you can't edit your path before libmavis is loaded or the thripple clanger will segfault and take out runible, so just patch the environment in memory using gdb again, see? You're already in gdb, so it couldn't be easier.

After that, it's mostly plain sailing, unless I've forgotten something. Just follow your nose and, if anything's not clear, log on to our discord from any BSD system with a reverse rsync pipe capability and specify the password. The password? No, I'm not going to specify on Fedi, of course I'm not. Don't want the rabble pouring in! Just wire up a quick FPGA-based system and write some VHDL to brute it. You can't go wrong.

It beats paying ten dollars a month, doesn't it? Eh?