All of lore.kernel.org
 help / color / mirror / Atom feed
* More trials with grub
@ 2009-05-27 14:05 James Jarvis
  2009-05-28 18:07 ` Pavel Roskin
  0 siblings, 1 reply; 2+ messages in thread
From: James Jarvis @ 2009-05-27 14:05 UTC (permalink / raw)
  To: grub-devel

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

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 see in the README CD support 
is not there yet however if someone has that working, tips would be 
appreciated.

Thanks for a great product,

James

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: More trials with grub
  2009-05-27 14:05 More trials with grub James Jarvis
@ 2009-05-28 18:07 ` Pavel Roskin
  0 siblings, 0 replies; 2+ messages in thread
From: Pavel Roskin @ 2009-05-28 18:07 UTC (permalink / raw)
  To: The development of GRUB 2

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-05-28 18:08 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-27 14:05 More trials with grub James Jarvis
2009-05-28 18:07 ` Pavel Roskin

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.