An interesting question, and a detailed technical rundown of how to make this happen, which involved building a custom Linux kernel, of course.
I really, really enjoy the conclusion.
And you know? It turned out fine. Nothing exploded on my system. As I could predict, because this was otherwise impossible, nobody did it. The signal system was setup in such a way that you would most likely realize something you were doing was wrong, and not try it.
To pull back further, it is interesting to notice how the rules we all take for granted are just set somewhere in code. They were written by someone, at some point. If there is code restricting you from doing something, someone wrote it. Either they did not think anyone would want to do that thing, or they specifically prevented you from doing it. Those rules are written somewhere, and you can take it in your paws to go sniff around the code, pull out the relevant parts, and hack around the things that bother you. For fun, learning, or convenience.
Snoop around. Sniff code. Put your paws in it. Hack shit.
↫ lux at VulpineCitrus
Even if there’s no real reason to do, even if it’s just to satiate an odd and possibly slightly morbid sense of curiosity, fuck with code.
