Hi,
I'd like to use cdrecord on the command line. I'm currently reading the relevant chapter in Carla Schroder's "Linux Cookbook". Unfortunately, some of the tricks and hints included in the book don't seem to work the same way on a standard CentOS 5 install.
1) Am I supposed to be root to use cdrecord and burn an .iso file?
2) How do I specify a device? 'cdrecord -scanbus' doesn't seem to work. Say my CD burner is /dev/hdc, would 'cdrecord dev=/dev/hdc' be the correct way to address it?
Cheers,
Niki
] On Sun, 2009-04-12 at 13:49 +0200, Niki Kovacs wrote:
Hi,
I'd like to use cdrecord on the command line. I'm currently reading the relevant chapter in Carla Schroder's "Linux Cookbook". Unfortunately, some of the tricks and hints included in the book don't seem to work the same way on a standard CentOS 5 install.
Am I supposed to be root to use cdrecord and burn an .iso file?
How do I specify a device? 'cdrecord -scanbus' doesn't seem to work.
Say my CD burner is /dev/hdc, would 'cdrecord dev=/dev/hdc' be the correct way to address it?
Linux has brogressed a lot in this area since cdrecord first began. Recentl (for me) it looks like the SCSI bus scan is not reliable. But using the standard /dev/h[abcd] could. However, you should have a link called /dev/cdrom. Use that if it's there. Be aware that you can config this stuff in /etc/cdrecord.conf and not have to put it on the command line, after testing is completed.
Cheers,
Niki
<snip sig stuff>
HTH
At Sun, 12 Apr 2009 13:49:03 +0200 CentOS mailing list centos@centos.org wrote:
Hi,
I'd like to use cdrecord on the command line. I'm currently reading the relevant chapter in Carla Schroder's "Linux Cookbook". Unfortunately, some of the tricks and hints included in the book don't seem to work the same way on a standard CentOS 5 install.
- Am I supposed to be root to use cdrecord and burn an .iso file?
Yes and no. Depends on the permissions of the recording device's /dev/ file. Probably recomended that you run as root. This also allows for near real time scheduling.
- How do I specify a device? 'cdrecord -scanbus' doesn't seem to work.
Say my CD burner is /dev/hdc, would 'cdrecord dev=/dev/hdc' be the correct way to address it?
Cheers,
Niki _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Niki Kovacs wrote:
Hi,
I'd like to use cdrecord on the command line. I'm currently reading the relevant chapter in Carla Schroder's "Linux Cookbook". Unfortunately, some of the tricks and hints included in the book don't seem to work the same way on a standard CentOS 5 install.
- Am I supposed to be root to use cdrecord and burn an .iso file?
I've found it works much better if you are root.
- How do I specify a device? 'cdrecord -scanbus' doesn't seem to work.
Say my CD burner is /dev/hdc, would 'cdrecord dev=/dev/hdc' be the correct way to address it?
cdrecord -dev=/dev/hdc -speed=24 -dao -pad file.iso
(of course your options may vary)
Note for SATA burners, /dev/scd0
is probably what you want. For PATA/ATAPI (what it sounds like you have) then /dev/hdc probably is best - I haven't burned an old ATA burner in a long time.
At Sun, 12 Apr 2009 12:39:06 -0700 CentOS mailing list centos@centos.org wrote:
Niki Kovacs wrote:
Hi,
I'd like to use cdrecord on the command line. I'm currently reading the relevant chapter in Carla Schroder's "Linux Cookbook". Unfortunately, some of the tricks and hints included in the book don't seem to work the same way on a standard CentOS 5 install.
- Am I supposed to be root to use cdrecord and burn an .iso file?
I've found it works much better if you are root.
- How do I specify a device? 'cdrecord -scanbus' doesn't seem to work.
Say my CD burner is /dev/hdc, would 'cdrecord dev=/dev/hdc' be the correct way to address it?
cdrecord -dev=/dev/hdc -speed=24 -dao -pad file.iso
(of course your options may vary)
Note for SATA burners, /dev/scd0
SATA devices should up as SCSI devices, so I would suspect that SCSI bus device specs would work also.
is probably what you want. For PATA/ATAPI (what it sounds like you have) then /dev/hdc probably is best - I haven't burned an old ATA burner in a long time. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Michael A. Peters a écrit :
- Am I supposed to be root to use cdrecord and burn an .iso file?
I've found it works much better if you are root.
I tried both, and see: cdrecord complains about not being able to set certain priorities while being run as user, which induces a high risk for buffer underruns. So I have my answer for that.
Another cdrecord-related question. Usually I should be able to copy a CD as simply as that:
$ dd if=/dev/cdrom of=copy.iso
Then insert a blank CD, and:
$ cdrecord -v -eject dev=/dev/cdrom copy.iso
Now I did that for data CDs, and it works very well. I thought, normally this *should* also work for audio CDs, so I gave that a spin. But everytime I try it, dd stops short and gives me an "Input/output error" for /dev/hdc.
I tried three different audio CDs, all three in good state. I can listen to them OK on the PC. But all I get with dd is a zero-byte-length copy.iso file.
Any idea what's happening?
Niki
On Wed, 2009-04-15 at 15:46 +0200, Niki Kovacs wrote:
Michael A. Peters a écrit :
- Am I supposed to be root to use cdrecord and burn an .iso file?
I've found it works much better if you are root.
I tried both, and see: cdrecord complains about not being able to set certain priorities while being run as user, which induces a high risk for buffer underruns. So I have my answer for that.
Another cdrecord-related question. Usually I should be able to copy a CD as simply as that:
$ dd if=/dev/cdrom of=copy.iso
Then insert a blank CD, and:
$ cdrecord -v -eject dev=/dev/cdrom copy.iso
Now I did that for data CDs, and it works very well. I thought, normally this *should* also work for audio CDs, so I gave that a spin. But everytime I try it, dd stops short and gives me an "Input/output error" for /dev/hdc.
I tried three different audio CDs, all three in good state. I can listen to them OK on the PC. But all I get with dd is a zero-byte-length copy.iso file.
Any idea what's happening?
Try padding copied image with a few hundred k of nulls.
dd if=/dev/zero of=copy.iso \ seek=<number of output blocks to skip forward> bs=2048
I've had to do this for my ISO images depending on the age/brand/model of the device. It seems that (at least in the past) there was a disconnect in the kernel handling of the end of file and writing the last blocks read in. This cured it.
I can't say if this would affect audio CDs as well, but worth a try.
Niki
<snip sig stuff>
HTH
On Wed, 2009-04-15 at 10:45 -0400, William L. Maltby wrote:
On Wed, 2009-04-15 at 15:46 +0200, Niki Kovacs wrote:
Michael A. Peters a écrit :
- Am I supposed to be root to use cdrecord and burn an .iso file?
I've found it works much better if you are root.
I tried both, and see: cdrecord complains about not being able to set certain priorities while being run as user, which induces a high risk for buffer underruns. So I have my answer for that.
Another cdrecord-related question. Usually I should be able to copy a CD as simply as that:
$ dd if=/dev/cdrom of=copy.iso
Then insert a blank CD, and:
$ cdrecord -v -eject dev=/dev/cdrom copy.iso
Now I did that for data CDs, and it works very well. I thought, normally this *should* also work for audio CDs, so I gave that a spin. But everytime I try it, dd stops short and gives me an "Input/output error" for /dev/hdc.
I tried three different audio CDs, all three in good state. I can listen to them OK on the PC. But all I get with dd is a zero-byte-length copy.iso file.
Any idea what's happening?
Try padding copied image with a few hundred k of nulls.
dd if=/dev/zero of=copy.iso \ seek=<number of output blocks to skip forward> bs=2048
OOPS! Forgot to limit the output. Add count=<number of blocks> to the end of the command.
<snip>
From: Niki Kovacs contact@kikinovak.net
Now I did that for data CDs, and it works very well. I thought, normally this *should* also work for audio CDs, so I gave that a spin. But everytime I try it, dd stops short and gives me an "Input/output error" for /dev/hdc.
Couldn't it be the copy protection...?
JD
From: Niki Kovacs contact@kikinovak.net
Couldn't it be the copy protection...?
In theory, dd should also take care of copying the copy protection, isn't it?
I think I am confusing with something else. The trick they used was to put errors. It would still play with hifi players (error correction codes), but would fail on PCs... I guess it is not the case since you can listen to them on your PC.
So ignore me... ^_^
JD
At Wed, 15 Apr 2009 15:46:20 +0200 CentOS mailing list centos@centos.org wrote:
Michael A. Peters a écrit :
- Am I supposed to be root to use cdrecord and burn an .iso file?
I've found it works much better if you are root.
I tried both, and see: cdrecord complains about not being able to set certain priorities while being run as user, which induces a high risk for buffer underruns. So I have my answer for that.
Another cdrecord-related question. Usually I should be able to copy a CD as simply as that:
$ dd if=/dev/cdrom of=copy.iso
Then insert a blank CD, and:
$ cdrecord -v -eject dev=/dev/cdrom copy.iso
Now I did that for data CDs, and it works very well. I thought, normally this *should* also work for audio CDs, so I gave that a spin. But everytime I try it, dd stops short and gives me an "Input/output error" for /dev/hdc.
While dd *can* be used to copy single-track data CDs, it is better to use the readcd program (comes with the cdrecord package). For audio CDs, the cdda2wav program would be a better option.
I tried three different audio CDs, all three in good state. I can listen to them OK on the PC. But all I get with dd is a zero-byte-length copy.iso file.
An audio CD is not like a data CD. It does not have a 'file system'. It is a collection of data tracks, containing cdda files.
Any idea what's happening?
Niki _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Robert Heller a écrit :
An audio CD is not like a data CD. It does not have a 'file system'. It is a collection of data tracks, containing cdda files.
Yeah, I know. But then, AFAIK, dd is supposed to handle these "binary sausages" as well. Meaning: take that input (whatever it is) and produce output without asking what it is.
Correct me if I'm wrong.
On Wed, 2009-04-15 at 18:22 +0200, Niki Kovacs wrote:
Robert Heller a écrit :
An audio CD is not like a data CD. It does not have a 'file system'. It is a collection of data tracks, containing cdda files.
Yeah, I know. But then, AFAIK, dd is supposed to handle these "binary sausages" as well. Meaning: take that input (whatever it is) and produce output without asking what it is.
Correct me if I'm wrong.
--- Try the no error option of dd see man dd.
At Wed, 15 Apr 2009 18:22:28 +0200 CentOS mailing list centos@centos.org wrote:
Robert Heller a écrit :
An audio CD is not like a data CD. It does not have a 'file system'. It is a collection of data tracks, containing cdda files.
Yeah, I know. But then, AFAIK, dd is supposed to handle these "binary sausages" as well. Meaning: take that input (whatever it is) and produce output without asking what it is.
Correct me if I'm wrong.
Assumes that the device in question behaves (or can behave) as a raw sequencental block device. Audio CDs are not, strictly speaking, like a partitioned (or partitionable) hard drive. CD-Rom 'tracks' are NOT like disk partitions. ReadCD and Cdda2wav don't just to raw read() calls (which is pretty much all dd does). They do some interesting ioctl() calls specific to CD-Roms as well -- these I/O calls relate to 'seeking' to the proper track and figuring out big the track is, etc.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
John Doe -
JohnS -
Michael A. Peters -
Niki Kovacs -
Robert Heller -
William L. Maltby