Linux.co.nz and a Number Plate: Betting on the Future
Return to Part 0: Table of ContentsPrevious Article: Part 4, Ten Minutes to Technical Manager: The ICONZ Gamble
A Concise History of Linux: 1997-2002
Episode 5
Ten Thousand Dollars on a Credit Card
It was 2001. I was sitting at my desk at Telecom XTRA, scrolling through the NZLUG mailing list, the New Zealand Linux User Group, when a post caught my eye. Someone was auctioning a package: the linux.co.nz domain name, the 0800-4-LINUX toll-free phone number, and a personalised LINUX number plate. All three, sold together.
I wanted them immediately. Not because I had a business plan. Not because I had run a return-on-investment calculation. I wanted them because I was a Linux professional in New Zealand, and these three items together represented something no amount of technical competence alone could buy: instant recognition.
The auction had competition. A bidder called "bgates" kept pushing the price up. Whether this was someone genuinely interested or the seller running interference to inflate the bid, I never found out. It did not matter. I kept bidding. The price climbed past what felt reasonable, past what felt comfortable, all the way to $10,000. That was the exact limit on my credit card. I could not have bid one cent more.
I won. And that single purchase, made on borrowed money while the dot-com crash was still burning through the industry, has paid for itself many times over across twenty-five years of a career built on Linux.
The Dot-Com Crash and the Domain Land Grab
To understand why spending $10,000 on a domain, a phone number, and a number plate made sense in 2001, you need to understand what had just happened to the industry.
The dot-com bubble had inflated throughout the late 1990s. By March 2000, the NASDAQ had risen 400 percent from its 1995 levels [1]. Internet companies with no revenue and no business model had commanded billion-dollar valuations. Domain names had become speculative assets. Generic words like business.com were changing hands for enormous sums. The registrations that had once been simple administrative acts had become gold rush claims.
Then the crash came. Between March 2000 and October 2002, the NASDAQ lost nearly 78 percent of its value [1]. Companies vanished. Venture capital dried up. The speculators who had treated domains as lottery tickets discovered that a name without a business behind it was worthless.
But the crash did not make domains irrelevant. It did the opposite: it separated the strategic claims from the speculative ones. The companies and individuals who owned names connected to real work, real expertise, and real industries kept their value. The ones holding beachfront.com and pets.com did not.
In New Zealand, the internet had been growing fast. ICONZ, where I had spent the previous three years building infrastructure and leading technical teams, was part of an ecosystem of roughly 30 ISPs serving a rapidly expanding user base. Telecom's XTRA service, where I now worked as Security and General Systems Team Leader, was the country's most successful ISP brand. Linux was everywhere in the infrastructure, even if the marketing materials featured Windows and Solaris logos.
Red Hat had gone public in August 1999. Its shares, priced at $14, hit $50 on the first day of trading [2]. IBM had taken a minority equity stake and was committing to pre-install Red Hat on its server lines. Dell was factory-installing Linux on PowerEdge servers. The commercial legitimacy of Linux was no longer in question. Wall Street had noticed before the crash, and enterprise adoption continued right through it.
Why Namespace Matters
A domain name is not just a URL. A toll-free number is not just a phone line. A number plate is not just a piece of tin on a car. Together, they form a namespace: a coherent, recognisable identity that tells the world who you are and what you do before you have said a single word.
In 2001, I was a Linux professional working inside one of New Zealand's largest telecommunications companies. My day job involved managing security, system administration, and OS patching across XTRA's entire server base and network infrastructure. I was designing and deploying the first BigIP systems in New Zealand. I was leading a NOC team, running Checkpoint firewalls, managing budgets and a team of contractors and permanent staff.
None of that was visible to anyone outside Telecom.
linux.co.nz changed that equation instantly. When I contacted recruitment agents, they called back. When I pitched consulting work, prospective clients already knew what I did before the conversation started. The domain, the phone number, the plate: they were a portable, permanent signal of expertise that followed me regardless of which employer's badge I happened to be wearing.
The return on that $10,000 has been extraordinary. Consulting contracts that came directly or indirectly through the linux.co.nz identity. The role at Novell, where I became a Pre-Sales Specialist for Enterprise Linux across Australia and New Zealand, winning global awards and closing enterprise agreements with organisations across retail, government services, and telecommunications. Immediate callbacks from hiring managers and agents who recognised the name. The cumulative career value has been well over $2-3 million. Probably more.
I still have the LINUX number plate. It sits on my wall now, retired from active service. A second one lives at SUSE headquarters in Nuremberg, a gift I sent them during the years when Novell owned SUSE and I was their man in the field. It felt right for the plate to live where the distribution lived.
The Broader Domain Land Grab
My auction was a tiny data point in a much larger phenomenon. By 2000, domain name registration had gone from an administrative formality to a speculative industry. The number of registered .com domains had exploded from around 120,000 in 1995 to over 20 million by 2000 [3]. Country-code domains like .co.nz followed a similar trajectory at smaller scale.
The speculation was often absurd. Companies added ".com" to their names to inflate stock prices. Domains were hoarded by speculators who had no intention of building anything. The bubble rewarded positioning over substance, hype over engineering.
But buried inside the speculation was a legitimate insight: naming matters. In a networked world, the name you claim shapes the opportunities that find you. The companies and individuals who understood this and acted on it early, not as speculation but as strategic positioning, gained advantages that compounded over decades.
Red Hat understood this. Their IPO was not just a financial event. It was a naming event. "Red Hat" became synonymous with enterprise Linux, a brand position they defended for twenty years until IBM acquired them for $34 billion in 2019 [4]. The name was worth as much as the technology.
Linux itself understood this, in its accidental way. Linus Torvalds initially wanted to call his operating system "Freax." The FTP server administrator at the Helsinki University of Technology, Ari Lemmke, named the directory "linux" instead [5]. One naming decision by one sysadmin shaped the identity of an entire operating system that now runs on everything from smartphones to the International Space Station.
Linux's Commercial Legitimacy in 2001
The year I bought linux.co.nz was the year Linux crossed from commercial legitimacy into enterprise infrastructure.
Red Hat's IPO had been one signal. IBM's investment was another. But the real validation was quieter: enterprises were deploying Linux in production, not as experiments but as infrastructure. At XTRA, we had "small Linux pockets" running alongside Windows and Solaris, handling specific workloads where reliability and cost mattered more than vendor relationships. Across the industry, the pattern was the same. Linux was earning its place by being better at the job.
The kernel itself had matured. Linux 2.4, released in January 2001, added support for up to 64 GB of RAM, USB, and enterprise storage [6]. These were the capabilities that procurement teams needed to see before signing purchase orders. Linux 2.2, released two years earlier, had brought improved SMP support and better networking [6]. The trajectory was clear: each release closed another gap between Linux and the proprietary UNIX systems it was replacing.
For someone like me, working inside a major ISP and watching Linux grow from a server room tool to a boardroom conversation, the trajectory was unmistakable. Owning linux.co.nz was not a bet that Linux would succeed. It was an acknowledgement that it already had.
The Modern Bridge: Namespace Is Power
In 2026, the namespace question has scaled beyond domains and number plates. The contest now is over data, models, compute, and governance.
Sovereign AI has become one of the defining themes of the decade. By early 2026, more than 130 government-backed sovereign AI projects exist across over 50 countries [7]. The EU AI Act is reshaping how organisations deploy artificial intelligence within European borders. The question is no longer whether AI will be regulated, but who gets to define what sovereignty means in practice.
The parallel to 2001 is direct. In the domain land grab, the people who claimed their namespace early gained advantages that compounded for decades. In the AI era, the organisations and nations that control their data pipelines, their model training infrastructure, their compute capacity, and their governance frameworks will hold similar advantages. Those that lease everything from someone else's cloud, train on someone else's data, and deploy someone else's models will find themselves in the same position as the companies that never registered their own domain: dependent on infrastructure they do not control, paying rent on namespace that should have been theirs.
For technology leaders in Aotearoa New Zealand, this is not abstract. The decisions being made now about cloud sovereignty, data residency, and AI governance will determine whether New Zealand organisations own their technological future or rent it. The same instinct that made me bid $10,000 on a credit card in 2001, the conviction that owning your namespace matters more than the short-term cost, applies at national scale in 2026.
If you control your namespace, you control your future. If someone else controls it, they control you.
Your Early Bet
What early bet did you make on technology that others thought was premature, expensive, or unnecessary?
Did you register a domain before anyone understood why it mattered? Did you learn a skill, adopt a platform, or commit to a technology before it had mainstream validation?
The best technology investments are rarely obvious at the time. They look obvious only in hindsight, after the compounding has done its work. Share your early bet. Someone reading this might be standing at their own $10,000 moment right now, wondering whether to click "confirm bid."
Next week in Episode 6: "Forty-Seven Seconds of National Darkness"
The views expressed in this article are entirely my own, informed by more than 30 years of professional experience in architecture, security, and technology leadership in New Zealand. They do not represent the views of my employer, any government agency, or the New Zealand government. My commentary on legislation and policy is analytical, drawing on publicly available sources and my professional expertise in architecture, security, and AI governance. I follow the Public Service Commissioner's Code of Conduct for the Public Sector and social media guidance.
About the Author: Andreas Hamberger is a New Zealand-based enterprise architect and technology strategist. Over 30 years, he has moved from compiling kernels on a 486 to leading cloud, cyber, and AI transformation programmes across government, banking, transport, and aviation. He founded Yoper Linux, served as a technology specialist for Novell during the Linux Wars, and is the author of "Generative AI: Skynet or Heaven" and "Space Mafia." He can be reached at linux@linux.co.nz.
A Concise History of Linux chronicles the operating system that changed the world, and the lessons it holds for the AI era.
I acknowledge the role of AI tools, such as Sudowrite, Claude, Perplexity AI, DeepSeek AI, ChatGPT, Grok, Copilot, Openart and Gemini, which assisted in drafting, editing and reviewing. They accelerated the process, but the first draft, revisions, vision, voice and final decisions were mine alone.
References
[1] Wikipedia. (2026). Dot-com bubble. https://en.wikipedia.org/wiki/Dot-com_bubble
[2] FundingUniverse / Encyclopedia.com. (n.d.). Red Hat Inc. company history. See also: Wikipedia. (2026). Red Hat. https://en.wikipedia.org/wiki/Red_Hat
[3] Dynadot. (n.d.). History of domain names. https://www.dynadot.com/blog/history-of-domain-names
[4] Wikipedia. (2026). Red Hat. https://en.wikipedia.org/wiki/Red_Hat
[5] Torvalds, L. & Diamond, D. (2001). Just for Fun: The Story of an Accidental Revolutionary. HarperBusiness.
[6] Wikipedia. (2026). Linux kernel version history. https://en.wikipedia.org/wiki/Linux_kernel
[7] Lawfare / CNAS. (2026, February). The sovereignty gap in U.S. AI statecraft. https://www.lawfaremedia.org/article/the-sovereignty-gap-in-u.s.-ai-statecraft