Re: Linux Kernel Source
- From: Michal Nazarewicz <mina86@xxxxxxx>
- Date: Sun, 27 Jan 2008 19:12:44 +0100
Chris Hills <chris@xxxxxxxxxxxx> writes:
In article <87odb7fn6g.fsf@xxxxxxxxxxxxxxxx>, Michal Nazarewicz
<mina86@xxxxxxx> writes
Chris Hills <chris@xxxxxxxxxxxx> writes:
In article <479b9562$0$25375$9b4e6d93@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Syren Baran <sbaran@xxxxxxxxxxxxxxx> writes
Chris Hills schrieb:
Industry is pragmatic and just ignores the GPL when it feels like
it. After al who is going to sue them?
Among others www.gpl-violations.org and the netfilter team.
A lot of people seem to be doing (ignoring GPL) it though.
The question is that if the GPL-violations team get good at this will
it kill the use of GPL software in the commercial space?
Why? Linux is used in business and it is GPL
Yes.. But not everyone releases their modified versions.
They they are committing a crime.
Nor do they feed the fixes back to others.
They are free to do so (if we are talking about situations where binary
is not distributed of course).
Most companies don't want to release their software to
competitors.
Then don't redistribute the binary,
But they do. That is the point
Then they can write it from stretch or use non-GPL software.
write application from stretch or
buy source code of closed source application.
What closed source? You seem to think things are either FOSS or closed
source.
Yes, they are. I've told you before: I consider everything that is not
open source to be closed source the same way doors that are not open are
closed. It does not mean that one particular company cannot buy source
codes of a closed source application.
I don't see your point
here. Should companies be allowed to take open source software and
redistribute it as closed source[1]? I consider this to be something
worse then theft.
No they shouldn't it breaches the license but that is what
I understand it happening more and more I am told.
Well, I hope it's not the case.
And in some cases releasing it will open the system to serious
security problems.
If knowing the source code opens system to serious security problems
then not-releasing source code does not prevent those serious security
problems.
Yes...
And releasing source code to general public could help find
and fix security issues.
SO you are happy to release source code of your security system to the
enemy? It is not released to YOUR public but the world including
terrorists. What if they find the holes long before your side
does....?
If we are talking about military equipment I might agree that there are
a bit different rules there.
--
Best regards, _ _
.o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michal "mina86" Nazarewicz (o o)
ooo +--<mina86*tlen.pl>--<jid:mina86*jabber.org>--ooO--(_)--Ooo--
.
- References:
- Linux Kernel Source
- From: Billy Bong
- Re: Linux Kernel Source
- From: Kaz Kylheku
- Re: Linux Kernel Source
- From: Billy Bong
- Re: Linux Kernel Source
- From: santosh
- Re: Linux Kernel Source
- From: CBFalconer
- Re: Linux Kernel Source
- From: Chris Hills
- Re: Linux Kernel Source
- From: Ian Collins
- Re: Linux Kernel Source
- From: Chris Hills
- Re: Linux Kernel Source
- From: Kelsey Bjarnason
- Re: Linux Kernel Source
- From: Chris Hills
- Re: Linux Kernel Source
- From: Syren Baran
- Re: Linux Kernel Source
- From: Chris Hills
- Re: Linux Kernel Source
- From: Michal Nazarewicz
- Re: Linux Kernel Source
- From: Chris Hills
- Linux Kernel Source
- Prev by Date: Re: Thoughts on file organisation
- Next by Date: Re: Thoughts on file organisation
- Previous by thread: Re: Linux Kernel Source
- Next by thread: Re: Linux Kernel Source
- Index(es):
Relevant Pages
|