All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gregg Lloyd" <gregg_99@lycos.com>
To: linux-kernel@vger.kernel.org
Subject: Cannot compile my kernel due to unpredictible situations:
Date: Thu, 11 Jan 2001 18:30:47 -0500	[thread overview]
Message-ID: <HKPKHOJMBOBKGAAA@mailcity.com> (raw)

Hi,
I have downloaded linux kernel 2.4. 
In /usr/src, I did untar the file: 
gzip -cd  linux-2.4.0.tar.gz  | tar xvf - 
I see several files being copied to several locations (/linux/Documentation, 
/linux/arch/..etc..). The problem is that there's no linux 2.4   directory created 
under /usr/src or anywhere else on my system! Anyway, there's nothing new 
under /usr/src!!! 
Linux is not new to me, so I know that this is weird ( I even tried it with  "tar -zxvf  linux-2.4.0.tar.gz", "gzcat  linux-2.4.0.tar.gz | tar xvf - " ..etc). Same result. 
Anyway, let's say that it doesn't matter whether there's a new kernel 2.4 directory or not..
how can I make sure that I  am  re-compiling my kernel (currently kernel 2.2.5) with 
the right 2.4 kernel?? (Kernel howto talks about going to /usr/src/linux and start compiling..but current /usr/src/linux is a link to my current 2.2.5 kernel !!!)

Current OS: Red Hat Linux 6.0 Kernel 2.2.5

Thanks



Get your small business started at Lycos Small Business at http://www.lycos.com/business/mail.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-11 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 23:30 Gregg Lloyd [this message]
2001-01-11 23:44 ` Cannot compile my kernel due to unpredictible situations: J . A . Magallon
2001-01-11 23:45 ` Yin Tan Cui
2001-01-12 11:34   ` Russell King

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=HKPKHOJMBOBKGAAA@mailcity.com \
    --to=gregg_99@lycos.com \
    --cc=gregg_99@mailcity.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.