Sorry it took me so long to get back to you on this, I've been busy. - I agree that making eject suid is a suboptimal solution. No argument there.
- I believe that eject is different vs. a simple umount. It does something to the USB device, though I'm not sure what. This is best illustrated by plugging in an iPod so that it kicks into disk mode. You'll get a USB mass storage device, and the display will show a little circle with a slash through it (you know, the universal "no" sign). If, at this point, you unmount it, the circle/slash stays. If you eject it, the circle/slash turns into a check, because it is okay to remove. - In my case, none of these are optical drives, they are all disk or flashed based devices of some type (iPods, SD cards from my camera, external magnetic hard disks, etc.) - Checking in to it, mine get assigned permissions of root:disk. Like the plugdev problem, if I gave every user membership to the disk group, this creates a potential problem. I think that a solution which may work here is <a href="https://bugs.launchpad.net/ubuntu/+source/udev/+bug/128257/comments/7";>this comment</a> from Scott James Remnant, where he suggests letting ConsoleKit handle it. At least in my case, this would work, because I'm at the console poking things. -- eject command fails with "unable to open" error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
