Date: Tue, 27 Nov 2001 09:06:48 +0100 (CET) From: Christoph Herrmann <C.Herrmann@science-computing.de> To: "Kenneth D. Merry" <ken@kdm.org> Cc: Christoph Herrmann <C.Herrmann@science-computing.de>, current@FreeBSD.ORG Subject: Re: cdrecord produces broken CDs on -CURRENT Message-ID: <Pine.BSF.4.21.0111270837240.49965-100000@scmsrv1.science-computing.de> In-Reply-To: <20011126133027.A5112@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Nov 2001, Kenneth D. Merry wrote:
> So did you try the statically linked -stable binary on -current?
Yes, I used the newest version from the ports (compiled on -CURRENT) and
the staticly linked from -STABLE both on -CURRENT, and the CDs are
identical.
> Is it completely static? (i.e. ldd cdrecord should report that it isn't a
> dynamic executable)
Yes it is.
> That may help narrow the problem down somewhat. I'm not sure, though,
> whether the -stable binary will work with the pass interface on -current.
It doesn't matter wether I take cdrecord from -CURRENT or from -STABLE,
the CDs (I burn on -CURRENT) are identical.
> Are there any areas with good data on the CD? i.e. can you see any pattern
> to the corruption? If you compare the same CD burned from -current and
> -stable you might begin to see a patern.
Yes, about half of the CD is correct, and the rest is filled up with
binary zero. If there are data other then zero on the CD, then they are
correct.
> Is the table of contents correct?
I don't know, but I don't think so. The first 60kB (exact 60kB!) of the
broken CD are zeros, and I can't mount it.
> Ken
> --
> Kenneth Merry
> ken@kdm.org
>
Ciao
Christoph &:-)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0111270837240.49965-100000>