Re: CD DVD drive docs

[doark@mail.com]

Forgive my absence, my internet connection is intermittent.
I tried to contact the kernel devs, no luck so far. It was nice of you
to recommend using the digests, but then I can't reply.
I tried signing up and got the same reply as before

"5.7.1 Hello [74.208.4.201], for your MAIL FROM address
<doark@mail.com> policy analysis reported: Your address is not liked
source for email"

I read the FAQ and it says that they block email addresses in bulk no
matter who or what they are (html/asci/rfc/etc). I'll sign up for
different services and see if I can get through. Worst case scenario, I
set up my own temporary email server and sign up for the digests.

Also, should I get a copy of the various coloured books? Orange, Red,
etc?

On Sat, 22 Aug 2015 14:45:13 +0000 (UTC) "Thomas Schmitt" wrote:
> This led to an interesting private discussion with Ted T'so
> which finally yielded that there is indeed no reliable
> method in Linux to force exclusive access to a burner drive.
> No lock function and no open(2) flag is really safe.
This sounds like bug could you forward or in some way enlighten me as
to the facts behind this conclusion?

I've been bitten by this, or so I suspect. I always thought that it was
due to the MBs bus being saturated and so the RT wodim burn task was
put on hold as a necessity. This occurs independent of media, drive or
kernel (2.26.X, 3.X.X,I have not tried 4.X.X) though it manifests much
more frequently at higher speeds. As a result, I have to leave my
computer while it burns because it can't stand another task running
and set the speed for DVD to 4x and CD to 10x. The only error, is that
some drives info is in an "orange forum", or some such thing, that costs
money to get info from.

Well, I think I'm at the end of what I can do on this end, I'll play
the part of the hydra. I'll hunt this bug down. Don't expect to have
this fixed tomorrow though, as I said several posts ago, I'm new to
optical media drive tech and though I've always wanted to, I never
looked into the kernel's source. When I have something solid I'll hit
them with it (so to speak).

Thanks, David