grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Mads Kiilerich <mads@kiilerich.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Subject: Re: [PATCH, RFC, RFT] Mactel integration
Date: Mon, 28 Nov 2011 15:27:37 +0100	[thread overview]
Message-ID: <4ED39A59.20503@kiilerich.com> (raw)
In-Reply-To: <4ED38BC0.6090100@gmail.com>

On 11/28/2011 02:25 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello all. Based on the information from
> http://mjg59.dreamwidth.org/7468.html I intend to add support for such
> install. It requires a small HFS+ volume mounted at /boot/mactel. I also
> simplify handling of EFI directories by adding explicit option to
> specify it and removing some "compatibility" kludges (they don't make
> anything compatible with anything since "old behaviour" was mostly not
> to install at all) which made the code in question difficult to
> maintain.

Matthew will perhaps give a more thorough response, but I would like to 
add a few quick comments.

Matthew also created http://www.codon.org.uk/~mjg59/mactel-boot/ , so 
there seems to be some duplicate work there.

His approach is discussed further on 
https://bugzilla.redhat.com/show_bug.cgi?id=755093 .

A quick summary is that it (in my opinion) is a bit unclear what Macs 
_really_ needs. There are several ways grub can be used to boot Macs, 
and it is not completely clear whether HFS blessing or HFS is necessary 
at all. The Mac boot loader detects FAT partitions and will by default 
also boot from /EFI/BOOT - also on the system partition. The OS/X 
"Startup Drive" configuration is a bit more sensitive, but it seems like 
what it writes to PRAM/VRAM is more important than the HFS blessing.

/Mads


  reply	other threads:[~2011-11-28 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 13:25 [PATCH, RFC, RFT] Mactel integration Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-28 14:27 ` Mads Kiilerich [this message]
2011-11-28 14:50   ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-28 22:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-28 22:29   ` Seth Goldberg
2011-11-29  6:34   ` Seth Goldberg
2011-11-29  7:25     ` Keshav P R
2011-11-29  8:05       ` Seth Goldberg
2011-11-29  9:00       ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-12-02  6:22         ` Keshav P R
2011-12-02  6:53           ` Vladimir 'φ-coder/phcoder' Serbinenko

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=4ED39A59.20503@kiilerich.com \
    --to=mads@kiilerich.com \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).