From: Matt Burgess <matthew@linuxfromscratch.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: index_mm_open: No such file or directory
Date: Sat, 21 Jan 2012 20:21:58 +0000 [thread overview]
Message-ID: <1327177318.1776.14.camel@kyoto.localdomain> (raw)
In-Reply-To: <1327176371.1776.7.camel@kyoto.localdomain>
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@linuxfromscratch.org> wrote:
> > Hi all,
> >
> > When running the following command...
> >
> > for NIC in /sys/class/net/* ; do
> > INTERFACE=${NIC##*/} udevadm test --actiond $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.
prev parent reply other threads:[~2012-01-21 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 20:06 index_mm_open: No such file or directory Matt Burgess
2012-01-21 20:09 ` Lucas De Marchi
2012-01-21 20:21 ` Matt Burgess [this message]
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=1327177318.1776.14.camel@kyoto.localdomain \
--to=matthew@linuxfromscratch.org \
--cc=linux-hotplug@vger.kernel.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