public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: walt <w41ter@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Words of wisdom from Theo de Raadt
Date: Fri, 27 Jun 2008 00:14:04 -0400	[thread overview]
Message-ID: <4864690C.2090504@garzik.org> (raw)
In-Reply-To: <g41j3i$eou$1@ger.gmane.org>

walt wrote:
> There is a thread "Continuation of OpenBSD's Stop the Blob" in progress
> in the openbsd.misc mailing list that may (or may not) be of interest
> to the Linux kernel devs.

As usual, Theo is clueless and uses propaganda to advance his agenda.

Specifically, in his email he mentions Intel ethernet being undocumented 
-- false.  The hardware docs are on SourceForge.

There are plenty of other examples of Linux people working to open up 
hardware documentation.  Many formerly-closed docs are posted at 
http://gkernel.sourceforge.net/specs/ or on ALSA's doc FTP site.

But the truth does not fit Theo's narrative, so....

	Jeff




  reply	other threads:[~2008-06-27  4:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27  2:26 Words of wisdom from Theo de Raadt walt
2008-06-27  4:14 ` Jeff Garzik [this message]
2008-06-27 12:04   ` markus reichelt

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=4864690C.2090504@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w41ter@gmail.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