On Sun, May 15, 2016 at 8:06 AM, Jerome E. Shidel Jr. <jer...@shidel.net> wrote:
> On May 15, 2016, at 1:17 AM, dmccunney <dennis.mccun...@gmail.com> wrote:
> [..]
>>> 4DOS - Listed as Free, No Sources. Kept for now, may get Dropped?
>> 4DOS sources, for the original 7.50 release, and the later 8.0 release
>> by Luchezar Georgiev may be found here, along with 4DOS original
>> author Rex Conn's open source license:
>> http://www.4dos.info/sources.htm#1
>> 4DOS is my command processor of choice under DOS.
> Thanks for the link. I have attached the sources to the my build copy of the
> 4DOS package.
> However, clause 3 for its license makes it NON-COMMERCIAL use only.
> (3) The Software, or any portion of it, may not be used in any commercial
>   product without written permission from Rex Conn <rc...@jpsoft.com>
> We will have to see if Jim is OK with keeping it in FreeDOS 1.2.

I fail to understand why that's a problem.

Many open source licenses have language about commercial use resolving
to "Contact the author about a license if you want to include the
software in a commercial product".  The assumption is that commercial
use involves taking it closed source.

Rex specifically released the 16bit 4DOS code as open source.  Later
32/64 bit products like TCC remain commercial.  If you expect to take
any of the 4DOS code and include it in something you will *sell*, Rex
expects a piece of the action.  I would be stunned if anyone ever
*did* contact Rex about it.

I can't imagine anyone taking stuff from a FreeDOS 1.2 release and
*wanting* to issue it as a commercial product.  Rex released 4DOS as
open source because it was no longer selling.  The world had moved on
from MSDOS and 16 bit, and so had he.

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
Freedos-user mailing list

Reply via email to