mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: Nick Warne <nick@linicks.net>, Chris Adams <cmadams@hiwaay.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Red Hat ES4 GPL Issues?
Date: Thu, 23 Feb 2006 18:47:08 +0100	[thread overview]
Message-ID: <1140716828.4672.80.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <43FDFBDE.2040304@wolfmountaingroup.com>

On Thu, 2006-02-23 at 11:15 -0700, Jeff V. Merkey wrote:
> Arjan van de Ven wrote:
> 
> >>But anyway, what has this thread to do with the kernel?
> >>    
> >>
> >
> >
> >since when does something need to be on-topic for Jeff Merkey to post to
> >lkml ? ;-)
> >
> >  
> >
> 
> I got the RPM's and located them from an earlier responder to the post.  
> It was just disturbing
> that RedHat does ont include the sources when you install from binary -- 
> which they always have
> before. 
> 

you forgot to download the cd images labeled "source".
What's the problem???

> I am glad Red Hat is still distributing the code, but I am disappointed 
> they are no longer
> including it in the base RPM install.

oh you don't mean the src.rpm but the full kernel source code installed?
That's explained in the release notes; it's 2 shell commands to create
it, and it's in a way silly to make an exception for the kernel here
compared to all other software. And CD real estate on the binary cd's is
scarse as well. 



  reply	other threads:[~2006-02-23 17:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  0:11 Jeff V. Merkey
2006-02-22 23:21 ` 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 [this message]
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=1140716828.4672.80.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=cmadams@hiwaay.net \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    /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®