From: jon@fourwinds.com (Jon Steinhart)
Subject: [TUHS] V7 Addendem
Date: Wed, 06 Dec 2017 08:15:20 -0800 [thread overview]
Message-ID: <201712061615.vB6GFKYd013874@darkstar.fourwinds.com> (raw)
In-Reply-To: <1512576671.3978479.1196132360.0C9F95D9@webmail.messagingengine.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
Random832 writes:
> On Tue, Dec 5, 2017, at 20:07, Warren Toomey wrote:
> > Ken tried to send it out, but the lawyers kept
> > stalling and stalling and stalling.
> >
> > When the lawyers found out about it, they called every
> > licensee and threatened them with dire consequences if they
> > didn’t destroy the tape, after trying to find out how they got
> > the tape. I would guess that no one would actually tell them
> > how they came by the tape (I didn’t).
>
> I have a question, if anyone has any idea... is there any recorded
> knowledge about *who was driving*? That is, beyond "the lawyers", who on
> the business side of AT&T was making the policy decisions that led to
> the various sometimes bizarre legal actions that caused problems for the
> Unix world, and to what end (was there some way they expected to profit?
> liability concerns?)
>
> In other words, what was the basis of the legal department's mandate to
> try to shut these things down? (This question is also something I've
> wondered for some non-Unix stuff like the E911 document, but that's not
> relevant to this list)
Can't answer your question directly, but I think that some of this was
the result of the prior consent decree banning them from being in the
data business. I seem to recall that it was technically illegal for
them to sell SW and don't know how giving it away would have been viewed.
next prev parent reply other threads:[~2017-12-06 16:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 0:33 Warner Losh
2017-12-06 1:07 ` Warren Toomey
2017-12-06 16:11 ` Random832
2017-12-06 16:15 ` Jon Steinhart [this message]
2017-12-06 18:39 ` Clem Cole
2017-12-06 18:49 ` [TUHS] V7 Addendem [ really lawyers and AT&T consent decree ] Jon Steinhart
2017-12-06 18:53 ` Warner Losh
2017-12-06 18:58 ` Jon Steinhart
2017-12-06 18:54 ` Clem Cole
2017-12-06 19:20 ` William Pechter
2017-12-07 14:26 ` Ron Natalie
2017-12-06 19:23 ` William Corcoran
2017-12-06 20:30 ` Kurt H Maier
2017-12-06 23:59 ` George Michaelson
2017-12-07 14:03 ` Ron Natalie
2017-12-07 15:34 ` William Corcoran
2017-12-07 5:08 ` Jon Steinhart
2017-12-07 15:09 ` Larry McVoy
2017-12-11 18:17 ` Paul Winalski
2017-12-11 18:39 ` Clem Cole
2017-12-12 0:27 ` Steve Johnson
2017-12-12 1:05 ` [TUHS] V7 Addendem [ really lawyers and AT&T consent decree ] [ and besides it's "Addendum" ] Jon Steinhart
2017-12-12 1:45 ` [TUHS] MERT? Larry McVoy
2017-12-12 2:09 ` Jon Steinhart
2017-12-13 17:09 ` [TUHS] V7 Addendem [ really lawyers and AT&T consent decree ] Jason Stevens
2017-12-13 17:05 ` Jason Stevens
2017-12-11 20:11 ` William Cheswick
2017-12-11 23:26 ` Arthur Krewat
2017-12-06 13:36 [TUHS] V7 Addendem Doug McIlroy
2017-12-06 14:29 ` Clem Cole
2017-12-06 14:45 ` Clem Cole
2017-12-07 18:03 Noel Chiappa
2017-12-07 18:38 ` Jon Steinhart
2017-12-08 13:01 Noel Chiappa
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=201712061615.vB6GFKYd013874@darkstar.fourwinds.com \
--to=jon@fourwinds.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).