Just Put It on Novell's Tab: The Night I Bought Linus Torvalds Drinks

  • Word count: ~2,050 (within narrative series 1,800-2,100 range)
  • PSC risk: Very Low
  • Primary source type: Personal memoir (D7 flags resolved via author confirmation 19 April 2026)
  • Government sources: None
  • NTP claim scan: All e-type claims sourced (LCA founding via linux.org.au; Novell/SUSE via public record; Open Source Pledge via frontendmasters.com; 75% stat via daily.dev). Personal testimony confirmed by author 19 April 2026. No unverified entities presented as real without qualification.

Return to Episode 12: Yoper and the Fastest Desktop: When NZ Topped DistroWatch

I sent the text just after midnight.

My manager was asleep in Auckland. I was standing somewhere near the bar at a venue on the UNSW Kensington campus in Sydney, where LinuxConf Australia 2007 had been running since 15 January, and something had just happened that I was not entirely sure how to explain.

The Google tab had run dry earlier in the evening. The Red Hat tab had followed. Several hundred of the most technically credentialed Linux people on the planet were in that room, and the evening showed no sign of ending. Then Linus Torvalds looked around, assessed the situation with the same pragmatic efficiency he applied to kernel patches, and gestured toward the bar.

"Just put it on Novell's tab."

I typed: you are about to receive a bar bill. It may be in the vicinity of $10,000. I apologise in advance.

The reply came the next morning.

"OK :-) All good, records are there to be broken."

That smiley face is one of the most consequential pieces of punctuation in my career.


The Conference at the End of the War

LinuxConf Australia 2007 was not a routine technology conference.

By January of that year, the community had been through four years of legal siege. SCO had filed suit in March 2003, claiming Unix code ownership inside the Linux kernel and threatening enterprise customers who deployed it. Novell had acquired SUSE in November 2003 for $210 million, in part to assert countervailing Unix copyright claims and give enterprise customers legal cover to keep running Linux in their data centres. That had been Episode 11's story: the legal argument, the indemnification, the assertion that Novell was on the community's side through courts, not just press releases. IBM had entered the fight. The case was grinding toward resolution. But the deeper question had not been answered: could commercial interests and the Bazaar coexist without one eventually consuming the other?

The answer, if there was going to be one, was going to come from the people in that room.

LinuxConf Australia had been running since 1999, founded by kernel hacker Rusty Russell using his personal credit card at Monash University. It moved cities each year, sustained entirely by volunteer organisers and community sponsorship. It attracted kernel developers, distribution maintainers, security researchers, and the project leads who kept the Bazaar running. Linus came. The people who maintained the code that ran the world's servers came. For five days in late January, the Asia-Pacific became the centre of the Linux universe.

Novell was there, as were Google, Red Hat, IBM, and a dozen other companies who had decided that showing up mattered. Not with booths and banners. With people: engineers, developers, pre-sales specialists who could hold technical conversations at the level the room demanded.

I was one of those people. Pre-Sales Specialist for Novell ANZ, selling SUSE Linux Enterprise Server across Australia and New Zealand. Also the founder of a distribution that, the previous year, had reached number one on DistroWatch from a cave under an Auckland bungalow.

Those two facts were about to intersect in a way I had not anticipated.


The Introduction

The conversation with Linus did not happen by accident. Crispin Cowan introduced us.

Crispin was the inventor of AppArmor, the Linux security framework that would eventually ship with every major enterprise distribution. He understood exactly who should be talking to whom in a room full of kernel developers, and his introduction was brief and precise.

"The fastest desktop from scratch."

That was how he described Yoper to Linus. It was accurate. The distribution I had built on evenings and weekends in the basement of an Auckland house had been optimised from the ground up for desktop performance on commodity hardware. Speed was the entire point. Crispin had understood that, and Linus, it turned out, had heard of it.

Not in passing. The conversation that followed went into the architecture: the compile-time optimisation choices, the trade-offs between desktop responsiveness and server workload profiles, the decisions that made Yoper fast and what they cost in other dimensions. This was technical engagement at the level the Bazaar reserved for things it had actually considered.

I had spent the better part of a year building that distribution. Tobias Gerschner had carried it forward when I could no longer give it the focus it deserved. The Yoper number-one ranking on DistroWatch had been the community's signal. And now the person who had started all of this, the person whose 1991 Usenet post had made every line of code that followed possible, was engaging with the technical choices as if they mattered.

They did matter. Finding out that he knew it mattered.

That is what giving your career genuine meaning looks like when you are standing in the middle of it. It does not feel like a milestone. It feels like the Bazaar confirming, in person, that it has been paying attention.

By the time Linus said "just put it on Novell's tab," we had been talking for some time.


The Bar Tab as Business Model

The bill arrived the following morning.

There was no friction. My manager laughed and replied with a smiley face: all good, records are there to be broken.

I want to be precise about what that reply represented.

That year, I had brought Novell $15 million in new revenue across ANZ. The bar bill was, proportionally, a rounding error, and my manager knew it. The reply was not managerial equanimity in the face of an awkward expense. It was the ROI calculation delivered in a single line of text.

