All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Ben Collins <bcollins@debian.org>
Cc: Adrian Bunk <bunk@fs.tum.de>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Non-GPL modules
Date: Thu, 18 Oct 2001 19:15:44 +0200	[thread overview]
Message-ID: <3BCF0E40.435D512D@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1011018101831.603A-100000@chaos.analogic.com> <3BCF0B10.CFA9E3FB@evision-ventures.com> <20011018131608.C10952@visi.net>

Ben Collins wrote:
> 
> On Thu, Oct 18, 2001 at 07:02:08PM +0200, Martin Dalecki wrote:
> > >
> > > Review of the driver source-code by a competent hardware designer,
> > > who knows how to read code, will give away the trade secret. Then
> > > anybody, who hasn't bothered to invest the millions of dollars of
> > > Engineering development cost, can make one of these cheaper and
> > > put us out of business.
> >
> > And what about the simple fact that the tainted flag will become
> > entierly useless when in fact most of us will be using tainted
> > kernel? Hey anyway most of us are now deploying "tainted" linux
> > distributions anyway and NOT GNU/Linux Debian. Most of use use
> > distros and kernels far away from the official Linus kernel too, so
> > this flagging doesn't help anybody it's just BLOAT.
> 
> So you think it is the responsibility of the l-k hackers to field bugs
> against highly hacked and forked versions of the kernel from a distro
> that you use?


Of course not, I never said that. But introducting this
stiupid tagging wan't help them anyway... so why do they introduce it?
The same solution applys as ever - just say: "We don't care about
kernels different from anything on ftp.kernel.org." and let it be...
I really see no advantage in this tagging. It's a common trap
in the western world to beleve that the introduction of some
"anti law" is actually preventing "voilence" from happenning.

  reply	other threads:[~2001-10-18 17:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 13:15 Non-GPL modules Richard B. Johnson
2001-10-18 13:38 ` Adrian Bunk
2001-10-18 13:58   ` Richard B. Johnson
2001-10-18 14:11     ` Ben Collins
2001-10-18 14:46       ` Richard B. Johnson
2001-10-18 14:53         ` Peter T. Breuer
2001-10-18 15:21           ` Richard B. Johnson
2001-10-18 15:40             ` Peter T. Breuer
2001-10-18 16:40               ` Jan Niehusmann
2001-10-18 17:02         ` Martin Dalecki
2001-10-18 17:16           ` Ben Collins
2001-10-18 17:15             ` Martin Dalecki [this message]
2001-10-18 18:06               ` Mark Hahn
2001-10-18 14:06   ` Ben Collins
2001-10-18 14:04 ` M. R. Brown
2001-10-18 14:31   ` Jesper Juhl
2001-10-18 14:37   ` Martin Donnelly
2001-10-18 14:50     ` Arjan van de Ven
2001-10-18 15:48     ` M. R. Brown
2001-10-20 22:08     ` Alan Cox

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=3BCF0E40.435D512D@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=bcollins@debian.org \
    --cc=bunk@fs.tum.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.