gnu-linux-faq.html (80064B)
1 <!--#include virtual="/server/header.html" --> 2 <!-- Parent-Version: 1.96 --> 3 <!-- This page is derived from /server/standards/boilerplate.html --> 4 <!--#set var="TAGS" value="gnulinux" --> 5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" --> 6 <title>GNU/Linux FAQ 7 - GNU Project - Free Software Foundation</title> 8 <!--#include virtual="/gnu/po/gnu-linux-faq.translist" --> 9 <!--#include virtual="/server/banner.html" --> 10 <!--#include virtual="/gnu/gnu-breadcrumb.html" --> 11 <!--GNUN: OUT-OF-DATE NOTICE--> 12 <!--#include virtual="/server/top-addendum.html" --> 13 <div class="article reduced-width"> 14 <h2>GNU/Linux FAQ</h2> 15 16 <address class="byline">by Richard Stallman</address> 17 18 <div class="introduction"> 19 <p> 20 When people see that we use and recommend the name GNU/Linux for a 21 system that many others call just “Linux,” they ask many questions. 22 Here are common questions, and our answers.</p> 23 </div> 24 25 <div class="toc"> 26 <hr class="no-display" /> 27 <h3 class="no-display">Table of Contents</h3> 28 <ul> 29 30 <li><a href="#why">Why do you call the system we use GNU/Linux and not Linux?</a></li> 31 32 <li><a href="#whycare">Why is the name important?</a></li> 33 34 <li><a href="#what">What is the real relationship between GNU and Linux?</a></li> 35 36 <li><a href="#howerror">How did it come about that most 37 people call the system “Linux”?</a></li> 38 39 <li><a href="#always">Should we always say 40 “GNU/Linux” instead of “Linux”?</a></li> 41 42 <li><a href="#linuxalone">Would Linux have achieved 43 the same success if there had been no GNU?</a></li> 44 45 <li><a href="#divide">Wouldn't it be better for the 46 community if you did not divide people with this request?</a></li> 47 48 <li><a href="#freespeech">Doesn't the GNU project 49 support an individual's free speech rights to call the system by 50 any name that individual chooses?</a></li> 51 52 <li><a href="#everyoneknows">Since everyone 53 knows the role of GNU in developing the system, doesn't the 54 “GNU/” in the name go without saying?</a></li> 55 56 <li><a href="#everyoneknows2">Since I know the role of 57 GNU in this system, why does it matter what name I use?</a></li> 58 59 <li><a href="#windows">Isn't shortening 60 “GNU/Linux” to “Linux” just like 61 shortening “Microsoft Windows” to 62 “Windows”?</a></li> 63 64 <li><a href="#tools">Isn't GNU a collection of programming 65 tools that were included in Linux?</a></li> 66 67 <li><a href="#osvskernel">What is the difference between an operating 68 system and a kernel?</a></li> 69 70 <li><a href="#house">The kernel of a system is like the foundation 71 of a house. How can a house be almost complete when it doesn't have a 72 foundation?</a></li> 73 74 <li><a href="#brain">Isn't the kernel the brain of the 75 system?</a></li> 76 77 <li><a href="#kernelmost">Isn't writing the kernel 78 most of the work in an operating system?</a></li> 79 80 <li><a href="#nokernel">An operating system requires a kernel. 81 Since the GNU Project didn't develop a kernel, how can 82 the system be GNU?</a></li> 83 84 <li><a href="#notinstallable">How can GNU be an 85 operating system, if I can't get something called “GNU” 86 and install it?</a></li> 87 88 <li><a href="#afterkernel">We're calling the whole 89 system after the kernel, Linux. Isn't it normal to name an 90 operating system after a kernel?</a></li> 91 92 <li><a href="#feel">Can another system have “the 93 feel of Linux”?</a></li> 94 95 <li><a href="#long">The problem with 96 “GNU/Linux” is that it is too long. How about 97 recommending a shorter name?</a></li> 98 99 <li><a href="#long1">How about calling the system 100 “GliNUx” (instead of “GNU/Linux”)?</a></li> 101 102 <li><a href="#long2">The problem with 103 “GNU/Linux” is that it is too long. Why should 104 I go to the trouble of saying “GNU/”?</a></li> 105 106 <li><a href="#long3">Unfortunately, 107 “GNU/Linux” is five syllables. People won't use such a 108 long term. Shouldn't you find a shorter one?</a></li> 109 110 <li><a href="#long4">Stallman doesn't ask us to call him 111 “Richard Matthew Stallman” every the time. 112 So why ask us to say “GNU/Linux” every time?</a></li> 113 114 <li><a href="#justgnu">Since Linux is a secondary 115 contribution, would it be false to the facts to call the system 116 simply “GNU”?</a></li> 117 118 <li><a href="#trademarkfee">I would have to pay a 119 fee if I use “Linux” in the name of a product, and 120 that would also apply if I say “GNU/Linux.” Is it 121 wrong if I use “GNU” without “Linux,” to 122 save the fee?</a></li> 123 124 <li><a href="#many">Many other projects contributed to the 125 system as it is today; it includes TeX, X11, Apache, Perl, and many 126 more programs. Don't your arguments imply we have to give them 127 credit too? (But that would lead to a name so long it is 128 absurd.)</a></li> 129 130 <li><a href="#systemd">systemd plays an important role in the GNU/Linux 131 system as it is today; are we obligated to call it 132 GNU/systemd/Linux?</a></li> 133 134 <li><a href="#others">Many other projects contributed to 135 the system as it is today, but they don't insist on calling it 136 XYZ/Linux. Why should we treat GNU specially?</a></li> 137 138 <li><a href="#allsmall">GNU is a small fraction of the system 139 nowadays, so why should we mention it?</a></li> 140 141 <li><a href="#manycompanies">Many companies 142 contributed to the system as it is today; doesn't that mean 143 we ought to call it GNU/Red Hat/Novell/Linux?</a></li> 144 145 <li><a href="#whyslash">Why do you write 146 “GNU/Linux” instead of “GNU 147 Linux”?</a></li> 148 149 <li><a href="#linuxlibre">Does GNU have its own version of Linux, 150 the kernel?</a></li> 151 152 <li><a href="#pronounce">How is the name “GNU/Linux” 153 pronounced?</a></li> 154 155 <li><a href="#whynoslash">Why do you write 156 “GNU Emacs” rather than “GNU/Emacs”?</a></li> 157 158 <li><a href="#whyorder">Why “GNU/Linux” 159 rather than “Linux/GNU”?</a></li> 160 161 <li><a href="#distronames0">My distro's developers call it 162 “Foobar Linux,” but that doesn't say anything about 163 what the system consists of. Why shouldn't they call it whatever 164 they like?</a></li> 165 166 <li><a href="#distronames">My distro is called 167 “Foobar Linux”; doesn't that show it's really 168 Linux?</a></li> 169 170 <li><a href="#distronames1">My distro's official 171 name is “Foobar Linux”; isn't it wrong to call the 172 distro anything but “Foobar Linux”?</a></li> 173 174 <li><a href="#companies">Wouldn't it be more 175 effective to ask companies such as Mandrake, Red Hat and IBM to 176 call their distributions “GNU/Linux” rather than 177 asking individuals?</a></li> 178 179 <li><a href="#reserve">Wouldn't it be better to 180 reserve the name “GNU/Linux” for distributions that 181 are purely free software? After all, that is the ideal of 182 GNU.</a></li> 183 184 <li><a href="#gnudist">Why not make a GNU distribution of 185 Linux (sic) and call that GNU/Linux?</a></li> 186 187 <li><a href="#linuxgnu">Why not just say “Linux 188 is the GNU kernel” and release some existing version of 189 GNU/Linux under the name “GNU”?</a></li> 190 191 <li><a href="#condemn">Did the GNU Project condemn and 192 oppose use of Linux in the early days?</a></li> 193 194 <li><a href="#wait">Why did you wait so long before 195 asking people to use the name GNU/Linux?</a></li> 196 197 <li><a href="#allgpled">Should the GNU/<i>name</i> convention 198 be applied to all programs that are GPL'ed?</a></li> 199 200 <li><a href="#unix">Since much of GNU comes from Unix, 201 shouldn't GNU give credit to Unix by using “Unix” in 202 its name?</a></li> 203 204 <li><a href="#bsd">Should we say “GNU/BSD” 205 too?</a></li> 206 207 <li><a href="#othersys">If I install the GNU tools on 208 Windows, does that mean I am running a GNU/Windows system?</a></li> 209 210 <li><a href="#justlinux">Can't Linux be used without 211 GNU?</a></li> 212 213 <li><a href="#howmuch">How much of the GNU system 214 is needed for the system to be GNU/Linux?</a></li> 215 216 <li><a href="#linuxsyswithoutgnu">Are there complete Linux systems [sic] without GNU?</a></li> 217 218 <li><a href="#usegnulinuxandandroid">Is it correct to say “using 219 Linux” if it refers to using GNU/Linux and using Android?</a></li> 220 221 <li><a href="#helplinus">Why not call the system 222 “Linux” anyway, and strengthen Linus Torvalds' role as 223 posterboy for our community?</a></li> 224 225 <li><a href="#claimlinux">Isn't it wrong for us to label Linus 226 Torvalds' work as GNU?</a></li> 227 228 <li><a href="#linusagreed">Does Linus Torvalds 229 agree that Linux is just the kernel?</a></li> 230 231 <li><a href="#finishhurd">Why not finish 232 the GNU Hurd kernel, release the GNU system as a whole, 233 and forget the question of what to call GNU/Linux?</a></li> 234 235 <li><a href="#lost">The battle is already 236 lost—society has made its decision and we can't change it, 237 so why even think about it?</a></li> 238 239 <li><a href="#whatgood">Society has made its decision 240 and we can't change it, so what good does it do if I say 241 “GNU/Linux”?</a></li> 242 243 <li><a href="#explain">Wouldn't it be better to call 244 the system “Linux” and teach people its real origin 245 with a ten-minute explanation?</a></li> 246 247 <li><a href="#treatment">Some people laugh at you when 248 you ask them to call the system GNU/Linux. Why do you subject yourself 249 to this treatment?</a></li> 250 251 <li><a href="#alienate">Some people condemn you when you 252 ask them to call the system GNU/Linux. Don't you lose by 253 alienating them?</a></li> 254 255 <li><a href="#rename">Whatever you contributed, 256 is it legitimate to rename the operating system?</a></li> 257 258 <li><a href="#force">Isn't it wrong to force people to call 259 the system “GNU/Linux”?</a></li> 260 261 <li><a href="#whynotsue">Why not sue people who call 262 the whole system “Linux”?</a></li> 263 264 <li><a href="#BSDlicense">Since you objected to the original 265 BSD license's advertising requirement to give credit to the University of 266 California, isn't it hypocritical to demand credit for the GNU project?</a></li> 267 268 <li><a href="#require">Shouldn't you put something in 269 the GNU GPL to require people to call the system 270 “GNU”?</a></li> 271 272 <li><a href="#deserve">Since you failed to put 273 something in the GNU GPL to require people to call the system 274 “GNU,” you deserve what happened; why are you 275 complaining now?</a></li> 276 277 <li><a href="#contradict">Wouldn't you be better off 278 not contradicting what so many people believe?</a></li> 279 280 <li><a href="#somanyright">Since many people call it 281 “Linux,” doesn't that make it right?</a></li> 282 283 <li><a href="#knownname">Isn't it better to call the 284 system by the name most users already know?</a></li> 285 286 <li><a href="#winning">Many people care about what's convenient or 287 who's winning, not about arguments of right or wrong. Couldn't you 288 get more of their support by a different road?</a></li> 289 290 </ul> 291 </div> 292 293 <div class="announcement comment" role="complementary"> 294 <p>To learn more about this issue, you can also read 295 our page on <a href="/gnu/linux-and-gnu.html">Linux and the GNU System</a>, our 296 page on <a href="/gnu/why-gnu-linux.html">Why GNU/Linux?</a> 297 and our page on <a href="/gnu/gnu-users-never-heard-of-gnu.html">GNU 298 Users Who Have Never Heard of GNU</a>.</p> 299 <hr class="no-display" /> 300 </div> 301 302 <dl> 303 304 <dt id="why">Why do you call the system we use GNU/Linux and not 305 Linux? <span class="anchor-reference-id">(<a href="#why">#why</a>)</span></dt> 306 307 <dd>Most operating system distributions based on Linux as kernel are 308 basically modified versions of the GNU operating system. We began 309 developing GNU in 1984, years before Linus Torvalds started to write 310 his kernel. Our goal was to develop a complete free operating system. 311 Of course, we did not develop all the parts ourselves—but we led the way. 312 We developed most of the central components, forming the largest single 313 contribution to the whole system. The basic vision was ours too. 314 <p> 315 In fairness, we ought to get at least equal mention.</p> 316 317 <p>See <a href="/gnu/linux-and-gnu.html">Linux and the GNU System</a> 318 and <a href="/gnu/gnu-users-never-heard-of-gnu.html">GNU Users Who Have 319 Never Heard of GNU</a> for more explanation, and <a 320 href="/gnu/the-gnu-project.html">The GNU Project</a> for the 321 history.</p> </dd> 322 323 <dt id="whycare">Why is the name 324 important? <span class="anchor-reference-id">(<a href="#whycare">#whycare</a>)</span></dt> 325 326 <dd>Although the developers of Linux, the kernel, are contributing to 327 the free software community, many of them do not care about freedom. 328 People who think the whole system is Linux tend to get confused and 329 assign to those developers a role in the history of our community 330 which they did not actually play. Then they give inordinate weight to 331 those developers' views. 332 <p> 333 Calling the system GNU/Linux recognizes the role that our idealism 334 played in building our community, and 335 <a href="/gnu/why-gnu-linux.html">helps the public recognize the 336 practical importance of these ideals</a>.</p> 337 </dd> 338 339 <dt id="what">What is the real relationship between GNU and Linux? <span class="anchor-reference-id">(<a href="#what">#what</a>)</span></dt> 340 341 <dd> 342 <p> 343 The GNU operating system and the Linux kernel are separate 344 software projects that do complementary jobs. Typically they are 345 packaged in a <a href="/distros/distros.html">GNU/Linux distribution</a>, and used 346 together.</p> 347 </dd> 348 349 <dt id="howerror">How did it come about that most 350 people call the system “Linux”? <span class="anchor-reference-id">(<a href="#howerror">#howerror</a>)</span></dt> 351 352 <dd>Calling the system “Linux” is a confusion that has spread faster 353 than the corrective information. 354 <p> 355 The people who combined Linux with the GNU system were not aware that 356 that's what their activity amounted to. They focused their attention 357 on the piece that was Linux and did not realize that more of the 358 combination was GNU. They started calling it “Linux” even though that 359 name did not fit what they had. It took a few years for us to realize 360 what a problem this was and ask people to correct the practice. By 361 that time, the confusion had a big head start.</p> 362 <p> 363 Most of the people who call the system “Linux” have never heard why 364 that's not the right thing. They saw others using that name and 365 assume it must be right. The name “Linux” also spreads a false 366 picture of the system's origin, because people tend to suppose that 367 the system's history was such as to fit that name. For 368 instance, they often believe its development was started by Linus 369 Torvalds in 1991. This false picture tends to reinforce the idea 370 that the system should be called “Linux.”</p> 371 <p> 372 Many of the questions in this file represent people's attempts to 373 justify the name they are accustomed to using.</p> 374 </dd> 375 376 <dt id="always">Should we always say 377 “GNU/Linux” instead of “Linux”? <span class="anchor-reference-id">(<a href="#always">#always</a>)</span></dt> 378 <dd> 379 Not always—only when you're talking about the whole system. When 380 you're referring specifically to the kernel, you should call it 381 “Linux,” the name its developer chose. 382 <p> 383 When people call the whole system “Linux,” as a consequence 384 they call the whole system by the same name as the kernel. 385 This causes many kinds of confusion, because only experts can tell 386 whether a statement is about the kernel or the whole system. 387 By calling the whole system “GNU/Linux,” and calling the kernel 388 “Linux,” you avoid the ambiguity.</p> 389 </dd> 390 391 <dt id="linuxalone">Would Linux have 392 achieved the same success if there had been no 393 GNU? <span class="anchor-reference-id">(<a href="#linuxalone">#linuxalone</a>)</span></dt> 394 395 <dd> 396 In that alternative world, there would be nothing today like the 397 GNU/Linux system, and probably no free operating system at all. No 398 one attempted to develop a free operating system in the 1980s except 399 the GNU Project and (later) Berkeley CSRG, which had been specifically 400 asked by the GNU Project to start freeing its code. 401 <p> 402 Linus Torvalds was partly influenced by a speech about GNU in Finland 403 in 1990. It's possible that even without this influence he might have 404 written a Unix-like kernel, but it probably would not have been free 405 software. Linux became free in 1992 when Linus rereleased it under 406 the GNU GPL. (See the release notes for version 0.12.)</p> 407 <p> 408 Even if Torvalds had released Linux under some other free software 409 license, a free kernel alone would not have made much difference to 410 the world. The significance of Linux came from fitting into a larger 411 framework, a complete free operating system: GNU/Linux.</p> 412 </dd> 413 414 <dt id="divide">Wouldn't it be better for the 415 community if you did not divide people with this request? <span class="anchor-reference-id">(<a href="#divide">#divide</a>)</span></dt> 416 417 <dd> 418 When we ask people to say “GNU/Linux,” we are not dividing people. We 419 are asking them to give the GNU Project credit for the GNU operating 420 system. This does not criticize anyone or push anyone away. 421 <p> 422 However, there are people who do not like our saying this. Sometimes 423 those people push us away in response. On occasion they are so rude 424 that one wonders if they are intentionally trying to intimidate us 425 into silence. It doesn't silence us, but it does tend to divide the 426 community, so we hope you can convince them to stop.</p> 427 <p> 428 However, this is only a secondary cause of division in our community. 429 The largest division in the community is between people who appreciate 430 free software as a social and ethical issue and consider proprietary 431 software a social problem (supporters of the free software movement), 432 and those who cite only practical benefits and present free software 433 only as an efficient development model (the open source movement).</p> 434 <p> 435 This disagreement is not just a matter of names—it is a matter 436 of differing basic values. It is essential for the community to see 437 and think about this disagreement. The names “free 438 software” and “open source” are the banners of the 439 two positions. 440 See <a href="/philosophy/open-source-misses-the-point.html">Why Open 441 Source misses the point of Free Software</a>.</p> 442 <p> 443 The disagreement over values partially aligns with the amount of 444 attention people pay to the GNU Project's role in our community. 445 People who value freedom are more likely to call the system 446 “GNU/Linux,” and people who learn that the system is “GNU/Linux” are 447 more likely to pay attention to our philosophical arguments for 448 freedom and community (which is why the choice of name for the system 449 makes a real difference for society). However, the disagreement would 450 probably exist even if everyone knew the system's real origin and its 451 proper name, because the issue is a real one. It can only go away if 452 we who value freedom either persuade everyone (which won't be easy) or 453 are defeated entirely (let's hope not).</p> 454 </dd> 455 456 <dt id="freespeech">Doesn't the GNU project 457 support an individual's free speech rights to call the system by 458 any name that individual chooses? <span class="anchor-reference-id">(<a href="#freespeech">#freespeech</a>)</span></dt> 459 <dd> 460 <p> 461 Yes, indeed, we believe you have a free speech right to call the 462 operating system by any name you wish. We ask that people call it 463 GNU/Linux as a matter of doing justice to the GNU project, to promote 464 the values of freedom that GNU stands for, and to inform others that 465 those values of freedom brought the system into existence.</p> 466 </dd> 467 468 <dt id="everyoneknows">Since everyone knows the role 469 of GNU in developing the system, doesn't the “GNU/” in the 470 name go without saying? <span class="anchor-reference-id">(<a href="#everyoneknows">#everyoneknows</a>)</span></dt> 471 472 <dd>Experience shows that the system's users, and the computer-using 473 public in general, often know nothing about the GNU system. Most 474 articles about the system do not mention the name “GNU,” or the ideals 475 that GNU stands for. <a 476 href="/gnu/gnu-users-never-heard-of-gnu.html">GNU Users Who Have Never 477 Heard of GNU</a> explains further. 478 <p> 479 The people who say this are probably geeks thinking of the geeks they 480 know. Geeks often do know about GNU, but many have a completely wrong 481 idea of what GNU is. For instance, many think it is a collection 482 of “<a href="#tools">tools</a>,” or a project to develop tools.</p> 483 <p> 484 The wording of this question, which is typical, illustrates another 485 common misconception. To speak of “GNU's role” in developing 486 something assumes that GNU is a group of people. GNU is an operating 487 system. It would make sense to talk about the GNU Project's role in 488 this or some other activity, but not that of GNU.</p> 489 </dd> 490 491 <dt id="everyoneknows2">Since I know the role of GNU in this system, 492 why does it matter what name I use? <span class="anchor-reference-id">(<a href="#everyoneknows2">#everyoneknows2</a>)</span></dt> 493 494 <dd> 495 <p> 496 If your words don't reflect your knowledge, you don't teach others. 497 Most people who have heard of the GNU/Linux system think it is 498 “Linux,” that it was started by Linus Torvalds, and that 499 it was intended to be “open source.” If you don't tell 500 them, who will?</p> 501 </dd> 502 503 <dt id="windows">Isn't shortening “GNU/Linux” 504 to “Linux” just like shortening “Microsoft Windows” to “Windows”? <span class="anchor-reference-id">(<a href="#windows">#windows</a>)</span></dt> 505 506 <dd> 507 It's useful to shorten a frequently-used name, but not if the 508 abbreviation is misleading. 509 <p> 510 Almost everyone in developed countries really does know that the 511 “Windows” system is made by Microsoft, so shortening “Microsoft 512 Windows” to “Windows” does not mislead anyone as to that system's 513 nature and origin. Shortening “GNU/Linux” to “Linux” does give the 514 wrong idea of where the system comes from.</p> 515 <p> 516 The question is itself misleading because GNU and Microsoft are 517 not the same kind of thing. Microsoft is a company; 518 GNU is an operating system.</p> 519 </dd> 520 521 <dt id="tools">Isn't GNU a collection of 522 programming tools that were included in Linux? <span class="anchor-reference-id">(<a href="#tools">#tools</a>)</span></dt> 523 524 <dd> 525 People who think that Linux is an entire operating system, if they 526 hear about GNU at all, often get a wrong idea of what GNU is. They 527 may think that GNU is the name of a collection of programs—often they 528 say “programming tools,” since some of our programming tools became 529 popular on their own. The idea that “GNU” is the name of an operating 530 system is hard to fit into a conceptual framework in which that 531 operating system is labeled “Linux.” 532 <p> 533 The GNU Project was named after the GNU operating system—it's the project 534 to develop the GNU system. (See <a 535 href="/gnu/initial-announcement.html">the 1983 initial announcement</a>.)</p> 536 <p> 537 We developed programs such as GCC, GNU Emacs, GAS, GLIBC, BASH, etc., 538 because we needed them for the GNU operating system. GCC, the GNU 539 Compiler Collection is the compiler that we wrote for the GNU 540 operating system. We, the many people working on the GNU Project, 541 developed Ghostscript, GNUCash, GNU Chess and GNOME for the GNU system 542 too.</p> 543 </dd> 544 545 <dt id="osvskernel">What is the difference 546 between an operating system and a kernel? <span class="anchor-reference-id">(<a href="#osvskernel">#osvskernel</a>)</span></dt> 547 548 <dd> 549 An operating system, as we use the term, means a collection of 550 programs that are sufficient to use the computer to do a wide variety 551 of jobs. A general purpose operating system, to be complete, ought to 552 handle all the jobs that many users may want to do. 553 <p> 554 The kernel is one of the programs in an operating system—the program 555 that allocates the machine's resources to the other programs that are 556 running. The kernel also takes care of starting and stopping other 557 programs.</p> 558 <p> 559 To confuse matters, some people use the term “operating system” to 560 mean “kernel.” Both uses of the term go back many years. The 561 use of “operating system” to mean “kernel” is found in a number of 562 textbooks on system design, going back to the 80s. At the same time, 563 in the 80s, the “Unix operating system” was understood to include all 564 the system programs, and Berkeley's version of Unix included even 565 games. Since we intended GNU to be a Unix-like operating system, we 566 use the term “operating system” in the same way.</p> 567 <p> 568 Most of the time when people speak of the “Linux operating system” 569 they are using “operating system” in the same sense we use: they mean 570 the whole collection of programs. If that's what you are referring 571 to, please call it “GNU/Linux.” If you mean just the kernel, then 572 “Linux” is the right name for it, but please say “kernel” also to 573 avoid ambiguity about which body of software you mean.</p> 574 <p> 575 If you prefer to use some other term such as “system distribution” for 576 the entire collection of programs, instead of “operating system,” 577 that's fine. Then you would talk about GNU/Linux system 578 distributions.</p> 579 </dd> 580 581 <dt id="house">The kernel of a system is like the foundation of a 582 house. How can a house be almost complete when it doesn't have a 583 foundation? <span class="anchor-reference-id">(<a href="#house">#house</a>)</span></dt> 584 585 <dd> 586 A kernel is not much like the foundation of a house because building 587 an operating system is not much like building a house. 588 589 <p>A house is built from lots of little general parts that are cut and 590 put together in situ. They have to be put together from the bottom 591 up. Thus, when the foundation has not been built, no substantial part 592 has been built; all you have is a hole in the ground.</p> 593 594 <p> 595 By contrast, an operating system consists of complex 596 components that can be developed in any order. When you have 597 developed most of the components, most of the work is done. This is 598 much more like the International Space Station than like a house. If 599 most of the Space Station modules were in orbit but awaiting one other 600 essential module, that would be like the GNU system in 1992. 601 </p> 602 </dd> 603 604 <dt id="brain">Isn't the kernel the brain of the system? <span class="anchor-reference-id">(<a href="#brain">#brain</a>)</span></dt> 605 606 <dd> 607 <p> 608 A computer system is not much like a human body, 609 and no part of it plays a role comparable to that of 610 the brain in a human.</p> 611 </dd> 612 613 <dt id="kernelmost">Isn't writing the kernel most of the work in an 614 operating system? <span class="anchor-reference-id">(<a href="#kernelmost">#kernelmost</a>)</span></dt> 615 616 <dd> 617 <p> 618 No, many components take a lot of work.</p> 619 </dd> 620 621 <dt id="nokernel">An operating system requires a kernel. 622 Since the GNU Project didn't develop a kernel, how can 623 the system be GNU?<span class="anchor-reference-id">(<a href="#nokernel">#nokernel</a>)</span></dt> 624 625 <dd> 626 The people who argue that way for calling the system 627 “Linux” are using a double standard. An operating system 628 requires compilers, editors, window systems, libraries, and much 629 more—hundreds of programs, even to match what BSD systems included 630 in 1983. Since Torvalds didn't develop any of those, how can the 631 system be “Linux”? 632 633 <p> 634 That standard is too strict, not the right way to judge the 635 contributions of any contributor.</p> 636 637 <p> 638 Linus Torvalds made an important contribution to the operating system 639 we use; the GNU Project started earlier and contributed much more. 640 The name “GNU/Linux” gives credit to each.</p> 641 </dd> 642 643 <dt id="notinstallable">How can GNU be an 644 operating system, if I can't get something called “GNU” 645 and install it? <span class="anchor-reference-id">(<a href="#notinstallable">#notinstallable</a>)</span></dt> 646 647 <dd> 648 Many <a href="/distros/distros.html"> packaged and installable 649 versions of GNU</a> are available. None of them is called simply 650 “GNU,” but GNU is what they basically are. 651 652 <p> 653 We expected to release the GNU system packaged for installation, but 654 this plan was overtaken by events: in 1992 others were already 655 packaging GNU variants containing Linux. Starting in 1993 we 656 sponsored an effort to make a better and freer GNU/Linux distribution, 657 called <a href="/distros/common-distros.html#Debian">Debian 658 GNU/Linux</a>. The founder of Debian had already chosen that name. 659 We did not ask him to call it just “GNU” because that was 660 to be the name of a system version with the GNU Hurd kernel—which 661 wasn't ready yet.</p> 662 663 <p> 664 The GNU Hurd kernel never became sufficiently ready; we only recommend 665 it to those interested in working on it. So we never packaged GNU 666 with the GNU Hurd kernel. However, Debian packaged this combination 667 as Debian GNU/Hurd.</p> 668 669 <p> 670 We are now developing an advanced Scheme-based package manager called 671 Guix and a complete system distribution based on it called the 672 <a href="/software/guix">Guix System Distribution</a> or GuixSD. 673 This includes repackaging a substantial part of the GNU system.</p> 674 675 <p> 676 We never took the last step of packaging GNU under the name 677 “GNU,” but that doesn't alter what kind of thing GNU is. 678 GNU is an operating system.</p> 679 </dd> 680 681 <dt id="afterkernel">We're calling the 682 whole system after the kernel, Linux. Isn't it normal to name an 683 operating system after a kernel? <span class="anchor-reference-id">(<a href="#afterkernel">#afterkernel</a>)</span></dt> 684 685 <dd> 686 That practice seems to be very rare—we can't find any examples other 687 than the misuse of the name “Linux.” Normally an operating system is 688 developed as a single unified project, and the developers choose a 689 name for the system as a whole. The kernel usually does not have a 690 name of its own—instead, people say “the kernel of such-and-such” or 691 “the such-and-such kernel.” 692 <p> 693 Because those two constructions are used synonymously, the expression 694 “the Linux kernel” can easily be misunderstood as meaning “the kernel 695 of Linux” and implying that Linux must be more than a kernel. You can 696 avoid the possibility of this misunderstanding by saying or writing 697 “the kernel, Linux” or “Linux, the kernel.”</p> 698 </dd> 699 700 <dt id="feel">Can another system have “the 701 feel of Linux”? <span class="anchor-reference-id">(<a href="#feel">#feel</a>)</span></dt> 702 703 <dd> 704 <p> 705 There is no such thing as the “feel of Linux” because 706 Linux has no user interfaces. Like any modern kernel, Linux is a base 707 for running programs; user interfaces belong elsewhere in the system. 708 Human interaction with GNU/Linux always goes through other programs, 709 and the “feel” comes from them.</p> 710 </dd> 711 712 <dt id="long">The problem with “GNU/Linux” is that it is too long. 713 How about recommending a shorter name? <span class="anchor-reference-id">(<a href="#long">#long</a>)</span></dt> 714 715 <dd> 716 For a while we tried the name “LiGNUx,” which combines the words “GNU” 717 and “Linux.” The reaction was very bad. People accept “GNU/Linux” 718 much better. 719 <p> 720 The shortest legitimate name for this system is “GNU,” but 721 we call it “GNU/Linux” <a href="#justgnu"> for the reasons 722 given below</a>.</p> 723 </dd> 724 725 <dt id="long1">How about calling the system 726 “GliNUx” (instead of “GNU/Linux”)? 727 <span class="anchor-reference-id">(<a href="#long1">#long1</a>)</span></dt> 728 729 <dd> 730 <p>The name “GNU” does not visibly appear in 731 “Glinux,” so most people would not notice it is there. 732 Even if it is capitalized as “GliNUx,” most people would 733 not realize that it contains a reference to GNU.</p> 734 735 <p>It would be comparable to writing “GNU/Linux,” but 736 putting “GNU/” in print so small that most people could 737 not read it.</p> 738 </dd> 739 740 <dt id="long2">The problem with “GNU/Linux” is that it is too long. 741 Why should I go to the trouble of saying “GNU/”? 742 <span class="anchor-reference-id">(<a href="#long2">#long2</a>)</span></dt> 743 744 <dd> 745 <p>It only takes a second to say or type “GNU/.” If you 746 appreciate the system that we developed, can't you take one second 747 to recognize our work?</p> 748 </dd> 749 750 <dt id="long3">Unfortunately, “GNU/Linux” is five 751 syllables. People won't use such a long term. Shouldn't you find a 752 shorter one? 753 <span class="anchor-reference-id">(<a href="#long3">#long3</a>)</span></dt> 754 <dd><p>Actually, “GNU/Linux” is only four syllables. 755 “Unfortunately” is five syllables, yet people show no 756 sign of reluctance to use that word.</p></dd> 757 758 <dt id="long4">Stallman doesn't ask us to call him 759 “Richard Matthew Stallman” every the time. 760 So why ask us to say “GNU/Linux” every time? 761 <span class="anchor-reference-id">(<a href="#long4">#long4</a>)</span></dt> 762 <dd> 763 <p>Omitting “Matthew” does not misrepresent anything 764 important about Stallman's nature, origin, ideas or purpose. Omitting 765 “GNU” does misrepresent those things about the GNU/Linux 766 system.</p> 767 768 <p>This is an example of a frequent way of hiding a fallacy: to bury 769 it inside a misleading analogy. A better analogy would be, “Why 770 shouldn't we call Stallman ‘Torvalds’?” 771 </p></dd> 772 773 <dt id="justgnu">Since Linux is a secondary 774 contribution, would it be false to the facts to call the system simply 775 “GNU”? <span class="anchor-reference-id">(<a href="#justgnu">#justgnu</a>)</span></dt> 776 777 <dd> 778 It would not be false to the facts, but it is not the best thing to 779 do. Here are the reasons we call that system version “GNU/Linux” 780 rather than just “GNU”: 781 782 <ul> 783 <li> 784 It's not exactly GNU—it has a different kernel (that is, Linux). 785 Distinguishing GNU/Linux from GNU is useful.</li> 786 <li> 787 It would be ungentlemanly to ask people to <em>stop</em> giving any 788 credit to Linus Torvalds. He did write an important component of the 789 system. We want to get credit for launching and sustaining the 790 system's development, but this doesn't mean we should treat Linus the 791 same way those who call the system “Linux” treat us. We strongly 792 disagree with his political views, but we deal with that disagreement 793 honorably and openly, rather than by trying to cut him out of the 794 credit for his contribution to the system.</li> 795 <li> 796 Since many people know of the system as “Linux,” if we say “GNU” they 797 may simply not recognize we're talking about the same system. If we 798 say “GNU/Linux,” they can make a connection to what they have heard 799 about.</li> 800 </ul> 801 </dd> 802 803 <dt id="trademarkfee">I would have 804 to pay a fee if I use “Linux” in the name of a product, and that 805 would also apply if I say “GNU/Linux.” Is it wrong if I use “GNU” 806 without “Linux,” to save the fee? <span class="anchor-reference-id">(<a href="#trademarkfee">#trademarkfee</a>)</span></dt> 807 <dd> 808 There's nothing wrong in calling the system “GNU”; basically, that's 809 what it is. It is nice to give Linus Torvalds a share of the credit 810 as well, but you have no obligation to pay for the privilege of doing 811 so. 812 <p> 813 So if you want to refer to the system simply as “GNU,” to avoid paying 814 the fee for calling it “Linux,” we won't criticize you.</p> 815 </dd> 816 817 <dt id="many">Many other projects contributed to 818 the system as it is today; it includes TeX, X11, Apache, Perl, and many 819 more programs. Don't your arguments imply we have to give them credit 820 too? (But that would lead to a name so long it is 821 absurd.) <span class="anchor-reference-id">(<a href="#many">#many</a>)</span></dt> 822 823 <dd> 824 What we say is that you ought to give the system's principal developer 825 a share of the credit. The principal developer is the GNU Project, 826 and the system is basically GNU. 827 <p> 828 If you feel even more strongly about giving credit where it is due, 829 you might feel that some secondary contributors also deserve credit in 830 the system's name. If so, far be it from us to argue against it. If 831 you feel that X11 deserves credit in the system's name, and you want 832 to call the system GNU/X11/Linux, please do. If you feel that Perl 833 simply cries out for mention, and you want to write GNU/Linux/Perl, go 834 ahead.</p> 835 <p> 836 Since a long name such as GNU/X11/Apache/Linux/TeX/Perl/Python/FreeCiv 837 becomes absurd, at some point you will have to set a threshold and 838 omit the names of the many other secondary contributions. There is no 839 one obvious right place to set the threshold, so wherever you set it, 840 we won't argue against it.</p> 841 <p> 842 Different threshold levels would lead to different choices of name for 843 the system. But one name that cannot result from concerns of fairness 844 and giving credit, not for any possible threshold level, is “Linux.” 845 It can't be fair to give all the credit to one secondary contribution 846 (Linux) while omitting the principal contribution (GNU).</p> 847 </dd> 848 849 <dt id="systemd">systemd plays an important role in the GNU/Linux 850 system as it is today; are we obligated to call it 851 GNU/systemd/Linux? <span class="anchor-reference-id">(<a href="#others">#others</a>)</span></dt> 852 853 <dd> 854 <p> 855 systemd is a fairly important component, but not as important as the 856 kernel (Linux), nor as important as the basis of the system as a whole 857 (GNU). However, if you want to emphasize the presence of systemd 858 by calling the system “GNU/systemd/Linux,” there is nothing 859 wrong with doing so.</p> 860 </dd> 861 862 <dt id="others">Many other projects contributed to 863 the system as it is today, but they don't insist on calling it 864 XYZ/Linux. Why should we treat GNU specially? <span class="anchor-reference-id">(<a href="#others">#others</a>)</span></dt> 865 866 <dd> 867 Thousands of projects have developed programs commonly included in 868 today's GNU/Linux systems. They all deserve credit for their 869 contributions, but they aren't the principal developers of the system 870 as a whole, so they don't ask to be credited as such. 871 <p> 872 GNU is different because it is more than just a contributed program, 873 more than just a collection of contributed programs. GNU is the 874 framework on which the system was made.</p> 875 </dd> 876 877 <dt id="allsmall">GNU is a small fraction of the system nowadays, 878 so why should we mention it? <span class="anchor-reference-id">(<a href="#allsmall">#allsmall</a>)</span></dt> 879 <dd> 880 In 2008, we found that GNU packages made up 15% of the 881 “main” repository of the gNewSense GNU/Linux distribution. 882 Linux made up 1.5%. So the same argument would apply even more 883 strongly to calling it “Linux.” 884 885 <p> 886 GNU is a small fraction of the system nowadays, and Linux is an 887 even smaller fraction. But they are the system's core; the system 888 was made by combining them. Thus, the name “GNU/Linux” 889 remains appropriate. 890 </p> 891 </dd> 892 893 <dt id="manycompanies">Many companies 894 contributed to the system as it is today; doesn't that mean 895 we ought to call it GNU/Red Hat/Novell/Linux? <span 896 class="anchor-reference-id">(<a 897 href="#manycompanies">#manycompanies</a>)</span></dt> 898 899 <dd> 900 <p> 901 GNU is not comparable to Red Hat or Novell; it is not a company, or an 902 organization, or even an activity. GNU is an operating system. (When 903 we speak of the GNU Project, that refers to the project to develop the 904 GNU system.) The GNU/Linux system is based on GNU, and that's why GNU 905 ought to appear in its name. 906 </p> 907 <p> 908 Much of those companies' contribution to the GNU/Linux system lies in 909 the code they have contributed to various GNU packages including GCC 910 and GNOME. Saying GNU/Linux gives credit to those companies along 911 with all the rest of the GNU developers. 912 </p> 913 </dd> 914 915 <dt id="whyslash">Why do you write “GNU/Linux” 916 instead of “GNU Linux”? <span class="anchor-reference-id">(<a href="#whyslash">#whyslash</a>)</span></dt> 917 918 <dd> 919 Following the rules of English, in the construction “GNU Linux” the 920 word “GNU” modifies “Linux.” This can mean either “GNU's version of 921 Linux” or “Linux, which is a GNU package.” Neither of those meanings 922 fits the situation at hand. 923 <p> 924 Linux is not a GNU package; that is, it wasn't developed under the GNU 925 Project's aegis or contributed specifically to the GNU Project. Linus 926 Torvalds wrote Linux independently, as his own project. So the 927 “Linux, which is a GNU package” meaning is not right.</p> 928 <p> 929 We're not talking about a distinct GNU version of Linux, the kernel. 930 The free GNU/Linux distros do have 931 a <a href="https://directory.fsf.org/wiki/Linux-libre">separate version of 932 Linux</a>, since the “standard” version contains nonfree 933 firmware “blobs.” If this were part of the GNU Project, 934 it could be considered “GNU Linux”; but we would not want 935 to call it that, because it would be too confusing.</p> 936 <p> 937 We're talking about a version of GNU, the operating system, 938 distinguished by having Linux as the kernel. A slash fits the 939 situation because it means “combination.” (Think of 940 “Input/Output.”) It's the GNU system, with the kernel 941 Linux underneath; hence, “GNU/Linux.”</p> 942 <p> 943 There are other ways to express “combination.” If you 944 think that a plus-sign is clearer, please use that. In French, a 945 hyphen is clear: “GNU-Linux.” In Spanish, we sometimes 946 say “GNU con Linux.”</p> 947 </dd> 948 949 <dt id="linuxlibre">Does GNU have its own version of Linux, the kernel? <span class="anchor-reference-id">(<a href="#linuxlibre">#linuxlibre</a>)</span></dt> 950 951 <dd> 952 Yes and no. The free GNU/Linux distros use slightly modified versions 953 of Linux, modified to remove the nonfree firmware “blobs” 954 contained in the “standard” release of Linux. Some of 955 them use <a href="https://directory.fsf.org/wiki/Linux-libre">GNU 956 Linux-Libre</a>, which is the GNU Project's freed version of Linux. 957 But this is not a fork; rather, it is a version of Linux—we 958 take the source of each standard Linux release and de-blob it. 959 <p> 960 Other free distros make their own arrangements to remove the blobs 961 from Linux.</p> 962 </dd> 963 964 <dt id="pronounce">How is the name “GNU/Linux” 965 pronounced? <span class="anchor-reference-id">(<a href="#pronounce">#pronounce</a>)</span></dt> 966 <dd> 967 <p> 968 Please pronounce it as “GNU slash Linux.” If you don't pronounce 969 the slash, people will think you are saying “GNU Linux,” 970 which is <a href="#whyslash">not a suitable name for the combination</a>. 971 </p> 972 </dd> 973 974 <dt id="whynoslash">Why do you write “GNU Emacs” 975 rather than “GNU/Emacs”? <span class="anchor-reference-id">(<a href="#whynoslash">#whynoslash</a>)</span></dt> 976 977 <dd> 978 <p> 979 Following the rules of English, in the construction “GNU 980 Emacs” the word “GNU” modifies “Emacs.” 981 That is the right way to describe a program called Emacs which is a 982 GNU package.</p> 983 <p> 984 “GNU/Emacs” would mean the combination of GNU, the 985 operating system, and the program Emacs. That doesn't fit this 986 program, so “GNU/Emacs” is the wrong way to refer to it.</p> 987 </dd> 988 989 <dt id="whyorder">Why “GNU/Linux” rather 990 than “Linux/GNU”? <span class="anchor-reference-id">(<a href="#whyorder">#whyorder</a>)</span></dt> 991 992 <dd> 993 <p> 994 It is right and proper to mention the principal contribution first. 995 The GNU contribution to the system is not only bigger than Linux and 996 prior to Linux, we actually started the whole activity.</p> 997 <p> 998 In addition, “GNU/Linux” fits the fact that Linux is the 999 lowest level of the system and GNU fills technically higher levels.</p> 1000 <p> 1001 However, if you prefer to call the system “Linux/GNU,” that is a lot 1002 better than what people usually do, which is to omit GNU entirely and 1003 make it seem that the whole system is Linux.</p> 1004 </dd> 1005 1006 <dt id="distronames0">My distro's developers call it 1007 “Foobar Linux,” but that doesn't say anything about 1008 what the system consists of. Why shouldn't they call it whatever 1009 they like? <span class="anchor-reference-id">(<a href="#distronames0">#distronames0</a>)</span></dt> 1010 <dd> 1011 Calling a system “Foobar Linux” implies that it's a flavor 1012 of “Linux,” and people <a href="#distronames">understand 1013 it that way</a>. 1014 1015 <p> 1016 If they called a GNU/Linux distro “Foobar BSD,” you would 1017 call that a mistake. “This system is not BSD,” you 1018 would tell them. Well, it's not Linux either.</p> 1019 </dd> 1020 1021 <dt id="distronames">My distro is called 1022 “Foobar Linux”; doesn't that show it's really Linux? <span class="anchor-reference-id">(<a href="#distronames">#distronames</a>)</span></dt> 1023 1024 <dd> 1025 <p>It means that the people who make the “Foobar Linux” distro are 1026 repeating the common mistake. We appreciate that distributions like Debian, Dragora, Musix, Trisquel, and Venenux have adopted 1027 GNU/Linux as part of their official name, and we hope that if you are involved with a different distribution, you will 1028 encourage it to do the same.</p> 1029 </dd> 1030 1031 <dt id="distronames1">My distro's official name is “Foobar 1032 Linux”; isn't it wrong to call the distro 1033 anything but “Foobar Linux”? <span class="anchor-reference-id">(<a href="#distronames1">#distronames1</a>)</span></dt> 1034 1035 <dd><p>When they spread misinformation by changing “GNU” 1036 to “Linux,” and call their version of it “Foobar 1037 Linux,” it's proper for you to correct the misinformation by 1038 calling it “Foobar GNU/Linux.”</p></dd> 1039 1040 <dt id="companies">Wouldn't it be more 1041 effective to ask companies such as Mandrake, Red Hat and IBM to 1042 call their distributions “GNU/Linux” rather than asking 1043 individuals? <span class="anchor-reference-id">(<a href="#companies">#companies</a>)</span></dt> 1044 1045 <dd> 1046 It isn't a choice of one or the other—we ask companies and 1047 organizations and individuals to help spread the word about this. In 1048 fact, we have asked all three of those companies. Mandrake said it 1049 would use the term “GNU/Linux” some of the time, but IBM 1050 and Red Hat were unwilling to help. One executive said, “This 1051 is a pure commercial decision; we expect to make more money calling it 1052 ‘Linux’.” In other words, that company did not care 1053 what was right. 1054 <p> 1055 We can't make them do this right, but we're not the sort to give up 1056 just because the road isn't easy. You may not have as much influence 1057 at your disposal as IBM or Red Hat, but you can still help. Together 1058 we can change the situation to the point where companies will make 1059 more profit calling it “GNU/Linux.”</p> 1060 </dd> 1061 1062 <dt id="reserve">Wouldn't it be better to 1063 reserve the name “GNU/Linux” for distributions that are purely 1064 free software? After all, that is the ideal of GNU. <span class="anchor-reference-id">(<a href="#reserve">#reserve</a>)</span></dt> 1065 1066 <dd> 1067 The widespread practice of adding nonfree software to the GNU/Linux 1068 system is a major problem for our community. It teaches the users 1069 that nonfree software is ok, and that using it is part of the spirit 1070 of “Linux.” Many “Linux” User Groups make it part of their mission to 1071 help users use nonfree add-ons, and may even invite salesmen to come 1072 and make sales pitches for them. They adopt goals such as “helping 1073 the users” of GNU/Linux (including helping them use nonfree 1074 applications and drivers), or making the system more popular even at 1075 the cost of freedom. 1076 <p> 1077 The question is how to try to change this.</p> 1078 <p> 1079 Given that most of the community which uses GNU with Linux already 1080 does not realize that's what it is, for us to disown these adulterated 1081 versions, saying they are not really GNU, would not teach the users to 1082 value freedom more. They would not get the intended message. They 1083 would only respond they never thought these systems were GNU in the 1084 first place.</p> 1085 <p> 1086 The way to lead these users to see a connection with freedom is 1087 exactly the opposite: to inform them that all these system 1088 versions <em>are</em> versions of GNU, that they all are based on a 1089 system that exists specifically for the sake of the users' freedom. 1090 With this understanding, they can start to recognize the distributions 1091 that include nonfree software as perverted, adulterated versions of 1092 GNU, instead of thinking they are proper and appropriate “versions of 1093 Linux.”</p> 1094 <p> 1095 It is very useful to start GNU/Linux User Groups, which call the 1096 system GNU/Linux and adopt the ideals of the GNU Project as a basis 1097 for their activities. If the Linux User Group in your area has the 1098 problems described above, we suggest you either campaign within the 1099 group to change its orientation (and name) or start a new group. The 1100 people who focus on the more superficial goals have a right to their 1101 views, but don't let them drag you along!</p> 1102 </dd> 1103 1104 <dt id="gnudist">Why not make a GNU 1105 distribution of Linux (sic) and call that GNU/Linux? <span class="anchor-reference-id">(<a href="#gnudist">#gnudist</a>)</span></dt> 1106 1107 <dd> 1108 All the “Linux” distributions are actually versions of the GNU system 1109 with Linux as the kernel. The purpose of the term “GNU/Linux” is to 1110 communicate this point. To develop one new distribution and call that 1111 alone “GNU/Linux” would obscure the point we want to make. 1112 <p> 1113 As for developing a distribution of GNU/Linux, we already did this 1114 once, when we funded the early development of Debian GNU/Linux. To do 1115 it again now does not seem useful; it would be a lot of work, and 1116 unless the new distribution had substantial practical advantages over 1117 other distributions, it would serve no purpose.</p> 1118 <p> 1119 Instead we help the developers of 100% free GNU/Linux distributions, 1120 such as Trisquel and Parabola.</p> 1121 </dd> 1122 1123 <dt id="linuxgnu">Why not just say “Linux is 1124 the GNU kernel” and release some existing version of GNU/Linux under 1125 the name “GNU”? <span class="anchor-reference-id">(<a href="#linuxgnu">#linuxgnu</a>)</span></dt> 1126 1127 <dd> 1128 It might have been a good idea to adopt Linux as the GNU kernel back 1129 in 1992. If we had realized, then, how long it would take to get the 1130 GNU Hurd to work, we might have done that. (Alas, that is hindsight.) 1131 <p> 1132 If we were to take an existing version of GNU/Linux and relabel it as 1133 “GNU,” that would be somewhat like making a version of the GNU system 1134 and labeling it “Linux.” That wasn't right, and we don't 1135 want to act like that.</p> 1136 </dd> 1137 1138 <dt id="condemn">Did the GNU Project condemn 1139 and oppose use of Linux in the early days? <span class="anchor-reference-id">(<a href="#condemn">#condemn</a>)</span></dt> 1140 1141 <dd> 1142 We did not adopt Linux as our kernel, but we didn't condemn or oppose 1143 it. In 1993 we started discussing the arrangements to sponsor the 1144 development of Debian GNU/Linux. We also sought to cooperate with the 1145 people who were changing some GNU packages for use with Linux. We 1146 wanted to include their changes in the standard releases so that these 1147 GNU packages would work out-of-the-box in combination with Linux. But 1148 the changes were often ad-hoc and nonportable; they needed to be cleaned 1149 up for installation. 1150 <p> 1151 The people who had made the changes showed little interest in 1152 cooperating with us. One of them actually told us that he didn't care 1153 about working with the GNU Project because he was a “Linux user.” 1154 That came as a shock, because the people who ported GNU packages to 1155 other systems had generally wanted to work with us to get their 1156 changes installed. Yet these people, developing a system that was 1157 primarily based on GNU, were the first (and still practically the 1158 only) group that was unwilling to work with us.</p> 1159 <p> 1160 It was this experience that first showed us that people were calling a 1161 version of the GNU system “Linux,” and that this confusion was 1162 obstructing our work. Asking you to call the system “GNU/Linux” is 1163 our response to that problem, and to the other problems caused by the 1164 “Linux” misnomer.</p> 1165 </dd> 1166 1167 <dt id="wait">Why did you wait so 1168 long before asking people to use the name GNU/Linux? <span class="anchor-reference-id">(<a href="#wait">#wait</a>)</span></dt> 1169 1170 <dd> 1171 <p>Actually we didn't. We began talking privately with developers and 1172 distributors about this in 1994, and made a more public campaign in 1173 1996. We will continue for as long as it's necessary.</p> 1174 </dd> 1175 1176 <dt id="allgpled">Should the GNU/<i>name</i> 1177 convention be applied to all programs that are GPL'ed? <span class="anchor-reference-id">(<a href="#allgpled">#allgpled</a>)</span></dt> 1178 1179 <dd> 1180 We never refer to individual programs as “GNU/<i>name</i>.” When a program 1181 is a GNU package, we may call it “GNU <i>name</i>.” 1182 <p> 1183 GNU, the operating system, is made up of many different programs. 1184 Some of the programs in GNU were written as part of the GNU Project or 1185 specifically contributed to it; these are the GNU packages, and we 1186 often use “GNU” in their names.</p> 1187 <p> 1188 It's up to the developers of a program to decide if they want to contribute 1189 it and make it a GNU package. If you have developed a program and you 1190 would like it to be a GNU package, please write to 1191 <a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>, so we can evaluate it 1192 and decide whether we want it.</p> 1193 <p> 1194 It wouldn't be fair to put the name GNU on every individual program 1195 that is released under the GPL. If you write a program and release it 1196 under the GPL, that doesn't mean the GNU Project wrote it or that you 1197 wrote it for us. For instance, the kernel, Linux, is released under 1198 the GNU GPL, but Linus did not write it as part of the GNU Project—he 1199 did the work independently. If something is not a GNU package, the 1200 GNU Project can't take credit for it, and putting “GNU” in its name 1201 would be improper.</p> 1202 <p> 1203 In contrast, we do deserve the overall credit for the GNU operating 1204 system as a whole, even though not for each and every program in it. 1205 The system exists as a system because of our determination and 1206 persistence, starting in 1984, many years before Linux was begun.</p> 1207 <p> 1208 The operating system in which Linux became popular was basically the 1209 same as the GNU operating system. It was not entirely the same, 1210 because it had a different kernel, but it was mostly the same system. 1211 It was a variant of GNU. It was the GNU/Linux system.</p> 1212 <p> 1213 Linux continues to be used primarily in derivatives of that system—in 1214 today's versions of the GNU/Linux system. What gives these systems 1215 their identity is GNU and Linux at the center of them, not particularly 1216 Linux alone.</p> 1217 </dd> 1218 1219 <dt id="unix">Since much of GNU comes 1220 from Unix, shouldn't GNU give credit 1221 to Unix by using “Unix” in its name? <span class="anchor-reference-id">(<a href="#unix">#unix</a>)</span></dt> 1222 1223 <dd> 1224 Actually, none of GNU comes from Unix. Unix was proprietary software 1225 (and still is), so using any of its code in GNU would have been 1226 illegal. This is not a coincidence; this is why we developed GNU: 1227 since you could not have freedom in using Unix, or any of the other 1228 operating systems of the day, we needed a free system to replace it. 1229 We could not copy programs, or even parts of them, from Unix; 1230 everything had to be written afresh. 1231 <p> 1232 No code in GNU comes from Unix, but GNU is a Unix-compatible system; 1233 therefore, many of the ideas and specifications of GNU do come from 1234 Unix. The name “GNU,” which stands for “GNU's Not 1235 Unix,” is a humorous way of giving credit to Unix for this, 1236 following a hacker tradition of recursive acronyms that started in the 1237 70s.</p> 1238 <p> 1239 The first such recursive acronym was TINT, “TINT Is Not 1240 TECO.” The author of TINT wrote another implementation of TECO 1241 (there were already many of them, for various systems), but instead of 1242 calling it by a dull name like “<em>somethingorother</em> TECO,” he 1243 thought of a clever amusing name. (That's what hacking 1244 means: <a href="https://stallman.org/articles/on-hacking.html">playful 1245 cleverness</a>.)</p> 1246 <p> 1247 Other hackers enjoyed that name so much that we imitated the approach. 1248 It became a tradition that, when you were writing from scratch a 1249 program that was similar to some existing program (let's imagine its 1250 name was “Klever”), you could give it a recursive acronym name, such 1251 as “MINK” for “MINK Is Not Klever.” In this same spirit we called our 1252 replacement for Unix “GNU's Not Unix.”</p> 1253 <p> 1254 Historically, AT&T which developed Unix did not want anyone to 1255 give it credit by using “Unix” in the name of a similar 1256 system, not even in a system 99% copied from Unix. AT&T actually 1257 threatened to sue anyone giving AT&T credit in that way. This is 1258 why each of the various modified versions of Unix (all proprietary, 1259 like Unix) had a completely different name that didn't include 1260 “Unix.”</p> 1261 </dd> 1262 1263 <dt id="bsd">Should we say “GNU/BSD” 1264 too? <span class="anchor-reference-id">(<a href="#bsd">#bsd</a>)</span></dt> 1265 1266 <dd> 1267 We don't call the BSD systems (FreeBSD, etc.) “GNU/BSD” systems, 1268 because that term does not fit the history of the BSD systems. 1269 <p> 1270 The BSD system was developed by UC Berkeley as nonfree software in 1271 the 80s, and became free in the early 90s. A free operating system 1272 that exists today is almost certainly either a variant of the GNU 1273 system, or a kind of BSD system.</p> 1274 <p> 1275 People sometimes ask whether BSD too is a variant of GNU, as GNU/Linux 1276 is. It is not. The BSD developers were inspired to make their code 1277 free software by the example of the GNU Project, and explicit appeals 1278 from GNU activists helped convince them to start, but the code had 1279 little overlap with GNU.</p> 1280 <p> 1281 BSD systems today use some GNU packages, just as the GNU system and 1282 its variants use some BSD programs; however, taken as wholes, they are 1283 two different systems that evolved separately. The BSD developers did 1284 not write a kernel and add it to the GNU system, so a name like 1285 GNU/BSD would not fit the situation.</p> 1286 <p> 1287 The connection between GNU/Linux and GNU is much closer, and that's 1288 why the name “GNU/Linux” is appropriate for it.</p> 1289 <p> 1290 There is a version of GNU which uses the kernel from NetBSD. Its 1291 developers call it “Debian GNU/NetBSD,” but “GNU/kernelofNetBSD” 1292 would be more accurate, since NetBSD is an entire system, not just 1293 the kernel. This is not a BSD system, since most of the system 1294 is the same as the GNU/Linux system.</p> 1295 </dd> 1296 1297 <dt id="othersys">If I install the GNU tools 1298 on Windows, does that mean I am running a GNU/Windows system? <span class="anchor-reference-id">(<a href="#othersys">#othersys</a>)</span></dt> 1299 1300 <dd> 1301 <p> 1302 Not in the same sense that we mean by “GNU/Linux.” The tools of GNU 1303 are just a part of the GNU software, which is just a part of the GNU 1304 system, and underneath them you would still have another complete 1305 operating system which has no code in common with GNU. All in all, 1306 that's a very different situation from GNU/Linux.</p> 1307 </dd> 1308 1309 <dt id="justlinux">Can't Linux be used without GNU? <span class="anchor-reference-id">(<a href="#justlinux">#justlinux</a>)</span></dt> 1310 1311 <dd> 1312 <p> 1313 Linux is used by itself, or with small other programs, in some 1314 appliances. These small software systems are a far cry from the 1315 GNU/Linux system. Users do not install them on PCs, for instance, and 1316 would find them rather disappointing. It is useful to say that these 1317 appliances run just Linux, to show how different those small platforms 1318 are from GNU/Linux.</p> 1319 </dd> 1320 1321 <dt id="howmuch">How much of the GNU system is needed for the system 1322 to be 1323 GNU/Linux? <span class="anchor-reference-id">(<a href="#howmuch">#howmuch</a>)</span></dt> 1324 1325 <dd> 1326 “How much” is not a meaningful question because the GNU 1327 system does not have precise boundaries. 1328 <p> 1329 GNU is an operating system maintained by a community. It includes far 1330 more than just the GNU software packages (of which we have a specific 1331 list), and people add more packages constantly. Despite these 1332 changes, it remains the GNU system, and adding Linux to that yields 1333 GNU/Linux. If you use part of the GNU system and omit part, there is 1334 no meaningful way to say “how much” you used.</p> 1335 <p> 1336 If we look at the level of packages, Linux is one important package in 1337 the GNU/Linux system. The inclusion of one important GNU package is 1338 enough to justify our request for equal mention. 1339 </p> 1340 </dd> 1341 1342 <dt id="linuxsyswithoutgnu">Are there complete Linux systems [sic] without GNU? <span class="anchor-reference-id">(<a href="#linuxsyswithoutgnu">#linuxsyswithoutgnu</a>)</span></dt> 1343 1344 <dd> 1345 There are complete systems that contain Linux and not GNU; Android is 1346 an example. But it is a mistake to call them “Linux” 1347 systems, just as it is a mistake to call GNU a “Linux” system. 1348 <p> 1349 Android is very different from the GNU/Linux system—because 1350 the two have very little code in common. In fact, the only thing they 1351 have in common is Linux.</p> 1352 <p> 1353 If you call the whole GNU/Linux system “Linux,” 1354 you will find it necessary to say things like, “Android contains 1355 Linux, but it isn't Linux, because it doesn't have the usual Linux 1356 [sic] libraries and utilities [meaning the GNU system].”</p> 1357 <p> 1358 Android contains just as much of Linux as GNU/Linux does. What it 1359 doesn't have is the GNU system. Android replaces that with Google 1360 software that works quite differently. What makes Android different 1361 from GNU/Linux is the absence of GNU.</p> 1362 </dd> 1363 1364 <dt id="usegnulinuxandandroid">Is it correct to say “using Linux” if it refers to using GNU/Linux and 1365 using Android? <span class="anchor-reference-id">(<a href="#usegnulinuxandandroidlinuxsyswithoutgnu">#usegnulinuxandandroidlinuxsyswithoutgnu</a>)</span></dt> 1366 1367 <dd> 1368 Far from it. That usage is so strained that 1369 people will not understand the intended meaning. 1370 <p> 1371 The public will find it very strange to speak of using Android as 1372 “using Linux.” It's like having a conversation, then 1373 saying you were conversing with the person's intestines or the 1374 person's circulatory system.</p> 1375 <p> 1376 The public <em>will</em> understand the idea of “using 1377 Linux” when it's really GNU/Linux, by way of the usual 1378 misunderstanding: thinking of the whole system as 1379 “Linux.”</p> 1380 <p> 1381 Use of Android and use of GNU/Linux are totally different, as 1382 different as driving a car and riding a bicycle. The fact that the 1383 first two both contain Linux is irrelevant to using them, just as the 1384 fact that a car and a bicycle both have a structure of metal is 1385 irrelevant to using those two. If you wish to talk about using cars 1386 and bikes, you wouldn't speak of “riding metal objects”—not 1387 unless you're playing games with the reader. You would 1388 say, “using cars and bikes.” Likewise, the clear way to 1389 talk about using GNU/Linux and Android is to say “using 1390 GNU/Linux and Android.”</p> 1391 </dd> 1392 1393 <dt id="helplinus">Why not call the system 1394 “Linux” anyway, and strengthen Linus Torvalds' role as posterboy for our 1395 community? <span class="anchor-reference-id">(<a href="#helplinus">#helplinus</a>)</span></dt> 1396 1397 <dd> 1398 Linus Torvalds is the “posterboy” (other people's choice of word, not 1399 ours) for his goals, not ours. His goal is to make the system more 1400 popular, and he believes its value to society lies merely in the 1401 practical advantages it offers: its power, reliability and easy 1402 availability. He has never advocated 1403 <a href="/philosophy/why-free.html">freedom to cooperate</a> as an 1404 ethical principle, which is why the public does not connect the name 1405 “Linux” with that principle. 1406 <p> 1407 Linus publicly states his disagreement with the free software 1408 movement's ideals. He developed nonfree software in his job for many 1409 years (and said so to a large audience at a “Linux”World show), and 1410 publicly invited fellow developers of Linux, the kernel, to use 1411 nonfree software to work on it with him. He goes even further, and 1412 rebukes people who suggest that engineers and scientists should 1413 consider social consequences of our technical work—rejecting the 1414 lessons society learned from the development of the atom bomb.</p> 1415 <p> 1416 There is nothing wrong with writing a free program for the motivations 1417 of learning and having fun; the kernel Linus wrote for those reasons 1418 was an important contribution to our community. But those motivations 1419 are not the reason why the complete free system, GNU/Linux, exists, 1420 and they won't secure our freedom in the future. The public needs to 1421 know this. Linus has the right to promote his views; however, people 1422 should be aware that the operating system in question 1423 stems from ideals of freedom, not from his views.</p> 1424 </dd> 1425 1426 <dt id="claimlinux">Isn't it wrong for us to label Linus Torvalds' 1427 work as GNU? <span class="anchor-reference-id">(<a href="#claimlinux">#claimlinux</a>)</span></dt> 1428 1429 <dd> 1430 <p> 1431 It would be wrong, so we don't do that. Torvalds' work is Linux, the 1432 kernel; we are careful not to attribute that work to the GNU Project 1433 or label it as “GNU.” When we talk about the whole 1434 system, the name “GNU/Linux” gives him a share of the 1435 credit.</p> 1436 </dd> 1437 1438 1439 <dt id="linusagreed">Does Linus Torvalds 1440 agree that Linux is just the kernel? <span class="anchor-reference-id">(<a href="#linusagreed">#linusagreed</a>)</span></dt> 1441 1442 <dd> 1443 <p>He recognized this at the beginning. The <a 1444 href="https://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> 1445 earliest Linux release notes</a> said:</p> 1446 <blockquote><p> 1447 Most of the tools used with linux are GNU software and are under the 1448 GNU copyleft. These tools aren't in the distribution - ask me (or GNU) 1449 for more info. 1450 </p></blockquote> 1451 </dd> 1452 1453 <dt id="finishhurd">Why not finish the GNU Hurd kernel, release the GNU system 1454 as a whole, and forget the question of what to call GNU/Linux? 1455 <span class="anchor-reference-id">(<a href="#finishhurd">#finishhurd</a>)</span></dt> 1456 1457 <dd> 1458 We would like credit for the GNU operating system no matter which 1459 kernel is used with it. 1460 1461 <p>Making the GNU Hurd work well enough to compete with Linux would be 1462 a big job, and it's not clearly necessary. The only thing ethically 1463 wrong with Linux as a kernel is its inclusion of firmware 1464 “blobs”; the best fix for that problem 1465 is <a href="https://www.fsf.org/campaigns/priority-projects"> developing 1466 free replacement for the blobs</a>.</p> 1467 </dd> 1468 1469 <dt id="lost">The battle is already lost—society 1470 has made its decision and we can't change it, so why even think about 1471 it? <span class="anchor-reference-id">(<a href="#lost">#lost</a>)</span></dt> 1472 1473 <dd> 1474 <p> 1475 This isn't a battle, it is a campaign of education. What to call the 1476 system is not a single decision, to be made at one moment by 1477 “society”: each person, each organization, can decide what 1478 name to use. You can't make others say “GNU/Linux,” but 1479 you can decide to call the system “GNU/Linux” 1480 yourself—and by doing so, you will help educate others.</p> 1481 </dd> 1482 1483 <dt id="whatgood">Society has made its 1484 decision and we can't change it, so what good does it do if I say 1485 “GNU/Linux”? <span class="anchor-reference-id">(<a href="#whatgood">#whatgood</a>)</span></dt> 1486 1487 <dd> 1488 <p> 1489 This is not an all-or-nothing situation: correct and incorrect 1490 pictures are being spread more or less by various people. If you call 1491 the system “GNU/Linux,” you will help others learn the system's true 1492 history, origin, and reason for being. You can't correct the misnomer 1493 everywhere on your own, any more than we can, but you can help. If 1494 only a few hundred people see you use the term “GNU/Linux,” you will 1495 have educated a substantial number of people with very little work. 1496 And some of them will spread the correction to others.</p> 1497 </dd> 1498 1499 <dt id="explain">Wouldn't it be better to call 1500 the system “Linux” and teach people its real origin with a ten-minute 1501 explanation? <span class="anchor-reference-id">(<a href="#explain">#explain</a>)</span></dt> 1502 1503 <dd> 1504 If you help us by explaining to others in that way, we appreciate your 1505 effort, but that is not the best method. It is not as effective as 1506 calling the system “GNU/Linux,” and uses your time inefficiently. 1507 <p> 1508 It is ineffective because it may not sink in, and surely will not 1509 propagate. Some of the people who hear your explanation will pay 1510 attention, and they may learn a correct picture of the system's 1511 origin. But they are unlikely to repeat the explanation to others 1512 whenever they talk about the system. They will probably just call it 1513 “Linux.” Without particularly intending to, they will help spread the 1514 incorrect picture.</p> 1515 <p> 1516 It is inefficient because it takes a lot more time. Saying and 1517 writing “GNU/Linux” will take you only a few seconds a day, not 1518 minutes, so you can afford to reach far more people that way. 1519 Distinguishing between Linux and GNU/Linux when you write and speak is 1520 by far the easiest way to help the GNU Project effectively.</p> 1521 </dd> 1522 1523 <dt id="treatment">Some people laugh at you 1524 when you ask them to call the system GNU/Linux. Why do you subject 1525 yourself to this treatment? <span class="anchor-reference-id">(<a href="#treatment">#treatment</a>)</span></dt> 1526 1527 <dd> 1528 Calling the system “Linux” tends to give people a mistaken picture of 1529 the system's history and reason for existence. People who laugh at 1530 our request probably have picked up that mistaken picture—they think 1531 our work was done by Linus, so they laugh when we ask for credit for 1532 it. If they knew the truth, they probably wouldn't laugh. 1533 <p> 1534 Why do we take the risk of making a request that sometimes leads 1535 people to ridicule us? Because often it has useful results that help 1536 the GNU Project. We will run the risk of undeserved abuse to achieve 1537 our goals.</p> 1538 <p> 1539 If you see such an ironically unfair situation occurring, please don't 1540 sit idly by. Please teach the laughing people the real history. When 1541 they see why the request is justified, those who have any sense will 1542 stop laughing.</p> 1543 </dd> 1544 1545 <dt id="alienate">Some people condemn you 1546 when you ask them to call the system GNU/Linux. Don't you lose by 1547 alienating them? <span class="anchor-reference-id">(<a href="#alienate">#alienate</a>)</span></dt> 1548 1549 <dd> 1550 Not much. People who don't appreciate our role in developing the 1551 system are unlikely to make substantial efforts to help us. If they 1552 do work that advances our goals, such as releasing free software, it 1553 is probably for other unrelated reasons, not because we asked them. 1554 Meanwhile, by teaching others to attribute our work to someone else, 1555 they are undermining our ability to recruit the help of others. 1556 <p> 1557 It makes no sense to worry about alienating people who are already 1558 mostly uncooperative, and it is self-defeating to be deterred from 1559 correcting a major problem lest we anger the people who perpetuate it. 1560 Therefore, we will continue trying to correct the misnomer.</p> 1561 </dd> 1562 1563 <dt id="rename">Whatever you contributed, 1564 is it legitimate to rename the operating system? <span class="anchor-reference-id">(<a href="#rename">#rename</a>)</span></dt> 1565 1566 <dd> 1567 <p> 1568 We are not renaming anything; we have been calling this system “GNU” 1569 ever since we announced it in 1983. The people who tried to rename 1570 it to “Linux” should not have done so.</p> 1571 </dd> 1572 1573 <dt id="force">Isn't it wrong to force people to call 1574 the system “GNU/Linux”? <span class="anchor-reference-id">(<a href="#force">#force</a>)</span></dt> 1575 1576 <dd> 1577 <p> 1578 It would be wrong to force them, and we don't try. We call the system 1579 “GNU/Linux,” and we ask you to do it too.</p> 1580 </dd> 1581 1582 <dt id="whynotsue">Why not sue people who call 1583 the whole system “Linux”? <span class="anchor-reference-id">(<a href="#whynotsue">#whynotsue</a>)</span></dt> 1584 1585 <dd> 1586 <p> 1587 There are no legal grounds to sue them, but since we believe in 1588 freedom of speech, we wouldn't want to do that anyway. We ask people 1589 to call the system “GNU/Linux” because that is the right thing to do.</p> 1590 </dd> 1591 1592 <dt id="require">Shouldn't you put something in 1593 the GNU GPL to require people to call the system “GNU”? <span class="anchor-reference-id">(<a href="#require">#require</a>)</span></dt> 1594 1595 <dd> 1596 <p> 1597 The purpose of the GNU GPL is to protect the users' freedom from those 1598 who would make proprietary versions of free software. While it is 1599 true that those who call the system “Linux” often do things that limit 1600 the users' freedom, such as bundling nonfree software with the 1601 GNU/Linux system or even developing nonfree software for such use, 1602 the mere act of calling the system “Linux” does not, in itself, deny 1603 users their freedom. It seems improper to make the GPL restrict what 1604 name people can use for the system.</p> 1605 </dd> 1606 1607 <dt id="BSDlicense">Since you objected to the original BSD license's 1608 advertising requirement to give credit to the University of California, 1609 isn't it hypocritical to demand credit for the GNU project? <span class="anchor-reference-id">(<a href="#BSDlicense">#BSDlicense</a>)</span></dt> 1610 1611 <dd> 1612 It would be hypocritical to make the name GNU/Linux a license 1613 requirement, and we don't. We only <em>ask</em> you to give us the 1614 credit we deserve. 1615 1616 <p> 1617 Please note that there are at least <a href="/licenses/bsd.html"> 1618 two different BSD licenses</a>. For clarity's sake, please don't use 1619 the term “BSD license” without specifying which one.</p> 1620 </dd> 1621 1622 <dt id="deserve">Since you failed to put 1623 something in the GNU GPL to require people to call the system “GNU,” 1624 you deserve what happened; why are you complaining now? <span class="anchor-reference-id">(<a href="#deserve">#deserve</a>)</span></dt> 1625 1626 <dd> 1627 The question presupposes a rather controversial general ethical 1628 premise: that if people do not force you to treat them fairly, you are 1629 entitled to take advantage of them as much as you like. In other 1630 words, it assumes that might makes right. 1631 <p> 1632 We hope you disagree with that premise just as we do.</p> 1633 </dd> 1634 1635 <dt id="contradict">Wouldn't you be better 1636 off not contradicting what so many people believe? <span class="anchor-reference-id">(<a href="#contradict">#contradict</a>)</span></dt> 1637 1638 <dd> 1639 We don't think we should go along with large numbers of people because 1640 they have been misled. We hope you too will decide that truth is 1641 important. 1642 <p> 1643 We could never have developed a free operating system without first 1644 denying the belief, held by most people, that proprietary software 1645 was legitimate and acceptable.</p> 1646 </dd> 1647 1648 <dt id="somanyright">Since many people call 1649 it “Linux,” doesn't that make it right? <span class="anchor-reference-id">(<a href="#somanyright">#somanyright</a>)</span></dt> 1650 1651 <dd> 1652 <p> 1653 We don't think that the popularity of an error makes it the truth.</p> 1654 </dd> 1655 1656 <dt id="knownname">Isn't it better to call the 1657 system by the name most users already know? <span class="anchor-reference-id">(<a href="#knownname">#knownname</a>)</span></dt> 1658 1659 <dd> 1660 <p> 1661 Users are not incapable of learning. Since “GNU/Linux” 1662 includes “Linux,” they will recognize what you're talking 1663 about. If you add “(often erroneously referred to as 1664 ‘Linux’)” once in a while, they will all understand.</p> 1665 </dd> 1666 1667 <dt id="winning">Many people care about what's 1668 convenient or who's winning, not about arguments of right or wrong. 1669 Couldn't you get more of their support by a different 1670 road? <span class="anchor-reference-id">(<a href="#winning">#winning</a>)</span></dt> 1671 1672 <dd> 1673 To care only about what's convenient or who's winning is an amoral 1674 approach to life. Nonfree software is an example of that amoral 1675 approach and thrives on it. Thus, in the long run it would be 1676 self-defeating for us to adopt that approach. We will continue 1677 talking in terms of right and wrong. 1678 <p> 1679 We hope that you are one of those for whom right and wrong do matter.</p> 1680 </dd> 1681 1682 </dl> 1683 </div> 1684 1685 </div><!-- for id="content", starts in the include above --> 1686 <!--#include virtual="/server/footer.html" --> 1687 <div id="footer" role="contentinfo"> 1688 <div class="unprintable"> 1689 1690 <p>Please send general FSF & GNU inquiries to 1691 <a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>. 1692 There are also <a href="/contact/">other ways to contact</a> 1693 the FSF. Broken links and other corrections or suggestions can be sent 1694 to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p> 1695 1696 <p><!-- TRANSLATORS: Ignore the original text in this paragraph, 1697 replace it with the translation of these two: 1698 1699 We work hard and do our best to provide accurate, good quality 1700 translations. However, we are not exempt from imperfection. 1701 Please send your comments and general suggestions in this regard 1702 to <a href="mailto:web-translators@gnu.org"> 1703 <web-translators@gnu.org></a>.</p> 1704 1705 <p>For information on coordinating and contributing translations of 1706 our web pages, see <a 1707 href="/server/standards/README.translations.html">Translations 1708 README</a>. --> 1709 Please see the <a 1710 href="/server/standards/README.translations.html">Translations 1711 README</a> for information on coordinating and contributing translations 1712 of this article.</p> 1713 </div> 1714 1715 <!-- Regarding copyright, in general, standalone pages (as opposed to 1716 files generated as part of manuals) on the GNU web server should 1717 be under CC BY-ND 4.0. Please do NOT change or remove this 1718 without talking with the webmasters or licensing team first. 1719 Please make sure the copyright date is consistent with the 1720 document. For web pages, it is ok to list just the latest year the 1721 document was modified, or published. 1722 1723 If you wish to list earlier years, that is ok too. 1724 Either "2001, 2002, 2003" or "2001-2003" are ok for specifying 1725 years, as long as each year in the range is in fact a copyrightable 1726 year, i.e., a year in which the document was published (including 1727 being publicly visible on the web or in a revision control system). 1728 1729 There is more detail about copyright years in the GNU Maintainers 1730 Information document, www.gnu.org/prep/maintain. --> 1731 1732 <p>Copyright © 2001-2011, 2013-2018, 2020, 2022 1733 Free Software Foundation, Inc.</p> 1734 1735 <p>This page is licensed under a <a rel="license" 1736 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative 1737 Commons Attribution-NoDerivatives 4.0 International License</a>.</p> 1738 1739 <!--#include virtual="/server/bottom-notes.html" --> 1740 1741 <p class="unprintable">Updated: 1742 <!-- timestamp start --> 1743 $Date: 2022/07/27 07:00:34 $ 1744 <!-- timestamp end --> 1745 </p> 1746 </div> 1747 </div><!-- for class="inner", starts in the banner include --> 1748 </body> 1749 </html>