> > And can you confirm that David's updated rule fixes this issue?
As I said in my other mail, there are many many reasons why things
can fail that are unrelated to the udev rule. Just proclaiming "it
doesn't work!" without investigating further and then scrapping a
good udev rule is non-sense.
For example, there are some issues with the kernel loop driver and
partitioned devices, that's probably what Zeeshan is running into
(support for partitioned loop devices is rather new). I don't know
what kernel it's fixed in (if fixed at all). But it's easy to check
if the expected block devices show up. Maybe Zeeshan didn't do that,
I don't know.
FWIW, the updated udev rule consistently works on my box; latest F18
packages, stock no customizations. That is, if the block devices
do show up.
David
