The original article is extremely clear on this fact. The title: > A Whirlwind Tutorial on Creating Really Teensy ELF Executables for Linux as opposed to ELF

The original article is extremely clear on this fact. The title: > A Whirlwind Tutorial on Creating Really Teensy ELF Executables for Linux as opposed to ELF Executables for non-Linux systems, or a.out executables for Linux. In the middle of the article, when the illegal shenanigans start: > Unless, that is, we could change the contents of the structures to make them match even further.... > How many of these fields is Linux actually looking at, anyway? For example, does Linux actually check to see if the e_machine field contains 3 (indicating an Intel 386 target), or is it just assuming that it does? At the end of the article: > Of course, half of the values in this file violate some part of the ELF standard, and it's a wonder that Linux will even consent to sneeze on it, much less give it a process ID. This is not the sort of program to which one would normally be willing to confess authorship. I don't see how the author could possibly be any clearer that this is Linux-specific and will probably not work (unmodified) on non-Linux systems.