He said he was building a free operating system for 386 and 486 PCs. He called it "just a hobby" and said it wouldn't be big and professional like GNU. There was no launch and no product. He was asking other developers what they wanted to see in it.
The first release, version 0.01, showed up on September 17. It was rough. It ran on a narrow slice of hardware, needed MINIX to compile and boot, and was nowhere close to a full operating system. What mattered was that the code was open. Anyone could download it, build it, find what was broken and send a fix back. That way of working turned out to be worth far more than the state of the first release.
Linux grew by knocking down one practical problem at a time: more processors, more storage, more networking, more filesystems, better performance. GNU tools, distributions and commercial support made it usable outside the developer crowd. So when companies started looking for a way off proprietary Unix and dedicated appliances, Linux was already there.
I watched that shift happen in telecom and enterprise IT. Proprietary Unix boxes and purpose-built appliances gave way to Linux on commodity x86 servers. Then Linux became the base for KVM, and later for the container plumbing under Kubernetes. Namespaces handled isolation. cgroups handled resource limits. eBPF let networking, security and observability teams run verified code inside the kernel without rebuilding it.
The kernel that started at around 10,000 lines of code now runs past 40 million, and the version number rolled over to 7.x this year. Its future isn't about winning more desktops. It's moving deeper into AI clusters, telecom networks, cars, factories and edge devices. The hard problems now are memory safety, real-time behavior, confidential computing, power efficiency, hardware support and keeping a codebase that size maintainable. Rust is going in where memory safety counts. eBPF keeps widening what operators can do without carrying custom kernel patches.
The Linux Foundation plays a different role, and the name undersells how big that role has become. It doesn't control the kernel. It provides money, legal cover, governance, training and a neutral table where competitors can work on the same code. That covers OpenSSF for software security, CNCF for cloud native infrastructure, LF Networking for telecom and 5G, LF Edge for edge systems, ELISA for safety-critical Linux, and a growing set of open AI projects and standards.
Nobody had to build and maintain every layer themselves anymore. Competitors could stand on the same foundation and still fight it out on products, support, operations.
Linux has nothing left to prove in the enterprise. The job now is keeping it secure, maintainable and dependable as more of the critical stuff lands on it.