From: "J . A . Magallon" <jamagallon@able.es>
To: gregg_99@mailcity.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cannot compile my kernel due to unpredictible situations:
Date: Fri, 12 Jan 2001 00:44:19 +0100 [thread overview]
Message-ID: <20010112004419.A751@werewolf.able.es> (raw)
In-Reply-To: <HKPKHOJMBOBKGAAA@mailcity.com>
In-Reply-To: <HKPKHOJMBOBKGAAA@mailcity.com>; from gregg_99@lycos.com on Fri, Jan 12, 2001 at 00:30:47 +0100
On 2001.01.12 Gregg Lloyd wrote:
> 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 !!!)
>
So you have just wrote kernel2.4 OVER your kernel2.2.
Kernel tarballs always untar and give a directory named 'linux'. So suppose
you have a setup like:
ls /usr/src:
linux -> linux-2.2.5
linux-2.2.5
If you untar linux-2.4.0.tar.gz in /usr/src, it writes over 'linux' that points
to you 2.2.5.
What I usually do is
rm -f linux (is just a link)
gtar zxf linux-2.4.0.tar.gz (gives a new REAL directory named 'linux')
mv linux linux-2.4.0
ln -s linux-2.4.0 linux
I don't know why kernels are not tarred as linux-X.X.X, but there will be
a reason, I suppose... (that will ease very much everyone's life).
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.4.0-ac5 #1 SMP Wed Jan 10 23:36:11 CET 2001 i686
-
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/
next prev parent reply other threads:[~2001-01-11 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 23:30 Cannot compile my kernel due to unpredictible situations: Gregg Lloyd
2001-01-11 23:44 ` J . A . Magallon [this message]
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=20010112004419.A751@werewolf.able.es \
--to=jamagallon@able.es \
--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.