From: dmr@plan9.att.com dmr@plan9.att.com
Subject: status of C license and network
Date: Thu, 4 Jan 1996 22:23:41 -0500 [thread overview]
Message-ID: <19960105032341.GByQQfIInrr0DzRDet28--oauo3XJ83L7zkBycWhJmo@z> (raw)
Chad (yandros@mit.edu) wondered
Can we have machines with the CD source code on it on the internet?
All our machines are directly on the net (no firewall), and we're not
likely to be willing to put up a plan 9 machine that isn't on the net
in the same way.
The operative phrase in the license is "made available on a computer
network external to you or your organization." The source can be
on a machine that's also on the internet (as ours is), but you have to
arrange that it's not accessible from outside.
In combination, permissions adjustment and limiting the namespace
visible to visitors should be sufficient.
Dennis
next reply other threads:[~1996-01-05 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-05 3:23 dmr [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-01-03 1:08 yandros
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=19960105032341.GByQQfIInrr0DzRDet28--oauo3XJ83L7zkBycWhJmo@z \
--to=dmr@plan9.att.com \
/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).