linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Fluke <fluke@gibson.mw.luc.edu>
Cc: linux-poweredge@dell.com, linux-kernel@vger.kernel.org
Subject: Re: Dell vs. GPL
Date: Sat, 28 Jun 2003 21:16:19 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10306282112400.1116-100000@master.linux-ide.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0306280005000.29249-100000@gibson.mw.luc.edu>


First since it effects ATA it is my issue for the most part.
You have no stake or issue to pursue GPL violations if there are any.
Three, until you have copyright status, you have not right to invoke GPL
unless you are a customer of Dell, and are not bound by a contract to
Dell.  So get your facts first.

If there is a GPL issue with Dell and it involves my work, my lawyers will
contact Dell.

Cheers and have a good day.

Andre Hedrick
LAD Storage Consulting Group

On Sat, 28 Jun 2003, Fluke wrote:

>   Dell is providing binary only derived works of the Linux kernel and the 
> modutils package at ftp://ftp.dell.com/fixes/boot-floppy-rh9.tar.gz
> 
>   The GPL appears to provide four terms under section 3 that Dell may 
> legally redistribute these works:
> 
> - In regards to GPL 3a, Dell does *NOT* provide the source code as part of 
> the tar.gz
> - In regards to GPL 3b, Dell does *NOT* provide a written offer as part of 
> the tar.gz
> - In regards to GPL 3c, Dell does *NOT* provide information regarding an 
> offer to the source code as part of the tar.gz
> - Lastly, Dell does *NOT* provide equivalent access to the source code 
> from the same ftp site
> 
>   I contacted Dell support and recieved confirmation that Dell does not 
> intend to provide the source code to these binary works.  He explained 
> that all Dell fixes are licensed by Dell from third parties for use by 
> Dell customers in binary only form and "Dell does not intend the fixes to 
> be open source products."
> 
>   If they don't want to honor the GPL with their fixes, why do they 
> continue to claim to take Linux seriously and why does RedHat continue to 
> back them?
> 
>   This is not the first time I have run into Dell trying to mislead 
> customers in regards to open source.  Dell continues to distribute their 
> ESM kernel module under an "open_src" directory and a license which 
> redistricts use, modification and redistribution.  I'm not sure how it 
> could ever qualify as an OSI approved license but it is clear that Dell is 
> trying to pass it off as such.
> 
>   I have also tried to contact RedHat activities but based on the responce 
> that I got from Mark Webbink, I don't think RedHat is prepaired to do 
> anything about it.
> 
>   Is the GPL as it applies to the kernel intended to be a legal set of 
> requirements or simply a set of optional guidelines like Dell/RedHat seems 
> to be treating it?
> 
> Thanks
> 
> -
> 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/
> 


  parent reply	other threads:[~2003-06-29  4:05 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28  5:51 Dell vs. GPL Fluke
2003-06-28  6:12 ` Joshua Penix
2003-06-28 15:05   ` Doug McNaught
2003-06-28 15:12     ` Svein Ove Aas
2003-06-28 15:18       ` Doug McNaught
2003-06-28 15:49         ` Arjan van de Ven
2003-06-29  4:22       ` Andre Hedrick
2003-06-29 10:33         ` Alan Cox
2003-06-30  4:07           ` Andre Hedrick
2003-06-30  6:39             ` Miles Bader
2003-06-30  6:56               ` Andre Hedrick
2003-06-30  9:45                 ` Miles Bader
2003-07-09 23:28                   ` Thomas Dodd
2003-07-10  2:48                     ` Miles Bader
2003-07-10 14:41                       ` Thomas Dodd
2003-07-10 15:05                         ` Gene Heskett
2003-07-10 15:20                           ` Richard B. Johnson
2003-07-10 15:52                             ` Mr. James W. Laferriere
2003-07-10 19:04                           ` Thomas Dodd
2003-07-10 19:22                             ` OT: " Dana Lacoste
2003-06-30 15:49                 ` Valdis.Kletnieks
2003-06-30 16:54                   ` Andre Hedrick
2003-06-30 17:50                     ` Valdis.Kletnieks
2003-06-30 18:28                       ` Andre Hedrick
2003-06-30 20:43                         ` Valdis.Kletnieks
2003-06-30 20:44                           ` Andre Hedrick
2003-06-30 21:25                             ` Valdis.Kletnieks
2003-06-30 21:34                               ` Andre Hedrick
2003-07-01  5:03                             ` vlad
2003-07-01  5:27                               ` Andre Hedrick
2003-07-01 12:50                             ` Henning P. Schmiedehausen
2003-06-30 20:55                           ` Trever L. Adams
2003-06-30 20:44                         ` Bernd Eckenfels
2003-06-30 20:48                           ` Andre Hedrick
2003-07-01  5:53                             ` Anders Karlsson
2003-07-01  6:56                               ` jw schultz
2003-07-01  7:21                                 ` Andre Hedrick
2003-07-01 15:38                                 ` Trever L. Adams
2003-07-01 13:17                               ` Henning P. Schmiedehausen
2003-07-01 15:36                               ` vlad
2003-07-01 16:05                                 ` Scott Robert Ladd
2003-07-01 16:45                                   ` Trever L. Adams
2003-07-01 17:45                                     ` Andre Hedrick
2003-07-09 23:24                                 ` Thomas Dodd
2003-07-01 12:46                           ` Henning P. Schmiedehausen
2003-06-30 17:22             ` Alan Cox
2003-06-30 17:37               ` Andre Hedrick
     [not found]         ` <3BZo.5iM.27@gated-at.bofh.it>
2003-06-29 14:04           ` Florian Weimer
2003-06-28 18:54 ` Alan Cox
2003-06-29 17:47   ` Fluke
2003-06-29 17:48     ` Arjan van de Ven
2003-06-29  4:16 ` Andre Hedrick [this message]
2003-06-29 11:49   ` Fluke
2003-06-29 21:45   ` David Schwartz
2003-06-30  4:01     ` ahorn
2003-06-30  4:10       ` Andre Hedrick
2003-06-30  6:59         ` ahorn
2003-06-30  8:29           ` David Schwartz
2003-06-30  8:29             ` Andre Hedrick
2003-06-30  8:44               ` David Schwartz
2003-06-30  5:59       ` David Schwartz
2003-06-30  6:57         ` ahorn
2003-06-30  7:39           ` Anders Karlsson
2003-06-30  8:24           ` David Schwartz
2003-06-30  9:02             ` root
2003-06-30  9:17               ` David Schwartz
2003-06-30 15:57                 ` Jamie Lokier
2003-06-30  4:23     ` Andre Hedrick
2003-07-14 20:35 ` Fluke
2003-06-29 14:24 Ricardo Galli
2003-06-29 19:50 ` Jamie Lokier
2003-06-29 19:58   ` Ricardo Galli
2003-06-29 20:21     ` Valdis.Kletnieks
2003-06-29 20:42     ` Jamie Lokier
2003-06-29 20:57       ` Russell King
2003-06-29 21:21         ` Jamie Lokier
2003-06-30 23:14       ` David Weinehall
2003-06-29 20:02   ` Matthias Schniedermeyer
2003-06-29 20:54   ` Bernd Petrovitsch
     [not found] <Pine.LNX.4.44.0307020931260.1400-100000@humbolt.us.dell.com>
2003-07-02 16:25 ` Andre Hedrick
     [not found] <20030715191651.GA6946@delft.aura.cs.cmu.edu>
2003-07-17  3:15 ` Fluke

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=Pine.LNX.4.10.10306282112400.1116-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=fluke@gibson.mw.luc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-poweredge@dell.com \
    /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;
as well as URLs for NNTP newsgroup(s).