export CDR_DEVICE=ATA:1,0,0; CDRD=cdrom; CDR_DRV= export CDR_DEVICE=ATA:1,1,0; CDRD=dvd; CDR_DRV='--driver generic-mmc-raw' export CDR_DEVICE=ATA:0,0,0; CDRD=sony; CDR_DRV=
export CDR_DEVICE=ATA:1,0,0; CDRD=cdrom; CDR_DRV= export CDR_DEVICE=ATA:1,1,0; CDRD=dvd; CDR_DRV='--driver generic-mmc-raw' export CDR_DEVICE=ATA:0,0,0; CDRD=sony; CDR_DRV=
export CDR_DEVICE=2,0,0; CDRD=cdrom; CDR_DRV= export CDR_DEVICE=2,1,0; CDRD=sr1; CDR_DRV='--driver generic-mmc' export CDR_DEVICE=ATAPI:0,1,0; CDRD=hdd; CDR_DRV=
export CDR_DEVICE=0,0,0 export CDR_DEVICE='ATAPI:0,0,0 --driver generic-mmc'
CDR_DRV= CDR_DRV='--driver generic-mmc' CDR_DRV='--driver generic-mmc-raw'
CDR_SPEED=8 CDR_SPEED=12 CDR_SPEED=16 export CDR_SPEED=20
CDR_ environment vars are for cdrecord.
ISOF=../disk1.iso
CDRW=/dev/scd0 CDRW=/dev/sg0
*N*:
/dev/scd0 is SCSI driver.
/dev/sg0 is IDE driver.
ISOF=VOL01.iso
cdrecord -dummy -multi -v -tao speed=48 "$ISOF"
# check for CDR_DEVICE & CDR_SPEED cdrecord -v -tao -multi -eject driveropts=burnfree "$ISOF"
/usr/lib/anaconda-runtime/checkisomd5 $ISOF
CDR_SPEED=4 CDR_SPEED=8 CDR_SPEED=12 CDR_SPEED=16 echo nice -n -1 cdrecord -v -tao -multi -eject driveropts=burnfree speed=$CDR_SPEED `fp2a "$ISOF"`
/usr/lib/anaconda-runtime/checkisomd5 /dev/cdrom
$ cdrecord -msinfo 31694,58903
cdrecord blank=fast
-msinfo retrieve multi-session info for mkisofs >= 1.10 -toc retrieve and print TOC/PMA data
-dummy do everything with laser turned off -fix fixate a corrupt or unfixated disk (generate a TOC)
CDR_DEVICE
This may either hold a device identifier that is suitable to the
open call of the SCSI transport library or a label in the file
/etc/default/cdrecord.
CDR_SPEED
Sets the default speed value for writing (see also -speed
option).
TRACK=`cdrecord -msinfo` TRACK=`cdrecord -msinfo dev=$CDRW` mkisofs -r -J -f -C $TRACK -M $CDRW files... | cdrecord -multi dev=$CDRW -eject -v speed=$CDR_SPEED
$ cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jorg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
scsibus0:
0,0,0 0) 'SONY ' 'CD-RW CRX175A1 ' '5YS2' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
$ cdrecord -msinfo dev=0,0,0 cdrecord: Input/output error. test unit ready: scsi sendcmd: no error CDB: 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.160s timeout 40s cdrecord: No disk / Wrong disk!
CD writer is on SCSI bus 0, with ID number 0 and LUN 0 (you can obtain these values by issuing a cdrecord -scanbus and assign them to the -dev= parameter).
cdrecord dev=/dev/sg0 blank=all -force
-force Force to continue on some errors. This option currently imple-
ments some tricks that will allow you to blank bad CD-RW disks.
blank=type
Blank a CD-RW and exit or blank a CD-RW before writing. The
blanking type may be one of:
help Display a list of possible blanking types.
all Blank the entire disk. This may take a long time.
fast Minimally blank the disk. This results in erasing
the PMA, the TOC and the pregap.
track Blank a track.
unreserve Unreserve a reserved track.
trtail Blank the tail of a track.
unclose Unclose last session.
session Blank the last session.
Blocks total: 337350 Blocks current: 337350 Blocks remaining: -22268 cdrecord: WARNING: Data may not fit on current disk. RBlocks total: 349030 RBlocks current: 349030 RBlocks remaining: -10588 cdrecord: Data does not fit on current disk.
If the overall speed of the system is sufficient and the structure of the filesystem is not too complex, cdrecord will run without creating an image of the ISO 9660 filesystem. Simply run the pipeline:
mkisofs -R /master/tree | cdrecord -v fs=6m speed=2 dev=2,0 -
The recommended minimum FIFO size for running this pipeline is 4 MBytes. As the default FIFO size is 4 MB, the fs= option needs only be present if you want to use a different FIFO size. If your system is loaded, you should run mkisofs in the real time class too. To raise the priority of mkisofs replace the command
mkisofs -R /master/tree by
priocntl -e -c RT -p 59 mkisofs -R /master/tree
on Solaris and by
nice --18 mkisofs -R /master/tree
on systems that don't have UNIX International compliant real-time scheduling.
Cdrecord runs at priority 59 on Solaris, you should run mkisofs at no more than priority 58. On other systems, you should run mkisofs at no less than nice —18.
Creating a CD-ROM without file system image on disk has been tested on a Sparcstation-2 with a Yamaha CDR-400. It did work up to quad speed when the machine was not loaded. A faster machine may be able to han- dle quad speed also in the loaded case.
fs= Set the FIFO (ring buffer) size to . You may use the same syn- tax as in dd(1), sdd(1) or star(1). The number representing the size is taken in bytes unless otherwise specified. If a number is followed directly by the letter `b', `k', `m', `s' or `f', the size is multiplied by 512, 1024, 1024*1024, 2048 or 2352. If the size consists of numbers separated by `x' or `*', multi- plication of the two numbers is performed. Thus fs=10x63k will specify a FIFO size of 630 kBytes.
+ The size specified by the fs= argument includes the shared memory that is needed for administration. This is at least one page of memory. If no fs= option is present, cdrecord will try to get the FIFO size value from the CDR_FIFOSIZE environment. The default FIFO size is currently 4 MB.
+ The FIFO is used to increase buffering for the real time writing process. It allows to run a pipe from mkisofs directly into cdrecord. If the FIFO is active and a pipe from mkisofs into cdrecord is used to create a CD, cdrecord will abort prior to do any modifications on the disk if mkisofs dies before it starts writing. The recommended FIFO size is between 4 and 128 MBytes. As a rule of thumb, the FIFO size should be at least equal to the size of the internal buffer of the CD/DVD-Recorder and no more than half of the physical amount of RAM available in the machine. If the FIFO size is big enough, the FIFO statistics will print a FIFO empty count of zero and the FIFO min fill is not below 20%. It is not wise to use too much space for the FIFO. If you need more than 8 MB to write a CD at a speed less than 20x from an image on a local file system on an idle machine, your machine is either underpowered, has hardware problems or is mis-configured. If you like to write DVDs or to write CDs at higher speed, it makes sense to use at least 16 MB for the FIFO.
-waiti Wait for input to become available on standard input before try- ing to open the SCSI driver. This allows cdrecord to read it's input from a pipe even when writing additional sessions to a multi session disk. When writing another session to a multi session disk, mkisofs needs to read the old session from the device before writing output. This cannot be done if cdrecord opens the SCSI driver at the same time.
-immed Tell cdrecord to set the SCSI IMMED flag in certain commands (load/eject/blank/close_track/close_session). This can be use- ful on broken systems with ATAPI harddisk and CD/DVD writer on the same bus or with SCSI systems that don't use discon- nect/reconnect. These systems will freeze while blanking or fixating a CD/DVD or while a DVD writer is filling up a session to the minimum amount (approx. 800 MB). Setting the -immed flag will request the command to return immediately while the opera- tion proceeds in background, making the bus usable for the other devices and avoiding the system freeze. This is an experimental feature which may work or not, depending on the model of the CD/DVD writer. A correct solution would be to set up a correct cabling but there seem to be notebooks around that have been set up the wrong way by the manufacturer. As it is impossible to fix this problem in notebooks, the -immed option has been added.
A second experimental feature of the -immed flag is to tell cdrecord to try to wait short times while writing to the media. This is expected to free the IDE bus if the CD/DVD writer and the data source are connected to the same IDE cable. In this case, the CD/DVD writer would otherwise usually block the IDE bus for nearly all the time making it impossible to fetch data from the source drive. See also minbuf= and -v option.
Use both features at your own risk. If it turns out that it would make sense to have a separate option for the wait feature, write to the author and convince him.
minbuf=value The # minbuf= option allows to define the minimum drive buffer fill ratio for the experimental ATAPI wait mode that is intended to free the IDE bus to allow hard disk and CD/DVD writer to be on the same IDE cable. As the wait mode currently only works when the verbose option -v has been specified, cdrecord implies the verbose option in case the -immed or minbuf= option have been specified. Valid values for minbuf= are between 25 and 95 for 25%…95% minimum drive buffer fill ratio.
cdrecord -tao -multi -v speed=16 "VOL04.iso" Forcespeed is OFF. Starting to write CD/DVD at speed 16 in real TAO mode for multi session. BURN-Free is OFF. Performing OPC... Starting new track at sector: 0 [...]
$ cdrecord -checkdrive scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.8'. Device type : Removable CD-ROM Version : 0 Response Format: 2 Capabilities : Vendor_info : 'SONY ' Identifikation : 'CD-RW CRX195E1 ' Revision : 'ZYS5' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
$ cdrecord driveropts=help -checkdrive [...] Driver options: burnfree Prepare writer to use BURN-Free technology noburnfree Disable using BURN-Free technology forcespeed Tell the drive to force speed even for low quality media
$ cdrecord -setdropts driveropts=burnfree [...] Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Turning BURN-Free on
$ cdrecord -tao -multi -v speed=16 "VOL05.iso" BURN-Free is ON. Turning BURN-Free off Performing OPC...
$ cdrecord -v -tao -multi -setdropts driveropts=burnfree speed=16 "VOL07.iso" cdrecord: No tracks allowed with this option
$ cdrecord -v -tao -multi driveropts=burnfree speed=16 "VOL08.iso" BURN-Free is OFF. Turning BURN-Free on Performing OPC...
$ cdrecord -v -tao -multi driveropts=burnfree speed=16 "VOL09.iso" BURN-Free is ON. Performing OPC...
documented on: 2004.09.17
Any way to ignore the "L-EC error" data, save them as is, without error correction and retrying?
$ cdrdao read-cd --read-raw --eject --device $CDR_DEVICE --speed 48 --datafile $ToBurn.bin $ToBurn.toc Cdrdao version 1.1.9 - (C) Andreas Mueller <andreas@daneb.de> Using libscg version 'schily-0.8' Using driver: Generic SCSI-3/MMC (raw writing) - Version 2.0 (options 0x0000)
PQ sub-channel reading (data track) is supported, data format is BCD. Raw P-W sub-channel reading (data track) is supported. Cooked R-W sub-channel reading (data track) is supported. Copying data track 1 (MODE2_RAW): start 00:00:00, length 01:14:00 to "hwdd-31.bin"... WARNING: Found L-EC error at sector 2114 - ignored. [...] WARNING: Found L-EC error at sector 2128 - ignored. [...]
That's pretty much all I can do.
The "L-EC error" is handled in dao/CdrDriver.cc, function CdrDriver::readDataTrack.
When the L-EC error is met (readTrackData returns -2), readDataTrack will stop the burst read mode and switch to single step mode, re-reading a single track instead, by setting the burst = 1 then n=1.
Should the readTrackData fails the 2nd time, readDataTrack will create a dummy sector for the sector with L-EC errors.
The readTrackData is defined in several places, e.g., dao/SonyCDU920.cc, dao/CDD2600.cc, etc. Normally it is provided by dao/GenericMMC.cc (and trackdb/Track.cc?).
When reading, the GenericMMC.cc will only "sendCmd" then use "getSense" to retrieve the return status of the command. When there is "Medium error", it simply return -2.
That's all handling in cdrdao. No several retries from this level.
--read-raw
Only used for commands read-cd and read-toc. All data sectors
will be written as 2352 byte blocks including the sector header
and L-EC data to the image file. The track mode will be set to
MODE1_RAW or MODE2_RAW in the created toc-file.
--read-subchan mode
Used by commands read-cd, read-toc and copy. Specifies the type
of sub-channel data that is extracted from the source CD and
written to the track image or copied to the destination CD.
Mode may be rw for reading packed R-W sub-channel data (de-
interleaved and error corrected) and rw_raw for reading raw R-W
sub-channel data (not de-interleaved, not error corrected, L-EC
data included in the track image). If this option is not speci-
fied no sub-channel data will be extracted.
$ cdrdao read-cd --read-raw --read-subchan rw_raw --eject --device $CDR_DEVICE --speed 48 --datafile $ToBurn.bin $ToBurn.toc PQ sub-channel reading (data track) is supported, data format is BCD. Raw P-W sub-channel reading (data track) is supported. Cooked R-W sub-channel reading (data track) is supported. Copying data track 1 (MODE2_RAW): start 00:00:00, length 01:14:00 to "hwdd-31.bin"... WARNING: Found L-EC error at sector 2114 - ignored.
don't know the effect adding it, and don't seem to speed up any. So, decided not to use it.
$ cdrdao read-cd --read-subchan rw_raw --eject --device $CDR_DEVICE --speed 48 --datafile $ToBurn.bin $ToBurn.toc Copying data track 1 (MODE2_FORM_MIX): start 00:00:00, length 01:14:00 to "hwdd-31.bin"... ERROR: L-EC error around sector 2106 while copying data from track. ERROR: Use option '--read-raw' to ignore L-EC errors.
documented on: 2005.02.15
> [Kevin@Keatings Disk-1]$ cdrecord -dummy -v speed=2 dev=1,0,0 -audio "5th > Element - The Diva Dance.wav" > Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J\u9c0eg Schilling > TOC Type: 0 = CD-DA > cdrecord: Operation not permitted. WARNING: Cannot do mlockall(2). > cdrecord: WARNING: This causes a high risk for buffer underruns. > cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler > cdrecord: Operation not permitted. WARNING: Cannot set priority using > nice(). > cdrecord: WARNING: This causes a high risk for buffer underruns. > cdrecord: Operation not permitted. shmctl failed to lock shared memory > segment > [Kevin@Keatings Disk-1]$
I think you need to be root to run cdrecord on most systems.
Stan Seibert
Date: 08/08/03
> > chmod 4710 /usr/bin/cdrecord.* > > chmod 755 /usr/bin/cdrecord > > Thanks, those two commands solved the problems :-)
Cool.
> I don't know the syntax chmod 4710 /usr/bin/cdrecord.* > ... well I'll have a look at the man page of chmod to > see what i means exactly :-)
It's a little terse… permit me to waffle :-)
The number 4710 is an octal number, ie. in base eight; each of its digits can have a value from 0 to 7 (decimal) which corresponds to 000 to 111 (binary) - ie. three bits per octal digit. The whole thing, 4 octal digits, is therefore a 12-bit binary number:
4 7 1 0 octal 1 0 0 1 1 1 0 0 1 0 0 0 binary
which is easy to convert in your head. It also fits neatly into the 12-bit file attributes value that chmod modifies:
4 7 1 0 octal 1 0 0 1 1 1 0 0 1 0 0 0 binary setuid setgid sticky r w x r w x r w x file attributes "special" flags user group other
or
setuid, user: read/write/execute, group: execute-only, other: no access
or
-rws--x---
The advantage of this method is that when making major changes to a file's permissions, and/or wanting to make sure that you wipe out any possibly untoward remnants of previous permissions, it saves a lot of typing over the chmod ug plus this wibble minus that dance. After a while, values like 4710, 755, 660 and suchlike become instinctive… having to set rw-rw-rw- is a bit dead and chewed though :-)
> By the way, I tried to be sure cd ripping works ok; > anyway > cdda2wav -D /dev/cdrom -B > doesn't give me any problems :-)
OOI is your cdda2wav setuid root? Mine is; this overcomes the problem Andreas mentioned, but I can't remember whether I set it that way or Debian did…
> Thank you for all your advice,
No prob. I take it you meant to post this to the list, rather than to me only? :-)
Pigeon
Newsgroups: gmane.linux.debian.user Date: Thu, 28 Oct 2004 12:42:09 -0700
On Thu, 2004-10-28 at 13:33 -0500, John Fleming wrote:
> Debian Sarge - I can burn CDs using K3B from the GUI, but I can't do > anything that uses cdrecord from the console, e.g. mondoarchive or direct > cdrecord commands. Here's the response from cdrecord --scanbus: > > # cdrecord --scanbus > cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open > SCSI driver. > cdrecord: For possible targets try 'cdrecord -scanbus'.
Post the output from:
cdrecord dev=ATA: -scanbus
Eric Gaumer
> > Check your CD/DVD drives using > > > > $>cdrecord -scanbus dev=ATAPI > > # cdrecord -scanbus dev=ATAPI > scsidev: 'ATAPI' > devname: 'ATAPI' > scsibus: -2 target: -2 lun: -2 > Warning: Using ATA Packet interface. > Warning: The related Linux kernel interface code seems to be unmaintained. > Warning: There is absolutely NO DMA, operations thus are slow. > Using libscg version 'schily-0.8'. > scsibus0: > 0,0,0 0) 'HL-DT-ST' 'RW/DVD GCC-4480B' 'C104' Removable CD-ROM > 0,1,0 1) * > 0,2,0 2) * > 0,3,0 3) * > 0,4,0 4) * > 0,5,0 5) * > 0,6,0 6) * > 0,7,0 7) * > # > > In KDE, the CDROM is device /dev/hde, NOT read-only, mount point > /media/cdrom0. > K3B works fine.
There you have it… use dev=ATAPI:0,0,0 in your cdrecord command.
Eric Gaumer
> > There you have it... use dev=ATAPI:0,0,0 in your cdrecord command. > > About this ATAPI interface. Anybody can give some comment on reliability > and speed? I read the following warning then switched to ide-scsi because > at least ide-scsi is actively maintained. I didn't want to hung onto a > dead-end module... > > > Warning: The related Linux kernel interface code seems to be unmaintained. > > Warning: There is absolutely NO DMA, operations thus are slow.
This is just Jorg trying to make everyone believe he knows more about kernels than Linus. The ATA interface is recommended over SCSI emulation by kernel developers. Search the kernel mailing list archives and you'll see pages of discussions about this. SCSI emulation is deprecated.
Eric Gaumer
http://forums.gentoo.org/viewtopic.php?t=71952
you don't need the scsi-modules to write a cd if you have an atapi cd writer then do the following
cdrecord dev=ATAPI:0,1,0 -checkdrive
the 0,1,0 can be something else according to your settings,
i get the following if i do this
Cdrecord 2.01a16 (i686-pc-linux-gnu) Copyright (C) 1995-2003 J\u9c0eg Schilling scsidev: 'ATAPI:0,1,0' devname: 'ATAPI' scsibus: 0 target: 1 lun: 0 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.7' Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'SAMSUNG ' Identifikation : 'CD-R/RW SW-240B ' Revision : 'R403' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-2 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R
then i start
gcombust
and the go to Burn and change the following settings below
Device: ATAPI:0,1,0 Driver: mmc_cdr
you can know what drive driver to use when u do the cdrecord stuff
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Last edited by PoLiPiE on Mon Sep 15, 2003
To add a tip for those more console oriented:
I found it useful to make a script that I use for burning iso files created with mkisofs:
#!/bin/bash cdrecord dev=ATAPI:0,0,0 driveropts=burnfree speed=12 -v -data $*
Put this in your path (/usr/local/bin, perhaps) and you can call it, for example, with "burn-image myimage.iso". It saves alot of time for typing all the options, but is completely unneccessary if you are using gcombust as instructed (and encouraged) above.
Chris I
> wait wait, does this mean i could burn CDs without having this scsi > emulation stuff in my kernel? grub also has an option that says > ide-scsi=/dev/hdc or something. my cdr seems to be on ATAPI:0,0,0 > (dev/hdc). would be cool if i could remove all this scsi stuff from the > kernel.
Yes, you need no scsi emulation and no grub modifications anymore. I have both K3b and Xcdroast working. K3b is very nice, but I can't dup cd's with it yet on my laptop since it only has one drive. I have to use Xcdroast for that.
> I was just wondering, a few months back ATAPI burning was still in alpha > status (and was really slow). Has this improved or should i wait a while > longer before i drop all the scsi emulation?
I haven't noticed any problems with speed. However, my laptop has a combo DVD/CDRW drive which is pretty slow to begin with. It's pretty easy to setup SCSI emulation so if that's already working, just go with it. For a new setup, I'd try ATAPI burning first though. I'm a firm believer in, "if it ain't broke, don't fix it."
The reason I started experimenting with ATAPI was that I had a problem with my burner where it would not read audio CDs well through SCSI emulation. By removing SCSI and going to straight ATAPI. it fixed it right up.
I would be interested in some comparisons between burning speed if anyone can supply them.
$ cdrecord dev=ATAPI:0,1,0 -checkdrive
Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jorg Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to <cdrtools@packages.debian.org>.
The original author should not be bothered with problems of this version.
scsidev: 'ATAPI:0,1,0' devname: 'ATAPI' scsibus: 0 target: 1 lun: 0 Warning: Using ATA Packet interface. Warning: The related Linux kernel interface code seems to be unmaintained. Warning: There is absolutely NO DMA, operations thus are slow. cdrecord: ERROR: unknow subsystem (scd0) in (/dev/sr0) [...] cdrecord: ERROR: unknow subsystem (scd13) in (/dev/sr13) cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. cdrecord: cdrecord: For more information, install the cdrtools-doc cdrecord: package and read /usr/share/doc/cdrecord/README.ATAPI.setup .
K3b detects my ATAPI DVD/CDRW and writes to it perfectly. No configuration was necessary. I had problems with .8.1, but .9 is running great!
ScubaStreb
xcdroast auto-detected and configured my ATAPI burner without issue, and in my opinion has a cleaner interface than gcombust. xcdroast also includes a wrapper that allows non-rooted users to burn CDs, which is quite nice.
DanWSB
A graphical front end for cdrecord and mkisofs that makes data, music and .iso file burning easy. Built on QT for KDE. K3b has a very user friendly interface and is the most similar to Roxio Easy Cd Creator that I've seen so far in Linux. K3b has drag-n-drop support, supports "BurnProof" and "overburning". K3b now has right click intergration in KDE 3.1.
A graphical front end for cdrecord and mkisofs that makes data, music and .iso file burning easy. Eroaster has a user friendly interface with many configuration options. Supports "BurnProof", "overburning", drag-n-drop and sound level normalization for burning music files.
documented on: 2004.09.15
Newsgroups: comp.os.linux.setup Date: 24 Feb 2003 04:30:10 GMT
> I want to be able to burn/rip CDs as a non-root user but I get this error: > > cdrecord: Permission denied. Cannot open '/dev/sg0'. Cannot open SCSI > driver.
An easy way around this is to create a "cdwriters" group chgrp cdwriters & chmod g+rw the appropriate enteries in /dev
Joel Mayes