From: Will Dyson <will_dyson@pobox.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: vcd, .dat files and isofs problem
Date: Thu, 04 Apr 2002 22:10:04 -0500 [thread overview]
Message-ID: <3CAD158C.3040301@pobox.com> (raw)
In-Reply-To: <E16tDuI-0006jc-00@the-village.bc.nu>
Alan Cox wrote:
>>I have problems reading the .dat files from VCD, here is the kernel
>>logs. I think it is an fs issue, since I am not the only one having the
>>same problem. In user space, read returns I/O error but I think it is an
>>fs issue or a cd-rom
Have a look at cdfs: http://www.elis.rug.ac.be/~ronsse/cdfs/
It will allow you to read those files. Of course, there are also userland
utilities for that. Just search freshmeat for vcd.
> VCD .dat files are not normal "files". They are encoded in a different mode
> to get more bytes/sector at the cost of lower error resistance (mpeg is
> error resistant in itself...)
I knew they were different, but not why. Learn something new every day.
--
Will Dyson
prev parent reply other threads:[~2002-04-05 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 20:04 vcd, .dat files and isofs problem David Chow
2002-04-04 20:32 ` Alan Cox
2002-04-05 3:10 ` Will Dyson [this message]
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=3CAD158C.3040301@pobox.com \
--to=will_dyson@pobox.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.