> Does not work does not help... Yes, I am well aware of that, which is why I asked: [I]which information do you need to diagnose potential problem(s)?[/I] (Please read below...)
> How do you expect help if you don't enlighten us > about your problems? I do not. "Does not work" does not help, I agree; but I needed to know which information you need and how you want it generated, and I've extracted the requirements for a bug report from the link you gave. > It would help if you describe your problems. > > http://cdrecord.berlios.de/old/private/problems.html OK. So you need: "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." I will generate the output for you with the above information as soon as time allows (probably tonight, if I manage scrape some time). This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
