On Tue, 2006-11-14 at 12:14 +0000, Bart Oldeman wrote:
> On 11/13/06, Jim Hall <[EMAIL PROTECTED]> wrote:
> 
> Rex Conn wrote:
> > > > > The only restrictions I'd put on the source code is that it not be 
> > > > > used for
> > > > > an OS other than FreeDOS or any commercial products without my
> > > > > permission.
> 
> This is a somewhat nasty term that makes it not "Open Source".

Technically, this still makes it "open source" but definitely not
"free".  OSI would likely disagree, but I am using the general
definition of "open source" here.


> I get the impression that what he really tries to prevent is that
> someone creates a competitor for 4NT using the 4DOS source code. It's
> a bit like Open Motif in that respect, you can look that up... and
> Fedora Core 6 doesn't have that any more because of legal concerns.
> 
> In any case, this means that FreeCOM hasn't suddenly become obsolete
> (a dosemu-freedos package with 4DOS wouldn't get past the license
> checks of many distributions).

Yes, I think that is the intention here - Rex doesn't want someone to
take his 4DOS code and create a commercial competitor to his 4NT
product.  Hence his restriction that the code not be used for any OS
other than FreeDOS.

I agree that FreeCOM definitely is still the preferred command.com shell
for FreeDOS.  I try to make sure we have GNU GPL (or similarly "free"
software) in the "Base" category of the FreeDOS software list, just so
FreeDOS can be included in Linux distros.  These license terms for 4DOS
mean 4DOS can only be included in our "Util" set.


-jh


-------------------------------------------------------------------------
SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now.
Check out Slashdot's new job board. Browse through tons of technical jobs
posted by companies looking to hire people just like you.
http://jobs.slashdot.org/
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to