From mboxrd@z Thu Jan 1 00:00:00 1970 From: mariodebian Date: Thu, 30 Aug 2007 15:38:24 +0000 Subject: UDEV mount event not generated Message-Id: <1188488304.6133.67.camel@mariodebian> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0985278581==" List-Id: To: linux-hotplug@vger.kernel.org --===============0985278581== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-wPKx1BtqQFz5P1STE1+8" --=-wPKx1BtqQFz5P1STE1+8 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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=3D=3D"block", RUN+=3D"/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=3D{ "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?re= v=3D444 [2] http://trac.tcosproject.org/browser/trunk/tcosmonitor/udev [3] http://www.tcosproject.org/tcos-devices-ng/ (screencast) --=20 mariodebian http://soleup.eup.uva.es/mariodebian --=-wPKx1BtqQFz5P1STE1+8 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD4DBQBG1uRvfHuNLH93QfsRAicUAJdqScLUZ843R8Ff78skch9fOS/fAKCpy9Vc vEwIUTL7v2XipM+QqFe6SA== =2di3 -----END PGP SIGNATURE----- --=-wPKx1BtqQFz5P1STE1+8-- --===============0985278581== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- 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/ --===============0985278581== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============0985278581==--