Re: SGI Freeware Feb. 2004
From: I R A Darth Aggie (sy_nttvr_at_gurcragntba.pbz)
Date: 01/30/04
- Next message: UNIX Museum: "Re: patchSG0005424 and 4Dwm fatal error"
- Previous message: R. Lynn Rardin: "patchSG0005424 and 4Dwm fatal error"
- In reply to: S.Chang: "Re: SGI Freeware Feb. 2004"
- Next in thread: Qubert: "Re: SGI Freeware Feb. 2004"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 30 Jan 2004 18:44:36 GMT
On Fri, 30 Jan 2004 16:39:16 GMT,
S.Chang <shu.chang@mapson.ieee.org>, in
<UMvSb.1679$ne7.16288956@news-text.cableinet.net> wrote:
>+ I R A Darth Aggie wrote:
>+ > On Fri, 30 Jan 2004 10:54:35 GMT,
>+ > S.Chang <shu.chang@mapson.ieee.org>, in
>+ > <LJqSb.1470$gK4.14231675@news-text.cableinet.net> wrote:
>+ >
>+ >
>+ >>+ Is that all you know? open source? take a look into GPL, it has more
>+ >>+ restrictions than commercial softwares,
>+ >
>+ >
>+ > Have you actually *read* the typical EULA that comes with those
>+ > commercial softwares? Have you actually *read* the GPL?
>+ >
>+ Lets see, if I released my 3.5G's HSDL algorithm under GPL, I would
>+ need
Is that a patented technology?
>+ to "share" the code with the rest of the world, sounds good, but what
>+ about security?
That's a good question. That's something you have to consider. Not
everything should be GPL'd. It's your code, you're free do with it as
you choose.
>+ what's stopping people from using my code and create
>+ their own equipment so they can browse the web for free on their
>+ hand set?
Instead of having to pay you a fee? probably the cost of creating
their own equipment and/or the effort needed to put it all
together. Yeah, some people will think that a cool project and do it
for the sake of doing it. But most are going to buy a pre-made handset
that's already properly configured.
There's a case of selling a physical item as well of a service.
Catering to people's lazienss is never a bad idea...if they're
willing to pay for it, and many are...
>+ what about copy right? if a multi billion dollar company decided to
>+ modify my code and use it as their own, how is GPL going to protect my
>+ copy right?
It won't? *you* protect your copyright. If your code is released under
the GPL, the only way they can *legally* use it is by agreeing to the
terms of the GPL. Nothing else gives them the right to redistribute,
modify or make derivative works. They could also ask you to relicense
it for their own use. MySQL uses that approach.
If this fictional company is not complying with the GPL and they
haven't made other arrangements with you, they become simple copyright
violators. You tell them what the deal is and how they can become
legal -- either comply with the GPL -or- arrange alternative licensing.
On the other hand, if they do comply with the GPL, they've just given
you their modifications. Do you want to tell me that has no value?
>+ You have company such as Sun, SGI, HP and IBM supporting their own
>+ version of Unix, so we can safely develope softwares and hardwares on
>+ it, what about Linux? who is supporting Linux? which Linux vendors is
>+ willing to support Hard RT applications running on their OS? and GPL
>+ states NO WARRENTY, huh!
So, what warranty *do* you have?
>+ don't we all love to have a get-out-of-jail-free card.
So, you give a warranty with your code? or do you (as is standard
practice) not warrant your code?
James
-- Consulting Minister for Consultants, DNRC I can please only one person per day. Today is not your day. Tomorrow isn't looking good, either. I am BOFH. Resistance is futile. Your network will be assimilated.
- Next message: UNIX Museum: "Re: patchSG0005424 and 4Dwm fatal error"
- Previous message: R. Lynn Rardin: "patchSG0005424 and 4Dwm fatal error"
- In reply to: S.Chang: "Re: SGI Freeware Feb. 2004"
- Next in thread: Qubert: "Re: SGI Freeware Feb. 2004"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
