Kenward Vaughan wrote:
> On Mon, 2008-10-27 at 18:31 +0100, Emanoil Kotsev wrote:
>> Kenward Vaughan wrote:
>>
>> > On Sun, 2008-10-26 at 23:58 +0100, Jochen Schulz wrote:
>> >> Kenward Vaughan:
>> >> > On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote:
> ...
>> >> Do you have DMA enabled at
On Mon, 2008-10-27 at 18:31 +0100, Emanoil Kotsev wrote:
> Kenward Vaughan wrote:
>
> > On Sun, 2008-10-26 at 23:58 +0100, Jochen Schulz wrote:
> >> Kenward Vaughan:
> >> > On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote:
...
> >> Do you have DMA enabled at all? Check with 'hdparm -d /dev/$
Kenward Vaughan wrote:
> On Sun, 2008-10-26 at 23:58 +0100, Jochen Schulz wrote:
>> Kenward Vaughan:
>> > On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote:
>> >> Kenward Vaughan:
>> >>>
>> >>> Speed set to 7056 KB/s
>> >>> /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at spee
On Sun, 2008-10-26 at 23:58 +0100, Jochen Schulz wrote:
> Kenward Vaughan:
> > On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote:
> >> Kenward Vaughan:
> >>>
> >>> Speed set to 7056 KB/s
> >>> /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed
> >>> 40x.
> >>
> >> This mig
Kenward Vaughan:
> On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote:
>> Kenward Vaughan:
>>>
>>> Speed set to 7056 KB/s
>>> /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed
>>> 40x.
>>
>> This might be your problem. Did you already try burning in a slower
>> mode?
>
>
On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote:
> Kenward Vaughan:
> >
> > Speed set to 7056 KB/s
> > /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed
> > 40x.
>
> This might be your problem. Did you already try burning in a slower
> mode?
>
> J.
It's on auto, so I h
Kenward Vaughan:
>
> Speed set to 7056 KB/s
> /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed
> 40x.
This might be your problem. Did you already try burning in a slower
mode?
J.
--
If nightclub doormen recognised me I would be more fulfilled.
[Agree] [Disagree]
On Sun, 2008-10-26 at 12:09 -0700, Kenward Vaughan wrote:
> After copying one CD, I find cdrecord losing it's permission to write to
> the blank for a second, new CD. Any thoughts why this is happening?
> Info is in the debugging output below. I was running Fluxbox after a
...
Restarting K3B an
* linuksos <[EMAIL PROTECTED]> 09.10.2008
> No difference. I can see enormous hard disk activity but no positive result...
>
> On Tue, Oct 7, 2008 at 1:33 AM, Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > On the cmdline:
> >
> > cdrecord -v dev=/dev/ blank=fast .iso
Hello linuksos,
No difference. I can see enormous hard disk activity but no positive result...
On Tue, Oct 7, 2008 at 1:33 AM, Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote:
> linuksos wrote:
>>
>> Hello Guys,
>>
>> I'm trying to erase and burn my cd-rw. I'm sure that there is no
>> problem with my cd-rw media as i
I have tried couple of them but the same result. Which driver exactly
do you have in mind?
thank you
On Mon, Oct 6, 2008 at 8:16 PM, Lalit Dhiri <[EMAIL PROTECTED]> wrote:
>
> Try changing the driver selection in K3B. I think you'll find this at K3b
> configure> Devices> Cdrdao driver.
>
> Linux
linuksos wrote:
Hello Guys,
I'm trying to erase and burn my cd-rw. I'm sure that there is no
problem with my cd-rw media as it works on my other system. After
unsuccessful attempt to burn it with k3b I have gone to command line
to see what is going on. For command line I have followed steps
desc
Try changing the driver selection in K3B. I think you'll find this at K3b
configure> Devices> Cdrdao driver.
Linux the Root to no GPFs
> Date: Mon, 6 Oct 2008 16:50:48 +1100
> From: [EMAIL PROTECTED]
> To: debian-user@lists.debian.org
> Subject: cdrecord - need for troubleshoot help
>
> Hello G
On Tue, Oct 02, 2007 at 03:46:51PM -0400, Wayne Topa wrote:
> steef([EMAIL PROTECTED]) is reported to have said:
> >
> > hi all and *especially j?rg s., long-term initiator of cdrecord and
> > cdrtools*.
> >
> > two weeks ago i asked on this list 'what is better': cdrecord or wodim. on
> > one of
Andrew Sackville-West wrote:
On Wed, Oct 03, 2007 at 04:05:38PM +, steef wrote:
Wayne already apologised for this, BTW, and I was not flaming with the
above comment.
you are right. i did not see that message up till now. i withdraw my remark.
regards,
steef
A
--
To UNSUBS
On Wed, Oct 03, 2007 at 04:05:38PM +, steef wrote:
> Andrew Sackville-West wrote:
>> I was merely speaking up in your defence since he was
>> getting all sarcastic because he couldn't read...
>
> thanks. yes: that stupid sarcasm sometimes is really is a problem.
Wayne already apologised f
Andrew Sackville-West wrote:
hdc: ST3120026A, ATA DISK drive
Right! Neither cdrecord or wodim can burn to a _Hard Disk_.
where do you get this? He provided no info on what command he used and
if you look, hdb is clearly an optical drive... are you drinking too
m
Andrew Sackville-West wrote:
On Tue, Oct 02, 2007 at 03:46:51PM -0400, Wayne Topa wrote:
steef([EMAIL PROTECTED]) is reported to have said:
hi all and *especially jörg s., long-term initiator of cdrecord and
cdrtools*.
two weeks ago i asked on this list 'what is better': cdrecord or
Mumia W.. wrote:
On 10/02/2007 05:11 AM, steef wrote:
hi all and *especially jörg s., long-term initiator of cdrecord and
cdrtools*.
two weeks ago i asked on this list 'what is better': cdrecord or
wodim. on one of the responses i answered that the most recent
version of cdrecord/cdr-tools
Wayne Topa wrote:
steef([EMAIL PROTECTED]) is reported to have said:
hi all and *especially jörg s., long-term initiator of cdrecord and
cdrtools*.
two weeks ago i asked on this list 'what is better': cdrecord or wodim. on
one of the responses i answered that the most recent version of
cd
Andrew Sackville-West([EMAIL PROTECTED]) is reported to have said:
> On Tue, Oct 02, 2007 at 03:46:51PM -0400, Wayne Topa wrote:
> > steef([EMAIL PROTECTED]) is reported to have said:
> > >
> > > hi all and *especially jörg s., long-term initiator of cdrecord and
> > > cdrtools*.
> > >
> > > two w
On Tue, Oct 02, 2007 at 10:11:29AM +, steef wrote:
>
> two weeks ago i asked on this list 'what is better': cdrecord or wodim.
> on one of the responses i answered that the most recent version of
> cdrecord/cdr-tools completely damaged two brandnew cdrom's.
Just to clarify, do you mean that
On Tue, Oct 02, 2007 at 03:46:51PM -0400, Wayne Topa wrote:
> steef([EMAIL PROTECTED]) is reported to have said:
> >
> > hi all and *especially jörg s., long-term initiator of cdrecord and
> > cdrtools*.
> >
> > two weeks ago i asked on this list 'what is better': cdrecord or wodim. on
> > one of
steef([EMAIL PROTECTED]) is reported to have said:
>
> hi all and *especially jörg s., long-term initiator of cdrecord and
> cdrtools*.
>
> two weeks ago i asked on this list 'what is better': cdrecord or wodim. on
> one of the responses i answered that the most recent version of
> cdrecord/cdr-
hallo joerg,
your two emails plus the info on your website contain enough
points/arguments for me to get rid of wodim and install the latest
version of cdrecords and the tools again. before wodim appeared i used
cdrecord for many years without any problem: the program did what it
promised.
>I have both cdrecord (Cdrecord-Clone 2.01.01a01) and wodim (1.1.6) on my
>Sarge system. I'm using kernel 2.6.22 right now.
This is a very very old version of cdrecord!
It is definitely unable to work around the bugs in a Linus-2.6 kernel.
Use a recent version of cdrecord
http://cdrecord.berli
>"I have an Etch box with a linux-image-2.6.18-5-k7. All works well but
> wodim -devices
> Beginning native device scan. This may take a while ...
> wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT
>Apt-get install wodim confirms I have the latest release. I have also
>run apt-get
Thomas H. George <[EMAIL PROTECTED]>:
> Joerg Schily's original cdrecord works perfectly.
>
> Apparently I have a box of bad blank cdrw disks, 100 of them unfortunately.
> I tried cdrw disks from another box and cdrecord ran the Lite-On drive at
> 25x with no problems.
fwiw, I've heard a
Joerg Schily's original cdrecord works perfectly.
Apparently I have a box of bad blank cdrw disks, 100 of them unfortunately.
I tried cdrw disks from another box and cdrecord ran the Lite-On drive at
25x with no problems.
Tom George
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
On 09/16/2007 07:29 PM, Thomas H. George wrote:
On Sept. 7 I posted a problem,
"I have an Etch box with a linux-image-2.6.18-5-k7. All works well but
wodim -devices
Beginning native device scan. This may take a while ...
wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT
Apt-get ins
On Sun, Sep 16, 2007 at 08:29:18PM -0400, Thomas H. George wrote:
> On Sept. 7 I posted a problem,
>
> "I have an Etch box with a linux-image-2.6.18-5-k7. All works well but
>
> wodim -devices
> Beginning native device scan. This may take a while ...
> wodim: Invalid argument. Cannot Set
Woohoo, reloading works indeed. The files are visible when I use the -eject
flag and mount the cd afterwards.
Thanks for the helping part
Regards,
Ben
2007/1/30, Eduard Bloch <[EMAIL PROTECTED]>:
#include
* Sonixxfx [Tue, Jan 23 2007, 03:11:47PM]:
> Hi,
>
> I am trying to burn multisession
#include
* Sonixxfx [Tue, Jan 23 2007, 03:11:47PM]:
> Hi,
>
> I am trying to burn multisession cd's with cdrecord but I have a problem.
> After I have written a multisession disc, and mount it, the burned files are
> not shown at /media/cdrom. The files are written to the disc though, because
> I
Please help me!
Thanks :)
2007/1/23, Sonixxfx <[EMAIL PROTECTED]>:
Hi,
I am trying to burn multisession cd's with cdrecord but I have a problem.
After I have written a multisession disc, and mount it, the burned files are
not shown at /media/cdrom. The files are written to the disc though, b
I thought this problem only occured with a 2.4 kernel, but it is also
happening with a 2.6 kernel.
Thanks
Ben
2007/1/23, Sonixxfx <[EMAIL PROTECTED]>:
Hi,
I am trying to burn multisession cd's with cdrecord but I have a problem.
After I have written a multisession disc, and mount it, the b
On Sat, 25 Nov 2006 19:04:21 +0100, Stephan Seitz wrote:
> Don't use the group disk, use group cdrom instead. Anyone in group disk
> can read and write direct to the disks (e.g deleting partitions). You
> don't want this.
Ah, sure ! - I think now it is perfect.
Thanks,
Uwe
--
To UNSUBSCRIBE
On Sun, Nov 26, 2006 at 01:22:47AM +0800, Uwe Dippel wrote:
# ls -l /dev/hdd
brw-rw 1 root disk 22, 64 2004-04-30 08:27 /dev/hdd
The only thing needed is that your user is member of group 'disk'. The
latter shows why.
Don’t use the group disk, use group cdrom instead. Anyone in group disk
On Wed October 25 2006 09:45, Javier-Elias Vasquez-Vivas wrote:
> [...]
>
> > I wonder why the change to wodim, cdrecord has been the main stay for cd
> > burning for as long as I can remember. If wodim is the default now I hope
> > it will work as well as cdrecord has all these years.
>
> http://l
[...]
I wonder why the change to wodim, cdrecord has been the main stay for cd
burning for as long as I can remember. If wodim is the default now I hope it
will work as well as cdrecord has all these years.
http://lwn.net/Articles/198171/
--
Javier
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
On Wed October 25 2006 09:12, Wayne Topa wrote:
> Wayne Topa([EMAIL PROTECTED]) is reported to have said:
> > Just upgraded cdrecord and k3b to burn a Knoppix CD and find that
> > the new replacement for cdrecord, wodim, can't handle it. It fails
> > saying the file is larger the the CD.
> >
Wayne Topa([EMAIL PROTECTED]) is reported to have said:
> Just upgraded cdrecord and k3b to burn a Knoppix CD and find that
> the new replacement for cdrecord, wodim, can't handle it. It fails
> saying the file is larger the the CD.
>
> I have burned 6-8 of these CD's with k3b/cdrecord wi
#include
* Wayne Topa [Tue, Oct 24 2006, 03:08:08PM]:
> Just upgraded cdrecord and k3b to burn a Knoppix CD and find that
> the new replacement for cdrecord, wodim, can't handle it. It fails
> saying the file is larger the the CD.
Show your media data, "wodim -atip". And the exact output w
On 8/31/06, Paul Dwerryhouse <[EMAIL PROTECTED]> wrote:
On Thu, Aug 31, 2006 at 11:11:37PM +0200, ciol wrote:> # cdrecord -v dev=1,1,0 speed=10 dl/debian-31r2-i386-binary-1.isoI've found that it's possible to just use the device name; whether thisis good or bad, I don't know, but it works for me:
c
ciol wrote:
Hello, I have got a problem with cdrecord. My CD-writer is an 'ATAPI'.
So I followed these instructions :
/usr/share/doc/cdrecord/README.ATAPI.setup
# cdrecord dev=ATA: -scanbus
I get :
scsidev: 'ATA:'
devname: 'ATA'
scsibus: -1 target: -1 lun: -1
Warning: Using badly designed ATA
ciol wrote:
Hello, I have got a problem with cdrecord. My CD-writer is an 'ATAPI'.
So I followed these instructions :
/usr/share/doc/cdrecord/README.ATAPI.setup
# cdrecord dev=ATA: -scanbus
I get :
scsidev: 'ATA:'
devname: 'ATA'
scsibus: -1 target: -1 lun: -1
Warning: Using badly designed ATA
Thanks Paul and Rage, your two solutions seem to be better, but it doesn't
work either. It doesn't matter : I think it's because my cd-writer is
broken (I can't remember if it worked with Windows(c) or not).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
On Thu, Aug 31, 2006 at 11:11:37PM +0200, ciol wrote:
> # cdrecord -v dev=1,1,0 speed=10 dl/debian-31r2-i386-binary-1.iso
I've found that it's possible to just use the device name; whether this
is good or bad, I don't know, but it works for me:
cdrecord -v dev=/dev/hdd(etc etc)
C
Hi,
On 9/1/06, ciol <[EMAIL PROTECTED]> wrote:
# cdrecord -v dev=1,1,0 speed=10 dl/debian-31r2-i386-binary-1.iso
This works for me. Instead of dev=1,1,0 try dev=ATA:1,1,0
Regards,
Rage
--
Free Software :: empower :: educate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
José Alburquerque wrote:
Does anyone know a way for regular users to use cdrecord for CD
writing/blanking without the need for it to setuid? Any pointers
would be greatly appreciated. Thanks!
Just thought I'd let everyone know, I think I'll just be using cdrecord
as it is. I'll keep all
David E. Fox wrote:
On Tue, 8 Aug 2006 16:55:54 -0600
"Dwayne C. Litzenberger" <[EMAIL PROTECTED]> wrote:
Also be CAREFUL. On my system, /usr/bin/cdrecord is a SHELL SCRIPT, and
SUID-root shell scripts are a big security hole, IIRC. You probably want
to set the permissions on /usr/bin/cd
On Wed, 2006-08-09 at 10:05 +0200, Eduard Bloch wrote:
> #include
> * Hank The Tank Winky Poo [Wed, Aug 09 2006, 03:01:37PM]:
> > Hello all
> >
> > While we're on cdrecord, at the end of the command
> >
> > sudo cdrecord -v -sao -dev=4,0,0 speed=4 driveropts=audiomaster
> > -audio
>
#include
* Hank The Tank Winky Poo [Wed, Aug 09 2006, 03:01:37PM]:
> Hello all
>
> While we're on cdrecord, at the end of the command
>
> sudo cdrecord -v -sao -dev=4,0,0 speed=4 driveropts=audiomaster
> -audio
> *.wav
>
> I get something like...(after the audio tracks have been
On Tue, Aug 08, 2006 at 08:53:35PM -0700, David E. Fox wrote:
To the OP - you can, I suppose, chmod the /usr/bin/cdrecord to regular
non-suid (chmod 750 /usr/bin/cdrecord). I notice the permissions here
for it are -rwsr-xr-- implying that others can read the binary, but not
execute it. (2754 in #
On 08/08/2006 12:32 AM, Mike McCarty wrote:
Mumia W. wrote:
[...] Sudo is the only
alternative to making cdrecord SUID root.
And a very viable one.
Mike
But people should know that they would have to create a
special script to run cdrecord under sudo, or it would be less
safe than SUID ro
On Tue, 8 Aug 2006 16:55:54 -0600
"Dwayne C. Litzenberger" <[EMAIL PROTECTED]> wrote:
>
> Also be CAREFUL. On my system, /usr/bin/cdrecord is a SHELL SCRIPT, and
> SUID-root shell scripts are a big security hole, IIRC. You probably want
> to set the permissions on /usr/bin/cdrecord.mmap.
Good
On Tue, 08 Aug 2006 03:13:23 GMT
"s. keeling" <[EMAIL PROTECTED]> wrote:
>
> (0) heretic /home/keeling_ all `which cdrecord`
> -rwxr-xr-x 1 root root 133 2005-01-09 09:55 /usr/bin/cdrecord*
It's kernel-dependent, is it not? I mean, maybe you can do this in
2.6.8 (sarge defautl kernel) but not in
On Mon, 07 Aug 2006 13:39:43 -0600
Glenn English <[EMAIL PROTECTED]> wrote:
> I fought with this for a while and found the real problem to be permissions
> on the /dev file.
etch too here :)
As I understand the situation, whether a user is able to use the CD
device to write (reliably, that is) i
On Tue, Aug 08, 2006 at 12:32:49AM -0500, Mike McCarty wrote:
The user won't get much mileage out of it either. Sudo is the only
alternative to making cdrecord SUID root.
And a very viable one.
And it opens up a rather large security hole.
cdrecord is designed to be made suid-root; It drops
On Tue, Aug 08, 2006 at 12:49:27PM -0400, José Alburquerque wrote:
The setuid-root sollution (give only the group executable rights, make it
suid root), please note that this is a security risk - you have been
warned):
1) create a group and add users as above
2) remove world executable from cd
José Alburquerque wrote:
s. keeling wrote:
Very odd, on both of you.
(0) heretic /home/keeling_ all `which cdrecord`
-rwxr-xr-x 1 root root 133 2005-01-09 09:55 /usr/bin/cdrecord*
No SUID needed.
(0) heretic /home/keeling_ id
uid=1000(keeling) gid=1000(keeling)
groups=20(dialout),24(cdrom)
s. keeling wrote:
José Alburquerque <[EMAIL PROTECTED]>:
Thanks for your reply :-) I believe that my cdrecord has the same
permissions and everything works fine like this:
[EMAIL PROTECTED]:~$ ll `which cdrecord`
-rwsr-xr-- 1 root cdrom 133 2006-01-07 13:43 /usr/bin/cdrecord*
My problem
On 08/07/2006 03:52 PM, Mumia W. wrote:
[...] Sudo is the only
alternative to making cdrecord SUID root.
Oops. Evidently that isn't the only alternative. Others have
posted that they've run cdrecord without SUID root. Oh well,
on my kernel SUID root is required.
--
To UNSUBSCRIBE, ema
Mumia W. wrote:
I find it hard to believe that this works. I tried that too and
discovered that running cdrecord SUID root is a requirement; cdrecord
uses privileged IOCTLS (whatever they are).
IOCTL - Input/Output ConTroL
This does direct communication with the device driver. In this case,
t
On 08/07/2006 02:39 PM, Glenn English wrote:
José Alburquerque wrote:
My problem is that I'd like cdrecord not to have the SUID set (the 's'
in '-rwsr-xr--' above). I'm not sure this is possible, but if it is and
someone out there knows, I'd really appreciate it! I'm running testing
(etch)
José Alburquerque <[EMAIL PROTECTED]>:
> Matej Cepl wrote:
>
> >José Alburquerque wrote:
> >
> >>Does anyone know a way for regular users to use cdrecord for CD
> >>writing/blanking without the need for it to setuid? Any pointers would
> >>be greatly appreciated. Thanks!
> >
> >I think you need
#include
* Dwayne C. Litzenberger [Mon, Aug 07 2006, 03:16:46PM]:
> On Mon, Aug 07, 2006 at 01:39:43PM -0600, Glenn English wrote:
> >If you want to do it without the extra group, just make the burner world
> >write-able. I don't see how a cracker could get much mileage out of that...
>
> Note, h
Dwayne C. Litzenberger wrote:
On Mon, Aug 07, 2006 at 01:39:43PM -0600, Glenn English wrote:
If you want to do it without the extra group, just make the burner world
write-able. I don't see how a cracker could get much mileage out of
that...
Note, however, that if cdrecord doesn't run SUID
On Mon, Aug 07, 2006 at 01:39:43PM -0600, Glenn English wrote:
If you want to do it without the extra group, just make the burner world
write-able. I don't see how a cracker could get much mileage out of that...
Note, however, that if cdrecord doesn't run SUID root, it can't get
realtime sched
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
José Alburquerque wrote:
> My problem is that I'd like cdrecord not to have the SUID set (the 's'
> in '-rwsr-xr--' above). I'm not sure this is possible, but if it is and
> someone out there knows, I'd really appreciate it! I'm running testing
> (e
Matej Cepl wrote:
José Alburquerque wrote:
Does anyone know a way for regular users to use cdrecord for CD
writing/blanking without the need for it to setuid? Any pointers would
be greatly appreciated. Thanks!
I think you need to have at leas this:
chelcicky:~$ ll `which cdrecord`
José Alburquerque wrote:
> Does anyone know a way for regular users to use cdrecord for CD
> writing/blanking without the need for it to setuid? Any pointers would
> be greatly appreciated. Thanks!
I think you need to have at leas this:
chelcicky:~$ ll `which cdrecord`
-rwsr-xr-- 1 root cdrom 1
On 10 Jul 2006, Anthony Campbell wrote:
> On 06 Jul 2006, Anthony Campbell wrote:
> > I had to burn 20 CDs. All but one of the first 18 went off OK; I put the
> > single failure down to a faulty disk. But after I'd done 18 they all
> > started failing. I tried a disk from a different source but the
On 06 Jul 2006, Anthony Campbell wrote:
> I had to burn 20 CDs. All but one of the first 18 went off OK; I put the
> single failure down to a faulty disk. But after I'd done 18 they all
> started failing. I tried a disk from a different source but the same
> thing happened. I then tried to burn dis
Hugo Vanwoerkom wrote:
> 1. introducing udev brought about a change in the transport layer
> identification from ATAPI:0,1,0 to ATA:1,1,0.
This is plain wrong as udev has NOTHING to do with your problem, really. You
said that you also changed kernel version and THAT is the point where it
change
On Fri, Apr 07, 2006 at 03:57:56PM -0500, Hugo Vanwoerkom wrote:
> It might be that most users use cdrecord through the frontends, which I
> never use. And those may be smart enough to do dev=help, get the
> available id's, then -scanbus dev= and you will probably get
> the right dev= parame
Christopher Nelson wrote:
On Fri, Apr 07, 2006 at 04:11:28AM -0500, Hugo Vanwoerkom wrote:
Christopher Nelson wrote:
On Thu, Apr 06, 2006 at 05:29:16PM -0500, Hugo Vanwoerkom wrote:
Just a thought: have you tried using the device name, eg.
dev=/dev/ ?
I did, and that produces a message fr
On Fri, Apr 07, 2006 at 04:11:28AM -0500, Hugo Vanwoerkom wrote:
> Christopher Nelson wrote:
> >On Thu, Apr 06, 2006 at 05:29:16PM -0500, Hugo Vanwoerkom wrote:
> >Just a thought: have you tried using the device name, eg.
> >dev=/dev/ ?
> >
>
> I did, and that produces a message from cdrecord t
ssage-
From: Christopher Nelson [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 06, 2006 11:27 PM
To: debian-user@lists.debian.org
Subject: Re: cdrecord + udev
On Thu, Apr 06, 2006 at 05:29:16PM -0500, Hugo Vanwoerkom wrote:
> Hi,
>
> On Sarge, before installing udev to be able t
Christopher Nelson wrote:
On Thu, Apr 06, 2006 at 05:29:16PM -0500, Hugo Vanwoerkom wrote:
Hi,
On Sarge, before installing udev to be able to run 2.6.16 I invoked
cdrecord with dev=ATAPI:0,1,0 and all was well.
However after udev that does not work anymore. Now cdrecord -scanbus gives:
Linu
On Thu, Apr 06, 2006 at 05:29:16PM -0500, Hugo Vanwoerkom wrote:
> Hi,
>
> On Sarge, before installing udev to be able to run 2.6.16 I invoked
> cdrecord with dev=ATAPI:0,1,0 and all was well.
>
> However after udev that does not work anymore. Now cdrecord -scanbus gives:
>
> Linux sg driver ve
oot cdrecording 323540 2005-09-17 /usr/bin/cdrecord.mmap
> -rwxr-xr-- 1 root cdrom 323540 2005-09-17 /usr/bin/cdrecord.shm
>
> -Original Message-
> From: Ernst-Magne Vindal [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 04, 2006 12:14 PM
> To: Lukas Ruf
> Cc:
cdrom 323540 2005-09-17 /usr/bin/cdrecord.shm
-Original Message-
From: Ernst-Magne Vindal [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 04, 2006 12:14 PM
To: Lukas Ruf
Cc: Debian User
Subject: Re: cdrecord as user
On Wed, January 4, 2006 11:41, Lukas Ruf said:
>> Ernst
On Wed, January 4, 2006 11:41, Lukas Ruf said:
>> Ernst-Magne Vindal <[EMAIL PROTECTED]> [2006-01-04 10:45]:
>>
>> Hi, I need help get cdrecord running as normal user.
>>
>> I have installed it as suid root but get access denied trying to run it
>> as
>> normal user. The user is in the group "cdro
On Wed, Jan 04, 2006 at 10:43:29AM +0100, Ernst-Magne Vindal wrote:
> Hi, I need help get cdrecord running as normal user.
>
> I have installed it as suid root but get access denied trying to run it as
> normal user. The user is in the group "cdrom"
>
> cdrom dev is: brw-rw 1 root cdrom 11,
> Ernst-Magne Vindal <[EMAIL PROTECTED]> [2006-01-04 10:45]:
>
> Hi, I need help get cdrecord running as normal user.
>
> I have installed it as suid root but get access denied trying to run it as
> normal user. The user is in the group "cdrom"
>
what is the output of 'id -a' as that user? If it'
On Wed, January 4, 2006 18:34, Sinan Nalkaya said:
> hi,
> you may need to add yourself in /etc/groups at cdrom part.
>
> On Wed, 2006-01-04 at 10:43 +0100, Ernst-Magne Vindal wrote:
>> Hi, I need help get cdrecord running as normal user.
>>
>> I have installed it as suid root but get access denie
hi,
you may need to add yourself in /etc/groups at cdrom part.
On Wed, 2006-01-04 at 10:43 +0100, Ernst-Magne Vindal wrote:
> Hi, I need help get cdrecord running as normal user.
>
> I have installed it as suid root but get access denied trying to run it as
> normal user. The user is in the group
Žáček Kryštof wrote:
>>
>>I recently had a similar problem. After starting the k3b
>>installation assistant, /usr/bin/cdrecord.mmap lost it's
>>set-uid bit. I reinstalled it with chmod u+s
>>/usr/bin/cdrecord.mmap and now, k3b works fine again (do not
>>start k3b assistant).
>>
>># l /usr/bin/
Tim Ruehsen wrote:
> I recently had a similar problem. After starting the k3b installation
> assistant, /usr/bin/cdrecord.mmap lost it's set-uid bit. I reinstalled it
> with chmod u+s /usr/bin/cdrecord.mmap and now, k3b works fine again (do not
> start k3b assistant).
>
> # l /usr/bin/cdrec*
>
? cdrecord ? K3b ? Communists ?
> -Original Message-
> From: Tim Ruehsen [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 26, 2005 6:01 PM
> To: debian-user@lists.debian.org
> Subject: Re: Cdrecord and linux 2.6.12
>
> Am Montag, 26. September 2005 16:48 schrieb Žáč
Sridhar M.A. wrote:
On Mon, Sep 26, 2005 at 10:55:39AM -0400, Arthur H. Johnson II wrote:
>
> You could always do what I did. 2.6.6 works fine for me. Of course, you
> might not be able to get to it now. Good think I never EVER remove old
> kernels unless they are REALLY old ;)
Am Montag, 26. September 2005 16:48 schrieb Žáček Kryštof:
> Lucky you. I did not even get so far to spoil the CD. K3b permanently fails
to burn any data CD for me with 2.6 kernel.
> It keeps reporting something about failing mkisofs or cdrecord, operation
not permitted or so.
I recently had a s
On Mon, Sep 26, 2005 at 10:55:39AM -0400, Arthur H. Johnson II wrote:
>
> You could always do what I did. 2.6.6 works fine for me. Of course, you
> might not be able to get to it now. Good think I never EVER remove old
> kernels unless they are REALLY old ;)
>
I beg to differ. I
You could always do what I did. 2.6.6 works fine for me. Of course, you
might not be able to get to it now. Good think I never EVER remove old
kernels unless they are REALLY old ;)
On Mon, 26 Sep 2005, [iso-8859-2] Žáček Kryštof wrote:
> Lucky you. I did not even get so far to spoil the CD. K
Lucky you. I did not even get so far to spoil the CD. K3b permanently fails to
burn any data CD for me with 2.6 kernel.
It keeps reporting something about failing mkisofs or cdrecord, operation not
permitted or so.
The same setup did work fine in the past with 2.6 kernels. Now, with fully
up-to
Hi and sorry for the delay
I'm not using a frontend. I'v tryed xcdroast once, but I'm not using it.
Thanks for all the replies. I'll try this.
Erdi Balint wrote:
Hi,
Yes, I went throught the same thing just some days ago and with the
dev=/dev/hdc (or wherever your CD writer is) setting it wo
On Wed, Sep 14, 2005 at 08:19:30AM +0200, Erdi Balint wrote:
> Hi,
>
> Yes, I went throught the same thing just some days ago and with the
> dev=/dev/hdc (or wherever your CD writer is) setting it works as it
> should. However, how do you make a front-end (namely xcdroast) use this
> setting?
Erdi Balint wrote:
Hi,
Yes, I went throught the same thing just some days ago and with
the dev=/dev/hdc (or wherever your CD writer is) setting it
works as it should. However, how do you make a front-end
(namely xcdroast) use this setting? I keep getting scanbus
errors using xcdroast and unable
Hi,
Yes, I went throught the same thing just some days ago and with the
dev=/dev/hdc (or wherever your CD writer is) setting it works as it
should. However, how do you make a front-end (namely xcdroast) use this
setting? I keep getting scanbus errors using xcdroast and unable to even
blank a
You might try -dev=hdc for the dev parameter and try cdrecord -scanbus
dev=atapi to see what kind of results you'll likely get. You're better
off loosing the speed parameter and loosing the -data parameter and
replace both of them with -sao. Beyond that I don't know since you're
using paramet
1 - 100 of 492 matches
Mail list logo
