On Tue, Jan 29, 2008 at 06:12:52AM +0100, Tristan Gingold wrote:
> > > --- grub2.orig/fs/fat.c 2007-08-02 20:40:36.000000000 +0200
> > > +++ grub2/fs/fat.c 2008-01-28 16:29:57.000000000 +0100
> > > @@ -568,7 +568,7 @@ grub_fat_find_dir (grub_disk_t disk, str
> > > continue;
> > > }
> > >
> > > - if (grub_strcmp (dirname, filename) == 0)
> > > + if (grub_strcasecmp (dirname, filename) == 0)
> > > {
> > > if (call_hook)
> > > hook (filename, dir.attr & GRUB_FAT_ATTR_DIRECTORY);
> > > @@ -601,7 +601,7 @@ grub_fat_find_dir (grub_disk_t disk, str
> > > if (hook (filename, dir.attr & GRUB_FAT_ATTR_DIRECTORY))
> > > break;
> > > }
> > > - else if (grub_strcmp (dirname, filename) == 0)
> > > + else if (grub_strcasecmp (dirname, filename) == 0)
> > > {
> > > if (call_hook)
> > > hook (filename, dir.attr & GRUB_FAT_ATTR_DIRECTORY);
> >
> > Why is this needed? I'm not sure if it's good to exploit this
> > "unreliability"
> > feature that fat provides us ;-)
>
> On EFI, the prefix is extracted from an EFI path, whose case may not match
> the FAT entries.
Can you be more specific about this? What do the specs say? We wrote
/boot/grub ourselves via grub-install; is an EFI-compliant firmware
allowed to actively mess up case in paths we provided?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
_______________________________________________
Grub-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/grub-devel
