Dear Greg, > Then do a simple s/proc/dev/ on $DEVICE in fxload and you will be fine, > right? That's not a fix, it's a bad work-around. I'm shocked that a kernel hacker of your seniority and experience could suggest such a terrible fix. The data coming in is garbage, you can mitigate but you can't just rewrite the data like that. Last thing any distro needs is to weigh it's self down with patches that can never be pushed upstream. We need this fix to work for everyone, even if you take ubuntu and change the usbfs mount point. > No, if it moved it, then it also just needs to patch fxload, like they > already did for libusb. fxload isn't wrong, that package is not where proc mount point is wrongly used. What ever code that sets $DEVICE is where the fix should be and I think that's in the kernel. Even if we did hack-break the fxload package, that doesn't fix the garbage data coming out of the kernel; nor does it fix the problem for any other package that thinks $DEVICE is a nice useful bit of data to rely upon. I've sent the question to Ubuntu kernel people so they can have a look too. Your right in that it's a distro problem, so they'll be able to take it from here. Regards, Martin Owens (Canonical) -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
