strange iso9660 bug

strange iso9660 bug

[Robert Millan]

Hi,

I was having a look at this iso9660 image:

  http://syllable.info/Syllable-0.6.4-LiveCD-1.1.iso.bz2

and GRUB seems to behave strangely with it.  When its contents are listed by
Linux, GRUB Legacy or isoinfo, you get a long list (the "real" data), but
when they're listed by GRUB 2, you get a short list with only 3 files:

  - autorun.inf
  - some *.ico file
  - readme.txt

which are obviously aimed at MS-Windows users.

I wonder if someone more knowledgeable than me about iso9660 has a clue on
what's going on.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

Re: strange iso9660 bug

[Urja Rannikko]

On Sun, Sep 28, 2008 at 11:08 PM, Robert Millan <rmh@aybabtu.com> wrote:
>
> Hi,
>
> I was having a look at this iso9660 image:
>
>  http://syllable.info/Syllable-0.6.4-LiveCD-1.1.iso.bz2
>
> and GRUB seems to behave strangely with it.  When its contents are listed by
> Linux, GRUB Legacy or isoinfo, you get a long list (the "real" data), but
> when they're listed by GRUB 2, you get a short list with only 3 files:
>
>  - autorun.inf
>  - some *.ico file
>  - readme.txt
>

One gets those for windows files in linux by doing:
mount -o loop,norock -t iso9660 /tmp/syllable.iso /mnt/loop
(that was my command line, YMMV)

So i think that you need to support rockridge extensions to see the
for linux content.

-- 
urjaman

Re: strange iso9660 bug

[Robert Millan]

On Mon, Sep 29, 2008 at 11:31:29AM +0300, Urja Rannikko wrote:
> On Sun, Sep 28, 2008 at 11:08 PM, Robert Millan <rmh@aybabtu.com> wrote:
> >
> > Hi,
> >
> > I was having a look at this iso9660 image:
> >
> >  http://syllable.info/Syllable-0.6.4-LiveCD-1.1.iso.bz2
> >
> > and GRUB seems to behave strangely with it.  When its contents are listed by
> > Linux, GRUB Legacy or isoinfo, you get a long list (the "real" data), but
> > when they're listed by GRUB 2, you get a short list with only 3 files:
> >
> >  - autorun.inf
> >  - some *.ico file
> >  - readme.txt
> >
> 
> One gets those for windows files in linux by doing:
> mount -o loop,norock -t iso9660 /tmp/syllable.iso /mnt/loop
> (that was my command line, YMMV)
> 
> So i think that you need to support rockridge extensions to see the
> for linux content.

Yup, that was it.

So anyone feels like hacking rockridge?  :-)

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

Re: strange iso9660 bug

[Bean]

On Mon, Sep 29, 2008 at 11:07 PM, Robert Millan <rmh@aybabtu.com> wrote:
> On Mon, Sep 29, 2008 at 11:31:29AM +0300, Urja Rannikko wrote:
>> On Sun, Sep 28, 2008 at 11:08 PM, Robert Millan <rmh@aybabtu.com> wrote:
>> >
>> > Hi,
>> >
>> > I was having a look at this iso9660 image:
>> >
>> >  http://syllable.info/Syllable-0.6.4-LiveCD-1.1.iso.bz2
>> >
>> > and GRUB seems to behave strangely with it.  When its contents are listed by
>> > Linux, GRUB Legacy or isoinfo, you get a long list (the "real" data), but
>> > when they're listed by GRUB 2, you get a short list with only 3 files:
>> >
>> >  - autorun.inf
>> >  - some *.ico file
>> >  - readme.txt
>> >
>>
>> One gets those for windows files in linux by doing:
>> mount -o loop,norock -t iso9660 /tmp/syllable.iso /mnt/loop
>> (that was my command line, YMMV)
>>
>> So i think that you need to support rockridge extensions to see the
>> for linux content.
>
> Yup, that was it.
>
> So anyone feels like hacking rockridge?  :-)

Hi,

Rockridge is supported in iso9660. However, the image file has three
namespaces, iso9660, joliet and rockridge. Currently, the priority is:

joliet > rockridge > iso9660

So only files in joliet is showed.

It's possible to change priority, but what if we need to access files
in the other namespace ? Perhaps we can control it with variables, for
example: disable_joliet, disable_rockridge, etc.


-- 
Bean

Re: strange iso9660 bug

[Robert Millan]

On Tue, Sep 30, 2008 at 01:15:21AM +0800, Bean wrote:
> 
> Hi,
> 
> Rockridge is supported in iso9660. However, the image file has three
> namespaces, iso9660, joliet and rockridge. Currently, the priority is:
> 
> joliet > rockridge > iso9660
> 
> So only files in joliet is showed.
> 
> It's possible to change priority, but what if we need to access files
> in the other namespace ? Perhaps we can control it with variables, for
> example: disable_joliet, disable_rockridge, etc.

Sounds fine to me.  But I'd also change the default priorities so that they
match with those in isoinfo, linux, grub legacy, etc.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."