Comment 28 for bug 463347

I'm confused. I don't have any command line experience yet, but I know USB drives never mount for me (unless I use the Karmic LiveCD, and then it's still mounted only sometimes), but the original poster said you can see if you have the bug with this command:
for p in `pidof udevd`; do sudo ls -l /proc/$p/fd | wc -l; done | awk '{$s += $1} END { print $s }'

"If the resulting number is around 1000 or higher, then you have the problem described in this bug report."

The workaround "sudo stop udev" and then "sudo start udev" works for me, but the result I got from the original command was:
$ for p in 'pidof udevd'; do sudo ls -l /proc/$p/fd | wc -l; done | awk '{$s += $1} END { print $s }'
ls: cannot access /proc/pidof: No such file or directory
ls: cannot access udevd/fd: No such file or directory
0

Now, after the workaround, it doesn't say it can't find anything, but it still returns 0.

Is my problem a different one? And, is it related to the fact that (before doing the workaround) Palimpsest Disk Utility never recognized my USB as a known filesystem (and also sometimes half, sometimes all of my other internal HD partitions)? GParted always saw everything find, though.