From: Bradley Reed <bradreed1@gmail.com>
To: "Bernd Schubert" <Bernd.Schubert@tc.pci.uni-heidelberg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CDR read problems with 2.6.11?
Date: Thu, 14 Apr 2005 02:16:43 +0200 [thread overview]
Message-ID: <20050414021643.4d72618f@galactus.localdomain> (raw)
In-Reply-To: <20050414000307.GA15733@tc.pci.uni-heidelberg.de>
On Thu, 14 Apr 2005 02:03:07 +0200
"Bernd Schubert" <Bernd.Schubert@tc.pci.uni-heidelberg.de> wrote:
> I have seen exactly the same on my fathers computer and could solve this
> by not starting the udftools. Didn't have the time to digg further into
> this...
> Can you confirm thats really a udf problem? Just run
> "/etc/init.d/udftools stop" or the similar for your distribution and try
> mounting again.
>
I am not running udftools. In fact it isn't even installed (not part of
Slackware 10.1). I'm trying to burn an iso9660 on a CDR using cdrecord.
There seems to be issues with CD burning under 2.6.11. I make an iso, and I
burn it to CDR with 2.6.11 and again with 2.4.28 on the same laptop/same DVD
+RW drive. The disk burnt under 2.4 is fine, md5sums all ok, can be read
under both kernels. The disk burnt under 2.6.11 burns without error from
cdrecord/k3b/etc, but afterwards is not readable under 2.6.11. It is readable
under 2.4.28, but the md5sums are not 100% correct, basically making 2.6.11
useless for making backups to CDR.
Brad
next prev parent reply other threads:[~2005-04-14 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 23:36 Bradley Reed
2005-04-14 0:03 ` Bernd Schubert
2005-04-14 0:16 ` Bradley Reed [this message]
2005-04-23 12:52 ` Jan Knutar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050414021643.4d72618f@galactus.localdomain \
--to=bradreed1@gmail.com \
--cc=Bernd.Schubert@tc.pci.uni-heidelberg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®