Glibc Is Finally Free Software
WebMink writes "Despite the fervour of some, the dark secret of every GNU/Linux distribution is that, until August 18 this year, it depended on software that was under a non-Free license — incompatible with the Open Source Definition and non-Free according to Debian and the FSF. A long tale of tenacity and software archeology has finally led to that software appearing under the 3-clause BSD license — ironically, at the behest of an Oracle VP. The result is that glibc, portmap and NFS are no longer tainted."
Interesting. But how is this "more free"? It's not quite a BSD license if they require the source and binaries contain that notice. Further, what I see is this re-branding of everything from Sun to Oracle all over the place. The latest updates for VirtualBox, OpenOffice and Java did little to patch or improve but most significantly changes everything to containing Oracle branding. I see this as no different.
Calling this more free while also including requirements such as the ones illustrated above it s bit of a mixed message.
I've been living a lie all these years??? Fuk!
Seriously, that's aggravating as hell. I just kind of assumed that GNU would have released all of their flagship software under the L?GPL and had no idea that they were distributing non-Free software. They were the one distributor I figured I'd never have to audit the licenses from. Are there any other hidden gems? Is there some shareware in Emacs? Maybe a bit of Shared Source in binutils?
People have laughed at the BSDs for replacing a lot of common software with locally-developed, BSD-licensed equivalents. That's starting to seem like a much saner alternative.
Dewey, what part of this looks like authorities should be involved?
It is a very good question, and the answer is to use the GPL.
Um, WTF? GPL is absolutely not similar to public domain; the gpl-violations people repeatedly make this very clear.
A better answer is, "that's not very clear, could you give an example of what you mean?". About the only thing I think it can sanely mean, is how to prevent other people from claiming it as their work (ie, plagiarism) and suing people (kinda like SCO suing people over Novell's copyrighted code). Maybe something like CC-zero is the answer (you keep a copyright, so you can sue them for... I think it was "slander of title" that Novell used), maybe just make sure your copy with the non-copyright notice gets well indexed by the search engines so any potential victims can find it when they need to defend themselves, maybe plagiarism can be a suable offence separately from copyright violation (I don't think that's the case here in the US, but I hear it might be in much of Europe).
You aren't supposed to read the GPL, only its preamble. The rest of meant for lawyers and is as long as it takes to be bulletproof.
Slashdot anagrams to "Sad Sloth"
You keep saying "public domain", but you are using it to define nearly the opposite concept.
I like to think of it this way. Least free to most free: GPL, BSD/MIT, Public Domain. GPL is very restrictive as to what the licensee can or cannot do with the work. BSD/MIT both allow nearly any use/modification/extension, but requires the licensee to retain copyright notices. Public Domain requires neither; anyone can use and abuse it without retaining copyright notices.
So is GPL more or less free than a commercial license? Usually less free, but it depends on what you want. The GPL is more restrictive in that source code must be provided, no charge, to anyone who gets a binary copy. Typical mega-corporation commercial licenses prevent modification or extension, and many times even use and reverse-engineering, but I'd say that smaller companies tend to be less restrictive in their licenses than the GPL (barring, of course, redistribution of the original source code).
All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
Sleepycat isn't NEARLY as comprehensive, but simplicity is usually well worth that loss.
When dealing with normal, reasonable people I agree because your audience is trying their best to understand the information you are trying to impart. When dealing with the law your audience is deliberately trying to misinterpret everything you have said to their advantage so you need everything specified absolutely precisely so that there is no possible way they can do that.
That's a pretty vanilla 3-clause BSD licence just like you'd see anywhere else, I don't see a problem with it.
Yup. The only thing different about it is that somebody actually bothered to change "The Regents of the University of California" to something else, and put in a date and so on.
That's actually fairly rare to see. Most people who license code under BSD do so very poorly, just copying the boilerplate and never filling in the blanks.
There are a handful of unix libc implementations out there, so someone, in fact, did.
Additionally, have you ever heard of a derivative work?
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
The reasons that you gave, plus the rest of your comment, tell me pretty conclusively that you don't.
You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
Believe me, I love Linux. Been running it is my main OS for 7-8 years now. But Compiz and PulseAudio are not fixed. At all. (At least under Kubuntu)
My last upgrade still required me to purge PulseAudio before my audio worked, and I get regular notices that "composting was too slow and has been disabled". The last time that happened, I was sitting with my hands 6" from the keyboard and mouse, reading slashdot, with no other programs running. I hadn't touched the computer for at least a minute. And this is on a dual-core desktop, with a decent video card, and a couple GB of ram.
I've been holding off on an entire system wipe and reinstall, because I need to get around to getting a couple new hard drives anyway. I'm hoping that fixes at least the Compiz problem. But I'm still not impressed with Compiz. If I'd ever seen PulseAudio do anything but destroy all the sound on my computer, I might like it. The philosophy is fucking fantastic, and I've been drooling about it ever since it was announced. It's something that Linux desperately needs. To generically say that everything is fixed, however, is a sweeping overstatement. For you, perhaps. But based on my searches to fix the issues I have, a ton of people are still having a terrible time with those things
Velociraptor = Distiraptor / Timeraptor