On 04/05/11 15:27, Patrick O'Callaghan wrote:
> On Wed, 2011-05-04 at 15:17 -0400, Bob Goodwin wrote:
>> I see several other app's that look as though they should work but
>> don't, e.g. grip, sound-juicer, asunder. They seem to have trouble
>> finding the cdrom drive and I'm not sure they are any faster to
>> use
>> than K3B. But it seems they ought to work.
>>
>> [bobg@box9 ~]$ asunder
>> Error: Couldn't open /dev/cdrom
>> Error: Couldn't open /dev/cdrom
>> Error: Couldn't open /dev/cdrom
>>
>> Grip produces an error message:
> /dev/cdrom is usually a symbolic link to the real device, e.g. on my
> system:
>
> $ ls -l /dev/cdrom
> lrwxrwxrwx. 1 root root 3 Apr 27 12:21 /dev/cdrom -> sr0
>
> That's what you need to check first. Since the automount thing is
> working, see what physical drive is mounted on /media/<whatever>. Note
> that you my need to unmount it (but not eject it) for the ripping apps
> to be able to access it directly. Alternatively, start the app before
> inserting the disc.
>
> poc
>
Yes, thank you, I am embarrassed. I should have checked for /dev/cdrom!
I linked it to sr0 and "asunder" works, most likely the others will
also.
What confused me was I thought it had worked a couple of months ago.
But I think I installed a new drive since that time and something
has changed as a result?
Thanks to all.
Bob
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
