From: BandiPat <magicpage91@earthlink.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub2 svn2059
Date: Mon, 06 Apr 2009 17:37:17 -0400 [thread overview]
Message-ID: <49DA760D.8090901@earthlink.net> (raw)
In-Reply-To: <200904040412.43072.okuji@enbug.org>
Yoshinori K. Okuji wrote:
> On Saturday 04 April 2009 04:02:18 BandiPat wrote:
>> Yoshinori K. Okuji wrote:
>>> On Friday 03 April 2009 14:17:04 step21 wrote:
>>>> Hey, just a wild guess, but I think boot.mod got dropped and the boot
>>>> command is now included in minicmd.mod
>>> Yes, it seems so. And, it is a mistake that boot and some other commands
>>> are not built into the kernel. We must reduce modules, and let them back
>>> to the kernel.
>>>
>>> Regards,
>>> Okuji
>> -----------
>> In the meantime, how do we get the new svn to work then? Is there some
>> trick or something in the compile we need to do? Presently I'm using
>> svn2031 successfully.
>
> I guess you just have some outdated files. As "make" depends on timestamps,
> checking out from any kind of version control system can confuse "make".
> Try "make clean all".
>
> Regards,
> Okuji
______________________________________________
Well, devs, I am making some advancements with the new svn versions. I
just did a brand new fresh install to a test computer which had LILO
installed as default. I first installed svn2059 for testing, which
worked! I then did an upgrade to svn2065 afterwards, ran the
grub-install command to replace all the files in /boot/grub.
Each time I've run or re-run grub-install though, I get this error.
grub-setup: error: cannot read '/boot/grub/core.img' correctly
Someone enlighten me as to what might be causing that? Otherwise,
things are looking favorable for Grub2 being okay, but I'm not letting
you devs off until I do a bit more testing. :-)
Regards,
Pat
next prev parent reply other threads:[~2009-04-06 21:37 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
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 [this message]
[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=49DA760D.8090901@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.