Non-GNU Linux
by
sfraggle
·
· Score: 4, Informative
I have a small linux distribution for the Psion Revo. Interestingly, I can name this just Linux (not GNU/Linux) because it contains no GNU software. All the normal GNU base utilities (glibc, gnu text/shellutils, bash) have been replaced with small embedded replacements (uclibc, busybox). So I can leave off "GNU/" and I am still correct.
-- were you expecting to see a sig here? perhaps you'd rather see the inside of an ambulance!
Re:Non-GNU Linux
by
wfrp01
·
· Score: 4, Insightful
I can name this just Linux (not GNU/Linux) because it contains no GNU software.
But you're missing the main point. The point is not that the OS contains a whole bunch of GNU components, so therefore you owe the FSF fealty. If that were the point, than as many have (incorrectly) pointed out, it would be equally valid to request the system be called Perl/Linux, etc.
Whether or not your system is built using GNU components, you still owe the FSF a debt of gratitude for promoting free software. Or did you put your system together from scratch? You did not: you're using busybox, for example, which is licenced under the GPL.
While there are many organizations which produce free software, which organizations do you look to unswervingly promote the ideals of software freedom? The FSF.
Again, the FSF is not asking you to use GNU/Linux out of respect for the amount of code they gave you. They want you to use the name GNU/Linux to increase awareness of the principle of software freedom on which your OS is based.
Also remember - it's just a request. Not a demand. Not a EULA. Not a law. Nothing to lose sleep over.
If the list truly was a faq, top of the list, to my mind (well, okay, second to 'what the hell are you thinking') would be 'how do you pronounce gnu/linux?'
If memory serves, RMS pronounced it guh-new-slash-linux; if I remember correctly, there's yet another compelling reason to pronounce it with a silent gnu.
Wouldn't a GNU OS need to "...be a kernel plus all the utilities needed to write and run C programs..."?
Since the Linux kernel is copyrighted by "me [Linus Torvalds] and others who actually wrote it.", wouldn't it rightfully not be the incarnation of the GNU project as envisioned by RMS nearly 19 years ago. Mach + the GNU tools, sure, but not Linux + the GNU tools.
Stallman sits in a basement, arguing with himself. He then writes the argument out (bad grammer and all - maybe he should have used a Microsoft product with helpful features like spell check and grammer check.) Finally, the dopes^H^H^H^H^Hfine people at Slashdot decide to give the fool an even bigger audience. *sigh*
What is a bigger waste of the Internet? Stallman's rants or those Bumfight tapes?
GNU: Get over it
by
Neil+Watson
·
· Score: 4, Interesting
Wah! wah! wah! call it by my name or I'm taking my toys and going home.
No one is denying the great tools that GNU provides. I always install various GNU tools on the Sun boxes I work on to keep me from going crazy. Stop acting so childish. It's this kind of behavior that can give Open Source a reputation of being a bunch of "childish geeks."
I call it linux, here's why, in a few short points
by
intermodal
·
· Score: 5, Insightful
1: because Linus does 2: Because Linus succeeded where GNU failed 3: Because GNU/Linux is too damn long to say 4: Because I don't call programs made/depending on MS Visual Studio 6 "MSVS/[program name]" 5: and finally, because Linux is common usage as the name of the OS. This is like trying to force the metric system on me when everything around me right down to my car's odometer is in miles. Let Stallman seethe in his jealous corner...I respect what he's done in creating the FSF, but that doesnt make me want to pander to his ego.
Re:Why are they so desperate ?
by
(void*)
·
· Score: 5, Insightful
I don't understand why people keep attributing motives and emotions to an organization like the FSF. FSF wrote a lot of GNU tools like gzip, sed, cat. They consciously set out to duplicate each and every piece of the software on Unix, whether it was glamorous work or not.
Now that they've done it, I have no problems giving them a little credit by typiing GNU/Linux, but still using "Lih-nooks" conversationally. Why is spelling things this way hard? It would be hard to write an emacs Macro that inserted "GNU" everytime one typed "Linux".
Heck, if one think this is petty, then it's even pettier to complain about the pettiness. (And I know what I just did: complain about your pettiness. So there!)
Take a page from Mozilla...
by
Craig+Maloney
·
· Score: 4, Funny
Remember, the correct pronunciation of Netcape is "Mozilla". Why can't the correct pronunciation of GNU/Linux be "Linux"? Oh, I forgot... the GNU is never silent.:)
However, there are people who do not like our saying this. Sometimes those people push us away in response. On occasion they are so rude that one wonders if they are intentionally trying to intimidate us into silence. It doesn't silence us, but it does tend to divide the community, so we hope you can convince them to stop.
If this isn't evidence of Stallman's mental illness, I don't know what is. Oh, the problem isn't with us, it's with everyone else. We insist that people use this ludicrous name that no one can cleanly pronounce, and if anyone disagrees, clearly they are dividing the community.
In other words, "if everyone would just agree with us, then there would be no disagreement". Well, no shit.
Stallman, how about this: you call it whatever you want. And how about respecting other people's decision on what they want to call it, and stop notoriously refusing to talk to anyone who disagrees with you.
-- Sometimes it's best to just let stupid people be stupid.
Re:Absolutely delusional
by
pjrc
·
· Score: 5, Insightful
A man works hard to help other and make the world a better place, with little gain for himself, devoting almost 20 years to a project which eventually leads to a completely free (speech/beer) operating system and applications, and what do people say....
If this isn't evidence of Stallman's mental illness, I don't know what is.
The man's been called crazy by many for a long time now...
In the first 10-12 years when there was not complete workable system, yet he labored away sacrificing personal wealth. A man such as this has a thick skin... you're just not going to phase him with the name "crazy" after others have tried repeatedly for two decades!
Oh, the problem isn't with us, it's with everyone else . We insist that people use this ludicrous name that no one can cleanly pronounce, and if anyone disagrees, clearly they are dividing the community.
The same could, and has many times been said, over the whole debate of the merits of Free vs Proprietary software. Remember, RMS started this whole crazy idea and stuck with it in the early years. Yes, years. Nowadays people regularily talk how GPL's software (or open source) has its advantages and the whole idea appeals to more than a small handful of hackers who easily written off as zealots.
I personally call it "linux" in conversation, and I rarely write GNU/Linux, but I don't say rude things like this:
Stallman, how about this: you call it whatever you want. And how about respecting other people's decision on what they want to call it, and stop notoriously refusing to talk to anyone who disagrees with you.
As an experiment, try this:
Quit your job
Start an overwhelming project, with the overall goal of allowing everyone to have freedom to make changes
Work with little or no pay for almost 20 years
Watch it finally become widely used
Observe people promote it for different reasons than why you started and kept with the project all those years
Listen to people talk about what started as your project, without knowing about you or the ideals you've tried to promote for 20 years
Sit by silently as millions fail to "get it" (the overall purpose, freedom vs proprietary)
Normally I agree with what you say Bruce but in this case no.
No one knows (i.e. the general public or pointy haired bosses) what 'GNU' means anyway and I think its just going to become more of problem as people get confused thinking it's another distro or something.
The solution in this case is to stop this stupid holy war. We have the DMCA, Palladium, and Microsoft to worry about, we don't need to fight amongst ourselves about a name and we need to ignore the select few that are trying to take credit for Linux at the expense of the thousands of people who work on it.
NDAs won't happen as long as the GPL stands up in court. If it doesn't then saying GNU a million times before you say Linux isn't going to stop companies from taking the code.
What about everything else?
by
Wee
·
· Score: 4, Insightful
Say it! GNU/Linux. Be part of the soultion.
But what about everything else that I use on my box? Sure, I use the GNU utils and libs and compiler along with the Linux kernel, but I also use XFree86 as well. In fact, I'd be willing to wager that on my personal desktop machines, what get the most "workout" is X. So why disparage the generous contibution they've made by leaving them out? Now I use an OS called XFree86/GNU/Linux.
But why stop there? I also use KDE extensively. That's in the user's face a lot as well. It's what everyone sees. What a newbie might think is the OS. Why leave them out? My dekstop machines wouldn't be very useful to me without KDE (or any other WM). So now I need KDE/XFree86/GNU/Linux.
I use "The Computers Formally Known As Red Hat and Gentoo" for servers as well. That's a web server and a database typically. I even run these on my "workstations" as low-end test machines. I couldn't get on without Apache and MySQL (and/or PostgreSQL, but we'll simplify). So I need to call it MySQL/Apache/XFree86/GNU/Linux.
Oh wait. Perl and PHP. I can't forget those. Perl/PHP/MySQL/Apache/XFree86/GNU/Linux is what I call my OS now. What about the work Red Hat nas put into my desktop OS? I should mention them as well...
Rinse, lather, repeat.
Ok, so that's all more than slightly contrived. But it illustrates a point: where does one stop with the attributions? I realize that most of the heavy lifting is done by the wonderful work the GNU people have done, and I know that 'Linux' wouldn't be where it is today without all that stuff. But are the GNU utils the tail or the dog? Which wags which? Without the Linux kernel, I couldn't use the "OS". I can use gcc on Solaris, but I can't use the Linux kernel there. Is everything in/bin in "user space", or is it more "core"? Will the kernel work without the GNU stuff? Is the kernel the OS, or are the utils the OS? Does kernel32 or command.com makes Windows the "Windows OS"?
My point is that everything's resting on the kernel. The kernel is called Linux. It's a simple name, with recognition. It's in use. It works. I'm afraid in this case, instead of being part of the solution I'm going to have to remain part of the precipitate.
-B
--
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
Re:What about everything else?
by
Wee
·
· Score: 4, Interesting
Hey, thanks for asking a question that is specifically answered in the FAQ.
Hey, thanks for the personal attack without providing anything meaningful to the discussion. My question isn't answered in the FAQ (which I did read). It's mentioned, but it's not answered.
The FAQ says: "Since a long name such as GNU/X11/Apache/Linux/TeX/Perl/Python/FreeCiv becomes absurd, at some point, you will have to set a threshold and omit the names of the many other secondary contributions. There is no one obvious right place to set the threshold, so wherever you set it, we won't argue against it."
OK? You read that too before bitching at me, right? So my questions (which were to Perens specifically, BTW) remain asked: Where does one stop? Is there really a compelling reason to advocate ignoring many groups in favor of one? Do people use GNU stuff more than KDE or X or even Perl?
The FAQ merely says "GNU is the most important secondary component, so we should include it" and Perens advocates using it as well. My point was that the threshold shouldn't be there, so why bother using it?
My day isn't complete until I read a post that took longer to write that it would have taken to actually read the linked article, and never would have been written if the poster had done so.
My day's not complete until someone takes the time out of their busy day to whine about how a discussion board shouldn't be used for a discussion.
Thanks again.
Blow me.
-B
--
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
Re:What about everything else?
by
mjh
·
· Score: 4, Interesting
The FAQ merely says "GNU is the most important secondary component, so we should include it" and Perens advocates using it as well. My point was that the threshold shouldn't be there, so why bother using it?
Actually the FAQ says that "The principal developer is the GNU Project" implying that Linux is the secondary component. So, according to GNU/Stallman, you need to give the principle developer recognition. You're free to cut off any secondary developers at any point you choose. Call it GNU, or GNU/Linux, or GNU/Linux/perl, etc.
I disagree with this assessment. I think that GNU will still be a nice set of free utilities for Solaris if Linux didn't come along. If you ask me the principle project is on Linux distros and it's Linux.
Now, that's just an opinion. Maybe we should measure somehow. How about lines of code? Check out this.
Top project is the kernel.
Well maybe it's overall contribution? The top 3 pieces of code, are not the GNU project. The first GNU project's contribution is only 15% of the contribution of the top three. 6 of the next 7 projects are GNU projects. Combined they still only account for 69% of the top three projects.
Ok. Well maybe it should be measured in terms of which code is more frequently resident in memory. Glibc runs a lot, that's for sure. But not as much as the kernel!
By what measure, other than "we were here first", can GNU make the claim that they're the principle developer?
I am a supporter of GNU and I agree with almost all of the things that they stand for... including the differentiation of open source from free software. But this silly demand is the stark exception. And it drives me crazy. I wish that they would have simplified the FAQ and put the real reason: "Because we want to ride on the PR coat tails of Linux".
-- Key to financial independence: Spend less than you earn. Save and invest the difference. Do it for a long time.
Re:What about everything else?
by
jdavidb
·
· Score: 4, Informative
Hi, I'm the article submitter.:)
where does one stop with the attributions?
Did you read the FAQ? I was hoping a few folks would and think about the ideas presented, even if they don't agree.
I did a little experiment today; I downloaded all the source code for Linux From Scratch, and moved all the GNU code into a directory. The uncompressed GNU code takes up 341648 bytes. The uncompressed Linux code (counting the kernel, the manpages, and modutils) takes up 155872 bytes.
Since you mentioned X, I uncompressed XFree86 4.1.0 and counted it: 289624 bytes. (I was actually surprised; I expected X to be bigger than GNU.)
For the record, this is not all the GNU software, either. Emacs, for example, is not counted (that would've put it way over the top), and LFS chooses many alternatives where GNU packages exist.
Now, when you talk about the tail wagging the dog, if you want to call GNU the tail, the tail is bigger than the dog.:)
Is the kernel the OS, or are the utils the OS?
Did you read the FAQ? This issue is addressed. There's some truth to both views.
Does kernel32 or command.com makes Windows the "Windows OS"?
That's what GNU is saying. Most people would say the Windows OS consists of those pieces, plus the GUI, plus many utilities. And when you say you got RedHat Linux, do you mean you got the version of Linux, the kernel, distributed by RedHat, or do you mean you got an OS comparable to Windows? Which sense are you using the term OS in there?
Re:Why are they so desperate ?
by
foobar104
·
· Score: 4, Insightful
When I hear, "preaching to the choir," I think you're talking about trying to convince people who already agree with you. I don't think that's what's happening here at all.
I think there's probably one guy in the world who agrees with everything on the gnu.org web site. And I don't have to tell you who he is.
This FAQ isn't preaching to the choir. It's preaching to a bunch of people who (1) don't really care, and who (2) don't like to be preached to. It's preaching to the cannibals.
GNU failed? You're insane
by
gosand
·
· Score: 5, Insightful
Because Linus succeeded where GNU failed
Excuse me? How exactly did GNU fail? Look at what they have created.
From the FAQ: We developed programs such as GCC, GNU Emacs, GAS, GLIBC, BASH, etc., because we needed them for the GNU operating system. GCC, the GNU Compiler Collection is the compiler that we wrote for the GNU operating system. We developed Ghostscript, GNUCash, GNU Chess and GNOME for the GNU system too.
If that is failure, I hope to fail someday.
To the point of the FAQ, I agree with pretty much everything that is pointed out. It SHOULD be called GNU/Linux, technically. But unfortunately, words change meanings and it doesn't seem that there is much you can do about it. Hackers used to be considered a good thing, now you can get jailed for it (even though it is technically cracking). Pirates used to murder and plunder, but now it someone who listens to MP3s or forwards over commercials on their TiVO.
--
My beliefs do not require that you agree with them.
Distro's GNU/Linux, not Linux GNU Linux
by
dh003i
·
· Score: 5, Insightful
Distributions -- like Debian, Redhat, Suse, etc etc -- which use predominantly GNU-software along with Linus' GPL'ed Linux kernel should be called "Distro GNU-Linux"; i.e., Debian officially calls itself "Debian GNU/Linux". This makes sense, because Debian is composed mainly of two parts: the Linux kernel, and the GNU software. Hence GNU/Linux. Duh.
However, the Linux kernel itself was made by Linus, not the GNU/FSF. Though Linus licensed Linux under the GPL, that doesn't mean that he should call it GNU/Linux or GPL/Linux. There's no reason to call every piece of software licensed unde rthe GPL GPL/Software. Hence, there is no reason why Linux itself should be called "GNU/Linux". Just call it Linux.
There is also no good reason why Linux in general (in reference to the many distributions of it, not the kernel), should be called GNU/Linux. Not all Linux distributions use mainly GNU software. Most do, and those distributions should be called, "Distribution GNU/Linux" to indicate that they are mainly composed of GNU software and Linux. Those that don't, however, shouldn't.
Also, note that RMS is not forcing anyone to do anything. He's simply saying why he thinks Linux (in reference to the distributions in general) should be called GNU/Linux. I disagree with him, but that hardly makes him the language police.
*smiling, backing away very slowly from stallman...*
Don't make eye contact!:-)
Milalwi
Re:Why are they so desperate ?
by
evilpenguin
·
· Score: 5, Interesting
While I agree with you about the lack of a working "Hurd," I totally disagree with you about them "contributing little." They contributed most of the systems software, compilers, and libraries that are used to build everything on your Linux (er, GNU/Linux) system. They created the license that guarantees that a programmer who gives away his code will be paid in kind. Some people are definitely hostile to the GPL, but an awful lot of us write Free Software (meaning GPL'd software) becuase we derive a lot of benefit from everyone else's Free Software and we want to keep that going.
Now, I have called it "Linux," and will continue to call it "Linux" simply because I think "GNU/Linux" is the antithesis of euphony (how's that for a pompous phrase?). Also, as an aside, do they insist that it be called GNU/FreeBSD? Don't the BSDs come with a bunch of GNU software? Or am I missing something? And do they insist that it be called GNU/Solaris when people install gcc and bash on the box? In other words, I don't agree with the FSF on this.
But to suggest that they have contributed litte is either displaying surprising malice or surprising ignorance. The FSF is one of the key reasons we have the goods today. I'd be more than willing to bet the by lines of code alone, the FSF's contribution to the average distribution dwarfs that of the Linux kernel. The FSF is based around a philosophy; an ideology in fact. And they evangelize that ideology. They want to persude you that their beliefs are right. The regard code politically. I think very few people do right now. But with DRM, Palladium, the DMCA, and many other developments, I think it is going to be more and more common.
In other words, I think the FSF's greatest contribution may turn out to be their ideology, and not their code at all. Time will tell on that point. In the meantime, even though I buy into their philosophy, I still will call it "Linux." Guess I'm not a True Believer, but rather a true believer.
Remember the Berkley License?
by
weave
·
· Score: 4, Insightful
The BSD license *used* to mandate that everytime any of it was used, the program or derivitive had to give credit, as in "Portions copyright regents of california" or something like that.
Stallman thought that was ridiculous at the time, and predicted if everyone wanted that, whenever an OS booted, it'd be filling the screen with mostly copyright and credit notices. Whenever a press release or advertisement went out, there'd be pages of "portions copyrighted" credits included.
So he worked with the Berkley folks and got them to drop the credit requirement from the license.
So this GNU thing to me sounds kind of like the same thing, although the FAQ does state that they are not going to insist on it by making it part of the GPL.
However, and we should all remember, there would be no Linux today without the GNU software. Maybe you guys are too young to remember, but back about 12 years ago, the only way you could get Unix on a PC was shell out thousands of dollars for Interactive Unix or AT&T or $99 for Mark Williams Unix which used the intel small memory model (ram was limited to 64K, yes 64K). BSD was around, of course, but who could afford the money for a Sun box?
GNUs downfall was they started coding from the top down, as in, all utilities, compilers, and editors, and left the kernel to last. Then Linus comes along, does the kernel, throws a lot of gnu stuff on top, done.
Not to belittle Linus, of course, but all of this was a joint effort and we should not be so quick to forget the efforts of everyone who contributed to the GNU project for the past almost 20 years...
Why I Can't Stand the FSF
I like open source. I use open source software when it's appropriate. I write open source software, at that, and I'm happy to do so.
That said, I really, really dislike the Free Software Foundation. When I have a choice between their offerings and someone else's, I nearly always go with the alternatives. I don't use their licenses. I don't defend them, or even their goals, really. In many ways, I'm actively antagonistic.
Why?
It's pretty simple. I thought the FSF rocked until I had to deal with them directly, and the repercussions of that interaction made me reconsider all my assumptions.
Starting Down the Slippery Slope
I was working as a consultant for IBM in 1997, on their ProductManager suite. ProductManager needed a little language, for which I designed a grammar and lexer. When you need a compiler compiler and a lexer, you look at packages in the yacc and lex family... and the best of those, for C, remain the FSF's bison and Vern Paxson's flex. Not only was I trying to do well for IBM, but I was also aiming at using the best products available.
IBM, understandably, wanted to cover its pockets in the case of liability, so they had me talk to the respective authors to make sure that their code was actually theirs to give away. The reasoning was, as I understand it, that if (say) flex incorporated some copyrighted Microsoft code, and Microsoft discovered that IBM was using that code, Microsoft could sue both the author of flex and IBM. However, if IBM had a signed affadavit from the respective authors that asserted their right to distribute code, then IBM would have done due diligence to protect itself and other companies from illegal activity. It wouldn't have been a full defense, but would be enough to mitigate most damage in court. (The realisation that IBM didn't expect due diligence to be a complete shield was a blow to my faith in civil courts, too, even though that faith was pretty weak to begin with.)
So I wrote Vern Paxson and the FSF (because Richard Stallman was listed as the author of bison, which surprised me.) Vern got back with me after a few hours, and said he'd be happy to sign a form for us. When I talked to him on the phone and explained the exact situation, he reversed his position, saying that he simply couldn't honestly say that flex had no copyrighted code in it. He didn't think it did, but he wasn't able to get such an assertion from each author.
That eliminated flex for our project. I didn't mind, for a few reasons: one was that lexers are fairly trivial, and we could replace lex with something feature-comparable; another reason was that Vern was very straightforward about the situation. I got the feeling that he actually considered the needs of his potential userbase.
A few hours after Vern's initial reply came back, the FSF responded, too. (I was genuinely surprised at how rapid both responses were made.) They said that Richard Stallman was, indeed, the author of bison, and soon we managed to strike up a dialog with him directly.
Eventually, we were in a conference call with him. I was a little awed, considering that I'd been using some of RMS's tools (like Emacs) for quite some time even then. Basically, we had in mind a sort of quid pro quo, in that we wanted an affadavit signed and he wanted a monetary grant. It was also a chance for the FSF to score points in the courts, since the GPL hadn't been challenged. Our reasoning was that if IBM was using the code, and was challenged, then the FSF would be piggybacking a defense of the LGPL from IBM's defense team.
RMS would have none of it. What we were asking for, to be clear, was an assertion that the FSF had the right to apply their license to the software they made available. A denial of that assertion undermines their whole reason for being, after all, and we were certainly going to recompense the FSF for making good software available. Instead, RMS refused outright to sign the affadavit, and suggested quite bluntly that ProductManager (which costed IBM millions to develop, and was a pretty vertical product) should be open source, and we could send a check to him at this address, etc.
I was not impressed. It wasn't so much the open source spiel that bothered me, but the refusal of the assertion. If it was my code, I'd have been happy to say it was mine, as long as I knew (a la Vern Paxson's response). RMS, however, didn't even entertain the thought from the impression he gave us. Instead, he came across as a complete hypocrite, an impression confirmed with further investigation of the FSF's policies and approach. He was effectively implying that he'd stolen the code, and released it as open source just to further his personal views on software source code availability.
The Air Over There
I think the FSF is on crack. They want software to be open-sourced, as a statement of ethics, and yet they advocate strong-arming companies in order to get what they want. They don't want the code, even - they just want all code to be open source, and they're willing to act like brown-shirts to do it.
If you go to their home page, for example, you see this announcement at the end of the first paragraph:
Variants of the GNU operating system, which use the kernel Linux, are now widely used; though these systems are often referred to as ``Linux'', they are more accurately called GNU/Linux systems.
The opening sentence for the paragraph is "Welcome to the GNU Project web server."
Um.
Not only is the sentence about Linux inappropriate for the paragraph's subject matter, it's retarded. Their justification is something like this: "Linux is just the kernel, and GNU provides the rest of the system that makes the kernel useful, so the name should be GNU/Linux instead of just Linux."
That's idiotic. For one thing, they're targeting Linux in this, for reasons of publicity only. (Yes, that's right, I just said the FSF was a bunch of publicity whores.) If they were going to be fair about this, they'd apply that reasoning to a lot of software: "GNU/Cygwin," et cetera. To my knowledge, they don't do this. For another, they presume that GNU is central to Linux... and it's not. I know of developers who've created Linux distributions with BSD tools instead of GNU, for example, and the mere fact that it's doable suggests that maybe GNU isn't as critical to Linux as the FSF seems to suggest. Sure, maybe Linus used GNU tools to generate the kernel. Does that mean that every Visual Basic app needs to trumpet "MS/Whatever" as part of its name, too?
It gets worse. The FSF not only demands recognition (which, by the way, it got plenty of already), but it actively supports piracy, offering this newspeak as a replacement. "Use neutral terms to describe piracy," they suggest, offering "unauthorized copying" as well as "sharing information with your neighbor." Pardon me, fellows, for actually setting the price I want as recompense for my effort. The freedoms the FSF supposedly tries to work for include the rights to say "No, I wrote this with my blood, sweat, and tears, I want $100 for it or you don't have to use it."
And that brings up another annoyance with the FSF - the GPL. The GPL is a viral license, requiring programs that use GPLed code to be under the GPL themselves. In a way, that makes sense, although most other similar licenses are less militaristic;most of them respect the right of authors to keep their code proprietary, usually requesting links to the source of licensed software. The GPL, on the other hand, says that it's all open, and they choose licenses accordingly.
To wit, they have a "Lesser GPL," the LGPL, which doesn't have the same viral effect that the GPL does. The FSF has a document, called Why you shouldn't use the Library GPL for your next library (written before the LGPL was renamed to "Lesser GPL"), which explains that the LGPL is used where there's no real reason to rely on the GNU offering. In other words, all the truly useful stuff they have (and there's a good bit of it) is basically bait for the GPL; "use GetOpt, and we have you!"
That's cowardly, in my opinion, arguing from a position of weakness.
And that's the FSF for you.
http://enigmastation.com/Q260
-- If we don't fight for ourselves no one will.
Re:By Joe Ottinger
by
sab39
·
· Score: 5, Insightful
I'm not going to reply to most of this for lack of time (so please don't infer any position, either way, on the rest of your post from this lack of response). But the use of cygwin as an example was particularly unfortunate.
You see, Cygwin is a contraction of the words "cygnus" and "windows". And "cygnus" is a recursive acronym from "cygnus your GNU software".
Oh, and one other point I have to argue. The FSF has never claimed that the GNU tools are vital to Linux-the-kernel. It's true that it's almost certainly possible to build a system with a Linux kernel that's otherwise entirely a BSD system. But from the content of the FAQ and every argument I've ever heard from RMS, he'd want to see that system called BSD/Linux, not GNU/Linux. His point isn't that such a system isn't possible, but that no distribution in any kind of wide use actually does so.
Interestingly, if systems like that actually were in wide use, it would validate his argument further. Think about it: instructions on how to do any given operation are far more likely to depend on the toolset than on the kernel. So instructions for "Linux" (meaning Linux+GNU-tools) are less likely to apply to BSD/Linux than instructions for BSD are. It would make much more sense to have to choose between instructions for BSD versus GNU (which would cover the case of GNU tools on a BSD kernel also, as in the fledgling Debian GNU/BSD project, not to mention Hurd) than for BSD versus "Linux" as you're more likely to see now.
I've always been surprised to see so little activity in the area of switchable kernels based on the same overall operating system / distro. I suspect that the naming issue is actually partly to blame for this - if you think of the whole system as "Linux", what are you actually running if you keep the whole rest of the system the same but switch in a BSD or Hurd kernel?
The benefits of the FSF agenda, on the other hand, are not so clear. Wasting time on trival things like renaming Linux ensures that they remain that way.
While I continue to use Linux in preference over GNU/Linux, I don't agree that FSF agenda is in
any way either irrational or trivial. Linux is a stepping
stone for learning about the free software ideology. While
an ideology of free sharing to form a commonwealth is beyond
what many are willing to contemplate, I am always quite happy
to explain those ideals to someone who asks me: 'Hey, I just
heard that some guy named Stallman wants everyone to change
the name of Linux to GNU/Linux.'
The effort to rename Linux is valuable in itself. It doesn't
ever need to succeed because its value is in education of those
who hear of the naming conflict. We still need Linux as the
stepping stone, so GNU/Linux can't really replace Linux in the
public mind; and once it has then the GNU prefix will no longer
be needed anyway.
Building a software commons from nothing is an incredible
achievement for the FSF to have completed. I'm sorry you don't
value that acheivement enough to donate to them, but hopefully
there will always be enough people who do take the time to
understand and value their contribution.
-- LibBT: BitTorrent for C - small - fast - clean (Now Versio
Re:GNU: Get over it
by
Stephen+VanDahm
·
· Score: 4, Insightful
And it's their own fault that no one refers to the GNU project by name. GNU is a stupid-sounding name to begin with, and their made-up pronunciation (Guh-New) is counterintuitive and only makes their name even less attractive. I deeply respect the work that the FSF has done, and I have nothing but praise for the actual software they've written. But the fact is that if you want to sell your product, it really helps to have a cool name for it, or at least not a stupid name.
"Linux" is a great name. It sounds fast and high tech. When you attach "Guh-New" to the front, it loses its sex appeal. Geeks night not care, but when you're pitching Linux to your PHB (or your PHB's PHB), these trivial cosmetic things matter.
It's not just the FSF -- many free software projects have totally brain-dead names. Like the GIMP. The GIMP is an awesome product, and many of the K12 schools that spend a zillion dollars for a single copy of Photoshop that everyone has to share could outfit their entire computer lab with the GIMP for free. But as soon as the teacher walks into the classroom and says, "All right kids, let's fire up the GIMP..." every kid in the room who's seen Pulp Fiction is going to burst out laughing. Then parents might get pissed because it isn't politically correct to have a program named "GIMP" loaded on school computers. Advocates of Free Software in the classroom would do the world a great service if they repackaged the GIMP and gave it a new, school-safe name.
Free Software developers need to start thinking about more than just making cool-ass software. They need to think about how they want to present their software to the public. If they don't start thinking about their images, Free Software will never break out of the server room.
Steev
Re:I call it linux, here's why, in a few short poi
by
MSG
·
· Score: 5, Insightful
1: because Linus does
The FSF FAQ covers this point here: http://www.gnu.org/gnu/gnu-linux-faq.html#h elplinu s
Generally, the FSF and likeminded people aren't much interesed in Linus' opinion of what the OS is called; his motivations don't reflect those of the Free Software movement.
In other words: Who cares what Linus calls the OS? Even smart people can be wrong.
2: Because Linus succeeded where GNU failed
What the.. are you talking about? I fail to see either where GNU "failed" or Linus succeeded withough them. GNU has a reputation for providing a highly reliable OS that provides it users with freedoms not available with other OS's.
3: Because GNU/Linux is too damn long to say
So is Windows 2000 or Mac OS X, but they're the proper names.
I'd be willing to bet that you don't call Mac OS X "Mach", though that's the kernel it uses, and is a shorter name.
4: Because I don't call programs made/depending on MS Visual Studio 6 "MSVS/[program name]"
The GNU part of the name isn't in there because Linux is compiled by GNU tools... It's there because Linux is a kernel and that's it. Linux is not a UNIX-like OS. GNU/Linux is.
A good question that is not in the FAQ
by
gosand
·
· Score: 5, Interesting
I was really expecting to see this question in the FAQ:
How come you haven't talked to Red Hat and other companies about changing their references?
Surely posting a FAQ on a website may get a few people to change, but getting Red Hat to call it Red Hat GNU/Linux would be HUGE.
--
My beliefs do not require that you agree with them.
Political views
by
vlad_petric
·
· Score: 4, Informative
We strongly disapprove of his political views, but we deal with that disagreement honorably and openly, rather than by trying to cut him out of the credit for his contribution to the system. ...
If you free that Perl simply cries out for mention, and you want to write GNU/Linux/Perl, go ahead. ...
Should we say "GNU/BSD" too?
BSD systems today use some GNU packages, just as the GNU system and its variants use some BSD programs; however, taken as wholes, they are two different systems that evolved separately.
jeez...
The Raven
--
The Raven
Overlooked question in FAQ by many /.'ers
by
dh003i
·
· Score: 5, Interesting
Here's something that many here seem to have overlooked, in their zeal to label Richard Stallman a speech-nazi:
Why not sue people who call the whole system "Linux"?
There are no legal grounds to sue them, but since we believe in freedom of speech, we wouldn't want to do that anyway. We ask people to call the system "GNU/Linux" because that is the right thing to do.
Though I don't think that Linux in general as a reference to all the distributions of Linux should be called GNU/Linux (because some Linux distributions do not use GNU software), I do think that any distribution which uses primarily GNU software along with the Linux kernel should call itself "Distribution GNU/Linux".
This is really an issue of academic credit and a kind of plaguarism. Due credit should be given to those who created/wrote something. This is the basis of the academic world.
Re:I believe they are wrong
by
jgerman
·
· Score: 5, Insightful
Boy are you off. They aren't the ones creating newspeak, everyone who doesn't call the operating system by it's correct name is. That little bit of semantic engineering that shrtens the name to Linux is newspeak. In this case it's not for some nefarious purpose. The people that simply call it Linux either a) don't know any better b) don't understand the concept of an operating system or c) think it's easier to just say Linux (especially since the intended meaning is there). This does not mean that Linux is the correct way to say it, it means that it's easiest. It's what I call the OS, because no one is trying to downplay the involvment of GNU software by changing the name. If that were the case I would stick with the proper name.
While it's a good thing to make sure credit is given to GNU software by asking people to use the right name, I don't think that it's needed. But to call them language police, that's ridiculous and wrong. GNU/Linux is what it is. Linux is an easy to say name that we call it by.
-- I'm the big fish in the big pond bitch.
Re:Why are they so desperate ?
by
DustMagnet
·
· Score: 5, Insightful
FSF wrote a lot of GNU tools like gzip, sed, cat.
Most of that code was donated to the FSF. For some reason, they never bothered to organize a kernel (until Hurd).
If it wasn't for Linus, I'm not sure we'd have a "GNU-OS" yet.
RMS was a great advocate for years. Now he's been totally neutralized by this stupid issue. What a waste.
This is probably redundant (and should be moderated as such, if it is), but I just had to collect my favorite little gems.
The largest division in the community is between people who appreciate free software as a social and ethical issue and consider proprietary software a social problem (supporters of the free software movement), and those whose cite only practical benefits and present free software only as an efficient development model (the open source movement).
GNU Law #1: Never, ever, pass by an opportunity to turn the conversation toward our particular political and social agenda. And don't be ashamed to really stretch to make the connection, either.
People who value freedom are more likely to call the system "GNU/Linux"...
You're not against freedom, are you?
The shortest legitimate name for this system is "GNU", but we call it "GNU/Linux" for the reasons given below. [...] It would be ungentlemanly to ask people to stop giving any credit to Linus Torvalds. He did write an important component of the system.
Well, that's mighty generous of you, Richard, throwing Linus a bone like that.
In Spanish we sometimes say "GNU con Linux".
Dude, a Google web search turned up exactly one instance of the phrase "GNU con Linux," in this context: "Todo esto es curro, pero entre todos podríamos remover GNU con Linux...ehr... digo Roma con Santiago..." Not being a speaker of Spanish, it looks to me like this example is just using "con" as a conjunction, like saying "GNU and Linux."
There were no matches at all for "GNU con Linux" as a phrase on Google Groups.
The widespread practice of adding non-free software to the GNU/Linux system is a major problem for our community. It teaches the users that non-free software is ok, and that using it is part of the spirit of "Linux".
I really don't know what to say here. The pedantry of this statement shocks and amazes me. If the phrase "It teaches the users that [blah blah] is ok" were included in a leaked Microsoft memo, I'd be up in arms. The thought that RMS would publish this sort of statement publicly is just bewildering.
With this understanding, they can start to recognize Lindows and so-called "United Linux" as perverted, adulterated versions of GNU.
Sounding more and more like L. Ron Hubbard here, RMS.
If the Linux User Group in your area has the problems describe above, we suggest you either campaign within the group to change its orientation (and name) or start a new group.
Go found your own user group... but not in a way that divides the community or anything.
[Linus] has never advocated the ideal of freedom to cooperate, which is why the name "Linux" is mostly disconnected from that ideal.
So let me get this straight. If you have never actively advocated an ideal, then you must necessarily be opposed to that ideal. And if that ideal is freedom, then we've got a real problem on our hands! Linus is opposed to freedom, everybody! Sheesh.
He goes even further, and rebukes anyone who suggests that engineers and scientists should consider social consequences of our technical work--rejecting the lessons society learned from the development of the atom bomb.
Comparing programming as a hobby to the effort to build the atomic bomb is pretty arrogant, Richard. Once again, you've shown that your ego is way out of proportion to your contributions.
People who laugh at our request probably have picked up that mistaken picture--they think our work was done by Linus, so they laugh when we ask for credit for it.
Actually, Richard, we laugh because you are asking for credit for it. Asking for credit in this way is rude and overbearing. The most common responses are to get angry, or to laugh. I'm choosing to laugh, simply so that I may not get angry.
GNU ignores the contributions of others
by
Danborg
·
· Score: 4, Insightful
Apache - not GNU. PHP - not GNU. Samba - not GNU. Sendmail - not GNU. Perl - not GNU. KDE - not GNU. (The list goes on and on...) Gee, it looks like a whole slew of important components of a Linux system are not GNU. Richard Stallman needs to grow up. (And get a hair cut.)
Re:GNU ignores the contributions of others
by
ajs
·
· Score: 4, Insightful
Apache - not GNU. PHP - not GNU. Samba - not GNU. Sendmail - not GNU. Perl - not GNU. KDE - not GNU.
Yep. FSF claims to be the "primary developer" of the GNU/Linux system because they wrote most of the code.
The phrase "bzzzt! Thanks for playing!" comes to mind.
You mentioned a few, but let's get that list under analysis. I just happen to have a *Linux* system here. It's specifically a Red Hat Linux 7.3 system. It's not a complete install, but it's quite functional, so it should be a fair comparison of the "required parts of GNU" vs. "the required parts of Linux".
When I do an "rpm -qa" and clean up/uniquify the output to remove all of the duplicate kde, GNOME, XFree86, etc packages (I don't count XFree86 fonts seperately from XFree86, for example) I see 677 packages. Now, let's say that some of those are man-pages (which GNU was unwilling to write for years because they didn't like the format) and other non-program packages (like redhat-relase, which is just a marker), so I'll round that down to 600.
Now, I go and look at ftp.gnu.org:/gnu, and I find that there are 216 sub-directories. Most of those are packages, but some are not.
To weed that down, I check to see which ones are installed on my system. I get a little shock... 52 GNU packages are installed on my machine.
Yes, gcc was a lot of work, and a great compiler. I love it, but it's utility doesn't make up for the fact that GNU tools are a small part of a working Linux system. Hey, I've got an idea! Let's call it little-bit-of-GNU/Linux!
Re:Why are they so desperate ?
by
spudnic
·
· Score: 4, Insightful
The biggest problem I have with GNU is that it is too hard to say. How many people pronounce Gnome 'gahnome' rather than 'nome'. GNU is just an annoying name. And if you don't pronounce it 'gahnu' it sounds like you are saying New/Linux.
Get a real name and then maybe we'll talk!
--
load "linux",8,1
Re:I call it linux, here's why, in a few short poi
by
hondo77
·
· Score: 5, Insightful
In other words: Who cares what Linus calls the OS? Even smart people can be wrong.
Substitute "Stallman" for "Linus" and you sum up my feelings exactly.
-- I live ze unknown. I love ze unknown. I am ze unknown.
Re:Why are they so desperate ?
by
eam
·
· Score: 4, Funny
I can't help thinking that this is a list of Frequently Asked Questions that just aren't frequently asked.
They are NOT enforcing a name change!
by
FooBarWidget
·
· Score: 4, Informative
They are asking you to CALL it GNU/Linux, not to change it's name! What they are *really* after is the general awareness of GNU's existence. They are not enforcing anything, and even if they can, they won't (as stated in the FAQ). You don't have to call it GNU/Linux. If you want to call it just "Linux" and educate the public by explaining the whole story in 10 minutes, go ahead (the FAQ says the same thing).
Also read this: http://www.gnu.org/gnu/gnu-linux-faq.html#T OCwhysl ash
"Following the rules of English, in the construction "GNU Linux" the word "GNU" modifies "Linux". This can mean either "GNU's version of Linux" or "Linux, which is a GNU package." Neither of those meanings fits the situation at hand.
Linux is not a GNU package; that is, it wasn't developed under the GNU Project's aegis or contributed specifically to the GNU Project. Linus Torvalds wrote Linux independently, as his own project. So the "Linux, which is a GNU package" meaning is not right."
Re:I believe they are wrong
by
aardvarkjoe
·
· Score: 4, Insightful
The two most common reasons I hear for not saying "GNU/Linux" are (1) it sounds stupid and (2) that a Linux system is not just Linux + GNU -- it's Linux + GNU + XFree +... Their response to that is that "You have to set a limit somewhere... so let's limit it to just calling it GNU/Linux."
Sorry, guys, that's bullshit. If you're going to insist that everyone give you credit for your contributions, you're going to have to credit everyone. And if the FSF isn't going to credit everyone involved, I feel no need to give them extra credit. My "threshold value" is just calling the system Linux.
--
How can we continue to believe in a
just universe and freedom to eat crackers if we have no ale?
Slashdot Mirror
I have a small linux distribution for the Psion Revo. Interestingly, I can name this just Linux (not GNU/Linux) because it contains no GNU software. All the normal GNU base utilities (glibc, gnu text/shellutils, bash) have been replaced with small embedded replacements (uclibc, busybox). So I can leave off "GNU/" and I am still correct.
were you expecting to see a sig here? perhaps you'd rather see the inside of an ambulance!
Somehow I doubt those are frequently asked questions...
No one is denying the great tools that GNU provides. I always install various GNU tools on the Sun boxes I work on to keep me from going crazy. Stop acting so childish. It's this kind of behavior that can give Open Source a reputation of being a bunch of "childish geeks."
UNIX/Linux Consulting
1: because Linus does
2: Because Linus succeeded where GNU failed
3: Because GNU/Linux is too damn long to say
4: Because I don't call programs made/depending on MS Visual Studio 6 "MSVS/[program name]"
5: and finally, because Linux is common usage as the name of the OS. This is like trying to force the metric system on me when everything around me right down to my car's odometer is in miles. Let Stallman seethe in his jealous corner...I respect what he's done in creating the FSF, but that doesnt make me want to pander to his ego.
In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
Now that they've done it, I have no problems giving them a little credit by typiing GNU/Linux, but still using "Lih-nooks" conversationally. Why is spelling things this way hard? It would be hard to write an emacs Macro that inserted "GNU" everytime one typed "Linux".
Heck, if one think this is petty, then it's even pettier to complain about the pettiness. (And I know what I just did: complain about your pettiness. So there!)
Remember, the correct pronunciation of Netcape is "Mozilla". Why can't the correct pronunciation of GNU/Linux be "Linux"? Oh, I forgot... the GNU is never silent. :)
(Tongue firmly in cheek)
However, there are people who do not like our saying this. Sometimes those people push us away in response. On occasion they are so rude that one wonders if they are intentionally trying to intimidate us into silence. It doesn't silence us, but it does tend to divide the community, so we hope you can convince them to stop.
If this isn't evidence of Stallman's mental illness, I don't know what is. Oh, the problem isn't with us, it's with everyone else. We insist that people use this ludicrous name that no one can cleanly pronounce, and if anyone disagrees, clearly they are dividing the community.
In other words, "if everyone would just agree with us, then there would be no disagreement". Well, no shit.
Stallman, how about this: you call it whatever you want. And how about respecting other people's decision on what they want to call it, and stop notoriously refusing to talk to anyone who disagrees with you.
Sometimes it's best to just let stupid people be stupid.
'nuff said.
Normally I agree with what you say Bruce but in this case no.
No one knows (i.e. the general public or pointy haired bosses) what 'GNU' means anyway and I think its just going to become more of problem as people get confused thinking it's another distro or something.
The solution in this case is to stop this stupid holy war. We have the DMCA, Palladium, and Microsoft to worry about, we don't need to fight amongst ourselves about a name and we need to ignore the select few that are trying to take credit for Linux at the expense of the thousands of people who work on it.
NDAs won't happen as long as the GPL stands up in court. If it doesn't then saying GNU a million times before you say Linux isn't going to stop companies from taking the code.
The Anti-Blog
But what about everything else that I use on my box? Sure, I use the GNU utils and libs and compiler along with the Linux kernel, but I also use XFree86 as well. In fact, I'd be willing to wager that on my personal desktop machines, what get the most "workout" is X. So why disparage the generous contibution they've made by leaving them out? Now I use an OS called XFree86/GNU/Linux.
But why stop there? I also use KDE extensively. That's in the user's face a lot as well. It's what everyone sees. What a newbie might think is the OS. Why leave them out? My dekstop machines wouldn't be very useful to me without KDE (or any other WM). So now I need KDE/XFree86/GNU/Linux.
I use "The Computers Formally Known As Red Hat and Gentoo" for servers as well. That's a web server and a database typically. I even run these on my "workstations" as low-end test machines. I couldn't get on without Apache and MySQL (and/or PostgreSQL, but we'll simplify). So I need to call it MySQL/Apache/XFree86/GNU/Linux.
Oh wait. Perl and PHP. I can't forget those. Perl/PHP/MySQL/Apache/XFree86/GNU/Linux is what I call my OS now. What about the work Red Hat nas put into my desktop OS? I should mention them as well...
Rinse, lather, repeat.
Ok, so that's all more than slightly contrived. But it illustrates a point: where does one stop with the attributions? I realize that most of the heavy lifting is done by the wonderful work the GNU people have done, and I know that 'Linux' wouldn't be where it is today without all that stuff. But are the GNU utils the tail or the dog? Which wags which? Without the Linux kernel, I couldn't use the "OS". I can use gcc on Solaris, but I can't use the Linux kernel there. Is everything in /bin in "user space", or is it more "core"? Will the kernel work without the GNU stuff? Is the kernel the OS, or are the utils the OS? Does kernel32 or command.com makes Windows the "Windows OS"?
My point is that everything's resting on the kernel. The kernel is called Linux. It's a simple name, with recognition. It's in use. It works. I'm afraid in this case, instead of being part of the solution I'm going to have to remain part of the precipitate.
-B
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
When I hear, "preaching to the choir," I think you're talking about trying to convince people who already agree with you. I don't think that's what's happening here at all.
I think there's probably one guy in the world who agrees with everything on the gnu.org web site. And I don't have to tell you who he is.
This FAQ isn't preaching to the choir. It's preaching to a bunch of people who (1) don't really care, and who (2) don't like to be preached to. It's preaching to the cannibals.
Excuse me? How exactly did GNU fail? Look at what they have created.
From the FAQ:
We developed programs such as GCC, GNU Emacs, GAS, GLIBC, BASH, etc., because we needed them for the GNU operating system. GCC, the GNU Compiler Collection is the compiler that we wrote for the GNU operating system. We developed Ghostscript, GNUCash, GNU Chess and GNOME for the GNU system too.
If that is failure, I hope to fail someday.
To the point of the FAQ, I agree with pretty much everything that is pointed out. It SHOULD be called GNU/Linux, technically. But unfortunately, words change meanings and it doesn't seem that there is much you can do about it. Hackers used to be considered a good thing, now you can get jailed for it (even though it is technically cracking). Pirates used to murder and plunder, but now it someone who listens to MP3s or forwards over commercials on their TiVO.
My beliefs do not require that you agree with them.
Distributions -- like Debian, Redhat, Suse, etc etc -- which use predominantly GNU-software along with Linus' GPL'ed Linux kernel should be called "Distro GNU-Linux"; i.e., Debian officially calls itself "Debian GNU/Linux". This makes sense, because Debian is composed mainly of two parts: the Linux kernel, and the GNU software. Hence GNU/Linux. Duh.
However, the Linux kernel itself was made by Linus, not the GNU/FSF. Though Linus licensed Linux under the GPL, that doesn't mean that he should call it GNU/Linux or GPL/Linux. There's no reason to call every piece of software licensed unde rthe GPL GPL/Software. Hence, there is no reason why Linux itself should be called "GNU/Linux". Just call it Linux.
There is also no good reason why Linux in general (in reference to the many distributions of it, not the kernel), should be called GNU/Linux. Not all Linux distributions use mainly GNU software. Most do, and those distributions should be called, "Distribution GNU/Linux" to indicate that they are mainly composed of GNU software and Linux. Those that don't, however, shouldn't.
Also, note that RMS is not forcing anyone to do anything. He's simply saying why he thinks Linux (in reference to the distributions in general) should be called GNU/Linux. I disagree with him, but that hardly makes him the language police.
social sciences can never use experience to verify their statemen
Don't make eye contact!
Milalwi
While I agree with you about the lack of a working "Hurd," I totally disagree with you about them "contributing little." They contributed most of the systems software, compilers, and libraries that are used to build everything on your Linux (er, GNU/Linux) system. They created the license that guarantees that a programmer who gives away his code will be paid in kind. Some people are definitely hostile to the GPL, but an awful lot of us write Free Software (meaning GPL'd software) becuase we derive a lot of benefit from everyone else's Free Software and we want to keep that going.
Now, I have called it "Linux," and will continue to call it "Linux" simply because I think "GNU/Linux" is the antithesis of euphony (how's that for a pompous phrase?). Also, as an aside, do they insist that it be called GNU/FreeBSD? Don't the BSDs come with a bunch of GNU software? Or am I missing something? And do they insist that it be called GNU/Solaris when people install gcc and bash on the box? In other words, I don't agree with the FSF on this.
But to suggest that they have contributed litte is either displaying surprising malice or surprising ignorance. The FSF is one of the key reasons we have the goods today. I'd be more than willing to bet the by lines of code alone, the FSF's contribution to the average distribution dwarfs that of the Linux kernel. The FSF is based around a philosophy; an ideology in fact. And they evangelize that ideology. They want to persude you that their beliefs are right. The regard code politically. I think very few people do right now. But with DRM, Palladium, the DMCA, and many other developments, I think it is going to be more and more common.
In other words, I think the FSF's greatest contribution may turn out to be their ideology, and not their code at all. Time will tell on that point. In the meantime, even though I buy into their philosophy, I still will call it "Linux." Guess I'm not a True Believer, but rather a true believer.
Stallman thought that was ridiculous at the time, and predicted if everyone wanted that, whenever an OS booted, it'd be filling the screen with mostly copyright and credit notices. Whenever a press release or advertisement went out, there'd be pages of "portions copyrighted" credits included.
So he worked with the Berkley folks and got them to drop the credit requirement from the license.
So this GNU thing to me sounds kind of like the same thing, although the FAQ does state that they are not going to insist on it by making it part of the GPL.
However, and we should all remember, there would be no Linux today without the GNU software. Maybe you guys are too young to remember, but back about 12 years ago, the only way you could get Unix on a PC was shell out thousands of dollars for Interactive Unix or AT&T or $99 for Mark Williams Unix which used the intel small memory model (ram was limited to 64K, yes 64K). BSD was around, of course, but who could afford the money for a Sun box?
GNUs downfall was they started coding from the top down, as in, all utilities, compilers, and editors, and left the kernel to last. Then Linus comes along, does the kernel, throws a lot of gnu stuff on top, done.
Not to belittle Linus, of course, but all of this was a joint effort and we should not be so quick to forget the efforts of everyone who contributed to the GNU project for the past almost 20 years...
They want to enforce the GNU/Linux issue, but hate BSD's advertising clause. This is not a troll: how do they say you can do one but not the other?
Why I Can't Stand the FSF I like open source. I use open source software when it's appropriate. I write open source software, at that, and I'm happy to do so.
That said, I really, really dislike the Free Software Foundation. When I have a choice between their offerings and someone else's, I nearly always go with the alternatives. I don't use their licenses. I don't defend them, or even their goals, really. In many ways, I'm actively antagonistic.
Why?
It's pretty simple. I thought the FSF rocked until I had to deal with them directly, and the repercussions of that interaction made me reconsider all my assumptions.
Starting Down the Slippery Slope I was working as a consultant for IBM in 1997, on their ProductManager suite. ProductManager needed a little language, for which I designed a grammar and lexer. When you need a compiler compiler and a lexer, you look at packages in the yacc and lex family... and the best of those, for C, remain the FSF's bison and Vern Paxson's flex. Not only was I trying to do well for IBM, but I was also aiming at using the best products available.
IBM, understandably, wanted to cover its pockets in the case of liability, so they had me talk to the respective authors to make sure that their code was actually theirs to give away. The reasoning was, as I understand it, that if (say) flex incorporated some copyrighted Microsoft code, and Microsoft discovered that IBM was using that code, Microsoft could sue both the author of flex and IBM. However, if IBM had a signed affadavit from the respective authors that asserted their right to distribute code, then IBM would have done due diligence to protect itself and other companies from illegal activity. It wouldn't have been a full defense, but would be enough to mitigate most damage in court. (The realisation that IBM didn't expect due diligence to be a complete shield was a blow to my faith in civil courts, too, even though that faith was pretty weak to begin with.)
So I wrote Vern Paxson and the FSF (because Richard Stallman was listed as the author of bison, which surprised me.) Vern got back with me after a few hours, and said he'd be happy to sign a form for us. When I talked to him on the phone and explained the exact situation, he reversed his position, saying that he simply couldn't honestly say that flex had no copyrighted code in it. He didn't think it did, but he wasn't able to get such an assertion from each author.
That eliminated flex for our project. I didn't mind, for a few reasons: one was that lexers are fairly trivial, and we could replace lex with something feature-comparable; another reason was that Vern was very straightforward about the situation. I got the feeling that he actually considered the needs of his potential userbase.
A few hours after Vern's initial reply came back, the FSF responded, too. (I was genuinely surprised at how rapid both responses were made.) They said that Richard Stallman was, indeed, the author of bison, and soon we managed to strike up a dialog with him directly.
Eventually, we were in a conference call with him. I was a little awed, considering that I'd been using some of RMS's tools (like Emacs) for quite some time even then. Basically, we had in mind a sort of quid pro quo, in that we wanted an affadavit signed and he wanted a monetary grant. It was also a chance for the FSF to score points in the courts, since the GPL hadn't been challenged. Our reasoning was that if IBM was using the code, and was challenged, then the FSF would be piggybacking a defense of the LGPL from IBM's defense team.
RMS would have none of it. What we were asking for, to be clear, was an assertion that the FSF had the right to apply their license to the software they made available. A denial of that assertion undermines their whole reason for being, after all, and we were certainly going to recompense the FSF for making good software available. Instead, RMS refused outright to sign the affadavit, and suggested quite bluntly that ProductManager (which costed IBM millions to develop, and was a pretty vertical product) should be open source, and we could send a check to him at this address, etc.
I was not impressed. It wasn't so much the open source spiel that bothered me, but the refusal of the assertion. If it was my code, I'd have been happy to say it was mine, as long as I knew (a la Vern Paxson's response). RMS, however, didn't even entertain the thought from the impression he gave us. Instead, he came across as a complete hypocrite, an impression confirmed with further investigation of the FSF's policies and approach. He was effectively implying that he'd stolen the code, and released it as open source just to further his personal views on software source code availability.
The Air Over There I think the FSF is on crack. They want software to be open-sourced, as a statement of ethics, and yet they advocate strong-arming companies in order to get what they want. They don't want the code, even - they just want all code to be open source, and they're willing to act like brown-shirts to do it.
If you go to their home page, for example, you see this announcement at the end of the first paragraph:
Variants of the GNU operating system, which use the kernel Linux, are now widely used; though these systems are often referred to as ``Linux'', they are more accurately called GNU/Linux systems. The opening sentence for the paragraph is "Welcome to the GNU Project web server."
Um.
Not only is the sentence about Linux inappropriate for the paragraph's subject matter, it's retarded. Their justification is something like this: "Linux is just the kernel, and GNU provides the rest of the system that makes the kernel useful, so the name should be GNU/Linux instead of just Linux."
That's idiotic. For one thing, they're targeting Linux in this, for reasons of publicity only. (Yes, that's right, I just said the FSF was a bunch of publicity whores.) If they were going to be fair about this, they'd apply that reasoning to a lot of software: "GNU/Cygwin," et cetera. To my knowledge, they don't do this. For another, they presume that GNU is central to Linux... and it's not. I know of developers who've created Linux distributions with BSD tools instead of GNU, for example, and the mere fact that it's doable suggests that maybe GNU isn't as critical to Linux as the FSF seems to suggest. Sure, maybe Linus used GNU tools to generate the kernel. Does that mean that every Visual Basic app needs to trumpet "MS/Whatever" as part of its name, too?
It gets worse. The FSF not only demands recognition (which, by the way, it got plenty of already), but it actively supports piracy, offering this newspeak as a replacement. "Use neutral terms to describe piracy," they suggest, offering "unauthorized copying" as well as "sharing information with your neighbor." Pardon me, fellows, for actually setting the price I want as recompense for my effort. The freedoms the FSF supposedly tries to work for include the rights to say "No, I wrote this with my blood, sweat, and tears, I want $100 for it or you don't have to use it."
And that brings up another annoyance with the FSF - the GPL. The GPL is a viral license, requiring programs that use GPLed code to be under the GPL themselves. In a way, that makes sense, although most other similar licenses are less militaristic;most of them respect the right of authors to keep their code proprietary, usually requesting links to the source of licensed software. The GPL, on the other hand, says that it's all open, and they choose licenses accordingly.
To wit, they have a "Lesser GPL," the LGPL, which doesn't have the same viral effect that the GPL does. The FSF has a document, called Why you shouldn't use the Library GPL for your next library (written before the LGPL was renamed to "Lesser GPL"), which explains that the LGPL is used where there's no real reason to rely on the GNU offering. In other words, all the truly useful stuff they have (and there's a good bit of it) is basically bait for the GPL; "use GetOpt, and we have you!"
That's cowardly, in my opinion, arguing from a position of weakness.
And that's the FSF for you.
http://enigmastation.com/Q260
If we don't fight for ourselves no one will.
While I continue to use Linux in preference over GNU/Linux, I don't agree that FSF agenda is in any way either irrational or trivial. Linux is a stepping stone for learning about the free software ideology. While an ideology of free sharing to form a commonwealth is beyond what many are willing to contemplate, I am always quite happy to explain those ideals to someone who asks me: 'Hey, I just heard that some guy named Stallman wants everyone to change the name of Linux to GNU/Linux.'
The effort to rename Linux is valuable in itself. It doesn't ever need to succeed because its value is in education of those who hear of the naming conflict. We still need Linux as the stepping stone, so GNU/Linux can't really replace Linux in the public mind; and once it has then the GNU prefix will no longer be needed anyway.
Building a software commons from nothing is an incredible achievement for the FSF to have completed. I'm sorry you don't value that acheivement enough to donate to them, but hopefully there will always be enough people who do take the time to understand and value their contribution.
LibBT: BitTorrent for C - small - fast - clean (Now Versio
And it's their own fault that no one refers to the GNU project by name. GNU is a stupid-sounding name to begin with, and their made-up pronunciation (Guh-New) is counterintuitive and only makes their name even less attractive. I deeply respect the work that the FSF has done, and I have nothing but praise for the actual software they've written. But the fact is that if you want to sell your product, it really helps to have a cool name for it, or at least not a stupid name.
"Linux" is a great name. It sounds fast and high tech. When you attach "Guh-New" to the front, it loses its sex appeal. Geeks night not care, but when you're pitching Linux to your PHB (or your PHB's PHB), these trivial cosmetic things matter.
It's not just the FSF -- many free software projects have totally brain-dead names. Like the GIMP. The GIMP is an awesome product, and many of the K12 schools that spend a zillion dollars for a single copy of Photoshop that everyone has to share could outfit their entire computer lab with the GIMP for free. But as soon as the teacher walks into the classroom and says, "All right kids, let's fire up the GIMP..." every kid in the room who's seen Pulp Fiction is going to burst out laughing. Then parents might get pissed because it isn't politically correct to have a program named "GIMP" loaded on school computers. Advocates of Free Software in the classroom would do the world a great service if they repackaged the GIMP and gave it a new, school-safe name.
Free Software developers need to start thinking about more than just making cool-ass software. They need to think about how they want to present their software to the public. If they don't start thinking about their images, Free Software will never break out of the server room.
Steev
1: because Linus does
h elplinu s
.. are you talking about? I fail to see either where GNU "failed" or Linus succeeded withough them. GNU has a reputation for providing a highly reliable OS that provides it users with freedoms not available with other OS's.
The FSF FAQ covers this point here:
http://www.gnu.org/gnu/gnu-linux-faq.html#
Generally, the FSF and likeminded people aren't much interesed in Linus' opinion of what the OS is called; his motivations don't reflect those of the Free Software movement.
In other words: Who cares what Linus calls the OS? Even smart people can be wrong.
2: Because Linus succeeded where GNU failed
What the
3: Because GNU/Linux is too damn long to say
So is Windows 2000 or Mac OS X, but they're the proper names.
I'd be willing to bet that you don't call Mac OS X "Mach", though that's the kernel it uses, and is a shorter name.
4: Because I don't call programs made/depending on MS Visual Studio 6 "MSVS/[program name]"
The GNU part of the name isn't in there because Linux is compiled by GNU tools... It's there because Linux is a kernel and that's it. Linux is not a UNIX-like OS. GNU/Linux is.
How come you haven't talked to Red Hat and other companies about changing their references?
Surely posting a FAQ on a website may get a few people to change, but getting Red Hat to call it Red Hat GNU/Linux would be HUGE.
My beliefs do not require that you agree with them.
We strongly disapprove of his political views, but we deal with that disagreement honorably and openly, rather than by trying to cut him out of the credit for his contribution to the system.
...
If you free that Perl simply cries out for mention, and you want to write GNU/Linux/Perl, go ahead.
...
Should we say "GNU/BSD" too?
BSD systems today use some GNU packages, just as the GNU system and its variants use some BSD programs; however, taken as wholes, they are two different systems that evolved separately.
jeez ...
The Raven
The Raven
Here's something that many here seem to have overlooked, in their zeal to label Richard Stallman a speech-nazi:
Why not sue people who call the whole system "Linux"?
There are no legal grounds to sue them, but since we believe in freedom of speech, we wouldn't want to do that anyway. We ask people to call the system "GNU/Linux" because that is the right thing to do.
Though I don't think that Linux in general as a reference to all the distributions of Linux should be called GNU/Linux (because some Linux distributions do not use GNU software), I do think that any distribution which uses primarily GNU software along with the Linux kernel should call itself "Distribution GNU/Linux".
This is really an issue of academic credit and a kind of plaguarism. Due credit should be given to those who created/wrote something. This is the basis of the academic world.
social sciences can never use experience to verify their statemen
While it's a good thing to make sure credit is given to GNU software by asking people to use the right name, I don't think that it's needed. But to call them language police, that's ridiculous and wrong. GNU/Linux is what it is. Linux is an easy to say name that we call it by.
I'm the big fish in the big pond bitch.
Most of that code was donated to the FSF. For some reason, they never bothered to organize a kernel (until Hurd).
If it wasn't for Linus, I'm not sure we'd have a "GNU-OS" yet.
RMS was a great advocate for years. Now he's been totally neutralized by this stupid issue. What a waste.
'SBEMAIL!' is better than a goat!!
This is probably redundant (and should be moderated as such, if it is), but I just had to collect my favorite little gems.
The largest division in the community is between people who appreciate free software as a social and ethical issue and consider proprietary software a social problem (supporters of the free software movement), and those whose cite only practical benefits and present free software only as an efficient development model (the open source movement).
GNU Law #1: Never, ever, pass by an opportunity to turn the conversation toward our particular political and social agenda. And don't be ashamed to really stretch to make the connection, either.
People who value freedom are more likely to call the system "GNU/Linux"...
You're not against freedom, are you?
The shortest legitimate name for this system is "GNU", but we call it "GNU/Linux" for the reasons given below. [...] It would be ungentlemanly to ask people to stop giving any credit to Linus Torvalds. He did write an important component of the system.
Well, that's mighty generous of you, Richard, throwing Linus a bone like that.
In Spanish we sometimes say "GNU con Linux".
Dude, a Google web search turned up exactly one instance of the phrase "GNU con Linux," in this context: "Todo esto es curro, pero entre todos podríamos remover GNU con Linux...ehr... digo Roma con Santiago..." Not being a speaker of Spanish, it looks to me like this example is just using "con" as a conjunction, like saying "GNU and Linux."
There were no matches at all for "GNU con Linux" as a phrase on Google Groups.
The widespread practice of adding non-free software to the GNU/Linux system is a major problem for our community. It teaches the users that non-free software is ok, and that using it is part of the spirit of "Linux".
I really don't know what to say here. The pedantry of this statement shocks and amazes me. If the phrase "It teaches the users that [blah blah] is ok" were included in a leaked Microsoft memo, I'd be up in arms. The thought that RMS would publish this sort of statement publicly is just bewildering.
With this understanding, they can start to recognize Lindows and so-called "United Linux" as perverted, adulterated versions of GNU.
Sounding more and more like L. Ron Hubbard here, RMS.
If the Linux User Group in your area has the problems describe above, we suggest you either campaign within the group to change its orientation (and name) or start a new group.
Go found your own user group... but not in a way that divides the community or anything.
[Linus] has never advocated the ideal of freedom to cooperate, which is why the name "Linux" is mostly disconnected from that ideal.
So let me get this straight. If you have never actively advocated an ideal, then you must necessarily be opposed to that ideal. And if that ideal is freedom, then we've got a real problem on our hands! Linus is opposed to freedom, everybody! Sheesh.
He goes even further, and rebukes anyone who suggests that engineers and scientists should consider social consequences of our technical work--rejecting the lessons society learned from the development of the atom bomb.
Comparing programming as a hobby to the effort to build the atomic bomb is pretty arrogant, Richard. Once again, you've shown that your ego is way out of proportion to your contributions.
People who laugh at our request probably have picked up that mistaken picture--they think our work was done by Linus, so they laugh when we ask for credit for it.
Actually, Richard, we laugh because you are asking for credit for it. Asking for credit in this way is rude and overbearing. The most common responses are to get angry, or to laugh. I'm choosing to laugh, simply so that I may not get angry.
Apache - not GNU.
PHP - not GNU.
Samba - not GNU.
Sendmail - not GNU.
Perl - not GNU.
KDE - not GNU.
(The list goes on and on...)
Gee, it looks like a whole slew of important components of a Linux system are not GNU. Richard Stallman needs to grow up. (And get a hair cut.)
The biggest problem I have with GNU is that it is too hard to say. How many people pronounce Gnome 'gahnome' rather than 'nome'. GNU is just an annoying name. And if you don't pronounce it 'gahnu' it sounds like you are saying New/Linux.
Get a real name and then maybe we'll talk!
load "linux",8,1
In other words: Who cares what Linus calls the OS? Even smart people can be wrong.
Substitute "Stallman" for "Linus" and you sum up my feelings exactly.
I live ze unknown. I love ze unknown. I am ze unknown.
I can't help thinking that this is a list of Frequently Asked Questions that just aren't frequently asked.
They are asking you to CALL it GNU/Linux, not to change it's name! What they are *really* after is the general awareness of GNU's existence. They are not enforcing anything, and even if they can, they won't (as stated in the FAQ).
T OCwhysl ash
You don't have to call it GNU/Linux. If you want to call it just "Linux" and educate the public by explaining the whole story in 10 minutes, go ahead (the FAQ says the same thing).
Also read this:
http://www.gnu.org/gnu/gnu-linux-faq.html#
"Following the rules of English, in the construction "GNU Linux" the word "GNU" modifies "Linux". This can mean either "GNU's version of Linux" or "Linux, which is a GNU package." Neither of those meanings fits the situation at hand.
Linux is not a GNU package; that is, it wasn't developed under the GNU Project's aegis or contributed specifically to the GNU Project. Linus Torvalds wrote Linux independently, as his own project. So the "Linux, which is a GNU package" meaning is not right."
Sorry, guys, that's bullshit. If you're going to insist that everyone give you credit for your contributions, you're going to have to credit everyone. And if the FSF isn't going to credit everyone involved, I feel no need to give them extra credit. My "threshold value" is just calling the system Linux.
How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?