LKML Archive on
help / color / mirror / Atom feed
From: (Vincent C Jones)
Subject: Re: protecting source code in 2.6
Date: Sat, 22 May 2004 10:54:21 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

In article <> Richard B. Johnson wrote:
   [ rant on proprietary kernel software removed ]
>There are very few persons who will allow you to insert secret
>code into their kernels where it could destroy everything of
>value to them.

If only this were true... but there are how many million Windows users?

Oh, and if they're too stupid to count, there are also large numbers of
HP-UX, AIX, Solaris and other proprietary UNIX variants out there, not
to mention IBM mainframe and AS/400 shops...

Oh, and if you only mean Linux users, we'll ignore all the ATI Radeon
and Nvidea sufferers, and vmware users, and winmodem users, and every
driver for a device which loads firmware, and every PC which does not
release source code for the BIOS, and . . .

Arguments tend to loose a lot of their impact when based on religion
rather than realism.
Dr. Vincent C. Jones, PE              Expert advice and a helping hand
Computer Network Consultant           for those who want to manage and
Networking Unlimited, Inc.            control their networking destiny
14 Dogwood Lane, Tenafly, NJ 07670  +1 201 568-7810  Fax: +1 201 568-7269 

       reply	other threads:[~2004-05-22 16:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2004-05-22 14:54   ` Vincent C Jones [this message]
2004-05-22 23:24     ` Benjamin Herrenschmidt
2004-05-23  0:56       ` Vincent C Jones
2004-05-20 13:21 Jinu M.
2004-05-20 14:08 ` Sam Ravnborg
2004-05-20 14:08 ` Giuliano Pochini
  -- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:18 Jinu M.
2004-05-20 13:44 ` John Bradford
2004-05-20 14:05 ` Bartlomiej Zolnierkiewicz
2004-05-20 15:43 ` Richard B. Johnson
2004-05-21  8:29 ` Matthias Andree
2004-05-21 16:05 ` Rik van Riel
2004-05-21 19:49 ` Bill Davidsen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: protecting source code in 2.6' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).