Path: utzoo!attcan!uunet!know!cs.utexas.edu!evax!utacfd!merch!rwsys!jim
From: jim@rwsys.lonestar.org (James Wyatt KA5VJL                .)
Newsgroups: comp.dcom.lans
Subject: Re: Please boycott Xircom
Summary: They were likely careless until they found it out.
Keywords: Xircom TCPIP Packet GPV GNU Clarkson
Message-ID: <2810@rwsys.lonestar.org>
Date: 30 Sep 90 14:45:17 GMT
References: <1990Sep28.192413.21255@ism.isc.com> <NELSON.90Sep28233146@image.clarkson.edu> <4132@lib.tmc.edu>
Reply-To: jim@rwsys.UUCP (James Wyatt KA5VJL                .)
Organization: R/W Systems, Irving Texas, 75060-6055
Lines: 42

On one hand, Jay writes (in article <4132@lib.tmc.edu>):

>I think Russ is right on the money with this one. While I think the GNU Public
>Virus...er...license amounts to software theft and should be boycotted itself,
>the proper course for Xircom would have been to not use the code at all if
>they were unhappy with the terms of the license. I ceased work on a
>Clarkson-derived packet driver because of the GPV, and Xircom should have
	...
>I won't buy anything from them either.

Then his signature says something I *really* like to remember:

>Never ascribe to malice that which can
>adequately be explained by stupidity.

No one outside of (and few within) Xircom knows what *really* happened, but
I'd buy their ignorance on the matter. We have come dangerously close to
letting GPL code into things - it has good source at times, it's tempting to
use it. Some software engineers recycle code by hoarding any code they can
find and cutting/pasting small (or large) parts of it into later work. Things
like reading the rest of the package for GPL can slip up. Once others within
(or outside of) the group find out, the *only* honarable thing to do is
withdraw the product and go back to the drawing board. Asking them to then
publish the source is either greedy or stupid. Sounds like sour grapes too.

I had to develop a network password encryption routine for my employer last
year when one of the other SEs brought a program over to scavenge. "Where did
it come from?" got a reply of "... a BBS, it's gotta be public!" - Bzzzzt!
It was RCRYPT.EXE from Tandy's MSDOS - I checked where he didn't in the data
area. It didn't put a banner up on use.

I like GPL code (I am using GNU EMACS - that's why this is so long 8{) and
I offer it to anyone who wants it. I also recommend against using it for
anything more than study or personal use. It is just too easy to goof and
use it in something you *don't* want to share in source form. Xircom makes
very good products and has supported us very well - what else am I supposed
to use on a laptop? I will be waiting for TCP/IP drivers, but I will *not*
stop supporting a company that supports me and *tries* to do the right thing.
Until then, their Novell and 3Com(munist) drivers work. On with Netware 3.1!
----
James Wyatt (KA5VJL) - Standard disclaimer applies...          (H)214-579-0425
{letni.lonestar.org,merch.tandy.com}!rwsys.lonestar.org!jim    (W)817-390-2864