cdrecord for Debian ---------------------- The author of cdrecord is Jörg Schilling and it was initally packaged for Debian by Erik Andersen . The Debian package includes few modifications: - /usr/bin/cdrecord is a shell script that automatically chooses the correct executable: * /usr/bin/cdrecord.shm, for Kernel 2.0.* and 2.2.*, using SHM method. * /usr/bin/cdrecord.mmap for Kernel >= 2.4. This is needed to make it work with all kernels versions in Debian, not depending on the build time version. - with default kernel configuration, cdrecord will fail with this message if you specify a fs= value larger than 31MiB: "cdrecord: Invalid argument. shmget failed." To fix this, change the value in /proc/sys/kernel/shmmax file. To set it permanently, add this line to /etc/sysctl.conf: kernel/shmmax = 33554432 - Per default the debian version of mkisofs does not include the commandline used to create the iso image in the image itself. To get this (for problem reports to Upstream) set the environment variable ISODEBUG to any value. If you are looking for a program for DVD-recording please take a look at README.DVD.Debian. If you want to report Bugs please read the following, taken from http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/problems.html (I refers to Joerg Schilling in this text). Please use only the recent version of cdrecord for bug-reports, it may be found on: ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/alpha. I don't have the time to check if your problem was recently fixed. For a list of the enhancements and bug fixes read the announcement files in the same directory. If you are using XCDroast, please first check the actual cdrecord version from command line to verify your bug. Please always include the following information in your bug-report: # The version number of cdrecord that caused the bug. # The command line that was used for the failing command. # The complete output (including error messages) from 'cdrecord -v ...' # Probably the important part of the 'cdrecord -V' output if we agreed on it # The OS name, release and hardware (processor) # Special conditions of your environment (libc vers. SCSI transport ...) # Sufficient information on the media used. This is at least the ATIP data, a note to CD-R/CD-RW and information on the state and the case history of this media. A message in the form: "Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found" is inaceptable as error report because I cannot see any reason why this message has been printed by cdrecord. For this reason, I would need the complete inquiry output to understand why this message was printed. Note that Linux is no Operating System, it is only a kernel. It does not help if you tell me: "I have RH-6.2". From this I know that you are using a buggy glibc-2.1.3 but I still don't know which Linux version you are using. The output from cdrecord -VVVVVV -vvvvvvv -debug is totally useless. It contains too much information to read it in an acceptable time. Try to write your mail in a way that the important information may be gathered in less than a minute. You then will have the best chance to get an answer that will help you with your problem. Please prepare your mail well and take care of my time. Top news Forums related to cdrecord: de.comp.periph.cdrom comp.os.linux.misc comp.os.linux.hardware It is always a good idea to first look at groups.google.com for your problem. If you are using Linux and get the error message: cdrecord: Cannot allocate memory. Cannot send SCSI cmd via ioctl then you have encountered a Linux kernel incompatibility. Recompile cdrecord and read README.linux from the current cdrecord alpha distribution. Please send a bug report to your Linux distributor too. Eduard Bloch , Mon, 26 Aug 2002 20:57:50 +0200 Joerg Jaspert , Mon, 18 Nov 2002 21:24:00 +0100