mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Kenneth Lavrsen <kenneth@lavrsen.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pwc+pwcx is not illegal
Date: Sat, 28 Aug 2004 15:11:38 +0200	[thread overview]
Message-ID: <20040828131138.GZ12772@fs.tum.de> (raw)
In-Reply-To: <6.1.2.0.2.20040828141825.01e5e7d8@inet.uni2.dk>

On Sat, Aug 28, 2004 at 02:18:54PM +0200, Kenneth Lavrsen wrote:
> 
> >In the case of pwc+pwcx, pwcx (the decoder module) is completely useless
> >without pwc (the driver module), and thus is obviously falling in the
> >second class described above.
> 
> It was accepted for 4 years.
> And then suddenly is was crippled without a replacement - because of a 
> personal disagreement.

Which "personal disagreement"?

There was a hook for a binary-only module in the kernel, and as soon as 
Greg was made aware of it he removed it.

> This is the issue.
> Not the principle. Not the spirit of GPL which I support. I don't know why 
> so many of you always turn these debates into a matter of law and rules.
> 
> The issue that I keep on raising that that none of the kernel maintainers 
> will answer is.
> 
> - Do you care about the 10000s of users that you harm?
> - Do you care at all about anything else than yourself and your principles?

The policy in the kernel is quite liberal concerning non-free code 
(compare with e.g. the FSF and Debian).

I'd prefer it if non-GPL modules were completely forbidden, but although 
Linus stated himself that binary-only modules are a pain in the ass, 
they are tolerated in the Linux kernel.

> - Could this have been handled in a better way that would lead to the 
> pwc/pwcx being handled according to the new policy and so that the users 
> would not be affected?

Which "new policy"?

The fact that hooks for non-free modules are not allowed isn't new.

> Too many of you keep on defending bad behavour hiding behind the GPL.

If non-GPL modules were simply completely forbidden, there would be no  
reason for you to complain...

> When a commercial company sells something and cuts support too early - the 
> customers complain and stop buying more products from that supplier.
> Many companies have for this reason discovered that the only way to run a 
> successful business is to be driven by the "Total Customer Satisfaction" 
> principle.
> I am sure many of you are familiar with it from your daytime jobs.

Thankfully, the Linux kernel development is leaded by people for whom 
technical things are more important than marketing issues.

There are many examples like e.g. EVMS or the current reiser4 
discussion where "we really need it because of $important_reason" code 
isn't accepted as it is for this or that technical reason.

I might not always agree with a specific decision, but generally it 
leads in the long term to a better kernel.

> Kenneth

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-08-28 13:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-28 12:18 Kenneth Lavrsen
2004-08-28 13:11 ` Adrian Bunk [this message]
2004-08-28 15:24   ` Kenneth Lavrsen
2004-08-29 14:02   ` Alan Cox
2004-09-01 22:51     ` Rogier Wolff
  -- strict thread matches above, loose matches on Subject: below --
2004-08-28  8:15 Gabucino
2004-08-28 10:30 ` Vojtech Pavlik
2004-08-27 19:18 Albert Cahalan
2004-08-27 19:29 ` Linus Torvalds
2004-08-27 20:06   ` Kenneth Lavrsen
2004-08-27 20:21     ` Linus Torvalds
2004-08-27 20:24     ` David S. Miller
2004-08-27 20:26     ` Paul Jakma
2004-08-30 17:41       ` Brian Litzinger
2004-08-27 20:38     ` David Ford
2004-08-27 20:57   ` Albert Cahalan
2004-08-27 21:04     ` Greg KH
2004-08-27 21:09     ` Linus Torvalds
2004-08-29 14:00   ` Alan Cox
2004-08-29 16:33     ` Nemosoft Unv.
2004-08-29 15:42       ` Alan Cox
2004-08-29 17:16       ` Norbert van Nobelen
2004-08-27 19:34 ` Paulo Marques
2004-08-27 21:34   ` Albert Cahalan

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=20040828131138.GZ12772@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=kenneth@lavrsen.dk \
    --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

all inboxes | Powered by JetHome®