HEADS UP TESTERS: Lates nautilus-cd-burner may work

[Jeremy Messenger]

On 21 May 2003 18:23:09 -0400, Joe Marcus Clarke <marcus at marcuscom.com> 
wrote:

> On Wed, 2003-05-21 at 14:49, Jeremy Messenger wrote:
>> On 21 May 2003 14:43:36 -0400, Joe Marcus Clarke <marcus at marcuscom.com> 
>> wrote:
>>
>> > On Wed, 2003-05-21 at 14:15, Jeremy Messenger wrote:
>> >> On 21 May 2003 12:12:22 -0400, Joe Marcus Clarke 
>> <marcus at marcuscom.com> >> wrote:
>> >>
>> >> > On Wed, 2003-05-21 at 04:40, Jeremy Messenger wrote:
>> >> >> On 21 May 2003 02:56:48 -0400, Joe Marcus Clarke >> 
>> <marcus at marcuscom.com> >> wrote:
>> >> >>
>> >> >> > On Wed, 2003-05-21 at 02:22, Jeremy Messenger wrote:
>> >> >> >> Oh wait a minute.. Now, I can see over six nautilus-cd-burner 
>> in >> the >> top >> and ps, which I exited them. Each of them are 
>> running >> around 10% >> of CPU. >> Seem like they are still running 
>> without exit.
>> >> >> >
>> >> >> > Nevermind, I see my mistake.  Note, you need to be root, or have 
>> >> all
>> >> >> > your cd devices 0666 (i.e. /dev/acd0c, /dev/cd0c, etc.).  Use 
>> this
>> >> >> > patch.
>> >> >>
>> >> >> I will rebuild and try it again this noon or so. My CD devices are 
>> on >> >> 0666 already, which burncd, cdrecord, mount and etc works fine 
>> on the >> >> normal user with operation group. :-)
>> >> >
>> >> > Ignore acd0c.  You need atapicam, and just make sure your cd*c 
>> devices
>> >> > are 0666.
>> >>
>> >> Yeah, I had this in my kernel for pretty long time, so I can burn the 
>> >> bin/cue. ;-) However, the create ISO is now working again, but the 
>> write >> burn is still disable. I tried to ran it under the gdb, but it 
>> shows >> nothing and normal. It does exit normal now. Looks like I will 
>> have to >> run under nautilus then run it with 'r burn:///'..
>> >
>> > Don't worry with gdb.  I'll send you a debugging patch that will spit
>> > some messages to the console/error log.  In the meantime, compile the
>> > attached program using:
>> >
>> > cc -o xxx -lcam xxx.c
>> >
>> > And run it.  It will try to open /dev/cd0c (cd0).  If this isn't 
>> right,
>> > then change it at lines 12 and 30.  Send me the output.  Thanks.
>>
>> Ummmm.. I chmod'ed it to 777 and still have the same thing.. Here's 
>> result:
>
> Sorry, you'll have to chmod all your pass and xpt devices as well.  I'm
> working on a new patch to fix some other things as we speak.

Oh that was it, thanks! I missed the pass, but I already have xpt correct. 
Now, it works as normal user with ./xxx... Look forward for your another 
patch, thanks!

Cheers,
Mezz

> Joe
>
>>
>> ==============================
>> $ cc -o xxx -lcam xxx.c
>> $ ./xxx
>> Failed to get CAM device: Permission denied
>> CD read speed: 1, write speed: -1077937035
>> ==============================
>>
>> ==============================
>> $ ls -l /dev/cd*
>> crwxrwxrwx  1 root  operator   15,   0 May 20 17:17 /dev/cd0
>>
>> $ id
>> uid=1001(mezz) gid=1001(mezz) groups=1001(mezz), 0(wheel), 5(operator)
>> ==============================
>>
>> So, I ran it under the root and here's result:
>>
>> ==============================
>> # ./xxx
>> device_path =
>> given_dev_name = cd
>> device_name = pass
>> dev_unit_num = 0
>> bus_id = 0
>> target_lun = 0
>> target_id = 1
>> vendor = TEAC    CD-W516EB       1.0A
>> product = CD-W516EB       1.0A
>> revision = 1.0A
>> CD read speed: 1, write speed: -1077937103
>> ==============================
>>
>> I don't understand why burncd, mount, cdrecord and others work fine on 
>> normal user with operation group..
>>
>> Cheers,
>> Mezz
>>
>> > Joe
>> >
>> >>
>> >> Cheers,
>> >> Mezz
>> >>
>> >> > Joe
>> >> >
>> >> >>
>> >> >> Cheers,
>> >> >> Mezz
>> >> >>
>> >> >> > Joe
>> <snip>



-- 
bsdforums.org 's moderator, mezz.