From: Samuel Flory <sflory@rackable.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: John Jasen <jjasen@realityfailure.org>,
Philip Dodd <smpcomputing@free.fr>,
linux-kernel@vger.kernel.org
Subject: Re: UnitedLinux violating GPL?
Date: Fri, 10 Jan 2003 11:05:07 -0800 [thread overview]
Message-ID: <3E1F1963.500@rackable.com> (raw)
In-Reply-To: 20030110024710.GA19760@gtf.org
Jeff Garzik wrote:
>On Thu, Jan 09, 2003 at 09:40:50PM -0500, John Jasen wrote:
>
>
>>On Thu, 9 Jan 2003, Philip Dodd wrote:
>>
>>
>>
>>>Jeff Garzik wrote:
>>>
>>>
>>>>Anybody know where the source rpm for UnitedLinux kernel is?
>>>>[to be distinguished from kernel-source rpm]
>>>>
>>>>
>>if they supply the kernel source rpm, how are they in violation? Since you
>>can compile a kernel from the source rpm.
>>
>>
>
>Read the GPL :) The source code "preferred form" is clearly not an
>on-disk kernel tree with no information about the changes [patches]
>that were processed in a specific sequence, to produce that end result.
>
>
>
Actually the reverse could be much more easily said to be true. If
they only supplied the src.rpm, and not the source rpm more people
would scream than the reverse. The number of people who know how to
produce a custom kernel from a src.rpm is fairly limited. Keep in mind
most of UL's customer are not kernel hackers.
Of course the correct thing to do is simply provide both and make
people happy. A determined person can still get what ever they want out
of either form. Making it hard just leads to your customers and the
community hating you.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-01-10 19:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 22:27 UnitedLinux violating GPL? Jeff Garzik
2003-01-09 22:45 ` Philip Dodd
2003-01-10 0:27 ` Adrian Bunk
2003-01-10 0:36 ` Cort Dougan
2003-01-10 2:40 ` John Jasen
2003-01-10 2:47 ` Jeff Garzik
2003-01-10 19:05 ` Samuel Flory [this message]
2003-01-09 22:53 ` Cort Dougan
2003-01-09 23:00 ` Tom Sightler
2003-01-09 23:06 ` GertJan Spoelman
2003-01-09 23:19 ` Lars Marowsky-Bree
2003-01-09 23:23 ` Jeff Garzik
2003-01-10 10:38 ` Pavel Machek
2003-01-17 20:12 ` Jeff Garzik
2003-01-09 23:45 ` Jeff V. Merkey
2003-01-09 22:46 ` Jeff Garzik
2003-01-10 1:22 ` Jeff V. Merkey
2003-01-10 0:31 ` Aaron T Porter
2003-01-10 8:34 ` Hubert Mantel
2003-01-10 10:46 ` Henning P. Schmiedehausen
2003-01-11 10:52 ` Christoph Hellwig
2003-01-10 10:55 ` Horst von Brand
2003-01-10 12:19 ` Adrian Bunk
2003-01-11 16:34 ` Horst von Brand
2003-01-11 19:27 ` David Woodhouse
2003-01-12 13:15 ` Hubert Mantel
2003-01-12 16:50 ` Alan Cox
2003-01-13 13:12 ` Dave Jones
2003-01-12 13:23 ` Horst von Brand
2003-01-11 10:50 ` Christoph Hellwig
2003-01-11 11:00 ` Andre Hedrick
2003-01-11 14:46 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 12:25 Nicholas Berry
[not found] <20030109224013$6e5e@gated-at.bofh.it>
[not found] ` <20030111110011$3252@gated-at.bofh.it>
2003-01-11 11:51 ` Andi Kleen
2003-01-11 14:28 ` Christoph Hellwig
2003-01-11 14:44 ` Andi Kleen
2003-01-11 20:34 Protasevich, Natalie
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=3E1F1963.500@rackable.com \
--to=sflory@rackable.com \
--cc=jgarzik@pobox.com \
--cc=jjasen@realityfailure.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smpcomputing@free.fr \
/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