From: Avi Schwartz <avi@CFFtechnologies.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] How do I keep multiple versions of modules?
Date: 02 Apr 2002 12:35:02 -0600 [thread overview]
Message-ID: <1017772502.6035.60.camel@seahorse> (raw)
Sounds strange, but not so.
The problem happened when I built the 2.4.19 kernel. I had to rebuild
the pcmcia and alsa modules as well. Guess what, I had some problems
with 2.4.19 (actually the problem is vmware and not the kernel. vmware
will not build the modules since it uses malloc.h which was depriciated
in 2.4.19). So I decided to boot 2.4.18. Suddenly none of the alsa
modules would load.
What happens is that when I built the alsa modules for 2.4.19, the
installation program removed the previous version and therefore the
modules where gone from the /lib/modules/2.4.18 hierarchy.
Kernel modules should be special and if you rebuild a module, it should
remove the module only for the currently running kernel hierarchy and
not from a different kernel version.
Is this even possible with the poratge system?
I wasn't sure where I should post this, so I crossposted to user and
dev.
Avi
--
Avi Schwartz
avi@CFFtechnologies.com
next reply other threads:[~2002-04-02 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 18:35 Avi Schwartz [this message]
2002-04-02 19:33 ` [gentoo-dev] How do I keep multiple versions of modules? Grant Goodyear
2002-04-02 20:16 ` Dan Armak
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=1017772502.6035.60.camel@seahorse \
--to=avi@cfftechnologies.com \
--cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox