linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
To: "'Kristofer T. Karas'" <ktk@enterprise.bidmc.harvard.edu>,
	"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
	"'steve.cameron@hp.com'" <steve.cameron@hp.com>
Subject: RE: How to identify contents of /lib/modules/*
Date: Thu, 17 Apr 2003 13:02:01 -0700	[thread overview]
Message-ID: <A46BBDB345A7D5118EC90002A5072C780C26308F@orsmsx116.jf.intel.com> (raw)

> From: Kristofer T. Karas [mailto:ktk@enterprise.bidmc.harvard.edu]
>
> I have a worse problem.  :-)   I often run several instances of the
> identically version-numbered kernel, all available from the LILO boot
> menu, each instance having a different .config or perhaps compiled with
> a different gcc.  If each instance wants to share
> /lib/modules/[sameversion]/... then I've got a problem.

I solve that appending to EXTRAVERSION ... 2.5.66.5.2-rtfutex is the
latest build of the 20+ 2.5.66 slightly different kernels I have 
installed in the same machine for testing. And they all have different
module directories.

Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own
(and my fault)

             reply	other threads:[~2003-04-17 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 20:02 Perez-Gonzalez, Inaky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16 18:57 How to identify contents of /lib/modules/* Cameron, Steve
2003-04-16 15:58 Cameron, Steve
2003-04-16 16:01 ` Alan Cox
2003-04-16 20:54   ` Henning P. Schmiedehausen
2003-04-16  2:00 Stephen Cameron
2003-04-16 14:21 ` Alan Cox
2003-04-16 16:06   ` Dominik Kubla
2003-04-17 18:08   ` Kristofer T. Karas
2003-04-16 15:18 ` Arjan van de Ven
2003-04-16 17:08 ` Jeremy Jackson
2003-04-16 17:20 ` Paul Clements

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=A46BBDB345A7D5118EC90002A5072C780C26308F@orsmsx116.jf.intel.com \
    --to=inaky.perez-gonzalez@intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ktk@enterprise.bidmc.harvard.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve.cameron@hp.com \
    /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).