June 23, 2026
Small file, big feelings
The Teensy Executable Revisited
Tiny file, huge nerd fight: fans gasp at the sequel and the rules-lawyering showdown
TLDR: A programmer revisited a famous stunt to make a ridiculously tiny Linux app while following the official rules more closely. In the comments, fans were split between sequel hype, standards-lawyer nitpicks, and serious “well actually” debate over how much rule-bending should count.
A cult favorite from the weird corner of programming just got a dramatic comeback, and yes, the comment section is absolutely eating it up. The article revisits a famous stunt: making a Linux program so absurdly small it barely feels real. The author admits the earlier version bent the rules so hard that some readers basically cried, “That doesn’t count!” Their complaint was simple: sure, Linux would run it, but was it really a proper executable file, or just a loophole in a trench coat? In this sequel, the author returns to please the purists by trying to keep the file tiny without cheating the official rulebook.
That setup alone sparked the classic internet split between spec worshippers and practical hackers. One side loves the stunt and the playful rebellion: if the computer accepts it, who cares? The other side wants receipts, standards, and moral cleanliness. The funniest energy in the comments, though, is pure delighted chaos. One reader popped in like a fan discovering a surprise post-credits scene: they didn’t even know there was a sequel, then immediately dropped a link to an even wilder part 3. Another commenter served a deadpan correction about Linux system calls being stable, which is the kind of ultra-serious nerd note that somehow makes the whole thing funnier. It’s less “small file news” and more fandom drama for people who argue with manuals for sport.
Key Points
- •The article responds to criticism that the earlier 45-byte file was not fully compliant with the ELF specification.
- •It reintroduces a 91-byte 32-bit ELF executable as the compliant baseline before later size reductions.
- •The baseline example includes explicit `Elf32_Ehdr` and `Elf32_Phdr` definitions and a small code section ending with `int 0x80`.
- •The author states that previous noncompliance began when unused ELF header fields were repurposed.
- •The article says the ELF specification permits overlap between different file data structures, enabling the ELF header and program header table to overlap by eight bytes.