Ubuntu 4.10: How One CD Lowered the Threshold to Linux

On October 20, 2004, Ubuntu’s first release offered a practical invitation: a selected desktop, a predictable update rhythm and a CD you could give a friend. Twenty-two years later, Warty Warthog’s most interesting achievement is how those pieces fitted together.

A software project can be publicly available and still feel out of reach. Before using it, a newcomer must find the files, choose the right components, understand the installation and decide where help will come from. Ubuntu 4.10 addressed that whole journey. Its story is about turning the enormous possibilities of free software into a manageable first encounter.

The anniversary in the Nerd Calendar marks the first stable Ubuntu release. Looking closely at the surviving documents also reveals a useful complication: the installation release and the final companion Live CD did not arrive on the same day.

What was new about Ubuntu’s invitation?

Mark Shuttleworth’s October 20 release announcement introduced Warty Warthog as a Debian-based distribution with selected default applications, six-month releases and an 18-month support commitment. GNOME 2.8, Firefox 0.9 with security patches, Evolution 2.0 and OpenOffice.org 1.1.2 supplied a concrete desktop rather than an empty starting point.

The name can be misleading: 4.10 really was Ubuntu’s first release. Ubuntu’s version numbers follow the release year and month: 4 means 2004, and 10 means October.

Those version numbers are useful historical coordinates, but the larger design choice was curation. Someone had made an initial set of decisions on the user’s behalf. A beginner could start with an agreed collection and learn what to change later. This is our reading of the product design, rather than a claim that every installation suddenly became effortless.

Good defaults create a shared reference. If two friends begin with similar software, one can explain where to find a tool without first reconstructing the other person’s entire setup. Choice remains available, but it no longer has to precede every useful action.

Debian supplied the foundation; Ubuntu chose a route

The contemporary Warty installation manual’s Debian chapter explains the relationship directly. Ubuntu drew on Debian’s development archive while making its own release decisions. It distinguished a supported selection of packages from the wider universe component, and described developers sending applicable fixes back to Debian.

That makes the debut more interesting than a simple story of replacement. Ubuntu relied on an existing ecosystem and offered a particular path through it. Packaging, integration and maintenance mattered alongside the individual programs. The collection needed to behave like a system a stranger could approach.

NerdSpot’s article on the first Linux source release in 1991 examines a different threshold: making an unfinished kernel available to read. Ubuntu’s 2004 question came later in the chain. How do you turn the work of many projects into a starting environment for someone who wants to use a computer?

A release schedule is part of the experience

A visible release rhythm answers questions that a list of features cannot. When should users expect another version? What does the project promise to maintain? When does an exciting snapshot become something a school or household can plan around?

Ubuntu’s six-month cadence and stated support window gave the first release a future tense. The announcement was also a commitment to return. That does not prove every later deadline or hardware combination would work perfectly; it explains why a schedule belongs in the product story.

Keep the original promise separate from later arrangements. Ubuntu’s official project history places the decision to introduce long-term support releases in 2006. Warty was not launched as an LTS release. Reading today’s terminology backwards would hide how the maintenance model developed.

The CD was a way to share an introduction

The October 13 release-candidate announcement already invited people to register for complimentary final-release CDs, including copies for friends, schools and Linux user groups. The documented offer matters more than trying to infer a particular recipient’s delivery date. An announcement about ordering is not proof that a parcel arrived that week.

A physical disc changed the social shape of discovery. It could be carried to someone else’s room, passed across a desk or used as the starting point for a conversation. The person offering it could also stay and help. In that situation, distribution includes both an object and an explanation.

This is an interpretation of what the medium enabled, not a measured account of every Ubuntu user’s experience. Still, it shows why the CD belongs in the history. Permission to share software becomes easier to understand when there is something ordinary you can actually hand over.

October 20 and October 27 are different milestones

The October 20 announcement pointed to the install CD and a release-candidate Live CD. On October 27, LaMont Jones announced the final companion Warty Live CD. That disc offered a bootable trial without repartitioning or replacing existing data and was available for i386-compatible processors.

The distinction prevents a familiar retrospective shortcut: imagining the modern combined “try or install” experience already complete on launch day. There were previews and release candidates, then a stable installation release, then the final companion trial disc. Each artefact answered a different question.

Trying a system before committing to an installation lowers a different barrier from making the installer easier. One addresses uncertainty about the unfamiliar environment; the other addresses the work of putting it on the machine. Treating them separately makes the design easier to appreciate.

What Warty still teaches about welcoming users

The useful birthday exercise is to read the old announcements as a newcomer’s journey. Identify the starting tools, the route to obtaining them, the maintenance promise and the way to ask for help. Then ask which decisions the project has already made and which it still leaves to you.

That approach also helps when reading Android’s several launch milestones: a platform’s announcement, available software and encounter with an actual user are separate events. A clean anniversary date is a signpost into the story, not the whole story.

Ubuntu 4.10 did not invent Linux or erase the difficulties of desktop computing. Its distinctive invitation combined a selected starting point, a repeatable rhythm and an explicit route for sharing. On its 22nd anniversary, that is the enduring lesson: access improves when the next step becomes concrete enough to take—and simple enough to explain to a friend.