RMS Accused Of Attempting Glibc Hostile Takeover 887
Bram Stolk sent a bit in thats been floating around lately where Ulrich Drepper, glibc maintainer announces the new version, and sidetracks to discuss an an RMS takeover attempt and how he feels about it. He raises several good points and I tend to agree with him. The FSF has done, and continues to do so much good, but more and more tension continues to grow between the extreme free speech faction and the more moderate folks. People have asked my opinion, and I'll just leave it by saying I don't prefix "Linux" with those 3 little letters and a slash even tho I've been asked.
Re:What I'd like to know... (Score:2, Informative)
Because glibc is very sensitive to changes in how the stack is laid out, etc. This is just one of those things, just like how 2.2 kernels could not be built with gcc 2.95. Eventually everyone will get their stuff straightened out, and that's that.
Re:Stallman.... (Score:5, Informative)
Well, it's not about stallman's ego, it's about making people realize that there is more to Free Software than the apolitical views of Linus.
BTW, here's a quote from one of Stallman's speeches (it was very well recieved):
Re:What I'd like to know... (Score:2, Informative)
Who knows? And anyway, who cares? Compiling glibc is a gigantic PITA. It takes hours even on a fast machine, and it's not really necessary for anyone except people doing distributions. Did you really need to compile glibc with gcc 3.0 right away? You can use glibc with gcc 3.0 just fine, you know.
And GCC 3.0.1 comes out tommorow.
Presumption of Innocence (Score:4, Informative)
How? Why?
Because you say so? I think I'll reserve judgement until I hear something more than "He just is, okay!"
Aha! So that's what it's all about. I find it surprising that someone working on "the GNU C library" as it's called in these release notes, should take exception to the idea that it's supposed to be a part of the GNU operating system.
Calling the operating system GNU/Linux, GNU/Hurd or whatever is not egotism (or not just egotism, anyway). It's an accurate description of what the system is. Look at, for instance, reviews [unixreview.com] calling openUNIX "Linux without Linux". That just sounds absurd, unless you know that the first "Linux" actually means "GNU".
Does not play well with others. End of story.
Call it GNU/Linux if you like... (Score:4, Informative)
Giving credit where credit is due is one thing, but trying to give everyone credit in the name is just going to lead to horribly long names.
Hypocrisy (Score:3, Informative)
I talked to Don Becker about GNU/Linux, and he had an interesting story to tell. Back in the day when he was at MIT and was an active contributor to gcc, he tried to get RMS to support Linux. RMS' answer back in the day went along the lines of `Linux is a waste of time, work on the Hurd instead, it is the future'.
An interesting twist to the Linux vs GNU/Linux debate.
Seems to confirm what RMS told Drepper. He seems to want it both ways . More developers need to come forward with their experiences - they will be doing the community a service.
Linus didn't name his OS (Score:2, Informative)
That sucked, so the FTP site maintainer
at ftp.funet.fi changed the name.
Re:GNU is Not UNIX or Linux. but Linux needs ' GNU (Score:5, Informative)
Being under the GPL is not the same as being GNU. I've written stuff and released it under the GPL and I'll be damned if anyone is going to tell me that the FSF deserves naming credit for my software.
Re:Thought Police (Score:3, Informative)
Actually, a lot of people tend to associate linux with open source, which, as we all know if different than free software. RMS wants to GNU out front so that the distributions people use will be associated with freedom (as in speach not beer). That is his goal as I see it.
links describing linux and its relation to GNU:
Garc
Re:Thought Police (Score:2, Informative)
Re:Thought Police (Score:1, Informative)
Linux was developed on what could justifiably be called GNU/Minix-- a 32-bit Minix with enough of the GNU system to be usable. As soon as Linux was viable enough to boot (before it was self hosting), it was basically outfitted with as much of then existing GNU software as possible to form a working system. At that time GNU software was basically aimed at replicating/improving the UNIX environment; many SUNs at the time ran GNU environments, for example. With the addition of X and associated tools, Linux systems continued to be essentially GNU. the GNU environment doesn't necessarily mean software written by Stallman/FSF--just that he considered it Free and fit to include in a definition of a Free environment. Since stallman observed that the environment he likes to call GNU has been wrapped around the Linux kernal, he chooses to call it GNU/Linux. However, those that don't share the vision of GNU may not care enough to do the same. They, for example, see GNU as part of a different vision.
Steering Committee an improvement so far (IMHO) (Score:5, Informative)
The basic idealogical dispute is that previously it was illegal to link glibc with proprietary software linked by non-GNU compilers due to a special "modified GPL" in the libio section of the GNU C Library. The change that the steering committee (who are developers like Roland McGrath, not just "Stallman") made was primiarily to convert that code to LGPL. Ulrich was the one being an idealogue about it. In this case, the steering committee was the group that was actually trying to get the right thing done for the users.
The glibc-2.2.4 announcement advised everyone to switch to it. What the announcement did not mention is that if you try to configure glibc-2.2.4, you discover that it does not want to build under gcc-3. The steering committee is pushing for a fast release of glibc-2.2.5 which will not have this problem.
So far, the steering committee seems to be a very positive influence. In the past, people were giving up hope on glibc due to its bloat, arcaneness, and legal issues. The SC seems much more focused on what users want.
By the way, let me say that Ulrich Drepper has made many contributions to glibc and I hope he will continue to be involved as a contributor.
Re:Steering Committee an improvement so far (IMHO) (Score:2, Informative)
> What the announcement did not mention is that if
> you try to configure glibc-2.2.4, you discover
> that it does not want to build under gcc-3.
Actually, there is a sentence that says that:
"And while we are talking about compilers; gcc 3
can NOT be used." (from glibc-2.2.4 release notes)