All of lore.kernel.org
 help / color / mirror / Atom feed
From: edgar.soldin@web.de
To: Bean <bean123ch@gmail.com>,
	 The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Is it possible to have grub2's boot.img as my MBR, but have it look in a separate partition for core.img?
Date: Thu, 28 Jan 2010 18:15:33 +0100	[thread overview]
Message-ID: <4B61C635.7000503@web.de> (raw)
In-Reply-To: <ca0f59981001280857p5f581035n4cd8519efda30e8@mail.gmail.com>

So grubinst bootcode seems superior over grub2 bootcode regarding 
partitions?

ede

On 28.01.2010 17:57, Bean wrote:
> On Fri, Jan 29, 2010 at 12:39 AM,<edgar.soldin@web.de>  wrote:
>    
>> I am pretty sure. If you want I am willing to retry.
>>
>> Still I wonder what is the deifference to the grubinst/g2ldr approach and
>> why the boot code can find g2ldr. Can it read fat fs?
>>      
> Hi,
>
> Yeah, grubinst contains its own fs reader, it's all written in
> assembly, 1 sector fat + 1 sector ext2 + 4 sector ntfs plus other
> utilities. The whole size is about 8K.
>
>
>    




  parent reply	other threads:[~2010-01-28 17:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28  3:37 Is it possible to have grub2's boot.img as my MBR, but have it look in a separate partition for core.img? Wesley Smith
2010-01-28 11:45 ` Colin Watson
2010-01-28 14:11   ` edgar.soldin
2010-01-28 14:55     ` Colin Watson
2010-01-28 16:39       ` edgar.soldin
     [not found]         ` <ca0f59981001280857p5f581035n4cd8519efda30e8@mail.gmail.com>
2010-01-28 17:15           ` edgar.soldin [this message]
     [not found]             ` <ca0f59981001280936o4457ff96wc95dad6f238ff461@mail.gmail.com>
2010-01-28 17:41               ` edgar.soldin
2010-01-29  5:43   ` Wesley Smith
2010-01-29  6:19     ` Bruce Dubbs
2010-01-29  9:54       ` Wesley Smith
2010-01-29  9:48     ` Grégoire Sutre

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=4B61C635.7000503@web.de \
    --to=edgar.soldin@web.de \
    --cc=bean123ch@gmail.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.