Sign In

Communications of the ACM

Kode Vicious

GNL Is Not Linux

GNL Is Not Linux, illustration

Credit: Andrij Borys Associates

back to top  Dear KV,

I keep seeing the terms "Linux" and "GNU/Linux" online when I am reading about open source software. The terms seem to be mixed up or confused a lot and generate a lot of angry mail and forum threads. When I use a Linux distro am I using Linux or GNU? Does it matter?

What's in a Name?

Back to Top

Dear Name,

What, indeed, is in a name? As you have already seen, this quasi-technical topic continues to cause a bit of heat in the software community, particularly in the open source world. You can find the narrative from the GNU side by utilizing the link provided in the postscript appearing at the end of this column, but KV finds that narrative lacking, and so, against my better judgment about pigs and dancing, I will weigh in with a few comments.

If you want the real back story on the GNU folks and FSF (Free Software Foundation), let me suggest you read Steven Levy's Hackers: Heroes of the Computer Revolution, which is still my favorite book about that period in the history of computing, covering the rise of the minicomputer in the 1960s through the rise of the early microcomputers in the 1970s and early 1980s. Before we get to the modern day and answer your question, however, we have to step back in time to the late 1960s, and the advent of the minicomputer.

Once upon a time, as all good stories start, nearly all computer software cost some amount of money and was licensed to various entities for use. That time was the 1950s and 1960s, when, in reality, very few individuals could afford a computer, and, in fact, the idea that anyone would want one was scoffed at by the companies who made them, to their later detriment. Software was developed either by the hardware manufacturer to make its very expensive machines even moderately usable, or by the government, often in collaboration with universities.

About the time of the advent of the minicomputer—which came along about the same time KV was born, screaming, because he knew he would have to fix them and their brethren someday—two key innovations occurred. Ken Thompson and Dennis Ritchie invented Unix, a now well-known reaction to the development of Multics, and computer hardware took one of its first steps toward affordability. No longer would the whole university have to share and time-slice a single large mainframe; now each department, if that department had $30,000 or so, could share a less powerful machine, but among a much smaller group of people.

Before Unix, operating systems were large, complicated, and mostly nonportable. Because Unix was simple and written in a new, portable assembler— which we now call C—it was possible for much smaller groups of people to write significant software with a lot less effort. There were good tools for writing portable operating systems and systems software, including a compiler, linker, assembler, and debugger—tools we now take for granted. All of these advances were significant and important, but they had one thing holding them back from even broader acceptance: licensing.

The Unix system and its tools were written and owned by AT&T, which, at that time, was the largest monopoly in the U.S. It did not have to license anything, of course, because it was the phone company, and the only phone company, which put it in a unique position, best summed up by Lily Tomlin in an old comedy sketch: "We don't care, we don't have to."

The truth was many people inside AT&T did care and they were able to get AT&T to sell "cheap" licenses for institutions such as universities that had to pay only $1,000 to get the entire source. Companies had to pay quite a bit more, but they were able to spread the cost over their entire computing infrastructure. Having the source meant you could update and modify the operating system. If you want to see innovation in any type of software, it is very important to have the source. In 2016, more than 50 years after all these changes started, it is now common to have access to the source, because of the open source movement, but this was uncommon at the start of the Unix age.

Over the course of the Unix era, several open source operating systems came to the fore. One was BSD (Berkeley Software Distribution), built by CSRG (Computer Software Research Group) at UC Berkeley. The Berkeley group had started out as a licensee of the AT&T source, and had, early on, written new tools for AT&T's version of Unix. Over time, CSRG began to swap out parts of the system in favor of its own pieces, notably the file system and virtual memory, and was the first to add the TCP/IP protocols, giving the world the first Internet (really DARPAnet)-capable Unix system.

At about the same time, FSF had, supposedly, been developing its own operating system (Hurd), as well as a C compiler, linker, assembler, debugger, and editor. The effort to build tools worked out better for FSF than its effort to build an operating system, and, in fact, I have never seen a running version of Hurd, though I suspect this column will generate an email message or two pointing to a sad set of neglected files. The GNU tools were, in a way, an advancement, because now software developers could have an open source set of tools with which to build both new tools and systems. I say, "in a way," because these tools came with two significant downsides. To understand the first downside, you should find a friend who works on compilers and ask if he or she has ever looked inside gcc (GNU C compiler), and, after the crying stops and you have bolstered your friend's spirits, ask if he or she has ever tried to extend the compiler. If you are still friends at that point, your final question should be about submitting patches upstream into this supposedly open source project.

The second downside was religious: the GPL (GNU Public License). If you read Hackers, it becomes quite obvious why FSF created the GPL, and the copyleft before it. The people who created FSF felt cheated when others took the software they had worked on—and which was developed under various government grants—started companies, and tried to make money with it. The open source community is very clearly split over the purity of what one develops. There are those who believe no one should be able to charge for software or to close it off from others, and those who want to share their knowledge, whether or not the receiver of that knowledge makes a buck with it.

All of this background brings us to Linux and its relationship to the GNU tools. Linux is an operating system kernel, initially developed by Linus Torvalds in reaction to the Minix operating system from Andrew Tanenbaum. Torvalds used the GNU tools—compiler, linker, assembler—to turn his C code into an operating system kernel and then launched it upon the world. He released the code under a GPLv2 license— the one it maintains to this day—rather than taking on GPLv3, which is even more restrictive than its predecessors. Other people took up the code, modified it, improved it, and built new tools and systems around it.

