From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: strange iso9660 bug
Date: Mon, 29 Sep 2008 17:07:39 +0200 [thread overview]
Message-ID: <20080929150739.GC12979@thorin> (raw)
In-Reply-To: <460f92b70809290131g5f1ffb7rc1bb32589ea971a8@mail.gmail.com>
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."
next prev parent reply other threads:[~2008-09-29 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 20:08 strange iso9660 bug Robert Millan
2008-09-29 8:31 ` Urja Rannikko
2008-09-29 15:07 ` Robert Millan [this message]
2008-09-29 17:15 ` Bean
2008-10-05 10:56 ` Robert Millan
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=20080929150739.GC12979@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.