From: Hubert Mantel <mantel@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: UnitedLinux violating GPL?
Date: Fri, 10 Jan 2003 09:34:10 +0100 [thread overview]
Message-ID: <20030110083409.GH30114@suse.de> (raw)
In-Reply-To: <20030109222748.GA3993@gtf.org>
Hi,
On Thu, Jan 09, Jeff Garzik wrote:
> Anybody know where the source rpm for UnitedLinux kernel is?
> [to be distinguished from kernel-source rpm]
Sure, it's here:
ftp.suse.com:/pub/unitedlinux/1.0/src/kernel-source-2.4.19.SuSE-82.nosrc.rpm
This RPM contains the individual patches as well as the specfile to create
the kernel-source.rpm. It's only missing the vanilla kernel source tarball
in order to save space (this tarball is available on every other ftp
server in the internet anyway).
For creation of the individual binary kernel RPMs you need the following
source RPMs which are of course also available:
-rw-r--r-- 1 root root 18972 Oct 21 21:45 k_athlon-2.4.19-111.src.rpm
-rw-r--r-- 1 root root 168055 Oct 21 22:28 k_debug-2.4.19-79.src.rpm
-rw-r--r-- 1 root root 186467 Oct 21 22:04 k_deflt-2.4.19-120.src.rpm
-rw-r--r-- 1 root root 178477 Oct 21 22:04 k_psmp-2.4.19-115.src.rpm
-rw-r--r-- 1 root root 185329 Oct 21 22:21 k_smp-2.4.19-113.src.rpm
> AFAICS they are not distributing source code to their published kernel
> binaries... which is a very obvious GPL violation.
Any chance you could check the facts before accusing people publically?
> I'm also surprised the even-more-pro-GPL-than-me people have not jumped
> on UnitedLinux for not distributing source code.
Because they are probably not too lazy to check the facts before offending
people.
> Jeff, looking for useful [rumored] drivers/net patches
-o)
Hubert Mantel Goodbye, dots... /\\
_\_v
next prev parent reply other threads:[~2003-01-10 8:25 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
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 [this message]
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=20030110083409.GH30114@suse.de \
--to=mantel@suse.de \
--cc=jgarzik@pobox.com \
--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