Re: cdrecord exit status 254

2003-01-30 Thread Jason Pepas
> UTSL. It looks to me like cdrecord exits with -2 (which is 254 as an > unsigned char IIRC) when there are non-fatal errors. UTSL - good idea. why didn't I think of that? :) (pts/8)root@marsala:/tmp/cdrtools-2.0/cdrecord$ grep -i return * | grep "\-2" (pts/8)root@marsala:/tmp/cdrtools-2.0/cdre

Re: cdrecord exit status 254

2003-01-30 Thread Nathan E Norman
On Wed, Jan 29, 2003 at 07:28:56PM -0600, Jason Pepas wrote: > > You know that without knowing anything about your cdrecord > > (pts/8)jason@marsala:~$ dpkg -l | grep cdrecord > ii cdrecord 1.10+11a34-1 A command line CD/DVD writing tool > > > or Debian version > > (pts/8)jason@marsala:

Re: cdrecord exit status 254

2003-01-29 Thread Jason Pepas
> You know that without knowing anything about your cdrecord (pts/8)jason@marsala:~$ dpkg -l | grep cdrecord ii cdrecord 1.10+11a34-1 A command line CD/DVD writing tool > or Debian version (pts/8)jason@marsala:~$ cat /etc/debian_version testing/unstable > without knowing what you are

Re: cdrecord exit status 254

2003-01-29 Thread Eduard Bloch
#include * Jason Pepas [Wed, Jan 29 2003, 03:28:25PM]: > cdrecord appears to exit with status 254, which works fine from console, and > burns good cd's, but causes make to think it failed, when it actually didn't. > > ideas? You know that without knowing anything about your cdrecord or Debian v