On Sat, 2012-01-21 at 18:09 -0200, Lucas De Marchi wrote:
> Hi Matt,
>
> On Sat, Jan 21, 2012 at 5:55 PM, Matt Burgess
> <matthew@xxxxxxxxxxxxxxxxxxxx> wrote:
> > Hi all,
> >
> > When running the following command...
> >
> > for NIC in /sys/class/net/* ; do
> > INTERFACE=${NIC##*/} udevadm test --action=add $NIC
> > done
> >
> > ... I see the following output:
> >
> > run_command: calling: test
> > adm_test: version 178
> > builtin_kmod_init: load module index
> > index_mm_open: No such file or directory
>
> You are missing a ".bin" file at /lib/modules/$(uname -r)/. Do you
> have all these 3 files below?
>
> modules.alias.bin
> modules.dep.bin
> modules.symbols.bin
Ah, that explains it perfectly, thanks! The exact scenario here is that
I'm building udev/kmod in a chroot environment from a Fedora 16 host.
Fedora is running a kernel with a module directory
of /lib/modules/3.1.9-1.fc16.x86_64 but my chroot environment
contains /lib/modules/3.2.1. So, while both the host and my chroot
environment contain all 3 .bin files in their respective modules
directories, because those directories are between the 2 environments, I
see the message above. As it doesn't appear to have any impact on the
functionality I'm after here, I'm happy enough to leave it as-is. I'm
guessing though, that a symlink with the same name as the host's module
directory to the chroot environment directory would work around the
issue.
Regards,
Matt.
--
To unsubscribe from this list: send the line "unsubscribe linux-modules" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
