Why does txt2bin exist?

One night, I was thinking about those old DOS programs that embedded a plain text file in an executable and let you view it just by running the .EXE (readme.exe). They were helpful for the uninitiated.

Some were quite full-featured but I always much preferred using Vernon D. Buerg's list.com.

It struck me: what if I made something like that for Linux - but comically simple? Surely it wouldn't be well-received. For a lot of reasons but mostly because of the implementation I had in mind.

Finding humor about a possible backlash (or more likely a collective shrug), a new short story was born!

The Council of Linux Greybeards

I didn't actually have a "text to self-displaying binary" to serve as the story's cursed artifact. So, while writing, I put together a little script that does exactly one thing: uses printf to send the text to stdout.

Its sole reason for existing is to be the tool that horrifies my "fictional" Greybeards - a prop for a story I had way too much fun (re)writing over ~three days.

note: the txt2bin script actually works well for its intended use (converts text to .C and compiles with musl-gcc with error-checking). Works best for text and/or ASCII Art that's the size of the terminal screen (I like 80x25).

License: CC BY-NC-SA 4.0
attribution: 640kb.neocities.org
Date: 14 dec 2025 (initial upload)
Date: 03 may 2026 (minor edits)