All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Douglas Morris <dougbmorris@yahoo.com>,
	Bruce Dubbs <bruce.dubbs@gmail.com>
Subject: Re: [Fwd: GRUB 1.99 Documentation Observation]
Date: Wed, 21 Dec 2011 11:47:00 +0100	[thread overview]
Message-ID: <4EF1B924.60906@gmail.com> (raw)
In-Reply-To: <4EF0EC46.3080802@gmail.com>

On 20.12.2011 21:12, Bruce Dubbs wrote:
> Forwarding.
>   -- Bruce
>
> -------- Original Message --------
> Subject: GRUB 1.99 Documentation Observation
> Date: Tue, 20 Dec 2011 11:55:54 -0800 (PST)
> From: Douglas Morris <dougbmorris@yahoo.com>
> Reply-To: Douglas Morris <dougbmorris@yahoo.com>
>
>
> Thanks for your work on documenting grub which I plan to use with my 
> installation of GNU/Linux. I have a comment on the GRUB documentation 
> posted online for version 1.99.
>
> 3.4 BIOS Installation, MBR section says: "there are two ways to 
> install GRUB: it can be
> embedded in the area between the MBR and the first partition (...), or 
> the core image can be installed in a
> file system and a list of the blocks that make it up can be stored in the
> first sector of that partition."
>
> However, when I look at 3.1 Installing GRUB using grub-install, there 
> is no explanation about where the 'core image' is installed or how its 
> placement is controlled.
>
The best suitable placement is automatically determined. Block-lists are 
only a fallback if mbr gap is unavailable and should be avoided due to 
reliability and security problems.
> My observation comes from trying to find out if I can boot GRUB if I 
> 'install' it in a /boot logical partition on an MBR harddrive.
As long as you install to MBR and not to partition it's fine.
> I will just try it not knowing the particulars and see what happens. I 
> can always start over using Clonezilla, which seems to have worked for 
> me once. 
You need to reinstall bootloader after cloning in any case
> It seems that OEM Windows 7 installed in an MBR format will not adapt 
> to the GPT format and I am not paying for MS installation CDs. So no 
> GPT for me. 
Microsoft misinforms you that you need EFI to boot on GPT.
> Happy Holidays and any religious salutations suitable to your 
> self-identity.
>

> Doug Morris
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



      reply	other threads:[~2011-12-21 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 20:12 [Fwd: GRUB 1.99 Documentation Observation] Bruce Dubbs
2011-12-21 10:47 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=4EF1B924.60906@gmail.com \
    --to=phcoder@gmail.com \
    --cc=bruce.dubbs@gmail.com \
    --cc=dougbmorris@yahoo.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.