All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub.elf? As in "How do I create that?"
Date: Wed, 12 Nov 2008 08:57:26 +0100	[thread overview]
Message-ID: <20081112075726.GA24075@thorin> (raw)
In-Reply-To: <30AC019EF05045F0AD1A52918F8BFC7A@who8>

On Wed, Nov 12, 2008 at 12:20:01AM -0500, Gregg C Levine wrote:
> Hello!
> I just managed to download the current subversion contents of what everyone
> is working on. The Grub2 trunk built perfectly, and with no complaints.
> 
> On the CoreBoot list there is news that the payloads of libpayload for
> example can be booted via Grub2, and indeed an example is given. It shows
> the booting of Grub2 booting this payload. It also shows the sequence of
> events to boot grub.elf via the command line for Grub-Legacy.
> 
> So, "How do I create that?".

Already replied on coreboot list :-)

> Of course I can cross post this to the help list if it is more appropriate.

Crossing grub-devel with other lists doesn't generally work well.  People tend
to complain that they can't post since they haven't subscribed.

-- 
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."



  reply	other threads:[~2008-11-12  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12  5:20 grub.elf? As in "How do I create that?" Gregg C Levine
2008-11-12  7:57 ` Robert Millan [this message]
2008-11-13  1:05   ` Gregg Levine
2008-11-22 19:58     ` Robert Millan
2008-11-23  2:33       ` Gregg Levine
2008-11-28 19:38         ` 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=20081112075726.GA24075@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.