Hi all

When trying to rip CDs with either ripperX or with Grip, I am informed that I should add myself to the cdrom group or otherwise ensure I have permissions to access the CDROM. However, since I have already set that up (adding myself to both the CDROM and wheel groups) I am not sure what else I can do. I have explored this through my well-worn copy of RUTE and googled a bit on this but still no dice.

How do I go about getting both rippers to recognise that I do have permissions to access the device. Would this be something in my /etc/fstab perhaps? I can play CDs and even burn CDs, but just not rip them.

Any suggestions?

Thanks

/etc/fstab should show your user has read/write permissions........
as well as the directory where the cdrom mounts........./mnt/cdrom

yesss .... ? And my /etc/fstab file reads:
just as I would expect it to. I'm not sure what your point is: are you suggesting that I change my /etc/fstab file or that I do something else in terms of the permissions? Please clarify.

Thx

One solution would be to configure sudo in the sudoers file then run Grip as root
I know that you didn't ask that. But it will allow you to rip. You'll have permission to the optical drives.

Surely there must be a more ordinary way of doing it without resorting to sudo. This just strikes me as being peculiar since I am able to play CDs, mount them, umount them and burn CDs as normal user and yet am unable/not permitted to rip them. That seems a rather inconsistent way for permissions to work - I would have thought that the user is either allowed to or not allowed to read/write to the device, but not sometimes yes and sometimes no.
So, to be fair, there are two questions to this post:
1. Why does it respond this way - i.e. what's going on here from a system's perspective; and
2. How can I fix this so that I can rip CDs as an ordinary user without having to su or sudo?

Thanks for any clues.

I don't know what problem you are having, here is some reference material. Sometimes you can't solve every problem that you have in Linux. You work around it.

If your using Slack like your profile says here is a book on it.
http://www.slackware.com/book/
ftp://ftp.slackbook.org/pub/slackbook/slackbook-2.0.pdf
And you already have rute
http://rute.2038bug.com/index.html.gz

I'll also give you this.
http://www.freebsd.org/doc/en_US.ISO...ook/index.html
It's for BSD not Linux but covers the same basics used in Linux.

Thanks for the references teckk. From an initial read of the relevant sections I cannot see anything obviously wrong with my set up, nor even with the permissions arrangement. Nor did I find anything that might explain why my system is responding this way. This is becoming rapidly frustrating

just try logging on as root first

Could you expand a little on that cryptic suggestion please cyblord?