This evening I'm on an odd historical sojourn into the history of the tar format (thanks, @thTrammell Hudson, for inadvertently nerd-sniping me).

The problem is, this involves reading old C code, because SeLf DoCuMeNtInG or whatever. And I can't not see ghosts in C code anymore.

Anyway, guess how many things enshrined in later standards (like POSIX) are a product of what appear to be coding mistakes, including buffer overruns and use of uninitialized stack memory, in the V7 Unix tar implementation?

As an industry, we've _never_ been able to hold this tool (C) correctly.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://hachyderm.io/users/cliffle/statuses/115415059671486164 on your instance and quote it. (Note that quoting is not supported in Mastodon.)