From: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Red Hat ES4 GPL Issues?
Date: Wed, 22 Feb 2006 17:11:50 -0700 [thread overview]
Message-ID: <43FCFDC6.9090109@soleranetworks.com> (raw)
I have been working on 2.6.9 kernels with red hat ES4 series
distributions (we purchased and have a license). I noticed that the ES4
series kernels
which support NPTL libs no longer provide the source code with the
distribution (the installed kernels sources point to empty source trees
which
only contain makefiles). I have discovered we have to use our Red Hat
Network account in order to download the Source RPMs
(which are in fact provided).
We got the distro via electronic fullfilment, so we did not get the
SRPMS CD iso images by default. This was a deviation from how Red Hat
normally distributes source code with their Linux distro.
I am curious if Red Hat views requiring people subscribing to RHN as a
requirement to obtain source code is in conflict with the GPL. We
have no objection to downloading it since we have an account, but I
found it strange Red Hat, the leaders in Open Source and GPL
technology, now appear to block downloads of ES4 source code without a
subscription. Have I got it all wrong here, or is this borderline GPL
avoidance?
I am unable to locate the Source Code on any public servers at Red Hat.
Jeff
next reply other threads:[~2006-02-22 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 0:11 Jeff V. Merkey [this message]
2006-02-22 23:21 ` Red Hat ES4 GPL Issues? Joel Jaeggli
2006-02-23 0:19 ` Jeff V. Merkey
2006-02-23 8:50 ` Arjan van de Ven
2006-02-23 14:59 ` Chris Adams
2006-02-23 16:31 ` Nick Warne
2006-02-23 16:43 ` Arjan van de Ven
2006-02-23 18:15 ` Jeff V. Merkey
2006-02-23 17:47 ` Arjan van de Ven
2006-02-23 18:45 ` Jeff V. Merkey
2006-02-23 19:38 ` Lennart Sorensen
2006-02-27 8:02 ` Ingo Molnar
2006-02-24 4:29 ` jdow
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=43FCFDC6.9090109@soleranetworks.com \
--to=jmerkey@soleranetworks.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