From: Arjan van de Ven <arjanv@redhat.com>
To: Stephen Liu <satimis@icare.com.hk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where to download kernel-headers-2.4.18-18.8.0
Date: 28 Apr 2003 13:37:19 +0200 [thread overview]
Message-ID: <1051529838.1388.1.camel@laptop.fenrus.com> (raw)
In-Reply-To: <1051529351.2573.16.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
On Mon, 2003-04-28 at 13:29, Stephen Liu wrote:
> Hi all folks,
>
> Just join this list.
>
> I have
>
> kernel-2.4.18-18.8.0
> kernel-source-2.4.18-18.8.0
>
> running in my system and I need "kernel-headers
> -2.4.18-18.8.0" working
> with them. Google.com could not find it.
why would you need glibc headers ????
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-28 11:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 11:29 Where to download kernel-headers-2.4.18-18.8.0 Stephen Liu
2003-04-28 11:37 ` Arjan van de Ven [this message]
2003-04-28 12:01 ` Stephen Liu
2003-04-28 12:02 ` Riley Williams
2003-04-28 12:55 ` Felipe Alfaro Solana
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=1051529838.1388.1.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=satimis@icare.com.hk \
/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).