[oe] What to do with obsolete kernel modules
John Lee
john_lee at openmoko.com
Mon Nov 24 11:40:53 UTC 2008
On Mon, Nov 24, 2008 at 10:26:38AM +0000, Phil Blundell wrote:
> On Mon, 2008-11-24 at 17:06 +0800, John Lee wrote:
> > If kernel-module-foobar exists in an old rootfs, but in later version
> > we disabled module foobar in kernel config, how can we remove the
> > obsolete module from the old rootfs after opkg upgrade ?
>
> Assuming the old module has a correctly versioned dependency on its
> corresponding kernel version, opkg should automatically tear out the
> module package when the kernel is upgraded since its dependencies will
> no longer be met. If that isn't working, I think it would be an opkg
> bug.
>
> p.
but that will only happen if you changed from, say, 2.6.24 to 2.6.26.
if just the git rev changed such as
a1e97c611253511ffc2d8c45e3e6d6894fa03fa3 to
6e2a723ef54ee2e739c34786981b2c508db803c1
then opkg wouldn't know about it.
my problem looks like this:
root at om-gta02:~# opkg status kernel-module-xt-physdev
Package: kernel-module-xt-physdev
Version: 2:2.6.24+git75969+a1e97c611253511ffc2d8c45e3e6d6894fa03fa3-r1.01
Depends: update-modules, kernel-2.6.24, kernel-module-x-tables
Status: install ok installed
Architecture: neo1973
Installed-Time: 1226894980
root at om-gta02:~# opkg status kernel-module-xt-tcpudp
Package: kernel-module-xt-tcpudp
Version: 3:2.6.24+gitr1+6e2a723ef54ee2e739c34786981b2c508db803c1-r2
Depends: update-modules, kernel-2.6.24, kernel-module-x-tables
Status: install user installed
Architecture: om-gta02
these 2 packages coexist on the same rootfs after opkg upgrade.
- John
More information about the Openembedded-devel
mailing list