From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] multiple /lib64/modules directories
Date: Tue, 17 May 2011 02:12:25 +0200 [thread overview]
Message-ID: <201105170212.25833.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4DD1BD4A.90309@gmail.com>
Apparently, though unproven, at 02:11 on Tuesday 17 May 2011, Valmor de
Almeida did opine thusly:
> Hello,
>
> After a recent sync, I ended up with these two modules
>
> /lib64/modules/2.6.36-gentoo-r5/misc/vboxdrv.ko
> /lib64/modules/2.6.37-gentoo-r4/misc/vboxdrv.ko
>
> and others too. I expected the directory for the older kernel to be
> removed. Is this the case? Virtualbox was re-emerged after the sync
> therefore the modules for the newer kernel were created. The current
> kernel is 2.6.37-gentoo-r4 (and it is the only one on my system). Should
> the directory /lib64/modules/2.6.36-gentoo-r5/ still exist?
This is basic Linux stuff.
There is a /lib/modules/xxxx for each installed kernel binary.
Portage will never remove them as portage did not install them, they are
installed by the "make modules_install" target of the kernel build process,
which you always run manually outside of portage's control.
The vbox modules are also in those directories under misc/ but this comes with
a quirk. They are usually built by remerging virtualbox-modules or running
module-rebuild. Unlike most other ebuilds, these do not delete everything from
the last emerge and replace all files (you will still need all installed
modules for any installed kernels you still have). So, portage simply does not
remove things from /lib/modules/
In other words, what you have is exactly what you should have and things as
working as designed. To remove anything in /lib/modules, you must manually rm
them yourself.
Incidentally, the same goes for the various kernel files in /boot/.
>
> Thanks,
>
> --
> Valmor
>
> -> locate vbox* | grep modules
> /lib64/modules/2.6.36-gentoo-r5/misc/vboxdrv.ko
> /lib64/modules/2.6.36-gentoo-r5/misc/vboxnetadp.ko
> /lib64/modules/2.6.36-gentoo-r5/misc/vboxnetflt.ko
> /lib64/modules/2.6.37-gentoo-r4/misc/vboxdrv.ko
> /lib64/modules/2.6.37-gentoo-r4/misc/vboxnetadp.ko
> /lib64/modules/2.6.37-gentoo-r4/misc/vboxnetflt.ko
>
> -> equery list gentoo-sources
> [ Searching for package 'gentoo-sources' in all categories among: ]
> * installed packages
> [I--] [ ] sys-kernel/gentoo-sources-2.6.37-r4 (2.6.37-r4)
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-05-17 0:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 0:11 [gentoo-user] multiple /lib64/modules directories Valmor de Almeida
2011-05-17 0:12 ` Alan McKinnon [this message]
2011-05-17 0:51 ` Valmor de Almeida
2011-05-17 1:55 ` Dale
2011-05-17 4:08 ` Thanasis
2011-05-17 6:51 ` Joost Roeleveld
2011-05-17 13:08 ` Dale
2011-05-17 14:49 ` Paul Hartman
2011-05-17 15:04 ` Joost Roeleveld
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=201105170212.25833.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.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