mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: wixor <wixorpeek@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VCD not readable under 2.6.18
Date: Thu, 19 Oct 2006 18:35:56 +0200	[thread overview]
Message-ID: <c43b2e150610190935tefd11eev510c7dee36c15a51@mail.gmail.com> (raw)
In-Reply-To: <1161124732.5014.20.camel@localhost.localdomain>

On 10/18/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Now where it all gets weirder is that some forms of VCD (especially the
> ones for philips short lived interactive stuff) have an ISO file system
> on them but where sector numbers in the file system for video blocks
> point to blocks that are not 2K data blocks but mpeg blocks that the
> file system layer can't handle, so a VCD disk can appear mountable and
> the like.
OK, but this is still mountable only from windows....... Is this ISO
filesystem hidden somewhere, or what? And that still does not explain
errors from xine, and the 8 megs that i actually can read using dd.
All after all - even if this disc would contain totally unsupported
tracks, with absolutly weird data, kernel should recognize it and
report something like:
cdrom: there are no tracks on hda i can recognize
(or something like that). If the errors do happen, it means kernel
thinks he can read the data, and he actually can't, yes? Is here
anything I can do to improve support of this disc under linux, or is
this just another hell-knows-what thing, the kernel implementation is
ok, and this is only some m$-dontated extension that prevents us from
accessing this disc? Even if it is, shouldn't it be implemented if it
is possible?

Thanks
--
wixor

  parent reply	other threads:[~2006-10-19 16:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 18:53 wixor
2006-10-16 23:12 ` Alan Cox
2006-10-17 18:16   ` wixor
2006-10-17 22:38     ` Alan Cox
2006-10-17 22:21       ` Prakash Punnoor
2006-10-17 22:45       ` Olivier Galibert
2006-10-19 16:35       ` wixor [this message]
2006-10-19 16:42         ` Alan Cox
2006-10-19 17:39           ` wixor
2006-10-20 13:05             ` Alan Cox
2006-10-24 16:06               ` wixor
2006-10-29 19:23               ` S.Çağlar Onur
2006-12-09  6:06 Rakhesh Sasidharan
2006-12-09  8:14 ` Ismail Donmez
2006-12-09 13:21 ` Alan
2006-12-09 14:15   ` Ismail Donmez
2006-12-09 14:36     ` Alan
2006-12-09 14:31       ` Ismail Donmez
2006-12-09 16:09     ` S.Çağlar Onur
2006-12-09  8:48 Rakhesh Sasidharan
2006-12-09 13:33 Rakhesh Sasidharan
2006-12-09 17:23 Rakhesh Sasidharan
2006-12-09 19:46 ` Bill Davidsen
2006-12-10  0:50   ` Alan
2006-12-09 23:19 ` S.Çağlar Onur
2006-12-10  0:44 ` Alan
2006-12-10  4:27 Rakhesh Sasidharan
2006-12-10  4:33 Rakhesh Sasidharan
2006-12-11 17:58 Rakhesh Sasidharan
2006-12-12 19:21 Rakhesh Sasidharan

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=c43b2e150610190935tefd11eev510c7dee36c15a51@mail.gmail.com \
    --to=wixorpeek@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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®