Linux Hotplug development
 help / color / mirror / Atom feed
From: Matt Burgess <matthew@linuxfromscratch.org>
To: linux-hotplug@vger.kernel.org
Subject: index_mm_open: No such file or directory
Date: Sat, 21 Jan 2012 20:06:11 +0000	[thread overview]
Message-ID: <1327176371.1776.7.camel@kyoto.localdomain> (raw)

[reposted to fix linux-hotplug address, apologies!]

Hi all,

When running the following command...

for NIC in /sys/class/net/* ; do
    INTERFACE=${NIC##*/} udevadm test --action­d $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

Now, the command actually runs successfully, and the persistent rules
file is correctly generated, but I'm left scratching my head as to what
file/directory is trying and failing to be read.

I've tried building both udev-178 and kmod-4 with '--enable-debug' but
still don't get any additional output.  What am I missing?

Thanks,

Matt.


             reply	other threads:[~2012-01-21 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 20:06 Matt Burgess [this message]
2012-01-21 20:09 ` index_mm_open: No such file or directory Lucas De Marchi
2012-01-21 20:21 ` Matt Burgess

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=1327176371.1776.7.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