From: "Hitoshi Ozeki" <h-ozeki@ck2.so-net.ne.jp>
To: "'The development of GRUB 2'" <grub-devel@gnu.org>
Subject: RE: i386-pc 'chainloader' is something wrong. (RE: I write a patch forJapanese NEC i386 old computers.)
Date: Sat, 31 Mar 2007 13:24:07 +0900 [thread overview]
Message-ID: <000001c7734c$6f105ac0$030010ac@temjin> (raw)
In-Reply-To: <000001c772ae$a4fa46d0$030010ac@temjin>
Hello,
I wrote:
> Please see 'grub-1.96/loader/i386/pc/chainloader.c' and
> 'grub-1.96/kern/loader.c'
>
> When we execute the 'boot' command, process the 'grub_loader_boot()'
(omit it)
To sum up, On 'chainloader' of i386-pc,
However 'grub_loader_boot()' executes 'grub_device_open()', it will fail
always.
But 'grub_loader_boot()' do it.
If this behavior is wrong, we do only fix it.
What I wish to know is which is the boot drive.
1. 'root' environment indicates it.
2. argument of 'chainloader' command indicates it.
For example:
grub> set root=hd0,1
grub> chainloader (hd0,2)0+2
grub> boot
If the 1st is, boot from (hd0,1) and bootloader is (hd0,2)0+2.
If the 2nd is, boot from (hd0,2) and bootloader is (hd0,2)0+2.
...Aha! EFI looks to choose 1st. Should I obey it?
next prev parent reply other threads:[~2007-03-31 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 6:33 I write a patch for Japanese NEC i386 old computers Ernest Sales
2007-03-28 15:27 ` Hitoshi Ozeki
2007-03-28 19:25 ` Yoshinori K. Okuji
2007-03-30 9:34 ` i386-pc 'chainloader' is something wrong. (RE: I write a patch for Japanese NEC i386 old computers.) Hitoshi Ozeki
2007-03-31 4:24 ` Hitoshi Ozeki [this message]
2007-04-07 13:13 ` i386-pc 'chainloader' is something wrong. (RE: I write a patch forJapanese " Yoshinori K. Okuji
2007-09-03 20:27 ` i386-pc 'chainloader' is something wrong. (RE: I write a patch for Japanese " Yoshinori K. Okuji
2007-04-10 18:56 ` I write a patch for Japanese NEC i386 old computers Hitoshi Ozeki
2007-04-13 10:57 ` Hitoshi Ozeki
2007-04-13 11:12 ` Vesa Jääskeläinen
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='000001c7734c$6f105ac0$030010ac@temjin' \
--to=h-ozeki@ck2.so-net.ne.jp \
--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.