Now, to the point about naming. When you build a house, you use many tools: hammers, saws, drills, and so forth. When the house is complete, do you call that a Craftsman/House, a Makita/House, or a Home Depot/House? Of course you don't. We do not name things after the tools we use to build them; we name things in ways that make sense because they describe the whole of the thing clearly and completely. Linux is an operating system kernel and some associated libraries that present a mostly, but not always, Posix, Unixlike system on top of which people write software. In point of fact, Linux distributions do not ship with the GNU tools, which must be installed from packages later. Linux is a thing unto itself, and the GNU tools are things unto themselves. That one might be used to work on the other is irrelevant, as is the fact that I am holding a Craftsman hammer from Home Depot right now ... must put the hammer down.

The whole GNU/Linux naming silliness is probably a case of kernel envy, not unlike the programmers who feel their ultimate achievement is to write a process or thread scheduler, which I addressed in my February 2014 column "Bugs and Bragging Rights" (, where I wrote, "I think the propensity for programmers to label their larger creations as operating systems comes from the need to secure bragging rights. Programmers never stop comparing their code with the code of their peers."

Why is this important? There are two reasons. One is intellectual honesty. KV prefers to see the credit go to those who did the work. Linus Torvalds and his team have built an important artifact, out of many tools, that many people use each day, so the credit goes to them, not to the producers of the tools. It takes more than a compiler, linker, and editor to build something as complex as an operating system, or even the operating system kernel, and many of the tools that go into building Linux have nothing at all to do with FSF or GNU. Should we now rename all of our systems as GNU/APACHE/FOO/BAR? Only a lawyer would think of that, and by now you all know what I think of letting lawyers name projects. The second reason this is important is to point out that while GNU stands for "GNU is not Unix," that was a reaction against the AT&T Unix of the 1980s. Now it might as well be "GNU is not Linux," because the tool is not the thing the tool builds. But then, GNL doesn't sound as good.

Back to Top


P.S. If you want to read the GNU side of this story, pour yourself a strong beverage and start here:

q stamp of ACM QueueRelated articles

Open Source to the Core
John Hubbard

A License to Kode
George Neville-Neil

Desktop Linux: Where Art Thou?
Bart Decrem

Back to Top


George V. Neville-Neil ( is the proprietor of Neville-Neil Consulting and co-chair of the ACM Queue editorial board. He works on networking and operating systems code for fun and profit, teaches courses on various programming-related subjects, and encourages your comments, quips, and code snips pertaining to his Communications column

Copyright held by author.

The Digital Library is published by the Association for Computing Machinery. Copyright © 2016 ACM, Inc.


CACM Administrator

The following letter was published in the Letters to the Editor of the June 2016 CACM (
--CACM Administrator

George V. Neville-Neil's Kode Vicious column "GNL Is Not Linux" (Apr. 2016) would have been better if it had ended with the opening paragraph. Instead Neville-Neil recapped yet again the history of Unix and Linux, then went off the rails, hinting, darkly, at ulterior motives behind GPL, particularly that it is anti-commercial. Red Hat's billions in revenue ($1.79 billion in 2015) should put such an assertion to rest. The Free Software Foundation apparently has no problem with individuals or companies making money from free software.

We do not call houses by the tools we use to build them, as in, say, "... a Craftsman/House, a Makita/House, or a Home Depot/House ..." in Neville-Neil's example. But we do call a house made of bricks a brick house in a nomenclature that causes no confusion. Why then would it be confusing to call a system with a Linux kernel and a user space largely from the GNU project a "GNU/Linux system"? Including "GNU" in the name seems to be a problem only for people with an anti-GNU bias or misunderstanding of GPL, both of which Neville-Neil exhibited through his "supposedly" slight (in paragraph 10) intended to cast aspersions on the Hurd operating system project and the dig (as I read it) at GPLv3 for being more restrictive than GPLv2. However, in fairness, GPLv3 is more restrictive and explicit about not allowing patents to circumvent the freedoms inherent in a license otherwise granted by copyright. As Neville-Neil appeared disdainful of the GPLv2 methods of securing users' freedoms, it is not surprising he would take a negative view of GPLv3.

Neville-Neil also suggested the "GNU/Linux" name is inappropriate, as it reflects the tools used to build the kernel. But as Richard Stallman explained in his 2008 article "Linux and the GNU System" ( to which Neville-Neil linked in his column, a typical Linux distribution includes more code from the GNU project than from the Linux kernel project. Perhaps Neville-Neil should pour himself a less-"strong beverage" and read Stallman's article again. He may find himself much less confused by the "GNU/Linux" name.

Todd M. Lewis
Sanford, NC


Lewis hints at my anti-GPL bias, though I have been quite direct in my opposition to any open source license that restricts the freedoms of those using the code, as is done explicitly by the GPLv2 licenses. Open source means just that open, free to everyone, without strings, caveats, codicils, or clawbacks. As for a strong drink and a reread of anything from Richard Stallman it would have to be a very strong drink indeed to induce me to do it again.

George V. Neville-Neil
Brooklyn, NY

Displaying 1 comment

Sign In for Full Access
» Forgot Password? » Create an ACM Web Account
Article Contents: