9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Running Version 2 along with Version 3
Date: Tue, 30 Jan 2001 19:24:35 +0000	[thread overview]
Message-ID: <20010130192602.18E6B19A0F@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

>>problem is that you have to get proprietary info out of Sun and that
>>would kill any chance of a release.

no, you wouldn't. that's the annoying thing.
there are public ports of other systems to the sparcs (and SGIs) that reveal the details.
unfortunately, that doesn't necessarily remove the restrictions on the older plan 9 code.


[-- Attachment #2: Type: message/rfc822, Size: 3058 bytes --]

From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Running Version 2 along with Version 3
Date: Tue, 30 Jan 2001 19:23:48 +0100
Message-ID: <006201c08ae9$ca2354a0$0ab9c6d4@cybercable.fr>

From: Mike Acar <mike@trolltech.com>
> > You need a 2nd edition license to get the SUN material, and once you've
> > got it you can't expect any work based on it to be included in updates to
the
> > 3rd edition because we don't have the rights to release it that way.
>
> Meaning that the most we could do with the 2nd edition code would be look it
> over before reimplementing its functionality for the 3rd edition, and even
that
> I think I'd be somewhat hesitant to do; getting a SPARC booting but being
> unable to release the code seems a bit of a waste.

err, if you had a 2nd ed license you couldn't release the code under the
terms of the 3rd ed licence.  i'm not even sure that 'looking' at the code
would wouldn't taint a release to a 3rd ed site.

now, if you did a 3rd ed port to the sparc then i would imagine you
could release this work.  however, i am not a lawyer.  i think the
problem is that you have to get proprietary info out of Sun and that
would kill any chance of a release.

i believe the phrase 'like pulling teeth' was used in reference to
getting certain information from certain vendors.


             reply	other threads:[~2001-01-30 19:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30 19:24 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-31 15:07 rob pike
2001-01-30 21:41 geoff
2001-01-30 14:30 rob pike
2001-01-30 14:59 ` Mike Acar
2001-01-30 18:23   ` Boyd Roberts
2001-01-30 18:42     ` Mike Acar
2001-01-30 18:43     ` Christian Smith
2001-01-31 10:20 ` Bobby Dimmette
2001-01-30 10:51 forsyth
2001-01-30 14:23 ` Mike Acar
2001-01-29 19:35 rob pike
2000-06-20 14:51 presotto
2001-01-29 18:30 ` splite
2001-01-29 18:52   ` Mike Acar
2001-01-29 19:29     ` Boyd Roberts
2000-06-20 13:58 Bill Gunshannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010130192602.18E6B19A0F@mail.cse.psu.edu \
    --to=forsyth@caldo.demon.co.uk \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).