Is this issue really fixed by using the native udev rules? I don't think so.

The rules' only purpose is to change the ownership and permissions on the 
/{dev,proc}/bus/usb device files, and the bug (at least my interpretation 
of it; the original submitter's statement was vague) is reproducible when 
bcmxcp_usb is run as root.

Please reopen this bug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to