All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: More trials with grub
Date: Thu, 28 May 2009 14:07:54 -0400	[thread overview]
Message-ID: <1243534074.21408.9.camel@mj> (raw)
In-Reply-To: <4A1D48C7.5090407@ed.ac.uk>

On Wed, 2009-05-27 at 15:05 +0100, James Jarvis wrote:
> Conscious that I am not a developer but it is useful to get feedback on 
> the project I have outlined progress mad so far with * to indicate 
> questions/discussion points.
> 
> I have been building a fat grub2 (using the fatglue.py script from rEFIT 
> project) to use on Intel Macs (mac mini; iMac 8,1; iMac 9,1 etc). This 
> works on both 32 and 64 bits architectures. Because the modules don't 
> work as fat files I tend to use a monolithic grub image. (FWIW, the idea 
> is to have a utility boot CD to pass out to our field operators.)
> 
> * Is there mileage in having the modules (when insertion is attempted to 
> not only try to insert <modpath>/name.mod but also <modpath>/name.<arch>.mod

It would be better to use different directories for different modules an
adjust prefix accordingly.

> Incidentally I have checked that I can insert the non-fat modules from 
> the fat grub2 monolithic image.
> 
> I have managed to have it boot from CD but it always chokes when trying 
> to find the grub.cfg on the CD - even though I have the required 
> filesystems in the monolithic grub image.

I believe it was caused by a bug in hfs filesystem that I have just
fixed.  With prefix ending with a slash, GRUB would add "/grub.cfg" and
the double slash would confuse hfs.

-- 
Regards,
Pavel Roskin



      reply	other threads:[~2009-05-28 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 14:05 More trials with grub James Jarvis
2009-05-28 18:07 ` Pavel Roskin [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=1243534074.21408.9.camel@mj \
    --to=proski@gnu.org \
    --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.