Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices

[Matthias Andree]

On Thu, 19 Aug 2004, Martin Mares wrote:

> That's really hard to believe, but on the other hand, when packaging
> my programs, SUSE people were always cooperating very well.

It depends on whom you talk to. The generic feedback ways don't work
well at all, 80% of issues are apparently dropped, no chance to query
status from the outside, and it takes ages until something happens.

> So, let's ask the SUSE'rs around there: is there any problem with adding such
> a notice to the cdrecord package?

Non-issue.  SuSE 9.1 PRO:

$ rpm -qf /usr/bin/cdrecord
cdrecord-2.01a27-21
$ /usr/bin/cdrecord -version
ZYï$: Operation not permitted. WARNING: Cannot set RR-scheduler
ZYï$: Permission denied. WARNING: Cannot set priority using setpriority().
ZYï$: WARNING: This causes a high risk for buffer underruns.
Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 JÃrg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://www.suse.de/feedback
Note: The author of cdrecord should not be bothered with problems in this version.

BTW:

$ /opt/schily/bin/cdrecord -version
Cdrecord-Clone 2.01a37 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jïrg Schilling
/opt/schily/bin/cdrecord: Warning: Running on Linux-2.6.8.1
/opt/schily/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer.
/opt/schily/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.

I read the discussion as though these issues had been settled with
Linux 2.6.8. Is 2.01a37 too old to be aware of the fix or is there an
issue left with finding the "right" header files?

-- 
Matthias Andree

Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/