Hi! I’m experiencing minor problems with cd-rom device (MAT****A DVD-RAM UJ-860H) on hp compaq 6710b GB887EA (openSUSE 11 GNOME, kernel 2.6.25.11-0.1-pae): the “eject /dev/cdrom” command shows:
“umount: /dev/sr0 is not in the fstab (and you are not root)
eject: unmount of `/dev/sr0’ failed”
Also, when I want to eject disc using device eject-button, error message saying “volume can’t be ejected” is displayed (only when it’s mounted); when I press button again once or twice it works, but message is still displayed.
How do I configure it properly? Should I edit /etc/fstab (if yes, how)? Thanks.
Pretty please? Can’t google my answer. Of course I’m noob, I wouldn’t ask otherwise.
I’m not a GNOME user, but KDE, but you should use the eject operation on the device icon, not the eject command from the CLI.
are you using eject on the command line? Please try “eject -v” and post the output.
Uwe
First of all, thank you for your concern!! - much appreciated 
*ken_yap:
eject operation on icon works perfectly (I haven’t tried this before, my fault)
*buckesfeld:
I used command line when eject-button failed
“eject -v” output with no disc inside:
eject: using default device `/dev/cdrom'
eject: device name is `/dev/cdrom'
eject: expanded name is `/dev/cdrom'
eject: `/dev/cdrom' is a link to `/dev/sr0'
eject: `/dev/sr0' is not mounted
eject: `/dev/sr0' is not a mount point
eject: `/dev/sr0' is not a multipartition device
eject: trying to eject `/dev/sr0' using CD-ROM eject command
eject: CD-ROM eject command succeeded
with disc inside/mounted:
eject: using default device `/dev/cdrom'
eject: device name is `/dev/cdrom'
eject: expanded name is `/dev/cdrom'
eject: `/dev/cdrom' is a link to `/dev/sr0'
eject: `/dev/sr0' is mounted at `/media/backup'
eject: unmounting `/dev/sr0'
umount: /dev/sr0 is not in the fstab (and you are not root)
eject: unmount of `/dev/sr0' failed
The reason CLI eject doesn’t work for a normal user is that you have no permission on the CDROM device, and it wasn’t mounted with the user’s ownership using fstab, which is one of the exceptions.
However the GUI eject works because it goes through the hal/dbus-1/policykit thingies which selectively grant permission to execute some actions by sending messages. If you are logged in on the desktop, then that satisfies a precondition for the permission.
If you were hoping to use the CLI command in a script or something like that, unfortunately you’ll have to do it through the “bureaucracy”, I’m sure there is a way to generate those messages with a CLI program. Sorry can’t give you much information to go on, I’m trying to learn this myself to figure out how I can get permission from a thin-client login, but these thingies are so new that there is a dearth of information and some of it is outdated.
Ken,
I was confused because eject on the CLI worked for me. I tried it again and now it doesn’t. Turns out the first time I tried it I had an audio CD in the drive.
Back to the drawing board…
Uwe
no, that fully satisfies my curiosity…for now 
thanks.