[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DotGNU]Uncovering Rotor -- A Shared Source CLI

From: David Sugar
Subject: Re: [DotGNU]Uncovering Rotor -- A Shared Source CLI
Date: Tue, 5 Mar 2002 09:37:15 -0500 (EST)

They believe they do not have to put such a clause in.  From what I recall
of so called "shared source", no freedom is given to modify the original
sources in any way, let alone distribute modifications.  However, a more
humorous hack might be to indirectly modify the sources thru inserting a
compile time --include file which redefines/maps BSD functions and clib
calls to match Linux and glibc, and perhaps write some small glue library
to link with for those calls that cannot be directly matched up.  I do not
actually suggest that is a "valid" solution, or something someone should
directly attempt, but use this to illustrace one of many flaws in the
concept of so called "Shared Source", and at some point in the future it
may prove useful in further demonstrating deliberately descriminitory

On Wed, 6 Mar 2002, Rhys Weatherley wrote:

> Bill Lance wrote:
> > Here's a good one.  Don't forget the 'Shared Source'
> > poision pill, folks.  Anyone appearing to be connected
> > with a 'Shared Source' agreement will be open to legal
> > attack by MS if they ever contribute to any OS/FSF
> > project.
> Yep, we need to avoid looking at their code when it
> is finally released.
> I do find it strange that they are only targetting FreeBSD.
> It will take an average Unix hacker about a day to port
> a FreeBSD program to GNU/Linux.  Who are they trying
> to kid anyway?
> Of course, they may try to put some kind of "cannot
> port this to any OS except what we say" clause in the
> license, which will make them look even more stupid.
> What I find weird is why it has taken them so long to
> do this.  Presumably, they were able to reuse much of
> the existing MS code for the C# libraries, etc.  It
> shouldn't have been that hard to build an engine for
> FreeBSD, given the resources at their command.
> Cheers,
> Rhys.
> _______________________________________________
> Developers mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]