A Folder Name Became the Project’s Public Name
In the early days of sharing software over the internet, a file-transfer server was more than a back-end storage system: it was where people went to fetch a project. Its directory names served as labels for what they found. When the kernel’s files appeared in a directory called Linux, that practical label was easier for visitors to use and repeat than “Freax.”
The name therefore spread through a mundane act of publishing, not a formal naming ceremony. People who downloaded the files encountered “Linux” as the project’s address and began using it for the software itself. A server administrator’s decision could shape how the work was discovered—and what it was called.
Why the Rename Stuck
A directory name is easy to change, but a name repeated across downloads, conversations, and later software packages becomes harder to replace. As the kernel circulated under “Linux,” the label attached itself to the growing project. The episode shows how, in collaborative software, public names can emerge from the tools and habits of distribution as much as from a creator’s original plan.
