On Tue, May 18, 2010 at 15:25, Nick Bowler <nbowler@xxxxxxxxxxxxxxxx> wrote: > On 07:08 Tue 18 May , Kay Sievers wrote: >> On Tue, May 18, 2010 at 00:54, Nicolas Thomas Bowler >> > On Mon, 17 May 2010 18:27:48 +0200, Kay Sievers wrote: >> >> > With the rules commented out, the command /sbin/blkid -p -oudev /dev/sr0 >> > on the non-spinning drive causes three distinct bursts of events to >> > occur: >> >> Ok, the drive seems to send out new events with every access. Maybe >> it's a device which tries to send AN (async) events by itself. >> >> What does: >> cat /sys/class/block/sr0/../../evt_media_change >> print for this device? > > Prints 1. Oh, seems to be an AN capable device, which actually really sends events. :) I don't know if that works, never tried, but if you chmod the evt_media_change file to 0664. and write 0 to it, does it still behave the same? Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
