* [gentoo-dev] How do I keep multiple versions of modules?
@ 2002-04-02 18:35 Avi Schwartz
2002-04-02 19:33 ` Grant Goodyear
0 siblings, 1 reply; 3+ messages in thread
From: Avi Schwartz @ 2002-04-02 18:35 UTC (permalink / raw
To: gentoo-dev
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] How do I keep multiple versions of modules?
2002-04-02 18:35 [gentoo-dev] How do I keep multiple versions of modules? Avi Schwartz
@ 2002-04-02 19:33 ` Grant Goodyear
2002-04-02 20:16 ` Dan Armak
0 siblings, 1 reply; 3+ messages in thread
From: Grant Goodyear @ 2002-04-02 19:33 UTC (permalink / raw
To: gentoo-dev
> 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.
True. I suspect that nobody had thought of it yet.
> Is this even possible with the poratge system?
Not right now, although such functionality shouldn't be hard to add.
> I wasn't sure where I should post this, so I crossposted to user and
> dev.
Please post your comment as a "bug" on bugs.gentoo.org. You have
a good point, and it would be a shame for it to get lost.
Thanks,
g2boojum
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] How do I keep multiple versions of modules?
2002-04-02 19:33 ` Grant Goodyear
@ 2002-04-02 20:16 ` Dan Armak
0 siblings, 0 replies; 3+ messages in thread
From: Dan Armak @ 2002-04-02 20:16 UTC (permalink / raw
To: gentoo-dev
On Tuesday 02 April 2002 22:33, Grant Goodyear wrote:
> > 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.
>
> True. I suspect that nobody had thought of it yet.
I did, but put it off for post-1.0 :-)
>
> > Is this even possible with the poratge system?
>
> Not right now, although such functionality shouldn't be hard to add.
One solution: where the modules have a separate ebuild (like nvidia-kernel,
not like pcmcia-cs - but they can be split), set SLOT=KERNEL_VERSION and
(once we have full slot functionality in Portage) remerging won't unmerge a
different kernel version's modules.
>
> > I wasn't sure where I should post this, so I crossposted to user and
> > dev.
>
> Please post your comment as a "bug" on bugs.gentoo.org. You have
> a good point, and it would be a shame for it to get lost.
>
> Thanks,
> g2boojum
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
--
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-04-02 20:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-04-02 18:35 [gentoo-dev] How do I keep multiple versions of modules? Avi Schwartz
2002-04-02 19:33 ` Grant Goodyear
2002-04-02 20:16 ` Dan Armak
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox