public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <spstarr@sh0n.net>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: "Paul G. Allen" <pgallen@randomlogic.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SSSCA: We're in trouble now
Date: 01 Mar 2002 16:29:08 -0500	[thread overview]
Message-ID: <1015018176.16520.66.camel@unaropia> (raw)
In-Reply-To: <1015014637.811.0.camel@bip>
In-Reply-To: <3C7FDAB1.6F687440@randomlogic.com>  <1015014449.16520.9.camel@unaropia>  <1015014637.811.0.camel@bip>

Linux doesnt use the BIOS if you tell it not to, if it can avoid using
it. It will :)

On Fri, 2002-03-01 at 15:30, Xavier Bestel wrote:
> le ven 01-03-2002 à 21:27, Shawn Starr a écrit :
> > Trouble or not. We will defeat this garbage. I will not allow any or my
> > (Canada) country to tell me how to control my own systems let alone my
> > own hardware! 
> > 
> > Let them pass it, they won't be able to enforce it. I won't let my Linux
> > kernel become 'tainted' by closed binary drivers and I will really
> > actively get involved in defeating such measures in Linux kernel
> > modules.
> 
> You already use much BIOS with linux today, and tomorrow ACPI will be
> mandatory to use your box. Both are untrusted binary "drivers".
> 
> 	Xav
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



  reply	other threads:[~2002-03-01 21:24 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 [this message]
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
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=1015018176.16520.66.camel@unaropia \
    --to=spstarr@sh0n.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgallen@randomlogic.com \
    --cc=xavier.bestel@free.fr \
    /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