mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Andrews <jeremy@kerneltrap.com>
To: linux-kernel@vger.kernel.org
Subject: Noise { was: Linux 2.2.20pre10 }
Date: Mon, 22 Oct 2001 17:27:48 -0400	[thread overview]
Message-ID: <20011022172748.507bb7c4.jeremy@kerneltrap.com> (raw)


What is the problem?

Some seem to think the problem is:  Alan has censored security information.

But ask yourself, 'Why has he done this?'

He has made a very valid point.  And by affecting the United States' users and
developers of Linux, we in turn stand to affect those around us.  Living in the
US, it looks as though we are in for some rough times.  Freedom is being
redefined around us.

Learn.  Educate.  Communicate.

There is a lot of information available on the internet.  Whether or not Alan
includes cliff-notes to his kernel patches, the larger problem still remains. 
And has potential to get much worse.

A good place to start:
  http://www.eff.org/
  
Specifically regarding the Digital Millennium Copyright Act (DMCA):
  http://www.eff.org/IP/DMCA
  http://www.dibona.com/dmca
  http://www.anti-dmca.org/

Take a look at the map here, and think a moment:
  http://thefreeworld.net/

There are voices in this noise that need to be heard.  Speak out!  But please,
speak towards the root of the problem.  Towards a government whos rhetoric is:
'Enduring Freedom'.

What is freedom?

If we have freedom left, and I believe we do, we must use it now.

--
 Jeremy Andrews    <mailto:jeremy@kerneltrap.com>
 PGP Key ID: 8F8B617A  http://www.kerneltrap.com/

                 reply	other threads:[~2001-10-22 21:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20011022172748.507bb7c4.jeremy@kerneltrap.com \
    --to=jeremy@kerneltrap.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®