Live data from Hacker News

Leaked Samsung exFat driver relicensed as GPL

lists.gpl-violations.org

91–100 of 206 posts

Re: Leaked Samsung exFat driver relicensed as GPL

#91
post #78

Earlier quoted context omitted.

Wasting man-years on reimplementing software is not a large enough problem to decide that authors no longer have any rights with their product.

but it is a large enough problem. Wasting man years is precisely the problem. Our collective knowledge is boundless, but time is finite. See the problem here? Why would we want to waste the effort of future generations with the problems of yesterday? So that an individual can live more comfortably with exclusive privileges to something that benefits all of mankind? We shouldn't be working towards selfishness and arbi…

[deleted]

Re: Leaked Samsung exFat driver relicensed as GPL

#93

GPL, and probably other licenses, were constructed to work with copyright law. Such cavalier dismissal (by rxrz) is disrespecting those who created the licenses, the legal system, and the open source community, at large. We live in the real world, not "The Matrix".

Sadly, this is a typical thing that goes on in the Android User development community. Lots of casual attitudes by hobbyists that modify the Linux Kernel and rattle off some sort of excuse for not posting their sources while distributing binary copies. Others end up "relicensing" similar to the guy on github, thinking that because they changed a few lines of code, they can claim to own the license to the software now…

The last point you raise is one of the reasons that I think the drive to bring as many "proverbial grandmothers" to Linux presents a very serious concern.

Imagine if Linux distros started getting treated like Android does? Android got those legions of "regular" users and participants that everybody seems to want and it is not a pretty scene because of it.

Re: Leaked Samsung exFat driver relicensed as GPL

#94

GPL, and probably other licenses, were constructed to work with copyright law. Such cavalier dismissal (by rxrz) is disrespecting those who created the licenses, the legal system, and the open source community, at large. We live in the real world, not "The Matrix".

What's wrong with disrespecting those who created the licenses, and the legal system? Maybe if we were disrespecting them sufficiently early on we wouldn't be in a mess we are currently in and the open source community wouldn't need to have a special name because it would be just called developer community?

> We live in the real world, not "The Matrix". So why does it feel like it's the other way around? Why does it feel like we are living in a world pull over by our eyes by lawers that restricts sharing our creativity?

Re: Leaked Samsung exFat driver relicensed as GPL

#95

Earlier quoted context omitted.

> The ROM scene has always been a grey (verging on black) area when it comes to IP Speak for yourself. There are two scenes: The binary modder scene, where people retro-fit vendor-created and provided firmware-images with their own modifications. Commonly referred to as "Photoshop ROMs". This scene is clearly grey at best. However, there is another scene: The one based on AOSP source and derivates of it. This scene l…

Cyanogenmod) are based on this scene, and there is nothing grey or remotely shady about it. So when Cyanogenmod was distributing the play store apps illegally there was nothing shady going on? It isn't like they suddenly decided to do the right thing, it was a C&D from Google that got them to stop. http://androidandme.com/2009/09/hacks/cyanogenmod-in-trouble...

Copyright and IP is such a mess that everything is "shady" for any entity if looked from the right (or wrong) angle or country.

I don't think that there has been actual harm and malicious intent in the redistribution of the apps, just the fact that few people can afford the legal counsel fee to understand a licence.

Re: Leaked Samsung exFat driver relicensed as GPL

#96
post #15

I agree with the actions of the repo maintainer. Why should we play along with unjust copyright laws? GPL sheep are just part of the problem, creating their own nest of licensing woes everytime you touch their code.

Even if you don't want to play along with copyright laws - and I can perfectly understand why one wouldn't - that's not a reason to deceive people by claiming the code to be GPL licensed and make them liable if they redistribute it. If one wants to say "fuck copyright", putting a copyright license in the code is not the really the most appropriate way.

I think deception is a valid tool for creating chaos and chaos is a valid tool for bringing down systems.

Re: Leaked Samsung exFat driver relicensed as GPL

#97
post #89
post #67

Earlier quoted context omitted.

>The fact that so many prebaked ROMs are distributed though megaupload-alikes is a bit of a giveaway as to the general philosophy of that community. What? Hosting (relatively) large files, on services that can deliver those around the world at faster than dialup is now some how bad? So I suppose all those companies using CDNs are also horrible and despicable. I mean, how dare they use servers that are well connected!

Less fly-by-night-ish projects seem to have little trouble finding mirroring that 1) isn't shared by so much warez 2) doesn't make me visit a webpage and make me do a CAPTCHA, 3) doesn't blast me with shady as hell popups and advertising.

The majority of Android ROMs (at least from the likes of XDA) are hosted at one of a few places -- goo.im being (probably) the most prevalent. There is 1) little to no warez (I've never seen any), 2) no CAPTCHA and 3) no pop ups and only text ads on goo.im.

Another popular one Dev-host (http://d-h.st/) also features none of the cruft you complain about.

CyanogenMOD (http://get.cm/) is hosted through several large partners and has no captchas, ads or warez.

MIUI's community fileserver (http://files.miuiandroid.com/) also has none of this.

AdroTransfer (http://androtransfer.com/) also has none of this.

Re: Leaked Samsung exFat driver relicensed as GPL

#98
post #91
post #78

Earlier quoted context omitted.

but it is a large enough problem. Wasting man years is precisely the problem. Our collective knowledge is boundless, but time is finite. See the problem here? Why would we want to waste the effort of future generations with the problems of yesterday? So that an individual can live more comfortably with exclusive privileges to something that benefits all of mankind? We shouldn't be working towards selfishness and arbi…

[deleted]

Why are you talking about infringing on the GPL? OP infringed on a "proprietary exfat driver, written by Samsung", not on GPL licensed code.

Re: Leaked Samsung exFat driver relicensed as GPL

#99

If it's a derivative work of the Linux kernel (links to internal kernel API) it should be GPL. If Samsung distribute it to users then it should do that under GPL. Samsung should be the first to relicense it.

Morally you might be right. Legally it's a grey area, and practically it's almost certainly a no-go.

So basically company can take your gpld code, extend it, slap their license on the whole thing it and redistiribute binaries without the source code and nobody can slap the gpl back on where it should be because it's a gray area?

Re: Leaked Samsung exFat driver relicensed as GPL

#100
post #50
post #14

"Originally, it was either public domain or GPL." He's claiming that this is actually GPL code that Samsung claimed as proprietary (which they can't do). Is he wrong?

It's hard to tell - there doesn't seem to be any proof of this and in the case of leaked code I'd be wanting proof.

I think judge should force Samsung to release all the information they have on history of this code. After all Samsung is suspected of violating the license. Shouldn't they be able to prove copyright before they can claim it?
Post reply on HN