From: mariodebian <mariodebian@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: UDEV mount event not generated
Date: Thu, 30 Aug 2007 15:38:24 +0000 [thread overview]
Message-ID: <1188488304.6133.67.camel@mariodebian> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2053 bytes --]
Hi all.
I'm developing an embeded thin client system based on initramfs using
debian kernel bins, and libs: www.tcosproject.org
I'm using debian unstable (udev 0.114-2 ).
My thin client remote devices manager (tcos-devices-ng.py [1]) uses udev
events, I load events using a XMLRPC server running on thin client.
1.- I have created one simple udev rule [2]:
SUBSYSTEM=="block", RUN+="/sbin/tcos-udevd.sh"
tcos-udev.sh [2] script is called in every udev block event.
Some time ago (when I start developing this tools) I filter this events
in my python app:
self.udev_events={
"insert": {"ID_BUS": "usb", "ACTION":"add"},
"remove": {"ID_BUS": "usb", "ACTION":"remove"},
"mount-floppy": {"DEVPATH": "/block/fd0", "ACTION":"mount"},
"umount-floppy":{"DEVPATH": "/block/fd0", "ACTION":"umount"},
"mount-cdrom": {"DEVPATH": "/block/hd*", "ACTION":"mount"},
"umount-cdrom": {"DEVPATH": "/block/hd*", "ACTION":"umount"},
"mount-flash": {"DEVPATH": "/block/sd*", "ACTION":"mount"},
"umount-flash": {"DEVPATH": "/block/sd*", "ACTION":"umount"}
}
This is the meaning of every element:
"udev-event-name": {"condition1":"condition1", "cond2":"cond2"}
All actions worked ok:
* add (tell thin client to mount DEVNAME)
* remove (tell thin client to umount all parts in DEVNAME)
* mount (show a message: Device XXX is ready)
* umount (show a message: You can unplug device XXX)
In 2007 June this tools works ok (don't remember udev version) [3]
I don't know when mount/umount stop working, but from some weeks ago I
can see mount/umount messages.
Why udev don't send mount/umount block events to my app?
Any ideas?
Bad rules file?
Thanks for your work
[1]
http://trac.tcosproject.org/browser/trunk/tcosmonitor/tcos-devices-ng.py?rev=444
[2] http://trac.tcosproject.org/browser/trunk/tcosmonitor/udev
[3] http://www.tcosproject.org/tcos-devices-ng/ (screencast)
--
mariodebian
http://soleup.eup.uva.es/mariodebian
[-- Attachment #1.2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 226 bytes --]
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2007-08-30 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 15:38 mariodebian [this message]
2007-08-30 16:13 ` UDEV mount event not generated Kay Sievers
2007-08-30 18:41 ` mariodebian
2007-08-30 19:31 ` Kay Sievers
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=1188488304.6133.67.camel@mariodebian \
--to=mariodebian@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).