Hello again Joerg,
> I think you meant "/dev/sgX"?
No, I mean /dev/scg*. [...] I expect that the users
are clever enough to replace this with their local name.
No, we're not. Users do not know what a SCSI generic passthrough is.
We know that most things in /dev are somehow connected to hardware
devices, but that's about all we know... and for many people, that's
all they *want* to know.
I cannot modify the man page for every OS.
You could list the names of the device nodes on the various platforms
that cdrecord supports. I can't see any reason why this would be
impossible, or even difficult.
For many users, this would save a lot of time and frustration, e.g.
trying to understand why they don't have device nodes called "scg".
> you want to
> prevent the OS from swapping cdrecord to disk, which would cause a
> buffer underrun. I really doubt that will happen on my system.
I know that it is needed, that's the difference.
> The manpage also mentions the need to run at the highest priority --
> also presumably to avoid buffer underruns.
Cdrecord needs this. CD/DVD writing is a real-time process.
Provisions like this allowed me to write CDs on a very slow PC, many
years ago. But on a new, fast, lightly-loaded system, they are likely
unnecessary.
If cdrecord fails to enable these things, it should emit a warning,
and continue running. Then, if I get a coaster because I have ignored
the warning, it is my fault.
Some newer drives may have workarounds but then the quality of the
media is not the same as it would be when writing uninterrupted.
Yes, I agree, burn-free and the like are not desirable, especially for
audio discs. It is good that cdrecord turns these features off by
default!
The Debian version is junk as it introduces Bugs that are not present in the
original. Also the Debian maintainers are unwilling to cooperate :-(
Would you stop the gratuitous mud-slinging? It's not helpful to anyone.
AFAICT, this bug was not caused by the Debian maintainers, so you
cannot blame them for it. Correct me if I'm wrong.
But your main Proplem was caused by the fact that you ignore the official
documentation.
No. I read the documentation. I simply disagree with the requirement
that cdrecord must be run as root.
-- graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]