Novell had spent months making the legal argument that it was on the community's side: asserting Unix copyright ownership, indemnifying enterprise customers, making it commercially safe to keep deploying Linux in data centres. That was Episode 11's story. It had spent years making the technical argument through SUSE's engineering. That was Episode 10's story. The bar tab was something different: a signal, entirely spontaneous and unrehearsed, that when Linus Torvalds needed someone to cover a round, Novell was the company in the room.

You cannot buy that position. You can only put yourself in a position where it happens.

Google and Red Hat running tabs at the same event was not coincidence. It was competitive acknowledgement that the community's trust was worth funding. You do not earn it by announcing your Linux credentials in a press release. You earn it by sending people who can hold their own in a room full of kernel developers, and by covering the bill when the formal tabs run dry.

The reply from Auckland was my manager confirming he understood what Novell was actually buying. Not the drinks. The position.

Novell's investment in the Linux community was not separate from its commercial interest: it was the instrument of that interest. Community legitimacy and commercial success ran on the same rails. The bar tab was the clearest possible expression of that.


The Community Investment Equation in 2026

In 2007, corporate investment in open-source community gatherings was largely informal. Companies funded conference sponsorships, covered travel for key engineers, and showed up at dinners with expense accounts because someone had worked out that the community mattered to their business.

By 2026, the same logic has been codified into structures with names and minimum standards.

The Open Source Pledge, backed by over 40 companies, sets a minimum contribution level: $2,000 per developer per year directed to open-source maintainers. GitHub Sponsors has processed millions of dollars in community investment that would previously have been invisible. The Linux Foundation's corporate membership tiers connect annual contributions to governance participation across dozens of critical infrastructure projects. According to research from daily.dev published in December 2025, corporate sponsorships of open-source projects increased 75% in 2024 alone.

The mechanism is identical to what Novell was running in January 2007. The formalisation is new. What drove it was not altruism: it was the same ROI calculation my manager made in seconds. Community legitimacy is a business asset. It does not appear on a balance sheet, but it determines whether the Bazaar treats your organisation as a participant or a parasite.

The AI labs are now running the same calculation, with higher stakes and less consensus on how to get it right. The companies funding developer conferences, contributing to open-source tooling, and putting engineers into the rooms where the AI community gathers understand what Novell understood: community trust is earned from inside the Bazaar, not purchased at the perimeter. The ones issuing "open source commitment" press releases are running a strategy the Linux community saw through twenty years ago.

The Bazaar can tell the difference between presence and participation. It always could.

The bar tab teaches this more effectively than any governance white paper.


What Stayed

There is a photograph from that evening. I am wearing a Linux Iron Man t-shirt and an orange LCA lanyard. Linus is in a dark shirt and khakis, and we are both smiling. The venue is somewhere behind us: palm plants and a covered atrium, the kind of tropical indoor space that makes Sydney in January feel like a reward.

I have thought about that evening a great deal in the years since. Not because it was the high point of my Novell career, or because Linus Torvalds is famous. Because of what it confirmed: the work done in a cave under an Auckland house, on evenings and weekends, funded by nothing more than the conviction that desktop Linux deserved to run fast, had been noticed by the person who started all of this.

The Bazaar is a meritocracy. Not a pure one, not an uncomplicated one, but one that pays attention to code and community in ways that corporate hierarchies do not always manage. The Yoper number-one ranking on DistroWatch was the community's signal. The night at LinuxConf was Linus's.

Both said the same thing: the Bazaar had looked at something built in New Zealand and said yes, that.

I have been trying to build things worthy of that response ever since.


Next episode: Android: The Kernel That Conquered Four Billion Pockets


Have you met your technical heroes? And when you found yourself in the same room as the people who shaped the tools you built on, what did that moment actually mean?


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 use AI tools, including Sudowrite, Claude, Perplexity AI, DeepSeek AI, ChatGPT, Grok, Copilot, Openart and Gemini, as deliberate production tools, not ghostwriters. This is consistent with my position: AI amplifies human judgement; it does not replace it. The frameworks, arguments, and editorial decisions in this series are original work. AI accelerated the process. The thinking is mine.


[1] linux.org.au. "Linux.conf.au History." Accessed April 2026. https://linux.org.au/linux-conf-au/

[2] linux.com. "Fun and Sun Down Under: Day One, LinuxConf.au." 16 January 2007. https://linux.com/news/fun-and-sun-down-under-day-one-linuxconfau/

[3] SUSE. "Novell Completes Acquisition of SUSE LINUX." November 2003. Public record.

[4] daily.dev. "The Complete Guide for Developer-Focused Sponsorships in 2025." December 2025. https://daily.dev/blog/the-complete-guide-for-developer-focused-sponsorships-in-2025

[5] Frontend Masters Blog. "Supporting Open Source in 2026." 2026. https://frontendmasters.com/blog/supporting-open-source-in-2026

Previous
Previous

Stability Is the Feature: What Linux 7.0 Is Actually Optimising For

Next
Next

Android: The Kernel That Conquered Four Billion Pockets