From: BandiPat <magicpage91@earthlink.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub2 svn2059
Date: Fri, 03 Apr 2009 08:19:01 -0400 [thread overview]
Message-ID: <49D5FEB5.2070902@earthlink.net> (raw)
In-Reply-To: <acc911d90904022217u3490cdb0g9d3143e08f697ba5@mail.gmail.com>
step21 wrote:
> Hey, just a wild guess, but I think boot.mod got dropped and the boot
> command is now included in minicmd.mod
> So maybe your build script needs to be adjusted for that, to copy that
> one to the right place? Not familiar with grub2 booting on i386/bios
> though anymore, so just a guess.
------------
This could be a very good guess on your part! Looking at the 2031
build, I see the boot.mod, but do not see that in the 2059 build. So
how should this be handled in the build? Add a symlink to minicmd.mod
with a boot.mod or something else. Shouldn't the new Grub2 know to look
at minicmd.mod instead of boot.mod?
I'll try with the symlink to test your theory, but this seems like a bug
to me, if that is the case?
...still testing
Pat
next prev parent reply other threads:[~2009-04-03 12:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 21:00 Grub2 svn2059 BandiPat
2009-04-02 22:19 ` Pavel Roskin
2009-04-03 4:15 ` BandiPat
2009-04-03 4:50 ` BandiPat
2009-04-03 5:17 ` step21
2009-04-03 12:19 ` BandiPat [this message]
2009-04-03 12:39 ` step21
2009-04-03 14:47 ` BandiPat
2009-04-03 18:44 ` Yoshinori K. Okuji
2009-04-03 19:02 ` BandiPat
2009-04-03 19:12 ` Yoshinori K. Okuji
2009-04-04 2:09 ` BandiPat
2009-04-04 10:53 ` phcoder
2009-04-04 12:50 ` BandiPat
2009-04-06 21:37 ` BandiPat
[not found] <49D7744B.4040708@googlemail.com>
2009-04-04 15:01 ` Andreas Born
2009-04-04 19:35 ` BandiPat
2009-04-05 13:56 ` Andreas Born
2009-04-06 3:27 ` BandiPat
2009-04-15 20:27 ` BandiPat
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=49D5FEB5.2070902@earthlink.net \
--to=magicpage91@earthlink.net \
--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.