CptnObvious999 wrote:Tsuroerusu wrote:CptnObvious999 wrote:Yes because making companies completely change how they work is definately what they want.
Why would the companies have to change how they work? The ones already using Linux or GPLed software just need to not put DRM crap in there if they do currently.
Maybe would should also tell them to give 10% of the profit to the project
What in the *bleep* world are talking about? If a company is already using GPLed software, GPLv3 will have zero impact on their profit, and frankly if you as a hacker could modify a cellphone with all kinds of Asterisks integration, I think they would sell a lot more, I'm very interested in what Trolltech is up to in this area.
CptnObvious999 wrote:and maybe we can also put a clause in there that Microsoft can't use any of the code.
Time to take up and smell the coffee, they can't already, and idealogically they won't. Microsoft sees the GPL as cancer, plus would not risk having to release the Windows source code, all versions of the GPL would require them to do that.
CptnObvious999 wrote:I am simply saying it's another restriction and depending on the project it could be easier said then done.
You may see it as a restriction, I see it as another way of ensuring that the down to earth end user of software has four essential freedoms that RMS defined over 20 years ago, both technically and spiritually.
CptnObvious999 wrote:Your views on DRM are entirely biased (although I doubt you will admit that). You are thinking about iTunes DRM where it is used to lock you in a product. It also serves the purpose of protecting their product.
I think a lot of about iTunes DRM, but that's not what I think the most about, although I use the example of iTunes the most as that one is reality right now, today.
The thing that concerns me the most, is what Eben Moglen mentioned on FLOSS Weekly #13, that in the future you might only be able to buy DRMed computers, maybe those will only run Windows or OS X, like the TiVo will only run their version of the Linux kernel today.
Linus' arguments are based on today's situation, please allow me to quote him:
I think stopping Tivo is a much bigger problem than Tivo itself ever was.
The key is that he says "was", from his statement I assume he doesn't consider that in the future we could be invaded by DRM everywhere, personally I HIGHLY doubt that HD DVD and BluRay will play on Linux and BSD any time soon.
CptnObvious999 wrote:I know I will not change your mind on this and I am sure you will keep blasting me for my views
Ḯ'm not blasting you, I'm just simple arguing with you because I don't agree with you on X, Y and Z, this is what free speech is for, which is protected under both the US and danish constiutions.
CptnObvious999 wrote:but let me just say that IMHO it's an unneccessary restriction.
At least it's not "digital restrictions management" (I just love that term, very accurate).
CptnObvious999 wrote:And if you ask Linus why he choose the GPL he would say because it is the best license to develop under.
I know that, and I think Linus made a good choice, over say the BSD license.
CptnObvious999 wrote:Everyone is focused on the Linux kernel because it is such a large project and effects everything unlike KDE and GNOME which mainly only run on desktops and not embedded devices or servers.
Fair enough, I can see that, but I'd hope KDE and GNOME are involved in some way with the GPLv3, because like Apache was a decade ago, I think KDE and GNOME is the exciting future of free software.
CptnObvious999 wrote:Also you said that the DRM only applies to hardware which makes it much less controversal.
Yes, the "DRM clause" of the GPLv3, is preventing hardware vendors from using an external meassure to ensure that the kernel that's running is the kernel that they have "blessed", aka signed or done a checksum on. Actually, it's only saying that if they use such meassures, they have to give the user their private key, as a part of the source tarball, so that he can sign his own kernels to run, so they can still use DRM to verify that a user calling for support is actually using their factory kernel, I think it's completely fair for vendors not to provide support for non-factory kernels.
It does not say that Apple, for example, couldn't port iTunes to Linux.
Software DRM is kind of already dealt with in the GPLv2, because if you use GPLv2ed code in a product that uses DRM, that product has to be under GPLv2 as well, so you could just go in and take the DRM right out, so essentially, a DRM system HAS to be proprietary unless it's gonna be pointless.
CptnObvious999 wrote:There is a problem and that is the directions you gave didn't work.
I'd like to kindly ask you, what was that problem?
If it's the package manager, there is a solution: Smart, YUM or apt4rpm.
Shit you could even install NetBSD's pkgsrc.
CptnObvious999 wrote:And if you expect me to go around chanting SUSE, SUSE, SUSE like you do after it took me a week to get it working and many many hours of frustration for someone who's been using Linux for over 3 and a half years (and Gentoo, the one that is deemed most advanced) and recomend it to a new user you are sadly mistaken.
First of all, please see
this, as I don't like repeating some things twice.
Also, maybe surprising to you, I don't recommend
SUSE Linux 10.1 to new users (10.0 is great for new users, 10.1 is not!), and I don't expect others to do. I only recommended it right after it's release, but when I ran into the issues with the package manager myself, it got an H- and failed "the test" quite misserably. As I said, today I don't recommend SUSE 10.1 to new Linux users, because of the immense process it takes to get around the package management problems.
CptnObvious999 wrote:Even the people on the #suse IRC channel didn't know how to fix most of the problems. Any distrobution that takes over 1 hour to install 3 repos is not exactly the greatest in my oppinion. </rant>
Please allow me to quote myself:
I am in no way afraid of admitting that the distro I talk about all the time and recommend to people, has errors/bugs and things that aren't necessarily working that well. Just as an example, before Novell bought SUSE, YaST was a proprietary component, but luckily Novell was kind enough to release YaST under the GPL, also SUSE's performance has not always been the best, when I switched from 9.2 to 9.3 I noticed that 9.3 was quite sluggish, and finally the package manager in 10.1 has been a disaster, I can't defend that, this ZENworks framework has been so crappy until just recently, that it's almost a disgrace, but as I've stated before, every distro has made at least one release that's not exactly that well put together, for example Mandriva's 2005 version I had some problems with (I'm sure some earlier releases had issues as well), Fedora 1 and 2 was not exactly a gift from heaven either, Kubuntu up until Dapper has been of significantly lower quality (Put it in a kind way) than just standard Ubuntu (Which is why I see the Ubuntu project's KDE support as half-hearted, because Kubuntu is always of less quality than Ubuntu) etc. etc.
So I ask people to at least cut SUSE a little slack, SUSE's past releases may not always have had the best performance but their stability has never had a problem, their releases have always been rock solid, but with not so good performance in too many cases,
CptnObvious999 wrote:Judland wrote:More... on GPLv3 and the issues Linus has to using it.
I think I'm starting to see his point of view a little clearer and would have to agree with his concerns.
Thanks for the find, it's a good overview.
There's another thing that concerns me although I am not sure how true it is. I was told that if a project needs funds to distribute the source code it could charge anything it wants which could be a possible way to lock away the source unless someone is willing to pay $1,000,000 for a copy of the source code. I haven't seen a whole lot about this issue so maybe I was told wrong or the issue was fixed in a later revision.
As far as a I know, one of the GPLv3 drafts had some wording that could be interpeted as the example you just gave, that is indeed fixed. Both the users and developers would be against it, and Richard Stallman himself would be against it, because if developers require you to pat a fee to get the sourcecode, a guy who can't afford that, doesn't have free (as in freedom) access to the sourcecode and thereby is unable to modify the program, unless he knows binary code inside and out, because he is being forced to pay an upfront fee, like a proprietary software company would do.