From: Petro <petro@auctionwatch.com>
To: "Paul G. Allen" <pgallen@randomlogic.com>
Cc: "Linux kernel developer's mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: SSSCA: We're in trouble now
Date: Tue, 5 Mar 2002 20:26:30 -0800 [thread overview]
Message-ID: <20020306042630.GG22934@auctionwatch.com> (raw)
In-Reply-To: <3C7FDAB1.6F687440@randomlogic.com> <1015014449.16520.9.camel@unaropia> <1015014637.811.0.camel@bip> <1015018176.16520.66.camel@unaropia> <87henzoqgy.fsf@CERT.Uni-Stuttgart.DE> <3C80400F.9A3B49CA@randomlogic.com>
In-Reply-To: <3C80400F.9A3B49CA@randomlogic.com>
On Fri, Mar 01, 2002 at 06:59:27PM -0800, Paul G. Allen wrote:
> Florian Weimer wrote:
> >
> > Shawn Starr <spstarr@sh0n.net> writes:
> >
> > > Linux doesnt use the BIOS if you tell it not to, if it can avoid using
> > > it. It will :)
> >
> > The problem is that if you don't follow the Trusted Computing Platform
> > Alliance booting procedure, you won't see much mass-compatible content
> > on the Internet any longer.
> >
> > The solution is simple: go and create your own content, and share it
> > with your friends. But you won't get Hollywood movies this way.
> >
>
> Not watching Hollywood movies sure won't end my life. I can do without
> them, and I'm sure eventually many other people will realize they can
> too. I already know many that stopped going to movies when the price hit
> $6.00 (it's $8.50 here now), and several that stopped buying and renting
> them as well.
Sure, but then if Linux cannot (for either legal men-with-guns reasons
or technical reasons) utilize this content, you lose at the desktop.
And if Linux cannot serve this traffic, you lose at the server.
And then you lose the critical support many of the people working on
it who need to do this stuff to make money.
If this becomes law, Linux in some fashion will support it. IBM and
the like are (or will be) making too much money off it not to.
And if the government tells you how or what to do with the contents
of your computer, you will because if the financial interests are
strong enough, the laws will get passed, the constitutions will get
modified, and the courts will accept it.
And then you have two choices.
Do what they tell you, or go to jail. (Well, there is a third
choice, but it would best not be discussed here).
--
Share and Enjoy.
next prev parent reply other threads:[~2002-03-06 4:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 19:46 SSSCA: We're in trouble now Paul G. Allen
2002-03-01 20:27 ` Shawn Starr
2002-03-01 20:30 ` Xavier Bestel
2002-03-01 21:29 ` Shawn Starr
2002-03-01 22:19 ` Alan Cox
2002-03-02 3:08 ` Neale Banks
2002-03-02 3:03 ` eddantes
2002-03-02 18:32 ` Alan Cox
2002-03-01 22:47 ` Florian Weimer
2002-03-02 2:59 ` Paul G. Allen
2002-03-06 4:26 ` Petro [this message]
2002-03-06 4:41 ` Trever L. Adams
2002-03-06 16:26 ` Rik van Riel
2002-03-06 17:03 ` Richard B. Johnson
2002-03-06 18:16 ` Paul G. Allen
2002-03-06 18:35 ` Trever L. Adams
2002-03-07 22:54 ` Florian Weimer
2002-03-08 2:12 ` Tom Rauschenbach
-- strict thread matches above, loose matches on Subject: below --
2002-03-02 0:21 Thomas Hood
2002-03-02 8:35 ` Florian Weimer
2002-03-02 17:34 ` M. Edward (Ed) Borasky
2002-03-04 8:30 ` Helge Hafting
2002-03-04 9:40 ` Martin Eriksson
2002-03-04 17:02 ` Paul G. Allen
2002-03-06 4:41 ` Petro
2002-03-06 9:27 ` Helge Hafting
2002-03-02 15:30 ` Paul P Komkoff Jr
2002-03-02 21:58 ` Rik van Riel
2002-03-03 1:29 ` Greg Louis
2002-03-06 4:51 ` Petro
2002-03-02 17:47 ` Jurgen Botz
2002-03-06 5:00 ` Petro
2002-03-06 16:42 ` Alan Cox
2002-03-06 18:24 ` Paul G. Allen
2002-03-06 23:56 ` Petro
2002-03-04 19:27 Jesse Pollard
2002-03-06 17:20 Ed Vance
2002-03-06 18:31 ` Paul G. Allen
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=20020306042630.GG22934@auctionwatch.com \
--to=petro@auctionwatch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pgallen@randomlogic.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