public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <spstarr@sh0n.net>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Binary drivers and GPL
Date: Sun, 5 Jan 2003 03:01:28 -0500	[thread overview]
Message-ID: <200301050301.28227.spstarr@sh0n.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10301042352540.421-100000@master.linux-ide.org>

Because when I look at the big picture.

If I look at a group of industries say, SCSI companies (say there are 3 only).

Company A: Releases specs to community to write a driver.

Company B: Refuses to release anything

Company C: Refuses to release anything

Now, because company A has released its specs Company B and C are free to view 
this and use ideas to improve their products thus hurting company A.

Now company A sees the other companies improving the products due to their 
specs being released and decides that all new products will be closed.

Now we have binary-only modules for all SCSI cards and more dependency on 
companies which to me denies me access to newer kernels due to API 
inconsistancies and thus kills my help in kernel development.

THIS is why I'm against binary drivers in the long run.

On Sunday 05 January 2003 2:54 am, Andre Hedrick wrote:
> Shawn,
>
> Why are you against it, and do you know that 2.5/2.6/3.0 has already
> modelled a method to do make it so painful to prevent binarys from being
> useful for the most part?
>
> Andre Hedrick
> LAD Storage Consulting Group
>
> On Sun, 5 Jan 2003, Shawn Starr wrote:
> > Enough is enough! I'm SO tired of hearing this over and over now. But
> > since it's raging on I might as well throw some coal into the fire a
> > little ;-)
> >
> > As much as I would love to see a ban on binary drivers to protect the
> > kernel, this issue isn't going away. Not only that but I'd love to see a
> > module blacklist in which a non-tainted kernel refuses to load binary
> > drivers that are not GPL.
> >
> > We have to make sure that we restrict binary drivers as much as possible
> > because other companies may decide that they don't need to release their
> > specs/sources anymore because binary drivers become the norm and because
> > their competition is also not releasing their specs/code. This I fear is
> > the danger if we go down this road. We can't allow companies to dictate
> > indirectly how a kernel will function.
> >
> > Shawn.
> >
> >
> >
> > -
> > 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:[~2003-01-05  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10301042352540.421-100000@master.linux-ide.org>
2003-01-05  8:01 ` Shawn Starr [this message]
2003-01-05  8:25   ` Binary drivers and GPL Andre Hedrick
2003-01-05  9:09     ` Shawn Starr
2003-01-05  9:33       ` Andre Hedrick
2003-01-05  7:47 Shawn Starr

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=200301050301.28227.spstarr@sh0n.net \
    --to=spstarr@sh0n.net \
    --cc=andre@linux-ide.org \
    --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