From: Valdis.Kletnieks@vt.edu
To: Rudo Thomas <thomr9am@ss1000.ms.mff.cuni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug with extraversion in kernel-2.4.23
Date: Sun, 30 Nov 2003 19:50:26 -0500 [thread overview]
Message-ID: <200312010050.hB10oR02008420@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 01 Dec 2003 01:16:02 +0100." <20031201011602.A12652@ss1000.ms.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Mon, 01 Dec 2003 01:16:02 +0100, Rudo Thomas <thomr9am@ss1000.ms.mff.cuni.cz> said:
> > The extraversion variable of the Makefile is very badly interpreted.
> > When the kernel is installed, I have 2 directory of modules :
> > /lib/modules/2.4.23
> > /lib/modules/2.4.23-fnux (my extraversion is -fnux)
>
> No way. The directory without -fnux is probably just a leftover from previous
> make modules_install. When you run 2.4.23-fnux, you won't need it.
On the other hand, you probably want to keep the 2.4.23(no-ext) directory
around as well, so you can boot a 2.4.23 kernel to clean up after a broken
build of a 2.4.23-fnux won't boot.
There's a reason why my /lib/modules has 6 subdirectories - I have 6
bootable kernels sitting around, Just In Case (well... OK. 2 spares would
probably be enough, but it's easier to do a "which -mm did the problem start?"
regression if you have the most recent few handy to try.. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
prev parent reply other threads:[~2003-12-01 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 22:01 Bug with extraversion in kernel-2.4.23 alexis
2003-12-01 0:16 ` Rudo Thomas
2003-12-01 0:50 ` Valdis.Kletnieks [this message]
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=200312010050.hB10oR02008420@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=thomr9am@ss1000.ms.mff.cuni.cz \
/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).