home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky misc.legal:21664 comp.sys.sun.misc:5974
- Newsgroups: misc.legal,comp.sys.sun.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!usc!news.cerf.net!shrike.irvine.com!jsweet
- From: jsweet@irvine.com (Jerry Sweet)
- Subject: Re: Put away your Motif manual; Sun's lawyers are at the door!
- In-Reply-To: Article from Steven Grimm on 22 Dec 1992 13:12:57 -0800.
- <1h80cpINNevp@spud.Hyperion.COM>
- Sender: usenet@irvine.com (News Administration)
- Organization: Irvine Compiler Corp., Irvine, California, USA
- Date: Tue, 22 Dec 1992 23:54:13 GMT
- To: koreth@spud.Hyperion.COM (Steven Grimm)
- Message-ID: <BzoqED.C0F@irvine.com>
- Lines: 22
-
- After reading the license agreement for myself, I grok that you CAN'T
- develop software under Solaris 2.1 **AT ALL**. Heh. Methinks the
- lawyers failed to run the language past any of the technical people.
-
- To quote from the license:
-
- > Developed Programs are to be OPEN LOOK(R) compliant and have an
- > application programming interface that is the same as that of
- > Software;
-
- So your application must have an API. And the API must be the SAME as
- that of "Software" (Solaris 2.1). This obviously means that you can
- only sell software that re-implements Solaris 2.1. Which would
- probably be prosecuted by Sun as some sort of intellectual property
- violation.
-
- So...Sun shot themselves in the feet. You CAN'T develop software for
- Solaris 2.1. At All. Not without violating their license.
-
- Disclaimer: this is not legal advice; just my interpretation of Sun's
- Solaris 2.1 license agreement. I predict that Sun rethinks this policy.
-
-